Skip to content
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

vistrails module uvcdat_cdms missing #581

Closed
doutriaux1 opened this issue Aug 28, 2014 · 25 comments
Closed

vistrails module uvcdat_cdms missing #581

doutriaux1 opened this issue Aug 28, 2014 · 25 comments
Assignees
Milestone

Comments

@doutriaux1
Copy link
Contributor

Jim's UVCDAT GUI fils loading in a variable

Going back commit after commit, we found that the breaking point was introduced between the follwing 2 commits. I guess @ThomasMaxwell you need to look into this.


commit 03624da5ff3c03cf6d0128de0ffd331266d10b98
Author: Thomas Maxwell <thomas.maxwell@nasa.gov>
Date:   Mon Aug 18 18:02:02 2014 -0400

    Parameter fixes

commit 5e6ac22be23c7bbf360b16676f8eb6da83d1ea30
Merge: b4dceec 0f17b6b
Author: Thomas Maxwell <thomas.maxwell@nasa.gov>
Date:   Mon Aug 18 16:32:08 2014 -0400
@ThomasMaxwell
Copy link
Contributor

I'll need more info on this issue. I've been using uvcdat-next and I don't see any problems with loading variables.

-- Tom

From: Charles <notifications@github.commailto:notifications@github.com>
Reply-To: UV-CDAT/uvcdat <reply@reply.github.commailto:reply@reply.github.com>
Date: Thursday, August 28, 2014 4:59 PM
To: UV-CDAT/uvcdat <uvcdat@noreply.github.commailto:uvcdat@noreply.github.com>
Cc: "Maxwell, Thomas P. (GSFC-606.2)[SCIENCE APPLICATIONS INTL CORP]" <thomas.maxwell@nasa.govmailto:thomas.maxwell@nasa.gov>
Subject: [uvcdat] vistrails module uvcdat_cdms missing (#581)

Jim's UVCDAT GUI fils loading in a variable

Going back commit after commit, we found that the breaking point was introduced between the follwing 2 commits. I guess @ThomasMaxwellhttps://github.com/ThomasMaxwell you need to look into this.

commit 03624da
Author: Thomas Maxwell <thomas.maxwell@nasa.govmailto:thomas.maxwell@nasa.gov>
Date: Mon Aug 18 18:02:02 2014 -0400

Parameter fixes

commit 5e6ac22be23c7bbf360b16676f8eb6da83d1ea30
Merge: b4dceec 0f17b6b
Author: Thomas Maxwell <thomas.maxwell@nasa.govmailto:thomas.maxwell@nasa.gov>
Date: Mon Aug 18 16:32:08 2014 -0400


Reply to this email directly or view it on GitHubhttps://github.com//issues/581.

@doutriaux1
Copy link
Contributor Author

I now get this as well....
here's the rror message:

Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/gui/uvcdat/variable.py", line 594, in defineVarCloseClicked
    self.getUpdatedVarCheck()
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/gui/uvcdat/variable.py", line 630, in getUpdatedVarCheck
    self.getUpdatedVar(tid)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/gui/uvcdat/variable.py", line 729, in getUpdatedVar
    updatedVar = controller.create_exec_new_variable_pipeline(targetId)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/gui/uvcdat/project_controller.py", line 1185, in create_exec_new_variable_pipeline
    self.get_var_module(targetId, dummyCell, CDMSPipelineHelper)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/gui/uvcdat/project_controller.py", line 925, in get_var_module
    module = var.to_module(self.vt_controller)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/uvcdat_cdms/init.py", line 144, in to_module
    module = Variable.to_module(self, controller, identifier)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/uvcdat/init.py", line 57, in to_module
    reg.get_descriptor_by_name(pkg_identifier, self.__class__.__name__))
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/modules/module_registry.py", line 745, in get_descriptor_by_name
    raise MissingPackage(identifier)
MissingPackage: Missing package: gov.llnl.uvcdat.cdms

@doutriaux1
Copy link
Contributor Author

and going back to your sha1 does not solve the issue.... No idea what is going on here....

@aashish24
Copy link
Contributor

I am not able to re-create this problem on my end

@aashish24
Copy link
Contributor

may be you want to send the .uvcdat folder to @dakoop

@doutriaux1
Copy link
Contributor Author

I think I'm onto something:
in vistrails/gui/application.py
i see:

        # BAB only load certain packages if requirements are met
        pkgs = [
            'uvcdat',
            'uvcdat_cdms'
        ]

        from packages.ParaView import package_requirements as paraview_requirements
        try:
            paraview_requirements()
            pkgs.append('ParaView')
            pkgs.append('pvclimate')
            pkgs.append('vtk')
#            pkgs.append('vtDV3D')
            pkgs.append('vis_analytics')
            pkgs.append('scikit_learn')
        except Exception:
            pass

        from packages.VisIt.info import package_requirements as visit_requirements
        try:
            visit_requirements()
            pkgs.append('VisIt')
        except Exception:
            pass
        self.vistrailsStartup.init()

essentially pkgs is never used. that's probably why.
@dakoop @remram44 do you know what's going on here? If I uncomment

#        self.vistrailsStartup.set_needed_packages(pkgs)

then it complians there's no such function.

Thanks for pointers.

@aashish24
Copy link
Contributor

I believe this code is not there in uvcdat-master. Make sure you are using the current vistails uvcdat-master.

@remram44
Copy link
Contributor

remram44 commented Sep 2, 2014

I removed that in 174d1ea5 for #520, I'm not sure where you're seeing this.

@doutriaux1
Copy link
Contributor Author

@aashish24 I don't think it has to do with .uvcdat. I removed it and it still does that. BUT when launching uvcdatI don't see the bits that says init uvcdaT_cdms (I think i used to):

doutriaux1@sofia:[/lgm/uvcdat/2014-09-02-devel/vistrails]:[1832]> uvcdat --output=""
UVCDAT setup already sourced for this install location.
Init package:  edu.utah.sci.vistrails.basic
ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b3f70870): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b6188b60): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

Adding VCS element: 3d_vector default 
ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b62b7e90): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b63cf7b0): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

Adding VCS element: 3d_scalar default 
ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b6501df0): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b61bc040): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

Adding VCS element: 3d_scalar xyt 
ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b64dd2a0): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b6376d90): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b620fdd0): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b3e98d90): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b67c8150): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b68dfa80): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b3edd350): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

ERROR: In /Users/doutriaux1/build_devel/build/VTK/IO/Image/vtkJPEGReader.cxx, line 142
vtkJPEGReader (0x7f97b3da3e10): Unable to open file /lgm/uvcdat/2014-09-02-devel/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/DV3D/data/buttons/BasemapOpacity.jpeg

2014-09-02 14:08:38.058 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
2014-09-02 14:08:38.058 Python[10292:d07] CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
2014-09-02 14:08:38.110 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
2014-09-02 14:08:38.203 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
FOR NOW STILL READING IN OLD WAY
FOR NOW STILL READING IN OLD WAY
2014-09-02 14:08:39.228 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
['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
2014-09-02 14:08:45.410 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
Init package:  edu.utah.sci.vistrails.http
Init package:  edu.utah.sci.vistrails.dialogs
Init package:  edu.utah.sci.vistrails.vtk
Generic Warning: In /Users/doutriaux1/build_devel/build/VTK/Rendering/OpenGL/vtkOpenGLPolyDataMapper.cxx, line 69
vtkOpenGLPolyDataMapper::vtkOpenGLPolyDataMapper was deprecated for VTK 6.2 and will be removed in a future version.

Warning: In /Users/doutriaux1/build_devel/build/VTK/Common/Math/vtkFastNumericConversion.cxx, line 60
vtkFastNumericConversion (0x7f97b3a71a40): Class vtkFastNumericConversion was depecated for VTK 6.0 and will be removed in a future version.

Generic Warning: In /Users/doutriaux1/build_devel/build/VTK/Rendering/OpenGL/vtkOpenGLPolyDataMapper.cxx, line 69
vtkOpenGLPolyDataMapper::vtkOpenGLPolyDataMapper was deprecated for VTK 6.2 and will be removed in a future version.

PVClimate plots not loaded.
Error when loading package_config_file: /lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plots/PVClimate/registry.cfg No module named paraview.simple
Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plotmanager.py", line 105, in load_plots
    helper = self.parse_helper_type_str(pkg_parser.get(p, 'helper'))
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plotmanager.py", line 80, in parse_helper_type_str
    module = __import__(path, globals(), locals(), [klass_name])
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/pvclimate/pvclimate_pipeline_helper.py", line 25, in <module>
    from pvgenericcell import *
  File "/lgm/uvcdat/2014-09-02-devel/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: /lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plots/VisIt/registry.cfg No module named visit
Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plotmanager.py", line 105, in load_plots
    helper = self.parse_helper_type_str(pkg_parser.get(p, 'helper'))
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/uvcdat/plotmanager.py", line 80, in parse_helper_type_str
    module = __import__(path, globals(), locals(), [klass_name])
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/VisIt/visit_pipeline_helper.py", line 23, in <module>
    import visitcell
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/VisIt/visitcell.py", line 23, in <module>
    import visit
ImportError: No module named visit
2014-09-02 14:08:51,758 CRITICAL:
/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/pylab/init.py, line 53
Exception: Installation of python package 'matplotlib' failed.
Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 70, in py_import
    result = _vanilla_import(module_name)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 60, in _vanilla_import
    return __import__(module_name, globals(), locals(), [])
ImportError: No module named matplotlib

2014-09-02 14:08:51,758 CRITICAL:
/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/pylab/init.py, line 53
Exception: Installation of python package 'matplotlib' failed.
Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 70, in py_import
    result = _vanilla_import(module_name)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 60, in _vanilla_import
    return __import__(module_name, globals(), locals(), [])
ImportError: No module named matplotlib

CRITICAL
2014-09-02 14:08:51,758
/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/packages/pylab/init.py, line 53
Exception: Installation of python package 'matplotlib' failed.
Traceback (most recent call last):
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 70, in py_import
    result = _vanilla_import(module_name)
  File "/lgm/uvcdat/2014-09-02-devel/vistrails/vistrails/core/bundles/pyimport.py", line 60, in _vanilla_import
    return __import__(module_name, globals(), locals(), [])
ImportError: No module named matplotlib

   ------ Loaded plot Histogram, varnum = 1 ------ 
2014-09-02 14:08:51.947 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
2014-09-02 14:08:52.066 Python[10292:d07] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.

@doutriaux1
Copy link
Contributor Author

@aashish24 you're right this code is not there anymore. I was looking at the sha1 of the "working" (not) one in this thread. What happened to this code? Where did it go?

@doutriaux1
Copy link
Contributor Author

fresh build this morning for jim made it disappear for him. Fresh build for me made it appear (both caes on macs 10.9.4)

@doutriaux1
Copy link
Contributor Author

@remram44 b86b91e works for me

@doutriaux1
Copy link
Contributor Author

so does 174d1ea

@doutriaux1
Copy link
Contributor Author

ok now switching back to uvcdat-master it works... That's like black magic.

@doutriaux1
Copy link
Contributor Author

I have absolutely no idea what is going on here... Both Jim and I had this appear and disappear

@aashish24
Copy link
Contributor

this code was not required and Remi removed it.

@doutriaux1
Copy link
Contributor Author

by the way this code IS in uvcdat-next....

@doutriaux1
Copy link
Contributor Author

is there a branch that was merged inappropriately?

@doutriaux1
Copy link
Contributor Author

doutriaux1@sofia:[/lgm/uvcdat/2014-09-02-devel/vistrails]:[uvcdat-next]:[1803]> git branch --no-merged
uvcdat-520-fix-dependencies
uvcdat-520-suppress-gui-errors
uvcdat-579-fix-animate-signals

@doutriaux1
Copy link
Contributor Author

@remram44 should I merge both 520 issues into uvcdat-next? or just one? which one?

@remram44
Copy link
Contributor

remram44 commented Sep 3, 2014

It's really difficult for me to follow your Git workflow.

The only thing I can see right now is uvcdat-520-fix-loaded-pkgs which is in uvcdat-master but not uvcdat-next.

@doutriaux1
Copy link
Contributor Author

cool! I think that's all i needed to know will merge uvcdat-520-fix-loaded-pkgs into uvcdat-next now. Thanks again.

Workflow is as follow:
1- start from uvcdat-master
2- do your bug fixes, push into your own branch
3- merge your branch into uvcdat-next
4- ask for your branch to be merged into uvcdat-master once it is approved as working inside uvcdat-next

Hope this helps.

@doutriaux1
Copy link
Contributor Author

thx @remram44

@doutriaux1
Copy link
Contributor Author

duplicate #595

@doutriaux1
Copy link
Contributor Author

that one appeared and disappeared magically for Jim and I. Going back and forth in commits seems to magically fix it....

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants