Add warning about unrecognised option
Hi,
Would it be possible to add some (small) sanity checks when reading the runcard? In particular could you check that all parameters are understood? E.g. with UNKNOWN_KEY: unknown
to the runcard, Sherpa could print to stderr: Found unrecognised "UNKNOWN_KEY", this key might not do anything.
. This would avoid having keys that one expect to work but don't (happened to me in !347 (merged)) or catch spelling mistake (Order
vs Orders
).
I don't know how central all possible arguments are stored, and how easy it is to check them all. But for example at the end of the big if else
list in Matrix_Element_Handler.C unrecognised keys could be caught.
Thank you,
Marian
Edited by Marian Heil