Peacock Segmentation Fault: 11 for all Examples
645 views
Skip to first unread message
Sterling Butters
Dec 3, 2017, 1:13:14 AM12/3/17
to moose-users
I am new to Moose and I am trying to get Peacock working. I have tried "make clobber" for this segmentation fault which did not work so I'm not sure what to try next. Any help is appreciated, thanks!
Wesley
Dec 3, 2017, 11:12:23 PM12/3/17
to moose-users
I follow (http://mooseframework.org/wiki/Peacock/) and I can run.
Miller, Jason M
Dec 4, 2017, 9:24:07 AM12/4/17
to moose...@googlegroups.com
Unfortunately the moose-environment package was updated but the specific instructions for running Peacock _with_ this new package was not. Quick fix:
execute:
moose/python/peacock/peacock
instead of:
moose/gui/peacock
The change to the moose-environment package consisted of a major upgrade to the VTK libraries (from 6.x to 7.x). A change which unfortunately merits two different versions of our moose GUI.
Folks still wanting to use the older version of peacock can, so long as they load the older VTK environment by performing the following:
module switch miniconda miniconda-old
(assuming the user is not doing anything special in their bash_profile)
Apologies that this is not listed _anywhere_ in our instructions. We will be fixing that today!
Cheers,
Jason
On Sat, Dec 2, 2017 at 11:13 PM, Sterling Butters <sterlin...@gmail.com> wrote:
I am new to Moose and I am trying to get Peacock working. I have tried "make clobber" for this segmentation fault which did not work so I'm not sure what to try next. Any help is appreciated, thanks!
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/cb1055da-a57e-478d-85b4-92378236e69d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sterling Butters
Dec 6, 2017, 12:45:45 AM12/6/17
to moose-users
@jason.miller
Executing
moose/python/peacock/peacock (1)
instead of
moose/gui/peacock (2)
yields same segmentation fault. However, navigating to directory (1) and executing peacock as such:
./peacock
I get the following error:
Error starting peacock: Could not import Qt5
You need to use the miniconda-dev module.
If you already have miniconda loaded you can run:
module switch miniconda miniconda-dev
I thought that since the python environment was running Python 2.7, Qt4 was required?
Anyway, following the suggestion yields the following:
ModuleCmd_Switch.c(215):ERROR:105: Unable to locate a
modulefile for 'miniconda-dev'
Running peacock in directory (2) via "./peacock" and "peacock" both yield segmentation faults. Any idea what the problem is? Im not sure I can simply pip install Qt5 as I was under the impressible this was incompatible with Python 2.7 as stated previously.
All help is appreciated, thanks
Miller, Jason M
Dec 6, 2017, 8:58:16 AM12/6/17
to moose...@googlegroups.com
Well, Qt5 comes with our moose-environment package, so no need to have you install it yourself. More accurately, the moose-environment comes with everything you need to run Peacock 1 and 2 (donno if we are calling it 1 or 2... old and new?) Anyways...
This error 'Error starting peacock' for peacock (2) needs to be updated. It is telling you to load a module I no longer make. The error should go to mention miniconda-old and not miniconda-dev.
Can you verify the version of the moose-environment package you have? I am sure its the latest, I just want to be 100% on that:
cat /opt/moose/build
This is all starting to look like some other environment is getting in our way (like MacPorts, Fink, Homebrew, etc). Can you perform the following three commands and report back the results of each:
module list
which python
env
Cheers!
Jason
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/1b983995-d1e0-490c-ac1e-f4ed5e814d90%40googlegroups.com.
Sterling Butters
Dec 6, 2017, 12:12:47 PM12/6/17
to moose-users
Please see outputs below:
Sterlings-MacBook-Pro:~ sterlingbutters$ cat /opt/moose/build
Package version: 9
Sterlings-MacBook-Pro:~ sterlingbutters$ module list
Currently Loaded Modulefiles:
1) moose/.gcc-7.2.0
2) moose/.clang-5.0.0
3) moose/.mpich-3.2_clang-5.0.0
4) moose/.petsc-3.7.6_mpich-3.2_clang-5.0.0-opt
5) moose/.tbb44_20150728
6) moose/.cppunit-1.12.1_clang-5.0.0
7) moose-dev-clang
8) miniconda
9) moose-tools
Sterlings-MacBook-Pro:~ sterlingbutters$ which python
/opt/moose/miniconda/bin/python
Sterlings-MacBook-Pro:~ sterlingbutters$ env
GCC_MAN=/opt/moose/gcc-7.2.0/share/man
CPLUS_INCLUDE_PATH=/opt/moose/mpich-3.2/clang-5.0.0/include
MODULE_VERSION_STACK=3.2.10
MANPATH=/opt/moose/gnuplot-4.6.5/share/man:/opt/moose/lcov-1.11/usr/share/man:/opt/moose/graphviz-2.38.0/share/man:/opt/moose/doxygen-1.8.11/man:/opt/moose/seacas/share/man:/opt/moose/mpich-3.2/clang-5.0.0/share/man:/opt/moose/gcc-7.2.0/share/man:/usr/share/man
TERM_PROGRAM=iTerm.app
ACCESS=/opt/moose/seacas
TERM=xterm-256color
SHELL=/bin/bash
TMPDIR=/var/folders/cc/vlcxq8t966z80gs3t2pjv0t80000gn/T/
LIBRARY_PATH=/opt/moose/llvm-5.0.0/lib
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.dERnPajeTp/Render
TERM_PROGRAM_VERSION=3.1.5
FPATH=/opt/moose/mpich-3.2/clang-5.0.0/include
TBB_DIR=/opt/moose/tbb44_20150728
MOOSE_CLANG_LIB=/opt/moose/llvm-5.0.0/lib
TERM_SESSION_ID=w0t0p0:5F3EF8BC-B5D7-4E0C-B14A-77B727F6EE0B
USER=sterlingbutters
MOOSE_JOBS=8
CPATH=/opt/moose/tbb44_20150728/include
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.jzwSDhAjBi/Listeners
__CF_USER_TEXT_ENCODING=0x0:0:0
LIBRARY=/opt/moose/tbb44_20150728/lib
MODULE_VERSION=3.2.10
PATH=/opt/moose/miniconda/bin:/opt/moose/gnuplot-4.6.5/bin:/opt/moose/lcov-1.11/usr/bin:/opt/moose/graphviz-2.38.0/bin:/opt/moose/doxygen-1.8.11/bin:/opt/moose/glib-2.47.92/bin:/opt/moose/pkg-config-0.29.1/bin:/opt/moose/seacas/bin:/seacas/etc:/opt/moose/cppunit-1.12.1/clang-5.0.0/bin:/opt/moose/mpich-3.2/clang-5.0.0/bin:/opt/moose/llvm-5.0.0/bin:/opt/moose/gcc-7.2.0/bin:/Users/sterlingbutters/anaconda3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/usr/local/share/dotnet:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/usr/local/bin:/Users/sterlingbutters/MooseProjects/moose/gui
GCC_BIN=/opt/moose/gcc-7.2.0/bin
TBBROOT=/opt/moose/tbb44_20150728
C_INCLUDE_PATH=/opt/moose/mpich-3.2/clang-5.0.0/include
F90=mpif90
PWD=/Users/sterlingbutters
_LMFILES_=/opt/moose/Modules/3.2.10/modulefiles/moose/.gcc-7.2.0:/opt/moose/Modules/3.2.10/modulefiles/moose/.clang-5.0.0:/opt/moose/Modules/3.2.10/modulefiles/moose/.mpich-3.2_clang-5.0.0:/opt/moose/Modules/3.2.10/modulefiles/moose/.petsc-3.7.6_mpich-3.2_clang-5.0.0-opt:/opt/moose/Modules/3.2.10/modulefiles/moose/.tbb44_20150728:/opt/moose/Modules/3.2.10/modulefiles/moose/.cppunit-1.12.1_clang-5.0.0:/opt/moose/Modules/3.2.10/modulefiles/moose-dev-clang:/opt/moose/Modules/3.2.10/modulefiles/miniconda:/opt/moose/Modules/3.2.10/modulefiles/moose-tools
MPLBACKEND=qt5Agg
LANG=en_US.UTF-8
MODULEPATH=/opt/moose/Modules/versions:/opt/moose/Modules/$MODULE_VERSION/modulefiles:/opt/moose/Modules/modulefiles
ITERM_PROFILE=Default
LOADEDMODULES=moose/.gcc-7.2.0:moose/.clang-5.0.0:moose/.mpich-3.2_clang-5.0.0:moose/.petsc-3.7.6_mpich-3.2_clang-5.0.0-opt:moose/.tbb44_20150728:moose/.cppunit-1.12.1_clang-5.0.0:moose-dev-clang:miniconda:moose-tools
XPC_FLAGS=0x0
F77=mpif77
CXX=mpicxx
XPC_SERVICE_NAME=0
SHLVL=1
HOME=/Users/sterlingbutters
COLORFGBG=7;0
GCC_LIB=/opt/moose/gcc-7.2.0/lib:/opt/moose/gcc-7.2.0/lib/i386
FC=mpif90
CPPUNIT_DIR=/opt/moose/cppunit-1.12.1/clang-5.0.0
ITERM_SESSION_ID=w0t0p0:5F3EF8BC-B5D7-4E0C-B14A-77B727F6EE0B
PYTHONPATH=/opt/moose/llvm-5.0.0/bindings/python:/Users/sterlingbutters/anaconda3/bin/python:
LOGNAME=sterlingbutters
MPI_HOME=/opt/moose/mpich-3.2/clang-5.0.0
MODULESHOME=/opt/moose/Modules/3.2.10
PKG_CONFIG_PATH=/opt/moose/pkg-config-0.29.1/pkgconfig
CC=mpicc
DISPLAY=/private/tmp/com.apple.launchd.wK0M8wNWjq/org.macosforge.xquartz:0
INCLUDE=/opt/moose/cppunit-1.12.1/clang-5.0.0/include
MOOSE_PPS_WIDTH=180
PETSC_DIR=/opt/moose/petsc-3.7.6/mpich-3.2_clang-5.0.0-opt
COLORTERM=truecolor
BASH_FUNC_module%%=() { eval `/opt/moose/Modules/$MODULE_VERSION/bin/modulecmd bash $*`
}
_=/usr/bin/env
I guess it is worth mentioning that I have both Homebrew and Anaconda, below:
Sterlings-MacBook-Pro:~ sterlingbutters$ which brew
/usr/local/bin/brew
Sterlings-MacBook-Pro:~ sterlingbutters$ which -a python
/opt/moose/miniconda/bin/python
/Users/sterlingbutters/anaconda3/bin/python
/usr/bin/python
Let me know if this helps, thanks!
Message has been deleted
Miller, Jason M
Dec 6, 2017, 12:49:58 PM12/6/17
to moose...@googlegroups.com
Looks like the _older_ miniconda (miniconda-old) is not set up correctly in the package:
[milljm][~/projects/moose/test]> module list
No Modulefiles Currently Loaded.
[milljm][~/projects/moose/test]> module load moose-dev-clang moose-tools
[milljm][~/projects/moose/test]> module list
Currently Loaded Modulefiles:
1) moose/.gcc-7.2.0 4) moose/.petsc-3.7.6_mpich-3.2_clang-5.0.0-opt 7) moose-dev-clang
2) moose/.clang-5.0.0 5) moose/.tbb44_20150728 8) miniconda
3) moose/.mpich-3.2_clang-5.0.0 6) moose/.cppunit-1.12.1_clang-5.0.0 9) moose-tools
[milljm][~/projects/moose/test]> ../gui/peacock
Traceback (most recent call last):
File "../gui/peacock", line 12, in <module>
raise ImportError("Cannot load either PyQt or PySide")
ImportError: Cannot load either PyQt or PySide
[milljm][~/projects/moose/test]> module switch miniconda miniconda-old
[milljm][~/projects/moose/test]> ../gui/peacock
Traceback (most recent call last):
File "../gui/peacock", line 12, in <module>
raise ImportError("Cannot load either PyQt or PySide")
ImportError: Cannot load either PyQt or PySide
[milljm][~/projects/moose/test]> conda list | grep -i "pyq\|side"
[milljm][~/projects/moose/test]>
Somehow, this iteration of the package failed to install PyQT or PySide for the older miniconda module. Sorry, my fault. uggh.....
That bit about the PYTHONPATH could be the culprit I suppose (if `/Users/sterlingbutters/anaconda3/bin/python` is actually a directory and not the python binary). Its odd that it seems to be pointing to a python binary, and not a `site-packages` directory or something. Can you modify that path and give it a shot?
export PYTHONPATH=/opt/moose/llvm-5.0.0/bindings/python
Also... can you remove the bit about your PATH pointing to the old peacock?
PATH=/opt/moose/miniconda/bin:/opt/moose/gnuplot-4.6.5/bin:/opt/moose/lcov-1.11/usr/bin:/opt/moose/graphviz-2.38.0/bin:/opt/moose/doxygen-1.8.11/bin:/opt/moose/glib-2.47.92/bin:/opt/moose/pkg-config-0.29.1/bin:/opt/moose/seacas/bin:/seacas/etc:/opt/moose/cppunit-1.12.1/clang-5.0.0/bin:/opt/moose/mpich-3.2/clang-5.0.0/bin:/opt/moose/llvm-5.0.0/bin:/opt/moose/gcc-7.2.0/bin:/Users/sterlingbutters/anaconda3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/usr/local/share/dotnet:/opt/X11/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/usr/local/bin:/Users/sterlingbutters/MooseProjects/moose/gui
Once those two changes have been made, try to running the newer peacock again...
On Wed, Dec 6, 2017 at 10:14 AM, Sterling Butters <sterlin...@gmail.com> wrote:
PYTHONPATH variable is the only potential conflict I see since multiple are listed but I am only guessing.
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/fddb3cbc-fde3-474d-a707-379727541dbb%40googlegroups.com.
Sterling Butters
Dec 6, 2017, 3:05:59 PM12/6/17
to moose-users
Jason,
I was previously getting the error you mentioned:
ImportError: Cannot load either PyQt or PySide
And I assume I was able to install PyQt on my own to this miniconda environment which is why this error message went away.
I exported the PYTHONPATH as you specified.
I REMOVED the old peacock filepath from my PATH. Should I REPLACE it with the filepath for new peacock as well?
PYTHONPATH output running "env" supplies:
PYTHONPATH=/opt/moose/llvm-5.0.0/bindings/python
as it should
Running the new peacock at moose/python/peacock/peacock
I still get the following:
Error starting peacock: Could not import Qt5
You need to use the miniconda-dev module.
If you already have miniconda loaded you can run:
module switch miniconda miniconda-dev
... Now that I am sure I am not working on this alone, perhaps it might be of use to do a clean build or update my copy of moose (assuming you have fixed the issue you found on your end)?:
cd ~/projects/moose git fetch origin git rebase origin/master
Thanks!
Miller, Jason M
Dec 6, 2017, 3:29:52 PM12/6/17
to moose...@googlegroups.com
No Qt5 ... Ok, lets verify that that it is indeed there, and if its not... we will investigate that direction. Can you perform the following (pasting exactly what I did, and its results for clarity):
[milljm][~]> which python
/usr/bin/python
[milljm][~]> module load moose-dev-clang moose-tools
[milljm][~]> which python
/opt/moose/miniconda/bin/python
[milljm][~]> python
Python 2.7.14 |Anaconda, Inc.| (default, Nov 8 2017, 16:45:25)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import PyQt5
>>> PyQt5.__file__
'/opt/moose/miniconda/lib/python2.7/site-packages/PyQt5/__init__.pyc'
>>>
I bolded the things that I typed...
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/fc732859-9a23-464f-b9f4-0f6067dabd77%40googlegroups.com.
Alger, Brian K
Dec 6, 2017, 3:32:14 PM12/6/17
to moose...@googlegroups.com
Oh, and, what does:
module load minicondaTo view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/CALgZTAfdnPCV6HXYfr6D9T_HaZ27%2B_O%2BuQO0WXFwey%3DQ%2BOAJpw%40mail.gmail.com.
Miller, Jason M
Dec 6, 2017, 3:37:30 PM12/6/17
to moose...@googlegroups.com
Oh and, this issue has nothing to do with your clone of the moose repo... so no need to rebase/clobber (not yet anyway!)
On Wed, Dec 6, 2017 at 1:29 PM, Miller, Jason M <jason....@inl.gov> wrote:
Sterling Butters
Dec 6, 2017, 5:36:28 PM12/6/17
to moose-users
@Jason
Sterlings-MacBook-Pro:~ sterlingbutters$ which python
/opt/moose/miniconda/bin/python
Sterlings-MacBook-Pro:~ sterlingbutters$ module load moose-dev-clang moose-tools
Sterlings-MacBook-Pro:~ sterlingbutters$ which python
/opt/moose/miniconda/bin/python
Sterlings-MacBook-Pro:~ sterlingbutters$ python
Python 2.7.14 |Anaconda, Inc.| (default, Nov 8 2017, 16:45:25)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import PyQt5
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named PyQt5
@Brian
Sterlings-MacBook-Pro:~ sterlingbutters$ module load miniconda
Sterlings-MacBook-Pro:~ sterlingbutters$ conda list
# packages in environment at /opt/moose/miniconda:
#
anytree 2.4.2 <pip>
astroid 1.4.9 <pip>
backports 1.0 py27hb4f9756_1
backports.functools_lru_cache 1.4 py27h2aca819_1
backports_abc 0.5 py27h6972548_0
beautifulsoup4 4.6.0 py27h9416283_1
bokeh 0.12.11 py27hb6705db_0
bs4 0.0.1 <pip>
ca-certificates 2017.08.26 ha1e5d58_0
certifi 2017.11.5 py27hfa9a1c4_0
cffi 1.9.1 py27_0
chardet 3.0.4 py27h2842e91_1
click 6.7 py27h2b86a94_0
cloudpickle 0.5.2 py27he962bb2_0
conda 4.3.29 py27_0 conda-forge
conda-build 3.0.30 py27h7e7b905_0
conda-env 2.6.0 0 conda-forge
conda-verify 2.0.0 py27hbebe81d_0
configparser 3.5.0 <pip>
contextlib2 0.5.5 py27h9cb85f4_0
coverage 4.4.2 py27hf37a882_0
cryptography 1.7.1 py27_0
cycler 0.10.0 py27hfc73c78_0
DaemonLite 0.0.2 <pip>
dask 0.16.0 py27h0cfea73_0
dask-core 0.16.0 py27h3e6bc05_0
dbus 1.10.22 h50d9ad6_0
decorator 4.1.2 py27h9f877ea_0
distributed 1.20.1 py27h2350da2_0
enum34 1.1.6 py27_0
expat 2.2.5 hb8e80ba_0
filelock 2.0.13 py27h2c227fa_0
freetype 2.8 h12048fb_1
funcsigs 1.0.2 py27hb9f6266_0
functools32 3.2.3.2 py27h8ceab06_1
futures 3.1.1 py27hb02a37a_0
gettext 0.19.8.1 h15daf44_3
glib 2.53.6 h33f6a65_2
glob2 0.6 py27h55c9705_0
google-api-python-client 1.6.4 <pip>
h5py 2.7.1 py27h75626f5_0
hdf5 1.10.1 ha036c08_1
heapdict 1.0.0 py27hb5e74ad_0
httplib2 0.10.3 <pip>
icu 58.2 h4b95b61_1
idna 2.6 py27hedea723_1
imageio 2.2.0 py27h37746d9_0
intel-openmp 2018.0.0 h8158457_8
ipaddress 1.0.18 py27_0
isort 4.2.15 <pip>
jinja2 2.9.6 py27h92590e2_1
jpeg 9b he5867d9_2
latexcodec 1.0.5 <pip>
lazy-object-proxy 1.3.1 <pip>
libcxx 4.0.1 h579ed51_0
libcxxabi 4.0.1 hebd6815_0
libedit 3.1 hb4e282d_0
libffi 3.2.1 h475c297_4
libgfortran 3.0.1 h93005f0_2
libiconv 1.15 hdd342a3_7
libpng 1.6.32 hd1e8b91_4
libtiff 4.0.9 h0dac147_0
libxml2 2.9.4 hf05c021_6
libxslt 1.1.29 hc208041_6
livereload 2.5.1 <pip>
locket 0.2.0 py27ha10513d_1
lxml 4.1.1 py27ha46c8db_0
mako 1.0.7 py27h07f8f8b_0
Markdown 2.6.9 <pip>
markupsafe 1.0 py27hd3c86fa_1
matplotlib 2.1.0 py27h3078195_0
mccabe 0.6.1 <pip>
mkl 2018.0.1 hfbd8650_4
mock 2.0.0 py27h300204c_0
msgpack-python 0.4.8 py27h635ded4_0
ncurses 6.0 hd04f020_2
networkx 1.11 py27h0a72f81_0
numpy 1.13.3 py27h62f9060_0
oauth2client 4.1.2 <pip>
olefile 0.44 py27h73ba740_0
openssl 1.0.2m h86d3e6a_1
pandas 0.21.0 py27h860f240_1
partd 0.3.8 py27h7560dbf_0
pbr 3.1.1 py27h45d16fa_0
pcre 8.41 hfb6ab37_1
pillow 4.2.1 py27h2cf1d5f_0
pip 9.0.1 py27h1567d89_4
pkginfo 1.4.1 py27ha9221e7_0
psutil 5.4.1 py27h533f8c4_0
pyasn1 0.4.2 <pip>
pyasn1 0.1.9 py27_0
pyasn1-modules 0.2.1 <pip>
pybtex 0.21 <pip>
pycosat 0.6.1 py27_1
pycparser 2.17 py27_0
pyflakes 1.6.0 py27h4446e76_0
pylatexenc 1.2 <pip>
pylint 1.6.5 <pip>
pyopenssl 16.2.0 py27_0
pyparsing 2.2.0 py27h5bb6aaf_0
pyqt 4.11.4 py27_2 conda-forge
PySide 1.2.2 <pip>
pysocks 1.6.7 py27h1cff6a6_1
python 2.7.14 h001abdc_23
python-dateutil 2.6.1 py27hd56c96b_1
python-markdown-math 0.3 <pip>
pytz 2017.3 py27h803c07a_0
pywavelets 0.5.2 py27hd99e88a_0
pyyaml 3.12 py27ha7932d0_1
qt 4.8.7 4
readline 7.0 hc1231fa_4
reportlab 3.4.0 py27_0
requests 2.18.4 py27h9b2b37c_1
rsa 3.4.2 <pip>
ruamel_yaml 0.11.14 py27h31666c4_2
scikit-image 0.13.1 py27ha753da8_0
scikit-learn 0.19.1 py27h9788993_0
scipy 1.0.0 py27h793f721_0
setuptools 27.2.0 py27_0
singledispatch 3.4.0.3 py27he22c18d_0
sip 4.18 py27_0 idaholab
six 1.10.0 py27_0
six 1.11.0 <pip>
sortedcontainers 1.5.7 py27h322dbbf_0
sqlite 3.20.1 h7e4c145_2
ssl_match_hostname 3.5.0.1 py27h8780752_2
subprocess32 3.2.7 py27h24b2887_0
tblib 1.3.2 py27ha684fc4_0
tk 8.6.7 h35a86e2_3
toolz 0.8.2 py27h27228c4_0
tornado 4.5.2 py27h29aec9e_0
uritemplate 3.0.0 <pip>
urllib3 1.22 py27hc3787e9_0
vtk 7.1.0 1 idaholab
wheel 0.29.0 py27_0
wrapt 1.10.11 <pip>
xz 5.2.3 h0278029_2
yaml 0.1.7 hc338f04_2
zict 0.1.3 py27h5fff8b1_0
zlib 1.2.11 hf3cbc9b_2
I want to say that I was the one that installed PySide and pyqt (post moose-installation) although I dont think PySide installed correctly and I can't remember what happened with pyqt. But, this confirms PyQt running version 4 not 5.
Alger, Brian K
Dec 6, 2017, 5:53:46 PM12/6/17
to moose...@googlegroups.com
OK. The original miniconda module had Qt 5 and pyqt 5 which is what the new peacock needs.
I would reinstall the moose environment package and try running moose/python/peacock/peacock with the miniconda module loaded.--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/9dac35d4-c863-405d-9907-9c7fdfe111c5%40googlegroups.com.
Sterling Butters
Dec 7, 2017, 2:28:06 AM12/7/17
to moose-users
This should accomplish that, correct?:
Miller, Jason M
Dec 7, 2017, 9:25:40 AM12/7/17
to moose...@googlegroups.com
We want you to reinstall this guy: moose-environment-9_highsierra-10.13_x86_64.pkg. That will 'reset' anything sitting in /opt/moose
What you are suggesting would update your local repository 'moose' which contains the framework source code, to the latest available hash against the master branch on origin (assuming there are no untracked files needing to be committed 'saved' first). Its completely different, but equally important down the road.
Because you have two python package environments (miniconda provided by the moose-environment package, and anaconda provided by you), my advice is to perform a `module purge`, thus switching back to your anaconda environment. In which case installing additional python packages will not affect the moose-environment. Please keep in mind, that `module purge` and `module load` are temporary adjustments to your environment. They go away, as soon as you close or open a terminal. The way we have things being applied when one installs the moose-environment package, is to automatically load the moose-dev-clang and moose-tools modules upon terminal startup. I'd be happy to discus how to modify this behavior if you want.
Thanks!
Jason
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/3131c3f8-325f-4362-a84c-915ca4568289%40googlegroups.com.
Sterling Butters
Dec 7, 2017, 1:42:48 PM12/7/17
to moose-users
@Brian && @Jason
Alright!!! It is working now. Thank you guys so much for your help!!
If I may be so bold as to make a suggestion regarding future peacock development:
I am not well versed in the Moose Framework or the package I am about to suggest, but Dash by Plotly (https://plot.ly/products/dash/) looks like an amazing tool that could be used as an interface for peacock with a fully pythonic backend. Let me know if this appeals to you as I, myself, have been very impressed with Plotly and their very active development and data visualization tools.
Thank you again so much for all your help!
Slaughter, Andrew E
Dec 7, 2017, 6:38:27 PM12/7/17
to moose...@googlegroups.com
Thanks for the tip, plotly is a great product, we will be using it for our website soon but not for peacock. The main purpose of peacock is to provide volume rendering of the finite element mesh, which plotly cannot handle, we use VTK. For the line plots we use matplotlib which is ubiquitous within the scientific community.
Thank you again so much for all your help!
--
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+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/moose-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/moose-users/47aa2972-c996-4a28-b837-394371dcbb89%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages