We met online, as is common these days. She was hanging out on the website template from which I built this user guide.
Marna is a gentleman and a scholar. She is also a marine iguana. Amblyrhynchus cristatus. Do you know what Ambly means? Blunt.
Her native disposition was further sharpened (blunted?) by a traumatic childhood spent fleeing snakes.
As such, she has acquired a healthy dislike for all things curve-shaped. Especially those that claim to be minimally disruptive.
Marna has expressed her reservations about MinimallyDisruptiveCurves.jl. So we've invited her for a Q&A session.
🦎: This doesn't make sense. The gradient of a function gives the direction of maximal sensitivity. It doesn't say much about the remaining directions, or how insensitive they are. But you're trying to use gradient information alone to evolve curves in a maximally insensitive direction of the cost function
You're correct. Usually the Hessian (second derivative) of a function gives the directions of local insensitivity. By Taylor expansion:
As you say, there are potential directions for that are uncorrelated with the gradient . So the gradient doesn't give information on their sensitivity, while the Hessian does (we can see if is small).
However, Hessians are generally very costly to compute, so we wanted a way of evolving insensitive directions using the gradient alone.
We can think again of the minimally disruptive curve as a ball rolling along a valley in the loss landscape (where height is cost, and lateral co-ordinates are parameter values). Once given an initial push, the ball just maintains constant speed in a flat (insensitive) direction. It only changes its course when the valley curves, and it starts to creep up the valley side. What makes it turn? Gravity pushes it back down in the direction of the valley slope (the gradient). So the trajectory curves along with the valley.
🦎: OK but then numerical error will prevent this algorithm from working. If you're near a local minimum of the cost, then the gradient . Which means that small numerical errors will massively bias the direction of the gradient.
Your intuition is good! But we bypass this problem somewhat. If you want to see this in action, look at our simplest mass-spring model example:
Evaluate the gradient at the minimum and you'll notice that it isn't zero as it should be. The entries are . Nevertheless the MD curve (which we know a priori in that problem), is extremely accurate. How come?
Roughly speaking, we could divide numerical errors into systematic, and unsystematic errors.
Unsystematic errors We can think again of the minimally disruptive curve as a ball rolling along a valley in the loss landscape (where height is cost, and lateral co-ordinates are parameter values). Our ball has weight, and thus some momentum. This is the costate variable described in the How it works section. We can think of the ball being buffeted by the wind (unsystematic numerical errors). The momentum of the ball prevents this buffeting from affecting the trajectory too much unless the direction is systematic....
Systematic errors Every so often, the minimally disruptive curve generator resets the momentum (costate) variable. This factors out numerical error that has integrated over time. You can set the numerical tolerance at which this reset happens, or switch it off entirely:
evolve(c::curveProblem, solmethod=nothing; callback=nothing, momentum_tol = 1e-3,kwargs...)
momentum_tol = nothing to switch off this resetting. In many examples, this will cause the minimally disruptive curve to veer off course or even go completely unstable.
🦎: Hmm, I see. But do we have to use a gradient at all? Why not just wiggle parameters, see which wiggles don't change model behaviour, and so on?
The profile likelihood method (introduced in (Venzon & Moolgavkar (1988)), and applied, with a software toolbox, for Systems Biology in (Raue, Andreas, et al. (2009))) does precisely this! And doesn't require a differentiable cost function.
Essentially they pick a parameter (), and iteratively change it. At each step, all the other parameters are re-optimised to minimise the cost function. This solves a slightly different problem: making effective confidence intervals on the parameters for a particular model behaviour. I informally tried to compare this method to mine on the examples of the 2017 paper, and couldn't use it to extract functional relationships between parameters. The reason? MD Curves have momentumum in a particular (potentially curving) insensitive direction. The iterative re-optimisation procedure can and will change parameters in a different insensitive direction at each iteration.
🦎: All these numerical methods though...what about numerical error?
The differential equation that MinimallyDisruptiveCurves.jl attempts to solved can be ill-conditioned. I've spent some effort alleviating this, but I haven't fully explored methods of making it as numerically stable as possible. Or even characterising the numerical stability of the solution. This would be a good research topic. In the Tips & Tricks section, I give some guidelines.
Fortunately I think it is acceptable to be much more tolerant than usual of numerical error in this type of problem. Why? The success of an MD curve is not defined by whether the numerical solution of the ODE defining curve evolution was accurate. It is defined by whether you generated a curve that doesn't disrupt model behaviour much. If this toolbox gives you that...great. This is different from usual use cases of ODE solvers, where you want to approximate as closely as possible an unknown 'ground truth' dynamical system.
Venzon, D. J., and S. H. Moolgavkar. "A method for computing profile‐likelihood‐based confidence intervals." Journal of the Royal Statistical Society: Series C (Applied Statistics) 37.1 (1988): 87-94.
"Structural and practical identifiability analysis of partially observed dynamical models by exploiting the profile likelihood." Bioinformatics 25.15 (2009): 1923-1929.