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
When (accidentally or intentionally) calling methods such as update_parameters before any measurements have been called (ie before the WorkerScriptManager instance has had a pulse_sequence_name parameter specified in any way), errors and/or undefined behaviour occurs.
The expected result should be that the processing of the methods should still be carried out. Potentially, doing so without specifying a pulse sequence name prior could issue a warning depending on the specific method in question.
The text was updated successfully, but these errors were encountered:
Original report by Samuel Wolski (Bitbucket: 557058:90b732eb-6ab1-4b27-9495-eb00eafde259, GitHub: samwolski).
When (accidentally or intentionally) calling methods such as
update_parameters
before any measurements have been called (ie before the WorkerScriptManager instance has had apulse_sequence_name
parameter specified in any way), errors and/or undefined behaviour occurs.The expected result should be that the processing of the methods should still be carried out. Potentially, doing so without specifying a pulse sequence name prior could issue a warning depending on the specific method in question.
The text was updated successfully, but these errors were encountered: