hayk
unlikely, implementing #48 is not that hard per se, but i don't know how useful it will be (it might also be quite memory-intensive, depending on the number of bins...
(the instructions are in the README) Basically, @Tissot11 just send me an email, and I'll add you to the slack using your email. It's open for everyone, but since it's...
@LudwigBoess agree with getting rid of overrides in `KOKKOS_INLINE` functions. I don't think we needs these really, the point was to throw an error if the supplied metric/distribution doesn't overload...
@LudwigBoess i rebased this to the latest version + changed the Field boundary condition name to `FIXED` which should be a bit more generic (basically, it drives to a fixed...
after giving it a thought, i actually came up with a slightly better convention. will push shortly, but basically i suggest we keep the atmosphere as is (with buffers), and...
i'm a bit confused. can you explain again the exact boundary conditions imposed? currently, in X-direction, it's using ["FIXED", "ABSORB"] for fields (and ["REFLECT", "ABSORB"] for particles). - "FIXED" --...
and this is what the function which sets the fields for "FIXED" looks like: ```c++ auto FixField(const em& comp) const -> real_t { if (comp == em::ex2) { return init_flds.ex2({...
@LudwigBoess can you outline exactly what boundaries are being imposed in tristan (both on E and B field, on what scale, which components etc)? for the scale across which you...
@LudwigBoess i'll merge this to v1.2.0 release candidate, and we can continue working on this setup from that version. i'll also add a description of how the BCs are defined...