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
There have been some bugs that cause the models not to work at the general Ersilia Level. This is hard to un-link from other issues but I will try to collect here bugs that need to be fixed:
It would be good to add these checks to the model test or the Ersilia CLI workflows to ensure they do not repeat. @Abellegese for the parsing to None outputs, we thought we could run a one single check in the Ersilia CLI with one model and one molecule we know fails in this model and ensure the None output is properly parsed. Thoughts?
Objective(s)
Ensure Ersilia is fully functional
Documentation
Ersilia's gitbook
The text was updated successfully, but these errors were encountered:
GemmaTuron
added
the
critical
Critical issue that is a blocker and we need to solve immediately; use sparingly
label
Feb 6, 2025
Yes @GemmaTuron I agree with that. Whats even best is I think to create a small functions that enforces a correct parsing for all models. How do we do this? One way is to use the schema of the api to construct parsing rules the None as well as for the correct values.
Summary
There have been some bugs that cause the models not to work at the general Ersilia Level. This is hard to un-link from other issues but I will try to collect here bugs that need to be fixed:
It would be good to add these checks to the model test or the Ersilia CLI workflows to ensure they do not repeat. @Abellegese for the parsing to None outputs, we thought we could run a one single check in the Ersilia CLI with one model and one molecule we know fails in this model and ensure the None output is properly parsed. Thoughts?
Objective(s)
Documentation
Ersilia's gitbook
The text was updated successfully, but these errors were encountered: