Run successfully but exit code 1

[tianninglyu]

Hi all,

I am running HydroBlast3D test, using input file benchmark_unifrom_256.in. The run completed successfully, but after running there is an "exit code 1", indicating there is some error.

Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.

mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

Process name: [[4670,1],0]
Exit code: 1

[dosubot[bot]]

This is expected behavior: the HydroBlast3D test checks if the kinetic energy matches the analytical solution at t=1 by default. If your simulation doesn't reach t=1 (for example, if max_timesteps is too low), the test fails this check and returns exit code 1—even though the run completes successfully. If you want to avoid this non-zero exit code, add blast_problem.check_solution=false to your input file or as a command-line parameter. This disables the solution check and lets the test exit with code 0. More details are in this thread.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[tianninglyu]

Hi @dosu, thank you very much. I have another question. If I only want to compile a specific problem but not all the test problem, What should I do?

[dosubot[bot]]

You can compile only a specific problem in quokka by building its individual CMake target. Each problem (like HydroBlast3D) is set up as a separate executable target in its own subdirectory. For example, to build just HydroBlast3D, run:

cmake --build . --target test_hydro3d_blast

Replace test_hydro3d_blast with the target name for your desired problem. This approach works for any problem listed in src/problems—each has its own target defined in its respective CMakeLists.txt (example). No need to build all test problems; just specify the target you want.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[tianninglyu]

Thanks @dosu. If I want to write and compile my own problem, what should I do?

[dosubot[bot]]

To write and compile your own problem in quokka, follow this pattern:

1. Create a new subdirectory under src/problems (for example, src/problems/MyProblem).
2. Add your problem source file (e.g., my_problem.cpp) in that directory. Your code should define a struct for your problem, specialize the required traits (like Physics_Traits, EOS_Traits, etc.), implement initial condition and grid refinement functions, and provide a problem_main() function that sets up and runs the simulation. You can use existing problems as templates—see HydroBlast3D or ParticleRadiation for examples.
3. Add a CMakeLists.txt in your problem directory. Define your executable with add_executable, include ${QuokkaObjSources}, and (if you use CUDA) call setup_target_for_cuda_compilation. You can also register a test with add_test. Example: HydroBlast3D CMakeLists.txt.
4. Edit src/problems/CMakeLists.txt and add a line: add_subdirectory(MyProblem) to integrate your problem into the build system (reference).
5. Build your problem with CMake, using your target name:

   cmake --build . --target my_problem
   

There’s no official template, but the existing problems are good practical guides. All necessary build logic for a problem lives in its own subdirectory and CMakeLists.txt, plus a single line in the central src/problems/CMakeLists.txt.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}