routing-only datastream

[quinnylee]

See issues CIROH-UA/ngen-datastream#269 and CIROH-UA/forcingprocessor#28

Once we have a workflow for our input data and directories, what needs to happen next to integrate the routing-only datastream into a regularly-scheduled NRDS run?

[JordanLaserGit]

DataStreamCLI includes a configuration step where many files/options are read and parts of the datastream (realization, forcings processing) are modified/configured. An example of why this is necssary is the FORCING_SOURCE option, which allows a user to pick their source of forcings in a single string (e.g. NWM_SHORT_RANGE_14). This string is interpreted and files like a forcingprocessor configuration file are created.

In order to get DataStreamCLI able to perform the workflow for nwm channel routing and troute, the functionality to create the proper conf_fp must be added in this function here.

datastreamcli/src/datastreamcli/configure_datastream.py

Line 120 in 2930a3a

def create_conf_nwm(args):

The syntax for this "forcing source" can be something like NWM_CHRT_SHORT_RANGE_14 and then we can just check for CHRT in the string and modify varinput accordingly.

datastreamcli/src/datastreamcli/configure_datastream.py

Line 233 in 2930a3a

"varinput" : varinput,

[quinnylee]

The NWM to NGEN map linked here needs to live somewhere in that docker image so that I can edit create_conf_fp https://alabama.box.com/s/kpcy8jg772bqpusouzt7wx1gfjn00spb

[quinnylee]

See the routing-only branch for updates -- I have made a separate routing-only bash script to bypass all the stuff that is not necessary.