Welcome to the cosmological hydrodynamical code
______ _________________
/ ___/ | / / _/ ___/_ __/
\__ \| | /| / // // /_ / /
___/ /| |/ |/ // // __/ / /
/____/ |__/|__/___/_/ /_/
SPH With Inter-dependent Fine-grained Tasking
Website: www.swiftsim.com
Twitter: @SwiftSimulation
See INSTALL.swift for install instructions.
Usage: swift [OPTION]... PARAMFILE
swift_mpi [OPTION]... PARAMFILE
Valid options are:
-a Pin runners using processor affinity.
-c Run with cosmological time integration.
-C Run with cooling.
-d Dry run. Read the parameter file, allocate memory but does not read
the particles from ICs and exit before the start of time integration.
Allows user to check validy of parameter and IC files as well as memory limits.
-D Always drift all particles even the ones far from active particles. This emulates
Gadget-[23] and GIZMO's default behaviours.
-e Enable floating-point exceptions (debugging mode).
-f {int} Overwrite the CPU frequency (Hz) to be used for time measurements.
-g Run with an external gravitational potential.
-G Run with self-gravity.
-n {int} Execute a fixed number of time steps. When unset use the time_end parameter to stop.
-s Run with hydrodynamics.
-S Run with stars.
-t {int} The number of threads to use on each MPI rank. Defaults to 1 if not specified.
-v [12] Increase the level of verbosity
1: MPI-rank 0 writes
2: All MPI-ranks write
-y {int} Time-step frequency at which task graphs are dumped.
-h Print this help message and exit.
See the file examples/parameter_example.yml for an example of parameter file.
"...Examples/git@gitlab.cosma.dur.ac.uk:swift/swiftsim.git" did not exist on "571d2b948b4c0fd677377823bc8cc997c29504f8"
Select Git revision
swiftsim
Matthieu Schaller authored
Added smoothing length correction limiter to Gizmo hydro_predict_extra. For some reason, the smoothing length prediction in GIZMO sometimes goes completely wrong, causing the code to crash in space_regrid, see #271. To overcome this, I have added a limit on the increase in smoothing length during the prediction step for GIZMO. This appears to solve the issue @jwillis was having with the EAGLE_12 test (I am currently testing it on one of my machines, and it's still running after 6000 steps). I'm not sure it is worth looking into the cause of the bad smoothing length predictions. The smoothing length update is computed based on a mixture of SPH and GIZMO variables, so this is bound to go wrong sometimes. Maybe there are smarter ways to do this. See merge request !318
| Name | Last commit | Last update |
|---|---|---|
| doc | ||
| examples | ||
| m4 | ||
| src | ||
| tests | ||
| theory | ||
| .clang-format | ||
| .gitignore | ||
| AUTHORS | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| ChangeLog | ||
| INSTALL.swift | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| autogen.sh | ||
| configure.ac | ||
| format.sh |