In the pulsed toolchain any uploaded PulseSequence from predifined methods does not show its own generation_method_parameters but rather the parameters of a former uploaded 'PulseBlockEnsemble'. This leads to false saving of the generation method paramters in the Metadata.
When does the bug occur?
The bug occurs when uploading predefined methods written as PulseSequences, e.g. t1_seq.
How do we replicate the issue?
-Upload any predefined method written as PulseSequence, e.g. t1_seq
-Check in the console the pulsed_measurement_logic.generation_method_parameters
Expected behavior
The generation method parameters should match.
Relevant log output
No response
Additional Comments
I think the issue is resolved when adding for sequences in the sequence_generator_logic in the method generate_predefined_sequence: sequence.generation_method_parameters = kwargs_dict just as for ensembles.
Version
current main
What is affected by the bug?
In the pulsed toolchain any uploaded
PulseSequencefrom predifined methods does not show its owngeneration_method_parametersbut rather the parameters of a former uploaded 'PulseBlockEnsemble'. This leads to false saving of the generation method paramters in the Metadata.When does the bug occur?
The bug occurs when uploading predefined methods written as PulseSequences, e.g.
t1_seq.How do we replicate the issue?
-Upload any predefined method written as PulseSequence, e.g.
t1_seq-Check in the console thepulsed_measurement_logic.generation_method_parametersExpected behavior
The generation method parameters should match.
Relevant log output
No response
Additional Comments
I think the issue is resolved when adding for sequences in the
sequence_generator_logicin the methodgenerate_predefined_sequence:sequence.generation_method_parameters = kwargs_dictjust as for ensembles.Contact Details
No response