open-ephys / plugin-GUI

Software for processing, recording, and visualizing multichannel electrophysiology data
https://open-ephys.org/gui
GNU General Public License v3.0
192 stars 684 forks source link

Loading timestamp for electrode in open e-phys #627

Open cellywiththesticks opened 1 week ago

cellywiththesticks commented 1 week ago

Hi all,

I am trying to see what my timestamps looks like in open e-phys for electrode 10. My timestamp files is currently saved as an .npy . Any help will be greatly appreciated!

jsiegle commented 4 days ago

I'd recommend either using open-ephys-python-tools or open-ephys-matlab-tools to load the entire recording. That will automatically load the timestamps for each data stream.

You can also replay the recording in the GUI by dragging the structure.oebin file into the File Reader.

cellywiththesticks commented 3 days ago

Okay, I want to synchronize the timestamps too because they aren’t starting ending at 25 minutes but seem to start at 25 minutes. My experiment runs for 25min but there is a 10 min waiting period where I just press play. However I am not sure what to input in this code that I found on the website. I do not know what TTL line number means, processor ID, or stream name.

recording = session.recordnodes[0].recordings[0]

recording.add_sync_line(8, # TTL line number 102, # processor ID 'Probe-A-AP', # stream name main=True) # use as the main stream

recording.add_sync_line(1, # TTL line number 100, # processor ID 'Probe-A-LFP',# stream name main=False) # align to the main stream

recording.add_sync_line(1, # TTL line number 100, # processor ID 'PXI-6133', # stream name main=False) # align to the main stream

Best, Celine From: Josh Siegle @.> Date: Monday, September 16, 2024 at 1:24 PM To: open-ephys/plugin-GUI @.> Cc: Persad, Celine E. @.>, Author @.> Subject: [EXTERNAL] Re: [open-ephys/plugin-GUI] Loading timestamp for electrode in open e-phys (Issue #627) You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

I'd recommend either using open-ephys-python-toolshttps://github.com/open-ephys/open-ephys-python-tools or open-ephys-matlab-toolshttps://github.com/open-ephys/open-ephys-matlab-tools to load the entire recording. That will automatically load the timestamps for each data stream.

You can also replay the recording in the GUI by dragging the structure.oebin file into the File Readerhttps://open-ephys.github.io/gui-docs/User-Manual/Plugins/File-Reader.html.

— Reply to this email directly, view it on GitHubhttps://github.com/open-ephys/plugin-GUI/issues/627#issuecomment-2353496209, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLIZNKJZSLVNRHS7TNQYG2LZW4H2VAVCNFSM6AAAAABOFX6676VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTGQ4TMMRQHE. You are receiving this because you authored the thread.Message ID: @.***>

jsiegle commented 3 days ago

What type of device did you use to record your data (e.g. Open Ephys Acquisition Board)? Depending on what you used, you may not need to do any additional synchronization.

cellywiththesticks commented 3 days ago

Yes I used the acquisition board but my timestamps start at around 2000 seconds which makes no sense since my recording ends at 25 min

Get Outlook for iOShttps://aka.ms/o0ukef


From: Josh Siegle @.> Sent: Tuesday, September 17, 2024 3:02:10 PM To: open-ephys/plugin-GUI @.> Cc: Persad, Celine E. @.>; Author @.> Subject: [EXTERNAL] Re: [open-ephys/plugin-GUI] Loading timestamp for electrode in open e-phys (Issue #627)

You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

What type of device did you use to record your data (e.g. Open Ephys Acquisition Board)? Depending on what you used, you may not need to do any additional synchronization.

— Reply to this email directly, view it on GitHubhttps://github.com/open-ephys/plugin-GUI/issues/627#issuecomment-2356680909, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLIZNKMZCR5UXY2XZLKETKTZXB4DFAVCNFSM6AAAAABOFX6676VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGY4DAOJQHE. You are receiving this because you authored the thread.Message ID: @.***>

jsiegle commented 3 days ago

The timestamps are always relative to the time you started streaming data, not the time when you started recording. This is so if you start and stop recording multiple times while data continues to stream, all of the timestamps will be aligned to the same start time (i.e., you will know exactly how much time has elapsed between recordings). If you stop data streaming by pressing the "play" button, then the timestamps will reset to 0.

If the recording ends at 25 minutes, the last timestamp should be around 25 * 60 + 2000 = 3500 seconds. Is that what you see?

cellywiththesticks commented 3 days ago

Yes the biggest timestamp does end around there. Thank you!

Best, Celine

From: Josh Siegle @.> Date: Tuesday, September 17, 2024 at 3:47 PM To: open-ephys/plugin-GUI @.> Cc: Persad, Celine E. @.>, Author @.> Subject: [EXTERNAL] Re: [open-ephys/plugin-GUI] Loading timestamp for electrode in open e-phys (Issue #627) You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

The timestamps are always relative to the time you started streaming data, not the time when you started recording. This is so if you start and stop recording multiple times while data continues to stream, all of the timestamps will be aligned to the same start time (i.e., you will know exactly how much time has elapsed between recordings). If you stop data streaming by pressing the "play" button, then the timestamps will reset to 0.

If the recording ends at 25 minutes, the last timestamp should be around 25 * 60 + 2000 = 3500 seconds. Is that what you see?

— Reply to this email directly, view it on GitHubhttps://github.com/open-ephys/plugin-GUI/issues/627#issuecomment-2356760626, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLIZNKLYESH4PFBUJACX3ALZXCBMPAVCNFSM6AAAAABOFX6676VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWG43DANRSGY. You are receiving this because you authored the thread.Message ID: @.***>