-
-
Notifications
You must be signed in to change notification settings - Fork 119
feat: add get_updated_symbolic_problem
#1141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add get_updated_symbolic_problem
#1141
Conversation
Should do the same in |
Wouldn't that do double the work for algorithms that call |
No it won't because of how the problems recurse. But I just realized that where this makes sense is actually in |
Wouldn't |
Well this is updating the u0 though? But yes, it's part of the concretization process. |
src/solve.jl
Outdated
prob | ||
end | ||
|
||
function get_concrete_problem(prob::SteadyStateProblem, isadapt; kwargs...) | ||
p = get_concrete_p(prob, kwargs) | ||
u0 = get_concrete_u0(prob, isadapt, Inf, kwargs) | ||
u0 = promote_u0(u0, p, nothing) | ||
remake(prob; u0 = u0, p = p) | ||
prob = remake(prob; u0 = u0, p = p) | ||
get_updated_symbolic_problem(_get_root_indp(prob), prob) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this after the remake and promotions? This should go up before promote_u0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh hm. Yeah in my head I thought if we do it after promotions MTK knows the type to use but of course that is backward. We should let MTK populate the values and then promote to the correct type after.
…m` instead of `init_call`
2f527fa
to
8140ed7
Compare
Is there a better place to call this than
init_call
?