Custom Query (210 matches)

(from minutes of FpDev Workshop 2012)

Backward mode for deposition quantities

This was considered as “nice to have”, but there are no plans to implement it as of now; this could be implemented as a pre-processing tool

(from minutes of FpDev Workshop 2012)

The introduction of netCDF output (post-processing) was considered useful, post-processing software should be put on the FLEXPART home page; as a disadvantage, however, it needs to be stressed that output in netCDF format is much larger compared with standard FLEXPART output.

With the introduction of a FLEXPART netCDF output converter, a large variety of visualization software becomes available

I think implementation should be as a postprocessing tool. Binding in netCDF libs can create trouble as we see in ticket:14 and makes the code more dependent on other software, while not everyone would want to use the feature.

(from minutes of FpDev Workshop 2012)

Currently, the FLEXPART output file header is binary. An ASCII-text header file for basic parameters would be useful (maybe in addition to the current header file to preserve compatibility with existing postprocessing software); in the header file, additional information should be stored, for example path names for input data (e.g., windfields)