I'm trying to specify multiple event codes in a category for averaging and
can't figure out the syntax for doing so. What I've tried is below. How
does one do this?
category {
name "Category 1"
event 11 12 13 21 22 23 31 32 33
# event 12
# event 13
# event 21
# event 22
# event 23
# event 31
# event 32
# event 33
tmin -0.1
tmax 0.7
color 0.91 0.47 0.09
}
category {
name "Category 2"
event 10 20 30
# event 20
# event 30
tmin -0.1
tmax 0.7
color 0.075 0.61 0.93
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20120221/1a626873/attachment.html
As far as I know this, the only way to do this is to rewrite the events in
your event file. For instance, to average events 10, 20, and 30 together,
you can get the event files for each subject and use some sort of script
(or even just find-and-replace in your text editor) to replace every
instance of 10, 20, or 30 with some other event number (such as "102030" or
whatever name you like). You can then do the same for any other events you
want to combine in a separate condition (e.g., events 11, 12, 13, 21, 22,
23, 31, 32, 33 might all be replaced with some different name). Then save
the file(s) and use those event files and the new numbers when averaging.
To do different combinations of triggers, you can just repeat the whole
process, just rewriting the events in some other way when you edit the
event files.
That's great news, this sounds like it'll be much easier than rewriting
event files! Just out of curiosity, does this also work with
mne_process_raw in batch mode (with .ave or .cov definition files)?
That's great news, this sounds like it'll be much easier than rewriting event files! Just out of curiosity, does this also work with mne_process_raw in batch mode (with .ave or .cov definition files)?
Yes, this applies to the ave and cov files.
- Matti
Best,
Steve Politzer-Ahles
Hi Andrew,
The mne_browse_raw in the nightly build of MNE now available on the web site you can specify
event 11
event 12
etc.
within a category to have multiple events averaged together.
- Matti
> Hi all,
>
> I'm trying to specify multiple event codes in a category for averaging and can't figure out the syntax for doing so. What I've tried is below. How does one do this?
>
> category {
> name "Category 1"
> event 11 12 13 21 22 23 31 32 33
> # event 12
> # event 13
> # event 21
> # event 22
> # event 23
> # event 31
> # event 32
> # event 33
> tmin -0.1
> tmax 0.7
> color 0.91 0.47 0.09
> }
> category {
> name "Category 2"
> event 10 20 30
> # event 20
> # event 30
> tmin -0.1
> tmax 0.7
> color 0.075 0.61 0.93
> }
>
> _______________________________________________
> Mne_analysis mailing list
> Mne_analysis at nmr.mgh.harvard.edu
> Mne_analysis Info Page
_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu Mne_analysis Info Page
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at MyComplianceReport.com: Compliance and Ethics Reporting . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
Thanks for the replies everyone. Just to follow up, I downloaded the
nightly build (from 21. Feb 2012) of MNE and indeed multiple events can now
be included in a category. But, I ran into the following error when
attempting to run mne_browse_raw:
*mne_browse_raw: error while loading shared libraries: libgfortran.so.1:
cannot open shared object file: No such file or directory*
although your method solved your problem - I would not recommend it in general.
Normally, a standard procedure to install the relevant libraries puts them into directories which are already scanned during program starts or extents the search list accordingly. If this, however, fails because the world is never perfect - there are the manual methods below to get the stuff repaired.
You can extent the list of pathes where linux searches for the shared libraries via LD_LIBRARYPATH (A) or via configuration files (B):
(A)
echo $LD_LIBRARY_PATH # if you see some output here use a), otherwise b)
a)
export LD_LIBRARY_PATH= ${LD_LIBRARY_PATH }:<where your libgfortran.so.1 is located>
b)
export LD_LIBRARY_PATH= <where your libgfortran.so.1 is located>
This is going to work in the existing shell until you close it (or logoff).
(B)
A more persistent way is this - provided you have superuser rights on your machine:
You should find a directory /etc/ld.so.conf.d/ at your machine. Additionally, there should be a file /etc/ld.so.conf mentioning this directory as to be included.
Create a new file within the directory and simply put the directory name in it.
run ldconfig to update the cache for the shared libraries.
