ML_BSSN ues its timelevel parameter for the constraints rather than other_timelevel

Looking at ML_BSSN's storage.ccl it seems as if it uses its timelevel parameter to control how many time levels are allocated and used for the constraints. However in ML_BSSN_Helper it seems clear (in ML_BSSN_SetGroupTags) that originally other_timelevels (which also fits better with the description of the parameter) should instead be used so that one can use different numbers of time levels for the constraints (ie. only 1 so that prolongation etc can be disabled which ML_BSSN_Helper does if other_timelevels is set to 0, however the extra memory is still allocated).

Keyword: ML_BSSN

Comments (2)