Closed jlashner closed 3 years ago
I'm tempted to just discard the G3PipelineInfo frame here which I think would solve the problem: https://github.com/simonsobs/socs/blob/5324b0768526bf427fdf5c13d7932f3551ef2f83/socs/agent/smurf_recorder.py#L263
Does anyone think we need to be saving the pipeline info frame?
Fine by me.
Are you setting a default stream_id with the --stream-id
argument to the Agent? That argument is used if there isn't one in the frames. That should at least prevent you from ending up with "None" in this case.
Sometimes the smurf-recorder is setting the stream-id component in the data path to None even if there is a stream-id present in the frames. I think it does this when it receives the PipelineInfo frame at the start, since that doesn't have the
sostream_id
key.For example, on the Penn system the file /data/timestreams/16022/None/1602279295_000.g3 contains the following frames: