WIP: Do not activate empty stars and BH pairs
Merge request reports
Activity
assigned to @matthieu
added 1 commit
- 856cd6de - Got rid of duplicate runner_do_timestep_collect().
added 1 commit
- ea4c019c - Re-added engine_unskip_timestep_communications() prototype to header file.
mentioned in merge request !1457 (closed)
Do we want to merge this before we figure out a better way to deal with the drift?
In principle, the drift at the beginning of the step (after the unskip) could reactivate some of the pair tasks that were not unskipped, which would lead to small errors in the neighbour finding which would not happen in the old version. The effect is likely to be small, and since we don't really care about the neighbourhood too much for stars and BH, it is probably not important either. Note that the ghost would not be able to correct for this, since we don't allow the ghost to rerun tasks that were not activated (this would go horribly wrong for domain-crossing pairs).
added 1 commit
- d70dd1bb - Also communicate cell information after drift_all in engine_dump_restarts().
added 487 commits
-
d70dd1bb...231cdd06 - 486 commits from branch
master
- 1838ec61 - Merge branch 'master' into fewer_timestep_comms_no_empty_pairs
-
d70dd1bb...231cdd06 - 486 commits from branch
Note for self: Merged master in to ease the comparison to !1595 (merged) where the focus is now shifting towards removing unnecessary BH comms too.