Incident Node

Incident Node

The Incident Node loads data off a local or remote Vestec System and provides it via the node editor.

Output port guessing

Based on the provided file metadata the incident node tries to guess the correct output port type.
When registering a dataset on an incident, set the Type field to one of the supported type mappings listed below.

Alternatively you can add your own Type -> Output mappings by calling IncidentNode.addTypeMapping(from, to);, where from is the content of the Type field, and to is one of the supported output types.

Supported Output Types

TEXTURES

A texture renderable by the TextureRenderNode.
Type-field mappings: 2D_Fire, DISEASES_TEXTURE

CINEMA_DB

CinemaDB json files readable by the VTK HttpDataSetReader.
The dataset should be a zip-file containing a single top-level folder which contains the index.json and data folder.
Type-field mappings: CINEMA_DB, CINEMA_DB_JSON

PATH

For nodes that expect a local file system path, the path type can be used. For Datasets with the type filed set to path, the incident node extracts the uplaoded dataset and outputs the path to the extracted files.

CinemaDB Path

A path to CinemaDB vtu files readable by the CinemaDBNode.
The CinemaDBNode convertes vtu files readable by the VTK HttpDataSetReader.
The dataset should be a zip-file containing data.csv and the data-folder. See the example below:

data.zip
│   data.csv
│
└───data
    │   110095.vtm
    │   113805.vtm
    │   ...
    │
    ├───110095
    │       110095_0.vtu
    │
    ├───113805
    │       113805_0.vtu
    │
    └───...

POINT_ARRAY

TBD