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

Potential issue with uncertainty quantification #57

Open
S-Math opened this issue Nov 15, 2021 · 3 comments
Open

Potential issue with uncertainty quantification #57

S-Math opened this issue Nov 15, 2021 · 3 comments

Comments

@S-Math
Copy link

S-Math commented Nov 15, 2021

I mentionned an issue I had using the library to assess the uncertainty of my DAE system solution on the forum :

https://discourse.julialang.org/t/problem-understanding-results-of-diffequncertainty/71193

I was encouraged to post an issue about it even though my code might be the problem and not the library.

The problem is basically that solving my DAE normally takes 9s

9.159245 seconds (21.20 M allocations: 1.964 GiB, 9.29% gc time, 0.10% compilation time)

whereas if I use the uncertainty library it takes way longer (for 5 trajectories) and a lot of allocations :

6588.658787 seconds (21.72 G allocations: 3.086 TiB, 52.83% gc time, 0.00% compilation time)

I am not pasting the whole discussion on the forum, to not clutter this post but the issue might be related to caching according to Chris Rackauckas

The code :

I add my code to this issue. The file interp2D.jl is used to defined interpolation functions on my main code model_MM_github.jl

I scraped the code as best as I coould, I believe it is fairly straightforward, if somehow something is not clear, do not hesitate to ask for more information.

code_github.zip

@ChrisRackauckas
Copy link
Member

Yeah this library isn't quite stable because of its setup. It needs a bit of work which will happen over the next year.

@S-Math
Copy link
Author

S-Math commented Nov 26, 2021

Ok, thank you for taking the time to reply.

@S-Math S-Math closed this as completed Nov 26, 2021
@ChrisRackauckas
Copy link
Member

I'll keep this open to track it with the performance changes.

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

2 participants