Coder Social home page Coder Social logo

Comments (5)

gidili avatar gidili commented on July 26, 2024

@jrmartin @tarelli @adrianq what do you guys think? I am currently blocked by the above, the way things changed makes it so without the change I suggest (or equivalent) whatever I was doing in the dev branch is not working in datamanager. Any better ideas?

BTW I have the same identical problem on the IVisualTreeFeature interface on this implementation where visulization tree variables where being fished from the recording.

from org.geppetto.core.

jrmartin avatar jrmartin commented on July 26, 2024

I spent some time looking at possibility of adding resutls to Aspect's model wrapper as before, to avoid any changes to interface. Best I thought would be to add ModelWrapper with results to Aspect node before calling the feature, this will have to happen somewhere in RuntimeExperiment.java class. Otherwise, interface change sounds good as well.

from org.geppetto.core.

adrianq avatar adrianq commented on July 26, 2024

@gidili I am not sure if I fully understand your problem. If you are dealing with recordings it is because the simulation is done and we can assume the experiment is finished, right? If so you shouldn't be calling populate simulation tree but the simulation tree should be populate here. I guess you don't have the aspect configurations with the watched variables for the recordings but what you have for sure is the experiment and maybe from there you can call a method like listWatchableVariables(AspectNode aspectNode, Experiment experiment). However I realise that you would still have the problem with the visualisation feature...

That said, I wouldn't move a comma without listening to @tarelli opinion ;)

from org.geppetto.core.

gidili avatar gidili commented on July 26, 2024

@adrianq thanks - we had a chat with @tarelli and I was confused by the fact that we are calling populateSimulationTree in GeppettoManager.updateRuntimeTreesWithResults so I thought it was necessary, but the trees are actually populate already before that call so it would seem it is redundant (I tried commenting it out and everything works so I guess we should take it out). I just have to extend the "createVariables" stuff for the visualisation tree and it should be OK.

Also thanks @jrmartin for you suggestion.

from org.geppetto.core.

tarelli avatar tarelli commented on July 26, 2024

Obsolete post instance type refactoring

from org.geppetto.core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.