Skip to content

Package: file_system

Filesystem-related nodes.

These nodes perform file-system related operations, such as loading and saving data to/from files on disk, and in some cases from network storage. Typically, the data packets that these nodes produce (in case of loader/importer nodes) or accept (in case of saver/exporter nodes) represent whole recordings, i.e., they are not streaming chunks. A small subset of nodes in this category works with streaming data. Some nodes perform auxiliary file system tasks, such as manipulating directories. Node classes in this package are: - nodes starting with Import: these nodes load data from files on disk - nodes starting with Export: these nodes save data to files on disk - nodes starting with Path: common path operations acting on strings When importing data from standard time-series file formats (e.g., EDF, BDF, SET), the data is typically loaded into a Packet with one Chunk (aka stream) per modality, for example 'eeg' or 'nirs', which has a time axis and a space axis. With many file formats, auxiliary measures (such as emg, accelerometer etc) will appear multiplexed in the primary modality's channels. Any event markers (or other sporadic annotations) present in the data will appear in a 'markers' modality, which has only an instance axis (where the .times array of the axis has time stamps in seconds relative to some arbitrary time base and the .data array of the axis is a record array that can be indexed either by field name (e.g., 'Marker') or by index). Other file formats (e.g., H5) are considerably more flexible and can produce a greater variety of data structure and axes, although the specific importer may only allow a restricted set of data representations in the file.

Nodes in this package: