When running casegen using LAM data, @egrell discovered that the UFS_case_gen.py script fails if providing ij indices. The same failure also exists when using global RTs.
The issue is main() calling _find_loc_indices_UFShistory(), which only has logic to find the indices nearest to the provided lon/lat point, hence why latitude/longitude are not subscriptable, since we are only providing ij. On the other hand, _find_loc_indices_UFSIC does have logic to handle either provided lon/lat or indicies. Can this similar logic be added to the problematic subroutine?
Note, the ensemble wrapper script does not even have an option for providing ij.
When running casegen using LAM data, @egrell discovered that the UFS_case_gen.py script fails if providing ij indices. The same failure also exists when using global RTs.
The issue is main() calling _find_loc_indices_UFShistory(), which only has logic to find the indices nearest to the provided lon/lat point, hence why latitude/longitude are not subscriptable, since we are only providing ij. On the other hand, _find_loc_indices_UFSIC does have logic to handle either provided lon/lat or indicies. Can this similar logic be added to the problematic subroutine?
Note, the ensemble wrapper script does not even have an option for providing ij.
Example command:
./UFS_case_gen.py -ij 142 69 -d 20210322060000 -i /scratch1/BMC/gmtb/Tracy.Hertneky/ccpp/case_gen/ufs/control_c48_intel_1h/INPUT -g /scratch1/BMC/gmtb/Tracy.Hertneky/ccpp/case_gen/ufs/control_c48_intel_1h/INPUT -f /scratch1/BMC/gmtb/Tracy.Hertneky/ccpp/case_gen/ufs/control_c48_intel_1h -n test_ij_rt -t 5
Error: