SciMLLogging Integration

[jClugstor]

Checklist

• Appropriate tests were added
• Any code changes were done in a way that does not break public API
• All documentation related to code changes were updated
• The new code follows the
  contributor guidelines, in particular the SciML Style Guide and
  COLPRAC.
• Any new documentation only uses public API

Additional context

Add any other context about the problem here.

[jClugstor]

will need SciML/SciMLBase.jl#1159 to fully work

[termi-official]

Since you are already working on the logging system, is there any chance that we can have additional logging messages for the time integration loop at trace level to debug issues in the timestepping itself? Or is that too costly?

[ChrisRackauckas]

We are splitting that to a different step. First let's get the infrastructure together, then add new messages.

Or is that too costly?

Never! If it's super costly, just put it in the All preset only. Semi? Detailed. Since there's individual switching and tons of levels, the goal is to just add tons and tons of default prints and if they are costly just don't have them on by default, but if you switch to All then you just get a lot of information.

[jClugstor]

At this point anything that was behind a verbose is now under a @SciMLMessage and is controlled by an ODEVerbosity.

Currently, the linear_verbosity and nonlinear_verbosity fields are not used because those get set in alg_cache or build_nlsolver which do not have access to the integrator or the DEOptions where the verbosity object is. So setting those in ODEVerbosity will not do anything.

For the Linear solves and Nonlinear solves I set verbose to Minimal() to prevent unnecessary printing from those during an ODE solve.

[ChrisRackauckas]

is this ready to review?

[jClugstor]

Yep, ready to be looked at.

[ChrisRackauckas]

Lots of test failures