Software Support

Please be patient with us as we attempt to build a new software resource library.  You will notice the tabbed content below, this will be the new structure for all of our software resouce pages.  This main software page is here to give you a quick look at what to expect on the individual Software pages.  We have tried to split our software into meaningful categories, but if you are having trouble finding help on a peice of software check out alhpabetical listing here.

  • Overview
  • HPC Docs
  • HPC Tutorials
  • Linux Docs
  • Linux Tutorials
  • Windows Docs
  • Windows Tutorials


Each Supported Software Title will have a page layout identical to this page.  The Overview will give a brief description of the software and a list of wear it is installed on campus.

HPC Docs

This tab will contain documentation about the general use of the software on the HPC.  This tab will only exist if the software is availabe on the HPC

HPC Tutorials

This tab will contain a single quickstart tutorial for using the application on our campus HPC System, or links to several tutorials.

Linux Docs

Linux Tutorials

For Ubuntu 14.04.

Installation Instructions

Install these first:
sudo -E apt-get install build-essential \
gfortran \
tcl \
git \
m4 \
freeglut3 \
libx11-dev \

Then download the .deb package

This version will change over time, but will be updated on the mooseframework website.

Once the moose .deb package is extracted and installed, you need to update your .bashrc file.

Add the following to your ~/.bashrc file to source the MOOSE environment. Once added, any new terminal window opened, will now have the necessary MOOSE environment.

# Source MOOSE Environment

if [ -f /opt/moose/environments/moose_profile ]; then
. /opt/moose/environments/moose_profile


Log back into the system, via terminal and do:

module list

This will list all of the recently created modules:

rlhaffer@r99itrss~$ module list
Currently Loaded Modulefiles:
1) moose/.gcc_4.9.1
2) moose/.tbb
3) moose/.openmpi-1.8.1_gcc
4) moose/.openmpi_petsc-3.5.2-gcc-superlu
5) moose-tools
6) moose/.ccache
7) moose-dev-gcc

Now that this is all complete, which should take about 15 minutes...the .deb extracts takes some then go to this site.

Start with step 2. Cloning MOOSE.

Make a projects directory somewhere. The developers have built this to not be dependent on 'sudo'/'root' for anything, but in our domain Ubuntu builds, we have to use sudo in some places.

What I did, was created the projects folder with rwx for everyone..chmod -R 777 /usr/local/projects
Clone the git repo in this projects folder.

mkdir ~/projects
chmod -R 777 projects
cd ~/projects
git clone
cd ~/projects/moose
git checkout master

Once you have verified you have checked out the master..go to step 3.

This is what sometimes does not finally did this last time of installation

cd ~/projects/moose/scripts

If building for more then one user...use sudo ./
If buildling for yourself, in you own profile, no need for sudo.

Building libmesh may take 10-30 minutes or more to compile.

Once compiled, its time to test -- Step 4.

cd ~/projects/moose/test
then run:

make -j8

This compile can take up to a couple of hours, even on one of the dual multi core precisions.

This should compile and not produce many errors, mainly, no PETSc errors... PETSc is a toolkit MOOSE uses, but is updated more frequently than MOOSE. Always use the MOOSE verified version.

When the make is finished, time to run the tests.

./run_tests -j8

This will take 10-30 minutes as well. But when done, it should tell you how many passed, failed or skipped.

Somewhere over 800 tests pass and even with a couple of failures, we have not had any students tell us those failures caused any issues.
MOOSE can connect and use so many tools & libraries, it tests everything, but if some of those libraries are not installed or compiled, its default is to tell you it failed on that test.




Running Peacock

First, you need to add this to your .bashrc file.
export PATH=/usr/local/MOOSE/moose/gui:$PATH

Peacock needs an input file to read from according to their documentation.

rlhaffer@r99itrss:~$ peacock -i
Usage: peacock [options] [input_file] [exodus_file]

If you go to the examples folder...

I used the ex01_inputfile example.

You must compile the example files. So, when you are in an example folder, just run make to compile.\\
When make completes, you will have an ex01.i file. The '.i' files are the input files peacock understands.\\

When that is done, run peacock in the example folder.
peacock -i ex01.i

The GUI will load with the example file's geometry.

Windows Docs

This tab will contain Windows Specific documenation about the software title

Windows Tutorials

This tab will contain a single quickstart tutorial for using the application on our campus Windows Systems, or links to several tutorials.