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
The tutorial: https://docs.sciml.ai/ModelingToolkit/stable/examples/remake/ is very useful for understanding the new parameter setup, but it would be nice if it could show a way for users to specify an initial guess for the optimizer via a parameter mapping, and/or specify the lb and ub bounds via one. Right now it isn't clear how a user can figure out the tunable parameter ordering, and hence they wouldn't easily know which components of lb and ub correspond to which parameters. While this can be done by inspection of tunable_parameters(sys), it seems like a more MTK consistent workflow would be to have a varmap_to_vars equivalent that takes a mapping of tunable_parameters to values, and a parameter object (or system?), and returns a vector of the parameter values that is consistent with canonicalize and replace!.