Giter Club home page Giter Club logo

Comments (4)

medengineer avatar medengineer commented on July 22, 2024

The timestamps are 64-bit integers that represent the sample numbers relative to the start of acquisition. If you are acquiring data at 40kHz and start recording 10 seconds after starting acquisition, the first timestamp written to disk would be 10 seconds x 40,000 samples / second = 400,000. If you then record for a total of 5 seconds, the final timestamp would be 400,000 + 5 * 40,000 = 600,000. This is why the final timestamp can be greater than the duration of the recording.

The unequal timestamps vs. data is due to using independent buffers to process the different data types (int64 and int16 respectively). The timestamps buffer can stop buffering faster than the data buffer at the end of recording resulting in a few extra data samples. If you have N total recorded timestamps at the end of recording and the first recorded timestamp is exactly the last recorded timestamp minus N, then the N recorded timestamps map directly to the first N samples recorded. If you have any gaps in the timestamps larger than 1 this suggests your computer was not able to keep up with the data processing during recording.

from analysis-tools.

crewl2 avatar crewl2 commented on July 22, 2024

Thank you. I think I understand the timestamps, however, how am I to match the length of data with the length of timestamps? Is the data also int64 or int16? I apologize for the questions, I'm just trying to preprocess my open ephys.dat file and have been struggling to do this via matlab. Any assistance would be appreciated. Thank you!

from analysis-tools.

medengineer avatar medengineer commented on July 22, 2024

The timestamps are int64 and the data is int16. Depending on your recording device there will be a bitVolts value to convert the data from int16 to float representing voltage. To match the timestamps length with the data length, simply discard the extra data samples.

Which version of the GUI was used for these recordings and which device did you record from? (ex: Neuropixels, OpenEphys Acquisition board, etc.). If possible can you attach the settings.xml file from your recording?

from analysis-tools.

crewl2 avatar crewl2 commented on July 22, 2024

Open Ephys v0.5.4 recorded on an Intan Acquisition board.

settings.xml file https://drive.google.com/file/d/1K9TcWSIItE1wfXiAPB211nyhh23HKI7e/view?usp=sharing

from analysis-tools.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.