Move scripts for generating WW3 inputs

Question

Move scripts for generating WW3 inputs

Opened this issue a year ago · 5 comments

Possibly move some of the contents of WW3_PreProc?

@ezhilsabareesh8, does it make sense to move GenGrid.py, update it to include info in the output files about how they were generated (see here) and then update the OM2_1.* files in the configuration repo?

Answer 1 · 2024-01-24T05:02:26.000Z

Thanks @dougiesquire. I think moving GenGrid.py to om3-scripts makes sense and l also think we could leave all the OM2_1.* in the config repo since these files can be regenerated with GenGrid.py. I will update GenGrid.py and move it to om3-scripts.

Answer 2 · 2024-01-24T05:09:24.000Z

Re the OM2_1.* files, can they contain comments? If so, it would be good to update them to include an auto-generated comment with the url and commit hash to the script used to create them.

Answer 3 · 2024-01-24T23:01:25.000Z

Re the OM2_1.* files, can they contain comments?

Regarding the OM2_1.* files, they cannot include comments. These files contain Lat, Lon, and depth data and adhere to a specific format for compatibility with the WW3 F77 routines, which rely on a predefined structure for proper interpretation.

Answer 4 · 2024-01-24T23:31:07.000Z

Regarding the OM2_1.* files, they cannot include comments

Rats. I guess the script could generate a README with the provenance info for the files, or am I getting carried away?

Answer 5 · 2024-01-29T00:54:39.000Z

The script could only generate WW3_grid executable - compatible latitude, longitude, and depth files from OM2's ocean_hgrid and topog data. We can include a separate readme file with information on OM2_1.* files.