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
(This is not really an issue, more of a consideration.)
The post_{implicit, explicit}! functions are called with signature: (u, p, t). Therefore, if the post_ function wants to use the value of the timestep dt, that has to be included in p. Now, in my opinion, this is a bit dissatisfying because I think that the integrator should own dt and be responsible for it. Hard-coding dt in p introduces a potential mode of failure in which the dt in the integrator and the dt in p disagree on the value of the timestep.
The text was updated successfully, but these errors were encountered:
(This is not really an issue, more of a consideration.)
The
post_{implicit, explicit}!
functions are called with signature:(u, p, t)
. Therefore, if thepost_
function wants to use the value of the timestepdt
, that has to be included inp
. Now, in my opinion, this is a bit dissatisfying because I think that the integrator should owndt
and be responsible for it. Hard-codingdt
inp
introduces a potential mode of failure in which thedt
in the integrator and thedt
inp
disagree on the value of the timestep.The text was updated successfully, but these errors were encountered: