`Since this was the default value, setting anyway - please fix!`

[Erik Schnetter]

I see many messages WARNING[L1,P0] (Cactus): Since this was the default value, setting anyway - please fix! in some simulation output. This message is repeated many times, and there is no other message providing context before or after this message.

[Roland Haas]

The default value for a parameter is out of range. Just why default values (in param.ccl) are not checked against the allowed range I do not quite know. It is possible that this was too complicated to do at CST time (b/c parameter ranges can be extended).

[Steven R. Brandt]

@Erik Schnetter can you tell me what parameter this was? The CST does have code for checking the default value falls within the allowed range.

[Erik Schnetter]

I don’t know which parameter caused this. I saw these errors in debug output sent by a collaborator.

Maybe the error message could mention the parameter name and value?

[Roland Haas]

This ticket is (basically) a duplicate of #2392 at least if the parameter in question was a “keyword” type parameter (which was the type I tested before responding to Erik). Apparently this was to be addressed after ET_2020_05 (though one assumes “shortly after” was implied ).

[Roland Haas]

Duplicate of #2392.