JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for NEUROMEG Archives


NEUROMEG Archives

NEUROMEG Archives


NEUROMEG@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

NEUROMEG Home

NEUROMEG Home

NEUROMEG  August 2008

NEUROMEG August 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Change digitised HPI points in raw .fif file ?

From:

Marie Smith <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 27 Aug 2008 13:06:32 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

Hi,

Thanks a lot for this advice.

I have now been able to obtain a successful hpi fit both using the  
three good coils, and inputting the second digitisation with the  
recorded data from the first. In both cases this results in a much  
more sensible device-head transformation matrix. I think with this  
correct transformation matrix (close to identity for rotation and  
translation close to 0,0,40 (-7 0.5 51) that i can now trust the  
results of SSS and trans -default. Is this correct?

However, i still have a problem. When i try to perform maxmove  
compensation the hpi fits still fail. I guess from looking at the file  
that its because the incorrect initial digitised hpi information is  
still in there (though it tells me that its ignoring the incorrect  
coil information). So i'm still wondering if there is some way to copy  
the second set of isotrak points values into the raw fif file, such  
that maxfilter would then compute fits from them during maxmove?

Thanks again,

Marie

Quoting Dionyssios Theofilou <[log in to unmask]>:

> Hello Marie,
>
> Yes, it is possible to tell maxfilter to ignore the incorrect coil and
> work only with the other three. (In fact only three of the coils are  
>  always used).
> To tell the hpifit program to try a different selection of the   
> necessary coils
> you must use the –swap option. For example:
>
> … /dacq/bin/hpifit  -file  <my_troubled_file.fif>  -swap 1234
>
> will try to select first the electrode 1, then the 2, and at the end  
>  the electrode 4.
>
> … /dacq/bin/hpifit  -file  <my_troubled_file.fif>  -swap 3142
>
> will try to select first the electrode 3, then the 1, and at the end the 2.
>
> You will have to use also the show_fiff command, for example:
>
> … /bin/util/show_fiff  -v  -t  222  <my_hpi_coils.fif>
>
> The copy_trans_fiff command, for example:
>
> … /bin/util/copy_trans_fiff  -f  <my_hpi_coils.fif>  <my_test_coils.fif>
>
> And perhaps also the copy_pos_fif command.
>
> (Use the –help option with all these commands for more details).
>
> I hope that this has helped,
>
> My Best,
> Dionyssios.
>
>
>> Hi,
>>
>> I was wondering if anyone could suggest how to go about changing the
>> stored HPI coil positions from digitisation in a continuous fif data file?
>>
>> We recently recorded a data set in which the digitized coil location of
>> one coil is incorrect and this causes HPI fitting in maxfilter to fail
>> (the coil fits are fine, just the distances are too big 80-100mm). I've
>> tried maxfiltering with the -hpicons tag, and although this tried to
>> correct the deviant coil position, the HPI fits still fail. Luckily, we
>> re-digitised the positions of the coils after recording and would like to
>> use these correct coil location points in the original raw file. Does
>> anyone know if how to go about doing this? Or is there is any way to tell
>> maxfilter to ignore the one coil location thats incorrect and work with
>> the other three?
>>
>> Any advice and/or suggestions would be greatly appreciated.
>>
>> Thanks,
>>
>> Marie
>>
>>
>>
>> --
>>
>>
>



------------------------------------------------------------------
The University of Glasgow, Department of Psychology WebMail system
------------------------------------------------------------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
May 2023
January 2023
March 2022
January 2022
December 2021
November 2021
May 2021
September 2020
August 2020
July 2020
May 2020
April 2020
January 2020
December 2019
June 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
November 2017
October 2017
September 2017
August 2017
March 2017
December 2016
September 2016
July 2016
April 2016
January 2016
August 2015
July 2015
June 2015
March 2015
December 2014
August 2014
May 2014
April 2014
January 2014
December 2013
November 2013
October 2013
September 2013
June 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
July 2012
May 2012
March 2012
February 2012
September 2011
July 2011
June 2011
May 2011
April 2011
March 2011
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
February 2010
January 2010
December 2009
November 2009
October 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
March 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager