Skip to content
André Castro edited this page Aug 27, 2024 · 1 revision

Parsivel and Config files

In order to produce netCDF with the correct metadata for each Parsivel, a general configuration file (configs_netcdf/config_general_parsivel.yml) is used in addition to a config file for each instrument or campaign (ie. configs_netcdf/config_PAR_009_LUTJEWAD.yml or (configs_netcdf/config_PAR_008_GV.yml) which includes only the parameters that change from instrument to instrument

To run the parsivel data acquisition script, either manually or as a service, it is necessary to declare the config file, corresponding to that specific Parsivel. ie. python main.py -c configs_netcdf/config_PAR_009_LUTJEWAD.yml

Parsivel Filename Conventions

The filename of Parsivel output files are based on:

  • date
  • instruments config file's keys:
    • site_name
    • station_code
    • sensor_name

Avoid using empty spaces (use _ instead) in the values of these keys, as filenames with spaces are more difficult to work with

Filename Conventions for Sites

file names are created by export_disdrodlDB2NC.py script and config files, with the following patters

f"{args.date.replace('-', '')}_{site_name}-{st_code}_{sensor_name}.nc"

Example: 20240826_Green_Village-GV_PAR008.nc

Filename Conventions for Campaigns

For campaigns, use the campaign code (should include the prefix Camp) in the station_code key

Example: 20230901_Lutjewad_Atmospheric_Station-CampRITA2022_PAR009.nc

Clone this wiki locally