Back to the main page.

Bug 2238 - read in and segment Netstation data

Reported 2013-08-08 23:39:00 +0200
Modified 2019-08-10 12:02:59 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P3 normal
Assigned to: Diego Lozano Soldevilla
Depends on:
See also:

Anne van Hoogmoed - 2013-08-08 23:39:31 +0200

I'm reading in and segmenting Netstation data. However, the trials seem shifted in FT. I've attached a picture of the same trial in Netstation and Fieldtrip. The waveforms above the red lines look the same, but in NS they are at the end of the trials, while in FT they are at the beginning of the trial. I've checked several things: - The timing of the events is the same in NS and FT - The raw data are the same - FT seems to produce the right trl - In NS, the triggers are in the same place in the raw and segmented data, so the error seems to be in FT. Thanks for looking into this! Anne PS. I can't get the files uploaded here, so since Diego said he'd look into it, I sent the files directly to him

Diego Lozano Soldevilla - 2013-08-09 08:28:41 +0200

Data received!

Gio Piantoni - 2013-08-09 14:53:25 +0200

Hi, I was wondering if the problem is related to this bug report: Can you check if epochs.xml contains a discontinuity, like: 0 1351000000 1 1 1801000000 573676000000 2 141 If that's the case, can you check if you have "epochs.xml" (and not "epoch.xml") in the dataset? I need to fix this issue ( ) but it's been a very busy period for me. I don't know if this is related to your problem though. HTH, g

Diego Lozano Soldevilla - 2013-09-23 23:21:31 +0200

Anne wrote that the error is in Netstation: Hi Diego, I just wanted to update you on the Fieldtrip issue I was having. It seems to be more of a Netstation problem, so the people who created the software are now looking into this. Thank you very much for your help! Best, Anne

Robert Oostenveld - 2019-08-10 12:02:59 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on