I am getting an error trying to open a surrogate file used for creating othar gridded emissions with GRDMAT. I have been using the monthly othar script with this surrogate for other sectors without any difficulty. I have attached the log file showing the error (grdmat_othar_jan_2024_assessment_ADMF36.log) where the surrogate file (CA_100_NOFILL.txt) seems to be found plus some additional pathing information.
I have attached the script for creating the othar emissions (including turning on the SMK_USE_FALLBACK option), the modified agref, amgref and gspro files (to remove the Mexico entries and add any missing SCC codes for any particular provinces), the input emission files, the surrogate file and log files showing any errors (all other log file showed normal completion of the SMOKE process up to the gridding with GRDMAT).
Your error in grdmat is showing that another path is concatenated to the end of your surrogate file name.
*** ERROR ABORT in subroutine GRDMAT
Could not open input surrogate file/run/media/root/DISK1_4TB/ADMF/2024_assessment/smoke_inputs/2019/ge_dat/gridding/surrogates/1980ADMF36_CA/CA_100_NOFILL.txt/run/media/root/DISK1_4TB/ADMF/2024_assessment/smoke_inputs/
The SRGPRO variable in your script is parsed through another script to get the SRGPRO_PATH that is simply the directory that contains the surrogate name in your SRGPRO variable: /run/media/root/DISK1_4TB/ADMF/2024_assessment/smoke_inputs/2019/ge_dat/gridding/surrogates/1980ADMF36_CA/
I verified that passing the SRGPRO variable through the parser functions as expected on our system. The surrogate file name is then concatenated to the SRGPRO_PATH using the file name from the surrogate description file (SRGDESC).
I did not see the surrogate description file included in your package. Can you check your surrogate description file (srgdesc_36ADMF_70x55_CA) and verify that you do not inadvertently have a path in the third semicolon-delimited column that specifies the surrogate file name?
Thanks for taking a look at this. I think the surrogate description file is correct but I have attached it (with the added .txt extension so I can upload it) for your review. My apologies, I thought I had attached it in my original post.