global-workflow icon indicating copy to clipboard operation
global-workflow copied to clipboard

Global Superstructure/Workflow supporting the Global Forecast System (GFS)

Results 100 global-workflow issues
Sort by recently updated
recently updated
newest added

### What new functionality do you need? Updated modules for all subcomponents to point to the UFS's hpc-stack suite in /apps/test/hpc-stack/i-19.1.3.304__m-8.1.12__h-1.14.0__n-4.9.2__p-2.5.10__e-8.4.2. ### What are the requirements for the new functionality?...

feature

**Description** We need a review of all files generated in COM and update filenames to NCO standards. ATM files are mostly good here, but wave and the new coupled filenames...

Epic

### Target fix directory am ### Type of change Cleanup and reorganization ### Any workflow changes needed? Fix version only ### Related issues https://github.com/NOAA-EMC/global-workflow/issues/2403

Fix Files

### Description Update both the operational GFSv16 and developmental GFSv17 systems to use the new `RTOFSv2.4.0`. "The scheduled handoff to NCO is March 11. Implementation for early June." - [...

production update

**Description** As we move towards the merger of GEFS into the GFS system, global workflow needs to be updated to archive the additional output created when running a forecast ensemble....

feature

### What new functionality do you need? In many places, our code waits for a file to exist by repeatedly checking its existence, then sleeping for a period if it...

maintenance

### What new functionality do you need? UFS-DA jobs currently look within the UFS-DA repo for a lot of settings (parm files, yaml files, etc.). To meet EE2 standards, all...

feature

**Description** Filenames currently with forecast length appended will run out of digits with the 48 forecast hours used for GEFSv13. Suggestion is to change filename based on ISO timestamp YYYY-MM-DDTHH:MM:SSZ...

### What new functionality do you need? Many gempak scripts have hard-coded forecast hours. These are difficult to maintain, are sometimes inconsistent or confusing, and can fall outside the bounds...

feature

**Description** Global workflow uses `global_soilmgldas.statsgo.t94.192.96.grb` and `global_slmask.t1534.3072.1536.grb` for the test c48 (ATM only). On the other side, ufswm uses `global_soilmgldas.statsgo.t92.192.94.grb` and `global_slmask.t62.192.94.grb` instead. As the c48 is a low resolution...