Repository navigation
Conversation
jbatterman
left a comment
jbatterman
left a comment
There was a problem hiding this comment.
Looking forward to seeing how this fits in with our workflow!
| "RTS_EXTRACT_START_TIME", | ||
| "RTS_FORECAST_TIME", | ||
| "RTS_END_TIME", | ||
| ) |
There was a problem hiding this comment.
Will this list of forecast variables be customizable if an office needs to pull anything else?
There was a problem hiding this comment.
Not unless you edit the script. Are there other variables you would want? I think any ResSim scripting is really a bridge too far, but anything from RTS context is probably easy enough to add.
There was a problem hiding this comment.
We also pull model alternatives from the forecast run and we grab the FPart from the forecast run model alts, unless I'm misunderstanding the environment variable name and you have those in your list already.
There was a problem hiding this comment.
Something else I just thought of. Some of our scripts run an extract to process while completing the rest of the setup. We can probably change our workflow, but is that something we'd do in the launcher piece before heading out to Python?
I updated this python script launcher example to renew and pass the RTS CDA token, pass some RTS env variables (current watershed, active run, forecast window etc...), and stream stout and staderr to output window. A bit of a hack but might work until cpython is more integrated into RTS.
EDIT: AI assisted