<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://fieldtrip.fcdonders.nl/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://fieldtrip.fcdonders.nl/feed.php">
        <title>FieldTrip</title>
        <description></description>
        <link>http://fieldtrip.fcdonders.nl/</link>
        <image rdf:resource="http://fieldtrip.fcdonders.nl/lib/images/favicon.ico" />
       <dc:date>2010-07-29T23:31:19+02:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/integrating_with_spm8?rev=1280411454&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/dataformat?rev=1280314790&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/faq/how_are_the_various_data_structures_defined?rev=1280308306&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/faq/what_does_a_typical_call_to_a_fieldtrip_function_look_like?rev=1280307914&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/faq?rev=1280307470&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/tutorial/forward?rev=1280236825&amp;do=diff"/>
                <rdf:li rdf:resource="http://fieldtrip.fcdonders.nl/faq/why_does_my_tfr_look_strange?rev=1280220997&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://fieldtrip.fcdonders.nl/lib/images/favicon.ico">
        <title>FieldTrip</title>
        <link>http://fieldtrip.fcdonders.nl/</link>
        <url>http://fieldtrip.fcdonders.nl/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://fieldtrip.fcdonders.nl/integrating_with_spm8?rev=1280411454&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-29T15:50:54+02:00</dc:date>
        <dc:creator>Vladimir Litvak</dc:creator>
        <title>integrating_with_spm8</title>
        <link>http://fieldtrip.fcdonders.nl/integrating_with_spm8?rev=1280411454&amp;do=diff</link>
        <description>Background

SPM8 is the newest version of SPM software developed by the Methods Group at the Wellcome Trust Centre for Neuroimaging, Institute of Neurology, University College London, UK and collaborators. SPM8 implements several advanced methods for M/EEG analysis:</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/dataformat?rev=1280314790&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-28T12:59:50+02:00</dc:date>
        <dc:creator>Jan-Mathijs Schoffelen</dc:creator>
        <title>dataformat</title>
        <link>http://fieldtrip.fcdonders.nl/dataformat?rev=1280314790&amp;do=diff</link>
        <description>dataformat,
	meg,
	eeg,
	lfp,
	spike





FieldTrip has a flexible way of supporting data formats. It uses three wrapper functions that provide a common interface to all electrophysiological (EEG/MEG) file formats: ft_read_header, ft_read_data and ft_read_event. These wrapper functions will call the low-level functions for each file format. Some of the low-level functions are written by ourselves, others are supplied by the manufacturers and again others are obtained from other open source toolb…</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/faq/how_are_the_various_data_structures_defined?rev=1280308306&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-28T11:11:46+02:00</dc:date>
        <dc:creator>Jan-Mathijs Schoffelen</dc:creator>
        <title>faq:how_are_the_various_data_structures_defined</title>
        <link>http://fieldtrip.fcdonders.nl/faq/how_are_the_various_data_structures_defined?rev=1280308306&amp;do=diff</link>
        <description>faq,
	datatype,
	todo

TODO complete the description of the main data formats (raw, comp, timelock, freq, source, volume) 



How are the various data structures defined?

The output of a FieldTrip function is a data structure of a particular type. Such data structure consists at least of numeric data specific to that particular datatype, and of descriptive fields which are needed to interpret the data. The different datatypes and their features are listed below:</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/faq/what_does_a_typical_call_to_a_fieldtrip_function_look_like?rev=1280307914&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-28T11:05:14+02:00</dc:date>
        <dc:creator>Jan-Mathijs Schoffelen</dc:creator>
        <title>faq:what_does_a_typical_call_to_a_fieldtrip_function_look_like</title>
        <link>http://fieldtrip.fcdonders.nl/faq/what_does_a_typical_call_to_a_fieldtrip_function_look_like?rev=1280307914&amp;do=diff</link>
        <description>faq,
	datatype,
	function



What does a typical call to a FieldTrip function look like?


The FieldTrip functions in general work like this

dataout = functionname(cfg);               % e.g. ft_preprocessing
dataout = functionname(cfg, datain, ...);  % e.g. ft_freqanalysis
functionname(cfg, datain, ...);            % e.g. plotting functions 

Type 'help functionname' to see which input arguments (cfg.xxx) ought to be defined before calling the function. The datain and dataout arguments to all F…</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/faq?rev=1280307470&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-28T10:57:50+02:00</dc:date>
        <dc:creator>Jan-Mathijs Schoffelen</dc:creator>
        <title>faq</title>
        <link>http://fieldtrip.fcdonders.nl/faq?rev=1280307470&amp;do=diff</link>
        <description>faq





On this page you can find (and add) answers to a variety of Fieldtrip-related questions.

We invite you to add your own example scripts or frequently asked questions on the wiki. Also tutorials can be added. Every time you explain somebody something about Fieldtrip, please consider whether you could use the wiki for this so others can learn from it as well.</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/tutorial/forward?rev=1280236825&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-27T15:20:25+02:00</dc:date>
        <title>tutorial:forward</title>
        <link>http://fieldtrip.fcdonders.nl/tutorial/forward?rev=1280236825&amp;do=diff</link>
        <description>Introduction


The goal of this tutorial is to give insights about biological electric-magnetic fields generated at the neural level and how this impacts signals from EEG, MEG, ECoG, single cell recordings, tetrodes, etc. A so-called forward solution is here intended as the set of equation which lead from sources in the brain to the signal recorded at the sensor level. The spatial pattern of activation corresponding to a specific neural source is called most of the times 'lead field'. The availa…</description>
    </item>
    <item rdf:about="http://fieldtrip.fcdonders.nl/faq/why_does_my_tfr_look_strange?rev=1280220997&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-27T10:56:37+02:00</dc:date>
        <dc:creator>Jan-Mathijs Schoffelen</dc:creator>
        <title>faq:why_does_my_tfr_look_strange</title>
        <link>http://fieldtrip.fcdonders.nl/faq/why_does_my_tfr_look_strange?rev=1280220997&amp;do=diff</link>
        <description>faq,
	ft freqanalysis,
	ft freqanalysis mtmconvol,
	freq,
	tfr




Why does my TFR look strange?


If you use 'mtmconvol' as a method for frequency analysis it could happen that the Time-Frequency Representation of your data looks like this:


This phenomenon is caused by the time domain data having a non-zero DC component. This component leaks into the estimates of all time-frequency points in a variable (but patterned) way. The reason why this actually happens is related to the exact algorithm…</description>
    </item>
</rdf:RDF>
