You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In adding tests for the streamflow/watershed API, I discovered that if a file does not have a run associated with it, then the models API endpoint fails. The key code is this:
{dfv.file.run.model.short_name for dfv in ensemble.data_file_variables}
where ensemble is a pycds.Ensemble object.
Overlooking the fact that there are likely alternative queries more robust to absent links between ensemble and model, there's the question of whether we already do or plan to allow for files without runs. I am not sure how we resolved this question, so this issue may just be a placeholder for retrieving a previous decision that resolves this problem while I continue working on the watershed API.
The text was updated successfully, but these errors were encountered:
Yeah, I'd argue that we should only be querying files that are linked to the runs table (and that non-model output should at least have something). If you both agree, then this could make a good-first-issue.
In adding tests for the
streamflow/watershed
API, I discovered that if a file does not have a run associated with it, then themodels
API endpoint fails. The key code is this:where
ensemble
is apycds.Ensemble
object.Overlooking the fact that there are likely alternative queries more robust to absent links between ensemble and model, there's the question of whether we already do or plan to allow for files without runs. I am not sure how we resolved this question, so this issue may just be a placeholder for retrieving a previous decision that resolves this problem while I continue working on the watershed API.
The text was updated successfully, but these errors were encountered: