Timeline for NDSolve fails to solve trivial PDE with mixed partial derivatives
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Dec 3, 2023 at 15:08 | vote | accept | phonon | ||
S Dec 3, 2023 at 15:08 | vote | accept | phonon | ||
S Dec 3, 2023 at 15:08 | |||||
Dec 3, 2023 at 15:08 | vote | accept | phonon | ||
S Dec 3, 2023 at 15:08 | |||||
Dec 3, 2023 at 0:42 | answer | added | xzczd♦ | timeline score: 2 | |
Dec 2, 2023 at 0:16 | vote | accept | phonon | ||
Dec 3, 2023 at 15:08 | |||||
Nov 23, 2023 at 1:31 | answer | added | user87932 | timeline score: 3 | |
Nov 22, 2023 at 20:42 | comment | added | user87932 | If I change the Method to "FiniteElement", it complains about your first boundary condition and states the NeumannValue should be used. If I simply comment out the first condition out, and use Table to display values for the solution for x,t values over the range, I get 1 everywhere. So it appears there's a problem with the first bc. Also, if I change the Method to "Adams" or "BDF" etc., I get messages indicating Differential-Algebraic equations aren't supported by these methods. So NDSolve isn't happy with that first Derivative[1,0][u][0,t] == 0 equation. (MethodOfLines is default BTW.) | |
Nov 22, 2023 at 16:37 | answer | added | Roland F | timeline score: 0 | |
Nov 22, 2023 at 16:05 | history | edited | phonon | CC BY-SA 4.0 |
deleted 5 characters in body
|
S Nov 22, 2023 at 16:03 | review | First questions | |||
Nov 22, 2023 at 17:42 | |||||
S Nov 22, 2023 at 16:03 | history | asked | phonon | CC BY-SA 4.0 |