In conus404_ba_hourly README.md please define how to update FIRST_STEP and LAST_STEP when extending time.

[mirizarry-ortiz]

*After extend-time is run, I assume that one has to rerun submit_c404-ba_hourly_workflow.sh. How do we figure out the new values for FIRST_STEP and LAST_STEP? You mentioned that there was a way to check that. Can you share that with us?

[shaider-usgs]

@pnorton-usgs I just re-watched the recording of our meeting and you mentioned a notebook.

[pnorton-usgs]

@mirizarry-ortiz @shaider-usgs - I've added a new command (info) to the c404-ba_hourly_workflow script (see PR #16 ). This command will show the starting and ending dates and chunks for the destination zarr dataset in the YAML file. The output looks similar to this:

base_date: 1979-10-01 00:00:00
chunk_plan={'time': 144, 'x': 175, 'y': 175}
First date: 1979-10-01T00, chunk: 0 (1979-10-01T00 to 1979-10-06T23)
Last date: 1980-01-31T23, chunk: 20 (1980-01-29T00 to 1980-02-03T23)
INFO: Last chunk in dataset is a partial chunk

You could run this command to get the chunk index for the last timestep prior to extending the dataset. The last date chunk value would then become the FIRST_STEP value (if it was a partial chunk) after extending the dataset (you could also set it to earlier chunks if you were wanting to rewrite existing chunks in the dataset). After extending the dataset you can then run the info command again to see what the new LAST_STEP chunk value should be.

[mirizarry-ortiz]

Great! Thanks Parker! I think it's probably the safest to set FIRST_STEP equal to the last date chunk value, in case it is a partial chunk.