id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2288	inconsistent solver flag	Lennart Ochel	Lennart Ochel	"If you run a simulation executable with {{{-help=s}}} you get this Output:
{{{
stdout            | info    | detaild flag-description for: <-s=value> or <-s value>
|                 | |       | value specifies the solver
|                 | |       |   dassl
|                 | |       |   euler
|                 | |       |   rungekutta
|                 | |       |   inline-euler
|                 | |       |   inline-rungekutta
|                 | |       |   dasslwort
|                 | |       |   dasslSymJac
|                 | |       |   dasslNumJac
|                 | |       |   dasslColorSymJac
|                 | |       |   dasslInternalNumJac
|                 | |       |   qss
}}}

If you run a simulation executable with an invalid solver (e.g. {{{-s=foo}}}) you get this list of available solvers:
{{{
stdout            | info    |  | Unrecognized solver: foo.
stdout            | info    |  | valid solvers are: dassl, euler, rungekutta, inline-euler, inline-rungekutta, dasslwort, dasslSymJac, dasslNumJac, dasslColorSymJac, dasslInternalNumJac, qss, radau1, radau3, radau5, lobatto2, lobatto4 or lobatto6
}}}

Please, keep the runtime consistent. This is quite easy due to the existing structure used by (most of the) other flags."	defect	closed	high	1.9.0	Run-time	trunk	fixed