-
Notifications
You must be signed in to change notification settings - Fork 12
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
Fix non-mandatory event IDs #255
Conversation
Closes #254 SBML says that IDs on events are actually not mandatory, this softens the data structure so that the ID-less events are supported. The vector-of-pairs implementation is chosen for backwards compatibility (iteration through a vector of pairs should work precisely like iteration through the dictionary that was there before). Notably, this might look like a breaking change _but_ it is not -- the main use case that is broken by this commit is indexing the events by ID, which was actually broken already.
4191514
to
df38e09
Compare
cc @sebapersson -- I added one of the models you reported as a test so this should technically work, but it would ne great if you could check if your usecase is solved. Thanks! |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #255 +/- ##
=======================================
Coverage 93.51% 93.51%
=======================================
Files 10 10
Lines 817 817
=======================================
Hits 764 764
Misses 53 53
☔ View full report in Codecov by Sentry. |
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. Looks good to me!
Thanks, it now works for my usercase. |
Perfect, thanks all for confirms! |
Mainly fixes #254 using approach #1. As a result, some new SBML usecases can be loaded.
I packed in the UL logo update (the original relied on line width setting and rendering, which is typically broken.
Also bumping to 1.5.0 (the new loadable models are a feature, also see discussion in the commits).