Currently measure_rate and recording_rate just do a mod on the current sweep and only LocalSweep() increments the sweep counter. This means you can get more recorded configurations/measurements than expected for a given sweep count (i.e. you may measure on a global update which doesn't increment the sweep counter)
I'll probably just increment the sweep counter on every update and let the scheduler do another update when it hits NoUpdate.
Currently measure_rate and recording_rate just do a
modon the current sweep and only LocalSweep() increments the sweep counter. This means you can get more recorded configurations/measurements than expected for a given sweep count (i.e. you may measure on a global update which doesn't increment the sweep counter)I'll probably just increment the sweep counter on every update and let the scheduler do another update when it hits
NoUpdate.