Ceil/Vis Retro Verification

Ceiling¶

1. Log onto the HPC (Jet or Hera) where your output grids are stored as the role.amb-verif role account. If you cannot become role.amb-verif, please let us know and we will have you added.

2. Reload observations for ceiling with the following command:

   /home/role.amb-verif/ceiling/get_ceil_obs_retro.pl {start_epoch} {end_epoch}

3. Go to the directory /home/role.amb-verif/ceiling/retro_data. If your retro is not already linked, create the soft links to the cycle-level directory of your output with a case name of your choosing to highlight the experiment, with the available conventions:

   ln -s {case_cycle_directory} {experiment_name}

4. Run retro ceiling verification (be sure that the case name starts with the correct prefix). Change the 0 to 1 if you’re reprocessing your verification. Alternatively, copy and modify the bash script “retro_driver.sh” with your relevant experiment name and time period to use with qsub if you want to submit your job to the back-end nodes.

   For standard/legacy ceiling field:
   /home/role.amb-verif/ceiling/ceil_driver_retro.pl {retro_name} {start_epoch} {end_epoch} 0

   For experimental ceiling diagnostic #1:
   /home/role.amb-verif/ceiling/ceil_driver_retro_exp_diag.pl {retro_name} {start_epoch} {end_epoch} 0

   For experimental ceiling diagnostic #2:
   /home/role.amb-verif/ceiling/ceil_driver_retro_exp_diag2.pl {retro_name} {start_epoch} {end_epoch} 0

5. The various ceiling-related diagnostics are summarized briefly in this document.

6. Results should appear on MATS the following morning, but a metadata scan can be run to expedite the process. As role.amb-verif on Hera/Jet, run:

   For standard/legacy ceiling field:
   ~role.amb-verif/mats_metadata/update_metadata_ceiling.py {case_name}

   For experimental ceiling diagnostic #1:
   ~role.amb-verif/mats_metadata/update_metadata_ceiling.py {case_name}_exp_diag

   For experimental ceiling diagnostic #2:
   ~role.amb-verif/mats_metadata/update_metadata_ceiling.py {case_name}_exp_diag2

   If you see a >0 number of records (‘numrecs’) found in the output, your retro is stored in the database with metadata enabled.

7. The final step is to refresh the metadata inside the MATS client by refreshing the Ceiling/Visibility app page a few times in your browser.

Visibility¶

1. Log onto the HPC (Jet or Hera) where your output grids are stored as the “role.amb-verif” role account. If you cannot become role.amb-verif, please let us know and we will have you added.

2. Reload observations for visibility with the following command:

   /home/role.amb-verif/visibility/get_vis_obs_retro.pl {start_epoch} {end_epoch}

3. Go to the directory “/home/role.amb-verif/visibility/retro_data”. If your retro is not already linked, create the soft links to the cycle-level directory of your output with a case name of your choosing to highlight the experiment, with the available conventions:

   ln -s {case_cycle_directory} {experiment_name}

4. Run retro visibility verification (be sure that the case name starts with the correct prefix)

   /home/role.amb-verif/visibility/retro_driver.tcsh {retro_name} {start_epoch} {end_epoch}

5. Results should appear on MATS the following morning, but a metadata scan can be run to expedite the process. As role.amb-verif on Hera/Jet, run

   ~role.amb-verif/mats_metadata/update_metadata_visibility.py {case_name}

   If you see a >0 number of records (‘numrecs’) found in the output, your retro is stored in the database with metadata enabled.

6. The final step is to refresh the metadata inside the MATS client by refreshing the Ceiling/Visibility app page a few times in your browser.