-
Notifications
You must be signed in to change notification settings - Fork 29
Feat/linspace measurements reversed registers divisor #901
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
base: master
Are you sure you want to change the base?
Feat/linspace measurements reversed registers divisor #901
Conversation
for freeing up register(<->depkey) once loop ends
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move to root examples directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move to root examples directory
qupulse/expressions/simple.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only needed to move them due to some circular import otherwise i believe. The name might indeed be misleading
qupulse/hardware/awgs/base.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should move most program specific stuff out of here
qupulse/hardware/dacs/alazar.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good
parsed.extend(t.transformations) | ||
else: | ||
parsed.append(t) | ||
self._transformations = tuple(parsed) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use chain_transformations or Transformation.chain
instead. Or is there a reason you can't?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will resolve this by adding documentation that you should not construct ChainedTransformation directly
""" | ||
|
||
def _hash_only_subset(self, channel_subset: Set[ChannelID]) -> int: | ||
"""Return a hash value of this Comparable object.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
|
||
|
||
|
||
class WaveformCollection(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
|
||
|
||
class AtomicTimeReversalPulseTemplate(AtomicPulseTemplate): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still required?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ths was probably before the to_single_waveform
kwarg was introduced
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There may have been some other reason i need to think about again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no valid reason comes to my mind now so this can probably be discarded
My estimate is that the changes that are not directly in
|
So as a checkbox list of what the main branch should support:
|
just to see how experimental branch differs