#616: Carpet breaks backwards-compatibility with parameter files ---------------------+------------------------------------------------------ Reporter: hinder | Owner: eschnett Type: defect | Status: new Priority: major | Milestone: ET_2011_10 Component: Carpet | Version: Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by barry.wardell):
Replying to [comment:3 eschnett]:
I don't think that's worthwhile. This parameter doesn't influence
correctness of the evolution, so let's keep things simple. 0 is already an unlikely value, most people would use 253 or so.
OK.
If you want to propose a patch, then it should probably run in
PARAMCHECK and use CCTK_ParameterQueryTimesSet. Please test checkpointing/recovery as well to ensure the warning works as intended.
Setting parameters which have no effect is usually not diagnosed in
Cactus; this should therefore likely be a low-priority warning (maybe level 2).
Now that I think about it more, this seems like feature which would be better suited as a part of Cactus. It happens quite often that parameters are deprecated, so having a standardised way of denoting this in the param.ccl would be better than implementing the code manually each time.