Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Documentation
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • anywave
  • Documentation
  • Wiki
  • MATLAB_BIDS

MATLAB_BIDS · Changes

Page history
Update MATLAB_BIDS authored Jul 23, 2025 by Bruno Colombet's avatar Bruno Colombet
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 17 deletions
+1 -17
  • MATLAB_BIDS.md MATLAB_BIDS.md +1 -17
  • No files found.
MATLAB_BIDS.md
View page @ 5959690e
...@@ -2,23 +2,8 @@ ...@@ -2,23 +2,8 @@
# Requirements # Requirements
The plugin must be able to handle command line launch mode. The plugin must be able to handle command line launch mode.
See this section [See this section](/anywave/documentation/-/wikis/MATLAB anywave function)
# Modify the dest.txt
Add the line:
````
flags = CanRunFromCommandLine
````
Note that you can set several flags separating them by '**:**'
# Specify the command line parameters your plugin will handle
The plugin will receive all the default command line options handled by AnyWave but if you need to handle your own options then you must provide a file called **args.json** and put it along with desc.txt file in the plugin folder.
Example of a plugin that will handle the options **eeg_file** (path to a EEG data file) and **meg_file** (path to a MEG data file):
````json
{
"Parameters" : [ "eeg_file", "meg_file"]
}
````
# Handle options in your code # Handle options in your code
````matlab ````matlab
function main(varargin) function main(varargin)
...@@ -35,7 +20,6 @@ else ...@@ -35,7 +20,6 @@ else
end end
end end
```` ````
# Avoid figure and GUIs # Avoid figure and GUIs
If you want the plugin to be run as a BIDS pipeline you must not stop the execution by using blocking dialog boxes. If you want the plugin to be run as a BIDS pipeline you must not stop the execution by using blocking dialog boxes.
......
Clone repository
  • Build_AnyWave
  • CLI
  • CLI_List
  • Changes
  • ExportData
  • ICA
  • Imaginary Coherence
  • MATLAB anywave function
  • MATLAB_BIDS
  • MATLAB_change_sig_prop
  • MATLAB_debug
  • MATLAB_get_data
  • MATLAB_get_markers
  • MATLAB_get_props
  • MATLAB_init
View All Pages