User Portlet User Portlet

Daniel Lichtblau
Discussions
You are setting precision higher than that of the input. This means some bits are effectively junk. As for assessing the condition number, one way is like so. {vv, ss, ww} = SingularValueDecomposition[g]; sv = Diagonal[ss]; ...
A reference implementation of a recent variant can be found in [this prior Community thread](https://community.wolfram.com/groups/-/m/t/2344199?p_p_auth=UZ0BHnEu).
Depending on the input, maybe you would want to do a Taylor expansion instead.
I will venture the obvious reason, that it does not know how to do this integral.
Maybe use `PseudoInverse[g].G`?
It appears to be badly conditioned though. Whether that's a problem is likely to be application dependent.
numBases = 100; (*Number of base pairs,representing a segment of DNA*) kappa = 1/ 10; (*Elasticity constant,chosen to reflect the \ stiffness;arbitrary unit*) omegaD = 2/10; (*Frequency term,speculative and...
It is not clear to me why this optimization is expected to recover `phi`. The discrepancy in your results is actually user error: in going from the solution of this Solve[D[llog[\[Phi]], \[Phi]] == 0, \[Phi]] to this f2[{m0_, m1_,...
This is strange behavior for a notebook. But difficult to diagnose without the actual one. Best I can suggest is to save it frequently, possibly to multiple versions e.g. based on timestamps.
Good question. I think one way is to find discontinuity points. Skipping some of the setup, here is hoq that could be done. ee = -m1 Log[2] + 4 m0 Log[Cos[\[Phi]/2]] + 4 m2 Log[Sin[\[Phi]/2]] + 2 m1 Log[Sin[\[Phi]]]; ...