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
For time-wise constraints (i.e. CI) we tamper with tstop across various models. It is worth implementing --full-run mode that will allow us to perform further validations of existing models.
Foreseeable impact:
add a new entry in MODELDB_RUN_FILE for tstop
isolate tstop tampering from the script entry
Considerations:
would it be possible to have a CI that takes lots of hours for all models? or is it smtg we need to perform manully?
can we make use of diffgout in the CI for better understanding of differences? (this may be worth an issue on its own)
The text was updated successfully, but these errors were encountered:
For time-wise constraints (i.e. CI) we tamper with
tstop
across various models. It is worth implementing--full-run
mode that will allow us to perform further validations of existing models.Foreseeable impact:
MODELDB_RUN_FILE
fortstop
tstop
tampering from thescript
entryConsiderations:
diffgout
in the CI for better understanding of differences? (this may be worth an issue on its own)The text was updated successfully, but these errors were encountered: