Data for SMuRF is maximally available at the flux ramp frequency. Previously, SMuRF could only use its internal "downsampler counter" where it ignores some of the incoming data until the counter is reached. This code change adds the ability for SMuRF to look at external timing bits from the SMuRF timing hardware to decide when to save data. I note that there are two places where SMuRF data is downsampled: at the firmware layer, and here at the software layer. The firmware layer does averaging of its data, but here the data is not averaged. The software downsampling simply drops the unused frames.
Data for SMuRF is maximally available at the flux ramp frequency. Previously, SMuRF could only use its internal "downsampler counter" where it ignores some of the incoming data until the counter is reached. This code change adds the ability for SMuRF to look at external timing bits from the SMuRF timing hardware to decide when to save data. I note that there are two places where SMuRF data is downsampled: at the firmware layer, and here at the software layer. The firmware layer does averaging of its data, but here the data is not averaged. The software downsampling simply drops the unused frames.