In the current version, the timestream aggregator would always write files of the configured length (default 1 hr). This would cause multiple operations which may produce other timestamped files, like tuning files, to end up in a single .g3 file. To make it convenient for the user to associate .g3 files on disk with other files produced at the same time we should start new files for each acquisition.
In the current version, the timestream aggregator would always write files of the configured length (default 1 hr). This would cause multiple operations which may produce other timestamped files, like tuning files, to end up in a single .g3 file. To make it convenient for the user to associate .g3 files on disk with other files produced at the same time we should start new files for each acquisition.