extend pad_to to pad_to_all_atomic_subtemplates

[Nomos11]

to increase convenience even more, the pad_to could be called from the top-level-pt to extend all atomic subtemplates to adhere to awg-specifications.
This is e.g. outlined in branch feat/linspace_measurements and should be simple to implement

qupulse/qupulse/pulses/pulse_template.py

Line 442 in 6facb1f

def pad_all_atomic_subtemplates_to(self,

Potentially for 1.0?
In that regard however, the PT time-extended in this manner should by default be translated into a single waveform, otherwise the convenience gets lost again.

[Nomos11]

also the padding should allow to create the pulse as a single waveform,otherwise the convenience is lost
maybe by inheriting from atomicPT?

qupulse/qupulse/pulses/time_extension_pulse_template.py

Line 22 in 6facb1f

class SingleWFTimeExtensionPulseTemplate(AtomicPulseTemplate):

[shumpohl]

Everything AWG specific should go into create_program if possible. Can you give a usecase?

In that regard however, the PT time-extended in this manner should by default be translated into a single waveform, otherwise the convenience gets lost again.

Do you mean the root PT? Where is then the difference to pad_to(..., to_single_waveform=True)?

[Nomos11]

But is to_single_waveform=True available on the master branch currently? it seems that a sequencePT is created when kwargs are provided (what does to_single_waveform do then?). Probably I don't understand it right now.

The usecase would be that I could imagine the user assuming this "padding" functionality to fix the awg quanta issue by extending the "same PT" object that the function is called on, but right now (maybe I'm missing the decisive step) a SequencePT is created which by default will be translated to two waveforms unless specified explicitly in create_program's to_single_waveform, which seems clumsy (?) for many pulses

[shumpohl]

But is to_single_waveform=True available on the master branch currently?

Touché. One neat hack would be to add to_single_waveform as a PulseTemplate.__init__ key word argument. I will make an issue for that.

The usecase would be that I could imagine the user assuming this "padding" functionality to fix the awg quanta issue by extending the "same PT" object that the function is called on, but right now (maybe I'm missing the decisive step) a SequencePT is created which by default will be translated to two waveforms unless specified explicitly in create_program's to_single_waveform, which seems clumsy (?) for many pulses

One solution is to add a wavefrom padding functionality to create_program. However, this breaks any duration dependent code, i.e. when you do

pt = some_pt()
other_pt = some_other_pt(pt.duration) @ pt

and the correctness of other_pt depends on the exact value of pt.duration. It is very hard/impossible to detect this automatically with the current design. Another question is wether this functionality should go into the pulse template or in the program builder code. I argue for pulse template so we can be sure that all program builders (linspace, plotting, measurement) work with the same waveform lengths.