You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Docs/source/install/dependencies.rst
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ List of Dependencies
6
6
WarpX depends on the following popular third party software.
7
7
Please see installation instructions below.
8
8
9
-
- a mature `C++20 <https://en.wikipedia.org/wiki/C%2B%2B17>`__ compiler, e.g., GCC 12+, Clang 14, NVCC 12.4, MSVC 19.39 or newer
9
+
- a mature `C++20 <https://en.wikipedia.org/wiki/C%2B%2B20>`__ compiler, e.g., GCC 12+, Clang 14, NVCC 12.4, MSVC 19.39 or newer
10
10
- `CMake 3.24.0+ <https://cmake.org>`__
11
11
- `Git 2.18+ <https://git-scm.com>`__
12
12
- `AMReX <https://amrex-codes.github.io>`__: we automatically download and compile a copy of AMReX
@@ -23,8 +23,8 @@ Optional dependencies include:
23
23
- for on-node accelerated compute *one of either*:
24
24
25
25
- `OpenMP 3.1+ <https://www.openmp.org>`__: for threaded CPU execution or
26
-
- `CUDA Toolkit 11.7+ <https://developer.nvidia.com/cuda-downloads>`__: for Nvidia GPU support (see `matching host-compilers <https://gist.github.com/ax3l/9489132>`__) or
27
-
- `ROCm 5.2+ (5.5+ recommended)<https://gpuopen.com/learn/amd-lab-notes/amd-lab-notes-rocm-installation-readme/>`__: for AMD GPU support
26
+
- `CUDA Toolkit 12.2+ <https://developer.nvidia.com/cuda-downloads>`__: for Nvidia GPU support (see `matching host-compilers <https://gist.github.com/ax3l/9489132>`__) or
27
+
- `ROCm 5.5+<https://gpuopen.com/learn/amd-lab-notes/amd-lab-notes-rocm-installation-readme/>`__: for AMD GPU support
28
28
- `oneAPI <https://www.intel.com/content/www/us/en/developer/tools/oneapi/overview.html>`__: for Intel GPU support
29
29
- `FFTW3 <http://www.fftw.org>`__: for spectral solver (PSATD or IGF) support when running on CPU or SYCL
30
30
@@ -35,10 +35,9 @@ Optional dependencies include:
35
35
36
36
- see `optional I/O backends <https://github.com/openPMD/openPMD-api#dependencies>`__, i.e., ADIOS2 and/or HDF5
37
37
- `Ascent 0.8.0+ <https://ascent.readthedocs.io>`__: for in situ 3D visualization
38
-
- `SENSEI 4.0.0+ <https://sensei-insitu.org>`__: for in situ analysis and visualization
39
38
- `CCache <https://ccache.dev>`__: to speed up rebuilds (For CUDA support, needs version 3.7.9+ and 4.2+ is recommended)
40
39
- `Ninja <https://ninja-build.org>`__: for faster parallel compiles
Copy file name to clipboardExpand all lines: Docs/source/usage/parameters.rst
+20-29Lines changed: 20 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3100,7 +3100,8 @@ Details about the collision models can be found in the :ref:`theory section <mul
3100
3100
:default: 0
3101
3101
:optional:
3102
3102
3103
-
For pairwisecoulomb collisions, whether to correct the energy and momentum after the collisions so that they are conserved.
3103
+
Only for ``pairwisecoulomb`` collisions, whether to correct the energy and momentum after the collisions so that they are conserved.
3104
+
This can be set for each collision using :pp:param:`<collision_name>.correct_energy_momentum`.
3104
3105
In binary collisions, if the weights of the colliding particles are not the same, the collision does not
3105
3106
exactly conserve energy and momentum. When this option is on, after the collisions, small modifications are made to the
3106
3107
particle momentum so that the energy and momentum are exactly conserved in each cell.
@@ -3111,25 +3112,39 @@ Details about the collision models can be found in the :ref:`theory section <mul
3111
3112
:default: 0.05
3112
3113
:optional:
3113
3114
3114
-
For pairwisecoulomb collisions, when correcting the energy and momentum conservation, the energy correction is applied to pairs of particles in their center of momentum frame.
3115
+
Only for ``pairwisecoulomb`` collisions, with :pp:param:`collisions.correct_energy_momentum` set, the energy correction is applied to pairs of particles in their center of momentum frame.
3116
+
This can be set for each collision using :pp:param:`<collision_name>.energy_fraction`.
3115
3117
This parameter is the fraction of the relative energy in the COM frame that is used in the correction.
3116
3118
3117
3119
.. pp:param:: collisions.energy_fraction_max
3118
3120
:type: ``float``
3119
3121
:default: 0.5
3120
3122
:optional:
3121
3123
3122
-
For pairwisecoulomb collisions, when correcting the energy and momentum conservation, the energy correction is applied to pairs of particles in their center of momentum frame.
3123
-
This parameter is the fraction of the total relative energy in the COM frame of all pairs that is used in the correction.
3124
+
Only for ``pairwisecoulomb`` collisions, with :pp:param:`collisions.correct_energy_momentum` set, the energy correction is applied to pairs of particles in their center of momentum frame.
3125
+
This can be set for each collision using :pp:param:`<collision_name>.energy_fraction_max`.
3126
+
This parameter sets the maximum allowed value for :pp:param:`collisions.energy_fraction`.
3127
+
If residual energy error remains after a pass over all particle pairs in a cell, the algorithm increases the effective correction fraction for the next pass based on an estimate of the remaining error.
3128
+
If this computed value exceeds the limit imposed by this parameter, the correction is deemed to have failed and particle velocities in the cell are restored to their pre-collision values.
3124
3129
3125
3130
.. pp:param:: collisions.beta_weight_exponent
3126
3131
:type: ``float``
3127
3132
:default: 1.
3128
3133
:optional:
3129
3134
3130
-
For pairwisecoulomb collisions, when correcting the energy and momentum conservation, this parameter controls the exponent used on the particle weight when distributing the momentum correction.
3135
+
Only for ``pairwisecoulomb`` collisions, with :pp:param:`collisions.correct_energy_momentum` set, this parameter controls the exponent used on the particle weight when distributing the momentum correction.
3136
+
This can be set for each collision using :pp:param:`<collision_name>.beta_weight_exponent`.
3131
3137
With a value greater than 1, it will distribute more of the correction to particles with higher weights.
Only for ``pairwisecoulomb`` collisions, with :pp:param:`collisions.correct_energy_momentum` set, specifies whether the particles are sorted by weight when the energy correction is applied.
3145
+
This can be set for each collision using :pp:param:`<collision_name>.energy_correction_sort_by_weight`.
3146
+
When the particles have a range of weights, sorting improves the correction by applying more of it to the heavier weighted particles, which has a proportionately smaller effect on their momenta, and typically reduces the number of particles that the correction is applied to.
3147
+
3133
3148
.. pp:param:: collisions.split_momentum_push
3134
3149
:type: ``bool``
3135
3150
:default: 1
@@ -3140,30 +3155,6 @@ Details about the collision models can be found in the :ref:`theory section <mul
3140
3155
This is only implemented for the explicit evolve scheme and is not available for the implicit evolve schemes, because the implicit
3141
3156
formulation is intrinsically energy-conserving when combined with MCC collisions, as shown in `Angus et al., J. Comput. Phys. 456, 2022 <https://doi.org/10.1016/j.jcp.2022.111030>`__.
0 commit comments