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
#496 has shown that we really can't trust non-QCed models. So we definitely want a caveat emptor-type warning if a user runs a model before it get's QCed. Related to #304 and #305.
The text was updated successfully, but these errors were encountered:
grahamgower
changed the title
Add CLI warning when using a non-QCed model
Add warning when using a non-QCed model
Apr 28, 2020
We should also have a warning in the catalog docs for non-QCed models. Actually, the developer docs regarding the QC process currently implies: non-QCed models are not connected to the CLI, and don't appear in the catalog documentation. This is clearly not the case. I don't think it's necessary for the non-QCed models to be avoided in the CLI or the catalog docs, but wanted to check in case others disagree.
#496 has shown that we really can't trust non-QCed models. So we definitely want a caveat emptor-type warning if a user runs a model before it get's QCed. Related to #304 and #305.
The text was updated successfully, but these errors were encountered: