Feature/arkode sts

[maggul]

This is a draft PR for feedback on new STS module.

[drreynolds]

Unfortunately, the rebase to develop seems to have marked hundreds of files as conflicts. I'll work on fixing this branch now, so that it will be easier for folks to review.

[balos1]

Unfortunately, the rebase to develop seems to have marked hundreds of files as conflicts. I'll work on fixing this branch now, so that it will be easier for folks to review.

Yeah, I think in the future we should not rebase develop on main (if main is updated directly) and instead do a merge. I don't see a real advantage to having the same linear history for main and develop, and it seems the rebase has a pretty big downside.

[drreynolds]

and it seems the rebase has a pretty big downside.

Indeed. Although rebasing might be no big deal for branches with 1-2 commits, it is a huge waste of time for a branch with any appreciable amount of development.

[Steven-Roberts]

This text

sundials/doc/arkode/guide/source/Usage/User_callable.rst

Lines 48 to 52 in 6117e71

	In the function descriptions below, we identify those that have any of the restrictions B-E above.
	Then in the introduction for each of the stepper-specific documentation sections
	(:numref:`ARKODE.Usage.ARKStep.UserCallable`, :numref:`ARKODE.Usage.ERKStep.UserCallable`,
	:numref:`ARKODE.Usage.MRIStep.UserCallable`, and :numref:`ARKODE.Usage.SPRKStep.UserCallable`)
	we clarify the categories of these functions that are supported.

and

sundials/doc/arkode/guide/source/Usage/User_callable.rst

Lines 60 to 61 in 6117e71

	For functions to create an ARKODE stepper instance see :c:func:`ARKStepCreate`,
	:c:func:`ERKStepCreate`, :c:func:`MRIStepCreate`, or :c:func:`SPRKStepCreate`.

need to be updated.

This list of steppers is growing long and text like this easily gets overlooked, so I think more generic statements without a long list of links would be ok.