Closed benegee closed 4 months ago
Can you please post the full stacktrace?
Sure! Just updated it in the original post.
Did you start with a clean state or may there be some other mesh/solution files?
I started the simulations from scratch and wrote to a fresh output directory each time.
Please provide the full set of information when describing a bug like this. In this specific case, I guess you ran the simulation with MPI? Does the same problem occur without AMR but with MPI?
Took a while to double check. It is related to MPI, but not to AMR!
I did the following on rocinante (Ubuntu 22.04) using julia 1.10.0, starting from a fresh directory:
JULIA_DEPOT_PATH=./julia-depot julia --project=.
julia> using Pkg
julia> Pkg.add(["Trixi", "Trixi2Vtk", "OrdinaryDiffEq", "MPI"])
julia> using MPI
julia> mpiexec() do cmd
run(`$cmd -n 2 $(Base.julia_cmd()) --threads=1 --project=@. -e 'using Trixi; trixi_include(default_example())'`)
end
julia> using Trixi2Vtk
julia> trixi2vtk("out/solution_*.h5")
Maybe this change https://github.com/trixi-framework/Trixi.jl/pull/1748 just needs to be done for
function save_mesh_file(mesh::TreeMesh, output_directory, timestep, mpi_parallel::True)
as well?
Yes, that looks like it. Would you like to look into it and prepare a PR?
I did a Trixi.jl simulation using a TreeMesh and AMR and SaveSolution callbacks. When I try to convert the output files using trixi2vtk, I get:
So, should the h5 files have the "capacity" attribute, or should Trixi not look for it?
It works for non-AMR simulations!