search

qipe-nlab / Labber-PSICT

The Pulse-Sequence Instrument Control Tool. Developing scripts to allow string-based input to Labber for more flexible control over pulse sequence configurations.
MIT License
3 stars 1 forks source link

Cannot use pulse 'spacing' parameter for iterations #5

Open SamWolski opened 5 years ago

SamWolski commented 5 years ago

Original report by Samuel Wolski (Bitbucket: 557058:90b732eb-6ab1-4b27-9495-eb00eafde259, GitHub: samwolski).

Due to the pulse timing calculation architecture having been built without properly handling iteration parameters, the pulse spacing is overwritten by the conversion from input to output pulse sequence (line 612 in PulseSequence.py on version 1.1.1.1). As this is carried out after all parameters (including iteration variables) are stored in the psictUIFInterface hierarchy, it is not possible to remedy this in the external script.

The workaround is simply to use a Manual value as the iteration and link it directly to the pulse spacing with a channel relation. Due to the ease and effectiveness of this workaround, as well as the fact that the bug arises from a fundamental architectural issue, this is rather low-priority for now.

SamWolski commented 5 years ago

Original comment by Samuel Wolski (Bitbucket: 557058:90b732eb-6ab1-4b27-9495-eb00eafde259, GitHub: samwolski).

This issue is planned to be resolved when we overhaul the SQPG/pulse-parameter-specification backend to allow for more direct manipulation of SQPG parameters within the SQPG/Labber restrictions. This will not be released earlier than v2.0.