castro.change_max = 1.0 means that the timestep can only ever stay the same or decrease relative to its initial value. I think we should disallow this value, I have a hard time imagining a use case for this (if you want a fixed timestep, use fixed_dt, and if you want a timestep cap but still allow the timestep to decrease, use max_dt). It causes problems with the retry functionality.
When creating a new simulation from scratch, I had to bounce between the equations/ folder and the examples/ folder to figure out the syntax for a new set of initial & boundary conditions. Ideally, the examples would be self-contained; from the user's point of view, there's nothing special about boundary_condition_two_interacting_blast_waves, which is exported as part of Trixi's API - it's o
A parallel, fast solver for the scalar advection-diffusion and the incompressible Navier-Stokes equations based on semi-Lagrangian/Volume-Integral method.
A Python framework for developing parallelized Computational Fluid Dynamics software to solve the hyperbolic 2D Euler equations on distributed, multi-block structured grids.
This is the educational project with main purpose is to develop and test the multidimensional adaptive grid which can be used in Reinforcement Learning area. Additional purpose of this project is to learn and try CUDA programming with Alea GPU.
My fork of NEMoSys, a platform for adaptive mesh refinement and solution verification. I was the primary developer of this software while at Illinois Rocstar LLC, funded by a DOE SBIR Phase I grant. The current version with Phase II developments can be found at https://github.com/IllinoisRocstar/Nemosys.
castro.change_max = 1.0means that the timestep can only ever stay the same or decrease relative to its initial value. I think we should disallow this value, I have a hard time imagining a use case for this (if you want a fixed timestep, use fixed_dt, and if you want a timestep cap but still allow the timestep to decrease, use max_dt). It causes problems with the retry functionality.