From 679d5d1ed482c7b6c870cc243dd52c84a3e87408 Mon Sep 17 00:00:00 2001 From: Mahmoud Eltawila Date: Mon, 7 Oct 2024 00:09:34 -0500 Subject: [PATCH] adding ticket (Ref. #30) --- .../CAD_based_workflow/CAD_workflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/content/verification_validation_examples/CAD_based_workflow/CAD_workflow.md b/doc/content/verification_validation_examples/CAD_based_workflow/CAD_workflow.md index 7cd06ac..c23a9c6 100644 --- a/doc/content/verification_validation_examples/CAD_based_workflow/CAD_workflow.md +++ b/doc/content/verification_validation_examples/CAD_based_workflow/CAD_workflow.md @@ -105,8 +105,8 @@ mpiexec -np 2 fenix-opt -i solid.i --n-threads=2 This will run both MOOSE and OpenMC (with Cardinal) with 2 MPI processes and 2 OpenMP threads per rank. To run the simulation faster, you can increase the parallel processes/threads, or simply decrease the number of particles used in OpenMC. When the simulation has completed, you will have created a number of different output files: -- `solid_out.e`, an Exodus output with the solid mesh and solution from the MOOSE/FENIX input file -- `solid_out_openmc0.e`, an Exodus output with the OpenMC solution and the data that was ultimately transferred in/out of OpenMC +- `solid_out.e`, an Exodus output with the solid mesh and solution from the MOOSE/FENIX input file. +- `solid_out_openmc0.e`, an Exodus output with the OpenMC solution and the data that was ultimately transferred in/out of OpenMC. ## Results