Building Reactor Module with WASP and LibMesh #27749
Answered
by
Theo21S
Theo21S
asked this question in
Q&A Meshing
-
|
I have installed MOOSE envs onto my PC but I cannot seem to build the Reactor. I'm not sure what I am doing wrong or how to fix it. |
Beta Was this translation helpful? Give feedback.
Answered by
Theo21S
Jun 7, 2024
Replies: 5 comments 53 replies
-
|
These errors are pretty common when libMesh has not yet been built. Also, it seems you may have copied-n-pasted from other instructions, being that these three commands were entered simultaneously: cd $MOOSE_DIR/modules/reactor
make -j4
./reactor-opt --versionWe certainly avoid telling folks to set and use |
Beta Was this translation helpful? Give feedback.
11 replies
-
|
From what I can tell It says I should have a module named reactor -opt. But that doesn't exist anywhere in my files when I installed MOOSE. I don't know if that's an installation failure or if I need to download it separately. |
Beta Was this translation helpful? Give feedback.
-
|
You are running as root outside of a container (Docker, Apptainer, Singularity, things of this nature), which is dangerous. Can we start again, without using the root user account? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I'm sorry I am pretty new to all of this. I'm still doing research to figure out how to even use the command terminals to get MOOSE. Thank you for being patient with me! I am using WSL ubuntu. Should I use WSL command prompt? |
Beta Was this translation helpful? Give feedback.
-
|
When you launch your WSL instance, does it log you in automatically as root? Or are you having to run something like |
Beta Was this translation helpful? Give feedback.
-
|
It automatically logs me in as root. |
Beta Was this translation helpful? Give feedback.
-
|
https://www.kapwing.com/w/IWvBtu_nVk This is how I navigate there. |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
Something is wrong with your installation of Conda. Can you start over and try again? What I mean by this, is uninstalling your current implementation of Conda: rm -rf /root/miniforgeAnd then running through the Miniforge install process again. Also, it would help if you entered one command at a time. That way we halt upon the first error. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense, yes ill try that. However the computer I am running Moose on is not my own. There are some installations that require me to open a ticket with my organization. Just letting you know if the process is delayed. |
Beta Was this translation helpful? Give feedback.
-
|
We can try to create an additional environment, just to see if we continue to see:
What does the following return: conda create -n testing -q -y
conda activate testing(this creates a blank environment) |
Beta Was this translation helpful? Give feedback.
-
|
I'll try uninstalling Conda because I don't think I need permission to install it. Do I need to install miniforge again too or just my conda environment? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
When I run |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Yeah that command will return nothing if nothing goes wrong :) Go ahead and proceed to installing Miniforge, and we will continue from there |
Beta Was this translation helpful? Give feedback.
-
|
Understood |
Beta Was this translation helpful? Give feedback.
-
|
https://conda-forge.org/miniforge/ Or must it be installed from MOOSE INL website? |
Beta Was this translation helpful? Give feedback.
-
|
The end results will be the same. But what you want to do is: curl -L -O https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh
bash Miniforge3-Linux-x86_64.sh -b -p ~/miniforgeThen, just follow the rest of the instructions on: https://mooseframework.inl.gov/getting_started/installation/conda.html |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if what I did is any different but Ill send you the results |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
23 replies
-
|
@milljm I'm not sure how much of this information is needed so ill just send all of the results: |
Beta Was this translation helpful? Give feedback.
-
|
excellent! Lets see if we can reactivate this environment: deactivate: conda deactivateThen activate: conda activate testingFrom here, you should be able to build the reactor example: cd ~/moose/modules/reactor
make -j4 |
Beta Was this translation helpful? Give feedback.
-
|
Yes sir! It's finally doing anything but giving me an error!! @milljm is definitely the GOAT I'll spare you the hundreds of lines of code by sending you the last few lines |
Beta Was this translation helpful? Give feedback.
-
|
To be a bit more aligned with production, you can create a properly named Conda environment other than "testing" if you choose. You can create as many as you have hard drive space for. That said, you can keep "testing" if you want 😄 conda deactivate
conda activate baseThis ensures you are in the base environment, and so as not to inherit anything from another specific environment while you create new ones. conda create -n moose moose-dev
conda activate mooseetc etc. repeat with new environments as necessary. You can also ignore this post and simply continue to use "testing"! Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much! |
Beta Was this translation helpful? Give feedback.
-
|
@milljm I followed the instructions for the reactor module however I am getting stopped up at the part where it says the following. I don't want to break my PATH again so I thought I would ask why it doesn't work. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I think it helps to be in the same directory as the input file when you run your application: cd ~/moose/modules/reactor/test/tests/meshgenerators/simple_hexagon_generator/
../../../../reactor-opt -i sim_hex.i --mesh-onlyReading your prompt very carefully, the issue I think is that you are already in the directory where And by providing a relative path: ...that is a path not preceding with a /moose/modules/reactor/moose/modules/reactor/reactor-opt |
Beta Was this translation helpful? Give feedback.
-
|
Thank you I understand now.
This code ran the input file. |
Beta Was this translation helpful? Give feedback.
Answer selected by
Theo21S
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you I understand now.
(moose) root@COMECH-0083:/moose/modules/reactor/test/tests/meshgenerators/simple_hexagon_generator# /moose/modules/reactor/reactor-opt -i sim_hex.i --mesh-onlyThis code ran the input file.