Timeline for How can I speed up NDSolve
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 18, 2021 at 10:14 | history | edited | Szabolcs |
edited tags
|
|
Feb 26, 2020 at 12:00 | history | tweeted | twitter.com/StackMma/status/1232636458621644801 | ||
Feb 21, 2020 at 5:34 | history | edited | Αλέξανδρος Ζεγγ | CC BY-SA 4.0 |
edited title
|
S Feb 21, 2020 at 2:38 | history | suggested | A little mouse on the pampas | CC BY-SA 4.0 |
deleted 1011 characters in body
|
Feb 21, 2020 at 1:43 | review | Suggested edits | |||
S Feb 21, 2020 at 2:38 | |||||
Feb 21, 2020 at 1:09 | answer | added | Alex Trounev | timeline score: 7 | |
Feb 20, 2020 at 16:26 | comment | added | Chris K |
As @user21 suggests, requiring 1000 points is a big problem. Since you have a 2D system, I think that means that NDSolve discretizes the PDE into 1000*1000 ODEs. Not surprising that's going to be slow.
|
|
Feb 20, 2020 at 15:17 | comment | added | user21 | Works in parallel on my machine. Have you changed the setup on yours? | |
Feb 20, 2020 at 12:46 | comment | added | Ben9172 | no particular reason, just wanted high definition. and it does not run on multiple CPU, how can i make it so it does? | |
Feb 20, 2020 at 12:40 | comment | added | user21 | If no option is specified the integration is faster. In other words why do you specify pts=1000? Also, this does run on multiple CPUs. | |
Feb 20, 2020 at 12:27 | history | edited | Ben9172 | CC BY-SA 4.0 |
deleted 3 characters in body
|
Feb 20, 2020 at 12:21 | history | asked | Ben9172 | CC BY-SA 4.0 |