Trigger for scope and camera with software timestamps

[ChucklesOnGitHub]

Until the TTL output is resolved for more precise hardware timestamping with an external clock, it could still be good to have a simple software timestamping approach to sync a camera and a scope like this #50, and one based on an external hardware trigger. Building on this, could the DAQ's external trigger be used to gate the camera acquisition too?

I've made an attempt here:

demo-miniscope-trigger-save-camera.zip

I tested it and it works, but I'd appreciate a review before writing the tutorial since I'm not sure the logic correct/simplest.

[cjsha]

try this workflow logic.

demo-miniscope-trigger-save-camera_cs.zip

i haven't tested it with a second camera, so make sure you take a close look that it works. also I would of course rename some of the nodes so they names are more helpful before publishing. For example I named one "wah", sorry about that. Also make sure that the videowriter and whatnot properties are as you want, because I probably accidentally changed those in the process.

[ChucklesOnGitHub]

demo-miniscope-trigger-save-camera_cs-ch.zip

This generates the amount of files expected each time the trigger signal is HIGH.
The start and end timestamps reported for both the miniscope and camera files match.

Same comment applies. I think this is publishable, but two things:

• Given that there are nested workflows, should we externalize the data writer properties so they are exposed in the outmost worfklow and easy to change?
• Can we tie the miniscope frame rate property to the videowriter property for ease of use? And for the camera I used 30 but maybe we should comment on it