Integer definitions are missed in write_seq.py

[sravan953]

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:

elif isinstance(values[block_counter], float):
                output_file.write(f'{values[block_counter]:0.9g} ')

to

elif isinstance(values[block_counter], (int,float)):
                output_file.write(f'{values[block_counter]:0.9g} ')

would solve this.

To Reproduce

• Share the pulse sequence code, if possible.
• 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):

• pypulseq version: 1.3.1