Skip to main content
20 events
when toggle format what by license comment
Oct 5, 2018 at 5:36 history edited xzczd CC BY-SA 4.0
added 4 characters in body
Feb 16, 2018 at 17:29 comment added dearN As late as this is, changing the Method from Adams to LSODA made is really fast to run.
Jun 27, 2016 at 13:45 history edited xzczd CC BY-SA 3.0
deleted 55 characters in body
Dec 21, 2012 at 9:32 history edited user21 CC BY-SA 3.0
deleted 32 characters in body
Aug 17, 2012 at 20:32 comment added Albert Retey @ruebenko: thanks for the explanation (I'm late, haven't been on my computer for a while...)
Aug 16, 2012 at 16:12 comment added user21 @xzczd, have a look at tutorial/NDSolvePDE (enter this in the help brwoser). Also, if you go to the NDSolve reference page there are a bunch of tutorials. Among them is tutorial/NDSolveOverview. Sorry, OP means original poster - so you in this case ;-).
Aug 16, 2012 at 15:29 comment added xzczd @ruebenko Well, where can I find the details of those methods for NDSolve? The document seems not say much about them…by the way, OP is the abbreviation for what?
Aug 16, 2012 at 15:11 vote accept xzczd
Oct 5, 2018 at 7:01
Aug 14, 2012 at 5:46 comment added xzczd @ruebenko Hehe, after times of trial I found my computer with 2GB memory can only bear a t around 0.736 at most…
Aug 13, 2012 at 16:20 history edited user21 CC BY-SA 3.0
added 39 characters in body
Aug 13, 2012 at 16:19 comment added user21 @AlbertRetey, in this case the error message NDSolve::ndsz made me try Method->Adams (which actually is not needed) as an alternative to the automatic stiffness switching. NDSolve::eerr: made me choose my own grid. The DifferenceOrder was because OP mentioned something about the boundary conditions in the post and that made me think this might be worth a try. So, yes, some experience and a try. I do have a note where I collect these type of questions and solutions that are found for them and then I consult this when needed. This might be something for a community wiki.
Aug 13, 2012 at 16:09 comment added user21 @xzczd, I am not sure what the minimum is, I uses a Linux-x86-64 with 4GB memory and did not have any problems.
Aug 13, 2012 at 16:07 comment added user21 @VitaliyKaurov, thanks for adding the pictures.
Aug 13, 2012 at 16:07 comment added user21 @PlatoManiac, there are a few things you can try: not using the EvaluationMonitor and/or using a lower AccuracyGoal and PrecisionGoal - with lowering those you may get away with using a smaller grid too.
Aug 11, 2012 at 13:51 comment added xzczd @ruebenko Wonderful!…well, but I wonder what's the minimum system requirements for the code?
Aug 11, 2012 at 10:15 comment added Albert Retey @ruebenko: can you explain how you found that exactly this combination of options does work? Do you have a strategy how to find a working set of parameters or are you using a clever combination of experience+guessing+trying? If you could explain, that would probably make the answer even more valuable, you eared a +1 anyway...
Aug 11, 2012 at 9:15 comment added Vitaliy Kaurov @ruebenko Big +1 - I am in awe you got this to work. I was almost sure there is an intrinsic divergence. I was also trying "Pseudospectral" with cyclic BC but to no avail. I am still puzzled why this works an nothing else does. I took a liberty to plot the beautiful solutions. Please feel free to remove my edit if you feel it's inappropriate.
Aug 11, 2012 at 9:11 history edited Vitaliy Kaurov CC BY-SA 3.0
added 548 characters in body
Aug 10, 2012 at 19:26 comment added PlatoManiac any chance of making it faster? Is it the optimal speed for NDSolve?
Aug 10, 2012 at 14:59 history answered user21 CC BY-SA 3.0