physical_domains.hpp serif/discretization/domain/types.hpp serif/discretization/domain/concepts.hpp src/include/serif/discretization/blocks/fields.hpp src/include/serif/discretization/domain/schema/schemas.hpp src/include/serif/discretization/quadrature/query.hpp src/include/serif/discretization/reconstruction/surface_power.hpp serif serif::discretization serif::discretization::domain File containing the physical domain types for SERiF. These are domain sets that are more useful physically since they group together computationally separate domains that may have no physically meaningful distinction. For example, the core and envelope domains are computationally distinct but physically they are both stellar domains. Emily M. Boudreaux the core and envelope domains do not necessarily correspond to the physical core and envelope of a star. Rather, this is terminology used to describe the two regions where we orient the mesh differently. Fundamentally we cannot reasonably continue a spherical mesh to the center of a stellar model due to the r=0 singularity. Therefore, the mesh generation program we use (stroid) generates a cartisan mesh embedded within a spherical mesh (there is a bit more to the topology to ensure we have a nicely structured mesh, see stroid for more details). It is this inner cartesian mesh (along with the transition region) that we call the core. The user may need to make choices about where that transition region occurs in their stellar model. #pragmaonce #include"serif/discretization/domain/types.hpp" #include"serif/discretization/domain/concepts.hpp" namespaceserif::discretization::domain{ usingStellarDomains=DomainSet<CoreDomain, EnvelopeDomain>; usingAllDomains=DomainSet<CoreDomain, EnvelopeDomain, VacuumDomain>; }