Philipp Grete
Philipp Grete
**Describe the bug** Our code outputs some warnings that get parsed as tests, e.g., ``` $ ctest -N Test project /home/pgrete/src/parthenon/build-catch2 Test #1: Kokkos::OpenMP::initialize WARNING: OMP_PROC_BIND environment variable not set...
With current `develop` and following env: ```bash $ module list Currently Loaded Modulefiles: 1) shared 4) cpe-cray 7) craype-arm-nsp1 10) cray-mvapich2_nogpu_sve/2.3.5 2) slurm/slurm/19.05.7 5) cce-sve/10.0.2 8) craype-network-infiniband 11) cmake/3.22.1 3)...
## PR Summary Add `yt` frontend for codes based on the `Parthenon` AMR framework (https://github.com/parthenon-hpc-lab/parthenon) including AthenaPK (https://github.com/parthenon-hpc-lab/athenapk), Phoebus (https://github.com/lanl/phoebus) or KHARMA (https://github.com/AFD-Illinois/kharma) Note that the mesh structure in `Parthenon`...
How many device atomics are used in Ascent and it's software stack and is the internal programming/memory model safe with regard to this, see https://docs.olcf.ornl.gov/systems/frontier_user_guide.html#floating-point-fp-atomic-operations-and-coarse-fine-grained-memory-allocations ? We've been using `Kokkos::ScatterView`s...
On Lumi (same architecture as Frontier) I am observing a significant performance regression (2x slower) when linking to Ascent (not even calling any function) in AthenaPK/Parthenon. I looked at some...
I managed to plot the mesh (with every singe cell). Is there also a way to only plot block (`Node`) boundaries?
I'm in the process of adding support for OpenPMD output to our block structured AMR code https://github.com/parthenon-hpc-lab/parthenon In light of the open PR on the standard for mesh refinement https://github.com/openPMD/openPMD-standard/pull/252...
Trying to open series with the `viewer` results in (same for trying the `%T` syntax directly): ```Python from openpmd_viewer import OpenPMDTimeSeries ts = OpenPMDTimeSeries("opmd.00007.bp/",backend="openpmd-api") [AbstractIOHandlerImpl] IO Task READ_ATT failed with...
What's the best practice/recommendation wrt to storing variables that share the same `Mesh`? Creating one mesh per variable is duplicating information -- especially thinking about deep mesh refinement hierarchies. This...
I just learned the long way that my naive approach to slice data (or even read full datasets) like ```python mydata = it.meshes['cons_cons_density_lvl1'][opmd.Record_Component.SCALAR][:,:,10] series.flush() do_work_with_mydata() ``` Does not play nicely...