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
We can maintain an old copy of the "result['h3']", and calculate the difference result_diff between current "result['h3']" and the old "result['h3']". We also need "result['countrate'][0]" which comes from the Virtual Instrument copied from the "countrate" recipe.
In the meantime, we consider if "result['countrate'][0]>threslold", then we add that result_diff to the final histogram variable, for live display or file saving. Otherwise we discard result_diff of this section.
I don't understand what i said
The text was updated successfully, but these errors were encountered:
you can simply write a FORMAT_QT_RAW to disk and use it with Lucas' solution as if shutter events are recorded physically
Maybe we can make a generic toolkit to add markers to a histogram and save the markers into memory with FORMAT_QT_RAW. I think the tricky part would be how to get the GUI work.
We can maintain an old copy of the "result['h3']", and calculate the difference result_diff between current "result['h3']" and the old "result['h3']". We also need "result['countrate'][0]" which comes from the Virtual Instrument copied from the "countrate" recipe.In the meantime, we consider if "result['countrate'][0]>threslold", then we add that result_diff to the final histogram variable, for live display or file saving. Otherwise we discard result_diff of this section.
I don't understand what i said
The text was updated successfully, but these errors were encountered: