Describe the bug
Originally reported by @mavel101 from #45:
The set_definition function accepts an integer as value, but in the write_seq an integer is only accepted as part of a list, tuple or ndarray not as a single integer. Changing this line in the write_seq:
If not, isolate the bug to a particular pulse sequence event by iteratively writing/plotting the sequence one event at a time.
If the sequence successfully writes/plots with individual pulse sequence events, isolate the bug by writing/plotting the sequence by successively adding events.
Desktop (please complete the following information):
Describe the bug Originally reported by @mavel101 from #45: The
set_definition
function accepts an integer as value, but in thewrite_seq
an integer is only accepted as part of alist
,tuple
orndarray
not as a single integer. Changing this line in thewrite_seq
:to
would solve this.
To Reproduce
Desktop (please complete the following information):
pypulseq
version: 1.3.1