-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
refactor: change SCCNonlinearProblem
fields
#884
Conversation
093ba15
to
7f8c129
Compare
SciMLSensitivity/Core5 failure seems random and unrelated, the failing test passed locally. |
c6268c8
to
e8238e2
Compare
e8238e2
to
1dcbd1f
Compare
parameter_object::Par | ||
# NonlinearFunction with `f = Returns(nothing)` | ||
f::F | ||
p::Par |
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.
wait what is this p
? How does it relate to the actual p
of the probs
?
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.
This p
is the parameter object for SII. Since the parameter object is not guaranteed to be identical for all problems, the user can provide one that SII will use and that prob.f.observed
will codegen for. There's a flag if all problems share the same parameter object, which aliases prob.p
and functions like set_parameter!
take advantage of this.
if u0 === missing && p === missing | ||
return state_values(prob), parameter_values(prob) | ||
end | ||
if indp === nothing | ||
if prob.f.sys === nothing |
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.
this line causes SciML/Integrals.jl#259
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.
Checklist
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
Additional context
Add any other context about the problem here.