#1932: ML_BSSN: other_timelevels Parameter Not Respected ---------------------------------+------------------------------------------ Reporter: zachetie@… | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Other | Version: development version Resolution: | Keywords: ---------------------------------+------------------------------------------
Comment (by knarf):
#1960 was marked as duplicate of this bug. It looks like a reasonable proposal to me to replace 'timelevels' by 'other_timelevels' in these cases. Concerning checkpointing: if other_timelevels is indeed 1, there is no need to store them. Would it be conceivable that someone might actually want to store them (and other_timelevels is set to a high enough value)?