Indicator log file for gridded output in production/GFS.v16

[MatthewMasarik-NOAA]

Pull Request Summary

Adds the writing of a log file to indicate that a particular gridded output file has finished writing.

Description

• Provide a detailed description of what this PR does.

  • This indicator file will be used to signal to the post-processing scripts that a gridded output file is ready to be accessed and read. This is implemented in a simple way by reusing the Fortran IO unit number for the gridded output once that file has already been closed (thanks to @JessicaMeixner-NOAA for the suggestion!).

• What bug does it fix, or what feature does it add?

  • This fixes an infrequent occurrence in the global-workflow where a gridded output file has an attempted read on it before the file has completed writing.

• Is a change of answers expected from this PR?

  • No. This just addresses an issue that has occurred in post-processing.

Please also include the following information:

• Add any suggestions for a reviewer
  • @JessicaMeixner-NOAA
• Mention any labels that should be added:
  • bug.
• Are answer changes expected from this PR?
  • No.

Issue(s) addressed

• Please list any issues associated with this PR, including those the PR will fix/close. For example:
  • fixes GFSv16 production: add logfile write functionality to indicate gridded output is complete #1321

Commit Message

w3iogomd.ftn: Add indicator log file write for gridded output

Check list

• Branch is up to date with the authoritative repository (NOAA-EMC) develop branch.
• Checked the checklist for a developer submitting to develop.
• If a version number update is required, checked the updating version number checklist.
• If a new feature was added, a regression test for testing the new feature is added.

Testing

• How were these changes tested?
  • Testing during development was done in standalone mode with a modified regtest which is verified by a separate process checking for out_grd files and indicator files.
  • Final testing was performed within global-workflow:dev/gfs.v16 and passed b4b.
• Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
  • N/A.
• Have the matrix regression tests been run (if yes, please note HPC and compiler)?
  • No. It is not a requirement for the production/GFS.v16 branch.
  • Functionality and b4b were confirmed in the global-workflow testing.
• Please indicate the expected changes in the regression test output, (Note the list of known non-identical tests.)
  • No changes expected, though indicator logs will now be present in the run directory.
• Please provide the summary output of matrix.comp (matrix.Diff.txt, matrixCompFull.txt and matrixCompSummary.txt):
  • Not required for production/GFS.v16.

[JessicaMeixner-NOAA]

Thanks for making this update @MatthewMasarik-NOAA