Dear Simon,
how will you manage communication? I’m asking because there is a
related issue in computing absorption. It is easy to define a common
interface with respect to what the functions have to provide. But in
that case (and perhaps also in your case) a problem is that they require
quite
>From the perspective of computing scattering (or absorption) properties
for a given location in the atmosphere there are two types of required data:
- constant data describing the scatterer (single scattering data for particles,
etc.)
- atmospheric input: These are quantities that vary with posi
Dear Simon,
The handling of the constant data is completely up to the
implementation of the specific scatterers.
For the ScatteringParticle class, for example, this is provided when
the object is constructed.
So when the ARTS user calls:
scattering_speciesAddScatteringHabit(...)
an object is
Simon, Stefan,
It seems to me that this is a proposal of using a modern "void *"
list/vector with some strict interface. Have I misunderstood something
here? I mean you might implement it with virtual classes, std::variant, or
some other reinterpreting interface but that seems about it.
I am no
Hej Richard,
to me the interesting point is that the specific inputs could be handled
where the “Add..Habit” happens. In the case of absorption, a lot of
difficulty comes from the dichotomy between the species tags and the
methods that have to be added to the absorption agenda to actually do
