The chgres_cube driver needs a --leadtime argument.

[christinaholtNOAA]

If this is a bug, please consider using the Bug Report template.
Your issue may already have been created!

Please look through the existing issues on the Issue tracker to see if this issue has been created.
If so, please consider using that Issue to add any additional information.

Description

When running the chgres_cube driver to create lateral boundary conditions, the namelist expects the date information to be consistent with the valid-time of the forecast file being processed, however, these forecast times are prepared for a given cycle, so we will need to pass both pieces of information to get the expected behavior -- the rundir has cycle information, but the namelist has cycle + leadtime information.

Requirements

Describe alternatives you've considered

This could be handled as an environment variable, but would be horribly inconsistent with the other drivers that do have an optional lead time argument.

Acceptance Criteria (Definition of Done)

• The chgres_cube driver can be appropriately configured for both initial and lateral boundary condition tasks with output behavior similar to that in existing apps.
• Docs and tests updated to support the new argument.