pde

If I run the copy&paste examples, such as https://mtk.sciml.ai/stable/tutorials/acausal_components/ :

using ModelingToolkit, Plots, DifferentialEquations

@variables t
@connector function Pin(;name)
    sts = @variables v(t)=1.0 i(t)=1.0 [connect = Flow]
    ODESystem(Equation[], t, sts, []; name=name)
end

function Ground(;name)
    @named g = Pin()
    eqs = [g.v ~ 0]
    

add in docs and in testset a Low-level API example with GPU

It would be useful to keep track of how many retries a simulation did in the amr_diag.out file, which already records the coarse timestep info

I was having problems reading in a single frame of a solution using solution.Solution and finally tracked it down to the fact that although the first parameter of Solution is named frame you cannot call it using this as a kwarg, e.g. the two commands below should load the same frame but the second silently does nothing:

>>> from clawpack.pyclaw.solution import Solution

>>> frameso

Solver::addMonitor() has a MonitorPosition pos argument that allows the user to control whether a new monitor is added to the beginning (front) or end (back) of the list of output monitors.
https://github.com/boutproject/BOUT-dev/blob/efb92e9672a3c380209420512e4e1ee94e91624a/include/bout/solver.hxx#L221

It would be nice to have a similar argument for Solver::addTimestepMonitor().
https: