-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling of noncontiguous segments in BioPac recordings #279
Comments
@tsalo do you have a file like the one you're describing to see? In any case, let's see a file and decide the course of action (maybe it's easier than expected). |
I have a couple, but they all have identifiable timestamps. I can try to see if I can overwrite the timestamps to make the files shareable. AcqKnowledge does just stitch the time series together, but this hides the missing time. The segments can be accessed, though, in order to see when those breaks occur, although without timestamps there's no way to know how long those breaks are. At least not as far as I know. |
Detailed Description
For multi-run workflows (including the one proposed in #219), the existence of noncontiguous segments (i.e., stopping and starting recording without saving to separate files) can present a problem for identifying runs, as there will be missing time in the overall time series that, at least currently, isn't reflected in the
BlueprintInput
object at all.Context / Motivation
I originally planned to address this in #219, but couldn't figure out an easy solution. BioPac segment time stamps only have second-level resolution, so stitching them together with empty values during the missing time would introduce 1-2 seconds of potential error. Additionally, the time stamps require a bit of customization in order to do, and still must be triggered manually when a new segment is started.
Possible Implementation
I'm not sure. I see three reasonable options:
--//--
).The text was updated successfully, but these errors were encountered: