Difference between revisions of "MOOSE Configuration"
Jump to navigation
Jump to search
(47 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
+ | {|align=right | ||
+ | |__TOC__ | ||
+ | |} | ||
== Configure and test your own "MOOSE" framework == | == Configure and test your own "MOOSE" framework == | ||
+ | ;Note: Make sure your .bashrc and .bash_profile shell initialization scripts are 'clean'. If you encounter errors while setting up MOOSE make sure there are no environment changes caused by those scripts. | ||
+ | |||
===Basic Steps=== | ===Basic Steps=== | ||
− | # mkdir projects | + | # mkdir projects (from a development session [[Development and Testing]]) |
# cd projects | # cd projects | ||
− | # module load moose/ | + | # module load moose/26-jul-21 |
# git clone https://github.com/idaholab/moose.git | # git clone https://github.com/idaholab/moose.git | ||
# cd moose | # cd moose | ||
# git checkout master | # git checkout master | ||
# export VTKLIB_DIR=${HPC_VTK_LIB} VTKINCLUDE_DIR=${HPC_VTK_INC} | # export VTKLIB_DIR=${HPC_VTK_LIB} VTKINCLUDE_DIR=${HPC_VTK_INC} | ||
− | # Run "./scripts/update_and_rebuild_libmesh.sh --enable-vtk-required | + | # Run "./scripts/update_and_rebuild_libmesh.sh --enable-vtk-required --with-vtk-lib=${HPC_VTK_LIB} --with-vtk-include=${HPC_VTK_INC}" and allow it to complete. It should finish without errors. |
− | + | # cd test; make -j 4; ./run_tests -j 4 (from a login node) | |
− | |||
− | |||
− | # cd test; run_tests -j 4 | ||
# Build and test the "phase field" module: | # Build and test the "phase field" module: | ||
## cd moose/modules/phase_field | ## cd moose/modules/phase_field | ||
Line 21: | Line 23: | ||
## make -j 4 | ## make -j 4 | ||
##./run_tests -j 4 | ##./run_tests -j 4 | ||
− | + | ||
− | + | ===Additional Information=== | |
− | === | + | See [https://support.rc.ufl.edu/show_bug.cgi?id=43807 Bugzilla Request #43807] |
− | + | ||
− | + | ==Running MOOSE== | |
− | + | Now that Moose is configured, learn how to use it at [[Running MOOSE]]. Or from a development session ([[Development and Testing]]). | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 15:20, 5 May 2023
Configure and test your own "MOOSE" framework
- Note
- Make sure your .bashrc and .bash_profile shell initialization scripts are 'clean'. If you encounter errors while setting up MOOSE make sure there are no environment changes caused by those scripts.
Basic Steps
- mkdir projects (from a development session Development and Testing)
- cd projects
- module load moose/26-jul-21
- git clone https://github.com/idaholab/moose.git
- cd moose
- git checkout master
- export VTKLIB_DIR=${HPC_VTK_LIB} VTKINCLUDE_DIR=${HPC_VTK_INC}
- Run "./scripts/update_and_rebuild_libmesh.sh --enable-vtk-required --with-vtk-lib=${HPC_VTK_LIB} --with-vtk-include=${HPC_VTK_INC}" and allow it to complete. It should finish without errors.
- cd test; make -j 4; ./run_tests -j 4 (from a login node)
- Build and test the "phase field" module:
- cd moose/modules/phase_field
- make -j 4
- ./run_tests -j 4
- Build and test the "combined" module:
- cd moose/modules/combined
- make -j 4
- ./run_tests -j 4
Additional Information
Running MOOSE
Now that Moose is configured, learn how to use it at Running MOOSE. Or from a development session (Development and Testing).