This is an automated email from the git hooks/post-receive script. yoh pushed a commit to annotated tag v0.1 in repository python-mne.
commit c02493accecf14e4a96ca62a6eb8178dbe94e01f Author: Emily Ruzich <[email protected]> Date: Mon May 16 12:20:52 2011 -0400 fixing manual --- doc/source/manual/analyze.rst | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/doc/source/manual/analyze.rst b/doc/source/manual/analyze.rst index 0ba6485..95bb94a 100755 --- a/doc/source/manual/analyze.rst +++ b/doc/source/manual/analyze.rst @@ -1606,14 +1606,14 @@ controls: | | yellow. Negative values will be bright blue. | +------------+---------------------------------------------------------+ | fmult | Apply this multiplier to the above thresholds. Default | - | | is 1 for statistical maps and INLINE_EQUATION for | - | | currents (MNE). The vertical bar locations in the | + | | is :math:`1` for statistical maps and :math:`1^{-10}` | + | | for currents (MNE). The vertical bar locations in the | | | histogram take this multiplier into account but the | | | values indicated are the threshold parameters without | | | the multiplier. | +------------+---------------------------------------------------------+ | tcmult | The upper limit of the timecourse vertical scale will | - | | be INLINE_EQUATION. | + | | be :math:`tc_{mult}f_{mult}f_{max}`. | +------------+---------------------------------------------------------+ @@ -1649,10 +1649,10 @@ The optional parameters are: **Time integr. (ms)** - Integration time for each frame (INLINE_EQUATION). + Integration time for each frame (:math:`\Delta t`). Before computing the estimates time integration will be performed - on sensor data. If the time specified for a frame is INLINE_EQUATION, - the integration range will be INLINE_EQUATION. + on sensor data. If the time specified for a frame is :math:`t_0`, + the integration range will be :math:`t_0 - ^{\Delta t}/_2 \leq t \leq t_0 + ^{\Delta t}/_2`. **# of smooth steps** @@ -1677,12 +1677,12 @@ shows the SNR estimated from the whitened data in red and the apparent SNR inferred from the mismatch between the measured and predicted data in green. -The SNR estimate is computed from the whitened data INLINE_EQUATION, -related to the measured data INLINE_EQUATION by +The SNR estimate is computed from the whitened data :math:`\tilde{x}(t)`, +related to the measured data :math:`x(t)` by .. math:: \tilde{x}(t) = C^{-^1/_2} x(t)\ , -where INLINE_EQUATION is the whitening +where :math:`C^{-^1/_2}` is the whitening operator, introduced in :ref:`CHDDHAGE`. The computation of the apparent SNR will be explained in @@ -1755,12 +1755,12 @@ are available: **L2 norm (sample by sample)** - Compute the INLINE_EQUATION norm over the values + Compute the :math:`l_2` norm over the values in the vertices at each time point. **Pick vertex with largest L2 norm over time** - Compute the INLINE_EQUATION norm over time in + Compute the :math:`l_2` norm over time in each vertex and show the time course at the vertex with the largest norm. @@ -1821,22 +1821,22 @@ The vertex-by-vertex output formats is summarized in :ref:`CACEFHIJ`. .. _CACEFHIJ: -.. table:: Vertex-by-vertex output format. INLINE_EQUATION is the number of vertices, INLINE_EQUATION is the number of time points, INLINE_EQUATION is the number of comment lines, INLINE_EQUATION indicate the times in milliseconds, INLINE_EQUATION is a vertex number, INLINE_EQUATION are the coordinates of vertex INLINE_EQUATION in millimeters, and INLINE_EQUATION are the values at vertex INLINE_EQUATION. Items in brackets are only included if Include coordinates is active. In the time-b [...] +.. table:: Vertex-by-vertex output format. :math:`n_p` is the number of vertices, :math:`n_t` is the number of time points, :math:`n_{com}` is the number of comment lines, :math:`t_1 \dotso t_{n_t}` indicate the times in milliseconds, :math:`p` is a vertex number, :math:`x_p y_p z_p` are the coordinates of vertex :math:`p` in millimeters, and :math:`v_p^{(1)} \dotso v_p^{(n_t)}` are the values at vertex :math:`p`. Items in brackets are only included if *Include coordinates* is active. I [...] - ================== ====================================================== - Line Contents - ================== ====================================================== - INLINE_EQUATION Comment lines beginning with % - INLINE_EQUATION {0.0 }[0.0 0.0 0.0] INLINE_EQUATION - INLINE_EQUATION {INLINE_EQUATION }[INLINE_EQUATION] INLINE_EQUATION - ================== ====================================================== + =================================== ====================================================== + Line Contents + =================================== ====================================================== + :math:`1-n_{com}` Comment lines beginning with % + :math:`n_{com}+1` :math:`\{0.0\}[0.0\ 0.0\ 0.0] t_1 \dotso t_{n_t}` + :math:`(n_{com}+1)-(n_p+n_{com}+1)` :math:`\{p\}[x_p y_p z_p]v_p^{(1)} \dotso v_p^{(n_t)}` + =================================== ====================================================== .. _CACJCFJJ: Creating new label files ======================== -It is easy to create new label files in mne_analyze . +It is easy to create new label files in mne_analyze. For this purpose, an inflated surface should be visible in the main display. Follow these steps: -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-med/python-mne.git _______________________________________________ debian-med-commit mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-commit
