You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the SUServo gateware/driver assume that there are two Urukuls per servo instance, and one Sampler. This isn't unreasonable, as it corresponds to 8 ADC channels and 8 DDSes.
However, in typical experiments, many laser beamlines will end up having more than one wavelength/frequency component, and hence on average more than one DDS channel per ADC channel.
We already support choosing the source ADC channel for each profile, so support for an unequal number of ADC and DDS channels should not be too hard to add.
@jordens: Any comments regarding this? I had a quick look at splitting w.channel into w.adc_channel and w.dds_channel, and it doesn't seem too bad, but I'm not sure whether I've noticed all the intricacies of the pipelined design.
The text was updated successfully, but these errors were encountered:
Currently, the SUServo gateware/driver assume that there are two Urukuls per servo instance, and one Sampler. This isn't unreasonable, as it corresponds to 8 ADC channels and 8 DDSes.
However, in typical experiments, many laser beamlines will end up having more than one wavelength/frequency component, and hence on average more than one DDS channel per ADC channel.
We already support choosing the source ADC channel for each profile, so support for an unequal number of ADC and DDS channels should not be too hard to add.
@jordens: Any comments regarding this? I had a quick look at splitting
w.channel
intow.adc_channel
andw.dds_channel
, and it doesn't seem too bad, but I'm not sure whether I've noticed all the intricacies of the pipelined design.The text was updated successfully, but these errors were encountered: