You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To enable rapid prototyping and calibration of our models, we would like to have:
a way to override any constant value at runtime (above and beyond the declared "input" variables)
a way to override data or lookup variables at runtime
The first one can be implemented similar to how I added support for capturing any variable as an output at runtime (see #105), i.e., generate a big switch statement that allows for overriding any constant value (referenced by "variable index").
The second one can also be implemented in a similar way. I prototyped this in my work-in-progress "generate JS" branch because I needed it for a small model we were working on. I believe that @ToddFincannonEI already has a related branch, so we should put our heads together on this.
I'm lumping these two things together into one feature because we will need to touch the same parts of the compile and runtime package, and it should be easier to implement them together instead of separately.
This will require changes to the code generation phase of the compiler, and will also require improvements and refactoring in the runtime packages.
The text was updated successfully, but these errors were encountered:
I started working on this but realized that it would be better if we divided the work into a few distinct parts, so I changed the focus of this issue to be on the first part only (overriding constants at runtime), and then filed two new issues:
To enable rapid prototyping and calibration of our models, we would like to have:
The first one can be implemented similar to how I added support for capturing any variable as an output at runtime (see #105), i.e., generate a big switch statement that allows for overriding any constant value (referenced by "variable index").
The second one can also be implemented in a similar way. I prototyped this in my work-in-progress "generate JS" branch because I needed it for a small model we were working on. I believe that @ToddFincannonEI already has a related branch, so we should put our heads together on this.
I'm lumping these two things together into one feature because we will need to touch the same parts of the compile and runtime package, and it should be easier to implement them together instead of separately.
This will require changes to the code generation phase of the compiler, and will also require improvements and refactoring in the runtime packages.
The text was updated successfully, but these errors were encountered: