Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug sampling of Pulse_Sequence objects. #85

Closed
drogenlied opened this issue Feb 2, 2017 · 1 comment
Closed

Debug sampling of Pulse_Sequence objects. #85

drogenlied opened this issue Feb 2, 2017 · 1 comment

Comments

@drogenlied
Copy link
Member

Migration: trac#199.

After merging of the branches the Pulse_Sequence sampling methods are outdated. Step through the process and make it work properly. Take the sample_pulse_block_ensemble method as example. The conventions used there (channel identification etc.) are a good starting point.
This is mainly concerning sequence_generator_logic.py and samples_write_methods.py.

Works with current version after commit 80a1811 but is still written in a not very good way.

@Neverhorst
Copy link
Member

Works now in a stable and good way (v0.7). If there are more issues related to the sampling of pulse sequences, one needs to open a more specific issue for that.

The convention is currently as follows:
If the rotating frame should be preserved across PulseBlockEnsembles within a sequence, the created waveform filenames are composed of "sequencename_3digitnumberofstep_channelspecifier.fileformat" (i.e. "testseq_001_ch1.wfm")
If rotating frame is only maintained within the PulseBlockEnsembles (or not at all) the waveform filenames are called the same as when you sample the ensemble alone. (i.e. "ensemblename_ch1.wfm").
All created waveforms are uploaded to the device as soon as they are created and the sequence file itself is created and uploaded last.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants