Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tellurium float errors lead to reset errors in subsequent simulations #113

Open
stellaprins opened this issue Jan 13, 2025 · 0 comments
Open

Comments

@stellaprins
Copy link
Collaborator

float errors

@robertvi and I noticed some pre-existing strange behaviour of Tellurium after float errors happen. In test suite cases that lead to float errors when running the models in Tellurium natively.

It seems to be the case that after a float error, all subsequent cases that would otherwise pass fail with reset errors. Nearly half of the fails in the original test suite results table was caused by these reset errors.

The models that cause the float errors all pass in Tellurium when run remotely through Biosimulators.

The float error message is 'float' object is not callable. The reset error message is reset. The error happens in Tellurium.

We tried reinstalling dependencies and freshly unimporting and reimporting tellurium in between runs, but this did not resolve the issue.

workaround
For now, float error cases are skipped from running in Tellurium natively and the following message is displayed in the Tellurium column skipped Case is skipped because it leads to a float error when trying to run it in tellurium natively, which leads to reset errors in subsequent cases that would otherwise pass.

Skipping these 14 float error cases makes the number of passes go up from 863 to 1576 .

Affected test suite cases that lead to float errors when run in Tellurium natively

  • 00952
  • 00953
  • 00962
  • 00963
  • 00964
  • 00965
  • 00966
  • 00967
  • 01588
  • 01590
  • 01591
  • 01599
  • 01605
  • 01627
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant