Thomas-Ulrich

I would change: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/pumi/package.py#L97-L98 to: ``` if self.spec.satisfies("simmodsuite=base"): args.append("-DENABLE_SIMMETRIX=ON") mpi_id = spec["mpi"].name + spec["mpi"].version.up_to(1).string args.append("-DSIM_MPI=" + mpi_id) ``` and change also https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/pumi/package.py#L104 to `mpi_id = spec["mpi"].name + spec["mpi"].version.up_to(1).string` Because the...

I double-checked and the ParaView outputs are written in the datatype used in the simulation. That is single precision simulations get written in float, double in double. (And that means...

I can confirm that the problem is fixed with the change in the branch. (and that it also works with the wiggle factor)

Well this does not work with the latest format of energy output: https://seissol.readthedocs.io/en/latest/energy-output.html#postprocessing-and-plotting ``` (base) ulrich@ulrich-ThinkPad-T490s:~/SeisSol/SeisSol$ head /home/ulrich/trash/./output_model_2603_s205_second_event_noDCFS/Turkey_2events_31mio_o5_2603_s205-energy.csv -n 100 time,variable,measurement 0,gravitational_energy,0 0,acoustic_energy,0 0,acoustic_kinetic_energy,0 0,elastic_energy,0 0,elastic_kinetic_energy,0 0,plastic_moment,0 0,total_frictional_work,0 0,static_frictional_work,0 0,seismic_moment,0...

Hi, I get the following error: ``` (base) ulrich@ulrich-ThinkPad-T490s:~/SeisSol/SeisSol$ python3 postprocessing/visualization/tools/plot_EnergyOutput.py /home/ulrich/trash/output_tpv1213/tpv13-energy.csv File selected: /home/ulrich/trash/output_tpv1213/tpv13-energy.csv Traceback (most recent call last): File "/home/ulrich/SeisSol/SeisSol/postprocessing/visualization/tools/plot_EnergyOutput.py", line 55, in df = df.pivot_table(index="time", columns="variable", values="measurement")...

Here is a comparison with the Kaikoura LSW training example:  With a zoom in to the end of the moment rate release  (note that I also increased the...

does your seissol integrates the fix of: https://github.com/SeisSol/SeisSol/issues/1026

I would put 0.4.0 once https://github.com/SeisSol/Visualization/pull/15/files is merged. 0.3.0 was buggy.

could be that your seissol is compiled with hdf5 1.10 or 1.12 and your paraview with hdf5 1.8. Try using xdmfWriterBackend = 'posix' in the parameter file (if not already...

@FURUNZ : if xdmfWriterBackend = 'posix' , then no h5 are created but several folder with *.bin in it. I close the issue. Please reopen if you still have the...