Database

Exploration

To check paths and files present in the dabase and used by the notebooks of the documentation.

User (over) specification

All paths and files are listed in osdyn.cfg files present throughout the library (lib/osdyn). As you may have saved a copy of the files (or close ones) in other directories, please create a ~/.config/config/osdyn.cfg and precise all your own different paths. In the example below, we have assigned different paths present in osdyn.cfg file under $PYTHONPATH/osdyn/obs/bathy/emodnet, $PYTHONPATH/osdyn.obs.radar.toulon directories and so on. Any variable of osdyn.cfg can be changed this way: it’s an over-assignment because the user specification (in ~/.config/config/osdyn.cfg) override the default ones.

[osdyn.obs.bathy.emodnet]
path_2018 = /export/home1/valerie/DATA/EMODNET/2018

[osdyn.obs.radar.toulon]
path = /export/home1/valerie/DATA/RADARHF

[osdyn.obs.satellite.xtrack]
path_main = /export/home1/valerie/DATA/XTRACK

[osdyn.obs.satellite.mdt]
path_rio = /export/home1/valerie/DATA/MDT

[osdyn.grcm.nemo]
path_medrys1v1 = /export/home1/valerie/DATA/NEMO

[osdyn.grcm.arome]
path_previ = /export/home1/valerie/DATA/AROME/PREVIMER

[osdyn.grcm.arpegehr]
path_previ = /export/home1/valerie/DATA/ARPEGE_HR/PREVIMER

[osdyn.grcm.era5]
path = /export/home1/valerie/DATA/WW3/FORCING/ERA5/NC4

[osdyn.grcm.ecmwf]
path = /export/home1/valerie/DATA/WW3/FORCING/ECMWF/NC4

Pre-processing

This preprocessing part is optional but is really powerful to speed up the reading of the data sets (see intake).

Create intake description files

The following notebooks detail some specific readers. The last section gives some links to different diagnostics.

To take full advantage of the intake catalog efficiency, the gridfile must be introduced into the catalog. In case the grid file of your dataset is missing, notebooks are available below. Equivalent scripts are also available under osapp-tools repositery.

Create a grid file for Mars data set