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

Incorrect graphical output for some sedml tests #7

Closed
shalinshah1993 opened this issue Aug 6, 2018 · 11 comments
Closed

Incorrect graphical output for some sedml tests #7

shalinshah1993 opened this issue Aug 6, 2018 · 11 comments
Assignees

Comments

@shalinshah1993
Copy link
Collaborator

From @shalinshah1993 on July 23, 2018 15:9

The tests that do not give correct answers:

  • osci-nested-pulse
  • repeated-scan-osci
  • repeated-steady-scan
  • repeated-stochastic-scan
  • param-scan-2D

The graphical outputs are exactly the same for all the repeated tasks i.e. the individual iterations don't apply changes from the listOfChanges sedml element.

Copied from original issue: shalinshah1993#60

@shalinshah1993
Copy link
Collaborator Author

The source of this bug is jlibsedml's ModelResolver class. As per description, SEDMLDocument.getModelString should apply all the list of changes to the model ( including repeatedTasks compute changes) but no changes are applied.

This is because jlibsedml's computeChange function only supports changing:

- CHANGE_ATTRIBUTE_KIND 
- REMOVE_XML_KIND
- ADD_XML_KIND
- NO_NAMESPACE
- CHANGE_XML_KIND

However, as per their documentation of Change class, there can be following categories of changes.

- SEDMLTags.CHANGE_ATTRIBUTE_KIND
- SEDMLTags.CHANGE_XML_KIND
- SEDMLTags.ADD_XML_KIND
- SEDMLTags.REMOVE_XML_KIND
- SEDMLTags.COMPUTE_CHANGE_KIND (missing in their implementation, required to comute model changes for each iteration of repeated tasks)
- SET_VALUE_KIND

@matthiaskoenig @draeger do you guys know who is working on jlibsedml who can respond to this issue?

I see Richard Adams maintains jlibsedml and he also wrote code for SBSCL in the past. Can you connect me with him?

@shalinshah1993
Copy link
Collaborator Author

From @draeger on July 24, 2018 8:46

I don't currently have any contact to @otter606 and am not aware of the current state of jlibsedml.

@shalinshah1993
Copy link
Collaborator Author

From @otter606 on July 24, 2018 22:3

Hi
I got the notification but have not worked on jlibsedml for years, I think
Frank Bergmann was maintaining itm, but this was some years ago.
Richard

On Tue, Jul 24, 2018 at 9:47 AM, Andreas Dräger notifications@github.com
wrote:

I don't currently have any contact to @otter606
https://github.com/otter606 and am not aware of the current state of
jlibsedml.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
shalinshah1993#60 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJA6nYKBDgC7AwVDNkBGRyY3l-aOJ4mQks5uJt8WgaJpZM4VbK9Z
.

@shalinshah1993
Copy link
Collaborator Author

From @draeger on July 25, 2018 6:56

Maybe @fbergmann can give more information?

@shalinshah1993
Copy link
Collaborator Author

From @fbergmann on July 25, 2018 7:25

I am not actively using jlibsedml. I'd be happy to propagate any code changes to the repository, or add another developer to the list. Chris Meyers was the last to commit to the project.

@shalinshah1993
Copy link
Collaborator Author

From @draeger on July 25, 2018 12:25

@cjmyers: what is the current state of jlibsedml?

@shalinshah1993
Copy link
Collaborator Author

From @cjmyers on July 25, 2018 16:30

Stalled. There is no one currently actively developing it. It would be great to have someone come along and champion it.

On Jul 25, 2018, at 5:25 AM, Andreas Dräger notifications@github.com wrote:

@cjmyers https://github.com/cjmyers: what is the current state of jlibsedml?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub shalinshah1993#60 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ADWD96U4wRYwWzCFhBQ5ohmBNR-8ASjZks5uKGO5gaJpZM4VbK9Z.

@shalinshah1993
Copy link
Collaborator Author

Since no one actively managing jlibsedml, I just added my own code for working with SEDMLTags.COMPUTE_CHANGE_KIND. Currently, the code uses string processing functions to extract SBML parameter from XPath and it updates them if SetValue element specifies a range for the parameter.

After pushing shalinshah1993@b64b096

The test cases that don't work:

  • osci-nested-pulse (because functional range MathML evaluation not supported by jlibsedml yet)
  • repeated-stochastic-scan (same as first)
  • param-scan-2D (because SBSCL doesn't support repeated task)

Two test cases that are giving unstable results:

  • repeated-steady-scan-oscli
  • repeated-stochastic-runs

Their outputs are as under. My guess why we get different results is because of the use of different simulation algorithm. We use Rosenbrock solver instead of what the SED-ML files ask.

image
image

@shalinshah1993
Copy link
Collaborator Author

@cjmyers
Do you have a Github repo that i can send pull request to?

On Jul 25, 2018, at 11:30 AM, cjmyers notifications@github.com wrote:

Stalled. There is no one currently actively developing it. It would be great to have someone come along and champion it.

On Jul 25, 2018, at 5:25 AM, Andreas Dräger notifications@github.com wrote:

@cjmyers https://github.com/cjmyers: what is the current state of jlibsedml?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub shalinshah1993#60 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ADWD96U4wRYwWzCFhBQ5ohmBNR-8ASjZks5uKGO5gaJpZM4VbK9Z.


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

@shalinshah1993
Copy link
Collaborator Author

From @fbergmann on July 26, 2018 18:45

so far sources are kept in sf svn ... but if you send me a patch i will apply it happily

@shalinshah1993
Copy link
Collaborator Author

This depends on #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant