opened
yeganer
username_0
Using the new distance2boundary calculation, we don't need recently_crossed_boundary flag, so it is
removed from all occurences.
This flag covered only outward propagating packets which have mu>0
anyway and result in the same calculation. This commit removes that
overhead and improves readability of the code.

This is in line with the discussion in Issue #517 .
If we are not 100% sure that there is no negative side effect, I'd suggest waiting for the improved C tests. Adding simple counters showed that `recently_crossed_boundary == 1` implies `mu > 0` for all testes setups (w7, abn_tom, example).
Remove rpacket.recently_crossed_boundary flag
issue
created
ssim
username_1
This looks good to me - happy to sign off is someone else is too!
comment