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
Do I understand correctly that you want to raise an error/warning when one runs a TimeDriver in the absence of system.dynamics term(s)?
Yes, you understand correctly
Also, what exactly do you mean by "nothing happens"? Do you mean that system.m does not update or the simulation continues endlessly? system.m does run but the inital state does not change after TimeDriver as system.dynamics were not mentioned.
Should we raise an error/warning if OOMMF is OK with running a time driver with no dynamics term?
I am leaning towards raising a warning. I think raising an error would be too strong a stance. Does this sound reasonable?
If we implement this in oommfc, it would good to know what mumax3 does in such a situation and maybe raise an error/warning in mumax3c as well for consistency. Does this sound reasonable?
The simulation "runs" but nothing happens.
The text was updated successfully, but these errors were encountered: