Re: [Users] PARAMCHECK and non fatal but inefficient parameter choices

On Wed, May 07, 2014 at 03:08:53PM -0700, Roland Haas wrote:

Note that current practise in most code seems to be to use CCTK_WARN_COMPLAIN (Level 1) for warnings about situations that do not invalidate the result and CCTK_WARN_ABORT (Level 0) for anything that invalidates results, ie. we do not adhere to the meaning of the levels documented in src/include/cctk_WarnLevel.h .

I think the best would probably also here be CCTK_WARN_COMPLAIN. Aborting an otherwise valid run doesn't seem right to me. There might be a reason someone wants to run this (wouldn't know why, but who knows), and you might just "kill" a week of wait time in the queue stopping in paramcheck.

Frank