ExportSET¶
Export non-streaming continuous data to an EEGLAB set file.
This node accepts a packet that is assumed to hold the entire recording to save (i.e., non-streaming data), and writes it to a .set file. This node further assumes that the data is a 2d array with a space axis (channels) and a time axis (samples). Note that this node currently cannot save segmented ("epoched") data, which is characterized by the presence of an instance axis in addition to time and space. There may also optionally be a second stream in the packet to save that holds markers, which will be written out as event markers into the set file. If this node is used after ICA has been performed it will back project the IC activations to the channel time series and store the ICA streams as fields in the EEG structure. Note: some processing nodes will insert axis types that this node cannot handle, such as feature axes (in the case of feature-extraction nodes). If your data has such axes, you can first replace those axes by a space axis (using the Override Axis node), or fold additional axes into the space or time axis (using the Fold Into Axis node). EEGLAB is a quite versatile environment for working with EEG data, and is a commonly-used target for data processed with NeuroPype for additional investigation. More Info... Version 1.3.0
Ports/Properties¶
data¶
Input signal.
filename¶
File name to export data to. Can be the full path or a relative path or filename if `output_root is specified.
output_root¶
Path to the output folder; if specified, the filename will be relative to this folder. Alternatively, this can be left empty and the full path may be specified in filename).
file_version¶
Specify the MAT-File version of the SET file to export. Version 7.3 MAT-files use an HDF5 based format
boundary_events¶
Add boundary events where there are a significant number of dropped samples.
max_dropped¶
Maximum dropped samples allowed before a boundary condition event is inserted.
set_breakpoint¶
Set a breakpoint on this node. If this is enabled, your debugger (if one is attached) will trigger a breakpoint.
metadata¶
User-definable meta-data associated with the node. Usually reserved for technical purposes.
cloud_host¶
Cloud storage host to use (if any). You can override this option to select from what kind of cloud storage service data should be downloaded. On some environments (e.g., on NeuroScale), the value Default will be map to the default storage provider on that environment.
cloud_account¶
Cloud account name on storage provider (use default if omitted). You can override this to choose a non-default account name for some storage provider (e.g., Azure or S3.). On some environments (e.g., on NeuroScale), this value will be default-initialized to your account.
cloud_bucket¶
Cloud bucket to read from (use default if omitted). This is the bucket or container on the cloud storage provider that the file would be written to. On some environments (e.g., on NeuroScale), this value will be default-initialized to a bucket that has been created for you.
cloud_credentials¶
Secure credential to access cloud data (use default if omitted). These are the security credentials (e.g., password or access token) for the the cloud storage provider. On some environments (e.g., on NeuroScale), this value will be default-initialized to the right credentials for you.