Centralize test data and/or fix files

guoqing-noaa commented 6 days ago

To start a conversation on centralizing the test data and/or fix files

I made a preliminary attempt on PR #91, the relevant code snippet:

case ${MACHINE_ID} in
  hera)
    RDAS_DATA=/scratch1/NCEPDEV/fv3-cam/RDAS_DATA
    ;;
  jet)
    RDAS_DATA=/lfs4/BMC/nrtrr/RDAS_DATA
    ;;
  orion|hercules)
    RDAS_DATA=/work/noaa/rtrr/RDAS_DATA
    ;;
  *)
    echo "platform not supported: ${MACHINE_ID}"
    ;;
esac

Since the role.rrfs-fv3-cam account only works on Hera, the current centralized location uses the fv3-cam disk space only on Hera. On Jet, Orion/Hercules, a GSl role account "rtrr" is used.

We would also like to get the role.rrfs-fv3-cam account to access HPSS so that we can archive RDAS_DATA to a permanent HPSS space directly.

delippi commented 6 days ago

@guoqing-noaa, thanks for getting this started. This has been in the back of my mind to start working on as well. Do we want to update the RDAS/hera.intel module (and other affected files) now since that seems ready to go or wait for the role account to work on all machines and do them all in one PR?

guoqing-noaa commented 6 days ago

@guoqing-noaa, thanks for getting this started. This has been in the back of my mind to start working on as well. Do we want to update the RDAS/hera.intel module (and other affected files) now since that seems ready to go or wait for the role account to work on all machines and do them all in one PR?

Thanks! I can do that using the current configuration while waiting for the role.rrfs-fv3-cam account to work on all platforms.

NOAA-EMC / RDASApp

Centralize test data and/or fix files #93