-
Notifications
You must be signed in to change notification settings - Fork 31
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
No flattening of timepoint specific overrides in jax #2641
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2641 +/- ##
===========================================
+ Coverage 77.14% 77.16% +0.01%
===========================================
Files 332 332
Lines 23021 23137 +116
Branches 1478 1478
===========================================
+ Hits 17760 17854 +94
- Misses 5250 5272 +22
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I'd didn't check super thoroughly, but looks good to me.
pysb_model, name, sigmas | ||
# note that this is a bit iffy since we are potentially using the same symbolic identifier in expressions (w) | ||
# and observables (y). This is not a problem as there currently are no model functions that use both. If this | ||
# changes, I would expect symbol redefinition warnings in CPP models and overwriting in JAX models, but as both |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these warnings are easily overlooked. Maybe we should turn them into errors. But this will break the import of at least one benchmark collection model that has something named NULL
. Fine for now.
Co-authored-by: Daniel Weindl <dweindl@users.noreply.github.com>
…into jax_no_flattening
|
No description provided.