unknown variable in input file/ obsolete variable in input file

[jonmaddock]

In GitLab by @Hlux on Dec 22, 2016, 09:36

Dear Manoj,

I think when an unknown or obsolete variable is specified in the input file, error = .True. in input.f90. I am not sure what that does, but my suspicion is that it just stops the code. For the Python utilities it would be helpful, if in that case still an MFILE was written out with error_status = 3. I think this is currently not the case. This is not urgent, but when you have the time, could you check this and implement the writing of the error_status values to MFILE.

Thanks,

Hanni

[jonmaddock]

In GitLab by @rkemp on May 3, 2017, 13:34

I think it would also be useful if the code were not stopped at this point but after a complete run through of IN.DAT, with a final total summary of input issues; the current situation is that the code stops after each error which means that you correct that error... and then the code stops again on the next line. If all the unknown/obsolete variables could be picked up and reported in one pass this would streamline runs.

[jonmaddock]

@clmould could you pick this up and see if this is still a problem?