Brief summary

Met.3D is able to visualize 3D trajectory data as "3D tubes" and "3D particles" coloured by pressure elevation or by any other auxiliary/traced variable.
- See Trajectory actor
Pre-computed trajectories can be loaded from NetCDF files.
Met.3D can also compute trajectories and streamlines on-the-fly, using trajectory computation equivalent to that of the LAGRANTO model (cf. https://doi.org/10.5194/gmd-8-2569-2015).
Trajectories can be filtered according to "ascent per time interval" to capture Warm Conveyor Belt features (see https://doi.org/10.5194/gmd-8-2355-2015).
Please let us know if this functionality is useful for you and you would require further development.

Description

Precomputed trajectories can be read from NetCDF files. The files have to be formatted as described in Trajectory data in NetCDF format.

To compute trajectories within Met.3D:

First load a gridded dataset containing the three wind components u, v, omega (horizontal components need to be in m/s, vertical component needs to be in Pa/s), either through the GUI ("File→New Dataset") or with a user-defined pipeline configuration file (cf. Gridded data);
then
- From the GUI select "File→New Dataset", then select the "Trajectories" tab and the "Computation in Met.3D" tab. Here, specify the gridded dataset to be used, the three wind components, and optionally the names of variables that shall be traced along the trajectories.
- Alternatively, specify the trajectoriy computation settings in your pipeline configuration (cf. comments in https://gitlab.com/wxmetvis/met.3d/-/blob/master/config/default_pipeline.cfg.template).
Specific settings of trajectory seeding and times take place in the Trajectory actor.

Trajectory visualization is configured in the Trajectory actor.

Trajectory visualization is implemented in MTrajectoryActor, located at

Trajectory computation is implemented in MTrajectoryComputationSource, located at