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
_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
8
+
Please check the relevant boxes and fill in the specific versions or details for the relevant items.
9
+
Thank you for taking the time to report this issue. We will respond as soon as possible._
10
+
11
+
## Description
12
+
A clear and concise description of the bug.
13
+
14
+
## Expected behavior
15
+
What did you expect to happen when you encountered the issue?
16
+
17
+
## How to reproduce
18
+
Please provide (if available):
19
+
- WarpX inputs files
20
+
- PICMI Python files
21
+
- Python post-processing scripts
22
+
23
+
If you are unable to provide certain files or scripts, please describe the steps you took to encounter the issue.
24
+
25
+
Please minimize your inputs/scripts to be concise and focused on the issue.
26
+
For instance, make the simulation scripts as small and fast to run as possible.
27
+
28
+
## System information
29
+
Please check all relevant boxes and provide details.
30
+
31
+
- Operating system (name and version):
32
+
-[ ] Linux: e.g., Ubuntu 22.04 LTS
33
+
-[ ] macOS: e.g., macOS Monterey 12.4
34
+
-[ ] Windows: e.g., Windows 11 Pro
35
+
- Version of WarpX: e.g., latest, 24.10, etc.
36
+
- Installation method:
37
+
-[ ] Conda
38
+
-[ ] Spack
39
+
-[ ] PyPI
40
+
-[ ] Brew
41
+
-[ ] From source with CMake
42
+
-[ ] Module system on an HPC cluster
43
+
- Other dependencies: yes/no, describe
44
+
- Computational resources:
45
+
-[ ] MPI: e.g., 2 MPI processes
46
+
-[ ] OpenMP: e.g., 2 OpenMP threads
47
+
-[ ] CPU: e.g., 2 CPUs
48
+
-[ ] GPU: e.g., 2 GPUs (NVIDIA, AMD, etc.)
49
+
50
+
If you encountered the issue on an HPC cluster, please check our [HPC documentation](https://warpx.readthedocs.io/en/latest/install/hpc.html) to see if your HPC cluster is already supported.
51
+
52
+
## Steps taken so far
53
+
What troubleshooting steps have you taken so far, and what were the results?
54
+
55
+
Have you tried debugging the code, following the instructions in our [debugging documentation](https://warpx.readthedocs.io/en/latest/usage/workflows/debugging.html)?
56
+
57
+
## Additional information
58
+
If applicable, please add any additional information that may help explain the issue, such as log files (e.g., build logs, error logs, etc.), error messages (e.g., compiler errors, runtime errors, etc.), screenshots, or other relevant details.
_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
8
+
Please check the relevant boxes and fill in the specific versions or details for the relevant items.
9
+
Thank you for taking the time to report this issue. We will respond as soon as possible._
10
+
11
+
## Context and motivation
12
+
Please provide a clear and concise description of the context that is prompting you to request a new feature. What problem are you trying to solve, and how will this feature help you achieve your goals?
13
+
14
+
## Proposed feature
15
+
Describe the feature you would like to add to WarpX in detail. Please include:
16
+
- A clear and concise description of the feature
17
+
- Any relevant technical requirements or specifications
18
+
- How you envision the feature being used
19
+
20
+
## Alternative solutions
21
+
Have you considered any alternative solutions or features that could achieve the same goal? If so, please describe them and explain why you believe the proposed feature is the best solution.
22
+
23
+
## Additional information
24
+
If applicable, please provide any additional information that may be relevant to the feature request, such as:
25
+
- Links to existing codes or implementations
26
+
- References to relevant publications or research
27
+
- Any specific use cases or scenarios where the feature would be particularly useful
about: Report an issue with installing or setting up WarpX.
4
+
labels: [install]
5
+
---
6
+
7
+
_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
8
+
Please check the relevant boxes and fill in the specific versions or details for the relevant items.
9
+
Thank you for taking the time to report this issue. We will respond as soon as possible._
10
+
11
+
## Description
12
+
A clear and concise description of the issue.
13
+
14
+
## System information
15
+
- Operating system (name and version):
16
+
-[ ] Linux: e.g., Ubuntu 22.04 LTS
17
+
-[ ] macOS: e.g., macOS Monterey 12.4
18
+
-[ ] Windows: e.g., Windows 11 Pro
19
+
- Version of WarpX: e.g., latest, 24.10, etc.
20
+
- Installation method:
21
+
-[ ] Conda
22
+
-[ ] Spack
23
+
-[ ] PyPI
24
+
-[ ] Brew
25
+
-[ ] From source with CMake
26
+
-[ ] Module system on an HPC cluster
27
+
- Other dependencies: yes/no, describe
28
+
- Computational resources:
29
+
-[ ] CPU
30
+
-[ ] GPU: e.g., NVIDIA, AMD, etc.
31
+
32
+
If you encountered the issue on an HPC cluster, please check our [HPC documentation](https://warpx.readthedocs.io/en/latest/install/hpc.html) to see if your HPC cluster is already supported.
33
+
34
+
If you encountered the issue installing from source with CMake, please provide the output of the following steps:
35
+
1. buildsystem generation: output of `cmake --fresh -S . -B build` (include your specific build options, e.g., `-DWarpX_DIMS=3`)
36
+
2. project build: output of `cmake --build build` (include your specific build options, e.g., `-j 4`)
37
+
38
+
If applicable, please add any additional information about your software environment:
39
+
-[ ] CMake: e.g., 3.24.0
40
+
-[ ] C++ compiler: e.g., GNU 11.3 with NVCC 12.0.76
41
+
-[ ] Python: e.g., CPython 3.12
42
+
-[ ] MPI: e.g., OpenMPI 4.1.1
43
+
-[ ] FFTW: e.g., 3.3.10
44
+
-[ ] HDF5: e.g., 1.14.0
45
+
-[ ] ADIOS2: e.g., 2.10.0
46
+
- Other dependencies: yes/no, describe
47
+
48
+
## Additional information
49
+
If applicable, please add any additional information that may help explain the issue, such as log files (e.g., build logs, error logs, etc.), error messages (e.g., compiler errors, runtime errors, etc.), screenshots, or other relevant details.
0 commit comments