New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error messages when launching uvcdat on Rhea. #727

Closed
cameronsmith1 opened this Issue Oct 2, 2014 · 14 comments

Comments

Projects
None yet
6 participants
@cameronsmith1

cameronsmith1 commented Oct 2, 2014

~ (140) uvcdat --output=""
UVCDAT setup already sourced for this install location.
Init package:  edu.utah.sci.vistrails.basic ['Adelon', 'Arabic', 'AvantGarde', 'Chinese', 'Clarendon', 'Courier', 'Greek', 'Hebrew', 'Helvetica', 'Maths1', 'Maths2', 'Maths3', 'Maths4', 'Russian', 'Times', 'default'] Init package:  edu.utah.sci.vistrails.basic Init package:  edu.utah.sci.vistrails.pythoncalc Init package:  edu.utah.sci.vistrails.spreadsheet
Init package:  edu.utah.sci.vistrails.http Init package:  edu.utah.sci.vistrails.dialogs Init package:  gov.llnl.uvcdat Init package:  edu.utah.sci.vistrails.vtk Init package:  gov.llnl.uvcdat.cdms Init package:  gov.nasa.nccs.vtdv3d 'NoneType' object has no attribute 'var'
Matplotlib dependent features will be disabled.
PVClimate plots not loaded.
Error when loading package_config_file: /lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plots/PVClimate/registry.cfg No module named paraview.simple Traceback (most recent call last):
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 105, in load_plots
    helper = self.parse_helper_type_str(pkg_parser.get(p, 'helper'))
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 80, in parse_helper_type_str
    module = __import__(path, globals(), locals(), [klass_name])
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/pvclimate/pvclimate_pipeline_helper.py", line 25, in <module>
    from pvgenericcell import *
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/pvclimate/pvgenericcell.py", line 12, in <module>
    import paraview.simple as pvsp
ImportError: No module named paraview.simple VisIt plots not loaded.
Error when loading package_config_file: /lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plots/VisIt/registry.cfg No module named visit Traceback (most recent call last):
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 105, in load_plots
    helper = self.parse_helper_type_str(pkg_parser.get(p, 'helper'))
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 80, in parse_helper_type_str
    module = __import__(path, globals(), locals(), [klass_name])
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/VisIt/visit_pipeline_helper.py", line 23, in <module>
    import visitcell
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/VisIt/visitcell.py", line 23, in <module>
    import visit
ImportError: No module named visit
Matplotlib plots not loaded.
Error when loading package_config_file: /lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plots/Matplotlib/registry.cfg Installation of python package 'matplotlib' failed.
Traceback (most recent call last):
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/bundles/pyimport.py", line 70, in py_import
    result = _vanilla_import(module_name)
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/bundles/pyimport.py", line 60, in _vanilla_import
    return __import__(module_name, globals(), locals(), [])
ImportError: No module named matplotlib

Traceback (most recent call last):
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 105, in load_plots
    helper = self.parse_helper_type_str(pkg_parser.get(p, 'helper'))
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/uvcdat/plotmanager.py", line 80, in parse_helper_type_str
    module = __import__(path, globals(), locals(), [klass_name])
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/pylab/pipeline_helper.py", line 1, in <module>
    from init import CDMSData
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/packages/pylab/init.py", line 45, in <module>
    matplotlib = py_import('matplotlib', mpl_dict)
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/bundles/pyimport.py", line 80, in py_import
    raise PyImportException(module_name, traceback.format_exc())
PyImportException: Installation of python package 'matplotlib' failed.
Traceback (most recent call last):
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/bundles/pyimport.py", line 70, in py_import
    result = _vanilla_import(module_name)
  File "/lustre/atlas2/csc121/world-shared/uvcdat/2014-10-01/vistrails/vistrails/core/bundles/pyimport.py", line 60, in _vanilla_import
    return __import__(module_name, globals(), locals(), [])
ImportError: No module named matplotlib

None None
@cameronsmith1

This comment has been minimized.

cameronsmith1 commented Oct 2, 2014

I should have noted that uvcdat actually seemed to run fine in spite of these errors.

@williams13

This comment has been minimized.

Contributor

williams13 commented Oct 2, 2014

We should make sure that all erroneous errors and print statements are removed. Thanks for pointing this out.

From: cameronsmith1 <notifications@github.commailto:notifications@github.com>
Reply-To: UV-CDAT/uvcdat <reply@reply.github.commailto:reply@reply.github.com>
Date: Wednesday, October 1, 2014 6:22 PM
To: UV-CDAT/uvcdat <uvcdat@noreply.github.commailto:uvcdat@noreply.github.com>
Subject: Re: [uvcdat] Error messages when launching uvcdat on Rhea. (#727)

I should have noted that uvcdat actually seemed to run fine in spite of these errors.


Reply to this email directly or view it on GitHubhttps://github.com//issues/727#issuecomment-57567387.

@durack1

This comment has been minimized.

Member

durack1 commented Oct 2, 2014

@cameronsmith1 it would be useful to know what your environment variables look like as the UVCDAT setup already sourced for this install location. comment is sourced from the uvcdat_install_dir/bin/setup_runtime.csh/.sh and tangled environment variables have caused me a lot of grief in the past having multiple versions of python sourced concurrently..

Can you list the output using the following please, just to make sure it's not an issue:

> env | grep PATH
@aashish24

This comment has been minimized.

Contributor

aashish24 commented Oct 2, 2014

Looks like you have slightly old version of CDAT. What SHA you are building?

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 2, 2014

he is using yesterday morning build of UV-CDAT on rhea, you're right it's already 24 hours old ;)
@remram44 do you mind taking a shot at this it is probably very similar to the fix you did to remove these warnings from pop-up windows.

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 2, 2014

@durack1 he is sourcing the setup_runtime.csh so he can use the command line, but the "Executable" uvcdat resources it. I will post an issue to remind us from unsetting the vars before runnnig uvcdat so we're sure uvcdat GUI is using the correct python.

@aashish24

This comment has been minimized.

Contributor

aashish24 commented Oct 2, 2014

I see. I can confirm that these messages I am seeing as well (but in the uvcdatsession.log file)

@durack1

This comment has been minimized.

Member

durack1 commented Oct 2, 2014

@doutriaux1 I agree, unsetting these variables as part of the script would be a good idea.. So that such tangles don't occur at anytime.. Getting this unsetting to work across shells though is going to be a pain, as was the original *.csh edits..

@cameronsmith1

This comment has been minimized.

cameronsmith1 commented Oct 2, 2014

The commands I used (from Charles) were:
module unload python ompi paraview PE-intel PE-gnu
module load gcc
source /lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/bin/setup_runtime.csh
uvcdat --output=""

The version I used is 2.0.beta-2337-g32b4249.

The output of env | grep PATH is (after the commands above):

PATH=/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/bin:/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/Externals/bin:/ccs/compilers/gcc/rhel6-x86_64/4.8.2/bin:.:/ccs/home/pjcs/bin:/ccs/home/pjcs/CDAT/bin:/ccs/home/pjcs/xxdiff:/sw/redhat6/subversion/1.8.3/rhel6.4_gnu4.4.7/bin:/sw/rhea/netcdf/3.6.2/rhel6.4_intel13.1.3/bin:/sw/redhat6/hdf5/1.8.11/rhel6.4_intel13.1.3/bin:/usr/lib64/qt3.3/bin:/sw/rhea/bin:/sw/redhat6/lustredu/1.4/rhel6.5_gnu4.7.1/install/bin:/usr/local/bin:/bin:/usr/bin:/opt/ibutils/bin:/opt/public/bin:/usr/local/bin:/usr/bin/X11:/ccs/home/pjcs/gem/bin:/ccs/home/pjcs/gem/esm_tools/bin:/ccs/home/pjcs/gem/actm/impact/Other/scripts:/ccs/home/pjcs/bin:.
MODULEPATH=/sw/rhea/modulefiles:/sw/redhat6/modulefiles:/ccs/compilers/modulefiles/rhel6-x86_64:/usr/share/Modules/modulefiles
LD_LIBRARY_PATH=/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/lib:/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/Externals/lib:/ccs/compilers/gcc/rhel6-x86_64/4.8.2/lib64:/ccs/compilers/gcc/rhel6x86_64/4.8.2/lib:/sw/redhat6/serf/1.3.2/rhel6.4_gnu4.4.7/lib:/sw/redhat6/subversion/1.8.3/rhel6.4_gnu4.4.7/lib:/sw/rhea/netcdf/3.6.2/rhel6.4_intel13.1.3/lib:/sw/redhat6/hdf5/1.8.11/rhel6.4_intel13.1.3/lib:/sw/redhat6/szip/2.1/rhel6_intel13.1.3/lib
LIBRARY_PATH=/sw/rhea/netcdf/3.6.2/rhel6.4_intel13.1.3/lib:/sw/redhat6/hdf5/1.8.11/rhel6.4_intel13.1.3/lib
MANPATH=/ccs/compilers/gcc/rhel6-x86_64/4.8.2/share/man:/sw/redhat6/subversion/1.8.3/rhel6.4_gnu4.4.7/share/man:/sw/rhea/netcdf/3.6.2/rhel6.4_intel13.1.3/share/man:/sw/sources/hpss/man:/sw/rhea/man:/sw/redhat6/lustredu/1.4/rhel6.5_gnu4.7.1/install/man:/usr/share/man:/usr/share/man
HDF5_INCLUDE_PATH=-I/sw/redhat6/hdf5/1.8.11/rhel6.4_intel13.1.3/include
INCLUDE_PATH=/sw/rhea/netcdf/3.6.2/rhel6.4_intel13.1.3/include:/sw/redhat6/hdf5/1.8.11/rhel6.4_intel13.1.3/include
PYTHONPATH=/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/lib/python2.7/site-packages:/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01/Externals/lib/python2.7/site-packages:
UVCDAT_SETUP_PATH=/lustre/atlas/world-shared/csc121/uvcdat/2014-10-01
@durack1

This comment has been minimized.

Member

durack1 commented Oct 2, 2014

@doutriaux1 I will clarify my badly made point above. It would be good if the setup scripts checked for existing python/uvcdat paths, and removed other installations.. I agree this would be painful to do, but would also attempt to resolve issues with tangled paths causing users problems in which no coherent error message will easily be able to explain (and consequently the user complains to you about it not working).

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 2, 2014

@durack1 please state this in the correct issue #730 thx

@remram44

This comment has been minimized.

Contributor

remram44 commented Oct 6, 2014

Other than the environment issues, is there a problem with VisTrails's output here? It seems that these messages popping up is the correct behavior here (when using --output="").

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 7, 2014

moving to 2.1

@doutriaux1 doutriaux1 modified the milestones: 2.1, 2.0.0 Oct 7, 2014

@doutriaux1

This comment has been minimized.

Member

doutriaux1 commented Oct 15, 2014

kind of agree with @remram44 print statement should probably be there when using --output="" closing for now.

@doutriaux1 doutriaux1 closed this Oct 15, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment