CTF reading routines now GPL
Robert Oostenveld
r.oostenveld at FCDONDERS.RU.NL
Fri Feb 18 15:08:44 CET 2005
On 18 Feb 2005, at 14:26, James Kilner wrote:
> Do you know if the *.m files you sent files can read in the CTF data
> acquired
> with the latest CTF software.
>
> Best, James
Hi James,
:-) Actually I thought about including a statement on that in my
mail, but deleted the line after I typed it.
No, the code that I just posted cannot read the V5 format yet, I
presume that that is what you are referring to with the latest. I did
get some documentation from Brent Taylor (from CTF) describing the
changes, but since we don't have the new software yet here in Nijmegen
and since I also don't have any testdata in the new format, I have not
made any efforts for implementing this new format.
Maybe Tom Holroyd (NIH) can help you out, otherwise you could ask Brent
whether he can give you the documentation for "MEGdefs.h" with which it
should be possible to add support for the new format. Below I have
included a part of the mail that I got from Brent, summarising the
changes in the new format.
best regards,
Robert
On 15 Feb 2005, at 23:41, VSM Customer Support wrote:
> -------
> There is a new file in the dataset, <datasetBasename>.infods, which
> replaces <datasetBasename>.newds (The .newds file is still written,
> but not used.)
>
> There are no changes in record sizes, just changes in values and a new
> field (which was previously reserved) - stimPolarity in
> NewSensorResRec, which replaces the now-deprecated meg41TriggerData
> record.
>
> Regarding changes in values, the single "STIM" channel has been
> replaced with multiple stimulus channels (both analog and digital),
> and one-point (single sample length) triggers are now acceptable. The
> channel name "STIM" is obsolete and replaced by multiple hardware
> stimulus channel names, which may be customized by the user.
>
> A new header identifier, MEG42_TRIG_FMT, in the header of the res4
> file, indicates the new format.
>
> The new MEGDefs.h file is attached (pdf copy), with new fields/values
> indicated (since release 4.16 are bolded; since release 4.17 are
> bolded and italicized).
> -------
More information about the fieldtrip
mailing list