Open jlashner opened 3 years ago
Easy to change. But my only concern is if some people expect this to be on by default.
After poking around, this feels more logical. I believe the correct way to start streaming data from pysmurf is with stream_data_on(), not set_stream_enable(1). So it feels like a bug that set_stream_enable(1) is in there. In fact, it might be nice to remove set_stream_enable to force usage of stream_data_on, but that's probably not backwards compatible.
Places that are now redundant:
Anywhere with disable_streaming=true: https://github.com/slaclab/pysmurf/search?q=disable_streaming
Places that should enable streaming and already do:
Anywhere with stream_data_on: https://github.com/slaclab/pysmurf/search?q=stream_data_on
Places that should enable streaming but do not:
Anywhere without stream_data_on: ???. This is the only concern. Is there anywhere that assumes streaming after setup().
Describe the bug
During S.setup() pysmurf sets
S.set_stream_enable(1)
to start a stream but never closes it. Because all this data is written to G3 files, this means data will be written indefinitely unless someone turns it off.