• Using ERA5 analysis, model level data
• minimum requirement as given here - https://mptrac.readthedocs.io/en/latest/meteorological-input-data/ - is lnsp,z,t,u,v,w,q
• after reading file for a certain timestep, it generates the following warmings and moves on to the next step without writing
  

Is your feature request related to a problem?

• Some additional variables (ul, vl, wl, o3c, ...) have recently been added to the meteo pre-processing code and meteo data structs of MPTRAC. These data should be added to the meteo binary files as they would otherwise be missing during the simulations.

Describe the solution you'd like

• Double check whether all the variables of meteo data struct met_t in libtrac.h are considered for input/output in read_met() and write_met() in libtrac.c. Add the missing variables.

Additional context

• As the binary file format will change, a new version number should be assigned.

Is your feature request related to a problem?

• looking for different methods for visualization of MPTRAC particle data

Describe the solution you'd like

• identify different visualization tools suitable for displaying the particle data in a more fancy way (3-D plots, animations, ...)
• possibly implement new I/O functions in MPTRAC for writing/converting particle data in file formats best suited for the visualization tools

Describe alternatives you've considered

• particle data output is currently provided in the form of ASCII tables for use with gnuplot
• particle data can also be written as netCDF files for use with other visualization tools, python, ...

Hi Mingzhao,

there is a bug in the netCDF grid output, I think.

When you use strcat() to build the netCDF variable names, it will overwrite the original data of the ctl struct. So the code crashes here with a netCDF error message:

You need to create a new string to make this work, e.g.

char varname[LEN];
sprintf(varname, "%s_mean", ctl->qnt_name[...]);
NC_PUT_DOUBLE(varname, help, 0); 

Can you please take a look?

Thanks
Lars

We already have interpolation functions and data structures for cartesian grids. Could we extend the interpolation functions to deal with icosahedral grids?

• Literature research: Can libraries be used for it?
• What routines can be shared with LaMETTA, YAC, ICON?
• Implement an icosahedral met grid type.
• Write a reading function for ico met type.
• Implement index search functions for the ICON grid.
• Implement a horizontal interpolation from the ICON grid to air parcel positions...
• Implement a horizontal interpolation from the ICON grid to the lat-lon support grid, which is required for parameterizations.
• Formulate a hybrid coordinate with potential temperature in the stratosphere and a non-hydrostatic coordinate in the troposphere.
• Generalize the vertical coordinate system in MPTRAC.
• Implement exact interpolations for winds on pressure levels that consider the tilt of the levels against the eta coordinate.
• Implement the vertical interpolation function and combine it with the horizontal interpolations.
• Implement a control flow to select between cartesian, icosahedral or any other potential grid geometry.
• Test the procedures with ICON output data...

From ESM-Buildbot this issue happens to the GPU building.
The CPU building pass this issue.

Suggestions to modify the library build script:

• Limit the set of libraries built with the default option/selection to those that are mandatory for building the model (i.e. GSL, HDF5, netCDF, and zlib). Optional libraries (thrustsort, zfp, zstd, KPP) should only be compiled if the users selects them. This avoids initial problems installing MPTRAC if the library build processes are failing. (suggested by @laomangio)

• Consider integrating the libraries as git submodules rather than adding the source packages to the MPTRAC git repository. (suggested by @hydrogencl )

List of potentially interesting case studies for MPTRAC:

• Sahara dust over Europe on 30-31 March 2021

  • https://www.ecmwf.int/en/newsletter/168/news/saharan-dust-events-spring-2021
  • https://datapub.fz-juelich.de/slcs/airs/volcanoes/html/view_2021_090.html

• Sahara dust over the Atlantic on 23-27 Feb 2020:

  • https://datapub.fz-juelich.de/slcs/airs/volcanoes/html/view_2020_056.html

• Australia wildfires on 1-5 January 2020:

  • https://datapub.fz-juelich.de/slcs/airs/volcanoes/html/view_2020_001.html

use nc2

atm_dist.c:47:3: optimized: Inlining printf/47 into main/185 (always_inline).
/usr/bin/ld: cannot find -lhdf5_hl
/usr/bin/ld: cannot find -lhdf5
collect2: error: ld returned 1 exit status
make: *** [Makefile:142: atm_select] Error 1
/usr/bin/ld: cannot find -lhdf5_hl
/usr/bin/ld: cannot find -lhdf5
collect2: error: ld returned 1 exit status
make: *** [Makefile:142: atm_init] Error 1
/usr/bin/ld: cannot find -lhdf5_hl
/usr/bin/ld: cannot find -lhdf5
collect2: error: ld returned 1 exit status
make: *** [Makefile:142: atm_dist] Error 1

MPTRAC test cases are not fully reproducible with different compilers and compiler versions.

(a) small numerical differences in GSL statistics functions (stddev, skew, kurt), possibly due to GSL results not being reproducible when GSL is compiled with different versions of gcc? also other (small) differences

(b) GPU test is conducted with make gpu_test rather than make check

• I've added automatic e-mail notifications for the MPTRAC nightly builds (https://datapub.fz-juelich.de/slcs/mptrac/nightly_builds/) on JUWELS and JURECA.

• We can add more colleagues (developers, in particular) to receive these notifications so that they would be informed on any new issue with code or HPC systems.

Is your feature request related to a problem?

• new users need more detailed documentation to get started with MPTRAC

Describe the solution you'd like

• check/revise the README file
• revise and extend the mkdocs manual, including descriptions of individual apps/tools
• add/check links to references and other sources of information
• revise and extend the doxygen manual

Additional ideas

• implement `-help' flags in the apps
• create and add small logo for MPTRAC on doxygen and mkdocs manual

The function read_met_monotonize() needs a definition of a timer here:

after ./build.sh nc4,there are some errors, but ./build.sh nc2 is no problem

***** 12 FAILURES! *****
Command exited with non-zero status 1
0.34user 0.29system 0:00.62elapsed 103%CPU (0avgtext+0avgdata 4236maxresident)k
0inputs+0outputs (0major+18632minor)pagefaults 0swaps
Makefile:3451: recipe for target 'dt_arith.chkexe_' failed
make[4]: *** [dt_arith.chkexe_] Error 1
make[4]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
Makefile:3436: recipe for target 'build-check-s' failed
make[3]: *** [build-check-s] Error 2
make[3]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
Makefile:3431: recipe for target 'test' failed
make[2]: *** [test] Error 2
make[2]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
Makefile:3207: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
Makefile:715: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1
root@LAPTOP-9C6L8HRA:/usr/local/meteo/mptrac/libs# cd build/

Overview

• A Fortran wrapper for MPTRAC has been developed in the context of the natESM LAGOON sprint.
• The code for the wrapper has been developed separately from the MPTRAC git repo, but should be integrated in the master branch.

Open tasks

• fix remaining issues with wrapper code:
  • fix memory issue when using the wrapper on a notebook (Ubuntu) rather than JUWELS
  • handling of pointer-to-pointer in get_met() function
  • use of argc/argv command line arguments in the wrapper
• adapt Makefile for compiling the wrapper:
  • add a flag WRAPPER to switch on/off the compilation of the Fortran wrapper (if needed)
  • allow for selection of the Fortran compiler (gfortran, nvfortran)
• improve test case:
  • check that Fortran wrapper code uses the same dimensions as the C code (EX, EX, EP, NP)
  • print selected variables from ctl_t, atm_t, met_t in trac_fortran to a logfile, compare logfile with reference output to make sure C-to-Fortran mapping of variables/arrays is correct
• documentation:
  • add markdown page to user/developer manual describing the wrapper
  • add doxygen documentation to Fortran wrapper and any additional/modified C code

Is your feature request related to a problem?

• Provide some simple examples of python scripts helping new users to work with MPTRAC simulation output.

Describe the solution you'd like

• Examples should show how to read atm- and grid-files in ASCII file format and make map plots of the data.
• Put Python code examples in a new directory ./projects/python

Additional context

• Add some context on python usage to the mkdocs documentation?

Hi, i have met some issues when i install MPTRAC onto server linux system.
Describe the bug

• sometimes it succeeded after running a build script, but sometimes it failed with same issue as #4

• when it succeeded, i tried to compile and check the installation, but it failed with following errors, more details can be seen in attachment. The errors show some issues with varname and longname size, but it still failed after changing the varname[LEN] and longname[LEN] in libtrac.h.

• The errors show some issues with varname and longname size, but it still failed after changing the varname[LEN] and longname[LEN] (from 5000 to 5100) in libtrac.h.

Environment
i use the Rocky Linux server

log_check.txt

• I downloaded surface variables corresponding to this selection - https://apps.ecmwf.int/data-catalogues/era5/?class=ea&stream=oper&expver=1&type=an&year=2005&month=jun&levtype=sfc - at a resolution of 0.3x0.3
• ML level data was also downloaded at the same resolution and the two were emerged in python (as the two files had different GRIB editions and CDO was apparently not able to handle that)
• Renamed u10 as u10m and modified attribute GRIB_cfVarNam to store the same, (as a try to address the 'invalid name' issue that followed); similarly for v10m and t2m
• LINUX output/ error as follows:

  Read meteo data: data_in/ea_2005_06_20_00.nc
  Read meteo grid information...
  Time: 172540800.00 (2005-06-20, 00:00 UTC)
  Number of longitudes: 434
  Number of latitudes: 217

Error (libtrac.c, read_met_grid, l3578): NetCDF: Invalid dimension ID or name

Could you please help me debug? Thank you.

Use the MPTRAC library to run trajectories as a replacement for the CLaMS trajectory module.

• Install MESSy/CLaMS and set up a test case with a climatological run.
• Identify potential "access points" to load functions of the MPTRAC library and to replace code from CLaMS
• Understand how to compile and use libraries in MESSy
• Implement converter functions from CLaMS to MPTRAC and vice versa.
• Implement functions to read the config for MPTRAC, either as name lists or by giving the pathway to the config.ctl file to the name list of CLaMS.
• Test using the library in MESSy/CLaMS by using read_ctl
• ... then by using get_met
• ... and so on ...
• When all components can be used run the entire script and intercompare results with the default run.

Collection of ideas for assessing the diffusion schemes in MPTRAC:

• check for dependencies of simulated diffusion on the time step of the model data or the meteo data

• estimates of vertical diffusivities from aircraft measurements (Wagner et al., 2017)

• look for diffusivity coefficients applied in Eulerian models? literature review?

• compare diffusion of isentropic and kinematic trajectories

• look at wind fluctuations from ESA Aeolus measurements: https://earth.esa.int/eogateway/missions/aeolus

C to Fortran Interface for the Library...

• Define structs in the interface
• Define functions in the interface
• Adapt the Makefile to compile everything correctly ...
• Implement high-level functions in Fortran to initialize, run and finalize MPTRAC
• Write kind of a trac.f90 as a Fortran time loop to run a test case...
• Write tests for the interface / establish workflow that makes interface errors transparent...

Is your feature request related to a problem?

• the library build script (libs/build.sh) can be improved by additional functionality

Describe the solution you'd like

• add a command line argument so that the number of threads for parallel builds can be selected (`make -j')
• add command line arguments so that the user can select which libraries to build (to avoid time-consuming builds of GSL or netCDF, if the software is already available)
• add an option to download the tarballs of the libraries from their respective sources from the web rather than including them in the MPTRAC git repository?
• perhaps implement this as a Makefile rather than a bash script?

Additional context

• pull request by Yen-Sen: #14

Describe the bug

MPTRAC nightly builds (https://datapub.fz-juelich.de/slcs/mptrac/nightly_builds/) show that the runtime of the physics timers on JUWELS Booster significantly increased on 3 Nov 2023, when the new stage 2024 was enabled. Switching back to stage 2023 on 10 Nov reproduced the original runtime:

Additionally, the new stage causes an issue in gpu_test sample.tab output:

To Reproduce

Rerun the test case at: /p/fastdata/slmet/slmet111/model_data/mptrac/nightly_builds/juwels-booster/run.sh

Expected behavior

Need to further investigate this issue and find the root cause.

Maybe next to updating the software stage also other changes of the JUWELS Booster system config were introduced?

Is your feature request related to a problem?

• MPTRAC may have limited capabilities for calculating trajectories in the boundary layer due to using pressure as vertical coordinate. Meteo data are converted from model level to pressure levels for usage with MPTRAC, which is causing interpolation errors. The pressure coordinate is not terrain-following.
• More recently, Jan added the option to calculate diabatic trajectories, which provides the option to use meteo data on model levels rather than pressure levels

Describe the solution you'd like

• Conduct a comparison of trajectory calculations for the boundary layer (model level versus pressure level meteo data) so that we can get an idea of how large the deviations are.
• Conduct a comparison with HYSPLIT online trajectories (or other models such as FLEXPART or CLaMS) as a reference.
• Assess what would be needed to make MPTRAC suitable for boundary layer applications.

Is your feature request related to a problem?

• Check the definition of pressure levels sets in level_definitions() in libtrac.c.

Describe the solution you'd like

• Add additional pressure levels between 1013.25 and 1044 hPa to achieve finer grid spacing. This might be critical for proper calculation of meteo variable that depend on the near-surface data (e.g. CAPE or PBL).
• Compare selected level with previous definition used for CDO ml2pl operator to convert ECMWF data from model levels to pressure levels.

Reference

• ECMWF level definitions: https://confluence.ecmwf.int/plugins/servlet/mobile?contentId=111155849#content/view/111155849

when I change ubuntu version to Ubuntu 20.04.4 LTS by windows10
after ./build.sh nc4 , there are also some problems:
***** 12 FAILURES! *****
Command exited with non-zero status 1
0.37user 0.20system 0:00.61elapsed 94%CPU (0avgtext+0avgdata 4200maxresident)k
0inputs+0outputs (0major+18348minor)pagefaults 0swaps
make[4]: *** [Makefile:3451: dt_arith.chkexe_] Error 1
make[4]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
make[3]: *** [Makefile:3437: build-check-s] Error 2
make[3]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
make[2]: *** [Makefile:3431: test] Error 2
make[2]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
make[1]: *** [Makefile:3208: check-am] Error 2
make[1]: Leaving directory '/usr/local/meteo/mptrac/libs/build/src/hdf5-1.12.1/test'
make: *** [Makefile:715: check-recursive] Error 1

Is your feature request related to a problem?

• a significant amount of runtime of the simulations is required for reading meteo data (in particular for ERA5 data)

Describe the solution you'd like

• implement asynchronous file-I/O so that meteo data for the next time interval are being read ahead of time while trajectories calculations for the current time interval are conducted in parallel

Describe alternatives you've considered

• compression of meteo data to reduce waiting time for file-I/O

Additional context

• Example of runtime measurements of a recent GPU run on JUWELS Booster with 100 million particles and using ERA5 data (packed binary):

TIMER_READ_MET_BIN = 35.306 s    (min= 1.09297 s, mean= 1.41225 s, max= 2.2265 s, n= 25)
TIMER_GROUP_INIT = 0.553 s
TIMER_GROUP_MEMORY = 19.416 s
TIMER_GROUP_INPUT = 36.961 s
TIMER_GROUP_PHYSICS = 89.866 s
TIMER_GROUP_OUTPUT = 32.075 s
TIMER_TOTAL = 178.871 s

• Reading the ERA5 requires about 20% of the total runtime.

MPTRAC routines could be made available to other Models (CLaMS) more easily if MPTRAC is properly organized into a library containing those routines (libtrac.h/libtrac.c), and a time loop (trac.c).

• Move routine declarations and macros etc. to libtrac.h, from trac.c
• Eventually, rename and reorder the routines.
• Create high-level functions for the initialisation, running and finalization of the library tools.
• Change the compile process if needed ...
• Test library in a set-up separate from MPTRAC...

Is your feature request related to a problem?

• The new mixing module in trac.c is limited to operating on CPUs. For GPU runs, particle data will be transferred form GPU to CPU memory, mixing will be calculated on the CPUs, and data will be transferred back to GPUs.

Describe the solution you'd like

• Mixing should be calculated directly on the GPUs, avoiding the data transfers between CPU and GPU memory.

Additional context

• The code might be rewritten for GPUs, following the example of module_sort().

Is your feature request related to a problem?

• Users might have difficulties compiling MPTRAC before they can run it on Juelich HPC systems.

Describe the solution you'd like

• Provide an EasyBuild installation of MPTRAC on JURECA and JUWELS so that the model can be used by loading it as a module.
• Check back with Sabine about EasyBuild configuration.
• Installation in $USERSOFTWARE of meteocloud data project.

Describe alternatives you've considered

• Prepare binaries with static compilation that can be copied to/from different machines.

Additional context

• Think about proper solutions for the automatic deployment of code?

• The CLaMS group identified a bug in polar trajectories using ERA5 data. Air parcels sometimes stick to the pole (see plot below):

• The issue seems to be related to a new interpolation scheme of the meteo data on MARS implemented in 2019.

• More information can be found in the meteocloud issue tracker: https://jugit.fz-juelich.de/slcs/meteocloud/-/issues/66

• Identify and further investigate a test case for MPTRAC

• Add a fix to the meteo data during meteo data preprocessing?