Fix path to CIME tools - Githubissues

billsacks commented 2 years ago

Fixes #45 . See description there for details.

Testing: ran the following tests from CTSM master with ccs_config updated to this branch:

SMS_D_Ld1.f10_f10_mg37.I1850Clm50BgcCrop.cheyenne_gnu.clm-default (run via create_test)
SMS_Ld5_D_P48x1.f10_f10_mg37.IHistClm51Bgc.izumi_nag.clm-decStart (run via run_sys_tests)

billsacks commented 2 years ago

I have now run the full aux_clm test suite on izumi with this change and it passes for me now (before this change, all tests were failing at runtime on izumi). So as far as I'm concerned this is ready to be merged.

billsacks commented 2 years ago

One difference I noticed between izumi and cheyenne that might explain the behavior on izumi: On cheyenne, you can load and unload python modules without it impacting the PYTHONPATH environment variable. On izumi, however, loading or unloading a python module resets your PYTHONPATH, deleting anything that had been added there. There are module loads of python both in my dot files and in config_machines for izumi. (That still doesn't explain why @ekluzek couldn't reproduce this, because he has a similar module load of python in his dot file – unless there is different behavior between bash (me) and tcsh (Erik I think).) Anyway, I need to stop trying to figure out why this problem only appears in some places... now it will be fixed and it's probably not worth understanding in excruciating detail.

ESMCI / ccs_config_cesm

Fix path to CIME tools #46