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/usage/run_artemis.rst
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,6 +111,34 @@ Advanced Usage
111
111
- **Micromagnetics**: When ``USE_LLG=TRUE``, additional array fields for magnetization components will be allocated, and the FDTD step will couple to LLG updates.
112
112
- **Superconductivity**: Some versions of ARTEMIS allow modeling superconductors with a two-fluid model. Ensure your input file is set up properly, referencing the parameters introduced in the relevant publication or example.
113
113
114
+
Common Pitfalls
115
+
---------------
116
+
117
+
1. **MPI Rank Mismatch / Library Errors**:
118
+
- Ensure that your environment is loading the correct MPI library before running, e.g.:
119
+
::
120
+
module load openmpi
121
+
mpirun -n 4 ./main3d...
122
+
- Mixing different MPI implementations at compile/run time can cause errors.
123
+
124
+
2. **CUDA or HIP Errors**:
125
+
- If you compiled with ``USE_GPU=TRUE``, verify that your CUDA or HIP drivers match the version you used during compilation.
126
+
- On HPC systems:
127
+
::
128
+
module load cuda
129
+
nvidia-smi
130
+
to confirm GPU visibility.
131
+
132
+
3. **Out-of-Memory**:
133
+
- Very fine meshes or many levels of AMR can exceed GPU or CPU memory. Try reducing resolution or domain size.
134
+
- Check if your domain decomposition is balanced across MPI ranks.
135
+
136
+
4. **Missing Output Files**:
137
+
- Check that the parameter ``plot_int`` in your input file is set appropriately (e.g., 100 steps) to generate plotfiles.
138
+
- If no plotfiles are produced, you might be running fewer steps than ``plot_int``.
139
+
140
+
For further assistance, please open an issue on our GitHub or consult the AMReX documentation.
0 commit comments