AnyWave:Faq

From WikiMEG
Revision as of 16:15, 12 June 2019 by Bruno (Talk | contribs)

Jump to: navigation, search

Frequently asked questions (FAQ) about AnyWave. If you don't have an answer to your question reading the Documentation, you may find useful information here.

Plug-ins

The application is provided with plug-ins which allow for example to read and write several data file formats, apply Time/Frequency representation to a signal, etc.

How to install a plug-in

The user may add custom plug-ins to AnyWave. Depending on the plug-in type (MATLAB, Python or Native) the location where to put the plug-in may vary.
We strongly recommend NOT to add plug-ins in the Application directory, as it may require administrative privileges and it also make the plug-ins available to all users on the computer.
We suggest to install plug-in in the user home directory where AnyWave created special folders to place custom files.
On the Windows platform, the base directory for plug-ins should be: "My Documents\AnyWave\Plugins".
On the Mac OS X and Linux platforms, the base directory for plug-ins should be: "AnyWave/Plugins" in the user's home directory.
There are several types of plug-ins:

  • An AnyWave native plug-in is a file (a C++ library) that must be copied directly in the root plugins directory.
  • A MATLAB plug-in is a directory containing several files and must be copied in the MATLAB sub-directory.
  • A Python plug-in is also a directory containing several files and must be copied in the Python sub-directory.

MATLAB Requirements

MATLAB plug-ins can be distributed as MATLAB .m files and thus require that MATLAB is available on the computer.
AnyWave will call the MATLAB execution engine to run those files.

MATLAB plug-ins can also be compiled and distributed as a standalone application.
This will required the MATLAB Runtime to be installed on the computer. The Runtime is freely available from the Mathworks web site.

Check for plugin log files

Every time a process is launched a log file is created by AnyWave.
This is also the case for batch mode execution.

Check for log files on the Log subfolder of AnyWave:
Log folder.png

batch processing

Some processes can be executed in batch mode, using the command line.
See this section Command Line Options for more details.
List of process that can be executed in batch mode:

File formats

AnyWave can read and/or write to different file formats depending on the available plug-ins.

For EEG data the following formats are supported for reading:

  • Micromed (.trc)
  • EDF+/BDF+ (.edf/.bdf)
  • Brainvision Analyser (.vhdr)
  • ANT EEProbe (.cnt)
  • Neuroscan old format (.cnt)
  • ADES (.ades) AnyWave simple format.
  • SPM (*.mat)
  • EEGLAB (*.set)
  • EGI (*.mff)

For MEG data the following formats are supported for reading:

  • 4DNI
  • CTF
  • Elekta (*.fif)
  • ADES (.ades) AnyWave simple format.

It is also possible to export to the following formats:

  • Brainvision Analyser (.vhdr)
  • ADES (.ades) AnyWave simple format.
  • MATLAB (.mat)

ADES format

This is a simple file format used mostly to exchange data between different software.
Here is a complete documentation of the ADES file format

MATLAB format

A new plugin allows AnyWave to export data into a MATLAB file.
Here is a complete documentation about what you will find inside the MATLAB file when exporting data.

Command line options

AnyWave can also be launched using the command line. This will prevent any GUI to pop up on the screen.
In this mode, you will be able to batch some operations, like converting files to another format or BIDSify some file.
See this section Command Line Options

BIDS support

The BIDS support is under development, but there is a command line feature that can be used to launch AnyWave without any GUI and
ask it to convert a SEEG file into a BIDS compatible format and place it to a specified folder.
options:
--toBIDS indicates we want to convert a file to BIDS.
--bids_modality <ieeg|meg> specify what the file to convert contains (ieeg, meg).REQUIRED
--bids_sub <subject> BIDS subject REQUIRED
--bids_task <task> BIDS task REQUIRED
--bids_run <run> BIDS run index (optional)
--bids_acq <acq> BIDS acquisition (optional)
--bids_proc <proc> process (optional)
--bids_output <sidecars|all> (sidecars : only generates .json and .tsv files. all: full conversion)
--bids_ses <session> BIDS session (optional)
--bids_format <edf | vhdr> (optional)

Example

Convert a file data.eeg containing SEEG recordings to BIDS for subject JohnDoe.
<syntax highlight lang='bash'> anywave --toBIDS --bids_modality ieeg --input_file data.eeg --output_dir d:\data\BIDS --bids_format vhdr --bids_sub johndoe --bids_task rest </syntax highlight>