-
Notifications
You must be signed in to change notification settings - Fork 1
Egg Structure
Ben LaRoque edited this page Apr 7, 2014
·
1 revision
Each egg file consists of a header which describes the contents, followed by a sequence of records. The records are continuous time series from the digitizer. For situations where a single egg file contains multiple channels worth of data, there are multiple modes for combining the data into the file.
Monarch provides an API for access to the header and the records stored in a file. Because of this, it should not be required for an end user to decode egg files directly. All functionality should be included. If you find a missing functionality, we should discuss implementing it in monarch rather than incorporating it into some other tool.