Difference between revisions of "AnyWave:Plugin Batch"
Line 63: | Line 63: | ||
=Make AnyWave recognize my arguments= | =Make AnyWave recognize my arguments= | ||
If you have followed the steps above, your plugin can run in a batch script. However, there is no way AnyWave can guess the expected arguments key/value you would like to get in your plugin code.<br/> | If you have followed the steps above, your plugin can run in a batch script. However, there is no way AnyWave can guess the expected arguments key/value you would like to get in your plugin code.<br/> | ||
+ | Suppose we want to handle two files using eeg_file and meg_file arguments.<br/> | ||
+ | eeg_file will hold the path to an EEG data file and meg_file will handle the path to a MEG data file.<br/> | ||
==Run with a json file== | ==Run with a json file== | ||
+ | One method to correctly parse our arguments is to define them in a json file and make AnyWave use that file:<br/> | ||
+ | <syntaxhighlight lang="java"> | ||
+ | "plugin" : "MyPlugin", | ||
+ | "eeg_file" : "d:\data\eeg\data.eeg", | ||
+ | "meg_file" : "d:\data\meg\data.meg" | ||
+ | </syntaxhighlight> | ||
+ | Note the plugin required plugin key that will inform AnyWave about the name of the plugin to run. In this case, our plugin called MyPlugin.<br/> | ||
+ | Then now run in command line:<br/> | ||
+ | <syntaxhighlight lang="bash"> | ||
+ | anywave --run args.json | ||
+ | </syntaxhighlight> |
Revision as of 15:52, 21 April 2020
Contents
Introduction
One of the features of AnyWave is to run some processing from the command line.
This is called batch processing, allowing to process many files in different locations using a script file run by the OS.
Make my plugin runnable in command line
If you want AnyWave to handle your plugin using the command line, you must do as follow:
MATLAB/Python
edit the desc.txt:
name = MyPlugin description = do something in MATLAB category = Process:Test:MyPlugin flags = CanRunFromCommandLine
Note: we've added a line with the flags keyword. This keyword will inform AnyWave of the capabilities of your plugin.
You may combine flags using the : (the colon character). Example:
flags = CanRunFromCommandLine:NoDataRequired
This indicates that the plugin can be called from the command line but also indicates that no data file is required. (The plugin will not run on a data file.)
edit MATLAB code
Modify the main.m file:
function main(varargin) global args; %% IMPORTANT: this variable will hold the arguments set by the user on the command line. if isdeployed % this is the code to use if you plan to Compile your plugin to distribute it. % STANDALONE AnyWave Plugin code global host; global port; global pid; if (nargin < 3) % basic argument checking error('missing arguments.'); end host = varargin{1}; port = str2num(varargin{2}); pid = str2num(varargin{3}); if (nargin > 3) args = varargin{4}; end assignin('base', 'host', host); assignin('base', 'port', port); assignin('base', 'pid', pid); assignin('base', 'args', args); % end of STANDALONE AnyWave Plugin code end % we assume here that the code will always run in batch mode. % To check if the plugin was called in batch mode, just check if args variable is empty or not. if isempty(args) error('this plugin will only run in batch mode'); end % code your stuff here % use args to get the arguments: % args is a structure containing fields named upon the arguments set by the command line. % % one of the common argument set by AnyWave is input_file which contains the path to the data file to process. % so to get the file use : file = args.input_file;
C++
tototo
Make AnyWave recognize my arguments
If you have followed the steps above, your plugin can run in a batch script. However, there is no way AnyWave can guess the expected arguments key/value you would like to get in your plugin code.
Suppose we want to handle two files using eeg_file and meg_file arguments.
eeg_file will hold the path to an EEG data file and meg_file will handle the path to a MEG data file.
Run with a json file
One method to correctly parse our arguments is to define them in a json file and make AnyWave use that file:
"plugin" : "MyPlugin", "eeg_file" : "d:\data\eeg\data.eeg", "meg_file" : "d:\data\meg\data.meg"
Note the plugin required plugin key that will inform AnyWave about the name of the plugin to run. In this case, our plugin called MyPlugin.
Then now run in command line:
anywave --run args.json