hi all,
we've recently added the option to compute the Gauss constraint in the ProcaEvolve thorn (https://bitbucket.org/canuda/proca/src/experimental_miguel/ProcaEvolve/) and we were surprised to see that, even for very small evolutions of a simple (unperturbed) charged black hole, this constraint violation does not converge. of course everything is converging just fine at t=0, but once the evolution starts, convergence is lost really quickly.
after experimenting with different things, i think i've narrowed the issue down to the subcycling in time. i've attached some plots as well as the corresponding parameter files. these plots are not convergence tests, it's just what i'm observing with and without subcycling in time (everything else is the same as you can see from the parfiles).
these are evolutions for a single charged BH, with Q=0.2. in one of the parfiles (LeanBSSN_RN_Q0.2_nosubcycl_hf40_202509.par) all timelevels update at the same rate with
Carpet::time_refinement_factors = "[1, 1, 1, 1, 1, 1, 1]"
for the other parfile (LeanBSSN_RN_Q0.2_hf40_202509.par), all timelevels update at the same rate *except* the two inner ones. for the "base" grid functions, i see no noticeable difference insofar as i've checked, but for the Gauss constraint violation the results are very different as you can see from the plots attached:
- in the gc_x_RN_nosubcycl.pdf plot, everything looks fine - in the gc_x_RN_subcycl.pdf case, notice how a lot of noise propagates from the two inner refinements levels -- the ones that updated more frequently than the rest.
the problem is that this noise is not contained in the buffer region (if it was, we'd be fine), but propagates out, contaminates the rest of the grid, and totally ruins any convergence study.
actually a similar thing also happens for the hamiltonian constraint -- plots also attached (hc_x_RN_nosubcycl.pdf, hc_x_RN_subcycl.pdf) -- but in this case the effect is smaller and it doesn't spoil convergence studies.
so i was wondering whether this is at all expected and/or if there are some parameters or setting that we may have overlooked?
thanks, Miguel