Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • physio-doc physio-doc
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Commits
Collapse sidebar

To receive notifications about scheduled maintenance, please subscribe to the mailing-list gitlab-operations@sympa.ethz.ch. You can subscribe to the mailing-list at https://sympa.ethz.ch

  • physio
  • physio-docphysio-doc
  • Wiki
  • FAQ

FAQ · Changes

Page history
typos authored Mar 18, 2019 by Lars Kasper's avatar Lars Kasper
Hide whitespace changes
Inline Side-by-side
FAQ.md
View page @ a87d16a2
......@@ -216,7 +216,7 @@ structure:
1. Note that these thresholds have to be set correctly only once for each
functional sequence, i.e., usually once per study. Even small changes to scan
geometry (e.g. slice tilt) between subject shouldn't affect them significantly.
geometry (e.g. slice tilt) between subjects shouldn't affect them significantly.
2. Setting the thresholds is an iterative procedure. You might start with the
defaults, probably running into an error or warning (`Warning: Invalid
MinPeakHeight. There are no data points greater than MinPeakHeight.` or `Not
......@@ -230,11 +230,11 @@ highest peaks and most regular features reflecting slice and/or volume scan
events.
4. `sync.zero` has to be smaller than `sync.slice` and `sync.vol`. It should
be about 4/5 of the typical peak height in the gradient trace. Note that you can
set this syncolds (and all other) either in absolute values or relative to the
set this thresholds (and all other) either in absolute values or relative to the
maximum peak height. Set a value below 1, if you prefer the latter.
5. `sync.sli` should be about 9/10 of the typical peak height of a slice scan
5. `sync.slice` should be about 9/10 of the typical peak height of a slice scan
event.
6. `sync.vol`, if you set it, should be larger than `sync.sli`. It should be
6. `sync.vol`, if you set it, should be larger than `sync.slice`. It should be
9/10 of the peak height that stands out at the beginning of a volume, and is
followed by some dozens of smaller peaks (for the slices) typically. It might
be, however, that there is no such peak marking the start of a volume. If so,
......@@ -247,6 +247,7 @@ onset differences. If once every few seconds (your `TR`) you find an exposed
peak, its height will give you the value for `sync.vol_spacing` (maybe reduce
it by about 5-10ms to allow for timing inaccuracies).
## 13. How do I know which logfile type ('vendor') I have to choose?
- Typically, you will know your scanner manufacturer or the supplier of your peripheral recording device. The currently supported vendors can always be found in the SPM Batch Editor, as dropdown options for the vendor parameter in any PhysIO batch, and are also listed as cases in `tapas_physio_read_physlogfiles.m`.
......
Clone repository
  • EXAMPLES
  • FAQ
  • HOME
  • MANUAL_PART_READIN
  • QUICKSTART