Closed manauref closed 7 months ago
This issue was addressed by commit https://github.com/ammarhakim/gkylzero/commit/9b22e4c8d7a0fc65f324ffc6fd0258a5193882e0
to more accurately compute the stable time step in BGK collisions. The use of this operator is now uniform across GK and Vlasov BGK collisions within the app.
currently the BGK operator
is put together, and its cflrate computed, with these 4 lines in app/gk_species_bgk (L174-181)
Rather than having 4 lines, 4 kernel launches, 4 places for potential mistakes and possible doubts about whether cflrate is computed correctly (although it seems to me that it is for the nu=const case), it'd be better to simply use the
gkyl_bgk_collisions
object inzero/
. That way we have 1 line, 1 kernel launch, only 1 place to make a mistake (in the app) and the cflfreq is also computed within it like it is for other objects. Further more, if we do that, these lines in apps/gk_species (L399-410)can be removed, and we'd be treating the BGK cflrate with the same code/interface we already treat the LBO cflrate.