how do I get peacock running?

897 views
Skip to first unread message

Stephen Thomas

unread,
Mar 19, 2014, 11:55:20 PM3/19/14
to moose...@googlegroups.com
Can someone tell me how to get peacock running?

Gaston, Derek R

unread,
Mar 20, 2014, 12:30:34 AM3/20/14
to Stephen Thomas, moose-users
If you installed one of the redistributable packages then all you need to do is add the moose/gui path to your $PATH like so:

export PATH=$HOME/projects/moose/gui:$PATH

(if you went by our directions and created a projects directory where you cloned MOOSE)

Then just run peacock in a MOOSE application directory.  For instance

cd $HOME/projects/moose/test
make -j8
peacock

The "make -j8" is just to make sure that you have built the moose_test executable.

I recommend putting the PATH export in your .bashrc or .bash_profile  (for Linux or OSX).

Derek



On Wed, Mar 19, 2014 at 11:55 PM, Stephen Thomas <stephen...@gmail.com> wrote:
Can someone tell me how to get peacock running?

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stephen Thomas

unread,
Mar 20, 2014, 12:49:37 AM3/20/14
to moose...@googlegroups.com, Stephen Thomas
Thanks Derek!
Now it seems to recognize peacock. But I am getting an error when I execute it:

sthomas@sthomas:~/projects/moose/examples/ex01_inputfile$ peacock
Using Executable: /home/sthomas/projects/moose/examples/ex01_inputfile/ex01-opt
Segmentation fault (core dumped)

Gaston, Derek R

unread,
Mar 20, 2014, 1:03:00 AM3/20/14
to Stephen Thomas, moose-users
Hmmm - you may need to update your copy of MOOSE (there was a segfault in Peacock on a select few architectures that we fixed last night).

You directly cloned MOOSE, right?  (as in, you're not working in a fork, right?)  If so, go into your MOOSE directory and do:

git pull --rebase origin master

That will update your copy of MOOSE - hopefully fixing up this issue with Peacock.

Derek

Gaston, Derek R

unread,
Mar 20, 2014, 1:04:57 AM3/20/14
to Stephen Thomas, moose-users
Oh - when you cloned MOOSE you also checked out the "master" branch, right?

To double check, in your MOOSE directory do a:

git status

And see what branch your'e on.  If you're not on the "master" branch then do a

git checkout master

Before doing that "pull --rebase" command...

Derek

Stephen Thomas

unread,
Mar 20, 2014, 1:26:40 AM3/20/14
to moose...@googlegroups.com, Stephen Thomas
Ok. I got the updates, checked if I was in master and ran make and tried again to get this error:

sthomas@sthomas:~/projects/moose/examples/ex01_inputfile$ peacock
Using Executable: /home/sthomas/projects/moose/examples/ex01_inputfile/ex01-opt
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: failed to load driver: vboxvideo
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Segmentation fault (core dumped)


Please note that I am running virtual box.

Stephen Thomas

unread,
Mar 20, 2014, 1:44:37 AM3/20/14
to moose...@googlegroups.com, Stephen Thomas

Yay! I disabled "3D acceleration" in Virtual Box and it worked! Thanks for the great support Derek!

Reply all
Reply to author
Forward
Message has been deleted
0 new messages