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

Use multi-threading #197

Closed
ViralBShah opened this issue Sep 8, 2019 · 7 comments · May be fixed by #230
Closed

Use multi-threading #197

ViralBShah opened this issue Sep 8, 2019 · 7 comments · May be fixed by #230
Assignees

Comments

@ViralBShah
Copy link
Member

ViralBShah commented Sep 8, 2019

We should move to Julia multi threading and get ready for 1.3. Might solve many memory issues and shared memory segments.

@ViralBShah
Copy link
Member Author

Also, with Omniscape using multi-threading, it makes sense for Circuitscape to also be doing the same.

@ranjanan ranjanan self-assigned this Mar 15, 2020
@ranjanan
Copy link
Member

ranjanan commented Mar 23, 2020

Blocking issue: I see this come up fairly often when I'm running it multi-threaded: JuliaLinearAlgebra/IterativeSolvers.jl#272.

@vlandau vlandau linked a pull request May 5, 2020 that will close this issue
@ViralBShah
Copy link
Member Author

@ranjanan Can you post here what the current issue is, and how one should reproduce it?

@ViralBShah
Copy link
Member Author

Never mind - I see it in #230.

@glaroc
Copy link
Contributor

glaroc commented Mar 1, 2021

Could Symbolics.jl be useful for implementing better parallelization and multi-threading in the Circuitscape?
https://discourse.julialang.org/t/ann-symbolics-jl-a-modern-computer-algebra-system-for-a-modern-language/56251

@ViralBShah
Copy link
Member Author

I think it is not related.

@glaroc
Copy link
Contributor

glaroc commented Mar 2, 2021

You're right, I originally misunderstood the description of this package.

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

Successfully merging a pull request may close this issue.

3 participants