Feat/linspace measurements reversed registers divisor

[Nomos11]

just to see how experimental branch differs

[shumpohl]

Move to root examples directory

[shumpohl]

Move to root examples directory

[shumpohl]

Looks good.

[shumpohl]

I reconsidered and remembered I did not put them there for a reason. The idea is that SimpleExpressions are more like context sensitive numbers than expressions.

[Nomos11]

I only needed to move them due to some circular import otherwise i believe. The name might indeed be misleading

[shumpohl]

We should move most program specific stuff out of here

[shumpohl]

Good

[shumpohl]

use chain_transformations or Transformation.chain instead. Or is there a reason you can't?

[Nomos11]

I vaguely remember contemplating to do that or attempting to do that, but uncertain if it did not work for some reason or I just forgot to try it

[shumpohl]

I will resolve this by adding documentation that you should not construct ChainedTransformation directly

[shumpohl]

???

[Nomos11]

I believe this was to further optimize waveform deduplication; i.e. try to reuse waveform data already sampled for one channel for another one. Otherwise the comparison included the channel name which prevented reusage across channels I believe.

The performance increase was minimal and noticeable only in specifically constructed examples, which means it is probably unnecessary

[shumpohl]

What is the purpose?

[Nomos11]

This also was for the "nested stepping", to have a collection of waveforms in a nested structure at hand that would be iterated over with the command table indices

[shumpohl]

Is this still required?

[Nomos11]

I'm not sure; i vaguely remember @maxbeer99 requesting some time reversal features for the T-junction and this was somehow the easiest way to do it, but I'd need to look into the usecase again

[shumpohl]

Ths was probably before the to_single_waveform kwarg was introduced

[Nomos11]

There may have been some other reason i need to think about again

[Nomos11]

no valid reason comes to my mind now so this can probably be discarded

[shumpohl]

My estimate is that the changes that are not directly in linspace.py are roughly a day of work to incorporate into the master branch. Those are:

• The examples (move to hdawg driver)
• Treating simple expression as a proper expression somehow
  • move to expression (trivial)
  • Transformation changes. Here we need to evaluate transformations that contain hardware dependent exprssions. Right now these are by default assumed to be the neutral element of the corresponding operation. The programbuilder is responsible for enusring that this assumption does not brek the program. However this code breaks if the TransformingWaveform is nested.
• Waveform changes (need to understand reasoning and motivation)
• pad_all_atomic_subtemplates_to -> add map_subtemplates function
• ...

[Nomos11]

So as a checkbox list of what the main branch should support:

• DynamicLinearValue with new methods if deemed sufficiently logical; including abs, eq, gt, lt, hash Experiment followup dlv #917
• the linspace-program-specific adaptions that on this branch live in awgs/base.py shift things, prepare move of modified LSB to qupulse_hdawg #918
• alazar.py channel is None convenience alazar channel convenience #916
• program.defined_channels or similar in hardware/setup.py instead of iterator over Loop -> some changes in loop.py required shift things, prepare move of modified LSB to qupulse_hdawg #918 , other compatibility hacks remaining from experiment branch #921
• Albeit hacky on this branch, some way to selectively downsample waveforms by powers of 2 - this can probably not be outsourced to qupules_hdawg. Needed coordination between packages here Linspace followup waveforms #920
• plotting deduplication Plotting constant deduplication #903
• some of the "features" for the supposedly to be outsourced linspacebuilder (->HDAWGBuilder on qupulse_hdawg or so) in the protocol definition in program/init.py? other compatibility hacks remaining from experiment branch #921
• handling of moving this linspacebuilder to qupulse_hdawg for now while ensuring compatibility -> most of the small additions in other files here and there had some usage in there shift things, prepare move of modified LSB to qupulse_hdawg #918 , other compatibility hacks remaining from experiment branch #921
• Transformation chain clarification; contains_sweepval property, trafos handling DLV #919
• waveforms _to_time_type->_to_hardware_time
• WaveformCollection feature in one way or another, Linspace followup waveforms #920
• pad all atomic subtemplates Add more sophisticated padding support and helper functions for that #902
• padding automatically creating atomic pt by default (here the SingleWFTimeExtensionPulseTemplate)
• handle pt.create_program hacks currently living in this method, other compatibility hacks remaining from experiment branch #921
• checked_is_close
• linspace.ResolutionDependentValue (rounding increment commands to bit-values to avoid drift in nD-scans) could actually be included in qupulse if appropriate tests are there, Experiment followup dlv #917
• all integration-tests with the example_checker working

[Nomos11]

these aspects have been split up into disjoints PRs (#914), #916, #917, #918, #919, #920, #921

[Nomos11]

also, #922