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
When setting a new model run, we need to make sure not only that the models show and are updated, but that the indices used are consistent to what is shown in the model catalog.
@hvarg is working towards a new table that includes the index/indicator, and also models and output variables of those models that can be used for selecting those indices.
I am not sure this will be ready for next evaluation, but it's something we could try.
The text was updated successfully, but these errors were encountered:
To do this, and solve #519 too, we need to use the data on the model catalog directly. Right now the indicators are necessary to create a new task, but the first step is selecting a model setup, so I think we can get the indicator from the model itself and set it then.
The idea is to allow the user to select model setups from different approaches. We could search models by name, indicator, keywords, etc. and the indicator will be set when the model is selected.
@varunratnakar what do you think about this change? If we do this the only data required to create a new task will be the dates.
This change will break the task-thread relationship, now task group threads by an indicator.
When setting a new model run, we need to make sure not only that the models show and are updated, but that the indices used are consistent to what is shown in the model catalog.
@hvarg is working towards a new table that includes the index/indicator, and also models and output variables of those models that can be used for selecting those indices.
I am not sure this will be ready for next evaluation, but it's something we could try.
The text was updated successfully, but these errors were encountered: