mesh_maker adds extra longitude (360) to mesh file

[slevis-lmwg]

In my blended TRENDY2024-GSWP3 datm case, the mesh_maker tool added an unnecessary longitude (360) to the mesh file. Other methods (ESMF_Scrip2Unstruct and mesh_mask_modifier) did not. The faulty mesh file did NOT crash the model but did change answers in the first column (0-degree meridian).

Modified comment by @slevis-lmwg from #2403 (comment)

[samsrabin]

I know you're busy, but would you also try generating the mesh file with subset_data? Or if you want to send me the mesh_maker command, I can try it.

[slevis-lmwg]

mesh_maker is under tools/site_and_regional

[samsrabin]

I mean the actual call of mesh_maker you used that included the extra longitude, so I can test subset_data with the same setup.

[slevis-lmwg]

Sorry for misunderstanding @samsrabin
./mesh_maker --input clmforc.CRUJRAv2.5_0.5x0.5.TPQWL.1901_wlandmask_and_permuted.nc --output mesh_new.nc --lon lon --lat lat --mask landmask
from
git describe: branch_tags/ctsm5.3.n04_ctsm5.2.028

[slevis-lmwg]

I ran it in this directory
/glade/derecho/scratch/slevis/temp_work/new_rawdata/tools/site_and_regional

[samsrabin]

Oops, sorry for misunderstanding. I guess subset_data can't be given an input dataset to work off of.

[samsrabin]

@adrifoster will mention this in the discussion she's going to start.