[Eeglablist] ANT import and elc

Mon Mar 7 02:33:18 PST 2011

Dear Beth and others,

Attached is a function readasalocs that can be used as a dedicated 
electrode locations reader for the ASA electrode file format.

EEGLAB development team, feel free to test / debug / rewrite / integrate 
this function for use in future versions of EEGLAB. Note that EEtrack 
files can also be read with this importer. Please contact me in case you 
need more files to test with.

Kind regards,
ruud

Am 04/03/2011 15:31, schrieb ruud kalis:
> Dear Beth and Balaji,
>
> Balaji's approach works fine to create a new electrode file that is
> similar to the recording montage that you use in ASA. Thanks for
> suggesting this. I've noticed, however, that the channel location
> importer requires a slightly different .elc file format: removing column
> 1 from the positions matrix, this is column contains the channel labels.
> This way your electrode files can be imported without errors.
>
> So use:
> NumberPositions=    3
> UnitPosition    mm
> HSPTransformed    false
> Positions
> 94.9    30.7    14.0
> 96.4    -31.5    14.1
> 98.3    -0.2    18.6
> Labels
> FP1    FPZ    FP2
>
> Instead of:
> NumberPositions=    3
> UnitPosition    mm
> HSPTransformed    false
> Positions
> FP1:    94.9    30.7    14.0
> FP2:    96.4    -31.5    14.1
> FPZ:    98.3    -0.2    18.6
> Labels
> FP1    FPZ    FP2
>
> Possible cause for this error:
>
> the .elc importer (a function called readeetraklocs) is written in 2003
> for the EETrak file format. EETrak was a digitizer software that ANT
> replaced with an improved electrode digitizer called Xensor
> (http://www.ant-neuro.com/products/xensor). The files that were written
> by EETrak didn't contain the channel labels before the 3D position. In
> fact you could write anything in front of the 3D position as long as it
> is separated with a colon (:), ASA will still be able to read that
> electrode file, since it uses the labels that are defined at the end of
> the file.
>
> Something similar was also reported by Sara Graziado in november 2010
> and filed as EEGLAB bug 956.
>
> Arno&  Dev, the parsing of the .elc file could be improved in
> readeetraklocs, taking the colon-separation into account. Better would
> be a function readasalocs. For this, you could use the 'delim' key for
> loadtxt with val [9 32 58] which are the ASCII symbols for spaces, tabs
> and colons. I'm currently working on that readasalocs function and hope
> to post it before the end of today or otherwise beginning of next week.
>
> Kind regards,
> ruud kalis
>
> Am 03/03/2011 21:05, schrieb Lakshmanan, Balaji:
>> Hi Beth,
>>
>> You can maybe try this.
>> Export(Data-->Write-->electrodes) the .elc file from ASA after you adjusted your recording montage and try importing this .elc file in to EEGLAB.
>> I have not done this but probably should work.
>>
>> Balaji
>>
>> -----Original Message-----
>> From: eeglablist-bounces at sccn.ucsd.edu [mailto:eeglablist-bounces at sccn.ucsd.edu] On Behalf Of Beth Smith
>> Sent: Wednesday, March 02, 2011 2:34 PM
>> To: 'eeglablist'
>> Subject: Re: [Eeglablist] ANT import and elc
>>
>> While we are on the topic of ANT caps and channel locations in EEGlab, I want to mention my current situation. The .elc file I have from ANT for the standard 32-channel waveguard cap contains the 3d-locations of the channels with 35 positions and 35 labels. But if I adjust the recording montage in ANT, then I believe the import into EEGLab mislabels my channels. I am collecting in ANT and then using EEGlab import function to import the ANT data from their .cnt and .trg files. Next I import locations from the .elc file. But when I plot data, I believe it assigning channel names based on a standard order of channel numbers in the .elc file that does not match the recording montage I have specified in ANT, leading to mislabeling of channel names in EEGLab. Has anyone else experienced this problem that can confirm this?
>>
>> Much thanks, Beth
>>
>> Beth A. Smith, PT, DPT, PhD
>> Postdoctoral Fellow
>> OHSU Balance Disorders Lab
>> ________________________________________
>> From: eeglablist-bounces at sccn.ucsd.edu [eeglablist-bounces at sccn.ucsd.edu] On Behalf Of Haass, Michael Joseph [mjhaass at sandia.gov]
>> Sent: Monday, February 28, 2011 3:22 PM
>> To: 'eeglablist'
>> Subject: Re: [Eeglablist] ANT read_eep_cnt 64 bit version
>>
>> Thanks for sharing this Balaji, I was just now looking for this same thing!
>>
>> Does anyone have a channel locations file for ANT's waveguard DUKE 128 cap?
>>
>> Thanks,
>> Haass
>>
>> From: eeglablist-bounces at sccn.ucsd.edu [mailto:eeglablist-bounces at sccn.ucsd.edu] On Behalf Of Lakshmanan, Balaji
>> Sent: Friday, February 25, 2011 8:55 PM
>> To: Arnaud Delorme
>> Cc: eeglablist
>> Subject: Re: [Eeglablist] ANT read_eep_cnt 64 bit version
>>
>> Hi Arnau,
>>
>> They did send me the 64bit compiled version(see attached). It is also available in their website(http://www.ant-neuro.com/download/misc).
>> I think this works for 32bit version also.. so you can replace the older version with this.
>>
>> Thanks!
>> Balaji
>>
>> ________________________________
>> From: Arnaud Delorme [arno at ucsd.edu]
>> Sent: Friday, February 25, 2011 9:38 PM
>> To: Lakshmanan, Balaji
>> Cc: eeglablist
>> Subject: Re: [Eeglablist] ANT read_eep_cnt 64 bit version
>> Dear Balaji,
>>
>> unfortunately, the plugin was developed by ANT and contains some proprietary code so they would need to recompile their code.
>> Please let us know if ANT sends you a function and we will update EEGLAB.
>> If you are a 64-bit ANT user, send them an email at support at ant-neuro.com<mailto:support at ant-neuro.com>. Maybe if they receive several emails, they will do something about it.
>> Best regards,
>>
>> A. Delorme
>>
>> On Feb 24, 2011, at 12:17 PM, Lakshmanan, Balaji wrote:
>>
>>
>> Hi  EEGLAB users/ANT support,
>>
>> I'm not able to read *.cnt files from ANT system using EEGLAB.
>> It was working fine in my 32bit MATLAB but stopped working when I upgraded to 64 bit.
>> I'm using the most current version of EEGLAB.( eeglab9_0_4_5s).
>>
>> I guess this might be due to 32bit compiled version of .mex file? Is it possible to get a 64bit compiled version of the mex file for the function read_eep_cnt.m?
>>
>> Thanks,
>> Balaji
>>
>>
>>
>> Disclaimer:
>> The materials in this e-mail are private and may contain Protected Health Information. Please note that e-mail is not necessarily confidential or secure. Your use of e-mail constitutes your acknowledgment of these confidentiality and security limitations. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender via telephone or return e-mail. _______________________________________________
>> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
>> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu<mailto:eeglablist-unsubscribe at sccn.ucsd.edu>
>> For digest mode, send an email with the subject "set digest mime" to eeglablist-request at sccn.ucsd.edu<mailto:eeglablist-request at sccn.ucsd.edu>
>>
>>
>> _______________________________________________
>> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
>> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu
>> For digest mode, send an email with the subject "set digest mime" to eeglablist-request at sccn.ucsd.edu
>>
>> _______________________________________________
>> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
>> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu
>> For digest mode, send an email with the subject "set digest mime" to eeglablist-request at sccn.ucsd.edu

-- 
Ruud Kalis
Product Manager
ANT (Advanced Neuro Technology)
eemagine GmbH, Berlin, Germany
T: +49 (0)30 2904 8404
F: +49 (0)30 2904 8405
I: www.ant-neuro.com
===
This message, including attachments, may contain confidential information that is proprietary and/or legally privileged. If you are not an intended recipient, or a person responsible for delivering it to the intended recipient, please notify the sender and then delete and destroy the original message and all copies. You should not copy, forward, or disclose this message, in whole or in part, without permission of the sender. Thank you for helping us to maintain the confidentiality of this information.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: readasalocs.m
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20110307/714afbd9/attachment.ksh>