entity-toolkit/entity

New generation astrophysical plasma simulation code with CPU/GPU portability

entity's Issues

add particle output

write particles, no way of tagging them for now (i.e., no tracking)

nttiny GUI not working properly

Needs to be for the newer v0.9 version of the code.

compile error

Error occurs when building with GPU codes
when only built with openmp, it works fine, also works for gpu on other computers, I don't get it

ibentity-framework.a(output_flds.cpp.o): In function ntt::OutputField::initialize(ntt::SimulationEngine const&)': tmpxft_001fda24_00000000-6_output_flds.cudafe1.cpp:(.text+0x74): multiple definition of ntt::OutputField::initialize(ntt::SimulationEngine const&)'
libentity-framework.a(engines.cpp.o):tmpxft_001fd9e9_00000000-6_engines.cudafe1.cpp:(.text+0x92): first defined here
libentity-framework.a(output_flds.cpp.o): In function ntt::OutputField::name[abi:cxx11](int const&) const': tmpxft_001fda24_00000000-6_output_flds.cudafe1.cpp:(.text+0x14c0): multiple definition of ntt::OutputField::name[abi:cxx11](int const&) const'
libentity-framework.a(engines.cpp.o):tmpxft_001fd9e9_00000000-6_engines.cudafe1.cpp:(.text+0x14de): first defined here
libentity-framework.a(fields.cpp.o): In function ntt::Fields<(ntt::Dimension)1, (ntt::SimulationEngine)2>::Fields(std::vector<unsigned int, std::allocator<unsigned int> >)': tmpxft_001fd9b6_00000000-6_fields.cudafe1.cpp:(.text+0x92): multiple definition of ntt::Fields<(ntt::Dimension)1, (ntt::SimulationEngine)2>::Fields(std::vector<unsigned int, std::allocator >)'
libentity-framework.a(engines.cpp.o):tmpxft_001fd9e9_00000000-6_engines.cudafe1.cpp:(.text+0x16e4): first defined here
libentity-framework.a(fields.cpp.o): In function ntt::Fields<(ntt::Dimension)1, (ntt::SimulationEngine)2>::Fields(std::vector<unsigned int, std::allocator<unsigned int> >)': tmpxft_001fd9b6_00000000-6_fields.cudafe1.cpp:(.text+0x92): multiple definition of ntt::Fields<(ntt::Dimension)1, (ntt::SimulationEngine)2>::Fields(std::vector<unsigned int, std::allocator >)'
libentity-framework.a(engines.cpp.o):tmpxft_001fd9e9_00000000-6_engines.cudafe1.cpp:(.text+0x16e4): first defined here
libentity-framework.a(fields.cpp.o): In function `ntt::Fields<(ntt::Dimension)2, (ntt::SimulationEngine)2>::Fields(std::vector<unsigned int, std::allocator >)':

Clean up GR branches

@alisagk @bcrinquand could you guys clean up the GR branches and merge into one? ideally, a working version would be merged into dev/latest. Also, we'll need to remove the output files from the commits (see data/)

add spectrum output

per-species binned particle distributions

Move all `PrtlCoordD` to metric template `M::PrtlD`

Leftover charge near the axis when strong U_theta

Left: SR, right: GR.

Only occurs when the particle is reflected off the axis with a large-enough $u_\theta$. Pgen to reproduce: -D pgen=debug/deposit with both engines.

compile with clang 13.0.0

1.In the file entity/framework/utils/qmath.h: line 58 & line 78:
Clang can't find matched template for the two instantiations and gives out errors. Removing the key word "Inline" solves the issue. While gcc is not having any problem compiling this.

2.In the file entity/framework/meshblock/meshblock.cpp: line 128:
if ((field == FieldID::Charge) && AlmostEqual(charge, ZERO)) {
Variable "charge" is float while "ZERO" is double when double_precision is defined.
This raises an ambiguity when using AlmostEqual() because only pure float and pure double versions are defined.
Clang don't like this and gives out an error while gcc only gives out an warning.
I changed it to:
if ((field == FieldID::Charge) && AlmostEqual(charge, static_cast(ZERO))) {

Segmentation fault

I'm testing the code using weibel.toml file as input
code build with
" cmake ../ -B build -D output=ON -D pgen=weibel -D engine=pic -D precision=double -DKokkos_ENABLE_OPENMP=ON"
In the file weibel.toml, when resolution = [512, 512] or larger than 512
I got error:
/tmp/slurmd/job29753857/slurm_script: line 17: 771687 Segmentation fault (core dumped) ./build/src/entity.xc -input ./weibel.toml

All the maxnparts are set to 1e6 to reduce running time, others remained as defaults.

GR | version 0.9

• Fieldsolver
  • added (compiles)
  • tested
• Particle pusher
  • added (compiles)
  • tested
• Current deposit
  • added (compiles)
  • tested
• Output
  • added (compiles)
  • tested

add parameter output

sim_params probably will be supported as attrs to the output hdf5 file