# Tag Info

8

Use Sinc[x] rather than Sin[x]/x BallooningFile = {0., 0.000136, 0.000572, 0.001152, 0.001907, 0.003004, 0.004199, 0.005479, 0.006834, 0.008256, 0.008985, 0.009738, 0.011271, 0.01285, 0.013651, 0.014468, 0.016119, 0.017797, 0.019496, 0.021211, 0.022069, 0.022934, 0.024661, 0.025522, 0.026386, 0.028103, 0.029806, ...

8

I think there's a bug in the internal function NDSolveSPRKDumpCheckSeparability that leads NDSolve to conclude that the system is not separable. I think you should report it and see if WRI can verify it (they would probably appreciate a link to this Q&A). It's a fair amount of work to track it down, and there is a lot of nearly unreadable stuff to ...

4

There was a wrong bracket in F. Also do not use { as a normal bracket, and second you wrote Exp{[ which has to be either {Exp[ or (Exp[ . F[k1_, k2_, λ1_, λ2_, δ_, w1_, w2_] := (1 - Exp[-(w1/λ1)^k1]) (1 - Exp[-(w2/λ2)^k2]) (Exp[(1 - (1 - Exp[-(w1/λ1)^k1]))^(-δ) + (1 + (1 - Exp[-(w2/λ2)^k2]))^-δ]^(1/-δ))

3

Confirmed by WRI (@ilian) as bug introduced in 10.1.

3

Needs["ErrorBarPlots"] data = {{34.2, 8.83, 5.8, 4.2, 1.3362, 1.3362}, {44.3, 3.02, 5.7, 4.3, 0.4324, 0.4324}, {54.3, 1.33, 5.7, 4.3, 0.190427, 0.190427}, {64.5, 0.615, 5.5, 4.5, 0.088054, 0.088054}, {78.1, 0.273, 11.9, 8.1, 0.03908765, 0.039087651}, {98.6, 0.0861, 11.4, 8.6, 0.014199975, 0.014199975}, {122.0, 0.0279, 18, 12, ...

2

The reason for this error is that NIntegrate uses fixed precision when computing the integration ranges, while EllipticK needs to raise the precision internally to obtain a good result. N[EllipticK[7/10], 20] (* 2.0753631352924691439 *) Block[{$MinPrecision =$MaxPrecision = 20}, N[EllipticK[7/10], 20]] (* Divide::infy: Infinite expression ...

2

When you call compiled functions inside another compiled function, you should consider to inline them. You can do this by wrapping a With statement around and using CompilationOptions -> {"InlineCompiledFunctions" -> True} as option to compile. I have cleaned your code, moving a lot of definitions of variable right where you declare it in Module. I ...

1

Even with the necessary correction by Lou, Solve cannot solve functions like gcsymb. More promising options are NSolve and FindRoot, although they must be provided numerical values for a and b. However, neither gives an answer, because gcsymb is ill-behaved for Ldp very near 0, which is the solution to the calculation for c >= 1/2. ...

1

As Bob Hanlon and MarcoB have already mentioned in the comments, the problem appears to be in the circular definition. Because of the way these are defined, neither m[s, d, T] nor F[s, d, T] can be evaluated with numerical values of s, d and T, so there isn't much FindRoot could do. A simplified example might be f[s_] := NIntegrate[f[s], {x, 0, 1}, {y, ...

1

Go to Preferences -> Messages and choose the desired option for Kernel Messages.

Only top voted, non community-wiki answers of a minimum length are eligible