From richard.grenon at onera.fr Wed Oct 1 03:53:26 2014 From: richard.grenon at onera.fr (Richard Grenon) Date: Wed, 01 Oct 2014 09:53:26 +0200 Subject: [Paraview] PV 420 unable to read state file from PV 410 In-Reply-To: References: <542A9896.7020201@onera.fr> <542AAEC7.7040405@onera.fr> Message-ID: <542BB2F6.40209@onera.fr> Hello Utkarsh. I attach an archive tar.gz file that contains two short structured datasets and two pvsm state files: * dataset1.tp = ASCII Tecplot file that contains an IxJ structured surface. * dataset2.tp = ASCII Tecplot file that contains an IxJ structured surface having a common boundary with the first one. * merge.pvsm: reproduces the bad plot with missing part of surface after MergeBlocks. * merge420.pvsm : no missing part after MergeBlocks, but error message. "merge.pvsm" and "merge420.pvsm" contain the same simple pipeline, but components were added in a different order. Richard Le 30/09/2014 22:24, Utkarsh Ayachit a ?crit : > This is a little less surprising since this release does include some > major refactors to VTK when relating to structured extents. Is it > possible to get some other dummy dataset that would help reproduce > this issue? That'll make the tracking down easier. > > Thanks > Utkarsh > > On Tue, Sep 30, 2014 at 9:23 AM, Richard Grenon wrote: >> Hello, >> >> The problem in PV 420 seems to be related with the "MergeBlocks" filter: >> when I open two Tecplot files, I first make a group with these two datasets, >> then I apply MergeBlocks on the group, and I see that there is a missing >> part on the result of MergeBlocks between the two datasets. I attach two >> pictures, one obtained with a pipeline built in PV 410 (Merge is OK) and the >> other obtained with the same pipeline built in PV 420 (Merge is not OK). >> >> Richard >> -- Richard GRENON ONERA Departement d'Aerodynamique Appliquee - DAAP/ACI 8 rue des Vertugadins 92190 MEUDON - FRANCE phone : +33 1 46 73 42 17 fax : +33 1 46 73 41 46 mailto:Richard.Grenon at onera.fr http://www.onera.fr -------------- next part -------------- A non-text attachment was scrubbed... Name: pv420_mergeblocks_test.tar.gz Type: application/x-gzip Size: 77743 bytes Desc: not available URL: From jfavre at cscs.ch Wed Oct 1 06:46:00 2014 From: jfavre at cscs.ch (Favre Jean) Date: Wed, 1 Oct 2014 10:46:00 +0000 Subject: [Paraview] PV 420 unable to read state file from PV 410 In-Reply-To: References: <542A9896.7020201@onera.fr> <542AAEC7.7040405@onera.fr>, Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F682814EA3E@MBX21.d.ethz.ch> as discussed with Utkarsh, this is most likely related to a bug about structured extents in version 4.2 I created a reproducer and filled a bug http://www.paraview.org/Bug/view.php?id=15022 ----------------- Jean/CSCS From lifeandfree at gmail.com Wed Oct 1 08:06:43 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Wed, 1 Oct 2014 18:06:43 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day. For the settings I used your instruction online http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 . Did everything there. Would you say it does not work? Ilya 2014-09-30 20:43 GMT+06:00 Scott Wittenburg : > Your client side request to the launcher is asking for the "visualizer" > application, while the launcher (according to your launcher config) doesn't > know about a command line to start that application. Try changing the > "pipeline" key under the "apps" section to "visualizer". > > Cheers, > Scott > > > On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev > wrote: > >> Good day! >> >> Yes, of course >> Attached. >> Also put the configuration file Apache. >> >> Ilya >> >> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg > >: >> >>> Can you share your launcher configuration file? It appears you may have >>> no "visualizer" application command line configured. >>> >>> Cheers, >>> Scott >>> >>> >>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >>> wrote: >>> >>>> >>>> And there is another question. >>>> Deployed software. I go to http://localhost/apps/Visualizer /. As a >>>> result, I see only the inscription ParaViewWeb and flailing wheel. And >>>> he gave me a list of errors in the console: >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1439, in dataReceived >>>> finishCallback(data[contentLength:]) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1668, in _finishRequestBody >>>> self.allContentReceived() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 1731, in allContentReceived >>>> req.requestReceived(command, path, version) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>> line 827, in requestReceived >>>> self.process() >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 189, in process >>>> self.render(resrc) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 238, in render >>>> body = resrc.render(self) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>> line 250, in render >>>> return m(request) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 399, in render_POST >>>> session = self.session_manager.createSession(payload) >>>> File >>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>> line 182, in createSession >>>> options['cmd'] = >>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>> self.config['properties']]) >>>> exceptions.KeyError: u'visualizer' >>>> Unhandled Error >>>> Traceback (most recent call last): >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>> line 321, in processingFailed >>>> % webutil.formatFailure(reason)) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>> line 425, in formatFailure >>>> flattenString(None, >>>> FailureElement(myFailure)).addBoth(result.append) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 420, in flattenString >>>> d = flatten(request, root, io.write) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 402, in flatten >>>> _writeFlattenedData(state, write, result) >>>> --- --- >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 359, in _writeFlattenedData >>>> element = state.next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 326, in _flattenTree >>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>> twisted.web.error.FlattenerError: Exception while flattening: >>>> >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 317, in _flattenTree >>>> element = stack[-1].next() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>> line 286, in _flattenElement >>>> result = root.render(request) >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>> line 184, in render >>>> return loader.load() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 465, in load >>>> self._loadedTemplate = self._loadDoc() >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>> line 446, in _loadDoc >>>> f = self._path.open('r') >>>> File >>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>> line 828, in open >>>> return open(self.path, mode + 'b') >>>> IOError: [Errno 2] No such file or directory: >>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>> >>>> >>>> In logs file error.log: >>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from >>>> remote server returned by /paraview/, referer: >>>> http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>>> AH01102: error reading status line from remote server localhost:8080, >>>> referer: http://localhost/apps/Visualizer/ >>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from >>>> remote server returned by /paraview/, referer: >>>> http://localhost/apps/Visualizer/ >>>> >>>> >>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>> >>>>> Good day. >>>>> Thank you. >>>>> >>>>> You may be able to explain. What kind of filter is it? >>>>> >>>>> Ilya >>>>> >>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> ParaView 4.2 has been released, so that would be the latest stable >>>>>> version available. >>>>>> There is no localization per say but the filter names could be >>>>>> customized the way you want. >>>>>> >>>>>> For continuous live visualization it is possible but that will be a >>>>>> custom development. And for that you can contact Kitware for either a >>>>>> support contract (http://www.kitware.com/products/support.html) or >>>>>> an end-product development ( >>>>>> http://www.kitware.com/products/consulting.html). >>>>>> >>>>>> Seb >>>>>> >>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>>>>> wrote: >>>>>> >>>>>>> thank you, ok. try to understand. I put the stable version and not the >>>>>>> release candidate. >>>>>>> >>>>>>> But there are a few more questions. >>>>>>> Do files are responsible for localization? I need to replace the >>>>>>> language in the design parawiewweb. >>>>>>> And the second. Is there a possibility of the file from which the >>>>>>> object is loaded into the web, continuously read the data? That is to >>>>>>> update the image in the browser loading new data, but this is not in >>>>>>> the manual and automatic. >>>>>>> >>>>>>> Sincerely, >>>>>>> Sukhachev Ilya! >>>>>>> >>>>>>> >>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>> with Apache. >>>>>>>> Moreover, can you enable the development tools on your browser to >>>>>>>> see what kind of error you got? >>>>>>>> >>>>>>>> Did you look also at the different types of logs? Apache, Launcher >>>>>>>> (see config to know where you choose to put them). >>>>>>>> That could also give you an idea on what went wrong. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi, Sebastien >>>>>>>>> >>>>>>>>> Thank you. >>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>>>> only displayed only the green bar at the top of the window, and >>>>>>>>> nothing more. >>>>>>>>> That in this case? >>>>>>>>> >>>>>>>>> Sincerely, >>>>>>>>> Sukhachev Ilya! >>>>>>>>> >>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> Moreover, the documentation that get's updated automatically can >>>>>>>>>> be found at the following address. (Which might be more accurate.) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>> >>>>>>>>>> This is the one you find when you go on paraview.org and go to >>>>>>>>>> the documentation section. >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>> >>>>>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should >>>>>>>>>>> be launched with a DISPLAY setup. >>>>>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>> >>>>>>>>>>> Seb >>>>>>>>>>> >>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Good day! >>>>>>>>>>>> Prompt please. >>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>>>>> as 1 Ceci. >>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>> Thank you >>>>>>>>>>>> >>>>>>>>>>>> Sincerely, >>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>> >>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>> >>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>> >>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ? ?????????, >>>>>>>>> ??????? ????! >>>>>>>>> +7 912 216 72 72 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ? ?????????, >>>>>>> ??????? ????! >>>>>>> +7 912 216 72 72 >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thomas.Otoole at pinntech.com Wed Oct 1 07:38:20 2014 From: Thomas.Otoole at pinntech.com (Thomas O'Toole) Date: Wed, 1 Oct 2014 11:38:20 +0000 Subject: [Paraview] Setting default Glyph Type to Sphere Message-ID: <4E09FD4309849147BFDAED6FAAC87A956984DEF3@EP1EXMB005.corp.halliburton.com> Hi everyone, I would like to set the Glyph filter Glyph Type to be Sphere by default. I've read through the blog post about setting defaults in Paraview 4.2 (http://www.kitware.com/blog/home/post/702) but have been unsuccessful in my attempts to set this default either through the GUI or using a JSON config file. Is it possible to set the Glyph Type to be Sphere by default? And if so, what JSON syntax is needed to achieve this? Many thanks, Tom ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Oct 1 08:46:06 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 1 Oct 2014 08:46:06 -0400 Subject: [Paraview] Setting default Glyph Type to Sphere In-Reply-To: <4E09FD4309849147BFDAED6FAAC87A956984DEF3@EP1EXMB005.corp.halliburton.com> References: <4E09FD4309849147BFDAED6FAAC87A956984DEF3@EP1EXMB005.corp.halliburton.com> Message-ID: Tom, Alas, the settings custom defaults work for most, but not all properties. This is one of those properties for which it does not work, unfortunately. One of my goals for the next release is to make custom defaults work for properties such as these. Best regards, Cory On Wed, Oct 1, 2014 at 7:38 AM, Thomas O'Toole wrote: > Hi everyone, > > > > I would like to set the Glyph filter Glyph Type to be Sphere by default. > I?ve read through the blog post about setting defaults in Paraview 4.2 > (http://www.kitware.com/blog/home/post/702) but have been unsuccessful in my > attempts to set this default either through the GUI or using a JSON config > file. > > > > Is it possible to set the Glyph Type to be Sphere by default? And if so, > what JSON syntax is needed to achieve this? > > > > Many thanks, > > > > Tom > > > > > > ________________________________ > This e-mail, including any attached files, may contain confidential and > privileged information for the sole use of the intended recipient. Any > review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive information > for the intended recipient), please contact the sender by reply e-mail and > delete all copies of this message. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Wed Oct 1 09:03:00 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 1 Oct 2014 09:03:00 -0400 Subject: [Paraview] Setting default Glyph Type to Sphere In-Reply-To: <4E09FD4309849147BFDAED6FAAC87A956984DF55@EP1EXMB005.corp.halliburton.com> References: <4E09FD4309849147BFDAED6FAAC87A956984DEF3@EP1EXMB005.corp.halliburton.com> <4E09FD4309849147BFDAED6FAAC87A956984DF55@EP1EXMB005.corp.halliburton.com> Message-ID: Tom, No, there is not a way to tell that at this time. Cory On Wed, Oct 1, 2014 at 8:50 AM, Thomas O'Toole wrote: > Cory, > > OK, thanks for this information. On a related note, is there an easy way of telling which properties can/cannot presently have custom defaults set? > > Cheers, > > Tom > > -----Original Message----- > From: Cory Quammen [mailto:cory.quammen at kitware.com] > Sent: 01 October 2014 13:46 > To: Thomas O'Toole > Cc: paraview at paraview.org > Subject: Re: [Paraview] Setting default Glyph Type to Sphere > > Tom, > > Alas, the settings custom defaults work for most, but not all properties. This is one of those properties for which it does not work, unfortunately. One of my goals for the next release is to make custom defaults work for properties such as these. > > Best regards, > Cory > > On Wed, Oct 1, 2014 at 7:38 AM, Thomas O'Toole wrote: >> Hi everyone, >> >> >> >> I would like to set the Glyph filter Glyph Type to be Sphere by default. >> I?ve read through the blog post about setting defaults in Paraview 4.2 >> (http://www.kitware.com/blog/home/post/702) but have been unsuccessful >> in my attempts to set this default either through the GUI or using a >> JSON config file. >> >> >> >> Is it possible to set the Glyph Type to be Sphere by default? And if >> so, what JSON syntax is needed to achieve this? >> >> >> >> Many thanks, >> >> >> >> Tom >> >> >> >> >> >> ________________________________ >> This e-mail, including any attached files, may contain confidential >> and privileged information for the sole use of the intended recipient. >> Any review, use, distribution, or disclosure by others is strictly prohibited. >> If you are not the intended recipient (or authorized to receive >> information for the intended recipient), please contact the sender by >> reply e-mail and delete all copies of this message. >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From Thomas.Otoole at pinntech.com Wed Oct 1 08:50:54 2014 From: Thomas.Otoole at pinntech.com (Thomas O'Toole) Date: Wed, 1 Oct 2014 12:50:54 +0000 Subject: [Paraview] Setting default Glyph Type to Sphere In-Reply-To: References: <4E09FD4309849147BFDAED6FAAC87A956984DEF3@EP1EXMB005.corp.halliburton.com> Message-ID: <4E09FD4309849147BFDAED6FAAC87A956984DF55@EP1EXMB005.corp.halliburton.com> Cory, OK, thanks for this information. On a related note, is there an easy way of telling which properties can/cannot presently have custom defaults set? Cheers, Tom -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: 01 October 2014 13:46 To: Thomas O'Toole Cc: paraview at paraview.org Subject: Re: [Paraview] Setting default Glyph Type to Sphere Tom, Alas, the settings custom defaults work for most, but not all properties. This is one of those properties for which it does not work, unfortunately. One of my goals for the next release is to make custom defaults work for properties such as these. Best regards, Cory On Wed, Oct 1, 2014 at 7:38 AM, Thomas O'Toole wrote: > Hi everyone, > > > > I would like to set the Glyph filter Glyph Type to be Sphere by default. > I?ve read through the blog post about setting defaults in Paraview 4.2 > (http://www.kitware.com/blog/home/post/702) but have been unsuccessful > in my attempts to set this default either through the GUI or using a > JSON config file. > > > > Is it possible to set the Glyph Type to be Sphere by default? And if > so, what JSON syntax is needed to achieve this? > > > > Many thanks, > > > > Tom > > > > > > ________________________________ > This e-mail, including any attached files, may contain confidential > and privileged information for the sole use of the intended recipient. > Any review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive > information for the intended recipient), please contact the sender by > reply e-mail and delete all copies of this message. > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Oct 1 09:39:52 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 1 Oct 2014 09:39:52 -0400 Subject: [Paraview] Edit Color Map In-Reply-To: References: Message-ID: I'd suggest downloading the 4.2 binaries from paraview.org. That may be easier. 3.14 is too old by now. Utkarsh On Wed, Oct 1, 2014 at 6:54 AM, Carlos Andr?s Bernal Castro wrote: > Hello Utkarsh, > > First of all thank you very much for answering. According to your answer, > yes you are right, that is exactly what I am doing I am ensuring that I am > using the appropriate array, that is to say, "Tracer1", "Tracer2" and so on. > My issue is that I am not getting what you got in the image that you sent me > (which is brilliant), for some reason I am not able to get that coloring. > The other thing is that I am using Paraview version 3.14.1 64-bit. I do not > know if that could be affecting the views. Please find attached the view > that I am getting. Thanks for your help. > > Kind Regards, > > > Carlos Andr?s Bernal Castro > Ingeniero Ambiental Y Sanitario > Universidad De La Salle > > >> Date: Tue, 30 Sep 2014 22:18:58 -0400 >> Subject: Re: [Paraview] Edit Color Map >> From: utkarsh.ayachit at kitware.com >> To: cabcias at hotmail.com >> CC: paraview at paraview.org > >> >> Andres, >> >> Edit Color Map is not really the thing you're looking for, I think. >> Once you've set up a slice to a specific Z value for a tracer, you >> need to ensure that you're coloring with the appropriate array, >> "Tracer1", "Tracer2" and so on. Attached is state generated using >> ParaView 4.2. That renders 2 slices showing tracer 1 and 2 in separate >> views. >> >> Is that what you're looking for? >> >> Utkarsh >> >> On Tue, Sep 30, 2014 at 3:16 PM, Carlos Andr?s Bernal Castro >> wrote: >> > >> > To whom it may concern, >> > >> > Hello... my name is Andres Bernal and I am a London South Bank >> > University >> > student carrying out a thesis about the influence of the buildings shape >> > onto the atmospheric pollutants concentration due to the innovative >> > forms of >> > them nowadays. I am working on a building known as "The Walkie-Talkie >> > Building" and the third stage of the project was to read the simulations >> > (coming from Fluidity) . In order to move along with the project we need >> > to >> > see/read the dispersion of pollutants (tracers) around the building >> > (coming >> > from some sources that I set up, in this case/file, 7 sources which >> > means 7 >> > Tracers ) with Paraview. When I set up a "Slice" in order to see such >> > dispersion at a certain height I cannot see anything and it seems to be >> > this >> > could be worked out in the "Edit Color Map". I would like you to help me >> > in >> > this issue as I have been trying to figure out the problem but I have >> > not >> > been able to and I got stuck for this matter. I would be really >> > grateful, >> > thanks. >> > >> > The heights of the tracers are: >> > >> > Tracer 1 = 0.3 >> > Tracer 2 = 0.5 >> > Tracer 3 = 0.7 >> > Tracer 4 = 0.3 >> > Tracer 5 = 0.8 >> > Tracer 6 = 0.5 >> > Tracer 7 = 0.762 >> > >> > The file attached below is a very simple scenario as I am working on >> > several >> > more complex scenarios even with more buildings. I would just like you >> > to >> > help me to sort out the colours issue to see the tracers, please. >> > >> > Any advice would be much appreciated. >> > >> > Kind Regards, >> > >> > Andres Bernal >> > >> > Carlos Andr?s Bernal Castro >> > Ingeniero Ambiental Y Sanitario >> > Universidad De La Salle >> > Carlos Andr?s tiene un archivo para compartir contigo en OneDrive. Para >> > verlo, haz clic en el siguiente v?nculo. >> > Walkie-Curved_29.vtu >> > >> > _______________________________________________ >> > Powered by www.kitware.com >> > >> > Visit other Kitware open-source projects at >> > http://www.kitware.com/opensource/opensource.html >> > >> > Please keep messages on-topic and check the ParaView Wiki at: >> > http://paraview.org/Wiki/ParaView >> > >> > Follow this link to subscribe/unsubscribe: >> > http://public.kitware.com/mailman/listinfo/paraview >> > From utkarsh.ayachit at kitware.com Wed Oct 1 09:48:37 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 1 Oct 2014 09:48:37 -0400 Subject: [Paraview] PV 420 unable to read state file from PV 410 In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F682814EA3E@MBX21.d.ethz.ch> References: <542A9896.7020201@onera.fr> <542AAEC7.7040405@onera.fr> <0EB9B6375711A04B820E6B6F5CCA9F682814EA3E@MBX21.d.ethz.ch> Message-ID: Thanks everyone. We'll have this tracked down soon. On Wed, Oct 1, 2014 at 6:46 AM, Favre Jean wrote: > as discussed with Utkarsh, this is most likely related to a bug about structured extents in version 4.2 > > I created a reproducer and filled a bug > > http://www.paraview.org/Bug/view.php?id=15022 > > ----------------- > Jean/CSCS From scott.wittenburg at kitware.com Wed Oct 1 10:09:46 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Wed, 1 Oct 2014 08:09:46 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: The launcher config file you sent to the list was missing a "visualizer" entry, but those instructions have one. Other than that, are things working properly now? When we do find problems with the instructions, we try to fix them, but I'm not sure yet if this is one of those cases. Cheers, Scott On Wed, Oct 1, 2014 at 6:06 AM, Ilya Sukhachev wrote: > Good day. > > For the settings I used your instruction online > http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 > . > Did everything there. Would you say it does not work? > > Ilya > > 2014-09-30 20:43 GMT+06:00 Scott Wittenburg > : > >> Your client side request to the launcher is asking for the "visualizer" >> application, while the launcher (according to your launcher config) doesn't >> know about a command line to start that application. Try changing the >> "pipeline" key under the "apps" section to "visualizer". >> >> Cheers, >> Scott >> >> >> On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev >> wrote: >> >>> Good day! >>> >>> Yes, of course >>> Attached. >>> Also put the configuration file Apache. >>> >>> Ilya >>> >>> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg < >>> scott.wittenburg at kitware.com>: >>> >>>> Can you share your launcher configuration file? It appears you may >>>> have no "visualizer" application command line configured. >>>> >>>> Cheers, >>>> Scott >>>> >>>> >>>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >>>> wrote: >>>> >>>>> >>>>> And there is another question. >>>>> Deployed software. I go to http://localhost/apps/Visualizer /. As a >>>>> result, I see only the inscription ParaViewWeb and flailing wheel. And >>>>> he gave me a list of errors in the console: >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1439, in dataReceived >>>>> finishCallback(data[contentLength:]) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1668, in _finishRequestBody >>>>> self.allContentReceived() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 1731, in allContentReceived >>>>> req.requestReceived(command, path, version) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>> line 827, in requestReceived >>>>> self.process() >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 189, in process >>>>> self.render(resrc) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 238, in render >>>>> body = resrc.render(self) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>> line 250, in render >>>>> return m(request) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 399, in render_POST >>>>> session = self.session_manager.createSession(payload) >>>>> File >>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>> line 182, in createSession >>>>> options['cmd'] = >>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>> self.config['properties']]) >>>>> exceptions.KeyError: u'visualizer' >>>>> Unhandled Error >>>>> Traceback (most recent call last): >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>> line 321, in processingFailed >>>>> % webutil.formatFailure(reason)) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>> line 425, in formatFailure >>>>> flattenString(None, >>>>> FailureElement(myFailure)).addBoth(result.append) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 420, in flattenString >>>>> d = flatten(request, root, io.write) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 402, in flatten >>>>> _writeFlattenedData(state, write, result) >>>>> --- --- >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 359, in _writeFlattenedData >>>>> element = state.next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 326, in _flattenTree >>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>> >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 317, in _flattenTree >>>>> element = stack[-1].next() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>> line 286, in _flattenElement >>>>> result = root.render(request) >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>> line 184, in render >>>>> return loader.load() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 465, in load >>>>> self._loadedTemplate = self._loadDoc() >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>> line 446, in _loadDoc >>>>> f = self._path.open('r') >>>>> File >>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>> line 828, in open >>>>> return open(self.path, mode + 'b') >>>>> IOError: [Errno 2] No such file or directory: >>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>> >>>>> >>>>> In logs file error.log: >>>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading from >>>>> remote server returned by /paraview/, referer: >>>>> http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>>>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>>>> AH01102: error reading status line from remote server localhost:8080, >>>>> referer: http://localhost/apps/Visualizer/ >>>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading from >>>>> remote server returned by /paraview/, referer: >>>>> http://localhost/apps/Visualizer/ >>>>> >>>>> >>>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>>> >>>>>> Good day. >>>>>> Thank you. >>>>>> >>>>>> You may be able to explain. What kind of filter is it? >>>>>> >>>>>> Ilya >>>>>> >>>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> ParaView 4.2 has been released, so that would be the latest stable >>>>>>> version available. >>>>>>> There is no localization per say but the filter names could be >>>>>>> customized the way you want. >>>>>>> >>>>>>> For continuous live visualization it is possible but that will be a >>>>>>> custom development. And for that you can contact Kitware for either a >>>>>>> support contract (http://www.kitware.com/products/support.html) or >>>>>>> an end-product development ( >>>>>>> http://www.kitware.com/products/consulting.html). >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>>>>> > wrote: >>>>>>> >>>>>>>> thank you, ok. try to understand. I put the stable version and not the >>>>>>>> release candidate. >>>>>>>> >>>>>>>> But there are a few more questions. >>>>>>>> Do files are responsible for localization? I need to replace the >>>>>>>> language in the design parawiewweb. >>>>>>>> And the second. Is there a possibility of the file from which the >>>>>>>> object is loaded into the web, continuously read the data? That is to >>>>>>>> update the image in the browser loading new data, but this is not in >>>>>>>> the manual and automatic. >>>>>>>> >>>>>>>> Sincerely, >>>>>>>> Sukhachev Ilya! >>>>>>>> >>>>>>>> >>>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>>> with Apache. >>>>>>>>> Moreover, can you enable the development tools on your browser to >>>>>>>>> see what kind of error you got? >>>>>>>>> >>>>>>>>> Did you look also at the different types of logs? Apache, Launcher >>>>>>>>> (see config to know where you choose to put them). >>>>>>>>> That could also give you an idea on what went wrong. >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, Sebastien >>>>>>>>>> >>>>>>>>>> Thank you. >>>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>>>>> only displayed only the green bar at the top of the window, and >>>>>>>>>> nothing more. >>>>>>>>>> That in this case? >>>>>>>>>> >>>>>>>>>> Sincerely, >>>>>>>>>> Sukhachev Ilya! >>>>>>>>>> >>>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>> >>>>>>>>>>> Moreover, the documentation that get's updated automatically can >>>>>>>>>>> be found at the following address. (Which might be more accurate.) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>>> >>>>>>>>>>> This is the one you find when you go on paraview.org and go to >>>>>>>>>>> the documentation section. >>>>>>>>>>> >>>>>>>>>>> Seb >>>>>>>>>>> >>>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>>> >>>>>>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should >>>>>>>>>>>> be launched with a DISPLAY setup. >>>>>>>>>>>> Otherwise, you will have to be more explicit on what you've >>>>>>>>>>>> done and what is not working. The log files usually helps to see what >>>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>>> >>>>>>>>>>>> Seb >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Good day! >>>>>>>>>>>>> Prompt please. >>>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>>> Unfolded, but for some reason I can not open in the web >>>>>>>>>>>>> browser Visualizer (http: // localhost / apps / Visualizer /) >>>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can >>>>>>>>>>>>> run only as 1 Ceci. >>>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>>> Thank you >>>>>>>>>>>>> >>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>> >>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>> >>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>>> >>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> ? ?????????, >>>>>>>>>> ??????? ????! >>>>>>>>>> +7 912 216 72 72 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ? ?????????, >>>>>>>> ??????? ????! >>>>>>>> +7 912 216 72 72 >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 1 10:51:44 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 1 Oct 2014 10:51:44 -0400 Subject: [Paraview] paraview book next edition - you work immortalized as the cover image? Message-ID: Hey group, The text for the next (completely revamped) edition of the Paraview guide is nearing completion. One of the last things on our todo list is to select a stunning cover image. I am quite partial to the cover of the current e-book edition (details below). But, if you would like you work immortalized, are OK with us using the image on the book and in the web page, and think you can do better than Greg and Arno did, please let us know about it by sending comm at kitware.com an email. In the email, please have "paraview book cover" in the subject somewhere, include the text that you want us to use to credit you and a description of the science behind the pretty picture. Oh, and don't forget to attach the proposed image. ? Image courtesy of Greg Schussman and Arno Candel of the Advanced Computations Department at SLAC. It is a visualization of an electromagnetic simulation performed at SLAC of a key component of a new particle accelerator being designed at CERN. In the visualization, the propagation of electric fields excited by decelerated particles is shown via the blue to red rainbow color map. cheers, thanks, and good luck! David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cover_gradient_dark_top-2.png Type: image/png Size: 132336 bytes Desc: not available URL: From sean at rogue-research.com Wed Oct 1 11:20:10 2014 From: sean at rogue-research.com (Sean McBride) Date: Wed, 1 Oct 2014 11:20:10 -0400 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: References: Message-ID: <20141001152010.1482049559@mail.rogue-research.com> Utkarsh, I can confirm the same crash with the binary you refer to. Note that AVFoundation framework was added in OS X 10.7. Sean On Tue, 30 Sep 2014 19:47:24 -0700, Fernando Paolo said: >Isn't the Dashboard binary the one incompatible with OSX 10.6: > >ParaView-4.2.0-Darwin-64bit.dmg >ParaView-4.2.0-Darwin-64bit.dmg> > > > >On Tue, Sep 30, 2014 at 7:43 PM, Utkarsh Ayachit < >utkarsh.ayachit at kitware.com> wrote: > >> Hmm...can you try downloading from the dashboard directly: >> >> http://open.cdash.org/viewFiles.php?buildid=3508570 >> >> Utkarsh >> >> On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo >> wrote: >> > I am receiving the exact same error: >> > >> > Process: paraview [10851] >> > Path: /Applications/paraview.app/Contents/MacOS/paraview >> > Identifier: paraview >> > Version: ??? (???) >> > Code Type: X86-64 (Native) >> > Parent Process: launchd [205] >> > >> > Date/Time: 2014-09-30 19:37:54.326 -0700 >> > OS Version: Mac OS X 10.6.8 (10K549) >> > Report Version: 6 >> > >> > Interval Since Last Report: 777959 sec >> > Crashes Since Last Report: 6 >> > Per-App Crashes Since Last Report: 4 >> > Anonymous UUID: 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 >> > >> > Exception Type: EXC_BREAKPOINT (SIGTRAP) >> > Exception Codes: 0x0000000000000002, 0x0000000000000000 >> > Crashed Thread: 0 >> > >> > Dyld Error Message: >> > Library not loaded: >> > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation >> > Referenced from: >> > >> /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat. >55.48.100.dylib >> > Reason: image not found >> > >> > Binary Images: >> > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) >> > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld From utkarsh.ayachit at kitware.com Wed Oct 1 12:28:18 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 1 Oct 2014 12:28:18 -0400 Subject: [Paraview] Problem installing Paraview 4.2 in Mac OSX 10.6 In-Reply-To: <20141001152010.1482049559@mail.rogue-research.com> References: <20141001152010.1482049559@mail.rogue-research.com> Message-ID: Sounds good. We'll track it down. I am sure we bungled things up when adding the sysroot fixes to get things working with Mavericks. Sigh! Why isn't everyone just using Linux yet! :) Utkarsh On Wed, Oct 1, 2014 at 11:20 AM, Sean McBride wrote: > Utkarsh, > > I can confirm the same crash with the binary you refer to. Note that AVFoundation framework was added in OS X 10.7. > > Sean > > > On Tue, 30 Sep 2014 19:47:24 -0700, Fernando Paolo said: > >>Isn't the Dashboard binary the one incompatible with OSX 10.6: >> >>ParaView-4.2.0-Darwin-64bit.dmg >>>ParaView-4.2.0-Darwin-64bit.dmg> >> >> >> >>On Tue, Sep 30, 2014 at 7:43 PM, Utkarsh Ayachit < >>utkarsh.ayachit at kitware.com> wrote: >> >>> Hmm...can you try downloading from the dashboard directly: >>> >>> http://open.cdash.org/viewFiles.php?buildid=3508570 >>> >>> Utkarsh >>> >>> On Tue, Sep 30, 2014 at 10:39 PM, Fernando Paolo >>> wrote: >>> > I am receiving the exact same error: >>> > >>> > Process: paraview [10851] >>> > Path: /Applications/paraview.app/Contents/MacOS/paraview >>> > Identifier: paraview >>> > Version: ??? (???) >>> > Code Type: X86-64 (Native) >>> > Parent Process: launchd [205] >>> > >>> > Date/Time: 2014-09-30 19:37:54.326 -0700 >>> > OS Version: Mac OS X 10.6.8 (10K549) >>> > Report Version: 6 >>> > >>> > Interval Since Last Report: 777959 sec >>> > Crashes Since Last Report: 6 >>> > Per-App Crashes Since Last Report: 4 >>> > Anonymous UUID: 85966E22-E0D4-4F86-BA2E-4F2130C9A4C5 >>> > >>> > Exception Type: EXC_BREAKPOINT (SIGTRAP) >>> > Exception Codes: 0x0000000000000002, 0x0000000000000000 >>> > Crashed Thread: 0 >>> > >>> > Dyld Error Message: >>> > Library not loaded: >>> > /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation >>> > Referenced from: >>> > >>> /Applications/paraview.app/Contents/MacOS/../Libraries/libavformat. >>55.48.100.dylib >>> > Reason: image not found >>> > >>> > Binary Images: >>> > 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) >>> > <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld > > From simon.m.su.ctr at mail.mil Wed Oct 1 13:15:34 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 1 Oct 2014 17:15:34 +0000 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: References: <20140930150356.GC12969@megas.kitwarein.com> <20140930154210.GA6846@megas.kitwarein.com> <20140930211540.GA25473@megas.kitwarein.com> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Utkarsh, I think your patch worked. Cmake not complaining all the way to the end. Thanks -simon [snip] -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-bg_glass_75_dadada_1x400.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-bg_glass_75_e6e6e6_1x400.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-bg_glass_95_fef1ec_1x400.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-bg_highlight-soft_75_cccccc_1x100.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-icons_222222_256x240.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-icons_2e83ff_256x240.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-icons_454545_256x240.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-icons_888888_256x240.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/images/ui-icons_cd0a0a_256x240.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/jquery-ui-1.10.0.css -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jquery-ui/jquery-ui-1.10.0.min.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/arrow.gif -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/cross.gif -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/demo.html -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/hs.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/hv.png -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/jscolor/jscolor.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/nvd3 -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/nvd3/nv.d3.css -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/nvd3/nv.d3.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/nvd3/nv.d3.min.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/pure -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/pure/README.md -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/pure/package.json -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/pure/pure.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/pure/pure.min.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/rickshaw -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/rickshaw/rickshaw.js -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/rickshaw/rickshaw.min.css -- Installing: /u/ssu/pv-test/4.2.0_osmesa/share/paraview-4.2/www/ext/rickshaw/rickshaw.min.js -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, September 30, 2014 8:33 PM To: Su, Simon M CTR USARMY ARL (US) Cc: ben.boeckel at kitware.com; paraview at paraview.org Subject: Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) Simon, Attached is a patch. It basically disables the "install" failing components with the Qt components are not being built. Let me know if that works and I can have these changes merged into the repository. Utkarsh On Tue, Sep 30, 2014 at 5:24 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Ben, > > Have we talked about how to make the changes? The network setting at > ARL is not letting me through the link... > > Thanks > -simon > > -----Original Message----- > From: Ben Boeckel [mailto:ben.boeckel at kitware.com] > Sent: Tuesday, September 30, 2014 5:16 PM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) > > On Tue, Sep 30, 2014 at 19:36:13 +0000, Su, Simon M CTR USARMY ARL (US) > wrote: >> can I safely ignore the error? Can we assume the binary installation >> is complete? or are there additional installation steps after appdata >> step that is needed for a proper ParaView binary installation? If so, >> how do I get around it? > > There are probably more files which need installed after the appdata, > but making the changes in the changeset should allow your "make install" > from the superbuild to complete fully. Once that happens, the install > should be fine. > > --Ben > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From bwvb at xs4all.nl Wed Oct 1 14:16:14 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 01 Oct 2014 20:16:14 +0200 Subject: [Paraview] HOWto create / extend sources? In-Reply-To: References: <5426BC2D.7000505@xs4all.nl> <542AF1F6.4050901@xs4all.nl> Message-ID: <542C44EE.40807@xs4all.nl> Bingo! It now works precisely as expected. Thanks! Bertwim On 10/01/2014 03:55 AM, Utkarsh Ayachit wrote: > Bert, > > The problem is the CMakeLists.txt. The sphBoxSource needs to be added > as SERVER_MANAGER_SOURCES, not SOURCES. A a rule of thumb, if it's a > vtkObject subclass and not a Qt class, you generally want to put that > under SERVER_MANAGER_SOURCES. This ensure that it will get wrapped so > that ParaView can instantiate classes through their names defined in > the XML. > > Utkarsh > > On Tue, Sep 30, 2014 at 2:09 PM, B.W.H. van Beest wrote: >> Utkash, >> >> I followed-up on your suggestions, but apparently I am doing something >> wrong. I hope you or somebody else can point me to the solution. >> >> This is what I did. >> >> 1) new class: sphBoxSource. I extended class vtkCubeSource with one >> data member, with corresponding get/set method. (Code below) >> 2) I added an xml-file, with the source description taken from >> source.xml (CubeSource). (Below) >> 3) I modified the CMakeList.txt accordingly. (Below) >> >> Magically, the new source appeared in the menu. But when clicking it, >> the program crashed. >> The error message I get is: >> >> ERROR: In >> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, >> line 307 >> vtkSISourceProxy (0x30289e0): Failed to create sphBoxSource. Aborting >> for debugging purposes. >> >> >> I noticed that several people running into similar problems, but so far >> I haven't been able to find the clue to the solution. >> >> >> Before showing the code, I give the result of the compilation. >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> >> chopin Plugins/SPHToolbar# make clean >> chopin Plugins/SPHToolbar# make >> [ 0%] Generating Documentation HTMLs from xmls >> Processing wiki sources >> Processing wiki filters >> Processing wiki writers >> Processing wiki readers >> [ 10%] Generating qrc_sph_icons.cxx >> [ 10%] Compiling Qt help project SPHToolbar.qhp >> Building up file structure... >> Insert custom filters... >> Insert help data for filter section (1 of 1)... >> Insert files... >> Warning: The file >> /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.css >> does not exist! Skipping it. >> Warning: The file >> /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.png >> does not exist! Skipping it. >> Warning: The file >> /usr/local/git/ParaView/build/Examples/All/Plugins/SPHToolbar/doc/*.jpg >> does not exist! Skipping it. >> Insert contents... >> Insert indices... >> Documentation successfully generated. >> [ 10%] Generating SPHToolbar_doc.h >> -- Generate module: SPHToolbar >> [ 10%] Generating vtkSMXML_SPHToolbar.h >> -- Generate module: sph_sources >> [ 20%] Generating moc_SPHToolbarActions.cpp >> [ 20%] Generating moc_sphBActionCreateSource.cpp >> [ 30%] Generating moc_sphBAction.cpp >> [ 30%] Generating moc_SPHToolbarActionsImplementation.cpp >> [ 40%] Generating moc_SPHToolbar_Plugin.cpp >> Scanning dependencies of target SPHToolbar >> [ 50%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/qrc_sph_icons.o >> [ 50%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActions.o >> [ 60%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBActionCreateSource.o >> [ 60%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_sphBAction.o >> [ 60%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActionsImplementation.o >> [ 70%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbarActionsImplementation.o >> [ 70%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbarActions.o >> [ 80%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionCreateSource.o >> [ 80%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBActionRegionInventory.o >> [ 90%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphBoxSource.o >> [ 90%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphUndoStack.o >> [ 90%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/sphObjectTracer.o >> [100%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/SPHToolbar_Plugin.o >> [100%] Building CXX object >> Plugins/SPHToolbar/CMakeFiles/SPHToolbar.dir/moc_SPHToolbar_Plugin.o >> Linking CXX shared library >> /usr/local/git/ParaView/build/lib/libSPHToolbar.so >> [100%] Built target SPHToolbar >> chopin Plugins/SPHToolbar# >> >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> >> >> >> >> >> >> >> >> >> >> ====================================================== >> Here is the new class: >> >> #include "vtkCubeSource.h" >> class sphBoxSource : public vtkCubeSource >> { >> private: >> int _type; >> >> public: >> static sphBoxSource *New(); // Monkey >> see, monkey do ?????????????? >> vtkTypeMacro(sphBoxSource,vtkCubeSource); // Monkey see, monkey >> do ?????????????? >> >> public: >> sphBoxSource( double=1.0, double=1.0, double=1.0 ); >> ~sphBoxSource(); >> >> public: >> void setType( int ); >> int getType() const; >> }; >> ============================================================ >> >> XML-file "sph_sources.xml": (adapted from sources.xml) >> ============================================================ >> >> >> > label="SPHBox" >> name="SPHBoxSource"> >> > short_help="3D box with specified X, Y, and Z >> lengths">The >> Box source can be used to add a box to the 3D >> scene. The >> output of the Box source is polygonal data >> containing both >> normals and texture coordinates. >> > command="SetXLength" >> default_values="1.0" >> name="XLength" >> number_of_elements="1" >> panel_visibility="default"> >> > name="range" /> >> This property specifies the length of the box in >> the X >> direction. >> >> > command="SetYLength" >> default_values="1.0" >> name="YLength" >> number_of_elements="1" >> panel_visibility="default"> >> > name="range" /> >> This property specifies the length of the box in >> the Y >> direction. >> >> > command="SetZLength" >> default_values="1.0" >> name="ZLength" >> number_of_elements="1" >> panel_visibility="default"> >> > name="range" /> >> This property specifies the length of the box in >> the Z >> direction. >> >> > command="SetCenter" >> default_values="0.0 0.0 0.0" >> name="Center" >> number_of_elements="3" >> panel_visibility="default"> >> >> This property specifies the center of the >> box. >> >> >> >> >> >> ====================================================================== >> >> Finally, the CMakeList.txt reads: >> ====================================================================== >> >> CMAKE_MINIMUM_REQUIRED(VERSION 2.4) >> >> IF(NOT ParaView_BINARY_DIR) >> FIND_PACKAGE(ParaView REQUIRED) >> INCLUDE(${PARAVIEW_USE_FILE}) >> ENDIF(NOT ParaView_BINARY_DIR) >> >> IF(PARAVIEW_BUILD_QT_GUI) >> # We need to wrap for Qt stuff such as signals/slots etc. to work >> correctly. >> IF (PARAVIEW_QT_VERSION VERSION_GREATER "4") >> QT5_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h >> sphBAction.h ) >> ELSE () >> QT4_WRAP_CPP(MOC_SRCS SPHToolbarActions.h sphBActionCreateSource.h >> sphBAction.h ) >> ENDIF () >> >> # This is a macro for adding QActionGroup subclasses automatically as >> toolbars. >> ADD_PARAVIEW_ACTION_GROUP(IFACES IFACE_SRCS >> CLASS_NAME SPHToolbarActions >> GROUP_NAME "ToolBar/SPHToolbar") >> >> # Now create a plugin for the toolbar. Here we pass IFACES and IFACE_SRCS >> # which are filled up by the above macro with relevant entries >> ADD_PARAVIEW_PLUGIN(SPHToolbar "1.0" >> GUI_INTERFACES ${IFACES} >> GUI_RESOURCES sph_icons.qrc >> SERVER_MANAGER_XML sph_sources.xml >> SOURCES ${MOC_SRCS} ${IFACE_SRCS} >> SPHToolbarActions.cpp >> sphBActionCreateSource.cpp sphBActionRegionInventory.cpp >> sphBoxSource.cpp >> sphUndoStack.cpp sphObjectTracer.cpp ) >> ENDIF(PARAVIEW_BUILD_QT_GUI) >> >> ====================================================================== >> >> On 09/29/2014 02:46 PM, Utkarsh Ayachit wrote: >>>> a) How to create a new source ("MyNewSource") >>> You define the 'proxy' under the "sources" group, rather than filters. >>> It will automatically show up in the Menu. Look at sources.xml under >>> [1] to see other source proxy definitions. >>> >>>> b) How can I extend an existing source (box, sphere, etc.) with new >>>> properties and methods ("MyBox, "MySphere"). >>> Similar to the filters, you basically need to write a new VTK >>> algorithm with these new methods. You can subclass the existing VTK >>> source. Looking at sources.xml, you can find out which proxy using >>> which VTK algorithm, e.g. "SphereSource" (labelled as "Sphere") uses >>> "vtkSphereSource". After adding the methods on the VTK algorithm, next >>> part is exposing those methods as properties using the XML. >>> >>> [1] https://github.com/Kitware/ParaView/tree/master/ParaViewCore/ServerManager/SMApplication/Resources >>> >>>> Any help or suggestions are greatly appreciated. >>>> >>>> Kind Regards, >>>> Bertwim >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Wed Oct 1 14:33:40 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 01 Oct 2014 20:33:40 +0200 Subject: [Paraview] -std=c++11 for a single directory? Message-ID: <542C4904.9000202@xs4all.nl> Hi, For a new plugin i'm currently writing, I'm using features of c++11. In order to do so, I need to specify the flag -std=c++11 to the gcc compiler. So far, I'm only able to achieve this by adding the flag -std=c++11 to the file "flags.make" appearing in a subdirectory of CMakeFiles in the *build* directory tree. This works, but this flags.cmake is overwritten every time a new configuration is done (e.g. after a change in CMakelist.txt). Where can I specify compile flags that only hold for a given directory? Kind Regards, Bertwim From robert.maynard at kitware.com Wed Oct 1 15:31:11 2014 From: robert.maynard at kitware.com (Robert Maynard) Date: Wed, 1 Oct 2014 15:31:11 -0400 Subject: [Paraview] -std=c++11 for a single directory? In-Reply-To: <542C4904.9000202@xs4all.nl> References: <542C4904.9000202@xs4all.nl> Message-ID: You need to force cache the CMAKE_CXX_FLAGS variable with c++11 in the CMakeLists.txt for the plugin. You should be aware of the potential ABI incompatibilities in the c++11 and c++98 libstdc++ library ( https://gcc.gnu.org/wiki/Cxx11AbiCompatibility ). Plus the fact this won't work with clang as they are ABI incompatible. On Wed, Oct 1, 2014 at 2:33 PM, B.W.H. van Beest wrote: > Hi, > > For a new plugin i'm currently writing, I'm using features of c++11. > In order to do so, I need to specify the flag -std=c++11 to the gcc > compiler. > So far, I'm only able to achieve this by adding the flag -std=c++11 to > the file "flags.make" appearing in a subdirectory of CMakeFiles in the > *build* directory tree. This works, but this flags.cmake is overwritten > every time a new configuration is done (e.g. after a change in > CMakelist.txt). > > Where can I specify compile flags that only hold for a given directory? > > Kind Regards, > Bertwim > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Wed Oct 1 22:43:38 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 04:43:38 +0200 Subject: [Paraview] -std=c++11 for a single directory? In-Reply-To: References: <542C4904.9000202@xs4all.nl> Message-ID: <542CBBDA.6010900@xs4all.nl> Triggered by your suggestion (CMake is still largely terra incognita for me), I googled a bit, finding that your suggestion boils down to adding set( CMAKE_CXX_FLAGS "-std=c++11" ) to the CMakeList.txt. It worked! Thanks. Also, I was not ware of the potential incompatibilities, so thanks for the warning. So far I haven't encountered any issues, but it is good to be aware. In the mean time, I hope ParaView will have the c++11 enabled soon. The new language features are too important to be missed! Regards, Bertweim On 10/01/2014 09:31 PM, Robert Maynard wrote: > You need to force cache the CMAKE_CXX_FLAGS variable with c++11 in the > CMakeLists.txt for the plugin. > > You should be aware of the potential ABI incompatibilities in the > c++11 and c++98 libstdc++ library ( > https://gcc.gnu.org/wiki/Cxx11AbiCompatibility ). Plus the fact this > won't work with clang as they are ABI incompatible. > > On Wed, Oct 1, 2014 at 2:33 PM, B.W.H. van Beest wrote: >> Hi, >> >> For a new plugin i'm currently writing, I'm using features of c++11. >> In order to do so, I need to specify the flag -std=c++11 to the gcc >> compiler. >> So far, I'm only able to achieve this by adding the flag -std=c++11 to >> the file "flags.make" appearing in a subdirectory of CMakeFiles in the >> *build* directory tree. This works, but this flags.cmake is overwritten >> every time a new configuration is done (e.g. after a change in >> CMakelist.txt). >> >> Where can I specify compile flags that only hold for a given directory? >> >> Kind Regards, >> Bertwim >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From ruggiero.guida at gmail.com Thu Oct 2 01:49:26 2014 From: ruggiero.guida at gmail.com (Ruggiero Guida) Date: Thu, 2 Oct 2014 09:49:26 +0400 Subject: [Paraview] Fwd: VTK interpolation help In-Reply-To: References: Message-ID: Thanks Ken. The subdivision filter you suggest does help by making the edges a bit blurred. Looking at the exact values though I have realized that it is a more fundamental issue. I am looking into other options like post-processing the contour with some kind of interpolation. Ruggiero On 29 September 2014 20:33, Moreland, Kenneth wrote: > I couldn't see the files you posted to dropbox because they were > deleted before I got a chance to see them. I also cannot even guess what > Star-CCM is doing since I haven't seen that either. > > One thing you can try is to apply the loop subdivision filter. That > filter subdivides triangles in a polygonal mesh and applies some nonlinear > smoothing to the data. To use this filter, first apply the "Extract > Surface" filter to your data (to convert it to polygons), and then apply > "Loop Subdivision." > > -Ken > > From: Ruggiero Guida > Date: Saturday, September 27, 2014 at 5:41 AM > To: Kenneth Moreland > Cc: "paraview at paraview.org" > Subject: [EXTERNAL] Re: [Paraview] Fwd: VTK interpolation help > > Thanks Ken. > > Got it. It makes sense. It seems that the only way to improve the > quality is to have a finer grid and a more detailed calculation of the > amount of radiation (the previous image included only the direct). New > images are at this link > > https://www.dropbox.com/s/z9m2nr7ybj5mqqp/finermesh.zip?dl=0 > > I was wondering whether there was a way to at least smooth the results > (see other attached image). I have looked at the filters available, but > there is no such thing. When I import these results onto StarCCM I > definitely see a smoother interpolation. > > Thanks > Ruggiero > > On 26 September 2014 19:01, Moreland, Kenneth wrote: > >> Yes, ParaView will use the triangles to interpolate values between >> points. The interpolation you are getting is exactly as I would expect >> based on your data and topology. I'm not sure what you mean by "not >> [interpolating] in the x,y directions". The triangles are in the x-y plane >> and interpolation is happening in this x-y plane. >> >> Moving into guesswork, I am imagining that you are expecting a smooth >> and fairly straight contour at some distance from the buildings. The >> reason you don't see this is due to the representation in your data. I >> notice that your data contains only two values for "RadiationOnPerson." The >> value is either 0 or 205.7. Presumably there is some contour in space where >> this field discontinuously transitions from 0 to 205.7, but there is no way >> to accurately predict where that is from the data you are providing. >> Instead, ParaView is just linearly interpolating between these values, >> which is wrong but probably the best you can do with the data provided. The >> problem is made even worse by the irregular sampling of the field. >> >> -Ken >> >> From: Ruggiero Guida >> Date: Thursday, September 25, 2014 at 10:44 PM >> To: "paraview at paraview.org" >> Subject: [EXTERNAL] [Paraview] Fwd: VTK interpolation help >> >> Dear group, >> >> I hope I will be able to find an answer to my problem here. >> >> I am not sure I understand how the interpolation works. I have >> generated a VTK file (attached) and I am trying to visualizing it in >> Paraview. The data represent the solar radiation on the ground around >> various buildings. >> >> My algorithm calculates the radiation in each node of a constrained >> delauney triangulation. The plan is to visualize this in paraview to have a >> nice smooth fillled contour. >> >> The image I get though, does not make sense to me; it seems that >> paraview is interpolating only within the triangles and not in the x,y >> directions. Am I missing something? >> >> Thanks a lot for any help >> Ruggiero >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From furutaka.kazuyoshi at jaea.go.jp Thu Oct 2 02:18:02 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Thu, 02 Oct 2014 15:18:02 +0900 (JST) Subject: [Paraview] Is the VIEW-UP vector updated automatically? Message-ID: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> Dear ParaView expert... I'm using ParaView Version 4.2.0 32-bit on linux (Fedora 20, i386). Is the view-up vector updated automatically after e.g. changing the camera position? >From Python Shell, I got the following result: ...resetting... Python 2.7.5 (default, Sep 25 2014, 13:58:10) [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 >>> from paraview.simple import * >>> box=Box() >>> Show(box) >>> cam=GetActiveCamera() >>> cam.SetPosition(0,3,3) >>> Render() >>> cam.GetViewUp() (0.0, 1.0, 0.0) >>> Is this correct behavior? Who/what routine/method is responsible for updating the vector? I'm observing a curious behavior of paraview.simple.Azimuth(); camera is NOT moving left/right. Thanks in advance. Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From lifeandfree at gmail.com Thu Oct 2 04:48:31 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Thu, 2 Oct 2014 14:48:31 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day. Sorry. Not the file sent. Attach desired. Everything worked. But there are a couple of questions. Why update the browser page when it loses the session? Starts a new process in nature. Is there any way to fix this? When you disable the client (browser), the session remains on the server to hang. How to deal with it? When you connect multiple clients, very often produces the message: "Session did not start before timeout expired. Check session logs." Add a log file with errors, unless of course it will help. What could the reason for this? Sincerely, Ilya 2014-10-01 20:09 GMT+06:00 Scott Wittenburg : > The launcher config file you sent to the list was missing a "visualizer" > entry, but those instructions have one. Other than that, are things > working properly now? When we do find problems with the instructions, we > try to fix them, but I'm not sure yet if this is one of those cases. > > Cheers, > Scott > > On Wed, Oct 1, 2014 at 6:06 AM, Ilya Sukhachev > wrote: > >> Good day. >> >> For the settings I used your instruction online >> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >> . >> Did everything there. Would you say it does not work? >> >> Ilya >> >> 2014-09-30 20:43 GMT+06:00 Scott Wittenburg > >: >> >>> Your client side request to the launcher is asking for the "visualizer" >>> application, while the launcher (according to your launcher config) doesn't >>> know about a command line to start that application. Try changing the >>> "pipeline" key under the "apps" section to "visualizer". >>> >>> Cheers, >>> Scott >>> >>> >>> On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev >>> wrote: >>> >>>> Good day! >>>> >>>> Yes, of course >>>> Attached. >>>> Also put the configuration file Apache. >>>> >>>> Ilya >>>> >>>> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg < >>>> scott.wittenburg at kitware.com>: >>>> >>>>> Can you share your launcher configuration file? It appears you may >>>>> have no "visualizer" application command line configured. >>>>> >>>>> Cheers, >>>>> Scott >>>>> >>>>> >>>>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >>>>> wrote: >>>>> >>>>>> >>>>>> And there is another question. >>>>>> Deployed software. I go to http://localhost/apps/Visualizer /. As a >>>>>> result, I see only the inscription ParaViewWeb and flailing wheel. >>>>>> And he gave me a list of errors in the console: >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1439, in dataReceived >>>>>> finishCallback(data[contentLength:]) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1668, in _finishRequestBody >>>>>> self.allContentReceived() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 1731, in allContentReceived >>>>>> req.requestReceived(command, path, version) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>> line 827, in requestReceived >>>>>> self.process() >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 189, in process >>>>>> self.render(resrc) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 238, in render >>>>>> body = resrc.render(self) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>> line 250, in render >>>>>> return m(request) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 399, in render_POST >>>>>> session = self.session_manager.createSession(payload) >>>>>> File >>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>> line 182, in createSession >>>>>> options['cmd'] = >>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>> self.config['properties']]) >>>>>> exceptions.KeyError: u'visualizer' >>>>>> Unhandled Error >>>>>> Traceback (most recent call last): >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>> line 321, in processingFailed >>>>>> % webutil.formatFailure(reason)) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>> line 425, in formatFailure >>>>>> flattenString(None, >>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 420, in flattenString >>>>>> d = flatten(request, root, io.write) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 402, in flatten >>>>>> _writeFlattenedData(state, write, result) >>>>>> --- --- >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 359, in _writeFlattenedData >>>>>> element = state.next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 326, in _flattenTree >>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>> >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 317, in _flattenTree >>>>>> element = stack[-1].next() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>> line 286, in _flattenElement >>>>>> result = root.render(request) >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>> line 184, in render >>>>>> return loader.load() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 465, in load >>>>>> self._loadedTemplate = self._loadDoc() >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>> line 446, in _loadDoc >>>>>> f = self._path.open('r') >>>>>> File >>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>> line 828, in open >>>>>> return open(self.path, mode + 'b') >>>>>> IOError: [Errno 2] No such file or directory: >>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>> >>>>>> >>>>>> In logs file error.log: >>>>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading >>>>>> from remote server returned by /paraview/, referer: >>>>>> http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>>>>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>> referer: http://localhost/apps/Visualizer/ >>>>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading >>>>>> from remote server returned by /paraview/, referer: >>>>>> http://localhost/apps/Visualizer/ >>>>>> >>>>>> >>>>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>>>> >>>>>>> Good day. >>>>>>> Thank you. >>>>>>> >>>>>>> You may be able to explain. What kind of filter is it? >>>>>>> >>>>>>> Ilya >>>>>>> >>>>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> ParaView 4.2 has been released, so that would be the latest stable >>>>>>>> version available. >>>>>>>> There is no localization per say but the filter names could be >>>>>>>> customized the way you want. >>>>>>>> >>>>>>>> For continuous live visualization it is possible but that will be a >>>>>>>> custom development. And for that you can contact Kitware for either a >>>>>>>> support contract (http://www.kitware.com/products/support.html) or >>>>>>>> an end-product development ( >>>>>>>> http://www.kitware.com/products/consulting.html). >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? < >>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>> >>>>>>>>> thank you, ok. try to understand. I put the stable version and not the >>>>>>>>> release candidate. >>>>>>>>> >>>>>>>>> But there are a few more questions. >>>>>>>>> Do files are responsible for localization? I need to replace the >>>>>>>>> language in the design parawiewweb. >>>>>>>>> And the second. Is there a possibility of the file from which the >>>>>>>>> object is loaded into the web, continuously read the data? That is to >>>>>>>>> update the image in the browser loading new data, but this is not in >>>>>>>>> the manual and automatic. >>>>>>>>> >>>>>>>>> Sincerely, >>>>>>>>> Sukhachev Ilya! >>>>>>>>> >>>>>>>>> >>>>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>>>> with Apache. >>>>>>>>>> Moreover, can you enable the development tools on your browser to >>>>>>>>>> see what kind of error you got? >>>>>>>>>> >>>>>>>>>> Did you look also at the different types of logs? Apache, >>>>>>>>>> Launcher (see config to know where you choose to put them). >>>>>>>>>> That could also give you an idea on what went wrong. >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, Sebastien >>>>>>>>>>> >>>>>>>>>>> Thank you. >>>>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>>>>>> only displayed only the green bar at the top of the window, and >>>>>>>>>>> nothing more. >>>>>>>>>>> That in this case? >>>>>>>>>>> >>>>>>>>>>> Sincerely, >>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>> >>>>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>> >>>>>>>>>>>> Moreover, the documentation that get's updated automatically >>>>>>>>>>>> can be found at the following address. (Which might be more accurate.) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>>>> >>>>>>>>>>>> This is the one you find when you go on paraview.org and go to >>>>>>>>>>>> the documentation section. >>>>>>>>>>>> >>>>>>>>>>>> Seb >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>>>> >>>>>>>>>>>>> The one thing that might not be explicit about the >>>>>>>>>>>>> ubuntu_14_04 guide might be that the script "/data/pvw/bin/ >>>>>>>>>>>>> start.sh" should be launched with a DISPLAY setup. >>>>>>>>>>>>> Otherwise, you will have to be more explicit on what you've >>>>>>>>>>>>> done and what is not working. The log files usually helps to see what >>>>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>>>> >>>>>>>>>>>>> Seb >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Good day! >>>>>>>>>>>>>> Prompt please. >>>>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>>>> Unfolded, but for some reason I can not open in the web >>>>>>>>>>>>>> browser Visualizer (http: // localhost / apps / Visualizer /) >>>>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can >>>>>>>>>>>>>> run only as 1 Ceci. >>>>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>>>> Thank you >>>>>>>>>>>>>> >>>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>> >>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> ? ?????????, >>>>>>>>>>> ??????? ????! >>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ? ?????????, >>>>>>>>> ??????? ????! >>>>>>>>> +7 912 216 72 72 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ? ?????????, >>>>>>> ??????? ????! >>>>>>> +7 912 216 72 72 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: launcher.json Type: application/json Size: 1783 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error.log Type: text/x-log Size: 14856 bytes Desc: not available URL: From lifeandfree at gmail.com Thu Oct 2 04:51:20 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Thu, 2 Oct 2014 14:51:20 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day to all! Can someone help and filters are we talking about? Sincerely, Ilya 2014-09-29 10:30 GMT+06:00 ???? ??????? : > Good day. > Thank you. > > You may be able to explain. What kind of filter is it? > > Ilya > > 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < > sebastien.jourdain at kitware.com>: > >> ParaView 4.2 has been released, so that would be the latest stable >> version available. >> There is no localization per say but the filter names could be customized >> the way you want. >> >> For continuous live visualization it is possible but that will be a >> custom development. And for that you can contact Kitware for either a >> support contract (http://www.kitware.com/products/support.html) or an >> end-product development (http://www.kitware.com/products/consulting.html >> ). >> >> Seb >> >> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >> wrote: >> >>> thank you, ok. try to understand. I put the stable version and not the >>> release candidate. >>> >>> But there are a few more questions. >>> Do files are responsible for localization? I need to replace the >>> language in the design parawiewweb. >>> And the second. Is there a possibility of the file from which the object is >>> loaded into the web, continuously read the data? That is to update the >>> image in the browser loading new data, but this is not in the manual and >>> automatic. >>> >>> Sincerely, >>> Sukhachev Ilya! >>> >>> >>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> The top bar is not green anymore. Try to replace the directory /lib, >>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>> Apache. >>>> Moreover, can you enable the development tools on your browser to see >>>> what kind of error you got? >>>> >>>> Did you look also at the different types of logs? Apache, Launcher (see >>>> config to know where you choose to put them). >>>> That could also give you an idea on what went wrong. >>>> >>>> Seb >>>> >>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>> wrote: >>>> >>>>> Hi, Sebastien >>>>> >>>>> Thank you. >>>>> I just took advantage of this documentation and to deploy. >>>>> I ran the script /data/pvw/bin/start.sh. >>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>> only displayed only the green bar at the top of the window, and >>>>> nothing more. >>>>> That in this case? >>>>> >>>>> Sincerely, >>>>> Sukhachev Ilya! >>>>> >>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> Moreover, the documentation that get's updated automatically can be >>>>>> found at the following address. (Which might be more accurate.) >>>>>> >>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>> >>>>>> This is the one you find when you go on paraview.org and go to the >>>>>> documentation section. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>> >>>>>>> Hi Sukhachev, >>>>>>> >>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>> launched with a DISPLAY setup. >>>>>>> Otherwise, you will have to be more explicit on what you've done and >>>>>>> what is not working. The log files usually helps to see what was skipped >>>>>>> from the documentation. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>> lifeandfree at gmail.com> wrote: >>>>>>> >>>>>>>> Good day! >>>>>>>> Prompt please. >>>>>>>> I used the instructions for deployment on Linux Ubuntu Paraviewweb >>>>>>>> (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>> When deployment by using the ( >>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>> as 1 Ceci. >>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>> Thank you >>>>>>>> >>>>>>>> Sincerely, >>>>>>>> Sukhachev Ilya! >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lifeandfree at gmail.com Thu Oct 2 05:07:05 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Thu, 2 Oct 2014 15:07:05 +0600 Subject: [Paraview] Edit xmf In-Reply-To: References: Message-ID: Good day to all! And what to do with the problem when it is not stored in the format xmf set of lines, but only one? Sincerely, Ilya 2014-09-30 19:24 GMT+06:00 Ilya Sukhachev : > Retains only one line, which is isolated > > Ilya > > 2014-09-30 18:00 GMT+06:00 Jason Fleming < > jason.fleming at seahorsecoastal.com>: > >> Can you send a sample file? >> >> Cheers >> Jason >> >> On Tue, Sep 30, 2014 at 1:08 AM, Ilya Sukhachev >> wrote: >> >>> Good day to all! >>> >>> Please tell me how to do. >>> I need to create a simple shape of the lines in ParaView. Further save >>> the file and open it in ParaViewWeb. But there is a condition necessary >>> to keep in the text file, for example, in the format type * .xmf. It is >>> necessary that manually edit the file. And to boot again in ParaViewWeb. >>> And also. Why when I try to "File -> Save Data", retained only one line, rather >>> than the entire set of lines? >>> >>> Sincerely, Ilya >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> >> >> -- >> Dr. Jason G. Fleming >> Chief Engineer, Seahorse Coastal Consulting >> 3103 Mandy Ln >> Morehead City, NC 28557 >> Tel: (252) 726-6323 >> Mobile: (252) 269-0962 >> Web: http://www.seahorsecoastal.com >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: line.xmf Type: application/octet-stream Size: 882 bytes Desc: not available URL: From bwvb at xs4all.nl Thu Oct 2 06:44:45 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 12:44:45 +0200 Subject: [Paraview] Property Panel and Inheritance? Message-ID: <542D2C9D.5010506@xs4all.nl> Hello, I'm struggling with getting the properties panel right for a new Source defined in plugin that I'm writing. In the class below, I'm extending the VTK class for a rectangular box, vtkCubeSource. The class also derives from another class, that has the well known method "foo". I have made corresponding changes to the server manager file (xml), given below. In the xml-file, I can specify the panel entries for the vtkCubeSource, referring to the methods of this vtk class which are available via inheritance, for instance "SetXLength(double)". However, when I do the same for the method "foo(int)" of the other base class, ParaView bombs, telling me that: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find requested method: "foo" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} Argument 1 = string_value {foo} Argument 2 = int32_value {1024} $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ The problem is gone when I provide the derived class also with a method "foo", which calls the "foo" of the base class. In short, I can refer, in the panel, to the methods of vtkCubeSource (as expected due to inheritance), but not for the other base class. What am I overlooking here, and what do I need to do to have the expected inheritance? Your view Kind Regards, Bertwim --------------------- This is my class: ===================================== class sphBoxSource : public vtkCubeSource , public SPHParticleProps { public: static sphBoxSource* New(); vtkTypeMacro(sphBoxSource,vtkCubeSource); public: sphBoxSource( double, double, double ); ~sphBoxSource(); public: // testing purposes only void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties pane,: Why can I can not just inherit the method "foo"? }; ======================================= The server manager configuration is taken from "sources.xml" that comes with ParaView (4.2), but extended with a property for "foo". ======================================= ... This property specifies the length of the box in the X direction. .... Just for testing. Does nothing. From livia.barazzetti at istb.unibe.ch Thu Oct 2 08:15:46 2014 From: livia.barazzetti at istb.unibe.ch (livia.barazzetti at istb.unibe.ch) Date: Thu, 2 Oct 2014 12:15:46 +0000 Subject: [Paraview] problem wirh python shell in Paraview 4.2.0 Message-ID: Hi all, I just downloaded the new version of Paraview, and I am very curious about the new features. Unfortunately I cannot use the new python trace, because as soon I click ok in the trace window, the application crashes. Actually, the problem is already at startup, opening a python shell I get this error: Python 2.7.3 (default, Sep 23 2014, 20:23:11) [MSC v.1500 64 bit (AMD64)] on win32 >>> from paraview.simple import * Traceback (most recent call last): File "", line 1, in File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\simple.py", line 39, in import servermanager File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 3184, in __initialize() File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 3175, in __initialize c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 1932, in __init__ _createModules(self.Modules) File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 2564, in _createModules m.filters = createModule('filters') File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 2626, in createModule if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' I am working on Windows 7, 64 bit (with paraview 4.2.0 64 bit) Regards, Livia -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Oct 2 08:18:35 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 08:18:35 -0400 Subject: [Paraview] problem wirh python shell in Paraview 4.2.0 In-Reply-To: References: Message-ID: Thanks for reporting. We'll test it out. BTW, do you have any plugins loaded when you're trying to one the Python shell? Utkarsh On Thu, Oct 2, 2014 at 8:15 AM, wrote: > Hi all, > > I just downloaded the new version of Paraview, and I am very curious about > the new features. Unfortunately I cannot use the new python trace, because > as soon I click ok in the trace window, the application crashes. > > Actually, the problem is already at startup, opening a python shell I get > this error: > > > > Python 2.7.3 (default, Sep 23 2014, 20:23:11) [MSC v.1500 64 bit (AMD64)] on > win32 > >>>> from paraview.simple import * > > Traceback (most recent call last): > > File "", line 1, in > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\simple.py", line 39, in > > > import servermanager > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 3184, > in > > __initialize() > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 3175, > in __initialize > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 1932, > in __init__ > > _createModules(self.Modules) > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 2564, > in _createModules > > m.filters = createModule('filters') > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line 2626, > in createModule > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > > > > I am working on Windows 7, 64 bit (with paraview 4.2.0 64 bit) > > Regards, > > Livia > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Thu Oct 2 08:23:14 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 08:23:14 -0400 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: <542D2C9D.5010506@xs4all.nl> References: <542D2C9D.5010506@xs4all.nl> Message-ID: I can't remember if the wrapping code can handle multiple inheritance. If you removed the second superclass, does that work? Also look the sphBoxSourceClientServer.h file generated in your build directory. That will indicate which methods from this class are getting wrapped and which ones aren't. Utkarsh On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: > Hello, I'm struggling with getting the properties panel right for a new > Source defined in plugin that I'm writing. > > In the class below, I'm extending the VTK class for a rectangular box, > vtkCubeSource. The class also derives from another class, > that has the well known method "foo". I have made corresponding > changes to the server manager file (xml), given below. > > In the xml-file, I can specify the panel entries for the vtkCubeSource, > referring to the methods of this vtk class which are available via > inheritance, for instance "SetXLength(double)". However, when I do the > same for the method "foo(int)" of the other base class, ParaView bombs, > telling me that: > > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ > tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find > requested method: "foo" > or the method was called with incorrect arguments. > > while processing > Message 0 = Invoke > Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} > Argument 1 = string_value {foo} > Argument 2 = int32_value {1024} > $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ > > The problem is gone when I provide the derived class also with a method > "foo", which calls the "foo" of the base class. > In short, I can refer, in the panel, to the methods of vtkCubeSource (as > expected due to inheritance), but not for the other base class. > What am I overlooking here, and what do I need to do to have the > expected inheritance? > > Your view > Kind Regards, > Bertwim > --------------------- > > > This is my class: > ===================================== > class sphBoxSource : public vtkCubeSource > , public SPHParticleProps > { > public: > static sphBoxSource* New(); > vtkTypeMacro(sphBoxSource,vtkCubeSource); > > public: > sphBoxSource( double, double, double ); > ~sphBoxSource(); > > public: // testing purposes only > void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties > pane,: Why can I can not just inherit the method "foo"? > }; > ======================================= > > The server manager configuration is taken from "sources.xml" that comes > with ParaView (4.2), but extended with a property for "foo". > > ======================================= > > > > label="SPHBox" > name="SPHBoxSource"> > ... > command="SetXLength" > default_values="10.0" > name="XLength" > number_of_elements="1" > panel_visibility="default"> > > This property specifies the length of the box in > the X direction. > > > .... > > > default_values="1024" > name="foobar" > number_of_elements="1"> > > Just for testing. Does nothing. > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Thu Oct 2 09:20:10 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 15:20:10 +0200 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: References: <542D2C9D.5010506@xs4all.nl> Message-ID: <542D510A.5030706@xs4all.nl> It seems to work. Inheritance of the vtkCubeSource methods just works. Also when I reverse the inheritance order, or when I have single inheritance (of vtkCubeSource), in the xml-file I can just refer to the methods of the base class vtkCubeSource (say SetLength()) and it works. But not so for the oher base class! So I *think* I am using the two baseclasses the same way, the effect however, is asymmetrial. I looked, as you suggested, into sphBoxSourceClientServer.h The methods of the baseclasses (vtkCubeSource), e.g. SetXLength(), do not show-up there either. But it works, so that might not be the place where to look. Any other ideas? Regards, Bertwim On 10/02/2014 02:23 PM, Utkarsh Ayachit wrote: > I can't remember if the wrapping code can handle multiple inheritance. > If you removed the second superclass, does that work? > > Also look the sphBoxSourceClientServer.h file generated in your build > directory. That will indicate which methods from this class are > getting wrapped and which ones aren't. > > Utkarsh > > On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: >> Hello, I'm struggling with getting the properties panel right for a new >> Source defined in plugin that I'm writing. >> >> In the class below, I'm extending the VTK class for a rectangular box, >> vtkCubeSource. The class also derives from another class, >> that has the well known method "foo". I have made corresponding >> changes to the server manager file (xml), given below. >> >> In the xml-file, I can specify the panel entries for the vtkCubeSource, >> referring to the methods of this vtk class which are available via >> inheritance, for instance "SetXLength(double)". However, when I do the >> same for the method "foo(int)" of the other base class, ParaView bombs, >> telling me that: >> >> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >> tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find >> requested method: "foo" >> or the method was called with incorrect arguments. >> >> while processing >> Message 0 = Invoke >> Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} >> Argument 1 = string_value {foo} >> Argument 2 = int32_value {1024} >> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >> >> The problem is gone when I provide the derived class also with a method >> "foo", which calls the "foo" of the base class. >> In short, I can refer, in the panel, to the methods of vtkCubeSource (as >> expected due to inheritance), but not for the other base class. >> What am I overlooking here, and what do I need to do to have the >> expected inheritance? >> >> Your view >> Kind Regards, >> Bertwim >> --------------------- >> >> >> This is my class: >> ===================================== >> class sphBoxSource : public vtkCubeSource >> , public SPHParticleProps >> { >> public: >> static sphBoxSource* New(); >> vtkTypeMacro(sphBoxSource,vtkCubeSource); >> >> public: >> sphBoxSource( double, double, double ); >> ~sphBoxSource(); >> >> public: // testing purposes only >> void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties >> pane,: Why can I can not just inherit the method "foo"? >> }; >> ======================================= >> >> The server manager configuration is taken from "sources.xml" that comes >> with ParaView (4.2), but extended with a property for "foo". >> >> ======================================= >> >> >> >> > label="SPHBox" >> name="SPHBoxSource"> >> ... >> > command="SetXLength" >> default_values="10.0" >> name="XLength" >> number_of_elements="1" >> panel_visibility="default"> >> >> This property specifies the length of the box in >> the X direction. >> >> >> .... >> >> >> > default_values="1024" >> name="foobar" >> number_of_elements="1"> >> >> Just for testing. Does nothing. >> >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Oct 2 09:24:57 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 09:24:57 -0400 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: <542D510A.5030706@xs4all.nl> References: <542D2C9D.5010506@xs4all.nl> <542D510A.5030706@xs4all.nl> Message-ID: It will only warp the 1 base. I'd suggest using a proxy pattern rather than multiple inheritance. On Thu, Oct 2, 2014 at 9:20 AM, B.W.H. van Beest wrote: > It seems to work. Inheritance of the vtkCubeSource methods just works. > Also when I reverse the inheritance order, or when I have single > inheritance (of vtkCubeSource), in the xml-file I can just refer to the > methods of the base class vtkCubeSource (say SetLength()) and it works. > But not so for the oher base class! > > So I *think* I am using the two baseclasses the same way, the effect > however, is asymmetrial. > > I looked, as you suggested, into sphBoxSourceClientServer.h The > methods of the baseclasses (vtkCubeSource), e.g. SetXLength(), do not > show-up there either. But it works, so that might not be the place where > to look. > > Any other ideas? > > Regards, > Bertwim > > > > On 10/02/2014 02:23 PM, Utkarsh Ayachit wrote: >> I can't remember if the wrapping code can handle multiple inheritance. >> If you removed the second superclass, does that work? >> >> Also look the sphBoxSourceClientServer.h file generated in your build >> directory. That will indicate which methods from this class are >> getting wrapped and which ones aren't. >> >> Utkarsh >> >> On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: >>> Hello, I'm struggling with getting the properties panel right for a new >>> Source defined in plugin that I'm writing. >>> >>> In the class below, I'm extending the VTK class for a rectangular box, >>> vtkCubeSource. The class also derives from another class, >>> that has the well known method "foo". I have made corresponding >>> changes to the server manager file (xml), given below. >>> >>> In the xml-file, I can specify the panel entries for the vtkCubeSource, >>> referring to the methods of this vtk class which are available via >>> inheritance, for instance "SetXLength(double)". However, when I do the >>> same for the method "foo(int)" of the other base class, ParaView bombs, >>> telling me that: >>> >>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>> tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find >>> requested method: "foo" >>> or the method was called with incorrect arguments. >>> >>> while processing >>> Message 0 = Invoke >>> Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} >>> Argument 1 = string_value {foo} >>> Argument 2 = int32_value {1024} >>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>> >>> The problem is gone when I provide the derived class also with a method >>> "foo", which calls the "foo" of the base class. >>> In short, I can refer, in the panel, to the methods of vtkCubeSource (as >>> expected due to inheritance), but not for the other base class. >>> What am I overlooking here, and what do I need to do to have the >>> expected inheritance? >>> >>> Your view >>> Kind Regards, >>> Bertwim >>> --------------------- >>> >>> >>> This is my class: >>> ===================================== >>> class sphBoxSource : public vtkCubeSource >>> , public SPHParticleProps >>> { >>> public: >>> static sphBoxSource* New(); >>> vtkTypeMacro(sphBoxSource,vtkCubeSource); >>> >>> public: >>> sphBoxSource( double, double, double ); >>> ~sphBoxSource(); >>> >>> public: // testing purposes only >>> void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties >>> pane,: Why can I can not just inherit the method "foo"? >>> }; >>> ======================================= >>> >>> The server manager configuration is taken from "sources.xml" that comes >>> with ParaView (4.2), but extended with a property for "foo". >>> >>> ======================================= >>> >>> >>> >>> >> label="SPHBox" >>> name="SPHBoxSource"> >>> ... >>> >> command="SetXLength" >>> default_values="10.0" >>> name="XLength" >>> number_of_elements="1" >>> panel_visibility="default"> >>> >>> This property specifies the length of the box in >>> the X direction. >>> >>> >>> .... >>> >>> >>> >> default_values="1024" >>> name="foobar" >>> number_of_elements="1"> >>> >>> Just for testing. Does nothing. >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Thu Oct 2 09:53:43 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 15:53:43 +0200 Subject: [Paraview] default representation? Message-ID: <542D58E7.1020905@xs4all.nl> Hello, I noticed that sources like a box, sphere etc., are always displayed initially with a surface representation, after which ione can set it manually to something else, e.g. a wireframe. Where is this preference being set? I cannot find it in the sources.xml file or in any of the other xml files, but maybe I don't recognise it. Background of this is that I would like to change this default behaviour, in particular for some new sources I'm creating in a plugin. (The sources that are derived from the standard ones.) Kind Regards, Bertwim From kmorel at sandia.gov Thu Oct 2 10:55:16 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 2 Oct 2014 14:55:16 +0000 Subject: [Paraview] default representation? Message-ID: The default representation is based more on the data type than the filter setup. I forget all the rules, but I believe that structured data types (like uniform and non-uniform rectilinear grids and curvilinear grids) default to outline. Unstructured data types (like poly data or unstructured grids) default to surface unless the size is larger than some threshold (which can be changed in settings). Multiblock data sets default to whatever is appropriate for the data type in the blocks. The rational for this behavior is that an unstructured data type likely represents some geometry of importance whereas a regular grid more likely represents some region in space where the relevant structure is internal. -Ken On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >Hello, > >I noticed that sources like a box, sphere etc., are always displayed >initially with a surface representation, after which ione can set it >manually to something else, e.g. a wireframe. Where is this preference >being set? I cannot find it in the sources.xml file or in any of the >other xml files, but maybe I don't recognise it. > >Background of this is that I would like to change this default >behaviour, in particular for some new sources I'm creating in a plugin. >(The sources that are derived from the standard ones.) > >Kind Regards, >Bertwim > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From jfeng at optomec.com Thu Oct 2 11:06:12 2014 From: jfeng at optomec.com (James Feng) Date: Thu, 2 Oct 2014 10:06:12 -0500 Subject: [Paraview] problem wirh python shell in Paraview 4.2.0 In-Reply-To: References: Message-ID: <8ff8fd1ed7819fd5bb9a1898934858c8@mail.gmail.com> Hi, I'm using paraview (4.1.0) with OpenFOAM 2.3.0 and "parafoam". I noticed my "python shell" under my parafoam "tool" menu is not activated (with an appearance "gray"). I wonder if you can tell me what I need to do to turn the python shell on. I tried with "makeParaView -python" and it didn't go through the "make". So I guess that is not a legitimate syntax. Many thanks. James -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit Sent: Thursday, October 02, 2014 7:19 AM To: Livia Barazzetti Cc: ParaView Subject: Re: [Paraview] problem wirh python shell in Paraview 4.2.0 Thanks for reporting. We'll test it out. BTW, do you have any plugins loaded when you're trying to one the Python shell? Utkarsh On Thu, Oct 2, 2014 at 8:15 AM, wrote: > Hi all, > > I just downloaded the new version of Paraview, and I am very curious > about the new features. Unfortunately I cannot use the new python > trace, because as soon I click ok in the trace window, the application crashes. > > Actually, the problem is already at startup, opening a python shell I > get this error: > > > > Python 2.7.3 (default, Sep 23 2014, 20:23:11) [MSC v.1500 64 bit > (AMD64)] on > win32 > >>>> from paraview.simple import * > > Traceback (most recent call last): > > File "", line 1, in > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\simple.py", line 39, in > > > import servermanager > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line > 3184, in > > __initialize() > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line > 3175, in __initialize > > c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line > 1932, in __init__ > > _createModules(self.Modules) > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line > 2564, in _createModules > > m.filters = createModule('filters') > > File "C:\Program Files (x86)\ParaView > 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line > 2626, in createModule > > if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ > > AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' > > > > I am working on Windows 7, 64 bit (with paraview 4.2.0 64 bit) > > Regards, > > Livia > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From scott.wittenburg at kitware.com Thu Oct 2 11:10:14 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 2 Oct 2014 09:10:14 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: On Thu, Oct 2, 2014 at 2:48 AM, Ilya Sukhachev wrote: > Good day. > > Sorry. Not the file sent. > Attach desired. > Everything worked. > But there are a couple of questions. > > Glad you got something working. > Why update the browser page when it loses the session? Starts a new > process in nature. Is there any way to fix this? > > I'm not sure what you are asking here. What do you mean by "update the browser page"? > When you disable the client (browser), the session remains on the server to > hang. How to deal with it? > > See the index.html for your particular application. The body tag has event handlers attached that will call the stop method when you close the tab or hit the back button. In that stop method, you can do what you like, like calling the rpc method "application.exit". > When you connect multiple clients, very often produces the message: > "Session did not start before timeout expired. Check session logs." > Add a log file with errors, unless of course it will help. What could the > reason for this? > > I looked briefly at your log files, and I'm not sure what could be going on. Can all your clients reach the host where the pvpython processes are running? Cheers, Scott > Sincerely, Ilya > > 2014-10-01 20:09 GMT+06:00 Scott Wittenburg > : > >> The launcher config file you sent to the list was missing a "visualizer" >> entry, but those instructions have one. Other than that, are things >> working properly now? When we do find problems with the instructions, we >> try to fix them, but I'm not sure yet if this is one of those cases. >> >> Cheers, >> Scott >> >> On Wed, Oct 1, 2014 at 6:06 AM, Ilya Sukhachev >> wrote: >> >>> Good day. >>> >>> For the settings I used your instruction online >>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>> . >>> Did everything there. Would you say it does not work? >>> >>> Ilya >>> >>> 2014-09-30 20:43 GMT+06:00 Scott Wittenburg < >>> scott.wittenburg at kitware.com>: >>> >>>> Your client side request to the launcher is asking for the "visualizer" >>>> application, while the launcher (according to your launcher config) doesn't >>>> know about a command line to start that application. Try changing the >>>> "pipeline" key under the "apps" section to "visualizer". >>>> >>>> Cheers, >>>> Scott >>>> >>>> >>>> On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev >>>> wrote: >>>> >>>>> Good day! >>>>> >>>>> Yes, of course >>>>> Attached. >>>>> Also put the configuration file Apache. >>>>> >>>>> Ilya >>>>> >>>>> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg < >>>>> scott.wittenburg at kitware.com>: >>>>> >>>>>> Can you share your launcher configuration file? It appears you may >>>>>> have no "visualizer" application command line configured. >>>>>> >>>>>> Cheers, >>>>>> Scott >>>>>> >>>>>> >>>>>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> And there is another question. >>>>>>> Deployed software. I go to http://localhost/apps/Visualizer /. As a >>>>>>> result, I see only the inscription ParaViewWeb and flailing wheel. >>>>>>> And he gave me a list of errors in the console: >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1439, in dataReceived >>>>>>> finishCallback(data[contentLength:]) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1668, in _finishRequestBody >>>>>>> self.allContentReceived() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 1731, in allContentReceived >>>>>>> req.requestReceived(command, path, version) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>> line 827, in requestReceived >>>>>>> self.process() >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 189, in process >>>>>>> self.render(resrc) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 238, in render >>>>>>> body = resrc.render(self) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>> line 250, in render >>>>>>> return m(request) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 399, in render_POST >>>>>>> session = self.session_manager.createSession(payload) >>>>>>> File >>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>> line 182, in createSession >>>>>>> options['cmd'] = >>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>> self.config['properties']]) >>>>>>> exceptions.KeyError: u'visualizer' >>>>>>> Unhandled Error >>>>>>> Traceback (most recent call last): >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>> line 321, in processingFailed >>>>>>> % webutil.formatFailure(reason)) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>> line 425, in formatFailure >>>>>>> flattenString(None, >>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 420, in flattenString >>>>>>> d = flatten(request, root, io.write) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 402, in flatten >>>>>>> _writeFlattenedData(state, write, result) >>>>>>> --- --- >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 359, in _writeFlattenedData >>>>>>> element = state.next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 326, in _flattenTree >>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>> >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 317, in _flattenTree >>>>>>> element = stack[-1].next() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>> line 286, in _flattenElement >>>>>>> result = root.render(request) >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>> line 184, in render >>>>>>> return loader.load() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 465, in load >>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>> line 446, in _loadDoc >>>>>>> f = self._path.open('r') >>>>>>> File >>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>> line 828, in open >>>>>>> return open(self.path, mode + 'b') >>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>> >>>>>>> >>>>>>> In logs file error.log: >>>>>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>>>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading >>>>>>> from remote server returned by /paraview/, referer: >>>>>>> http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>>>>>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>>>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading >>>>>>> from remote server returned by /paraview/, referer: >>>>>>> http://localhost/apps/Visualizer/ >>>>>>> >>>>>>> >>>>>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>>>>> >>>>>>>> Good day. >>>>>>>> Thank you. >>>>>>>> >>>>>>>> You may be able to explain. What kind of filter is it? >>>>>>>> >>>>>>>> Ilya >>>>>>>> >>>>>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>> >>>>>>>>> ParaView 4.2 has been released, so that would be the latest stable >>>>>>>>> version available. >>>>>>>>> There is no localization per say but the filter names could be >>>>>>>>> customized the way you want. >>>>>>>>> >>>>>>>>> For continuous live visualization it is possible but that will be >>>>>>>>> a custom development. And for that you can contact Kitware for either a >>>>>>>>> support contract (http://www.kitware.com/products/support.html) >>>>>>>>> or an end-product development ( >>>>>>>>> http://www.kitware.com/products/consulting.html). >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? < >>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> thank you, ok. try to understand. I put the stable version and >>>>>>>>>> not the release candidate. >>>>>>>>>> >>>>>>>>>> But there are a few more questions. >>>>>>>>>> Do files are responsible for localization? I need to replace the >>>>>>>>>> language in the design parawiewweb. >>>>>>>>>> And the second. Is there a possibility of the file from which the >>>>>>>>>> object is loaded into the web, continuously read the data? That >>>>>>>>>> is to update the image in the browser loading new data, but this >>>>>>>>>> is not in the manual and automatic. >>>>>>>>>> >>>>>>>>>> Sincerely, >>>>>>>>>> Sukhachev Ilya! >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>> >>>>>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>>>>> with Apache. >>>>>>>>>>> Moreover, can you enable the development tools on your browser >>>>>>>>>>> to see what kind of error you got? >>>>>>>>>>> >>>>>>>>>>> Did you look also at the different types of logs? Apache, >>>>>>>>>>> Launcher (see config to know where you choose to put them). >>>>>>>>>>> That could also give you an idea on what went wrong. >>>>>>>>>>> >>>>>>>>>>> Seb >>>>>>>>>>> >>>>>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, Sebastien >>>>>>>>>>>> >>>>>>>>>>>> Thank you. >>>>>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>>>>>>> only displayed only the green bar at the top of the window, and >>>>>>>>>>>> nothing more. >>>>>>>>>>>> That in this case? >>>>>>>>>>>> >>>>>>>>>>>> Sincerely, >>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>> >>>>>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>> >>>>>>>>>>>>> Moreover, the documentation that get's updated automatically >>>>>>>>>>>>> can be found at the following address. (Which might be more accurate.) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>>>>> >>>>>>>>>>>>> This is the one you find when you go on paraview.org and go >>>>>>>>>>>>> to the documentation section. >>>>>>>>>>>>> >>>>>>>>>>>>> Seb >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>>>>> >>>>>>>>>>>>>> The one thing that might not be explicit about the >>>>>>>>>>>>>> ubuntu_14_04 guide might be that the script "/data/pvw/bin/ >>>>>>>>>>>>>> start.sh" should be launched with a DISPLAY setup. >>>>>>>>>>>>>> Otherwise, you will have to be more explicit on what you've >>>>>>>>>>>>>> done and what is not working. The log files usually helps to see what >>>>>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Seb >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Good day! >>>>>>>>>>>>>>> Prompt please. >>>>>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>>>>> Unfolded, but for some reason I can not open in the web >>>>>>>>>>>>>>> browser Visualizer (http: // localhost / apps / Visualizer >>>>>>>>>>>>>>> /) >>>>>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can >>>>>>>>>>>>>>> run only as 1 Ceci. >>>>>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>>>>> Thank you >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki >>>>>>>>>>>>>>> at: http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> ? ?????????, >>>>>>>>>>>> ??????? ????! >>>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> ? ?????????, >>>>>>>>>> ??????? ????! >>>>>>>>>> +7 912 216 72 72 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ? ?????????, >>>>>>>> ??????? ????! >>>>>>>> +7 912 216 72 72 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ? ?????????, >>>>>>> ??????? ????! >>>>>>> +7 912 216 72 72 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>> http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Thu Oct 2 11:15:33 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 17:15:33 +0200 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: References: <542D2C9D.5010506@xs4all.nl> <542D510A.5030706@xs4all.nl> Message-ID: <542D6C15.5000100@xs4all.nl> Hi Utkarsh, Not sure how to do that, really in Paraview. The relationshop and dynamics between what is in the xml file, source files I write and generated files by mysterious macros make me still a bit uncomfortable in finding my way in ParaView. Maybe you could a bit more verbose? Regards, Bertwim On 10/02/2014 03:24 PM, Utkarsh Ayachit wrote: > It will only warp the 1 base. I'd suggest using a proxy pattern rather > than multiple inheritance. > > On Thu, Oct 2, 2014 at 9:20 AM, B.W.H. van Beest wrote: >> It seems to work. Inheritance of the vtkCubeSource methods just works. >> Also when I reverse the inheritance order, or when I have single >> inheritance (of vtkCubeSource), in the xml-file I can just refer to the >> methods of the base class vtkCubeSource (say SetLength()) and it works. >> But not so for the oher base class! >> >> So I *think* I am using the two baseclasses the same way, the effect >> however, is asymmetrial. >> >> I looked, as you suggested, into sphBoxSourceClientServer.h The >> methods of the baseclasses (vtkCubeSource), e.g. SetXLength(), do not >> show-up there either. But it works, so that might not be the place where >> to look. >> >> Any other ideas? >> >> Regards, >> Bertwim >> >> >> >> On 10/02/2014 02:23 PM, Utkarsh Ayachit wrote: >>> I can't remember if the wrapping code can handle multiple inheritance. >>> If you removed the second superclass, does that work? >>> >>> Also look the sphBoxSourceClientServer.h file generated in your build >>> directory. That will indicate which methods from this class are >>> getting wrapped and which ones aren't. >>> >>> Utkarsh >>> >>> On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: >>>> Hello, I'm struggling with getting the properties panel right for a new >>>> Source defined in plugin that I'm writing. >>>> >>>> In the class below, I'm extending the VTK class for a rectangular box, >>>> vtkCubeSource. The class also derives from another class, >>>> that has the well known method "foo". I have made corresponding >>>> changes to the server manager file (xml), given below. >>>> >>>> In the xml-file, I can specify the panel entries for the vtkCubeSource, >>>> referring to the methods of this vtk class which are available via >>>> inheritance, for instance "SetXLength(double)". However, when I do the >>>> same for the method "foo(int)" of the other base class, ParaView bombs, >>>> telling me that: >>>> >>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>> tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find >>>> requested method: "foo" >>>> or the method was called with incorrect arguments. >>>> >>>> while processing >>>> Message 0 = Invoke >>>> Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} >>>> Argument 1 = string_value {foo} >>>> Argument 2 = int32_value {1024} >>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>> >>>> The problem is gone when I provide the derived class also with a method >>>> "foo", which calls the "foo" of the base class. >>>> In short, I can refer, in the panel, to the methods of vtkCubeSource (as >>>> expected due to inheritance), but not for the other base class. >>>> What am I overlooking here, and what do I need to do to have the >>>> expected inheritance? >>>> >>>> Your view >>>> Kind Regards, >>>> Bertwim >>>> --------------------- >>>> >>>> >>>> This is my class: >>>> ===================================== >>>> class sphBoxSource : public vtkCubeSource >>>> , public SPHParticleProps >>>> { >>>> public: >>>> static sphBoxSource* New(); >>>> vtkTypeMacro(sphBoxSource,vtkCubeSource); >>>> >>>> public: >>>> sphBoxSource( double, double, double ); >>>> ~sphBoxSource(); >>>> >>>> public: // testing purposes only >>>> void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties >>>> pane,: Why can I can not just inherit the method "foo"? >>>> }; >>>> ======================================= >>>> >>>> The server manager configuration is taken from "sources.xml" that comes >>>> with ParaView (4.2), but extended with a property for "foo". >>>> >>>> ======================================= >>>> >>>> >>>> >>>> >>> label="SPHBox" >>>> name="SPHBoxSource"> >>>> ... >>>> >>> command="SetXLength" >>>> default_values="10.0" >>>> name="XLength" >>>> number_of_elements="1" >>>> panel_visibility="default"> >>>> >>>> This property specifies the length of the box in >>>> the X direction. >>>> >>>> >>>> .... >>>> >>>> >>>> >>> default_values="1024" >>>> name="foobar" >>>> number_of_elements="1"> >>>> >>>> Just for testing. Does nothing. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview > From scott.wittenburg at kitware.com Thu Oct 2 11:19:13 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 2 Oct 2014 09:19:13 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: You can specify which filters you would like to make available to ParaViewWeb using the "--proxies" argument to the pv_web_visualizer.py. By default ParaViewWeb can use all the filters listed in "defaultProxies.json", which is located in your build or install tree under site-packages/paraview/web/. You can use this one as an example to create your own. You can find out about the filters by looking at filters.xml in the source tree (ParaViewCore/ServerManager/SMApplication/Resources/). You can read more about the filters on the wiki: http://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_filters Hope this helps. Cheers, Scott On Thu, Oct 2, 2014 at 2:51 AM, Ilya Sukhachev wrote: > Good day to all! > > Can someone help and filters are we talking about? > > Sincerely, Ilya > > 2014-09-29 10:30 GMT+06:00 ???? ??????? : > >> Good day. >> Thank you. >> >> You may be able to explain. What kind of filter is it? >> >> Ilya >> >> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >> sebastien.jourdain at kitware.com>: >> >>> ParaView 4.2 has been released, so that would be the latest stable >>> version available. >>> There is no localization per say but the filter names could be >>> customized the way you want. >>> >>> For continuous live visualization it is possible but that will be a >>> custom development. And for that you can contact Kitware for either a >>> support contract (http://www.kitware.com/products/support.html) or an >>> end-product development (http://www.kitware.com/products/consulting.html >>> ). >>> >>> Seb >>> >>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>> wrote: >>> >>>> thank you, ok. try to understand. I put the stable version and not the >>>> release candidate. >>>> >>>> But there are a few more questions. >>>> Do files are responsible for localization? I need to replace the >>>> language in the design parawiewweb. >>>> And the second. Is there a possibility of the file from which the >>>> object is loaded into the web, continuously read the data? That is to >>>> update the image in the browser loading new data, but this is not in >>>> the manual and automatic. >>>> >>>> Sincerely, >>>> Sukhachev Ilya! >>>> >>>> >>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>> sebastien.jourdain at kitware.com>: >>>> >>>>> The top bar is not green anymore. Try to replace the directory /lib, >>>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>>> Apache. >>>>> Moreover, can you enable the development tools on your browser to see >>>>> what kind of error you got? >>>>> >>>>> Did you look also at the different types of logs? Apache, Launcher >>>>> (see config to know where you choose to put them). >>>>> That could also give you an idea on what went wrong. >>>>> >>>>> Seb >>>>> >>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>>> wrote: >>>>> >>>>>> Hi, Sebastien >>>>>> >>>>>> Thank you. >>>>>> I just took advantage of this documentation and to deploy. >>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>> only displayed only the green bar at the top of the window, and >>>>>> nothing more. >>>>>> That in this case? >>>>>> >>>>>> Sincerely, >>>>>> Sukhachev Ilya! >>>>>> >>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>> sebastien.jourdain at kitware.com>: >>>>>> >>>>>>> Moreover, the documentation that get's updated automatically can be >>>>>>> found at the following address. (Which might be more accurate.) >>>>>>> >>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>> >>>>>>> This is the one you find when you go on paraview.org and go to the >>>>>>> documentation section. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>> >>>>>>>> Hi Sukhachev, >>>>>>>> >>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>>> launched with a DISPLAY setup. >>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>> was skipped from the documentation. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>> >>>>>>>>> Good day! >>>>>>>>> Prompt please. >>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>> Paraviewweb (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>> When deployment by using the ( >>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>> as 1 Ceci. >>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>> Thank you >>>>>>>>> >>>>>>>>> Sincerely, >>>>>>>>> Sukhachev Ilya! >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From f_magician at mac.com Thu Oct 2 11:31:10 2014 From: f_magician at mac.com (Magician) Date: Fri, 03 Oct 2014 00:31:10 +0900 Subject: [Paraview] How to create streamlines from tecplot velocity data In-Reply-To: References: Message-ID: Hi Danyang, Your question is one of the FAQ: http://public.kitware.com/pipermail/paraview/2010-September/018889.html Magician On Sep 24, 2014, at 15:26, paraview-request at paraview.org wrote: > Message: 2 > Date: Tue, 23 Sep 2014 23:26:00 -0700 > From: Danyang Su > To: "paraview at paraview.org" > Subject: [Paraview] How to create streamlines from tecplot velocity > data > Message-ID: <542263F8.5000001 at gmail.com> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Dear All, > > I have tecplot velocity dataset that I want to view with Paraview. I can > successfully import the data to paraview, but neither 'cell data to > point data' nor 'stream tracer' button is available (grey). The data set > is in ascii format as shown below. The source data is also attached. > > Would anybody please give me some tips? I am a new to paraview and only > have basic knowledge of it. > > Thanks, > > Danyang > > title = "dataset concrete-decalc" > variables = "x", "y", "z", "vx", "vy", "vz" > zone t = "velocities, solution time = 1.000E+02 years " i = 83, j > = 159, k = 1, f=point > 0.2626316E-04 0.0000000E+00 0.1052632E-02 0.3647120E-11 > 0.0000000E+00 -0.6160582E-05 > 0.7878948E-04 0.0000000E+00 0.1052632E-02 0.1094119E-10 > 0.0000000E+00 -0.6160582E-05 > 0.1313158E-03 0.0000000E+00 0.1052632E-02 0.1823477E-10 > 0.0000000E+00 -0.6160581E-05 > 0.1838421E-03 0.0000000E+00 0.1052632E-02 0.2552754E-10 > 0.0000000E+00 -0.6160580E-05 > 0.2363684E-03 0.0000000E+00 0.1052632E-02 0.3281916E-10 > 0.0000000E+00 -0.6160578E-05 > 0.2888947E-03 0.0000000E+00 0.1052632E-02 0.4010932E-10 > 0.0000000E+00 -0.6160576E-05 > 0.3414211E-03 0.0000000E+00 0.1052632E-02 0.4739768E-10 > 0.0000000E+00 -0.6160574E-05 > 0.3939474E-03 0.0000000E+00 0.1052632E-02 0.5468392E-10 > 0.0000000E+00 -0.6160572E-05 > 0.4464737E-03 0.0000000E+00 0.1052632E-02 0.6196771E-10 > 0.0000000E+00 -0.6160569E-05 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: concrete-decalc_3.vel.7z > Type: application/x-7z-compressed > Size: 86267 bytes > Desc: not available > URL: From utkarsh.ayachit at kitware.com Thu Oct 2 11:33:58 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 11:33:58 -0400 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: <542D6C15.5000100@xs4all.nl> References: <542D2C9D.5010506@xs4all.nl> <542D510A.5030706@xs4all.nl> <542D6C15.5000100@xs4all.nl> Message-ID: In other words, just don't use mutliple inheritance. Often you can restruture your code to "has-a" instead of "is-a" style. Make sphBoxSource subclass vtkCubeSource and have a member variable of type SPHParticleProps. For which ever methods from SPHParticleProps you want to expose, add those as methods on sphBoxSource and then forward those calls explictly to the SPHParticleProps instance. Utkarsh On Thu, Oct 2, 2014 at 11:15 AM, B.W.H. van Beest wrote: > Hi Utkarsh, > > Not sure how to do that, really in Paraview. The relationshop and > dynamics between what is in the xml file, source files I write and > generated files by mysterious macros make me still a bit uncomfortable > in finding my way in ParaView. > Maybe you could a bit more verbose? > > Regards, > Bertwim > > On 10/02/2014 03:24 PM, Utkarsh Ayachit wrote: >> It will only warp the 1 base. I'd suggest using a proxy pattern rather >> than multiple inheritance. >> >> On Thu, Oct 2, 2014 at 9:20 AM, B.W.H. van Beest wrote: >>> It seems to work. Inheritance of the vtkCubeSource methods just works. >>> Also when I reverse the inheritance order, or when I have single >>> inheritance (of vtkCubeSource), in the xml-file I can just refer to the >>> methods of the base class vtkCubeSource (say SetLength()) and it works. >>> But not so for the oher base class! >>> >>> So I *think* I am using the two baseclasses the same way, the effect >>> however, is asymmetrial. >>> >>> I looked, as you suggested, into sphBoxSourceClientServer.h The >>> methods of the baseclasses (vtkCubeSource), e.g. SetXLength(), do not >>> show-up there either. But it works, so that might not be the place where >>> to look. >>> >>> Any other ideas? >>> >>> Regards, >>> Bertwim >>> >>> >>> >>> On 10/02/2014 02:23 PM, Utkarsh Ayachit wrote: >>>> I can't remember if the wrapping code can handle multiple inheritance. >>>> If you removed the second superclass, does that work? >>>> >>>> Also look the sphBoxSourceClientServer.h file generated in your build >>>> directory. That will indicate which methods from this class are >>>> getting wrapped and which ones aren't. >>>> >>>> Utkarsh >>>> >>>> On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: >>>>> Hello, I'm struggling with getting the properties panel right for a new >>>>> Source defined in plugin that I'm writing. >>>>> >>>>> In the class below, I'm extending the VTK class for a rectangular box, >>>>> vtkCubeSource. The class also derives from another class, >>>>> that has the well known method "foo". I have made corresponding >>>>> changes to the server manager file (xml), given below. >>>>> >>>>> In the xml-file, I can specify the panel entries for the vtkCubeSource, >>>>> referring to the methods of this vtk class which are available via >>>>> inheritance, for instance "SetXLength(double)". However, when I do the >>>>> same for the method "foo(int)" of the other base class, ParaView bombs, >>>>> telling me that: >>>>> >>>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>>> tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find >>>>> requested method: "foo" >>>>> or the method was called with incorrect arguments. >>>>> >>>>> while processing >>>>> Message 0 = Invoke >>>>> Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} >>>>> Argument 1 = string_value {foo} >>>>> Argument 2 = int32_value {1024} >>>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>>> >>>>> The problem is gone when I provide the derived class also with a method >>>>> "foo", which calls the "foo" of the base class. >>>>> In short, I can refer, in the panel, to the methods of vtkCubeSource (as >>>>> expected due to inheritance), but not for the other base class. >>>>> What am I overlooking here, and what do I need to do to have the >>>>> expected inheritance? >>>>> >>>>> Your view >>>>> Kind Regards, >>>>> Bertwim >>>>> --------------------- >>>>> >>>>> >>>>> This is my class: >>>>> ===================================== >>>>> class sphBoxSource : public vtkCubeSource >>>>> , public SPHParticleProps >>>>> { >>>>> public: >>>>> static sphBoxSource* New(); >>>>> vtkTypeMacro(sphBoxSource,vtkCubeSource); >>>>> >>>>> public: >>>>> sphBoxSource( double, double, double ); >>>>> ~sphBoxSource(); >>>>> >>>>> public: // testing purposes only >>>>> void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties >>>>> pane,: Why can I can not just inherit the method "foo"? >>>>> }; >>>>> ======================================= >>>>> >>>>> The server manager configuration is taken from "sources.xml" that comes >>>>> with ParaView (4.2), but extended with a property for "foo". >>>>> >>>>> ======================================= >>>>> >>>>> >>>>> >>>>> >>>> label="SPHBox" >>>>> name="SPHBoxSource"> >>>>> ... >>>>> >>>> command="SetXLength" >>>>> default_values="10.0" >>>>> name="XLength" >>>>> number_of_elements="1" >>>>> panel_visibility="default"> >>>>> >>>>> This property specifies the length of the box in >>>>> the X direction. >>>>> >>>>> >>>>> .... >>>>> >>>>> >>>>> >>>> default_values="1024" >>>>> name="foobar" >>>>> number_of_elements="1"> >>>>> >>>>> Just for testing. Does nothing. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >> > From utkarsh.ayachit at kitware.com Thu Oct 2 11:36:41 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 11:36:41 -0400 Subject: [Paraview] problem wirh python shell in Paraview 4.2.0 In-Reply-To: <8ff8fd1ed7819fd5bb9a1898934858c8@mail.gmail.com> References: <8ff8fd1ed7819fd5bb9a1898934858c8@mail.gmail.com> Message-ID: I'd suggest asking the question on OpenFoam mailing lists/forums. They must have some mechanism to build with Python enabled. On Thu, Oct 2, 2014 at 11:06 AM, James Feng wrote: > Hi, > > I'm using paraview (4.1.0) with OpenFOAM 2.3.0 and "parafoam". I noticed > my "python shell" under my parafoam "tool" menu is not activated (with an > appearance "gray"). I wonder if you can tell me what I need to do to > turn the python shell on. I tried with "makeParaView -python" and it > didn't go through the "make". So I guess that is not a legitimate syntax. > > > Many thanks. > > James > > -----Original Message----- > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh > Ayachit > Sent: Thursday, October 02, 2014 7:19 AM > To: Livia Barazzetti > Cc: ParaView > Subject: Re: [Paraview] problem wirh python shell in Paraview 4.2.0 > > Thanks for reporting. We'll test it out. BTW, do you have any plugins > loaded when you're trying to one the Python shell? > Utkarsh > > On Thu, Oct 2, 2014 at 8:15 AM, wrote: >> Hi all, >> >> I just downloaded the new version of Paraview, and I am very curious >> about the new features. Unfortunately I cannot use the new python >> trace, because as soon I click ok in the trace window, the application > crashes. >> >> Actually, the problem is already at startup, opening a python shell I >> get this error: >> >> >> >> Python 2.7.3 (default, Sep 23 2014, 20:23:11) [MSC v.1500 64 bit >> (AMD64)] on >> win32 >> >>>>> from paraview.simple import * >> >> Traceback (most recent call last): >> >> File "", line 1, in >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\simple.py", line 39, in >> >> >> import servermanager >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line >> 3184, in >> >> __initialize() >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line >> 3175, in __initialize >> >> c = Connection(iter.GetCurrentSessionId(), iter.GetCurrentSession()) >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line >> 1932, in __init__ >> >> _createModules(self.Modules) >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line >> 2564, in _createModules >> >> m.filters = createModule('filters') >> >> File "C:\Program Files (x86)\ParaView >> 4.2.0\lib\paraview-4.2\site-packages\paraview\servermanager.py", line >> 2626, in createModule >> >> if (prop.GetInformationOnly() and propName != "TimestepValues" ) \ >> >> AttributeError: 'NoneType' object has no attribute 'GetInformationOnly' >> >> >> >> I am working on Windows 7, 64 bit (with paraview 4.2.0 64 bit) >> >> Regards, >> >> Livia >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Thu Oct 2 12:37:07 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 18:37:07 +0200 Subject: [Paraview] default representation? In-Reply-To: References: Message-ID: <542D7F33.6010109@xs4all.nl> But how can I set the default, especially for a new source? Regards, Bertwim On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: > The default representation is based more on the data type than the filter > setup. I forget all the rules, but I believe that structured data types > (like uniform and non-uniform rectilinear grids and curvilinear grids) > default to outline. Unstructured data types (like poly data or > unstructured grids) default to surface unless the size is larger than some > threshold (which can be changed in settings). Multiblock data sets default > to whatever is appropriate for the data type in the blocks. > > > The rational for this behavior is that an unstructured data type likely > represents some geometry of importance whereas a regular grid more likely > represents some region in space where the relevant structure is internal. > > -Ken > > On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: > >> Hello, >> >> I noticed that sources like a box, sphere etc., are always displayed >> initially with a surface representation, after which ione can set it >> manually to something else, e.g. a wireframe. Where is this preference >> being set? I cannot find it in the sources.xml file or in any of the >> other xml files, but maybe I don't recognise it. >> >> Background of this is that I would like to change this default >> behaviour, in particular for some new sources I'm creating in a plugin. >> (The sources that are derived from the standard ones.) >> >> Kind Regards, >> Bertwim >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > From bwvb at xs4all.nl Thu Oct 2 12:44:39 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 02 Oct 2014 18:44:39 +0200 Subject: [Paraview] Property Panel and Inheritance? In-Reply-To: References: <542D2C9D.5010506@xs4all.nl> <542D510A.5030706@xs4all.nl> <542D6C15.5000100@xs4all.nl> Message-ID: <542D80F7.7080409@xs4all.nl> Hm, that is a lot of extra work, especially because the base class sphParticleProps has a similar role not only for a box source, but also for sphere, cone, cylinder, etc. But one has to live with the given limitations of the tool. Anyway, thanks. Bertwim On 10/02/2014 05:33 PM, Utkarsh Ayachit wrote: > In other words, just don't use mutliple inheritance. Often you can > restruture your code to "has-a" instead of "is-a" style. Make > sphBoxSource subclass vtkCubeSource and have a member variable of > type SPHParticleProps. For which ever methods from SPHParticleProps > you want to expose, add those as methods on sphBoxSource and then > forward those calls explictly to the SPHParticleProps instance. > > Utkarsh > > On Thu, Oct 2, 2014 at 11:15 AM, B.W.H. van Beest wrote: >> Hi Utkarsh, >> >> Not sure how to do that, really in Paraview. The relationshop and >> dynamics between what is in the xml file, source files I write and >> generated files by mysterious macros make me still a bit uncomfortable >> in finding my way in ParaView. >> Maybe you could a bit more verbose? >> >> Regards, >> Bertwim >> >> On 10/02/2014 03:24 PM, Utkarsh Ayachit wrote: >>> It will only warp the 1 base. I'd suggest using a proxy pattern rather >>> than multiple inheritance. >>> >>> On Thu, Oct 2, 2014 at 9:20 AM, B.W.H. van Beest wrote: >>>> It seems to work. Inheritance of the vtkCubeSource methods just works. >>>> Also when I reverse the inheritance order, or when I have single >>>> inheritance (of vtkCubeSource), in the xml-file I can just refer to the >>>> methods of the base class vtkCubeSource (say SetLength()) and it works. >>>> But not so for the oher base class! >>>> >>>> So I *think* I am using the two baseclasses the same way, the effect >>>> however, is asymmetrial. >>>> >>>> I looked, as you suggested, into sphBoxSourceClientServer.h The >>>> methods of the baseclasses (vtkCubeSource), e.g. SetXLength(), do not >>>> show-up there either. But it works, so that might not be the place where >>>> to look. >>>> >>>> Any other ideas? >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> >>>> On 10/02/2014 02:23 PM, Utkarsh Ayachit wrote: >>>>> I can't remember if the wrapping code can handle multiple inheritance. >>>>> If you removed the second superclass, does that work? >>>>> >>>>> Also look the sphBoxSourceClientServer.h file generated in your build >>>>> directory. That will indicate which methods from this class are >>>>> getting wrapped and which ones aren't. >>>>> >>>>> Utkarsh >>>>> >>>>> On Thu, Oct 2, 2014 at 6:44 AM, B.W.H. van Beest wrote: >>>>>> Hello, I'm struggling with getting the properties panel right for a new >>>>>> Source defined in plugin that I'm writing. >>>>>> >>>>>> In the class below, I'm extending the VTK class for a rectangular box, >>>>>> vtkCubeSource. The class also derives from another class, >>>>>> that has the well known method "foo". I have made corresponding >>>>>> changes to the server manager file (xml), given below. >>>>>> >>>>>> In the xml-file, I can specify the panel entries for the vtkCubeSource, >>>>>> referring to the methods of this vtk class which are available via >>>>>> inheritance, for instance "SetXLength(double)". However, when I do the >>>>>> same for the method "foo(int)" of the other base class, ParaView bombs, >>>>>> telling me that: >>>>>> >>>>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>>>> tkPVSessionCore (0x113a740): Object type: sphBoxSource, could not find >>>>>> requested method: "foo" >>>>>> or the method was called with incorrect arguments. >>>>>> >>>>>> while processing >>>>>> Message 0 = Invoke >>>>>> Argument 0 = vtk_object_pointer {sphBoxSource (0x30fbe00)} >>>>>> Argument 1 = string_value {foo} >>>>>> Argument 2 = int32_value {1024} >>>>>> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ >>>>>> >>>>>> The problem is gone when I provide the derived class also with a method >>>>>> "foo", which calls the "foo" of the base class. >>>>>> In short, I can refer, in the panel, to the methods of vtkCubeSource (as >>>>>> expected due to inheritance), but not for the other base class. >>>>>> What am I overlooking here, and what do I need to do to have the >>>>>> expected inheritance? >>>>>> >>>>>> Your view >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> --------------------- >>>>>> >>>>>> >>>>>> This is my class: >>>>>> ===================================== >>>>>> class sphBoxSource : public vtkCubeSource >>>>>> , public SPHParticleProps >>>>>> { >>>>>> public: >>>>>> static sphBoxSource* New(); >>>>>> vtkTypeMacro(sphBoxSource,vtkCubeSource); >>>>>> >>>>>> public: >>>>>> sphBoxSource( double, double, double ); >>>>>> ~sphBoxSource(); >>>>>> >>>>>> public: // testing purposes only >>>>>> void foo( int i ){ SPHParticleProps::foo(i);} // For the Properties >>>>>> pane,: Why can I can not just inherit the method "foo"? >>>>>> }; >>>>>> ======================================= >>>>>> >>>>>> The server manager configuration is taken from "sources.xml" that comes >>>>>> with ParaView (4.2), but extended with a property for "foo". >>>>>> >>>>>> ======================================= >>>>>> >>>>>> >>>>>> >>>>>> >>>>> label="SPHBox" >>>>>> name="SPHBoxSource"> >>>>>> ... >>>>>> >>>>> command="SetXLength" >>>>>> default_values="10.0" >>>>>> name="XLength" >>>>>> number_of_elements="1" >>>>>> panel_visibility="default"> >>>>>> >>>>>> This property specifies the length of the box in >>>>>> the X direction. >>>>>> >>>>>> >>>>>> .... >>>>>> >>>>>> >>>>>> >>>>> default_values="1024" >>>>>> name="foobar" >>>>>> number_of_elements="1"> >>>>>> >>>>>> Just for testing. Does nothing. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview > From kmorel at sandia.gov Thu Oct 2 14:38:27 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 2 Oct 2014 18:38:27 +0000 Subject: [Paraview] default representation? Message-ID: As far as I know (and anyone else on the list is welcome to correct me), you cannot directly change the default representation for the output of a source/filter. The default representation is automatically chosen based on the type of the data and the view it is being shown in. What kind of data is the output from your source? -Ken On 10/2/14, 10:37 AM, "B.W.H. van Beest" wrote: >But how can I set the default, especially for a new source? > > >Regards, >Bertwim > >On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: >> The default representation is based more on the data type than the >>filter >> setup. I forget all the rules, but I believe that structured data types >> (like uniform and non-uniform rectilinear grids and curvilinear grids) >> default to outline. Unstructured data types (like poly data or >> unstructured grids) default to surface unless the size is larger than >>some >> threshold (which can be changed in settings). Multiblock data sets >>default >> to whatever is appropriate for the data type in the blocks. >> >> >> The rational for this behavior is that an unstructured data type likely >> represents some geometry of importance whereas a regular grid more >>likely >> represents some region in space where the relevant structure is >>internal. >> >> -Ken >> >> On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >> >>> Hello, >>> >>> I noticed that sources like a box, sphere etc., are always displayed >>> initially with a surface representation, after which ione can set it >>> manually to something else, e.g. a wireframe. Where is this preference >>> being set? I cannot find it in the sources.xml file or in any of the >>> other xml files, but maybe I don't recognise it. >>> >>> Background of this is that I would like to change this default >>> behaviour, in particular for some new sources I'm creating in a plugin. >>> (The sources that are derived from the standard ones.) >>> >>> Kind Regards, >>> Bertwim >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> > From wascott at sandia.gov Thu Oct 2 15:02:45 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 2 Oct 2014 19:02:45 +0000 Subject: [Paraview] PV 4.2.0 custom site settings Message-ID: <5d1149f2ac6942af9c8f73a9021ccb89@ES05AMSNLNT.srn.sandia.gov> I am trying to set default offscreen rendering in ParaView for my site. Where is this new functionality located? Where is it documented? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmorel at sandia.gov Thu Oct 2 15:12:49 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Thu, 2 Oct 2014 19:12:49 +0000 Subject: [Paraview] PV 4.2.0 custom site settings Message-ID: I see some hints about it in this bug report: http://www.paraview.org/Bug/view.php?id=13575 It looks like there is a Wiki page that is supposed to talk about user- and site-specific settings (http://www.paraview.org/Wiki/ParaView_Settings_Files), but it looks to be quite a bit out of date. Someone should probably update this information. (One, two, three, not it!) -Ken From: , Walter Scott > Date: Thursday, October 2, 2014 at 1:02 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] PV 4.2.0 custom site settings I am trying to set default offscreen rendering in ParaView for my site. Where is this new functionality located? Where is it documented? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Oct 2 15:18:52 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 15:18:52 -0400 Subject: [Paraview] PV 4.2.0 custom site settings In-Reply-To: References: Message-ID: Check this out as well: http://www.kitware.com/blog/home/post/672 There's a chapter in the new user's guide that covers this as well. Utkarsh On Thu, Oct 2, 2014 at 3:12 PM, Moreland, Kenneth wrote: > I see some hints about it in this bug report: > http://www.paraview.org/Bug/view.php?id=13575 > > It looks like there is a Wiki page that is supposed to talk about user- and > site-specific settings > (http://www.paraview.org/Wiki/ParaView_Settings_Files), but it looks to be > quite a bit out of date. Someone should probably update this information. > (One, two, three, not it!) > > -Ken > > From: , Walter Scott > Date: Thursday, October 2, 2014 at 1:02 PM > To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] PV 4.2.0 custom site settings > > I am trying to set default offscreen rendering in ParaView for my site. > Where is this new functionality located? Where is it documented? > > Thanks, > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From wascott at sandia.gov Thu Oct 2 15:18:56 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 2 Oct 2014 19:18:56 +0000 Subject: [Paraview] PV 4.2.0 custom site settings In-Reply-To: References: Message-ID: I found notes to myself, that I wrote when I was testing this new feature, from last July. However, we do need this documented, since there are many, many settings that a user can create defaults for. Here are my notes: - Install ParaView in some directory $INSTALL - Delete $HOME/.config/ParaView directory - Launch paraview (local server) - Edit -> Settings... - Click on gear icon to enable advanced settings - Click on Render View tab - Enter search text "Off". See that offscreen rendering is not enabled - Quit ParaView - Create a file $INSTALL/share/paraview4.1/ParaView-SiteSettings.json with the content { "settings" : { "RenderViewSettings" : { "UseOffscreenRenderingForScreenshots" : 1 } } } - Launch paraview - Edit -> Settings... - Click on Render View tab - Enter search text "Off". See that offscreen rendering is now enabled - Remove search text - Click on General tab - Enable "Automatically convert data arrays as needed..." - Click OK in settings dialog box - Quit ParaView - View file $HOME/.config/ParaView/ParaView-UserSettings.json - It should have the contents { "settings" : { "GeneralSettings" : { "AutoConvertProperties" : 1 }, "RenderViewSettings" : { "UseOffscreenRenderingForScreenshots" : 1 } } } Note that you can also define the environment variable PV_SETTINGS_DEBUG to view the directories where the settings are being searched. Alan From: Moreland, Kenneth Sent: Thursday, October 02, 2014 1:13 PM To: Scott, W Alan; paraview at paraview.org Subject: Re: [Paraview] PV 4.2.0 custom site settings I see some hints about it in this bug report: http://www.paraview.org/Bug/view.php?id=13575 It looks like there is a Wiki page that is supposed to talk about user- and site-specific settings (http://www.paraview.org/Wiki/ParaView_Settings_Files), but it looks to be quite a bit out of date. Someone should probably update this information. (One, two, three, not it!) -Ken From: , Walter Scott > Date: Thursday, October 2, 2014 at 1:02 PM To: "paraview at paraview.org" > Subject: [EXTERNAL] [Paraview] PV 4.2.0 custom site settings I am trying to set default offscreen rendering in ParaView for my site. Where is this new functionality located? Where is it documented? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Thu Oct 2 15:20:29 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 2 Oct 2014 15:20:29 -0400 Subject: [Paraview] PV 4.2.0 custom site settings In-Reply-To: <5d1149f2ac6942af9c8f73a9021ccb89@ES05AMSNLNT.srn.sandia.gov> References: <5d1149f2ac6942af9c8f73a9021ccb89@ES05AMSNLNT.srn.sandia.gov> Message-ID: Alan, Documentation for this is in the new ParaView Users Guide. Relevant text adapted from the LaTeX: ==== Configuring site-wide default settings In addition to individual custom default settings, ParaView offers a way to specify site-wide custom default settings for a ParaView installation. These site-wide custom defaults must be defined in a JSON file with the same structure as the user settings file. In fact, one way to create a site settings file is to set the custom defaults desired in paraview, close the program, then copy the user settings file to the site settings file. The site settings file must be named ParaView-SiteSettings.json. The ParaView executables will search for the site settings file in several locations. If you installed ParaView in the directory INSTALL, then the ParaView executables will search for the site settings file in these directories in the specified order: - INSTALL/share/paraview-X.Y - INSTALL/lib - INSTALL - INSTALL/.. where X is ParaView's major version number and Y is the minor version number. ParaView executables will search these directories in the given order, reading in the first ParaView-SiteSettings.json file it finds. The conventional location for this kind of configuration file is in the 'share' directory (the first directory searched), so we recommend placing the site settings file there. Custom defaults in the user settings file take precedence over custom defaults in the site settings. If the same default is specified in both the ParaView-SiteSettings.json file and ParaView-UserSettings.json file in a user's directory, the default specified in the ParaView-UserSettings.json file will be used. This is true for both object property settings and application-settings set through the Edit -> Settings menu. To aid in debugging problems with the site settings file location, you can define an evironment variable named PV_SETTINGS_DEBUG to something other than an empty string. This will turn on verbose output showing where the ParaView executables are looking for the site settings file. ==== Cory On Thu, Oct 2, 2014 at 3:02 PM, Scott, W Alan wrote: > I am trying to set default offscreen rendering in ParaView for my site. > Where is this new functionality located? Where is it documented? > > Thanks, > > Alan > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Thu Oct 2 15:27:49 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 2 Oct 2014 19:27:49 +0000 Subject: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON (UNCLASSIFIED) In-Reply-To: References: <20140916185553.GA32690@megas.kitwarein.com> , Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Dave, I talked to Andrew (ARL developer working on xdmf) about the file size issue. I am using the ParaView-v4.2.0-source.tar.gz downloaded from ParaView download page. Can you point me to the location of your file/code for the reader/writer you put in? After looking at the data file generated, he mentioned by setting setReleaseData to true on the writer could fix the issue. writer->getHeavyDataWriter()->setReleaseData(true); Please see below on his comment on the matter. I have also included Andrew in this email. If you can point me to your reader/writer code file, maybe I can see if I can add that option to change the writer default settings. Thanks -simon Classification: UNCLASSIFIED Caveats: NONE Here's a detailed look at the problem. The generated Xdmf file has 31 timesteps listed in this format: What I noticed is that the hdf5 data sets written start on dataset number 7688. Which means that there are 7687 datasets in the hdf5 file prior to the creation of the xmf file. All of these unreferenced sets are contributing to a large hdf5 file. I suspect that this issue may be due to the way that the writer is parsing out the xdmf data. I presume that it is writing all data to hdf5 each time an array is encountered, and it does make sense to do this to save on memory. The problem is it seems that ALL arrays are getting written to hdf5 each time. This is probably because the XdmfHDF5Writer is on its default settings. The following call should help. writer->getHeavyDataWriter()->setReleaseData(true); This sets the writer to release the data currently contained within the array from memory. If the XdmfWriter sees an array that has heavy data in it, it assumes that the data has changed since the last write and creates a new hdf5 dataset. Setting this flag causes the heavy data writer to clear the xdmf array of data so that it will not be written to file on a new pass. -Andrew -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Su, Simon M CTR USARMY ARL (US) Sent: Wednesday, September 17, 2014 1:07 PM To: David E DeMarle Cc: paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON thanks Dave.... I will pass along the info and see what they want to do... -simon ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Wednesday, September 17, 2014 12:24 PM To: Su, Simon M CTR USARMY ARL (US) Cc: Ben Boeckel; paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON I briefly looked at that a couple of weeks ago. Sorry I didn't get back to you before now. My findings were: 1) xdm3writer performs the same as xdmf2writer 2) I didn't find a compression option. So, in other words, I don't have a quick fix and someone needs to put some development time in to improve it. The good news is that there is lots of room for improvement and it shouldn't be too hard to do better on the writer end. It is very likely that the ARL guys will have ideas of on ways to compress within libxdmf. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Sep 17, 2014 at 10:16 AM, Su, Simon M CTR USARMY ARL (US) wrote: thanks Dave. We will remember that when we do the compile after 4.2 release... I tried xdmf3 writer using the File->Save Data option in PV v4.2.0-RC1-75-gf64ee7a and the 82M pvd file still turn into a 4.4G h5 file. Not sure if something that I am not doing right? Is there like a compression flag that I can turn on? thanks... thanks -simon ________________________________ From: David E DeMarle [dave.demarle at kitware.com] Sent: Wednesday, September 17, 2014 11:56 AM To: Ben Boeckel Cc: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] compiling ParaView v4.2.0-RC1-75-gf64ee7a with -DModule_vtkIOXdmf3:BOOL=ON I had similar config problems in the DoD HPC machines I tested on. The root cause was that the system boost was CMakefied and find boost didn't like it but insisted on using it. To get around it I downloaded my own boost (no need to compile it) and made the my PV build use it by: In cmakecache.txt set Boost_NO_SYSTEM_PATHS:BOOL=ON set Boost_NO_BOOST_CMAKE:BOOL=ON Then it will ask for an respect your choice of boost headers to use. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Sep 16, 2014 at 12:55 PM, Ben Boeckel wrote: On Tue, Sep 16, 2014 at 16:22:38 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I would like to test out the xdmf3 writer in ParaView 4.2 RC to see if the file > size is still increase 10 fold when saving pvd file to xmf format. > > However, when I configure ParaView v4.2.0-RC1-75-gf64ee7a with > -DModule_vtkIOXdmf3:BOOL=ON > > cmake -DCMAKE_BUILD_TYPE=release -DCMAKE_INSTALL_PREFIX=/home/simonsm/tools/ > paraview/paraview-v4.2.0-RC1-75-gf64ee7a_mesa -DPARAVIEW_ENABLE_PYTHON:BOOL=ON > -DPARAVIEW_USE_MPI:BOOL=ON -DPARAVIEW_ENABLE_WEB:BOOL=OFF > -DModule_vtkIOXdmf3:BOOL=ON ../ParaView-v4.2.0-RC1-75-gf64ee7a > > I got whole bunch of boost related cmake error with cmake version 3.0.0 and > cmake version 2.8.12.2. Some of the error messages are included at the end of > this email. > > I am able to compile RC1-22-g9ca4e44 version ok but without Module_vtkIOXdmf3 > set to ON. Is there anything on the boost side that I am not setting it right? > I am compiling on RHEL 6.5 with boost-devel-1.41.0-18.el6.x86_64 installed. Looks to be a CMake-ified boost. It worked here on Fedora with 1.54.0 (which I don't believe is built using CMake anymore). It seems that it doesn't support multiple find_package calls. Try setting Boost_NO_BOOST_CMAKE to ON to force the FindBoost.cmake logic to kick in. --Ben _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Thu Oct 2 16:00:33 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 2 Oct 2014 16:00:33 -0400 Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> References: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> Message-ID: Yes, vtkCamera does often update its itself. Look at vtkCamera.cxx [1]. [1] https://github.com/Kitware/VTK/blob/83be7b1b77a6bfbf296ccaa5155cec57d0c77a8c/Rendering/Core/vtkCamera.cxx On Thu, Oct 2, 2014 at 2:18 AM, Kazuyoshi Furutaka wrote: > Dear ParaView expert... > > I'm using ParaView Version 4.2.0 32-bit on linux (Fedora 20, > i386). > > Is the view-up vector updated automatically after > e.g. changing the camera position? > > From Python Shell, I got the following result: > > ...resetting... > Python 2.7.5 (default, Sep 25 2014, 13:58:10) > [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 >>>> from paraview.simple import * >>>> box=Box() >>>> Show(box) > >>>> cam=GetActiveCamera() >>>> cam.SetPosition(0,3,3) >>>> Render() > >>>> cam.GetViewUp() > (0.0, 1.0, 0.0) >>>> > > Is this correct behavior? > Who/what routine/method is responsible for updating the > vector? > > I'm observing a curious behavior of paraview.simple.Azimuth(); > camera is NOT moving left/right. > > Thanks in advance. > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Thu Oct 2 22:50:47 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 03 Oct 2014 04:50:47 +0200 Subject: [Paraview] default representation? In-Reply-To: References: Message-ID: <542E0F07.8050704@xs4all.nl> It is just a box, sphere, etc (originating from vtkCubeSource, vtpSPhereSource). I want to display them initially in a wireframe representation. Regards, Bertwim On 10/02/2014 08:38 PM, Moreland, Kenneth wrote: > As far as I know (and anyone else on the list is welcome to correct me), > you cannot directly change the default representation for the output of a > source/filter. The default representation is automatically chosen based on > the type of the data and the view it is being shown in. > > > What kind of data is the output from your source? > > -Ken > > On 10/2/14, 10:37 AM, "B.W.H. van Beest" wrote: > >> But how can I set the default, especially for a new source? >> >> >> Regards, >> Bertwim >> >> On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: >>> The default representation is based more on the data type than the >>> filter >>> setup. I forget all the rules, but I believe that structured data types >>> (like uniform and non-uniform rectilinear grids and curvilinear grids) >>> default to outline. Unstructured data types (like poly data or >>> unstructured grids) default to surface unless the size is larger than >>> some >>> threshold (which can be changed in settings). Multiblock data sets >>> default >>> to whatever is appropriate for the data type in the blocks. >>> >>> >>> The rational for this behavior is that an unstructured data type likely >>> represents some geometry of importance whereas a regular grid more >>> likely >>> represents some region in space where the relevant structure is >>> internal. >>> >>> -Ken >>> >>> On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >>> >>>> Hello, >>>> >>>> I noticed that sources like a box, sphere etc., are always displayed >>>> initially with a surface representation, after which ione can set it >>>> manually to something else, e.g. a wireframe. Where is this preference >>>> being set? I cannot find it in the sources.xml file or in any of the >>>> other xml files, but maybe I don't recognise it. >>>> >>>> Background of this is that I would like to change this default >>>> behaviour, in particular for some new sources I'm creating in a plugin. >>>> (The sources that are derived from the standard ones.) >>>> >>>> Kind Regards, >>>> Bertwim >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> > > From lifeandfree at gmail.com Fri Oct 3 02:03:08 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Fri, 3 Oct 2014 12:03:08 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day! Thank. 2014-10-02 21:10 GMT+06:00 Scott Wittenburg : On Thu, Oct 2, 2014 at 2:48 AM, Ilya Sukhachev wrote: > > Why update the browser page when it loses the session? Starts a new > process in nature. Is there any way to fix this? > > I'm not sure what you are asking here. What do you mean by "update the browser page"? *Go to page http://localhost/apps/Visualizer/ . We perform a series of actions. Press F5. All flies. Session is lost.* > When you disable the client (browser), the session remains on the server to > hang. How to deal with it? > > See the index.html for your particular application. The body tag has event handlers attached that will call the stop method when you close the tab or hit the back button. In that stop method, you can do what you like, like calling the rpc method "application.exit". *Good. Thank you. And please tell me where the class for the method to "application.exit"? And at what point is the creation of a compound?* When you connect multiple clients, very often produces the message: > "Session did not start before timeout expired. Check session logs." > Add a log file with errors, unless of course it will help. What could the > reason for this? > > I looked briefly at your log files, and I'm not sure what could be going on. Can all your clients reach the host where the pvpython processes are running? *Go to page http://SERVER_IP/apps/Visualizer . Displays your inscription ParaViewWeb. Spinning wheel. And then the following message appears: "Session did not start before timeout expired. Check session logs." And when such a couple of users are connected. Helps to restart. But 3-5 sessions and the application starts to behave inadequately.* Ilya 2014-10-02 21:10 GMT+06:00 Scott Wittenburg : > > > On Thu, Oct 2, 2014 at 2:48 AM, Ilya Sukhachev > wrote: > >> Good day. >> >> Sorry. Not the file sent. >> Attach desired. >> Everything worked. >> But there are a couple of questions. >> >> Glad you got something working. > > >> Why update the browser page when it loses the session? Starts a new >> process in nature. Is there any way to fix this? >> >> I'm not sure what you are asking here. What do you mean by "update the > browser page"? > > >> When you disable the client (browser), the session remains on the server to >> hang. How to deal with it? >> >> See the index.html for your particular application. The body tag has > event handlers attached that will call the stop method when you close the > tab or hit the back button. In that stop method, you can do what you like, > like calling the rpc method "application.exit". > > >> When you connect multiple clients, very often produces the message: >> "Session did not start before timeout expired. Check session logs." >> Add a log file with errors, unless of course it will help. What could the >> reason for this? >> >> I looked briefly at your log files, and I'm not sure what could be going > on. Can all your clients reach the host where the pvpython processes are > running? > > Cheers, > Scott > > > >> Sincerely, Ilya >> >> 2014-10-01 20:09 GMT+06:00 Scott Wittenburg > >: >> >>> The launcher config file you sent to the list was missing a "visualizer" >>> entry, but those instructions have one. Other than that, are things >>> working properly now? When we do find problems with the instructions, we >>> try to fix them, but I'm not sure yet if this is one of those cases. >>> >>> Cheers, >>> Scott >>> >>> On Wed, Oct 1, 2014 at 6:06 AM, Ilya Sukhachev >>> wrote: >>> >>>> Good day. >>>> >>>> For the settings I used your instruction online >>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>> . >>>> Did everything there. Would you say it does not work? >>>> >>>> Ilya >>>> >>>> 2014-09-30 20:43 GMT+06:00 Scott Wittenburg < >>>> scott.wittenburg at kitware.com>: >>>> >>>>> Your client side request to the launcher is asking for the >>>>> "visualizer" application, while the launcher (according to your launcher >>>>> config) doesn't know about a command line to start that application. Try >>>>> changing the "pipeline" key under the "apps" section to "visualizer". >>>>> >>>>> Cheers, >>>>> Scott >>>>> >>>>> >>>>> On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev >>>> > wrote: >>>>> >>>>>> Good day! >>>>>> >>>>>> Yes, of course >>>>>> Attached. >>>>>> Also put the configuration file Apache. >>>>>> >>>>>> Ilya >>>>>> >>>>>> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg < >>>>>> scott.wittenburg at kitware.com>: >>>>>> >>>>>>> Can you share your launcher configuration file? It appears you may >>>>>>> have no "visualizer" application command line configured. >>>>>>> >>>>>>> Cheers, >>>>>>> Scott >>>>>>> >>>>>>> >>>>>>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? >>>>>> > wrote: >>>>>>> >>>>>>>> >>>>>>>> And there is another question. >>>>>>>> Deployed software. I go to http://localhost/apps/Visualizer /. As >>>>>>>> a result, I see only the inscription ParaViewWeb and flailing >>>>>>>> wheel. And he gave me a list of errors in the console: >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1439, in dataReceived >>>>>>>> finishCallback(data[contentLength:]) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1668, in _finishRequestBody >>>>>>>> self.allContentReceived() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 1731, in allContentReceived >>>>>>>> req.requestReceived(command, path, version) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>> line 827, in requestReceived >>>>>>>> self.process() >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 189, in process >>>>>>>> self.render(resrc) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 238, in render >>>>>>>> body = resrc.render(self) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>> line 250, in render >>>>>>>> return m(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 399, in render_POST >>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>> File >>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>> line 182, in createSession >>>>>>>> options['cmd'] = >>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>> self.config['properties']]) >>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>> Unhandled Error >>>>>>>> Traceback (most recent call last): >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>> line 321, in processingFailed >>>>>>>> % webutil.formatFailure(reason)) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>> line 425, in formatFailure >>>>>>>> flattenString(None, >>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 420, in flattenString >>>>>>>> d = flatten(request, root, io.write) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 402, in flatten >>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>> --- --- >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 359, in _writeFlattenedData >>>>>>>> element = state.next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 326, in _flattenTree >>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>> >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 317, in _flattenTree >>>>>>>> element = stack[-1].next() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>> line 286, in _flattenElement >>>>>>>> result = root.render(request) >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>> line 184, in render >>>>>>>> return loader.load() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 465, in load >>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>> line 446, in _loadDoc >>>>>>>> f = self._path.open('r') >>>>>>>> File >>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>> line 828, in open >>>>>>>> return open(self.path, mode + 'b') >>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>> >>>>>>>> >>>>>>>> In logs file error.log: >>>>>>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38924] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533720598272] (20014)Internal error: [client 127.0.0.1:38923] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38925] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38926] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38922] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533745776384] (20014)Internal error: [client 127.0.0.1:38921] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533737383680] (20014)Internal error: [client 127.0.0.1:38933] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>>>>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading >>>>>>>> from remote server returned by /paraview/, referer: >>>>>>>> http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533787739904] (20014)Internal error: [client 127.0.0.1:38939] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533762561792] (20014)Internal error: [client 127.0.0.1:38940] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533829703424] (20014)Internal error: [client 127.0.0.1:38944] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533854881536] (20014)Internal error: [client 127.0.0.1:38943] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533821310720] (20014)Internal error: [client 127.0.0.1:38942] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid 14562:tid >>>>>>>> 140533804525312] (20014)Internal error: [client 127.0.0.1:38941] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid 14563:tid >>>>>>>> 140533754169088] (20014)Internal error: [client 127.0.0.1:38951] >>>>>>>> AH01102: error reading status line from remote server localhost:8080, >>>>>>>> referer: http://localhost/apps/Visualizer/ >>>>>>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>>>>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading >>>>>>>> from remote server returned by /paraview/, referer: >>>>>>>> http://localhost/apps/Visualizer/ >>>>>>>> >>>>>>>> >>>>>>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>>>>>> >>>>>>>>> Good day. >>>>>>>>> Thank you. >>>>>>>>> >>>>>>>>> You may be able to explain. What kind of filter is it? >>>>>>>>> >>>>>>>>> Ilya >>>>>>>>> >>>>>>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>> >>>>>>>>>> ParaView 4.2 has been released, so that would be the latest >>>>>>>>>> stable version available. >>>>>>>>>> There is no localization per say but the filter names could be >>>>>>>>>> customized the way you want. >>>>>>>>>> >>>>>>>>>> For continuous live visualization it is possible but that will be >>>>>>>>>> a custom development. And for that you can contact Kitware for either a >>>>>>>>>> support contract (http://www.kitware.com/products/support.html) >>>>>>>>>> or an end-product development ( >>>>>>>>>> http://www.kitware.com/products/consulting.html). >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? < >>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> thank you, ok. try to understand. I put the stable version and >>>>>>>>>>> not the release candidate. >>>>>>>>>>> >>>>>>>>>>> But there are a few more questions. >>>>>>>>>>> Do files are responsible for localization? I need to replace the >>>>>>>>>>> language in the design parawiewweb. >>>>>>>>>>> And the second. Is there a possibility of the file from which the >>>>>>>>>>> object is loaded into the web, continuously read the data? That >>>>>>>>>>> is to update the image in the browser loading new data, but >>>>>>>>>>> this is not in the manual and automatic. >>>>>>>>>>> >>>>>>>>>>> Sincerely, >>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>> >>>>>>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>>>>>> with Apache. >>>>>>>>>>>> Moreover, can you enable the development tools on your browser >>>>>>>>>>>> to see what kind of error you got? >>>>>>>>>>>> >>>>>>>>>>>> Did you look also at the different types of logs? Apache, >>>>>>>>>>>> Launcher (see config to know where you choose to put them). >>>>>>>>>>>> That could also give you an idea on what went wrong. >>>>>>>>>>>> >>>>>>>>>>>> Seb >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, Sebastien >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you. >>>>>>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>>>>>> But when entering the address: >>>>>>>>>>>>> http://localhost/apps/Visualizer is only displayed only the >>>>>>>>>>>>> green bar at the top of the window, and nothing more. >>>>>>>>>>>>> That in this case? >>>>>>>>>>>>> >>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>> >>>>>>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>>> >>>>>>>>>>>>>> Moreover, the documentation that get's updated automatically >>>>>>>>>>>>>> can be found at the following address. (Which might be more accurate.) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>>>>>> >>>>>>>>>>>>>> This is the one you find when you go on paraview.org and go >>>>>>>>>>>>>> to the documentation section. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Seb >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The one thing that might not be explicit about the >>>>>>>>>>>>>>> ubuntu_14_04 guide might be that the script "/data/pvw/bin/ >>>>>>>>>>>>>>> start.sh" should be launched with a DISPLAY setup. >>>>>>>>>>>>>>> Otherwise, you will have to be more explicit on what you've >>>>>>>>>>>>>>> done and what is not working. The log files usually helps to see what >>>>>>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Seb >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Good day! >>>>>>>>>>>>>>>> Prompt please. >>>>>>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>>>>>> Unfolded, but for some reason I can not open in the web >>>>>>>>>>>>>>>> browser Visualizer (http: // localhost / apps / Visualizer >>>>>>>>>>>>>>>> /) >>>>>>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I >>>>>>>>>>>>>>>> can run only as 1 Ceci. >>>>>>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>>>>>> Thank you >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki >>>>>>>>>>>>>>>> at: http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> ? ?????????, >>>>>>>>>>>>> ??????? ????! >>>>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> ? ?????????, >>>>>>>>>>> ??????? ????! >>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ? ?????????, >>>>>>>>> ??????? ????! >>>>>>>>> +7 912 216 72 72 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> ? ?????????, >>>>>>>> ??????? ????! >>>>>>>> +7 912 216 72 72 >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> ? ?????????, >>>>>> ??????? ????! >>>>>> +7 912 216 72 72 >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> ? ?????????, >>>> ??????? ????! >>>> +7 912 216 72 72 >>>> >>> >>> >> >> >> -- >> ? ?????????, >> ??????? ????! >> +7 912 216 72 72 >> > > -- ? ?????????, ??????? ????! +7 912 216 72 72 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lifeandfree at gmail.com Fri Oct 3 02:05:40 2014 From: lifeandfree at gmail.com (Ilya Sukhachev) Date: Fri, 3 Oct 2014 12:05:40 +0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: Good day! And how can I help with the localization? Locate each structure? Ilya 2014-10-02 21:19 GMT+06:00 Scott Wittenburg : > You can specify which filters you would like to make available to > ParaViewWeb using the "--proxies" argument to the pv_web_visualizer.py. By > default ParaViewWeb can use all the filters listed in > "defaultProxies.json", which is located in your build or install tree under > site-packages/paraview/web/. You can use this one as an example to create > your own. You can find out about the filters by looking at filters.xml in > the source tree (ParaViewCore/ServerManager/SMApplication/Resources/). You > can read more about the filters on the wiki: > > http://www.paraview.org/Wiki/ParaView/Users_Guide/List_of_filters > > Hope this helps. > > Cheers, > Scott > > > On Thu, Oct 2, 2014 at 2:51 AM, Ilya Sukhachev > wrote: > >> Good day to all! >> >> Can someone help and filters are we talking about? >> >> Sincerely, Ilya >> >> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >> >>> Good day. >>> Thank you. >>> >>> You may be able to explain. What kind of filter is it? >>> >>> Ilya >>> >>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>> sebastien.jourdain at kitware.com>: >>> >>>> ParaView 4.2 has been released, so that would be the latest stable >>>> version available. >>>> There is no localization per say but the filter names could be >>>> customized the way you want. >>>> >>>> For continuous live visualization it is possible but that will be a >>>> custom development. And for that you can contact Kitware for either a >>>> support contract (http://www.kitware.com/products/support.html) or an >>>> end-product development ( >>>> http://www.kitware.com/products/consulting.html). >>>> >>>> Seb >>>> >>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? >>>> wrote: >>>> >>>>> thank you, ok. try to understand. I put the stable version and not the >>>>> release candidate. >>>>> >>>>> But there are a few more questions. >>>>> Do files are responsible for localization? I need to replace the >>>>> language in the design parawiewweb. >>>>> And the second. Is there a possibility of the file from which the >>>>> object is loaded into the web, continuously read the data? That is to >>>>> update the image in the browser loading new data, but this is not in >>>>> the manual and automatic. >>>>> >>>>> Sincerely, >>>>> Sukhachev Ilya! >>>>> >>>>> >>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>> sebastien.jourdain at kitware.com>: >>>>> >>>>>> The top bar is not green anymore. Try to replace the directory /lib, >>>>>> /apps, /ext within the ParaView /www inside the directory you serve with >>>>>> Apache. >>>>>> Moreover, can you enable the development tools on your browser to see >>>>>> what kind of error you got? >>>>>> >>>>>> Did you look also at the different types of logs? Apache, Launcher >>>>>> (see config to know where you choose to put them). >>>>>> That could also give you an idea on what went wrong. >>>>>> >>>>>> Seb >>>>>> >>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? >>>>>> wrote: >>>>>> >>>>>>> Hi, Sebastien >>>>>>> >>>>>>> Thank you. >>>>>>> I just took advantage of this documentation and to deploy. >>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>> But when entering the address: http://localhost/apps/Visualizer is >>>>>>> only displayed only the green bar at the top of the window, and >>>>>>> nothing more. >>>>>>> That in this case? >>>>>>> >>>>>>> Sincerely, >>>>>>> Sukhachev Ilya! >>>>>>> >>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>> sebastien.jourdain at kitware.com>: >>>>>>> >>>>>>>> Moreover, the documentation that get's updated automatically can be >>>>>>>> found at the following address. (Which might be more accurate.) >>>>>>>> >>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>> >>>>>>>> This is the one you find when you go on paraview.org and go to the >>>>>>>> documentation section. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>> >>>>>>>>> Hi Sukhachev, >>>>>>>>> >>>>>>>>> The one thing that might not be explicit about the ubuntu_14_04 >>>>>>>>> guide might be that the script "/data/pvw/bin/start.sh" should be >>>>>>>>> launched with a DISPLAY setup. >>>>>>>>> Otherwise, you will have to be more explicit on what you've done >>>>>>>>> and what is not working. The log files usually helps to see what >>>>>>>>> was skipped from the documentation. >>>>>>>>> >>>>>>>>> Seb >>>>>>>>> >>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Good day! >>>>>>>>>> Prompt please. >>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>> Paraviewweb (http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04 >>>>>>>>>> ) >>>>>>>>>> Unfolded, but for some reason I can not open in the web browser Visualizer >>>>>>>>>> (http: // localhost / apps / Visualizer /) >>>>>>>>>> When deployment by using the ( >>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I can run only >>>>>>>>>> as 1 Ceci. >>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>> Thank you >>>>>>>>>> >>>>>>>>>> Sincerely, >>>>>>>>>> Sukhachev Ilya! >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Fri Oct 3 06:46:30 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 03 Oct 2014 12:46:30 +0200 Subject: [Paraview] Intersection a source with a grid? Message-ID: <542E7E86.4090006@xs4all.nl> I need to fill the interior of a CubeSource, a SphereSource etc. with points that lie on a (HCP) grid. The lattice constant of the grid is a parameter. Can this be done in ParaView? Any hint to the solution is appreciated. Kind Regards, Bertwim From cory.quammen at kitware.com Fri Oct 3 09:11:19 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 3 Oct 2014 09:11:19 -0400 Subject: [Paraview] default representation? In-Reply-To: <542E0F07.8050704@xs4all.nl> References: <542E0F07.8050704@xs4all.nl> Message-ID: Bertwim, Ken is right, the default representation is chosen by the view in which the source output is displayed. See, for instance, ParaView/ParaViewCore/ServerManager/Rendering/vtkSMRenderViewProxy::GetRepresentationType() for the logic used to pick the default representation used in the 3D View. - Cory On Thu, Oct 2, 2014 at 10:50 PM, B.W.H. van Beest wrote: > It is just a box, sphere, etc (originating from vtkCubeSource, > vtpSPhereSource). > I want to display them initially in a wireframe representation. > > Regards, > Bertwim > > On 10/02/2014 08:38 PM, Moreland, Kenneth wrote: >> As far as I know (and anyone else on the list is welcome to correct me), >> you cannot directly change the default representation for the output of a >> source/filter. The default representation is automatically chosen based on >> the type of the data and the view it is being shown in. >> >> >> What kind of data is the output from your source? >> >> -Ken >> >> On 10/2/14, 10:37 AM, "B.W.H. van Beest" wrote: >> >>> But how can I set the default, especially for a new source? >>> >>> >>> Regards, >>> Bertwim >>> >>> On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: >>>> The default representation is based more on the data type than the >>>> filter >>>> setup. I forget all the rules, but I believe that structured data types >>>> (like uniform and non-uniform rectilinear grids and curvilinear grids) >>>> default to outline. Unstructured data types (like poly data or >>>> unstructured grids) default to surface unless the size is larger than >>>> some >>>> threshold (which can be changed in settings). Multiblock data sets >>>> default >>>> to whatever is appropriate for the data type in the blocks. >>>> >>>> >>>> The rational for this behavior is that an unstructured data type likely >>>> represents some geometry of importance whereas a regular grid more >>>> likely >>>> represents some region in space where the relevant structure is >>>> internal. >>>> >>>> -Ken >>>> >>>> On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >>>> >>>>> Hello, >>>>> >>>>> I noticed that sources like a box, sphere etc., are always displayed >>>>> initially with a surface representation, after which ione can set it >>>>> manually to something else, e.g. a wireframe. Where is this preference >>>>> being set? I cannot find it in the sources.xml file or in any of the >>>>> other xml files, but maybe I don't recognise it. >>>>> >>>>> Background of this is that I would like to change this default >>>>> behaviour, in particular for some new sources I'm creating in a plugin. >>>>> (The sources that are derived from the standard ones.) >>>>> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Fri Oct 3 10:01:05 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 3 Oct 2014 10:01:05 -0400 Subject: [Paraview] default representation? In-Reply-To: References: <542E0F07.8050704@xs4all.nl> Message-ID: Here are a few points to note: There are two parts to choosing the default representation: (a) Picking the representation proxy to use (b) Picking which "Representation" type (e.g. Surface/Wireframe etc.) to use -- this currently is only relevant for representations in Render Views (or similar). (a) happens with code pointed to by Cory (vtkSMRenderViewProxy::GetRepresentationType). For representations in "Render View", (b) happens in vtkSMRepresentationTypeDomain::SetDefaultValues(). To display everything as "Wireframe", you're looking at changing (b), more so than (a). Utkarsh On Fri, Oct 3, 2014 at 9:11 AM, Cory Quammen wrote: > Bertwim, > > Ken is right, the default representation is chosen by the view in > which the source output is displayed. See, for instance, > > ParaView/ParaViewCore/ServerManager/Rendering/vtkSMRenderViewProxy::GetRepresentationType() > > for the logic used to pick the default representation used in the 3D View. > > - Cory > > On Thu, Oct 2, 2014 at 10:50 PM, B.W.H. van Beest wrote: >> It is just a box, sphere, etc (originating from vtkCubeSource, >> vtpSPhereSource). >> I want to display them initially in a wireframe representation. >> >> Regards, >> Bertwim >> >> On 10/02/2014 08:38 PM, Moreland, Kenneth wrote: >>> As far as I know (and anyone else on the list is welcome to correct me), >>> you cannot directly change the default representation for the output of a >>> source/filter. The default representation is automatically chosen based on >>> the type of the data and the view it is being shown in. >>> >>> >>> What kind of data is the output from your source? >>> >>> -Ken >>> >>> On 10/2/14, 10:37 AM, "B.W.H. van Beest" wrote: >>> >>>> But how can I set the default, especially for a new source? >>>> >>>> >>>> Regards, >>>> Bertwim >>>> >>>> On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: >>>>> The default representation is based more on the data type than the >>>>> filter >>>>> setup. I forget all the rules, but I believe that structured data types >>>>> (like uniform and non-uniform rectilinear grids and curvilinear grids) >>>>> default to outline. Unstructured data types (like poly data or >>>>> unstructured grids) default to surface unless the size is larger than >>>>> some >>>>> threshold (which can be changed in settings). Multiblock data sets >>>>> default >>>>> to whatever is appropriate for the data type in the blocks. >>>>> >>>>> >>>>> The rational for this behavior is that an unstructured data type likely >>>>> represents some geometry of importance whereas a regular grid more >>>>> likely >>>>> represents some region in space where the relevant structure is >>>>> internal. >>>>> >>>>> -Ken >>>>> >>>>> On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I noticed that sources like a box, sphere etc., are always displayed >>>>>> initially with a surface representation, after which ione can set it >>>>>> manually to something else, e.g. a wireframe. Where is this preference >>>>>> being set? I cannot find it in the sources.xml file or in any of the >>>>>> other xml files, but maybe I don't recognise it. >>>>>> >>>>>> Background of this is that I would like to change this default >>>>>> behaviour, in particular for some new sources I'm creating in a plugin. >>>>>> (The sources that are derived from the standard ones.) >>>>>> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>> >>> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From scott.wittenburg at kitware.com Fri Oct 3 10:58:42 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Fri, 3 Oct 2014 08:58:42 -0600 Subject: [Paraview] Help me In-Reply-To: References: Message-ID: On Fri, Oct 3, 2014 at 12:03 AM, Ilya Sukhachev wrote: > Good day! > Thank. > > 2014-10-02 21:10 GMT+06:00 Scott Wittenburg > : > > > On Thu, Oct 2, 2014 at 2:48 AM, Ilya Sukhachev > wrote: >> >> Why update the browser page when it loses the session? Starts a new >> process in nature. Is there any way to fix this? >> >> I'm not sure what you are asking here. What do you mean by "update the > browser page"? > > *Go to page http://localhost/apps/Visualizer/ > . We perform a series of actions. Press > F5. All flies. Session is lost.* > > Pressing F5 causes your page to reload, which triggers the event handlers I mentioned yesterday. If you don't want to close session when reloading page, you have to change the "stop" functionality set up in the index.html > When you disable the client (browser), the session remains on the server to >> hang. How to deal with it? >> >> See the index.html for your particular application. The body tag has > event handlers attached that will call the stop method when you close the > tab or hit the back button. In that stop method, you can do what you like, > like calling the rpc method "application.exit". > > *Good. Thank you. And please tell me where the class for the method to > "application.exit"? And at what point is the creation of a compound?* > > See "wamp.py". In the source tree, it's VTK/Web/Python/vtk/web/wamp.py. > When you connect multiple clients, very often produces the message: >> "Session did not start before timeout expired. Check session logs." >> Add a log file with errors, unless of course it will help. What could the >> reason for this? >> >> I looked briefly at your log files, and I'm not sure what could be going > on. Can all your clients reach the host where the pvpython processes are > running? > > > > *Go to page http://SERVER_IP/apps/Visualizer > . Displays your inscription ParaViewWeb. > Spinning wheel. And then the following message appears: "Session did not > start before timeout expired. Check session logs." And when such a couple > of users are connected. Helps to restart. But 3-5 sessions and the > application starts to behave inadequately.* > > > Again, I'm not sure what could be going on here. Usually, 3-5 session shouldn't be a problem. If you start running more than that, you might consider distributing the load a bit, see the Launching Examples guide for information about using multiple machines to host pvpython processes. http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/launching_examples > Ilya > > 2014-10-02 21:10 GMT+06:00 Scott Wittenburg > : > >> >> >> On Thu, Oct 2, 2014 at 2:48 AM, Ilya Sukhachev >> wrote: >> >>> Good day. >>> >>> Sorry. Not the file sent. >>> Attach desired. >>> Everything worked. >>> But there are a couple of questions. >>> >>> Glad you got something working. >> >> >>> Why update the browser page when it loses the session? Starts a new >>> process in nature. Is there any way to fix this? >>> >>> I'm not sure what you are asking here. What do you mean by "update the >> browser page"? >> >> >>> When you disable the client (browser), the session remains on the server to >>> hang. How to deal with it? >>> >>> See the index.html for your particular application. The body tag has >> event handlers attached that will call the stop method when you close the >> tab or hit the back button. In that stop method, you can do what you like, >> like calling the rpc method "application.exit". >> >> >>> When you connect multiple clients, very often produces the message: >>> "Session did not start before timeout expired. Check session logs." >>> Add a log file with errors, unless of course it will help. What could the >>> reason for this? >>> >>> I looked briefly at your log files, and I'm not sure what could be going >> on. Can all your clients reach the host where the pvpython processes are >> running? >> >> Cheers, >> Scott >> >> >> >>> Sincerely, Ilya >>> >>> 2014-10-01 20:09 GMT+06:00 Scott Wittenburg < >>> scott.wittenburg at kitware.com>: >>> >>>> The launcher config file you sent to the list was missing a >>>> "visualizer" entry, but those instructions have one. Other than that, are >>>> things working properly now? When we do find problems with the >>>> instructions, we try to fix them, but I'm not sure yet if this is one of >>>> those cases. >>>> >>>> Cheers, >>>> Scott >>>> >>>> On Wed, Oct 1, 2014 at 6:06 AM, Ilya Sukhachev >>>> wrote: >>>> >>>>> Good day. >>>>> >>>>> For the settings I used your instruction online >>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/ubuntu_14_04 >>>>> . >>>>> Did everything there. Would you say it does not work? >>>>> >>>>> Ilya >>>>> >>>>> 2014-09-30 20:43 GMT+06:00 Scott Wittenburg < >>>>> scott.wittenburg at kitware.com>: >>>>> >>>>>> Your client side request to the launcher is asking for the >>>>>> "visualizer" application, while the launcher (according to your launcher >>>>>> config) doesn't know about a command line to start that application. Try >>>>>> changing the "pipeline" key under the "apps" section to "visualizer". >>>>>> >>>>>> Cheers, >>>>>> Scott >>>>>> >>>>>> >>>>>> On Mon, Sep 29, 2014 at 9:36 PM, Ilya Sukhachev < >>>>>> lifeandfree at gmail.com> wrote: >>>>>> >>>>>>> Good day! >>>>>>> >>>>>>> Yes, of course >>>>>>> Attached. >>>>>>> Also put the configuration file Apache. >>>>>>> >>>>>>> Ilya >>>>>>> >>>>>>> 2014-09-29 20:54 GMT+06:00 Scott Wittenburg < >>>>>>> scott.wittenburg at kitware.com>: >>>>>>> >>>>>>>> Can you share your launcher configuration file? It appears you may >>>>>>>> have no "visualizer" application command line configured. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Scott >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Sep 29, 2014 at 1:43 AM, ???? ??????? < >>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> And there is another question. >>>>>>>>> Deployed software. I go to http://localhost/apps/Visualizer /. As >>>>>>>>> a result, I see only the inscription ParaViewWeb and flailing >>>>>>>>> wheel. And he gave me a list of errors in the console: >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1439, in dataReceived >>>>>>>>> finishCallback(data[contentLength:]) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1668, in _finishRequestBody >>>>>>>>> self.allContentReceived() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 1731, in allContentReceived >>>>>>>>> req.requestReceived(command, path, version) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/http.py", >>>>>>>>> line 827, in requestReceived >>>>>>>>> self.process() >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 189, in process >>>>>>>>> self.render(resrc) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 238, in render >>>>>>>>> body = resrc.render(self) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/resource.py", >>>>>>>>> line 250, in render >>>>>>>>> return m(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 399, in render_POST >>>>>>>>> session = self.session_manager.createSession(payload) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-current/lib/paraview-4.2/site-packages/vtk/web/launcher.py", >>>>>>>>> line 182, in createSession >>>>>>>>> options['cmd'] = >>>>>>>>> replaceList(self.config['apps'][options['application']]['cmd'], [options, >>>>>>>>> self.config['properties']]) >>>>>>>>> exceptions.KeyError: u'visualizer' >>>>>>>>> Unhandled Error >>>>>>>>> Traceback (most recent call last): >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/server.py", >>>>>>>>> line 321, in processingFailed >>>>>>>>> % webutil.formatFailure(reason)) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/util.py", >>>>>>>>> line 425, in formatFailure >>>>>>>>> flattenString(None, >>>>>>>>> FailureElement(myFailure)).addBoth(result.append) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 420, in flattenString >>>>>>>>> d = flatten(request, root, io.write) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 402, in flatten >>>>>>>>> _writeFlattenedData(state, write, result) >>>>>>>>> --- --- >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 359, in _writeFlattenedData >>>>>>>>> element = state.next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 326, in _flattenTree >>>>>>>>> raise FlattenerError(e, roots, extract_tb(exc_info()[2])) >>>>>>>>> twisted.web.error.FlattenerError: Exception while flattening: >>>>>>>>> >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 317, in _flattenTree >>>>>>>>> element = stack[-1].next() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_flatten.py", >>>>>>>>> line 286, in _flattenElement >>>>>>>>> result = root.render(request) >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/_element.py", >>>>>>>>> line 184, in render >>>>>>>>> return loader.load() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 465, in load >>>>>>>>> self._loadedTemplate = self._loadDoc() >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/template.py", >>>>>>>>> line 446, in _loadDoc >>>>>>>>> f = self._path.open('r') >>>>>>>>> File >>>>>>>>> "/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/python/filepath.py", >>>>>>>>> line 828, in open >>>>>>>>> return open(self.path, mode + 'b') >>>>>>>>> IOError: [Errno 2] No such file or directory: >>>>>>>>> '/data/pv/pv-20140410/lib/paraview-4.2/site-packages/twisted/web/failure.xhtml' >>>>>>>>> >>>>>>>>> >>>>>>>>> In logs file error.log: >>>>>>>>> [Mon Sep 29 13:34:03.884092 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533745776384] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38924] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.905642 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533720598272] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38923] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.908441 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533787739904] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38925] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.923450 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533762561792] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38926] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.925919 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533754169088] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38922] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.928206 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533745776384] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38921] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.930176 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533737383680] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38933] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:03.930197 2014] [proxy:error] [pid 14563:tid >>>>>>>>> 140533737383680] [client 127.0.0.1:38933] AH00898: Error reading >>>>>>>>> from remote server returned by /paraview/, referer: >>>>>>>>> http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.357181 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533787739904] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38939] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.359293 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533762561792] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38940] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.361335 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533829703424] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38944] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.363796 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533854881536] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38943] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.366176 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533821310720] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38942] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.368434 2014] [proxy_http:error] [pid >>>>>>>>> 14562:tid 140533804525312] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38941] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.370937 2014] [proxy_http:error] [pid >>>>>>>>> 14563:tid 140533754169088] (20014)Internal error: [client >>>>>>>>> 127.0.0.1:38951] AH01102: error reading status line from remote >>>>>>>>> server localhost:8080, referer: http://localhost/apps/Visualizer/ >>>>>>>>> [Mon Sep 29 13:34:20.370960 2014] [proxy:error] [pid 14563:tid >>>>>>>>> 140533754169088] [client 127.0.0.1:38951] AH00898: Error reading >>>>>>>>> from remote server returned by /paraview/, referer: >>>>>>>>> http://localhost/apps/Visualizer/ >>>>>>>>> >>>>>>>>> >>>>>>>>> 2014-09-29 10:30 GMT+06:00 ???? ??????? : >>>>>>>>> >>>>>>>>>> Good day. >>>>>>>>>> Thank you. >>>>>>>>>> >>>>>>>>>> You may be able to explain. What kind of filter is it? >>>>>>>>>> >>>>>>>>>> Ilya >>>>>>>>>> >>>>>>>>>> 2014-09-26 20:18 GMT+06:00 Sebastien Jourdain < >>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>> >>>>>>>>>>> ParaView 4.2 has been released, so that would be the latest >>>>>>>>>>> stable version available. >>>>>>>>>>> There is no localization per say but the filter names could be >>>>>>>>>>> customized the way you want. >>>>>>>>>>> >>>>>>>>>>> For continuous live visualization it is possible but that will >>>>>>>>>>> be a custom development. And for that you can contact Kitware for either a >>>>>>>>>>> support contract (http://www.kitware.com/products/support.html) >>>>>>>>>>> or an end-product development ( >>>>>>>>>>> http://www.kitware.com/products/consulting.html). >>>>>>>>>>> >>>>>>>>>>> Seb >>>>>>>>>>> >>>>>>>>>>> On Fri, Sep 26, 2014 at 4:57 AM, ???? ??????? < >>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> thank you, ok. try to understand. I put the stable version and >>>>>>>>>>>> not the release candidate. >>>>>>>>>>>> >>>>>>>>>>>> But there are a few more questions. >>>>>>>>>>>> Do files are responsible for localization? I need to replace >>>>>>>>>>>> the language in the design parawiewweb. >>>>>>>>>>>> And the second. Is there a possibility of the file from which the >>>>>>>>>>>> object is loaded into the web, continuously read the data? That >>>>>>>>>>>> is to update the image in the browser loading new data, but >>>>>>>>>>>> this is not in the manual and automatic. >>>>>>>>>>>> >>>>>>>>>>>> Sincerely, >>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> 2014-09-25 19:21 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>> >>>>>>>>>>>>> The top bar is not green anymore. Try to replace the directory >>>>>>>>>>>>> /lib, /apps, /ext within the ParaView /www inside the directory you serve >>>>>>>>>>>>> with Apache. >>>>>>>>>>>>> Moreover, can you enable the development tools on your browser >>>>>>>>>>>>> to see what kind of error you got? >>>>>>>>>>>>> >>>>>>>>>>>>> Did you look also at the different types of logs? Apache, >>>>>>>>>>>>> Launcher (see config to know where you choose to put them). >>>>>>>>>>>>> That could also give you an idea on what went wrong. >>>>>>>>>>>>> >>>>>>>>>>>>> Seb >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Sep 25, 2014 at 3:02 AM, ???? ??????? < >>>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, Sebastien >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thank you. >>>>>>>>>>>>>> I just took advantage of this documentation and to deploy. >>>>>>>>>>>>>> I ran the script /data/pvw/bin/start.sh. >>>>>>>>>>>>>> But when entering the address: >>>>>>>>>>>>>> http://localhost/apps/Visualizer is only displayed only the >>>>>>>>>>>>>> green bar at the top of the window, and nothing more. >>>>>>>>>>>>>> That in this case? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2014-09-24 20:33 GMT+06:00 Sebastien Jourdain < >>>>>>>>>>>>>> sebastien.jourdain at kitware.com>: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Moreover, the documentation that get's updated automatically >>>>>>>>>>>>>>> can be found at the following address. (Which might be more accurate.) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> This is the one you find when you go on paraview.org and go >>>>>>>>>>>>>>> to the documentation section. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Seb >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 24, 2014 at 8:30 AM, Sebastien Jourdain < >>>>>>>>>>>>>>> sebastien.jourdain at kitware.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Sukhachev, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> The one thing that might not be explicit about the >>>>>>>>>>>>>>>> ubuntu_14_04 guide might be that the script "/data/pvw/bin/ >>>>>>>>>>>>>>>> start.sh" should be launched with a DISPLAY setup. >>>>>>>>>>>>>>>> Otherwise, you will have to be more explicit on what you've >>>>>>>>>>>>>>>> done and what is not working. The log files usually helps to see what >>>>>>>>>>>>>>>> was skipped from the documentation. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Seb >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Sep 23, 2014 at 11:30 PM, ???? ??????? < >>>>>>>>>>>>>>>> lifeandfree at gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Good day! >>>>>>>>>>>>>>>>> Prompt please. >>>>>>>>>>>>>>>>> I used the instructions for deployment on Linux Ubuntu >>>>>>>>>>>>>>>>> Paraviewweb ( >>>>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/ubuntu_14_04) >>>>>>>>>>>>>>>>> Unfolded, but for some reason I can not open in the web >>>>>>>>>>>>>>>>> browser Visualizer (http: // localhost / apps / >>>>>>>>>>>>>>>>> Visualizer /) >>>>>>>>>>>>>>>>> When deployment by using the ( >>>>>>>>>>>>>>>>> http://paraviewweb.kitware.com/#!/guide/quick_start), I >>>>>>>>>>>>>>>>> can run only as 1 Ceci. >>>>>>>>>>>>>>>>> How do I get access to many jobs, and through the web? >>>>>>>>>>>>>>>>> Thank you >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Sincerely, >>>>>>>>>>>>>>>>> Sukhachev Ilya! >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki >>>>>>>>>>>>>>>>> at: http://paraview.org/Wiki/ParaView >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> ? ?????????, >>>>>>>>>>>>>> ??????? ????! >>>>>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> ? ?????????, >>>>>>>>>>>> ??????? ????! >>>>>>>>>>>> +7 912 216 72 72 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> ? ?????????, >>>>>>>>>> ??????? ????! >>>>>>>>>> +7 912 216 72 72 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> ? ?????????, >>>>>>>>> ??????? ????! >>>>>>>>> +7 912 216 72 72 >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> ? ?????????, >>>>>>> ??????? ????! >>>>>>> +7 912 216 72 72 >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> ? ?????????, >>>>> ??????? ????! >>>>> +7 912 216 72 72 >>>>> >>>> >>>> >>> >>> >>> -- >>> ? ?????????, >>> ??????? ????! >>> +7 912 216 72 72 >>> >> >> > > > -- > ? ?????????, > ??????? ????! > +7 912 216 72 72 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Fri Oct 3 11:59:18 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 03 Oct 2014 17:59:18 +0200 Subject: [Paraview] default representation? In-Reply-To: References: <542E0F07.8050704@xs4all.nl> Message-ID: <542EC7D6.6010500@xs4all.nl> Cory, Ken , All, Thanks for looking into this. Maybe resetting the default was a bit too ambitious. It is a bit annoying, though, that I cannot display the 'my own source" the first time right. regards, Bertwim On 10/03/2014 03:11 PM, Cory Quammen wrote: > Bertwim, > > Ken is right, the default representation is chosen by the view in > which the source output is displayed. See, for instance, > > ParaView/ParaViewCore/ServerManager/Rendering/vtkSMRenderViewProxy::GetRepresentationType() > > for the logic used to pick the default representation used in the 3D View. > > - Cory > > On Thu, Oct 2, 2014 at 10:50 PM, B.W.H. van Beest wrote: >> It is just a box, sphere, etc (originating from vtkCubeSource, >> vtpSPhereSource). >> I want to display them initially in a wireframe representation. >> >> Regards, >> Bertwim >> >> On 10/02/2014 08:38 PM, Moreland, Kenneth wrote: >>> As far as I know (and anyone else on the list is welcome to correct me), >>> you cannot directly change the default representation for the output of a >>> source/filter. The default representation is automatically chosen based on >>> the type of the data and the view it is being shown in. >>> >>> >>> What kind of data is the output from your source? >>> >>> -Ken >>> >>> On 10/2/14, 10:37 AM, "B.W.H. van Beest" wrote: >>> >>>> But how can I set the default, especially for a new source? >>>> >>>> >>>> Regards, >>>> Bertwim >>>> >>>> On 10/02/2014 04:55 PM, Moreland, Kenneth wrote: >>>>> The default representation is based more on the data type than the >>>>> filter >>>>> setup. I forget all the rules, but I believe that structured data types >>>>> (like uniform and non-uniform rectilinear grids and curvilinear grids) >>>>> default to outline. Unstructured data types (like poly data or >>>>> unstructured grids) default to surface unless the size is larger than >>>>> some >>>>> threshold (which can be changed in settings). Multiblock data sets >>>>> default >>>>> to whatever is appropriate for the data type in the blocks. >>>>> >>>>> >>>>> The rational for this behavior is that an unstructured data type likely >>>>> represents some geometry of importance whereas a regular grid more >>>>> likely >>>>> represents some region in space where the relevant structure is >>>>> internal. >>>>> >>>>> -Ken >>>>> >>>>> On 10/2/14, 7:53 AM, "B.W.H. van Beest" wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I noticed that sources like a box, sphere etc., are always displayed >>>>>> initially with a surface representation, after which ione can set it >>>>>> manually to something else, e.g. a wireframe. Where is this preference >>>>>> being set? I cannot find it in the sources.xml file or in any of the >>>>>> other xml files, but maybe I don't recognise it. >>>>>> >>>>>> Background of this is that I would like to change this default >>>>>> behaviour, in particular for some new sources I'm creating in a plugin. >>>>>> (The sources that are derived from the standard ones.) >>>>>> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>> http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From ben.boeckel at kitware.com Fri Oct 3 23:00:44 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 3 Oct 2014 23:00:44 -0400 Subject: [Paraview] PV 4.2.0 make install error (UNCLASSIFIED) In-Reply-To: References: <20140930150356.GC12969@megas.kitwarein.com> <20140930154210.GA6846@megas.kitwarein.com> <20140930211540.GA25473@megas.kitwarein.com> Message-ID: <20141004030044.GA12740@bronto-burt.dev.benboeckel.net> On Wed, Oct 01, 2014 at 17:15:34 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I think your patch worked. Cmake not complaining all the way to the end. The patch has been merged into master now. --Ben From Marschmann at stud.uni-heidelberg.de Sat Oct 4 04:14:50 2014 From: Marschmann at stud.uni-heidelberg.de (Marschmann at stud.uni-heidelberg.de) Date: Sat, 04 Oct 2014 10:14:50 +0200 Subject: [Paraview] calculator tensor field Message-ID: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> Hello everyone, I have three displacement field vector components u, v, w in my .vtk file and wish to display the associated stress tensor. I made the following steps: - Apply the filter Gradient Of Unstructued DataSet -> Now have 9 scalars Gradient_0, ... , Gradient 8 - compute components of stress tensor via sigma_ij = div(Gradient) + u_i,j -> Now have additional 9 scalars sigma_ij - from this form traction vectors: T_i = sigma_ij e_j ,where e_j are the unit vectors iHat -> Now have three traction vectors from which the tensor field computation doesnt work: - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor calculation and get the following error message: ERROR: In /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, line 201 vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous operators ERROR: In /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, line 300 vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar and a vector ERROR: In /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, line 201 vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous operators - Can you help me or tell me gow to visualize the stress tensor from the displacement field? - Alternatively you it would also be good to know how to multiply the result of filter Gradient of Unstructured DataSet by a scalar value. Many thanks for helping! Gianna From bwvb at xs4all.nl Sat Oct 4 11:30:37 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 04 Oct 2014 17:30:37 +0200 Subject: [Paraview] new Source plugin: no show! Message-ID: <5430129D.3020508@xs4all.nl> Hello, I need to write a new Source, representing a 'TriPrism", i.e. a prism where the top and bottom planes are triangles. So far, I failed. Being unable to find appropriate documentation, I used the source code of vtkCubeSource as an example, thinking it would be an easy change. Wrong! The prism doesn't show on the screen. The properties panel behaves as expected (and ok, as far I can see). The member function 'RequestData' seems to be the important method. But the code of the example (as well as other source examples) is on closer inspection not clear to me at all. The following is happening in the vtkCubeSource: a) The point of the cube are generated. This is straightforward and easily translates to the triprism. The new points are updated via a call "output->setPoints( newPoints );" b) The normals (to the side planes of the cube) are being calculated. The new normals are updated via a call "output->GetPointData()->SetNormals(newNormals);" This is also straightforward for the triprism, but: Q: although calculating the normals is straightforward, in which order are they supposed to be given? c) Also, texture coordinates (TCoords) are calculated. Q: What are these? Are these mandatory? d) Also, a new vtkCellArray is being created. ('newPolys') Q: Same question. No clue what I should do here. As usual, any clue of how to attack this is greatly appreciated. Bertwim From bloring at lbl.gov Sat Oct 4 23:05:16 2014 From: bloring at lbl.gov (Burlen Loring) Date: Sat, 04 Oct 2014 20:05:16 -0700 Subject: [Paraview] new Source plugin: no show! In-Reply-To: <5430129D.3020508@xs4all.nl> References: <5430129D.3020508@xs4all.nl> Message-ID: <5430B56C.2090208@lbl.gov> I assume in your request data you are generating a vtkPolyData dataset. At the end of request data call "dataset->Print(cerr);" . That's the one of the best debug method when you don't see what you think you should in PV while developing a new filter/source/reader what ever. The information tab in the GUI gives a subset of that, also useful. texture coordinates are usually for applying an image to the surface. google it and you'll find volumes of info. In pv they are optional. the cell array I'm afraid is not. when generating poly or unstructured data. If you have no cells what do you expect to see? normals are per point. some of your questions suggest that the book VTK user guide would be a good investment for you. Hope I didn't miss anything. ;-) On 10/4/2014 8:30 AM, B.W.H. van Beest wrote: > Hello, > > I need to write a new Source, representing a 'TriPrism", > i.e. a prism where the top and bottom planes are triangles. So far, I > failed. > > Being unable to find appropriate documentation, I used the source code > of vtkCubeSource as an example, thinking it would be an easy change. > Wrong! The prism doesn't show on the screen. The > properties panel behaves as expected (and ok, as far I can see). > > The member function 'RequestData' seems to be the important method. > But the code of the example (as well as other source examples) is on > closer inspection not clear to me at all. > > The following is happening in the vtkCubeSource: > > a) The point of the cube are generated. This is straightforward and > easily > translates to the triprism. > The new points are updated via a call "output->setPoints( > newPoints );" > > b) The normals (to the side planes of the cube) are being calculated. > The new normals are updated via a call > "output->GetPointData()->SetNormals(newNormals);" > This is also straightforward for the triprism, but: > > Q: although calculating the normals is straightforward, > in which order are they supposed to be given? > > c) Also, texture coordinates (TCoords) are calculated. > Q: What are these? Are these mandatory? > > d) Also, a new vtkCellArray is being created. ('newPolys') > Q: Same question. No clue what I should do here. > > As usual, any clue of how to attack this is greatly appreciated. > > Bertwim > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Sun Oct 5 11:17:33 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sun, 05 Oct 2014 17:17:33 +0200 Subject: [Paraview] new Source plugin: no show! In-Reply-To: <5430B56C.2090208@lbl.gov> References: <5430129D.3020508@xs4all.nl> <5430B56C.2090208@lbl.gov> Message-ID: <5431610D.2030403@xs4all.nl> Hi Burlen, Thanks for your reply. On the cell-info: I now (finally) understood what was there to be. After implementing the cells, I indeed got the expected display. On the book: what keeps me from buying is that it seems outdated (because it refers to version 3). The texture coordinates I had found on Google indeed. What I needed was how to apply it in Paraview/VTK. I will look into that again Maybe it becomes clear now. Thanks Bertwim On 10/05/2014 05:05 AM, Burlen Loring wrote: > I assume in your request data you are generating a vtkPolyData > dataset. At the end of request data call "dataset->Print(cerr);" . > That's the one of the best debug method when you don't see what you > think you should in PV while developing a new filter/source/reader > what ever. The information tab in the GUI gives a subset of that, also > useful. > > texture coordinates are usually for applying an image to the surface. > google it and you'll find volumes of info. In pv they are optional. > > the cell array I'm afraid is not. when generating poly or unstructured > data. If you have no cells what do you expect to see? > > normals are per point. > > some of your questions suggest that the book VTK user guide > would be a good > investment for you. > > Hope I didn't miss anything. ;-) > > On 10/4/2014 8:30 AM, B.W.H. van Beest wrote: >> Hello, >> >> I need to write a new Source, representing a 'TriPrism", >> i.e. a prism where the top and bottom planes are triangles. So far, I >> failed. >> >> Being unable to find appropriate documentation, I used the source code >> of vtkCubeSource as an example, thinking it would be an easy change. >> Wrong! The prism doesn't show on the screen. The >> properties panel behaves as expected (and ok, as far I can see). >> >> The member function 'RequestData' seems to be the important method. >> But the code of the example (as well as other source examples) is on >> closer inspection not clear to me at all. >> >> The following is happening in the vtkCubeSource: >> >> a) The point of the cube are generated. This is straightforward and >> easily >> translates to the triprism. >> The new points are updated via a call "output->setPoints( >> newPoints );" >> >> b) The normals (to the side planes of the cube) are being calculated. >> The new normals are updated via a call >> "output->GetPointData()->SetNormals(newNormals);" >> This is also straightforward for the triprism, but: >> >> Q: although calculating the normals is straightforward, >> in which order are they supposed to be given? >> >> c) Also, texture coordinates (TCoords) are calculated. >> Q: What are these? Are these mandatory? >> >> d) Also, a new vtkCellArray is being created. ('newPolys') >> Q: Same question. No clue what I should do here. >> >> As usual, any clue of how to attack this is greatly appreciated. >> >> Bertwim >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Sun Oct 5 11:26:25 2014 From: bloring at lbl.gov (Burlen Loring) Date: Sun, 05 Oct 2014 08:26:25 -0700 Subject: [Paraview] new Source plugin: no show! In-Reply-To: <5431610D.2030403@xs4all.nl> References: <5430129D.3020508@xs4all.nl> <5430B56C.2090208@lbl.gov> <5431610D.2030403@xs4all.nl> Message-ID: <54316321.2080000@lbl.gov> Hi Bertwim, I should have explained the cells better. The cells are descriptions of how points are combined into geometric primitives that can be rendered by OpenGL (or converted into those understood by OpenGL). Here is an excerpt of the User Guide describing VTK's cells, see p9-10. Burlen On 10/5/2014 8:17 AM, B.W.H. van Beest wrote: > Hi Burlen, > > Thanks for your reply. On the cell-info: I now (finally) understood > what was there to be. After implementing the cells, I indeed got the > expected display. On the book: what keeps me from buying is that it > seems outdated (because it refers to version 3). > The texture coordinates I had found on Google indeed. What I needed > was how to apply it in Paraview/VTK. I will look into that again Maybe > it becomes clear now. > > Thanks > Bertwim > > > On 10/05/2014 05:05 AM, Burlen Loring wrote: >> I assume in your request data you are generating a vtkPolyData >> dataset. At the end of request data call "dataset->Print(cerr);" . >> That's the one of the best debug method when you don't see what you >> think you should in PV while developing a new filter/source/reader >> what ever. The information tab in the GUI gives a subset of that, >> also useful. >> >> texture coordinates are usually for applying an image to the surface. >> google it and you'll find volumes of info. In pv they are optional. >> >> the cell array I'm afraid is not. when generating poly or >> unstructured data. If you have no cells what do you expect to see? >> >> normals are per point. >> >> some of your questions suggest that the book VTK user guide >> would be a good >> investment for you. >> >> Hope I didn't miss anything. ;-) >> >> On 10/4/2014 8:30 AM, B.W.H. van Beest wrote: >>> Hello, >>> >>> I need to write a new Source, representing a 'TriPrism", >>> i.e. a prism where the top and bottom planes are triangles. So far, I >>> failed. >>> >>> Being unable to find appropriate documentation, I used the source code >>> of vtkCubeSource as an example, thinking it would be an easy change. >>> Wrong! The prism doesn't show on the screen. The >>> properties panel behaves as expected (and ok, as far I can see). >>> >>> The member function 'RequestData' seems to be the important method. >>> But the code of the example (as well as other source examples) is on >>> closer inspection not clear to me at all. >>> >>> The following is happening in the vtkCubeSource: >>> >>> a) The point of the cube are generated. This is straightforward and >>> easily >>> translates to the triprism. >>> The new points are updated via a call "output->setPoints( >>> newPoints );" >>> >>> b) The normals (to the side planes of the cube) are being calculated. >>> The new normals are updated via a call >>> "output->GetPointData()->SetNormals(newNormals);" >>> This is also straightforward for the triprism, but: >>> >>> Q: although calculating the normals is straightforward, >>> in which order are they supposed to be given? >>> >>> c) Also, texture coordinates (TCoords) are calculated. >>> Q: What are these? Are these mandatory? >>> >>> d) Also, a new vtkCellArray is being created. ('newPolys') >>> Q: Same question. No clue what I should do here. >>> >>> As usual, any clue of how to attack this is greatly appreciated. >>> >>> Bertwim >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Sun Oct 5 12:02:57 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sun, 05 Oct 2014 18:02:57 +0200 Subject: [Paraview] new Source plugin: no show! In-Reply-To: <54316321.2080000@lbl.gov> References: <5430129D.3020508@xs4all.nl> <5430B56C.2090208@lbl.gov> <5431610D.2030403@xs4all.nl> <54316321.2080000@lbl.gov> Message-ID: <54316BB1.8000404@xs4all.nl> Hi Burlen, Thanks for pointing me to the User guide. Very useful. Im rather new to Paraview/vtk, and I find it it hard to find precise information how to get started *as a developer*. There is plenty of material giving a more or less high level description, or it assumes that all kind of knowlegde is already there ...). I'm not complaining though, just need the time and the right references. Thanks for your help. Bertwim On 10/05/2014 05:26 PM, Burlen Loring wrote: > Hi Bertwim, > > I should have explained the cells better. The cells are descriptions > of how points are combined into geometric primitives that can be > rendered by OpenGL (or converted into those understood by OpenGL). > Here is an excerpt of > the User Guide describing VTK's cells, see p9-10. > > Burlen > > On 10/5/2014 8:17 AM, B.W.H. van Beest wrote: >> Hi Burlen, >> >> Thanks for your reply. On the cell-info: I now (finally) understood >> what was there to be. After implementing the cells, I indeed got the >> expected display. On the book: what keeps me from buying is that it >> seems outdated (because it refers to version 3). >> The texture coordinates I had found on Google indeed. What I needed >> was how to apply it in Paraview/VTK. I will look into that again >> Maybe it becomes clear now. >> >> Thanks >> Bertwim >> >> >> On 10/05/2014 05:05 AM, Burlen Loring wrote: >>> I assume in your request data you are generating a vtkPolyData >>> dataset. At the end of request data call "dataset->Print(cerr);" . >>> That's the one of the best debug method when you don't see what you >>> think you should in PV while developing a new filter/source/reader >>> what ever. The information tab in the GUI gives a subset of that, >>> also useful. >>> >>> texture coordinates are usually for applying an image to the >>> surface. google it and you'll find volumes of info. In pv they are >>> optional. >>> >>> the cell array I'm afraid is not. when generating poly or >>> unstructured data. If you have no cells what do you expect to see? >>> >>> normals are per point. >>> >>> some of your questions suggest that the book VTK user guide >>> would be a >>> good investment for you. >>> >>> Hope I didn't miss anything. ;-) >>> >>> On 10/4/2014 8:30 AM, B.W.H. van Beest wrote: >>>> Hello, >>>> >>>> I need to write a new Source, representing a 'TriPrism", >>>> i.e. a prism where the top and bottom planes are triangles. So far, I >>>> failed. >>>> >>>> Being unable to find appropriate documentation, I used the source code >>>> of vtkCubeSource as an example, thinking it would be an easy change. >>>> Wrong! The prism doesn't show on the screen. The >>>> properties panel behaves as expected (and ok, as far I can see). >>>> >>>> The member function 'RequestData' seems to be the important method. >>>> But the code of the example (as well as other source examples) is on >>>> closer inspection not clear to me at all. >>>> >>>> The following is happening in the vtkCubeSource: >>>> >>>> a) The point of the cube are generated. This is straightforward and >>>> easily >>>> translates to the triprism. >>>> The new points are updated via a call "output->setPoints( >>>> newPoints );" >>>> >>>> b) The normals (to the side planes of the cube) are being calculated. >>>> The new normals are updated via a call >>>> "output->GetPointData()->SetNormals(newNormals);" >>>> This is also straightforward for the triprism, but: >>>> >>>> Q: although calculating the normals is straightforward, >>>> in which order are they supposed to be given? >>>> >>>> c) Also, texture coordinates (TCoords) are calculated. >>>> Q: What are these? Are these mandatory? >>>> >>>> d) Also, a new vtkCellArray is being created. ('newPolys') >>>> Q: Same question. No clue what I should do here. >>>> >>>> As usual, any clue of how to attack this is greatly appreciated. >>>> >>>> Bertwim >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From furutaka.kazuyoshi at jaea.go.jp Sun Oct 5 22:26:09 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Mon, 06 Oct 2014 11:26:09 +0900 (JST) Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: References: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> Dear Utkarsh, Thanks for your mail. From: Utkarsh Ayachit Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? Date: Thu, 2 Oct 2014 16:00:33 -0400 > Yes, vtkCamera does often update its itself. Look at vtkCamera.cxx [1]. > > [1] https://github.com/Kitware/VTK/blob/83be7b1b77a6bfbf296ccaa5155cec57d0c77a8c/Rendering/Core/vtkCamera.cxx Then, how does the following happen? > On Thu, Oct 2, 2014 at 2:18 AM, Kazuyoshi Furutaka > wrote: >> From Python Shell, I got the following result: >> >> ...resetting... >> Python 2.7.5 (default, Sep 25 2014, 13:58:10) >> [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 >>>>> from paraview.simple import * >>>>> box=Box() >>>>> Show(box) >> >>>>> cam=GetActiveCamera() >>>>> cam.SetPosition(0,3,3) >>>>> Render() >> >>>>> cam.GetViewUp() >> (0.0, 1.0, 0.0) >>>>> My understanding from the "Figure 3-11 Camera attributes" of `The Visualization Toolkit (4th ed.)' is that the view-up vector always points upward to the camera and should always be normal to the direction of projection (and therefore parallel to the SCREEN). Is this correct? Do I misunderstand something? Thanks, Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From utkarsh.ayachit at kitware.com Mon Oct 6 10:46:10 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Oct 2014 10:46:10 -0400 Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> References: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> Message-ID: Kazuyoshi, I just noticed that you're getting a "SliceView". I am not entirely sure why. Is there something different with your configuration? Here's what I get: >>> from paraview.simple import * paraview version 4.2.0-4-g03d4c39 >>> Box() >>> Show() >>> Render() With SliceView, the camera is managed by the SliceVIew itself. To be able to freely play with the camera, you want the RenderView, which is indeed the default. Did you manually create the SliceView before running the script? Utkarsh On Sun, Oct 5, 2014 at 10:26 PM, Kazuyoshi Furutaka wrote: > Dear Utkarsh, > > Thanks for your mail. > > From: Utkarsh Ayachit > Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? > Date: Thu, 2 Oct 2014 16:00:33 -0400 > >> Yes, vtkCamera does often update its itself. Look at vtkCamera.cxx [1]. >> >> [1] https://github.com/Kitware/VTK/blob/83be7b1b77a6bfbf296ccaa5155cec57d0c77a8c/Rendering/Core/vtkCamera.cxx > > Then, how does the following happen? > > >> On Thu, Oct 2, 2014 at 2:18 AM, Kazuyoshi Furutaka >> wrote: >>> From Python Shell, I got the following result: >>> >>> ...resetting... >>> Python 2.7.5 (default, Sep 25 2014, 13:58:10) >>> [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 >>>>>> from paraview.simple import * >>>>>> box=Box() >>>>>> Show(box) >>> >>>>>> cam=GetActiveCamera() >>>>>> cam.SetPosition(0,3,3) >>>>>> Render() >>> >>>>>> cam.GetViewUp() >>> (0.0, 1.0, 0.0) >>>>>> > > My understanding from the "Figure 3-11 Camera attributes" > of `The Visualization Toolkit (4th ed.)' is that the view-up > vector always points upward to the camera and should always > be normal to the direction of projection (and therefore > parallel to the SCREEN). Is this correct? Do I misunderstand > something? > > > Thanks, > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From f.veronesi at scsitaly.com Mon Oct 6 11:31:10 2014 From: f.veronesi at scsitaly.com (Federico Veronesi) Date: Mon, 6 Oct 2014 17:31:10 +0200 Subject: [Paraview] Bug Report: Image Data are not pickable Message-ID: Hello, I am developing a tool based on Paraview and I found this incorrect functionality: Image Data (I tested with Wavelet Source) is not pickable when it is displayed with slice, volume or outline representation, even if the pickable checkbox is checked. In my test I opened a render view and visualized a polydata (box) and an image data (wavelet) source, if I click on the box it is selected, but if I click on the wavelet in slice, volume and outlie representation it is not. Even if it it less problematic, the same behaviour happens for Text source as it has been reported in this bug http://www.paraview.org/Bug/view.php?id=12177 Should I open a bug report on Matis? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisneal at ufl.edu Mon Oct 6 14:14:55 2014 From: chrisneal at ufl.edu (Neal,Christopher R) Date: Mon, 6 Oct 2014 18:14:55 +0000 Subject: [Paraview] Paraview-Python Looping over multiple state files Message-ID: <1412619294991.49495@ufl.edu> Hello, This is my first time using the Paraview listserv. I am working on a python script to automate the production of images(for purposes to making short videos from a data set). I am using Paraview version 4.1.0-64bit. My data is in an Ensight Gold format, which Paraview seems to read in just fine. Here is my thought process: 1.) Open a file that has a list of state file names and store the list of state files. (rflu_states.inp) 2.) Load my Ensight data using the Paraview EnsightReader() 3.) Load a state file. (http://www.paraview.org/Wiki/ParaView/Python_Scripting#Loading_State_and_Manipulating_It) 4.) Loop over all times in the data and export an image for each time step in the data from Step 2. 5.) Close the state file and delete any data that may cause a memory leak(Basically to reset paraview for the next state file to be read in) 6.) Return to Step 3. Issues that I am having: 1.) I can't seem to delete all of the data from each state file once I am done using it. (I see the memory usage keep creeping up when each state file loads) 2.) When I run the script I notice that Paraview keeps opening up new layout windows, but I never explicitly tell it to do that. Does anyone have any experience with using Paraview like this? I have been using the Paraview User's Manual, the Paraview Wiki, and the Paraview Trace feature to make my script. Here is an old post from someone with a similar issue as me, but I don't think their problem ever got resolved: http://public.kitware.com/pipermail/paraview/2012-November/026756.html Here is my script so far: #import os options import os import errno #Load Paraview Python libraries #from paraview.simple import * #Image Extension extension = '.png' #Max Image Number Indicator ImNum='000' # for padding image numbers with 0s #Filename where state files are to be read from fname = "rflu_states.inp" #Count the number of lines in the rflu_states.inp file(gives the number of states to load) num_lines = sum(1 for line in open(fname)) #Error Check: Print the number of lines that were read from file print("\nNumber of lines read from input file, %s , is: %d " %(fname,num_lines) ) #Store list of state files to be loaded with open(fname) as f: state_names = f.read().splitlines() #Strip newline characters from the end of each line state_names = [x.strip('\n') for x in state_names] #Error Check: Print stored state names to screen print("\nFollowing state files will be processed: " ) for x in range(0,num_lines): print("%s" %(state_names[x]) ) print("\n") #Loop over all state files in rflu_states.inp for bigLoop in range(0,num_lines): #Print state number and state name print( "Loading State %d: %s" %(bigLoop+1,state_names[bigLoop]) ) #Call Paraview Ensight Data Reader on case file in current directory reader = EnSightReader(CaseFileName='cylds.case.00001') #Get all timesteps that are in data file timesteps = reader.TimestepValues #Load the State servermanager.LoadState(state_names[bigLoop]) #Store directory name from state file name dirname = state_names[bigLoop] #Store loop state name start = dirname.find('_') + 1 #Find location of first _ end = dirname.find('.',start) #Find location of . after first _ dirname = dirname[start:end] #Take region between _ and . #Error Check: Display directory name that will be created print("Images for State, %s, are output to directory: %s" %(state_names[bigLoop],dirname)) #Check if output directory exists. Create one if it does not try: os.makedirs(dirname) except OSError: if os.path.isdir(dirname): # We are nearly safe pass else: # There was an error on creation, so make sure we know about it raise #Loop over all time steps and output images for TimeStepNum in range(0,len(timesteps)): #Determine padding zeros for image if TimeStepNum+1 > 999: zero_pad = '' elif TimeStepNum+1 > 99: zero_pad = ImNum[:1] elif TimeStepNum+1 > 9: zero_pad = ImNum[:2] else: zero_pad = ImNum #Store active view view = GetActiveView() view.ViewTime = timesteps[TimeStepNum] #Render current view Render() #Adjust image name be of the of the form _.extension(png, jpg, etc) ImageName = dirname + '_' + zero_pad + str(TimeStepNum+1) + extension print("Printing Image %d of %d " %(TimeStepNum+1,len(timesteps)) ) #Append directory path to image name to prepare for output outputDir = dirname + '/' +ImageName #Write image of current view to file WriteImage(outputDir) #Delete all sources(To clean up memory) for f in GetSources().values(): Delete(f) #Delete the reader data(To clean up memory) Delete(reader) del(reader) Thank you, Christopher R. Neal Graduate Student Center for Compressible Multiphase Turbulence Mechanical and Aerospace Engineering Department University of Florida Cell: (863)-697-1958 E-mail: chrisneal at ufl.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Mon Oct 6 16:27:20 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Oct 2014 16:27:20 -0400 Subject: [Paraview] Bug Report: Image Data are not pickable In-Reply-To: References: Message-ID: Yes, that is a known issue, but don't think we have a bug tracker item for it. Please feel free to add one. Thanks, Utkarsh On Mon, Oct 6, 2014 at 11:31 AM, Federico Veronesi wrote: > Hello, > > I am developing a tool based on Paraview and I found this incorrect > functionality: > > Image Data (I tested with Wavelet Source) is not pickable when it is > displayed with slice, volume or outline representation, even if the pickable > checkbox is checked. > In my test I opened a render view and visualized a polydata (box) and an > image data (wavelet) source, if I click on the box it is selected, but if I > click on the wavelet in slice, volume and outlie representation it is not. > > Even if it it less problematic, the same behaviour happens for Text source > as it has been reported in this bug > http://www.paraview.org/Bug/view.php?id=12177 > > Should I open a bug report on Matis? > > Thanks > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Mon Oct 6 16:31:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Oct 2014 16:31:02 -0400 Subject: [Paraview] calculator tensor field In-Reply-To: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> References: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> Message-ID: Can you attach a sample data file/state file? That'll make it easier to identify the problem and suggest a solution. Thanks Utkarsh On Sat, Oct 4, 2014 at 4:14 AM, wrote: > Hello everyone, > > I have three displacement field vector components u, v, w in my .vtk file > and wish to display the associated stress tensor. > I made the following steps: > > - Apply the filter Gradient Of Unstructued DataSet > -> Now have 9 scalars Gradient_0, ... , Gradient 8 > > - compute components of stress tensor via sigma_ij = div(Gradient) + u_i,j > -> Now have additional 9 scalars sigma_ij > > - from this form traction vectors: > T_i = sigma_ij e_j ,where e_j are the unit vectors iHat > > -> Now have three traction vectors from which the tensor field computation > doesnt work: > > - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor calculation > and get the following error message: > > ERROR: In > /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, > line 201 > vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous > operators > > > ERROR: In > /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, > line 300 > vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar and a > vector > > > ERROR: In > /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, > line 201 > vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous > operators > > > - Can you help me or tell me gow to visualize the stress tensor from the > displacement field? > - Alternatively you it would also be good to know how to multiply the result > of filter Gradient of Unstructured DataSet by a scalar value. > > > Many thanks for helping! > Gianna > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From furutaka.kazuyoshi at jaea.go.jp Mon Oct 6 19:57:30 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Tue, 07 Oct 2014 08:57:30 +0900 (JST) Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: <20141002.151802.248776726.furutaka.kazuyoshi@jaea.go.jp> References: <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20141007.085730.238515892.furutaka.kazuyoshi@jaea.go.jp> Dear Utkarsh, Thanks for the response. From: Utkarsh Ayachit Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? Date: Mon, 6 Oct 2014 10:46:10 -0400 > I just noticed that you're getting a "SliceView". I am not entirely > sure why. Is there something different with your configuration? Here's > what I get: > >>>> from paraview.simple import * > paraview version 4.2.0-4-g03d4c39 >>>> Box() > >>>> Show() > >>>> Render() > > > With SliceView, the camera is managed by the SliceVIew itself. To be > able to freely play with the camera, you want the RenderView, which is > indeed the default. > Did you manually create the SliceView before running the script? Yes, for a reason, I set SliceView as my default view. Therefore, though I'm not sure, as I remember, what I did were... 1. "Edit -> Reset Session", 2. Close "SliceView1" view, 3. Create View "Render View", 4. Open "Tools -> Python Shell", then 5. Create a Box(), then Show() and Render(), change the camera position, and see what the view-up is... This time I did the same procedure again (to see if the above really happens in the Render view) and get almost the same result. 1. Run ParaView 4.2.0 32-bit on linux (fedora-20), 2. Close "SliceView1" view, 3. Create View "Render View", 4. Open "Tools -> Python Shell", 5. type and get the following: Python 2.7.5 (default, Sep 25 2014, 13:58:10) [GCC 4.8.3 20140911 (Red Hat 4.8.3-7)] on linux2 >>> from paraview.simple import * paraview version 4.2.0 >>> Box() >>> Show() >>> Render() >>> cam=GetActiveCamera() >>> cam.GetViewUp() (0.0, 1.0, 0.0) >>> cam.SetPosition(0,3,3) >>> Render() >>> cam.GetViewUp() (0.0, 1.0, 0.0) >>> So, it seems the view-up is not updated... I just want to write a Python macro to change/rotate the camera position using Azimuth() and Elevation(). In addition to the following: > I'm observing a curious behavior of paraview.simple.Azimuth(); > camera is NOT moving left/right. I sometimes get the following message Warning: In /home/furutaka/work/ParaView/ParaView.git/VTK/Rendering/Core/vtkRenderer.cxx, line 1030 vtkOpenGLRenderer (0xa702510): Resetting view-up since view plane normal is parallel and am wondering how can the view-up be parallel to the view-plane normal... My understanding is that the view-up is (always) perpendicular to the direction of projection (pointing upward of the computer display) and therefore parallel to the view-plane, so the view-up should always be normal to view-plane normal. Isn't the view-plane normal parallel to the direction of projection? Isn't the view-plane parallel to the front/back clipping planes? Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From furutaka.kazuyoshi at jaea.go.jp Mon Oct 6 20:25:39 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Tue, 07 Oct 2014 09:25:39 +0900 (JST) Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: <20141007.085730.238515892.furutaka.kazuyoshi@jaea.go.jp> References: <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> <20141007.085730.238515892.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20141007.092539.149711884.furutaka.kazuyoshi@jaea.go.jp> Could someone tell me whether the meanings of the azimuth and the elevation in ParaView the same as those in VTK (or "The Visualization Toolkit" book, 4th ed.) or not? In the book it reads: "Changing the \textit{azimuth} of a camera rotates its position around its view up vector, centered at the focal point. Think of this as moving the cmaera to the left or right while always keeping the distance to the focal point constant. Changing a camera's \textit{elevation} rotates its position around the cross product of its direction of projection and view up centered at the focal point. This corresponds to moving the camera up and down. To \textit{roll} the camera, we rotate the view up vector about the view plane normal. Roll is sometimes called twist." I sometimes observe that (in the Multi Slice view,) Azimuth() "rolls" instead of moving the camera left/right. That's why I want to understand the geometry of view-up, direction of projection, and so on... Kazuyoshi From: Kazuyoshi Furutaka Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? Date: Tue, 07 Oct 2014 08:57:30 +0900 (JST) > I just want to write a Python macro to change/rotate the camera > position using Azimuth() and Elevation(). > > In addition to the following: > >> I'm observing a curious behavior of paraview.simple.Azimuth(); >> camera is NOT moving left/right. > > I sometimes get the following message > > Warning: In /home/furutaka/work/ParaView/ParaView.git/VTK/Rendering/Core/vtkRenderer.cxx, line 1030 > vtkOpenGLRenderer (0xa702510): Resetting view-up since view plane normal is parallel > > and am wondering how can the view-up be parallel to the view-plane > normal... > > My understanding is that the view-up is (always) perpendicular to > the direction of projection (pointing upward of the computer display) > and therefore parallel to the view-plane, so the view-up should always > be normal to view-plane normal. > Isn't the view-plane normal parallel to the direction of projection? > Isn't the view-plane parallel to the front/back clipping planes? -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From utkarsh.ayachit at kitware.com Mon Oct 6 20:49:35 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 6 Oct 2014 20:49:35 -0400 Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: <20141007.092539.149711884.furutaka.kazuyoshi@jaea.go.jp> References: <20141006.112609.53816885.furutaka.kazuyoshi@jaea.go.jp> <20141007.085730.238515892.furutaka.kazuyoshi@jaea.go.jp> <20141007.092539.149711884.furutaka.kazuyoshi@jaea.go.jp> Message-ID: The meaning of azimuth, elevation etc. is indeed same with VTK and ParaVIew. ParaView uses the same code for Camera as in VTK, so there's no different there. Here's some explanation on the inner workings of the camera: + The camera->ViewUp is used by vtkCamera as a "hint" for the up direction. Thus, it is need not always be orthogonal to the view direction (defined by camera position and camera focal point). Unless the ViewUp is parallel to the view -direction, the vtkCamera will automatically compute the true "viewup" internally using vtkCamera::ViewUp as a hint. + You can use cam.OrthogonalizeViewUp() to force the vtkCamera to update the VIewUp based on the internally used ViewUp. e.g. >>> cam = GetActiveCamera() >>> cam.SetPosition(0, 3, 3) >>> Render() >>> cam.GetViewUp() (0.0, 1.0, 0.0) >>> cam.OrthogonalizeViewUp() >>> cam.GetViewUp() (0.0, 0.7071067811865476, -0.7071067811865476) I am not sure I observe the same problem as you mention with Azimuth/Roll. Utkarsh On Mon, Oct 6, 2014 at 8:25 PM, Kazuyoshi Furutaka wrote: > Could someone tell me whether the meanings of the azimuth and > the elevation in ParaView the same as those in VTK (or "The > Visualization Toolkit" book, 4th ed.) or not? > > In the book it reads: > "Changing the \textit{azimuth} of a camera rotates its position > around its view up vector, centered at the focal point. Think > of this as moving the cmaera to the left or right while always > keeping the distance to the focal point constant. Changing a > camera's \textit{elevation} rotates its position around the cross > product of its direction of projection and view up centered at the > focal point. This corresponds to moving the camera up and down. > To \textit{roll} the camera, we rotate the view up vector about > the view plane normal. Roll is sometimes called twist." > > I sometimes observe that (in the Multi Slice view,) Azimuth() > "rolls" instead of moving the camera left/right. > > That's why I want to understand the geometry of view-up, direction > of projection, and so on... > > Kazuyoshi > > > From: Kazuyoshi Furutaka > Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? > Date: Tue, 07 Oct 2014 08:57:30 +0900 (JST) > >> I just want to write a Python macro to change/rotate the camera >> position using Azimuth() and Elevation(). >> >> In addition to the following: >> >>> I'm observing a curious behavior of paraview.simple.Azimuth(); >>> camera is NOT moving left/right. >> >> I sometimes get the following message >> >> Warning: In /home/furutaka/work/ParaView/ParaView.git/VTK/Rendering/Core/vtkRenderer.cxx, line 1030 >> vtkOpenGLRenderer (0xa702510): Resetting view-up since view plane normal is parallel >> >> and am wondering how can the view-up be parallel to the view-plane >> normal... >> >> My understanding is that the view-up is (always) perpendicular to >> the direction of projection (pointing upward of the computer display) >> and therefore parallel to the view-plane, so the view-up should always >> be normal to view-plane normal. >> Isn't the view-plane normal parallel to the direction of projection? >> Isn't the view-plane parallel to the front/back clipping planes? > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From furutaka.kazuyoshi at jaea.go.jp Mon Oct 6 21:29:16 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Tue, 07 Oct 2014 10:29:16 +0900 (JST) Subject: [Paraview] Is the VIEW-UP vector updated automatically? In-Reply-To: References: <20141007.085730.238515892.furutaka.kazuyoshi@jaea.go.jp> <20141007.092539.149711884.furutaka.kazuyoshi@jaea.go.jp> Message-ID: <20141007.102916.331281688.furutaka.kazuyoshi@jaea.go.jp> Dear Utkarsh, Thanks for the great hint! By forcing the update of view-up using cam.OrthogonalizeViewUp() on initialization as well as on changing azimuthal angle etc., I can successfully change azimuth angle instead of rolling. Thanks again. Kazuyoshi From: Utkarsh Ayachit Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? Date: Mon, 6 Oct 2014 20:49:35 -0400 > The meaning of azimuth, elevation etc. is indeed same with VTK and > ParaVIew. ParaView uses the same code for Camera as in VTK, so there's > no different there. Here's some explanation on the inner workings of > the camera: > > + The camera->ViewUp is used by vtkCamera as a "hint" for the up > direction. Thus, it is need not always be orthogonal to the view > direction (defined by camera position and camera focal point). Unless > the ViewUp is parallel to the view -direction, the vtkCamera will > automatically compute the true "viewup" internally using > vtkCamera::ViewUp as a hint. > + You can use cam.OrthogonalizeViewUp() to force the vtkCamera to > update the VIewUp based on the internally used ViewUp. > > e.g. > >>>> cam = GetActiveCamera() >>>> cam.SetPosition(0, 3, 3) >>>> Render() >>>> cam.GetViewUp() > (0.0, 1.0, 0.0) >>>> cam.OrthogonalizeViewUp() >>>> cam.GetViewUp() > (0.0, 0.7071067811865476, -0.7071067811865476) > > I am not sure I observe the same problem as you mention with Azimuth/Roll. > > Utkarsh > > On Mon, Oct 6, 2014 at 8:25 PM, Kazuyoshi Furutaka > wrote: >> Could someone tell me whether the meanings of the azimuth and >> the elevation in ParaView the same as those in VTK (or "The >> Visualization Toolkit" book, 4th ed.) or not? >> >> In the book it reads: >> "Changing the \textit{azimuth} of a camera rotates its position >> around its view up vector, centered at the focal point. Think >> of this as moving the cmaera to the left or right while always >> keeping the distance to the focal point constant. Changing a >> camera's \textit{elevation} rotates its position around the cross >> product of its direction of projection and view up centered at the >> focal point. This corresponds to moving the camera up and down. >> To \textit{roll} the camera, we rotate the view up vector about >> the view plane normal. Roll is sometimes called twist." >> >> I sometimes observe that (in the Multi Slice view,) Azimuth() >> "rolls" instead of moving the camera left/right. >> >> That's why I want to understand the geometry of view-up, direction >> of projection, and so on... >> >> Kazuyoshi >> >> >> From: Kazuyoshi Furutaka >> Subject: Re: [Paraview] Is the VIEW-UP vector updated automatically? >> Date: Tue, 07 Oct 2014 08:57:30 +0900 (JST) >> >>> I just want to write a Python macro to change/rotate the camera >>> position using Azimuth() and Elevation(). >>> >>> In addition to the following: >>> >>>> I'm observing a curious behavior of paraview.simple.Azimuth(); >>>> camera is NOT moving left/right. >>> >>> I sometimes get the following message >>> >>> Warning: In /home/furutaka/work/ParaView/ParaView.git/VTK/Rendering/Core/vtkRenderer.cxx, line 1030 >>> vtkOpenGLRenderer (0xa702510): Resetting view-up since view plane normal is parallel >>> >>> and am wondering how can the view-up be parallel to the view-plane >>> normal... >>> >>> My understanding is that the view-up is (always) perpendicular to >>> the direction of projection (pointing upward of the computer display) >>> and therefore parallel to the view-plane, so the view-up should always >>> be normal to view-plane normal. >>> Isn't the view-plane normal parallel to the direction of projection? >>> Isn't the view-plane parallel to the front/back clipping planes? >> -- >> Kazuyoshi Furutaka >> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From cjm2176 at columbia.edu Mon Oct 6 23:31:44 2014 From: cjm2176 at columbia.edu (Colin McAuliffe) Date: Mon, 6 Oct 2014 23:31:44 -0400 Subject: [Paraview] Exporting a selection Message-ID: Dear all, I would like to be able to look at a particular part of my output and plot the maximum value of some fields over time. This needs to be done in a script since the process needs to be applied to several different runs. I tried to use the trace to get the list of point IDs in the region of interest, but the result of doing select point on followed by extract selection is this # create a new 'Extract Selection' extractSelection1 = ExtractSelection(Input=pK10HOJ_0001000, Selection=None) so it is not giving me the ID's. To get the plot maximum over time I am using find data to select all points and then using plot selection over time. However, again the trace does not tell me what the selection should be # create a new 'Plot Selection Over Time' plotSelectionOverTime1 = PlotSelectionOverTime(Input=pK10HOJ_0001000, Selection=None) plotSelectionOverTime1.OnlyReportSelectionStatistics = 0 Is there any way to get this info? Or perhaps an alternate way to go about plotting max over time in a specified region? Thanks and all the best, Colin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Eliot at awe.co.uk Tue Oct 7 09:25:10 2014 From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk) Date: Tue, 7 Oct 2014 13:25:10 +0000 Subject: [Paraview] Problem building plugin against ParaView 4.2.0 Message-ID: <201410071325.s97DPBsq004082@msw1.awe.co.uk> Hello everyone, I am trying to build a file reader plugin against ParaView 4.2.0 and have been experiencing some difficulties. Qt is not found by cmake during the build process causing it to fail. To illustrate the issue, I created the following simplified CMakeLists.txt file: CMAKE_MINIMUM_REQUIRED FIND_PACKAGE(ParaView REQUIRED) INCLUDE(${PARAVIEW_USE_FILE}) When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is found, but with 4.2.0 Qt is NOT found. ParaView was built using Superbuild and Qt was built as part of that process. Should Qt be detected from ParaViewConfig.cmake? Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow need to specify the location of Qt manually? Any ideas? Thank you, Jim Jim Eliot High Performance Computing Group AWE, Aldermaston, Reading, RG7 4PR ___________________________________________________ ____________________________ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Oct 7 10:03:04 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Oct 2014 10:03:04 -0400 Subject: [Paraview] calculator tensor field In-Reply-To: <20141007003139.pp0jn9l7kgw4040s@wwwmail.urz.uni-heidelberg.de> References: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> <20141007003139.pp0jn9l7kgw4040s@wwwmail.urz.uni-heidelberg.de> Message-ID: Gianna, For Calculator filter, names with "_X", "_Y" have special meaning. Try change Calulators 1-9 to use Result Array names as "sigmaXX", "sigmaYY", etc. Does that work? Utkarsh On Mon, Oct 6, 2014 at 6:31 PM, wrote: > Hello Utkarsh, > thanks for looking at it. > Attached is the state file: > - Calculators 1-6 calculate the 6 independent components of the symmetric > stress tensor sigma_ij > > - Calculators 7-9 calculate the traction vectors s_i from the stress > components (s_i = sigma_ij e_j , summation over j implied, e_j basis > vectors) > > Now in another calculator I'd like to compute the stress tensor field, > either directly from the stress components sigma_ij or from the traction > vectors. Both approaches fail with the error message. > The stress tensor is given by > sigma = > sigma_xx(e_x*e_x)+sigma_yy(e_y*e_y)+sigma_zz(e_z*_ez)+sigma_xy)(e_xe_y+e_ye_x)+sigma_xz(e_xe_z+e_ze_x)+sigma_yz(e_ye_z+e_ze_y) > equivalent to > sigma = s_x*e_x + s_y*e_y +s_z*e_z > > Thanks, > Gianna > > > > Quoting Utkarsh Ayachit : > >> Can you attach a sample data file/state file? That'll make it easier >> to identify the problem and suggest a solution. >> >> Thanks >> Utkarsh >> >> On Sat, Oct 4, 2014 at 4:14 AM, >> wrote: >>> >>> Hello everyone, >>> >>> I have three displacement field vector components u, v, w in my .vtk file >>> and wish to display the associated stress tensor. >>> I made the following steps: >>> >>> - Apply the filter Gradient Of Unstructued DataSet >>> -> Now have 9 scalars Gradient_0, ... , Gradient 8 >>> >>> - compute components of stress tensor via sigma_ij = div(Gradient) + >>> u_i,j >>> -> Now have additional 9 scalars sigma_ij >>> >>> - from this form traction vectors: >>> T_i = sigma_ij e_j ,where e_j are the unit vectors iHat >>> >>> -> Now have three traction vectors from which the tensor field >>> computation >>> doesnt work: >>> >>> - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor calculation >>> and get the following error message: >>> >>> ERROR: In >>> >>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>> line 201 >>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>> operators >>> >>> >>> ERROR: In >>> >>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>> line 300 >>> vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar >>> and a >>> vector >>> >>> >>> ERROR: In >>> >>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>> line 201 >>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>> operators >>> >>> >>> - Can you help me or tell me gow to visualize the stress tensor from the >>> displacement field? >>> - Alternatively you it would also be good to know how to multiply the >>> result >>> of filter Gradient of Unstructured DataSet by a scalar value. >>> >>> >>> Many thanks for helping! >>> Gianna >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > > From maja.vrzdovnik at helmholtz-muenchen.de Tue Oct 7 10:22:27 2014 From: maja.vrzdovnik at helmholtz-muenchen.de (Maja) Date: Tue, 7 Oct 2014 14:22:27 +0000 (UTC) Subject: [Paraview] Recommendations for display of 4D color dataset References: Message-ID: Utkarsh Ayachit kitware.com> writes: > > ParaView associates color maps with array-names, so all arrays with > the same name use the same color map. An easiest way around this is to > apply the "Calculator" filter to each of the mha file readers set the > expression to the name of the input array while change the "Result > Array Name" for every instance of the calculator to be something > unique. Now you can color the results produced by each of the > calculators differently using different colormaps. > > Utkarsh Hi, I have scientific data from a microscope with 2 channels. I have to merge these two channels, but unfortunately there is only one color map. So both channels ( Reprensentation: "Volume") are expressed in one color. I need two color maps,so that the channels have different colors . My ParaView Version is 4.2.0. Is anyone able to help me with detailed steps? Thanks From dave.demarle at kitware.com Tue Oct 7 11:09:57 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Tue, 7 Oct 2014 11:09:57 -0400 Subject: [Paraview] announce: VTK and ParaView scripting training October 21 at Kitware's North Carolina office In-Reply-To: References: Message-ID: Just a quick reminder, tomorrow is the last day for early registration for the next VTK and ParaView scripting course held in the US. Hope to see you in Carrboro, David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 22, 2014 at 11:48 AM, David E DeMarle wrote: > Kitware is hosting a VTK-ParaView training course in Carrboro, NC. The > course will be held on October 21, 2014. Attendees will gain practical > experience in both ParaView, a scalable application for general purpose > scientific visualization, and The Visualization Toolkit (VTK), the > underlying open-source library from which ParaView is built. > > The training mixes theory and application to guide attendees through a set > of exercises, which are all given in the python programming language. Upon > completion of this course, attendees will not only know how to use ParaView > and VTK, but they will also know how to extend ParaView at run time, use it > in concert with other Python capable applications, and run it in batch > processing HPC contexts. Additional details and registration information > are available on the Kitware website > . > > The price of the course via early registration is $650. Early registration > is available through October 8, 2014. The price of the course via regular > registration is $815. > > In addition, Kitware will be hosting a ?Project Lifecycle Management with > the CMake Family of Tools? training course on October 20, 2014. This course > will also be hosted in Carrboro. For more information, please visit > http://www.kitware.com/products/protraining.php. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 7 12:55:40 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 07 Oct 2014 18:55:40 +0200 Subject: [Paraview] Problem building plugin against ParaView 4.2.0 In-Reply-To: <201410071325.s97DPBsq004082@msw1.awe.co.uk> References: <201410071325.s97DPBsq004082@msw1.awe.co.uk> Message-ID: <54341B0C.9070902@xs4all.nl> Jim, I had similar issues you describe. They were gone when I made sure that, before actually calling cmake, the right 'qmake' was in the PATH (i.e. 'which qmake' points to the qmake of the AQT-version your expect). This assumes that you do have a Qt installation which is complete. In other words: 1. ensure qmake of the Qt distribution you expect is in your path 2. ensure your paraview build directory is clean ( rm -rf /build/* ) 3. start the cmake configuration. Hope this works for you too, Regards, Bertwim On 10/07/2014 03:25 PM, Jim.Eliot at awe.co.uk wrote: > > > > Hello everyone, > > > > I am trying to build a file reader plugin against ParaView 4.2.0 and > have been experiencing some difficulties. Qt is not found by cmake > during the build process causing it to fail. > > > > To illustrate the issue, I created the following simplified > CMakeLists.txt file: > > > > CMAKE_MINIMUM_REQUIRED > > FIND_PACKAGE(ParaView REQUIRED) > > INCLUDE(${PARAVIEW_USE_FILE}) > > > > When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is > found, but with 4.2.0 Qt is NOT found. > > > > ParaView was built using Superbuild and Qt was built as part of that > process. Should Qt be detected from ParaViewConfig.cmake? > > > > Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow > need to specify the location of Qt manually? > > > > Any ideas? > > > > Thank you, > > Jim > > > > *Jim Eliot* > *High Performance Computing Group* > AWE, Aldermaston, Reading, RG7 4PR > > > > ___________________________________________________ > ____________________________ The information in this email and in any > attachment(s) is commercial in confidence. If you are not the named > addressee(s) or if you receive this email in error then any > distribution, copying or use of this communication or the information > in it is strictly prohibited. Please notify us immediately by email at > admin.internet(at)awe.co.uk, and then delete this message from your > computer. While attachments are virus checked, AWE plc does not accept > any liability in respect of any virus which is not detected. AWE Plc > Registered in England and Wales Registration No 02763902 AWE, > Aldermaston, Reading, RG7 4PR > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Tue Oct 7 13:22:51 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Tue, 7 Oct 2014 17:22:51 +0000 Subject: [Paraview] ParaView plugin load error Message-ID: <7F781841FF1E044388AFA42B70703A7A89FB5CB6@CHIMBX6.ad.uillinois.edu> Hi, I'm working on a legacy ParaView 3.14.1 plugin project. On Windows, I can't seem to figure out the settings so that the plugin .dlls will work on any machine other than the dev machine. The errors I get are along the lines of: *************************************************** Attempting to load C:\Program Files\ParaView 3.14.1\bin\plugins\RVA_Core_Plugin.dll ERROR: In ..\..\..\..\src\ParaViewCore\ClientServerCore\vtkPVPluginLoader.cxx, line 296 vtkPVPluginLoader (000000000B21CBC0): The specified procedure could not be found. I take this to mean that some other library can't be found. I'm not doing a Superbuild, because I don't want to redistribute an entire ParaView, just the the plugin. Should I be using the Superbuild anyway? Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From Marschmann at stud.uni-heidelberg.de Tue Oct 7 14:51:38 2014 From: Marschmann at stud.uni-heidelberg.de (Marschmann at stud.uni-heidelberg.de) Date: Tue, 07 Oct 2014 20:51:38 +0200 Subject: [Paraview] calculator tensor field In-Reply-To: References: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> <20141007003139.pp0jn9l7kgw4040s@wwwmail.urz.uni-heidelberg.de> Message-ID: <20141007205138.f1papyan4kookoko@wwwmail.urz.uni-heidelberg.de> Dear Utkarsh, I changed the Result Array names to sigmaXX etc but still get the same error message. I think the problem is with the product between the two unit vectors. Simply calculating for example " iHat*iHat " yields the same error message. Would you know in general how to form a tensor field in paraview from its components? Thanks, Gianna Quoting Utkarsh Ayachit : > Gianna, > > For Calculator filter, names with "_X", "_Y" have special meaning. > Try change Calulators 1-9 to use Result Array names as "sigmaXX", > "sigmaYY", etc. > Does that work? > > Utkarsh > > On Mon, Oct 6, 2014 at 6:31 PM, wrote: >> Hello Utkarsh, >> thanks for looking at it. >> Attached is the state file: >> - Calculators 1-6 calculate the 6 independent components of the symmetric >> stress tensor sigma_ij >> >> - Calculators 7-9 calculate the traction vectors s_i from the stress >> components (s_i = sigma_ij e_j , summation over j implied, e_j basis >> vectors) >> >> Now in another calculator I'd like to compute the stress tensor field, >> either directly from the stress components sigma_ij or from the traction >> vectors. Both approaches fail with the error message. >> The stress tensor is given by >> sigma = >> sigma_xx(e_x*e_x)+sigma_yy(e_y*e_y)+sigma_zz(e_z*_ez)+sigma_xy)(e_xe_y+e_ye_x)+sigma_xz(e_xe_z+e_ze_x)+sigma_yz(e_ye_z+e_ze_y) >> equivalent to >> sigma = s_x*e_x + s_y*e_y +s_z*e_z >> >> Thanks, >> Gianna >> >> >> >> Quoting Utkarsh Ayachit : >> >>> Can you attach a sample data file/state file? That'll make it easier >>> to identify the problem and suggest a solution. >>> >>> Thanks >>> Utkarsh >>> >>> On Sat, Oct 4, 2014 at 4:14 AM, >>> wrote: >>>> >>>> Hello everyone, >>>> >>>> I have three displacement field vector components u, v, w in my .vtk file >>>> and wish to display the associated stress tensor. >>>> I made the following steps: >>>> >>>> - Apply the filter Gradient Of Unstructued DataSet >>>> -> Now have 9 scalars Gradient_0, ... , Gradient 8 >>>> >>>> - compute components of stress tensor via sigma_ij = div(Gradient) + >>>> u_i,j >>>> -> Now have additional 9 scalars sigma_ij >>>> >>>> - from this form traction vectors: >>>> T_i = sigma_ij e_j ,where e_j are the unit vectors iHat >>>> >>>> -> Now have three traction vectors from which the tensor field >>>> computation >>>> doesnt work: >>>> >>>> - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor calculation >>>> and get the following error message: >>>> >>>> ERROR: In >>>> >>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>> line 201 >>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>> operators >>>> >>>> >>>> ERROR: In >>>> >>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>> line 300 >>>> vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar >>>> and a >>>> vector >>>> >>>> >>>> ERROR: In >>>> >>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>> line 201 >>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>> operators >>>> >>>> >>>> - Can you help me or tell me gow to visualize the stress tensor from the >>>> displacement field? >>>> - Alternatively you it would also be good to know how to multiply the >>>> result >>>> of filter Gradient of Unstructured DataSet by a scalar value. >>>> >>>> >>>> Many thanks for helping! >>>> Gianna >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >> >> > > From andy.bauer at kitware.com Tue Oct 7 15:02:50 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Tue, 7 Oct 2014 15:02:50 -0400 Subject: [Paraview] calculator tensor field In-Reply-To: <20141007205138.f1papyan4kookoko@wwwmail.urz.uni-heidelberg.de> References: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> <20141007003139.pp0jn9l7kgw4040s@wwwmail.urz.uni-heidelberg.de> <20141007205138.f1papyan4kookoko@wwwmail.urz.uni-heidelberg.de> Message-ID: This may be easier to do in the Python Calculator, which is more efficient anyway. For accessing a specific component of a vector you can do something like "Normals[:,0]". For a 2nd order tensor you'd do something like "StrainRate[:,0,1]". On Tue, Oct 7, 2014 at 2:51 PM, wrote: > Dear Utkarsh, > > I changed the Result Array names to sigmaXX etc but still get the same > error message. > I think the problem is with the product between the two unit vectors. > Simply calculating for example " iHat*iHat " yields the same error message. > > Would you know in general how to form a tensor field in paraview from its > components? > > Thanks, > Gianna > > > > > > > > > > Quoting Utkarsh Ayachit : > > Gianna, >> >> For Calculator filter, names with "_X", "_Y" have special meaning. >> Try change Calulators 1-9 to use Result Array names as "sigmaXX", >> "sigmaYY", etc. >> Does that work? >> >> Utkarsh >> >> On Mon, Oct 6, 2014 at 6:31 PM, >> wrote: >> >>> Hello Utkarsh, >>> thanks for looking at it. >>> Attached is the state file: >>> - Calculators 1-6 calculate the 6 independent components of the symmetric >>> stress tensor sigma_ij >>> >>> - Calculators 7-9 calculate the traction vectors s_i from the stress >>> components (s_i = sigma_ij e_j , summation over j implied, e_j basis >>> vectors) >>> >>> Now in another calculator I'd like to compute the stress tensor field, >>> either directly from the stress components sigma_ij or from the traction >>> vectors. Both approaches fail with the error message. >>> The stress tensor is given by >>> sigma = >>> sigma_xx(e_x*e_x)+sigma_yy(e_y*e_y)+sigma_zz(e_z*_ez)+ >>> sigma_xy)(e_xe_y+e_ye_x)+sigma_xz(e_xe_z+e_ze_x)+sigma_yz(e_ye_z+e_ze_y) >>> equivalent to >>> sigma = s_x*e_x + s_y*e_y +s_z*e_z >>> >>> Thanks, >>> Gianna >>> >>> >>> >>> Quoting Utkarsh Ayachit : >>> >>> Can you attach a sample data file/state file? That'll make it easier >>>> to identify the problem and suggest a solution. >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> On Sat, Oct 4, 2014 at 4:14 AM, >>>> wrote: >>>> >>>>> >>>>> Hello everyone, >>>>> >>>>> I have three displacement field vector components u, v, w in my .vtk >>>>> file >>>>> and wish to display the associated stress tensor. >>>>> I made the following steps: >>>>> >>>>> - Apply the filter Gradient Of Unstructued DataSet >>>>> -> Now have 9 scalars Gradient_0, ... , Gradient 8 >>>>> >>>>> - compute components of stress tensor via sigma_ij = div(Gradient) + >>>>> u_i,j >>>>> -> Now have additional 9 scalars sigma_ij >>>>> >>>>> - from this form traction vectors: >>>>> T_i = sigma_ij e_j ,where e_j are the unit vectors iHat >>>>> >>>>> -> Now have three traction vectors from which the tensor field >>>>> computation >>>>> doesnt work: >>>>> >>>>> - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor >>>>> calculation >>>>> and get the following error message: >>>>> >>>>> ERROR: In >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/ >>>>> Common/Misc/vtkFunctionParser.cxx, >>>>> line 201 >>>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>>> operators >>>>> >>>>> >>>>> ERROR: In >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/ >>>>> Common/Misc/vtkFunctionParser.cxx, >>>>> line 300 >>>>> vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar >>>>> and a >>>>> vector >>>>> >>>>> >>>>> ERROR: In >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/ >>>>> Common/Misc/vtkFunctionParser.cxx, >>>>> line 201 >>>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>>> operators >>>>> >>>>> >>>>> - Can you help me or tell me gow to visualize the stress tensor from >>>>> the >>>>> displacement field? >>>>> - Alternatively you it would also be good to know how to multiply the >>>>> result >>>>> of filter Gradient of Unstructured DataSet by a scalar value. >>>>> >>>>> >>>>> Many thanks for helping! >>>>> Gianna >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> >>>> >>> >>> >> >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 7 16:30:42 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 07 Oct 2014 22:30:42 +0200 Subject: [Paraview] Bug in Paraview 4.2 example + fix Message-ID: <54344D72.8080407@xs4all.nl> Hello, I think there is a bug in the plugin example in ../ParaView/Examples/Plugin/Representation (Paraview 4.2) As given, loading the plugin manually, and then creating a new source (e.g. Box) causes Paraview to crash with the error message: > ERROR: In > /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 565 > vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: > group=representations and proxy=SurfaceRepresentationBase were found. > > > ERROR: In > /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, > line 989 > vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy > definition (representations, SurfaceRepresentationBase). Aborting for > debugging purposes. > > > Abort The error seems to be in the file Representation.xml, where the attribute base_proxyname is set to "SurfaceRepresentationBase", which should be "SurfaceRepresentation" according to the documentation in http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 When I make the change, recompile the plugin and load in into Paraview, there is no longer the above crash when I create a new Box, and the representation "Special Mapper" feautures in the Representationnn combobox. > [243] Representation> diff Representation.xml.org Representation.xml > 7c7 > < base_proxyname="SurfaceRepresentationBase"> > --- > > base_proxyname="SurfaceRepresentation"> Kind Regards, Bertwim From cory.quammen at kitware.com Tue Oct 7 17:02:26 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 7 Oct 2014 17:02:26 -0400 Subject: [Paraview] calculator tensor field In-Reply-To: <20141007205138.f1papyan4kookoko@wwwmail.urz.uni-heidelberg.de> References: <20141004101450.qdbds4v1688sswcs@wwwmail.urz.uni-heidelberg.de> <20141007003139.pp0jn9l7kgw4040s@wwwmail.urz.uni-heidelberg.de> <20141007205138.f1papyan4kookoko@wwwmail.urz.uni-heidelberg.de> Message-ID: Gianna, If I understand correctly, you are trying to multiply a row vector [a, b, c] by a column vector [d, e, f]^T (where ^T indicates transpose) to get a matrix. Actually, you are doing this three times and then summing the resulting matrices to get a tensor matrix. Is that correct? If that its the case, I do not believe it is possible to produce a matrix output. Like Andy, I suggest using the Python Calculator. Documentation is available here: http://www.itk.org/Wiki/ParaView/Users_Guide/Python_Calculator Hope that helps, Cory On Tue, Oct 7, 2014 at 2:51 PM, wrote: > Dear Utkarsh, > > I changed the Result Array names to sigmaXX etc but still get the same error > message. > I think the problem is with the product between the two unit vectors. > Simply calculating for example " iHat*iHat " yields the same error message. > > Would you know in general how to form a tensor field in paraview from its > components? > > > Thanks, > Gianna > > > > > > > > > > Quoting Utkarsh Ayachit : > >> Gianna, >> >> For Calculator filter, names with "_X", "_Y" have special meaning. >> Try change Calulators 1-9 to use Result Array names as "sigmaXX", >> "sigmaYY", etc. >> Does that work? >> >> Utkarsh >> >> On Mon, Oct 6, 2014 at 6:31 PM, >> wrote: >>> >>> Hello Utkarsh, >>> thanks for looking at it. >>> Attached is the state file: >>> - Calculators 1-6 calculate the 6 independent components of the symmetric >>> stress tensor sigma_ij >>> >>> - Calculators 7-9 calculate the traction vectors s_i from the stress >>> components (s_i = sigma_ij e_j , summation over j implied, e_j basis >>> vectors) >>> >>> Now in another calculator I'd like to compute the stress tensor field, >>> either directly from the stress components sigma_ij or from the traction >>> vectors. Both approaches fail with the error message. >>> The stress tensor is given by >>> sigma = >>> >>> sigma_xx(e_x*e_x)+sigma_yy(e_y*e_y)+sigma_zz(e_z*_ez)+sigma_xy)(e_xe_y+e_ye_x)+sigma_xz(e_xe_z+e_ze_x)+sigma_yz(e_ye_z+e_ze_y) >>> equivalent to >>> sigma = s_x*e_x + s_y*e_y +s_z*e_z >>> >>> Thanks, >>> Gianna >>> >>> >>> >>> Quoting Utkarsh Ayachit : >>> >>>> Can you attach a sample data file/state file? That'll make it easier >>>> to identify the problem and suggest a solution. >>>> >>>> Thanks >>>> Utkarsh >>>> >>>> On Sat, Oct 4, 2014 at 4:14 AM, >>>> wrote: >>>>> >>>>> >>>>> Hello everyone, >>>>> >>>>> I have three displacement field vector components u, v, w in my .vtk >>>>> file >>>>> and wish to display the associated stress tensor. >>>>> I made the following steps: >>>>> >>>>> - Apply the filter Gradient Of Unstructued DataSet >>>>> -> Now have 9 scalars Gradient_0, ... , Gradient 8 >>>>> >>>>> - compute components of stress tensor via sigma_ij = div(Gradient) + >>>>> u_i,j >>>>> -> Now have additional 9 scalars sigma_ij >>>>> >>>>> - from this form traction vectors: >>>>> T_i = sigma_ij e_j ,where e_j are the unit vectors iHat >>>>> >>>>> -> Now have three traction vectors from which the tensor field >>>>> computation >>>>> doesnt work: >>>>> >>>>> - I do Result = T_1*iHat + T_2*jHat + T_3*kHat for the tensor >>>>> calculation >>>>> and get the following error message: >>>>> >>>>> ERROR: In >>>>> >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>>> line 201 >>>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>>> operators >>>>> >>>>> >>>>> ERROR: In >>>>> >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>>> line 300 >>>>> vtkFunctionParser (0x205ddac0): expecting either 2 scalars or a scalar >>>>> and a >>>>> vector >>>>> >>>>> >>>>> ERROR: In >>>>> >>>>> >>>>> /home/abuild/rpmbuild/BUILD/ParaView-v4.0.1-source/VTK/Common/Misc/vtkFunctionParser.cxx, >>>>> line 201 >>>>> vtkFunctionParser (0x205ddac0): Parse: Error deciding between ambiguous >>>>> operators >>>>> >>>>> >>>>> - Can you help me or tell me gow to visualize the stress tensor from >>>>> the >>>>> displacement field? >>>>> - Alternatively you it would also be good to know how to multiply the >>>>> result >>>>> of filter Gradient of Unstructured DataSet by a scalar value. >>>>> >>>>> >>>>> Many thanks for helping! >>>>> Gianna >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>>> >>> >>> >> >> > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From mvanmoer at illinois.edu Tue Oct 7 18:40:38 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Tue, 7 Oct 2014 22:40:38 +0000 Subject: [Paraview] ParaView plugin load error Message-ID: <7F781841FF1E044388AFA42B70703A7A89FB6D4E@CHIMBX6.ad.uillinois.edu> Follow up question, since the ParaView 3.14.1 pre-built 64 bit binaries come with msvcr90.dll, msvcp90.dll, etc. which is from VS 2005, does that mean VS 2005 is the newest Visual Studio I can use to build redistributable plugins for ParaView 3.14.1? Mark From: Vanmoer, Mark W Sent: Tuesday, October 07, 2014 12:22 PM To: paraview Subject: ParaView plugin load error Hi, I'm working on a legacy ParaView 3.14.1 plugin project. On Windows, I can't seem to figure out the settings so that the plugin .dlls will work on any machine other than the dev machine. The errors I get are along the lines of: *************************************************** Attempting to load C:\Program Files\ParaView 3.14.1\bin\plugins\RVA_Core_Plugin.dll ERROR: In ..\..\..\..\src\ParaViewCore\ClientServerCore\vtkPVPluginLoader.cxx, line 296 vtkPVPluginLoader (000000000B21CBC0): The specified procedure could not be found. I take this to mean that some other library can't be found. I'm not doing a Superbuild, because I don't want to redistribute an entire ParaView, just the the plugin. Should I be using the Superbuild anyway? Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Tue Oct 7 19:07:46 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 7 Oct 2014 19:07:46 -0400 Subject: [Paraview] ParaView plugin load error In-Reply-To: <7F781841FF1E044388AFA42B70703A7A89FB6D4E@CHIMBX6.ad.uillinois.edu> References: <7F781841FF1E044388AFA42B70703A7A89FB6D4E@CHIMBX6.ad.uillinois.edu> Message-ID: Mark, If you intend your plugin to be loadable with the distributed binaries for 3.14, you must indeed use the same compiler as listed here[1] for the appropriate version and OS. For 3.14, that's VS2008. [1] http://www.paraview.org/Wiki/ParaView/Binaries On Tue, Oct 7, 2014 at 6:40 PM, Vanmoer, Mark W wrote: > Follow up question, since the ParaView 3.14.1 pre-built 64 bit binaries come > with msvcr90.dll, msvcp90.dll, etc. which is from VS 2005, does that mean VS > 2005 is the newest Visual Studio I can use to build redistributable plugins > for ParaView 3.14.1? > > > > Mark > > > > From: Vanmoer, Mark W > Sent: Tuesday, October 07, 2014 12:22 PM > To: paraview > Subject: ParaView plugin load error > > > > Hi, > > > > I?m working on a legacy ParaView 3.14.1 plugin project. On Windows, I can?t > seem to figure out the settings so that the plugin .dlls will work on any > machine other than the dev machine. > > > > The errors I get are along the lines of: > > *************************************************** > Attempting to load C:\Program Files\ParaView > 3.14.1\bin\plugins\RVA_Core_Plugin.dll > ERROR: In > ..\..\..\..\src\ParaViewCore\ClientServerCore\vtkPVPluginLoader.cxx, line > 296 > vtkPVPluginLoader (000000000B21CBC0): The specified procedure could not be > found. > > I take this to mean that some other library can?t be found. > > > > I?m not doing a Superbuild, because I don?t want to redistribute an entire > ParaView, just the the plugin. Should I be using the Superbuild anyway? > > > > Mark > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From pspeachum at gmail.com Wed Oct 8 03:11:35 2014 From: pspeachum at gmail.com (Philipp E) Date: Wed, 08 Oct 2014 09:11:35 +0200 Subject: [Paraview] 3D contour smoothness In-Reply-To: References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> Message-ID: <5434E3A7.1030009@googlemail.com> Hi Cory, can you report any updates for this issue? Best regards and thanks for your efforts Philipp On 09/19/2014 07:17 PM, Cory Quammen wrote: > Just a little more info on this. The problem starts with 3.98. > > On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: >> Sorry Cory, >> >> you are right. The cell number is the same. >> >> Regards >> Philipp >> >> >> Am 19.09.2014 um 17:46 schrieb Cory Quammen: >>> Philipp, >>> >>> I can confirm what you see with a pre 4.2 version of ParaView. >>> However, the number of produced cells is the same. >>> >>> I will try to track down why this changed. >>> >>> Thanks, >>> Cory >>> >>> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>>> Hi Cory >>>> >>>> I managed to compress the data set to a fair size and attached it to >>>> this mail. The data set is pressure, contour value is 0.55. >>>> >>>> By looking again at the data (contour -> information), I just found that >>>> the old version (3.14.1) uses 148432 cells , while the the new one >>>> employs 75232 cells. Hope that helps. >>>> >>>> Kind regards >>>> Philipp >>>> >>>> Errata: I meant 4.2.0RC1 in the previous mails. >>>> >>>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>>> Phillipp, >>>>> >>>>> Do you have a data set similar to the one you've shown that you can share? >>>>> >>>>> Thanks, >>>>> Cory >>>>> >>>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>>> Hi Cory, >>>>>> >>>>>> thank you for your fast feedback. >>>>>> >>>>>> a) Compute normal is checked. (Without normals, the contour is >>>>>> completely stepped) >>>>>> b) Contour values are the same. >>>>>> >>>>>> Regards >>>>>> Philipp >>>>>> >>>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>>> Philipp, >>>>>>> >>>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>>> >>>>>>> Also, are the contour values the same between the two versions? >>>>>>> >>>>>>> Thanks, >>>>>>> Cory >>>>>>> >>>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>>> Hello everyone, >>>>>>>> >>>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>>> >>>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>>> >>>>>>>> 3.14.1 >>>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>>> 4.0.RC1 >>>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>>> >>>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>>> option we/setting/data problem we are not aware of. >>>>>>>> >>>>>>>> Kind regards and thanks in advance >>>>>>>> Philipp Engels. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview From Jim.Eliot at awe.co.uk Wed Oct 8 04:20:13 2014 From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk) Date: Wed, 8 Oct 2014 08:20:13 +0000 Subject: [Paraview] Problem building plugin against ParaView 4.2.0 In-Reply-To: <54341B0C.9070902@xs4all.nl> References: <201410071325.s97DPBsq004082@msw1.awe.co.uk> <54341B0C.9070902@xs4all.nl> Message-ID: <201410080820.s988KG1j011536@msw1.awe.co.uk> Hi Bertwim, This worked for me - cmake now finds Qt and builds the plugin. Many thanks. It isn't clear to me why it previously worked with PV 4.1.0 but not with 4.2.0. I guess it doesn't matter as long as it's working :) Kind regards, Jim ________________________________ From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of B.W.H. van Beest Sent: 07 October 2014 17:56 To: paraview at paraview.org Subject: EXTERNAL: Re: [Paraview] Problem building plugin against ParaView 4.2.0 Jim, I had similar issues you describe. They were gone when I made sure that, before actually calling cmake, the right 'qmake' was in the PATH (i.e. 'which qmake' points to the qmake of the AQT-version your expect). This assumes that you do have a Qt installation which is complete. In other words: 1. ensure qmake of the Qt distribution you expect is in your path 2. ensure your paraview build directory is clean ( rm -rf /build/* ) 3. start the cmake configuration. Hope this works for you too, Regards, Bertwim On 10/07/2014 03:25 PM, Jim.Eliot at awe.co.uk wrote: Hello everyone, I am trying to build a file reader plugin against ParaView 4.2.0 and have been experiencing some difficulties. Qt is not found by cmake during the build process causing it to fail. To illustrate the issue, I created the following simplified CMakeLists.txt file: CMAKE_MINIMUM_REQUIRED FIND_PACKAGE(ParaView REQUIRED) INCLUDE(${PARAVIEW_USE_FILE}) When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is found, but with 4.2.0 Qt is NOT found. ParaView was built using Superbuild and Qt was built as part of that process. Should Qt be detected from ParaViewConfig.cmake? Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow need to specify the location of Qt manually? Any ideas? Thank you, Jim Jim Eliot High Performance Computing Group AWE, Aldermaston, Reading, RG7 4PR ___________________________________________________ ____________________________ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview ___________________________________________________ ____________________________ The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Wed Oct 8 07:47:52 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Wed, 8 Oct 2014 07:47:52 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <5434E3A7.1030009@googlemail.com> References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> <5434E3A7.1030009@googlemail.com> Message-ID: Philipp, I apologize, but I haven't had time to look more into this problem. I'll have another look soon. Thanks, Cory On Wed, Oct 8, 2014 at 3:11 AM, Philipp E wrote: > Hi Cory, > > can you report any updates for this issue? > > Best regards and thanks for your efforts > Philipp > > On 09/19/2014 07:17 PM, Cory Quammen wrote: >> Just a little more info on this. The problem starts with 3.98. >> >> On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: >>> Sorry Cory, >>> >>> you are right. The cell number is the same. >>> >>> Regards >>> Philipp >>> >>> >>> Am 19.09.2014 um 17:46 schrieb Cory Quammen: >>>> Philipp, >>>> >>>> I can confirm what you see with a pre 4.2 version of ParaView. >>>> However, the number of produced cells is the same. >>>> >>>> I will try to track down why this changed. >>>> >>>> Thanks, >>>> Cory >>>> >>>> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>>>> Hi Cory >>>>> >>>>> I managed to compress the data set to a fair size and attached it to >>>>> this mail. The data set is pressure, contour value is 0.55. >>>>> >>>>> By looking again at the data (contour -> information), I just found that >>>>> the old version (3.14.1) uses 148432 cells , while the the new one >>>>> employs 75232 cells. Hope that helps. >>>>> >>>>> Kind regards >>>>> Philipp >>>>> >>>>> Errata: I meant 4.2.0RC1 in the previous mails. >>>>> >>>>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>>>> Phillipp, >>>>>> >>>>>> Do you have a data set similar to the one you've shown that you can share? >>>>>> >>>>>> Thanks, >>>>>> Cory >>>>>> >>>>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>>>> Hi Cory, >>>>>>> >>>>>>> thank you for your fast feedback. >>>>>>> >>>>>>> a) Compute normal is checked. (Without normals, the contour is >>>>>>> completely stepped) >>>>>>> b) Contour values are the same. >>>>>>> >>>>>>> Regards >>>>>>> Philipp >>>>>>> >>>>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>>>> Philipp, >>>>>>>> >>>>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>>>> >>>>>>>> Also, are the contour values the same between the two versions? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Cory >>>>>>>> >>>>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>>>> Hello everyone, >>>>>>>>> >>>>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>>>> >>>>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>>>> >>>>>>>>> 3.14.1 >>>>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>>>> 4.0.RC1 >>>>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>>>> >>>>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>>>> option we/setting/data problem we are not aware of. >>>>>>>>> >>>>>>>>> Kind regards and thanks in advance >>>>>>>>> Philipp Engels. >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview > From f.veronesi at scsitaly.com Wed Oct 8 08:57:09 2014 From: f.veronesi at scsitaly.com (Federico Veronesi) Date: Wed, 8 Oct 2014 14:57:09 +0200 Subject: [Paraview] Bug Report: Image Data are not pickable In-Reply-To: References: Message-ID: Dear Utkarsh, I opened the bug report. However If you or somebody else can point me in the right direction I can try to fix the bug. Regards Federico -------------------------------- Federico Veronesi, PhD SCS s.r.l. - Via Parini 1, Casalecchio di Reno (BO) Italy CINECA - Via Magnanelli 6/3, Casalecchio di Reno (BO) Italy Phone: +39 051 6171624 E-mail: f.veronesi at scsitaly.com 2014-10-06 22:27 GMT+02:00 Utkarsh Ayachit : > Yes, that is a known issue, but don't think we have a bug tracker item > for it. Please feel free to add one. > > Thanks, > Utkarsh > > On Mon, Oct 6, 2014 at 11:31 AM, Federico Veronesi > wrote: > > Hello, > > > > I am developing a tool based on Paraview and I found this incorrect > > functionality: > > > > Image Data (I tested with Wavelet Source) is not pickable when it is > > displayed with slice, volume or outline representation, even if the > pickable > > checkbox is checked. > > In my test I opened a render view and visualized a polydata (box) and an > > image data (wavelet) source, if I click on the box it is selected, but > if I > > click on the wavelet in slice, volume and outlie representation it is > not. > > > > Even if it it less problematic, the same behaviour happens for Text > source > > as it has been reported in this bug > > http://www.paraview.org/Bug/view.php?id=12177 > > > > Should I open a bug report on Matis? > > > > Thanks > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dragowsky at case.edu Wed Oct 8 08:59:06 2014 From: dragowsky at case.edu (E.M. Dragowsky) Date: Wed, 8 Oct 2014 08:59:06 -0400 Subject: [Paraview] Newbie question: How to search the archive? Working with 'point data' Message-ID: Greetings -- I'm new to the list, and working through the Paraview Tutorial a 2nd time (amazing how much can be forgotten with a 1 year lapse). This time around, I'm specifically interested in working with point data, for which I have 3D positions and velocities in white-space delimited text (ascii) files. I'd like to search the archives for discussions related to handling this type of data, but there are no obvious search capabilities at the public.kitware.com/ archive-related pages that I've found -- just instructions to register for the mailing list. Help with any of the above will be appreciated! Cheers, ~ E.m. ---------------------------------- E.M. Dragowsky, Ph.D. Advanced Research Computing -- ITS Adjunct Research Associate Professor, Physics Case Western Reserve University (216) 368-8995 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 8 09:29:39 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Oct 2014 09:29:39 -0400 Subject: [Paraview] Newbie question: How to search the archive? Working with 'point data' In-Reply-To: References: Message-ID: Hey E.M., First thing I recommend is to read the data in with the delimited text reader, then apply table to points. Attached is a state file to demonstrate. Eventually you may want to move to a more efficient (e.g. binary) format for performance and scalability but this will get you started. My preferred way to search the list archives is markmail.org. http://markmail.org/search/?q=paraview cheers David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 8:59 AM, E.M. Dragowsky wrote: > Greetings -- > > I'm new to the list, and working through the Paraview Tutorial a 2nd time > (amazing how much can be forgotten with a 1 year lapse). > > This time around, I'm specifically interested in working with point data, > for which I have 3D positions and velocities in white-space delimited text > (ascii) files. > > I'd like to search the archives for discussions related to handling this > type of data, but there are no obvious search capabilities at the > public.kitware.com/ archive-related pages that I've found -- just > instructions to register for the mailing list. > > Help with any of the above will be appreciated! > Cheers, > ~ E.m. > > ---------------------------------- > E.M. Dragowsky, Ph.D. > Advanced Research Computing -- ITS > Adjunct Research Associate Professor, Physics > Case Western Reserve University > (216) 368-8995 > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ptx pty ptz vx vy vz 0 1 2 0 -1 -2 3 4 5 -3 -4 -5 -------------- next part -------------- A non-text attachment was scrubbed... Name: txt_to_ptvect.pvsm Type: application/octet-stream Size: 59836 bytes Desc: not available URL: From a.benitez at student.maastrichtuniversity.nl Wed Oct 8 09:57:50 2014 From: a.benitez at student.maastrichtuniversity.nl (Benitez Andonegui, Amaia (Stud. FPN)) Date: Wed, 8 Oct 2014 15:57:50 +0200 Subject: [Paraview] exporting .vtk files to Matlab Message-ID: Hi Paraview community, I want to export a .vtk file to Matlab. To do so, I read some time ago that I could save the .vtk file as a .csv and read it easily in Matlab. Thus, that's what I tried. When I open the .csv file in Matlab, I get the position of the vertices but not the intensities associated to them. That information is basically missing. I also tried to read the .vtk file in Matlab by a customized function, and again, the information related to the intensities is missing. So I was wondering if there is a way to keep those intensity values. Thanks in advance! Cheers, Amaia. From mike.jackson at bluequartz.net Wed Oct 8 12:26:25 2014 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Wed, 8 Oct 2014 12:26:25 -0400 Subject: [Paraview] Animating over MultiBlock data set Message-ID: I am writing an Xdmf file with 75 "Grids" where each grid represents a time step from a simulation. When I read it into ParaView it shows 75 Blocks. I can load each one at a time and I get the expected output. What is the magic to animating over a multi-block data set. Each block has the same exact set of Data arrays. Ideas? _________________________________________________________ Mike Jackson BlueQuartz Software Help: dream3d at bluequartz.net Web|Download http://dream3d.bluequartz.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Wed Oct 8 13:18:24 2014 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 08 Oct 2014 20:18:24 +0300 Subject: [Paraview] Animating over MultiBlock data set In-Reply-To: References: Message-ID: <543571E0.5030300@gmail.com> Do I understand it correctly that you have always a uniform geometry, just the data changes in time? Are you using something like this: Well, I attached a small xdmf file that shows how to animate in time (assuming a constant geometry). Hope it is of help. -Armin On 10/08/2014 07:26 PM, Michael Jackson wrote: > I am writing an Xdmf file with 75 "Grids" where each grid represents a > time step from a simulation. When I read it into ParaView it shows 75 > Blocks. I can load each one at a time and I get the expected output. > What is the magic to animating over a multi-block data set. Each block > has the same exact set of Data arrays. > > Ideas? > _________________________________________________________ > Mike Jackson BlueQuartz Software > Help: dream3d at bluequartz.net > Web|Download http://dream3d.bluequartz.net > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: circAvg2.xmf Type: audio/x-xmf Size: 1924 bytes Desc: not available URL: From mike.jackson at bluequartz.net Wed Oct 8 14:14:54 2014 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Wed, 8 Oct 2014 14:14:54 -0400 Subject: [Paraview] Animating over MultiBlock data set In-Reply-To: <543571E0.5030300@gmail.com> References: <543571E0.5030300@gmail.com> Message-ID: The Topology stays the same for every time step (There are Vertex Points). The actual position of the points move in time (The Geometry changes). Mike Jackson. On Oct 8, 2014, at 1:18 PM, Armin Wehrfritz wrote: > Do I understand it correctly that you have always a uniform geometry, just the data changes in time? > > Are you using something like this: > > > Well, I attached a small xdmf file that shows how to animate in time (assuming a constant geometry). Hope it is of help. > > -Armin > > > > On 10/08/2014 07:26 PM, Michael Jackson wrote: >> I am writing an Xdmf file with 75 "Grids" where each grid represents a >> time step from a simulation. When I read it into ParaView it shows 75 >> Blocks. I can load each one at a time and I get the expected output. >> What is the magic to animating over a multi-block data set. Each block >> has the same exact set of Data arrays. >> >> Ideas? >> _________________________________________________________ >> Mike Jackson BlueQuartz Software >> Help: dream3d at bluequartz.net >> Web|Download http://dream3d.bluequartz.net >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From dfiorillo at lara.unb.br Wed Oct 8 14:43:09 2014 From: dfiorillo at lara.unb.br (David Fiorillo) Date: Wed, 8 Oct 2014 15:43:09 -0300 Subject: [Paraview] Video generation Message-ID: Dear all, I am running paraview 4.2.0 under ubuntu 14 and trying to generate a ogv video but appeared this error. ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/Animation/vtkSMAnimationSceneImageWriter.cxx, line 385 pqAnimationSceneImageWriter (0x89c4ab0): Unknown extension .ogv I returned to 4.1.0 version and worked. Could anyone suggest solution to 4.2.0? Best regards, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkxls23 at gmail.com Wed Oct 8 14:48:55 2014 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Wed, 08 Oct 2014 21:48:55 +0300 Subject: [Paraview] Animating over MultiBlock data set In-Reply-To: References: <543571E0.5030300@gmail.com> Message-ID: <54358717.3020803@gmail.com> In that case you have to at least put the Geometry section inside the temporal grid. I attached a xdmf file that shows how it should look then (the file works for changing Geometry and Topology). If you can post the relevant part of your xdmf file, it would probably be easier see what is going wrong. -Armin On 10/08/2014 09:14 PM, Michael Jackson wrote: > The Topology stays the same for every time step (There are Vertex Points). The actual position of the points move in time (The Geometry changes). > > > Mike Jackson. > > On Oct 8, 2014, at 1:18 PM, Armin Wehrfritz wrote: > >> Do I understand it correctly that you have always a uniform geometry, just the data changes in time? >> >> Are you using something like this: >> >> >> Well, I attached a small xdmf file that shows how to animate in time (assuming a constant geometry). Hope it is of help. >> >> -Armin >> >> >> >> On 10/08/2014 07:26 PM, Michael Jackson wrote: >>> I am writing an Xdmf file with 75 "Grids" where each grid represents a >>> time step from a simulation. When I read it into ParaView it shows 75 >>> Blocks. I can load each one at a time and I get the expected output. >>> What is the magic to animating over a multi-block data set. Each block >>> has the same exact set of Data arrays. >>> >>> Ideas? >>> _________________________________________________________ >>> Mike Jackson BlueQuartz Software >>> Help: dream3d at bluequartz.net >>> Web|Download http://dream3d.bluequartz.net >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: surfaces.runTime_xzPlane2.xmf Type: audio/x-xmf Size: 2195 bytes Desc: not available URL: From mike.jackson at bluequartz.net Wed Oct 8 16:28:27 2014 From: mike.jackson at bluequartz.net (Michael Jackson) Date: Wed, 8 Oct 2014 16:28:27 -0400 Subject: [Paraview] Animating over MultiBlock data set In-Reply-To: <54358717.3020803@gmail.com> References: <543571E0.5030300@gmail.com> <54358717.3020803@gmail.com> Message-ID: <1838E9F4-FCD2-4D44-95F4-8FD9DF2336FA@bluequartz.net> Thanks for the help. I was able to get an animation to work. Now I just need to clean up some of my own code that writes the .xdmf file. Cheers Mike Jackson On Oct 8, 2014, at 2:48 PM, Armin Wehrfritz wrote: > In that case you have to at least put the Geometry section inside the temporal grid. > > I attached a xdmf file that shows how it should look then (the file works for changing Geometry and Topology). > > If you can post the relevant part of your xdmf file, it would probably be easier see what is going wrong. > > -Armin > > > > > On 10/08/2014 09:14 PM, Michael Jackson wrote: >> The Topology stays the same for every time step (There are Vertex Points). The actual position of the points move in time (The Geometry changes). >> >> >> Mike Jackson. >> >> On Oct 8, 2014, at 1:18 PM, Armin Wehrfritz wrote: >> >>> Do I understand it correctly that you have always a uniform geometry, just the data changes in time? >>> >>> Are you using something like this: >>> >>> >>> Well, I attached a small xdmf file that shows how to animate in time (assuming a constant geometry). Hope it is of help. >>> >>> -Armin >>> >>> >>> >>> On 10/08/2014 07:26 PM, Michael Jackson wrote: >>>> I am writing an Xdmf file with 75 "Grids" where each grid represents a >>>> time step from a simulation. When I read it into ParaView it shows 75 >>>> Blocks. I can load each one at a time and I get the expected output. >>>> What is the magic to animating over a multi-block data set. Each block >>>> has the same exact set of Data arrays. >>>> >>>> Ideas? >>>> _________________________________________________________ >>>> Mike Jackson BlueQuartz Software >>>> Help: dream3d at bluequartz.net >>>> Web|Download http://dream3d.bluequartz.net >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From phil.amburn at gmail.com Wed Oct 8 17:25:43 2014 From: phil.amburn at gmail.com (Phil Amburn) Date: Wed, 8 Oct 2014 14:25:43 -0700 Subject: [Paraview] displaying simulation time rather than time step Message-ID: <5435abd6.0576320a.7a74.1035@mx.google.com> I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 . So, rather than Time: 0 at the bottom of the 3D window, I'd like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Oct 8 17:38:17 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 8 Oct 2014 17:38:17 -0400 Subject: [Paraview] ANNOUNCE: Kitware is hiring Message-ID: Hi folks, We are looking to hire visualization developers to our Scientific Computing team. If you are a talented visualization researcher and developer with strong C++ skills, please consider applying. You will join a great team and work on many interesting and challenging technical problems - always aiming to deliver robust and widely used software solutions. For the full posting see: http://tinyurl.com/l8sgvzw JOB DESCRIPTION Kitware is seeking to hire highly skilled Research and Development Engineers (R&D Engineers) to join our Scientific Computing team and contribute to our scientific and information visualization efforts. Candidates will work to develop and improve leading visualization software solutions. Kitware collaborates on a multitude of basic and applied research and development projects. Our collaborators include the top universities from around the world, national research labs, medical device manufacturers, car manufacturers, oil and gas companies, financial institutes, and many others. The projects range from extending our open source C++ libraries and applications, such as VTK, ParaView, and CMake, to developing proprietary domain-specific vertical applications for a wide array of platforms including web and mobile devices. By joining our team you will participate in a dynamic work environment with exceptionally talented and friendly coworkers who are committed to high-quality development practices. You will collaborate with esteemed researchers from around the world by: * Designing and developing scalable data analysis and visualization tools for use by researchers and professionals from various domains; * Solving a wide array of problems ranging from developing distributed memory parallel algorithms for data analysis, optimizing distributed parallel codes to compiling and maintaining software on supercomputers. * Designing and developing tools to improve scientific data analysis workflows; * Contributing to and supporting our dynamic open source communities built around several of our open source tools. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Oct 8 18:17:50 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 8 Oct 2014 22:17:50 +0000 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: <5435abd6.0576320a.7a74.1035@mx.google.com> References: <5435abd6.0576320a.7a74.1035@mx.google.com> Message-ID: Phil, I have no idea how to put out what you are asking for, but it is a really good idea. If you don't get an answer, be sure to write up a bug report/ feature request. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Phil Amburn Sent: Wednesday, October 08, 2014 3:26 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] displaying simulation time rather than time step I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 ... So, rather than Time: 0 at the bottom of the 3D window, I'd like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sean.Ziegeler at engilitycorp.com Wed Oct 8 18:41:09 2014 From: Sean.Ziegeler at engilitycorp.com (Sean.Ziegeler at engilitycorp.com) Date: Wed, 8 Oct 2014 22:41:09 +0000 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: References: <5435abd6.0576320a.7a74.1035@mx.google.com>, Message-ID: Hey Phil, You *might* be able to hack it with a combination of a Programmable Filter and a Python Annotation Filter. Use the Programmable Filter to add a FieldData value to each time step that is a string with the appropriate date. Then use the Python Annotation Filter to display the date as an annotation. The first part is the hard one. The Programmable Filter could either (1) read the file once to get all the dates, or (2) compute the dates using the starting date, the time step value, and Python's datetime module. Thanks, Sean ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: Wednesday, October 08, 2014 5:17 PM To: Phil Amburn; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Phil, I have no idea how to put out what you are asking for, but it is a really good idea. If you don?t get an answer, be sure to write up a bug report/ feature request. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Phil Amburn Sent: Wednesday, October 08, 2014 3:26 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] displaying simulation time rather than time step I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 ? So, rather than Time: 0 at the bottom of the 3D window, I?d like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: From phil.amburn at gmail.com Wed Oct 8 19:53:32 2014 From: phil.amburn at gmail.com (Phil Amburn) Date: Wed, 8 Oct 2014 16:53:32 -0700 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: References: <5435abd6.0576320a.7a74.1035@mx.google.com>, Message-ID: <5435ce7a.2a61320a.0987.ffffd1bb@mx.google.com> Hi Sean, Can we talk? I'm not smart enough to understand your suggestion (hate it when that happens). If I get something worked out, even a hack, I'll post the solution back to this list. Thanks! Phil From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Sean.Ziegeler at engilitycorp.com Sent: Wednesday, October 08, 2014 3:41 PM To: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Hey Phil, You *might* be able to hack it with a combination of a Programmable Filter and a Python Annotation Filter. Use the Programmable Filter to add a FieldData value to each time step that is a string with the appropriate date. Then use the Python Annotation Filter to display the date as an annotation. The first part is the hard one. The Programmable Filter could either (1) read the file once to get all the dates, or (2) compute the dates using the starting date, the time step value, and Python's datetime module. Thanks, Sean _____ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: Wednesday, October 08, 2014 5:17 PM To: Phil Amburn; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Phil, I have no idea how to put out what you are asking for, but it is a really good idea. If you don't get an answer, be sure to write up a bug report/ feature request. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Phil Amburn Sent: Wednesday, October 08, 2014 3:26 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] displaying simulation time rather than time step I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 . So, rather than Time: 0 at the bottom of the 3D window, I'd like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 8 20:53:04 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Oct 2014 20:53:04 -0400 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: <5435ce7a.2a61320a.0987.ffffd1bb@mx.google.com> References: <5435abd6.0576320a.7a74.1035@mx.google.com> <5435ce7a.2a61320a.0987.ffffd1bb@mx.google.com> Message-ID: I think that Sean is on the right track and suggest that a Python Animation cue is the way to go. Attached is a state file to demonstrate. Load the state file in ParaView, open Views->Animation View and double click on the existing Python track to see the script that gets the pipeline time and feeds it into a text source for display. I've left the parts about reading the file and mapping the Animation time into the corresponding simulation time as an exercise to the reader. Note: many time varying file formats produce the data time for you so this translation is unnecessary and the Annotate Time filter will do what you want it to. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 7:53 PM, Phil Amburn wrote: > Hi Sean, > > > > Can we talk? I?m not smart enough to understand your suggestion (hate it > when that happens). > > > > If I get something worked out, even a hack, I?ll post the solution back to > this list. > > > > Thanks! > > Phil > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of * > Sean.Ziegeler at engilitycorp.com > *Sent:* Wednesday, October 08, 2014 3:41 PM > *To:* paraview at paraview.org > > *Subject:* Re: [Paraview] [EXTERNAL] displaying simulation time rather > than time step > > > > Hey Phil, > You *might* be able to hack it with a combination of a Programmable Filter > and a Python Annotation Filter. Use the Programmable Filter to add a > FieldData value to each time step that is a string with the appropriate > date. Then use the Python Annotation Filter to display the date as an > annotation. > > The first part is the hard one. The Programmable Filter could either (1) > read the file once to get all the dates, or (2) compute the dates using the > starting date, the time step value, and Python's datetime module. > > Thanks, > Sean > ------------------------------ > > *From:* ParaView [paraview-bounces at paraview.org] on behalf of Scott, W > Alan [wascott at sandia.gov] > *Sent:* Wednesday, October 08, 2014 5:17 PM > *To:* Phil Amburn; paraview at paraview.org > *Subject:* Re: [Paraview] [EXTERNAL] displaying simulation time rather > than time step > > Phil, > > I have no idea how to put out what you are asking for, but it is a really > good idea. If you don?t get an answer, be sure to write up a bug report/ > feature request. > > > > Alan > > > > *From:* ParaView [mailto:paraview-bounces at paraview.org > ] *On Behalf Of *Phil Amburn > *Sent:* Wednesday, October 08, 2014 3:26 PM > *To:* paraview at paraview.org > *Subject:* [EXTERNAL] [Paraview] displaying simulation time rather than > time step > > > > I would like to do something similar to the Annotate Time filter, but > rather than displaying the time step number, I need to display simulation > date and time. > > > > I have a text file with the actual simulation date and time associated > with each time step. Here are the first few lines of that file > > > > Time step Time step output, Actual time > > 0 0.00, 4/1/2013 15:00 > > 1 65.83, 4/1/2013 15:01 > > 2 125.88, 4/1/2013 15:02 > > 3 201.00, 4/1/2013 15:03 > > 4 268.65, 4/1/2013 15:04 > > 5 328.83, 4/1/2013 15:05 > > 6 366.46, 4/1/2013 15:06 > > > > ? > > > > So, rather than Time: 0 at the bottom of the 3D window, I?d like to have > 4/1/2013 15:00 > > > > Any thoughts / recommendations on how to accomplish this task will be > greatly appreciated. > > > > Thanks, > > Phil > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: showtime.pvsm Type: application/octet-stream Size: 30449 bytes Desc: not available URL: From dave.demarle at kitware.com Wed Oct 8 20:56:42 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Oct 2014 20:56:42 -0400 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: References: <5435abd6.0576320a.7a74.1035@mx.google.com> <5435ce7a.2a61320a.0987.ffffd1bb@mx.google.com> Message-ID: Strike that last comment about Annotate Time doing the right thing. There are probably file formats that make the date/time string available, but I can't name one off the top of my head and you will still need to hook up the connection to the Text Source something like above. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 8:53 PM, David E DeMarle wrote: > I think that Sean is on the right track and suggest that a Python > Animation cue is the way to go. > > Attached is a state file to demonstrate. Load the state file in ParaView, > open Views->Animation View and double click on the existing Python track to > see the script that gets the pipeline time and feeds it into a text source > for display. I've left the parts about reading the file and mapping the > Animation time into the corresponding simulation time as an exercise to the > reader. > > Note: many time varying file formats produce the data time for you so this > translation is unnecessary and the Annotate Time filter will do what you > want it to. > > > > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Oct 8, 2014 at 7:53 PM, Phil Amburn wrote: > >> Hi Sean, >> >> >> >> Can we talk? I?m not smart enough to understand your suggestion (hate it >> when that happens). >> >> >> >> If I get something worked out, even a hack, I?ll post the solution back >> to this list. >> >> >> >> Thanks! >> >> Phil >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of * >> Sean.Ziegeler at engilitycorp.com >> *Sent:* Wednesday, October 08, 2014 3:41 PM >> *To:* paraview at paraview.org >> >> *Subject:* Re: [Paraview] [EXTERNAL] displaying simulation time rather >> than time step >> >> >> >> Hey Phil, >> You *might* be able to hack it with a combination of a Programmable >> Filter and a Python Annotation Filter. Use the Programmable Filter to add >> a FieldData value to each time step that is a string with the appropriate >> date. Then use the Python Annotation Filter to display the date as an >> annotation. >> >> The first part is the hard one. The Programmable Filter could either (1) >> read the file once to get all the dates, or (2) compute the dates using the >> starting date, the time step value, and Python's datetime module. >> >> Thanks, >> Sean >> ------------------------------ >> >> *From:* ParaView [paraview-bounces at paraview.org] on behalf of Scott, W >> Alan [wascott at sandia.gov] >> *Sent:* Wednesday, October 08, 2014 5:17 PM >> *To:* Phil Amburn; paraview at paraview.org >> *Subject:* Re: [Paraview] [EXTERNAL] displaying simulation time rather >> than time step >> >> Phil, >> >> I have no idea how to put out what you are asking for, but it is a really >> good idea. If you don?t get an answer, be sure to write up a bug report/ >> feature request. >> >> >> >> Alan >> >> >> >> *From:* ParaView [mailto:paraview-bounces at paraview.org >> ] *On Behalf Of *Phil Amburn >> *Sent:* Wednesday, October 08, 2014 3:26 PM >> *To:* paraview at paraview.org >> *Subject:* [EXTERNAL] [Paraview] displaying simulation time rather than >> time step >> >> >> >> I would like to do something similar to the Annotate Time filter, but >> rather than displaying the time step number, I need to display simulation >> date and time. >> >> >> >> I have a text file with the actual simulation date and time associated >> with each time step. Here are the first few lines of that file >> >> >> >> Time step Time step output, Actual time >> >> 0 0.00, 4/1/2013 15:00 >> >> 1 65.83, 4/1/2013 15:01 >> >> 2 125.88, 4/1/2013 15:02 >> >> 3 201.00, 4/1/2013 15:03 >> >> 4 268.65, 4/1/2013 15:04 >> >> 5 328.83, 4/1/2013 15:05 >> >> 6 366.46, 4/1/2013 15:06 >> >> >> >> ? >> >> >> >> So, rather than Time: 0 at the bottom of the 3D window, I?d like to have >> 4/1/2013 15:00 >> >> >> >> Any thoughts / recommendations on how to accomplish this task will be >> greatly appreciated. >> >> >> >> Thanks, >> >> Phil >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From praveenn at nvidia.com Wed Oct 8 21:08:11 2014 From: praveenn at nvidia.com (Praveen Narayanan) Date: Thu, 9 Oct 2014 01:08:11 +0000 Subject: [Paraview] Paraview Build Option - VTK_SMP_IMPLEMENTATION_TYPE; parallelization questions Message-ID: I would like to know what the flags imply: VTK_SMP_IMPLEMENTATION_TYPE: Which multi-threaded parallelism implementation to use. Options are Sequential, Simple, Kaapi or TBB. Is there a proper description of these parameters (or a an example/test in the suite)? The following paper yields some information: http://hal.inria.fr/docs/00/78/98/14/PDF/RR-8245.pdf I would assume that these improvements translate to the insertion of appropriate directives, semaphores and the like in several parts of VTK. Could you point me to material/papers which would explain implementation specific details? Some online sources (probably outdated) claim that VTK is not thread safe. Thanks Praveen. ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 8 21:34:12 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 8 Oct 2014 21:34:12 -0400 Subject: [Paraview] Paraview Build Option - VTK_SMP_IMPLEMENTATION_TYPE; parallelization questions In-Reply-To: References: Message-ID: Hi Praveen, The paper that you linked is the original implementation and is still quite relevant. See: http://www.vtk.org/Wiki/images/3/3b/VTK_SMP_Guide.pdf for more information on the work as it stands now that it has been brought into VTK proper (as of release 6.1) As that doc says, VTK is still largely _not_ thread safe. Portions of it always have been. For example anything used within the threaded image filters was before vtkSMP, and anything used within Filters/SMP is now. Turn on the Filters/SMP module to try it and take a look at the Cxx regression tests in the module itself for starters. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 9:08 PM, Praveen Narayanan wrote: > I would like to know what the flags imply: > > > > VTK_SMP_IMPLEMENTATION_TYPE: Which multi-threaded parallelism > implementation to use. Options are Sequential, Simple, Kaapi or TBB. > > > > Is there a proper description of these parameters (or a an example/test in > the suite)? > > The following paper yields some information: > http://hal.inria.fr/docs/00/78/98/14/PDF/RR-8245.pdf > > > > I would assume that these improvements translate to the insertion of > appropriate directives, semaphores and the like in several parts of VTK. > Could you point me to material/papers which would explain implementation > specific details? > > Some online sources (probably outdated) claim that VTK is not thread safe. > > > > > Thanks > > Praveen. > > > ------------------------------ > This email message is for the sole use of the intended recipient(s) and > may contain confidential information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. > ------------------------------ > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.harrison at liquidmesh.com Thu Oct 9 00:52:55 2014 From: ben.harrison at liquidmesh.com (ben) Date: Thu, 09 Oct 2014 15:52:55 +1100 Subject: [Paraview] Point swarm with one cell Message-ID: <543614A7.9060003@liquidmesh.com> I have a point swarm (output from Underworld thermal model), with one cell, and 32768 points. I cannot seem to get any sort of visualisation from it after filtering. If I apply a Threshold filter to 'remove' some of the data, nothing shows at all. If I first apply a Clip filter, but set it outside the range of the data, then the result is a dataset with 32768 cells, and 32768 points. The Threshold filter works after that. Why is this? Ben From biddisco at cscs.ch Thu Oct 9 02:59:55 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Thu, 9 Oct 2014 06:59:55 +0000 Subject: [Paraview] Point swarm with one cell In-Reply-To: <543614A7.9060003@liquidmesh.com> References: <543614A7.9060003@liquidmesh.com> Message-ID: <50320452A334BD42A5EC72BAD214509918F351E9@MBX210.d.ethz.ch> It's because most of the filters which operate on 'cells' don't really handle the multi-vertex cell type in the way you'd like. Converting the data to 32768 cells with one point each is the solution. you used to be able to use MaskPoints filter to do that, but the singlecellpervertex function is not exposed in paraview, so the threshold is one way to do it. -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of ben Sent: 09 October 2014 06:53 To: paraview at paraview.org Subject: [Paraview] Point swarm with one cell I have a point swarm (output from Underworld thermal model), with one cell, and 32768 points. I cannot seem to get any sort of visualisation from it after filtering. If I apply a Threshold filter to 'remove' some of the data, nothing shows at all. If I first apply a Clip filter, but set it outside the range of the data, then the result is a dataset with 32768 cells, and 32768 points. The Threshold filter works after that. Why is this? Ben _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From aleksejs.fomins at lspr.ch Thu Oct 9 05:33:00 2014 From: aleksejs.fomins at lspr.ch (Aleksejs Fomins) Date: Thu, 09 Oct 2014 11:33:00 +0200 Subject: [Paraview] Threshold not working for unstructured grid Message-ID: <5436564C.8030302@lspr.ch> Dear Paraview, I am new to this list, so I would like to immediately apologise if my style does not meet your standard. I am learning to use Paraview, and I have problems using the threshold filter. I have attached 2 .vtk files based on documentation examples to explain my point I use filters->common->threshold, then specify Scalars->cell_scalars and choose range [1,3]. * For the "polydata.vtk" I observe some of the rectangles disappear as expected. If I manipulate the range, I can get any one rectangle disappear. * For the "unstructured.vtk" I see all but one triangle disappear, which is unexpected. If I manipulate the range, either the tetrahedron disappears altogether, or only one triangle is visible. Could you please tell me what am I doing wrong? ---------------------------------------------------------------------- Paraview Version 4.1.0 64-bit QT Version 4.8.2 Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux ---------------------------------------------------------------------- Thank you, Aleksejs Fomins -------------- next part -------------- # vtk DataFile Version 2.0 Cube example ASCII DATASET POLYDATA POINTS 8 float 0.0 0.0 0.0 1.0 0.0 0.0 1.0 1.0 0.0 0.0 1.0 0.0 0.0 0.0 1.0 1.0 0.0 1.0 1.0 1.0 1.0 0.0 1.0 1.0 POLYGONS 6 30 4 0 1 2 3 4 4 5 6 7 4 0 1 5 4 4 2 3 7 6 4 0 4 7 3 4 1 2 6 5 CELL_DATA 6 SCALARS cell_scalars int 1 LOOKUP_TABLE default 0 1 2 3 4 5 -------------- next part -------------- # vtk DataFile Version 2.0 Test Paraview Example ASCII DATASET UNSTRUCTURED_GRID POINTS 4 float 0.0 0.0 0.0 1.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 1.0 CELLS 4 16 3 0 1 2 3 0 1 3 3 0 2 3 3 1 2 3 CELL_TYPES 4 5 5 5 5 CELL_DATA 4 SCALARS cell_scalars int 1 LOOKUP_TABLE default 0 1 2 3 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From biddisco at cscs.ch Thu Oct 9 07:12:21 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Thu, 9 Oct 2014 11:12:21 +0000 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: Message-ID: A similar question came up a few weeks ago and I posted this link https://hpcforge.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=pv-echam/pv-echam.git;a=blob;f=vtkJulianDayToTextConvertor.h;h=490320de30539ed88527ca79c53e2acc17264bf5;hb=HEAD To a class which takes climate simulation time stamps and converts them from julian date to a string. This can then be viewed in the paraview gui as a time stamp with an arbitrary format ? you can add the time as well as the date by some simple changes. I have not used it myself for several years, but just copied the vtkJulianDayToTextConverter.* files and jdn.c into another plugin and tried them. Apart from one tweak because DATA/UPDATE_TIME_STEPS are now singular it compiled ok and is working as expected. The class create a single text string in a 1x1 table and paraview displays this as an annotation. HTH JB From: David DeMarle > Date: Thursday 9 October 2014 02:56 To: Phil Amburn > Cc: "paraview at paraview.org" > Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Strike that last comment about Annotate Time doing the right thing. There are probably file formats that make the date/time string available, but I can't name one off the top of my head and you will still need to hook up the connection to the Text Source something like above. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 8:53 PM, David E DeMarle > wrote: I think that Sean is on the right track and suggest that a Python Animation cue is the way to go. Attached is a state file to demonstrate. Load the state file in ParaView, open Views->Animation View and double click on the existing Python track to see the script that gets the pipeline time and feeds it into a text source for display. I've left the parts about reading the file and mapping the Animation time into the corresponding simulation time as an exercise to the reader. Note: many time varying file formats produce the data time for you so this translation is unnecessary and the Annotate Time filter will do what you want it to. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 7:53 PM, Phil Amburn > wrote: Hi Sean, Can we talk? I?m not smart enough to understand your suggestion (hate it when that happens). If I get something worked out, even a hack, I?ll post the solution back to this list. Thanks! Phil From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Sean.Ziegeler at engilitycorp.com Sent: Wednesday, October 08, 2014 3:41 PM To: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Hey Phil, You *might* be able to hack it with a combination of a Programmable Filter and a Python Annotation Filter. Use the Programmable Filter to add a FieldData value to each time step that is a string with the appropriate date. Then use the Python Annotation Filter to display the date as an annotation. The first part is the hard one. The Programmable Filter could either (1) read the file once to get all the dates, or (2) compute the dates using the starting date, the time step value, and Python's datetime module. Thanks, Sean ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: Wednesday, October 08, 2014 5:17 PM To: Phil Amburn; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Phil, I have no idea how to put out what you are asking for, but it is a really good idea. If you don?t get an answer, be sure to write up a bug report/ feature request. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Phil Amburn Sent: Wednesday, October 08, 2014 3:26 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] displaying simulation time rather than time step I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 ? So, rather than Time: 0 at the bottom of the 3D window, I?d like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From andy.bauer at kitware.com Thu Oct 9 10:16:51 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 9 Oct 2014 10:16:51 -0400 Subject: [Paraview] Threshold not working for unstructured grid In-Reply-To: <5436564C.8030302@lspr.ch> References: <5436564C.8030302@lspr.ch> Message-ID: Hi Aleksejs, Welcome to the ParaView mailing list. This appears to be a bug that you've found. In case you didn't notice, for the unstructured grid there are 4 triangle cells that connect to look like a tet. I've added a Mantis issue at http://www.paraview.org/Bug/view.php?id=15040. Thanks, Andy On Thu, Oct 9, 2014 at 5:33 AM, Aleksejs Fomins wrote: > Dear Paraview, > > I am new to this list, so I would like to immediately apologise if my > style does not meet your standard. > > I am learning to use Paraview, and I have problems using the threshold > filter. I have attached 2 .vtk files based on documentation examples to > explain my point > > I use filters->common->threshold, then specify Scalars->cell_scalars > and choose range [1,3]. > > * For the "polydata.vtk" I observe some of the rectangles disappear as > expected. If I manipulate the range, I can get any one rectangle disappear. > > * For the "unstructured.vtk" I see all but one triangle disappear, which > is unexpected. If I manipulate the range, either the tetrahedron > disappears altogether, or only one triangle is visible. > > Could you please tell me what am I doing wrong? > > ---------------------------------------------------------------------- > Paraview Version 4.1.0 64-bit > QT Version 4.8.2 > Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux > ---------------------------------------------------------------------- > > Thank you, > Aleksejs Fomins > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Thu Oct 9 10:48:27 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Thu, 9 Oct 2014 14:48:27 +0000 Subject: [Paraview] ParaView plugin load error In-Reply-To: References: <7F781841FF1E044388AFA42B70703A7A89FB6D4E@CHIMBX6.ad.uillinois.edu> Message-ID: <7F781841FF1E044388AFA42B70703A7A89FB72D3@CHIMBX6.ad.uillinois.edu> Thanks Utkarsh, I'm so used to only building for my own system and not distributing that I hadn't run into this before. -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, October 07, 2014 6:08 PM To: Vanmoer, Mark W Cc: paraview Subject: Re: [Paraview] ParaView plugin load error Mark, If you intend your plugin to be loadable with the distributed binaries for 3.14, you must indeed use the same compiler as listed here[1] for the appropriate version and OS. For 3.14, that's VS2008. [1] http://www.paraview.org/Wiki/ParaView/Binaries On Tue, Oct 7, 2014 at 6:40 PM, Vanmoer, Mark W wrote: > Follow up question, since the ParaView 3.14.1 pre-built 64 bit > binaries come with msvcr90.dll, msvcp90.dll, etc. which is from VS > 2005, does that mean VS > 2005 is the newest Visual Studio I can use to build redistributable > plugins for ParaView 3.14.1? > > > > Mark > > > > From: Vanmoer, Mark W > Sent: Tuesday, October 07, 2014 12:22 PM > To: paraview > Subject: ParaView plugin load error > > > > Hi, > > > > I?m working on a legacy ParaView 3.14.1 plugin project. On Windows, I > can?t seem to figure out the settings so that the plugin .dlls will > work on any machine other than the dev machine. > > > > The errors I get are along the lines of: > > *************************************************** > Attempting to load C:\Program Files\ParaView > 3.14.1\bin\plugins\RVA_Core_Plugin.dll > ERROR: In > ..\..\..\..\src\ParaViewCore\ClientServerCore\vtkPVPluginLoader.cxx, > line > 296 > vtkPVPluginLoader (000000000B21CBC0): The specified procedure could > not be found. > > I take this to mean that some other library can?t be found. > > > > I?m not doing a Superbuild, because I don?t want to redistribute an > entire ParaView, just the the plugin. Should I be using the Superbuild anyway? > > > > Mark > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From leonardopessanha74 at gmail.com Thu Oct 9 11:12:13 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Thu, 9 Oct 2014 12:12:13 -0300 Subject: [Paraview] VRPN Interactions Message-ID: Dear all, I've been working with VRPN in a CAVE environment and my next goal is to do a slice in a vtk structured grid. I can choose the slice position pressing and moving the selected button and wand in the VR interaction configuration, but how can i hit the "Apply" button and actually slice the object? Att, Leonardo Pessanha -------------- next part -------------- An HTML attachment was scrubbed... URL: From e.a.hereth at gmail.com Thu Oct 9 15:57:25 2014 From: e.a.hereth at gmail.com (Ethan Hereth) Date: Thu, 9 Oct 2014 15:57:25 -0400 Subject: [Paraview] Python script running out of memory Message-ID: Hey folks, I have created the attached script by using the Trace feature in Paraview (version 4.2.0-RC1-128-gc89b0ad) and then tweaked it to run on multiple .pvtu files. I don't doubt that there is a better way to do this but this is what I came up with. I run the script using pvbatch. The problem is that it'll run for a while and then run out of memory. I also get the following errors on every pass through the script after the first pass. ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMViewLayoutProxy.cxx, line 481 vtkSMViewLayoutProxy (0x385f370): Cell identified by location '0' is already split. Cannot split the cell again. ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMViewLayoutProxy.cxx, line 551 vtkSMViewLayoutProxy (0x385f370): Cell is not empty. It seems to me that Paraview is trying to reuse the slice created in the last pass and perhaps I need to do something to reset the data or free the data or something like that. I tried a few things like Delete(fileReader) del fileReader Delete(slice1) del slice1 etc. at the end of each pass but nothing I tried eliminated the errors. Incidentally, these errors seemed to be irrelevant as the images exported just fine until the pvbatch crashed after ' throwing an instance of 'std::bad_alloc' hat(): std::bad_alloc' Does anybody mind taking a look at this and telling me what I'm doing wrong, or at least pointing me to documentation/examples that might help me to figure this out. I did read through the seemingly relevant Google search results dealing with scripting with Paraview with no luck. I appreciate your time, -- *Ethan Alan Hereth* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: process_pvtu.py Type: text/x-python Size: 11491 bytes Desc: not available URL: From cory.quammen at kitware.com Thu Oct 9 17:24:39 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Thu, 9 Oct 2014 17:24:39 -0400 Subject: [Paraview] Problem building plugin against ParaView 4.2.0 In-Reply-To: <201410080820.s988KG1j011536@msw1.awe.co.uk> References: <201410071325.s97DPBsq004082@msw1.awe.co.uk> <54341B0C.9070902@xs4all.nl> <201410080820.s988KG1j011536@msw1.awe.co.uk> Message-ID: Jim, I believe this was accidentally changed when support for Qt5 was added in commit eed7ccd3f7e804fed3864fcbe54fbd6958e63b41. In ParaView/CMake/UseParaView.cmake, can you try adding set(QT_QMAKE_EXECUTABLE ${PARAVIEW_QT_QMAKE_EXECUTABLE}) just before the lines with find_package(Qt4) and see if that works? This was the line that was removed. If that works (without qmake being in your PATH), I'll put a patch in the repository. Thanks, Cory On Wed, Oct 8, 2014 at 4:20 AM, wrote: > Hi Bertwim, > > > > This worked for me ? cmake now finds Qt and builds the plugin. Many thanks. > > > > It isn?t clear to me why it previously worked with PV 4.1.0 but not with > 4.2.0. I guess it doesn?t matter as long as it?s working J > > > > Kind regards, > > Jim > > > > ________________________________ > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of B.W.H. > van Beest > Sent: 07 October 2014 17:56 > To: paraview at paraview.org > Subject: EXTERNAL: Re: [Paraview] Problem building plugin against ParaView > 4.2.0 > > > > Jim, > > I had similar issues you describe. They were gone when I made sure that, > before actually calling cmake, the right 'qmake' was in the PATH (i.e. > 'which qmake' points to the qmake of the AQT-version your expect). This > assumes that you do have a Qt installation which is complete. > In other words: > 1. ensure qmake of the Qt distribution you expect is in your path > 2. ensure your paraview build directory is clean ( rm -rf /build/* ) > 3. start the cmake configuration. > > Hope this works for you too, > > Regards, > Bertwim > > On 10/07/2014 03:25 PM, Jim.Eliot at awe.co.uk wrote: > > > > Hello everyone, > > > > I am trying to build a file reader plugin against ParaView 4.2.0 and have > been experiencing some difficulties. Qt is not found by cmake during the > build process causing it to fail. > > > > To illustrate the issue, I created the following simplified CMakeLists.txt > file: > > > > CMAKE_MINIMUM_REQUIRED > > FIND_PACKAGE(ParaView REQUIRED) > > INCLUDE(${PARAVIEW_USE_FILE}) > > > > When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is found, > but with 4.2.0 Qt is NOT found. > > > > ParaView was built using Superbuild and Qt was built as part of that > process. Should Qt be detected from ParaViewConfig.cmake? > > > > Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow need to > specify the location of Qt manually? > > > > Any ideas? > > > > Thank you, > > Jim > > > > Jim Eliot > High Performance Computing Group > AWE, Aldermaston, Reading, RG7 4PR > > > > ___________________________________________________ > ____________________________ The information in this email and in any > attachment(s) is commercial in confidence. If you are not the named > addressee(s) or if you receive this email in error then any distribution, > copying or use of this communication or the information in it is strictly > prohibited. Please notify us immediately by email at > admin.internet(at)awe.co.uk, and then delete this message from your > computer. While attachments are virus checked, AWE plc does not accept any > liability in respect of any virus which is not detected. AWE Plc Registered > in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 > 4PR > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > ___________________________________________________ > ____________________________ The information in this email and in any > attachment(s) is commercial in confidence. If you are not the named > addressee(s) or if you receive this email in error then any distribution, > copying or use of this communication or the information in it is strictly > prohibited. Please notify us immediately by email at > admin.internet(at)awe.co.uk, and then delete this message from your > computer. While attachments are virus checked, AWE plc does not accept any > liability in respect of any virus which is not detected. AWE Plc Registered > in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 > 4PR > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From phil.amburn at gmail.com Thu Oct 9 17:58:44 2014 From: phil.amburn at gmail.com (Phil Amburn) Date: Thu, 9 Oct 2014 14:58:44 -0700 Subject: [Paraview] [EXTERNAL] displaying simulation time rather than time step In-Reply-To: References: <5435abd6.0576320a.7a74.1035@mx.google.com> <5435ce7a.2a61320a.0987.ffffd1bb@mx.google.com> Message-ID: <54370513.8217460a.73d3.436f@mx.google.com> Using David?s example and a very helpful conversation with Sean I was able to successfully use a Python track in animation and show the actual simulation time. I?m not an experienced Python user (as you?ll see in the example below), but I got some simple code to work. Below is an example of the code I ended up with in the Python animation track. def start_cue: pass def tick(self): # set up the mapping from time step to date/time information # dateTimes = [] dateTimes.append( '4/1/2013 15:00' ) dateTimes.append( '4/1/2013 15:01' ) dateTimes.append( '4/1/2013 15:02' ) dateTimes.append( '4/1/2013 15:03' ) maxIndex = len(dateTimes) index = int( self.GetClockTime() ) if index >= maxIndex : index = maxIndex - 1 textSource = paraview.simple.FindSource("TheText") textSource.Text = dateTimes[index] def end_cue(self): pass Thanks! Phil From: David E DeMarle [mailto:dave.demarle at kitware.com] Sent: Wednesday, October 08, 2014 5:53 PM To: Phil Amburn Cc: Sean.Ziegeler at engilitycorp.com; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step I think that Sean is on the right track and suggest that a Python Animation cue is the way to go. Attached is a state file to demonstrate. Load the state file in ParaView, open Views->Animation View and double click on the existing Python track to see the script that gets the pipeline time and feeds it into a text source for display. I've left the parts about reading the file and mapping the Animation time into the corresponding simulation time as an exercise to the reader. Note: many time varying file formats produce the data time for you so this translation is unnecessary and the Annotate Time filter will do what you want it to. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 8, 2014 at 7:53 PM, Phil Amburn wrote: Hi Sean, Can we talk? I?m not smart enough to understand your suggestion (hate it when that happens). If I get something worked out, even a hack, I?ll post the solution back to this list. Thanks! Phil From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Sean.Ziegeler at engilitycorp.com Sent: Wednesday, October 08, 2014 3:41 PM To: paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Hey Phil, You *might* be able to hack it with a combination of a Programmable Filter and a Python Annotation Filter. Use the Programmable Filter to add a FieldData value to each time step that is a string with the appropriate date. Then use the Python Annotation Filter to display the date as an annotation. The first part is the hard one. The Programmable Filter could either (1) read the file once to get all the dates, or (2) compute the dates using the starting date, the time step value, and Python's datetime module. Thanks, Sean _____ From: ParaView [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov] Sent: Wednesday, October 08, 2014 5:17 PM To: Phil Amburn; paraview at paraview.org Subject: Re: [Paraview] [EXTERNAL] displaying simulation time rather than time step Phil, I have no idea how to put out what you are asking for, but it is a really good idea. If you don?t get an answer, be sure to write up a bug report/ feature request. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Phil Amburn Sent: Wednesday, October 08, 2014 3:26 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] displaying simulation time rather than time step I would like to do something similar to the Annotate Time filter, but rather than displaying the time step number, I need to display simulation date and time. I have a text file with the actual simulation date and time associated with each time step. Here are the first few lines of that file Time step Time step output, Actual time 0 0.00, 4/1/2013 15:00 1 65.83, 4/1/2013 15:01 2 125.88, 4/1/2013 15:02 3 201.00, 4/1/2013 15:03 4 268.65, 4/1/2013 15:04 5 328.83, 4/1/2013 15:05 6 366.46, 4/1/2013 15:06 ? So, rather than Time: 0 at the bottom of the 3D window, I?d like to have 4/1/2013 15:00 Any thoughts / recommendations on how to accomplish this task will be greatly appreciated. Thanks, Phil _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From insley at anl.gov Thu Oct 9 19:32:11 2014 From: insley at anl.gov (Insley, Joseph A.) Date: Thu, 9 Oct 2014 23:32:11 +0000 Subject: [Paraview] XMLUnstructuredGridWriter and VTK_POLYHEDRON elements Message-ID: Hi, I have a serial vtu dataset provided by one of my users. Their current code can produce this in either ascii or inline binary. I am currently trying to convert this to appended binary (ultimately to pvtu with appended binary). I'm having trouble, which I now believe may stem from the data containing VTK_POLYHEDRON. I have a simple python script that I use with pvbatch to do this conversion, but I see the same results when I load the original data set with ParaView (4.1.0, in client/server mode), and use the Save Data option and save as vtu. I get the same results for each input format (ascii or inline binary), and output format (ascii, binary, appended). The first few lines of the original vtu file look like this: The first few lines of the converted file look like this: offset="177748206"ructuredGrid" version="0.1" byte_order="LittleEndian"> Something is clearly getting jumbled at the beginning of the converted file. If I manually edit the header of the file to read argonne leadership computing facility (630) 252-5649 argonne national laboratory -------------- next part -------------- An HTML attachment was scrubbed... URL: From Marschmann at stud.uni-heidelberg.de Fri Oct 10 05:11:24 2014 From: Marschmann at stud.uni-heidelberg.de (Marschmann at stud.uni-heidelberg.de) Date: Fri, 10 Oct 2014 11:11:24 +0200 Subject: [Paraview] Quadratic/Cubic interpolation Message-ID: <20141010111124.9xyp1eynq8o44sow@wwwmail.urz.uni-heidelberg.de> Hello all, is quadratic or cubic interpolation possible with Paraview? How can it be enabled? I am loading a VTK file. Thanks, Gianna From gregor.olenik at web.de Fri Oct 10 07:31:42 2014 From: gregor.olenik at web.de (gregor olenik) Date: Fri, 10 Oct 2014 13:31:42 +0200 Subject: [Paraview] Paraview v4.2 python bindings Message-ID: An HTML attachment was scrubbed... URL: From gregor.olenik at web.de Fri Oct 10 09:13:11 2014 From: gregor.olenik at web.de (gregor olenik) Date: Fri, 10 Oct 2014 15:13:11 +0200 Subject: [Paraview] Paraview v4.2 python bindings In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From michoski at gmail.com Fri Oct 10 11:42:30 2014 From: michoski at gmail.com (Craig Michoski) Date: Fri, 10 Oct 2014 10:42:30 -0500 Subject: [Paraview] Newbie question on python filter and integrating over a dimension Message-ID: Hi all, I have a super newbie question, I am trying to properly learn how to use the programmable python filter to integrate along dimensions of my arrays. The below seems to work, but it is extremely slow, and I'm sure the dumbest thing I can be doing. What I have is a scalar field in 2d called alpha_0, and a vector field in 2d called sigma_0_0__sigma_0_1, and I want to integrate the term: f(alpha)*g(sigma) along a single dimension of my mesh. In latex form, if my domain is (x,y) \in Omega\subset R^2, then I want to compute for every x: int_y f*g dy. The terms f and g are defined in more detail below in the script. The best solution would include the one-diemsnional output graph as well, whereas now, I just compute the values at each point and output to print. Any advice would be very appreciated. Cheers, Craig -------------------- import numpy alpha0 = inputs[0].PointData['alpha_0'] alpha1 = inputs[0].PointData['alpha_0'] sigma0 = inputs[0].PointData['sigma_0_0__sigma_0_1'] pdi = self.GetInputDataObject(0,0) bg_field = 1 pdi = self.GetInputDataObject(0,0) pdo = self.GetOutputDataObject(0) numPoints = pdi.GetNumberOfPoints() import time ind=self.GetInput() iin=ind.GetInformation() timestep = time.clock() dx = 100.0 dy = 100.0 # Find the dx and dy for integration on the uniform mesh (there must be a better way?) for (j,alpha) in enumerate(alpha0): x1,y1,z1 = pdi.GetPoint(j)[:3] x2,y2,z2 = pdi.GetPoint(j+1)[:3] if abs(x2-x1) <= dx and abs(x2-x1)>0: dx = x2 - x1 if abs(y2-y1) <= dy and abs(y2-y1)>1e-6: dy = y2 - y1 counter = 0 last_step = -1.0 prev_x = 0.0 efold = numpy.zeros(numPoints) y_first = -1.0 #integrate the term using a simple Reimann sum: int_at_each_x_coordinate_along_y # (1/exp(2*alpha))*sigma_x_component dy (this is very slow!) for (j,alpha) in enumerate(alpha0): x,y,z = pdi.GetPoint(j) if x<380.0 and x>70.0 and y==0.0: y_first = [] for (i,alpha_1) in enumerate(alpha1): x1,y1,z1 = pdi.GetPoint(i) if x1 == x and y1 == y: for (k,sigmax) in enumerate(sigma0): x2,y2,z2 = pdi.GetPoint(i) if x2 == x1: #and y2 == y1: if y2 not in y_first: efold[j] += ( 1.0/exp(2.0*alpha_1) ) * sigmax[0] * dy #exp(alpha_1)*sigmax[0]*dy y_first.append(y2) if x!=last_step: counter = counter + 1 print "y_integrated_chi_at1(",floor(timestep),",", counter,") = ", efold[j]/377.0, ";" print "x(",counter,") = ", x, ";" last_step = x From cory.quammen at kitware.com Fri Oct 10 13:20:35 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 10 Oct 2014 13:20:35 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> <5434E3A7.1030009@googlemail.com> Message-ID: Hi Philipp, I looked into this more, and it turns out it isn't a bug, but a new feature in ParaView/VTK that lets provides more flexibility in the numeric type of the point positions. By default, most filters will set the numeric type of the output points to the numeric type of their inputs. In the data set you sent me, the points are set to have type int (specified on line 7), which means that the points in the output of the Contour filter will be cast to ints. This explains the jagged appearance of your surfaces. The change in VTK that brings about this behavior is: commit f830ef4cd79b1e7c8af2fae6ed1dd02ffa2cd670 Author: Paul Edwards Date: Thu Jan 10 10:01:47 2013 -0500 Fixing loss of point-precision in certain filters. Certain filters tend to loose point precision and end up converting double point arrays to flot arrays. This patch address the issue for a few filters using the API added to vtkAlgorithm by commit 49d1f124. Change-Id: I8740e4e4bfdd9944fbadb45744038e42eff04830 Now, how to fix your problem? If you change the type of points from int to double in your data file so that it reads POINTS 6823544 double instead of POINTS 6823544 int all should work as expected. Please let me know if that doesn't solve the problem for you. Best regards, Cory On Wed, Oct 8, 2014 at 7:47 AM, Cory Quammen wrote: > Philipp, > > I apologize, but I haven't had time to look more into this problem. > I'll have another look soon. > > Thanks, > Cory > > On Wed, Oct 8, 2014 at 3:11 AM, Philipp E wrote: >> Hi Cory, >> >> can you report any updates for this issue? >> >> Best regards and thanks for your efforts >> Philipp >> >> On 09/19/2014 07:17 PM, Cory Quammen wrote: >>> Just a little more info on this. The problem starts with 3.98. >>> >>> On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: >>>> Sorry Cory, >>>> >>>> you are right. The cell number is the same. >>>> >>>> Regards >>>> Philipp >>>> >>>> >>>> Am 19.09.2014 um 17:46 schrieb Cory Quammen: >>>>> Philipp, >>>>> >>>>> I can confirm what you see with a pre 4.2 version of ParaView. >>>>> However, the number of produced cells is the same. >>>>> >>>>> I will try to track down why this changed. >>>>> >>>>> Thanks, >>>>> Cory >>>>> >>>>> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>>>>> Hi Cory >>>>>> >>>>>> I managed to compress the data set to a fair size and attached it to >>>>>> this mail. The data set is pressure, contour value is 0.55. >>>>>> >>>>>> By looking again at the data (contour -> information), I just found that >>>>>> the old version (3.14.1) uses 148432 cells , while the the new one >>>>>> employs 75232 cells. Hope that helps. >>>>>> >>>>>> Kind regards >>>>>> Philipp >>>>>> >>>>>> Errata: I meant 4.2.0RC1 in the previous mails. >>>>>> >>>>>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>>>>> Phillipp, >>>>>>> >>>>>>> Do you have a data set similar to the one you've shown that you can share? >>>>>>> >>>>>>> Thanks, >>>>>>> Cory >>>>>>> >>>>>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>>>>> Hi Cory, >>>>>>>> >>>>>>>> thank you for your fast feedback. >>>>>>>> >>>>>>>> a) Compute normal is checked. (Without normals, the contour is >>>>>>>> completely stepped) >>>>>>>> b) Contour values are the same. >>>>>>>> >>>>>>>> Regards >>>>>>>> Philipp >>>>>>>> >>>>>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>>>>> Philipp, >>>>>>>>> >>>>>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>>>>> >>>>>>>>> Also, are the contour values the same between the two versions? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Cory >>>>>>>>> >>>>>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>>>>> Hello everyone, >>>>>>>>>> >>>>>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>>>>> >>>>>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>>>>> >>>>>>>>>> 3.14.1 >>>>>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>>>>> 4.0.RC1 >>>>>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>>>>> >>>>>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>>>>> option we/setting/data problem we are not aware of. >>>>>>>>>> >>>>>>>>>> Kind regards and thanks in advance >>>>>>>>>> Philipp Engels. >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >> From bwvb at xs4all.nl Fri Oct 10 13:53:57 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 10 Oct 2014 19:53:57 +0200 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: <54344D72.8080407@xs4all.nl> References: <54344D72.8080407@xs4all.nl> Message-ID: <54381D35.1050000@xs4all.nl> Could perhaps somebody of Kitware react to this posting of a bug? I noticed a similar issue with the Example plugin "HiddenLinesRemoval", although in that case there seems to be more wrong. Regards, Bertwim On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: > Hello, > > I think there is a bug in the plugin example in > ../ParaView/Examples/Plugin/Representation (Paraview 4.2) > > As given, loading the plugin manually, and then creating a new source > (e.g. Box) causes Paraview to crash with the error message: > >> ERROR: In >> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >> line 565 >> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >> group=representations and proxy=SurfaceRepresentationBase were found. >> >> >> ERROR: In >> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >> line 989 >> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >> definition (representations, SurfaceRepresentationBase). Aborting for >> debugging purposes. >> >> >> Abort > The error seems to be in the file Representation.xml, where the attribute > base_proxyname is set to "SurfaceRepresentationBase", which should be > "SurfaceRepresentation" according to the documentation in > http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 > > When I make the change, recompile the plugin and load in into Paraview, > there is no longer the above crash when I create a new Box, and the > representation "Special Mapper" feautures in the Representationnn combobox. > >> [243] Representation> diff Representation.xml.org Representation.xml >> 7c7 >> < base_proxyname="SurfaceRepresentationBase"> >> --- >>> base_proxyname="SurfaceRepresentation"> > Kind Regards, > Bertwim > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From simon.m.su.ctr at mail.mil Fri Oct 10 14:31:13 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 10 Oct 2014 18:31:13 +0000 Subject: [Paraview] ParaView 4.2.0 client/server execution error on SGI UV System (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, We are wondering if someone can point us in the right direction to track down the issue we are getting. We managed to get ParaView OSMESA compile on our SGI UV System. But in a client/server execution mode, although we are able to connect and paraview starts up on the HPC side, as soon as we try to draw something, we get a segmentation fault error - please see error message at the bottom of this email. ParaView 4.2.0 osmesa is configure with the following options. -DCMAKE_BUILD_TYPE=Release \ -DParaView_FROM_GIT=ON \ -DENABLE_boost=ON \ -DENABLE_cgns=OFF \ -DENABLE_ffmpeg=ON \ -DENABLE_fontconfig=ON \ -DENABLE_freetype=ON \ -DENABLE_hdf5=ON \ -DENABLE_libxml2=ON \ -DENABLE_matplotlib=ON \ -DENABLE_mesa=OFF \ -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_osmesa=ON \ -DENABLE_paraview=ON \ -DENABLE_png=ON \ -DENABLE_python=ON \ -DENABLE_qhull=ON \ -DENABLE_qt=OFF \ -DENABLE_silo=ON \ -DENABLE_szip=ON \ -DENABLE_visitbridge=ON \ -DMPI_CXX_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ -DMPI_C_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi.so" \ -DMPI_LIBRARY:FILEPATH="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ -DMPI_CXX_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ -DMPI_C_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ -DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=OFF \ -DUSE_SYSTEM_zlib=OFF \ And pvserver is invoked with the following arguments mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering --server-port=1486 --client-host=${HOSTNAME} --reverse-connection --timeout=00:10:00 --connect-id=43826 Any suggestion on what/where we can start to track this segmentation fault issue down is much appreciated. Thanks -simon =========================== client/server execution error ======================== mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering --server-port=1486 --client-host=predator --reverse-connection --timeout=00:10:00 --connect-id=43826 Accepting connection(s): phineas.arl.army.mil:55816 ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPV SessionCore.cxx, line 390 vtkPVSessionCore (0x7f8f85b63810): Object type: vtkGlyph3DRepresentation, could not find requested method: "SetTriangulate" or the method was called with incorrect arguments. while processing Message 0 = Invoke Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation (0x7f8f8833fe90)} Argument 1 = string_value {SetTriangulate} Argument 2 = int32_value {0} ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPV SessionCore.cxx, line 391 vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging purposes. ############ ABORT ############# ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkSI Proxy.cxx, line 487 vtkSISourceProxy (0x7f8f8833fc10): Could not parse property: Triangulate ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVAlgo rithmPortsInformation.cxx, line 56 vtkPVAlgorithmPortsInformation (0x7f8f88367ee0): Could not downcast vtkAlgorithm. ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPV SessionCore.cxx, line 390 vtkPVSessionCore (0x7f8f85b63810): Wrapper function not found for class "(vtk object is NULL)". while processing Message 0 = Invoke Argument 0 = stream_value { Message 0 = Invoke Argument 0 = id_value {1} Argument 1 = string_value {GetVTKObject} Argument 2 = uint32_value {4525} } Argument 1 = string_value {Initialize} Argument 2 = uint32_value {4525} Argument 3 = uint32_value {4535} ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release- Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkPV SessionCore.cxx, line 391 vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging purposes. ############ ABORT ############# Segmentation fault Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From cory.quammen at kitware.com Fri Oct 10 14:47:23 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 10 Oct 2014 14:47:23 -0400 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: <54381D35.1050000@xs4all.nl> References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> Message-ID: Hi Bertwim, Thanks for reporting this bug and proposing a fix. I posted your report as a bug in the bug tracker: http://www.paraview.org/Bug/view.php?id=15044 I also pushed a git topic to gerrit with your fix and some fixes for the HiddenLinesRemoval plugin. Please feel free to review it: http://review.source.kitware.com/#/t/4837/ Thanks, Cory On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: > Could perhaps somebody of Kitware react to this posting of a bug? > I noticed a similar issue with the Example plugin "HiddenLinesRemoval", > although in that case there seems to be more wrong. > > Regards, > Bertwim > > > On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >> Hello, >> >> I think there is a bug in the plugin example in >> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >> >> As given, loading the plugin manually, and then creating a new source >> (e.g. Box) causes Paraview to crash with the error message: >> >>> ERROR: In >>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>> line 565 >>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>> group=representations and proxy=SurfaceRepresentationBase were found. >>> >>> >>> ERROR: In >>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>> line 989 >>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>> definition (representations, SurfaceRepresentationBase). Aborting for >>> debugging purposes. >>> >>> >>> Abort >> The error seems to be in the file Representation.xml, where the attribute >> base_proxyname is set to "SurfaceRepresentationBase", which should be >> "SurfaceRepresentation" according to the documentation in >> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >> >> When I make the change, recompile the plugin and load in into Paraview, >> there is no longer the above crash when I create a new Box, and the >> representation "Special Mapper" feautures in the Representationnn combobox. >> >>> [243] Representation> diff Representation.xml.org Representation.xml >>> 7c7 >>> < base_proxyname="SurfaceRepresentationBase"> >>> --- >>>> base_proxyname="SurfaceRepresentation"> >> Kind Regards, >> Bertwim >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Fri Oct 10 15:36:31 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 10 Oct 2014 21:36:31 +0200 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> Message-ID: <5438353F.9050906@xs4all.nl> Hi Cory, Thanks for putting the fix in. Though willing to contribute, I have no experience with gerrit. So I don't know what to do, really. Regards, Bertwim On 10/10/2014 08:47 PM, Cory Quammen wrote: > Hi Bertwim, > > Thanks for reporting this bug and proposing a fix. > > I posted your report as a bug in the bug tracker: > > http://www.paraview.org/Bug/view.php?id=15044 > > I also pushed a git topic to gerrit with your fix and some fixes for > the HiddenLinesRemoval plugin. Please feel free to review it: > > http://review.source.kitware.com/#/t/4837/ > > Thanks, > Cory > > On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >> Could perhaps somebody of Kitware react to this posting of a bug? >> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >> although in that case there seems to be more wrong. >> >> Regards, >> Bertwim >> >> >> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>> Hello, >>> >>> I think there is a bug in the plugin example in >>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>> >>> As given, loading the plugin manually, and then creating a new source >>> (e.g. Box) causes Paraview to crash with the error message: >>> >>>> ERROR: In >>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>> line 565 >>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>> >>>> >>>> ERROR: In >>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>> line 989 >>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>> debugging purposes. >>>> >>>> >>>> Abort >>> The error seems to be in the file Representation.xml, where the attribute >>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>> "SurfaceRepresentation" according to the documentation in >>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>> >>> When I make the change, recompile the plugin and load in into Paraview, >>> there is no longer the above crash when I create a new Box, and the >>> representation "Special Mapper" feautures in the Representationnn combobox. >>> >>>> [243] Representation> diff Representation.xml.org Representation.xml >>>> 7c7 >>>> < base_proxyname="SurfaceRepresentationBase"> >>>> --- >>>>> base_proxyname="SurfaceRepresentation"> >>> Kind Regards, >>> Bertwim >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Fri Oct 10 15:45:10 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 10 Oct 2014 21:45:10 +0200 Subject: [Paraview] BOX -> volume? Message-ID: <54383746.6010105@xs4all.nl> Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim From simon.m.su.ctr at mail.mil Fri Oct 10 16:09:53 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 10 Oct 2014 20:09:53 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to build a specific version, I will do git clone git://paraview.org/ParaViewSuperbuild.git cd ParaViewSuperbuild git checkout v4.1.0 That has always worked for me for v4.1.0 tag But with v4.2.0 release, if I do the following on different days, git clone git://paraview.org/ParaViewSuperbuild.git cd ParaViewSuperbuild git checkout v4.2.0 I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. Am I missing something? This is causing me problem when I am trying to get the same version of ParaView mesa and osmesa build for client/server mode. I end up doing a -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz To get around the problem. Thoughts? Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From biddisco at cscs.ch Fri Oct 10 18:09:42 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Fri, 10 Oct 2014 22:09:42 +0000 Subject: [Paraview] ParaView 4.2.0 client/server execution error on SGI UV System (UNCLASSIFIED) In-Reply-To: Message-ID: The client has created the representation glyph3d, but the server hasn?t got it compiled in by the looks of it, so the create representation fails. Does it get skipped when using osmesa (and hence doesn?t exist on the server)? I?m not certain of this, but it happens all the time with the same error when one of my plugins that create a representation is loaded on the client - but not on the server. JB On 10/10/14 20:31, "Su, Simon M CTR USARMY ARL (US)" wrote: >Classification: UNCLASSIFIED >Caveats: NONE > >Hello, > >We are wondering if someone can point us in the right direction to track >down the issue we are getting. We managed to get ParaView OSMESA compile >on >our SGI UV System. But in a client/server execution mode, although we are >able to connect and paraview starts up on the HPC side, as soon as we try >to >draw something, we get a segmentation fault error - please see error >message >at the bottom of this email. > >ParaView 4.2.0 osmesa is configure with the following options. > >-DCMAKE_BUILD_TYPE=Release \ >-DParaView_FROM_GIT=ON \ >-DENABLE_boost=ON \ >-DENABLE_cgns=OFF \ >-DENABLE_ffmpeg=ON \ >-DENABLE_fontconfig=ON \ >-DENABLE_freetype=ON \ >-DENABLE_hdf5=ON \ >-DENABLE_libxml2=ON \ >-DENABLE_matplotlib=ON \ >-DENABLE_mesa=OFF \ >-DENABLE_mpi=ON \ >-DENABLE_numpy=ON \ >-DENABLE_osmesa=ON \ >-DENABLE_paraview=ON \ >-DENABLE_png=ON \ >-DENABLE_python=ON \ >-DENABLE_qhull=ON \ >-DENABLE_qt=OFF \ >-DENABLE_silo=ON \ >-DENABLE_szip=ON \ >-DENABLE_visitbridge=ON \ >-DMPI_CXX_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >-DMPI_C_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi.so" \ >-DMPI_LIBRARY:FILEPATH="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >-DMPI_CXX_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >-DMPI_C_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >-DUSE_SYSTEM_mpi=ON \ >-DUSE_SYSTEM_python=OFF \ >-DUSE_SYSTEM_zlib=OFF \ > >And pvserver is invoked with the following arguments > >mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >--server-port=1486 --client-host=${HOSTNAME} --reverse-connection >--timeout=00:10:00 --connect-id=43826 > >Any suggestion on what/where we can start to track this segmentation fault >issue down is much appreciated. > >Thanks >-simon > > >=========================== client/server execution error >======================== > >mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >--server-port=1486 --client-host=predator --reverse-connection >--timeout=00:10:00 --connect-id=43826 > >Accepting connection(s): phineas.arl.army.mil:55816 >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >V >SessionCore.cxx, line 390 >vtkPVSessionCore (0x7f8f85b63810): Object type: vtkGlyph3DRepresentation, >could not find requested method: "SetTriangulate" >or the method was called with incorrect arguments. > >while processing >Message 0 = Invoke > Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation >(0x7f8f8833fe90)} > Argument 1 = string_value {SetTriangulate} > Argument 2 = int32_value {0} > > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >V >SessionCore.cxx, line 391 >vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >purposes. > > >############ ABORT ############# >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkS >I >Proxy.cxx, line 487 >vtkSISourceProxy (0x7f8f8833fc10): Could not parse property: Triangulate > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVAlg >o >rithmPortsInformation.cxx, line 56 >vtkPVAlgorithmPortsInformation (0x7f8f88367ee0): Could not downcast >vtkAlgorithm. > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >V >SessionCore.cxx, line 390 >vtkPVSessionCore (0x7f8f85b63810): Wrapper function not found for class >"(vtk object is NULL)". >while processing >Message 0 = Invoke > Argument 0 = stream_value { > Message 0 = Invoke > Argument 0 = id_value {1} > Argument 1 = string_value {GetVTKObject} > Argument 2 = uint32_value {4525} > } > Argument 1 = string_value {Initialize} > Argument 2 = uint32_value {4525} > Argument 3 = uint32_value {4535} > > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >V >SessionCore.cxx, line 391 >vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >purposes. > > >############ ABORT ############# >Segmentation fault > > > >Classification: UNCLASSIFIED >Caveats: NONE > > From cory.quammen at kitware.com Fri Oct 10 21:07:41 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Fri, 10 Oct 2014 21:07:41 -0400 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: <5438353F.9050906@xs4all.nl> References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> <5438353F.9050906@xs4all.nl> Message-ID: Hi Bertwin, No problem. It would be helpful to me, though, if you could checkout the change, try it out, and report back on the list if it works for you. To get the change, you will need to have obtained the source via git. If this is the case, go to your ParaView source directory and enter git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 git checkout FETCH_HEAD -b 15044_update_example_plugins This will download my topic branch and check it out in your local repository. Compile it again and test. Thanks, Cory On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: > Hi Cory, > > Thanks for putting the fix in. Though willing to contribute, I have no > experience with gerrit. So I don't know what to do, really. > > Regards, > Bertwim > > > On 10/10/2014 08:47 PM, Cory Quammen wrote: >> Hi Bertwim, >> >> Thanks for reporting this bug and proposing a fix. >> >> I posted your report as a bug in the bug tracker: >> >> http://www.paraview.org/Bug/view.php?id=15044 >> >> I also pushed a git topic to gerrit with your fix and some fixes for >> the HiddenLinesRemoval plugin. Please feel free to review it: >> >> http://review.source.kitware.com/#/t/4837/ >> >> Thanks, >> Cory >> >> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>> Could perhaps somebody of Kitware react to this posting of a bug? >>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>> although in that case there seems to be more wrong. >>> >>> Regards, >>> Bertwim >>> >>> >>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>> Hello, >>>> >>>> I think there is a bug in the plugin example in >>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>> >>>> As given, loading the plugin manually, and then creating a new source >>>> (e.g. Box) causes Paraview to crash with the error message: >>>> >>>>> ERROR: In >>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>> line 565 >>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>> >>>>> >>>>> ERROR: In >>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>> line 989 >>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>> debugging purposes. >>>>> >>>>> >>>>> Abort >>>> The error seems to be in the file Representation.xml, where the attribute >>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>> "SurfaceRepresentation" according to the documentation in >>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>> >>>> When I make the change, recompile the plugin and load in into Paraview, >>>> there is no longer the above crash when I create a new Box, and the >>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>> >>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>> 7c7 >>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>> --- >>>>>> base_proxyname="SurfaceRepresentation"> >>>> Kind Regards, >>>> Bertwim >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From bwvb at xs4all.nl Fri Oct 10 22:37:13 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 11 Oct 2014 04:37:13 +0200 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> <5438353F.9050906@xs4all.nl> Message-ID: <543897D9.2040102@xs4all.nl> Cory: I did as you explained. The fixes work: After 'make clean' in the examples directory and 'make all'; Tools -> Manage Plugins -> load libRepresentation.so 1. The representation plugin works correctly (After loading e.g. Box source, gives the representation "Special Mapper") Tools -> Manage Plugins -> load libHiddenLinesRemoval.so 2. The HiddenLinesRemoval plugin works correctly as well. (After loading e.g. Box source, gives the representation "Visible Wireframe", which works as expected) Regards, Bertwim On 10/11/2014 03:07 AM, Cory Quammen wrote: > Hi Bertwin, > > No problem. It would be helpful to me, though, if you could checkout > the change, try it out, and report back on the list if it works for > you. > > To get the change, you will need to have obtained the source via git. > If this is the case, go to your ParaView source directory and enter > > git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 > git checkout FETCH_HEAD -b 15044_update_example_plugins > > This will download my topic branch and check it out in your local > repository. Compile it again and test. > > Thanks, > Cory > > On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: >> Hi Cory, >> >> Thanks for putting the fix in. Though willing to contribute, I have no >> experience with gerrit. So I don't know what to do, really. >> >> Regards, >> Bertwim >> >> >> On 10/10/2014 08:47 PM, Cory Quammen wrote: >>> Hi Bertwim, >>> >>> Thanks for reporting this bug and proposing a fix. >>> >>> I posted your report as a bug in the bug tracker: >>> >>> http://www.paraview.org/Bug/view.php?id=15044 >>> >>> I also pushed a git topic to gerrit with your fix and some fixes for >>> the HiddenLinesRemoval plugin. Please feel free to review it: >>> >>> http://review.source.kitware.com/#/t/4837/ >>> >>> Thanks, >>> Cory >>> >>> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>>> Could perhaps somebody of Kitware react to this posting of a bug? >>>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>>> although in that case there seems to be more wrong. >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>>> Hello, >>>>> >>>>> I think there is a bug in the plugin example in >>>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>>> >>>>> As given, loading the plugin manually, and then creating a new source >>>>> (e.g. Box) causes Paraview to crash with the error message: >>>>> >>>>>> ERROR: In >>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>> line 565 >>>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>>> >>>>>> >>>>>> ERROR: In >>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>> line 989 >>>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>>> debugging purposes. >>>>>> >>>>>> >>>>>> Abort >>>>> The error seems to be in the file Representation.xml, where the attribute >>>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>>> "SurfaceRepresentation" according to the documentation in >>>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>>> >>>>> When I make the change, recompile the plugin and load in into Paraview, >>>>> there is no longer the above crash when I create a new Box, and the >>>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>>> >>>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>>> 7c7 >>>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>>> --- >>>>>>> base_proxyname="SurfaceRepresentation"> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview From onlyrey at gmail.com Sat Oct 11 02:33:52 2014 From: onlyrey at gmail.com (Jose Rey) Date: Sat, 11 Oct 2014 02:33:52 -0400 Subject: [Paraview] Contour volume quantification (volume fractions of a scalar in an unstructured grid) Message-ID: Good day, I would like to calculate the volume contained by each contour surface applied to an unstructured dataset. How do I do this? Here is what I have: 1. An 3D unstructured grid resulting from a CFD code (OpenFOAM) with velocities (Ux, Uy, Uz) 2. Applied the "Calculator" filter to calculate Result Array = Umagnitude from the point data with the formula (U_X^2+U_Y^2+U_Z^2)^.5 (I used point data for the calculator because I can only apply contour to point data) 3. Applied the "Contour" filter, and generated 11 volumetric contours (from 0.0 to 0.3 m/s) Here is where I am stuck (and what I intend): *. Trying to calculate the volume inside each contour surface The reason I want to calculate this: * To calculate a distribution of velocity magnitudes (where the X axis is velocity magnitude ranges /bins, and Y axis is total volume occupied by the cells in each velocity magnitude range -- not cell count as is the case of histograms) My Paraview version: * 4.2 running on Win64 (I also have aversion of paraview 4.1 modified to work with OpenFOAM, and installed in a Ubuntu64x-12.04 virtual box) Thank you very much in advance, Jose -- Jose I. Rey onlyrey at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Sat Oct 11 09:48:38 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Oct 2014 09:48:38 -0400 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: <543897D9.2040102@xs4all.nl> References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> <5438353F.9050906@xs4all.nl> <543897D9.2040102@xs4all.nl> Message-ID: Bertwin, Great, thanks for letting us know. We'll get the patch in master probably in the next week or so. By the way, if you have the time and interest in contributing patches to ParaView using our development workflow, this page provides instructions for how to do it: http://www.paraview.org/Wiki/ParaView/Git/Develop Thanks, Cory On Fri, Oct 10, 2014 at 10:37 PM, B.W.H. van Beest wrote: > Cory: > > I did as you explained. The fixes work: > After 'make clean' in the examples directory and 'make all'; > > Tools -> Manage Plugins -> load libRepresentation.so > 1. The representation plugin works correctly (After loading e.g. Box > source, gives the representation "Special Mapper") > > Tools -> Manage Plugins -> load libHiddenLinesRemoval.so > 2. The HiddenLinesRemoval plugin works correctly as well. (After loading > e.g. Box source, gives the representation "Visible Wireframe", which > works as expected) > > Regards, > Bertwim > > > On 10/11/2014 03:07 AM, Cory Quammen wrote: >> Hi Bertwin, >> >> No problem. It would be helpful to me, though, if you could checkout >> the change, try it out, and report back on the list if it works for >> you. >> >> To get the change, you will need to have obtained the source via git. >> If this is the case, go to your ParaView source directory and enter >> >> git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 >> git checkout FETCH_HEAD -b 15044_update_example_plugins >> >> This will download my topic branch and check it out in your local >> repository. Compile it again and test. >> >> Thanks, >> Cory >> >> On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: >>> Hi Cory, >>> >>> Thanks for putting the fix in. Though willing to contribute, I have no >>> experience with gerrit. So I don't know what to do, really. >>> >>> Regards, >>> Bertwim >>> >>> >>> On 10/10/2014 08:47 PM, Cory Quammen wrote: >>>> Hi Bertwim, >>>> >>>> Thanks for reporting this bug and proposing a fix. >>>> >>>> I posted your report as a bug in the bug tracker: >>>> >>>> http://www.paraview.org/Bug/view.php?id=15044 >>>> >>>> I also pushed a git topic to gerrit with your fix and some fixes for >>>> the HiddenLinesRemoval plugin. Please feel free to review it: >>>> >>>> http://review.source.kitware.com/#/t/4837/ >>>> >>>> Thanks, >>>> Cory >>>> >>>> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>>>> Could perhaps somebody of Kitware react to this posting of a bug? >>>>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>>>> although in that case there seems to be more wrong. >>>>> >>>>> Regards, >>>>> Bertwim >>>>> >>>>> >>>>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>>>> Hello, >>>>>> >>>>>> I think there is a bug in the plugin example in >>>>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>>>> >>>>>> As given, loading the plugin manually, and then creating a new source >>>>>> (e.g. Box) causes Paraview to crash with the error message: >>>>>> >>>>>>> ERROR: In >>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>> line 565 >>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>>>> >>>>>>> >>>>>>> ERROR: In >>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>> line 989 >>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>>>> debugging purposes. >>>>>>> >>>>>>> >>>>>>> Abort >>>>>> The error seems to be in the file Representation.xml, where the attribute >>>>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>>>> "SurfaceRepresentation" according to the documentation in >>>>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>>>> >>>>>> When I make the change, recompile the plugin and load in into Paraview, >>>>>> there is no longer the above crash when I create a new Box, and the >>>>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>>>> >>>>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>>>> 7c7 >>>>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>>>> --- >>>>>>>> base_proxyname="SurfaceRepresentation"> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Sat Oct 11 09:54:27 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 11 Oct 2014 15:54:27 +0200 Subject: [Paraview] Bug in Paraview 4.2 example + fix In-Reply-To: References: <54344D72.8080407@xs4all.nl> <54381D35.1050000@xs4all.nl> <5438353F.9050906@xs4all.nl> <543897D9.2040102@xs4all.nl> Message-ID: <54393693.40605@xs4all.nl> Cory, Thanks. I will seriously consider your suggestion on submitting patches. Regards, Bertwim On 10/11/2014 03:48 PM, Cory Quammen wrote: > Bertwin, > > Great, thanks for letting us know. We'll get the patch in master > probably in the next week or so. > > By the way, if you have the time and interest in contributing patches > to ParaView using our development workflow, this page provides > instructions for how to do it: > > http://www.paraview.org/Wiki/ParaView/Git/Develop > > Thanks, > Cory > > On Fri, Oct 10, 2014 at 10:37 PM, B.W.H. van Beest wrote: >> Cory: >> >> I did as you explained. The fixes work: >> After 'make clean' in the examples directory and 'make all'; >> >> Tools -> Manage Plugins -> load libRepresentation.so >> 1. The representation plugin works correctly (After loading e.g. Box >> source, gives the representation "Special Mapper") >> >> Tools -> Manage Plugins -> load libHiddenLinesRemoval.so >> 2. The HiddenLinesRemoval plugin works correctly as well. (After loading >> e.g. Box source, gives the representation "Visible Wireframe", which >> works as expected) >> >> Regards, >> Bertwim >> >> >> On 10/11/2014 03:07 AM, Cory Quammen wrote: >>> Hi Bertwin, >>> >>> No problem. It would be helpful to me, though, if you could checkout >>> the change, try it out, and report back on the list if it works for >>> you. >>> >>> To get the change, you will need to have obtained the source via git. >>> If this is the case, go to your ParaView source directory and enter >>> >>> git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 >>> git checkout FETCH_HEAD -b 15044_update_example_plugins >>> >>> This will download my topic branch and check it out in your local >>> repository. Compile it again and test. >>> >>> Thanks, >>> Cory >>> >>> On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: >>>> Hi Cory, >>>> >>>> Thanks for putting the fix in. Though willing to contribute, I have no >>>> experience with gerrit. So I don't know what to do, really. >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> On 10/10/2014 08:47 PM, Cory Quammen wrote: >>>>> Hi Bertwim, >>>>> >>>>> Thanks for reporting this bug and proposing a fix. >>>>> >>>>> I posted your report as a bug in the bug tracker: >>>>> >>>>> http://www.paraview.org/Bug/view.php?id=15044 >>>>> >>>>> I also pushed a git topic to gerrit with your fix and some fixes for >>>>> the HiddenLinesRemoval plugin. Please feel free to review it: >>>>> >>>>> http://review.source.kitware.com/#/t/4837/ >>>>> >>>>> Thanks, >>>>> Cory >>>>> >>>>> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>>>>> Could perhaps somebody of Kitware react to this posting of a bug? >>>>>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>>>>> although in that case there seems to be more wrong. >>>>>> >>>>>> Regards, >>>>>> Bertwim >>>>>> >>>>>> >>>>>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>>>>> Hello, >>>>>>> >>>>>>> I think there is a bug in the plugin example in >>>>>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>>>>> >>>>>>> As given, loading the plugin manually, and then creating a new source >>>>>>> (e.g. Box) causes Paraview to crash with the error message: >>>>>>> >>>>>>>> ERROR: In >>>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>>> line 565 >>>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>>>>> >>>>>>>> >>>>>>>> ERROR: In >>>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>>> line 989 >>>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>>>>> debugging purposes. >>>>>>>> >>>>>>>> >>>>>>>> Abort >>>>>>> The error seems to be in the file Representation.xml, where the attribute >>>>>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>>>>> "SurfaceRepresentation" according to the documentation in >>>>>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>>>>> >>>>>>> When I make the change, recompile the plugin and load in into Paraview, >>>>>>> there is no longer the above crash when I create a new Box, and the >>>>>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>>>>> >>>>>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>>>>> 7c7 >>>>>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>>>>> --- >>>>>>>>> base_proxyname="SurfaceRepresentation"> >>>>>>> Kind Regards, >>>>>>> Bertwim >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Sat Oct 11 10:23:30 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 11 Oct 2014 16:23:30 +0200 Subject: [Paraview] sources: why redundant number of points needed? Message-ID: <54393D62.30905@xs4all.nl> Hi, When I look into the source code of vtkCubeSource.cpp, I noticed that, although a (rectangular) 3D box can be described by 8 3D points and 6 2D faces (hence also 6 3D normal vectors), in the actual code of vtkCubeBoxSource:RequestData() there are 24 3D points generated, with for every point a normal (???), and indeed 6 faces (polys). Why is there this redundancy? I bumped on this when I applied the "HiddenLineRemoval" representation to my own handcrafted box (with 8 points, 6 faces and 6 normals). It yielded an incorrect view whereas the box with the redundant numbers of data gave the correct one. But I don't get the logic. Regards, Bertwim From cory.quammen at kitware.com Sat Oct 11 10:48:47 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Oct 2014 10:48:47 -0400 Subject: [Paraview] sources: why redundant number of points needed? In-Reply-To: <54393D62.30905@xs4all.nl> References: <54393D62.30905@xs4all.nl> Message-ID: Bertwim, You are right that there is a redundancy in points. That stems from the need for defining different normals at the corner points for each face. In theory, you could define more than one normal for the same point and associate it with a face, but that complicates the data structure. It is much simpler to duplicate points and associate exactly one normal per point. In most polygonal data, you won't see duplicated points at most places. But for anything that should be displayed with a sharp edge, duplicate points will be present. - Cory On Sat, Oct 11, 2014 at 10:23 AM, B.W.H. van Beest wrote: > Hi, > > When I look into the source code of vtkCubeSource.cpp, > I noticed that, although a (rectangular) 3D box can be described by > 8 3D points and 6 2D faces (hence also 6 3D normal vectors), > in the actual code of vtkCubeBoxSource:RequestData() there are 24 3D > points generated, > with for every point a normal (???), and indeed 6 faces (polys). > Why is there this redundancy? > > I bumped on this when I applied the "HiddenLineRemoval" representation to > my own handcrafted box (with 8 points, 6 faces and 6 normals). It yielded > an incorrect view whereas the box with the redundant numbers of data > gave the correct one. But I don't get the logic. > > Regards, > Bertwim > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Sat Oct 11 11:13:49 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 11 Oct 2014 17:13:49 +0200 Subject: [Paraview] sources: why redundant number of points needed? In-Reply-To: References: <54393D62.30905@xs4all.nl> Message-ID: <5439492D.5080704@xs4all.nl> Cory, So indeed there has to be a normal *per point and per face*, and not *per face*? And, likewise, points are not shared between adjacent faces. I had overlooked that detail in the documentation, tacitly assuming that "of course" the normals are *per face*. Regards, Bertwim On 10/11/2014 04:48 PM, Cory Quammen wrote: > Bertwim, > > You are right that there is a redundancy in points. That stems from > the need for defining different normals at the corner points for each > face. In theory, you could define more than one normal for the same > point and associate it with a face, but that complicates the data > structure. It is much simpler to duplicate points and associate > exactly one normal per point. > > In most polygonal data, you won't see duplicated points at most > places. But for anything that should be displayed with a sharp edge, > duplicate points will be present. > > - Cory > > On Sat, Oct 11, 2014 at 10:23 AM, B.W.H. van Beest wrote: >> Hi, >> >> When I look into the source code of vtkCubeSource.cpp, >> I noticed that, although a (rectangular) 3D box can be described by >> 8 3D points and 6 2D faces (hence also 6 3D normal vectors), >> in the actual code of vtkCubeBoxSource:RequestData() there are 24 3D >> points generated, >> with for every point a normal (???), and indeed 6 faces (polys). >> Why is there this redundancy? >> >> I bumped on this when I applied the "HiddenLineRemoval" representation to >> my own handcrafted box (with 8 points, 6 faces and 6 normals). It yielded >> an incorrect view whereas the box with the redundant numbers of data >> gave the correct one. But I don't get the logic. >> >> Regards, >> Bertwim >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Sat Oct 11 11:34:28 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Oct 2014 11:34:28 -0400 Subject: [Paraview] sources: why redundant number of points needed? In-Reply-To: <5439492D.5080704@xs4all.nl> References: <54393D62.30905@xs4all.nl> <5439492D.5080704@xs4all.nl> Message-ID: Bertwim, In fact, with Gouraud shading enabled (the default in ParaView when point normals are available), normals are defined only per point - no face normal is needed. If you change the Interpolation to Flat under the "Lighting" section in the Properties panel, only the face normal will be computed and used for lighting, but objects with smooth surfaces, such as spheres, won't be rendered very nicely - edges between adjacent faces will be sharp. For a general overview of Gouraud shading and some background on what is needed for getting sharp edges, please see http://msdn.microsoft.com/en-us/library/windows/desktop/bb324491(v=vs.85).aspx It is geared towards Direct3D, but the same concepts apply to OpenGL and in turn VTK and ParaView. Cory On Sat, Oct 11, 2014 at 11:13 AM, B.W.H. van Beest wrote: > Cory, > > So indeed there has to be a normal *per point and per face*, and not > *per face*? > And, likewise, points are not shared between adjacent faces. > I had overlooked that detail in the documentation, tacitly assuming that > "of course" > the normals are *per face*. > > Regards, > Bertwim > > On 10/11/2014 04:48 PM, Cory Quammen wrote: >> Bertwim, >> >> You are right that there is a redundancy in points. That stems from >> the need for defining different normals at the corner points for each >> face. In theory, you could define more than one normal for the same >> point and associate it with a face, but that complicates the data >> structure. It is much simpler to duplicate points and associate >> exactly one normal per point. >> >> In most polygonal data, you won't see duplicated points at most >> places. But for anything that should be displayed with a sharp edge, >> duplicate points will be present. >> >> - Cory >> >> On Sat, Oct 11, 2014 at 10:23 AM, B.W.H. van Beest wrote: >>> Hi, >>> >>> When I look into the source code of vtkCubeSource.cpp, >>> I noticed that, although a (rectangular) 3D box can be described by >>> 8 3D points and 6 2D faces (hence also 6 3D normal vectors), >>> in the actual code of vtkCubeBoxSource:RequestData() there are 24 3D >>> points generated, >>> with for every point a normal (???), and indeed 6 faces (polys). >>> Why is there this redundancy? >>> >>> I bumped on this when I applied the "HiddenLineRemoval" representation to >>> my own handcrafted box (with 8 points, 6 faces and 6 normals). It yielded >>> an incorrect view whereas the box with the redundant numbers of data >>> gave the correct one. But I don't get the logic. >>> >>> Regards, >>> Bertwim >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > From bwvb at xs4all.nl Sat Oct 11 13:00:05 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 11 Oct 2014 19:00:05 +0200 Subject: [Paraview] sources: why redundant number of points needed? In-Reply-To: References: <54393D62.30905@xs4all.nl> <5439492D.5080704@xs4all.nl> Message-ID: <54396215.80703@xs4all.nl> Got it. Thanks for the ref. Bw On 10/11/2014 05:34 PM, Cory Quammen wrote: > Bertwim, > > In fact, with Gouraud shading enabled (the default in ParaView when > point normals are available), normals are defined only per point - no > face normal is needed. If you change the Interpolation to Flat under > the "Lighting" section in the Properties panel, only the face normal > will be computed and used for lighting, but objects with smooth > surfaces, such as spheres, won't be rendered very nicely - edges > between adjacent faces will be sharp. > > For a general overview of Gouraud shading and some background on what > is needed for getting sharp edges, please see > > http://msdn.microsoft.com/en-us/library/windows/desktop/bb324491(v=vs.85).aspx > > It is geared towards Direct3D, but the same concepts apply to OpenGL > and in turn VTK and ParaView. > > Cory > > > On Sat, Oct 11, 2014 at 11:13 AM, B.W.H. van Beest wrote: >> Cory, >> >> So indeed there has to be a normal *per point and per face*, and not >> *per face*? >> And, likewise, points are not shared between adjacent faces. >> I had overlooked that detail in the documentation, tacitly assuming that >> "of course" >> the normals are *per face*. >> >> Regards, >> Bertwim >> >> On 10/11/2014 04:48 PM, Cory Quammen wrote: >>> Bertwim, >>> >>> You are right that there is a redundancy in points. That stems from >>> the need for defining different normals at the corner points for each >>> face. In theory, you could define more than one normal for the same >>> point and associate it with a face, but that complicates the data >>> structure. It is much simpler to duplicate points and associate >>> exactly one normal per point. >>> >>> In most polygonal data, you won't see duplicated points at most >>> places. But for anything that should be displayed with a sharp edge, >>> duplicate points will be present. >>> >>> - Cory >>> >>> On Sat, Oct 11, 2014 at 10:23 AM, B.W.H. van Beest wrote: >>>> Hi, >>>> >>>> When I look into the source code of vtkCubeSource.cpp, >>>> I noticed that, although a (rectangular) 3D box can be described by >>>> 8 3D points and 6 2D faces (hence also 6 3D normal vectors), >>>> in the actual code of vtkCubeBoxSource:RequestData() there are 24 3D >>>> points generated, >>>> with for every point a normal (???), and indeed 6 faces (polys). >>>> Why is there this redundancy? >>>> >>>> I bumped on this when I applied the "HiddenLineRemoval" representation to >>>> my own handcrafted box (with 8 points, 6 faces and 6 normals). It yielded >>>> an incorrect view whereas the box with the redundant numbers of data >>>> gave the correct one. But I don't get the logic. >>>> >>>> Regards, >>>> Bertwim >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview > From cory.quammen at kitware.com Sat Oct 11 18:04:17 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Sat, 11 Oct 2014 18:04:17 -0400 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Hi Simon, What you are doing as a workaround is indeed how production builds should be created. The ParaView superbuild is now set up to check out the master branch of ParaView, which varies day to day. In 4.1 and prior to that, it was set up to check out out the release branch, which was far more static. If you disable ParaView_FROM_GIT in CMake, it will download the release source tar ball and build from that, essentially what you have been doing. I'll update the superbuild wiki instructions to note this. Best regards, Cory On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to > build a specific version, I will do > > git clone git://paraview.org/ParaViewSuperbuild.git > cd ParaViewSuperbuild > git checkout v4.1.0 > > That has always worked for me for v4.1.0 tag > > But with v4.2.0 release, if I do the following on different days, > > git clone git://paraview.org/ParaViewSuperbuild.git > cd ParaViewSuperbuild > git checkout v4.2.0 > > I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. Am I > missing something? This is causing me problem when I am trying to get the > same version of ParaView mesa and osmesa build for client/server mode. I end > up doing a > > -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz > > To get around the problem. Thoughts? > > > Thanks > -simon > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From praveenn at nvidia.com Sat Oct 11 22:30:30 2014 From: praveenn at nvidia.com (Praveen Narayanan) Date: Sat, 11 Oct 2014 19:30:30 -0700 Subject: [Paraview] ParaView 4.2.0 client/server execution error In-Reply-To: References: Message-ID: <5439E7C6.8080101@nvidia.com> I haven't worked on client-server mode, but building Paraview with OSMesa was a very challenging exercise, and I used it for my workstation. Not sure if these notes would help here. Nevertheless, it may be pertinent for installation notes. 1) Build OSMesa (obtained from the paraview wiki, and this is for vanilla OsMesa). $ ./configure CXXFLAGS=-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31 CFLAGS=-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31 --disable-xvmc --disable-glx --disable-dri --with-dri-drivers= --with-gallium-drivers= --enable-texture-float --disable-shared-glapi --disable-egl --with-egl-platforms= --enable-osmesa --enable-gallium-llvm=no --prefix=/home/praveen/software/osmesa_vanilla_install 2) Use ccmake+superbuild to build paraview, configuring repeatedly. I had managed several paraview builds with my system mpi (from ubuntu) but somehow, on that particular day, cmake rejected all of them, and hence the superbuild install asking it to download mpi and build. 3) For some reason, it would default to using 2 MPI tasks, which we should change in the ncurses menu. Likewise, the max number of threads is specified as 64. I am not sure what this would imply. 4) I think it is enough to turn on the OPENGL_HAS_OSMESA flag for it to use OsMesa. 5) Next, we specify the path for the OsMesa installation (we can point to any of the OsMesa builds, such as Gallium or Nouveau). If I recall correctly, ccmake complains if we turn on the GUI. I wonder if these failures have something to do with the flavor of OsMesa used. On 10/10/2014 07:37 PM, paraview-request at paraview.org wrote: > > Message: 2 > Date: Fri, 10 Oct 2014 22:09:42 +0000 > From: "Biddiscombe, John A." > To: "Su, Simon M CTR USARMY ARL (US)" , > "paraview at paraview.org" > Subject: Re: [Paraview] ParaView 4.2.0 client/server execution error > on SGI UV System (UNCLASSIFIED) > Message-ID: > Content-Type: text/plain; charset="utf-8" > > The client has created the representation glyph3d, but the server hasn?t > got it compiled in by the looks of it, so the create representation fails. > Does it get skipped when using osmesa (and hence doesn?t exist on the > server)? > > I?m not certain of this, but it happens all the time with the same error > when one of my plugins that create a representation is loaded on the > client - but not on the server. > > JB > > On 10/10/14 20:31, "Su, Simon M CTR USARMY ARL (US)" > wrote: > >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> We are wondering if someone can point us in the right direction to track >> down the issue we are getting. We managed to get ParaView OSMESA compile >> on >> our SGI UV System. But in a client/server execution mode, although we are >> able to connect and paraview starts up on the HPC side, as soon as we try >> to >> draw something, we get a segmentation fault error - please see error >> message >> at the bottom of this email. >> >> ParaView 4.2.0 osmesa is configure with the following options. >> >> -DCMAKE_BUILD_TYPE=Release \ >> -DParaView_FROM_GIT=ON \ >> -DENABLE_boost=ON \ >> -DENABLE_cgns=OFF \ >> -DENABLE_ffmpeg=ON \ >> -DENABLE_fontconfig=ON \ >> -DENABLE_freetype=ON \ >> -DENABLE_hdf5=ON \ >> -DENABLE_libxml2=ON \ >> -DENABLE_matplotlib=ON \ >> -DENABLE_mesa=OFF \ >> -DENABLE_mpi=ON \ >> -DENABLE_numpy=ON \ >> -DENABLE_osmesa=ON \ >> -DENABLE_paraview=ON \ >> -DENABLE_png=ON \ >> -DENABLE_python=ON \ >> -DENABLE_qhull=ON \ >> -DENABLE_qt=OFF \ >> -DENABLE_silo=ON \ >> -DENABLE_szip=ON \ >> -DENABLE_visitbridge=ON \ >> -DMPI_CXX_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >> -DMPI_C_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi.so" \ >> -DMPI_LIBRARY:FILEPATH="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >> -DMPI_CXX_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >> -DMPI_C_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >> -DUSE_SYSTEM_mpi=ON \ >> -DUSE_SYSTEM_python=OFF \ >> -DUSE_SYSTEM_zlib=OFF \ >> >> And pvserver is invoked with the following arguments >> >> mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >> --server-port=1486 --client-host=${HOSTNAME} --reverse-connection >> --timeout=00:10:00 --connect-id=43826 >> >> Any suggestion on what/where we can start to track this segmentation fault >> issue down is much appreciated. >> >> Thanks >> -simon >> >> >> =========================== client/server execution error >> ======================== >> >> mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >> --server-port=1486 --client-host=predator --reverse-connection >> --timeout=00:10:00 --connect-id=43826 >> >> Accepting connection(s): phineas.arl.army.mil:55816 >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >> V >> SessionCore.cxx, line 390 >> vtkPVSessionCore (0x7f8f85b63810): Object type: vtkGlyph3DRepresentation, >> could not find requested method: "SetTriangulate" >> or the method was called with incorrect arguments. >> >> while processing >> Message 0 = Invoke >> Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation >> (0x7f8f8833fe90)} >> Argument 1 = string_value {SetTriangulate} >> Argument 2 = int32_value {0} >> >> >> >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >> V >> SessionCore.cxx, line 391 >> vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >> purposes. >> >> >> ############ ABORT ############# >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkS >> I >> Proxy.cxx, line 487 >> vtkSISourceProxy (0x7f8f8833fc10): Could not parse property: Triangulate >> >> >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPVAlg >> o >> rithmPortsInformation.cxx, line 56 >> vtkPVAlgorithmPortsInformation (0x7f8f88367ee0): Could not downcast >> vtkAlgorithm. >> >> >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >> V >> SessionCore.cxx, line 390 >> vtkPVSessionCore (0x7f8f85b63810): Wrapper function not found for class >> "(vtk object is NULL)". >> while processing >> Message 0 = Invoke >> Argument 0 = stream_value { >> Message 0 = Invoke >> Argument 0 = id_value {1} >> Argument 1 = string_value {GetVTKObject} >> Argument 2 = uint32_value {4525} >> } >> Argument 1 = string_value {Initialize} >> Argument 2 = uint32_value {4525} >> Argument 3 = uint32_value {4535} >> >> >> >> ERROR: In >> /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release >> - >> Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/vtkP >> V >> SessionCore.cxx, line 391 >> vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >> purposes. >> >> >> ############ ABORT ############# >> Segmentation fault >> >> >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> > > ------------------------------ > > Message: 3 > Date: Fri, 10 Oct 2014 21:07:41 -0400 > From: Cory Quammen > To: "B.W.H. van Beest" > Cc: ParaView > Subject: Re: [Paraview] Bug in Paraview 4.2 example + fix > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Hi Bertwin, > > No problem. It would be helpful to me, though, if you could checkout > the change, try it out, and report back on the list if it works for > you. > > To get the change, you will need to have obtained the source via git. > If this is the case, go to your ParaView source directory and enter > > git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 > git checkout FETCH_HEAD -b 15044_update_example_plugins > > This will download my topic branch and check it out in your local > repository. Compile it again and test. > > Thanks, > Cory > > On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: >> Hi Cory, >> >> Thanks for putting the fix in. Though willing to contribute, I have no >> experience with gerrit. So I don't know what to do, really. >> >> Regards, >> Bertwim >> >> >> On 10/10/2014 08:47 PM, Cory Quammen wrote: >>> Hi Bertwim, >>> >>> Thanks for reporting this bug and proposing a fix. >>> >>> I posted your report as a bug in the bug tracker: >>> >>> http://www.paraview.org/Bug/view.php?id=15044 >>> >>> I also pushed a git topic to gerrit with your fix and some fixes for >>> the HiddenLinesRemoval plugin. Please feel free to review it: >>> >>> http://review.source.kitware.com/#/t/4837/ >>> >>> Thanks, >>> Cory >>> >>> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>>> Could perhaps somebody of Kitware react to this posting of a bug? >>>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>>> although in that case there seems to be more wrong. >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>>> Hello, >>>>> >>>>> I think there is a bug in the plugin example in >>>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>>> >>>>> As given, loading the plugin manually, and then creating a new source >>>>> (e.g. Box) causes Paraview to crash with the error message: >>>>> >>>>>> ERROR: In >>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>> line 565 >>>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>>> >>>>>> >>>>>> ERROR: In >>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>> line 989 >>>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>>> debugging purposes. >>>>>> >>>>>> >>>>>> Abort >>>>> The error seems to be in the file Representation.xml, where the attribute >>>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>>> "SurfaceRepresentation" according to the documentation in >>>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>>> >>>>> When I make the change, recompile the plugin and load in into Paraview, >>>>> there is no longer the above crash when I create a new Box, and the >>>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>>> >>>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>>> 7c7 >>>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>>> --- >>>>>>> base_proxyname="SurfaceRepresentation"> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview > > ------------------------------ > > Message: 4 > Date: Sat, 11 Oct 2014 04:37:13 +0200 > From: "B.W.H. van Beest" > To: Cory Quammen > Cc: ParaView > Subject: Re: [Paraview] Bug in Paraview 4.2 example + fix > Message-ID: <543897D9.2040102 at xs4all.nl> > Content-Type: text/plain; charset=utf-8 > > Cory: > > I did as you explained. The fixes work: > After 'make clean' in the examples directory and 'make all'; > > Tools -> Manage Plugins -> load libRepresentation.so > 1. The representation plugin works correctly (After loading e.g. Box > source, gives the representation "Special Mapper") > > Tools -> Manage Plugins -> load libHiddenLinesRemoval.so > 2. The HiddenLinesRemoval plugin works correctly as well. (After loading > e.g. Box source, gives the representation "Visible Wireframe", which > works as expected) > > Regards, > Bertwim > > > On 10/11/2014 03:07 AM, Cory Quammen wrote: >> Hi Bertwin, >> >> No problem. It would be helpful to me, though, if you could checkout >> the change, try it out, and report back on the list if it works for >> you. >> >> To get the change, you will need to have obtained the source via git. >> If this is the case, go to your ParaView source directory and enter >> >> git fetch http://review.source.kitware.com/p/ParaView refs/topics/37/4837/1 >> git checkout FETCH_HEAD -b 15044_update_example_plugins >> >> This will download my topic branch and check it out in your local >> repository. Compile it again and test. >> >> Thanks, >> Cory >> >> On Fri, Oct 10, 2014 at 3:36 PM, B.W.H. van Beest wrote: >>> Hi Cory, >>> >>> Thanks for putting the fix in. Though willing to contribute, I have no >>> experience with gerrit. So I don't know what to do, really. >>> >>> Regards, >>> Bertwim >>> >>> >>> On 10/10/2014 08:47 PM, Cory Quammen wrote: >>>> Hi Bertwim, >>>> >>>> Thanks for reporting this bug and proposing a fix. >>>> >>>> I posted your report as a bug in the bug tracker: >>>> >>>> http://www.paraview.org/Bug/view.php?id=15044 >>>> >>>> I also pushed a git topic to gerrit with your fix and some fixes for >>>> the HiddenLinesRemoval plugin. Please feel free to review it: >>>> >>>> http://review.source.kitware.com/#/t/4837/ >>>> >>>> Thanks, >>>> Cory >>>> >>>> On Fri, Oct 10, 2014 at 1:53 PM, B.W.H. van Beest wrote: >>>>> Could perhaps somebody of Kitware react to this posting of a bug? >>>>> I noticed a similar issue with the Example plugin "HiddenLinesRemoval", >>>>> although in that case there seems to be more wrong. >>>>> >>>>> Regards, >>>>> Bertwim >>>>> >>>>> >>>>> On 10/07/2014 10:30 PM, B.W.H. van Beest wrote: >>>>>> Hello, >>>>>> >>>>>> I think there is a bug in the plugin example in >>>>>> ../ParaView/Examples/Plugin/Representation (Paraview 4.2) >>>>>> >>>>>> As given, loading the plugin manually, and then creating a new source >>>>>> (e.g. Box) causes Paraview to crash with the error message: >>>>>> >>>>>>> ERROR: In >>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>> line 565 >>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches: >>>>>>> group=representations and proxy=SurfaceRepresentationBase were found. >>>>>>> >>>>>>> >>>>>>> ERROR: In >>>>>>> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx, >>>>>>> line 989 >>>>>>> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy >>>>>>> definition (representations, SurfaceRepresentationBase). Aborting for >>>>>>> debugging purposes. >>>>>>> >>>>>>> >>>>>>> Abort >>>>>> The error seems to be in the file Representation.xml, where the attribute >>>>>> base_proxyname is set to "SurfaceRepresentationBase", which should be >>>>>> "SurfaceRepresentation" according to the documentation in >>>>>> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7 >>>>>> >>>>>> When I make the change, recompile the plugin and load in into Paraview, >>>>>> there is no longer the above crash when I create a new Box, and the >>>>>> representation "Special Mapper" feautures in the Representationnn combobox. >>>>>> >>>>>>> [243] Representation> diff Representation.xml.org Representation.xml >>>>>>> 7c7 >>>>>>> < base_proxyname="SurfaceRepresentationBase"> >>>>>>> --- >>>>>>>> base_proxyname="SurfaceRepresentation"> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > ------------------------------ > > End of ParaView Digest, Vol 126, Issue 37 > ***************************************** ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- From jan.brezina at tul.cz Sun Oct 12 14:00:33 2014 From: jan.brezina at tul.cz (Jan Brezina) Date: Sun, 12 Oct 2014 20:00:33 +0200 Subject: [Paraview] Using PythonProgrammableFilter as a reader Message-ID: <543AC1C1.9060309@tul.cz> Hi, I'm trying to use vtkPythonProgrammableFilter to implement a reader in Python. The problem is in passing the filename (form the filebrowser dialog) to the python script (the RequestData script). I need a method in vtkPythonProgrammableFilter with one char * argument that can behave like SetFileName(char *) to set this method to command property in the XML file. Unfortunately, this scheme is not compatible with SetParameter methods of vtkPythonProgrammableFilter. Finally, I find a hack using the method SetProgressText (from vtkAlgorithm) instead of SetFileName. So my XML looks like: Is there a beter way how to pass the filename to the script? If not, could a SetFileName method be implemented in vtkPythonProgrammableFilter that simply calls SetParameter("FileName", the_path) ? Thank you for a help, Jan -- ------------------------ Mgr. Jan Brezina, Ph. D. Technical University in Liberec, New technologies institute http://www.nti.tul.cz/cz/WikiUser:Jan.Brezina -- ------------------------ Mgr. Jan Brezina, Ph. D. Technical University in Liberec, New technologies institute http://www.nti.tul.cz/cz/WikiUser:Jan.Brezina From utkarsh.ayachit at kitware.com Sun Oct 12 17:02:05 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 12 Oct 2014 17:02:05 -0400 Subject: [Paraview] Using PythonProgrammableFilter as a reader In-Reply-To: <543AC1C1.9060309@tul.cz> References: <543AC1C1.9060309@tul.cz> Message-ID: I am not sure I follow why SetParameter won't work in your case. Something like following is what I often end up using for such cases. On Sun, Oct 12, 2014 at 2:00 PM, Jan Brezina wrote: > Hi, > > I'm trying to use vtkPythonProgrammableFilter to implement a reader in > Python. The problem is in passing the filename (form the filebrowser > dialog) to the python script (the RequestData script). I need a method > in vtkPythonProgrammableFilter with one char * argument that can behave > like SetFileName(char *) to set this method to command property in the > XML file. Unfortunately, this scheme is not compatible with SetParameter > methods of vtkPythonProgrammableFilter. Finally, I find a hack using the > method SetProgressText (from vtkAlgorithm) instead of SetFileName. So my > XML looks like: > > > > class="vtkPythonProgrammableFilter" > label="EGrid Reader"> > name="FileName" > animateable="0" > command="SetProgressText" > number_of_elements="1" > panel_visibility="advanced"> > > > default_values="4" > name="OutputDataSetType" > number_of_elements="1" > panel_visibility="never"> > > name="Script" > command="SetScript" > number_of_elements="1" > default_values="print self.GetProgressText()" > panel_visibility="advanced"> > > > > > > file_description="Eclipse mesh File Format" /> > > > > > > Is there a beter way how to pass the filename to the script? If not, > could a SetFileName method be implemented in vtkPythonProgrammableFilter > that simply calls > > SetParameter("FileName", the_path) > > ? > > Thank you for a help, > Jan > > -- > ------------------------ > Mgr. Jan Brezina, Ph. D. > Technical University in Liberec, New technologies institute > http://www.nti.tul.cz/cz/WikiUser:Jan.Brezina > > -- > ------------------------ > Mgr. Jan Brezina, Ph. D. > Technical University in Liberec, New technologies institute > http://www.nti.tul.cz/cz/WikiUser:Jan.Brezina > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From pspeachum at gmail.com Mon Oct 13 03:17:12 2014 From: pspeachum at gmail.com (Philipp E) Date: Mon, 13 Oct 2014 09:17:12 +0200 Subject: [Paraview] 3D contour smoothness In-Reply-To: References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> <5434E3A7.1030009@googlemail.com> Message-ID: <543B7C78.4040704@googlemail.com> Hi Cory, you are correct. This tiny change solves the problem! I hope that our discussion will also allow others to review their output code with respect to this change. Thank you very much for clarification and your help (and your great software as well). Best regards Philipp Engels On 10/10/2014 07:20 PM, Cory Quammen wrote: > Hi Philipp, > > I looked into this more, and it turns out it isn't a bug, but a new > feature in ParaView/VTK that lets provides more flexibility in the > numeric type of the point positions. By default, most filters will set > the numeric type of the output points to the numeric type of their > inputs. In the data set you sent me, the points are set to have type > int (specified on line 7), which means that the points in the output > of the Contour filter will be cast to ints. This explains the jagged > appearance of your surfaces. > > The change in VTK that brings about this behavior is: > > commit f830ef4cd79b1e7c8af2fae6ed1dd02ffa2cd670 > Author: Paul Edwards > Date: Thu Jan 10 10:01:47 2013 -0500 > > Fixing loss of point-precision in certain filters. > > Certain filters tend to loose point precision and end up > converting double point > arrays to flot arrays. This patch address the issue for a few > filters using the > API added to vtkAlgorithm by commit 49d1f124. > > Change-Id: I8740e4e4bfdd9944fbadb45744038e42eff04830 > > Now, how to fix your problem? If you change the type of points from > int to double in your data file so that it reads > > POINTS 6823544 double > > instead of > > POINTS 6823544 int > > all should work as expected. > > Please let me know if that doesn't solve the problem for you. > > Best regards, > Cory > > On Wed, Oct 8, 2014 at 7:47 AM, Cory Quammen wrote: >> Philipp, >> >> I apologize, but I haven't had time to look more into this problem. >> I'll have another look soon. >> >> Thanks, >> Cory >> >> On Wed, Oct 8, 2014 at 3:11 AM, Philipp E wrote: >>> Hi Cory, >>> >>> can you report any updates for this issue? >>> >>> Best regards and thanks for your efforts >>> Philipp >>> >>> On 09/19/2014 07:17 PM, Cory Quammen wrote: >>>> Just a little more info on this. The problem starts with 3.98. >>>> >>>> On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: >>>>> Sorry Cory, >>>>> >>>>> you are right. The cell number is the same. >>>>> >>>>> Regards >>>>> Philipp >>>>> >>>>> >>>>> Am 19.09.2014 um 17:46 schrieb Cory Quammen: >>>>>> Philipp, >>>>>> >>>>>> I can confirm what you see with a pre 4.2 version of ParaView. >>>>>> However, the number of produced cells is the same. >>>>>> >>>>>> I will try to track down why this changed. >>>>>> >>>>>> Thanks, >>>>>> Cory >>>>>> >>>>>> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>>>>>> Hi Cory >>>>>>> >>>>>>> I managed to compress the data set to a fair size and attached it to >>>>>>> this mail. The data set is pressure, contour value is 0.55. >>>>>>> >>>>>>> By looking again at the data (contour -> information), I just found that >>>>>>> the old version (3.14.1) uses 148432 cells , while the the new one >>>>>>> employs 75232 cells. Hope that helps. >>>>>>> >>>>>>> Kind regards >>>>>>> Philipp >>>>>>> >>>>>>> Errata: I meant 4.2.0RC1 in the previous mails. >>>>>>> >>>>>>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>>>>>> Phillipp, >>>>>>>> >>>>>>>> Do you have a data set similar to the one you've shown that you can share? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Cory >>>>>>>> >>>>>>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>>>>>> Hi Cory, >>>>>>>>> >>>>>>>>> thank you for your fast feedback. >>>>>>>>> >>>>>>>>> a) Compute normal is checked. (Without normals, the contour is >>>>>>>>> completely stepped) >>>>>>>>> b) Contour values are the same. >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> Philipp >>>>>>>>> >>>>>>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>>>>>> Philipp, >>>>>>>>>> >>>>>>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>>>>>> >>>>>>>>>> Also, are the contour values the same between the two versions? >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Cory >>>>>>>>>> >>>>>>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>>>>>> Hello everyone, >>>>>>>>>>> >>>>>>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>>>>>> >>>>>>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>>>>>> >>>>>>>>>>> 3.14.1 >>>>>>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>>>>>> 4.0.RC1 >>>>>>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>>>>>> >>>>>>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>>>>>> option we/setting/data problem we are not aware of. >>>>>>>>>>> >>>>>>>>>>> Kind regards and thanks in advance >>>>>>>>>>> Philipp Engels. >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>> >>>>>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>>>>>> >>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>>>>> >>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview From cory.quammen at kitware.com Mon Oct 13 07:51:26 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Oct 2014 07:51:26 -0400 Subject: [Paraview] 3D contour smoothness In-Reply-To: <543B7C78.4040704@googlemail.com> References: <541C3CBC.9080302@googlemail.com> <541C422F.70508@googlemail.com> <541C48F2.2090704@googlemail.com> <541C5519.505@googlemail.com> <5434E3A7.1030009@googlemail.com> <543B7C78.4040704@googlemail.com> Message-ID: Philipp, Great, I'm glad to hear it is working again as you expect. - Cory On Mon, Oct 13, 2014 at 3:17 AM, Philipp E wrote: > Hi Cory, > > you are correct. This tiny change solves the problem! I hope that our > discussion will also allow others to review their output code with > respect to this change. > > Thank you very much for clarification and your help (and your great > software as well). > > Best regards > Philipp Engels > > On 10/10/2014 07:20 PM, Cory Quammen wrote: >> Hi Philipp, >> >> I looked into this more, and it turns out it isn't a bug, but a new >> feature in ParaView/VTK that lets provides more flexibility in the >> numeric type of the point positions. By default, most filters will set >> the numeric type of the output points to the numeric type of their >> inputs. In the data set you sent me, the points are set to have type >> int (specified on line 7), which means that the points in the output >> of the Contour filter will be cast to ints. This explains the jagged >> appearance of your surfaces. >> >> The change in VTK that brings about this behavior is: >> >> commit f830ef4cd79b1e7c8af2fae6ed1dd02ffa2cd670 >> Author: Paul Edwards >> Date: Thu Jan 10 10:01:47 2013 -0500 >> >> Fixing loss of point-precision in certain filters. >> >> Certain filters tend to loose point precision and end up >> converting double point >> arrays to flot arrays. This patch address the issue for a few >> filters using the >> API added to vtkAlgorithm by commit 49d1f124. >> >> Change-Id: I8740e4e4bfdd9944fbadb45744038e42eff04830 >> >> Now, how to fix your problem? If you change the type of points from >> int to double in your data file so that it reads >> >> POINTS 6823544 double >> >> instead of >> >> POINTS 6823544 int >> >> all should work as expected. >> >> Please let me know if that doesn't solve the problem for you. >> >> Best regards, >> Cory >> >> On Wed, Oct 8, 2014 at 7:47 AM, Cory Quammen wrote: >>> Philipp, >>> >>> I apologize, but I haven't had time to look more into this problem. >>> I'll have another look soon. >>> >>> Thanks, >>> Cory >>> >>> On Wed, Oct 8, 2014 at 3:11 AM, Philipp E wrote: >>>> Hi Cory, >>>> >>>> can you report any updates for this issue? >>>> >>>> Best regards and thanks for your efforts >>>> Philipp >>>> >>>> On 09/19/2014 07:17 PM, Cory Quammen wrote: >>>>> Just a little more info on this. The problem starts with 3.98. >>>>> >>>>> On Fri, Sep 19, 2014 at 12:08 PM, Philipp E. wrote: >>>>>> Sorry Cory, >>>>>> >>>>>> you are right. The cell number is the same. >>>>>> >>>>>> Regards >>>>>> Philipp >>>>>> >>>>>> >>>>>> Am 19.09.2014 um 17:46 schrieb Cory Quammen: >>>>>>> Philipp, >>>>>>> >>>>>>> I can confirm what you see with a pre 4.2 version of ParaView. >>>>>>> However, the number of produced cells is the same. >>>>>>> >>>>>>> I will try to track down why this changed. >>>>>>> >>>>>>> Thanks, >>>>>>> Cory >>>>>>> >>>>>>> On Fri, Sep 19, 2014 at 11:17 AM, Philipp E wrote: >>>>>>>> Hi Cory >>>>>>>> >>>>>>>> I managed to compress the data set to a fair size and attached it to >>>>>>>> this mail. The data set is pressure, contour value is 0.55. >>>>>>>> >>>>>>>> By looking again at the data (contour -> information), I just found that >>>>>>>> the old version (3.14.1) uses 148432 cells , while the the new one >>>>>>>> employs 75232 cells. Hope that helps. >>>>>>>> >>>>>>>> Kind regards >>>>>>>> Philipp >>>>>>>> >>>>>>>> Errata: I meant 4.2.0RC1 in the previous mails. >>>>>>>> >>>>>>>> On 09/19/2014 04:59 PM, Cory Quammen wrote: >>>>>>>>> Phillipp, >>>>>>>>> >>>>>>>>> Do you have a data set similar to the one you've shown that you can share? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Cory >>>>>>>>> >>>>>>>>> On Fri, Sep 19, 2014 at 10:48 AM, Philipp E wrote: >>>>>>>>>> Hi Cory, >>>>>>>>>> >>>>>>>>>> thank you for your fast feedback. >>>>>>>>>> >>>>>>>>>> a) Compute normal is checked. (Without normals, the contour is >>>>>>>>>> completely stepped) >>>>>>>>>> b) Contour values are the same. >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> Philipp >>>>>>>>>> >>>>>>>>>> On 09/19/2014 04:40 PM, Cory Quammen wrote: >>>>>>>>>>> Philipp, >>>>>>>>>>> >>>>>>>>>>> In the contour filter, is the option "Compute Normals" checked in 4.0 RC1? >>>>>>>>>>> >>>>>>>>>>> Also, are the contour values the same between the two versions? >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Cory >>>>>>>>>>> >>>>>>>>>>> On Fri, Sep 19, 2014 at 10:25 AM, Philipp E wrote: >>>>>>>>>>>> Hello everyone, >>>>>>>>>>>> >>>>>>>>>>>> after extensive search I was desperate enough to post on this list: >>>>>>>>>>>> >>>>>>>>>>>> It appears that the surface smoothing algorithm of the contour filter >>>>>>>>>>>> does not work as "aggressive" as in older version (3.14.1 was the last >>>>>>>>>>>> one we found to do so). As an example I prepared this two screenshots, >>>>>>>>>>>> VTK data are scalars on a structured grid (200x100x100), legacy format. >>>>>>>>>>>> (An additional call of the "smooth" filter does not help.) >>>>>>>>>>>> >>>>>>>>>>>> 3.14.1 >>>>>>>>>>>> http://s7.directupload.net/images/140919/euadfvko.png >>>>>>>>>>>> 4.0.RC1 >>>>>>>>>>>> http://s14.directupload.net/images/140919/84y689mi.png >>>>>>>>>>>> >>>>>>>>>>>> Both versions are running with the shipped settings. Since the effect >>>>>>>>>>>> could be reproduced on several workstations, we are wondering whether >>>>>>>>>>>> there has been an (undocumented?) change in the filter mechanism or some >>>>>>>>>>>> option we/setting/data problem we are not aware of. >>>>>>>>>>>> >>>>>>>>>>>> Kind regards and thanks in advance >>>>>>>>>>>> Philipp Engels. >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Powered by www.kitware.com >>>>>>>>>>>> >>>>>>>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>>>>>>> >>>>>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>>>>>> >>>>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Mon Oct 13 09:48:49 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 13 Oct 2014 13:48:49 +0000 Subject: [Paraview] ParaView 4.2.0 client/server execution error on SGI UV System (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thanks JB. I will dig into the compilation process and see if there is anything I missed. Thanks -simon -----Original Message----- From: Biddiscombe, John A. [mailto:biddisco at cscs.ch] Sent: Friday, October 10, 2014 6:10 PM To: Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] ParaView 4.2.0 client/server execution error on SGI UV System (UNCLASSIFIED) The client has created the representation glyph3d, but the server hasn?t got it compiled in by the looks of it, so the create representation fails. Does it get skipped when using osmesa (and hence doesn?t exist on the server)? I?m not certain of this, but it happens all the time with the same error when one of my plugins that create a representation is loaded on the client - but not on the server. JB On 10/10/14 20:31, "Su, Simon M CTR USARMY ARL (US)" wrote: >Classification: UNCLASSIFIED >Caveats: NONE > >Hello, > >We are wondering if someone can point us in the right direction to >track down the issue we are getting. We managed to get ParaView OSMESA >compile on our SGI UV System. But in a client/server execution mode, >although we are able to connect and paraview starts up on the HPC side, >as soon as we try to draw something, we get a segmentation fault error >- please see error message at the bottom of this email. > >ParaView 4.2.0 osmesa is configure with the following options. > >-DCMAKE_BUILD_TYPE=Release \ >-DParaView_FROM_GIT=ON \ >-DENABLE_boost=ON \ >-DENABLE_cgns=OFF \ >-DENABLE_ffmpeg=ON \ >-DENABLE_fontconfig=ON \ >-DENABLE_freetype=ON \ >-DENABLE_hdf5=ON \ >-DENABLE_libxml2=ON \ >-DENABLE_matplotlib=ON \ >-DENABLE_mesa=OFF \ >-DENABLE_mpi=ON \ >-DENABLE_numpy=ON \ >-DENABLE_osmesa=ON \ >-DENABLE_paraview=ON \ >-DENABLE_png=ON \ >-DENABLE_python=ON \ >-DENABLE_qhull=ON \ >-DENABLE_qt=OFF \ >-DENABLE_silo=ON \ >-DENABLE_szip=ON \ >-DENABLE_visitbridge=ON \ >-DMPI_CXX_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >-DMPI_C_LIBRARIES:STRING="/opt/sgi/mpt/mpt-2.08/lib/libmpi.so" \ >-DMPI_LIBRARY:FILEPATH="/opt/sgi/mpt/mpt-2.08/lib/libmpi++.so" \ >-DMPI_CXX_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >-DMPI_C_INCLUDE_PATH:STRING="/opt/sgi/mpt/mpt-2.08/include" \ >-DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=OFF \ -DUSE_SYSTEM_zlib=OFF \ > >And pvserver is invoked with the following arguments > >mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >--server-port=1486 --client-host=${HOSTNAME} --reverse-connection >--timeout=00:10:00 --connect-id=43826 > >Any suggestion on what/where we can start to track this segmentation >fault issue down is much appreciated. > >Thanks >-simon > > >=========================== client/server execution error >======================== > >mpiexec_mpt -np ${NUM_MPITASKS} pvserver --use-offscreen-rendering >--server-port=1486 --client-host=predator --reverse-connection >--timeout=00:10:00 --connect-id=43826 > >Accepting connection(s): phineas.arl.army.mil:55816 >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/v >tkP >V >SessionCore.cxx, line 390 >vtkPVSessionCore (0x7f8f85b63810): Object type: >vtkGlyph3DRepresentation, could not find requested method: "SetTriangulate" >or the method was called with incorrect arguments. > >while processing >Message 0 = Invoke > Argument 0 = vtk_object_pointer {vtkGlyph3DRepresentation >(0x7f8f8833fe90)} > Argument 1 = string_value {SetTriangulate} > Argument 2 = int32_value {0} > > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/v >tkP >V >SessionCore.cxx, line 391 >vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >purposes. > > >############ ABORT ############# >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/v >tkS >I >Proxy.cxx, line 487 >vtkSISourceProxy (0x7f8f8833fc10): Could not parse property: >Triangulate > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ClientServerCore/Core/vtkPV >Alg >o >rithmPortsInformation.cxx, line 56 >vtkPVAlgorithmPortsInformation (0x7f8f88367ee0): Could not downcast >vtkAlgorithm. > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/v >tkP >V >SessionCore.cxx, line 390 >vtkPVSessionCore (0x7f8f85b63810): Wrapper function not found for class >"(vtk object is NULL)". >while processing >Message 0 = Invoke > Argument 0 = stream_value { > Message 0 = Invoke > Argument 0 = id_value {1} > Argument 1 = string_value {GetVTKObject} > Argument 2 = uint32_value {4525} > } > Argument 1 = string_value {Initialize} > Argument 2 = uint32_value {4525} > Argument 3 = uint32_value {4535} > > > >ERROR: In >/Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Rele >ase >- >Python27/paraview/src/paraview/ParaViewCore/ServerImplementation/Core/v >tkP >V >SessionCore.cxx, line 391 >vtkPVSessionCore (0x7f8f85b63810): Aborting execution for debugging >purposes. > > >############ ABORT ############# >Segmentation fault > > > >Classification: UNCLASSIFIED >Caveats: NONE > > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From jfavre at cscs.ch Mon Oct 13 09:49:17 2014 From: jfavre at cscs.ch (Favre Jean) Date: Mon, 13 Oct 2014 13:49:17 +0000 Subject: [Paraview] Contour volume quantification (volume fractions of a scalar in an unstructured grid) In-Reply-To: References: Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6828154E7A@MBX21.d.ethz.ch> Given the new features of the python calculator, it ought not to be difficult to compute volumes. I would do it iteratively, using an Isovolume between two different values [min, max] However, I find that the clipper, or isovolume filter do not seem to always create consistently oriented cells. By that I mean that some cells are returned with negative volumes, and that throws off the global computation totally. the python calculator can let you type in an expression like volume(inputs[0]), which would compute a cell-by-cell volume (left image in the attached script) We can also do a global summation like sum(volume(inputs[0])) (right image in my script) using well-behaved cuts (such as orthonormal cuts), and flipping the clipper's normal by toggling "inside out", I do get global volumes that add up to the full volume = 20^3 = 8000. Anything else with arbitrary cuts (as per my python scripts) show volumes which do not add up to the global volume, because of the negative volumes cells. I hope I am not making errors here. Can anyone confirm my findings about negative volumes? ----------------- Jean / CSCS ________________________________ From: ParaView [paraview-bounces at paraview.org] on behalf of Jose Rey [onlyrey at gmail.com] Sent: Saturday, October 11, 2014 8:33 AM To: paraview at paraview.org Subject: [Paraview] Contour volume quantification (volume fractions of a scalar in an unstructured grid) Good day, I would like to calculate the volume contained by each contour surface applied to an unstructured dataset. How do I do this? Here is what I have: 1. An 3D unstructured grid resulting from a CFD code (OpenFOAM) with velocities (Ux, Uy, Uz) 2. Applied the "Calculator" filter to calculate Result Array = Umagnitude from the point data with the formula (U_X^2+U_Y^2+U_Z^2)^.5 (I used point data for the calculator because I can only apply contour to point data) 3. Applied the "Contour" filter, and generated 11 volumetric contours (from 0.0 to 0.3 m/s) Here is where I am stuck (and what I intend): *. Trying to calculate the volume inside each contour surface The reason I want to calculate this: * To calculate a distribution of velocity magnitudes (where the X axis is velocity magnitude ranges /bins, and Y axis is total volume occupied by the cells in each velocity magnitude range -- not cell count as is the case of histograms) My Paraview version: * 4.2 running on Win64 (I also have aversion of paraview 4.1 modified to work with OpenFOAM, and installed in a Ubuntu64x-12.04 virtual box) Thank you very much in advance, Jose -- Jose I. Rey onlyrey at gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: volumes.py Type: text/x-python Size: 6089 bytes Desc: volumes.py URL: From simon.m.su.ctr at mail.mil Mon Oct 13 09:52:27 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 13 Oct 2014 13:52:27 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hi Cory, Thanks for the info. I will update my build script. Thanks -simon -----Original Message----- From: Cory Quammen [mailto:cory.quammen at kitware.com] Sent: Saturday, October 11, 2014 6:04 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED) Hi Simon, What you are doing as a workaround is indeed how production builds should be created. The ParaView superbuild is now set up to check out the master branch of ParaView, which varies day to day. In 4.1 and prior to that, it was set up to check out out the release branch, which was far more static. If you disable ParaView_FROM_GIT in CMake, it will download the release source tar ball and build from that, essentially what you have been doing. I'll update the superbuild wiki instructions to note this. Best regards, Cory On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want > to build a specific version, I will do > > git clone git://paraview.org/ParaViewSuperbuild.git > cd ParaViewSuperbuild > git checkout v4.1.0 > > That has always worked for me for v4.1.0 tag > > But with v4.2.0 release, if I do the following on different days, > > git clone git://paraview.org/ParaViewSuperbuild.git > cd ParaViewSuperbuild > git checkout v4.2.0 > > I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. > Am I missing something? This is causing me problem when I am trying to > get the same version of ParaView mesa and osmesa build for > client/server mode. I end up doing a > > -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz > > To get around the problem. Thoughts? > > > Thanks > -simon > > > > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From bwvb at xs4all.nl Mon Oct 13 10:19:36 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 16:19:36 +0200 Subject: [Paraview] Disappearing volume rendering? Message-ID: <543BDF78.3090909@xs4all.nl> Hi, I'm struggling to get a proper 3D view of my model system (yes, embarrassing!) but must admit my defeat. After stripping almost everything, keeping the minimum to exhibit the issue, I'm left with the following: I have created a simple box source. To get a 3D representation, I sub-classed the code for this Source from vtkUnstructuredGridAlgorithm. In the RequestData method, I define the 8 point of the unit cube. I added the points to the underlying unstructed grid, and I specified the cell topology. This all seems to work: when instantiating this box Source, I *do* get the expected cube in the representations (Surface, wireframe, Points). However, when I select the "Volume" representation, *the image disappears* What am I doing wrong? As the code is not too long and very simple, I take the freedom to paste it below. Kind regards. Bertwim ========================================= int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector) { // Get the info object vtkInformation *outInfo = outputVector->GetInformationObject(0); vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); // Pre-allocate some memory umesh->Allocate( 1024 ); // Specify points. double r0[] = { 0.0, 0.0, 0.0 }; double r1[] = { 1.0, 0.0, 0.0 }; double r2[] = { 0.0, 1.0, 0.0 }; double r3[] = { 1.0, 1.0, 0.0 }; double r4[] = { 0.0, 0.0, 1.0 }; double r5[] = { 1.0, 0.0, 1.0 }; double r6[] = { 0.0, 1.0, 1.0 }; double r7[] = { 1.0, 1.0, 1.0 }; // Collect the points in a vtk data structures. { vtkSmartPointer points = vtkSmartPointer::New(); points->SetDataType( VTK_DOUBLE ); points->InsertNextPoint( r0 ); points->InsertNextPoint( r1 ); points->InsertNextPoint( r2 ); points->InsertNextPoint( r3 ); points->InsertNextPoint( r4 ); points->InsertNextPoint( r5 ); points->InsertNextPoint( r6 ); points->InsertNextPoint( r7 ); // Transfer points to umesh. umesh->SetPoints( points ); } // Cell Topology vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); return 1; } From aashish.chaudhary at kitware.com Mon Oct 13 11:28:23 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 13 Oct 2014 11:28:23 -0400 Subject: [Paraview] BOX -> volume? In-Reply-To: <54383746.6010105@xs4all.nl> References: <54383746.6010105@xs4all.nl> Message-ID: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest wrote: > Can perhaps somebody point me how to address the following. > > When I create a new source (say: a box) I get an a box that > can be displayed via its surfaces, its constituing points, or wireframe > representation. > But I need a volume rendering (so that I can add e.g. a clipping plane) > How do I get that? > > Regards, > Bertwim > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Mon Oct 13 11:36:04 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Mon, 13 Oct 2014 11:36:04 -0400 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: <543BDF78.3090909@xs4all.nl> References: <543BDF78.3090909@xs4all.nl> Message-ID: Bertwim, I'm not sure that the volume renderer can handle VTK_HEXAHEDRON elements. Try the "Tetrahedralize" filter on your source and see if the Volume representation works. Thanks, Cory On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest wrote: > Hi, > > I'm struggling to get a proper 3D view of my model system (yes, > embarrassing!) > but must admit my defeat. > After stripping almost everything, keeping the minimum to exhibit the > issue, > I'm left with the following: > > I have created a simple box source. To get a 3D representation, I > sub-classed > the code for this Source from vtkUnstructuredGridAlgorithm. > > In the RequestData method, I define the 8 point of the unit cube. I > added the points to the > underlying unstructed grid, and I specified the cell topology. > > This all seems to work: when instantiating this box Source, I *do* get the > expected cube in the representations (Surface, wireframe, Points). > > However, when I select the "Volume" representation, *the image disappears* > What am I doing wrong? > > As the code is not too long and very simple, I take the freedom to paste > it below. > > Kind regards. > Bertwim > > ========================================= > > int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), > vtkInformationVector > **vtkNotUsed(inputVector), > vtkInformationVector *outputVector) > { > // Get the info object > vtkInformation *outInfo = outputVector->GetInformationObject(0); > vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( > outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > > // Pre-allocate some memory > umesh->Allocate( 1024 ); > > // Specify points. > double r0[] = { 0.0, 0.0, 0.0 }; > double r1[] = { 1.0, 0.0, 0.0 }; > double r2[] = { 0.0, 1.0, 0.0 }; > double r3[] = { 1.0, 1.0, 0.0 }; > double r4[] = { 0.0, 0.0, 1.0 }; > double r5[] = { 1.0, 0.0, 1.0 }; > double r6[] = { 0.0, 1.0, 1.0 }; > double r7[] = { 1.0, 1.0, 1.0 }; > > // Collect the points in a vtk data structures. > { > vtkSmartPointer points = vtkSmartPointer::New(); > points->SetDataType( VTK_DOUBLE ); > > points->InsertNextPoint( r0 ); > points->InsertNextPoint( r1 ); > points->InsertNextPoint( r2 ); > points->InsertNextPoint( r3 ); > points->InsertNextPoint( r4 ); > points->InsertNextPoint( r5 ); > points->InsertNextPoint( r6 ); > points->InsertNextPoint( r7 ); > > // Transfer points to umesh. > umesh->SetPoints( points ); > } > > // Cell Topology > vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > > return 1; > } > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From aashish.chaudhary at kitware.com Mon Oct 13 11:49:01 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 13 Oct 2014 11:49:01 -0400 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: References: <543BDF78.3090909@xs4all.nl> Message-ID: I believe that is correct. Run the Tetrahedralize filter and see if that works. - Aashish On Mon, Oct 13, 2014 at 11:36 AM, Cory Quammen wrote: > Bertwim, > > I'm not sure that the volume renderer can handle VTK_HEXAHEDRON > elements. Try the "Tetrahedralize" filter on your source and see if > the Volume representation works. > > Thanks, > Cory > > On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest wrote: > > Hi, > > > > I'm struggling to get a proper 3D view of my model system (yes, > > embarrassing!) > > but must admit my defeat. > > After stripping almost everything, keeping the minimum to exhibit the > > issue, > > I'm left with the following: > > > > I have created a simple box source. To get a 3D representation, I > > sub-classed > > the code for this Source from vtkUnstructuredGridAlgorithm. > > > > In the RequestData method, I define the 8 point of the unit cube. I > > added the points to the > > underlying unstructed grid, and I specified the cell topology. > > > > This all seems to work: when instantiating this box Source, I *do* get > the > > expected cube in the representations (Surface, wireframe, Points). > > > > However, when I select the "Volume" representation, *the image > disappears* > > What am I doing wrong? > > > > As the code is not too long and very simple, I take the freedom to paste > > it below. > > > > Kind regards. > > Bertwim > > > > ========================================= > > > > int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), > > vtkInformationVector > > **vtkNotUsed(inputVector), > > vtkInformationVector *outputVector) > > { > > // Get the info object > > vtkInformation *outInfo = outputVector->GetInformationObject(0); > > vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( > > outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > > > > // Pre-allocate some memory > > umesh->Allocate( 1024 ); > > > > // Specify points. > > double r0[] = { 0.0, 0.0, 0.0 }; > > double r1[] = { 1.0, 0.0, 0.0 }; > > double r2[] = { 0.0, 1.0, 0.0 }; > > double r3[] = { 1.0, 1.0, 0.0 }; > > double r4[] = { 0.0, 0.0, 1.0 }; > > double r5[] = { 1.0, 0.0, 1.0 }; > > double r6[] = { 0.0, 1.0, 1.0 }; > > double r7[] = { 1.0, 1.0, 1.0 }; > > > > // Collect the points in a vtk data structures. > > { > > vtkSmartPointer points = > vtkSmartPointer::New(); > > points->SetDataType( VTK_DOUBLE ); > > > > points->InsertNextPoint( r0 ); > > points->InsertNextPoint( r1 ); > > points->InsertNextPoint( r2 ); > > points->InsertNextPoint( r3 ); > > points->InsertNextPoint( r4 ); > > points->InsertNextPoint( r5 ); > > points->InsertNextPoint( r6 ); > > points->InsertNextPoint( r7 ); > > > > // Transfer points to umesh. > > umesh->SetPoints( points ); > > } > > > > // Cell Topology > > vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > > umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > > > > return 1; > > } > > > > > > > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Mon Oct 13 13:22:06 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 19:22:06 +0200 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: References: <543BDF78.3090909@xs4all.nl> Message-ID: <543C0A3E.5000403@xs4all.nl> No, it doesn't work. The filter creates tets, which are visible in the wireframe representation, but when I select "Volume" representation the image disappears. I can't imagine it is so difficult to render a volume in Paraview. I must be doing something wrong.... Regards, Bertwim On 10/13/2014 05:36 PM, Cory Quammen wrote: > Bertwim, > > I'm not sure that the volume renderer can handle VTK_HEXAHEDRON > elements. Try the "Tetrahedralize" filter on your source and see if > the Volume representation works. > > Thanks, > Cory > > On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest wrote: >> Hi, >> >> I'm struggling to get a proper 3D view of my model system (yes, >> embarrassing!) >> but must admit my defeat. >> After stripping almost everything, keeping the minimum to exhibit the >> issue, >> I'm left with the following: >> >> I have created a simple box source. To get a 3D representation, I >> sub-classed >> the code for this Source from vtkUnstructuredGridAlgorithm. >> >> In the RequestData method, I define the 8 point of the unit cube. I >> added the points to the >> underlying unstructed grid, and I specified the cell topology. >> >> This all seems to work: when instantiating this box Source, I *do* get the >> expected cube in the representations (Surface, wireframe, Points). >> >> However, when I select the "Volume" representation, *the image disappears* >> What am I doing wrong? >> >> As the code is not too long and very simple, I take the freedom to paste >> it below. >> >> Kind regards. >> Bertwim >> >> ========================================= >> >> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), >> vtkInformationVector >> **vtkNotUsed(inputVector), >> vtkInformationVector *outputVector) >> { >> // Get the info object >> vtkInformation *outInfo = outputVector->GetInformationObject(0); >> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( >> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); >> >> // Pre-allocate some memory >> umesh->Allocate( 1024 ); >> >> // Specify points. >> double r0[] = { 0.0, 0.0, 0.0 }; >> double r1[] = { 1.0, 0.0, 0.0 }; >> double r2[] = { 0.0, 1.0, 0.0 }; >> double r3[] = { 1.0, 1.0, 0.0 }; >> double r4[] = { 0.0, 0.0, 1.0 }; >> double r5[] = { 1.0, 0.0, 1.0 }; >> double r6[] = { 0.0, 1.0, 1.0 }; >> double r7[] = { 1.0, 1.0, 1.0 }; >> >> // Collect the points in a vtk data structures. >> { >> vtkSmartPointer points = vtkSmartPointer::New(); >> points->SetDataType( VTK_DOUBLE ); >> >> points->InsertNextPoint( r0 ); >> points->InsertNextPoint( r1 ); >> points->InsertNextPoint( r2 ); >> points->InsertNextPoint( r3 ); >> points->InsertNextPoint( r4 ); >> points->InsertNextPoint( r5 ); >> points->InsertNextPoint( r6 ); >> points->InsertNextPoint( r7 ); >> >> // Transfer points to umesh. >> umesh->SetPoints( points ); >> } >> >> // Cell Topology >> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; >> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); >> >> return 1; >> } >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From bloring at lbl.gov Mon Oct 13 13:28:01 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 13 Oct 2014 10:28:01 -0700 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: <543C0A3E.5000403@xs4all.nl> References: <543BDF78.3090909@xs4all.nl> <543C0A3E.5000403@xs4all.nl> Message-ID: <543C0BA1.5000000@lbl.gov> do you have any scalars? those are not optional for volume rendering. Additionally you may need to adjust the transfer function, On 10/13/2014 10:22 AM, B.W.H. van Beest wrote: > No, it doesn't work. The filter creates tets, which are visible in the > wireframe representation, > but when I select "Volume" representation the image disappears. > > I can't imagine it is so difficult to render a volume in Paraview. I > must be doing something wrong.... > > Regards, > Bertwim > > On 10/13/2014 05:36 PM, Cory Quammen wrote: >> Bertwim, >> >> I'm not sure that the volume renderer can handle VTK_HEXAHEDRON >> elements. Try the "Tetrahedralize" filter on your source and see if >> the Volume representation works. >> >> Thanks, >> Cory >> >> On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest wrote: >>> Hi, >>> >>> I'm struggling to get a proper 3D view of my model system (yes, >>> embarrassing!) >>> but must admit my defeat. >>> After stripping almost everything, keeping the minimum to exhibit the >>> issue, >>> I'm left with the following: >>> >>> I have created a simple box source. To get a 3D representation, I >>> sub-classed >>> the code for this Source from vtkUnstructuredGridAlgorithm. >>> >>> In the RequestData method, I define the 8 point of the unit cube. I >>> added the points to the >>> underlying unstructed grid, and I specified the cell topology. >>> >>> This all seems to work: when instantiating this box Source, I *do* get the >>> expected cube in the representations (Surface, wireframe, Points). >>> >>> However, when I select the "Volume" representation, *the image disappears* >>> What am I doing wrong? >>> >>> As the code is not too long and very simple, I take the freedom to paste >>> it below. >>> >>> Kind regards. >>> Bertwim >>> >>> ========================================= >>> >>> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), >>> vtkInformationVector >>> **vtkNotUsed(inputVector), >>> vtkInformationVector *outputVector) >>> { >>> // Get the info object >>> vtkInformation *outInfo = outputVector->GetInformationObject(0); >>> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( >>> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); >>> >>> // Pre-allocate some memory >>> umesh->Allocate( 1024 ); >>> >>> // Specify points. >>> double r0[] = { 0.0, 0.0, 0.0 }; >>> double r1[] = { 1.0, 0.0, 0.0 }; >>> double r2[] = { 0.0, 1.0, 0.0 }; >>> double r3[] = { 1.0, 1.0, 0.0 }; >>> double r4[] = { 0.0, 0.0, 1.0 }; >>> double r5[] = { 1.0, 0.0, 1.0 }; >>> double r6[] = { 0.0, 1.0, 1.0 }; >>> double r7[] = { 1.0, 1.0, 1.0 }; >>> >>> // Collect the points in a vtk data structures. >>> { >>> vtkSmartPointer points = vtkSmartPointer::New(); >>> points->SetDataType( VTK_DOUBLE ); >>> >>> points->InsertNextPoint( r0 ); >>> points->InsertNextPoint( r1 ); >>> points->InsertNextPoint( r2 ); >>> points->InsertNextPoint( r3 ); >>> points->InsertNextPoint( r4 ); >>> points->InsertNextPoint( r5 ); >>> points->InsertNextPoint( r6 ); >>> points->InsertNextPoint( r7 ); >>> >>> // Transfer points to umesh. >>> umesh->SetPoints( points ); >>> } >>> >>> // Cell Topology >>> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; >>> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); >>> >>> return 1; >>> } >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Mon Oct 13 13:33:13 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 19:33:13 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: References: <54383746.6010105@xs4all.nl> Message-ID: <543C0CD9.3080207@xs4all.nl> Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grrrrrr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: > You can create a wavelet source and then display it as a volume. > > > > On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest > wrote: > > Can perhaps somebody point me how to address the following. > > When I create a new source (say: a box) I get an a box that > can be displayed via its surfaces, its constituing points, or > wireframe > representation. > But I need a volume rendering (so that I can add e.g. a clipping > plane) > How do I get that? > > Regards, > Bertwim > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Oct 13 13:35:25 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 13 Oct 2014 13:35:25 -0400 Subject: [Paraview] BOX -> volume? In-Reply-To: <543C0CD9.3080207@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> Message-ID: So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest wrote: > Aashish, > > Thanks for the suggestion. > > However, doing this gives me all kinds of opengl errors (invalid > instruction). > > Besides that, the wavelet gives me a cube indeed, but I need to understand > when > I can have a volume rendering. I created new Source's (e.g. tri-prism, a > wedge, > a box with boundaries of finite thickness etc.). But I cannot get volume > rendering > to work, grrrrrr. (See other thread) > > Kind Regards, > Bertwim > > > > On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: > > You can create a wavelet source and then display it as a volume. > > > > On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest wrote: > >> Can perhaps somebody point me how to address the following. >> >> When I create a new source (say: a box) I get an a box that >> can be displayed via its surfaces, its constituing points, or wireframe >> representation. >> But I need a volume rendering (so that I can add e.g. a clipping plane) >> How do I get that? >> >> Regards, >> Bertwim >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Mon Oct 13 13:35:24 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 19:35:24 +0200 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: <543C0BA1.5000000@lbl.gov> References: <543BDF78.3090909@xs4all.nl> <543C0A3E.5000403@xs4all.nl> <543C0BA1.5000000@lbl.gov> Message-ID: <543C0D5C.7090105@xs4all.nl> Yes, I do set a scalar for each cell. I left them out in the example, as also with a scalar I couldn't get a volume display. I'm not sure what you mean by "adjusting the transfer function". Regards, Bertwim On 10/13/2014 07:28 PM, Burlen Loring wrote: > do you have any scalars? those are not optional for volume rendering. > Additionally you may need to adjust the transfer function, > > On 10/13/2014 10:22 AM, B.W.H. van Beest wrote: >> No, it doesn't work. The filter creates tets, which are visible in the >> wireframe representation, >> but when I select "Volume" representation the image disappears. >> >> I can't imagine it is so difficult to render a volume in Paraview. I >> must be doing something wrong.... >> >> Regards, >> Bertwim >> >> On 10/13/2014 05:36 PM, Cory Quammen wrote: >>> Bertwim, >>> >>> I'm not sure that the volume renderer can handle VTK_HEXAHEDRON >>> elements. Try the "Tetrahedralize" filter on your source and see if >>> the Volume representation works. >>> >>> Thanks, >>> Cory >>> >>> On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest >>> wrote: >>>> Hi, >>>> >>>> I'm struggling to get a proper 3D view of my model system (yes, >>>> embarrassing!) >>>> but must admit my defeat. >>>> After stripping almost everything, keeping the minimum to exhibit the >>>> issue, >>>> I'm left with the following: >>>> >>>> I have created a simple box source. To get a 3D representation, I >>>> sub-classed >>>> the code for this Source from vtkUnstructuredGridAlgorithm. >>>> >>>> In the RequestData method, I define the 8 point of the unit cube. I >>>> added the points to the >>>> underlying unstructed grid, and I specified the cell topology. >>>> >>>> This all seems to work: when instantiating this box Source, I *do* >>>> get the >>>> expected cube in the representations (Surface, wireframe, Points). >>>> >>>> However, when I select the "Volume" representation, *the image >>>> disappears* >>>> What am I doing wrong? >>>> >>>> As the code is not too long and very simple, I take the freedom to >>>> paste >>>> it below. >>>> >>>> Kind regards. >>>> Bertwim >>>> >>>> ========================================= >>>> >>>> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), >>>> vtkInformationVector >>>> **vtkNotUsed(inputVector), >>>> vtkInformationVector *outputVector) >>>> { >>>> // Get the info object >>>> vtkInformation *outInfo = outputVector->GetInformationObject(0); >>>> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( >>>> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); >>>> >>>> // Pre-allocate some memory >>>> umesh->Allocate( 1024 ); >>>> >>>> // Specify points. >>>> double r0[] = { 0.0, 0.0, 0.0 }; >>>> double r1[] = { 1.0, 0.0, 0.0 }; >>>> double r2[] = { 0.0, 1.0, 0.0 }; >>>> double r3[] = { 1.0, 1.0, 0.0 }; >>>> double r4[] = { 0.0, 0.0, 1.0 }; >>>> double r5[] = { 1.0, 0.0, 1.0 }; >>>> double r6[] = { 0.0, 1.0, 1.0 }; >>>> double r7[] = { 1.0, 1.0, 1.0 }; >>>> >>>> // Collect the points in a vtk data structures. >>>> { >>>> vtkSmartPointer points = >>>> vtkSmartPointer::New(); >>>> points->SetDataType( VTK_DOUBLE ); >>>> >>>> points->InsertNextPoint( r0 ); >>>> points->InsertNextPoint( r1 ); >>>> points->InsertNextPoint( r2 ); >>>> points->InsertNextPoint( r3 ); >>>> points->InsertNextPoint( r4 ); >>>> points->InsertNextPoint( r5 ); >>>> points->InsertNextPoint( r6 ); >>>> points->InsertNextPoint( r7 ); >>>> >>>> // Transfer points to umesh. >>>> umesh->SetPoints( points ); >>>> } >>>> >>>> // Cell Topology >>>> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; >>>> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); >>>> >>>> return 1; >>>> } >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > From bwvb at xs4all.nl Mon Oct 13 13:41:17 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 19:41:17 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> Message-ID: <543C0EBD.3050304@xs4all.nl> Hi Aashish, This is what I do: 1. start paraview 2. Sources -> Wavelet -> Apply. A cube is displayed (Outline representation). 3. Select 'Volume" representation" cube disappears. Then: ===================== Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation ========================= On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: > So when you created a wavelet source and change the representation to > volume you got the errors? Can you post those errors? > > Thanks, > > > On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest > wrote: > > Aashish, > > Thanks for the suggestion. > > However, doing this gives me all kinds of opengl errors (invalid > instruction). > > Besides that, the wavelet gives me a cube indeed, but I need to > understand when > I can have a volume rendering. I created new Source's (e.g. > tri-prism, a wedge, > a box with boundaries of finite thickness etc.). But I cannot get > volume rendering > to work, grrrrrr. (See other thread) > > Kind Regards, > Bertwim > > > > On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >> You can create a wavelet source and then display it as a volume. >> >> >> >> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest > > wrote: >> >> Can perhaps somebody point me how to address the following. >> >> When I create a new source (say: a box) I get an a box that >> can be displayed via its surfaces, its constituing points, or >> wireframe >> representation. >> But I need a volume rendering (so that I can add e.g. a >> clipping plane) >> How do I get that? >> >> Regards, >> Bertwim >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Oct 13 13:42:53 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 13 Oct 2014 13:42:53 -0400 Subject: [Paraview] BOX -> volume? In-Reply-To: <543C0EBD.3050304@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> Message-ID: What graphics card / graphics driver version / OS this system has? - Aashish On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest wrote: > Hi Aashish, > > This is what I do: > 1. start paraview > 2. Sources -> Wavelet -> Apply. > A cube is displayed (Outline representation). > 3. Select 'Volume" representation" > > cube disappears. Then: > ===================== > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > ========================= > > > > > > > On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: > > So when you created a wavelet source and change the representation to > volume you got the errors? Can you post those errors? > > Thanks, > > > On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest wrote: > >> Aashish, >> >> Thanks for the suggestion. >> >> However, doing this gives me all kinds of opengl errors (invalid >> instruction). >> >> Besides that, the wavelet gives me a cube indeed, but I need to >> understand when >> I can have a volume rendering. I created new Source's (e.g. tri-prism, a >> wedge, >> a box with boundaries of finite thickness etc.). But I cannot get volume >> rendering >> to work, grrrrrr. (See other thread) >> >> Kind Regards, >> Bertwim >> >> >> >> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >> >> You can create a wavelet source and then display it as a volume. >> >> >> >> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest wrote: >> >>> Can perhaps somebody point me how to address the following. >>> >>> When I create a new source (say: a box) I get an a box that >>> can be displayed via its surfaces, its constituing points, or wireframe >>> representation. >>> But I need a volume rendering (so that I can add e.g. a clipping plane) >>> How do I get that? >>> >>> Regards, >>> Bertwim >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> >> >> > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Mon Oct 13 13:43:49 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Mon, 13 Oct 2014 13:43:49 -0400 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: <543C0D5C.7090105@xs4all.nl> References: <543BDF78.3090909@xs4all.nl> <543C0A3E.5000403@xs4all.nl> <543C0BA1.5000000@lbl.gov> <543C0D5C.7090105@xs4all.nl> Message-ID: Bertwim, If you are seeing errors (like you mentioned in other email), I am afraid that you won't see any volume. Would it be possible for you to upload your data somewhere? - Aashish On Mon, Oct 13, 2014 at 1:35 PM, B.W.H. van Beest wrote: > Yes, I do set a scalar for each cell. I left them out in the example, as > also with a scalar I couldn't get a volume display. > > I'm not sure what you mean by "adjusting the transfer function". > > Regards, > Bertwim > > > > On 10/13/2014 07:28 PM, Burlen Loring wrote: > > do you have any scalars? those are not optional for volume rendering. > > Additionally you may need to adjust the transfer function, > > > > On 10/13/2014 10:22 AM, B.W.H. van Beest wrote: > >> No, it doesn't work. The filter creates tets, which are visible in the > >> wireframe representation, > >> but when I select "Volume" representation the image disappears. > >> > >> I can't imagine it is so difficult to render a volume in Paraview. I > >> must be doing something wrong.... > >> > >> Regards, > >> Bertwim > >> > >> On 10/13/2014 05:36 PM, Cory Quammen wrote: > >>> Bertwim, > >>> > >>> I'm not sure that the volume renderer can handle VTK_HEXAHEDRON > >>> elements. Try the "Tetrahedralize" filter on your source and see if > >>> the Volume representation works. > >>> > >>> Thanks, > >>> Cory > >>> > >>> On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest > >>> wrote: > >>>> Hi, > >>>> > >>>> I'm struggling to get a proper 3D view of my model system (yes, > >>>> embarrassing!) > >>>> but must admit my defeat. > >>>> After stripping almost everything, keeping the minimum to exhibit the > >>>> issue, > >>>> I'm left with the following: > >>>> > >>>> I have created a simple box source. To get a 3D representation, I > >>>> sub-classed > >>>> the code for this Source from vtkUnstructuredGridAlgorithm. > >>>> > >>>> In the RequestData method, I define the 8 point of the unit cube. I > >>>> added the points to the > >>>> underlying unstructed grid, and I specified the cell topology. > >>>> > >>>> This all seems to work: when instantiating this box Source, I *do* > >>>> get the > >>>> expected cube in the representations (Surface, wireframe, Points). > >>>> > >>>> However, when I select the "Volume" representation, *the image > >>>> disappears* > >>>> What am I doing wrong? > >>>> > >>>> As the code is not too long and very simple, I take the freedom to > >>>> paste > >>>> it below. > >>>> > >>>> Kind regards. > >>>> Bertwim > >>>> > >>>> ========================================= > >>>> > >>>> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), > >>>> vtkInformationVector > >>>> **vtkNotUsed(inputVector), > >>>> vtkInformationVector *outputVector) > >>>> { > >>>> // Get the info object > >>>> vtkInformation *outInfo = outputVector->GetInformationObject(0); > >>>> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( > >>>> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > >>>> > >>>> // Pre-allocate some memory > >>>> umesh->Allocate( 1024 ); > >>>> > >>>> // Specify points. > >>>> double r0[] = { 0.0, 0.0, 0.0 }; > >>>> double r1[] = { 1.0, 0.0, 0.0 }; > >>>> double r2[] = { 0.0, 1.0, 0.0 }; > >>>> double r3[] = { 1.0, 1.0, 0.0 }; > >>>> double r4[] = { 0.0, 0.0, 1.0 }; > >>>> double r5[] = { 1.0, 0.0, 1.0 }; > >>>> double r6[] = { 0.0, 1.0, 1.0 }; > >>>> double r7[] = { 1.0, 1.0, 1.0 }; > >>>> > >>>> // Collect the points in a vtk data structures. > >>>> { > >>>> vtkSmartPointer points = > >>>> vtkSmartPointer::New(); > >>>> points->SetDataType( VTK_DOUBLE ); > >>>> > >>>> points->InsertNextPoint( r0 ); > >>>> points->InsertNextPoint( r1 ); > >>>> points->InsertNextPoint( r2 ); > >>>> points->InsertNextPoint( r3 ); > >>>> points->InsertNextPoint( r4 ); > >>>> points->InsertNextPoint( r5 ); > >>>> points->InsertNextPoint( r6 ); > >>>> points->InsertNextPoint( r7 ); > >>>> > >>>> // Transfer points to umesh. > >>>> umesh->SetPoints( points ); > >>>> } > >>>> > >>>> // Cell Topology > >>>> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > >>>> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > >>>> > >>>> return 1; > >>>> } > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Powered by www.kitware.com > >>>> > >>>> Visit other Kitware open-source projects at > >>>> http://www.kitware.com/opensource/opensource.html > >>>> > >>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>> http://paraview.org/Wiki/ParaView > >>>> > >>>> Follow this link to subscribe/unsubscribe: > >>>> http://public.kitware.com/mailman/listinfo/paraview > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Mon Oct 13 13:55:56 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 19:55:56 +0200 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: References: <543BDF78.3090909@xs4all.nl> <543C0A3E.5000403@xs4all.nl> <543C0BA1.5000000@lbl.gov> <543C0D5C.7090105@xs4all.nl> Message-ID: <543C122C.9040103@xs4all.nl> Aashish, I do see errors in the wavelet example, but not in the other cases. If ok with you , I'll send the full code (it is not much, ~100K) as a zipped tar file by email. There is no other data. Regards, Bertwim On 10/13/2014 07:43 PM, Aashish Chaudhary wrote: > Bertwim, > > If you are seeing errors (like you mentioned in other email), I am > afraid that you won't see any volume. Would it be possible for you to > upload your data somewhere? > > - Aashish > > On Mon, Oct 13, 2014 at 1:35 PM, B.W.H. van Beest > wrote: > > Yes, I do set a scalar for each cell. I left them out in the > example, as > also with a scalar I couldn't get a volume display. > > I'm not sure what you mean by "adjusting the transfer function". > > Regards, > Bertwim > > > > On 10/13/2014 07:28 PM, Burlen Loring wrote: > > do you have any scalars? those are not optional for volume > rendering. > > Additionally you may need to adjust the transfer function, > > > > On 10/13/2014 10:22 AM, B.W.H. van Beest wrote: > >> No, it doesn't work. The filter creates tets, which are visible > in the > >> wireframe representation, > >> but when I select "Volume" representation the image disappears. > >> > >> I can't imagine it is so difficult to render a volume in > Paraview. I > >> must be doing something wrong.... > >> > >> Regards, > >> Bertwim > >> > >> On 10/13/2014 05:36 PM, Cory Quammen wrote: > >>> Bertwim, > >>> > >>> I'm not sure that the volume renderer can handle VTK_HEXAHEDRON > >>> elements. Try the "Tetrahedralize" filter on your source and > see if > >>> the Volume representation works. > >>> > >>> Thanks, > >>> Cory > >>> > >>> On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest > > > >>> wrote: > >>>> Hi, > >>>> > >>>> I'm struggling to get a proper 3D view of my model system (yes, > >>>> embarrassing!) > >>>> but must admit my defeat. > >>>> After stripping almost everything, keeping the minimum to > exhibit the > >>>> issue, > >>>> I'm left with the following: > >>>> > >>>> I have created a simple box source. To get a 3D representation, I > >>>> sub-classed > >>>> the code for this Source from vtkUnstructuredGridAlgorithm. > >>>> > >>>> In the RequestData method, I define the 8 point of the unit > cube. I > >>>> added the points to the > >>>> underlying unstructed grid, and I specified the cell topology. > >>>> > >>>> This all seems to work: when instantiating this box Source, I > *do* > >>>> get the > >>>> expected cube in the representations (Surface, wireframe, > Points). > >>>> > >>>> However, when I select the "Volume" representation, *the image > >>>> disappears* > >>>> What am I doing wrong? > >>>> > >>>> As the code is not too long and very simple, I take the > freedom to > >>>> paste > >>>> it below. > >>>> > >>>> Kind regards. > >>>> Bertwim > >>>> > >>>> ========================================= > >>>> > >>>> int sphBoxSourceC::RequestData( vtkInformation > *vtkNotUsed(request), > >>>> vtkInformationVector > >>>> **vtkNotUsed(inputVector), > >>>> vtkInformationVector > *outputVector) > >>>> { > >>>> // Get the info object > >>>> vtkInformation *outInfo = > outputVector->GetInformationObject(0); > >>>> vtkUnstructuredGrid *umesh = > vtkUnstructuredGrid::SafeDownCast( > >>>> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > >>>> > >>>> // Pre-allocate some memory > >>>> umesh->Allocate( 1024 ); > >>>> > >>>> // Specify points. > >>>> double r0[] = { 0.0, 0.0, 0.0 }; > >>>> double r1[] = { 1.0, 0.0, 0.0 }; > >>>> double r2[] = { 0.0, 1.0, 0.0 }; > >>>> double r3[] = { 1.0, 1.0, 0.0 }; > >>>> double r4[] = { 0.0, 0.0, 1.0 }; > >>>> double r5[] = { 1.0, 0.0, 1.0 }; > >>>> double r6[] = { 0.0, 1.0, 1.0 }; > >>>> double r7[] = { 1.0, 1.0, 1.0 }; > >>>> > >>>> // Collect the points in a vtk data structures. > >>>> { > >>>> vtkSmartPointer points = > >>>> vtkSmartPointer::New(); > >>>> points->SetDataType( VTK_DOUBLE ); > >>>> > >>>> points->InsertNextPoint( r0 ); > >>>> points->InsertNextPoint( r1 ); > >>>> points->InsertNextPoint( r2 ); > >>>> points->InsertNextPoint( r3 ); > >>>> points->InsertNextPoint( r4 ); > >>>> points->InsertNextPoint( r5 ); > >>>> points->InsertNextPoint( r6 ); > >>>> points->InsertNextPoint( r7 ); > >>>> > >>>> // Transfer points to umesh. > >>>> umesh->SetPoints( points ); > >>>> } > >>>> > >>>> // Cell Topology > >>>> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > >>>> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > >>>> > >>>> return 1; > >>>> } > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Powered by www.kitware.com > >>>> > >>>> Visit other Kitware open-source projects at > >>>> http://www.kitware.com/opensource/opensource.html > >>>> > >>>> Please keep messages on-topic and check the ParaView Wiki at: > >>>> http://paraview.org/Wiki/ParaView > >>>> > >>>> Follow this link to subscribe/unsubscribe: > >>>> http://public.kitware.com/mailman/listinfo/paraview > >> _______________________________________________ > >> Powered by www.kitware.com > >> > >> Visit other Kitware open-source projects at > >> http://www.kitware.com/opensource/opensource.html > >> > >> Please keep messages on-topic and check the ParaView Wiki at: > >> http://paraview.org/Wiki/ParaView > >> > >> Follow this link to subscribe/unsubscribe: > >> http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From samuelkey at bresnan.net Mon Oct 13 13:17:06 2014 From: samuelkey at bresnan.net (Samuel Key) Date: Mon, 13 Oct 2014 11:17:06 -0600 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: References: <543BDF78.3090909@xs4all.nl> Message-ID: <543C0912.5080807@bresnan.net> Cory, Bertwin, et al.; The exact volume of an arbitrarily oriented, arbitrary 8-vertex hexahedron can be computed with a very elementary construct. First, place an average-coordinate point at the center of the hexahedron; this point will be a common vertex point for a set of tetrahedrons whose construction follows. Second, visiting the six faces of the hexahedron, place an average-coordinate point at the center of the quadrilateral polygonal face. For each of the four triangles, construct the four tetrahedrons using the center point above of the parent hexahedron. The only limitation is that the arbitrary 8-vertex hexhedron must be star-convex with respect to the hexaheron's average-coordinate center point. This construct works for triangular prisms and pyramids with a quadrilateral base. Once one has the coordinates of four vertex nodes defining a tetrahedron, the volume calculation of a tetrahedron is straight forward. Clearly, the total volume of the hexahedron is the sum of its 24 tetrahedral decomposition volumes. If an n-vertex polyhedron finite element's mean quadrature gradient operator is constructed the same way as above, then the above construct works for the n-vertex polyhedron. If an iso-surface transects the edges of an 8-node hexahedron and the resulting two sibling n-vertex polyhedrons are used as individual finite elements (which has been done), then the the above construct also provides exact volume fractions with respect to the two sibling n-vertex polyhedrons. The polygonal intersection surface need not be planar surface. If multiple, non-intersecting iso-surfaces transect a hexahedron, then the respective volume fractions within the hexahedron can exactly be calculated inductively. Cory, If you want to follow up off-line, I can provide a more lengthy write up with references plus example coding. Because of computational costs, I don't recommend this algorithm except in a user-invoked filter. Samuel W Key FMA Development, LLC 1005 39th Ave NE Great Falls, Montana 59404 On 10/13/2014 9:36 AM, Cory Quammen wrote: > Bertwim, > > I'm not sure that the volume renderer can handle VTK_HEXAHEDRON > elements. Try the "Tetrahedralize" filter on your source and see if > the Volume representation works. > > Thanks, > Cory > > On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest wrote: >> Hi, >> >> I'm struggling to get a proper 3D view of my model system (yes, >> embarrassing!) >> but must admit my defeat. >> After stripping almost everything, keeping the minimum to exhibit the >> issue, >> I'm left with the following: >> >> I have created a simple box source. To get a 3D representation, I >> sub-classed >> the code for this Source from vtkUnstructuredGridAlgorithm. >> >> In the RequestData method, I define the 8 point of the unit cube. I >> added the points to the >> underlying unstructed grid, and I specified the cell topology. >> >> This all seems to work: when instantiating this box Source, I *do* get the >> expected cube in the representations (Surface, wireframe, Points). >> >> However, when I select the "Volume" representation, *the image disappears* >> What am I doing wrong? >> >> As the code is not too long and very simple, I take the freedom to paste >> it below. >> >> Kind regards. >> Bertwim >> >> ========================================= >> >> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), >> vtkInformationVector >> **vtkNotUsed(inputVector), >> vtkInformationVector *outputVector) >> { >> // Get the info object >> vtkInformation *outInfo = outputVector->GetInformationObject(0); >> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( >> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); >> >> // Pre-allocate some memory >> umesh->Allocate( 1024 ); >> >> // Specify points. >> double r0[] = { 0.0, 0.0, 0.0 }; >> double r1[] = { 1.0, 0.0, 0.0 }; >> double r2[] = { 0.0, 1.0, 0.0 }; >> double r3[] = { 1.0, 1.0, 0.0 }; >> double r4[] = { 0.0, 0.0, 1.0 }; >> double r5[] = { 1.0, 0.0, 1.0 }; >> double r6[] = { 0.0, 1.0, 1.0 }; >> double r7[] = { 1.0, 1.0, 1.0 }; >> >> // Collect the points in a vtk data structures. >> { >> vtkSmartPointer points = vtkSmartPointer::New(); >> points->SetDataType( VTK_DOUBLE ); >> >> points->InsertNextPoint( r0 ); >> points->InsertNextPoint( r1 ); >> points->InsertNextPoint( r2 ); >> points->InsertNextPoint( r3 ); >> points->InsertNextPoint( r4 ); >> points->InsertNextPoint( r5 ); >> points->InsertNextPoint( r6 ); >> points->InsertNextPoint( r7 ); >> >> // Transfer points to umesh. >> umesh->SetPoints( points ); >> } >> >> // Cell Topology >> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; >> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); >> >> return 1; >> } >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From bwvb at xs4all.nl Mon Oct 13 14:29:34 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 20:29:34 +0200 Subject: [Paraview] Disappearing volume rendering? In-Reply-To: <543C0912.5080807@bresnan.net> References: <543BDF78.3090909@xs4all.nl> <543C0912.5080807@bresnan.net> Message-ID: <543C1A0E.3050308@xs4all.nl> Samuel, Thanks for taking the efforts to dive into this. In fact, it is a good reminder to me to try a single tetraeder first. My primary problem seems to be that I cannot get volume rendering to work. Kind Regards, Bertwim On 10/13/2014 07:17 PM, Samuel Key wrote: > Cory, Bertwin, et al.; > > The exact volume of an arbitrarily oriented, arbitrary 8-vertex > hexahedron can be computed with a very elementary construct. > > First, place an average-coordinate point at the center of the > hexahedron; this point will be a common vertex point for a set of > tetrahedrons whose construction follows. > > Second, visiting the six faces of the hexahedron, place an > average-coordinate point at the center of the quadrilateral polygonal > face. > For each of the four triangles, construct the four tetrahedrons using > the center point above of the parent hexahedron. > > The only limitation is that the arbitrary 8-vertex hexhedron must be > star-convex with respect to the hexaheron's average-coordinate center > point. This construct works for triangular prisms and pyramids with a > quadrilateral base. > > Once one has the coordinates of four vertex nodes defining a > tetrahedron, the volume calculation of a tetrahedron is straight > forward. Clearly, the total volume of the hexahedron is the sum of its > 24 tetrahedral decomposition volumes. > > If an n-vertex polyhedron finite element's mean quadrature gradient > operator is constructed the same way as above, then the above > construct works for the n-vertex polyhedron. > > If an iso-surface transects the edges of an 8-node hexahedron and the > resulting two sibling n-vertex polyhedrons are used as individual > finite elements (which has been done), then the the above construct > also provides exact volume fractions with respect to the two sibling > n-vertex polyhedrons. The polygonal intersection surface need not be > planar surface. > > If multiple, non-intersecting iso-surfaces transect a hexahedron, then > the respective volume fractions within the hexahedron can exactly be > calculated inductively. > > Cory, If you want to follow up off-line, I can provide a more lengthy > write up with references plus example coding. Because of computational > costs, I don't recommend this algorithm except in a user-invoked filter. > > Samuel W Key > FMA Development, LLC > 1005 39th Ave NE > Great Falls, Montana 59404 > > > > > On 10/13/2014 9:36 AM, Cory Quammen wrote: >> Bertwim, >> >> I'm not sure that the volume renderer can handle VTK_HEXAHEDRON >> elements. Try the "Tetrahedralize" filter on your source and see if >> the Volume representation works. >> >> Thanks, >> Cory >> >> On Mon, Oct 13, 2014 at 10:19 AM, B.W.H. van Beest >> wrote: >>> Hi, >>> >>> I'm struggling to get a proper 3D view of my model system (yes, >>> embarrassing!) >>> but must admit my defeat. >>> After stripping almost everything, keeping the minimum to exhibit the >>> issue, >>> I'm left with the following: >>> >>> I have created a simple box source. To get a 3D representation, I >>> sub-classed >>> the code for this Source from vtkUnstructuredGridAlgorithm. >>> >>> In the RequestData method, I define the 8 point of the unit cube. I >>> added the points to the >>> underlying unstructed grid, and I specified the cell topology. >>> >>> This all seems to work: when instantiating this box Source, I *do* >>> get the >>> expected cube in the representations (Surface, wireframe, Points). >>> >>> However, when I select the "Volume" representation, *the image >>> disappears* >>> What am I doing wrong? >>> >>> As the code is not too long and very simple, I take the freedom to >>> paste >>> it below. >>> >>> Kind regards. >>> Bertwim >>> >>> ========================================= >>> >>> int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), >>> vtkInformationVector >>> **vtkNotUsed(inputVector), >>> vtkInformationVector *outputVector) >>> { >>> // Get the info object >>> vtkInformation *outInfo = outputVector->GetInformationObject(0); >>> vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( >>> outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); >>> >>> // Pre-allocate some memory >>> umesh->Allocate( 1024 ); >>> >>> // Specify points. >>> double r0[] = { 0.0, 0.0, 0.0 }; >>> double r1[] = { 1.0, 0.0, 0.0 }; >>> double r2[] = { 0.0, 1.0, 0.0 }; >>> double r3[] = { 1.0, 1.0, 0.0 }; >>> double r4[] = { 0.0, 0.0, 1.0 }; >>> double r5[] = { 1.0, 0.0, 1.0 }; >>> double r6[] = { 0.0, 1.0, 1.0 }; >>> double r7[] = { 1.0, 1.0, 1.0 }; >>> >>> // Collect the points in a vtk data structures. >>> { >>> vtkSmartPointer points = >>> vtkSmartPointer::New(); >>> points->SetDataType( VTK_DOUBLE ); >>> >>> points->InsertNextPoint( r0 ); >>> points->InsertNextPoint( r1 ); >>> points->InsertNextPoint( r2 ); >>> points->InsertNextPoint( r3 ); >>> points->InsertNextPoint( r4 ); >>> points->InsertNextPoint( r5 ); >>> points->InsertNextPoint( r6 ); >>> points->InsertNextPoint( r7 ); >>> >>> // Transfer points to umesh. >>> umesh->SetPoints( points ); >>> } >>> >>> // Cell Topology >>> vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; >>> umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); >>> >>> return 1; >>> } >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From bwvb at xs4all.nl Mon Oct 13 14:44:47 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 13 Oct 2014 20:44:47 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> Message-ID: <543C1D9F.5070803@xs4all.nl> OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, GL_ARB_texture_float, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc OpenGL version string: 3.0 Mesa 9.2.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_texture_array, GL_MESA_texture_signed_rgba, GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, GL_NV_primitive_restart, GL_NV_texgen_reflection, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays 20 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 44 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: > What graphics card / graphics driver version / OS this system has? > > - Aashish > > On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest > wrote: > > Hi Aashish, > > This is what I do: > 1. start paraview > 2. Sources -> Wavelet -> Apply. > A cube is displayed (Outline representation). > 3. Select 'Volume" representation" > > cube disappears. Then: > ===================== > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > ========================= > > > > > > > On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >> So when you created a wavelet source and change the >> representation to volume you got the errors? Can you post those >> errors? >> >> Thanks, >> >> >> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest > > wrote: >> >> Aashish, >> >> Thanks for the suggestion. >> >> However, doing this gives me all kinds of opengl errors >> (invalid instruction). >> >> Besides that, the wavelet gives me a cube indeed, but I need >> to understand when >> I can have a volume rendering. I created new Source's (e.g. >> tri-prism, a wedge, >> a box with boundaries of finite thickness etc.). But I cannot >> get volume rendering >> to work, grrrrrr. (See other thread) >> >> Kind Regards, >> Bertwim >> >> >> >> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>> You can create a wavelet source and then display it as a >>> volume. >>> >>> >>> >>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>> > wrote: >>> >>> Can perhaps somebody point me how to address the following. >>> >>> When I create a new source (say: a box) I get an a box that >>> can be displayed via its surfaces, its constituing >>> points, or wireframe >>> representation. >>> But I need a volume rendering (so that I can add e.g. a >>> clipping plane) >>> How do I get that? >>> >>> Regards, >>> Bertwim >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView >>> Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.m.edwards at gmail.com Mon Oct 13 18:13:43 2014 From: paul.m.edwards at gmail.com (Paul Edwards) Date: Mon, 13 Oct 2014 23:13:43 +0100 Subject: [Paraview] XMLUnstructuredGridWriter and VTK_POLYHEDRON elements In-Reply-To: References: Message-ID: Hi Joe, I've seen this before and there is a bug report in mantis here: http://www.paraview.org/Bug/view.php?id=13382 There has also been a patch posted to the vtk-developers list a while back although I haven't tested it: http://markmail.org/message/zg3damrg27p5sgue Regards, Paul On 10 October 2014 00:32, Insley, Joseph A. wrote: > Hi, > > I have a serial vtu dataset provided by one of my users. Their current > code can produce this in either ascii or inline binary. I am currently > trying to convert this to appended binary (ultimately to pvtu with appended > binary). > I'm having trouble, which I now believe may stem from the data containing > VTK_POLYHEDRON. > > I have a simple python script that I use with pvbatch to do this > conversion, but I see the same results when I load the original data set > with ParaView (4.1.0, in client/server mode), and use the Save Data option > and save as vtu. > I get the same results for each input format (ascii or inline binary), and > output format (ascii, binary, appended). > > The first few lines of the original vtu file look like this: > > > > > > > The first few lines of the converted file look like this: > > offset="177748206"ructuredGrid" version="0.1" byte_order="LittleEndian"> > > > > > > Something is clearly getting jumbled at the beginning of the converted > file. If I manually edit the header of the file to read type="UnstructuredGrid", there are still problems with the file. In that > case the info tab in ParaView reports the correct number of points and > cells, but no geometry is drawn. I have successfully converted other vtu > files using this same method. The primary difference that I've been able > to identify is that the files that are not converting happily contain > VTK_POLYHEDRON elements. > > Has anyone else seen similar behavior? > > Thanks, > joe > > =================================================== > joseph a. insley > insley at anl.gov > argonne leadership computing facility (630) > 252-5649 > argonne national laboratory > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Tue Oct 14 08:12:10 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Tue, 14 Oct 2014 12:12:10 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: When doing a clean production build, it?s very useful to be able to do a ?git pull? to get all of the correct tarballs downloaded. The functionality that was previous to 4.2.0 was exactly appropriate - ?git checkout v4.1.0? The alternative (as I understand it) is to enable GIT and do a build from the development tree. (This will pull all of the tarballs for the supporting libraries). Then re-run the build with ?GIT=OFF? , manually download the production tarball, and then re-run the build. Does this sound like the best solution? __________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 On 10/11/14, 6:04 PM, "Cory Quammen" wrote: >Hi Simon, > >What you are doing as a workaround is indeed how production builds >should be created. The ParaView superbuild is now set up to check out >the master branch of ParaView, which varies day to day. In 4.1 and >prior to that, it was set up to check out out the release branch, >which was far more static. If you disable ParaView_FROM_GIT in CMake, >it will download the release source tar ball and build from that, >essentially what you have been doing. > >I'll update the superbuild wiki instructions to note this. > >Best regards, >Cory > >On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) > wrote: >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> Hello, >> >> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to >> build a specific version, I will do >> >> git clone git://paraview.org/ParaViewSuperbuild.git >> cd ParaViewSuperbuild >> git checkout v4.1.0 >> >> That has always worked for me for v4.1.0 tag >> >> But with v4.2.0 release, if I do the following on different days, >> >> git clone git://paraview.org/ParaViewSuperbuild.git >> cd ParaViewSuperbuild >> git checkout v4.2.0 >> >> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. >>Am I >> missing something? This is causing me problem when I am trying to get >>the >> same version of ParaView mesa and osmesa build for client/server mode. >>I end >> up doing a >> >> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >> >> To get around the problem. Thoughts? >> >> >> Thanks >> -simon >> >> >> >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >>http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >>http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Oct 14 08:45:26 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Oct 2014 08:45:26 -0400 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Rick, Are you taking referring to the "v4.1.0" tag on the superbuild repo? I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about that. Utkarsh On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > When doing a clean production build, it?s very useful to be able to do a > ?git pull? to get all of the correct tarballs downloaded. The > functionality that was previous to 4.2.0 was exactly appropriate - ?git > checkout v4.1.0? > > The alternative (as I understand it) is to enable GIT and do a build from > the development tree. (This will pull all of the tarballs for the > supporting libraries). Then re-run the build with ?GIT=OFF? , manually > download the production tarball, and then re-run the build. Does this > sound like the best solution? > > > > > > > __________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > On 10/11/14, 6:04 PM, "Cory Quammen" wrote: > >>Hi Simon, >> >>What you are doing as a workaround is indeed how production builds >>should be created. The ParaView superbuild is now set up to check out >>the master branch of ParaView, which varies day to day. In 4.1 and >>prior to that, it was set up to check out out the release branch, >>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>it will download the release source tar ball and build from that, >>essentially what you have been doing. >> >>I'll update the superbuild wiki instructions to note this. >> >>Best regards, >>Cory >> >>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >> wrote: >>> Classification: UNCLASSIFIED >>> Caveats: NONE >>> >>> Hello, >>> >>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want to >>> build a specific version, I will do >>> >>> git clone git://paraview.org/ParaViewSuperbuild.git >>> cd ParaViewSuperbuild >>> git checkout v4.1.0 >>> >>> That has always worked for me for v4.1.0 tag >>> >>> But with v4.2.0 release, if I do the following on different days, >>> >>> git clone git://paraview.org/ParaViewSuperbuild.git >>> cd ParaViewSuperbuild >>> git checkout v4.2.0 >>> >>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. >>>Am I >>> missing something? This is causing me problem when I am trying to get >>>the >>> same version of ParaView mesa and osmesa build for client/server mode. >>>I end >>> up doing a >>> >>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>> >>> To get around the problem. Thoughts? >>> >>> >>> Thanks >>> -simon >>> >>> >>> >>> >>> Classification: UNCLASSIFIED >>> Caveats: NONE >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>>http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>>http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>_______________________________________________ >>Powered by www.kitware.com >> >>Visit other Kitware open-source projects at >>http://www.kitware.com/opensource/opensource.html >> >>Please keep messages on-topic and check the ParaView Wiki at: >>http://paraview.org/Wiki/ParaView >> >>Follow this link to subscribe/unsubscribe: >>http://public.kitware.com/mailman/listinfo/paraview > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From richard.c.angelini.civ at mail.mil Tue Oct 14 08:49:34 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Tue, 14 Oct 2014 12:49:34 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Yes - we want the 4.2.0 tag on the Superbuild (and for all future production releases). In an earlier message on the this thread, Corey implied that it was no longer supported ?. of course, at this point we?re more or less done with the 4.2.0 implementation. Next time, it would be nice to have when the production release is announced! 8-) ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 On 10/14/14, 8:45 AM, "Utkarsh Ayachit" wrote: >Rick, > >Are you taking referring to the "v4.1.0" tag on the superbuild repo? >I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about >that. > >Utkarsh > >On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY >ARL (US) wrote: >> When doing a clean production build, it?s very useful to be able to do >>a >> ?git pull? to get all of the correct tarballs downloaded. The >> functionality that was previous to 4.2.0 was exactly appropriate - ?git >> checkout v4.1.0? >> >> The alternative (as I understand it) is to enable GIT and do a build >>from >> the development tree. (This will pull all of the tarballs for the >> supporting libraries). Then re-run the build with ?GIT=OFF? , manually >> download the production tarball, and then re-run the build. Does this >> sound like the best solution? >> >> >> >> >> >> >> __________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> On 10/11/14, 6:04 PM, "Cory Quammen" wrote: >> >>>Hi Simon, >>> >>>What you are doing as a workaround is indeed how production builds >>>should be created. The ParaView superbuild is now set up to check out >>>the master branch of ParaView, which varies day to day. In 4.1 and >>>prior to that, it was set up to check out out the release branch, >>>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>>it will download the release source tar ball and build from that, >>>essentially what you have been doing. >>> >>>I'll update the superbuild wiki instructions to note this. >>> >>>Best regards, >>>Cory >>> >>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>> wrote: >>>> Classification: UNCLASSIFIED >>>> Caveats: NONE >>>> >>>> Hello, >>>> >>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want >>>>to >>>> build a specific version, I will do >>>> >>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>> cd ParaViewSuperbuild >>>> git checkout v4.1.0 >>>> >>>> That has always worked for me for v4.1.0 tag >>>> >>>> But with v4.2.0 release, if I do the following on different days, >>>> >>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>> cd ParaViewSuperbuild >>>> git checkout v4.2.0 >>>> >>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. >>>>Am I >>>> missing something? This is causing me problem when I am trying to get >>>>the >>>> same version of ParaView mesa and osmesa build for client/server mode. >>>>I end >>>> up doing a >>>> >>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>> >>>> To get around the problem. Thoughts? >>>> >>>> >>>> Thanks >>>> -simon >>>> >>>> >>>> >>>> >>>> Classification: UNCLASSIFIED >>>> Caveats: NONE >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>>http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>_______________________________________________ >>>Powered by www.kitware.com >>> >>>Visit other Kitware open-source projects at >>>http://www.kitware.com/opensource/opensource.html >>> >>>Please keep messages on-topic and check the ParaView Wiki at: >>>http://paraview.org/Wiki/ParaView >>> >>>Follow this link to subscribe/unsubscribe: >>>http://public.kitware.com/mailman/listinfo/paraview >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >>http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >>http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Tue Oct 14 08:51:14 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Oct 2014 08:51:14 -0400 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Doh! I see I added the tag but forgot to toggle the git/branch name, which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1" tag fixing this issue. Again, really sorry about this :/. Utkarsh On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > Yes - we want the 4.2.0 tag on the Superbuild (and for all future > production releases). In an earlier message on the this thread, Corey > implied that it was no longer supported ?. of course, at this point we?re > more or less done with the 4.2.0 implementation. Next time, it would be > nice to have when the production release is announced! 8-) > > > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > On 10/14/14, 8:45 AM, "Utkarsh Ayachit" > wrote: > >>Rick, >> >>Are you taking referring to the "v4.1.0" tag on the superbuild repo? >>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about >>that. >> >>Utkarsh >> >>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY >>ARL (US) wrote: >>> When doing a clean production build, it?s very useful to be able to do >>>a >>> ?git pull? to get all of the correct tarballs downloaded. The >>> functionality that was previous to 4.2.0 was exactly appropriate - ?git >>> checkout v4.1.0? >>> >>> The alternative (as I understand it) is to enable GIT and do a build >>>from >>> the development tree. (This will pull all of the tarballs for the >>> supporting libraries). Then re-run the build with ?GIT=OFF? , manually >>> download the production tarball, and then re-run the build. Does this >>> sound like the best solution? >>> >>> >>> >>> >>> >>> >>> __________________ >>> Rick Angelini >>> USArmy Research Laboratory >>> CISD/HPC Architectures Team >>> Phone: 410-278-6266 >>> >>> >>> >>> >>> On 10/11/14, 6:04 PM, "Cory Quammen" wrote: >>> >>>>Hi Simon, >>>> >>>>What you are doing as a workaround is indeed how production builds >>>>should be created. The ParaView superbuild is now set up to check out >>>>the master branch of ParaView, which varies day to day. In 4.1 and >>>>prior to that, it was set up to check out out the release branch, >>>>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>>>it will download the release source tar ball and build from that, >>>>essentially what you have been doing. >>>> >>>>I'll update the superbuild wiki instructions to note this. >>>> >>>>Best regards, >>>>Cory >>>> >>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>>> wrote: >>>>> Classification: UNCLASSIFIED >>>>> Caveats: NONE >>>>> >>>>> Hello, >>>>> >>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want >>>>>to >>>>> build a specific version, I will do >>>>> >>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>> cd ParaViewSuperbuild >>>>> git checkout v4.1.0 >>>>> >>>>> That has always worked for me for v4.1.0 tag >>>>> >>>>> But with v4.2.0 release, if I do the following on different days, >>>>> >>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>> cd ParaViewSuperbuild >>>>> git checkout v4.2.0 >>>>> >>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. >>>>>Am I >>>>> missing something? This is causing me problem when I am trying to get >>>>>the >>>>> same version of ParaView mesa and osmesa build for client/server mode. >>>>>I end >>>>> up doing a >>>>> >>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>>> >>>>> To get around the problem. Thoughts? >>>>> >>>>> >>>>> Thanks >>>>> -simon >>>>> >>>>> >>>>> >>>>> >>>>> Classification: UNCLASSIFIED >>>>> Caveats: NONE >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>>http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>_______________________________________________ >>>>Powered by www.kitware.com >>>> >>>>Visit other Kitware open-source projects at >>>>http://www.kitware.com/opensource/opensource.html >>>> >>>>Please keep messages on-topic and check the ParaView Wiki at: >>>>http://paraview.org/Wiki/ParaView >>>> >>>>Follow this link to subscribe/unsubscribe: >>>>http://public.kitware.com/mailman/listinfo/paraview >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>>http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>>http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Tue Oct 14 08:57:39 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Oct 2014 08:57:39 -0400 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Tag "v4.2.0-1" is now available on the ParaView Superbuild repo. Utkarsh On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit wrote: > Doh! I see I added the tag but forgot to toggle the git/branch name, > which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1" > tag fixing this issue. > > Again, really sorry about this :/. > > Utkarsh > > On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY > ARL (US) wrote: >> Yes - we want the 4.2.0 tag on the Superbuild (and for all future >> production releases). In an earlier message on the this thread, Corey >> implied that it was no longer supported ?. of course, at this point we?re >> more or less done with the 4.2.0 implementation. Next time, it would be >> nice to have when the production release is announced! 8-) >> >> >> >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> On 10/14/14, 8:45 AM, "Utkarsh Ayachit" >> wrote: >> >>>Rick, >>> >>>Are you taking referring to the "v4.1.0" tag on the superbuild repo? >>>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about >>>that. >>> >>>Utkarsh >>> >>>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY >>>ARL (US) wrote: >>>> When doing a clean production build, it?s very useful to be able to do >>>>a >>>> ?git pull? to get all of the correct tarballs downloaded. The >>>> functionality that was previous to 4.2.0 was exactly appropriate - ?git >>>> checkout v4.1.0? >>>> >>>> The alternative (as I understand it) is to enable GIT and do a build >>>>from >>>> the development tree. (This will pull all of the tarballs for the >>>> supporting libraries). Then re-run the build with ?GIT=OFF? , manually >>>> download the production tarball, and then re-run the build. Does this >>>> sound like the best solution? >>>> >>>> >>>> >>>> >>>> >>>> >>>> __________________ >>>> Rick Angelini >>>> USArmy Research Laboratory >>>> CISD/HPC Architectures Team >>>> Phone: 410-278-6266 >>>> >>>> >>>> >>>> >>>> On 10/11/14, 6:04 PM, "Cory Quammen" wrote: >>>> >>>>>Hi Simon, >>>>> >>>>>What you are doing as a workaround is indeed how production builds >>>>>should be created. The ParaView superbuild is now set up to check out >>>>>the master branch of ParaView, which varies day to day. In 4.1 and >>>>>prior to that, it was set up to check out out the release branch, >>>>>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>>>>it will download the release source tar ball and build from that, >>>>>essentially what you have been doing. >>>>> >>>>>I'll update the superbuild wiki instructions to note this. >>>>> >>>>>Best regards, >>>>>Cory >>>>> >>>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>>>> wrote: >>>>>> Classification: UNCLASSIFIED >>>>>> Caveats: NONE >>>>>> >>>>>> Hello, >>>>>> >>>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I want >>>>>>to >>>>>> build a specific version, I will do >>>>>> >>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>> cd ParaViewSuperbuild >>>>>> git checkout v4.1.0 >>>>>> >>>>>> That has always worked for me for v4.1.0 tag >>>>>> >>>>>> But with v4.2.0 release, if I do the following on different days, >>>>>> >>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>> cd ParaViewSuperbuild >>>>>> git checkout v4.2.0 >>>>>> >>>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every time. >>>>>>Am I >>>>>> missing something? This is causing me problem when I am trying to get >>>>>>the >>>>>> same version of ParaView mesa and osmesa build for client/server mode. >>>>>>I end >>>>>> up doing a >>>>>> >>>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>>>> >>>>>> To get around the problem. Thoughts? >>>>>> >>>>>> >>>>>> Thanks >>>>>> -simon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Classification: UNCLASSIFIED >>>>>> Caveats: NONE >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>>http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>_______________________________________________ >>>>>Powered by www.kitware.com >>>>> >>>>>Visit other Kitware open-source projects at >>>>>http://www.kitware.com/opensource/opensource.html >>>>> >>>>>Please keep messages on-topic and check the ParaView Wiki at: >>>>>http://paraview.org/Wiki/ParaView >>>>> >>>>>Follow this link to subscribe/unsubscribe: >>>>>http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>>http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >> From richard.c.angelini.civ at mail.mil Tue Oct 14 09:07:04 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Tue, 14 Oct 2014 13:07:04 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Should you also update the Paraview SuperBuild wiki page? ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 On 10/14/14, 8:57 AM, "Utkarsh Ayachit" wrote: >Tag "v4.2.0-1" is now available on the ParaView Superbuild repo. > >Utkarsh > > >On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit > wrote: >> Doh! I see I added the tag but forgot to toggle the git/branch name, >> which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1" >> tag fixing this issue. >> >> Again, really sorry about this :/. >> >> Utkarsh >> >> On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY >> ARL (US) wrote: >>> Yes - we want the 4.2.0 tag on the Superbuild (and for all future >>> production releases). In an earlier message on the this thread, Corey >>> implied that it was no longer supported ?. of course, at this point >>>we?re >>> more or less done with the 4.2.0 implementation. Next time, it would >>>be >>> nice to have when the production release is announced! 8-) >>> >>> >>> >>> ________________________________ >>> Rick Angelini >>> USArmy Research Laboratory >>> CISD/HPC Architectures Team >>> Phone: 410-278-6266 >>> >>> >>> >>> >>> On 10/14/14, 8:45 AM, "Utkarsh Ayachit" >>> wrote: >>> >>>>Rick, >>>> >>>>Are you taking referring to the "v4.1.0" tag on the superbuild repo? >>>>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about >>>>that. >>>> >>>>Utkarsh >>>> >>>>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY >>>>ARL (US) wrote: >>>>> When doing a clean production build, it?s very useful to be able to >>>>>do >>>>>a >>>>> ?git pull? to get all of the correct tarballs downloaded. The >>>>> functionality that was previous to 4.2.0 was exactly appropriate - >>>>>?git >>>>> checkout v4.1.0? >>>>> >>>>> The alternative (as I understand it) is to enable GIT and do a build >>>>>from >>>>> the development tree. (This will pull all of the tarballs for the >>>>> supporting libraries). Then re-run the build with ?GIT=OFF? , >>>>>manually >>>>> download the production tarball, and then re-run the build. Does >>>>>this >>>>> sound like the best solution? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> __________________ >>>>> Rick Angelini >>>>> USArmy Research Laboratory >>>>> CISD/HPC Architectures Team >>>>> Phone: 410-278-6266 >>>>> >>>>> >>>>> >>>>> >>>>> On 10/11/14, 6:04 PM, "Cory Quammen" >>>>>wrote: >>>>> >>>>>>Hi Simon, >>>>>> >>>>>>What you are doing as a workaround is indeed how production builds >>>>>>should be created. The ParaView superbuild is now set up to check out >>>>>>the master branch of ParaView, which varies day to day. In 4.1 and >>>>>>prior to that, it was set up to check out out the release branch, >>>>>>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>>>>>it will download the release source tar ball and build from that, >>>>>>essentially what you have been doing. >>>>>> >>>>>>I'll update the superbuild wiki instructions to note this. >>>>>> >>>>>>Best regards, >>>>>>Cory >>>>>> >>>>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>>>>> wrote: >>>>>>> Classification: UNCLASSIFIED >>>>>>> Caveats: NONE >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I >>>>>>>want >>>>>>>to >>>>>>> build a specific version, I will do >>>>>>> >>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>> cd ParaViewSuperbuild >>>>>>> git checkout v4.1.0 >>>>>>> >>>>>>> That has always worked for me for v4.1.0 tag >>>>>>> >>>>>>> But with v4.2.0 release, if I do the following on different days, >>>>>>> >>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>> cd ParaViewSuperbuild >>>>>>> git checkout v4.2.0 >>>>>>> >>>>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every >>>>>>>time. >>>>>>>Am I >>>>>>> missing something? This is causing me problem when I am trying to >>>>>>>get >>>>>>>the >>>>>>> same version of ParaView mesa and osmesa build for client/server >>>>>>>mode. >>>>>>>I end >>>>>>> up doing a >>>>>>> >>>>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>>>>> >>>>>>> To get around the problem. Thoughts? >>>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> -simon >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Classification: UNCLASSIFIED >>>>>>> Caveats: NONE >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>>http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>_______________________________________________ >>>>>>Powered by www.kitware.com >>>>>> >>>>>>Visit other Kitware open-source projects at >>>>>>http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>>Please keep messages on-topic and check the ParaView Wiki at: >>>>>>http://paraview.org/Wiki/ParaView >>>>>> >>>>>>Follow this link to subscribe/unsubscribe: >>>>>>http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>>http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>> From utkarsh.ayachit at kitware.com Tue Oct 14 09:10:48 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Oct 2014 09:10:48 -0400 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Yup :)...all set. On Tue, Oct 14, 2014 at 9:07 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > Should you also update the Paraview SuperBuild wiki page? > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > On 10/14/14, 8:57 AM, "Utkarsh Ayachit" > wrote: > >>Tag "v4.2.0-1" is now available on the ParaView Superbuild repo. >> >>Utkarsh >> >> >>On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit >> wrote: >>> Doh! I see I added the tag but forgot to toggle the git/branch name, >>> which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1" >>> tag fixing this issue. >>> >>> Again, really sorry about this :/. >>> >>> Utkarsh >>> >>> On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV USARMY >>> ARL (US) wrote: >>>> Yes - we want the 4.2.0 tag on the Superbuild (and for all future >>>> production releases). In an earlier message on the this thread, Corey >>>> implied that it was no longer supported ?. of course, at this point >>>>we?re >>>> more or less done with the 4.2.0 implementation. Next time, it would >>>>be >>>> nice to have when the production release is announced! 8-) >>>> >>>> >>>> >>>> ________________________________ >>>> Rick Angelini >>>> USArmy Research Laboratory >>>> CISD/HPC Architectures Team >>>> Phone: 410-278-6266 >>>> >>>> >>>> >>>> >>>> On 10/14/14, 8:45 AM, "Utkarsh Ayachit" >>>> wrote: >>>> >>>>>Rick, >>>>> >>>>>Are you taking referring to the "v4.1.0" tag on the superbuild repo? >>>>>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry about >>>>>that. >>>>> >>>>>Utkarsh >>>>> >>>>>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV USARMY >>>>>ARL (US) wrote: >>>>>> When doing a clean production build, it?s very useful to be able to >>>>>>do >>>>>>a >>>>>> ?git pull? to get all of the correct tarballs downloaded. The >>>>>> functionality that was previous to 4.2.0 was exactly appropriate - >>>>>>?git >>>>>> checkout v4.1.0? >>>>>> >>>>>> The alternative (as I understand it) is to enable GIT and do a build >>>>>>from >>>>>> the development tree. (This will pull all of the tarballs for the >>>>>> supporting libraries). Then re-run the build with ?GIT=OFF? , >>>>>>manually >>>>>> download the production tarball, and then re-run the build. Does >>>>>>this >>>>>> sound like the best solution? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> __________________ >>>>>> Rick Angelini >>>>>> USArmy Research Laboratory >>>>>> CISD/HPC Architectures Team >>>>>> Phone: 410-278-6266 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 10/11/14, 6:04 PM, "Cory Quammen" >>>>>>wrote: >>>>>> >>>>>>>Hi Simon, >>>>>>> >>>>>>>What you are doing as a workaround is indeed how production builds >>>>>>>should be created. The ParaView superbuild is now set up to check out >>>>>>>the master branch of ParaView, which varies day to day. In 4.1 and >>>>>>>prior to that, it was set up to check out out the release branch, >>>>>>>which was far more static. If you disable ParaView_FROM_GIT in CMake, >>>>>>>it will download the release source tar ball and build from that, >>>>>>>essentially what you have been doing. >>>>>>> >>>>>>>I'll update the superbuild wiki instructions to note this. >>>>>>> >>>>>>>Best regards, >>>>>>>Cory >>>>>>> >>>>>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>>>>>> wrote: >>>>>>>> Classification: UNCLASSIFIED >>>>>>>> Caveats: NONE >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if I >>>>>>>>want >>>>>>>>to >>>>>>>> build a specific version, I will do >>>>>>>> >>>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>>> cd ParaViewSuperbuild >>>>>>>> git checkout v4.1.0 >>>>>>>> >>>>>>>> That has always worked for me for v4.1.0 tag >>>>>>>> >>>>>>>> But with v4.2.0 release, if I do the following on different days, >>>>>>>> >>>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>>> cd ParaViewSuperbuild >>>>>>>> git checkout v4.2.0 >>>>>>>> >>>>>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every >>>>>>>>time. >>>>>>>>Am I >>>>>>>> missing something? This is causing me problem when I am trying to >>>>>>>>get >>>>>>>>the >>>>>>>> same version of ParaView mesa and osmesa build for client/server >>>>>>>>mode. >>>>>>>>I end >>>>>>>> up doing a >>>>>>>> >>>>>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>>>>>> >>>>>>>> To get around the problem. Thoughts? >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> -simon >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Classification: UNCLASSIFIED >>>>>>>> Caveats: NONE >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>>http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>_______________________________________________ >>>>>>>Powered by www.kitware.com >>>>>>> >>>>>>>Visit other Kitware open-source projects at >>>>>>>http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>>Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>>Follow this link to subscribe/unsubscribe: >>>>>>>http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>>http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> > From simon.m.su.ctr at mail.mil Tue Oct 14 10:54:32 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 14 Oct 2014 14:54:32 +0000 Subject: [Paraview] ParaView superbuild git question (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thanks Utkarsh -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, October 14, 2014 9:11 AM To: Angelini, Richard C (Rick) CIV USARMY ARL (US) Cc: Cory Quammen; Su, Simon M CTR USARMY ARL (US); paraview at paraview.org Subject: Re: [Paraview] ParaView superbuild git question (UNCLASSIFIED) Yup :)...all set. On Tue, Oct 14, 2014 at 9:07 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > Should you also update the Paraview SuperBuild wiki page? > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > On 10/14/14, 8:57 AM, "Utkarsh Ayachit" > wrote: > >>Tag "v4.2.0-1" is now available on the ParaView Superbuild repo. >> >>Utkarsh >> >> >>On Tue, Oct 14, 2014 at 8:51 AM, Utkarsh Ayachit >> wrote: >>> Doh! I see I added the tag but forgot to toggle the git/branch name, >>> which for 4.1.0 I had set to be "release". I'll add a new "v4.2.0-1" >>> tag fixing this issue. >>> >>> Again, really sorry about this :/. >>> >>> Utkarsh >>> >>> On Tue, Oct 14, 2014 at 8:49 AM, Angelini, Richard C (Rick) CIV >>> USARMY ARL (US) wrote: >>>> Yes - we want the 4.2.0 tag on the Superbuild (and for all future >>>> production releases). In an earlier message on the this thread, Corey >>>> implied that it was no longer supported ?. of course, at this >>>>point we?re more or less done with the 4.2.0 implementation. Next >>>>time, it would be >>>> nice to have when the production release is announced! 8-) >>>> >>>> >>>> >>>> ________________________________ >>>> Rick Angelini >>>> USArmy Research Laboratory >>>> CISD/HPC Architectures Team >>>> Phone: 410-278-6266 >>>> >>>> >>>> >>>> >>>> On 10/14/14, 8:45 AM, "Utkarsh Ayachit" >>>> >>>> wrote: >>>> >>>>>Rick, >>>>> >>>>>Are you taking referring to the "v4.1.0" tag on the superbuild repo? >>>>>I'll add the v4.2.0 tag soon -- it just slipped my mind. Sorry >>>>>about that. >>>>> >>>>>Utkarsh >>>>> >>>>>On Tue, Oct 14, 2014 at 8:12 AM, Angelini, Richard C (Rick) CIV >>>>>USARMY ARL (US) wrote: >>>>>> When doing a clean production build, it?s very useful to be able >>>>>>to do a >>>>>> ?git pull? to get all of the correct tarballs downloaded. The >>>>>> functionality that was previous to 4.2.0 was exactly appropriate >>>>>>- ?git checkout v4.1.0? >>>>>> >>>>>> The alternative (as I understand it) is to enable GIT and do a >>>>>>build from the development tree. (This will pull all of the >>>>>>tarballs for the >>>>>> supporting libraries). Then re-run the build with ?GIT=OFF? , >>>>>>manually >>>>>> download the production tarball, and then re-run the build. Does >>>>>>this >>>>>> sound like the best solution? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> __________________ >>>>>> Rick Angelini >>>>>> USArmy Research Laboratory >>>>>> CISD/HPC Architectures Team >>>>>> Phone: 410-278-6266 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 10/11/14, 6:04 PM, "Cory Quammen" >>>>>>wrote: >>>>>> >>>>>>>Hi Simon, >>>>>>> >>>>>>>What you are doing as a workaround is indeed how production >>>>>>>builds should be created. The ParaView superbuild is now set up >>>>>>>to check out the master branch of ParaView, which varies day to >>>>>>>day. In 4.1 and prior to that, it was set up to check out out the >>>>>>>release branch, which was far more static. If you disable >>>>>>>ParaView_FROM_GIT in CMake, it will download the release source >>>>>>>tar ball and build from that, essentially what you have been doing. >>>>>>> >>>>>>>I'll update the superbuild wiki instructions to note this. >>>>>>> >>>>>>>Best regards, >>>>>>>Cory >>>>>>> >>>>>>>On Fri, Oct 10, 2014 at 4:09 PM, Su, Simon M CTR USARMY ARL (US) >>>>>>> wrote: >>>>>>>> Classification: UNCLASSIFIED >>>>>>>> Caveats: NONE >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> http://www.paraview.org/Wiki/ParaView/Superbuild mentioned, if >>>>>>>>I want to build a specific version, I will do >>>>>>>> >>>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>>> cd ParaViewSuperbuild >>>>>>>> git checkout v4.1.0 >>>>>>>> >>>>>>>> That has always worked for me for v4.1.0 tag >>>>>>>> >>>>>>>> But with v4.2.0 release, if I do the following on different >>>>>>>> days, >>>>>>>> >>>>>>>> git clone git://paraview.org/ParaViewSuperbuild.git >>>>>>>> cd ParaViewSuperbuild >>>>>>>> git checkout v4.2.0 >>>>>>>> >>>>>>>> I am getting v4.2.0-${SOME HASH NUMBER} that is different every >>>>>>>>time. >>>>>>>>Am I >>>>>>>> missing something? This is causing me problem when I am trying >>>>>>>>to get the same version of ParaView mesa and osmesa build for >>>>>>>>client/server mode. >>>>>>>>I end >>>>>>>> up doing a >>>>>>>> >>>>>>>> -DParaView_URL=../paraview/ParaView-v4.2.0-source.tar.gz >>>>>>>> >>>>>>>> To get around the problem. Thoughts? >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> -simon >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Classification: UNCLASSIFIED >>>>>>>> Caveats: NONE >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>>http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>>http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>_______________________________________________ >>>>>>>Powered by www.kitware.com >>>>>>> >>>>>>>Visit other Kitware open-source projects at >>>>>>>http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>>Please keep messages on-topic and check the ParaView Wiki at: >>>>>>>http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>>Follow this link to subscribe/unsubscribe: >>>>>>>http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>>http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>>>http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From insley at anl.gov Tue Oct 14 11:37:56 2014 From: insley at anl.gov (Insley, Joseph A.) Date: Tue, 14 Oct 2014 15:37:56 +0000 Subject: [Paraview] XMLUnstructuredGridWriter and VTK_POLYHEDRON elements In-Reply-To: References: Message-ID: <46BDF76B-C0C7-4048-BE52-0FA12B3564F4@anl.gov> Hi, Paul, Thanks for the pointers. joe On Oct 13, 2014, at 5:13 PM, Paul Edwards > wrote: Hi Joe, I've seen this before and there is a bug report in mantis here: http://www.paraview.org/Bug/view.php?id=13382 There has also been a patch posted to the vtk-developers list a while back although I haven't tested it: http://markmail.org/message/zg3damrg27p5sgue Regards, Paul On 10 October 2014 00:32, Insley, Joseph A. > wrote: Hi, I have a serial vtu dataset provided by one of my users. Their current code can produce this in either ascii or inline binary. I am currently trying to convert this to appended binary (ultimately to pvtu with appended binary). I'm having trouble, which I now believe may stem from the data containing VTK_POLYHEDRON. I have a simple python script that I use with pvbatch to do this conversion, but I see the same results when I load the original data set with ParaView (4.1.0, in client/server mode), and use the Save Data option and save as vtu. I get the same results for each input format (ascii or inline binary), and output format (ascii, binary, appended). The first few lines of the original vtu file look like this: The first few lines of the converted file look like this: offset="177748206"ructuredGrid" version="0.1" byte_order="LittleEndian"> Something is clearly getting jumbled at the beginning of the converted file. If I manually edit the header of the file to read argonne leadership computing facility (630) 252-5649 argonne national laboratory _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Tue Oct 14 12:06:56 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Tue, 14 Oct 2014 09:06:56 -0700 Subject: [Paraview] BOX -> volume? In-Reply-To: <543C1D9F.5070803@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> Message-ID: <543D4A20.5080507@gmail.com> Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find "volume rendering mode" and set it to "ray cast only". This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers . This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: > > > OS: OpenSuSe 13.1 > > # lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core > Processor Integrated Graphics Controller (rev 06) > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] > > # glxinfo > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_INTEL_swap_event, > GLX_MESA_copy_sub_buffer, > GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, > GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, > GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync > GLX version: 1.4 > GLX extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync > OpenGL vendor string: Intel Open Source Technology Center > OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile > OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 > OpenGL core profile shading language version string: 1.40 > OpenGL core profile context flags: (none) > OpenGL core profile extensions: > GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_base_instance, > GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, > GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, > GL_ARB_provoking_vertex, > GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, > GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_sync, > GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, > GL_ARB_texture_float, GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, > GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, > GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, > GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, > GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, > GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, > GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback, > GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, > GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, > GL_MESA_ycbcr_texture, > GL_NV_conditional_render, GL_NV_depth_clamp, > GL_NV_packed_depth_stencil, > GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc > > OpenGL version string: 3.0 Mesa 9.2.3 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, > GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, > GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, > GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, > GL_ARB_fragment_shader, GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, > GL_ARB_multisample, > GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, > GL_ARB_point_sprite, > GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, > GL_ARB_texture_border_clamp, GL_ARB_texture_compression, > GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, > GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, > GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, > GL_ARB_texture_env_dot3, GL_ARB_texture_float, > GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, > GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, > GL_ARB_vertex_program, GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, > GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, > GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, > GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, > GL_EXT_blend_func_separate, GL_EXT_blend_minmax, > GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, > GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, > GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, > GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, > GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, GL_EXT_polygon_offset, > GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, GL_EXT_secondary_color, > GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, > GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, > GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, > GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, > GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, > GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, > GL_EXT_texture_lod_bias, GL_EXT_texture_object, > GL_EXT_texture_rectangle, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback, > GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, > GL_MESA_pack_invert, GL_MESA_texture_array, > GL_MESA_texture_signed_rgba, > GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, > GL_NV_conditional_render, GL_NV_depth_clamp, > GL_NV_light_max_exponent, > GL_NV_packed_depth_stencil, GL_NV_primitive_restart, > GL_NV_texgen_reflection, GL_NV_texture_env_combine4, > GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, > GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, > GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, > GL_SUN_multi_draw_arrays > > 20 GLX Visuals > visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer > ms cav > id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns > b eat > ---------------------------------------------------------------------------- > 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 > 0 Slow > 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 > 1 None > 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 > 1 None > 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 > 1 None > 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 > 1 None > 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 > 0 Slow > 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 > 1 None > 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 > 1 None > 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 > 1 None > 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 > 1 None > 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > > 44 GLXFBConfigs: > visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer > ms cav > id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns > b eat > ---------------------------------------------------------------------------- > 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 > 0 None > 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 > 0 None > 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 > 0 None > 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 > 0 None > 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 > 0 Slow > 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 > 0 Slow > 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 > 1 None > 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 > 1 None > 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 > 1 None > 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 > 1 None > 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 > 1 None > 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 > 1 None > 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 > 1 None > 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 > 1 None > 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 > 0 None > 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 > 0 None > 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 > 0 None > 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 > 0 None > 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 > 0 None > 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 > 0 None > 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 > 0 Slow > 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 > 0 None > 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 > 0 Slow > 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 > 1 None > 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 > 1 None > 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 > 1 None > 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 > 1 None > 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 > 1 None > 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 > 1 None > 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 > 1 None > 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 > 1 None > > > On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >> What graphics card / graphics driver version / OS this system has? >> >> - Aashish >> >> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest > > wrote: >> >> Hi Aashish, >> >> This is what I do: >> 1. start paraview >> 2. Sources -> Wavelet -> Apply. >> A cube is displayed (Outline representation). >> 3. Select 'Volume" representation" >> >> cube disappears. Then: >> ===================== >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> >> >> >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> >> >> >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> ========================= >> >> >> >> >> >> >> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>> So when you created a wavelet source and change the >>> representation to volume you got the errors? Can you post those >>> errors? >>> >>> Thanks, >>> >>> >>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>> > wrote: >>> >>> Aashish, >>> >>> Thanks for the suggestion. >>> >>> However, doing this gives me all kinds of opengl errors >>> (invalid instruction). >>> >>> Besides that, the wavelet gives me a cube indeed, but I need >>> to understand when >>> I can have a volume rendering. I created new Source's (e.g. >>> tri-prism, a wedge, >>> a box with boundaries of finite thickness etc.). But I >>> cannot get volume rendering >>> to work, grrrrrr. (See other thread) >>> >>> Kind Regards, >>> Bertwim >>> >>> >>> >>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>> You can create a wavelet source and then display it as a >>>> volume. >>>> >>>> >>>> >>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>> > wrote: >>>> >>>> Can perhaps somebody point me how to address the following. >>>> >>>> When I create a new source (say: a box) I get an a box that >>>> can be displayed via its surfaces, its constituing >>>> points, or wireframe >>>> representation. >>>> But I need a volume rendering (so that I can add e.g. a >>>> clipping plane) >>>> How do I get that? >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView >>>> Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>>> >>>> >>>> >>>> -- >>>> /| Aashish Chaudhary >>>> | Technical Leader >>>> | Kitware Inc. >>>> / >>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 14 13:40:05 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 14 Oct 2014 19:40:05 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: <543D4A20.5080507@gmail.com> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> Message-ID: <543D5FF5.3000600@xs4all.nl> Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting "volume" representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in "volume" representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: > Hi Bertwim, > > In recent releases of ParaView I have experienced issues/flakeyness > with volume rendering. Something you should try: Create the wavelet > source, then in the properties panel find "volume rendering mode" and > set it to "ray cast only". This has worked for me on a number of > systems. may or may not work, but worth a try. > > The output you pasted below shows that although you've got a sweet ATI > GPU you're not taking advantage of it! You're using the Intel > integrated GPU with Mesa drivers. If I were you I would install > proprietary the AMD drivers . > This should give you nice performance boost and may even solve the > OpenGL errors you reported, which these days are as often (or more) a > result of bugs in the Mesa drivers than in VTK. > > Burlen > > On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >> >> >> OS: OpenSuSe 13.1 >> >> # lspci | grep -i vga >> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core >> Processor Integrated Graphics Controller (rev 06) >> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >> [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >> >> # glxinfo >> name of display: :0 >> display: :0 screen: 0 >> direct rendering: Yes >> server glx vendor string: SGI >> server glx version string: 1.4 >> server glx extensions: >> GLX_ARB_create_context, GLX_ARB_create_context_profile, >> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >> GLX_EXT_visual_info, >> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >> GLX_MESA_copy_sub_buffer, >> GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, >> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control >> client glx vendor string: Mesa Project and SGI >> client glx version string: 1.4 >> client glx extensions: >> GLX_ARB_create_context, GLX_ARB_create_context_profile, >> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >> GLX_ARB_multisample, >> GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, >> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >> GLX_EXT_visual_rating, >> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >> GLX version: 1.4 >> GLX extensions: >> GLX_ARB_create_context, GLX_ARB_create_context_profile, >> GLX_ARB_get_proc_address, GLX_ARB_multisample, >> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >> GLX_EXT_visual_rating, >> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >> OpenGL vendor string: Intel Open Source Technology Center >> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >> OpenGL core profile shading language version string: 1.40 >> OpenGL core profile context flags: (none) >> OpenGL core profile extensions: >> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >> GL_ANGLE_texture_compression_dxt3, >> GL_ANGLE_texture_compression_dxt5, >> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, >> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, >> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >> GL_ARB_provoking_vertex, >> GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, >> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >> GL_ARB_shading_language_packing, GL_ARB_sync, >> GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, >> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, >> GL_ARB_texture_float, GL_ARB_texture_multisample, >> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >> GL_ARB_texture_rgb10_a2ui, >> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >> GL_ARB_texture_swizzle, GL_ARB_timer_query, >> GL_ARB_uniform_buffer_object, >> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >> GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, >> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >> GL_EXT_framebuffer_multisample, >> GL_EXT_framebuffer_multisample_blit_scaled, >> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >> GL_EXT_packed_float, >> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >> GL_EXT_texture_array, >> GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, >> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >> GL_EXT_texture_swizzle, GL_EXT_timer_query, >> GL_EXT_transform_feedback, >> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >> GL_MESA_ycbcr_texture, >> GL_NV_conditional_render, GL_NV_depth_clamp, >> GL_NV_packed_depth_stencil, >> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >> >> OpenGL version string: 3.0 Mesa 9.2.3 >> OpenGL shading language version string: 1.30 >> OpenGL context flags: (none) >> OpenGL extensions: >> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >> GL_ANGLE_texture_compression_dxt3, >> GL_ANGLE_texture_compression_dxt5, >> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, >> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, >> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >> GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, >> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >> GL_ARB_multisample, >> GL_ARB_multitexture, GL_ARB_occlusion_query, >> GL_ARB_occlusion_query2, >> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >> GL_ARB_point_sprite, >> GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, >> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >> GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, >> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >> GL_ARB_texture_rgb10_a2ui, >> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >> GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, >> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >> GL_ARB_vertex_program, GL_ARB_vertex_shader, >> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >> GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, >> GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, >> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >> GL_EXT_blend_subtract, >> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >> GL_EXT_draw_buffers2, >> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, >> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >> GL_EXT_framebuffer_multisample_blit_scaled, >> GL_EXT_framebuffer_object, >> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >> GL_EXT_packed_float, GL_EXT_packed_pixels, >> GL_EXT_pixel_buffer_object, >> GL_EXT_point_parameters, GL_EXT_polygon_offset, >> GL_EXT_provoking_vertex, >> GL_EXT_rescale_normal, GL_EXT_secondary_color, >> GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, >> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, >> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >> GL_EXT_texture_rectangle, >> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >> GL_EXT_texture_swizzle, GL_EXT_timer_query, >> GL_EXT_transform_feedback, >> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >> GL_MESA_pack_invert, GL_MESA_texture_array, >> GL_MESA_texture_signed_rgba, >> GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, >> GL_NV_conditional_render, GL_NV_depth_clamp, >> GL_NV_light_max_exponent, >> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >> GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, >> GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, >> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >> GL_SUN_multi_draw_arrays >> >> 20 GLX Visuals >> visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer >> ms cav >> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >> ns b eat >> ---------------------------------------------------------------------------- >> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >> 0 0 Slow >> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 4 1 None >> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 8 1 None >> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >> 0 0 Slow >> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 4 1 None >> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 8 1 None >> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> >> 44 GLXFBConfigs: >> visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer >> ms cav >> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >> ns b eat >> ---------------------------------------------------------------------------- >> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 >> 0 0 Slow >> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >> 0 0 Slow >> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 4 1 None >> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 8 1 None >> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 4 1 None >> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 8 1 None >> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 0 0 None >> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 0 0 None >> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 >> 0 0 Slow >> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 0 0 None >> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >> 0 0 Slow >> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 4 1 None >> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >> 8 1 None >> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 4 1 None >> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >> 8 1 None >> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 4 1 None >> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >> 8 1 None >> >> >> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>> What graphics card / graphics driver version / OS this system has? >>> >>> - Aashish >>> >>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >> > wrote: >>> >>> Hi Aashish, >>> >>> This is what I do: >>> 1. start paraview >>> 2. Sources -> Wavelet -> Apply. >>> A cube is displayed (Outline representation). >>> 3. Select 'Volume" representation" >>> >>> cube disappears. Then: >>> ===================== >>> Generic Warning: In >>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>> line 487 >>> failed at glBindTexture 1 OpenGL errors detected >>> 0 : (1282) Invalid operation >>> >>> >>> >>> Generic Warning: In >>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>> line 487 >>> failed at glBindTexture 1 OpenGL errors detected >>> 0 : (1282) Invalid operation >>> >>> >>> >>> Generic Warning: In >>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>> line 487 >>> failed at glBindTexture 1 OpenGL errors detected >>> 0 : (1282) Invalid operation >>> ========================= >>> >>> >>> >>> >>> >>> >>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>> So when you created a wavelet source and change the >>>> representation to volume you got the errors? Can you post those >>>> errors? >>>> >>>> Thanks, >>>> >>>> >>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>> > wrote: >>>> >>>> Aashish, >>>> >>>> Thanks for the suggestion. >>>> >>>> However, doing this gives me all kinds of opengl errors >>>> (invalid instruction). >>>> >>>> Besides that, the wavelet gives me a cube indeed, but I >>>> need to understand when >>>> I can have a volume rendering. I created new Source's (e.g. >>>> tri-prism, a wedge, >>>> a box with boundaries of finite thickness etc.). But I >>>> cannot get volume rendering >>>> to work, grrrrrr. (See other thread) >>>> >>>> Kind Regards, >>>> Bertwim >>>> >>>> >>>> >>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>> You can create a wavelet source and then display it as a >>>>> volume. >>>>> >>>>> >>>>> >>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>> > wrote: >>>>> >>>>> Can perhaps somebody point me how to address the >>>>> following. >>>>> >>>>> When I create a new source (say: a box) I get an a box >>>>> that >>>>> can be displayed via its surfaces, its constituing >>>>> points, or wireframe >>>>> representation. >>>>> But I need a volume rendering (so that I can add e.g. >>>>> a clipping plane) >>>>> How do I get that? >>>>> >>>>> Regards, >>>>> Bertwim >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView >>>>> Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> /| Aashish Chaudhary >>>>> | Technical Leader >>>>> | Kitware Inc. >>>>> / >>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>> >>>> >>>> >>>> >>>> -- >>>> /| Aashish Chaudhary >>>> | Technical Leader >>>> | Kitware Inc. >>>> / >>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Tue Oct 14 15:03:47 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 14 Oct 2014 19:03:47 +0000 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) Message-ID: Classification: UNCLASSIFIED Caveats: NONE Hello, We have several HPC systems that we compile/install different ParaView releases. We are wondering what would be a good test to verify that pvserver compiled is actually running on the system. Is there like a python script that when we run on the new installation, and it worked, we have a good confidence that the compilation/installation of the ParaView released is working? Will "a plot of a sphere + the process id scalar filter + save output to image = beach ball image" a good verification test? Thanks -simon Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Tue Oct 14 15:21:30 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Tue, 14 Oct 2014 15:21:30 -0400 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: Message-ID: Simon, Yup, that'd be a perfect test (attached). You should run it with pvbatch. Utkarsh On Tue, Oct 14, 2014 at 3:03 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > We have several HPC systems that we compile/install different ParaView > releases. We are wondering what would be a good test to verify that pvserver > compiled is actually running on the system. Is there like a python script > that when we run on the new installation, and it worked, we have a good > confidence that the compilation/installation of the ParaView released is > working? Will "a plot of a sphere + the process id scalar filter + save > output to image = beach ball image" a good verification test? > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: sample.py Type: text/x-python Size: 175 bytes Desc: not available URL: From simon.m.su.ctr at mail.mil Tue Oct 14 15:52:09 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Tue, 14 Oct 2014 19:52:09 +0000 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Thank you very much Utkarsh. -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, October 14, 2014 3:22 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] pvserver test on different systems (UNCLASSIFIED) Simon, Yup, that'd be a perfect test (attached). You should run it with pvbatch. Utkarsh On Tue, Oct 14, 2014 at 3:03 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > We have several HPC systems that we compile/install different ParaView > releases. We are wondering what would be a good test to verify that > pvserver compiled is actually running on the system. Is there like a > python script that when we run on the new installation, and it worked, > we have a good confidence that the compilation/installation of the > ParaView released is working? Will "a plot of a sphere + the process > id scalar filter + save output to image = beach ball image" a good > verification test? > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From bloring at lbl.gov Tue Oct 14 15:58:43 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 14 Oct 2014 12:58:43 -0700 Subject: [Paraview] BOX -> volume? In-Reply-To: <543D5FF5.3000600@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> Message-ID: <543D8073.60305@lbl.gov> progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset->Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and "save data". On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: > Hi Burlen, > > I have upgraded to the AMD drivers. Thanks for the hint. It has > improved the situation a bit. > > Furthermore, I created the wavelet source. When selecting "volume" > representation, I do see a three 3 picture, in all 5 volume rendering > mode (smart, raycast and texture mapping, ray cast only, texture > mapping only, GPU based). The picture a rather fuzzy, but then I don't > know what I'm supposed to see here. The good news is that the openGL > errors I had before when displaying a wavelet, now have gone. > > The situation with my own cube, though, has unchanged. unfortunately. > The cube disappears in "volume" representation node, also when I > re-inserted scalar values for each of the 8 vertices. > > Regards, > Bertwim > > On 10/14/2014 06:06 PM, Burlen Loring wrote: >> Hi Bertwim, >> >> In recent releases of ParaView I have experienced issues/flakeyness >> with volume rendering. Something you should try: Create the wavelet >> source, then in the properties panel find "volume rendering mode" and >> set it to "ray cast only". This has worked for me on a number of >> systems. may or may not work, but worth a try. >> >> The output you pasted below shows that although you've got a sweet >> ATI GPU you're not taking advantage of it! You're using the Intel >> integrated GPU with Mesa drivers. If I were you I would install >> proprietary the AMD drivers . >> This should give you nice performance boost and may even solve the >> OpenGL errors you reported, which these days are as often (or more) a >> result of bugs in the Mesa drivers than in VTK. >> >> Burlen >> >> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>> >>> >>> OS: OpenSuSe 13.1 >>> >>> # lspci | grep -i vga >>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core >>> Processor Integrated Graphics Controller (rev 06) >>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >>> [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>> >>> # glxinfo >>> name of display: :0 >>> display: :0 screen: 0 >>> direct rendering: Yes >>> server glx vendor string: SGI >>> server glx version string: 1.4 >>> server glx extensions: >>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>> GLX_EXT_visual_info, >>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>> GLX_MESA_copy_sub_buffer, >>> GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, >>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control >>> client glx vendor string: Mesa Project and SGI >>> client glx version string: 1.4 >>> client glx extensions: >>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>> GLX_ARB_multisample, >>> GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, >>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>> GLX_EXT_visual_rating, >>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >>> GLX version: 1.4 >>> GLX extensions: >>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>> GLX_EXT_visual_rating, >>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >>> OpenGL vendor string: Intel Open Source Technology Center >>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >>> OpenGL core profile shading language version string: 1.40 >>> OpenGL core profile context flags: (none) >>> OpenGL core profile extensions: >>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>> GL_ANGLE_texture_compression_dxt3, >>> GL_ANGLE_texture_compression_dxt5, >>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>> GL_ARB_debug_output, >>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, >>> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>> GL_ARB_provoking_vertex, >>> GL_ARB_robustness, GL_ARB_sampler_objects, >>> GL_ARB_seamless_cube_map, >>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>> GL_ARB_shading_language_packing, GL_ARB_sync, >>> GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, >>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, >>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>> GL_ARB_texture_rgb10_a2ui, >>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>> GL_ARB_uniform_buffer_object, >>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, >>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>> GL_EXT_framebuffer_multisample, >>> GL_EXT_framebuffer_multisample_blit_scaled, >>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>> GL_EXT_packed_float, >>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>> GL_EXT_texture_array, >>> GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, >>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>> GL_EXT_transform_feedback, >>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>> GL_MESA_ycbcr_texture, >>> GL_NV_conditional_render, GL_NV_depth_clamp, >>> GL_NV_packed_depth_stencil, >>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>> >>> OpenGL version string: 3.0 Mesa 9.2.3 >>> OpenGL shading language version string: 1.30 >>> OpenGL context flags: (none) >>> OpenGL extensions: >>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>> GL_ANGLE_texture_compression_dxt3, >>> GL_ANGLE_texture_compression_dxt5, >>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, >>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>> GL_ARB_depth_texture, >>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>> GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, >>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>> GL_ARB_multisample, >>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>> GL_ARB_occlusion_query2, >>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>> GL_ARB_point_sprite, >>> GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, >>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>> GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, >>> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>> GL_ARB_texture_rgb10_a2ui, >>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>> GL_ARB_transpose_matrix, >>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, >>> GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, >>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>> GL_EXT_blend_subtract, >>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>> GL_EXT_draw_buffers2, >>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>> GL_EXT_fog_coord, >>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>> GL_EXT_framebuffer_multisample_blit_scaled, >>> GL_EXT_framebuffer_object, >>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>> GL_EXT_pixel_buffer_object, >>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>> GL_EXT_provoking_vertex, >>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>> GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, >>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, >>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>> GL_EXT_texture_rectangle, >>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>> GL_EXT_transform_feedback, >>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >>> GL_MESA_pack_invert, GL_MESA_texture_array, >>> GL_MESA_texture_signed_rgba, >>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, >>> GL_NV_conditional_render, GL_NV_depth_clamp, >>> GL_NV_light_max_exponent, >>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>> GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, >>> GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, >>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>> GL_SUN_multi_draw_arrays >>> >>> 20 GLX Visuals >>> visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer >>> ms cav >>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >>> ns b eat >>> ---------------------------------------------------------------------------- >>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >>> 0 0 Slow >>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 4 1 None >>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 8 1 None >>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >>> 0 0 Slow >>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 4 1 None >>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 8 1 None >>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> >>> 44 GLXFBConfigs: >>> visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer >>> ms cav >>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >>> ns b eat >>> ---------------------------------------------------------------------------- >>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 >>> 0 0 Slow >>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >>> 0 0 Slow >>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 4 1 None >>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 8 1 None >>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 4 1 None >>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 8 1 None >>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 0 0 None >>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 0 0 None >>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 >>> 0 0 Slow >>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 0 0 None >>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 >>> 0 0 Slow >>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 4 1 None >>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 >>> 8 1 None >>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 4 1 None >>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 >>> 8 1 None >>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 4 1 None >>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 >>> 8 1 None >>> >>> >>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>> What graphics card / graphics driver version / OS this system has? >>>> >>>> - Aashish >>>> >>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>> > wrote: >>>> >>>> Hi Aashish, >>>> >>>> This is what I do: >>>> 1. start paraview >>>> 2. Sources -> Wavelet -> Apply. >>>> A cube is displayed (Outline representation). >>>> 3. Select 'Volume" representation" >>>> >>>> cube disappears. Then: >>>> ===================== >>>> Generic Warning: In >>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>> line 487 >>>> failed at glBindTexture 1 OpenGL errors detected >>>> 0 : (1282) Invalid operation >>>> >>>> >>>> >>>> Generic Warning: In >>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>> line 487 >>>> failed at glBindTexture 1 OpenGL errors detected >>>> 0 : (1282) Invalid operation >>>> >>>> >>>> >>>> Generic Warning: In >>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>> line 487 >>>> failed at glBindTexture 1 OpenGL errors detected >>>> 0 : (1282) Invalid operation >>>> ========================= >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>> So when you created a wavelet source and change the >>>>> representation to volume you got the errors? Can you post >>>>> those errors? >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>> > wrote: >>>>> >>>>> Aashish, >>>>> >>>>> Thanks for the suggestion. >>>>> >>>>> However, doing this gives me all kinds of opengl errors >>>>> (invalid instruction). >>>>> >>>>> Besides that, the wavelet gives me a cube indeed, but I >>>>> need to understand when >>>>> I can have a volume rendering. I created new Source's >>>>> (e.g. tri-prism, a wedge, >>>>> a box with boundaries of finite thickness etc.). But I >>>>> cannot get volume rendering >>>>> to work, grrrrrr. (See other thread) >>>>> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> >>>>> >>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>> You can create a wavelet source and then display it as a >>>>>> volume. >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>> > wrote: >>>>>> >>>>>> Can perhaps somebody point me how to address the >>>>>> following. >>>>>> >>>>>> When I create a new source (say: a box) I get an a >>>>>> box that >>>>>> can be displayed via its surfaces, its constituing >>>>>> points, or wireframe >>>>>> representation. >>>>>> But I need a volume rendering (so that I can add e.g. >>>>>> a clipping plane) >>>>>> How do I get that? >>>>>> >>>>>> Regards, >>>>>> Bertwim >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered by www.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects at >>>>>> http://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView >>>>>> Wiki at: http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> /| Aashish Chaudhary >>>>>> | Technical Leader >>>>>> | Kitware Inc. >>>>>> / >>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> /| Aashish Chaudhary >>>>> | Technical Leader >>>>> | Kitware Inc. >>>>> / >>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>> >>>> >>>> >>>> >>>> -- >>>> /| Aashish Chaudhary >>>> | Technical Leader >>>> | Kitware Inc. >>>> / >>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 14 16:23:28 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 14 Oct 2014 22:23:28 +0200 Subject: [Paraview] Export to vtk file needed to get colours! Message-ID: <543D8640.9050504@xs4all.nl> Hello All, I wonder if I stumbled upon a bug, or if I made a thinking error myself. The issue is: I can get colouring of my Source object only after I write it first to a vtk file and then read it back again! This is what I do: -) I create a single (rectangular) 3D cell from a (handcrafted) Source type, subclassed from vtkUnstructuredGridAlgorithm. This cell has scalar properties assigned to both its vertices as well as the cell itself. -) After "Apply", the box becomes visible (surface representation) However, there are no colours. The "Coloring" section in the Properties panel does not show the scalar properties. Only "Solid Color" and "cellNormals" appear as combo-options. -) After writing the model to a vtk file, and loading the latter, the loaded box does appear in its coloured form, with the scalar properties selectable in the "Coloring" combo box. Why do the colours not show up immediately after I created ("Apply") the source object. I naively tried a Modified() on the underlying unstructed grid object, but that didn't help. For completeness, I paste the relevant code as well as the vtk file (ascii). Kind Regards, Bertwim ==================== int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), vtkInformationVector **vtkNotUsed(inputVector), vtkInformationVector *outputVector) { // Get the info object vtkInformation *outInfo = outputVector->GetInformationObject(0); vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); // Pre-allocate some memory umesh->Allocate( 1024 ); // Scalars for the property values vtkFloatArray* vtxdata = vtkFloatArray::New(); // property defined on a vertex. vtkFloatArray* vxldata = vtkFloatArray::New(); // property defined in a voxel. // Specify points. float r0[] = { 0.0, 0.0, 0.0 }; float r1[] = { 1.0, 0.0, 0.0 }; float r2[] = { 0.0, 1.0, 0.0 }; float r3[] = { 1.0, 1.0, 0.0 }; float r4[] = { 0.0, 0.0, 1.0 }; float r5[] = { 1.0, 0.0, 1.0 }; float r6[] = { 0.0, 1.0, 1.0 }; float r7[] = { 1.0, 1.0, 1.0 }; // Collect the points in a vtk data structures. { vtkSmartPointer points = vtkSmartPointer::New(); points->SetDataType( VTK_FLOAT ); points->InsertNextPoint( r0 ); vtxdata->InsertNextValue( cos(0.1) ); points->InsertNextPoint( r1 ); vtxdata->InsertNextValue( cos(0.4) ); points->InsertNextPoint( r2 ); vtxdata->InsertNextValue( cos(0.7) ); points->InsertNextPoint( r3 ); vtxdata->InsertNextValue( cos(1.0) ); points->InsertNextPoint( r4 ); vtxdata->InsertNextValue( cos(1.3) ); points->InsertNextPoint( r5 ); vtxdata->InsertNextValue( cos(1.6) ); points->InsertNextPoint( r6 ); vtxdata->InsertNextValue( cos(1.9) ); points->InsertNextPoint( r7 ); vtxdata->InsertNextValue( cos(2.2) ); // Transfer points to umesh. umesh->SetPoints( points ); umesh->GetPointData()->SetScalars( vtxdata ); } // Cell Topology vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); vxldata->InsertNextValue( 3.14 ); umesh->GetCellData()->SetScalars( vxldata ); // Write data to a file { std::string fileName( "myfile.vtk" ); V3D::Utils::WriteUMesh( umesh, "Rectangular block as umesh", fileName, VTK_ASCII ); cerr << "Created: " << fileName << std::endl; } vtxdata->Delete(); vxldata->Delete(); return 1; } ======================= The file "myfile.vtk", written above read: ======================= # vtk DataFile Version 3.0 Rectangular block as umesh ASCII DATASET UNSTRUCTURED_GRID POINTS 8 float 0 0 0 1 0 0 0 1 0 1 1 0 0 0 1 1 0 1 0 1 1 1 1 1 CELLS 1 9 8 0 1 3 2 4 5 7 6 CELL_TYPES 1 12 CELL_DATA 1 SCALARS scalars float LOOKUP_TABLE default 3.14 POINT_DATA 8 SCALARS scalars float LOOKUP_TABLE default 0.995004 0.921061 0.764842 0.540302 0.267499 -0.0291995 -0.32329 -0.588501 ======================= -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory.quammen at kitware.com Tue Oct 14 16:28:57 2014 From: cory.quammen at kitware.com (Cory Quammen) Date: Tue, 14 Oct 2014 16:28:57 -0400 Subject: [Paraview] Export to vtk file needed to get colours! In-Reply-To: <543D8640.9050504@xs4all.nl> References: <543D8640.9050504@xs4all.nl> Message-ID: Bertwim, Try naming your arrays, e.g. vtxdata->SetName("Point Scalars"); vxldata->SetName("Cell Scalars"); and see if that makes them appear in the Coloring combo box. Thanks, Cory On Tue, Oct 14, 2014 at 4:23 PM, B.W.H. van Beest wrote: > Hello All, > > I wonder if I stumbled upon a bug, or if I made a thinking error myself. > > The issue is: I can get colouring of my Source object only after I write > it first to a vtk file and then read it back again! > > This is what I do: > > -) I create a single (rectangular) 3D cell from a (handcrafted) Source > type, > subclassed from vtkUnstructuredGridAlgorithm. > This cell has scalar properties assigned to both its vertices as well > as the cell itself. > > -) After "Apply", the box becomes visible (surface representation) > However, there are no colours. The "Coloring" section in the > Properties panel does not show the scalar properties. Only > "Solid Color" and "cellNormals" appear as combo-options. > > -) After writing the model to a vtk file, and loading the latter, the > loaded box does appear in its coloured form, with the scalar > properties > selectable in the "Coloring" combo box. > > Why do the colours not show up immediately after I created ("Apply") the > source object. I naively tried a Modified() on the underlying unstructed > grid object, > but that didn't help. > > For completeness, I paste the relevant code as well as the vtk file > (ascii). > > Kind Regards, > Bertwim > > > > ==================== > int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), > vtkInformationVector > **vtkNotUsed(inputVector), > vtkInformationVector *outputVector) > { > // Get the info object > vtkInformation *outInfo = outputVector->GetInformationObject(0); > vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( > outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > > // Pre-allocate some memory > umesh->Allocate( 1024 ); > > // Scalars for the property values > vtkFloatArray* vtxdata = vtkFloatArray::New(); // property defined on a > vertex. > vtkFloatArray* vxldata = vtkFloatArray::New(); // property defined in a > voxel. > > // Specify points. > float r0[] = { 0.0, 0.0, 0.0 }; > float r1[] = { 1.0, 0.0, 0.0 }; > float r2[] = { 0.0, 1.0, 0.0 }; > float r3[] = { 1.0, 1.0, 0.0 }; > float r4[] = { 0.0, 0.0, 1.0 }; > float r5[] = { 1.0, 0.0, 1.0 }; > float r6[] = { 0.0, 1.0, 1.0 }; > float r7[] = { 1.0, 1.0, 1.0 }; > > // Collect the points in a vtk data structures. > { > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetDataType( VTK_FLOAT ); > > points->InsertNextPoint( r0 ); vtxdata->InsertNextValue( cos(0.1) ); > points->InsertNextPoint( r1 ); vtxdata->InsertNextValue( cos(0.4) ); > points->InsertNextPoint( r2 ); vtxdata->InsertNextValue( cos(0.7) ); > points->InsertNextPoint( r3 ); vtxdata->InsertNextValue( cos(1.0) ); > points->InsertNextPoint( r4 ); vtxdata->InsertNextValue( cos(1.3) ); > points->InsertNextPoint( r5 ); vtxdata->InsertNextValue( cos(1.6) ); > points->InsertNextPoint( r6 ); vtxdata->InsertNextValue( cos(1.9) ); > points->InsertNextPoint( r7 ); vtxdata->InsertNextValue( cos(2.2) ); > > // Transfer points to umesh. > umesh->SetPoints( points ); > umesh->GetPointData()->SetScalars( vtxdata ); > } > > // Cell Topology > vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > vxldata->InsertNextValue( 3.14 ); > umesh->GetCellData()->SetScalars( vxldata ); > > // Write data to a file > { > std::string fileName( "myfile.vtk" ); > V3D::Utils::WriteUMesh( umesh, "Rectangular block as umesh", > fileName, VTK_ASCII ); > cerr << "Created: " << fileName << std::endl; > } > > vtxdata->Delete(); > vxldata->Delete(); > > return 1; > } > > ======================= > The file "myfile.vtk", written above read: > ======================= > # vtk DataFile Version > 3.0 > > Rectangular block as > umesh > > ASCII > > DATASET > UNSTRUCTURED_GRID > > POINTS 8 > float > > 0 0 0 1 0 0 0 1 > 0 > > 1 1 0 0 0 1 1 0 > 1 > > 0 1 1 1 1 > 1 > > CELLS 1 > 9 > > 8 0 1 3 2 4 5 7 > 6 > > > > CELL_TYPES > 1 > > 12 > > > > CELL_DATA > 1 > > SCALARS scalars > float > > LOOKUP_TABLE > default > > 3.14 > > POINT_DATA > 8 > > SCALARS scalars > float > > LOOKUP_TABLE > default > > 0.995004 0.921061 0.764842 0.540302 0.267499 -0.0291995 -0.32329 > -0.588501 > > ======================= > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 14 16:53:31 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 14 Oct 2014 22:53:31 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: <543D8073.60305@lbl.gov> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> Message-ID: <543D8D4B.30204@xs4all.nl> Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: > progress! it sounds like volume rendering is working on the wavelet > dataset. > > You do need the scalars for volume rendering, so make sure you have > those when you try. You need to select the scalars in the drop down > also, I usually do this before changing to the volume representation. > You also may need to edit the transfer function. For testing you could > make the opacity over the entire scalar range in which case you should > see a solid cube. > > If you've done all that and don't see anything it's likely that the > dataset is messed up. Add a dataset->Print(cerr) statement to the end > of your request data, look in the information panel and verify > correct number of points and scalar ranges. > > If all else fails post the dataset to the list. After creating your > cube go to the file menu and "save data". > > > On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >> Hi Burlen, >> >> I have upgraded to the AMD drivers. Thanks for the hint. It has >> improved the situation a bit. >> >> Furthermore, I created the wavelet source. When selecting "volume" >> representation, I do see a three 3 picture, in all 5 volume rendering >> mode (smart, raycast and texture mapping, ray cast only, texture >> mapping only, GPU based). The picture a rather fuzzy, but then I >> don't know what I'm supposed to see here. The good news is that the >> openGL errors I had before when displaying a wavelet, now have gone. >> >> The situation with my own cube, though, has unchanged. unfortunately. >> The cube disappears in "volume" representation node, also when I >> re-inserted scalar values for each of the 8 vertices. >> >> Regards, >> Bertwim >> >> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>> Hi Bertwim, >>> >>> In recent releases of ParaView I have experienced issues/flakeyness >>> with volume rendering. Something you should try: Create the wavelet >>> source, then in the properties panel find "volume rendering mode" >>> and set it to "ray cast only". This has worked for me on a number >>> of systems. may or may not work, but worth a try. >>> >>> The output you pasted below shows that although you've got a sweet >>> ATI GPU you're not taking advantage of it! You're using the Intel >>> integrated GPU with Mesa drivers. If I were you I would install >>> proprietary the AMD drivers . >>> This should give you nice performance boost and may even solve the >>> OpenGL errors you reported, which these days are as often (or more) >>> a result of bugs in the Mesa drivers than in VTK. >>> >>> Burlen >>> >>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>> >>>> >>>> OS: OpenSuSe 13.1 >>>> >>>> # lspci | grep -i vga >>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core >>>> Processor Integrated Graphics Controller (rev 06) >>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >>>> [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>> >>>> # glxinfo >>>> name of display: :0 >>>> display: :0 screen: 0 >>>> direct rendering: Yes >>>> server glx vendor string: SGI >>>> server glx version string: 1.4 >>>> server glx extensions: >>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>> GLX_EXT_visual_info, >>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>> GLX_MESA_copy_sub_buffer, >>>> GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, >>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>> GLX_SGI_swap_control >>>> client glx vendor string: Mesa Project and SGI >>>> client glx version string: 1.4 >>>> client glx extensions: >>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>> GLX_ARB_multisample, >>>> GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, >>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>> GLX_EXT_visual_rating, >>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >>>> GLX version: 1.4 >>>> GLX extensions: >>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>> GLX_EXT_visual_rating, >>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>> GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, >>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync >>>> OpenGL vendor string: Intel Open Source Technology Center >>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >>>> OpenGL core profile shading language version string: 1.40 >>>> OpenGL core profile context flags: (none) >>>> OpenGL core profile extensions: >>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>> GL_ANGLE_texture_compression_dxt3, >>>> GL_ANGLE_texture_compression_dxt5, >>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>> GL_ARB_debug_output, >>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>> GL_ARB_draw_buffers, >>>> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>> GL_ARB_provoking_vertex, >>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>> GL_ARB_seamless_cube_map, >>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>> GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, >>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, >>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>> GL_ARB_texture_rgb10_a2ui, >>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>> GL_ARB_uniform_buffer_object, >>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, >>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>> GL_EXT_framebuffer_multisample, >>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>> GL_EXT_packed_float, >>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>> GL_EXT_texture_array, >>>> GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, >>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>> GL_EXT_transform_feedback, >>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>> GL_MESA_ycbcr_texture, >>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>> GL_NV_packed_depth_stencil, >>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>> >>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>> OpenGL shading language version string: 1.30 >>>> OpenGL context flags: (none) >>>> OpenGL extensions: >>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>> GL_ANGLE_texture_compression_dxt3, >>>> GL_ANGLE_texture_compression_dxt5, >>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>> GL_ARB_debug_output, >>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>> GL_ARB_depth_texture, >>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>> GL_ARB_explicit_attrib_location, >>>> GL_ARB_fragment_coord_conventions, >>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>> GL_ARB_multisample, >>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>> GL_ARB_occlusion_query2, >>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>> GL_ARB_point_sprite, >>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>> GL_ARB_sampler_objects, >>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>> GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, >>>> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>> GL_ARB_texture_rgb10_a2ui, >>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>> GL_ARB_transpose_matrix, >>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, >>>> GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, >>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>> GL_EXT_blend_subtract, >>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>> GL_EXT_draw_buffers2, >>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>> GL_EXT_fog_coord, >>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>> GL_EXT_framebuffer_object, >>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>> GL_EXT_pixel_buffer_object, >>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>> GL_EXT_provoking_vertex, >>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>> GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, >>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, >>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>> GL_EXT_texture_rectangle, >>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>> GL_EXT_transform_feedback, >>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>> GL_MESA_texture_signed_rgba, >>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, >>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>> GL_NV_light_max_exponent, >>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>> GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, >>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, >>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>> GL_SUN_multi_draw_arrays >>>> >>>> 20 GLX Visuals >>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>> accumbuffer ms cav >>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >>>> ns b eat >>>> ---------------------------------------------------------------------------- >>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 >>>> 16 0 0 Slow >>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 4 1 None >>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 8 1 None >>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 >>>> 16 0 0 Slow >>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 4 1 None >>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 8 1 None >>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> >>>> 44 GLXFBConfigs: >>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>> accumbuffer ms cav >>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a >>>> ns b eat >>>> ---------------------------------------------------------------------------- >>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 >>>> 0 0 0 Slow >>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 >>>> 16 0 0 Slow >>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 4 1 None >>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 8 1 None >>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 4 1 None >>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 8 1 None >>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 0 0 None >>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 0 0 None >>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 >>>> 0 0 0 Slow >>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 0 0 None >>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 >>>> 16 0 0 Slow >>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 4 1 None >>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 >>>> 0 8 1 None >>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 4 1 None >>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 >>>> 0 8 1 None >>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 4 1 None >>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 >>>> 0 8 1 None >>>> >>>> >>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>> What graphics card / graphics driver version / OS this system has? >>>>> >>>>> - Aashish >>>>> >>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>> > wrote: >>>>> >>>>> Hi Aashish, >>>>> >>>>> This is what I do: >>>>> 1. start paraview >>>>> 2. Sources -> Wavelet -> Apply. >>>>> A cube is displayed (Outline representation). >>>>> 3. Select 'Volume" representation" >>>>> >>>>> cube disappears. Then: >>>>> ===================== >>>>> Generic Warning: In >>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>> line 487 >>>>> failed at glBindTexture 1 OpenGL errors detected >>>>> 0 : (1282) Invalid operation >>>>> >>>>> >>>>> >>>>> Generic Warning: In >>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>> line 487 >>>>> failed at glBindTexture 1 OpenGL errors detected >>>>> 0 : (1282) Invalid operation >>>>> >>>>> >>>>> >>>>> Generic Warning: In >>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>> line 487 >>>>> failed at glBindTexture 1 OpenGL errors detected >>>>> 0 : (1282) Invalid operation >>>>> ========================= >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>> So when you created a wavelet source and change the >>>>>> representation to volume you got the errors? Can you post >>>>>> those errors? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>> > wrote: >>>>>> >>>>>> Aashish, >>>>>> >>>>>> Thanks for the suggestion. >>>>>> >>>>>> However, doing this gives me all kinds of opengl errors >>>>>> (invalid instruction). >>>>>> >>>>>> Besides that, the wavelet gives me a cube indeed, but I >>>>>> need to understand when >>>>>> I can have a volume rendering. I created new Source's >>>>>> (e.g. tri-prism, a wedge, >>>>>> a box with boundaries of finite thickness etc.). But I >>>>>> cannot get volume rendering >>>>>> to work, grrrrrr. (See other thread) >>>>>> >>>>>> Kind Regards, >>>>>> Bertwim >>>>>> >>>>>> >>>>>> >>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>> You can create a wavelet source and then display it as a >>>>>>> volume. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>> > wrote: >>>>>>> >>>>>>> Can perhaps somebody point me how to address the >>>>>>> following. >>>>>>> >>>>>>> When I create a new source (say: a box) I get an a >>>>>>> box that >>>>>>> can be displayed via its surfaces, its constituing >>>>>>> points, or wireframe >>>>>>> representation. >>>>>>> But I need a volume rendering (so that I can add >>>>>>> e.g. a clipping plane) >>>>>>> How do I get that? >>>>>>> >>>>>>> Regards, >>>>>>> Bertwim >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at >>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView >>>>>>> Wiki at: http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> /| Aashish Chaudhary >>>>>>> | Technical Leader >>>>>>> | Kitware Inc. >>>>>>> / >>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> /| Aashish Chaudhary >>>>>> | Technical Leader >>>>>> | Kitware Inc. >>>>>> / >>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> /| Aashish Chaudhary >>>>> | Technical Leader >>>>> | Kitware Inc. >>>>> / >>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Tue Oct 14 17:01:31 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Tue, 14 Oct 2014 23:01:31 +0200 Subject: [Paraview] Export to vtk file needed to get colours! In-Reply-To: References: <543D8640.9050504@xs4all.nl> Message-ID: <543D8F2B.7050204@xs4all.nl> Yes, that works! Now the box comes up immediately, in coloured form. Thanks! Bertwim On 10/14/2014 10:28 PM, Cory Quammen wrote: > Bertwim, > > Try naming your arrays, e.g. > > vtxdata->SetName("Point Scalars"); > vxldata->SetName("Cell Scalars"); > > and see if that makes them appear in the Coloring combo box. > > Thanks, > Cory > > On Tue, Oct 14, 2014 at 4:23 PM, B.W.H. van Beest > wrote: > > Hello All, > > I wonder if I stumbled upon a bug, or if I made a thinking error > myself. > > The issue is: I can get colouring of my Source object only after I > write > it first to a vtk file and then read it back again! > > This is what I do: > > -) I create a single (rectangular) 3D cell from a (handcrafted) > Source type, > subclassed from vtkUnstructuredGridAlgorithm. > This cell has scalar properties assigned to both its vertices > as well as the cell itself. > > -) After "Apply", the box becomes visible (surface representation) > However, there are no colours. The "Coloring" section in the > Properties panel does not show the scalar properties. Only > "Solid Color" and "cellNormals" appear as combo-options. > > -) After writing the model to a vtk file, and loading the > latter, the > loaded box does appear in its coloured form, with the scalar > properties > selectable in the "Coloring" combo box. > > Why do the colours not show up immediately after I created > ("Apply") the > source object. I naively tried a Modified() on the underlying > unstructed grid object, > but that didn't help. > > For completeness, I paste the relevant code as well as the vtk > file (ascii). > > Kind Regards, > Bertwim > > > > ==================== > int sphBoxSourceC::RequestData( vtkInformation *vtkNotUsed(request), > vtkInformationVector > **vtkNotUsed(inputVector), > vtkInformationVector *outputVector) > { > // Get the info object > vtkInformation *outInfo = outputVector->GetInformationObject(0); > vtkUnstructuredGrid *umesh = vtkUnstructuredGrid::SafeDownCast( > outInfo->Get( vtkDataObject::DATA_OBJECT() ) ); > > // Pre-allocate some memory > umesh->Allocate( 1024 ); > > // Scalars for the property values > vtkFloatArray* vtxdata = vtkFloatArray::New(); // property > defined on a vertex. > vtkFloatArray* vxldata = vtkFloatArray::New(); // property > defined in a voxel. > > // Specify points. > float r0[] = { 0.0, 0.0, 0.0 }; > float r1[] = { 1.0, 0.0, 0.0 }; > float r2[] = { 0.0, 1.0, 0.0 }; > float r3[] = { 1.0, 1.0, 0.0 }; > float r4[] = { 0.0, 0.0, 1.0 }; > float r5[] = { 1.0, 0.0, 1.0 }; > float r6[] = { 0.0, 1.0, 1.0 }; > float r7[] = { 1.0, 1.0, 1.0 }; > > // Collect the points in a vtk data structures. > { > vtkSmartPointer points = > vtkSmartPointer::New(); > points->SetDataType( VTK_FLOAT ); > > points->InsertNextPoint( r0 ); vtxdata->InsertNextValue( > cos(0.1) ); > points->InsertNextPoint( r1 ); vtxdata->InsertNextValue( > cos(0.4) ); > points->InsertNextPoint( r2 ); vtxdata->InsertNextValue( > cos(0.7) ); > points->InsertNextPoint( r3 ); vtxdata->InsertNextValue( > cos(1.0) ); > points->InsertNextPoint( r4 ); vtxdata->InsertNextValue( > cos(1.3) ); > points->InsertNextPoint( r5 ); vtxdata->InsertNextValue( > cos(1.6) ); > points->InsertNextPoint( r6 ); vtxdata->InsertNextValue( > cos(1.9) ); > points->InsertNextPoint( r7 ); vtxdata->InsertNextValue( > cos(2.2) ); > > // Transfer points to umesh. > umesh->SetPoints( points ); > umesh->GetPointData()->SetScalars( vtxdata ); > } > > // Cell Topology > vtkIdType vtx[8] = { 0, 1, 3, 2, 4, 5, 7, 6 }; > umesh->InsertNextCell( VTK_HEXAHEDRON, 8, vtx ); > vxldata->InsertNextValue( 3.14 ); > umesh->GetCellData()->SetScalars( vxldata ); > > // Write data to a file > { > std::string fileName( "myfile.vtk" ); > V3D::Utils::WriteUMesh( umesh, "Rectangular block as umesh", > fileName, VTK_ASCII ); > cerr << "Created: " << fileName << std::endl; > } > > vtxdata->Delete(); > vxldata->Delete(); > > return 1; > } > > ======================= > The file "myfile.vtk", written above read: > ======================= > # vtk DataFile Version > 3.0 > > Rectangular block as > umesh > > ASCII > > DATASET > UNSTRUCTURED_GRID > > POINTS 8 > float > > 0 0 0 1 0 0 0 1 > 0 > > 1 1 0 0 0 1 1 0 > 1 > > 0 1 1 1 1 > 1 > > CELLS 1 > 9 > > 8 0 1 3 2 4 5 7 > 6 > > > > CELL_TYPES > 1 > > 12 > > > > CELL_DATA > 1 > > SCALARS scalars > float > > LOOKUP_TABLE > default > > 3.14 > > POINT_DATA > 8 > > SCALARS scalars > float > > LOOKUP_TABLE > default > > 0.995004 0.921061 0.764842 0.540302 0.267499 -0.0291995 -0.32329 > -0.588501 > > ======================= > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aashish.chaudhary at kitware.com Tue Oct 14 17:07:21 2014 From: aashish.chaudhary at kitware.com (Aashish Chaudhary) Date: Tue, 14 Oct 2014 17:07:21 -0400 Subject: [Paraview] BOX -> volume? In-Reply-To: <543D8D4B.30204@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> Message-ID: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions-> DriverIsATI() && (extensions->GetDriverGLVersionMajor() >= 3)) || extensions ->GetIgnoreDriverBugs("ATI texturing bug"); #endif On line number 181: can you change this code to : this->HasHardwareSupport = renwin != NULL && this->IsSupported(renwin); to this->HasHardwareSupport = 1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest wrote: > Progress indeed. But I don't understand what you are saying about the > transfer function. > > I' starting to wonder if I have two issues occurring simultaneously. > In a new thread I just posted I described my problem in getting the > colours in place. > I need to write to a vtk file first and load it back. I just found that > when I just did that > and then switched fo volume rendering, an error was there about the absence > of an opengl extension: > > ERROR: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, > line 185 > vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions > are not supported. > > This is complete unknown terrain for me. > > Regards, > Bertwim > > > > On 10/14/2014 09:58 PM, Burlen Loring wrote: > > progress! it sounds like volume rendering is working on the wavelet > dataset. > > You do need the scalars for volume rendering, so make sure you have those > when you try. You need to select the scalars in the drop down also, I > usually do this before changing to the volume representation. You also may > need to edit the transfer function. For testing you could make the opacity > over the entire scalar range in which case you should see a solid cube. > > If you've done all that and don't see anything it's likely that the > dataset is messed up. Add a dataset->Print(cerr) statement to the end of > your request data, look in the information panel and verify correct number > of points and scalar ranges. > > If all else fails post the dataset to the list. After creating your cube > go to the file menu and "save data". > > > On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: > > Hi Burlen, > > I have upgraded to the AMD drivers. Thanks for the hint. It has improved > the situation a bit. > > Furthermore, I created the wavelet source. When selecting "volume" > representation, I do see a three 3 picture, in all 5 volume rendering mode > (smart, raycast and texture mapping, ray cast only, texture mapping only, > GPU based). The picture a rather fuzzy, but then I don't know what I'm > supposed to see here. The good news is that the openGL errors I had before > when displaying a wavelet, now have gone. > > The situation with my own cube, though, has unchanged. unfortunately. > The cube disappears in "volume" representation node, also when I > re-inserted scalar values for each of the 8 vertices. > > Regards, > Bertwim > > On 10/14/2014 06:06 PM, Burlen Loring wrote: > > Hi Bertwim, > > In recent releases of ParaView I have experienced issues/flakeyness with > volume rendering. Something you should try: Create the wavelet source, then > in the properties panel find "volume rendering mode" and set it to "ray > cast only". This has worked for me on a number of systems. may or may not > work, but worth a try. > > The output you pasted below shows that although you've got a sweet ATI GPU > you're not taking advantage of it! You're using the Intel integrated GPU > with Mesa drivers. If I were you I would install proprietary the AMD > drivers . This should give you > nice performance boost and may even solve the OpenGL errors you reported, > which these days are as often (or more) a result of bugs in the Mesa > drivers than in VTK. > > Burlen > > On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: > > > > OS: OpenSuSe 13.1 > > # lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core > Processor Integrated Graphics Controller (rev 06) > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Mars [Radeon HD 8670A/8670M/8750M] > > # glxinfo > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, > GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, > GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync > GLX version: 1.4 > GLX extensions: > GLX_ARB_create_context, GLX_ARB_create_context_profile, > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync > OpenGL vendor string: Intel Open Source Technology Center > OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile > OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 > OpenGL core profile shading language version string: 1.40 > OpenGL core profile context flags: (none) > OpenGL core profile extensions: > GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_base_instance, > GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, > GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, > GL_ARB_provoking_vertex, > GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, > GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_sync, > GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, > GL_ARB_texture_float, GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, > GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, > GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, > GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, > GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, > GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, > GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, > GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, > GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, > GL_MESA_ycbcr_texture, > GL_NV_conditional_render, GL_NV_depth_clamp, > GL_NV_packed_depth_stencil, > GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc > > OpenGL version string: 3.0 Mesa 9.2.3 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, > GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, > GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, > GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, > GL_ARB_fragment_shader, GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, > GL_ARB_multisample, > GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, > GL_ARB_point_sprite, > GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, > GL_ARB_texture_border_clamp, GL_ARB_texture_compression, > GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, > GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, > GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, > GL_ARB_texture_env_dot3, GL_ARB_texture_float, > GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, > GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, > GL_ARB_vertex_program, GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, > GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, > GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, > GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, > GL_EXT_blend_func_separate, GL_EXT_blend_minmax, > GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, > GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, > GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, > GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, GL_EXT_polygon_offset, > GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, GL_EXT_secondary_color, > GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, > GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, > GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, > GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, > GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, > GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, > GL_EXT_texture_lod_bias, GL_EXT_texture_object, > GL_EXT_texture_rectangle, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, > GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, > GL_MESA_pack_invert, GL_MESA_texture_array, > GL_MESA_texture_signed_rgba, > GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, > GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent, > GL_NV_packed_depth_stencil, GL_NV_primitive_restart, > GL_NV_texgen_reflection, GL_NV_texture_env_combine4, > GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, > GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, > GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, > GL_SUN_multi_draw_arrays > > 20 GLX Visuals > visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms > cav > id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b > eat > > ---------------------------------------------------------------------------- > 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 > Slow > 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 > None > 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 > None > 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 > None > 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 > None > 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 > Slow > 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 > None > 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 > None > 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 > None > 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 > None > 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > > 44 GLXFBConfigs: > visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms > cav > id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b > eat > > ---------------------------------------------------------------------------- > 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 > None > 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 > None > 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 > None > 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 > None > 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 > Slow > 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 > Slow > 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 > None > 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 > None > 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 > None > 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 > None > 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 > None > 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 > None > 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 > None > 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 > None > 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 > None > 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 > None > 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 > None > 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 > None > 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 > None > 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 > None > 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 > Slow > 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 > None > 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 > Slow > 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 > None > 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 > None > 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 > None > 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 > None > 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 > None > 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 > None > 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 > None > 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 > None > > > On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: > > What graphics card / graphics driver version / OS this system has? > > - Aashish > > On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest wrote: > >> Hi Aashish, >> >> This is what I do: >> 1. start paraview >> 2. Sources -> Wavelet -> Apply. >> A cube is displayed (Outline representation). >> 3. Select 'Volume" representation" >> >> cube disappears. Then: >> ===================== >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> >> >> >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> >> >> >> Generic Warning: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >> line 487 >> failed at glBindTexture 1 OpenGL errors detected >> 0 : (1282) Invalid operation >> ========================= >> >> >> >> >> >> >> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >> >> So when you created a wavelet source and change the representation to >> volume you got the errors? Can you post those errors? >> >> Thanks, >> >> >> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest wrote: >> >>> Aashish, >>> >>> Thanks for the suggestion. >>> >>> However, doing this gives me all kinds of opengl errors (invalid >>> instruction). >>> >>> Besides that, the wavelet gives me a cube indeed, but I need to >>> understand when >>> I can have a volume rendering. I created new Source's (e.g. tri-prism, a >>> wedge, >>> a box with boundaries of finite thickness etc.). But I cannot get volume >>> rendering >>> to work, grrrrrr. (See other thread) >>> >>> Kind Regards, >>> Bertwim >>> >>> >>> >>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>> >>> You can create a wavelet source and then display it as a volume. >>> >>> >>> >>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>> wrote: >>> >>>> Can perhaps somebody point me how to address the following. >>>> >>>> When I create a new source (say: a box) I get an a box that >>>> can be displayed via its surfaces, its constituing points, or wireframe >>>> representation. >>>> But I need a volume rendering (so that I can add e.g. a clipping plane) >>>> How do I get that? >>>> >>>> Regards, >>>> Bertwim >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >>> * >>> *| http://www.kitware.com/company/team/chaudhary.html >>> * >>> >>> >>> >> >> >> -- >> >> >> >> *| Aashish Chaudhary | Technical Leader | Kitware Inc. >> * >> *| http://www.kitware.com/company/team/chaudhary.html >> * >> >> >> > > > -- > > > > *| Aashish Chaudhary | Technical Leader | Kitware Inc. > * > *| http://www.kitware.com/company/team/chaudhary.html > * > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -- *| Aashish Chaudhary | Technical Leader | Kitware Inc. * *| http://www.kitware.com/company/team/chaudhary.html * -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Tue Oct 14 18:46:48 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 14 Oct 2014 15:46:48 -0700 Subject: [Paraview] BOX -> volume? In-Reply-To: References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> Message-ID: <543DA7D8.2090807@lbl.gov> You could try it without modifying any code by setting the following cmake variable. VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON and recompile ParaView. With my ATI Radeon HD7780 projected tetrahedra just hangs. Burlen On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: > Looks like certain extensions are still not quite working on yours > system even with the proprietary driver. I will see if I can run your > code on my laptop but that would be for tomorrow. > > ** Assuming that this is not data dependent issue (which it should not). > > I think its probably this line causing the issue: > > bool driverSupport > > #if defined(__APPLE__) > > = true; > > #else > > = !(extensions->DriverIsATI() > > && (extensions->GetDriverGLVersionMajor() >= 3)) > > || extensions->GetIgnoreDriverBugs("ATI texturing bug"); > > #endif > > > > On line number 181: can you change this code to : > > this->HasHardwareSupport=renwin!=NULL&&this->IsSupported(renwin); > to > this->HasHardwareSupport=1; > > - Aashish > > > > On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > wrote: > > Progress indeed. But I don't understand what you are saying about > the transfer function. > > I' starting to wonder if I have two issues occurring simultaneously. > In a new thread I just posted I described my problem in getting > the colours in place. > I need to write to a vtk file first and load it back. I just > found that when I just did that > and then switched fo volume rendering, an error was there about > the absence > of an opengl extension: > > ERROR: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, > line 185 > vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required > extensions are not supported. > > This is complete unknown terrain for me. > > Regards, > Bertwim > > > > On 10/14/2014 09:58 PM, Burlen Loring wrote: >> progress! it sounds like volume rendering is working on the >> wavelet dataset. >> >> You do need the scalars for volume rendering, so make sure you >> have those when you try. You need to select the scalars in the >> drop down also, I usually do this before changing to the volume >> representation. You also may need to edit the transfer function. >> For testing you could make the opacity over the entire scalar >> range in which case you should see a solid cube. >> >> If you've done all that and don't see anything it's likely that >> the dataset is messed up. Add a dataset->Print(cerr) statement >> to the end of your request data, look in the information panel >> and verify correct number of points and scalar ranges. >> >> If all else fails post the dataset to the list. After creating >> your cube go to the file menu and "save data". >> >> >> On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >>> Hi Burlen, >>> >>> I have upgraded to the AMD drivers. Thanks for the hint. It has >>> improved the situation a bit. >>> >>> Furthermore, I created the wavelet source. When selecting >>> "volume" representation, I do see a three 3 picture, in all 5 >>> volume rendering mode (smart, raycast and texture mapping, ray >>> cast only, texture mapping only, GPU based). The picture a >>> rather fuzzy, but then I don't know what I'm supposed to see >>> here. The good news is that the openGL errors I had before when >>> displaying a wavelet, now have gone. >>> >>> The situation with my own cube, though, has unchanged. >>> unfortunately. >>> The cube disappears in "volume" representation node, also when >>> I re-inserted scalar values for each of the 8 vertices. >>> >>> Regards, >>> Bertwim >>> >>> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>>> Hi Bertwim, >>>> >>>> In recent releases of ParaView I have experienced >>>> issues/flakeyness with volume rendering. Something you should >>>> try: Create the wavelet source, then in the properties panel >>>> find "volume rendering mode" and set it to "ray cast only". >>>> This has worked for me on a number of systems. may or may not >>>> work, but worth a try. >>>> >>>> The output you pasted below shows that although you've got a >>>> sweet ATI GPU you're not taking advantage of it! You're using >>>> the Intel integrated GPU with Mesa drivers. If I were you I >>>> would install proprietary the AMD drivers >>>> . This should give you >>>> nice performance boost and may even solve the OpenGL errors you >>>> reported, which these days are as often (or more) a result of >>>> bugs in the Mesa drivers than in VTK. >>>> >>>> Burlen >>>> >>>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>>> >>>>> >>>>> OS: OpenSuSe 13.1 >>>>> >>>>> # lspci | grep -i vga >>>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen >>>>> Core Processor Integrated Graphics Controller (rev 06) >>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, >>>>> Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>>> >>>>> # glxinfo >>>>> name of display: :0 >>>>> display: :0 screen: 0 >>>>> direct rendering: Yes >>>>> server glx vendor string: SGI >>>>> server glx version string: 1.4 >>>>> server glx extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>>> GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>>> GLX_MESA_copy_sub_buffer, >>>>> GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, >>>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>>> GLX_SGI_swap_control >>>>> client glx vendor string: Mesa Project and SGI >>>>> client glx version string: 1.4 >>>>> client glx extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>>> GLX_ARB_multisample, >>>>> GLX_EXT_create_context_es2_profile, >>>>> GLX_EXT_fbconfig_packed_float, >>>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, >>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>> GLX_SGIS_multisample, >>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>> GLX_SGIX_visual_select_group, >>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>> GLX_SGI_video_sync >>>>> GLX version: 1.4 >>>>> GLX extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, >>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>> GLX_SGIS_multisample, >>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>> GLX_SGIX_visual_select_group, >>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>> GLX_SGI_video_sync >>>>> OpenGL vendor string: Intel Open Source Technology Center >>>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >>>>> OpenGL core profile shading language version string: 1.40 >>>>> OpenGL core profile context flags: (none) >>>>> OpenGL core profile extensions: >>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>> GL_ANGLE_texture_compression_dxt3, >>>>> GL_ANGLE_texture_compression_dxt5, >>>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>>> GL_ARB_debug_output, >>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>> GL_ARB_draw_buffers, >>>>> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >>>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>>> GL_ARB_provoking_vertex, >>>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>>> GL_ARB_seamless_cube_map, >>>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>>> GL_ARB_texture_buffer_object, >>>>> GL_ARB_texture_buffer_object_rgb32, >>>>> GL_ARB_texture_compression_rgtc, >>>>> GL_ARB_texture_cube_map_array, >>>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>> GL_ARB_texture_rgb10_a2ui, >>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>> GL_ARB_uniform_buffer_object, >>>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, >>>>> GL_EXT_abgr, >>>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>>> GL_EXT_framebuffer_multisample, >>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>>> GL_EXT_packed_float, >>>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>>> GL_EXT_texture_array, >>>>> GL_EXT_texture_compression_dxt1, >>>>> GL_EXT_texture_compression_rgtc, >>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>> GL_EXT_transform_feedback, >>>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>>> GL_MESA_ycbcr_texture, >>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>> GL_NV_packed_depth_stencil, >>>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>>> >>>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>>> OpenGL shading language version string: 1.30 >>>>> OpenGL context flags: (none) >>>>> OpenGL extensions: >>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>> GL_ANGLE_texture_compression_dxt3, >>>>> GL_ANGLE_texture_compression_dxt5, >>>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>>> GL_ARB_debug_output, >>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>> GL_ARB_depth_texture, >>>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>>> GL_ARB_explicit_attrib_location, >>>>> GL_ARB_fragment_coord_conventions, >>>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>>> GL_ARB_multisample, >>>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>>> GL_ARB_occlusion_query2, >>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>>> GL_ARB_point_sprite, >>>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>>> GL_ARB_sampler_objects, >>>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>>> GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, >>>>> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >>>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>> GL_ARB_texture_rgb10_a2ui, >>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>> GL_ARB_transpose_matrix, >>>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, >>>>> GL_EXT_abgr, >>>>> GL_EXT_bgra, GL_EXT_blend_color, >>>>> GL_EXT_blend_equation_separate, >>>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>>> GL_EXT_blend_subtract, >>>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>>> GL_EXT_draw_buffers2, >>>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>>> GL_EXT_fog_coord, >>>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>> GL_EXT_framebuffer_object, >>>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>>> GL_EXT_pixel_buffer_object, >>>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>>> GL_EXT_provoking_vertex, >>>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>>> GL_EXT_separate_shader_objects, >>>>> GL_EXT_separate_specular_color, >>>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, >>>>> GL_EXT_stencil_wrap, >>>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>>> GL_EXT_texture_rectangle, >>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>> GL_EXT_transform_feedback, >>>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>>> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >>>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>>> GL_MESA_texture_signed_rgba, >>>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, >>>>> GL_NV_blend_square, >>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>> GL_NV_light_max_exponent, >>>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>>> GL_NV_texture_rectangle, GL_OES_EGL_image, >>>>> GL_OES_read_format, >>>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, >>>>> GL_SGIS_texture_border_clamp, >>>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>>> GL_SUN_multi_draw_arrays >>>>> >>>>> 20 GLX Visuals >>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>> accumbuffer ms cav >>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g >>>>> b a ns b eat >>>>> ---------------------------------------------------------------------------- >>>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> >>>>> 44 GLXFBConfigs: >>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>> accumbuffer ms cav >>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g >>>>> b a ns b eat >>>>> ---------------------------------------------------------------------------- >>>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>> 16 0 0 0 Slow >>>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>> 16 0 0 0 Slow >>>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> >>>>> >>>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>>> What graphics card / graphics driver version / OS this system >>>>>> has? >>>>>> >>>>>> - Aashish >>>>>> >>>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>>>> > wrote: >>>>>> >>>>>> Hi Aashish, >>>>>> >>>>>> This is what I do: >>>>>> 1. start paraview >>>>>> 2. Sources -> Wavelet -> Apply. >>>>>> A cube is displayed (Outline representation). >>>>>> 3. Select 'Volume" representation" >>>>>> >>>>>> cube disappears. Then: >>>>>> ===================== >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> >>>>>> >>>>>> >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> >>>>>> >>>>>> >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> ========================= >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>>> So when you created a wavelet source and change the >>>>>>> representation to volume you got the errors? Can you >>>>>>> post those errors? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>>> > wrote: >>>>>>> >>>>>>> Aashish, >>>>>>> >>>>>>> Thanks for the suggestion. >>>>>>> >>>>>>> However, doing this gives me all kinds of opengl >>>>>>> errors (invalid instruction). >>>>>>> >>>>>>> Besides that, the wavelet gives me a cube indeed, >>>>>>> but I need to understand when >>>>>>> I can have a volume rendering. I created new >>>>>>> Source's (e.g. tri-prism, a wedge, >>>>>>> a box with boundaries of finite thickness etc.). But >>>>>>> I cannot get volume rendering >>>>>>> to work, grrrrrr. (See other thread) >>>>>>> >>>>>>> Kind Regards, >>>>>>> Bertwim >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>>> You can create a wavelet source and then display it >>>>>>>> as a volume. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Can perhaps somebody point me how to address >>>>>>>> the following. >>>>>>>> >>>>>>>> When I create a new source (say: a box) I get >>>>>>>> an a box that >>>>>>>> can be displayed via its surfaces, its >>>>>>>> constituing points, or wireframe >>>>>>>> representation. >>>>>>>> But I need a volume rendering (so that I can >>>>>>>> add e.g. a clipping plane) >>>>>>>> How do I get that? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Bertwim >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the >>>>>>>> ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /| Aashish Chaudhary >>>>>>>> | Technical Leader >>>>>>>> | Kitware Inc. >>>>>>>> / >>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> /| Aashish Chaudhary >>>>>>> | Technical Leader >>>>>>> | Kitware Inc. >>>>>>> / >>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> /| Aashish Chaudhary >>>>>> | Technical Leader >>>>>> | Kitware Inc. >>>>>> / >>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered bywww.kitware.com >>>>> >>>>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Oct 14 18:53:54 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 14 Oct 2014 22:53:54 +0000 Subject: [Paraview] [EXTERNAL] Re: BOX -> volume? In-Reply-To: <543DA7D8.2090807@lbl.gov> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543DA7D8.2090807@lbl.gov> Message-ID: <914eb2b027994c51a3ca7801c58ca6ca@ES05AMSNLNT.srn.sandia.gov> Burlen/ Aashish/ B.W.H, I haven?t been following this thread, but just a note that there is a bug already written about this code, and a similar (but not exact) error. Said bug report is here: http://www.paraview.org/Bug/view.php?id=15020 It is slated to be fixed in a minor release within the next few months. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Burlen Loring Sent: Tuesday, October 14, 2014 4:47 PM To: Aashish Chaudhary; B.W.H. van Beest Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] BOX -> volume? You could try it without modifying any code by setting the following cmake variable. VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON and recompile ParaView. With my ATI Radeon HD7780 projected tetrahedra just hangs. Burlen On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions->DriverIsATI() && (extensions->GetDriverGLVersionMajor() >= 3)) || extensions->GetIgnoreDriverBugs("ATI texturing bug"); #endif On line number 181: can you change this code to : this->HasHardwareSupport = renwin != NULL && this->IsSupported(renwin); to this->HasHardwareSupport = 1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset->Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and "save data". On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting "volume" representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in "volume" representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find "volume rendering mode" and set it to "ray cast only". This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, GL_ARB_texture_float, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc OpenGL version string: 3.0 Mesa 9.2.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_texture_array, GL_MESA_texture_signed_rgba, GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, GL_NV_primitive_restart, GL_NV_texgen_reflection, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays 20 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 44 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: What graphics card / graphics driver version / OS this system has? - Aashish On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest > wrote: Hi Aashish, This is what I do: 1. start paraview 2. Sources -> Wavelet -> Apply. A cube is displayed (Outline representation). 3. Select 'Volume" representation" cube disappears. Then: ===================== Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation ========================= On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest > wrote: Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grrrrrr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest > wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Tue Oct 14 19:17:39 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 14 Oct 2014 16:17:39 -0700 Subject: [Paraview] [EXTERNAL] Re: BOX -> volume? In-Reply-To: <914eb2b027994c51a3ca7801c58ca6ca@ES05AMSNLNT.srn.sandia.gov> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543DA7D8.2090807@lbl.gov> <914eb2b027994c51a3ca7801c58ca6ca@ES05AMSNLNT.srn.sandia.gov> Message-ID: <543DAF13.7040408@lbl.gov> Hi Alan, That is a different issue. You're seeing that warning because your Mesa build is missing floating point support. Some of the older releases didn't have it, however newer releases do. It's always been a build option that's off by default because of patent issues, so you need to expeictly enable it when compiling mesa. The intention behind that (in hindsight annoying) warning is to alert you are using an ancient version of mesa and or that you may have not built mesa with floating point support. At the time the warning seemed reasonable to me since without floating point support the projected tets algorithm *could produce precision related artifacts depending on data and rendering parameters and downloading and installing a newer mesa (or simply recompiling your existing mesa build with floating point support enabled) is a relatively easy fix. For me I'd rather know that there's potentially a problem and update mesa, rather than scratch my head about why there are artifacts in my rendering. With regard to the current thread and Bertwim's issue with ATI GPU, I think the code is currently doing the right thing because projected tets algorithm hangs on the ATI card. A workaround if you have an ATI card is to set the "select mapper" to "Bunyk ray cast" Burlen On 10/14/2014 03:53 PM, Scott, W Alan wrote: > > Burlen/ Aashish/ B.W.H, > > I haven?t been following this thread, but just a note that there is a > bug already written about this code, and a similar (but not exact) > error. Said bug report is here: > http://www.paraview.org/Bug/view.php?id=15020 It is slated to be fixed > in a minor release within the next few months. > > Alan > > *From:*ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of > *Burlen Loring > *Sent:* Tuesday, October 14, 2014 4:47 PM > *To:* Aashish Chaudhary; B.W.H. van Beest > *Cc:* ParaView > *Subject:* [EXTERNAL] Re: [Paraview] BOX -> volume? > > You could try it without modifying any code by setting the following > cmake variable. > > VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON > > and recompile ParaView. With my ATI Radeon HD7780 projected tetrahedra > just hangs. > > Burlen > > On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: > > Looks like certain extensions are still not quite working on yours > system even with the proprietary driver. I will see if I can run > your code on my laptop but that would be for tomorrow. > > ** Assuming that this is not data dependent issue (which it should > not). > > I think its probably this line causing the issue: > > > *bool* > > driverSupport > > > > > > * #if* > > * defined(__APPLE__)* > > > > > > *=* true; > > > > > > ** > > *#else* > > > > > > *=* *!*(extensions*->*DriverIsATI() > > > > > > *&&* > > (extensions*->*GetDriverGLVersionMajor() *>=* 3)) > > > > > > *||* extensions*->*GetIgnoreDriverBugs("ATI texturing bug"); > > > > > > ** > > *#endif* > > > > > > > > On line number 181: can you change this code to : > > *this->*HasHardwareSupport > > *=* > > renwin > > *!=* > > NULL > > *&&* > > *this->*IsSupported(renwin); > > to > > *this->*HasHardwareSupport > > *=* > > 1; > > > > - Aashish > > On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > wrote: > > Progress indeed. But I don't understand what you are saying about > the transfer function. > > I' starting to wonder if I have two issues occurring simultaneously. > In a new thread I just posted I described my problem in getting > the colours in place. > I need to write to a vtk file first and load it back. I just found > that when I just did that > and then switched fo volume rendering, an error was there about > the absence > of an opengl extension: > > ERROR: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, > line 185 > vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required > extensions are not supported. > > This is complete unknown terrain for me. > > Regards, > Bertwim > > > > On 10/14/2014 09:58 PM, Burlen Loring wrote: > > progress! it sounds like volume rendering is working on the > wavelet dataset. > > You do need the scalars for volume rendering, so make sure you > have those when you try. You need to select the scalars in the > drop down also, I usually do this before changing to the > volume representation. You also may need to edit the transfer > function. For testing you could make the opacity over the > entire scalar range in which case you should see a solid cube. > > If you've done all that and don't see anything it's likely > that the dataset is messed up. Add a dataset->Print(cerr) > statement to the end of your request data, look in the > information panel and verify correct number of points and > scalar ranges. > > If all else fails post the dataset to the list. After creating > your cube go to the file menu and "save data". > > On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: > > Hi Burlen, > > I have upgraded to the AMD drivers. Thanks for the hint. > It has improved the situation a bit. > > Furthermore, I created the wavelet source. When selecting > "volume" representation, I do see a three 3 picture, in > all 5 volume rendering mode (smart, raycast and texture > mapping, ray cast only, texture mapping only, GPU based). > The picture a rather fuzzy, but then I don't know what I'm > supposed to see here. The good news is that the openGL > errors I had before when displaying a wavelet, now have gone. > > The situation with my own cube, though, has unchanged. > unfortunately. > The cube disappears in "volume" representation node, also > when I re-inserted scalar values for each of the 8 vertices. > > Regards, > Bertwim > > On 10/14/2014 06:06 PM, Burlen Loring wrote: > > Hi Bertwim, > > In recent releases of ParaView I have experienced > issues/flakeyness with volume rendering. Something you > should try: Create the wavelet source, then in the > properties panel find "volume rendering mode" and set > it to "ray cast only". This has worked for me on a > number of systems. may or may not work, but worth a try. > > The output you pasted below shows that although you've > got a sweet ATI GPU you're not taking advantage of it! > You're using the Intel integrated GPU with Mesa > drivers. If I were you I would install proprietary the > AMD drivers . > This should give you nice performance boost and may > even solve the OpenGL errors you reported, which these > days are as often (or more) a result of bugs in the > Mesa drivers than in VTK. > > Burlen > > On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: > > > > OS: OpenSuSe 13.1 > > # lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel > Corporation 4th Gen Core Processor Integrated > Graphics Controller (rev 06) > 01:00.0 VGA compatible controller: Advanced Micro > Devices, Inc. [AMD/ATI] Mars [Radeon HD > 8670A/8670M/8750M] > > # glxinfo > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, GLX_INTEL_swap_event, > GLX_MESA_copy_sub_buffer, > GLX_OML_swap_method, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, GLX_SGI_swap_control > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_create_context_robustness, > GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_fbconfig_packed_float, > GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, > GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, > GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, > GLX_SGI_swap_control, GLX_SGI_video_sync > GLX version: 1.4 > GLX extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, > GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, > GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, > GLX_SGI_swap_control, GLX_SGI_video_sync > OpenGL vendor string: Intel Open Source Technology > Center > OpenGL renderer string: Mesa DRI Intel(R) Haswell > Mobile > OpenGL core profile version string: 3.1 (Core > Profile) Mesa 9.2.3 > OpenGL core profile shading language version > string: 1.40 > OpenGL core profile context flags: (none) > OpenGL core profile extensions: > GL_3DFX_texture_compression_FXT1, > GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, > GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, > GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, GL_ARB_base_instance, > GL_ARB_blend_func_extended, > GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, > GL_ARB_draw_buffers, > GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, > GL_ARB_point_sprite, GL_ARB_provoking_vertex, > GL_ARB_robustness, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, > GL_ARB_shader_texture_lod, > GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_sync, > GL_ARB_texture_buffer_object, > GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map_array, > GL_ARB_texture_float, GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, > GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, > GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, > GL_ATI_blend_equation_separate, > GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_blend_equation_separate, > GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_sRGB, > GL_EXT_packed_depth_stencil, GL_EXT_packed_float, > GL_EXT_pixel_buffer_object, > GL_EXT_provoking_vertex, GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, > GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, > GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback, > GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, > GL_MESA_pack_invert, > GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, > GL_NV_conditional_render, GL_NV_depth_clamp, > GL_NV_packed_depth_stencil, > GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc > > OpenGL version string: 3.0 Mesa 9.2.3 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > GL_3DFX_texture_compression_FXT1, > GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, > GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, > GL_APPLE_packed_pixels, > GL_APPLE_vertex_array_object, > GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, > GL_ARB_blend_func_extended, > GL_ARB_color_buffer_float, GL_ARB_copy_buffer, > GL_ARB_debug_output, > GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, > GL_ARB_depth_texture, > GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_program, > GL_ARB_fragment_program_shadow, > GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, GL_ARB_multisample, > GL_ARB_multitexture, GL_ARB_occlusion_query, > GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, > GL_ARB_point_parameters, GL_ARB_point_sprite, > GL_ARB_provoking_vertex, GL_ARB_robustness, > GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, > GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, > GL_ARB_shadow, GL_ARB_sync, > GL_ARB_texture_border_clamp, > GL_ARB_texture_compression, > GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map, > GL_ARB_texture_cube_map_array, > GL_ARB_texture_env_add, > GL_ARB_texture_env_combine, > GL_ARB_texture_env_crossbar, > GL_ARB_texture_env_dot3, GL_ARB_texture_float, > GL_ARB_texture_mirrored_repeat, > GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, GL_ARB_texture_rg, > GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, GL_ARB_timer_query, > GL_ARB_transpose_matrix, > GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, > GL_ARB_vertex_buffer_object, > GL_ARB_vertex_program, GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, > GL_ARB_window_pos, > GL_ATI_blend_equation_separate, > GL_ATI_draw_buffers, > GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, > GL_ATI_texture_env_combine3, > GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_bgra, GL_EXT_blend_color, > GL_EXT_blend_equation_separate, > GL_EXT_blend_func_separate, > GL_EXT_blend_minmax, GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, > GL_EXT_copy_texture, GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, > GL_EXT_draw_range_elements, GL_EXT_fog_coord, > GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, > GL_EXT_gpu_program_parameters, > GL_EXT_multi_draw_arrays, > GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, > GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, > GL_EXT_polygon_offset, GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, GL_EXT_secondary_color, > GL_EXT_separate_shader_objects, > GL_EXT_separate_specular_color, > GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, > GL_EXT_stencil_wrap, > GL_EXT_subtexture, GL_EXT_texture, > GL_EXT_texture3D, > GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, > GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, > GL_EXT_texture_env_add, > GL_EXT_texture_env_combine, > GL_EXT_texture_env_dot3, > GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, > GL_EXT_texture_lod_bias, > GL_EXT_texture_object, GL_EXT_texture_rectangle, > GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, > GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, GL_EXT_timer_query, > GL_EXT_transform_feedback, > GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, > GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, > GL_INGR_blend_func_separate, > GL_MESA_pack_invert, GL_MESA_texture_array, > GL_MESA_texture_signed_rgba, > GL_MESA_window_pos, GL_MESA_ycbcr_texture, > GL_NV_blend_square, > GL_NV_conditional_render, GL_NV_depth_clamp, > GL_NV_light_max_exponent, > GL_NV_packed_depth_stencil, > GL_NV_primitive_restart, > GL_NV_texgen_reflection, > GL_NV_texture_env_combine4, > GL_NV_texture_rectangle, GL_OES_EGL_image, > GL_OES_read_format, > GL_S3_s3tc, GL_SGIS_generate_mipmap, > GL_SGIS_texture_border_clamp, > GL_SGIS_texture_edge_clamp, > GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays > > 20 GLX Visuals > visual x bf lv rg d st colorbuffer sr ax > dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a F gb bf > th cl r g b a ns b eat > ---------------------------------------------------------------------------- > 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 16 16 16 16 0 0 Slow > 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 4 1 None > 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 8 1 None > 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 4 1 None > 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 8 1 None > 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 16 16 16 16 0 0 Slow > 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 4 1 None > 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 8 1 None > 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 4 1 None > 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 8 1 None > 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > > 44 GLXFBConfigs: > visual x bf lv rg d st colorbuffer sr ax > dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a F gb bf > th cl r g b a ns b eat > ---------------------------------------------------------------------------- > 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 0 0 None > 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 > 0 0 0 0 0 0 0 0 None > 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 24 8 0 0 0 0 0 0 None > 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 > 24 8 0 0 0 0 0 0 None > 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 16 16 16 0 0 0 Slow > 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 16 16 16 16 0 0 Slow > 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 4 1 None > 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 8 1 None > 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 4 1 None > 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 8 1 None > 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 4 1 None > 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 8 1 None > 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 4 1 None > 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 8 1 None > 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 0 0 None > 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 > 0 0 0 0 0 0 0 0 None > 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 24 8 0 0 0 0 0 0 None > 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 > 24 8 0 0 0 0 0 0 None > 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 > 0 0 0 0 0 0 0 0 None > 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 0 0 None > 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 16 16 16 0 0 0 Slow > 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 0 0 None > 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 16 16 16 16 0 0 Slow > 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 4 1 None > 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 0 0 0 0 0 0 8 1 None > 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 4 1 None > 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 > 16 0 0 0 0 0 8 1 None > 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 4 1 None > 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 0 0 0 0 0 0 8 1 None > 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 4 1 None > 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 > 24 8 0 0 0 0 8 1 None > > On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: > > What graphics card / graphics driver version / > OS this system has? > > - Aashish > > On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van > Beest > > wrote: > > Hi Aashish, > > This is what I do: > 1. start paraview > 2. Sources -> Wavelet -> Apply. > A cube is displayed (Outline representation). > 3. Select 'Volume" representation" > > cube disappears. Then: > ===================== > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors detected > 0 : (1282) Invalid operation > ========================= > > > > > > > On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: > > So when you created a wavelet source and > change the representation to volume you > got the errors? Can you post those errors? > > Thanks, > > On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. > van Beest > wrote: > > Aashish, > > Thanks for the suggestion. > > However, doing this gives me all kinds of > opengl errors (invalid instruction). > > Besides that, the wavelet gives me a cube > indeed, but I need to understand when > I can have a volume rendering. I created > new Source's (e.g. tri-prism, a wedge, > a box with boundaries of finite thickness > etc.). But I cannot get volume rendering > to work, grrrrrr. (See other thread) > > Kind Regards, > Bertwim > > > > On 10/13/2014 05:28 PM, Aashish Chaudhary > wrote: > > You can create a wavelet source and > then display it as a volume. > > On Fri, Oct 10, 2014 at 3:45 PM, > B.W.H. van Beest > wrote: > > Can perhaps somebody point me how to > address the following. > > When I create a new source (say: a > box) I get an a box that > can be displayed via its surfaces, its > constituing points, or wireframe > representation. > But I need a volume rendering (so that > I can add e.g. a clipping plane) > How do I get that? > > Regards, > Bertwim > > > > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source > projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and > check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > //http://www.kitware.com/company/team/chaudhary.html/ > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > //http://www.kitware.com/company/team/chaudhary.html/ > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > //http://www.kitware.com/company/team/chaudhary.html/ > > > > > _______________________________________________ > > Powered bywww.kitware.com > > > > Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > > Powered bywww.kitware.com > > > > Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| //http://www.kitware.com/company/team/chaudhary.html/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Oct 14 19:45:44 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 14 Oct 2014 23:45:44 +0000 Subject: [Paraview] [EXTERNAL] Re: BOX -> volume? In-Reply-To: <543DAF13.7040408@lbl.gov> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543DA7D8.2090807@lbl.gov> <914eb2b027994c51a3ca7801c58ca6ca@ES05AMSNLNT.srn.sandia.gov> <543DAF13.7040408@lbl.gov> Message-ID: <79f3790ae87f4d0bb9706ddbe82a75a0@ES05AMSNLNT.srn.sandia.gov> Understand. I replied into the bug itself, but the simple answer is that I didn?t build this version of Mesa ? it was provided by a vender and I have no control over it. And it has to work on this version of Mesa, as it has before. Alan From: Burlen Loring [mailto:bloring at lbl.gov] Sent: Tuesday, October 14, 2014 5:18 PM To: Scott, W Alan; Aashish Chaudhary; B.W.H. van Beest Cc: ParaView Subject: Re: [EXTERNAL] Re: [Paraview] BOX -> volume? Hi Alan, That is a different issue. You're seeing that warning because your Mesa build is missing floating point support. Some of the older releases didn't have it, however newer releases do. It's always been a build option that's off by default because of patent issues, so you need to expeictly enable it when compiling mesa. The intention behind that (in hindsight annoying) warning is to alert you are using an ancient version of mesa and or that you may have not built mesa with floating point support. At the time the warning seemed reasonable to me since without floating point support the projected tets algorithm *could produce precision related artifacts depending on data and rendering parameters and downloading and installing a newer mesa (or simply recompiling your existing mesa build with floating point support enabled) is a relatively easy fix. For me I'd rather know that there's potentially a problem and update mesa, rather than scratch my head about why there are artifacts in my rendering. With regard to the current thread and Bertwim's issue with ATI GPU, I think the code is currently doing the right thing because projected tets algorithm hangs on the ATI card. A workaround if you have an ATI card is to set the "select mapper" to "Bunyk ray cast" Burlen On 10/14/2014 03:53 PM, Scott, W Alan wrote: Burlen/ Aashish/ B.W.H, I haven?t been following this thread, but just a note that there is a bug already written about this code, and a similar (but not exact) error. Said bug report is here: http://www.paraview.org/Bug/view.php?id=15020 It is slated to be fixed in a minor release within the next few months. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Burlen Loring Sent: Tuesday, October 14, 2014 4:47 PM To: Aashish Chaudhary; B.W.H. van Beest Cc: ParaView Subject: [EXTERNAL] Re: [Paraview] BOX -> volume? You could try it without modifying any code by setting the following cmake variable. VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON and recompile ParaView. With my ATI Radeon HD7780 projected tetrahedra just hangs. Burlen On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: Looks like certain extensions are still not quite working on yours system even with the proprietary driver. I will see if I can run your code on my laptop but that would be for tomorrow. ** Assuming that this is not data dependent issue (which it should not). I think its probably this line causing the issue: bool driverSupport #if defined(__APPLE__) = true; #else = !(extensions->DriverIsATI() && (extensions->GetDriverGLVersionMajor() >= 3)) || extensions->GetIgnoreDriverBugs("ATI texturing bug"); #endif On line number 181: can you change this code to : this->HasHardwareSupport = renwin != NULL && this->IsSupported(renwin); to this->HasHardwareSupport = 1; - Aashish On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > wrote: Progress indeed. But I don't understand what you are saying about the transfer function. I' starting to wonder if I have two issues occurring simultaneously. In a new thread I just posted I described my problem in getting the colours in place. I need to write to a vtk file first and load it back. I just found that when I just did that and then switched fo volume rendering, an error was there about the absence of an opengl extension: ERROR: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, line 185 vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required extensions are not supported. This is complete unknown terrain for me. Regards, Bertwim On 10/14/2014 09:58 PM, Burlen Loring wrote: progress! it sounds like volume rendering is working on the wavelet dataset. You do need the scalars for volume rendering, so make sure you have those when you try. You need to select the scalars in the drop down also, I usually do this before changing to the volume representation. You also may need to edit the transfer function. For testing you could make the opacity over the entire scalar range in which case you should see a solid cube. If you've done all that and don't see anything it's likely that the dataset is messed up. Add a dataset->Print(cerr) statement to the end of your request data, look in the information panel and verify correct number of points and scalar ranges. If all else fails post the dataset to the list. After creating your cube go to the file menu and "save data". On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: Hi Burlen, I have upgraded to the AMD drivers. Thanks for the hint. It has improved the situation a bit. Furthermore, I created the wavelet source. When selecting "volume" representation, I do see a three 3 picture, in all 5 volume rendering mode (smart, raycast and texture mapping, ray cast only, texture mapping only, GPU based). The picture a rather fuzzy, but then I don't know what I'm supposed to see here. The good news is that the openGL errors I had before when displaying a wavelet, now have gone. The situation with my own cube, though, has unchanged. unfortunately. The cube disappears in "volume" representation node, also when I re-inserted scalar values for each of the 8 vertices. Regards, Bertwim On 10/14/2014 06:06 PM, Burlen Loring wrote: Hi Bertwim, In recent releases of ParaView I have experienced issues/flakeyness with volume rendering. Something you should try: Create the wavelet source, then in the properties panel find "volume rendering mode" and set it to "ray cast only". This has worked for me on a number of systems. may or may not work, but worth a try. The output you pasted below shows that although you've got a sweet ATI GPU you're not taking advantage of it! You're using the Intel integrated GPU with Mesa drivers. If I were you I would install proprietary the AMD drivers. This should give you nice performance boost and may even solve the OpenGL errors you reported, which these days are as often (or more) a result of bugs in the Mesa drivers than in VTK. Burlen On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: OS: OpenSuSe 13.1 # lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] # glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, GL_ARB_texture_float, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, GL_MESA_ycbcr_texture, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc OpenGL version string: 3.0 Mesa 9.2.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, GL_ARB_color_buffer_float, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_shader_objects, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_texture_array, GL_MESA_texture_signed_rgba, GL_MESA_window_pos, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, GL_NV_primitive_restart, GL_NV_texgen_reflection, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays 20 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 44 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: What graphics card / graphics driver version / OS this system has? - Aashish On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest > wrote: Hi Aashish, This is what I do: 1. start paraview 2. Sources -> Wavelet -> Apply. A cube is displayed (Outline representation). 3. Select 'Volume" representation" cube disappears. Then: ===================== Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation Generic Warning: In /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, line 487 failed at glBindTexture 1 OpenGL errors detected 0 : (1282) Invalid operation ========================= On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: So when you created a wavelet source and change the representation to volume you got the errors? Can you post those errors? Thanks, On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest > wrote: Aashish, Thanks for the suggestion. However, doing this gives me all kinds of opengl errors (invalid instruction). Besides that, the wavelet gives me a cube indeed, but I need to understand when I can have a volume rendering. I created new Source's (e.g. tri-prism, a wedge, a box with boundaries of finite thickness etc.). But I cannot get volume rendering to work, grrrrrr. (See other thread) Kind Regards, Bertwim On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: You can create a wavelet source and then display it as a volume. On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest > wrote: Can perhaps somebody point me how to address the following. When I create a new source (say: a box) I get an a box that can be displayed via its surfaces, its constituing points, or wireframe representation. But I need a volume rendering (so that I can add e.g. a clipping plane) How do I get that? Regards, Bertwim _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -- | Aashish Chaudhary | Technical Leader | Kitware Inc. | http://www.kitware.com/company/team/chaudhary.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From michoski at gmail.com Tue Oct 14 20:14:20 2014 From: michoski at gmail.com (Craig Michoski) Date: Tue, 14 Oct 2014 19:14:20 -0500 Subject: [Paraview] ParaView with VirtualGL Message-ID: Hi all, I'm running ParaView via VirtualGL through a remote host, and experiencing some difficulties. The host has me set an env variable, export NO_HOSTSORT=1 (and I'm not sure what this is trying to accomplish). Paraview for the most part runs fine, but when I try to run a programmable python filter, I get no output to the output window to speak of. For example, just typing print "anything" does nothing. Does anyone have any suggestions? Thanks, Craig From bloring at lbl.gov Tue Oct 14 22:55:56 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 14 Oct 2014 19:55:56 -0700 Subject: [Paraview] [EXTERNAL] Re: BOX -> volume? In-Reply-To: <79f3790ae87f4d0bb9706ddbe82a75a0@ES05AMSNLNT.srn.sandia.gov> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543DA7D8.2090807@lbl.gov> <914eb2b027994c51a3ca7801c58ca6ca@ES05AMSNLNT.srn.sandia.gov> <543DAF13.7040408@lbl.gov> <79f3790ae87f4d0bb9706ddbe82a75a0@ES05AMSNLNT.srn.sandia.gov> Message-ID: <543DE23C.6050109@lbl.gov> the warning is just a warning the algorithm continues to work as it had in the past. (right?) Maybe the warning could be removed in release builds. On 10/14/2014 04:45 PM, Scott, W Alan wrote: > > Understand. I replied into the bug itself, but the simple answer is > that I didn?t build this version of Mesa ? it was provided by a vender > and I have no control over it. And it has to work on this version of > Mesa, as it has before. > > Alan > > *From:*Burlen Loring [mailto:bloring at lbl.gov] > *Sent:* Tuesday, October 14, 2014 5:18 PM > *To:* Scott, W Alan; Aashish Chaudhary; B.W.H. van Beest > *Cc:* ParaView > *Subject:* Re: [EXTERNAL] Re: [Paraview] BOX -> volume? > > Hi Alan, > > That is a different issue. You're seeing that warning because your > Mesa build is missing floating point support. Some of the older > releases didn't have it, however newer releases do. It's always been a > build option that's off by default because of patent issues, so you > need to expeictly enable it when compiling mesa. The intention behind > that (in hindsight annoying) warning is to alert you are using an > ancient version of mesa and or that you may have not built mesa with > floating point support. At the time the warning seemed reasonable to > me since without floating point support the projected tets algorithm > *could produce precision related artifacts depending on data and > rendering parameters and downloading and installing a newer mesa (or > simply recompiling your existing mesa build with floating point > support enabled) is a relatively easy fix. For me I'd rather know that > there's potentially a problem and update mesa, rather than scratch my > head about why there are artifacts in my rendering. > > With regard to the current thread and Bertwim's issue with ATI GPU, I > think the code is currently doing the right thing because projected > tets algorithm hangs on the ATI card. > > A workaround if you have an ATI card is to set the "select mapper" to > "Bunyk ray cast" > > Burlen > > On 10/14/2014 03:53 PM, Scott, W Alan wrote: > > Burlen/ Aashish/ B.W.H, > > I haven?t been following this thread, but just a note that there > is a bug already written about this code, and a similar (but not > exact) error. Said bug report is here: > http://www.paraview.org/Bug/view.php?id=15020 It is slated to be > fixed in a minor release within the next few months. > > Alan > > *From:*ParaView [mailto:paraview-bounces at paraview.org] *On Behalf > Of *Burlen Loring > *Sent:* Tuesday, October 14, 2014 4:47 PM > *To:* Aashish Chaudhary; B.W.H. van Beest > *Cc:* ParaView > *Subject:* [EXTERNAL] Re: [Paraview] BOX -> volume? > > You could try it without modifying any code by setting the > following cmake variable. > > VTK_IGNORE_GLDRIVER_BUGS:BOOL=ON > > and recompile ParaView. With my ATI Radeon HD7780 projected > tetrahedra just hangs. > > Burlen > > On 10/14/2014 02:07 PM, Aashish Chaudhary wrote: > > Looks like certain extensions are still not quite working on > yours system even with the proprietary driver. I will see if I > can run your code on my laptop but that would be for tomorrow. > > ** Assuming that this is not data dependent issue (which it > should not). > > I think its probably this line causing the issue: > > > *bool* > > driverSupport > > > > > > > * #if* > > * defined(__APPLE__)* > > > > > > > *=* true; > > > > > > > ** > > *#else* > > > > > > > *=* *!*(extensions*->*DriverIsATI() > > > > > > > *&&* > > (extensions*->*GetDriverGLVersionMajor() *>=* 3)) > > > > > > > *||* extensions*->*GetIgnoreDriverBugs("ATI texturing bug"); > > > > > > > ** > > *#endif* > > > > > > > > > On line number 181: can you change this code to : > > *this->*HasHardwareSupport > > *=* > > renwin > > *!=* > > NULL > > *&&* > > *this->*IsSupported(renwin); > > to > > *this->*HasHardwareSupport > > *=* > > 1; > > > > > - Aashish > > On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > > wrote: > > Progress indeed. But I don't understand what you are saying > about the transfer function. > > I' starting to wonder if I have two issues occurring > simultaneously. > In a new thread I just posted I described my problem in > getting the colours in place. > I need to write to a vtk file first and load it back. I just > found that when I just did that > and then switched fo volume rendering, an error was there > about the absence > of an opengl extension: > > ERROR: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, > line 185 > vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required > extensions are not supported. > > This is complete unknown terrain for me. > > Regards, > Bertwim > > > > > On 10/14/2014 09:58 PM, Burlen Loring wrote: > > progress! it sounds like volume rendering is working on > the wavelet dataset. > > You do need the scalars for volume rendering, so make sure > you have those when you try. You need to select the > scalars in the drop down also, I usually do this before > changing to the volume representation. You also may need > to edit the transfer function. For testing you could make > the opacity over the entire scalar range in which case you > should see a solid cube. > > If you've done all that and don't see anything it's likely > that the dataset is messed up. Add a dataset->Print(cerr) > statement to the end of your request data, look in the > information panel and verify correct number of points and > scalar ranges. > > If all else fails post the dataset to the list. After > creating your cube go to the file menu and "save data". > > > On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: > > Hi Burlen, > > I have upgraded to the AMD drivers. Thanks for the > hint. It has improved the situation a bit. > > Furthermore, I created the wavelet source. When > selecting "volume" representation, I do see a three 3 > picture, in all 5 volume rendering mode (smart, > raycast and texture mapping, ray cast only, texture > mapping only, GPU based). The picture a rather fuzzy, > but then I don't know what I'm supposed to see here. > The good news is that the openGL errors I had before > when displaying a wavelet, now have gone. > > The situation with my own cube, though, has unchanged. > unfortunately. > The cube disappears in "volume" representation node, > also when I re-inserted scalar values for each of the > 8 vertices. > > Regards, > Bertwim > > On 10/14/2014 06:06 PM, Burlen Loring wrote: > > Hi Bertwim, > > In recent releases of ParaView I have experienced > issues/flakeyness with volume rendering. Something > you should try: Create the wavelet source, then in > the properties panel find "volume rendering mode" > and set it to "ray cast only". This has worked > for me on a number of systems. may or may not > work, but worth a try. > > The output you pasted below shows that although > you've got a sweet ATI GPU you're not taking > advantage of it! You're using the Intel integrated > GPU with Mesa drivers. If I were you I would > install proprietary the AMD drivers > . This > should give you nice performance boost and may > even solve the OpenGL errors you reported, which > these days are as often (or more) a result of bugs > in the Mesa drivers than in VTK. > > Burlen > > On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: > > > > OS: OpenSuSe 13.1 > > # lspci | grep -i vga > 00:02.0 VGA compatible controller: Intel > Corporation 4th Gen Core Processor Integrated > Graphics Controller (rev 06) > 01:00.0 VGA compatible controller: Advanced > Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD > 8670A/8670M/8750M] > > # glxinfo > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, > GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, > GLX_OML_swap_method, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, > GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, GLX_SGI_swap_control > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_create_context_robustness, > GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, > GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_fbconfig_packed_float, > GLX_EXT_framebuffer_sRGB, > GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, > GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, > GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, > GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, > GLX_SGI_swap_control, GLX_SGI_video_sync > GLX version: 1.4 > GLX extensions: > GLX_ARB_create_context, > GLX_ARB_create_context_profile, > GLX_ARB_get_proc_address, > GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, > GLX_EXT_import_context, > GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, > GLX_MESA_copy_sub_buffer, > GLX_MESA_multithread_makecurrent, > GLX_MESA_swap_control, > GLX_OML_swap_method, GLX_OML_sync_control, > GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, > GLX_SGI_swap_control, GLX_SGI_video_sync > OpenGL vendor string: Intel Open Source > Technology Center > OpenGL renderer string: Mesa DRI Intel(R) > Haswell Mobile > OpenGL core profile version string: 3.1 (Core > Profile) Mesa 9.2.3 > OpenGL core profile shading language version > string: 1.40 > OpenGL core profile context flags: (none) > OpenGL core profile extensions: > GL_3DFX_texture_compression_FXT1, > GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, > GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, > GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, > GL_ARB_base_instance, > GL_ARB_blend_func_extended, > GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, > GL_ARB_depth_clamp, GL_ARB_draw_buffers, > GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, > GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, > GL_ARB_point_sprite, GL_ARB_provoking_vertex, > GL_ARB_robustness, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, > GL_ARB_shader_texture_lod, > GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, GL_ARB_sync, > GL_ARB_texture_buffer_object, > GL_ARB_texture_buffer_object_rgb32, > GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map_array, > GL_ARB_texture_float, > GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, > GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, > GL_ARB_timer_query, GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, > GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, > GL_ATI_blend_equation_separate, > GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_blend_equation_separate, > GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, > GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_sRGB, > GL_EXT_packed_depth_stencil, GL_EXT_packed_float, > GL_EXT_pixel_buffer_object, > GL_EXT_provoking_vertex, GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, > GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, > GL_EXT_texture_sRGB, > GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, > GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, > GL_EXT_timer_query, GL_EXT_transform_feedback, > GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, > GL_MESA_pack_invert, > GL_MESA_texture_signed_rgba, > GL_MESA_ycbcr_texture, > GL_NV_conditional_render, > GL_NV_depth_clamp, GL_NV_packed_depth_stencil, > GL_OES_EGL_image, GL_OES_read_format, > GL_S3_s3tc > > OpenGL version string: 3.0 Mesa 9.2.3 > OpenGL shading language version string: 1.30 > OpenGL context flags: (none) > OpenGL extensions: > GL_3DFX_texture_compression_FXT1, > GL_AMD_draw_buffers_blend, > GL_ANGLE_texture_compression_dxt3, > GL_ANGLE_texture_compression_dxt5, > GL_APPLE_object_purgeable, > GL_APPLE_packed_pixels, > GL_APPLE_vertex_array_object, > GL_ARB_ES2_compatibility, > GL_ARB_ES3_compatibility, > GL_ARB_blend_func_extended, > GL_ARB_color_buffer_float, > GL_ARB_copy_buffer, GL_ARB_debug_output, > GL_ARB_depth_buffer_float, > GL_ARB_depth_clamp, GL_ARB_depth_texture, > GL_ARB_draw_buffers, > GL_ARB_draw_buffers_blend, > GL_ARB_draw_elements_base_vertex, > GL_ARB_draw_instanced, > GL_ARB_explicit_attrib_location, > GL_ARB_fragment_coord_conventions, > GL_ARB_fragment_program, > GL_ARB_fragment_program_shadow, > GL_ARB_fragment_shader, > GL_ARB_framebuffer_object, > GL_ARB_framebuffer_sRGB, > GL_ARB_get_program_binary, > GL_ARB_half_float_pixel, > GL_ARB_half_float_vertex, > GL_ARB_instanced_arrays, > GL_ARB_internalformat_query, > GL_ARB_invalidate_subdata, > GL_ARB_map_buffer_range, GL_ARB_multisample, > GL_ARB_multitexture, > GL_ARB_occlusion_query, GL_ARB_occlusion_query2, > GL_ARB_pixel_buffer_object, > GL_ARB_point_parameters, GL_ARB_point_sprite, > GL_ARB_provoking_vertex, > GL_ARB_robustness, GL_ARB_sampler_objects, > GL_ARB_seamless_cube_map, > GL_ARB_shader_bit_encoding, > GL_ARB_shader_objects, > GL_ARB_shader_texture_lod, > GL_ARB_shading_language_100, > GL_ARB_shading_language_420pack, > GL_ARB_shading_language_packing, > GL_ARB_shadow, GL_ARB_sync, > GL_ARB_texture_border_clamp, > GL_ARB_texture_compression, > GL_ARB_texture_compression_rgtc, > GL_ARB_texture_cube_map, > GL_ARB_texture_cube_map_array, > GL_ARB_texture_env_add, > GL_ARB_texture_env_combine, > GL_ARB_texture_env_crossbar, > GL_ARB_texture_env_dot3, > GL_ARB_texture_float, > GL_ARB_texture_mirrored_repeat, > GL_ARB_texture_multisample, > GL_ARB_texture_non_power_of_two, > GL_ARB_texture_query_lod, > GL_ARB_texture_rectangle, > GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, > GL_ARB_texture_storage, > GL_ARB_texture_storage_multisample, > GL_ARB_texture_swizzle, > GL_ARB_timer_query, GL_ARB_transpose_matrix, > GL_ARB_uniform_buffer_object, > GL_ARB_vertex_array_bgra, > GL_ARB_vertex_array_object, > GL_ARB_vertex_buffer_object, > GL_ARB_vertex_program, GL_ARB_vertex_shader, > GL_ARB_vertex_type_2_10_10_10_rev, > GL_ARB_window_pos, > GL_ATI_blend_equation_separate, > GL_ATI_draw_buffers, > GL_ATI_envmap_bumpmap, > GL_ATI_separate_stencil, > GL_ATI_texture_env_combine3, > GL_ATI_texture_float, GL_EXT_abgr, > GL_EXT_bgra, GL_EXT_blend_color, > GL_EXT_blend_equation_separate, > GL_EXT_blend_func_separate, > GL_EXT_blend_minmax, GL_EXT_blend_subtract, > GL_EXT_compiled_vertex_array, > GL_EXT_copy_texture, GL_EXT_draw_buffers2, > GL_EXT_draw_instanced, > GL_EXT_draw_range_elements, GL_EXT_fog_coord, > GL_EXT_framebuffer_blit, > GL_EXT_framebuffer_multisample, > GL_EXT_framebuffer_multisample_blit_scaled, > GL_EXT_framebuffer_object, > GL_EXT_framebuffer_sRGB, > GL_EXT_gpu_program_parameters, > GL_EXT_multi_draw_arrays, > GL_EXT_packed_depth_stencil, > GL_EXT_packed_float, GL_EXT_packed_pixels, > GL_EXT_pixel_buffer_object, > GL_EXT_point_parameters, > GL_EXT_polygon_offset, GL_EXT_provoking_vertex, > GL_EXT_rescale_normal, > GL_EXT_secondary_color, > GL_EXT_separate_shader_objects, > GL_EXT_separate_specular_color, > GL_EXT_shadow_funcs, > GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, > GL_EXT_subtexture, GL_EXT_texture, > GL_EXT_texture3D, > GL_EXT_texture_array, > GL_EXT_texture_compression_dxt1, > GL_EXT_texture_compression_rgtc, > GL_EXT_texture_cube_map, > GL_EXT_texture_edge_clamp, > GL_EXT_texture_env_add, > GL_EXT_texture_env_combine, > GL_EXT_texture_env_dot3, > GL_EXT_texture_filter_anisotropic, > GL_EXT_texture_integer, > GL_EXT_texture_lod_bias, > GL_EXT_texture_object, GL_EXT_texture_rectangle, > GL_EXT_texture_sRGB, > GL_EXT_texture_sRGB_decode, > GL_EXT_texture_shared_exponent, > GL_EXT_texture_snorm, > GL_EXT_texture_swizzle, > GL_EXT_timer_query, GL_EXT_transform_feedback, > GL_EXT_vertex_array, > GL_EXT_vertex_array_bgra, > GL_IBM_multimode_draw_arrays, > GL_IBM_rasterpos_clip, > GL_IBM_texture_mirrored_repeat, > GL_INGR_blend_func_separate, > GL_MESA_pack_invert, > GL_MESA_texture_array, > GL_MESA_texture_signed_rgba, > GL_MESA_window_pos, GL_MESA_ycbcr_texture, > GL_NV_blend_square, > GL_NV_conditional_render, > GL_NV_depth_clamp, GL_NV_light_max_exponent, > GL_NV_packed_depth_stencil, > GL_NV_primitive_restart, > GL_NV_texgen_reflection, > GL_NV_texture_env_combine4, > GL_NV_texture_rectangle, GL_OES_EGL_image, > GL_OES_read_format, > GL_S3_s3tc, GL_SGIS_generate_mipmap, > GL_SGIS_texture_border_clamp, > GL_SGIS_texture_edge_clamp, > GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays > > 20 GLX Visuals > visual x bf lv rg d st colorbuffer sr > ax dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a F gb > bf th cl r g b a ns b eat > ---------------------------------------------------------------------------- > 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 16 16 16 16 0 0 Slow > 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 4 1 None > 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 8 1 None > 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 4 1 None > 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 8 1 None > 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 16 16 16 16 0 0 Slow > 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 4 1 None > 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 8 1 None > 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 4 1 None > 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 8 1 None > 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > > 44 GLXFBConfigs: > visual x bf lv rg d st colorbuffer sr > ax dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a F gb > bf th cl r g b a ns b eat > ---------------------------------------------------------------------------- > 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 0 0 None > 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . > 0 0 0 0 0 0 0 0 0 None > 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 24 8 0 0 0 0 0 0 None > 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . > 0 24 8 0 0 0 0 0 0 None > 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 16 16 16 0 0 0 Slow > 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 16 16 16 16 0 0 Slow > 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 4 1 None > 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 8 1 None > 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 4 1 None > 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 8 1 None > 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 4 1 None > 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 8 1 None > 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 4 1 None > 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 8 1 None > 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 0 0 None > 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . > 0 0 0 0 0 0 0 0 0 None > 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 24 8 0 0 0 0 0 0 None > 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . > 0 24 8 0 0 0 0 0 0 None > 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . > 0 0 0 0 0 0 0 0 0 None > 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 0 0 None > 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 16 16 16 0 0 0 Slow > 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 0 0 None > 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 16 16 16 16 0 0 Slow > 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 4 1 None > 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 0 0 0 0 0 0 8 1 None > 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 4 1 None > 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . > 0 16 0 0 0 0 0 8 1 None > 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 4 1 None > 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 0 0 0 0 0 0 8 1 None > 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 4 1 None > 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . > 0 24 8 0 0 0 0 8 1 None > > > On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: > > What graphics card / graphics driver > version / OS this system has? > > - Aashish > > On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. > van Beest > wrote: > > Hi Aashish, > > This is what I do: > 1. start paraview > 2. Sources -> Wavelet -> Apply. > A cube is displayed (Outline > representation). > 3. Select 'Volume" representation" > > cube disappears. Then: > ===================== > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors > detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors > detected > 0 : (1282) Invalid operation > > > > Generic Warning: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, > line 487 > failed at glBindTexture 1 OpenGL errors > detected > 0 : (1282) Invalid operation > ========================= > > > > > > > > On 10/13/2014 07:35 PM, Aashish Chaudhary > wrote: > > So when you created a wavelet source > and change the representation to > volume you got the errors? Can you > post those errors? > > Thanks, > > On Mon, Oct 13, 2014 at 1:33 PM, > B.W.H. van Beest > wrote: > > Aashish, > > Thanks for the suggestion. > > However, doing this gives me all kinds > of opengl errors (invalid instruction). > > Besides that, the wavelet gives me a > cube indeed, but I need to understand > when > I can have a volume rendering. I > created new Source's (e.g. tri-prism, > a wedge, > a box with boundaries of finite > thickness etc.). But I cannot get > volume rendering > to work, grrrrrr. (See other thread) > > Kind Regards, > Bertwim > > > > > On 10/13/2014 05:28 PM, Aashish > Chaudhary wrote: > > You can create a wavelet source > and then display it as a volume. > > On Fri, Oct 10, 2014 at 3:45 PM, > B.W.H. van Beest > wrote: > > Can perhaps somebody point me how > to address the following. > > When I create a new source (say: a > box) I get an a box that > can be displayed via its surfaces, > its constituing points, or wireframe > representation. > But I need a volume rendering (so > that I can add e.g. a clipping plane) > How do I get that? > > Regards, > Bertwim > > > > _______________________________________________ > Powered by www.kitware.com > > > Visit other Kitware open-source > projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and > check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to > subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > http://www.kitware.com/company/team/chaudhary.html/ > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > http://www.kitware.com/company/team/chaudhary.html/ > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| > http://www.kitware.com/company/team/chaudhary.html/ > > > > > > _______________________________________________ > > Powered bywww.kitware.com > > > > Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > _______________________________________________ > > Powered bywww.kitware.com > > > > Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > -- > > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. / > > /| http://www.kitware.com/company/team/chaudhary.html/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbording at ivec.org Wed Oct 15 05:19:09 2014 From: cbording at ivec.org (Chris Bording) Date: Wed, 15 Oct 2014 17:19:09 +0800 Subject: [Paraview] Unable to compile with Python enabled Message-ID: <543E3C0D.1040203@ivec.org> Hi, Okay spent a couple days experimenting with building Paraview-4.1 and 4.2. on our local GPU-cluster it is The SGI supercomputer comprises 96 nodes, each containing two 6-core Intel Xeon X5650 CPUs, an NVIDIA Tesla C2075 GPU and 72 GB RAM, resulting in a system containing 1152 cores and 96 GPUs. I keep hitting the build.make errors when I set -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DUSE_SYSTEM_python:BOOL=ON -DPYTHON_EXECUTABLE:FILEPATH=$PYTHON_DIR/bin/python -DPYTHON_LIBRARY:FILEPATH=$PYTHONPATH -DPYTHON_INCLUDE_DIR:PATH=$PYTHON_DIR/include/python$PYTHON_LIB_VERSION The error.... make[2]: Entering directory `/group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build' VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build.make:127: *** target pattern contains no `%'. Stop. if I go to the VTK/Utilities/PythonInterpreter/CmakeFiles/vtkPythonInterpreter.dir [cbording at login2 PythonInterpreter]$ cd CMakeFiles/ [cbording at login2 CMakeFiles]$ ls CMakeDirectoryInformation.cmake progress.marks vtkPythonInterpreter.cmake vtkPythonInterpreter.dir [cbording at login2 CMakeFiles]$ cd vtkPythonInterpreter.dir/ [cbording at login2 vtkPythonInterpreter.dir]$ ls build.make cmake_clean.cmake DependInfo.cmake depend.make flags.make Labels.txt link.txt progress.make [cbording at login2 vtkPythonInterpreter.dir]$ pwd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir so build.make is there and offending line is in RED # Object files for target vtkPythonInterpreter vtkPythonInterpreter_OBJECTS = \ "CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInterpreter.cxx.o" \ "CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInteractiveInterpreter.cxx.o" # External object files for target vtkPythonInterpreter vtkPythonInterpreter_EXTERNAL_OBJECTS = lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInterpreter.cxx.o lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInteractiveInterpreter.cxx.o lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build.make lib/libvtkPythonInterpreter-pv4.1.so.1: lib/libvtkCommonCore-pv4.1.so.1 lib/libvtkPythonInterpreter-pv4.1.so.1: /ivec/apps/gcc/4.4.7/python/2.6.9/lib/python2.6/site-packages:/ivec/python/lib/python2.6/site-packages lib/libvtkPythonInterpreter-pv4.1.so.1: lib/libvtksys-pv4.1.so.1 lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/link.txt @$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --red --bold "Linking CXX shared library ../../../lib/libvtkPythonInterpreter-pv4.1.so" cd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Utilities/PythonInterpreter && $(CMAKE_COMMAND) -E cmake_link_script CMakeFiles/vtkPythonInterpreter.dir/link.txt --verbose=$(VERBOSE) cd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Utilities/PythonInterpreter && $(CMAKE_COMMAND) -E cmake_symlink_library ../../../lib/libvtkPythonInterpreter-pv4.1.so.1 ../../../lib/libvtkPythonInterpreter-pv4.1.so.1 ../../../lib/libvtkPythonInterpreter-pv4.1.so lib/libvtkPythonInterpreter-pv4.1.so: lib/libvtkPythonInterpreter-pv4.1.so.1 # Rule to build all files generated by this target. VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build: lib/libvtkPythonInterpreter-pv4.1.so .PHONY : VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build Here is what is in the python module. ------------------------------------------------------------------- /ivec/modulefiles/apps/python/2.6.9: setenv PYTHON_VERSION 2.6.9 setenv PYTHON_LIB_VERSION 2.6 setenv PYTHON_DIR /ivec/apps/gcc/4.4.7/python/2.6.9 setenv IBS_PYTHON_LIBDIR lib prepend-path PATH /ivec/apps/gcc/4.4.7/python/2.6.9/bin prepend-path LD_LIBRARY_PATH /ivec/apps/gcc/4.4.7/python/2.6.9/lib prepend-path MANPATH /ivec/apps/gcc/4.4.7/python/2.6.9/share/man prepend-path PYTHONPATH /ivec/apps/gcc/4.4.7/python/2.6.9/lib/python2.6/site-packages Currently Loaded Modulefiles: 1) ibs/1.5.7 2) gcc/4.4.7 .. loading openmpi/1.6.5 .. loading python/2.6.9 .. loading qt/4.8.4 .. loading zlib/1.2.7 .. loading hdf5/1.8.10 .. loading netcdf/4.2.1.1 .. loading boost/1.55.0 .. loading silo/4.8 .. check for build only modules .. you are using cmake, will use ibs_cmake_build to process .. loading cmake/2.8.12.1 .. unpacking the source code for paraview 4.1.0 .... only need to unpack first source .. compiling paraview 4.1.0 with gcc/4.4.7 Running cmake -DCMAKE_INSTALL_PREFIX=/group/director100/cbording/vis/apps/gcc/4.4.7/paraview/4.1.0 -DBUILD_TESTING:BOOL=OFF -DBUILD_EXAMPLES:BOOL=OFF -DPARAVIEW_USE_MPI:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so;/usr/lib64/libdl.so" -DMPI_C_INCLUDE_PATH:PATH=$MPI_HOME/include -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so;/usr/lib64/libdl.so" -DMPI_CXX_INCLUDE_PATH:PATH=$MPI_HOME/include -DMPI_Fortran_LIBRARIES:PATH=$MPI_HOME/lib/libmpi.so -DMPI_Fortran_INCLUDE_PATH:PATH=$MPI_HOME/include -DCMAKE_BUILD_TYPE:STRING=Release -DZLIB_INCLUDE_DIR:PATH=$IBS_ZLIB_HOME/include -DZLIB_LIBRARY:PATH=$IBS_ZLIB_HOME/lib/libz.so -DPARAVIEW_ENABLE_WEB:BOOL=OFF -DPARAVIEW_DATA_ROOT:FILEPATH=/group/director100/cbording/vis/ParaViewData-v4.1 -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON -DBoost_DIR:PATH=$Boost_DIR -DBoost_INCLUDE_DIR:PATH=$Boost_DIR/include -DBoost_LIBRARY_DIRS:PATH=$Boost_DIR/lib -DVISIT_BUILD_READER_Silo:BOOL=ON -DSILO_INCLUDE_DIR:PATH=$IBS_SILO_HOME/include -DSILO_LIBRARY:FILEPATH=$IBS_SILO_HOME/lib/libsiloh5.so -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DUSE_SYSTEM_python:BOOL=ON -DPYTHON_EXECUTABLE:FILEPATH=$PYTHON_DIR/bin/python -DPYTHON_LIBRARY:FILEPATH=$PYTHONPATH -DPYTHON_INCLUDE_DIR:PATH=$PYTHON_DIR/include/python$PYTHON_LIB_VERSION -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON .. in /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build -- The C compiler identification is GNU 4.4.7 -- The CXX compiler identification is GNU 4.4.7 -- Check for working C compiler: /ivec/devel/gcc/4.4.7/openmpi/1.6.5/bin/mpicc -- Check for working C compiler: /ivec/devel/gcc/4.4.7/openmpi/1.6.5/bin/mpicc -- works -- Detecting C compiler ABI info If I configure the build without python then it does not fail. I have tried with both python version 2.6.9 and 2.7.6 Do I have the right flags set for python. more importantly to I have the right configure flags set so we can run the pvserver and have it use the GPUs? The ultimate goal is to be able to render on the cluster and view on the multi-display panels we have. Next I want to install paraview on our new CRAY XC-30, any suggestions on configuring that? I found this in the from the good folks at CSCS for their CRAY XC-30 however ours is all Haswell without GPUs. We also have a SGI UV2000 has anyone installed paraview on large single image systems? Thanks in advance! -- R.Christopher Bording Supercomputing Specialist iVEC Supercomputing Team T +61 8 6488 6905 F +61 8 6488 8088 E cbording at ivec.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Wed Oct 15 10:49:33 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 15 Oct 2014 14:49:33 +0000 Subject: [Paraview] Unable to compile with Python enabled (UNCLASSIFIED) In-Reply-To: <543E3C0D.1040203@ivec.org> References: <543E3C0D.1040203@ivec.org> Message-ID: Classification: UNCLASSIFIED Caveats: NONE Chris, Maybe try the http://www.paraview.org/Wiki/ParaView/Superbuild route? I can confirm that for ParaView v4.2.0-1 and Superbuild, ParaView is building for CRAY XC-30, SGI UV And we are building it with -DUSE_SYSTEM_python:BOOL=OFF HTH, -simon -----Original Message----- From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Chris Bording Sent: Wednesday, October 15, 2014 5:19 AM To: paraview at paraview.org Subject: [Paraview] Unable to compile with Python enabled Hi, Okay spent a couple days experimenting with building Paraview-4.1 and 4.2. on our local GPU-cluster it is The SGI supercomputer comprises 96 nodes, each containing two 6-core Intel Xeon X5650 CPUs, an NVIDIA Tesla C2075 GPU and 72 GB RAM, resulting in a system containing 1152 cores and 96 GPUs. I keep hitting the build.make errors when I set -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DUSE_SYSTEM_python:BOOL=ON -DPYTHON_EXECUTABLE:FILEPATH=$PYTHON_DIR/bin/python -DPYTHON_LIBRARY:FILEPATH=$PYTHONPATH -DPYTHON_INCLUDE_DIR:PATH=$PYTHON_DIR/include/python$PYTHON_LIB_VERSION The error.... make[2]: Entering directory `/group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build' VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build.ma ke:127: *** target pattern contains no `%'. Stop. if I go to the VTK/Utilities/PythonInterpreter/CmakeFiles/vtkPythonInterpreter.dir [cbording at login2 PythonInterpreter]$ cd CMakeFiles/ [cbording at login2 CMakeFiles]$ ls CMakeDirectoryInformation.cmake progress.marks vtkPythonInterpreter.cmake vtkPythonInterpreter.dir [cbording at login2 CMakeFiles]$ cd vtkPythonInterpreter.dir/ [cbording at login2 vtkPythonInterpreter.dir]$ ls build.make cmake_clean.cmake DependInfo.cmake depend.make flags.make Labels.txt link.txt progress.make [cbording at login2 vtkPythonInterpreter.dir]$ pwd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Uti lities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir so build.make is there and offending line is in RED # Object files for target vtkPythonInterpreter vtkPythonInterpreter_OBJECTS = \ "CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInterpreter.cxx.o" \ "CMakeFiles/vtkPythonInterpreter.dir/vtkPythonInteractiveInterpreter.cxx.o" # External object files for target vtkPythonInterpreter vtkPythonInterpreter_EXTERNAL_OBJECTS = lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/vtkPytho nInterpreter.cxx.o lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/vtkPytho nInteractiveInterpreter.cxx.o lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build.ma ke lib/libvtkPythonInterpreter-pv4.1.so.1: lib/libvtkCommonCore-pv4.1.so.1 lib/libvtkPythonInterpreter-pv4.1.so.1: /ivec/apps/gcc/4.4.7/python/2.6.9/lib/python2.6/site-packages:/ivec/python/l ib/python2.6/site-packages lib/libvtkPythonInterpreter-pv4.1.so.1: lib/libvtksys-pv4.1.so.1 lib/libvtkPythonInterpreter-pv4.1.so.1: VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/link.txt @$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --red --bold "Linking CXX shared library ../../../lib/libvtkPythonInterpreter-pv4.1.so" cd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Uti lities/PythonInterpreter && $(CMAKE_COMMAND) -E cmake_link_script CMakeFiles/vtkPythonInterpreter.dir/link.txt --verbose=$(VERBOSE) cd /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build/VTK/Uti lities/PythonInterpreter && $(CMAKE_COMMAND) -E cmake_symlink_library ../../../lib/libvtkPythonInterpreter-pv4.1.so.1 ../../../lib/libvtkPythonInterpreter-pv4.1.so.1 ../../../lib/libvtkPythonInterpreter-pv4.1.so lib/libvtkPythonInterpreter-pv4.1.so: lib/libvtkPythonInterpreter-pv4.1.so.1 # Rule to build all files generated by this target. VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build: lib/libvtkPythonInterpreter-pv4.1.so .PHONY : VTK/Utilities/PythonInterpreter/CMakeFiles/vtkPythonInterpreter.dir/build Here is what is in the python module. ------------------------------------------------------------------- /ivec/modulefiles/apps/python/2.6.9: setenv PYTHON_VERSION 2.6.9 setenv PYTHON_LIB_VERSION 2.6 setenv PYTHON_DIR /ivec/apps/gcc/4.4.7/python/2.6.9 setenv IBS_PYTHON_LIBDIR lib prepend-path PATH /ivec/apps/gcc/4.4.7/python/2.6.9/bin prepend-path LD_LIBRARY_PATH /ivec/apps/gcc/4.4.7/python/2.6.9/lib prepend-path MANPATH /ivec/apps/gcc/4.4.7/python/2.6.9/share/man prepend-path PYTHONPATH /ivec/apps/gcc/4.4.7/python/2.6.9/lib/python2.6/site-packages Currently Loaded Modulefiles: 1) ibs/1.5.7 2) gcc/4.4.7 .. loading openmpi/1.6.5 .. loading python/2.6.9 .. loading qt/4.8.4 .. loading zlib/1.2.7 .. loading hdf5/1.8.10 .. loading netcdf/4.2.1.1 .. loading boost/1.55.0 .. loading silo/4.8 .. check for build only modules .. you are using cmake, will use ibs_cmake_build to process .. loading cmake/2.8.12.1 .. unpacking the source code for paraview 4.1.0 .... only need to unpack first source .. compiling paraview 4.1.0 with gcc/4.4.7 Running cmake -DCMAKE_INSTALL_PREFIX=/group/director100/cbording/vis/apps/gcc/4.4.7/paravi ew/4.1.0 -DBUILD_TESTING:BOOL=OFF -DBUILD_EXAMPLES:BOOL=OFF -DPARAVIEW_USE_MPI:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON -DPARAVIEW_BUILD_QT_GUI:BOOL=OFF -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so;/usr/lib64/libdl.so" -DMPI_C_INCLUDE_PATH:PATH=$MPI_HOME/include -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so;/usr/lib64/libdl.so" -DMPI_CXX_INCLUDE_PATH:PATH=$MPI_HOME/include -DMPI_Fortran_LIBRARIES:PATH=$MPI_HOME/lib/libmpi.so -DMPI_Fortran_INCLUDE_PATH:PATH=$MPI_HOME/include -DCMAKE_BUILD_TYPE:STRING=Release -DZLIB_INCLUDE_DIR:PATH=$IBS_ZLIB_HOME/include -DZLIB_LIBRARY:PATH=$IBS_ZLIB_HOME/lib/libz.so -DPARAVIEW_ENABLE_WEB:BOOL=OFF -DPARAVIEW_DATA_ROOT:FILEPATH=/group/director100/cbording/vis/ParaViewData-v 4.1 -DPARAVIEW_USE_VISITBRIDGE:BOOL=ON -DBoost_DIR:PATH=$Boost_DIR -DBoost_INCLUDE_DIR:PATH=$Boost_DIR/include -DBoost_LIBRARY_DIRS:PATH=$Boost_DIR/lib -DVISIT_BUILD_READER_Silo:BOOL=ON -DSILO_INCLUDE_DIR:PATH=$IBS_SILO_HOME/include -DSILO_LIBRARY:FILEPATH=$IBS_SILO_HOME/lib/libsiloh5.so -DPARAVIEW_ENABLE_PYTHON:BOOL=ON -DUSE_SYSTEM_python:BOOL=ON -DPYTHON_EXECUTABLE:FILEPATH=$PYTHON_DIR/bin/python -DPYTHON_LIBRARY:FILEPATH=$PYTHONPATH -DPYTHON_INCLUDE_DIR:PATH=$PYTHON_DIR/include/python$PYTHON_LIB_VERSION -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON .. in /group/director100/cbording/vis/build/ParaView-v4.1.0/paraview-build -- The C compiler identification is GNU 4.4.7 -- The CXX compiler identification is GNU 4.4.7 -- Check for working C compiler: /ivec/devel/gcc/4.4.7/openmpi/1.6.5/bin/mpicc -- Check for working C compiler: /ivec/devel/gcc/4.4.7/openmpi/1.6.5/bin/mpicc -- works -- Detecting C compiler ABI info If I configure the build without python then it does not fail. I have tried with both python version 2.6.9 and 2.7.6 Do I have the right flags set for python. more importantly to I have the right configure flags set so we can run the pvserver and have it use the GPUs? The ultimate goal is to be able to render on the cluster and view on the multi-display panels we have. Next I want to install paraview on our new CRAY XC-30, any suggestions on configuring that? I found this in the from the good folks at CSCS for their CRAY XC-30 however ours is all Haswell without GPUs. We also have a SGI UV2000 has anyone installed paraview on large single image systems? Thanks in advance! -- R.Christopher Bording Supercomputing Specialist iVEC Supercomputing Team T +61 8 6488 6905 F +61 8 6488 8088 E cbording at ivec.org Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 9990 bytes Desc: not available URL: From kit.chambers.kc at gmail.com Wed Oct 15 11:51:46 2014 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Wed, 15 Oct 2014 16:51:46 +0100 Subject: [Paraview] service_identity issue Message-ID: Hi All, I am currently getting the following error message when running a matplot lib script through a ParaView derived application. lib/paraview-4.2/site-packages/twisted/internet/_sslverify.py:184: UserWarning: You do not have the service_identity module installed. Please install it from . Without the service_identity module and a recent enough pyOpenSSL tosupport it, Twisted can perform only rudimentary TLS client hostnameverification. Many valid certificate/hostname mappings may be rejected. verifyHostname, VerificationError = _selectVerifyImplementation() I have tried various things: -- installing python3-openssl -- installing python-pip and through that service_identity. -- recompiles tce. However, the message keeps coming up. I am running Ubuntu 14.04 using the git ParaView. Has anyone else seen this? Any ideas are welcome. Cheers Kit Chambers -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Oct 15 13:43:59 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 15 Oct 2014 13:43:59 -0400 Subject: [Paraview] service_identity issue In-Reply-To: References: Message-ID: I am not sure why that module is being imported. Is something importing it manually? On Wed, Oct 15, 2014 at 11:51 AM, Kit Chambers wrote: > Hi All, > > I am currently getting the following error message when running a matplot > lib script through a ParaView derived application. > > lib/paraview-4.2/site-packages/twisted/internet/_sslverify.py:184: > UserWarning: You do not have the service_identity module installed. Please > install it from . Without the > service_identity module and a recent enough pyOpenSSL tosupport it, Twisted > can perform only rudimentary TLS client hostnameverification. Many valid > certificate/hostname mappings may be rejected. > verifyHostname, VerificationError = _selectVerifyImplementation() > > I have tried various things: > -- installing python3-openssl > -- installing python-pip and through that service_identity. > -- recompiles tce. > > However, the message keeps coming up. I am running Ubuntu 14.04 using the > git ParaView. Has anyone else seen this? Any ideas are welcome. > > Cheers > > Kit Chambers > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From michoski at gmail.com Wed Oct 15 16:52:26 2014 From: michoski at gmail.com (Craig Michoski) Date: Wed, 15 Oct 2014 15:52:26 -0500 Subject: [Paraview] ParaView with VirtualGL Message-ID: Ah, okay, I figured out part of my problem. I had to connect to the server and display the output on the server side, not just the client side, which I guess is where the print commands redirects. Now I have several other problems. First: 1) the print command outputs n_processor number of outputs. Can I make this just one value? For example, if I am summing a value over a mesh, I just want to total value output once over the entire mesh? Is this possible? 2) I am getting an error when trying to simply get my loaded inputs. When I do: print "Gets here!" alpha0 = inputs[0].PointData['alpha_0'] Traceback (most recent call last): File "", line 22, in File "", line 8, in RequestData TypeError: 'NoneType' object has no attribute '__getitem__' I don't understand what is hppening here, can anyone help please? Craig From berk.geveci at kitware.com Wed Oct 15 18:38:47 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 15 Oct 2014 18:38:47 -0400 Subject: [Paraview] ParaView with VirtualGL In-Reply-To: References: Message-ID: Hi Craig, Which version of ParaView are you using? What file format are you loading? Best, -berk On Wed, Oct 15, 2014 at 4:52 PM, Craig Michoski wrote: > Ah, okay, I figured out part of my problem. I had to connect to the > server and display the output on the server side, not just the client > side, which I guess is where the print commands redirects. Now I have > several other problems. First: > > 1) the print command outputs n_processor number of outputs. Can I > make this just one value? For example, if I am summing a value over a > mesh, I just want to total value output once over the entire mesh? Is > this possible? > > 2) I am getting an error when trying to simply get my loaded inputs. > When I do: > > print "Gets here!" > > alpha0 = inputs[0].PointData['alpha_0'] > > Traceback (most recent call last): > File "", line 22, in > File "", line 8, in RequestData > TypeError: 'NoneType' object has no attribute '__getitem__' > > I don't understand what is hppening here, can anyone help please? > > Craig > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michoski at gmail.com Wed Oct 15 18:47:23 2014 From: michoski at gmail.com (Craig Michoski) Date: Wed, 15 Oct 2014 17:47:23 -0500 Subject: [Paraview] ParaView with VirtualGL In-Reply-To: References: Message-ID: Hi Berk, Thanks for the response. I see I'm at the fount. So, I'm using paraview 4.1.0, and loading everything in from vtu files. The basic python filter I'm trying to get running in parallel is this below, for a basic integration along a dimension in two of the loaded fields (one a scalar alpha_0, the other a two dimensional vector sigma_0_0__sigma_0_1). ---------------- import numpy alpha0 = inputs[0].PointData['alpha_0'] alpha1 = inputs[0].PointData['alpha_0'] sigma0 = inputs[0].PointData['sigma_0_0__sigma_0_1'] pdi = self.GetInputDataObject(0,0) bg_field = 1 pdi = self.GetInputDataObject(0,0) pdo = self.GetOutputDataObject(0) numPoints = pdi.GetNumberOfPoints() import time ind=self.GetInput() iin=ind.GetInformation() timestep = time.clock() dx = 100.0 dy = 100.0 for (j,alpha) in enumerate(alpha0): x1,y1,z1 = pdi.GetPoint(j)[:3] x2,y2,z2 = pdi.GetPoint(j+1)[:3] if abs(x2-x1) <= dx and abs(x2-x1)>0: dx = x2 - x1 if abs(y2-y1) <= dy and abs(y2-y1)>1e-6: dy = y2 - y1 counter = 0 last_step = -1.0 prev_x = 0.0 efold = numpy.zeros(numPoints) y_first = -1.0 for (j,alpha) in enumerate(alpha0): x,y,z = pdi.GetPoint(j) if x<380.0 and x>70.0 and y==0.0: y_first = [] for (i,alpha_1) in enumerate(alpha1): x1,y1,z1 = pdi.GetPoint(i) if x1 == x and y1 == y: for (k,sigmax) in enumerate(sigma0): x2,y2,z2 = pdi.GetPoint(i) if x2 == x1: #and y2 == y1: if y2 not in y_first: efold[k] += ( 1.0/exp(2.0*alpha_1) ) * sigmax[0] * dy #exp(alpha_1)*sigmax[0]*dy y_first.append(y2) if x!=last_step: counter = counter + 1 print "y_integrated_chi_at1(",floor(timestep),",", counter,") = ", efold[k]/377.0, ";" print "x(",counter,") = ", x, ";" last_step = x ---------------- Craig On Wed, Oct 15, 2014 at 5:38 PM, Berk Geveci wrote: > Hi Craig, > > Which version of ParaView are you using? > > What file format are you loading? > > Best, > -berk > > On Wed, Oct 15, 2014 at 4:52 PM, Craig Michoski > wrote: > >> Ah, okay, I figured out part of my problem. I had to connect to the >> server and display the output on the server side, not just the client >> side, which I guess is where the print commands redirects. Now I have >> several other problems. First: >> >> 1) the print command outputs n_processor number of outputs. Can I >> make this just one value? For example, if I am summing a value over a >> mesh, I just want to total value output once over the entire mesh? Is >> this possible? >> >> 2) I am getting an error when trying to simply get my loaded inputs. >> When I do: >> >> print "Gets here!" >> >> alpha0 = inputs[0].PointData['alpha_0'] >> >> Traceback (most recent call last): >> File "", line 22, in >> File "", line 8, in RequestData >> TypeError: 'NoneType' object has no attribute '__getitem__' >> >> I don't understand what is hppening here, can anyone help please? >> >> Craig >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Wed Oct 15 19:08:54 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Wed, 15 Oct 2014 19:08:54 -0400 Subject: [Paraview] ParaView with VirtualGL In-Reply-To: References: Message-ID: First things first, you need to upgrade to 4.2 :-) It has significant improvements to the Python API and you are like to need them. When running in parallel, if you want to restrict which ranks print out information, you can do something like this: import vtk contr = vtk.vtkMultiProcessController.GetGlobalController() rank = contr.GetLocalProcessId() if id == 0: print 'hello' You will likely need MPI methods here. See: http://www.kitware.com/blog/home/post/716 The reason you are seeing the error is that one of the ranks does not have any data. I can't remember from the top of my head if we automatically distribute vtu files. Try applying the D3 filter and see what happens. Best, -berk On Wed, Oct 15, 2014 at 6:47 PM, Craig Michoski wrote: > Hi Berk, > > Thanks for the response. I see I'm at the fount. So, I'm using paraview > 4.1.0, and loading everything in from vtu files. The basic python filter > I'm trying to get running in parallel is this below, for a basic > integration along a dimension in two of the loaded fields (one a scalar > alpha_0, the other a two dimensional vector sigma_0_0__sigma_0_1). > > ---------------- > import numpy > > alpha0 = inputs[0].PointData['alpha_0'] > alpha1 = inputs[0].PointData['alpha_0'] > sigma0 = inputs[0].PointData['sigma_0_0__sigma_0_1'] > > pdi = self.GetInputDataObject(0,0) > bg_field = 1 > pdi = self.GetInputDataObject(0,0) > pdo = self.GetOutputDataObject(0) > numPoints = pdi.GetNumberOfPoints() > import time > > ind=self.GetInput() > iin=ind.GetInformation() > timestep = time.clock() > > dx = 100.0 > dy = 100.0 > > for (j,alpha) in enumerate(alpha0): > x1,y1,z1 = pdi.GetPoint(j)[:3] > x2,y2,z2 = pdi.GetPoint(j+1)[:3] > if abs(x2-x1) <= dx and abs(x2-x1)>0: > dx = x2 - x1 > if abs(y2-y1) <= dy and abs(y2-y1)>1e-6: > dy = y2 - y1 > > counter = 0 > last_step = -1.0 > prev_x = 0.0 > efold = numpy.zeros(numPoints) > y_first = -1.0 > > for (j,alpha) in enumerate(alpha0): > x,y,z = pdi.GetPoint(j) > if x<380.0 and x>70.0 and y==0.0: > y_first = [] > for (i,alpha_1) in enumerate(alpha1): > x1,y1,z1 = pdi.GetPoint(i) > if x1 == x and y1 == y: > for (k,sigmax) in enumerate(sigma0): > x2,y2,z2 = pdi.GetPoint(i) > if x2 == x1: #and y2 == y1: > if y2 not in y_first: > efold[k] += ( 1.0/exp(2.0*alpha_1) ) * > sigmax[0] * dy #exp(alpha_1)*sigmax[0]*dy > y_first.append(y2) > > if x!=last_step: > counter = counter + 1 > print "y_integrated_chi_at1(",floor(timestep),",", > counter,") = ", efold[k]/377.0, ";" > print "x(",counter,") = ", x, ";" > last_step = x > ---------------- > > Craig > > > On Wed, Oct 15, 2014 at 5:38 PM, Berk Geveci > wrote: > >> Hi Craig, >> >> Which version of ParaView are you using? >> >> What file format are you loading? >> >> Best, >> -berk >> >> On Wed, Oct 15, 2014 at 4:52 PM, Craig Michoski >> wrote: >> >>> Ah, okay, I figured out part of my problem. I had to connect to the >>> server and display the output on the server side, not just the client >>> side, which I guess is where the print commands redirects. Now I have >>> several other problems. First: >>> >>> 1) the print command outputs n_processor number of outputs. Can I >>> make this just one value? For example, if I am summing a value over a >>> mesh, I just want to total value output once over the entire mesh? Is >>> this possible? >>> >>> 2) I am getting an error when trying to simply get my loaded inputs. >>> When I do: >>> >>> print "Gets here!" >>> >>> alpha0 = inputs[0].PointData['alpha_0'] >>> >>> Traceback (most recent call last): >>> File "", line 22, in >>> File "", line 8, in RequestData >>> TypeError: 'NoneType' object has no attribute '__getitem__' >>> >>> I don't understand what is hppening here, can anyone help please? >>> >>> Craig >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Wed Oct 15 21:58:50 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 16 Oct 2014 03:58:50 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> Message-ID: <543F265A.5000505@xs4all.nl> I am still busy with finding out which etensions are needed, and how I can enable them. THis opebnGL-world is a bit alien to me, so it will take some time. Regards, Bertwim On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: > Looks like certain extensions are still not quite working on yours > system even with the proprietary driver. I will see if I can run your > code on my laptop but that would be for tomorrow. > > ** Assuming that this is not data dependent issue (which it should not). > > I think its probably this line causing the issue: > > bool driverSupport > > #if defined(__APPLE__) > > = true; > > #else > > = !(extensions->DriverIsATI() > > && (extensions->GetDriverGLVersionMajor() >= 3)) > > || extensions->GetIgnoreDriverBugs("ATI texturing bug"); > > #endif > > > > On line number 181: can you change this code to : > > this->HasHardwareSupport=renwin!=NULL&&this->IsSupported(renwin); > to > this->HasHardwareSupport=1; > > - Aashish > > > > On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > wrote: > > Progress indeed. But I don't understand what you are saying about > the transfer function. > > I' starting to wonder if I have two issues occurring simultaneously. > In a new thread I just posted I described my problem in getting > the colours in place. > I need to write to a vtk file first and load it back. I just > found that when I just did that > and then switched fo volume rendering, an error was there about > the absence > of an opengl extension: > > ERROR: In > /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, > line 185 > vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required > extensions are not supported. > > This is complete unknown terrain for me. > > Regards, > Bertwim > > > > On 10/14/2014 09:58 PM, Burlen Loring wrote: >> progress! it sounds like volume rendering is working on the >> wavelet dataset. >> >> You do need the scalars for volume rendering, so make sure you >> have those when you try. You need to select the scalars in the >> drop down also, I usually do this before changing to the volume >> representation. You also may need to edit the transfer function. >> For testing you could make the opacity over the entire scalar >> range in which case you should see a solid cube. >> >> If you've done all that and don't see anything it's likely that >> the dataset is messed up. Add a dataset->Print(cerr) statement >> to the end of your request data, look in the information panel >> and verify correct number of points and scalar ranges. >> >> If all else fails post the dataset to the list. After creating >> your cube go to the file menu and "save data". >> >> >> On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >>> Hi Burlen, >>> >>> I have upgraded to the AMD drivers. Thanks for the hint. It has >>> improved the situation a bit. >>> >>> Furthermore, I created the wavelet source. When selecting >>> "volume" representation, I do see a three 3 picture, in all 5 >>> volume rendering mode (smart, raycast and texture mapping, ray >>> cast only, texture mapping only, GPU based). The picture a >>> rather fuzzy, but then I don't know what I'm supposed to see >>> here. The good news is that the openGL errors I had before when >>> displaying a wavelet, now have gone. >>> >>> The situation with my own cube, though, has unchanged. >>> unfortunately. >>> The cube disappears in "volume" representation node, also when >>> I re-inserted scalar values for each of the 8 vertices. >>> >>> Regards, >>> Bertwim >>> >>> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>>> Hi Bertwim, >>>> >>>> In recent releases of ParaView I have experienced >>>> issues/flakeyness with volume rendering. Something you should >>>> try: Create the wavelet source, then in the properties panel >>>> find "volume rendering mode" and set it to "ray cast only". >>>> This has worked for me on a number of systems. may or may not >>>> work, but worth a try. >>>> >>>> The output you pasted below shows that although you've got a >>>> sweet ATI GPU you're not taking advantage of it! You're using >>>> the Intel integrated GPU with Mesa drivers. If I were you I >>>> would install proprietary the AMD drivers >>>> . This should give you >>>> nice performance boost and may even solve the OpenGL errors you >>>> reported, which these days are as often (or more) a result of >>>> bugs in the Mesa drivers than in VTK. >>>> >>>> Burlen >>>> >>>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>>> >>>>> >>>>> OS: OpenSuSe 13.1 >>>>> >>>>> # lspci | grep -i vga >>>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen >>>>> Core Processor Integrated Graphics Controller (rev 06) >>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, >>>>> Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>>> >>>>> # glxinfo >>>>> name of display: :0 >>>>> display: :0 screen: 0 >>>>> direct rendering: Yes >>>>> server glx vendor string: SGI >>>>> server glx version string: 1.4 >>>>> server glx extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>>> GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>>> GLX_MESA_copy_sub_buffer, >>>>> GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, >>>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>>> GLX_SGI_swap_control >>>>> client glx vendor string: Mesa Project and SGI >>>>> client glx version string: 1.4 >>>>> client glx extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>>> GLX_ARB_multisample, >>>>> GLX_EXT_create_context_es2_profile, >>>>> GLX_EXT_fbconfig_packed_float, >>>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, >>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>> GLX_SGIS_multisample, >>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>> GLX_SGIX_visual_select_group, >>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>> GLX_SGI_video_sync >>>>> GLX version: 1.4 >>>>> GLX extensions: >>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>> GLX_EXT_visual_rating, >>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>> GLX_SGIS_multisample, >>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>> GLX_SGIX_visual_select_group, >>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>> GLX_SGI_video_sync >>>>> OpenGL vendor string: Intel Open Source Technology Center >>>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >>>>> OpenGL core profile shading language version string: 1.40 >>>>> OpenGL core profile context flags: (none) >>>>> OpenGL core profile extensions: >>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>> GL_ANGLE_texture_compression_dxt3, >>>>> GL_ANGLE_texture_compression_dxt5, >>>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>>> GL_ARB_debug_output, >>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>> GL_ARB_draw_buffers, >>>>> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >>>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>>> GL_ARB_provoking_vertex, >>>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>>> GL_ARB_seamless_cube_map, >>>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>>> GL_ARB_texture_buffer_object, >>>>> GL_ARB_texture_buffer_object_rgb32, >>>>> GL_ARB_texture_compression_rgtc, >>>>> GL_ARB_texture_cube_map_array, >>>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>> GL_ARB_texture_rgb10_a2ui, >>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>> GL_ARB_uniform_buffer_object, >>>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, >>>>> GL_EXT_abgr, >>>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>>> GL_EXT_framebuffer_multisample, >>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>>> GL_EXT_packed_float, >>>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>>> GL_EXT_texture_array, >>>>> GL_EXT_texture_compression_dxt1, >>>>> GL_EXT_texture_compression_rgtc, >>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>> GL_EXT_transform_feedback, >>>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>>> GL_MESA_ycbcr_texture, >>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>> GL_NV_packed_depth_stencil, >>>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>>> >>>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>>> OpenGL shading language version string: 1.30 >>>>> OpenGL context flags: (none) >>>>> OpenGL extensions: >>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>> GL_ANGLE_texture_compression_dxt3, >>>>> GL_ANGLE_texture_compression_dxt5, >>>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>>> GL_ARB_debug_output, >>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>> GL_ARB_depth_texture, >>>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>>> GL_ARB_explicit_attrib_location, >>>>> GL_ARB_fragment_coord_conventions, >>>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>>> GL_ARB_multisample, >>>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>>> GL_ARB_occlusion_query2, >>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>>> GL_ARB_point_sprite, >>>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>>> GL_ARB_sampler_objects, >>>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>>> GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, >>>>> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >>>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>> GL_ARB_texture_rgb10_a2ui, >>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>> GL_ARB_transpose_matrix, >>>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, >>>>> GL_EXT_abgr, >>>>> GL_EXT_bgra, GL_EXT_blend_color, >>>>> GL_EXT_blend_equation_separate, >>>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>>> GL_EXT_blend_subtract, >>>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>>> GL_EXT_draw_buffers2, >>>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>>> GL_EXT_fog_coord, >>>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>> GL_EXT_framebuffer_object, >>>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>>> GL_EXT_pixel_buffer_object, >>>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>>> GL_EXT_provoking_vertex, >>>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>>> GL_EXT_separate_shader_objects, >>>>> GL_EXT_separate_specular_color, >>>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, >>>>> GL_EXT_stencil_wrap, >>>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>>> GL_EXT_texture_rectangle, >>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>> GL_EXT_transform_feedback, >>>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>>> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >>>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>>> GL_MESA_texture_signed_rgba, >>>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, >>>>> GL_NV_blend_square, >>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>> GL_NV_light_max_exponent, >>>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>>> GL_NV_texture_rectangle, GL_OES_EGL_image, >>>>> GL_OES_read_format, >>>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, >>>>> GL_SGIS_texture_border_clamp, >>>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>>> GL_SUN_multi_draw_arrays >>>>> >>>>> 20 GLX Visuals >>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>> accumbuffer ms cav >>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g >>>>> b a ns b eat >>>>> ---------------------------------------------------------------------------- >>>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> >>>>> 44 GLXFBConfigs: >>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>> accumbuffer ms cav >>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r g >>>>> b a ns b eat >>>>> ---------------------------------------------------------------------------- >>>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>> 16 0 0 0 Slow >>>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>> 16 0 0 0 Slow >>>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 0 0 None >>>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>> 16 16 0 0 Slow >>>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 4 1 None >>>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>> 0 0 8 1 None >>>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 4 1 None >>>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>> 0 0 8 1 None >>>>> >>>>> >>>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>>> What graphics card / graphics driver version / OS this system >>>>>> has? >>>>>> >>>>>> - Aashish >>>>>> >>>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>>>> > wrote: >>>>>> >>>>>> Hi Aashish, >>>>>> >>>>>> This is what I do: >>>>>> 1. start paraview >>>>>> 2. Sources -> Wavelet -> Apply. >>>>>> A cube is displayed (Outline representation). >>>>>> 3. Select 'Volume" representation" >>>>>> >>>>>> cube disappears. Then: >>>>>> ===================== >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> >>>>>> >>>>>> >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> >>>>>> >>>>>> >>>>>> Generic Warning: In >>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>> line 487 >>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>> 0 : (1282) Invalid operation >>>>>> ========================= >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>>> So when you created a wavelet source and change the >>>>>>> representation to volume you got the errors? Can you >>>>>>> post those errors? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>>> > wrote: >>>>>>> >>>>>>> Aashish, >>>>>>> >>>>>>> Thanks for the suggestion. >>>>>>> >>>>>>> However, doing this gives me all kinds of opengl >>>>>>> errors (invalid instruction). >>>>>>> >>>>>>> Besides that, the wavelet gives me a cube indeed, >>>>>>> but I need to understand when >>>>>>> I can have a volume rendering. I created new >>>>>>> Source's (e.g. tri-prism, a wedge, >>>>>>> a box with boundaries of finite thickness etc.). But >>>>>>> I cannot get volume rendering >>>>>>> to work, grrrrrr. (See other thread) >>>>>>> >>>>>>> Kind Regards, >>>>>>> Bertwim >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>>> You can create a wavelet source and then display it >>>>>>>> as a volume. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Can perhaps somebody point me how to address >>>>>>>> the following. >>>>>>>> >>>>>>>> When I create a new source (say: a box) I get >>>>>>>> an a box that >>>>>>>> can be displayed via its surfaces, its >>>>>>>> constituing points, or wireframe >>>>>>>> representation. >>>>>>>> But I need a volume rendering (so that I can >>>>>>>> add e.g. a clipping plane) >>>>>>>> How do I get that? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Bertwim >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Powered by www.kitware.com >>>>>>>> >>>>>>>> Visit other Kitware open-source projects at >>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>> >>>>>>>> Please keep messages on-topic and check the >>>>>>>> ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>>> >>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /| Aashish Chaudhary >>>>>>>> | Technical Leader >>>>>>>> | Kitware Inc. >>>>>>>> / >>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> /| Aashish Chaudhary >>>>>>> | Technical Leader >>>>>>> | Kitware Inc. >>>>>>> / >>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> /| Aashish Chaudhary >>>>>> | Technical Leader >>>>>> | Kitware Inc. >>>>>> / >>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Wed Oct 15 22:30:37 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Thu, 16 Oct 2014 04:30:37 +0200 Subject: [Paraview] Cannot add 3D cell to umesh Message-ID: <543F2DCD.9030204@xs4all.nl> Hello, I'm wondering how I should add e.g. a 3D cell like a tri-prism (a prism with identical triangles as base) or a skew variation of it (triangles are not the same) to an (empty) unstructured grid. The 3D cell itself is described by its points (vtkPoints) and its faces, collected in a vtkCellArray. Is this a cell of type VTK_POLYHEDRON? Do I need to add such a cell face by face, or what? There are quite a few methods in vtkUnstructuredGrid that promise to do so or something similar, but so far I did not have success (segfaults). The methods I found from the documentation are: vtkIdType InsertNextCell (int type, vtkIdType npts, vtkIdType *pts) vtkIdType InsertNextCell (int type, vtkIdList *ptIds) void SetCells (int type, vtkCellArray *cells) void SetCells (int *types, vtkCellArray *cells) void SetCells (vtkUnsignedCharArray *cellTypes, vtkIdTypeArray *cellLocations, vtkCellArray *cells) int InsertNextLinkedCell (int type, int npts, vtkIdType *pts) I'm afraid I don't really appreciate the differences. Any help is appreciated. Kind Regards, Bertwim From kit.chambers.kc at gmail.com Thu Oct 16 05:27:12 2014 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Thu, 16 Oct 2014 10:27:12 +0100 Subject: [Paraview] service_identity issue In-Reply-To: References: Message-ID: <543F8F70.1040109@googlemail.com> As a follow up on this it turns out my python plotting script had the following line: from twisted.protocols.amp import AMP It turns out twisted is only required for paraview web (which I am not using) so commented this out and it works fine. I am sure you can all rest easy now. On 15/10/2014 18:43, Utkarsh Ayachit wrote: > I am not sure why that module is being imported. Is something > importing it manually? > > On Wed, Oct 15, 2014 at 11:51 AM, Kit Chambers > wrote: >> Hi All, >> >> I am currently getting the following error message when running a matplot >> lib script through a ParaView derived application. >> >> lib/paraview-4.2/site-packages/twisted/internet/_sslverify.py:184: >> UserWarning: You do not have the service_identity module installed. Please >> install it from . Without the >> service_identity module and a recent enough pyOpenSSL tosupport it, Twisted >> can perform only rudimentary TLS client hostnameverification. Many valid >> certificate/hostname mappings may be rejected. >> verifyHostname, VerificationError = _selectVerifyImplementation() >> >> I have tried various things: >> -- installing python3-openssl >> -- installing python-pip and through that service_identity. >> -- recompiles tce. >> >> However, the message keeps coming up. I am running Ubuntu 14.04 using the >> git ParaView. Has anyone else seen this? Any ideas are welcome. >> >> Cheers >> >> Kit Chambers >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From redkite at virgin.net Thu Oct 16 07:03:23 2014 From: redkite at virgin.net (redkite) Date: Thu, 16 Oct 2014 12:03:23 +0100 Subject: [Paraview] Bug? - ExtractedSelection is mapped between Extracted Blocks Message-ID: <543FA5FB.9010303@virgin.net> Hi, I understand that objects in a vtk pipeline will be updated if something earlier changes, but I can see no use for this behaviour (and it's quite a pain to me ;). To replicate: 1) Load the can.ex2 example and apply the 'Extract Block' filter. 2) Navigate to the ExtractBlock/'Block indices' menu and switch on 'Unnamed block ID 1' so you can see the semi-circular can object. 3) Click the 'Select Points On' rubber-band selection button and draw a rectangle of points on the can. 4) Click the 'Extract Selection' button. 5) Go back to the ExtractBlock/'Block indices' menu, switch off 'Unnamed block ID 1' and turn on 'Unnamed block ID 2' You will see that the extracted selection is mapped to apparently arbitrary points in or on the second block (you may need to change opacity to see the mapped points). Other similar but strange behaviour occurs if you select across blocks and switch to view just one or a few of them. I note that if I obtain the pqSelectionManager I can clear the selection, but as the docs say, the selection still exists somewhere in the vtk code. Is there a better way to control this action? (Tested with ParaView 4.1 and Windows and Ubuntu, and 4.2 on Ubuntu.) Thanks, Richard ps I tried searching through the archives for block/selection issues and I'm a bit surprised not to find anything like this before.... though it may be related to issue raised by Robert Ainsworth ?? [so I've just cc'd this to him] (http://paraview.markmail.org/message/z4eq4hj2zerrwste?q=selection+on+blocks&page=3) From kit.chambers.kc at gmail.com Thu Oct 16 07:29:56 2014 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Thu, 16 Oct 2014 12:29:56 +0100 Subject: [Paraview] Labeling specific points in dataset Message-ID: Hi Everyone, I have a dataset of about 1000 or so points and I want to label say every 100'th point with the point id. I can use the DataLabelRepresentation if I want to label every point, but as far as I can tell this cannot label only certain points it is everything or nothing. I could also create a new dataset with every 100th point in it and use that with the DataLabelRepresentation but then the point ids would be wrong. Any ideas or suggestions are welcome. Cheers Kit -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Thu Oct 16 08:19:10 2014 From: david.thompson at kitware.com (David Thompson) Date: Thu, 16 Oct 2014 08:19:10 -0400 Subject: [Paraview] Labeling specific points in dataset In-Reply-To: References: Message-ID: Hi Kit, If you can find a way to create a selection of the points, the selected points can be labeled. Is that feasible? David On Oct 16, 2014, at 7:29, Kit Chambers wrote: > Hi Everyone, > > I have a dataset of about 1000 or so points and I want to label say every 100'th point with the point id. I can use the DataLabelRepresentation if I want to label every point, but as far as I can tell this cannot label only certain points it is everything or nothing. I could also create a new dataset with every 100th point in it and use that with the DataLabelRepresentation but then the point ids would be wrong. > > Any ideas or suggestions are welcome. > > Cheers > > Kit > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From biddisco at cscs.ch Thu Oct 16 08:58:14 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Thu, 16 Oct 2014 12:58:14 +0000 Subject: [Paraview] Catalyst question In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> Andy I appear to be suffering from a confusion of what the catalyst framework does - or how it is used ... I had imagined that I?d run a simulation on N ranks, have catalyst bound to them and be able to do vis on those N ranks. But in fact, when I connect to a live simulation, I have to ?extract? results from them and then render them back on the client. Is this the case or did I miss something? The parallel image generation appears to work as advertised, but the images go off to disk and not to the renderwindow. Is there a way on configuring it so that I can see the actual rendering taking place in the renderview? I wanted to display the contents of a custom render plugin using cuda based rendering on many GPUs and be able to interact with it, but I am obviously missing something in my setup. thanks JB From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: 26 August 2014 15:34 To: Biddiscombe, John A. Cc: paraview at paraview.org Subject: Re: [Paraview] Catalyst question Hi John, This live capability is now available and recently has been cleaned up quite a bit. There are still a couple more small changes that are waiting a code review process before they go into the master branch. The user's guide needs an update for a bunch of new information (live, catalyst editions, zero-copy arrays) that's important for Catalyst. We're also doing some preliminary testing with a newly developed ADIOS writer for better IO performance as well. Getting back to the live viz stuff, when you create a Catalyst Python script and export it using the wizard you'll have the option to enable live viz (it's the same wizard page as the screenshot output specification). Then, while your simulation is running use the Catalyst->Connect option to connect. There are two tests (pv.CatalystLiveSetBreakpoint and pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live functionality which now includes the option to set a breakpoint in the simulation. If you get a chance to try it out, let me know what you think. Andy On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: Dear Catalyst people I dragged out an old simulation demo I created some time ago and got it working with paraview/catalyst from git master branch - my plan was to test a live visualization of the simulation with the paraview GUI connected to the simulation. I had thought this capability was now possible, but I have not been following development closely and it looks like I was mistaken. Is it possible to visualize the simulation live - rather than just generate images (which works fine). (I had a quick skim through the user manual, but didn?t see this feature mentioned). Thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Oct 16 09:16:43 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Oct 2014 09:16:43 -0400 Subject: [Paraview] Labeling specific points in dataset In-Reply-To: References: Message-ID: You can tell DataLabelRepresentation to label using any data array. By adding an array such as "original ids" or something during the extraction processes, you can tell the representation to use that array for labeling instead. That's pretty much on extract-selection filters work too. On Thu, Oct 16, 2014 at 7:29 AM, Kit Chambers wrote: > Hi Everyone, > > I have a dataset of about 1000 or so points and I want to label say every > 100'th point with the point id. I can use the DataLabelRepresentation if I > want to label every point, but as far as I can tell this cannot label only > certain points it is everything or nothing. I could also create a new > dataset with every 100th point in it and use that with the > DataLabelRepresentation but then the point ids would be wrong. > > Any ideas or suggestions are welcome. > > Cheers > > Kit > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From andy.bauer at kitware.com Thu Oct 16 10:08:30 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 16 Oct 2014 10:08:30 -0400 Subject: [Paraview] Catalyst question In-Reply-To: <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> Message-ID: Hi John, You are correct that the rendering that's done by Catalyst to create images is not directly available to the client. I hope to fix this in the not too distant future. The idea being that you select which Catalyst view you want to interact with and then it switches the view to that such that you can update view options like camera angles, lookup tables, etc. as well as output frequency and filename for that view when from Catalyst. As for creating a live connection to a Catalyst enabled simulation, maybe the thing you want is to use a live connection with pausing the simulation to get to data at a specific point in the simulation. If this data is too much to download to the client you can create a separate pvserver to connect to Catalyst and then connect your client to that pvserver. I haven't tried this but Utkarsh said that it was designed to work this way. Does this sound like a reasonable way of doing what you want? Now that the live functionality also has the ability to pause a simulation, it's feasible that we could go the libsim route and have Catalyst act as server for everything instead of downloading it to the client or separate server. We just haven't had a lot of impetus for providing that use case yet so we've focused on other stuff. Regards, Andy On Thu, Oct 16, 2014 at 8:58 AM, Biddiscombe, John A. wrote: > Andy > > > > I appear to be suffering from a confusion of what the catalyst framework > does - or how it is used ... > > > > I had imagined that I?d run a simulation on N ranks, have catalyst bound > to them and be able to do vis on those N ranks. But in fact, when I connect > to a live simulation, I have to ?extract? results from them and then render > them back on the client. > > > > Is this the case or did I miss something? > > > > The parallel image generation appears to work as advertised, but the > images go off to disk and not to the renderwindow. Is there a way on > configuring it so that I can see the actual rendering taking place in the > renderview? I wanted to display the contents of a custom render plugin > using cuda based rendering on many GPUs and be able to interact with it, > but I am obviously missing something in my setup. > > > > thanks > > > > JB > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* 26 August 2014 15:34 > *To:* Biddiscombe, John A. > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Catalyst question > > > > Hi John, > > > This live capability is now available and recently has been cleaned up > quite a bit. There are still a couple more small changes that are waiting a > code review process before they go into the master branch. The user's guide > needs an update for a bunch of new information (live, catalyst editions, > zero-copy arrays) that's important for Catalyst. We're also doing some > preliminary testing with a newly developed ADIOS writer for better IO > performance as well. > > Getting back to the live viz stuff, when you create a Catalyst Python > script and export it using the wizard you'll have the option to enable live > viz (it's the same wizard page as the screenshot output specification). > Then, while your simulation is running use the Catalyst->Connect option to > connect. There are two tests (pv.CatalystLiveSetBreakpoint and > pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live > functionality which now includes the option to set a breakpoint in the > simulation. > > If you get a chance to try it out, let me know what you think. > > Andy > > > > On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: > > Dear Catalyst people > > > > I dragged out an old simulation demo I created some time ago and got it > working with paraview/catalyst from git master branch - my plan was to test > a live visualization of the simulation with the paraview GUI connected to > the simulation. I had thought this capability was now possible, but I have > not been following development closely and it looks like I was mistaken. > > > > Is it possible to visualize the simulation live - rather than just > generate images (which works fine). (I had a quick skim through the user > manual, but didn?t see this feature mentioned). > > > > Thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan.lipsa at kitware.com Thu Oct 16 10:32:15 2014 From: dan.lipsa at kitware.com (Dan Lipsa) Date: Thu, 16 Oct 2014 10:32:15 -0400 Subject: [Paraview] Catalyst question In-Reply-To: <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> Message-ID: Hi John, I had imagined that I?d run a simulation on N ranks, have catalyst bound to > them and be able to do vis on those N ranks. But in fact, when I connect to > a live simulation, I have to ?extract? results from them and then render > them back on the client. > > > > Is this the case or did I miss something? > Just to confirm Andy's answer, you can do the rendering on a separate ParaView server (pvserver), which can be the same as the server you run the simulation on. Catalyst will send extracts to this server which will render them. Only images will be send back to the client. We show that use case at the end of our article. http://www.kitware.com/blog/home/post/722 Dan > > > The parallel image generation appears to work as advertised, but the > images go off to disk and not to the renderwindow. Is there a way on > configuring it so that I can see the actual rendering taking place in the > renderview? I wanted to display the contents of a custom render plugin > using cuda based rendering on many GPUs and be able to interact with it, > but I am obviously missing something in my setup. > > > > thanks > > > > JB > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* 26 August 2014 15:34 > *To:* Biddiscombe, John A. > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Catalyst question > > > > Hi John, > > > This live capability is now available and recently has been cleaned up > quite a bit. There are still a couple more small changes that are waiting a > code review process before they go into the master branch. The user's guide > needs an update for a bunch of new information (live, catalyst editions, > zero-copy arrays) that's important for Catalyst. We're also doing some > preliminary testing with a newly developed ADIOS writer for better IO > performance as well. > > Getting back to the live viz stuff, when you create a Catalyst Python > script and export it using the wizard you'll have the option to enable live > viz (it's the same wizard page as the screenshot output specification). > Then, while your simulation is running use the Catalyst->Connect option to > connect. There are two tests (pv.CatalystLiveSetBreakpoint and > pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live > functionality which now includes the option to set a breakpoint in the > simulation. > > If you get a chance to try it out, let me know what you think. > > Andy > > > > On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: > > Dear Catalyst people > > > > I dragged out an old simulation demo I created some time ago and got it > working with paraview/catalyst from git master branch - my plan was to test > a live visualization of the simulation with the paraview GUI connected to > the simulation. I had thought this capability was now possible, but I have > not been following development closely and it looks like I was mistaken. > > > > Is it possible to visualize the simulation live - rather than just > generate images (which works fine). (I had a quick skim through the user > manual, but didn?t see this feature mentioned). > > > > Thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Thu Oct 16 10:43:22 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Thu, 16 Oct 2014 14:43:22 +0000 Subject: [Paraview] Catalyst question In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509918F587A4@MBX210.d.ethz.ch> Andy, Dan Thank you both for clarifying this. I might give the catalyst->server->client version a go, but it seems like it might be too much trouble ... I expect I?ll just use the solution we developed here at CSCS a couple of years ago where we just connect the simulation to the pvservers and then connect the client to them. That way I won?t need to copy the data between processes again (there is already a copy because the simulation is writing to a shared memory buffer and the pvservers would read from that - not the same as the H5FDdsm stuff we developed, but very similar, and I can simply piggy back our live viz on top of that). We wanted to do a live demo of GPU rendering on 1024 or so nodes at SC14 so it may be that using something I?m already familiar with will save me time as were getting close to Nov ... On that note : It ought to be trivial to whip up a catalyst ?view? which captures the images from the internal renderwindow created by catalyst and have them displayed in the GUI so that the user can see the ?live? viz. Not sure how you?d pass the interactions back to handle mouse etc, but if the client can write to the camera objects via proxies then it should be possible .... might try this myself if I have a moment spare. thanks again JB From: Dan Lipsa [mailto:dan.lipsa at kitware.com] Sent: 16 October 2014 16:32 To: Biddiscombe, John A. Cc: Andy Bauer; paraview at paraview.org Subject: Re: [Paraview] Catalyst question Hi John, I had imagined that I?d run a simulation on N ranks, have catalyst bound to them and be able to do vis on those N ranks. But in fact, when I connect to a live simulation, I have to ?extract? results from them and then render them back on the client. Is this the case or did I miss something? Just to confirm Andy's answer, you can do the rendering on a separate ParaView server (pvserver), which can be the same as the server you run the simulation on. Catalyst will send extracts to this server which will render them. Only images will be send back to the client. We show that use case at the end of our article. http://www.kitware.com/blog/home/post/722 Dan The parallel image generation appears to work as advertised, but the images go off to disk and not to the renderwindow. Is there a way on configuring it so that I can see the actual rendering taking place in the renderview? I wanted to display the contents of a custom render plugin using cuda based rendering on many GPUs and be able to interact with it, but I am obviously missing something in my setup. thanks JB From: Andy Bauer [mailto:andy.bauer at kitware.com] Sent: 26 August 2014 15:34 To: Biddiscombe, John A. Cc: paraview at paraview.org Subject: Re: [Paraview] Catalyst question Hi John, This live capability is now available and recently has been cleaned up quite a bit. There are still a couple more small changes that are waiting a code review process before they go into the master branch. The user's guide needs an update for a bunch of new information (live, catalyst editions, zero-copy arrays) that's important for Catalyst. We're also doing some preliminary testing with a newly developed ADIOS writer for better IO performance as well. Getting back to the live viz stuff, when you create a Catalyst Python script and export it using the wizard you'll have the option to enable live viz (it's the same wizard page as the screenshot output specification). Then, while your simulation is running use the Catalyst->Connect option to connect. There are two tests (pv.CatalystLiveSetBreakpoint and pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live functionality which now includes the option to set a breakpoint in the simulation. If you get a chance to try it out, let me know what you think. Andy On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: Dear Catalyst people I dragged out an old simulation demo I created some time ago and got it working with paraview/catalyst from git master branch - my plan was to test a live visualization of the simulation with the paraview GUI connected to the simulation. I had thought this capability was now possible, but I have not been following development closely and it looks like I was mistaken. Is it possible to visualize the simulation live - rather than just generate images (which works fine). (I had a quick skim through the user manual, but didn?t see this feature mentioned). Thanks JB -- John Biddiscombe, email:biddisco @.at.@ cscs.ch http://www.cscs.ch/ CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Oct 16 10:46:06 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 16 Oct 2014 10:46:06 -0400 Subject: [Paraview] Catalyst question In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> Message-ID: Hi Dan, Thanks for the correction -- I should have read your post closer! Thanks, Andy On Thu, Oct 16, 2014 at 10:32 AM, Dan Lipsa wrote: > Hi John, > > I had imagined that I?d run a simulation on N ranks, have catalyst bound >> to them and be able to do vis on those N ranks. But in fact, when I connect >> to a live simulation, I have to ?extract? results from them and then render >> them back on the client. >> >> >> >> Is this the case or did I miss something? >> > > Just to confirm Andy's answer, you can do the rendering on a separate > ParaView server (pvserver), which can be the same as the server you run the > simulation on. Catalyst will send extracts to this server which will render > them. > Only images will be send back to the client. > > We show that use case at the end of our article. > > http://www.kitware.com/blog/home/post/722 > > Dan > > > > >> >> >> The parallel image generation appears to work as advertised, but the >> images go off to disk and not to the renderwindow. Is there a way on >> configuring it so that I can see the actual rendering taking place in the >> renderview? I wanted to display the contents of a custom render plugin >> using cuda based rendering on many GPUs and be able to interact with it, >> but I am obviously missing something in my setup. >> >> >> >> thanks >> >> >> >> JB >> >> >> >> *From:* Andy Bauer [mailto:andy.bauer at kitware.com] >> *Sent:* 26 August 2014 15:34 >> *To:* Biddiscombe, John A. >> *Cc:* paraview at paraview.org >> *Subject:* Re: [Paraview] Catalyst question >> >> >> >> Hi John, >> >> >> This live capability is now available and recently has been cleaned up >> quite a bit. There are still a couple more small changes that are waiting a >> code review process before they go into the master branch. The user's guide >> needs an update for a bunch of new information (live, catalyst editions, >> zero-copy arrays) that's important for Catalyst. We're also doing some >> preliminary testing with a newly developed ADIOS writer for better IO >> performance as well. >> >> Getting back to the live viz stuff, when you create a Catalyst Python >> script and export it using the wizard you'll have the option to enable live >> viz (it's the same wizard page as the screenshot output specification). >> Then, while your simulation is running use the Catalyst->Connect option to >> connect. There are two tests (pv.CatalystLiveSetBreakpoint and >> pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live >> functionality which now includes the option to set a breakpoint in the >> simulation. >> >> If you get a chance to try it out, let me know what you think. >> >> Andy >> >> >> >> On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. >> wrote: >> >> Dear Catalyst people >> >> >> >> I dragged out an old simulation demo I created some time ago and got it >> working with paraview/catalyst from git master branch - my plan was to test >> a live visualization of the simulation with the paraview GUI connected to >> the simulation. I had thought this capability was now possible, but I have >> not been following development closely and it looks like I was mistaken. >> >> >> >> Is it possible to visualize the simulation live - rather than just >> generate images (which works fine). (I had a quick skim through the user >> manual, but didn?t see this feature mentioned). >> >> >> >> Thanks >> >> >> >> JB >> >> >> >> -- >> >> John Biddiscombe, email:biddisco @.at.@ cscs.ch >> >> http://www.cscs.ch/ >> >> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 >> >> Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.bauer at kitware.com Thu Oct 16 10:48:35 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Thu, 16 Oct 2014 10:48:35 -0400 Subject: [Paraview] Catalyst question In-Reply-To: <50320452A334BD42A5EC72BAD214509918F587A4@MBX210.d.ethz.ch> References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F587A4@MBX210.d.ethz.ch> Message-ID: Hi John, I'll be at SC14 and I'd be interested in seeing your demo. Are the details of when and where ready yet? Regards, Andy On Thu, Oct 16, 2014 at 10:43 AM, Biddiscombe, John A. wrote: > Andy, Dan > > > > Thank you both for clarifying this. I might give the > catalyst->server->client version a go, but it seems like it might be too > much trouble ... > > I expect I?ll just use the solution we developed here at CSCS a couple of > years ago where we just connect the simulation to the pvservers and then > connect the client to them. That way I won?t need to copy the data between > processes again (there is already a copy because the simulation is writing > to a shared memory buffer and the pvservers would read from that - not the > same as the H5FDdsm stuff we developed, but very similar, and I can simply > piggy back our live viz on top of that). > > > > We wanted to do a live demo of GPU rendering on 1024 or so nodes at SC14 > so it may be that using something I?m already familiar with will save me > time as were getting close to Nov ... > > > > On that note : It ought to be trivial to whip up a catalyst ?view? which > captures the images from the internal renderwindow created by catalyst and > have them displayed in the GUI so that the user can see the ?live? viz. Not > sure how you?d pass the interactions back to handle mouse etc, but if the > client can write to the camera objects via proxies then it should be > possible .... might try this myself if I have a moment spare. > > > > thanks again > > > > JB > > > > *From:* Dan Lipsa [mailto:dan.lipsa at kitware.com] > *Sent:* 16 October 2014 16:32 > *To:* Biddiscombe, John A. > *Cc:* Andy Bauer; paraview at paraview.org > > *Subject:* Re: [Paraview] Catalyst question > > > > Hi John, > > > > I had imagined that I?d run a simulation on N ranks, have catalyst bound > to them and be able to do vis on those N ranks. But in fact, when I connect > to a live simulation, I have to ?extract? results from them and then render > them back on the client. > > > > Is this the case or did I miss something? > > > > Just to confirm Andy's answer, you can do the rendering on a separate > ParaView server (pvserver), which can be the same as the server you run the > simulation on. Catalyst will send extracts to this server which will render > them. > > Only images will be send back to the client. > > > > We show that use case at the end of our article. > > > > http://www.kitware.com/blog/home/post/722 > > > > Dan > > > > > > > > > > The parallel image generation appears to work as advertised, but the > images go off to disk and not to the renderwindow. Is there a way on > configuring it so that I can see the actual rendering taking place in the > renderview? I wanted to display the contents of a custom render plugin > using cuda based rendering on many GPUs and be able to interact with it, > but I am obviously missing something in my setup. > > > > thanks > > > > JB > > > > *From:* Andy Bauer [mailto:andy.bauer at kitware.com] > *Sent:* 26 August 2014 15:34 > *To:* Biddiscombe, John A. > *Cc:* paraview at paraview.org > *Subject:* Re: [Paraview] Catalyst question > > > > Hi John, > > > > This live capability is now available and recently has been cleaned up > quite a bit. There are still a couple more small changes that are waiting a > code review process before they go into the master branch. The user's guide > needs an update for a bunch of new information (live, catalyst editions, > zero-copy arrays) that's important for Catalyst. We're also doing some > preliminary testing with a newly developed ADIOS writer for better IO > performance as well. > > Getting back to the live viz stuff, when you create a Catalyst Python > script and export it using the wizard you'll have the option to enable live > viz (it's the same wizard page as the screenshot output specification). > Then, while your simulation is running use the Catalyst->Connect option to > connect. There are two tests (pv.CatalystLiveSetBreakpoint and > pvcs.CatalystLiveSetBreakpoint) that demonstrate the newly implemented live > functionality which now includes the option to set a breakpoint in the > simulation. > > If you get a chance to try it out, let me know what you think. > > Andy > > > > On Tue, Aug 26, 2014 at 3:40 AM, Biddiscombe, John A. > wrote: > > Dear Catalyst people > > > > I dragged out an old simulation demo I created some time ago and got it > working with paraview/catalyst from git master branch - my plan was to test > a live visualization of the simulation with the paraview GUI connected to > the simulation. I had thought this capability was now possible, but I have > not been following development closely and it looks like I was mistaken. > > > > Is it possible to visualize the simulation live - rather than just > generate images (which works fine). (I had a quick skim through the user > manual, but didn?t see this feature mentioned). > > > > Thanks > > > > JB > > > > -- > > John Biddiscombe, email:biddisco @.at.@ cscs.ch > > http://www.cscs.ch/ > > CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07 > > Via Trevano 131, 6900 Lugano, Switzerland | Fax: +41 (91) 610.82.82 > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gda at tacc.utexas.edu Thu Oct 16 11:26:39 2014 From: gda at tacc.utexas.edu (Greg Abram) Date: Thu, 16 Oct 2014 15:26:39 +0000 Subject: [Paraview] OpenGL2 backend in 4.2 Message-ID: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> Hey y'all - Anyone able to get the OpenGL2 backend to build? If I set VTK_RENDERING_BACKEND to OpenGL2, I get: CMake Error at VTK/Rendering/OpenGL/CMakeLists.txt:3 (message): vtkRenderingOpenGL cannot be built with vtkRenderingOpenGL2, please disable one of them. And I can't figure out how to get past it. Greg Gregory D. Abram, Ph.D. Research Engineering/Scientist Associate Texas Advanced Computing Center The University of Texas at Austin (512) 471-8196 gda at tacc.utexas.edu [TACC Website] Connect With TACC -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Oct 16 11:38:41 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Oct 2014 11:38:41 -0400 Subject: [Paraview] OpenGL2 backend in 4.2 In-Reply-To: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> References: <88F95E89-085C-4D9F-B061-8E32BC94E9C3@tacc.utexas.edu> Message-ID: Greg, This isn't ready for testing yet. There are still code changes that need to go into ParaView before folks can start building with OpenGL2 backend support. Utkarsh On Thu, Oct 16, 2014 at 11:26 AM, Greg Abram wrote: > Hey y'all - > > Anyone able to get the OpenGL2 backend to build? If I set > VTK_RENDERING_BACKEND to OpenGL2, I get: > > CMake Error at VTK/Rendering/OpenGL/CMakeLists.txt:3 (message): > vtkRenderingOpenGL cannot be built with vtkRenderingOpenGL2, please > disable > one of them. > > And I can't figure out how to get past it. > > Greg > > Gregory D. Abram, Ph.D. > Research Engineering/Scientist Associate > Texas Advanced Computing Center > The University of Texas at Austin > (512) 471-8196 > gda at tacc.utexas.edu > > [image: TACC Website] > > Connect With TACC > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Thu Oct 16 11:49:09 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Oct 2014 11:49:09 -0400 Subject: [Paraview] Bug? - ExtractedSelection is mapped between Extracted Blocks In-Reply-To: <543FA5FB.9010303@virgin.net> References: <543FA5FB.9010303@virgin.net> Message-ID: Try unchecking the "Purne Output" checkbox on the "Extract Block" filter's Property panel. The problem is that "Prune Output" changes the structure of the multiblock. Hence the selection defined in (3) resolves differently after (5). Utkarsh On Thu, Oct 16, 2014 at 7:03 AM, redkite wrote: > Hi, > > I understand that objects in a vtk pipeline will be updated if something > earlier changes, but I can see no use for this behaviour (and it's quite a > pain to me ;). To replicate: > > 1) Load the can.ex2 example and apply the 'Extract Block' filter. > 2) Navigate to the ExtractBlock/'Block indices' menu and switch on 'Unnamed > block ID 1' so you can see the semi-circular can object. > 3) Click the 'Select Points On' rubber-band selection button and draw a > rectangle of points on the can. > 4) Click the 'Extract Selection' button. > 5) Go back to the ExtractBlock/'Block indices' menu, switch off 'Unnamed > block ID 1' and turn on 'Unnamed block ID 2' > > You will see that the extracted selection is mapped to apparently arbitrary > points in or on the second block (you may need to change opacity to see the > mapped points). Other similar but strange behaviour occurs if you select > across blocks and switch to view just one or a few of them. > > I note that if I obtain the pqSelectionManager I can clear the selection, > but as the docs say, the selection still exists somewhere in the vtk code. > Is there a better way to control this action? > > (Tested with ParaView 4.1 and Windows and Ubuntu, and 4.2 on Ubuntu.) > > Thanks, > Richard > > ps > I tried searching through the archives for block/selection issues and I'm a > bit surprised not to find anything like this before.... though it may be > related to issue raised by Robert Ainsworth ?? [so I've just cc'd this to > him] > (http://paraview.markmail.org/message/z4eq4hj2zerrwste?q=selection+on+blocks&page=3) > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Thu Oct 16 11:59:30 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 16 Oct 2014 11:59:30 -0400 Subject: [Paraview] using calculator filter on a table? In-Reply-To: <8D5C1B82EA40014E8B222E92B907632502135877436A@MAILBOX.LASP.colorado.edu> References: <8D5C1B82EA40014E8B222E92B9076325021358774366@MAILBOX.LASP.colorado.edu> <8D5C1B82EA40014E8B222E92B907632502135877436A@MAILBOX.LASP.colorado.edu> Message-ID: I think I've tracked down the problem...I'll have a fix soon. Utkarsh On Thu, Sep 25, 2014 at 6:18 PM, Joshua Murphy wrote: > Hi Utkarsh, > > I have tried this once again in v4.2.0, and I am getting the same segfault. > > any thoughts? my input is a multi-block table... > > -Josh > > ________________________________________ > From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] > Sent: Thursday, September 25, 2014 11:23 AM > To: Joshua Murphy > Cc: paraview at paraview.org > Subject: Re: [Paraview] using calculator filter on a table? > > For now, with 4.2 RC1, stick to using "Programmable Filter" with > "Script" as follows: > > expr = inputs[0].RowData["RTData"] * 2.0 > output.RowData.append(expr, "result") > > If you can add a bug to the bug tracker for this, that'd be great too. > > Thanks > Utkarsh > > On Thu, Sep 25, 2014 at 12:45 PM, Joshua Murphy > wrote: >> Hello all, >> >> Is there a way to use the Calculator filter on a table? >> >> My reader loads a bunch of auxiliary files that loads time-series information for a specific point (at a higher temporal resolution than the 3D model output). I need to be able to convert the units in the time series information with some simple calculations so that I can match the units of the remainder of my work. >> >> Is there a way to use the calculator filter to do this? It is greyed out when I have the table selected... Are there some other steps I need to do to make it work? >> >> Thanks, >> Josh >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Thu Oct 16 13:53:37 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 16 Oct 2014 10:53:37 -0700 Subject: [Paraview] BOX -> volume? In-Reply-To: <543F265A.5000505@xs4all.nl> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543F265A.5000505@xs4all.nl> Message-ID: <54400621.2040900@gmail.com> Hi Bertwim, The problem you're experiencing is not an issue of missing extensions, but rather a bug in ATI's driver. Projected tetrahedra is disabled when an ATI device is detected to avoid that bug(ParaView will hang). However it's not a big deal. because you can use the "Bunyk raycast" algrothim instead. After your data is on screen scroll to the bottom of the properties panel and look for the field "Select mapper", set that to "Bunyk ray cast", then change the representation to "volume". Burlen On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: > I am still busy with finding out which etensions are needed, and how I > can enable them. > THis opebnGL-world is a bit alien to me, so it will take some time. > > Regards, > Bertwim > > On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: >> Looks like certain extensions are still not quite working on yours >> system even with the proprietary driver. I will see if I can run your >> code on my laptop but that would be for tomorrow. >> >> ** Assuming that this is not data dependent issue (which it should not). >> >> I think its probably this line causing the issue: >> >> bool driverSupport >> >> #if defined(__APPLE__) >> >> = true; >> >> #else >> >> = !(extensions->DriverIsATI() >> >> && (extensions->GetDriverGLVersionMajor() >= 3)) >> >> || extensions->GetIgnoreDriverBugs("ATI texturing bug"); >> >> #endif >> >> >> >> On line number 181: can you change this code to : >> >> this->HasHardwareSupport=renwin!=NULL&&this->IsSupported(renwin); >> to >> this->HasHardwareSupport=1; >> >> - Aashish >> >> >> >> On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest > > wrote: >> >> Progress indeed. But I don't understand what you are saying about >> the transfer function. >> >> I' starting to wonder if I have two issues occurring simultaneously. >> In a new thread I just posted I described my problem in getting >> the colours in place. >> I need to write to a vtk file first and load it back. I just >> found that when I just did that >> and then switched fo volume rendering, an error was there about >> the absence >> of an opengl extension: >> >> ERROR: In >> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, >> line 185 >> vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required >> extensions are not supported. >> >> This is complete unknown terrain for me. >> >> Regards, >> Bertwim >> >> >> >> On 10/14/2014 09:58 PM, Burlen Loring wrote: >>> progress! it sounds like volume rendering is working on the >>> wavelet dataset. >>> >>> You do need the scalars for volume rendering, so make sure you >>> have those when you try. You need to select the scalars in the >>> drop down also, I usually do this before changing to the volume >>> representation. You also may need to edit the transfer function. >>> For testing you could make the opacity over the entire scalar >>> range in which case you should see a solid cube. >>> >>> If you've done all that and don't see anything it's likely that >>> the dataset is messed up. Add a dataset->Print(cerr) statement >>> to the end of your request data, look in the information panel >>> and verify correct number of points and scalar ranges. >>> >>> If all else fails post the dataset to the list. After creating >>> your cube go to the file menu and "save data". >>> >>> >>> On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >>>> Hi Burlen, >>>> >>>> I have upgraded to the AMD drivers. Thanks for the hint. It has >>>> improved the situation a bit. >>>> >>>> Furthermore, I created the wavelet source. When selecting >>>> "volume" representation, I do see a three 3 picture, in all 5 >>>> volume rendering mode (smart, raycast and texture mapping, ray >>>> cast only, texture mapping only, GPU based). The picture a >>>> rather fuzzy, but then I don't know what I'm supposed to see >>>> here. The good news is that the openGL errors I had before when >>>> displaying a wavelet, now have gone. >>>> >>>> The situation with my own cube, though, has unchanged. >>>> unfortunately. >>>> The cube disappears in "volume" representation node, also when >>>> I re-inserted scalar values for each of the 8 vertices. >>>> >>>> Regards, >>>> Bertwim >>>> >>>> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>>>> Hi Bertwim, >>>>> >>>>> In recent releases of ParaView I have experienced >>>>> issues/flakeyness with volume rendering. Something you should >>>>> try: Create the wavelet source, then in the properties panel >>>>> find "volume rendering mode" and set it to "ray cast only". >>>>> This has worked for me on a number of systems. may or may not >>>>> work, but worth a try. >>>>> >>>>> The output you pasted below shows that although you've got a >>>>> sweet ATI GPU you're not taking advantage of it! You're using >>>>> the Intel integrated GPU with Mesa drivers. If I were you I >>>>> would install proprietary the AMD drivers >>>>> . This should give you >>>>> nice performance boost and may even solve the OpenGL errors >>>>> you reported, which these days are as often (or more) a result >>>>> of bugs in the Mesa drivers than in VTK. >>>>> >>>>> Burlen >>>>> >>>>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>>>> >>>>>> >>>>>> OS: OpenSuSe 13.1 >>>>>> >>>>>> # lspci | grep -i vga >>>>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen >>>>>> Core Processor Integrated Graphics Controller (rev 06) >>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, >>>>>> Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>>>> >>>>>> # glxinfo >>>>>> name of display: :0 >>>>>> display: :0 screen: 0 >>>>>> direct rendering: Yes >>>>>> server glx vendor string: SGI >>>>>> server glx version string: 1.4 >>>>>> server glx extensions: >>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>>>> GLX_EXT_visual_info, >>>>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>>>> GLX_MESA_copy_sub_buffer, >>>>>> GLX_OML_swap_method, GLX_SGIS_multisample, >>>>>> GLX_SGIX_fbconfig, >>>>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>>>> GLX_SGI_swap_control >>>>>> client glx vendor string: Mesa Project and SGI >>>>>> client glx version string: 1.4 >>>>>> client glx extensions: >>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>>>> GLX_ARB_multisample, >>>>>> GLX_EXT_create_context_es2_profile, >>>>>> GLX_EXT_fbconfig_packed_float, >>>>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>> GLX_EXT_visual_rating, >>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>> GLX_SGIS_multisample, >>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>> GLX_SGIX_visual_select_group, >>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>> GLX_SGI_video_sync >>>>>> GLX version: 1.4 >>>>>> GLX extensions: >>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>> GLX_EXT_visual_rating, >>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>> GLX_SGIS_multisample, >>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>> GLX_SGIX_visual_select_group, >>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>> GLX_SGI_video_sync >>>>>> OpenGL vendor string: Intel Open Source Technology Center >>>>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 >>>>>> OpenGL core profile shading language version string: 1.40 >>>>>> OpenGL core profile context flags: (none) >>>>>> OpenGL core profile extensions: >>>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>>>> GL_ARB_debug_output, >>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>> GL_ARB_draw_buffers, >>>>>> GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, >>>>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>>>> GL_ARB_provoking_vertex, >>>>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>>>> GL_ARB_seamless_cube_map, >>>>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>>>> GL_ARB_texture_buffer_object, >>>>>> GL_ARB_texture_buffer_object_rgb32, >>>>>> GL_ARB_texture_compression_rgtc, >>>>>> GL_ARB_texture_cube_map_array, >>>>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>> GL_ARB_uniform_buffer_object, >>>>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, >>>>>> GL_EXT_abgr, >>>>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>>>> GL_EXT_framebuffer_multisample, >>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>>>> GL_EXT_packed_float, >>>>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>>>> GL_EXT_texture_array, >>>>>> GL_EXT_texture_compression_dxt1, >>>>>> GL_EXT_texture_compression_rgtc, >>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>> GL_EXT_transform_feedback, >>>>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>>>> GL_MESA_ycbcr_texture, >>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>> GL_NV_packed_depth_stencil, >>>>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>>>> >>>>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>>>> OpenGL shading language version string: 1.30 >>>>>> OpenGL context flags: (none) >>>>>> OpenGL extensions: >>>>>> GL_3DFX_texture_compression_FXT1, GL_AMD_draw_buffers_blend, >>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>>>> GL_ARB_debug_output, >>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>> GL_ARB_depth_texture, >>>>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>>>> GL_ARB_explicit_attrib_location, >>>>>> GL_ARB_fragment_coord_conventions, >>>>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>>>> GL_ARB_multisample, >>>>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>>>> GL_ARB_occlusion_query2, >>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>>>> GL_ARB_point_sprite, >>>>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>>>> GL_ARB_sampler_objects, >>>>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>>>> GL_ARB_shading_language_100, >>>>>> GL_ARB_shading_language_420pack, >>>>>> GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, >>>>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>> GL_ARB_transpose_matrix, >>>>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, >>>>>> GL_EXT_abgr, >>>>>> GL_EXT_bgra, GL_EXT_blend_color, >>>>>> GL_EXT_blend_equation_separate, >>>>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>>>> GL_EXT_blend_subtract, >>>>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>>>> GL_EXT_draw_buffers2, >>>>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>>>> GL_EXT_fog_coord, >>>>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>> GL_EXT_framebuffer_object, >>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>>>> GL_EXT_pixel_buffer_object, >>>>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>>>> GL_EXT_provoking_vertex, >>>>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>>>> GL_EXT_separate_shader_objects, >>>>>> GL_EXT_separate_specular_color, >>>>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, >>>>>> GL_EXT_stencil_wrap, >>>>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>>>> GL_EXT_texture_rectangle, >>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>> GL_EXT_transform_feedback, >>>>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>>>> GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, >>>>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>>>> GL_MESA_texture_signed_rgba, >>>>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, >>>>>> GL_NV_blend_square, >>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>> GL_NV_light_max_exponent, >>>>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>>>> GL_NV_texture_rectangle, GL_OES_EGL_image, >>>>>> GL_OES_read_format, >>>>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, >>>>>> GL_SGIS_texture_border_clamp, >>>>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>>>> GL_SUN_multi_draw_arrays >>>>>> >>>>>> 20 GLX Visuals >>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>> accumbuffer ms cav >>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>> g b a ns b eat >>>>>> ---------------------------------------------------------------------------- >>>>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>>> 16 16 0 0 Slow >>>>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>>> 16 16 0 0 Slow >>>>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> >>>>>> 44 GLXFBConfigs: >>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>> accumbuffer ms cav >>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>> g b a ns b eat >>>>>> ---------------------------------------------------------------------------- >>>>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>>> 16 0 0 0 Slow >>>>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>>> 16 16 0 0 Slow >>>>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 >>>>>> 16 0 0 0 Slow >>>>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 0 0 None >>>>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 >>>>>> 16 16 0 0 Slow >>>>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 >>>>>> 0 0 8 1 None >>>>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 4 1 None >>>>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 >>>>>> 0 0 8 1 None >>>>>> >>>>>> >>>>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>>>> What graphics card / graphics driver version / OS this >>>>>>> system has? >>>>>>> >>>>>>> - Aashish >>>>>>> >>>>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>>>>> > wrote: >>>>>>> >>>>>>> Hi Aashish, >>>>>>> >>>>>>> This is what I do: >>>>>>> 1. start paraview >>>>>>> 2. Sources -> Wavelet -> Apply. >>>>>>> A cube is displayed (Outline representation). >>>>>>> 3. Select 'Volume" representation" >>>>>>> >>>>>>> cube disappears. Then: >>>>>>> ===================== >>>>>>> Generic Warning: In >>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>> line 487 >>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>> 0 : (1282) Invalid operation >>>>>>> >>>>>>> >>>>>>> >>>>>>> Generic Warning: In >>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>> line 487 >>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>> 0 : (1282) Invalid operation >>>>>>> >>>>>>> >>>>>>> >>>>>>> Generic Warning: In >>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>> line 487 >>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>> 0 : (1282) Invalid operation >>>>>>> ========================= >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>>>> So when you created a wavelet source and change the >>>>>>>> representation to volume you got the errors? Can you >>>>>>>> post those errors? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Aashish, >>>>>>>> >>>>>>>> Thanks for the suggestion. >>>>>>>> >>>>>>>> However, doing this gives me all kinds of opengl >>>>>>>> errors (invalid instruction). >>>>>>>> >>>>>>>> Besides that, the wavelet gives me a cube indeed, >>>>>>>> but I need to understand when >>>>>>>> I can have a volume rendering. I created new >>>>>>>> Source's (e.g. tri-prism, a wedge, >>>>>>>> a box with boundaries of finite thickness etc.). >>>>>>>> But I cannot get volume rendering >>>>>>>> to work, grrrrrr. (See other thread) >>>>>>>> >>>>>>>> Kind Regards, >>>>>>>> Bertwim >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>>>> You can create a wavelet source and then display >>>>>>>>> it as a volume. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>> Can perhaps somebody point me how to address >>>>>>>>> the following. >>>>>>>>> >>>>>>>>> When I create a new source (say: a box) I get >>>>>>>>> an a box that >>>>>>>>> can be displayed via its surfaces, its >>>>>>>>> constituing points, or wireframe >>>>>>>>> representation. >>>>>>>>> But I need a volume rendering (so that I can >>>>>>>>> add e.g. a clipping plane) >>>>>>>>> How do I get that? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Bertwim >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Powered by www.kitware.com >>>>>>>>> >>>>>>>>> >>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>> >>>>>>>>> Please keep messages on-topic and check the >>>>>>>>> ParaView Wiki at: >>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>> >>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> /| Aashish Chaudhary >>>>>>>>> | Technical Leader >>>>>>>>> | Kitware Inc. >>>>>>>>> / >>>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /| Aashish Chaudhary >>>>>>>> | Technical Leader >>>>>>>> | Kitware Inc. >>>>>>>> / >>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> /| Aashish Chaudhary >>>>>>> | Technical Leader >>>>>>> | Kitware Inc. >>>>>>> / >>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Powered bywww.kitware.com >>>>>> >>>>>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>>>>> >>>>>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>>>>> >>>>>> Follow this link to subscribe/unsubscribe: >>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered bywww.kitware.com >>>> >>>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> >> >> >> -- >> /| Aashish Chaudhary >> | Technical Leader >> | Kitware Inc. >> / >> /| http://www.kitware.com/company/team/chaudhary.html/ > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Thu Oct 16 18:32:14 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 17 Oct 2014 00:32:14 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: <54400621.2040900@gmail.com> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543F265A.5000505@xs4all.nl> <54400621.2040900@gmail.com> Message-ID: <5440476E.1030905@xs4all.nl> Got it! Impressive, your knowledge on these matters. Regards, Bertwim On 10/16/2014 07:53 PM, Burlen Loring wrote: > Hi Bertwim, > > The problem you're experiencing is not an issue of missing extensions, > but rather a bug in ATI's driver. Projected tetrahedra is disabled > when an ATI device is detected to avoid that bug(ParaView will hang). > However it's not a big deal. because you can use the "Bunyk raycast" > algrothim instead. After your data is on screen scroll to the bottom > of the properties panel and look for the field "Select mapper", set > that to "Bunyk ray cast", then change the representation to "volume". > > Burlen > > > On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: >> I am still busy with finding out which etensions are needed, and how >> I can enable them. >> THis opebnGL-world is a bit alien to me, so it will take some time. >> >> Regards, >> Bertwim >> >> On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: >>> Looks like certain extensions are still not quite working on yours >>> system even with the proprietary driver. I will see if I can run >>> your code on my laptop but that would be for tomorrow. >>> >>> ** Assuming that this is not data dependent issue (which it should >>> not). >>> >>> I think its probably this line causing the issue: >>> >>> bool driverSupport >>> >>> #if defined(__APPLE__) >>> >>> = true; >>> >>> #else >>> >>> = !(extensions->DriverIsATI() >>> >>> && (extensions->GetDriverGLVersionMajor() >= 3)) >>> >>> || extensions->GetIgnoreDriverBugs("ATI texturing bug"); >>> >>> #endif >>> >>> >>> >>> On line number 181: can you change this code to : >>> >>> this->HasHardwareSupport=renwin!=NULL&&this->IsSupported(renwin); >>> to >>> this->HasHardwareSupport=1; >>> >>> - Aashish >>> >>> >>> >>> On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest >> > wrote: >>> >>> Progress indeed. But I don't understand what you are saying >>> about the transfer function. >>> >>> I' starting to wonder if I have two issues occurring simultaneously. >>> In a new thread I just posted I described my problem in getting >>> the colours in place. >>> I need to write to a vtk file first and load it back. I just >>> found that when I just did that >>> and then switched fo volume rendering, an error was there about >>> the absence >>> of an opengl extension: >>> >>> ERROR: In >>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, >>> line 185 >>> vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required >>> extensions are not supported. >>> >>> This is complete unknown terrain for me. >>> >>> Regards, >>> Bertwim >>> >>> >>> >>> On 10/14/2014 09:58 PM, Burlen Loring wrote: >>>> progress! it sounds like volume rendering is working on the >>>> wavelet dataset. >>>> >>>> You do need the scalars for volume rendering, so make sure you >>>> have those when you try. You need to select the scalars in the >>>> drop down also, I usually do this before changing to the volume >>>> representation. You also may need to edit the transfer >>>> function. For testing you could make the opacity over the >>>> entire scalar range in which case you should see a solid cube. >>>> >>>> If you've done all that and don't see anything it's likely that >>>> the dataset is messed up. Add a dataset->Print(cerr) statement >>>> to the end of your request data, look in the information panel >>>> and verify correct number of points and scalar ranges. >>>> >>>> If all else fails post the dataset to the list. After creating >>>> your cube go to the file menu and "save data". >>>> >>>> >>>> On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >>>>> Hi Burlen, >>>>> >>>>> I have upgraded to the AMD drivers. Thanks for the hint. It >>>>> has improved the situation a bit. >>>>> >>>>> Furthermore, I created the wavelet source. When selecting >>>>> "volume" representation, I do see a three 3 picture, in all 5 >>>>> volume rendering mode (smart, raycast and texture mapping, ray >>>>> cast only, texture mapping only, GPU based). The picture a >>>>> rather fuzzy, but then I don't know what I'm supposed to see >>>>> here. The good news is that the openGL errors I had before >>>>> when displaying a wavelet, now have gone. >>>>> >>>>> The situation with my own cube, though, has unchanged. >>>>> unfortunately. >>>>> The cube disappears in "volume" representation node, also when >>>>> I re-inserted scalar values for each of the 8 vertices. >>>>> >>>>> Regards, >>>>> Bertwim >>>>> >>>>> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>>>>> Hi Bertwim, >>>>>> >>>>>> In recent releases of ParaView I have experienced >>>>>> issues/flakeyness with volume rendering. Something you should >>>>>> try: Create the wavelet source, then in the properties panel >>>>>> find "volume rendering mode" and set it to "ray cast only". >>>>>> This has worked for me on a number of systems. may or may not >>>>>> work, but worth a try. >>>>>> >>>>>> The output you pasted below shows that although you've got a >>>>>> sweet ATI GPU you're not taking advantage of it! You're using >>>>>> the Intel integrated GPU with Mesa drivers. If I were you I >>>>>> would install proprietary the AMD drivers >>>>>> . This should give you >>>>>> nice performance boost and may even solve the OpenGL errors >>>>>> you reported, which these days are as often (or more) a >>>>>> result of bugs in the Mesa drivers than in VTK. >>>>>> >>>>>> Burlen >>>>>> >>>>>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>>>>> >>>>>>> >>>>>>> OS: OpenSuSe 13.1 >>>>>>> >>>>>>> # lspci | grep -i vga >>>>>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen >>>>>>> Core Processor Integrated Graphics Controller (rev 06) >>>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, >>>>>>> Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>>>>> >>>>>>> # glxinfo >>>>>>> name of display: :0 >>>>>>> display: :0 screen: 0 >>>>>>> direct rendering: Yes >>>>>>> server glx vendor string: SGI >>>>>>> server glx version string: 1.4 >>>>>>> server glx extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>>>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>>>>> GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>>>>> GLX_MESA_copy_sub_buffer, >>>>>>> GLX_OML_swap_method, GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, >>>>>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_swap_control >>>>>>> client glx vendor string: Mesa Project and SGI >>>>>>> client glx version string: 1.4 >>>>>>> client glx extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>>>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>>>>> GLX_ARB_multisample, >>>>>>> GLX_EXT_create_context_es2_profile, >>>>>>> GLX_EXT_fbconfig_packed_float, >>>>>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, >>>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>>> GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>>> GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>>> GLX_SGI_video_sync >>>>>>> GLX version: 1.4 >>>>>>> GLX extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>>>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, >>>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>>> GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>>> GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>>> GLX_SGI_video_sync >>>>>>> OpenGL vendor string: Intel Open Source Technology Center >>>>>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>>>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa >>>>>>> 9.2.3 >>>>>>> OpenGL core profile shading language version string: 1.40 >>>>>>> OpenGL core profile context flags: (none) >>>>>>> OpenGL core profile extensions: >>>>>>> GL_3DFX_texture_compression_FXT1, >>>>>>> GL_AMD_draw_buffers_blend, >>>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>>>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>>>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>>>>> GL_ARB_debug_output, >>>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>>> GL_ARB_draw_buffers, >>>>>>> GL_ARB_draw_buffers_blend, >>>>>>> GL_ARB_draw_elements_base_vertex, >>>>>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>>>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>>>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>>>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>>>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>>>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>>>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>>>>> GL_ARB_provoking_vertex, >>>>>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>>>>> GL_ARB_seamless_cube_map, >>>>>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>>>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>>>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>>>>> GL_ARB_texture_buffer_object, >>>>>>> GL_ARB_texture_buffer_object_rgb32, >>>>>>> GL_ARB_texture_compression_rgtc, >>>>>>> GL_ARB_texture_cube_map_array, >>>>>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>>> GL_ARB_uniform_buffer_object, >>>>>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>>>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>>>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, >>>>>>> GL_EXT_abgr, >>>>>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>>>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>>>>> GL_EXT_framebuffer_multisample, >>>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>>>>> GL_EXT_packed_float, >>>>>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>>>>> GL_EXT_texture_array, >>>>>>> GL_EXT_texture_compression_dxt1, >>>>>>> GL_EXT_texture_compression_rgtc, >>>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>>> GL_EXT_transform_feedback, >>>>>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>>>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>>>>> GL_MESA_ycbcr_texture, >>>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>>> GL_NV_packed_depth_stencil, >>>>>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>>>>> >>>>>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>>>>> OpenGL shading language version string: 1.30 >>>>>>> OpenGL context flags: (none) >>>>>>> OpenGL extensions: >>>>>>> GL_3DFX_texture_compression_FXT1, >>>>>>> GL_AMD_draw_buffers_blend, >>>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>>>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>>>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>>>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>>>>> GL_ARB_debug_output, >>>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>>> GL_ARB_depth_texture, >>>>>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>>>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>>>>> GL_ARB_explicit_attrib_location, >>>>>>> GL_ARB_fragment_coord_conventions, >>>>>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>>>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>>>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>>>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>>>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>>>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>>>>> GL_ARB_multisample, >>>>>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>>>>> GL_ARB_occlusion_query2, >>>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>>>>> GL_ARB_point_sprite, >>>>>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>>>>> GL_ARB_sampler_objects, >>>>>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>>>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>>>>> GL_ARB_shading_language_100, >>>>>>> GL_ARB_shading_language_420pack, >>>>>>> GL_ARB_shading_language_packing, GL_ARB_shadow, >>>>>>> GL_ARB_sync, >>>>>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>>>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>>>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>>>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>>>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>>>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>>> GL_ARB_transpose_matrix, >>>>>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>>>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>>>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>>>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>>>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>>>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>>>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, >>>>>>> GL_EXT_abgr, >>>>>>> GL_EXT_bgra, GL_EXT_blend_color, >>>>>>> GL_EXT_blend_equation_separate, >>>>>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>>>>> GL_EXT_blend_subtract, >>>>>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>>>>> GL_EXT_draw_buffers2, >>>>>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>>>>> GL_EXT_fog_coord, >>>>>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>>> GL_EXT_framebuffer_object, >>>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>>>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>>>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>>>>> GL_EXT_pixel_buffer_object, >>>>>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>>>>> GL_EXT_provoking_vertex, >>>>>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>>>>> GL_EXT_separate_shader_objects, >>>>>>> GL_EXT_separate_specular_color, >>>>>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, >>>>>>> GL_EXT_stencil_wrap, >>>>>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>>>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>>>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>>>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>>>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>>>>> GL_EXT_texture_rectangle, >>>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>>> GL_EXT_transform_feedback, >>>>>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>>>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>>>>> GL_IBM_texture_mirrored_repeat, >>>>>>> GL_INGR_blend_func_separate, >>>>>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>>>>> GL_MESA_texture_signed_rgba, >>>>>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, >>>>>>> GL_NV_blend_square, >>>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>>> GL_NV_light_max_exponent, >>>>>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>>>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>>>>> GL_NV_texture_rectangle, GL_OES_EGL_image, >>>>>>> GL_OES_read_format, >>>>>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, >>>>>>> GL_SGIS_texture_border_clamp, >>>>>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>>>>> GL_SUN_multi_draw_arrays >>>>>>> >>>>>>> 20 GLX Visuals >>>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>>> accumbuffer ms cav >>>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>>> g b a ns b eat >>>>>>> ---------------------------------------------------------------------------- >>>>>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> >>>>>>> 44 GLXFBConfigs: >>>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>>> accumbuffer ms cav >>>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>>> g b a ns b eat >>>>>>> ---------------------------------------------------------------------------- >>>>>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 >>>>>>> 16 16 0 0 0 Slow >>>>>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 >>>>>>> 16 16 0 0 0 Slow >>>>>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> >>>>>>> >>>>>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>>>>> What graphics card / graphics driver version / OS this >>>>>>>> system has? >>>>>>>> >>>>>>>> - Aashish >>>>>>>> >>>>>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Hi Aashish, >>>>>>>> >>>>>>>> This is what I do: >>>>>>>> 1. start paraview >>>>>>>> 2. Sources -> Wavelet -> Apply. >>>>>>>> A cube is displayed (Outline representation). >>>>>>>> 3. Select 'Volume" representation" >>>>>>>> >>>>>>>> cube disappears. Then: >>>>>>>> ===================== >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> ========================= >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>>>>> So when you created a wavelet source and change the >>>>>>>>> representation to volume you got the errors? Can you >>>>>>>>> post those errors? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>> Aashish, >>>>>>>>> >>>>>>>>> Thanks for the suggestion. >>>>>>>>> >>>>>>>>> However, doing this gives me all kinds of opengl >>>>>>>>> errors (invalid instruction). >>>>>>>>> >>>>>>>>> Besides that, the wavelet gives me a cube indeed, >>>>>>>>> but I need to understand when >>>>>>>>> I can have a volume rendering. I created new >>>>>>>>> Source's (e.g. tri-prism, a wedge, >>>>>>>>> a box with boundaries of finite thickness etc.). >>>>>>>>> But I cannot get volume rendering >>>>>>>>> to work, grrrrrr. (See other thread) >>>>>>>>> >>>>>>>>> Kind Regards, >>>>>>>>> Bertwim >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>>>>> You can create a wavelet source and then display >>>>>>>>>> it as a volume. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>> Can perhaps somebody point me how to address >>>>>>>>>> the following. >>>>>>>>>> >>>>>>>>>> When I create a new source (say: a box) I get >>>>>>>>>> an a box that >>>>>>>>>> can be displayed via its surfaces, its >>>>>>>>>> constituing points, or wireframe >>>>>>>>>> representation. >>>>>>>>>> But I need a volume rendering (so that I can >>>>>>>>>> add e.g. a clipping plane) >>>>>>>>>> How do I get that? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Bertwim >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the >>>>>>>>>> ParaView Wiki at: >>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> /| Aashish Chaudhary >>>>>>>>>> | Technical Leader >>>>>>>>>> | Kitware Inc. >>>>>>>>>> / >>>>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> /| Aashish Chaudhary >>>>>>>>> | Technical Leader >>>>>>>>> | Kitware Inc. >>>>>>>>> / >>>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /| Aashish Chaudhary >>>>>>>> | Technical Leader >>>>>>>> | Kitware Inc. >>>>>>>> / >>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Thu Oct 16 18:33:37 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Fri, 17 Oct 2014 00:33:37 +0200 Subject: [Paraview] BOX -> volume? In-Reply-To: <54400621.2040900@gmail.com> References: <54383746.6010105@xs4all.nl> <543C0CD9.3080207@xs4all.nl> <543C0EBD.3050304@xs4all.nl> <543C1D9F.5070803@xs4all.nl> <543D4A20.5080507@gmail.com> <543D5FF5.3000600@xs4all.nl> <543D8073.60305@lbl.gov> <543D8D4B.30204@xs4all.nl> <543F265A.5000505@xs4all.nl> <54400621.2040900@gmail.com> Message-ID: <544047C1.2010003@xs4all.nl> Got it! Impressive, your knowledge on these matters ... Thanks & Regards, Bertwim On 10/16/2014 07:53 PM, Burlen Loring wrote: > Hi Bertwim, > > The problem you're experiencing is not an issue of missing extensions, > but rather a bug in ATI's driver. Projected tetrahedra is disabled > when an ATI device is detected to avoid that bug(ParaView will hang). > However it's not a big deal. because you can use the "Bunyk raycast" > algrothim instead. After your data is on screen scroll to the bottom > of the properties panel and look for the field "Select mapper", set > that to "Bunyk ray cast", then change the representation to "volume". > > Burlen > > > On 10/15/2014 06:58 PM, B.W.H. van Beest wrote: >> I am still busy with finding out which etensions are needed, and how >> I can enable them. >> THis opebnGL-world is a bit alien to me, so it will take some time. >> >> Regards, >> Bertwim >> >> On 10/14/2014 11:07 PM, Aashish Chaudhary wrote: >>> Looks like certain extensions are still not quite working on yours >>> system even with the proprietary driver. I will see if I can run >>> your code on my laptop but that would be for tomorrow. >>> >>> ** Assuming that this is not data dependent issue (which it should >>> not). >>> >>> I think its probably this line causing the issue: >>> >>> bool driverSupport >>> >>> #if defined(__APPLE__) >>> >>> = true; >>> >>> #else >>> >>> = !(extensions->DriverIsATI() >>> >>> && (extensions->GetDriverGLVersionMajor() >= 3)) >>> >>> || extensions->GetIgnoreDriverBugs("ATI texturing bug"); >>> >>> #endif >>> >>> >>> >>> On line number 181: can you change this code to : >>> >>> this->HasHardwareSupport=renwin!=NULL&&this->IsSupported(renwin); >>> to >>> this->HasHardwareSupport=1; >>> >>> - Aashish >>> >>> >>> >>> On Tue, Oct 14, 2014 at 4:53 PM, B.W.H. van Beest >> > wrote: >>> >>> Progress indeed. But I don't understand what you are saying >>> about the transfer function. >>> >>> I' starting to wonder if I have two issues occurring simultaneously. >>> In a new thread I just posted I described my problem in getting >>> the colours in place. >>> I need to write to a vtk file first and load it back. I just >>> found that when I just did that >>> and then switched fo volume rendering, an error was there about >>> the absence >>> of an opengl extension: >>> >>> ERROR: In >>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx, >>> line 185 >>> vtkOpenGLProjectedTetrahedraMapper (0x58ae490): The required >>> extensions are not supported. >>> >>> This is complete unknown terrain for me. >>> >>> Regards, >>> Bertwim >>> >>> >>> >>> On 10/14/2014 09:58 PM, Burlen Loring wrote: >>>> progress! it sounds like volume rendering is working on the >>>> wavelet dataset. >>>> >>>> You do need the scalars for volume rendering, so make sure you >>>> have those when you try. You need to select the scalars in the >>>> drop down also, I usually do this before changing to the volume >>>> representation. You also may need to edit the transfer >>>> function. For testing you could make the opacity over the >>>> entire scalar range in which case you should see a solid cube. >>>> >>>> If you've done all that and don't see anything it's likely that >>>> the dataset is messed up. Add a dataset->Print(cerr) statement >>>> to the end of your request data, look in the information panel >>>> and verify correct number of points and scalar ranges. >>>> >>>> If all else fails post the dataset to the list. After creating >>>> your cube go to the file menu and "save data". >>>> >>>> >>>> On 10/14/2014 10:40 AM, B.W.H. van Beest wrote: >>>>> Hi Burlen, >>>>> >>>>> I have upgraded to the AMD drivers. Thanks for the hint. It >>>>> has improved the situation a bit. >>>>> >>>>> Furthermore, I created the wavelet source. When selecting >>>>> "volume" representation, I do see a three 3 picture, in all 5 >>>>> volume rendering mode (smart, raycast and texture mapping, ray >>>>> cast only, texture mapping only, GPU based). The picture a >>>>> rather fuzzy, but then I don't know what I'm supposed to see >>>>> here. The good news is that the openGL errors I had before >>>>> when displaying a wavelet, now have gone. >>>>> >>>>> The situation with my own cube, though, has unchanged. >>>>> unfortunately. >>>>> The cube disappears in "volume" representation node, also when >>>>> I re-inserted scalar values for each of the 8 vertices. >>>>> >>>>> Regards, >>>>> Bertwim >>>>> >>>>> On 10/14/2014 06:06 PM, Burlen Loring wrote: >>>>>> Hi Bertwim, >>>>>> >>>>>> In recent releases of ParaView I have experienced >>>>>> issues/flakeyness with volume rendering. Something you should >>>>>> try: Create the wavelet source, then in the properties panel >>>>>> find "volume rendering mode" and set it to "ray cast only". >>>>>> This has worked for me on a number of systems. may or may not >>>>>> work, but worth a try. >>>>>> >>>>>> The output you pasted below shows that although you've got a >>>>>> sweet ATI GPU you're not taking advantage of it! You're using >>>>>> the Intel integrated GPU with Mesa drivers. If I were you I >>>>>> would install proprietary the AMD drivers >>>>>> . This should give you >>>>>> nice performance boost and may even solve the OpenGL errors >>>>>> you reported, which these days are as often (or more) a >>>>>> result of bugs in the Mesa drivers than in VTK. >>>>>> >>>>>> Burlen >>>>>> >>>>>> On 10/13/2014 11:44 AM, B.W.H. van Beest wrote: >>>>>>> >>>>>>> >>>>>>> OS: OpenSuSe 13.1 >>>>>>> >>>>>>> # lspci | grep -i vga >>>>>>> 00:02.0 VGA compatible controller: Intel Corporation 4th Gen >>>>>>> Core Processor Integrated Graphics Controller (rev 06) >>>>>>> 01:00.0 VGA compatible controller: Advanced Micro Devices, >>>>>>> Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] >>>>>>> >>>>>>> # glxinfo >>>>>>> name of display: :0 >>>>>>> display: :0 screen: 0 >>>>>>> direct rendering: Yes >>>>>>> server glx vendor string: SGI >>>>>>> server glx version string: 1.4 >>>>>>> server glx extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, >>>>>>> GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, >>>>>>> GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, GLX_INTEL_swap_event, >>>>>>> GLX_MESA_copy_sub_buffer, >>>>>>> GLX_OML_swap_method, GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, >>>>>>> GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_swap_control >>>>>>> client glx vendor string: Mesa Project and SGI >>>>>>> client glx version string: 1.4 >>>>>>> client glx extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, >>>>>>> GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, >>>>>>> GLX_ARB_multisample, >>>>>>> GLX_EXT_create_context_es2_profile, >>>>>>> GLX_EXT_fbconfig_packed_float, >>>>>>> GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, >>>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, >>>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>>> GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>>> GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>>> GLX_SGI_video_sync >>>>>>> GLX version: 1.4 >>>>>>> GLX extensions: >>>>>>> GLX_ARB_create_context, GLX_ARB_create_context_profile, >>>>>>> GLX_ARB_get_proc_address, GLX_ARB_multisample, >>>>>>> GLX_EXT_create_context_es2_profile, GLX_EXT_import_context, >>>>>>> GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, >>>>>>> GLX_EXT_visual_rating, >>>>>>> GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, >>>>>>> GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, >>>>>>> GLX_OML_swap_method, GLX_OML_sync_control, >>>>>>> GLX_SGIS_multisample, >>>>>>> GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, >>>>>>> GLX_SGIX_visual_select_group, >>>>>>> GLX_SGI_make_current_read, GLX_SGI_swap_control, >>>>>>> GLX_SGI_video_sync >>>>>>> OpenGL vendor string: Intel Open Source Technology Center >>>>>>> OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile >>>>>>> OpenGL core profile version string: 3.1 (Core Profile) Mesa >>>>>>> 9.2.3 >>>>>>> OpenGL core profile shading language version string: 1.40 >>>>>>> OpenGL core profile context flags: (none) >>>>>>> OpenGL core profile extensions: >>>>>>> GL_3DFX_texture_compression_FXT1, >>>>>>> GL_AMD_draw_buffers_blend, >>>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>>> GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, >>>>>>> GL_ARB_ES3_compatibility, GL_ARB_base_instance, >>>>>>> GL_ARB_blend_func_extended, GL_ARB_copy_buffer, >>>>>>> GL_ARB_debug_output, >>>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>>> GL_ARB_draw_buffers, >>>>>>> GL_ARB_draw_buffers_blend, >>>>>>> GL_ARB_draw_elements_base_vertex, >>>>>>> GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, >>>>>>> GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, >>>>>>> GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, >>>>>>> GL_ARB_get_program_binary, GL_ARB_half_float_pixel, >>>>>>> GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, >>>>>>> GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, >>>>>>> GL_ARB_map_buffer_range, GL_ARB_occlusion_query2, >>>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, >>>>>>> GL_ARB_provoking_vertex, >>>>>>> GL_ARB_robustness, GL_ARB_sampler_objects, >>>>>>> GL_ARB_seamless_cube_map, >>>>>>> GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, >>>>>>> GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, >>>>>>> GL_ARB_shading_language_packing, GL_ARB_sync, >>>>>>> GL_ARB_texture_buffer_object, >>>>>>> GL_ARB_texture_buffer_object_rgb32, >>>>>>> GL_ARB_texture_compression_rgtc, >>>>>>> GL_ARB_texture_cube_map_array, >>>>>>> GL_ARB_texture_float, GL_ARB_texture_multisample, >>>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>>> GL_ARB_uniform_buffer_object, >>>>>>> GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, >>>>>>> GL_ARB_vertex_shader, GL_ARB_vertex_type_2_10_10_10_rev, >>>>>>> GL_ATI_blend_equation_separate, GL_ATI_texture_float, >>>>>>> GL_EXT_abgr, >>>>>>> GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, >>>>>>> GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, >>>>>>> GL_EXT_framebuffer_multisample, >>>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, >>>>>>> GL_EXT_packed_float, >>>>>>> GL_EXT_pixel_buffer_object, GL_EXT_provoking_vertex, >>>>>>> GL_EXT_texture_array, >>>>>>> GL_EXT_texture_compression_dxt1, >>>>>>> GL_EXT_texture_compression_rgtc, >>>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>>> GL_EXT_transform_feedback, >>>>>>> GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, >>>>>>> GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, >>>>>>> GL_MESA_ycbcr_texture, >>>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>>> GL_NV_packed_depth_stencil, >>>>>>> GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc >>>>>>> >>>>>>> OpenGL version string: 3.0 Mesa 9.2.3 >>>>>>> OpenGL shading language version string: 1.30 >>>>>>> OpenGL context flags: (none) >>>>>>> OpenGL extensions: >>>>>>> GL_3DFX_texture_compression_FXT1, >>>>>>> GL_AMD_draw_buffers_blend, >>>>>>> GL_ANGLE_texture_compression_dxt3, >>>>>>> GL_ANGLE_texture_compression_dxt5, >>>>>>> GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, >>>>>>> GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, >>>>>>> GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, >>>>>>> GL_ARB_color_buffer_float, GL_ARB_copy_buffer, >>>>>>> GL_ARB_debug_output, >>>>>>> GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, >>>>>>> GL_ARB_depth_texture, >>>>>>> GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, >>>>>>> GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, >>>>>>> GL_ARB_explicit_attrib_location, >>>>>>> GL_ARB_fragment_coord_conventions, >>>>>>> GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, >>>>>>> GL_ARB_fragment_shader, GL_ARB_framebuffer_object, >>>>>>> GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, >>>>>>> GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, >>>>>>> GL_ARB_instanced_arrays, GL_ARB_internalformat_query, >>>>>>> GL_ARB_invalidate_subdata, GL_ARB_map_buffer_range, >>>>>>> GL_ARB_multisample, >>>>>>> GL_ARB_multitexture, GL_ARB_occlusion_query, >>>>>>> GL_ARB_occlusion_query2, >>>>>>> GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, >>>>>>> GL_ARB_point_sprite, >>>>>>> GL_ARB_provoking_vertex, GL_ARB_robustness, >>>>>>> GL_ARB_sampler_objects, >>>>>>> GL_ARB_seamless_cube_map, GL_ARB_shader_bit_encoding, >>>>>>> GL_ARB_shader_objects, GL_ARB_shader_texture_lod, >>>>>>> GL_ARB_shading_language_100, >>>>>>> GL_ARB_shading_language_420pack, >>>>>>> GL_ARB_shading_language_packing, GL_ARB_shadow, >>>>>>> GL_ARB_sync, >>>>>>> GL_ARB_texture_border_clamp, GL_ARB_texture_compression, >>>>>>> GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, >>>>>>> GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, >>>>>>> GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, >>>>>>> GL_ARB_texture_env_dot3, GL_ARB_texture_float, >>>>>>> GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, >>>>>>> GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_lod, >>>>>>> GL_ARB_texture_rectangle, GL_ARB_texture_rg, >>>>>>> GL_ARB_texture_rgb10_a2ui, >>>>>>> GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, >>>>>>> GL_ARB_texture_swizzle, GL_ARB_timer_query, >>>>>>> GL_ARB_transpose_matrix, >>>>>>> GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, >>>>>>> GL_ARB_vertex_array_object, GL_ARB_vertex_buffer_object, >>>>>>> GL_ARB_vertex_program, GL_ARB_vertex_shader, >>>>>>> GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, >>>>>>> GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, >>>>>>> GL_ATI_envmap_bumpmap, GL_ATI_separate_stencil, >>>>>>> GL_ATI_texture_env_combine3, GL_ATI_texture_float, >>>>>>> GL_EXT_abgr, >>>>>>> GL_EXT_bgra, GL_EXT_blend_color, >>>>>>> GL_EXT_blend_equation_separate, >>>>>>> GL_EXT_blend_func_separate, GL_EXT_blend_minmax, >>>>>>> GL_EXT_blend_subtract, >>>>>>> GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, >>>>>>> GL_EXT_draw_buffers2, >>>>>>> GL_EXT_draw_instanced, GL_EXT_draw_range_elements, >>>>>>> GL_EXT_fog_coord, >>>>>>> GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, >>>>>>> GL_EXT_framebuffer_multisample_blit_scaled, >>>>>>> GL_EXT_framebuffer_object, >>>>>>> GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, >>>>>>> GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, >>>>>>> GL_EXT_packed_float, GL_EXT_packed_pixels, >>>>>>> GL_EXT_pixel_buffer_object, >>>>>>> GL_EXT_point_parameters, GL_EXT_polygon_offset, >>>>>>> GL_EXT_provoking_vertex, >>>>>>> GL_EXT_rescale_normal, GL_EXT_secondary_color, >>>>>>> GL_EXT_separate_shader_objects, >>>>>>> GL_EXT_separate_specular_color, >>>>>>> GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, >>>>>>> GL_EXT_stencil_wrap, >>>>>>> GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, >>>>>>> GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, >>>>>>> GL_EXT_texture_compression_rgtc, GL_EXT_texture_cube_map, >>>>>>> GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, >>>>>>> GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, >>>>>>> GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, >>>>>>> GL_EXT_texture_lod_bias, GL_EXT_texture_object, >>>>>>> GL_EXT_texture_rectangle, >>>>>>> GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, >>>>>>> GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, >>>>>>> GL_EXT_texture_swizzle, GL_EXT_timer_query, >>>>>>> GL_EXT_transform_feedback, >>>>>>> GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, >>>>>>> GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, >>>>>>> GL_IBM_texture_mirrored_repeat, >>>>>>> GL_INGR_blend_func_separate, >>>>>>> GL_MESA_pack_invert, GL_MESA_texture_array, >>>>>>> GL_MESA_texture_signed_rgba, >>>>>>> GL_MESA_window_pos, GL_MESA_ycbcr_texture, >>>>>>> GL_NV_blend_square, >>>>>>> GL_NV_conditional_render, GL_NV_depth_clamp, >>>>>>> GL_NV_light_max_exponent, >>>>>>> GL_NV_packed_depth_stencil, GL_NV_primitive_restart, >>>>>>> GL_NV_texgen_reflection, GL_NV_texture_env_combine4, >>>>>>> GL_NV_texture_rectangle, GL_OES_EGL_image, >>>>>>> GL_OES_read_format, >>>>>>> GL_S3_s3tc, GL_SGIS_generate_mipmap, >>>>>>> GL_SGIS_texture_border_clamp, >>>>>>> GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, >>>>>>> GL_SUN_multi_draw_arrays >>>>>>> >>>>>>> 20 GLX Visuals >>>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>>> accumbuffer ms cav >>>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>>> g b a ns b eat >>>>>>> ---------------------------------------------------------------------------- >>>>>>> 0x042 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x043 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0ad 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0ae 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0af 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b0 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0b1 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0b2 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0b3 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0b4 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0b5 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b6 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b7 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0b9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0ba 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0bb 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0bc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0bd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x080 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> >>>>>>> 44 GLXFBConfigs: >>>>>>> visual x bf lv rg d st colorbuffer sr ax dp st >>>>>>> accumbuffer ms cav >>>>>>> id dep cl sp sz l ci b ro r g b a F gb bf th cl r >>>>>>> g b a ns b eat >>>>>>> ---------------------------------------------------------------------------- >>>>>>> 0x081 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x082 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x084 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x086 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x088 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08a 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08b 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08c 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 >>>>>>> 16 16 0 0 0 Slow >>>>>>> 0x08d 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x08e 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x08f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x090 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x091 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x092 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x093 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x094 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x095 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x096 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x097 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x098 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x099 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09a 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09b 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09c 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09d 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09e 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a0 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a1 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a2 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 >>>>>>> 16 16 0 0 0 Slow >>>>>>> 0x0a3 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 0 0 None >>>>>>> 0x0a4 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 >>>>>>> 16 16 16 0 0 Slow >>>>>>> 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0a7 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0a8 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 >>>>>>> 0 0 0 8 1 None >>>>>>> 0x0ab 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 4 1 None >>>>>>> 0x0ac 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 >>>>>>> 0 0 0 8 1 None >>>>>>> >>>>>>> >>>>>>> On 10/13/2014 07:42 PM, Aashish Chaudhary wrote: >>>>>>>> What graphics card / graphics driver version / OS this >>>>>>>> system has? >>>>>>>> >>>>>>>> - Aashish >>>>>>>> >>>>>>>> On Mon, Oct 13, 2014 at 1:41 PM, B.W.H. van Beest >>>>>>>> > wrote: >>>>>>>> >>>>>>>> Hi Aashish, >>>>>>>> >>>>>>>> This is what I do: >>>>>>>> 1. start paraview >>>>>>>> 2. Sources -> Wavelet -> Apply. >>>>>>>> A cube is displayed (Outline representation). >>>>>>>> 3. Select 'Volume" representation" >>>>>>>> >>>>>>>> cube disappears. Then: >>>>>>>> ===================== >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Generic Warning: In >>>>>>>> /usr/local/git/ParaView/VTK/Rendering/VolumeOpenGL/vtkOpenGLGPUVolumeRayCastMapper.cxx, >>>>>>>> line 487 >>>>>>>> failed at glBindTexture 1 OpenGL errors detected >>>>>>>> 0 : (1282) Invalid operation >>>>>>>> ========================= >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 10/13/2014 07:35 PM, Aashish Chaudhary wrote: >>>>>>>>> So when you created a wavelet source and change the >>>>>>>>> representation to volume you got the errors? Can you >>>>>>>>> post those errors? >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Oct 13, 2014 at 1:33 PM, B.W.H. van Beest >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>> Aashish, >>>>>>>>> >>>>>>>>> Thanks for the suggestion. >>>>>>>>> >>>>>>>>> However, doing this gives me all kinds of opengl >>>>>>>>> errors (invalid instruction). >>>>>>>>> >>>>>>>>> Besides that, the wavelet gives me a cube indeed, >>>>>>>>> but I need to understand when >>>>>>>>> I can have a volume rendering. I created new >>>>>>>>> Source's (e.g. tri-prism, a wedge, >>>>>>>>> a box with boundaries of finite thickness etc.). >>>>>>>>> But I cannot get volume rendering >>>>>>>>> to work, grrrrrr. (See other thread) >>>>>>>>> >>>>>>>>> Kind Regards, >>>>>>>>> Bertwim >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 10/13/2014 05:28 PM, Aashish Chaudhary wrote: >>>>>>>>>> You can create a wavelet source and then display >>>>>>>>>> it as a volume. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Oct 10, 2014 at 3:45 PM, B.W.H. van Beest >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>> Can perhaps somebody point me how to address >>>>>>>>>> the following. >>>>>>>>>> >>>>>>>>>> When I create a new source (say: a box) I get >>>>>>>>>> an a box that >>>>>>>>>> can be displayed via its surfaces, its >>>>>>>>>> constituing points, or wireframe >>>>>>>>>> representation. >>>>>>>>>> But I need a volume rendering (so that I can >>>>>>>>>> add e.g. a clipping plane) >>>>>>>>>> How do I get that? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Bertwim >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Powered by www.kitware.com >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Visit other Kitware open-source projects at >>>>>>>>>> http://www.kitware.com/opensource/opensource.html >>>>>>>>>> >>>>>>>>>> Please keep messages on-topic and check the >>>>>>>>>> ParaView Wiki at: >>>>>>>>>> http://paraview.org/Wiki/ParaView >>>>>>>>>> >>>>>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> /| Aashish Chaudhary >>>>>>>>>> | Technical Leader >>>>>>>>>> | Kitware Inc. >>>>>>>>>> / >>>>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> /| Aashish Chaudhary >>>>>>>>> | Technical Leader >>>>>>>>> | Kitware Inc. >>>>>>>>> / >>>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> /| Aashish Chaudhary >>>>>>>> | Technical Leader >>>>>>>> | Kitware Inc. >>>>>>>> / >>>>>>>> /| http://www.kitware.com/company/team/chaudhary.html/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Powered by www.kitware.com >>>>>>> >>>>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>>>> >>>>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>>>> >>>>>>> Follow this link to subscribe/unsubscribe: >>>>>>> http://public.kitware.com/mailman/listinfo/paraview >>>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >>> >>> >>> -- >>> /| Aashish Chaudhary >>> | Technical Leader >>> | Kitware Inc. >>> / >>> /| http://www.kitware.com/company/team/chaudhary.html/ >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From biddisco at cscs.ch Fri Oct 17 03:47:16 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Fri, 17 Oct 2014 07:47:16 +0000 Subject: [Paraview] Catalyst question In-Reply-To: References: <50320452A334BD42A5EC72BAD214509916BFB287@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F57632@MBX210.d.ethz.ch> <50320452A334BD42A5EC72BAD214509918F587A4@MBX210.d.ethz.ch> Message-ID: <50320452A334BD42A5EC72BAD214509918F70572@MBX110.d.ethz.ch> Andy >I'll be at SC14 and I'd be interested in seeing your demo. Are the details of when and where ready yet? At the CSCS booth, we will have a display of the simulation running on our cray. Hopefully it?ll be running on and off for a significant part of the week and we wanted to display the live results and allow interaction with the simulation by random passers by (with supervision!) so with luck, it?ll be available any time you want to see. I?ll be doing my duty and manning the booth in between the presentations at the conf etc. I think I?ll also be doing a brief guest slot on the kitware booth, but I don?t yet know the time etc. yours JB -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Fri Oct 17 11:18:00 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 17 Oct 2014 15:18:00 +0000 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option Message-ID: Hello, We would like to use the xdmf3 exporter in ParaView. Dave mentioned to add in the cmake flags to ParaView -DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON But for the superbuild process cmake -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa -DCMAKE_BUILD_TYPE=Release -DParaView_FROM_GIT=OFF -DParaView_URL=/mnt/lustre/people/ssu/build/paraview/dl/ParaView-v4.2.0-source-xdmf3.tar.gz -DENABLE_boost=ON -DENABLE_cgns=OFF -DENABLE_ffmpeg=ON -DENABLE_fontconfig=ON -DENABLE_freetype=ON -DENABLE_hdf5=ON -DENABLE_libxml2=ON -DENABLE_matplotlib=ON -DENABLE_mesa=OFF -DENABLE_mpi=ON -DENABLE_numpy=ON -DENABLE_osmesa=ON -DENABLE_paraview=ON -DENABLE_png=ON -DENABLE_python=ON -DENABLE_qhull=ON -DENABLE_qt=OFF -DENABLE_silo=ON -DENABLE_szip=ON -DENABLE_visitbridge=ON -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpich.so" -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DUSE_SYSTEM_mpi=ON -DUSE_SYSTEM_python=OFF -DUSE_SYSTEM_zlib=OFF -DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON ../ParaViewSuperbuild_4.2.0 cmake gave warning CMake Warning: Manually-specified variables were not used by the project: Boost_NO_BOOST_CMAKE Module_vtkIOXdmf3 How do I go around that? Any help is much appreciated. thanks -simon -------------- next part -------------- An HTML attachment was scrubbed... URL: From saif.a.abdulameer at gmail.com Fri Oct 17 13:06:42 2014 From: saif.a.abdulameer at gmail.com (Saif) Date: Fri, 17 Oct 2014 11:06:42 -0600 Subject: [Paraview] Paraview keep crahsing on windows 7 Message-ID: <54413cfb.282cec0a.7ff1.1fd4@mx.google.com> Hi, I am using paraview the portable version on windows 7 (64 bit), I used it for more than two month but suddenly windows give this message (paraview.exe has stopped working) I tried to install older and newer version of the program but the same results or it works for one time an crash after that could you please help me solving this issue. Problem signature: Problem Event Name: APPCRASH Application Name: paraview.exe Application Version: 0.0.0.0 Application Timestamp: 51be7198 Fault Module Name: QtCore4.dll Fault Module Version: 4.8.4.0 Fault Module Timestamp: 51959bd9 Exception Code: c0000005 Exception Offset: 0000000000070863 OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional Information 1: 0032 Additional Information 2: 00320ab9c697324423c7ceffa9a6d3f8 Additional Information 3: afb8 Additional Information 4: afb8cffc6787f3f6f9a08151e1684bb4 Thank you, -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Fri Oct 17 12:23:23 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 17 Oct 2014 12:23:23 -0400 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: Message-ID: <20141017162323.GD5747@megas.kitwarein.com> On Fri, Oct 17, 2014 at 15:18:00 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > CMake Warning: > Manually-specified variables were not used by the project: > > Boost_NO_BOOST_CMAKE > Module_vtkIOXdmf3 > > How do I go around that? The options need to be passed to the ParaView build itself, not the superbuild. There's a cache option in the superbuild named PV_EXTRA_CMAKE_ARGS which should contain "-DBoost_NO_BOOST_CMAKE:BOOL=ON -DModule_vtkIOXdmf3:BOOL=ON" to pass it to the ParaView build properly. --Ben From wascott at sandia.gov Fri Oct 17 13:21:10 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Fri, 17 Oct 2014 17:21:10 +0000 Subject: [Paraview] [EXTERNAL] Paraview keep crahsing on windows 7 In-Reply-To: <54413cfb.282cec0a.7ff1.1fd4@mx.google.com> References: <54413cfb.282cec0a.7ff1.1fd4@mx.google.com> Message-ID: Try deleting your configuration files? I would be surprised if this is the issue, since you tried multiple versions. http://www.paraview.org/Wiki/ParaView_Settings_Files. Only other thing I can think of is you have a corrupt video driver? Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Saif Sent: Friday, October 17, 2014 11:07 AM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] Paraview keep crahsing on windows 7 Hi, I am using paraview the portable version on windows 7 (64 bit), I used it for more than two month but suddenly windows give this message (paraview.exe has stopped working) I tried to install older and newer version of the program but the same results or it works for one time an crash after that could you please help me solving this issue. Problem signature: Problem Event Name: APPCRASH Application Name: paraview.exe Application Version: 0.0.0.0 Application Timestamp: 51be7198 Fault Module Name: QtCore4.dll Fault Module Version: 4.8.4.0 Fault Module Timestamp: 51959bd9 Exception Code: c0000005 Exception Offset: 0000000000070863 OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional Information 1: 0032 Additional Information 2: 00320ab9c697324423c7ceffa9a6d3f8 Additional Information 3: afb8 Additional Information 4: afb8cffc6787f3f6f9a08151e1684bb4 Thank you, -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Fri Oct 17 13:41:58 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Fri, 17 Oct 2014 17:41:58 +0000 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: <20141017162323.GD5747@megas.kitwarein.com> References: , <20141017162323.GD5747@megas.kitwarein.com> Message-ID: Hi Ben, Thanks for your help. How do I pass both arguments to ParaView build with PV_EXTRA_CMAKE_ARGS? When I do -DPV_EXTRA_CMAKE_ARGS separately, cmake didn't like it. -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON" -DPV_EXTRA_CMAKE_ARGS="-DBoost_NO_BOOST_CMAKE:BOOL=ON" I am getting CMake Warning: Manually-specified variables were not used by the project: PV_EXTRA_CMAKE_ARGS=-DBoost_NO_BOOST_CMAKE When I do both argument in the same -DPV_EXTRA_CMAKE_ARGS, cmake also didn't like it. -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" I am getting CMake Warning: Manually-specified variables were not used by the project: PV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3 But if I just do one of the argument, -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON" it worked. Please see below... thanks -simon Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build> cmake -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa -DCMAKE_BUILD_TYPE=Release -DParaView_FROM_GIT=OFF -DParaView_URL=/mnt/lustre/people/ssu/build/paraview/dl/ParaView-v4.2.0-source-xdmf3.tar.gz -DENABLE_boost=ON -DENABLE_cgns=OFF -DENABLE_ffmpeg=ON -DENABLE_fontconfig=ON -DENABLE_freetype=ON -DENABLE_hdf5=ON -DENABLE_libxml2=ON -DENABLE_matplotlib=ON -DENABLE_mesa=OFF -DENABLE_mpi=ON -DENABLE_numpy=ON -DENABLE_osmesa=ON -DENABLE_paraview=ON -DENABLE_png=ON -DENABLE_python=ON -DENABLE_qhull=ON -DENABLE_qt=OFF -DENABLE_silo=ON -DENABLE_szip=ON -DENABLE_visitbridge=ON -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpich.so" -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DUSE_SYSTEM_mpi=ON -DUSE_SYSTEM_python=OFF -DUSE_SYSTEM_zlib=OFF -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" ../ParaViewSuperbuild_4.2.0 -- Enabling zlib since needed by: boost;ffmpeg;freetype;hdf5;png;python;silo -- Enabling boost as requested. -- Enabling ffmpeg as requested. -- Enabling freetype as requested. -- Enabling libxml2 as requested. -- Enabling fontconfig as requested. -- Enabling szip as requested. -- Enabling hdf5 as requested. -- Enabling bzip2 since needed by: python -- Enabling png as requested. -- Enabling python as requested. -- Enabling numpy as requested. -- Enabling matplotlib as requested. -- Enabling mpi as requested. -- Enabling osmesa as requested. -- Enabling qhull as requested. -- Enabling silo as requested. -- Enabling visitbridge as requested. -- Enabling paraview as requested. -- PROJECTS_ENABLED zlib;boost;ffmpeg;freetype;libxml2;fontconfig;szip;hdf5;bzip2;png;python;numpy;matplotlib;mpi;osmesa;qhull;silo;visitbridge;paraview -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: PV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3 -- Build files have been written to: /usr/people/ssu/build/paraview/Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build> cmake -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa -DCMAKE_BUILD_TYPE=Release -DParaView_FROM_GIT=OFF -DParaView_URL=/mnt/lustre/people/ssu/build/paraview/dl/ParaView-v4.2.0-source-xdmf3.tar.gz -DENABLE_boost=ON -DENABLE_cgns=OFF -DENABLE_ffmpeg=ON -DENABLE_fontconfig=ON -DENABLE_freetype=ON -DENABLE_hdf5=ON -DENABLE_libxml2=ON -DENABLE_matplotlib=ON -DENABLE_mesa=OFF -DENABLE_mpi=ON -DENABLE_numpy=ON -DENABLE_osmesa=ON -DENABLE_paraview=ON -DENABLE_png=ON -DENABLE_python=ON -DENABLE_qhull=ON -DENABLE_qt=OFF -DENABLE_silo=ON -DENABLE_szip=ON -DENABLE_visitbridge=ON -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpich.so" -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DUSE_SYSTEM_mpi=ON -DUSE_SYSTEM_python=OFF -DUSE_SYSTEM_zlib=OFF -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON" ../ParaViewSuperbuild_4.2.0 -- Enabling zlib since needed by: boost;ffmpeg;freetype;hdf5;png;python;silo -- Enabling boost as requested. -- Enabling ffmpeg as requested. -- Enabling freetype as requested. -- Enabling libxml2 as requested. -- Enabling fontconfig as requested. -- Enabling szip as requested. -- Enabling hdf5 as requested. -- Enabling bzip2 since needed by: python -- Enabling png as requested. -- Enabling python as requested. -- Enabling numpy as requested. -- Enabling matplotlib as requested. -- Enabling mpi as requested. -- Enabling osmesa as requested. -- Enabling qhull as requested. -- Enabling silo as requested. -- Enabling visitbridge as requested. -- Enabling paraview as requested. -- PROJECTS_ENABLED zlib;boost;ffmpeg;freetype;libxml2;fontconfig;szip;hdf5;bzip2;png;python;numpy;matplotlib;mpi;osmesa;qhull;silo;visitbridge;paraview -- Configuring done -- Generating done -- Build files have been written to: /usr/people/ssu/build/paraview/Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build> cmake -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_osmesa -DCMAKE_BUILD_TYPE=Release -DParaView_FROM_GIT=OFF -DParaView_URL=/mnt/lustre/people/ssu/build/paraview/dl/ParaView-v4.2.0-source-xdmf3.tar.gz -DENABLE_boost=ON -DENABLE_cgns=OFF -DENABLE_ffmpeg=ON -DENABLE_fontconfig=ON -DENABLE_freetype=ON -DENABLE_hdf5=ON -DENABLE_libxml2=ON -DENABLE_matplotlib=ON -DENABLE_mesa=OFF -DENABLE_mpi=ON -DENABLE_numpy=ON -DENABLE_osmesa=ON -DENABLE_paraview=ON -DENABLE_png=ON -DENABLE_python=ON -DENABLE_qhull=ON -DENABLE_qt=OFF -DENABLE_silo=ON -DENABLE_szip=ON -DENABLE_visitbridge=ON -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpich.so" -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/lib/libmpichcxx.so" -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/5.3.5/xt/seastar/mpich2-gnu/46/include/" -DUSE_SYSTEM_mpi=ON -DUSE_SYSTEM_python=OFF -DUSE_SYSTEM_zlib=OFF -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON" -DPV_EXTRA_CMAKE_ARGS="-DBoost_NO_BOOST_CMAKE:BOOL=ON" ../ParaViewSuperbuild_4.2.0 -- Enabling zlib since needed by: boost;ffmpeg;freetype;hdf5;png;python;silo -- Enabling boost as requested. -- Enabling ffmpeg as requested. -- Enabling freetype as requested. -- Enabling libxml2 as requested. -- Enabling fontconfig as requested. -- Enabling szip as requested. -- Enabling hdf5 as requested. -- Enabling bzip2 since needed by: python -- Enabling png as requested. -- Enabling python as requested. -- Enabling numpy as requested. -- Enabling matplotlib as requested. -- Enabling mpi as requested. -- Enabling osmesa as requested. -- Enabling qhull as requested. -- Enabling silo as requested. -- Enabling visitbridge as requested. -- Enabling paraview as requested. -- PROJECTS_ENABLED zlib;boost;ffmpeg;freetype;libxml2;fontconfig;szip;hdf5;bzip2;png;python;numpy;matplotlib;mpi;osmesa;qhull;silo;visitbridge;paraview -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: PV_EXTRA_CMAKE_ARGS=-DBoost_NO_BOOST_CMAKE -- Build files have been written to: /usr/people/ssu/build/paraview/Build_mesa-2014-10-15/ParaViewSuperbuild_4.2.0-build ________________________________________ From: Ben Boeckel [ben.boeckel at kitware.com] Sent: Friday, October 17, 2014 12:23 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option On Fri, Oct 17, 2014 at 15:18:00 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > CMake Warning: > Manually-specified variables were not used by the project: > > Boost_NO_BOOST_CMAKE > Module_vtkIOXdmf3 > > How do I go around that? The options need to be passed to the ParaView build itself, not the superbuild. There's a cache option in the superbuild named PV_EXTRA_CMAKE_ARGS which should contain "-DBoost_NO_BOOST_CMAKE:BOOL=ON -DModule_vtkIOXdmf3:BOOL=ON" to pass it to the ParaView build properly. --Ben From ben.boeckel at kitware.com Fri Oct 17 22:06:00 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Fri, 17 Oct 2014 22:06:00 -0400 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: <20141017162323.GD5747@megas.kitwarein.com> Message-ID: <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> On Fri, Oct 17, 2014 at 17:41:58 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > When I do both argument in the same -DPV_EXTRA_CMAKE_ARGS, cmake also didn't like it. > -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > > I am getting > CMake Warning: > Manually-specified variables were not used by the project: > > PV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3 Weird. It looks like the argument is being split at the colon? Playing around with it a bit, it seems it's the shell's doing. Put the quotes around the entire argument, not after the equals sign. --Ben From artemiev.mikhail at gmail.com Sat Oct 18 16:57:16 2014 From: artemiev.mikhail at gmail.com (Mikhail Artemyev) Date: Sat, 18 Oct 2014 15:57:16 -0500 Subject: [Paraview] Questions on vector images output Message-ID: Dear all, I have two questions related to the vector images output from ParaView for 3D. I use ParaView 4.1.0 32-bit on Ubuntu. 1. I've read here (http://www.kitware.com/blog/home/post/508) in the discussion after the post that if the "colors are generated from point/cell attributes", "the exporter should be able to handle it once 'Rasterize 3D geometry' turned off". Otherwise "you may end up with your exported object appearing grey/colorless". That's exactly what happens in my case. However my 3D picture is based on a rectangular grid with values of the computed field defined at the vertices of the grid. I understand that for visualization ParaView convert the rectangles to triangles first (and it's clearly seen from the grey/colorless image I have), therefore I'm wondering if it'll help if I replace rectangular mesh to triangular from my side. 2. The second question is why the labels of the axis have some triangulation inside them (here is a picture http://drive.google.com/file/d/0B-0jjlhN_6HyWkR1bWoxc3dVazA/view?usp=sharing). Is it GL2PS feature? How can I make them look like labels on colour bar? Thank you, Mikhail -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.lonie at kitware.com Mon Oct 20 10:22:41 2014 From: david.lonie at kitware.com (David Lonie) Date: Mon, 20 Oct 2014 10:22:41 -0400 Subject: [Paraview] Questions on vector images output In-Reply-To: References: Message-ID: Hi Mikhail, 1) The triangulation artifacts you're seeing are likely due to antialiasing in the viewer. Turning AA off (or using a different viewer) should make the gaps between the triangles disappear and the surface should appear smooth again. 2) The axis labels are 3D objects with rotations away from the plane of the image, while the scalar bar labels are in the plane of the image. This means that the scalar bar labels can be inserted as actual text (i.e. tell the viewer to draw the string "interior_bf_0"), but the axis labels have to be drawn as bezier curves (i.e. tells the viewer to draw the shape of the text) since the output image formats can't embed arbitrarily oriented text. To fix the issue with the gaps, it looks like viewer antialiasing is the likely culprit again. Hope this helps, Dave On Sat, Oct 18, 2014 at 4:57 PM, Mikhail Artemyev < artemiev.mikhail at gmail.com> wrote: > Dear all, > > I have two questions related to the vector images output from ParaView for > 3D. I use ParaView 4.1.0 32-bit on Ubuntu. > > 1. I've read here (http://www.kitware.com/blog/home/post/508) in the > discussion after the post that if the "colors are generated from > point/cell attributes", "the exporter should be able to handle it once > 'Rasterize 3D geometry' turned off". Otherwise "you may end up with your > exported object appearing grey/colorless". That's exactly what happens in > my case. However my 3D picture is based on a rectangular grid with values > of the computed field defined at the vertices of the grid. I understand > that for visualization ParaView convert the rectangles to triangles first > (and it's clearly seen from the grey/colorless image I have), therefore I'm > wondering if it'll help if I replace rectangular mesh to triangular from my > side. > > 2. The second question is why the labels of the axis have some > triangulation inside them (here is a picture > http://drive.google.com/file/d/0B-0jjlhN_6HyWkR1bWoxc3dVazA/view?usp=sharing). > Is it GL2PS feature? How can I make them look like labels on colour bar? > > Thank you, > Mikhail > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From artemiev.mikhail at gmail.com Mon Oct 20 10:30:17 2014 From: artemiev.mikhail at gmail.com (Mikhail Artemyev) Date: Mon, 20 Oct 2014 09:30:17 -0500 Subject: [Paraview] Questions on vector images output In-Reply-To: References: Message-ID: <54451C79.9090909@gmail.com> Hi Dave, Thank you for the reply. Switching from evince viewer to acroread did resolve this issue. Best regards, Mikhail On 10/20/2014 09:22 AM, David Lonie wrote: > Hi Mikhail, > > 1) The triangulation artifacts you're seeing are likely due to > antialiasing in the viewer. Turning AA off (or using a different > viewer) should make the gaps between the triangles disappear and the > surface should appear smooth again. > > 2) The axis labels are 3D objects with rotations away from the plane > of the image, while the scalar bar labels are in the plane of the > image. This means that the scalar bar labels can be inserted as actual > text (i.e. tell the viewer to draw the string "interior_bf_0"), but > the axis labels have to be drawn as bezier curves (i.e. tells the > viewer to draw the shape of the text) since the output image formats > can't embed arbitrarily oriented text. To fix the issue with the gaps, > it looks like viewer antialiasing is the likely culprit again. > > Hope this helps, > Dave > > On Sat, Oct 18, 2014 at 4:57 PM, Mikhail Artemyev > > wrote: > > Dear all, > > I have two questions related to the vector images output from > ParaView for 3D. I use ParaView 4.1.0 32-bit on Ubuntu. > > 1. I've read here (http://www.kitware.com/blog/home/post/508) in > the discussion after the post that if the "colors are generated > from point/cell attributes", "the exporter should be able to > handle it once 'Rasterize 3D geometry' turned off". Otherwise "you > may end up with your exported object appearing grey/colorless". > That's exactly what happens in my case. However my 3D picture is > based on a rectangular grid with values of the computed field > defined at the vertices of the grid. I understand that for > visualization ParaView convert the rectangles to triangles first > (and it's clearly seen from the grey/colorless image I have), > therefore I'm wondering if it'll help if I replace rectangular > mesh to triangular from my side. > > 2. The second question is why the labels of the axis have some > triangulation inside them (here is a picture > http://drive.google.com/file/d/0B-0jjlhN_6HyWkR1bWoxc3dVazA/view?usp=sharing). > Is it GL2PS feature? How can I make them look like labels on > colour bar? > > Thank you, > Mikhail > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Mon Oct 20 11:15:59 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 20 Oct 2014 15:15:59 +0000 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> References: <20141017162323.GD5747@megas.kitwarein.com> , <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> Message-ID: Ben, I ran cmake with -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable PV_EXTRA_CMAKE_ARGS It appears :STRING does the trick. I am running the compile now. Hopefully that does the trick. thanks -simon ________________________________________ From: Ben Boeckel [ben.boeckel at kitware.com] Sent: Friday, October 17, 2014 10:06 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option On Fri, Oct 17, 2014 at 17:41:58 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > When I do both argument in the same -DPV_EXTRA_CMAKE_ARGS, cmake also didn't like it. > -DPV_EXTRA_CMAKE_ARGS="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > > I am getting > CMake Warning: > Manually-specified variables were not used by the project: > > PV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3 Weird. It looks like the argument is being split at the colon? Playing around with it a bit, it seems it's the shell's doing. Put the quotes around the entire argument, not after the equals sign. --Ben From ben.boeckel at kitware.com Mon Oct 20 11:43:32 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Mon, 20 Oct 2014 11:43:32 -0400 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: <20141017162323.GD5747@megas.kitwarein.com> <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> Message-ID: <20141020154332.GB7304@megas.kitwarein.com> On Mon, Oct 20, 2014 at 15:15:59 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I ran cmake with > > -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > > and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON > -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable > PV_EXTRA_CMAKE_ARGS > > It appears :STRING does the trick. Yep. This is a CMake parsing bug; the regular expression for this is too greedy (it allows '=' in the variable name). Compare: > -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON |-------------------------------------| |--| |-------------------------------| variable type value versus: > -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON |-----------------| |----| |--------------------------------------------------------| variable type value this works: > -DSOME_PATH=C:/path/to/file |-------| |-------------| variable value because paths with '=' are very rare: > -DSOME_PATH=C:/path/to/file/with/=/sign |---------| |-----------------| |---| variable type value --Ben From simon.m.su.ctr at mail.mil Mon Oct 20 11:57:26 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 20 Oct 2014 15:57:26 +0000 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: <20141020154332.GB7304@megas.kitwarein.com> References: <20141017162323.GD5747@megas.kitwarein.com> <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> , <20141020154332.GB7304@megas.kitwarein.com> Message-ID: Ben, Unfortunately, when I checked the CMakeCache.txt in the directory paraview/src/paraview-build after the cmake ran, I am still finding //Request building vtkIOXdmf3 Module_vtkIOXdmf3:BOOL=OFF and Boost_NO_BOOST_CMAKE is none existence in the CMakeCache.txt I even tried both -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" and -DPV_EXTRA_CMAKE_ARGS:STRING="Module_vtkIOXdmf3:BOOL=ON Boost_NO_BOOST_CMAKE:BOOL=ON" thoughts? thanks -simon ________________________________________ From: Ben Boeckel [ben.boeckel at kitware.com] Sent: Monday, October 20, 2014 11:43 AM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option On Mon, Oct 20, 2014 at 15:15:59 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > I ran cmake with > > -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > > and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON > -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable > PV_EXTRA_CMAKE_ARGS > > It appears :STRING does the trick. Yep. This is a CMake parsing bug; the regular expression for this is too greedy (it allows '=' in the variable name). Compare: > -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON |-------------------------------------| |--| |-------------------------------| variable type value versus: > -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON |-----------------| |----| |--------------------------------------------------------| variable type value this works: > -DSOME_PATH=C:/path/to/file |-------| |-------------| variable value because paths with '=' are very rare: > -DSOME_PATH=C:/path/to/file/with/=/sign |---------| |-----------------| |---| variable type value --Ben From ben.boeckel at kitware.com Tue Oct 21 15:06:27 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Tue, 21 Oct 2014 15:06:27 -0400 Subject: [Paraview] [ANN] New 4.2.0 Release Binary for OS X 10.6 (Snow Leopard) Message-ID: <20141021190627.GA3913@megas.kitwarein.com> Hi all, We've tracked down the error with the Snow Leopard builds of ParaView 4.2.0 and new binaries have been uploaded to the website available through the normal download page. To ensure you have the new binary, the md5sum of the new dmg file is: b1289277d12563321212ed83b70c2f20 The cause of the issue was that the machine building the binaries is a newer OS X install which contains AVFoundation. This is detected and linked to by FFmpeg automatically because it never received the proper --sysroot flag for 10.6. FFmpeg now receives the proper CFLAGS and LDFLAGS in the superbuild (which should be receiving a new tag in the next day or two). Thanks, --Ben From kit.chambers.kc at gmail.com Tue Oct 21 21:32:13 2014 From: kit.chambers.kc at gmail.com (Kit Chambers) Date: Tue, 21 Oct 2014 20:32:13 -0500 Subject: [Paraview] Labeling specific points in dataset In-Reply-To: References: Message-ID: <5447091D.7080500@googlemail.com> Thanks David/Utkarsh, In the end the proceedure I went for to construct the labels was. 1- Use GenerateScalarIds filter to create a data array with the point IDs 2- Use MaskPoints filter to decimate the array 3- Use the DataLabel representation with the decimated array to show and the original IDs to draw the labels. Thanks for you help on this. Kit On 16/10/2014 08:16, Utkarsh Ayachit wrote: > You can tell DataLabelRepresentation to label using any data array. By > adding an array such as "original ids" or something during the > extraction processes, you can tell the representation to use that > array for labeling instead. That's pretty much on extract-selection > filters work too. > > On Thu, Oct 16, 2014 at 7:29 AM, Kit Chambers wrote: >> Hi Everyone, >> >> I have a dataset of about 1000 or so points and I want to label say every >> 100'th point with the point id. I can use the DataLabelRepresentation if I >> want to label every point, but as far as I can tell this cannot label only >> certain points it is everything or nothing. I could also create a new >> dataset with every 100th point in it and use that with the >> DataLabelRepresentation but then the point ids would be wrong. >> >> Any ideas or suggestions are welcome. >> >> Cheers >> >> Kit >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> From stephen.wornom at inria.fr Wed Oct 22 05:39:59 2014 From: stephen.wornom at inria.fr (Stephen Wornom) Date: Wed, 22 Oct 2014 11:39:59 +0200 Subject: [Paraview] PV 4.1 How to extract a slice for z= constant Message-ID: <54477B6F.1090906@inria.fr> The mesh is unstructured, PV running mpi. The mesh is rectangular. I would like to extract an exterior boundary. How does one do this? Thanks, Stephen From kmorel at sandia.gov Wed Oct 22 08:40:36 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Wed, 22 Oct 2014 12:40:36 +0000 Subject: [Paraview] PV 4.1 How to extract a slice for z= constant In-Reply-To: <54477B6F.1090906@inria.fr> References: <54477B6F.1090906@inria.fr> Message-ID: <1c1714612259491b8d158fe200fa13e0@ES02AMSNLNT.srn.sandia.gov> The subject line of this email asks how to extract a slice in a z=constant plane. That can easily be done with the slice filter with the normal set to 0,0,1. The text of this email asks a completely different question, extracting the exterior boundary of an unstructured mesh. This is done with the Extract Surface filter. If your data is distributed with MPI and does not have ghost cells (which is common in unstructured data files) it is possible that Extract Surface will also extract some interior surfaces at the boundary of the geometry partitions. If this is a problem, you can first use the D3 filter to generate ghost cells and then run the Extract Surface filter. -Ken ________________________________________ From: ParaView on behalf of Stephen Wornom Sent: Wednesday, October 22, 2014 3:39 AM To: paraview Subject: [EXTERNAL] [Paraview] PV 4.1 How to extract a slice for z= constant The mesh is unstructured, PV running mpi. The mesh is rectangular. I would like to extract an exterior boundary. How does one do this? Thanks, Stephen _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Wed Oct 22 10:19:55 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 22 Oct 2014 16:19:55 +0200 Subject: [Paraview] Filter to keep points, dropping topology Message-ID: <5447BD0B.50509@xs4all.nl> Hello, I need a filter that only keeps the 3D points of a certain source (e.g. coming from an stl file). The topology of the data set may go. I thought that the following filter, only passing through the pointdata, would do the job, but that appears not to be the case (no points after the filter!) What's going wrong and how should I change the filter? Kind Regards, Bertwim ================ int FilterPoints::RequestData( vtkInformation*, vtkInformationVector** inputVector, vtkInformationVector* outputVector) { // Get the input and output data objects. vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); vtkDataSet* output = vtkDataSet::GetData( outputVector ); // output->CopyStructure( input ); output->GetPointData()->PassData( input->GetPointData() ); return 1; } From biddisco at cscs.ch Wed Oct 22 10:52:43 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Wed, 22 Oct 2014 14:52:43 +0000 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: <5447BD0B.50509@xs4all.nl> Message-ID: Output->SetPoints(input->GetPoints()); Or Output->CopyStructure(input); Output->SetCells(NULL) Then copy point field data etc On 22/10/14 16:19, "B.W.H. van Beest" wrote: >Hello, > >I need a filter that only keeps the 3D points of a certain source (e.g. >coming from an stl file). >The topology of the data set may go. > >I thought that the following filter, only passing through the pointdata, >would do the job, >but that appears not to be the case (no points after the filter!) >What's going wrong and how should I change the filter? > >Kind Regards, >Bertwim > >================ > >int FilterPoints::RequestData( vtkInformation*, > vtkInformationVector** >inputVector, > vtkInformationVector* >outputVector) >{ > // Get the input and output data objects. > vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); > vtkDataSet* output = vtkDataSet::GetData( outputVector ); > > // output->CopyStructure( input ); > output->GetPointData()->PassData( input->GetPointData() ); > > return 1; >} > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Wed Oct 22 10:58:33 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 22 Oct 2014 07:58:33 -0700 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: References: Message-ID: <5447C619.9080508@gmail.com> don't forget to add vertex type cells, or you will not be able to see the points, and that it's going to be more complicated if you're starting from data types that have implicit points. On 10/22/2014 07:52 AM, Biddiscombe, John A. wrote: > Output->SetPoints(input->GetPoints()); > > Or > > Output->CopyStructure(input); > Output->SetCells(NULL) > > Then copy point field data etc > > > On 22/10/14 16:19, "B.W.H. van Beest" wrote: > >> Hello, >> >> I need a filter that only keeps the 3D points of a certain source (e.g. >> coming from an stl file). >> The topology of the data set may go. >> >> I thought that the following filter, only passing through the pointdata, >> would do the job, >> but that appears not to be the case (no points after the filter!) >> What's going wrong and how should I change the filter? >> >> Kind Regards, >> Bertwim >> >> ================ >> >> int FilterPoints::RequestData( vtkInformation*, >> vtkInformationVector** >> inputVector, >> vtkInformationVector* >> outputVector) >> { >> // Get the input and output data objects. >> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >> >> // output->CopyStructure( input ); >> output->GetPointData()->PassData( input->GetPointData() ); >> >> return 1; >> } >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Wed Oct 22 11:01:13 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 22 Oct 2014 08:01:13 -0700 Subject: [Paraview] artifacts in image data volume rendering Message-ID: <5447C6B9.4020902@gmail.com> Hi, I'm encountering what look like process boundaries in image data volume rendering. This is view dependent, only certain camera locations reveal the issue. In examples below these are "horizontal line" like artifacts. This data is large, and I have not been able to successfully volume render after tetrahedralizing it. I'm not sure if it's just insanely slow or there's a deadlock. My attempts have been up to 1024 procs with 8 per node (8 GB per proc), That's about the smallest I can to get enough ram to do the terahedralization, about 50% of the ram is used after the tetrahedralization. Does anyone know if the fixed point vr algorithm is parallel aware, would adding ghost zones to the image data help?? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bcjjciig.png Type: image/png Size: 375832 bytes Desc: not available URL: From bwvb at xs4all.nl Wed Oct 22 11:11:21 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 22 Oct 2014 17:11:21 +0200 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: References: Message-ID: <5447C919.5080803@xs4all.nl> The compiler tells me: error: ?class vtkDataSet? has no member named ?SetPoints? Likewise, SetCells() is also not a member function of vtkDataSet. Indeed, according to the doc, there is no such function. Any idea? On 10/22/2014 04:52 PM, Biddiscombe, John A. wrote: > Output->SetPoints(input->GetPoints()); > > Or > > Output->CopyStructure(input); > Output->SetCells(NULL) > > Then copy point field data etc > > > On 22/10/14 16:19, "B.W.H. van Beest" wrote: > >> Hello, >> >> I need a filter that only keeps the 3D points of a certain source (e.g. >> coming from an stl file). >> The topology of the data set may go. >> >> I thought that the following filter, only passing through the pointdata, >> would do the job, >> but that appears not to be the case (no points after the filter!) >> What's going wrong and how should I change the filter? >> >> Kind Regards, >> Bertwim >> >> ================ >> >> int FilterPoints::RequestData( vtkInformation*, >> vtkInformationVector** >> inputVector, >> vtkInformationVector* >> outputVector) >> { >> // Get the input and output data objects. >> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >> >> // output->CopyStructure( input ); >> output->GetPointData()->PassData( input->GetPointData() ); >> >> return 1; >> } >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From bwvb at xs4all.nl Wed Oct 22 11:15:55 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 22 Oct 2014 17:15:55 +0200 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: <5447C619.9080508@gmail.com> References: <5447C619.9080508@gmail.com> Message-ID: <5447CA2B.2070804@xs4all.nl> Are you saying that one cannot have just points? In my case, I want to snap the points to a structured grid, but haven't done that yet, as I wanted to see the points first, and do the snapping as a next step. So that is not a good idea? I need to do it all in one go? Regards, Bertwim On 10/22/2014 04:58 PM, Burlen Loring wrote: > don't forget to add vertex type cells, or you will not be able to see > the points, and that it's going to be more complicated if you're > starting from data types that have implicit points. > > > On 10/22/2014 07:52 AM, Biddiscombe, John A. wrote: >> Output->SetPoints(input->GetPoints()); >> >> Or >> >> Output->CopyStructure(input); >> Output->SetCells(NULL) >> >> Then copy point field data etc >> >> >> On 22/10/14 16:19, "B.W.H. van Beest" wrote: >> >>> Hello, >>> >>> I need a filter that only keeps the 3D points of a certain source (e.g. >>> coming from an stl file). >>> The topology of the data set may go. >>> >>> I thought that the following filter, only passing through the >>> pointdata, >>> would do the job, >>> but that appears not to be the case (no points after the filter!) >>> What's going wrong and how should I change the filter? >>> >>> Kind Regards, >>> Bertwim >>> >>> ================ >>> >>> int FilterPoints::RequestData( vtkInformation*, >>> vtkInformationVector** >>> inputVector, >>> vtkInformationVector* >>> outputVector) >>> { >>> // Get the input and output data objects. >>> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >>> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >>> >>> // output->CopyStructure( input ); >>> output->GetPointData()->PassData( input->GetPointData() ); >>> return 1; >>> } >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > > > From biddisco at cscs.ch Wed Oct 22 11:32:13 2014 From: biddisco at cscs.ch (Biddiscombe, John A.) Date: Wed, 22 Oct 2014 15:32:13 +0000 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: <5447CA2B.2070804@xs4all.nl> Message-ID: SetPoints is present in vtkDataSets that are subclasses of vtkPointSet You said you didn?t want any topology, so I didn?t think you wanted vertex cells. vtkSmartPointer vertices = vtkSmartPointer::New(); vtkIdType *cells = vertices->WritePointer(Nt, 2*Nt); for (vtkIdType i=0; iSetVerts(vertices); } On 22/10/14 17:15, "B.W.H. van Beest" wrote: >Are you saying that one cannot have just points? > >In my case, I want to snap the points to a structured grid, >but haven't done that yet, as I wanted to see the >points first, and do the snapping as a next step. >So that is not a good idea? I need to do it all in one go? > >Regards, >Bertwim > > > > > >On 10/22/2014 04:58 PM, Burlen Loring wrote: >> don't forget to add vertex type cells, or you will not be able to see >> the points, and that it's going to be more complicated if you're >> starting from data types that have implicit points. >> >> >> On 10/22/2014 07:52 AM, Biddiscombe, John A. wrote: >>> Output->SetPoints(input->GetPoints()); >>> >>> Or >>> >>> Output->CopyStructure(input); >>> Output->SetCells(NULL) >>> >>> Then copy point field data etc >>> >>> >>> On 22/10/14 16:19, "B.W.H. van Beest" wrote: >>> >>>> Hello, >>>> >>>> I need a filter that only keeps the 3D points of a certain source >>>>(e.g. >>>> coming from an stl file). >>>> The topology of the data set may go. >>>> >>>> I thought that the following filter, only passing through the >>>> pointdata, >>>> would do the job, >>>> but that appears not to be the case (no points after the filter!) >>>> What's going wrong and how should I change the filter? >>>> >>>> Kind Regards, >>>> Bertwim >>>> >>>> ================ >>>> >>>> int FilterPoints::RequestData( vtkInformation*, >>>> vtkInformationVector** >>>> inputVector, >>>> vtkInformationVector* >>>> outputVector) >>>> { >>>> // Get the input and output data objects. >>>> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >>>> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >>>> >>>> // output->CopyStructure( input ); >>>> output->GetPointData()->PassData( input->GetPointData() ); >>>> return 1; >>>> } >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Wed Oct 22 11:58:29 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Wed, 22 Oct 2014 08:58:29 -0700 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: <5447CA2B.2070804@xs4all.nl> References: <5447C619.9080508@gmail.com> <5447CA2B.2070804@xs4all.nl> Message-ID: <5447D425.6080409@gmail.com> you can have just points, they'll be ignored during rendering without vertex type cells. On 10/22/2014 08:15 AM, B.W.H. van Beest wrote: > Are you saying that one cannot have just points? > > In my case, I want to snap the points to a structured grid, > but haven't done that yet, as I wanted to see the > points first, and do the snapping as a next step. > So that is not a good idea? I need to do it all in one go? > > Regards, > Bertwim > > > > > > On 10/22/2014 04:58 PM, Burlen Loring wrote: >> don't forget to add vertex type cells, or you will not be able to see >> the points, and that it's going to be more complicated if you're >> starting from data types that have implicit points. >> >> >> On 10/22/2014 07:52 AM, Biddiscombe, John A. wrote: >>> Output->SetPoints(input->GetPoints()); >>> >>> Or >>> >>> Output->CopyStructure(input); >>> Output->SetCells(NULL) >>> >>> Then copy point field data etc >>> >>> >>> On 22/10/14 16:19, "B.W.H. van Beest" wrote: >>> >>>> Hello, >>>> >>>> I need a filter that only keeps the 3D points of a certain source (e.g. >>>> coming from an stl file). >>>> The topology of the data set may go. >>>> >>>> I thought that the following filter, only passing through the >>>> pointdata, >>>> would do the job, >>>> but that appears not to be the case (no points after the filter!) >>>> What's going wrong and how should I change the filter? >>>> >>>> Kind Regards, >>>> Bertwim >>>> >>>> ================ >>>> >>>> int FilterPoints::RequestData( vtkInformation*, >>>> vtkInformationVector** >>>> inputVector, >>>> vtkInformationVector* >>>> outputVector) >>>> { >>>> // Get the input and output data objects. >>>> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >>>> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >>>> >>>> // output->CopyStructure( input ); >>>> output->GetPointData()->PassData( input->GetPointData() ); >>>> return 1; >>>> } >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> >> From bwvb at xs4all.nl Wed Oct 22 13:32:00 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Wed, 22 Oct 2014 19:32:00 +0200 Subject: [Paraview] Filter to keep points, dropping topology In-Reply-To: References: Message-ID: <5447EA10.1060107@xs4all.nl> Ah, I found it. It is the other way around: vtkPointSet is a subclass of vtkDataSet. The former has SetPoints, the latter has not. So I subclassed my filter class from vtkPointSet instead of vtkDataSet, and it now it works. Thanks. Bertwim Kind Regards, Bertwim On 10/22/2014 05:32 PM, Biddiscombe, John A. wrote: > SetPoints is present in vtkDataSets that are subclasses of vtkPointSet > > You said you didn?t want any topology, so I didn?t think you wanted vertex > cells. > > vtkSmartPointer vertices = > vtkSmartPointer::New(); > vtkIdType *cells = vertices->WritePointer(Nt, 2*Nt); > for (vtkIdType i=0; i { > cells[2*i] = 1; > cells[2*i+1] = i; > } > output->SetVerts(vertices); > } > > > > > On 22/10/14 17:15, "B.W.H. van Beest" wrote: > >> Are you saying that one cannot have just points? >> >> In my case, I want to snap the points to a structured grid, >> but haven't done that yet, as I wanted to see the >> points first, and do the snapping as a next step. >> So that is not a good idea? I need to do it all in one go? >> >> Regards, >> Bertwim >> >> >> >> >> >> On 10/22/2014 04:58 PM, Burlen Loring wrote: >>> don't forget to add vertex type cells, or you will not be able to see >>> the points, and that it's going to be more complicated if you're >>> starting from data types that have implicit points. >>> >>> >>> On 10/22/2014 07:52 AM, Biddiscombe, John A. wrote: >>>> Output->SetPoints(input->GetPoints()); >>>> >>>> Or >>>> >>>> Output->CopyStructure(input); >>>> Output->SetCells(NULL) >>>> >>>> Then copy point field data etc >>>> >>>> >>>> On 22/10/14 16:19, "B.W.H. van Beest" wrote: >>>> >>>>> Hello, >>>>> >>>>> I need a filter that only keeps the 3D points of a certain source >>>>> (e.g. >>>>> coming from an stl file). >>>>> The topology of the data set may go. >>>>> >>>>> I thought that the following filter, only passing through the >>>>> pointdata, >>>>> would do the job, >>>>> but that appears not to be the case (no points after the filter!) >>>>> What's going wrong and how should I change the filter? >>>>> >>>>> Kind Regards, >>>>> Bertwim >>>>> >>>>> ================ >>>>> >>>>> int FilterPoints::RequestData( vtkInformation*, >>>>> vtkInformationVector** >>>>> inputVector, >>>>> vtkInformationVector* >>>>> outputVector) >>>>> { >>>>> // Get the input and output data objects. >>>>> vtkDataSet* input = vtkDataSet::GetData( inputVector[0] ); >>>>> vtkDataSet* output = vtkDataSet::GetData( outputVector ); >>>>> >>>>> // output->CopyStructure( input ); >>>>> output->GetPointData()->PassData( input->GetPointData() ); >>>>> return 1; >>>>> } >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From wascott at sandia.gov Wed Oct 22 19:44:15 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 22 Oct 2014 23:44:15 +0000 Subject: [Paraview] Feature request - Need more detailed control of generating nodal quantities from element results Message-ID: <6652ad5b31d448968120dde0977cff7e@ES05AMSNLNT.srn.sandia.gov> A question from a user. I believe that answer is correct to the first bullet, and the answer is no to the second bullet? 1 - Averaging a nodal result from surrounding elements is OK as long as the node is within a homogenous body. This process is not correct for nodes on the boundary between two different materials. 2 - Is there a process to extrapolate element integration point quantities (stresses, strains) to nodes for elements with non-linear shape functions? Thanks, Alan From burlen.loring at gmail.com Thu Oct 23 09:31:55 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Thu, 23 Oct 2014 06:31:55 -0700 Subject: [Paraview] artifacts in image data volume rendering In-Reply-To: References: <5447C6B9.4020902@gmail.com> Message-ID: <5449034B.70308@gmail.com> Hi Aashish, Great! I've been seeing this bug for a long time going back at least to ParaView 3.8. It's image data, and I have used the ray cast only option in ParaView which in the end (via vtk smart volume mapper) corresponds to the vtk fixed point volume mapper. For this run I used 256 procs, I can share the data and a state file if it would help. Burlen On 10/23/2014 12:41 AM, Aashish Chaudhary wrote: > Burlen, > > this certainly looks like the parallel compositing issue to me and we > have seen it before. Just to be clear what mapper you were using to > generate this image? I would love to track dow this issue and > can certainly use your help here. > > - Aashish > > On Wed, Oct 22, 2014 at 11:01 AM, Burlen Loring > > wrote: > > Hi, I'm encountering what look like process boundaries in image > data volume rendering. This is view dependent, only certain camera > locations reveal the issue. In examples below these are > "horizontal line" like artifacts. This data is large, and I have > not been able to successfully volume render after tetrahedralizing > it. I'm not sure if it's just insanely slow or there's a deadlock. > My attempts have been up to 1024 procs with 8 per node (8 GB per > proc), That's about the smallest I can to get enough ram to do the > terahedralization, about 50% of the ram is used after the > tetrahedralization. Does anyone know if the fixed point vr > algorithm is parallel aware, would adding ghost zones to the image > data help?? > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > -- > /| Aashish Chaudhary > | Technical Leader > | Kitware Inc. > / > /| http://www.kitware.com/company/team/chaudhary.html/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdaqui at simscale.de Thu Oct 23 09:26:58 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Thu, 23 Oct 2014 15:26:58 +0200 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader Message-ID: <54490222.9000809@simscale.de> Hello all, I am attempting to write some code in c++ which uses the vtkPVDReader from the paraview library to read a series of vtm files. However I am encountering some problems and I am not sure whether there is something I am missing or whether this could be a bug. I am trying to use the reader in the following manner: My Code: vtkSmartPointer pReader = vtkPVDReader::New(); pReader->SetForceOutputTypeToMultiBlock(1); pReader->SetFileName("/some/fileName.pvd"); pReader->Update(); vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); Error: The error occurs at Update() with the following result: ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default /vtkXMLCollectionReader.cxx, line 316 vtkPVDReader (0x224d9e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. Segmentation fault Possible error Source The code concerning line 316 from vtkXMLCollectionReader.cxx is: // Use the instantiator to create the reader. vtkObject* o = vtkPVInstantiator::CreateInstance(rname); vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); this->Internal->Readers[index] = reader; if(reader) { reader->Delete(); } else { // The class was not registered with the instantiator. vtkErrorMacro("Error creating \"" << rname << "\" using vtkPVInstantiator."); if(o) { o->Delete(); } } } I have isolated the following lines and tested them independently: vtkObject* o = vtkPVInstantiator::CreateInstance(rname); vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); The pointer "vtkObject* o" is NULL regardless of the class name I pass to instantiate, and I can imagine something like that happening in the library, too and causing the segmentation fault, when calling a SafeDownCast(o) (which is NULL). Any suggestions on how to deal with this problem or if you would be so kind to point me to an example for an alternative solution (Could be vtkFileSeriesReader, but this fails, as well in my case) would be appreciated. Kind Regards, Bogdan P.S.: Using the PVDReader from python code works flawlessly, which is also quite confusing, as to why it would fail in the C++ code. -- Bogdan Daqui Software Development SimScale GmbH Lichtenbergstra?e 8 85748 Garching bei M?nchen Phone: +49 (0)89 3398 4078 Email: bdaqui at simscale.de Amtsgericht M?nchen, HRB 201813 Gesch?ftsf?hrer: Vincenz D?lle & David Heiny http://www.simscale.de From sebastien.jourdain at kitware.com Thu Oct 23 10:47:45 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Oct 2014 08:47:45 -0600 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <54490222.9000809@simscale.de> References: <54490222.9000809@simscale.de> Message-ID: Hi Bogdan, here are some issue in your code: vtkSmartPointer pReader = vtkPVDReader::New(); // <== Memory LEAK // Should be either // vtkNew pReader; // vtkSmartPointer pReader = vtkSmartPointer::New() Then here on a "NULL" object you try to call a method. vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet:: SafeDownCast(pReader->GetOutputDataObject(0))); Should be something like that: vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader-> GetOutputDataObject(0))); Then you might have some other issue where pReader output being empty/null, but for that I don't know. Are you managing your project with CMake? Did you include the necessary file with the proper dependency declaration. This seems to be related to the factory not being properly initialized. You can search the mailing list, Marcus did answer several questions about that. Seb On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera wrote: > Hello all, > > I am attempting to write some code in c++ which uses the vtkPVDReader from > the paraview library to read a series of vtm files. However I am > encountering some > problems and I am not sure whether there is something I am missing or > whether this could be a bug. > > I am trying to use the reader in the following manner: > My Code: > vtkSmartPointer pReader = vtkPVDReader::New(); > pReader->SetForceOutputTypeToMultiBlock(1); > pReader->SetFileName("/some/fileName.pvd"); > pReader->Update(); > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > Error: > The error occurs at Update() with the following result: > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > /vtkXMLCollectionReader.cxx, line 316 > vtkPVDReader (0x224d9e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > Segmentation fault > > Possible error Source > The code concerning line 316 from vtkXMLCollectionReader.cxx is: > > // Use the instantiator to create the reader. > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > this->Internal->Readers[index] = reader; > if(reader) > { > reader->Delete(); > } > else > { > // The class was not registered with the instantiator. > vtkErrorMacro("Error creating \"" << rname > << "\" using vtkPVInstantiator."); > if(o) > { > o->Delete(); > } > } > } > > I have isolated the following lines and tested them independently: > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > The pointer "vtkObject* o" is NULL regardless of the class name I pass to > instantiate, and I can imagine something like that happening in the > library, too and > causing the segmentation fault, when calling a SafeDownCast(o) (which is > NULL). > > > Any suggestions on how to deal with this problem or if you would be so > kind to point me to an example for an alternative solution (Could be > vtkFileSeriesReader, > but this fails, as well in my case) would be appreciated. > > Kind Regards, > Bogdan > > P.S.: Using the PVDReader from python code works flawlessly, which is also > quite confusing, as to why it would fail in the C++ code. > > -- > Bogdan Daqui > Software Development > > SimScale GmbH > Lichtenbergstra?e 8 > 85748 Garching bei M?nchen > > Phone: +49 (0)89 3398 4078 > Email: bdaqui at simscale.de > > Amtsgericht M?nchen, HRB 201813 > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > http://www.simscale.de > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berk.geveci at kitware.com Thu Oct 23 11:05:42 2014 From: berk.geveci at kitware.com (Berk Geveci) Date: Thu, 23 Oct 2014 11:05:42 -0400 Subject: [Paraview] Feature request - Need more detailed control of generating nodal quantities from element results In-Reply-To: <6652ad5b31d448968120dde0977cff7e@ES05AMSNLNT.srn.sandia.gov> References: <6652ad5b31d448968120dde0977cff7e@ES05AMSNLNT.srn.sandia.gov> Message-ID: Hi Alan, You are correct (although (1) is somewhat unclear - are we talking about Exodus files that have different element sets here?). I would also recommend this document: http://www.vtk.org/Wiki/images/7/78/VTK-Quadrature-Point-Design-Doc.pdf which explains the current integration (gauss) point support. It doesn't do what he wants but it's worth a read. Best, -berk On Wed, Oct 22, 2014 at 7:44 PM, Scott, W Alan wrote: > A question from a user. I believe that answer is correct to the first > bullet, and the answer is no to the second bullet? > > > 1 - Averaging a nodal result from surrounding elements is OK as long as > the node is within a homogenous body. This process is not correct for > nodes on the boundary between two different materials. > 2 - Is there a process to extrapolate element integration point quantities > (stresses, strains) to nodes for elements with non-linear shape functions? > > > Thanks, > > Alan > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.wittenburg at kitware.com Thu Oct 23 11:26:59 2014 From: scott.wittenburg at kitware.com (Scott Wittenburg) Date: Thu, 23 Oct 2014 09:26:59 -0600 Subject: [Paraview] ScalarOpacityFunction property not set when saving python state Message-ID: Hi all, Has anyone else noticed this recently? At the bottom of this email is an example of some state I just saved, which seems to be missing the following line: magnitudeDisplay.ScalarOpactiyFunction = splatterValuesPWF If this is a bug, I can enter a bug report. Cheers, Scott # get color transfer function/color map for 'SplatterValues' splatterValuesLUT = GetColorTransferFunction('SplatterValues') splatterValuesLUT.RGBPoints = [0.0, 0.0, 0.0, 1.0, 1211.3642578125, 0.0, 0.12549019607843137, 1.0, 1338.4827880859375, 0.00392156862745098, 1.0, 0.0, 1450.6461181640625, 1.0, 0.1568627450980392, 0.0, 2205.8794212053426, 1.0, 0.0, 0.0] splatterValuesLUT.ColorSpace = 'HSV' splatterValuesLUT.NanColor = [0.498039, 0.498039, 0.498039] splatterValuesLUT.ScalarRangeInitialized = 1.0 # get opacity transfer function/opacity map for 'SplatterValues' splatterValuesPWF = GetOpacityTransferFunction('SplatterValues') splatterValuesPWF.Points = [0.0, 0.0, 0.5, 0.0, 0.0, 0.0, 0.5, 0.0, 1001.99267578125, 0.0, 0.5, 0.0, 1293.617431640625, 1.0, 0.5, 0.0, 1674.9727783203125, 0.0, 0.5, 0.0, 2205.87939453125, 0.0, 0.5, 0.0] splatterValuesPWF.ScalarRangeInitialized = 1 # ---------------------------------------------------------------- # setup the visualization in view 'renderView1' # ---------------------------------------------------------------- # show data from magnitude magnitudeDisplay = Show(magnitude, renderView1) # trace defaults for the display properties. magnitudeDisplay.Representation = 'Volume' magnitudeDisplay.ColorArrayName = ['POINTS', 'SplatterValues'] magnitudeDisplay.LookupTable = splatterValuesLUT magnitudeDisplay.ScalarOpacityUnitDistance = 0.8868099940416558 magnitudeDisplay.Slice = 127 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdaqui at simscale.de Thu Oct 23 12:36:57 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Thu, 23 Oct 2014 18:36:57 +0200 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: References: <54490222.9000809@simscale.de> Message-ID: <54492EA9.9020507@simscale.de> Hi Seb, Thanks for the quick reply. Yes the project is managed with CMake. I have not however been able to find the relevant posts by Marcus (in the users list). Is that in the users or developers mailing list? It does sound like it could be a problem with some initialization, as you can see below. One short update, it looks like setting ForceMultiBlockDataSet Output with: pReader->SetForceOutputTypeToMultiBlock(1); leads to the segmentation fault at Update() (The deepcopy is never reached). With or without setting the previous line, the error vtkPVDReader (0x1cb49e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. The code looks like this now: vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < vtkPVDReader >::New(); pReader->SetFileName("/some/file.pvd"); pReader->Update(); (where the error is triggered) Kind Regards, Bogdan On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: > Hi Bogdan, > > here are some issue in your code: > > vtkSmartPointer pReader = vtkPVDReader::New(); // <== Memory LEAK > // Should be either > // vtkNew pReader; > // vtkSmartPointer pReader = vtkSmartPointer::New() > > Then here on a "NULL" object you try to call a method. > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > Should be something like that: > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > Then you might have some other issue where pReader output being empty/null, but for that I don't know. > > Are you managing your project with CMake? Did you include the necessary file with the proper dependency declaration. This seems to be related to the factory not > being properly initialized. You can search the mailing list, Marcus did answer several questions about that. > > Seb > > > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera > wrote: > > Hello all, > > I am attempting to write some code in c++ which uses the vtkPVDReader from the paraview library to read a series of vtm files. However I am encountering some > problems and I am not sure whether there is something I am missing or whether this could be a bug. > > I am trying to use the reader in the following manner: > My Code: > vtkSmartPointer pReader = vtkPVDReader::New(); > pReader->SetForceOutputTypeToMultiBlock(1); > pReader->SetFileName("/some/fileName.pvd"); > pReader->Update(); > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > Error: > The error occurs at Update() with the following result: > ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > /vtkXMLCollectionReader.cxx, line 316 > vtkPVDReader (0x224d9e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > Segmentation fault > > Possible error Source > The code concerning line 316 from vtkXMLCollectionReader.cxx is: > > // Use the instantiator to create the reader. > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > this->Internal->Readers[index] = reader; > if(reader) > { > reader->Delete(); > } > else > { > // The class was not registered with the instantiator. > vtkErrorMacro("Error creating \"" << rname > << "\" using vtkPVInstantiator."); > if(o) > { > o->Delete(); > } > } > } > > I have isolated the following lines and tested them independently: > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > The pointer "vtkObject* o" is NULL regardless of the class name I pass to instantiate, and I can imagine something like that happening in the library, too and > causing the segmentation fault, when calling a SafeDownCast(o) (which is NULL). > > > Any suggestions on how to deal with this problem or if you would be so kind to point me to an example for an alternative solution (Could be vtkFileSeriesReader, > but this fails, as well in my case) would be appreciated. > > Kind Regards, > Bogdan > > P.S.: Using the PVDReader from python code works flawlessly, which is also quite confusing, as to why it would fail in the C++ code. > > -- > Bogdan Daqui > Software Development > > SimScale GmbH > Lichtenbergstra?e 8 > 85748 Garching bei M?nchen > > Phone: +49 (0)89 3398 4078 > Email: bdaqui at simscale.de > > Amtsgericht M?nchen, HRB 201813 > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > http://www.simscale.de > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > From wascott at sandia.gov Thu Oct 23 12:55:36 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 23 Oct 2014 16:55:36 +0000 Subject: [Paraview] [EXTERNAL] Re: Feature request - Need more detailed control of generating nodal quantities from element results In-Reply-To: References: <6652ad5b31d448968120dde0977cff7e@ES05AMSNLNT.srn.sandia.gov> Message-ID: Thanks Berk! Alan From: Berk Geveci [mailto:berk.geveci at kitware.com] Sent: Thursday, October 23, 2014 9:06 AM To: Scott, W Alan Cc: paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] Feature request - Need more detailed control of generating nodal quantities from element results Hi Alan, You are correct (although (1) is somewhat unclear - are we talking about Exodus files that have different element sets here?). I would also recommend this document: http://www.vtk.org/Wiki/images/7/78/VTK-Quadrature-Point-Design-Doc.pdf which explains the current integration (gauss) point support. It doesn't do what he wants but it's worth a read. Best, -berk On Wed, Oct 22, 2014 at 7:44 PM, Scott, W Alan > wrote: A question from a user. I believe that answer is correct to the first bullet, and the answer is no to the second bullet? 1 - Averaging a nodal result from surrounding elements is OK as long as the node is within a homogenous body. This process is not correct for nodes on the boundary between two different materials. 2 - Is there a process to extrapolate element integration point quantities (stresses, strains) to nodes for elements with non-linear shape functions? Thanks, Alan _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From sebastien.jourdain at kitware.com Thu Oct 23 13:51:40 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Oct 2014 11:51:40 -0600 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <54492EA9.9020507@simscale.de> References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> Message-ID: If you provide the stack trace, that may be helpful. Seb On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera wrote: > Hi Seb, > > Thanks for the quick reply. Yes the project is managed with CMake. I have > not however been able to find the relevant posts by Marcus (in the users > list). Is > that in the users or developers mailing list? > > It does sound like it could be a problem with some initialization, as you > can see below. > > One short update, it looks like setting ForceMultiBlockDataSet Output with: > pReader->SetForceOutputTypeToMultiBlock(1); > leads to the segmentation fault at Update() (The deepcopy is never > reached). With or without setting the previous line, the error > vtkPVDReader (0x1cb49e0): Error creating "vtkXMLMultiBlockDataReader" > using vtkPVInstantiator. > > The code looks like this now: > vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < > vtkPVDReader >::New(); > pReader->SetFileName("/some/file.pvd"); > pReader->Update(); (where the error is triggered) > > Kind Regards, > Bogdan > > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: > > Hi Bogdan, > > > > here are some issue in your code: > > > > vtkSmartPointer pReader = vtkPVDReader::New(); // <== > Memory LEAK > > // Should be either > > // vtkNew pReader; > > // vtkSmartPointer pReader = > vtkSmartPointer::New() > > > > Then here on a "NULL" object you try to call a method. > > > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Should be something like that: > > > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; > > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Then you might have some other issue where pReader output being > empty/null, but for that I don't know. > > > > Are you managing your project with CMake? Did you include the necessary > file with the proper dependency declaration. This seems to be related to > the factory not > > being properly initialized. You can search the mailing list, Marcus did > answer several questions about that. > > > > Seb > > > > > > > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera < > bdaqui at simscale.de > wrote: > > > > Hello all, > > > > I am attempting to write some code in c++ which uses the > vtkPVDReader from the paraview library to read a series of vtm files. > However I am encountering some > > problems and I am not sure whether there is something I am missing > or whether this could be a bug. > > > > I am trying to use the reader in the following manner: > > My Code: > > vtkSmartPointer pReader = vtkPVDReader::New(); > > pReader->SetForceOutputTypeToMultiBlock(1); > > pReader->SetFileName("/some/fileName.pvd"); > > pReader->Update(); > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Error: > > The error occurs at Update() with the following result: > > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > > /vtkXMLCollectionReader.cxx, line 316 > > vtkPVDReader (0x224d9e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > Segmentation fault > > > > Possible error Source > > The code concerning line 316 from vtkXMLCollectionReader.cxx is: > > > > // Use the instantiator to create the reader. > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > this->Internal->Readers[index] = reader; > > if(reader) > > { > > reader->Delete(); > > } > > else > > { > > // The class was not registered with the instantiator. > > vtkErrorMacro("Error creating \"" << rname > > << "\" using vtkPVInstantiator."); > > if(o) > > { > > o->Delete(); > > } > > } > > } > > > > I have isolated the following lines and tested them independently: > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > > > The pointer "vtkObject* o" is NULL regardless of the class name I > pass to instantiate, and I can imagine something like that happening in the > library, too and > > causing the segmentation fault, when calling a SafeDownCast(o) > (which is NULL). > > > > > > Any suggestions on how to deal with this problem or if you would be > so kind to point me to an example for an alternative solution (Could be > vtkFileSeriesReader, > > but this fails, as well in my case) would be appreciated. > > > > Kind Regards, > > Bogdan > > > > P.S.: Using the PVDReader from python code works flawlessly, which > is also quite confusing, as to why it would fail in the C++ code. > > > > -- > > Bogdan Daqui > > Software Development > > > > SimScale GmbH > > Lichtenbergstra?e 8 > > 85748 Garching bei M?nchen > > > > Phone: +49 (0)89 3398 4078 > > Email: bdaqui at simscale.de > > > > Amtsgericht M?nchen, HRB 201813 > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > > > http://www.simscale.de > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdaqui at simscale.de Thu Oct 23 14:19:57 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Thu, 23 Oct 2014 20:19:57 +0200 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> Message-ID: <544946CD.1080502@simscale.de> Certainly. I should mention, I am using a pre-compiled version of Paraview 4.1 bundled with Salome (Ubuntu package). Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, line 316 vtkPVDReader (0x6559e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () from /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 #1 0x00007ffff68cc128 in vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 #2 0x00007ffff68cd35d in vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 #3 0x00007ffff7b97fd0 in vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #4 0x00007ffff7b93447 in vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #5 0x00007ffff7b91181 in vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #6 0x00007ffff7b95bb1 in vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #7 0x00007ffff7ba8c21 in vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #9 0x00007ffff7ba9765 in vtkStreamingDemandDrivenPipeline::Update(int) () from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, fileName=..., pMultiBlockDataSet=...) at /home/.../someProject/src/testing.cpp:85 Please let me know if you need something additional On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: > If you provide the stack trace, that may be helpful. > > Seb > > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera > wrote: > > Hi Seb, > > Thanks for the quick reply. Yes the project is managed with CMake. I have not however been able to find the relevant posts by Marcus (in the users list). Is > that in the users or developers mailing list? > > It does sound like it could be a problem with some initialization, as you can see below. > > One short update, it looks like setting ForceMultiBlockDataSet Output with: > pReader->SetForceOutputTypeToMultiBlock(1); > leads to the segmentation fault at Update() (The deepcopy is never reached). With or without setting the previous line, the error > vtkPVDReader (0x1cb49e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > The code looks like this now: > vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < vtkPVDReader >::New(); > pReader->SetFileName("/some/file.pvd"); > pReader->Update(); (where the error is triggered) > > Kind Regards, > Bogdan > > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: > > Hi Bogdan, > > > > here are some issue in your code: > > > > vtkSmartPointer pReader = vtkPVDReader::New(); // <== Memory LEAK > > // Should be either > > // vtkNew pReader; > > // vtkSmartPointer pReader = vtkSmartPointer::New() > > > > Then here on a "NULL" object you try to call a method. > > > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Should be something like that: > > > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Then you might have some other issue where pReader output being empty/null, but for that I don't know. > > > > Are you managing your project with CMake? Did you include the necessary file with the proper dependency declaration. This seems to be related to the factory not > > being properly initialized. You can search the mailing list, Marcus did answer several questions about that. > > > > Seb > > > > > > > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera >> wrote: > > > > Hello all, > > > > I am attempting to write some code in c++ which uses the vtkPVDReader from the paraview library to read a series of vtm files. However I am > encountering some > > problems and I am not sure whether there is something I am missing or whether this could be a bug. > > > > I am trying to use the reader in the following manner: > > My Code: > > vtkSmartPointer pReader = vtkPVDReader::New(); > > pReader->SetForceOutputTypeToMultiBlock(1); > > pReader->SetFileName("/some/fileName.pvd"); > > pReader->Update(); > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > Error: > > The error occurs at Update() with the following result: > > ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > > /vtkXMLCollectionReader.cxx, line 316 > > vtkPVDReader (0x224d9e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > Segmentation fault > > > > Possible error Source > > The code concerning line 316 from vtkXMLCollectionReader.cxx is: > > > > // Use the instantiator to create the reader. > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > this->Internal->Readers[index] = reader; > > if(reader) > > { > > reader->Delete(); > > } > > else > > { > > // The class was not registered with the instantiator. > > vtkErrorMacro("Error creating \"" << rname > > << "\" using vtkPVInstantiator."); > > if(o) > > { > > o->Delete(); > > } > > } > > } > > > > I have isolated the following lines and tested them independently: > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > > > The pointer "vtkObject* o" is NULL regardless of the class name I pass to instantiate, and I can imagine something like that happening in the library, > too and > > causing the segmentation fault, when calling a SafeDownCast(o) (which is NULL). > > > > > > Any suggestions on how to deal with this problem or if you would be so kind to point me to an example for an alternative solution (Could be > vtkFileSeriesReader, > > but this fails, as well in my case) would be appreciated. > > > > Kind Regards, > > Bogdan > > > > P.S.: Using the PVDReader from python code works flawlessly, which is also quite confusing, as to why it would fail in the C++ code. > > > > -- > > Bogdan Daqui > > Software Development > > > > SimScale GmbH > > Lichtenbergstra?e 8 > > 85748 Garching bei M?nchen > > > > Phone: +49 (0)89 3398 4078 > > Email: bdaqui at simscale.de > > > > > Amtsgericht M?nchen, HRB 201813 > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > > > http://www.simscale.de > > _______________________________________________ > > Powered by www.kitware.com > > > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > > > Follow this link to subscribe/unsubscribe: > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > From simon.m.su.ctr at mail.mil Thu Oct 23 14:23:14 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 23 Oct 2014 18:23:14 +0000 Subject: [Paraview] loading multiple pvd files - create an xml vtp file that will load all the vtp files Message-ID: Hello, Please see below for a list of file that I write to vtp format in parallel. So the number of files I get is dependent on how many processes I used to write the data out. When loading the pieces, Material-volume-fraction---1_Merged_000.vtp ..... Material-volume-fraction---1_Merged_030.vtp ParaView loader is intelligent enough to group the files into 1 file group that I can click to load them. However, in some cases the file grouping are not available to me and I end up having to click on all the files pieces to load the whole visualization piece that I am interested in. From the Material-volume-fraction---1_Merged_000.vtp xml format, I can see that it is loading all the pieces in files Material-volume-fraction---1_Merged_000_0.vtp .. Material-volume-fraction---1_Merged_000_3.vtp how can I write a Material-volume-fraction---1_Merged.vtp file that has all the pieces spread out in the files Material-volume-fraction---1_Merged_000.vtp ..... Material-volume-fraction---1_Merged_030.vtp ? Are there utility that I can use to generate the vtp xml file? or I have to code it up by hand? Any help is much appreciated thanks -simon ==================================================================================== -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_000.vtp -rw------- 1 simonsm users 2387349 May 23 13:18 Material-volume-fraction---1_Merged_000_0.vtp -rw------- 1 simonsm users 1778725 May 23 13:18 Material-volume-fraction---1_Merged_000_1.vtp -rw------- 1 simonsm users 2805 May 23 13:18 Material-volume-fraction---1_Merged_000_2.vtp -rw------- 1 simonsm users 2805 May 23 13:18 Material-volume-fraction---1_Merged_000_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_001.vtp -rw------- 1 simonsm users 276919 May 23 13:18 Material-volume-fraction---1_Merged_001_0.vtp -rw------- 1 simonsm users 255538 May 23 13:18 Material-volume-fraction---1_Merged_001_1.vtp -rw------- 1 simonsm users 283476 May 23 13:18 Material-volume-fraction---1_Merged_001_2.vtp -rw------- 1 simonsm users 248965 May 23 13:18 Material-volume-fraction---1_Merged_001_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_002.vtp -rw------- 1 simonsm users 294932 May 23 13:18 Material-volume-fraction---1_Merged_002_0.vtp -rw------- 1 simonsm users 236913 May 23 13:18 Material-volume-fraction---1_Merged_002_1.vtp -rw------- 1 simonsm users 286037 May 23 13:18 Material-volume-fraction---1_Merged_002_2.vtp -rw------- 1 simonsm users 246192 May 23 13:18 Material-volume-fraction---1_Merged_002_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_003.vtp -rw------- 1 simonsm users 308410 May 23 13:18 Material-volume-fraction---1_Merged_003_0.vtp -rw------- 1 simonsm users 224929 May 23 13:18 Material-volume-fraction---1_Merged_003_1.vtp -rw------- 1 simonsm users 311348 May 23 13:18 Material-volume-fraction---1_Merged_003_2.vtp -rw------- 1 simonsm users 222535 May 23 13:18 Material-volume-fraction---1_Merged_003_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_004.vtp -rw------- 1 simonsm users 316539 May 23 13:18 Material-volume-fraction---1_Merged_004_0.vtp -rw------- 1 simonsm users 218368 May 23 13:18 Material-volume-fraction---1_Merged_004_1.vtp -rw------- 1 simonsm users 319790 May 23 13:18 Material-volume-fraction---1_Merged_004_2.vtp -rw------- 1 simonsm users 215373 May 23 13:18 Material-volume-fraction---1_Merged_004_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_005.vtp -rw------- 1 simonsm users 317601 May 23 13:18 Material-volume-fraction---1_Merged_005_0.vtp -rw------- 1 simonsm users 207750 May 23 13:18 Material-volume-fraction---1_Merged_005_1.vtp -rw------- 1 simonsm users 305459 May 23 13:18 Material-volume-fraction---1_Merged_005_2.vtp -rw------- 1 simonsm users 219908 May 23 13:18 Material-volume-fraction---1_Merged_005_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_006.vtp -rw------- 1 simonsm users 328800 May 23 13:18 Material-volume-fraction---1_Merged_006_0.vtp -rw------- 1 simonsm users 215271 May 23 13:18 Material-volume-fraction---1_Merged_006_1.vtp -rw------- 1 simonsm users 323746 May 23 13:18 Material-volume-fraction---1_Merged_006_2.vtp -rw------- 1 simonsm users 220650 May 23 13:18 Material-volume-fraction---1_Merged_006_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_007.vtp -rw------- 1 simonsm users 352780 May 23 13:18 Material-volume-fraction---1_Merged_007_0.vtp -rw------- 1 simonsm users 224689 May 23 13:18 Material-volume-fraction---1_Merged_007_1.vtp -rw------- 1 simonsm users 353205 May 23 13:18 Material-volume-fraction---1_Merged_007_2.vtp -rw------- 1 simonsm users 225473 May 23 13:18 Material-volume-fraction---1_Merged_007_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_008.vtp -rw------- 1 simonsm users 411938 May 23 13:18 Material-volume-fraction---1_Merged_008_0.vtp -rw------- 1 simonsm users 252460 May 23 13:18 Material-volume-fraction---1_Merged_008_1.vtp -rw------- 1 simonsm users 354602 May 23 13:18 Material-volume-fraction---1_Merged_008_2.vtp -rw------- 1 simonsm users 247965 May 23 13:18 Material-volume-fraction---1_Merged_008_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_009.vtp -rw------- 1 simonsm users 474651 May 23 13:18 Material-volume-fraction---1_Merged_009_0.vtp -rw------- 1 simonsm users 261574 May 23 13:18 Material-volume-fraction---1_Merged_009_1.vtp -rw------- 1 simonsm users 490329 May 23 13:18 Material-volume-fraction---1_Merged_009_2.vtp -rw------- 1 simonsm users 186282 May 23 13:18 Material-volume-fraction---1_Merged_009_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_010.vtp -rw------- 1 simonsm users 535644 May 23 13:18 Material-volume-fraction---1_Merged_010_0.vtp -rw------- 1 simonsm users 283020 May 23 13:18 Material-volume-fraction---1_Merged_010_1.vtp -rw------- 1 simonsm users 538664 May 23 13:18 Material-volume-fraction---1_Merged_010_2.vtp -rw------- 1 simonsm users 205897 May 23 13:18 Material-volume-fraction---1_Merged_010_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_011.vtp -rw------- 1 simonsm users 561044 May 23 13:18 Material-volume-fraction---1_Merged_011_0.vtp -rw------- 1 simonsm users 312516 May 23 13:18 Material-volume-fraction---1_Merged_011_1.vtp -rw------- 1 simonsm users 563540 May 23 13:18 Material-volume-fraction---1_Merged_011_2.vtp -rw------- 1 simonsm users 310835 May 23 13:18 Material-volume-fraction---1_Merged_011_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_012.vtp -rw------- 1 simonsm users 627747 May 23 13:18 Material-volume-fraction---1_Merged_012_0.vtp -rw------- 1 simonsm users 341561 May 23 13:18 Material-volume-fraction---1_Merged_012_1.vtp -rw------- 1 simonsm users 626824 May 23 13:18 Material-volume-fraction---1_Merged_012_2.vtp -rw------- 1 simonsm users 340930 May 23 13:18 Material-volume-fraction---1_Merged_012_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_013.vtp -rw------- 1 simonsm users 690196 May 23 13:18 Material-volume-fraction---1_Merged_013_0.vtp -rw------- 1 simonsm users 383751 May 23 13:18 Material-volume-fraction---1_Merged_013_1.vtp -rw------- 1 simonsm users 682791 May 23 13:18 Material-volume-fraction---1_Merged_013_2.vtp -rw------- 1 simonsm users 374141 May 23 13:18 Material-volume-fraction---1_Merged_013_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_014.vtp -rw------- 1 simonsm users 771537 May 23 13:18 Material-volume-fraction---1_Merged_014_0.vtp -rw------- 1 simonsm users 395242 May 23 13:18 Material-volume-fraction---1_Merged_014_1.vtp -rw------- 1 simonsm users 631732 May 23 13:18 Material-volume-fraction---1_Merged_014_2.vtp -rw------- 1 simonsm users 496985 May 23 13:18 Material-volume-fraction---1_Merged_014_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_015.vtp -rw------- 1 simonsm users 851331 May 23 13:18 Material-volume-fraction---1_Merged_015_0.vtp -rw------- 1 simonsm users 421645 May 23 13:18 Material-volume-fraction---1_Merged_015_1.vtp -rw------- 1 simonsm users 644639 May 23 13:18 Material-volume-fraction---1_Merged_015_2.vtp -rw------- 1 simonsm users 572823 May 23 13:18 Material-volume-fraction---1_Merged_015_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_016.vtp -rw------- 1 simonsm users 844784 May 23 13:18 Material-volume-fraction---1_Merged_016_0.vtp -rw------- 1 simonsm users 501078 May 23 13:18 Material-volume-fraction---1_Merged_016_1.vtp -rw------- 1 simonsm users 793161 May 23 13:18 Material-volume-fraction---1_Merged_016_2.vtp -rw------- 1 simonsm users 512324 May 23 13:18 Material-volume-fraction---1_Merged_016_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_017.vtp -rw------- 1 simonsm users 919813 May 23 13:18 Material-volume-fraction---1_Merged_017_0.vtp -rw------- 1 simonsm users 522214 May 23 13:18 Material-volume-fraction---1_Merged_017_1.vtp -rw------- 1 simonsm users 841893 May 23 13:18 Material-volume-fraction---1_Merged_017_2.vtp -rw------- 1 simonsm users 543854 May 23 13:18 Material-volume-fraction---1_Merged_017_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_018.vtp -rw------- 1 simonsm users 935025 May 23 13:18 Material-volume-fraction---1_Merged_018_0.vtp -rw------- 1 simonsm users 558037 May 23 13:18 Material-volume-fraction---1_Merged_018_1.vtp -rw------- 1 simonsm users 891893 May 23 13:18 Material-volume-fraction---1_Merged_018_2.vtp -rw------- 1 simonsm users 593873 May 23 13:18 Material-volume-fraction---1_Merged_018_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_019.vtp -rw------- 1 simonsm users 1032963 May 23 13:18 Material-volume-fraction---1_Merged_019_0.vtp -rw------- 1 simonsm users 533044 May 23 13:18 Material-volume-fraction---1_Merged_019_1.vtp -rw------- 1 simonsm users 1022794 May 23 13:18 Material-volume-fraction---1_Merged_019_2.vtp -rw------- 1 simonsm users 574583 May 23 13:18 Material-volume-fraction---1_Merged_019_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_020.vtp -rw------- 1 simonsm users 1076039 May 23 13:18 Material-volume-fraction---1_Merged_020_0.vtp -rw------- 1 simonsm users 549074 May 23 13:18 Material-volume-fraction---1_Merged_020_1.vtp -rw------- 1 simonsm users 987766 May 23 13:18 Material-volume-fraction---1_Merged_020_2.vtp -rw------- 1 simonsm users 718499 May 23 13:18 Material-volume-fraction---1_Merged_020_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_021.vtp -rw------- 1 simonsm users 1170888 May 23 13:18 Material-volume-fraction---1_Merged_021_0.vtp -rw------- 1 simonsm users 576954 May 23 13:18 Material-volume-fraction---1_Merged_021_1.vtp -rw------- 1 simonsm users 1167430 May 23 13:18 Material-volume-fraction---1_Merged_021_2.vtp -rw------- 1 simonsm users 576311 May 23 13:18 Material-volume-fraction---1_Merged_021_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_022.vtp -rw------- 1 simonsm users 1220152 May 23 13:18 Material-volume-fraction---1_Merged_022_0.vtp -rw------- 1 simonsm users 599996 May 23 13:18 Material-volume-fraction---1_Merged_022_1.vtp -rw------- 1 simonsm users 1217851 May 23 13:18 Material-volume-fraction---1_Merged_022_2.vtp -rw------- 1 simonsm users 602726 May 23 13:18 Material-volume-fraction---1_Merged_022_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_023.vtp -rw------- 1 simonsm users 1273128 May 23 13:18 Material-volume-fraction---1_Merged_023_0.vtp -rw------- 1 simonsm users 621312 May 23 13:18 Material-volume-fraction---1_Merged_023_1.vtp -rw------- 1 simonsm users 1243798 May 23 13:18 Material-volume-fraction---1_Merged_023_2.vtp -rw------- 1 simonsm users 652838 May 23 13:18 Material-volume-fraction---1_Merged_023_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_024.vtp -rw------- 1 simonsm users 1170259 May 23 13:18 Material-volume-fraction---1_Merged_024_0.vtp -rw------- 1 simonsm users 641654 May 23 13:18 Material-volume-fraction---1_Merged_024_1.vtp -rw------- 1 simonsm users 1396175 May 23 13:18 Material-volume-fraction---1_Merged_024_2.vtp -rw------- 1 simonsm users 728459 May 23 13:18 Material-volume-fraction---1_Merged_024_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_025.vtp -rw------- 1 simonsm users 1203867 May 23 13:18 Material-volume-fraction---1_Merged_025_0.vtp -rw------- 1 simonsm users 663060 May 23 13:18 Material-volume-fraction---1_Merged_025_1.vtp -rw------- 1 simonsm users 1445490 May 23 13:18 Material-volume-fraction---1_Merged_025_2.vtp -rw------- 1 simonsm users 744663 May 23 13:18 Material-volume-fraction---1_Merged_025_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_026.vtp -rw------- 1 simonsm users 1400281 May 23 13:18 Material-volume-fraction---1_Merged_026_0.vtp -rw------- 1 simonsm users 678254 May 23 13:18 Material-volume-fraction---1_Merged_026_1.vtp -rw------- 1 simonsm users 1318587 May 23 13:18 Material-volume-fraction---1_Merged_026_2.vtp -rw------- 1 simonsm users 774407 May 23 13:18 Material-volume-fraction---1_Merged_026_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_027.vtp -rw------- 1 simonsm users 1452928 May 23 13:18 Material-volume-fraction---1_Merged_027_0.vtp -rw------- 1 simonsm users 691845 May 23 13:18 Material-volume-fraction---1_Merged_027_1.vtp -rw------- 1 simonsm users 1372582 May 23 13:18 Material-volume-fraction---1_Merged_027_2.vtp -rw------- 1 simonsm users 774480 May 23 13:18 Material-volume-fraction---1_Merged_027_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_028.vtp -rw------- 1 simonsm users 1371912 May 23 13:18 Material-volume-fraction---1_Merged_028_0.vtp -rw------- 1 simonsm users 707038 May 23 13:18 Material-volume-fraction---1_Merged_028_1.vtp -rw------- 1 simonsm users 1375771 May 23 13:18 Material-volume-fraction---1_Merged_028_2.vtp -rw------- 1 simonsm users 943017 May 23 13:18 Material-volume-fraction---1_Merged_028_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_029.vtp -rw------- 1 simonsm users 1423992 May 23 13:18 Material-volume-fraction---1_Merged_029_0.vtp -rw------- 1 simonsm users 718310 May 23 13:18 Material-volume-fraction---1_Merged_029_1.vtp -rw------- 1 simonsm users 1530159 May 23 13:18 Material-volume-fraction---1_Merged_029_2.vtp -rw------- 1 simonsm users 808720 May 23 13:18 Material-volume-fraction---1_Merged_029_3.vtp -rw------- 1 simonsm users 1194 May 23 13:18 Material-volume-fraction---1_Merged_030.vtp -rw------- 1 simonsm users 1465504 May 23 13:18 Material-volume-fraction---1_Merged_030_0.vtp -rw------- 1 simonsm users 725670 May 23 13:18 Material-volume-fraction---1_Merged_030_1.vtp -rw------- 1 simonsm users 1577352 May 23 13:18 Material-volume-fraction---1_Merged_030_2.vtp -rw------- 1 simonsm users 816794 May 23 13:18 Material-volume-fraction---1_Merged_030_3.vtp -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Thu Oct 23 14:32:46 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 23 Oct 2014 18:32:46 +0000 Subject: [Paraview] accessing parallel xdmf3 writer Message-ID: Hello, I used the python script below to convert pvd format into xmf file with xdmf3 enable ParaView that I compiled. The writer is working if I run it in serial (pvbatch pvd_to_xmf.py pvd/mvf2.pvd) . How do I access to xmf parallel writer? I am getting the following error vtkSMWriterFactory (0x66c5d0): No matching writer found for extension: xmf if I run the script with aprun -n 12 pvbatch pvd_to_xmf.py pvd/mvf2.pvd thank you in advanced for your help. thanks -simon ================ pvbatch pvd_to_xmf.py ========== #### import the simple module from the paraview import sys try: paraview.simple except: from paraview.simple import * #### get the filename from command line fileName = str(sys.argv[1]) print "Reading " + fileName #### reading pvd file mvfpvd = PVDReader(FileName=fileName) #### create output file name (prefix, sep, suffix) = fileName.rpartition('.') ofileName = prefix + '.xmf' print "Writing xmf output file to " + ofileName #### create output file SaveData(ofileName, proxy=mvfpvd, WriteAllTimeSteps=1) -------------- next part -------------- An HTML attachment was scrubbed... URL: From simon.m.su.ctr at mail.mil Thu Oct 23 16:06:46 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Thu, 23 Oct 2014 20:06:46 +0000 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: Message-ID: Classification: UNCLASSIFIED Caveats: NONE Utkarsh, I have been thinking and just want to check with you on this. If pvbatch sample.py is running, will that also test the ParaView binary we produced has a working python within the ParaView? What about checking and see if numpy is available for the ParaView binary produced? I even tried to turn off the numpy library (in the superbuild compile using the cmake flag -DENABLE_numpy=OFF) but the compilation process compiled numpy nevertheless. Do I have to include statement like import numpy to test if numpy or other python packages were properly compiled and available within ParaView? Thanks -simon -----Original Message----- From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] Sent: Tuesday, October 14, 2014 3:22 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] pvserver test on different systems (UNCLASSIFIED) Simon, Yup, that'd be a perfect test (attached). You should run it with pvbatch. Utkarsh On Tue, Oct 14, 2014 at 3:03 PM, Su, Simon M CTR USARMY ARL (US) wrote: > Classification: UNCLASSIFIED > Caveats: NONE > > Hello, > > We have several HPC systems that we compile/install different ParaView > releases. We are wondering what would be a good test to verify that > pvserver compiled is actually running on the system. Is there like a > python script that when we run on the new installation, and it worked, > we have a good confidence that the compilation/installation of the > ParaView released is working? Will "a plot of a sphere + the process > id scalar filter + save output to image = beach ball image" a good > verification test? > > Thanks > -simon > > Classification: UNCLASSIFIED > Caveats: NONE > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > Classification: UNCLASSIFIED Caveats: NONE -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5633 bytes Desc: not available URL: From sebastien.jourdain at kitware.com Thu Oct 23 21:37:09 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Thu, 23 Oct 2014 19:37:09 -0600 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <544946CD.1080502@simscale.de> References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> Message-ID: Thanks Bogdan, that's not helping me but someone else might have some idea. Seb On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera wrote: > Certainly. I should mention, I am using a pre-compiled version of Paraview > 4.1 bundled with Salome (Ubuntu package). > > Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, > line 316 > vtkPVDReader (0x6559e0): Error creating "vtkXMLMultiBlockDataReader" using > vtkPVInstantiator. > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () > from > /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 > #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 > #1 0x00007ffff68cc128 in vtkXMLReader::RequestData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 > #2 0x00007ffff68cd35d in vtkXMLReader::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 > #3 0x00007ffff7b97fd0 in vtkExecutive::CallAlgorithm(vtkInformation*, > int, vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #4 0x00007ffff7b93447 in > vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #5 0x00007ffff7b91181 in > vtkCompositeDataPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #6 0x00007ffff7b95bb1 in > vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #7 0x00007ffff7ba8c21 in > vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #9 0x00007ffff7ba9765 in vtkStreamingDemandDrivenPipeline::Update(int) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, > fileName=..., pMultiBlockDataSet=...) > at /home/.../someProject/src/testing.cpp:85 > > > Please let me know if you need something additional > On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: > > If you provide the stack trace, that may be helpful. > > > > Seb > > > > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera < > bdaqui at simscale.de > wrote: > > > > Hi Seb, > > > > Thanks for the quick reply. Yes the project is managed with CMake. I > have not however been able to find the relevant posts by Marcus (in the > users list). Is > > that in the users or developers mailing list? > > > > It does sound like it could be a problem with some initialization, > as you can see below. > > > > One short update, it looks like setting ForceMultiBlockDataSet > Output with: > > pReader->SetForceOutputTypeToMultiBlock(1); > > leads to the segmentation fault at Update() (The deepcopy is never > reached). With or without setting the previous line, the error > > vtkPVDReader (0x1cb49e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > > > The code looks like this now: > > vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < > vtkPVDReader >::New(); > > pReader->SetFileName("/some/file.pvd"); > > pReader->Update(); (where the error is triggered) > > > > Kind Regards, > > Bogdan > > > > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: > > > Hi Bogdan, > > > > > > here are some issue in your code: > > > > > > vtkSmartPointer pReader = vtkPVDReader::New(); // > <== Memory LEAK > > > // Should be either > > > // vtkNew pReader; > > > // vtkSmartPointer pReader = > vtkSmartPointer::New() > > > > > > Then here on a "NULL" object you try to call a method. > > > > > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Should be something like that: > > > > > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; > > > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Then you might have some other issue where pReader output being > empty/null, but for that I don't know. > > > > > > Are you managing your project with CMake? Did you include the > necessary file with the proper dependency declaration. This seems to be > related to the factory not > > > being properly initialized. You can search the mailing list, > Marcus did answer several questions about that. > > > > > > Seb > > > > > > > > > > > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera < > bdaqui at simscale.de > >> wrote: > > > > > > Hello all, > > > > > > I am attempting to write some code in c++ which uses the > vtkPVDReader from the paraview library to read a series of vtm files. > However I am > > encountering some > > > problems and I am not sure whether there is something I am > missing or whether this could be a bug. > > > > > > I am trying to use the reader in the following manner: > > > My Code: > > > vtkSmartPointer pReader = > vtkPVDReader::New(); > > > pReader->SetForceOutputTypeToMultiBlock(1); > > > pReader->SetFileName("/some/fileName.pvd"); > > > pReader->Update(); > > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Error: > > > The error occurs at Update() with the following result: > > > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > > > /vtkXMLCollectionReader.cxx, line 316 > > > vtkPVDReader (0x224d9e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > > Segmentation fault > > > > > > Possible error Source > > > The code concerning line 316 from vtkXMLCollectionReader.cxx > is: > > > > > > // Use the instantiator to create the reader. > > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > > this->Internal->Readers[index] = reader; > > > if(reader) > > > { > > > reader->Delete(); > > > } > > > else > > > { > > > // The class was not registered with the instantiator. > > > vtkErrorMacro("Error creating \"" << rname > > > << "\" using vtkPVInstantiator."); > > > if(o) > > > { > > > o->Delete(); > > > } > > > } > > > } > > > > > > I have isolated the following lines and tested them > independently: > > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); > > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); > > > > > > The pointer "vtkObject* o" is NULL regardless of the class > name I pass to instantiate, and I can imagine something like that happening > in the library, > > too and > > > causing the segmentation fault, when calling a SafeDownCast(o) > (which is NULL). > > > > > > > > > Any suggestions on how to deal with this problem or if you > would be so kind to point me to an example for an alternative solution > (Could be > > vtkFileSeriesReader, > > > but this fails, as well in my case) would be appreciated. > > > > > > Kind Regards, > > > Bogdan > > > > > > P.S.: Using the PVDReader from python code works flawlessly, > which is also quite confusing, as to why it would fail in the C++ code. > > > > > > -- > > > Bogdan Daqui > > > Software Development > > > > > > SimScale GmbH > > > Lichtenbergstra?e 8 > > > 85748 Garching bei M?nchen > > > > > > Phone: +49 (0)89 3398 4078 > > > Email: bdaqui at simscale.de bdaqui at simscale.de > > > > > > > Amtsgericht M?nchen, HRB 201813 > > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > > > > > http://www.simscale.de > > > _______________________________________________ > > > Powered by www.kitware.com < > http://www.kitware.com> > > > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > > > > > Follow this link to subscribe/unsubscribe: > > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Fri Oct 24 12:14:42 2014 From: bloring at lbl.gov (Burlen Loring) Date: Fri, 24 Oct 2014 09:14:42 -0700 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> Message-ID: <544A7AF2.7070603@lbl.gov> Hi Bogdan, You are writing a stand alone C++ app right? Are you setting up to run the composite data pipeline as in the following example? 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); 102 cexec->Delete(); Burlen On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: > Thanks Bogdan, > > that's not helping me but someone else might have some idea. > > Seb > > On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera > > wrote: > > Certainly. I should mention, I am using a pre-compiled version of > Paraview 4.1 bundled with Salome (Ubuntu package). > > Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, > line 316 > vtkPVDReader (0x6559e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () > from > /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 > #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 > #1 0x00007ffff68cc128 in > vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, > vtkInformationVector*) () from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 > #2 0x00007ffff68cd35d in > vtkXMLReader::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 > #3 0x00007ffff7b97fd0 in > vtkExecutive::CallAlgorithm(vtkInformation*, int, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #4 0x00007ffff7b93447 in > vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #5 0x00007ffff7b91181 in > vtkCompositeDataPipeline::ExecuteData(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #6 0x00007ffff7b95bb1 in > vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #7 0x00007ffff7ba8c21 in > vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, > vtkInformationVector**, vtkInformationVector*) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #9 0x00007ffff7ba9765 in > vtkStreamingDemandDrivenPipeline::Update(int) () > from > /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 > #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, > fileName=..., pMultiBlockDataSet=...) > at /home/.../someProject/src/testing.cpp:85 > > > Please let me know if you need something additional > On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: > > If you provide the stack trace, that may be helpful. > > > > Seb > > > > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera > > >> wrote: > > > > Hi Seb, > > > > Thanks for the quick reply. Yes the project is managed with > CMake. I have not however been able to find the relevant posts by > Marcus (in the users list). Is > > that in the users or developers mailing list? > > > > It does sound like it could be a problem with some > initialization, as you can see below. > > > > One short update, it looks like setting > ForceMultiBlockDataSet Output with: > > pReader->SetForceOutputTypeToMultiBlock(1); > > leads to the segmentation fault at Update() (The deepcopy is > never reached). With or without setting the previous line, the error > > vtkPVDReader (0x1cb49e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > > > The code looks like this now: > > vtkSmartPointer < vtkPVDReader > pReader = > vtkSmartPointer < vtkPVDReader >::New(); > > pReader->SetFileName("/some/file.pvd"); > > pReader->Update(); (where the error is triggered) > > > > Kind Regards, > > Bogdan > > > > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: > > > Hi Bogdan, > > > > > > here are some issue in your code: > > > > > > vtkSmartPointer pReader = > vtkPVDReader::New(); // <== Memory LEAK > > > // Should be either > > > // vtkNew pReader; > > > // vtkSmartPointer pReader = > vtkSmartPointer::New() > > > > > > Then here on a "NULL" object you try to call a method. > > > > > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Should be something like that: > > > > > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; > > > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Then you might have some other issue where pReader output > being empty/null, but for that I don't know. > > > > > > Are you managing your project with CMake? Did you include > the necessary file with the proper dependency declaration. This > seems to be related to the factory not > > > being properly initialized. You can search the mailing > list, Marcus did answer several questions about that. > > > > > > Seb > > > > > > > > > > > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera > > > > > > >>> wrote: > > > > > > Hello all, > > > > > > I am attempting to write some code in c++ which uses > the vtkPVDReader from the paraview library to read a series of vtm > files. However I am > > encountering some > > > problems and I am not sure whether there is something > I am missing or whether this could be a bug. > > > > > > I am trying to use the reader in the following manner: > > > My Code: > > > vtkSmartPointer pReader = > vtkPVDReader::New(); > > > pReader->SetForceOutputTypeToMultiBlock(1); > > > pReader->SetFileName("/some/fileName.pvd"); > > > pReader->Update(); > > > vtkMultiBlockDataSet* > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); > > > > > > Error: > > > The error occurs at Update() with the > following result: > > > ERROR: In > /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default > > > /vtkXMLCollectionReader.cxx, line 316 > > > vtkPVDReader (0x224d9e0): Error creating > "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. > > > Segmentation fault > > > > > > Possible error Source > > > The code concerning line 316 from > vtkXMLCollectionReader.cxx is: > > > > > > // Use the instantiator to create the reader. > > > vtkObject* o = > vtkPVInstantiator::CreateInstance(rname); > > > vtkXMLReader* reader = > vtkXMLReader::SafeDownCast(o); > > > this->Internal->Readers[index] = reader; > > > if(reader) > > > { > > > reader->Delete(); > > > } > > > else > > > { > > > // The class was not registered with the > instantiator. > > > vtkErrorMacro("Error creating \"" << rname > > > << "\" using vtkPVInstantiator."); > > > if(o) > > > { > > > o->Delete(); > > > } > > > } > > > } > > > > > > I have isolated the following lines and tested them > independently: > > > vtkObject* o = > vtkPVInstantiator::CreateInstance(rname); > > > vtkXMLReader* reader = > vtkXMLReader::SafeDownCast(o); > > > > > > The pointer "vtkObject* o" is NULL regardless of the > class name I pass to instantiate, and I can imagine something like > that happening in the library, > > too and > > > causing the segmentation fault, when calling a > SafeDownCast(o) (which is NULL). > > > > > > > > > Any suggestions on how to deal with this problem or if > you would be so kind to point me to an example for an alternative > solution (Could be > > vtkFileSeriesReader, > > > but this fails, as well in my case) would be appreciated. > > > > > > Kind Regards, > > > Bogdan > > > > > > P.S.: Using the PVDReader from python code works > flawlessly, which is also quite confusing, as to why it would fail > in the C++ code. > > > > > > -- > > > Bogdan Daqui > > > Software Development > > > > > > SimScale GmbH > > > Lichtenbergstra?e 8 > > > 85748 Garching bei M?nchen > > > > > > Phone: +49 (0)89 3398 4078 > > > Email: bdaqui at simscale.de > > > > >> > > > > > > Amtsgericht M?nchen, HRB 201813 > > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny > > > > > > http://www.simscale.de > > > _______________________________________________ > > > Powered by www.kitware.com > > > > > > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > > > > > Please keep messages on-topic and check the ParaView > Wiki at: http://paraview.org/Wiki/ParaView > > > > > > Follow this link to subscribe/unsubscribe: > > > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From matei.stroila at gmail.com Fri Oct 24 16:20:48 2014 From: matei.stroila at gmail.com (Matei Stroila) Date: Fri, 24 Oct 2014 15:20:48 -0500 Subject: [Paraview] PointSprite_Plugin not displaying textures on ParaView 4.2.0 Mac OSX 10.10 Message-ID: Hi, I believe this is a bug: The PointSprite_Plugin with ParaView 4.2.0 does not display textures (same textures that ParaView 4.1.0 can display on same machine with OS X 10.10. .) The texture seems to be loaded but it is not displayed. I used the release from this link: http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit.dmg Same behavior with ParaView built on the same machine from the ParaView 4.2.0 sources. Thanks, Matei From nortysp at gmail.com Sat Oct 25 04:54:48 2014 From: nortysp at gmail.com (Peter Dvorcak) Date: Sat, 25 Oct 2014 10:54:48 +0200 Subject: [Paraview] [Delaunay 3D] Message-ID: <000901cff031$55c8f210$015ad630$@gmail.com> Hello everyone, I have object like in the picture above, it is created from x,y,z points that are loaded from excel. I need to create a body with rigid surface, I have used Delaunay 3D filter and the result is good but not perfect. The problem is with this white linse and also at some places there are holes in surface. Is there any way how to make this surface smoother ?? I have tried to change Delaunay parameters but this is the best I was able to obtain. Do you have any suggestions how to make it better ? S pozdravom/Best regards Peter Dvor??k -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11243 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 99610 bytes Desc: not available URL: From bwvb at xs4all.nl Sat Oct 25 13:33:44 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Sat, 25 Oct 2014 19:33:44 +0200 Subject: [Paraview] pipeline?? Message-ID: <544BDEF8.8000104@xs4all.nl> Hello, How can I accomplish the following? I have created a number of source objects (some are read from file, e.g. an stl file), some are from other Sources. On each of these segments in the pipeline browser I can apply a filter that I have written, by selecting it and applying my filter. Works ok. But how can I apply this filter to all of them in one go? Initially, I thought that applying the filter to the last element in the pipeline would be enough, it is a pipeline after all, but that is not the case. Do i need to specify somehow in my ::DataRequest method that it needs to get its input from all segemnts in the pipe? But how does that work? This is what I have in this routine now: // Get the input data object vtkPolyData* input = vtkPolyData::GetData( inputVector[0] ); assert( input ); Kind Regards, Bertwim From gda at tacc.utexas.edu Sun Oct 26 11:12:08 2014 From: gda at tacc.utexas.edu (Greg Abram) Date: Sun, 26 Oct 2014 15:12:08 +0000 Subject: [Paraview] Lights Message-ID: Can anyone tell me where the **** to set the lighting directions etc. in PV 4.2? Gregory D. Abram, Ph.D. Research Engineering/Scientist Associate Texas Advanced Computing Center The University of Texas at Austin (512) 471-8196 gda at tacc.utexas.edu [TACC Website] Connect With TACC -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:33:01 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:33:01 +0800 Subject: [Paraview] CFP: CGMIP2014 Conference in Malaysia Message-ID: *http://sdiwc.net/conferences/2014/cgmip2014/ * The International Conference on Computer Graphics, Multimedia and Image Processing (CGMIP2014) November 17-19, 2014 Asia Pacific University of Technology and Innovation (APU) Kuala Lumpur, Malaysia All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: - 3D imaging - Case studies - Case studies and emerging technologies - Classification and clustering techniques - Color and texture - Compression methods - Computational geometry - Computer animation - Computer art and entertainment (including games) - Curves and meshes - e-Learning applications and computer graphics - Emerging display technologies - Emerging technologies - Face recognition, face detection, and gesture recognition - Fractal geometry and applications - Graph theory in image processing and vision - Graphics algorithms and applications - Haptic devices and techniques - Human-computer interfaces - Illumination and reflection techniques - Image compression, coding, and encryption - Image data structures for computer graphics - Image feature extraction - Image generation, acquisition, and processing - Image geometry and multi-view geometry - Image-based modeling and algorithms - Immersive virtual reality - Integration of virtual reality and multimedia - Interactive digital media - Interactive techniques - Knowledge-based recognition - Learning and assessment based on virtual reality approaches - Machine architectures/engines for graphics and VR - Machine learning technologies for vision - Modeling of natural scenes and phenomena - Modeling techniques - Multimedia Systems and Applications - Multimodal display systems - Object recognition - Real-time collision detection algorithms - Real-time rendering for VR - Rendering methods - Shadows, translucency and visibility - Signal and speech processing - Simulation and virtual reality - Software tools for computer graphics - Software tools for virtual reality - Sound rendering technologies - Surface modeling - Virtual and augmented reality - Virtual environments - Virtual humans and artificial life - Virtual laboratories - Virtual reality and emerging applications - Virtual reality software tools and languages - Virtual reality techniques for behavioral and cognitive assessment - Virtual reality, visualization, and education - Visual computing and graphics - Visualization - Web 3D and applications Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/2014/cgmip2014/paper-submission/ IMPORTANT DATES: Submission Deadline : Extended to Oct. 30, 2014 Notification of Acceptance : Nov. 04, 2014 Camera Ready Submission : Open from now until Nov. 07, 2014 Registration Date : Open from now until Nov. 07, 2014 Conference Dates : November 17-19, 2014 Write us for more details: cgmip2014 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:34:19 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:34:19 +0800 Subject: [Paraview] CFP: ISDF2014 Conference in Greece Message-ID: *http://sdiwc.net/conferences/isdf2014/ * The International Conference in Information Security, and Digital Forensics (ISDF2014) December 12-14, 2014 AMC Metropolitan College, Thessaloniki, Greece All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: ~~ Cyber Security - Distributed and Pervasive System Security - Formal Methods Application in Security - Incident Handling and Penetration Testing - Multimedia and Document Security - Privacy Issues - Secure Software Development, Architecture and Outsourcing - Security in Cloud Computing - Security of Web-based Applications and Services - VOIP, Wireless and Telecommunications Network Security - Enterprise System Security - Hardware-Based Security - Legal issues - Operating System and Database - SCADA and Embedded Systems - Security for Future Networks - Security in Social Networks ~~ Digital Forensics - Anti-Forensics and Anti-Forensics Techniques - Data leakage, Data protection and Database forensics - Executable Content and Content Filtering - Forensics of Virtual and Cloud Environments - Investigation of Insider Attacks - Malware forensics, and Anti-Malware Techniques - New Treats and Non-Traditional approaches - Cyber-Crimes - Evidentiary Aspects of Digital Forensics - File System and Memory Analysis Multimedia Forensics - Information Hiding - Large Scale Investigations - Network Forensics and Traffic Analysis Hardware Vulnerabilities and Device Forensics ~~ Information Assurance and Security Management - Business Continuity & Disaster Recovery Planning - Critical Infrastructure Protection - Digital Rights Management and Intellectual Property Protection - Fraud Management - Laws and Regulations - Corporate Governance - Decidability and Complexity - Economics of Security - Treats, Vulnerabilities, and Risk Management - Identity Management - Security Policies and Trust Management Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/isdf2014/openconf/openconf.php IMPORTANT DATES: Submission Deadline : Extended to November 20, 2014 Notification of Acceptance : November 28, 2014 or 4 weeks after the submission date Camera Ready Submission : Open from now until December 02, 2014 Registration Date : Open from now until December 02, 2014 Conference Dates : December 12-14, 2014 Write us for more details: isdf14 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:35:26 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:35:26 +0800 Subject: [Paraview] CFP: ICESS2015 Conference in Japan Message-ID: http://sdiwc.net/conferences/icess2015/ The International Conference on Electronics and Software Science (ICESS2015) Kagawa University, Takamatsu, Japan July 20-22, 2015 All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: Advanced Power System and Control System Analog and digital circuit Design Automobile Engineering Broad Band Communication Communication Computer and Intelligent Communication Control and Robotics Disaster Prevention Engineering e-Healthcare System Electromagnetics and Photonics Ergonomics and Application Expert Systems and Artificial Intelligence Techniques Feedback Control Systems High Voltage Engineering Information systems and network security Kansei Engineering Measurements and Instrumentation Mechatronics and Avionics Medical Engineering Nano Devices and Integrated Systems Non Conventional Energy Resources Optical Networks & communication Power Electronics Power Electronics & Electric Drives Power Electronics and Energy Efficient Drives Power Quality Improvement Techniques Power Systems Processing and Multimedia, Biomedical Imaging Remote sensing and satellite communication RF and Microwave Engineering Sensor technology & Virtual Instrumentation Server Virtualization Technology Soft Computing Techniques in Power Systems Software for Life Science Software for Material Science System Modeling & Simulation Systems Science and Signal Processing VLSI technology & Design ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT DATES Submission Deadline : May 25, 2015 Notification of Acceptance : June 20, 2015 or 3 weeks from the submission date Camera Ready Submission : Open from now until July 5, 2015 Registration Deadline : Open from now until July 5, 2015 ------------------------------------------------------------------------- Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: hhttp://sdiwc.net/conferences/icess2015/paper-submission/ Write us for more details: icess2015 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:36:45 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:36:45 +0800 Subject: [Paraview] CFP: ISDF2015 Conference in Malaysia Message-ID: *http://sdiwc.net/conferences/isdf2015/ * The Second International Conference on Information Security and Digital Forensics (ISDF2015) October 29-30 & Sep. 01, 2015 Asia Pacific University of Technology and Innovations (APU) Kuala Lumpur, Malaysia All registered papers will be included in SDIWC Digital Library. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The conference welcomes papers on the following (but not limited to) research topics: - Management of Semantic Web data and Linked Data - Semantic Sensor Networks - Database, IR, NLP and AI technologies for the Semantic Web - Search, query, integration, and analysis on the Semantic Web - Query and inference over data streams - Ontology-based data access - Semantic technologies for mobile platforms - Ontology engineering and ontology patterns for the Semantic Web - Ontology modularity, mapping, merging, and alignment - Social networks and processes on the Semantic Web - Semantic Web and Linked Data for Cloud Environments - Information visualization of Semantic Web data and Linked Data - Languages, tools, and methodologies for representing and managing Semantic Web data - Robust and scalable knowledge management and reasoning on the Web - Cleaning, assurance, and provenance of Semantic Web data, services, and processes - Information Extraction from unstructured data - Supporting multi-linguality in the Semantic Web - Geospatial Semantic Web - User Interfaces and interacting with Semantic Web data and Linked Data - Personalized access to Semantic Web data and applications Semantic Web technologies - The Latest Trends in Web Services - Cryptography for Enabling E-Commerce - E-Business Applications and Software - Business Technology Intelligence - Practices and Cases in E-Commerce - Computational Intelligence - Confidentiality Protection - Future Development of E-Business - Future Development of E-Business - Critical Computing and Storage - Customer Relationship Management - Information visualization of Semantic Web data and Linked Data - Digital Data Mining - Digital Economy - Digital Enterprises - Digital Innovation Management - Digital Libraries - Digital Management Products - Digital Economics, and Digital Content - Distributed and Parallel Applications - E-Communities - E-Learning - E-commerce business models - E-commerce Payment Systems - E-commerce Technology Adoption - E-commerce, E-Business Strategies - E-tailing and Multi-Channel selling - EDI and the Internet - Economics Issues of E-Commerce - Evolution of E-Commerce - Internet Payment Systems - M-commerce and Pervasive Computing - Production of Knowledge Economy - Semantic Web, Ontologies - Sensor Networks and Social Sensing - Trust or Security for E-Commerce - Web Applications - Web Advertising and Web Publishing - XML-Based Languages - Digital Economics, and Digital Content ---------------------------------------------------- Important Dates: Submission Dates : Open from now until September 27, 2015 Notification of Acceptance : 3- 4 weeks from the submission date Camera Ready Submission : Open from now until October 17, 2015 Registration : Open from now until October 17, 2015 ----------------------------------------------------- Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/isdf2015/paper-submission/ Write us for more details: isdf15 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:37:51 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:37:51 +0800 Subject: [Paraview] CFP: DEIS2015 Conference in China Message-ID: *http://sdiwc.net/conferences/deis2015/ * The Third International Conference on Digital Enterprise and Information Systems (DEIS2015) April 16-18, 2015 Xueyuan Avenue 1068, Shenzhen University Town, Shenzhen, China All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: - Access Controls - Anti-cyberterrorism - Assurance of Service - Biometrics Technologies - Cloud Computing - Computational Intelligence - Computer Crime Prevention and Detection - Computer Forensics - Computer Security - Confidentiality Protection - Critical Computing and Storage - Critical Infrastructure Management -Cryptography and Data Protection - Data Compression - Data Management in Mobile Peer-to-Peer Networks - Data Mining - Data Stream Processing in Mobile/Sensor Networks - Data and Information Quality - Distributed and Parallel Applications - E-Government, E-Learning and E-Technology - Embedded Systems and Software - Forensics, Recognition Technologies and Applications - Fuzzy and Neural Network Systems - Green Computing - Grid Computing Image Processing - Indexing and Query Processing for Moving Objects - Information Content Security - Information Ethics - Information Propagation on Social Networks - Information and Data Management - Internet Modeling - Mobile Networking, Mobility and Nomadicity - Mobile Social Networks - Mobile, Ad Hoc and Sensor Network Management - Multimedia Computing - Network Security - Peer-to-Peer Social Networks - Quality of Service, Scalability and Performance - Real-Time Systems - Resource and Knowledge Discovery Using Social Networks - Self-Organizing Networks and Networked Systems - Semantic Web, Ontologies - Sensor Networks and Social Sensing - Signal Processing, Pattern Recognition and Applications - Social Networks - Social Search - Soft Computing Techniques - Software Engineeing - Ubiquitous Computing, Services and Applications - User Interfaces and Usability Issues form Mobile Applications - User Interfaces, Visualization and Modeling - Web Services Architecture, Modeling and Design - Web Services Security - Wireless Communications - XML-Based Languages Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/deis2015/openconf/openconf.php IMPORTANT DATES: Submission Deadline : open from now until March 16, 2015 Notification of Acceptance : 2 - 4 weeks from the submission date Camera Ready Submission : Open from from now April 06, 2015 Registration Date : Open from now until April 06, 2015 Conference Dates : April 16-18, 2015 Contact email: : deis15 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Oct 26 11:54:02 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Oct 2014 11:54:02 -0400 Subject: [Paraview] Lights In-Reply-To: References: Message-ID: There isn't any direct mechanism for it. ParaView currently only has two options: head light, or the "light kit" which comes with a fixed set of lights. Utkarsh On Sun, Oct 26, 2014 at 11:12 AM, Greg Abram wrote: > Can anyone tell me where the **** to set the lighting directions etc. in > PV 4.2? > > Gregory D. Abram, Ph.D. > Research Engineering/Scientist Associate > Texas Advanced Computing Center > The University of Texas at Austin > (512) 471-8196 > gda at tacc.utexas.edu > > [image: TACC Website] > > Connect With TACC > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Sun Oct 26 12:02:51 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Oct 2014 12:02:51 -0400 Subject: [Paraview] PointSprite_Plugin not displaying textures on ParaView 4.2.0 Mac OSX 10.10 In-Reply-To: References: Message-ID: Matei, I was indeed able to reproduce the issue. I've reported a bug [1]. We'll track it down soon. Utkarsh [1] http://www.paraview.org/Bug/view.php?id=15078 On Fri, Oct 24, 2014 at 4:20 PM, Matei Stroila wrote: > Hi, > > I believe this is a bug: > The PointSprite_Plugin with ParaView 4.2.0 does not display textures (same textures that ParaView 4.1.0 can display on same machine with OS X 10.10. .) > The texture seems to be loaded but it is not displayed. > > I used the release from this link: > http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v4.2&type=binary&os=osx&downloadFile=ParaView-4.2.0-Darwin-64bit.dmg > > Same behavior with ParaView built on the same machine from the ParaView 4.2.0 sources. > > > Thanks, > Matei > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Sun Oct 26 12:16:25 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Oct 2014 12:16:25 -0400 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: Message-ID: Simon, > is running, will that also test the ParaView binary we produced has a working > python within the ParaView? No. For that, you can run paraview executable and have it run the script on launch instead: paraview --script=sample.py > What about checking and see if numpy is available > for the ParaView binary produced? Yes, you should do something like the following: import numpy print numpy.version.version Same is true for other packages like matplotlib. The API to check the version will of course be different with each. > I even tried to turn off the numpy library > (in the superbuild compile using the cmake flag -DENABLE_numpy=OFF) but the > compilation process compiled numpy nevertheless. The only component in the ParaView superbuild that depends directly on numpy is matplotlib. Is that enabled? If so, it will automatically enable numpy as well. You'll need to turn both off to disable numpy entirely from the build. Utkarsh From tanakas at gmx.ch Sun Oct 26 13:03:28 2014 From: tanakas at gmx.ch (Tanaka Simon) Date: Sun, 26 Oct 2014 18:03:28 +0100 Subject: [Paraview] only displaying a range of line attribute values Message-ID: <544D2960.505@gmx.ch> easy question, but somehow i failed to google it. i have (4.2.0): - multiblock .vtm data - applied "ExtractBlock" filter to get the block containing some lines - the lines have a scalar attribute now i want to only display those lines which have attribute==1, for example. what filter do i have to apply? thanks s From utkarsh.ayachit at kitware.com Sun Oct 26 13:10:03 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Sun, 26 Oct 2014 13:10:03 -0400 Subject: [Paraview] only displaying a range of line attribute values In-Reply-To: <544D2960.505@gmx.ch> References: <544D2960.505@gmx.ch> Message-ID: Did you try using the "Threshold" filter? On Sun, Oct 26, 2014 at 1:03 PM, Tanaka Simon wrote: > easy question, but somehow i failed to google it. > > i have (4.2.0): > - multiblock .vtm data > - applied "ExtractBlock" filter to get the block containing some lines > - the lines have a scalar attribute > > now i want to only display those lines which have attribute==1, for example. > > what filter do i have to apply? > > thanks > s > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From tanakas at gmx.ch Sun Oct 26 13:21:50 2014 From: tanakas at gmx.ch (Tanaka Simon) Date: Sun, 26 Oct 2014 18:21:50 +0100 Subject: [Paraview] only displaying a range of line attribute values In-Reply-To: References: <544D2960.505@gmx.ch> Message-ID: <544D2DAE.2090904@gmx.ch> thank you, that works for now. but: the attribute contains unsigned ints (flags). assuming {1,2,3,4,5,6,7,8}, what if i'd like to only display discontinuous subsets, e.g. lines with {1,4,7} flags? thanks s On 26.10.2014 18:10, Utkarsh Ayachit wrote: > Did you try using the "Threshold" filter? > > On Sun, Oct 26, 2014 at 1:03 PM, Tanaka Simon wrote: >> easy question, but somehow i failed to google it. >> >> i have (4.2.0): >> - multiblock .vtm data >> - applied "ExtractBlock" filter to get the block containing some lines >> - the lines have a scalar attribute >> >> now i want to only display those lines which have attribute==1, for example. >> >> what filter do i have to apply? >> >> thanks >> s >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From kmorel at sandia.gov Sun Oct 26 20:43:22 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 27 Oct 2014 00:43:22 +0000 Subject: [Paraview] pipeline?? In-Reply-To: <544BDEF8.8000104@xs4all.nl> References: <544BDEF8.8000104@xs4all.nl> Message-ID: The visualization pipeline does not have to be a single linear pipeline. You can have multiple pipelines that can fan in and fan out. When you load multiple data sets, you are actually creating several short independent pipelines. This fan in and fan out of pipelines is explained several places including the ParaView tutorial. To answer your question, simply use the group datasets filter. It is available in the common filters toolbar. It can accept several inputs. Group all of your files together and then add filters to the group datasets filter. -Ken Sent from my iPad so blame autocorrect. > On Oct 25, 2014, at 11:34 AM, B.W.H. van Beest wrote: > > Hello, > > How can I accomplish the following? > > I have created a number of source objects (some are read > from file, e.g. an stl file), some are from other Sources. > On each of these segments in the pipeline browser > I can apply a filter that I have written, by selecting > it and applying my filter. Works ok. > > But how can I apply this filter to all of them in one go? > Initially, I thought that applying the filter to the last element > in the pipeline would be enough, it is a pipeline after all, > but that is not the case. > > Do i need to specify somehow in my ::DataRequest > method that it needs to get its input from all segemnts in > the pipe? But how does that work? > > This is what I have in this routine now: > // Get the input data object > vtkPolyData* input = vtkPolyData::GetData( inputVector[0] ); assert( > input ); > > Kind Regards, > Bertwim > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From kmorel at sandia.gov Sun Oct 26 20:47:56 2014 From: kmorel at sandia.gov (Moreland, Kenneth) Date: Mon, 27 Oct 2014 00:47:56 +0000 Subject: [Paraview] Lights In-Reply-To: References: , Message-ID: <8971CB1A-02EB-4DB1-A58E-34EB9E82DE77@sandia.gov> In ParaView 4.2, these controls, as well as everything else in the view properties dialog, have moved to the properties panel. Type light in the search bar at the to of the properties panel and you'll see a button to edit the lights. -Ken Sent from my iPad so blame autocorrect. On Oct 26, 2014, at 9:54 AM, Utkarsh Ayachit > wrote: There isn't any direct mechanism for it. ParaView currently only has two options: head light, or the "light kit" which comes with a fixed set of lights. Utkarsh On Sun, Oct 26, 2014 at 11:12 AM, Greg Abram > wrote: Can anyone tell me where the **** to set the lighting directions etc. in PV 4.2? Gregory D. Abram, Ph.D. Research Engineering/Scientist Associate Texas Advanced Computing Center The University of Texas at Austin (512) 471-8196 gda at tacc.utexas.edu [TACC Website] Connect With TACC _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bwvb at xs4all.nl Sun Oct 26 22:35:35 2014 From: bwvb at xs4all.nl (B.W.H. van Beest) Date: Mon, 27 Oct 2014 03:35:35 +0100 Subject: [Paraview] pipeline?? In-Reply-To: References: <544BDEF8.8000104@xs4all.nl> Message-ID: <544DAF77.6090702@xs4all.nl> Hi Ken, Thanks for your answer. I found and tried the filter you mentioned and it worked. Despite my reading I don't know how many pages on paraview/vtk doc I read, but I missed that multiple pipeline picture, so thanks for pointing me to it. Remains to find out how to do that programmatically. Regards, Bertwim On 10/27/2014 01:43 AM, Moreland, Kenneth wrote: > The visualization pipeline does not have to be a single linear pipeline. You can have multiple pipelines that can fan in and fan out. When you load multiple data sets, you are actually creating several short independent pipelines. This fan in and fan out of pipelines is explained several places including the ParaView tutorial. > > To answer your question, simply use the group datasets filter. It is available in the common filters toolbar. It can accept several inputs. Group all of your files together and then add filters to the group datasets filter. > > -Ken > > Sent from my iPad so blame autocorrect. > >> On Oct 25, 2014, at 11:34 AM, B.W.H. van Beest wrote: >> >> Hello, >> >> How can I accomplish the following? >> >> I have created a number of source objects (some are read >> from file, e.g. an stl file), some are from other Sources. >> On each of these segments in the pipeline browser >> I can apply a filter that I have written, by selecting >> it and applying my filter. Works ok. >> >> But how can I apply this filter to all of them in one go? >> Initially, I thought that applying the filter to the last element >> in the pipeline would be enough, it is a pipeline after all, >> but that is not the case. >> >> Do i need to specify somehow in my ::DataRequest >> method that it needs to get its input from all segemnts in >> the pipe? But how does that work? >> >> This is what I have in this routine now: >> // Get the input data object >> vtkPolyData* input = vtkPolyData::GetData( inputVector[0] ); assert( >> input ); >> >> Kind Regards, >> Bertwim >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From grace.sdiwc at gmail.com Sun Oct 26 11:35:26 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:35:26 +0800 Subject: [Paraview] [Mycolleagues] CFP: ICESS2015 Conference in Japan Message-ID: http://sdiwc.net/conferences/icess2015/ The International Conference on Electronics and Software Science (ICESS2015) Kagawa University, Takamatsu, Japan July 20-22, 2015 All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: Advanced Power System and Control System Analog and digital circuit Design Automobile Engineering Broad Band Communication Communication Computer and Intelligent Communication Control and Robotics Disaster Prevention Engineering e-Healthcare System Electromagnetics and Photonics Ergonomics and Application Expert Systems and Artificial Intelligence Techniques Feedback Control Systems High Voltage Engineering Information systems and network security Kansei Engineering Measurements and Instrumentation Mechatronics and Avionics Medical Engineering Nano Devices and Integrated Systems Non Conventional Energy Resources Optical Networks & communication Power Electronics Power Electronics & Electric Drives Power Electronics and Energy Efficient Drives Power Quality Improvement Techniques Power Systems Processing and Multimedia, Biomedical Imaging Remote sensing and satellite communication RF and Microwave Engineering Sensor technology & Virtual Instrumentation Server Virtualization Technology Soft Computing Techniques in Power Systems Software for Life Science Software for Material Science System Modeling & Simulation Systems Science and Signal Processing VLSI technology & Design ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IMPORTANT DATES Submission Deadline : May 25, 2015 Notification of Acceptance : June 20, 2015 or 3 weeks from the submission date Camera Ready Submission : Open from now until July 5, 2015 Registration Deadline : Open from now until July 5, 2015 ------------------------------------------------------------------------- Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: hhttp://sdiwc.net/conferences/icess2015/paper-submission/ Write us for more details: icess2015 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Mycolleagues mailing list Mycolleagues at mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/mycolleagues - Through this link above you can "subscribe", "unsubscribe", or change your settings in the list, using "username=ufsc" and "password=ufsc". - If you need any help, please send a message to mycolleagues-owner at mailman.ufsc.br. - ENJOY this COURTESY offered by FEDERAL UNIVERSITY OF SANTA CATARINA. From cbording at ivec.org Mon Oct 27 01:22:53 2014 From: cbording at ivec.org (R C Bording) Date: Mon, 27 Oct 2014 13:22:53 +0800 Subject: [Paraview] Paravew on XC30 Message-ID: Hi, Trying to build Paraview on our XC30, here is the end of the build log where it goes pear-shape, Making install in test /usr/bin/install -c -m 644 fonts.dtd '/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts' /usr/bin/install -c -m 644 ./fonts.conf /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v /usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs /usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v make[5]: *** [install-data-local] Error 132 make[4]: *** [install-am] Error 2 make[3]: *** [install-recursive] Error 1 make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] Error 2 make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2 make: *** [all] Error 2 Here is the cmake build flags for the paraviewsuperbuild script. IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ -DParaView_FROM_GIT=OFF \ -DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \ -DENABLE_boost=ON \ -DENABLE_cgns=OFF \ -DENABLE_ffmpeg=ON \ -DENABLE_fontconfig=ON \ -DENABLE_freetype=ON \ -DENABLE_hdf5=ON \ -DENABLE_libxml2=ON \ -DENABLE_matplotlib=OFF \ -DENABLE_mesa=OFF \ -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_osmesa=ON \ -DENABLE_paraview=ON \ -DENABLE_png=ON \ -DENABLE_python=ON \ -DENABLE_qhull=ON \ -DENABLE_qt=OFF \ -DENABLE_silo=ON \ -DENABLE_szip=ON \ -DENABLE_visitbridge=ON \ -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpichcxx.so" \ -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/mpt/lib/libmpich.so" \ -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpichcxx.so" \ -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include" \ -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include" \ -DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=OFF \ -DUSE_SYSTEM_zlib=ON ' Is there other CRAY specific libraries that I should check for before I try again to install paraview? Our Cray does NOT have any GPUS! R. Christopher Bording Supercomputing Team-iVEC at UWA E: cbording at ivec.org T: +61 8 6488 6905 26 Dick Perry Avenue, Technology Park Kensington, Western Australia. 6151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbording at ivec.org Mon Oct 27 01:23:47 2014 From: cbording at ivec.org (R C Bording) Date: Mon, 27 Oct 2014 13:23:47 +0800 Subject: [Paraview] HPC paraview Message-ID: Hi, Managed to get a "working version of Paraview-4.2.0.1" on our GPU cluster but when I try to run the parallelSphere.py script on more than one node it just hangs. Work like it is supposed to up to 12 cores on a single node. I am still trying work out if I a running on the GPU "tesla- C2070). Here is the list of cake configurations IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ -DParaView_FROM_GIT=OFF \ -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ -DENABLE_boost=ON \ -DENABLE_cgns=OFF \ -DENABLE_ffmpeg=ON \ -DENABLE_fontconfig=ON \ -DENABLE_freetype=ON \ -DENABLE_hdf5=ON \ -DENABLE_libxml2=ON \ -DENABLE_matplotlib=ON \ -DENABLE_mesa=OFF \ -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_osmesa=OFF \ -DENABLE_paraview=ON \ -DENABLE_png=ON \ -DENABLE_python=ON \ -DENABLE_qhull=ON \ -DENABLE_qt=ON \ -DENABLE_silo=ON \ -DENABLE_szip=ON \ -DENABLE_visitbridge=ON \ -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ -DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=OFF \ -DUSE_SYSTEM_qt=OFF \ -DUSE_SYSTEM_zlib=OFF ' The goal is to be able to support batch rendering on the whole cluster ~96 nodes. Also do I need set another environment variable in my Paraview module to make the Xlib warning go away? [cbording at f100 Paraview]$ mpirun -n 12 pvbatch --use-offscreen-rendering parallelSphere.py Xlib: extension "NV-GLX" missing on display "localhost:50.0". Xlib: extension "NV-GLX" missing on display "localhost:50.0". Xlib: extension "NV-GLX" missing on display "localhost:50.0". Xlib: extension "NV-GLX" missing on display "localhost:50.0". Xlib: extension "NV-GLX" missing on display "localhost:50.0". Xlib: extension "NV-GLX" missing on display "localhost:50.0". Is this related to my not being able to run across multiple nodes? R. Christopher Bording Supercomputing Team-iVEC at UWA E: cbording at ivec.org T: +61 8 6488 6905 26 Dick Perry Avenue, Technology Park Kensington, Western Australia. 6151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From grace.sdiwc at gmail.com Sun Oct 26 11:34:19 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:34:19 +0800 Subject: [Paraview] [Mycolleagues] CFP: ISDF2014 Conference in Greece Message-ID: *http://sdiwc.net/conferences/isdf2014/ * The International Conference in Information Security, and Digital Forensics (ISDF2014) December 12-14, 2014 AMC Metropolitan College, Thessaloniki, Greece All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: ~~ Cyber Security - Distributed and Pervasive System Security - Formal Methods Application in Security - Incident Handling and Penetration Testing - Multimedia and Document Security - Privacy Issues - Secure Software Development, Architecture and Outsourcing - Security in Cloud Computing - Security of Web-based Applications and Services - VOIP, Wireless and Telecommunications Network Security - Enterprise System Security - Hardware-Based Security - Legal issues - Operating System and Database - SCADA and Embedded Systems - Security for Future Networks - Security in Social Networks ~~ Digital Forensics - Anti-Forensics and Anti-Forensics Techniques - Data leakage, Data protection and Database forensics - Executable Content and Content Filtering - Forensics of Virtual and Cloud Environments - Investigation of Insider Attacks - Malware forensics, and Anti-Malware Techniques - New Treats and Non-Traditional approaches - Cyber-Crimes - Evidentiary Aspects of Digital Forensics - File System and Memory Analysis Multimedia Forensics - Information Hiding - Large Scale Investigations - Network Forensics and Traffic Analysis Hardware Vulnerabilities and Device Forensics ~~ Information Assurance and Security Management - Business Continuity & Disaster Recovery Planning - Critical Infrastructure Protection - Digital Rights Management and Intellectual Property Protection - Fraud Management - Laws and Regulations - Corporate Governance - Decidability and Complexity - Economics of Security - Treats, Vulnerabilities, and Risk Management - Identity Management - Security Policies and Trust Management Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/isdf2014/openconf/openconf.php IMPORTANT DATES: Submission Deadline : Extended to November 20, 2014 Notification of Acceptance : November 28, 2014 or 4 weeks after the submission date Camera Ready Submission : Open from now until December 02, 2014 Registration Date : Open from now until December 02, 2014 Conference Dates : December 12-14, 2014 Write us for more details: isdf14 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Mycolleagues mailing list Mycolleagues at mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/mycolleagues - Through this link above you can "subscribe", "unsubscribe", or change your settings in the list, using "username=ufsc" and "password=ufsc". - If you need any help, please send a message to mycolleagues-owner at mailman.ufsc.br. - ENJOY this COURTESY offered by FEDERAL UNIVERSITY OF SANTA CATARINA. From nawijn at gmail.com Mon Oct 27 06:43:31 2014 From: nawijn at gmail.com (Marco Nawijn) Date: Mon, 27 Oct 2014 11:43:31 +0100 Subject: [Paraview] [Delaunay 3D] In-Reply-To: <000901cff031$55c8f210$015ad630$@gmail.com> References: <000901cff031$55c8f210$015ad630$@gmail.com> Message-ID: Hi Peter, Does every profile have the same number of points? If so, I would generate the connectivity myself and generate a grid with quads. Another option could be to try to do the Delaunay triangulation segment by segment (so two profiles at a time). I am no expert whatsoever, but I think the problem with Delauny is that is just sees a cloud of points to operate on. In your case, there is a clear structure in the points (they are located on section profiles). If you can use this underlying structure I believe you will get a better result. Marco On Sat, Oct 25, 2014 at 10:54 AM, Peter Dvorcak wrote: > Hello everyone, I have object like in the picture above, it is created > from x,y,z points that are loaded from excel. > > I need to create a body with rigid surface, I have used Delaunay 3D filter > and the result is good but not perfect. > > > > > > The problem is with this white linse and also at some places there are > holes in surface. Is there any way how to make this surface smoother ?? I > have tried to change Delaunay parameters but this is the best I was able to > obtain. Do you have any suggestions how to make it better ? > > > > S pozdravom/Best regards > > > > Peter Dvor??k > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 99610 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 11243 bytes Desc: not available URL: From bdaqui at simscale.de Mon Oct 27 06:56:08 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Mon, 27 Oct 2014 11:56:08 +0100 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <544A7AF2.7070603@lbl.gov> References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> <544A7AF2.7070603@lbl.gov> Message-ID: <544E24C8.302@simscale.de> Hi Burlen, Yes, it is a stand-alone C++ application, which makes use of VTK and Paraview as libraries, linking against them and calling functionality to interpret the data. I am not setting up any pipeline (as of now). Is this from the TestExodusTime or TestTemporalFractal examples. I will try adding this. Currently I need to read and traverse the dataset without adding any filters or processing the data. I it still needed to create a pipeline in this case? Kind regards, Bogdan On 10/24/2014 06:14 PM, Burlen Loring wrote: > Hi Bogdan, > > You are writing a stand alone C++ app right? Are you setting up to run the composite data pipeline as in the following example? > > 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); > 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); > 102 cexec->Delete(); > > Burlen > > On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: >> Thanks Bogdan, >> >> that's not helping me but someone else might have some idea. >> >> Seb >> >> On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera > wrote: >> >> Certainly. I should mention, I am using a pre-compiled version of Paraview 4.1 bundled with Salome (Ubuntu package). >> >> Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): >> ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, >> line 316 >> vtkPVDReader (0x6559e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >> from /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >> #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >> #1 0x00007ffff68cc128 in vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from >> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >> #2 0x00007ffff68cd35d in vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from >> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >> #3 0x00007ffff7b97fd0 in vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #4 0x00007ffff7b93447 in vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #5 0x00007ffff7b91181 in vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #6 0x00007ffff7b95bb1 in vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #7 0x00007ffff7ba8c21 in vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #9 0x00007ffff7ba9765 in vtkStreamingDemandDrivenPipeline::Update(int) () >> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >> #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, fileName=..., pMultiBlockDataSet=...) >> at /home/.../someProject/src/testing.cpp:85 >> >> >> Please let me know if you need something additional >> On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: >> > If you provide the stack trace, that may be helpful. >> > >> > Seb >> > >> > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera > >> wrote: >> > >> > Hi Seb, >> > >> > Thanks for the quick reply. Yes the project is managed with CMake. I have not however been able to find the relevant posts by Marcus (in the users >> list). Is >> > that in the users or developers mailing list? >> > >> > It does sound like it could be a problem with some initialization, as you can see below. >> > >> > One short update, it looks like setting ForceMultiBlockDataSet Output with: >> > pReader->SetForceOutputTypeToMultiBlock(1); >> > leads to the segmentation fault at Update() (The deepcopy is never reached). With or without setting the previous line, the error >> > vtkPVDReader (0x1cb49e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >> > >> > The code looks like this now: >> > vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < vtkPVDReader >::New(); >> > pReader->SetFileName("/some/file.pvd"); >> > pReader->Update(); (where the error is triggered) >> > >> > Kind Regards, >> > Bogdan >> > >> > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: >> > > Hi Bogdan, >> > > >> > > here are some issue in your code: >> > > >> > > vtkSmartPointer pReader = vtkPVDReader::New(); // <== Memory LEAK >> > > // Should be either >> > > // vtkNew pReader; >> > > // vtkSmartPointer pReader = vtkSmartPointer::New() >> > > >> > > Then here on a "NULL" object you try to call a method. >> > > >> > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >> > > >> > > Should be something like that: >> > > >> > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; >> > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >> > > >> > > Then you might have some other issue where pReader output being empty/null, but for that I don't know. >> > > >> > > Are you managing your project with CMake? Did you include the necessary file with the proper dependency declaration. This seems to be related to >> the factory not >> > > being properly initialized. You can search the mailing list, Marcus did answer several questions about that. >> > > >> > > Seb >> > > >> > > >> > > >> > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera > > >> > >>> wrote: >> > > >> > > Hello all, >> > > >> > > I am attempting to write some code in c++ which uses the vtkPVDReader from the paraview library to read a series of vtm files. However I am >> > encountering some >> > > problems and I am not sure whether there is something I am missing or whether this could be a bug. >> > > >> > > I am trying to use the reader in the following manner: >> > > My Code: >> > > vtkSmartPointer pReader = vtkPVDReader::New(); >> > > pReader->SetForceOutputTypeToMultiBlock(1); >> > > pReader->SetFileName("/some/fileName.pvd"); >> > > pReader->Update(); >> > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >> > > >> > > Error: >> > > The error occurs at Update() with the following result: >> > > ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default >> > > /vtkXMLCollectionReader.cxx, line 316 >> > > vtkPVDReader (0x224d9e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >> > > Segmentation fault >> > > >> > > Possible error Source >> > > The code concerning line 316 from vtkXMLCollectionReader.cxx is: >> > > >> > > // Use the instantiator to create the reader. >> > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); >> > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); >> > > this->Internal->Readers[index] = reader; >> > > if(reader) >> > > { >> > > reader->Delete(); >> > > } >> > > else >> > > { >> > > // The class was not registered with the instantiator. >> > > vtkErrorMacro("Error creating \"" << rname >> > > << "\" using vtkPVInstantiator."); >> > > if(o) >> > > { >> > > o->Delete(); >> > > } >> > > } >> > > } >> > > >> > > I have isolated the following lines and tested them independently: >> > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); >> > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); >> > > >> > > The pointer "vtkObject* o" is NULL regardless of the class name I pass to instantiate, and I can imagine something like that happening in the >> library, >> > too and >> > > causing the segmentation fault, when calling a SafeDownCast(o) (which is NULL). >> > > >> > > >> > > Any suggestions on how to deal with this problem or if you would be so kind to point me to an example for an alternative solution (Could be >> > vtkFileSeriesReader, >> > > but this fails, as well in my case) would be appreciated. >> > > >> > > Kind Regards, >> > > Bogdan >> > > >> > > P.S.: Using the PVDReader from python code works flawlessly, which is also quite confusing, as to why it would fail in the C++ code. >> > > >> > > -- >> > > Bogdan Daqui >> > > Software Development >> > > >> > > SimScale GmbH >> > > Lichtenbergstra?e 8 >> > > 85748 Garching bei M?nchen >> > > >> > > Phone: +49 (0)89 3398 4078 >> > > Email: bdaqui at simscale.de > > >> >> > > >> > > Amtsgericht M?nchen, HRB 201813 >> > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny >> > > >> > > http://www.simscale.de >> > > _______________________________________________ >> > > Powered by www.kitware.com >> > > >> > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> > > >> > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> > > >> > > Follow this link to subscribe/unsubscribe: >> > > http://public.kitware.com/mailman/listinfo/paraview >> > > >> > > >> > >> > >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From florian.hoffmann at inutech.de Mon Oct 27 08:16:50 2014 From: florian.hoffmann at inutech.de (Florian Hoffmann) Date: Mon, 27 Oct 2014 13:16:50 +0100 Subject: [Paraview] PointSprite_Plugin not displaying textures on ParaView 4.2.0 : solution proposal In-Reply-To: References: Message-ID: <544E37B2.5030808@inutech.de> Dear Utkarsh, Dear Matei I am writing you because of the bug detected in the point sprite plugin: [1]http://www.paraview.org/Bug/view.php?id=15078 I am currently working on my own version of the point sprite plugin and also detected it. Comparing source code of version 4.1 with 4.2 I guess I found the problem. in the source file source\Plugins\PointSprite\ParaViewPlugin\pqPointSpriteControls.cxx after line 261 the following command is missing this->Internals->Links.addPropertyLink(this->Internals->RenderMode, "currentText", SIGNAL(currentIndexChanged(int)), this->Internals->RepresentationProxy, prop); Hope this helps Best regards, Florian Am 26.10.2014 um 17:02 schrieb Utkarsh Ayachit: > [1]http://www.paraview.org/Bug/view.php?id=15078 -- Mit freundlichen Gr??en -- Dr.-Ing. Florian Hoffmann inuTech GmbH Phone : +49-(0)911-323843-22 Fuerther Strasse 212 Fax : +49-(0)911-323843-43 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de Germany Internet : http://www.inutech.de inuTech GmbH Sitz / Registered Office: Nuernberg Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 Gesch?ftsf?hrer / Managing Director: Frank Vogel ***************************************************************** DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! Go to http://www.diffpack.com to read the details ***************************************************************** From utkarsh.ayachit at kitware.com Mon Oct 27 08:33:06 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 27 Oct 2014 08:33:06 -0400 Subject: [Paraview] PointSprite_Plugin not displaying textures on ParaView 4.2.0 : solution proposal In-Reply-To: <544E37B2.5030808@inutech.de> References: <544E37B2.5030808@inutech.de> Message-ID: Florian, Fantastic! I am quite sure that's indeed the issue. I'll track it down once I get to work later today. Utkarsh On Mon, Oct 27, 2014 at 8:16 AM, Florian Hoffmann wrote: > Dear Utkarsh, > Dear Matei > > I am writing you because of the bug detected in the point sprite plugin: > > [1]http://www.paraview.org/Bug/view.php?id=15078 > > > I am currently working on my own version of the point sprite plugin and also > detected it. > Comparing source code of version 4.1 with 4.2 I guess I found the problem. > > in the source file > source\Plugins\PointSprite\ParaViewPlugin\pqPointSpriteControls.cxx > > after > > line 261 > > the following command is missing > > this->Internals->Links.addPropertyLink(this->Internals->RenderMode, > "currentText", SIGNAL(currentIndexChanged(int)), > this->Internals->RepresentationProxy, prop); > > > Hope this helps > > Best regards, > > > Florian > > > Am 26.10.2014 um 17:02 schrieb Utkarsh Ayachit: >> >> [1]http://www.paraview.org/Bug/view.php?id=15078 > > > -- > Mit freundlichen Gr??en > -- > Dr.-Ing. Florian Hoffmann > inuTech GmbH Phone : +49-(0)911-323843-22 > Fuerther Strasse 212 Fax : +49-(0)911-323843-43 > 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de > Germany Internet : http://www.inutech.de > > inuTech GmbH > Sitz / Registered Office: Nuernberg > Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 > Gesch?ftsf?hrer / Managing Director: Frank Vogel > > ***************************************************************** > DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! > > Go to http://www.diffpack.com to read the details > ***************************************************************** > From simon.m.su.ctr at mail.mil Mon Oct 27 09:43:39 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 27 Oct 2014 13:43:39 +0000 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: , Message-ID: Utkarsh, thank you for your explanations. So, paraview --script=sample.py this will test to see if the python within ParaView pvpython sample.py pvbatch sample.py than what will the above two tests show? If paraview --script=sample.py test is a successful test, can we also assume that pvpython and pvbatch test will also work? So for individual python packages, I will need to do the import test for all the packages I want to test in the script right? Yes I have matplotlib enabled and that's why numpy is still there when I turn it off. Thanks... thanks again for your help -simon ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Sunday, October 26, 2014 12:16 PM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] pvserver test on different systems (UNCLASSIFIED) Simon, > is running, will that also test the ParaView binary we produced has a working > python within the ParaView? No. For that, you can run paraview executable and have it run the script on launch instead: paraview --script=sample.py > What about checking and see if numpy is available > for the ParaView binary produced? Yes, you should do something like the following: import numpy print numpy.version.version Same is true for other packages like matplotlib. The API to check the version will of course be different with each. > I even tried to turn off the numpy library > (in the superbuild compile using the cmake flag -DENABLE_numpy=OFF) but the > compilation process compiled numpy nevertheless. The only component in the ParaView superbuild that depends directly on numpy is matplotlib. Is that enabled? If so, it will automatically enable numpy as well. You'll need to turn both off to disable numpy entirely from the build. Utkarsh From matei.stroila at gmail.com Mon Oct 27 10:06:30 2014 From: matei.stroila at gmail.com (Matei Stroila) Date: Mon, 27 Oct 2014 09:06:30 -0500 Subject: [Paraview] PointSprite_Plugin not displaying textures on ParaView 4.2.0 : solution proposal In-Reply-To: References: <544E37B2.5030808@inutech.de> Message-ID: <049D3342-E7F2-4458-816C-33EB646E3069@gmail.com> I added the command and that fixed the issue. Thank you, Florian! > On Oct 27, 2014, at 7:33 AM, Utkarsh Ayachit wrote: > > Florian, > > Fantastic! I am quite sure that's indeed the issue. I'll track it down > once I get to work later today. > > Utkarsh > > On Mon, Oct 27, 2014 at 8:16 AM, Florian Hoffmann > wrote: >> Dear Utkarsh, >> Dear Matei >> >> I am writing you because of the bug detected in the point sprite plugin: >> >> [1]http://www.paraview.org/Bug/view.php?id=15078 >> >> >> I am currently working on my own version of the point sprite plugin and also >> detected it. >> Comparing source code of version 4.1 with 4.2 I guess I found the problem. >> >> in the source file >> source\Plugins\PointSprite\ParaViewPlugin\pqPointSpriteControls.cxx >> >> after >> >> line 261 >> >> the following command is missing >> >> this->Internals->Links.addPropertyLink(this->Internals->RenderMode, >> "currentText", SIGNAL(currentIndexChanged(int)), >> this->Internals->RepresentationProxy, prop); >> >> >> Hope this helps >> >> Best regards, >> >> >> Florian >> >> >> Am 26.10.2014 um 17:02 schrieb Utkarsh Ayachit: >>> >>> [1]http://www.paraview.org/Bug/view.php?id=15078 >> >> >> -- >> Mit freundlichen Gr??en >> -- >> Dr.-Ing. Florian Hoffmann >> inuTech GmbH Phone : +49-(0)911-323843-22 >> Fuerther Strasse 212 Fax : +49-(0)911-323843-43 >> 90429 Nuernberg E-Mai l : florian.hoffmann at inutech.de >> Germany Internet : http://www.inutech.de >> >> inuTech GmbH >> Sitz / Registered Office: Nuernberg >> Handelsregister / Companies' Register: AG N?rnberg HRB Nr. 19026 >> Gesch?ftsf?hrer / Managing Director: Frank Vogel >> >> ***************************************************************** >> DIFFPACK - THE NEW GENERATION OF SIMULATION-SOFTWARE! >> >> Go to http://www.diffpack.com to read the details >> ***************************************************************** >> From utkarsh.ayachit at kitware.com Mon Oct 27 10:10:14 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 27 Oct 2014 10:10:14 -0400 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: Message-ID: Simon, Although, explicit pvpython/pvbatch test isn't necessary, it's worth doing it since sometimes the paths to locate ParaView's Python modules can get messed up between different executables. > So for individual python packages, I will need to do the import test for all the packages I want to test in the script right? Yes, ideally. Utkarsh From bloring at lbl.gov Mon Oct 27 11:00:43 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 27 Oct 2014 08:00:43 -0700 Subject: [Paraview] Paravew on XC30 In-Reply-To: References: Message-ID: <544E5E1B.8080608@lbl.gov> Hi Christopher, I can't help you with the superbuild, but I can show you how to build PV on the XC30. here's the script I used to build ParaView 4.2 with PrgEnv-gnu/5.2.25 on our XC30 You'll see a bunch of paths that need to be set specific to the version of PrgEnv-gnu that you are running. The easiest way to figure out these is to look at the CRAY_LD_LIBRARY_PATH environment variable. If for some reason that isn't set then you can alway look at the output of "CC --verbose". You also need to point to an OSMesa install . Burlen On 10/26/2014 10:22 PM, R C Bording wrote: > Hi, > Trying to build Paraview on our XC30, > here is the end of the build log where it goes pear-shape, > > Making install in test > /usr/bin/install -c -m 644 fonts.dtd > '/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts' > /usr/bin/install -c -m 644 ./fonts.conf > /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf > /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache > -s -f -v > /usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs > /usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction > /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2.0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache > -s -f -v > make[5]: *** [install-data-local] Error 132 > make[4]: *** [install-am] Error 2 > make[3]: *** [install-recursive] Error 1 > make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] Error 2 > make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2 > make: *** [all] Error 2 > > Here is the cmake build flags for the paraviewsuperbuild script. > > IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ > -DParaView_FROM_GIT=OFF \ > -DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \ > -DENABLE_boost=ON \ > -DENABLE_cgns=OFF \ > -DENABLE_ffmpeg=ON \ > -DENABLE_fontconfig=ON \ > -DENABLE_freetype=ON \ > -DENABLE_hdf5=ON \ > -DENABLE_libxml2=ON \ > -DENABLE_matplotlib=OFF \ > -DENABLE_mesa=OFF \ > -DENABLE_mpi=ON \ > -DENABLE_numpy=ON \ > -DENABLE_osmesa=ON \ > -DENABLE_paraview=ON \ > -DENABLE_png=ON \ > -DENABLE_python=ON \ > -DENABLE_qhull=ON \ > -DENABLE_qt=OFF \ > -DENABLE_silo=ON \ > -DENABLE_szip=ON \ > -DENABLE_visitbridge=ON \ > -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpichcxx.so" > \ > -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/mpt/lib/libmpich.so" > \ > -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpichcxx.so" > \ > -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include" > \ > -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include" > \ > -DUSE_SYSTEM_mpi=ON \ > -DUSE_SYSTEM_python=OFF \ > -DUSE_SYSTEM_zlib=ON ' > > Is there other CRAY specific libraries that I should check for before > I try again to install paraview? > Our Cray does NOT have any GPUS! > > R. Christopher Bording > Supercomputing Team-iVEC at UWA > E: cbording at ivec.org > T: +61 8 6488 6905 > > 26 Dick Perry Avenue, > Technology Park > Kensington, Western Australia. > 6151 > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Mon Oct 27 11:10:01 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 27 Oct 2014 08:10:01 -0700 Subject: [Paraview] HPC paraview In-Reply-To: References: Message-ID: <544E6049.6000003@lbl.gov> Hi Christopher, Are you by any chance logged in with ssh X11 forwarding (ssh -X ...)? It seems the error you report comes up often in that context. X forwarding would not be the right way to run PV on your cluster. Depending on how your cluster is setup you may need to start up the xserver before launching PV, and make sure to close it after PV exits. IUn that scenario your xorg.conf would specify the nvidia driver and a screen for each gpu which you would refernece in the shell used to start PV through the DISPLAY variable. If you already have x11 running and screens configured then it's just a matter of setting the display variable correctly. When there are multiple GPU's per node then you'd need to set the display using mpi rank modulo the number of gpus per node. I'm not sure it matters that much but I don't think that you want --use-offscreen-rendering option. Burlen On 10/26/2014 10:23 PM, R C Bording wrote: > Hi, > Managed to get a "working version of Paraview-4.2.0.1" on our GPU > cluster but when I try to run the > parallelSphere.py script on more than one node it just hangs. Work > like it is supposed to up to 12 cores on a single node. I am still > trying work out if I a running on the GPU "tesla- C2070). > > Here is the list of cake configurations > > IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ > -DParaView_FROM_GIT=OFF \ > -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ > -DENABLE_boost=ON \ > -DENABLE_cgns=OFF \ > -DENABLE_ffmpeg=ON \ > -DENABLE_fontconfig=ON \ > -DENABLE_freetype=ON \ > -DENABLE_hdf5=ON \ > -DENABLE_libxml2=ON \ > -DENABLE_matplotlib=ON \ > -DENABLE_mesa=OFF \ > -DENABLE_mpi=ON \ > -DENABLE_numpy=ON \ > -DENABLE_osmesa=OFF \ > -DENABLE_paraview=ON \ > -DENABLE_png=ON \ > -DENABLE_python=ON \ > -DENABLE_qhull=ON \ > -DENABLE_qt=ON \ > -DENABLE_silo=ON \ > -DENABLE_szip=ON \ > -DENABLE_visitbridge=ON \ > -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ > -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ > -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ > -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ > -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ > -DUSE_SYSTEM_mpi=ON \ > -DUSE_SYSTEM_python=OFF \ > -DUSE_SYSTEM_qt=OFF \ > -DUSE_SYSTEM_zlib=OFF ' > > The goal is to be able to support batch rendering on the whole cluster > ~96 nodes. > > Also do I need set another environment variable in my Paraview module > to make the Xlib > warning go away? > > [cbording at f100 Paraview]$ mpirun -n 12 pvbatch > --use-offscreen-rendering parallelSphere.py > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > Xlib: extension "NV-GLX" missing on display "localhost:50.0". > > Is this related to my not being able to run across multiple nodes? > > R. Christopher Bording > Supercomputing Team-iVEC at UWA > E: cbording at ivec.org > T: +61 8 6488 6905 > > 26 Dick Perry Avenue, > Technology Park > Kensington, Western Australia. > 6151 > > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Mon Oct 27 11:14:31 2014 From: bloring at lbl.gov (Burlen Loring) Date: Mon, 27 Oct 2014 08:14:31 -0700 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <544E24C8.302@simscale.de> References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> <544A7AF2.7070603@lbl.gov> <544E24C8.302@simscale.de> Message-ID: <544E6157.7030507@lbl.gov> Unless something's changed in the pipeline recently that I'm unaware of, when dealing with multiblock data you still need to force the composite data pipeline first. that may or or may not be the cause of your segfault, but you need to do it. On 10/27/2014 03:56 AM, Bogdan Daqui Herrera wrote: > Hi Burlen, > > Yes, it is a stand-alone C++ application, which makes use of VTK and Paraview as libraries, linking against them and calling functionality to interpret the data. > I am not setting up any pipeline (as of now). Is this from the TestExodusTime or TestTemporalFractal examples. I will try adding this. > > Currently I need to read and traverse the dataset without adding any filters or processing the data. I it still needed to create a pipeline in this case? > > Kind regards, > Bogdan > > On 10/24/2014 06:14 PM, Burlen Loring wrote: >> Hi Bogdan, >> >> You are writing a stand alone C++ app right? Are you setting up to run the composite data pipeline as in the following example? >> >> 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); >> 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); >> 102 cexec->Delete(); >> >> Burlen >> >> On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: >>> Thanks Bogdan, >>> >>> that's not helping me but someone else might have some idea. >>> >>> Seb >>> >>> On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera > wrote: >>> >>> Certainly. I should mention, I am using a pre-compiled version of Paraview 4.1 bundled with Salome (Ubuntu package). >>> >>> Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): >>> ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, >>> line 316 >>> vtkPVDReader (0x6559e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >>> from /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>> #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>> #1 0x00007ffff68cc128 in vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from >>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>> #2 0x00007ffff68cd35d in vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () from >>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>> #3 0x00007ffff7b97fd0 in vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #4 0x00007ffff7b93447 in vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #5 0x00007ffff7b91181 in vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #6 0x00007ffff7b95bb1 in vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #7 0x00007ffff7ba8c21 in vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #9 0x00007ffff7ba9765 in vtkStreamingDemandDrivenPipeline::Update(int) () >>> from /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>> #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, fileName=..., pMultiBlockDataSet=...) >>> at /home/.../someProject/src/testing.cpp:85 >>> >>> >>> Please let me know if you need something additional >>> On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: >>> > If you provide the stack trace, that may be helpful. >>> > >>> > Seb >>> > >>> > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera >> >> wrote: >>> > >>> > Hi Seb, >>> > >>> > Thanks for the quick reply. Yes the project is managed with CMake. I have not however been able to find the relevant posts by Marcus (in the users >>> list). Is >>> > that in the users or developers mailing list? >>> > >>> > It does sound like it could be a problem with some initialization, as you can see below. >>> > >>> > One short update, it looks like setting ForceMultiBlockDataSet Output with: >>> > pReader->SetForceOutputTypeToMultiBlock(1); >>> > leads to the segmentation fault at Update() (The deepcopy is never reached). With or without setting the previous line, the error >>> > vtkPVDReader (0x1cb49e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>> > >>> > The code looks like this now: >>> > vtkSmartPointer < vtkPVDReader > pReader = vtkSmartPointer < vtkPVDReader >::New(); >>> > pReader->SetFileName("/some/file.pvd"); >>> > pReader->Update(); (where the error is triggered) >>> > >>> > Kind Regards, >>> > Bogdan >>> > >>> > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: >>> > > Hi Bogdan, >>> > > >>> > > here are some issue in your code: >>> > > >>> > > vtkSmartPointer pReader = vtkPVDReader::New(); // <== Memory LEAK >>> > > // Should be either >>> > > // vtkNew pReader; >>> > > // vtkSmartPointer pReader = vtkSmartPointer::New() >>> > > >>> > > Then here on a "NULL" object you try to call a method. >>> > > >>> > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>> > > >>> > > Should be something like that: >>> > > >>> > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; >>> > > pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>> > > >>> > > Then you might have some other issue where pReader output being empty/null, but for that I don't know. >>> > > >>> > > Are you managing your project with CMake? Did you include the necessary file with the proper dependency declaration. This seems to be related to >>> the factory not >>> > > being properly initialized. You can search the mailing list, Marcus did answer several questions about that. >>> > > >>> > > Seb >>> > > >>> > > >>> > > >>> > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera >> > >>> > >>> wrote: >>> > > >>> > > Hello all, >>> > > >>> > > I am attempting to write some code in c++ which uses the vtkPVDReader from the paraview library to read a series of vtm files. However I am >>> > encountering some >>> > > problems and I am not sure whether there is something I am missing or whether this could be a bug. >>> > > >>> > > I am trying to use the reader in the following manner: >>> > > My Code: >>> > > vtkSmartPointer pReader = vtkPVDReader::New(); >>> > > pReader->SetForceOutputTypeToMultiBlock(1); >>> > > pReader->SetFileName("/some/fileName.pvd"); >>> > > pReader->Update(); >>> > > vtkMultiBlockDataSet* pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>> > > >>> > > Error: >>> > > The error occurs at Update() with the following result: >>> > > ERROR: In /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default >>> > > /vtkXMLCollectionReader.cxx, line 316 >>> > > vtkPVDReader (0x224d9e0): Error creating "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>> > > Segmentation fault >>> > > >>> > > Possible error Source >>> > > The code concerning line 316 from vtkXMLCollectionReader.cxx is: >>> > > >>> > > // Use the instantiator to create the reader. >>> > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); >>> > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); >>> > > this->Internal->Readers[index] = reader; >>> > > if(reader) >>> > > { >>> > > reader->Delete(); >>> > > } >>> > > else >>> > > { >>> > > // The class was not registered with the instantiator. >>> > > vtkErrorMacro("Error creating \"" << rname >>> > > << "\" using vtkPVInstantiator."); >>> > > if(o) >>> > > { >>> > > o->Delete(); >>> > > } >>> > > } >>> > > } >>> > > >>> > > I have isolated the following lines and tested them independently: >>> > > vtkObject* o = vtkPVInstantiator::CreateInstance(rname); >>> > > vtkXMLReader* reader = vtkXMLReader::SafeDownCast(o); >>> > > >>> > > The pointer "vtkObject* o" is NULL regardless of the class name I pass to instantiate, and I can imagine something like that happening in the >>> library, >>> > too and >>> > > causing the segmentation fault, when calling a SafeDownCast(o) (which is NULL). >>> > > >>> > > >>> > > Any suggestions on how to deal with this problem or if you would be so kind to point me to an example for an alternative solution (Could be >>> > vtkFileSeriesReader, >>> > > but this fails, as well in my case) would be appreciated. >>> > > >>> > > Kind Regards, >>> > > Bogdan >>> > > >>> > > P.S.: Using the PVDReader from python code works flawlessly, which is also quite confusing, as to why it would fail in the C++ code. >>> > > >>> > > -- >>> > > Bogdan Daqui >>> > > Software Development >>> > > >>> > > SimScale GmbH >>> > > Lichtenbergstra?e 8 >>> > > 85748 Garching bei M?nchen >>> > > >>> > > Phone: +49 (0)89 3398 4078 >>> > > Email: bdaqui at simscale.de > >> >> >>> > > >>> > > Amtsgericht M?nchen, HRB 201813 >>> > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny >>> > > >>> > > http://www.simscale.de >>> > > _______________________________________________ >>> > > Powered by www.kitware.com >>> > > >>> > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> > > >>> > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> > > >>> > > Follow this link to subscribe/unsubscribe: >>> > > http://public.kitware.com/mailman/listinfo/paraview >>> > > >>> > > >>> > >>> > >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview From richard.c.angelini.civ at mail.mil Mon Oct 27 11:22:01 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Mon, 27 Oct 2014 15:22:01 +0000 Subject: [Paraview] Paravew on XC30 In-Reply-To: <544E5E1B.8080608@lbl.gov> References: <544E5E1B.8080608@lbl.gov> Message-ID: Chris - I?ve been able to build on 3 different XC30 systems ? here?s my script. I?m using PrgEnv-gnu/5.2.14 cray-mpich/6.3.1 gcc/4.8.2 #!/bin/csh module unload PrgEnv-cray module load PrgEnv-gnu module load cray-mpich module load pbs module list setenv gcc "gcc" setenv gplusplus "g++" setenv gfortran "gfortran" setenv CC $gcc setenv CXX $gplusplus setenv FC $gfortran setenv F70 $gfortran setenv F77 $gfortran setenv F90 $gfortran setenv F95 $gfortran set version=4.2.0 if (! -d Build_${version}_mesa) mkdir Build_${version}_mesa cd Build_${version}_mesa if (! -d install) mkdir install set INSTALLPATH=`pwd`/install #Build the latest version of CMAKE if (! -e install/bin/cmake) then echo "Need to build cmake" cp ../Downloads/cmake-2.8.11.tar.gz . tar xzvf cmake-2.8.11.tar.gz cd cmake-2.8.11 ./bootstrap --prefix=$INSTALLPATH make -j 8 install cd .. endif setenv PATH ${INSTALLPATH}/bin:$PATH cmake \ -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_mesa \ -DCMAKE_BUILD_TYPE=Release \ -DParaView_FROM_GIT=OFF \ -Ddownload_location=`pwd`/../Downloads \ -DParaView_URL=`pwd`/../Downloads/ParaView-v4.2.0-source.tar.gz \ -DENABLE_boost=ON \ -DENABLE_cgns=OFF \ -DENABLE_ffmpeg=ON \ -DENABLE_fontconfig=ON \ -DENABLE_freetype=ON \ -DENABLE_hdf5=ON \ -DENABLE_libxml2=ON \ -DENABLE_matplotlib=OFF \ -DENABLE_osmesa=OFF \ -DENABLE_mesa=ON \ -DENABLE_qt=ON \ -DENABLE_mpi=ON \ -DENABLE_numpy=ON \ -DENABLE_paraview=ON \ -DENABLE_png=ON \ -DENABLE_python=ON \ -DENABLE_qhull=ON \ -DENABLE_silo=ON \ -DENABLE_szip=ON \ -DENABLE_visitbridge=OFF \ -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp ichcxx.so" \ -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic h.so" \ -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc xx.so" \ -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ e/" \ -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/ " \ -DUSE_SYSTEM_mpi=ON \ -DUSE_SYSTEM_python=ON \ -DUSE_SYSTEM_zlib=ON \ ../Source make -j 4 install ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 On 10/27/14, 11:00 AM, "Burlen Loring" wrote: > > > >Hi Christopher, > >I can't help you with the superbuild, but I can show you how to build PV >on the XC30. here's > >the script >lds/config-pv-mesa.sh> I used to build ParaView 4.2 with >PrgEnv-gnu/5.2.25 on our XC30 > >You'll see a bunch of paths that need to be set specific to the version >of PrgEnv-gnu that you are running. The easiest way to figure out these >is to look at the CRAY_LD_LIBRARY_PATH environment variable. If for some >reason that isn't set then you can alway > look at the output of "CC --verbose". You also need to point to an >OSMesa install >. > >Burlen > >On 10/26/2014 10:22 PM, R C Bording wrote: > > >Hi, > Trying to build Paraview on our XC30, >here is the end of the build log where it goes pear-shape, > >Making install in test >/usr/bin/install -c -m 644 fonts.dtd >'/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2 >.0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts' >/usr/bin/install -c -m 644 ./fonts.conf >/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf >/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >/usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs >/usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction >/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >make[5]: *** [install-data-local] Error 132 >make[4]: *** [install-am] Error 2 >make[3]: *** [install-recursive] Error 1 >make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] Error 2 >make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2 >make: *** [all] Error 2 > >Here is the cmake build flags for the paraviewsuperbuild script. > >IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >-DParaView_FROM_GIT=OFF \ >-DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \ >-DENABLE_boost=ON \ >-DENABLE_cgns=OFF \ >-DENABLE_ffmpeg=ON \ >-DENABLE_fontconfig=ON \ >-DENABLE_freetype=ON \ >-DENABLE_hdf5=ON \ >-DENABLE_libxml2=ON \ >-DENABLE_matplotlib=OFF \ >-DENABLE_mesa=OFF \ >-DENABLE_mpi=ON \ >-DENABLE_numpy=ON \ >-DENABLE_osmesa=ON \ >-DENABLE_paraview=ON \ >-DENABLE_png=ON \ >-DENABLE_python=ON \ >-DENABLE_qhull=ON \ >-DENABLE_qt=OFF \ >-DENABLE_silo=ON \ >-DENABLE_szip=ON \ >-DENABLE_visitbridge=ON \ >-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libm >pichcxx.so" \ >-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/mpt/lib/li >bmpich.so" \ >-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpich >cxx.so" \ >-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/inclu >de" \ >-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include >" \ >-DUSE_SYSTEM_mpi=ON \ >-DUSE_SYSTEM_python=OFF \ >-DUSE_SYSTEM_zlib=ON ' > >Is there other CRAY specific libraries that I should check for before I >try again to install paraview? >Our Cray does NOT have any GPUS! > >R. Christopher Bording >Supercomputing Team-iVEC at UWA >E: cbording at ivec.org >T: +61 8 6488 6905 > > >26 Dick Perry Avenue, >Technology Park >Kensington, Western Australia. >6151 > > > > > > > > > > > > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at >http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: >http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview > > From utkarsh.ayachit at kitware.com Mon Oct 27 11:24:28 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Mon, 27 Oct 2014 11:24:28 -0400 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: <544E6157.7030507@lbl.gov> References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> <544A7AF2.7070603@lbl.gov> <544E24C8.302@simscale.de> <544E6157.7030507@lbl.gov> Message-ID: Bogdan, The deal is this: the vtkPVDReader is designed for ParaView, it uses some of the core client-server infrastructure in ParaView. Thus, you can't use it directly is a VTK-based C++ executable without initializing ParaView environment. Initializing ParaView environment is not too complicated. Look at pvserver_common.h or pvpython.h, it should give you the necessary code. You basically use vtkInitializationHelper API to initialize the ParaView environment. Hope that helps, Utkarsh On Mon, Oct 27, 2014 at 11:14 AM, Burlen Loring wrote: > Unless something's changed in the pipeline recently that I'm unaware of, > when dealing with multiblock data you still need to force the composite data > pipeline first. that may or or may not be the cause of your segfault, but > you need to do it. > > > On 10/27/2014 03:56 AM, Bogdan Daqui Herrera wrote: >> >> Hi Burlen, >> >> Yes, it is a stand-alone C++ application, which makes use of VTK and >> Paraview as libraries, linking against them and calling functionality to >> interpret the data. >> I am not setting up any pipeline (as of now). Is this from the >> TestExodusTime or TestTemporalFractal examples. I will try adding this. >> >> Currently I need to read and traverse the dataset without adding any >> filters or processing the data. I it still needed to create a pipeline in >> this case? >> >> Kind regards, >> Bogdan >> >> On 10/24/2014 06:14 PM, Burlen Loring wrote: >>> >>> Hi Bogdan, >>> >>> You are writing a stand alone C++ app right? Are you setting up to run >>> the composite data pipeline as in the following example? >>> >>> 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); >>> 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); >>> 102 cexec->Delete(); >>> >>> Burlen >>> >>> On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: >>>> >>>> Thanks Bogdan, >>>> >>>> that's not helping me but someone else might have some idea. >>>> >>>> Seb >>>> >>>> On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera >>>> > wrote: >>>> >>>> Certainly. I should mention, I am using a pre-compiled version of >>>> Paraview 4.1 bundled with Salome (Ubuntu package). >>>> >>>> Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): >>>> ERROR: In >>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, >>>> line 316 >>>> vtkPVDReader (0x6559e0): Error creating >>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>> >>>> Program received signal SIGSEGV, Segmentation fault. >>>> 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >>>> from >>>> /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>> #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() >>>> () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>> #1 0x00007ffff68cc128 in >>>> vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, >>>> vtkInformationVector*) () from >>>> >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>> #2 0x00007ffff68cd35d in >>>> vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, >>>> vtkInformationVector*) () from >>>> >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>> #3 0x00007ffff7b97fd0 in >>>> vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, >>>> vtkInformationVector*) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #4 0x00007ffff7b93447 in >>>> vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, >>>> vtkInformationVector**, vtkInformationVector*) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #5 0x00007ffff7b91181 in >>>> vtkCompositeDataPipeline::ExecuteData(vtkInformation*, >>>> vtkInformationVector**, vtkInformationVector*) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #6 0x00007ffff7b95bb1 in >>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>> vtkInformationVector**, vtkInformationVector*) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #7 0x00007ffff7ba8c21 in >>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>> vtkInformationVector**, vtkInformationVector*) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) >>>> () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #9 0x00007ffff7ba9765 in >>>> vtkStreamingDemandDrivenPipeline::Update(int) () >>>> from >>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>> #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, >>>> fileName=..., pMultiBlockDataSet=...) >>>> at /home/.../someProject/src/testing.cpp:85 >>>> >>>> >>>> Please let me know if you need something additional >>>> On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: >>>> > If you provide the stack trace, that may be helpful. >>>> > >>>> > Seb >>>> > >>>> > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera >>>> >>> >> wrote: >>>> > >>>> > Hi Seb, >>>> > >>>> > Thanks for the quick reply. Yes the project is managed with >>>> CMake. I have not however been able to find the relevant posts by Marcus (in >>>> the users >>>> list). Is >>>> > that in the users or developers mailing list? >>>> > >>>> > It does sound like it could be a problem with some >>>> initialization, as you can see below. >>>> > >>>> > One short update, it looks like setting >>>> ForceMultiBlockDataSet Output with: >>>> > pReader->SetForceOutputTypeToMultiBlock(1); >>>> > leads to the segmentation fault at Update() (The deepcopy is >>>> never reached). With or without setting the previous line, the error >>>> > vtkPVDReader (0x1cb49e0): Error creating >>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>> > >>>> > The code looks like this now: >>>> > vtkSmartPointer < vtkPVDReader > pReader = >>>> vtkSmartPointer < vtkPVDReader >::New(); >>>> > pReader->SetFileName("/some/file.pvd"); >>>> > pReader->Update(); (where the error is triggered) >>>> > >>>> > Kind Regards, >>>> > Bogdan >>>> > >>>> > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: >>>> > > Hi Bogdan, >>>> > > >>>> > > here are some issue in your code: >>>> > > >>>> > > vtkSmartPointer pReader = >>>> vtkPVDReader::New(); // <== Memory LEAK >>>> > > // Should be either >>>> > > // vtkNew pReader; >>>> > > // vtkSmartPointer pReader = >>>> vtkSmartPointer::New() >>>> > > >>>> > > Then here on a "NULL" object you try to call a method. >>>> > > >>>> > > vtkMultiBlockDataSet* >>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>> > > >>>> > > Should be something like that: >>>> > > >>>> > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; >>>> > > >>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>> > > >>>> > > Then you might have some other issue where pReader output >>>> being empty/null, but for that I don't know. >>>> > > >>>> > > Are you managing your project with CMake? Did you include >>>> the necessary file with the proper dependency declaration. This seems to be >>>> related to >>>> the factory not >>>> > > being properly initialized. You can search the mailing >>>> list, Marcus did answer several questions about that. >>>> > > >>>> > > Seb >>>> > > >>>> > > >>>> > > >>>> > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera >>>> >>> > >>> >>>> > >>> >>>> wrote: >>>> > > >>>> > > Hello all, >>>> > > >>>> > > I am attempting to write some code in c++ which uses >>>> the vtkPVDReader from the paraview library to read a series of vtm files. >>>> However I am >>>> > encountering some >>>> > > problems and I am not sure whether there is something I >>>> am missing or whether this could be a bug. >>>> > > >>>> > > I am trying to use the reader in the following manner: >>>> > > My Code: >>>> > > vtkSmartPointer pReader = >>>> vtkPVDReader::New(); >>>> > > pReader->SetForceOutputTypeToMultiBlock(1); >>>> > > pReader->SetFileName("/some/fileName.pvd"); >>>> > > pReader->Update(); >>>> > > vtkMultiBlockDataSet* >>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>> > > >>>> > > Error: >>>> > > The error occurs at Update() with the following >>>> result: >>>> > > ERROR: In >>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default >>>> > > /vtkXMLCollectionReader.cxx, line 316 >>>> > > vtkPVDReader (0x224d9e0): Error creating >>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>> > > Segmentation fault >>>> > > >>>> > > Possible error Source >>>> > > The code concerning line 316 from >>>> vtkXMLCollectionReader.cxx is: >>>> > > >>>> > > // Use the instantiator to create the reader. >>>> > > vtkObject* o = >>>> vtkPVInstantiator::CreateInstance(rname); >>>> > > vtkXMLReader* reader = >>>> vtkXMLReader::SafeDownCast(o); >>>> > > this->Internal->Readers[index] = reader; >>>> > > if(reader) >>>> > > { >>>> > > reader->Delete(); >>>> > > } >>>> > > else >>>> > > { >>>> > > // The class was not registered with the >>>> instantiator. >>>> > > vtkErrorMacro("Error creating \"" << rname >>>> > > << "\" using >>>> vtkPVInstantiator."); >>>> > > if(o) >>>> > > { >>>> > > o->Delete(); >>>> > > } >>>> > > } >>>> > > } >>>> > > >>>> > > I have isolated the following lines and tested them >>>> independently: >>>> > > vtkObject* o = >>>> vtkPVInstantiator::CreateInstance(rname); >>>> > > vtkXMLReader* reader = >>>> vtkXMLReader::SafeDownCast(o); >>>> > > >>>> > > The pointer "vtkObject* o" is NULL regardless of the >>>> class name I pass to instantiate, and I can imagine something like that >>>> happening in the >>>> library, >>>> > too and >>>> > > causing the segmentation fault, when calling a >>>> SafeDownCast(o) (which is NULL). >>>> > > >>>> > > >>>> > > Any suggestions on how to deal with this problem or if >>>> you would be so kind to point me to an example for an alternative solution >>>> (Could be >>>> > vtkFileSeriesReader, >>>> > > but this fails, as well in my case) would be >>>> appreciated. >>>> > > >>>> > > Kind Regards, >>>> > > Bogdan >>>> > > >>>> > > P.S.: Using the PVDReader from python code works >>>> flawlessly, which is also quite confusing, as to why it would fail in the >>>> C++ code. >>>> > > >>>> > > -- >>>> > > Bogdan Daqui >>>> > > Software Development >>>> > > >>>> > > SimScale GmbH >>>> > > Lichtenbergstra?e 8 >>>> > > 85748 Garching bei M?nchen >>>> > > >>>> > > Phone: +49 (0)89 3398 4078 >>>> > > Email: bdaqui at simscale.de >>>> > >>>> >>> >>> >> >>>> > > >>>> > > Amtsgericht M?nchen, HRB 201813 >>>> > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny >>>> > > >>>> > > http://www.simscale.de >>>> > > _______________________________________________ >>>> > > Powered by www.kitware.com >>>> >>>> > > >>>> > > Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> > > >>>> > > Please keep messages on-topic and check the ParaView >>>> Wiki at: http://paraview.org/Wiki/ParaView >>>> > > >>>> > > Follow this link to subscribe/unsubscribe: >>>> > > http://public.kitware.com/mailman/listinfo/paraview >>>> > > >>>> > > >>>> > >>>> > >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Powered by www.kitware.com >>>> >>>> Visit other Kitware open-source projects at >>>> http://www.kitware.com/opensource/opensource.html >>>> >>>> Please keep messages on-topic and check the ParaView Wiki at: >>>> http://paraview.org/Wiki/ParaView >>>> >>>> Follow this link to subscribe/unsubscribe: >>>> http://public.kitware.com/mailman/listinfo/paraview > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From bdaqui at simscale.de Mon Oct 27 11:29:20 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Mon, 27 Oct 2014 16:29:20 +0100 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> <544A7AF2.7070603@lbl.gov> <544E24C8.302@simscale.de> <544E6157.7030507@lbl.gov> Message-ID: <544E64D0.40603@simscale.de> Burlen, Uktarsh, Thanks for the clarification. I will give this a try and write back. This might actually also help me with another problem I am having at setting the timestep for which I want to fetch cell/point data. This also has to be done from the pipeline object, right? Kind Regards, Bogdan On 10/27/2014 04:24 PM, Utkarsh Ayachit wrote: > Bogdan, > > The deal is this: the vtkPVDReader is designed for ParaView, it uses > some of the core client-server infrastructure in ParaView. Thus, you > can't use it directly is a VTK-based C++ executable without > initializing ParaView environment. Initializing ParaView environment > is not too complicated. Look at pvserver_common.h or pvpython.h, it > should give you the necessary code. You basically use > vtkInitializationHelper API to initialize the ParaView environment. > > Hope that helps, > > Utkarsh > > > On Mon, Oct 27, 2014 at 11:14 AM, Burlen Loring wrote: >> Unless something's changed in the pipeline recently that I'm unaware of, >> when dealing with multiblock data you still need to force the composite data >> pipeline first. that may or or may not be the cause of your segfault, but >> you need to do it. >> >> >> On 10/27/2014 03:56 AM, Bogdan Daqui Herrera wrote: >>> >>> Hi Burlen, >>> >>> Yes, it is a stand-alone C++ application, which makes use of VTK and >>> Paraview as libraries, linking against them and calling functionality to >>> interpret the data. >>> I am not setting up any pipeline (as of now). Is this from the >>> TestExodusTime or TestTemporalFractal examples. I will try adding this. >>> >>> Currently I need to read and traverse the dataset without adding any >>> filters or processing the data. I it still needed to create a pipeline in >>> this case? >>> >>> Kind regards, >>> Bogdan >>> >>> On 10/24/2014 06:14 PM, Burlen Loring wrote: >>>> >>>> Hi Bogdan, >>>> >>>> You are writing a stand alone C++ app right? Are you setting up to run >>>> the composite data pipeline as in the following example? >>>> >>>> 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); >>>> 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); >>>> 102 cexec->Delete(); >>>> >>>> Burlen >>>> >>>> On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: >>>>> >>>>> Thanks Bogdan, >>>>> >>>>> that's not helping me but someone else might have some idea. >>>>> >>>>> Seb >>>>> >>>>> On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera >>>>> > wrote: >>>>> >>>>> Certainly. I should mention, I am using a pre-compiled version of >>>>> Paraview 4.1 bundled with Salome (Ubuntu package). >>>>> >>>>> Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): >>>>> ERROR: In >>>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, >>>>> line 316 >>>>> vtkPVDReader (0x6559e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> >>>>> Program received signal SIGSEGV, Segmentation fault. >>>>> 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >>>>> from >>>>> /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>>> #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() >>>>> () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>>> #1 0x00007ffff68cc128 in >>>>> vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, >>>>> vtkInformationVector*) () from >>>>> >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>>> #2 0x00007ffff68cd35d in >>>>> vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, >>>>> vtkInformationVector*) () from >>>>> >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>>> #3 0x00007ffff7b97fd0 in >>>>> vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, >>>>> vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #4 0x00007ffff7b93447 in >>>>> vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #5 0x00007ffff7b91181 in >>>>> vtkCompositeDataPipeline::ExecuteData(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #6 0x00007ffff7b95bb1 in >>>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #7 0x00007ffff7ba8c21 in >>>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) >>>>> () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #9 0x00007ffff7ba9765 in >>>>> vtkStreamingDemandDrivenPipeline::Update(int) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, >>>>> fileName=..., pMultiBlockDataSet=...) >>>>> at /home/.../someProject/src/testing.cpp:85 >>>>> >>>>> >>>>> Please let me know if you need something additional >>>>> On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: >>>>> > If you provide the stack trace, that may be helpful. >>>>> > >>>>> > Seb >>>>> > >>>>> > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera >>>>> >>>> >> wrote: >>>>> > >>>>> > Hi Seb, >>>>> > >>>>> > Thanks for the quick reply. Yes the project is managed with >>>>> CMake. I have not however been able to find the relevant posts by Marcus (in >>>>> the users >>>>> list). Is >>>>> > that in the users or developers mailing list? >>>>> > >>>>> > It does sound like it could be a problem with some >>>>> initialization, as you can see below. >>>>> > >>>>> > One short update, it looks like setting >>>>> ForceMultiBlockDataSet Output with: >>>>> > pReader->SetForceOutputTypeToMultiBlock(1); >>>>> > leads to the segmentation fault at Update() (The deepcopy is >>>>> never reached). With or without setting the previous line, the error >>>>> > vtkPVDReader (0x1cb49e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> > >>>>> > The code looks like this now: >>>>> > vtkSmartPointer < vtkPVDReader > pReader = >>>>> vtkSmartPointer < vtkPVDReader >::New(); >>>>> > pReader->SetFileName("/some/file.pvd"); >>>>> > pReader->Update(); (where the error is triggered) >>>>> > >>>>> > Kind Regards, >>>>> > Bogdan >>>>> > >>>>> > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: >>>>> > > Hi Bogdan, >>>>> > > >>>>> > > here are some issue in your code: >>>>> > > >>>>> > > vtkSmartPointer pReader = >>>>> vtkPVDReader::New(); // <== Memory LEAK >>>>> > > // Should be either >>>>> > > // vtkNew pReader; >>>>> > > // vtkSmartPointer pReader = >>>>> vtkSmartPointer::New() >>>>> > > >>>>> > > Then here on a "NULL" object you try to call a method. >>>>> > > >>>>> > > vtkMultiBlockDataSet* >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Should be something like that: >>>>> > > >>>>> > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; >>>>> > > >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Then you might have some other issue where pReader output >>>>> being empty/null, but for that I don't know. >>>>> > > >>>>> > > Are you managing your project with CMake? Did you include >>>>> the necessary file with the proper dependency declaration. This seems to be >>>>> related to >>>>> the factory not >>>>> > > being properly initialized. You can search the mailing >>>>> list, Marcus did answer several questions about that. >>>>> > > >>>>> > > Seb >>>>> > > >>>>> > > >>>>> > > >>>>> > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera >>>>> >>>> > >>>> >>>>> > >>> >>>>> wrote: >>>>> > > >>>>> > > Hello all, >>>>> > > >>>>> > > I am attempting to write some code in c++ which uses >>>>> the vtkPVDReader from the paraview library to read a series of vtm files. >>>>> However I am >>>>> > encountering some >>>>> > > problems and I am not sure whether there is something I >>>>> am missing or whether this could be a bug. >>>>> > > >>>>> > > I am trying to use the reader in the following manner: >>>>> > > My Code: >>>>> > > vtkSmartPointer pReader = >>>>> vtkPVDReader::New(); >>>>> > > pReader->SetForceOutputTypeToMultiBlock(1); >>>>> > > pReader->SetFileName("/some/fileName.pvd"); >>>>> > > pReader->Update(); >>>>> > > vtkMultiBlockDataSet* >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Error: >>>>> > > The error occurs at Update() with the following >>>>> result: >>>>> > > ERROR: In >>>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default >>>>> > > /vtkXMLCollectionReader.cxx, line 316 >>>>> > > vtkPVDReader (0x224d9e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> > > Segmentation fault >>>>> > > >>>>> > > Possible error Source >>>>> > > The code concerning line 316 from >>>>> vtkXMLCollectionReader.cxx is: >>>>> > > >>>>> > > // Use the instantiator to create the reader. >>>>> > > vtkObject* o = >>>>> vtkPVInstantiator::CreateInstance(rname); >>>>> > > vtkXMLReader* reader = >>>>> vtkXMLReader::SafeDownCast(o); >>>>> > > this->Internal->Readers[index] = reader; >>>>> > > if(reader) >>>>> > > { >>>>> > > reader->Delete(); >>>>> > > } >>>>> > > else >>>>> > > { >>>>> > > // The class was not registered with the >>>>> instantiator. >>>>> > > vtkErrorMacro("Error creating \"" << rname >>>>> > > << "\" using >>>>> vtkPVInstantiator."); >>>>> > > if(o) >>>>> > > { >>>>> > > o->Delete(); >>>>> > > } >>>>> > > } >>>>> > > } >>>>> > > >>>>> > > I have isolated the following lines and tested them >>>>> independently: >>>>> > > vtkObject* o = >>>>> vtkPVInstantiator::CreateInstance(rname); >>>>> > > vtkXMLReader* reader = >>>>> vtkXMLReader::SafeDownCast(o); >>>>> > > >>>>> > > The pointer "vtkObject* o" is NULL regardless of the >>>>> class name I pass to instantiate, and I can imagine something like that >>>>> happening in the >>>>> library, >>>>> > too and >>>>> > > causing the segmentation fault, when calling a >>>>> SafeDownCast(o) (which is NULL). >>>>> > > >>>>> > > >>>>> > > Any suggestions on how to deal with this problem or if >>>>> you would be so kind to point me to an example for an alternative solution >>>>> (Could be >>>>> > vtkFileSeriesReader, >>>>> > > but this fails, as well in my case) would be >>>>> appreciated. >>>>> > > >>>>> > > Kind Regards, >>>>> > > Bogdan >>>>> > > >>>>> > > P.S.: Using the PVDReader from python code works >>>>> flawlessly, which is also quite confusing, as to why it would fail in the >>>>> C++ code. >>>>> > > >>>>> > > -- >>>>> > > Bogdan Daqui >>>>> > > Software Development >>>>> > > >>>>> > > SimScale GmbH >>>>> > > Lichtenbergstra?e 8 >>>>> > > 85748 Garching bei M?nchen >>>>> > > >>>>> > > Phone: +49 (0)89 3398 4078 >>>>> > > Email: bdaqui at simscale.de >>>>> > >>>>> >>>> >>>> >> >>>>> > > >>>>> > > Amtsgericht M?nchen, HRB 201813 >>>>> > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny >>>>> > > >>>>> > > http://www.simscale.de >>>>> > > _______________________________________________ >>>>> > > Powered by www.kitware.com >>>>> >>>>> > > >>>>> > > Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> > > >>>>> > > Please keep messages on-topic and check the ParaView >>>>> Wiki at: http://paraview.org/Wiki/ParaView >>>>> > > >>>>> > > Follow this link to subscribe/unsubscribe: >>>>> > > http://public.kitware.com/mailman/listinfo/paraview >>>>> > > >>>>> > > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From burlen.loring at gmail.com Mon Oct 27 12:11:54 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Mon, 27 Oct 2014 09:11:54 -0700 Subject: [Paraview] Paravew on XC30 In-Reply-To: References: <544E5E1B.8080608@lbl.gov> Message-ID: <544E6ECA.3010408@gmail.com> Hi Rick, It doesn't look like you're building for the compute nodes, either that or you've got GPU's. for example Qt is on and OSMesa is off. I'm unfamiliar with the superbuild process but normally that would produce a binary that couldn't be run on the compute node without gpu's. I'm expecting my installs to work with the Kitware provided client binaries. For that in the past at least we need to match their build options to some some extent. For example the VisIt bridge would be on. I know there have been some updates to how the server capabilities are exposed so I'm not sure how much of an issue that is in 4.2. Burlen On 10/27/2014 08:22 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) wrote: > Chris - I?ve been able to build on 3 different XC30 systems ? here?s my > script. I?m using > PrgEnv-gnu/5.2.14 > cray-mpich/6.3.1 > gcc/4.8.2 > > > > #!/bin/csh > > module unload PrgEnv-cray > module load PrgEnv-gnu > module load cray-mpich > module load pbs > module list > > > setenv gcc "gcc" > setenv gplusplus "g++" > setenv gfortran "gfortran" > > setenv CC $gcc > setenv CXX $gplusplus > setenv FC $gfortran > setenv F70 $gfortran > setenv F77 $gfortran > setenv F90 $gfortran > setenv F95 $gfortran > > set version=4.2.0 > > if (! -d Build_${version}_mesa) mkdir Build_${version}_mesa > > cd Build_${version}_mesa > > if (! -d install) mkdir install > > set INSTALLPATH=`pwd`/install > > #Build the latest version of CMAKE > if (! -e install/bin/cmake) then > echo "Need to build cmake" > cp ../Downloads/cmake-2.8.11.tar.gz . > tar xzvf cmake-2.8.11.tar.gz > cd cmake-2.8.11 > ./bootstrap --prefix=$INSTALLPATH > make -j 8 install > cd .. > endif > > setenv PATH ${INSTALLPATH}/bin:$PATH > > cmake \ > -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_mesa \ > -DCMAKE_BUILD_TYPE=Release \ > -DParaView_FROM_GIT=OFF \ > -Ddownload_location=`pwd`/../Downloads \ > -DParaView_URL=`pwd`/../Downloads/ParaView-v4.2.0-source.tar.gz \ > -DENABLE_boost=ON \ > -DENABLE_cgns=OFF \ > -DENABLE_ffmpeg=ON \ > -DENABLE_fontconfig=ON \ > -DENABLE_freetype=ON \ > -DENABLE_hdf5=ON \ > -DENABLE_libxml2=ON \ > -DENABLE_matplotlib=OFF \ > -DENABLE_osmesa=OFF \ > -DENABLE_mesa=ON \ > -DENABLE_qt=ON \ > -DENABLE_mpi=ON \ > -DENABLE_numpy=ON \ > -DENABLE_paraview=ON \ > -DENABLE_png=ON \ > -DENABLE_python=ON \ > -DENABLE_qhull=ON \ > -DENABLE_silo=ON \ > -DENABLE_szip=ON \ > -DENABLE_visitbridge=OFF \ > -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp > ichcxx.so" \ > -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic > h.so" \ > -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpichc > xx.so" \ > -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ > e/" \ > -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/ > " \ > -DUSE_SYSTEM_mpi=ON \ > -DUSE_SYSTEM_python=ON \ > -DUSE_SYSTEM_zlib=ON \ > ../Source > > make -j 4 install > > ________________________________ > Rick Angelini > USArmy Research Laboratory > CISD/HPC Architectures Team > Phone: 410-278-6266 > > > > > On 10/27/14, 11:00 AM, "Burlen Loring" wrote: > >> >> >> Hi Christopher, >> >> I can't help you with the superbuild, but I can show you how to build PV >> on the XC30. here's >> >> the script >> > lds/config-pv-mesa.sh> I used to build ParaView 4.2 with >> PrgEnv-gnu/5.2.25 on our XC30 >> >> You'll see a bunch of paths that need to be set specific to the version >> of PrgEnv-gnu that you are running. The easiest way to figure out these >> is to look at the CRAY_LD_LIBRARY_PATH environment variable. If for some >> reason that isn't set then you can alway >> look at the output of "CC --verbose". You also need to point to an >> OSMesa install >> . >> >> Burlen >> >> On 10/26/2014 10:22 PM, R C Bording wrote: >> >> >> Hi, >> Trying to build Paraview on our XC30, >> here is the end of the build log where it goes pear-shape, >> >> Making install in test >> /usr/bin/install -c -m 644 fonts.dtd >> '/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2 >> .0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts' >> /usr/bin/install -c -m 644 ./fonts.conf >> /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >> 0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf >> /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >> 0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >> /usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs >> /usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction >> /group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4.2. >> 0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >> make[5]: *** [install-data-local] Error 132 >> make[4]: *** [install-am] Error 2 >> make[3]: *** [install-recursive] Error 1 >> make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] Error 2 >> make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2 >> make: *** [all] Error 2 >> >> Here is the cmake build flags for the paraviewsuperbuild script. >> >> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >> -DParaView_FROM_GIT=OFF \ >> -DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \ >> -DENABLE_boost=ON \ >> -DENABLE_cgns=OFF \ >> -DENABLE_ffmpeg=ON \ >> -DENABLE_fontconfig=ON \ >> -DENABLE_freetype=ON \ >> -DENABLE_hdf5=ON \ >> -DENABLE_libxml2=ON \ >> -DENABLE_matplotlib=OFF \ >> -DENABLE_mesa=OFF \ >> -DENABLE_mpi=ON \ >> -DENABLE_numpy=ON \ >> -DENABLE_osmesa=ON \ >> -DENABLE_paraview=ON \ >> -DENABLE_png=ON \ >> -DENABLE_python=ON \ >> -DENABLE_qhull=ON \ >> -DENABLE_qt=OFF \ >> -DENABLE_silo=ON \ >> -DENABLE_szip=ON \ >> -DENABLE_visitbridge=ON \ >> -DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libm >> pichcxx.so" \ >> -DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/mpt/lib/li >> bmpich.so" \ >> -DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpich >> cxx.so" \ >> -DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/inclu >> de" \ >> -DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/include >> " \ >> -DUSE_SYSTEM_mpi=ON \ >> -DUSE_SYSTEM_python=OFF \ >> -DUSE_SYSTEM_zlib=ON ' >> >> Is there other CRAY specific libraries that I should check for before I >> try again to install paraview? >> Our Cray does NOT have any GPUS! >> >> R. Christopher Bording >> Supercomputing Team-iVEC at UWA >> E: cbording at ivec.org >> T: +61 8 6488 6905 >> >> >> 26 Dick Perry Avenue, >> Technology Park >> Kensington, Western Australia. >> 6151 >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> >> > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From cbording at ivec.org Mon Oct 27 12:12:25 2014 From: cbording at ivec.org (R C Bording) Date: Tue, 28 Oct 2014 00:12:25 +0800 Subject: [Paraview] paraview performance Message-ID: Hi, Is there a rendering model that you have for testing the performance of the paraview? I have install paraview on our GPU cluster and would like validated it someway other than just putting timing calls around the Render command in the parallelSphere.py script. Or is that sufficient? Cheers, Chris B R. Christopher Bording Supercomputing Team-iVEC at UWA E: cbording at ivec.org T: +61 8 6488 6905 26 Dick Perry Avenue, Technology Park Kensington, Western Australia. 6151 -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.c.angelini.civ at mail.mil Mon Oct 27 12:14:45 2014 From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY ARL (US)) Date: Mon, 27 Oct 2014 16:14:45 +0000 Subject: [Paraview] Paravew on XC30 In-Reply-To: <544E6ECA.3010408@gmail.com> References: <544E5E1B.8080608@lbl.gov> <544E6ECA.3010408@gmail.com> Message-ID: Yeah - I have two builds - one for the login nodes and one for the compute nodes ? yeah, I included the login node build - but the structure is essentially the same. ________________________________ Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 On 10/27/14, 12:11 PM, "Burlen Loring" wrote: >Hi Rick, > >It doesn't look like you're building for the compute nodes, either that >or you've got GPU's. for example Qt is on and OSMesa is off. I'm >unfamiliar with the superbuild process but normally that would produce a >binary that couldn't be run on the compute node without gpu's. > >I'm expecting my installs to work with the Kitware provided client >binaries. For that in the past at least we need to match their build >options to some some extent. For example the VisIt bridge would be on. I >know there have been some updates to how the server capabilities are >exposed so I'm not sure how much of an issue that is in 4.2. > >Burlen > >On 10/27/2014 08:22 AM, Angelini, Richard C (Rick) CIV USARMY ARL (US) >wrote: >> Chris - I?ve been able to build on 3 different XC30 systems ? here?s my >> script. I?m using >> PrgEnv-gnu/5.2.14 >> cray-mpich/6.3.1 >> gcc/4.8.2 >> >> >> >> #!/bin/csh >> >> module unload PrgEnv-cray >> module load PrgEnv-gnu >> module load cray-mpich >> module load pbs >> module list >> >> >> setenv gcc "gcc" >> setenv gplusplus "g++" >> setenv gfortran "gfortran" >> >> setenv CC $gcc >> setenv CXX $gplusplus >> setenv FC $gfortran >> setenv F70 $gfortran >> setenv F77 $gfortran >> setenv F90 $gfortran >> setenv F95 $gfortran >> >> set version=4.2.0 >> >> if (! -d Build_${version}_mesa) mkdir Build_${version}_mesa >> >> cd Build_${version}_mesa >> >> if (! -d install) mkdir install >> >> set INSTALLPATH=`pwd`/install >> >> #Build the latest version of CMAKE >> if (! -e install/bin/cmake) then >> echo "Need to build cmake" >> cp ../Downloads/cmake-2.8.11.tar.gz . >> tar xzvf cmake-2.8.11.tar.gz >> cd cmake-2.8.11 >> ./bootstrap --prefix=$INSTALLPATH >> make -j 8 install >> cd .. >> endif >> >> setenv PATH ${INSTALLPATH}/bin:$PATH >> >> cmake \ >> -DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv-test/${version}_mesa \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DParaView_FROM_GIT=OFF \ >> -Ddownload_location=`pwd`/../Downloads \ >> -DParaView_URL=`pwd`/../Downloads/ParaView-v4.2.0-source.tar.gz \ >> -DENABLE_boost=ON \ >> -DENABLE_cgns=OFF \ >> -DENABLE_ffmpeg=ON \ >> -DENABLE_fontconfig=ON \ >> -DENABLE_freetype=ON \ >> -DENABLE_hdf5=ON \ >> -DENABLE_libxml2=ON \ >> -DENABLE_matplotlib=OFF \ >> -DENABLE_osmesa=OFF \ >> -DENABLE_mesa=ON \ >> -DENABLE_qt=ON \ >> -DENABLE_mpi=ON \ >> -DENABLE_numpy=ON \ >> -DENABLE_paraview=ON \ >> -DENABLE_png=ON \ >> -DENABLE_python=ON \ >> -DENABLE_qhull=ON \ >> -DENABLE_silo=ON \ >> -DENABLE_szip=ON \ >> -DENABLE_visitbridge=OFF \ >> >>-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/lib >>mp >> ichcxx.so" \ >> >>-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmp >>ic >> h.so" \ >> >>-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/lib/libmpic >>hc >> xx.so" \ >> >>-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/incl >>ud >> e/" \ >> >>-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/includ >>e/ >> " \ >> -DUSE_SYSTEM_mpi=ON \ >> -DUSE_SYSTEM_python=ON \ >> -DUSE_SYSTEM_zlib=ON \ >> ../Source >> >> make -j 4 install >> >> ________________________________ >> Rick Angelini >> USArmy Research Laboratory >> CISD/HPC Architectures Team >> Phone: 410-278-6266 >> >> >> >> >> On 10/27/14, 11:00 AM, "Burlen Loring" wrote: >> >>> >>> >>> Hi Christopher, >>> >>> I can't help you with the superbuild, but I can show you how to build >>>PV >>> on the XC30. here's >>> >>> the script >>> >>>>>ui >>> lds/config-pv-mesa.sh> I used to build ParaView 4.2 with >>> PrgEnv-gnu/5.2.25 on our XC30 >>> >>> You'll see a bunch of paths that need to be set specific to the version >>> of PrgEnv-gnu that you are running. The easiest way to figure out these >>> is to look at the CRAY_LD_LIBRARY_PATH environment variable. If for >>>some >>> reason that isn't set then you can alway >>> look at the output of "CC --verbose". You also need to point to an >>> OSMesa install >>> . >>> >>> Burlen >>> >>> On 10/26/2014 10:22 PM, R C Bording wrote: >>> >>> >>> Hi, >>> Trying to build Paraview on our XC30, >>> here is the end of the build log where it goes pear-shape, >>> >>> Making install in test >>> /usr/bin/install -c -m 644 fonts.dtd >>> >>>'/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4 >>>.2 >>> .0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts' >>> /usr/bin/install -c -m 644 ./fonts.conf >>> >>>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4. >>>2. >>> 0/ParaViewSuperbuild-4.2.0-build/install/etc/fonts/fonts.conf >>> >>>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4. >>>2. >>> 0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >>> /usr/share/fonts: caching, new cache contents: 0 fonts, 10 dirs >>> /usr/share/fonts/100dpi: /bin/sh: line 9: 16194 Illegal instruction >>> >>>/group/director100/cbording/vis/cle52/build/osmesa-ParaViewSuperbuild-4. >>>2. >>> 0/ParaViewSuperbuild-4.2.0-build/install/bin/fc-cache -s -f -v >>> make[5]: *** [install-data-local] Error 132 >>> make[4]: *** [install-am] Error 2 >>> make[3]: *** [install-recursive] Error 1 >>> make[2]: *** [fontconfig/src/fontconfig-stamp/fontconfig-install] >>>Error 2 >>> make[1]: *** [CMakeFiles/fontconfig.dir/all] Error 2 >>> make: *** [all] Error 2 >>> >>> Here is the cmake build flags for the paraviewsuperbuild script. >>> >>> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >>> -DParaView_FROM_GIT=OFF \ >>> -DParaView_URL=$MYGROUP/vis/cle52/src/ParaView-v4.2.0-source.tar.gz \ >>> -DENABLE_boost=ON \ >>> -DENABLE_cgns=OFF \ >>> -DENABLE_ffmpeg=ON \ >>> -DENABLE_fontconfig=ON \ >>> -DENABLE_freetype=ON \ >>> -DENABLE_hdf5=ON \ >>> -DENABLE_libxml2=ON \ >>> -DENABLE_matplotlib=OFF \ >>> -DENABLE_mesa=OFF \ >>> -DENABLE_mpi=ON \ >>> -DENABLE_numpy=ON \ >>> -DENABLE_osmesa=ON \ >>> -DENABLE_paraview=ON \ >>> -DENABLE_png=ON \ >>> -DENABLE_python=ON \ >>> -DENABLE_qhull=ON \ >>> -DENABLE_qt=OFF \ >>> -DENABLE_silo=ON \ >>> -DENABLE_szip=ON \ >>> -DENABLE_visitbridge=ON \ >>> >>>-DMPI_CXX_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/li >>>bm >>> pichcxx.so" \ >>> >>>-DMPI_C_LIBRARIES:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/mpt/lib/ >>>li >>> bmpich.so" \ >>> >>>-DMPI_LIBRARY:FILEPATH="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/lib/libmpi >>>ch >>> cxx.so" \ >>> >>>-DMPI_CXX_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/inc >>>lu >>> de" \ >>> >>>-DMPI_C_INCLUDE_PATH:STRING="/opt/cray/mpt/7.0.0/gni/mpich2-gnu/49/inclu >>>de >>> " \ >>> -DUSE_SYSTEM_mpi=ON \ >>> -DUSE_SYSTEM_python=OFF \ >>> -DUSE_SYSTEM_zlib=ON ' >>> >>> Is there other CRAY specific libraries that I should check for before I >>> try again to install paraview? >>> Our Cray does NOT have any GPUS! >>> >>> R. Christopher Bording >>> Supercomputing Team-iVEC at UWA >>> E: cbording at ivec.org >>> T: +61 8 6488 6905 >>> >>> >>> 26 Dick Perry Avenue, >>> Technology Park >>> Kensington, Western Australia. >>> 6151 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >>> >>> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >>http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >>http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Mon Oct 27 13:11:57 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Mon, 27 Oct 2014 17:11:57 +0000 Subject: [Paraview] pvserver test on different systems (UNCLASSIFIED) In-Reply-To: References: , Message-ID: Utkarsh, thanks again for your help. I think I have all I need now... thanks -simon ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Monday, October 27, 2014 10:10 AM To: Su, Simon M CTR USARMY ARL (US) Cc: paraview at paraview.org Subject: Re: [Paraview] pvserver test on different systems (UNCLASSIFIED) Simon, Although, explicit pvpython/pvbatch test isn't necessary, it's worth doing it since sometimes the paths to locate ParaView's Python modules can get messed up between different executables. > So for individual python packages, I will need to do the import test for all the packages I want to test in the script right? Yes, ideally. Utkarsh From grace.sdiwc at gmail.com Sun Oct 26 11:36:45 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:36:45 +0800 Subject: [Paraview] [Mycolleagues] CFP: ISDF2015 Conference in Malaysia Message-ID: *http://sdiwc.net/conferences/isdf2015/ * The Second International Conference on Information Security and Digital Forensics (ISDF2015) October 29-30 & Sep. 01, 2015 Asia Pacific University of Technology and Innovations (APU) Kuala Lumpur, Malaysia All registered papers will be included in SDIWC Digital Library. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The conference welcomes papers on the following (but not limited to) research topics: - Management of Semantic Web data and Linked Data - Semantic Sensor Networks - Database, IR, NLP and AI technologies for the Semantic Web - Search, query, integration, and analysis on the Semantic Web - Query and inference over data streams - Ontology-based data access - Semantic technologies for mobile platforms - Ontology engineering and ontology patterns for the Semantic Web - Ontology modularity, mapping, merging, and alignment - Social networks and processes on the Semantic Web - Semantic Web and Linked Data for Cloud Environments - Information visualization of Semantic Web data and Linked Data - Languages, tools, and methodologies for representing and managing Semantic Web data - Robust and scalable knowledge management and reasoning on the Web - Cleaning, assurance, and provenance of Semantic Web data, services, and processes - Information Extraction from unstructured data - Supporting multi-linguality in the Semantic Web - Geospatial Semantic Web - User Interfaces and interacting with Semantic Web data and Linked Data - Personalized access to Semantic Web data and applications Semantic Web technologies - The Latest Trends in Web Services - Cryptography for Enabling E-Commerce - E-Business Applications and Software - Business Technology Intelligence - Practices and Cases in E-Commerce - Computational Intelligence - Confidentiality Protection - Future Development of E-Business - Future Development of E-Business - Critical Computing and Storage - Customer Relationship Management - Information visualization of Semantic Web data and Linked Data - Digital Data Mining - Digital Economy - Digital Enterprises - Digital Innovation Management - Digital Libraries - Digital Management Products - Digital Economics, and Digital Content - Distributed and Parallel Applications - E-Communities - E-Learning - E-commerce business models - E-commerce Payment Systems - E-commerce Technology Adoption - E-commerce, E-Business Strategies - E-tailing and Multi-Channel selling - EDI and the Internet - Economics Issues of E-Commerce - Evolution of E-Commerce - Internet Payment Systems - M-commerce and Pervasive Computing - Production of Knowledge Economy - Semantic Web, Ontologies - Sensor Networks and Social Sensing - Trust or Security for E-Commerce - Web Applications - Web Advertising and Web Publishing - XML-Based Languages - Digital Economics, and Digital Content ---------------------------------------------------- Important Dates: Submission Dates : Open from now until September 27, 2015 Notification of Acceptance : 3- 4 weeks from the submission date Camera Ready Submission : Open from now until October 17, 2015 Registration : Open from now until October 17, 2015 ----------------------------------------------------- Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/isdf2015/paper-submission/ Write us for more details: isdf15 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Mycolleagues mailing list Mycolleagues at mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/mycolleagues - Through this link above you can "subscribe", "unsubscribe", or change your settings in the list, using "username=ufsc" and "password=ufsc". - If you need any help, please send a message to mycolleagues-owner at mailman.ufsc.br. - ENJOY this COURTESY offered by FEDERAL UNIVERSITY OF SANTA CATARINA. From grace.sdiwc at gmail.com Sun Oct 26 11:33:01 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:33:01 +0800 Subject: [Paraview] [Mycolleagues] CFP: CGMIP2014 Conference in Malaysia Message-ID: *http://sdiwc.net/conferences/2014/cgmip2014/ * The International Conference on Computer Graphics, Multimedia and Image Processing (CGMIP2014) November 17-19, 2014 Asia Pacific University of Technology and Innovation (APU) Kuala Lumpur, Malaysia All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: - 3D imaging - Case studies - Case studies and emerging technologies - Classification and clustering techniques - Color and texture - Compression methods - Computational geometry - Computer animation - Computer art and entertainment (including games) - Curves and meshes - e-Learning applications and computer graphics - Emerging display technologies - Emerging technologies - Face recognition, face detection, and gesture recognition - Fractal geometry and applications - Graph theory in image processing and vision - Graphics algorithms and applications - Haptic devices and techniques - Human-computer interfaces - Illumination and reflection techniques - Image compression, coding, and encryption - Image data structures for computer graphics - Image feature extraction - Image generation, acquisition, and processing - Image geometry and multi-view geometry - Image-based modeling and algorithms - Immersive virtual reality - Integration of virtual reality and multimedia - Interactive digital media - Interactive techniques - Knowledge-based recognition - Learning and assessment based on virtual reality approaches - Machine architectures/engines for graphics and VR - Machine learning technologies for vision - Modeling of natural scenes and phenomena - Modeling techniques - Multimedia Systems and Applications - Multimodal display systems - Object recognition - Real-time collision detection algorithms - Real-time rendering for VR - Rendering methods - Shadows, translucency and visibility - Signal and speech processing - Simulation and virtual reality - Software tools for computer graphics - Software tools for virtual reality - Sound rendering technologies - Surface modeling - Virtual and augmented reality - Virtual environments - Virtual humans and artificial life - Virtual laboratories - Virtual reality and emerging applications - Virtual reality software tools and languages - Virtual reality techniques for behavioral and cognitive assessment - Virtual reality, visualization, and education - Visual computing and graphics - Visualization - Web 3D and applications Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/2014/cgmip2014/paper-submission/ IMPORTANT DATES: Submission Deadline : Extended to Oct. 30, 2014 Notification of Acceptance : Nov. 04, 2014 Camera Ready Submission : Open from now until Nov. 07, 2014 Registration Date : Open from now until Nov. 07, 2014 Conference Dates : November 17-19, 2014 Write us for more details: cgmip2014 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Mycolleagues mailing list Mycolleagues at mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/mycolleagues - Through this link above you can "subscribe", "unsubscribe", or change your settings in the list, using "username=ufsc" and "password=ufsc". - If you need any help, please send a message to mycolleagues-owner at mailman.ufsc.br. - ENJOY this COURTESY offered by FEDERAL UNIVERSITY OF SANTA CATARINA. From grace.sdiwc at gmail.com Sun Oct 26 11:37:51 2014 From: grace.sdiwc at gmail.com (Grace Allas) Date: Sun, 26 Oct 2014 23:37:51 +0800 Subject: [Paraview] [Mycolleagues] CFP: DEIS2015 Conference in China Message-ID: *http://sdiwc.net/conferences/deis2015/ * The Third International Conference on Digital Enterprise and Information Systems (DEIS2015) April 16-18, 2015 Xueyuan Avenue 1068, Shenzhen University Town, Shenzhen, China All registered papers will be included in SDIWC Digital Library. ============================================================== The conference aims to enable researchers build connections between different digital applications. The event will be held over three days, with presentations delivered by researchers from the international community, including presentations from keynote speakers and state-of-the-art lectures. RESEARCH TOPICS ARE NOT LIMITED TO: - Access Controls - Anti-cyberterrorism - Assurance of Service - Biometrics Technologies - Cloud Computing - Computational Intelligence - Computer Crime Prevention and Detection - Computer Forensics - Computer Security - Confidentiality Protection - Critical Computing and Storage - Critical Infrastructure Management -Cryptography and Data Protection - Data Compression - Data Management in Mobile Peer-to-Peer Networks - Data Mining - Data Stream Processing in Mobile/Sensor Networks - Data and Information Quality - Distributed and Parallel Applications - E-Government, E-Learning and E-Technology - Embedded Systems and Software - Forensics, Recognition Technologies and Applications - Fuzzy and Neural Network Systems - Green Computing - Grid Computing Image Processing - Indexing and Query Processing for Moving Objects - Information Content Security - Information Ethics - Information Propagation on Social Networks - Information and Data Management - Internet Modeling - Mobile Networking, Mobility and Nomadicity - Mobile Social Networks - Mobile, Ad Hoc and Sensor Network Management - Multimedia Computing - Network Security - Peer-to-Peer Social Networks - Quality of Service, Scalability and Performance - Real-Time Systems - Resource and Knowledge Discovery Using Social Networks - Self-Organizing Networks and Networked Systems - Semantic Web, Ontologies - Sensor Networks and Social Sensing - Signal Processing, Pattern Recognition and Applications - Social Networks - Social Search - Soft Computing Techniques - Software Engineeing - Ubiquitous Computing, Services and Applications - User Interfaces and Usability Issues form Mobile Applications - User Interfaces, Visualization and Modeling - Web Services Architecture, Modeling and Design - Web Services Security - Wireless Communications - XML-Based Languages Researchers are encouraged to submit their work electronically. All papers will be fully refereed by a minimum of two specialized referees. Before final acceptance, all referees comments must be considered. Paper Submission: http://sdiwc.net/conferences/deis2015/openconf/openconf.php IMPORTANT DATES: Submission Deadline : open from now until March 16, 2015 Notification of Acceptance : 2 - 4 weeks from the submission date Camera Ready Submission : Open from from now April 06, 2015 Registration Date : Open from now until April 06, 2015 Conference Dates : April 16-18, 2015 Contact email: : deis15 at sdiwc.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ Mycolleagues mailing list Mycolleagues at mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/mycolleagues - Through this link above you can "subscribe", "unsubscribe", or change your settings in the list, using "username=ufsc" and "password=ufsc". - If you need any help, please send a message to mycolleagues-owner at mailman.ufsc.br. - ENJOY this COURTESY offered by FEDERAL UNIVERSITY OF SANTA CATARINA. From cbording at ivec.org Tue Oct 28 05:52:19 2014 From: cbording at ivec.org (R C Bording) Date: Tue, 28 Oct 2014 17:52:19 +0800 Subject: [Paraview] HPC paraview In-Reply-To: <544E6049.6000003@lbl.gov> References: <544E6049.6000003@lbl.gov> Message-ID: <45C5063E-EB1E-457A-8EDD-948BF1046C34@ivec.org> HI Burlen, Yes I am for the purpose of testing on our debug queue. But you are bang on with setting the DISPLAY environment variable. so setting in the preview module setenv LIBGL_ALWAYS_INDIRECT 1 or in bash in the job script export LIBGL_ALWAYS_INDIRECT 1 but also adding export DISPLAY=:1 is needed to render on the GPU. Renders the parallelSphere.py example with no errors across multiple nodes. my mpirun command looks like this mpirun pvbatch parallelSphere.py note we have PBSpro installed so it determines the -np ##-number of processors/cores based on the #PBS -l select=..... So now to see if I can render something awesome! Chris B On 27/10/2014, at 11:10 PM, Burlen Loring wrote: > Hi Christopher, > > Are you by any chance logged in with ssh X11 forwarding (ssh -X ...)? It seems the error you report comes up often in that context. X forwarding would not be the right way to run PV on your cluster. > > Depending on how your cluster is setup you may need to start up the xserver before launching PV, and make sure to close it after PV exits. IUn that scenario your xorg.conf would specify the nvidia driver and a screen for each gpu which you would refernece in the shell used to start PV through the DISPLAY variable. If you already have x11 running and screens configured then it's just a matter of setting the display variable correctly. When there are multiple GPU's per node then you'd need to set the display using mpi rank modulo the number of gpus per node. > > I'm not sure it matters that much but I don't think that you want --use-offscreen-rendering option. > > Burlen > > On 10/26/2014 10:23 PM, R C Bording wrote: >> Hi, >> Managed to get a "working version of Paraview-4.2.0.1" on our GPU cluster but when I try to run the >> parallelSphere.py script on more than one node it just hangs. Work like it is supposed to up to 12 cores on a single node. I am still trying work out if I a running on the GPU "tesla- C2070). >> >> Here is the list of cake configurations >> >> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >> -DParaView_FROM_GIT=OFF \ >> -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ >> -DENABLE_boost=ON \ >> -DENABLE_cgns=OFF \ >> -DENABLE_ffmpeg=ON \ >> -DENABLE_fontconfig=ON \ >> -DENABLE_freetype=ON \ >> -DENABLE_hdf5=ON \ >> -DENABLE_libxml2=ON \ >> -DENABLE_matplotlib=ON \ >> -DENABLE_mesa=OFF \ >> -DENABLE_mpi=ON \ >> -DENABLE_numpy=ON \ >> -DENABLE_osmesa=OFF \ >> -DENABLE_paraview=ON \ >> -DENABLE_png=ON \ >> -DENABLE_python=ON \ >> -DENABLE_qhull=ON \ >> -DENABLE_qt=ON \ >> -DENABLE_silo=ON \ >> -DENABLE_szip=ON \ >> -DENABLE_visitbridge=ON \ >> -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ >> -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ >> -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ >> -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >> -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >> -DUSE_SYSTEM_mpi=ON \ >> -DUSE_SYSTEM_python=OFF \ >> -DUSE_SYSTEM_qt=OFF \ >> -DUSE_SYSTEM_zlib=OFF ' >> >> The goal is to be able to support batch rendering on the whole cluster ~96 nodes. >> >> Also do I need set another environment variable in my Paraview module to make the Xlib >> warning go away? >> >> [cbording at f100 Paraview]$ mpirun -n 12 pvbatch --use-offscreen-rendering parallelSphere.py >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> >> Is this related to my not being able to run across multiple nodes? >> >> R. Christopher Bording >> Supercomputing Team-iVEC at UWA >> E: cbording at ivec.org >> T: +61 8 6488 6905 >> >> 26 Dick Perry Avenue, >> Technology Park >> Kensington, Western Australia. >> 6151 >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdaqui at simscale.de Tue Oct 28 11:04:08 2014 From: bdaqui at simscale.de (Bogdan Daqui Herrera) Date: Tue, 28 Oct 2014 16:04:08 +0100 Subject: [Paraview] Segmentation Fault when using the vtkPVDReader In-Reply-To: References: <54490222.9000809@simscale.de> <54492EA9.9020507@simscale.de> <544946CD.1080502@simscale.de> <544A7AF2.7070603@lbl.gov> <544E24C8.302@simscale.de> <544E6157.7030507@lbl.gov> Message-ID: <544FB068.4030008@simscale.de> Hi Uktarsh, Burlen, The PVD reader is finally working, thanks for the suggestions. Initializing the environment before using the PVDReader is what did the trick. Should it be useful to somebody else, you can use something akin to the following for initialization: static vtkSmartPointer options = vtkSmartPointer::New(); char** execName = new char*[1]; execName[0] = vtksys::SystemTools::DuplicateString("foobar_string"); vtkInitializationHelper::Initialize( 1, execName, vtkProcessModule::PROCESS_CLIENT, options ); Useful examples are pvserver_common.h, pvpython.h (as suggested by Uktarsh) as well as vtkCPCxxHelper.cxx. Is there any risk of a memory leak if the environment is initialized multiple times? For instance, if this is done within a class' constructor and this class is instantiated several times during program execution, or will this initialization be confined to the live of the object? Kind Regards, Bogdan On 10/27/2014 04:24 PM, Utkarsh Ayachit wrote: > Bogdan, > > The deal is this: the vtkPVDReader is designed for ParaView, it uses > some of the core client-server infrastructure in ParaView. Thus, you > can't use it directly is a VTK-based C++ executable without > initializing ParaView environment. Initializing ParaView environment > is not too complicated. Look at pvserver_common.h or pvpython.h, it > should give you the necessary code. You basically use > vtkInitializationHelper API to initialize the ParaView environment. > > Hope that helps, > > Utkarsh > > > On Mon, Oct 27, 2014 at 11:14 AM, Burlen Loring wrote: >> Unless something's changed in the pipeline recently that I'm unaware of, >> when dealing with multiblock data you still need to force the composite data >> pipeline first. that may or or may not be the cause of your segfault, but >> you need to do it. >> >> >> On 10/27/2014 03:56 AM, Bogdan Daqui Herrera wrote: >>> >>> Hi Burlen, >>> >>> Yes, it is a stand-alone C++ application, which makes use of VTK and >>> Paraview as libraries, linking against them and calling functionality to >>> interpret the data. >>> I am not setting up any pipeline (as of now). Is this from the >>> TestExodusTime or TestTemporalFractal examples. I will try adding this. >>> >>> Currently I need to read and traverse the dataset without adding any >>> filters or processing the data. I it still needed to create a pipeline in >>> this case? >>> >>> Kind regards, >>> Bogdan >>> >>> On 10/24/2014 06:14 PM, Burlen Loring wrote: >>>> >>>> Hi Bogdan, >>>> >>>> You are writing a stand alone C++ app right? Are you setting up to run >>>> the composite data pipeline as in the following example? >>>> >>>> 100 vtkCompositeDataPipeline* cexec=vtkCompositeDataPipeline::New(); >>>> 101 vtkAlgorithm::SetDefaultExecutivePrototype(cexec); >>>> 102 cexec->Delete(); >>>> >>>> Burlen >>>> >>>> On 10/23/2014 06:37 PM, Sebastien Jourdain wrote: >>>>> >>>>> Thanks Bogdan, >>>>> >>>>> that's not helping me but someone else might have some idea. >>>>> >>>>> Seb >>>>> >>>>> On Thu, Oct 23, 2014 at 12:19 PM, Bogdan Daqui Herrera >>>>> > wrote: >>>>> >>>>> Certainly. I should mention, I am using a pre-compiled version of >>>>> Paraview 4.1 bundled with Salome (Ubuntu package). >>>>> >>>>> Here it is (using pReader->SetForceOutputTypeToMultiBlock(1)): >>>>> ERROR: In >>>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default/vtkXMLCollectionReader.cxx, >>>>> line 316 >>>>> vtkPVDReader (0x6559e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> >>>>> Program received signal SIGSEGV, Segmentation fault. >>>>> 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() () >>>>> from >>>>> /opt/salomeUbuntu_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>>> #0 0x00007ffff65c4270 in vtkXMLCollectionReader::ReadXMLDataImpl() >>>>> () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkPVVTKExtensionsDefault-pv4.1.so.1 >>>>> #1 0x00007ffff68cc128 in >>>>> vtkXMLReader::RequestData(vtkInformation*, vtkInformationVector**, >>>>> vtkInformationVector*) () from >>>>> >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>>> #2 0x00007ffff68cd35d in >>>>> vtkXMLReader::ProcessRequest(vtkInformation*, vtkInformationVector**, >>>>> vtkInformationVector*) () from >>>>> >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkIOXML-pv4.1.so.1 >>>>> #3 0x00007ffff7b97fd0 in >>>>> vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, >>>>> vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #4 0x00007ffff7b93447 in >>>>> vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #5 0x00007ffff7b91181 in >>>>> vtkCompositeDataPipeline::ExecuteData(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #6 0x00007ffff7b95bb1 in >>>>> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #7 0x00007ffff7ba8c21 in >>>>> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, >>>>> vtkInformationVector**, vtkInformationVector*) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #8 0x00007ffff7b9486d in vtkDemandDrivenPipeline::UpdateData(int) >>>>> () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #9 0x00007ffff7ba9765 in >>>>> vtkStreamingDemandDrivenPipeline::Update(int) () >>>>> from >>>>> /opt/salome_740/ParaView-4.1.0/lib/paraview-4.1/libvtkCommonExecutionModel-pv4.1.so.1 >>>>> #10 0x0000000000414fbf in testing::TestingIO::read (this=0x652b30, >>>>> fileName=..., pMultiBlockDataSet=...) >>>>> at /home/.../someProject/src/testing.cpp:85 >>>>> >>>>> >>>>> Please let me know if you need something additional >>>>> On 10/23/2014 07:51 PM, Sebastien Jourdain wrote: >>>>> > If you provide the stack trace, that may be helpful. >>>>> > >>>>> > Seb >>>>> > >>>>> > On Thu, Oct 23, 2014 at 10:36 AM, Bogdan Daqui Herrera >>>>> >>>> >> wrote: >>>>> > >>>>> > Hi Seb, >>>>> > >>>>> > Thanks for the quick reply. Yes the project is managed with >>>>> CMake. I have not however been able to find the relevant posts by Marcus (in >>>>> the users >>>>> list). Is >>>>> > that in the users or developers mailing list? >>>>> > >>>>> > It does sound like it could be a problem with some >>>>> initialization, as you can see below. >>>>> > >>>>> > One short update, it looks like setting >>>>> ForceMultiBlockDataSet Output with: >>>>> > pReader->SetForceOutputTypeToMultiBlock(1); >>>>> > leads to the segmentation fault at Update() (The deepcopy is >>>>> never reached). With or without setting the previous line, the error >>>>> > vtkPVDReader (0x1cb49e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> > >>>>> > The code looks like this now: >>>>> > vtkSmartPointer < vtkPVDReader > pReader = >>>>> vtkSmartPointer < vtkPVDReader >::New(); >>>>> > pReader->SetFileName("/some/file.pvd"); >>>>> > pReader->Update(); (where the error is triggered) >>>>> > >>>>> > Kind Regards, >>>>> > Bogdan >>>>> > >>>>> > On 10/23/2014 04:47 PM, Sebastien Jourdain wrote: >>>>> > > Hi Bogdan, >>>>> > > >>>>> > > here are some issue in your code: >>>>> > > >>>>> > > vtkSmartPointer pReader = >>>>> vtkPVDReader::New(); // <== Memory LEAK >>>>> > > // Should be either >>>>> > > // vtkNew pReader; >>>>> > > // vtkSmartPointer pReader = >>>>> vtkSmartPointer::New() >>>>> > > >>>>> > > Then here on a "NULL" object you try to call a method. >>>>> > > >>>>> > > vtkMultiBlockDataSet* >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Should be something like that: >>>>> > > >>>>> > > vtkNew< vtkMultiBlockDataSet > pMultiBlockDataSet; >>>>> > > >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Then you might have some other issue where pReader output >>>>> being empty/null, but for that I don't know. >>>>> > > >>>>> > > Are you managing your project with CMake? Did you include >>>>> the necessary file with the proper dependency declaration. This seems to be >>>>> related to >>>>> the factory not >>>>> > > being properly initialized. You can search the mailing >>>>> list, Marcus did answer several questions about that. >>>>> > > >>>>> > > Seb >>>>> > > >>>>> > > >>>>> > > >>>>> > > On Thu, Oct 23, 2014 at 7:26 AM, Bogdan Daqui Herrera >>>>> >>>> > >>>> >>>>> > >>> >>>>> wrote: >>>>> > > >>>>> > > Hello all, >>>>> > > >>>>> > > I am attempting to write some code in c++ which uses >>>>> the vtkPVDReader from the paraview library to read a series of vtm files. >>>>> However I am >>>>> > encountering some >>>>> > > problems and I am not sure whether there is something I >>>>> am missing or whether this could be a bug. >>>>> > > >>>>> > > I am trying to use the reader in the following manner: >>>>> > > My Code: >>>>> > > vtkSmartPointer pReader = >>>>> vtkPVDReader::New(); >>>>> > > pReader->SetForceOutputTypeToMultiBlock(1); >>>>> > > pReader->SetFileName("/some/fileName.pvd"); >>>>> > > pReader->Update(); >>>>> > > vtkMultiBlockDataSet* >>>>> pMultiBlockDataSet->DeepCopy(vtkMultiBlockDataSet::SafeDownCast(pReader->GetOutputDataObject(0))); >>>>> > > >>>>> > > Error: >>>>> > > The error occurs at Update() with the following >>>>> result: >>>>> > > ERROR: In >>>>> /misc/dn47/SALOME/PRODUCTS/7x/opt/Ubuntu.13.10.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/VTKExtensions/Default >>>>> > > /vtkXMLCollectionReader.cxx, line 316 >>>>> > > vtkPVDReader (0x224d9e0): Error creating >>>>> "vtkXMLMultiBlockDataReader" using vtkPVInstantiator. >>>>> > > Segmentation fault >>>>> > > >>>>> > > Possible error Source >>>>> > > The code concerning line 316 from >>>>> vtkXMLCollectionReader.cxx is: >>>>> > > >>>>> > > // Use the instantiator to create the reader. >>>>> > > vtkObject* o = >>>>> vtkPVInstantiator::CreateInstance(rname); >>>>> > > vtkXMLReader* reader = >>>>> vtkXMLReader::SafeDownCast(o); >>>>> > > this->Internal->Readers[index] = reader; >>>>> > > if(reader) >>>>> > > { >>>>> > > reader->Delete(); >>>>> > > } >>>>> > > else >>>>> > > { >>>>> > > // The class was not registered with the >>>>> instantiator. >>>>> > > vtkErrorMacro("Error creating \"" << rname >>>>> > > << "\" using >>>>> vtkPVInstantiator."); >>>>> > > if(o) >>>>> > > { >>>>> > > o->Delete(); >>>>> > > } >>>>> > > } >>>>> > > } >>>>> > > >>>>> > > I have isolated the following lines and tested them >>>>> independently: >>>>> > > vtkObject* o = >>>>> vtkPVInstantiator::CreateInstance(rname); >>>>> > > vtkXMLReader* reader = >>>>> vtkXMLReader::SafeDownCast(o); >>>>> > > >>>>> > > The pointer "vtkObject* o" is NULL regardless of the >>>>> class name I pass to instantiate, and I can imagine something like that >>>>> happening in the >>>>> library, >>>>> > too and >>>>> > > causing the segmentation fault, when calling a >>>>> SafeDownCast(o) (which is NULL). >>>>> > > >>>>> > > >>>>> > > Any suggestions on how to deal with this problem or if >>>>> you would be so kind to point me to an example for an alternative solution >>>>> (Could be >>>>> > vtkFileSeriesReader, >>>>> > > but this fails, as well in my case) would be >>>>> appreciated. >>>>> > > >>>>> > > Kind Regards, >>>>> > > Bogdan >>>>> > > >>>>> > > P.S.: Using the PVDReader from python code works >>>>> flawlessly, which is also quite confusing, as to why it would fail in the >>>>> C++ code. >>>>> > > >>>>> > > -- >>>>> > > Bogdan Daqui >>>>> > > Software Development >>>>> > > >>>>> > > SimScale GmbH >>>>> > > Lichtenbergstra?e 8 >>>>> > > 85748 Garching bei M?nchen >>>>> > > >>>>> > > Phone: +49 (0)89 3398 4078 >>>>> > > Email: bdaqui at simscale.de >>>>> > >>>>> >>>> >>>> >> >>>>> > > >>>>> > > Amtsgericht M?nchen, HRB 201813 >>>>> > > Gesch?ftsf?hrer: Vincenz D?lle & David Heiny >>>>> > > >>>>> > > http://www.simscale.de >>>>> > > _______________________________________________ >>>>> > > Powered by www.kitware.com >>>>> >>>>> > > >>>>> > > Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> > > >>>>> > > Please keep messages on-topic and check the ParaView >>>>> Wiki at: http://paraview.org/Wiki/ParaView >>>>> > > >>>>> > > Follow this link to subscribe/unsubscribe: >>>>> > > http://public.kitware.com/mailman/listinfo/paraview >>>>> > > >>>>> > > >>>>> > >>>>> > >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Powered by www.kitware.com >>>>> >>>>> Visit other Kitware open-source projects at >>>>> http://www.kitware.com/opensource/opensource.html >>>>> >>>>> Please keep messages on-topic and check the ParaView Wiki at: >>>>> http://paraview.org/Wiki/ParaView >>>>> >>>>> Follow this link to subscribe/unsubscribe: >>>>> http://public.kitware.com/mailman/listinfo/paraview >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview From bloring at lbl.gov Tue Oct 28 11:57:04 2014 From: bloring at lbl.gov (Burlen Loring) Date: Tue, 28 Oct 2014 08:57:04 -0700 Subject: [Paraview] HPC paraview In-Reply-To: <45C5063E-EB1E-457A-8EDD-948BF1046C34@ivec.org> References: <544E6049.6000003@lbl.gov> <45C5063E-EB1E-457A-8EDD-948BF1046C34@ivec.org> Message-ID: <544FBCD0.4070708@lbl.gov> Hi Chris, your reply makes me suspicious that you may not really be rendering on your tesla yet. LIBGL_ALWAYS_INDIRECT should not be needed and as far as I know this is a Mesa specific variable. Even in an interactive batch job you shouldn't use x11 forwarding for ParaView (I couldn't tell if you are using it or not, but I wanted to be clear about that because it doesn't scale well). If I were you I'd verify that you're really using the your tesla by examining the output of glxinfo. Burlen On 10/28/2014 02:52 AM, R C Bording wrote: > HI Burlen, > Yes I am for the purpose of testing on our debug queue. But you are > bang on with setting the DISPLAY environment variable. > > so setting in the preview module > setenv LIBGL_ALWAYS_INDIRECT 1 > or in bash in the job script > export LIBGL_ALWAYS_INDIRECT 1 > > but also adding > export DISPLAY=:1 > is needed to render on the GPU. > > Renders the parallelSphere.py example with no errors across multiple > nodes. > > my mpirun command looks like this > > mpirun pvbatch parallelSphere.py > > note we have PBSpro installed so it determines the -np ##-number of > processors/cores based on the > #PBS -l select=..... > > So now to see if I can render something awesome! > > Chris B > > On 27/10/2014, at 11:10 PM, Burlen Loring wrote: > >> Hi Christopher, >> >> Are you by any chance logged in with ssh X11 forwarding (ssh -X ...)? >> It seems the error you report comes up often in that context. X >> forwarding would not be the right way to run PV on your cluster. >> >> Depending on how your cluster is setup you may need to start up the >> xserver before launching PV, and make sure to close it after PV >> exits. IUn that scenario your xorg.conf would specify the nvidia >> driver and a screen for each gpu which you would refernece in the >> shell used to start PV through the DISPLAY variable. If you already >> have x11 running and screens configured then it's just a matter of >> setting the display variable correctly. When there are multiple GPU's >> per node then you'd need to set the display using mpi rank modulo the >> number of gpus per node. >> >> I'm not sure it matters that much but I don't think that you want >> --use-offscreen-rendering option. >> >> Burlen >> >> On 10/26/2014 10:23 PM, R C Bording wrote: >>> Hi, >>> Managed to get a "working version of Paraview-4.2.0.1" on our GPU >>> cluster but when I try to run the >>> parallelSphere.py script on more than one node it just hangs. Work >>> like it is supposed to up to 12 cores on a single node. I am still >>> trying work out if I a running on the GPU "tesla- C2070). >>> >>> Here is the list of cake configurations >>> >>> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >>> -DParaView_FROM_GIT=OFF \ >>> -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ >>> -DENABLE_boost=ON \ >>> -DENABLE_cgns=OFF \ >>> -DENABLE_ffmpeg=ON \ >>> -DENABLE_fontconfig=ON \ >>> -DENABLE_freetype=ON \ >>> -DENABLE_hdf5=ON \ >>> -DENABLE_libxml2=ON \ >>> -DENABLE_matplotlib=ON \ >>> -DENABLE_mesa=OFF \ >>> -DENABLE_mpi=ON \ >>> -DENABLE_numpy=ON \ >>> -DENABLE_osmesa=OFF \ >>> -DENABLE_paraview=ON \ >>> -DENABLE_png=ON \ >>> -DENABLE_python=ON \ >>> -DENABLE_qhull=ON \ >>> -DENABLE_qt=ON \ >>> -DENABLE_silo=ON \ >>> -DENABLE_szip=ON \ >>> -DENABLE_visitbridge=ON \ >>> -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ >>> -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ >>> -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ >>> -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >>> -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >>> -DUSE_SYSTEM_mpi=ON \ >>> -DUSE_SYSTEM_python=OFF \ >>> -DUSE_SYSTEM_qt=OFF \ >>> -DUSE_SYSTEM_zlib=OFF ' >>> >>> The goal is to be able to support batch rendering on the whole >>> cluster ~96 nodes. >>> >>> Also do I need set another environment variable in my Paraview >>> module to make the Xlib >>> warning go away? >>> >>> [cbording at f100 Paraview]$ mpirun -n 12 pvbatch >>> --use-offscreen-rendering parallelSphere.py >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> >>> Is this related to my not being able to run across multiple nodes? >>> >>> R. Christopher Bording >>> Supercomputing Team-iVEC at UWA >>> E: cbording at ivec.org >>> T: +61 8 6488 6905 >>> >>> 26 Dick Perry Avenue, >>> Technology Park >>> Kensington, Western Australia. >>> 6151 >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Tue Oct 28 12:54:20 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Tue, 28 Oct 2014 16:54:20 +0000 Subject: [Paraview] FW: (ParaView) Lofting Shells (INC000000978412) In-Reply-To: <609460753.216121414506332720.JavaMail.AS345SNLNT$@AS345SNLNT> References: <609460753.216121414506332720.JavaMail.AS345SNLNT$@AS345SNLNT> Message-ID: <83bb08bd13344fd695f6bfe6d3570a6f@ES05AMSNLNT.srn.sandia.gov> My user wants to know if ParaView can "loft" shells? Any ideas? Thanks! Alan Alan, A shell is a 3d element with 0 thickness in the mesh but includes a thickness in the formulation of the element. By default paraview renders a shell as a thin surface. In some cases this is good enough but in other cases such as contact it is difficult to visualize the mechanical behavior of the element without being able to see the thickness of the shell that the mechanical formulation uses. In some codes a shell element that has thickness for visualization was called ?lofted? there may be other terms used to describe this. Kurtis > > Is there a way to loft shells so that they have thickness in paraview? > > Thanks, > > Kurtis > From david.thompson at kitware.com Tue Oct 28 13:06:46 2014 From: david.thompson at kitware.com (David Thompson) Date: Tue, 28 Oct 2014 13:06:46 -0400 Subject: [Paraview] FW: (ParaView) Lofting Shells (INC000000978412) In-Reply-To: <83bb08bd13344fd695f6bfe6d3570a6f@ES05AMSNLNT.srn.sandia.gov> References: <609460753.216121414506332720.JavaMail.AS345SNLNT$@AS345SNLNT> <83bb08bd13344fd695f6bfe6d3570a6f@ES05AMSNLNT.srn.sandia.gov> Message-ID: <6B6C6563-AEFC-41FF-9979-2C86A3D881D7@kitware.com> > My user wants to know if ParaView can "loft" shells? Any ideas? Not as far as I know. One issue is that different FEM codes parameterize shell elements differently: + Some assume that the surface is a true mid-surface. Others allow different "top" and "bottom" heights. Others "loft" only in one direction. + Some treat neighboring shells as constraining the offset nodes for problems where contact may be an issue. Others do not do contact. The latter in particular can lead to tricky problems when angles between neighboring shell elements are acute. Doing something akin to the "tube" filter, but for quads+tris would be easy as a Python programmable filter. Doing something where neighboring elements were taken into account would be significantly more work. David From leonardopessanha74 at gmail.com Tue Oct 28 14:25:38 2014 From: leonardopessanha74 at gmail.com (=?UTF-8?Q?L=C3=A9o_Pessanha?=) Date: Tue, 28 Oct 2014 16:25:38 -0200 Subject: [Paraview] VRPN Interactions Message-ID: Hi, I am starting to work with VRPN. I have a HeadTracking Glass and a FlyStick and i would like to know if i can have the Grab Interaction with an Object I am using the grab interaction with the Model Transform Matrix, and it works fine. My next goal is to use it this interaction with a single object, rotating and translating the object instead of the whole Model Transform Matrix Can someone help? Thanks in advance Leonardo Pessanha, Federal University of Rio de Janeiro -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.Murphy at lasp.colorado.edu Tue Oct 28 22:48:43 2014 From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy) Date: Tue, 28 Oct 2014 20:48:43 -0600 Subject: [Paraview] Question on programmable filter Message-ID: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu> Hi all, I am working with a scientist who is attempting to run a complex programmable filter that uses two inputs and produces one output. The script generates a result for the first time step is applied on, but if you advance paraview to the next time step, the new result is NOT generated. (no streamline update, no recalculation, nothing..) I am not seeing why this is the case. If you advance the time step, then force a re-apply of the filter, it will run, but that doesn't help for automated image generation. I am sure the problem has to do with updating the pipeline, but I don't have enough experience with the programmable filter to say for sure what needs to be done. If someone could take a look and let me know if there is a simple solution, I would be grateful. I have tried this with the same result on PV4.0.1 and PV4.1.0. I have not tried on PV4.2 as our reader plugin has not yet been compiled against 4.2. Thanks, Josh The programmable filter script follows: from paraview.vtk import dataset_adapter as DA from paraview import vtk from numpy import * # get inputs and define output # first input needs to define the grid used to provide the seed points to the stream tracer # the second are the resulting stream lines # the output is a modified version of the first input in1 = self.GetInputDataObject(0,0) in2 = self.GetInputDataObject(0,1) pdo = self.GetOutputDataObject(0) # get number of lines and total number of pts on the lines # note: paraview does the filed line integration first forward for all seed # points, then backward in the same order # ncells is twice the total number of field lines ncells = inputs[1].GetNumberOfCells() npts = inputs[1].GetNumberOfPoints() nc2 = ncells/2 # figure out the location and and number of points in each line numpts = zeros(ncells,dtype=int) cellpointer = zeros(ncells,dtype=int) for i in range(0,ncells): numpts[i] = in2.GetCell(i).GetNumberOfPoints() print numpts for i in range(1,ncells): cellpointer[i] = cellpointer[i-1] + numpts[i-1] #for i in range(0,ncells): # print cellpointer[i],numpts[i],r2[cellpointer[i],:] # # put points into numpy arrays # r = inputs[0].Points r2 = inputs[1].Points rmag = mag(r2) dR = r2[1:npts,:] - r2[0:npts-1,:] dr = mag(dR) # # get variables needed for integration # B = inputs[1].PointData['Magnetic Field Vector'] den = inputs[1].PointData['Plasma Density'] csound = inputs[1].PointData['Sound Speed'] pressure = den*csound**2 b = mag(B) binv = 1./b # # get midpoint values # bav = 0.5*(b[1:npts]+b[:npts-1]) denav = 0.5*(den[1:npts]+den[0:npts-1]) pav = 0.5*(pressure[1:npts]+pressure[0:npts-1]) print 'DR',dR.shape,r.shape print numpts print cellpointer # # integrate along field lines # FTvolume = zeros(ncells) FTden = zeros(ncells) FTP = zeros(ncells) print FTvolume for i in range(ncells): for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1): FTvolume[i] = FTvolume[i] + binv[j]*dr[j] FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j] FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6 for i in range(nc2): FTvolume[i] = FTvolume[i] + FTvolume[i+nc2] FTden[i] = FTden[i] + FTden[i+nc2] FTP[i] = FTP[i] + FTP[i+nc2] print FTvolume print FTden print FTP # # don't really need to reset the positions # but can be useful if we modify to plot in min B surface, say # newPoints = vtk.vtkPoints() denout = zeros(ncells) for i in range(0,nc2): xi = r2[cellpointer[i],0] yi = r2[cellpointer[i],1] zi = r2[cellpointer[i],2] denout[i] = b[cellpointer[i]] print i,xi,yi,zi,denout[i] newPoints.InsertPoint(i,xi,yi,zi) print newPoints pdo.SetPoints(newPoints) # # add computed arrays # arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume') pdo.GetPointData().AddArray(arrFTV) print 'added stuff' arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass') pdo.GetPointData().AddArray(arrFTden) arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy') pdo.GetPointData().AddArray(arrFTP) From mexas at bris.ac.uk Wed Oct 29 08:36:35 2014 From: mexas at bris.ac.uk (Anton Shterenlikht) Date: Wed, 29 Oct 2014 12:36:35 +0000 Subject: [Paraview] 550 Neither MX nor MTA found for domain:paraview.org Message-ID: I get: Delivery to the following recipient failed permanently: paraview at paraview.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the relay outbounds200.obsmtp.com by ou tbounds200.obsmtp.com. [207.126.147.11]. The error that the other server returned was: 550 Neither MX nor MTA found for domain:paraview.org - psmtp Now sending via a different mailer. Hope this gets to the list Anton From sebastien.jourdain at kitware.com Wed Oct 29 11:23:37 2014 From: sebastien.jourdain at kitware.com (Sebastien Jourdain) Date: Wed, 29 Oct 2014 09:23:37 -0600 Subject: [Paraview] [Paraview-developers] Question on programmable filter In-Reply-To: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu> References: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu> Message-ID: Hi Josh, I've noticed that the default programmable filters does not advertise that it handle time. To properly do that you can use the attached XML plugin. Let us know if that fix the problem. Seb On Tue, Oct 28, 2014 at 8:48 PM, Joshua Murphy < Joshua.Murphy at lasp.colorado.edu> wrote: > Hi all, > > I am working with a scientist who is attempting to run a complex > programmable filter that uses two inputs and produces one output. The > script generates a result for the first time step is applied on, but if you > advance paraview to the next time step, the new result is NOT generated. > (no streamline update, no recalculation, nothing..) I am not seeing why > this is the case. If you advance the time step, then force a re-apply of > the filter, it will run, but that doesn't help for automated image > generation. I am sure the problem has to do with updating the pipeline, > but I don't have enough experience with the programmable filter to say for > sure what needs to be done. If someone could take a look and let me know > if there is a simple solution, I would be grateful. > > I have tried this with the same result on PV4.0.1 and PV4.1.0. I have not > tried on PV4.2 as our reader plugin has not yet been compiled against 4.2. > > Thanks, > > Josh > > The programmable filter script follows: > > from paraview.vtk import dataset_adapter as DA > from paraview import vtk > from numpy import * > > # get inputs and define output > # first input needs to define the grid used to provide the seed points to > the stream tracer > # the second are the resulting stream lines > # the output is a modified version of the first input > > in1 = self.GetInputDataObject(0,0) > in2 = self.GetInputDataObject(0,1) > pdo = self.GetOutputDataObject(0) > > # get number of lines and total number of pts on the lines > # note: paraview does the filed line integration first forward for all > seed > # points, then backward in the same order > # ncells is twice the total number of field lines > > ncells = inputs[1].GetNumberOfCells() > npts = inputs[1].GetNumberOfPoints() > nc2 = ncells/2 > > # figure out the location and and number of points in each line > > numpts = zeros(ncells,dtype=int) > cellpointer = zeros(ncells,dtype=int) > for i in range(0,ncells): > numpts[i] = in2.GetCell(i).GetNumberOfPoints() > print numpts > for i in range(1,ncells): > cellpointer[i] = cellpointer[i-1] + numpts[i-1] > > #for i in range(0,ncells): > # print cellpointer[i],numpts[i],r2[cellpointer[i],:] > > # > # put points into numpy arrays > # > r = inputs[0].Points > r2 = inputs[1].Points > rmag = mag(r2) > dR = r2[1:npts,:] - r2[0:npts-1,:] > dr = mag(dR) > > # > # get variables needed for integration > # > > B = inputs[1].PointData['Magnetic Field Vector'] > den = inputs[1].PointData['Plasma Density'] > csound = inputs[1].PointData['Sound Speed'] > pressure = den*csound**2 > b = mag(B) > binv = 1./b > > # > # get midpoint values > # > > bav = 0.5*(b[1:npts]+b[:npts-1]) > denav = 0.5*(den[1:npts]+den[0:npts-1]) > pav = 0.5*(pressure[1:npts]+pressure[0:npts-1]) > print 'DR',dR.shape,r.shape > print numpts > print cellpointer > > # > # integrate along field lines > # > FTvolume = zeros(ncells) > FTden = zeros(ncells) > FTP = zeros(ncells) > print FTvolume > for i in range(ncells): > for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1): > FTvolume[i] = FTvolume[i] + binv[j]*dr[j] > FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j] > FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6 > for i in range(nc2): > FTvolume[i] = FTvolume[i] + FTvolume[i+nc2] > FTden[i] = FTden[i] + FTden[i+nc2] > FTP[i] = FTP[i] + FTP[i+nc2] > print FTvolume > print FTden > print FTP > # > # don't really need to reset the positions > # but can be useful if we modify to plot in min B surface, say > # > > newPoints = vtk.vtkPoints() > denout = zeros(ncells) > for i in range(0,nc2): > xi = r2[cellpointer[i],0] > yi = r2[cellpointer[i],1] > zi = r2[cellpointer[i],2] > denout[i] = b[cellpointer[i]] > print i,xi,yi,zi,denout[i] > newPoints.InsertPoint(i,xi,yi,zi) > > print newPoints > > > pdo.SetPoints(newPoints) > > # > # add computed arrays > # > > arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume') > pdo.GetPointData().AddArray(arrFTV) > print 'added stuff' > arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass') > pdo.GetPointData().AddArray(arrFTden) > > arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy') > pdo.GetPointData().AddArray(arrFTP) > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: TemporalPythonProxy.xml Type: text/xml Size: 1018 bytes Desc: not available URL: From andy.bauer at kitware.com Wed Oct 29 12:00:22 2014 From: andy.bauer at kitware.com (Andy Bauer) Date: Wed, 29 Oct 2014 12:00:22 -0400 Subject: [Paraview] [Paraview-developers] Question on programmable filter In-Reply-To: References: <8D5C1B82EA40014E8B222E92B907632502135A8C55AE@MAILBOX.LASP.colorado.edu> Message-ID: The Programmable Filter can handle time but it has to be done explicitly. You'll need to do the proper calls in RequestUpdateExtentScript, RequestInformationScript and Script. (i.e. RequestData). You can use inInfo and outInfo to set the required information objections like UPDATE_TIME_STEP, TIME_STEPS, etc. Andy On Wed, Oct 29, 2014 at 11:23 AM, Sebastien Jourdain < sebastien.jourdain at kitware.com> wrote: > Hi Josh, > > I've noticed that the default programmable filters does not advertise that > it handle time. To properly do that you can use the attached XML plugin. > > Let us know if that fix the problem. > > Seb > > On Tue, Oct 28, 2014 at 8:48 PM, Joshua Murphy < > Joshua.Murphy at lasp.colorado.edu> wrote: > >> Hi all, >> >> I am working with a scientist who is attempting to run a complex >> programmable filter that uses two inputs and produces one output. The >> script generates a result for the first time step is applied on, but if you >> advance paraview to the next time step, the new result is NOT generated. >> (no streamline update, no recalculation, nothing..) I am not seeing why >> this is the case. If you advance the time step, then force a re-apply of >> the filter, it will run, but that doesn't help for automated image >> generation. I am sure the problem has to do with updating the pipeline, >> but I don't have enough experience with the programmable filter to say for >> sure what needs to be done. If someone could take a look and let me know >> if there is a simple solution, I would be grateful. >> >> I have tried this with the same result on PV4.0.1 and PV4.1.0. I have >> not tried on PV4.2 as our reader plugin has not yet been compiled against >> 4.2. >> >> Thanks, >> >> Josh >> >> The programmable filter script follows: >> >> from paraview.vtk import dataset_adapter as DA >> from paraview import vtk >> from numpy import * >> >> # get inputs and define output >> # first input needs to define the grid used to provide the seed points to >> the stream tracer >> # the second are the resulting stream lines >> # the output is a modified version of the first input >> >> in1 = self.GetInputDataObject(0,0) >> in2 = self.GetInputDataObject(0,1) >> pdo = self.GetOutputDataObject(0) >> >> # get number of lines and total number of pts on the lines >> # note: paraview does the filed line integration first forward for all >> seed >> # points, then backward in the same order >> # ncells is twice the total number of field lines >> >> ncells = inputs[1].GetNumberOfCells() >> npts = inputs[1].GetNumberOfPoints() >> nc2 = ncells/2 >> >> # figure out the location and and number of points in each line >> >> numpts = zeros(ncells,dtype=int) >> cellpointer = zeros(ncells,dtype=int) >> for i in range(0,ncells): >> numpts[i] = in2.GetCell(i).GetNumberOfPoints() >> print numpts >> for i in range(1,ncells): >> cellpointer[i] = cellpointer[i-1] + numpts[i-1] >> >> #for i in range(0,ncells): >> # print cellpointer[i],numpts[i],r2[cellpointer[i],:] >> >> # >> # put points into numpy arrays >> # >> r = inputs[0].Points >> r2 = inputs[1].Points >> rmag = mag(r2) >> dR = r2[1:npts,:] - r2[0:npts-1,:] >> dr = mag(dR) >> >> # >> # get variables needed for integration >> # >> >> B = inputs[1].PointData['Magnetic Field Vector'] >> den = inputs[1].PointData['Plasma Density'] >> csound = inputs[1].PointData['Sound Speed'] >> pressure = den*csound**2 >> b = mag(B) >> binv = 1./b >> >> # >> # get midpoint values >> # >> >> bav = 0.5*(b[1:npts]+b[:npts-1]) >> denav = 0.5*(den[1:npts]+den[0:npts-1]) >> pav = 0.5*(pressure[1:npts]+pressure[0:npts-1]) >> print 'DR',dR.shape,r.shape >> print numpts >> print cellpointer >> >> # >> # integrate along field lines >> # >> FTvolume = zeros(ncells) >> FTden = zeros(ncells) >> FTP = zeros(ncells) >> print FTvolume >> for i in range(ncells): >> for j in range(cellpointer[i],cellpointer[i]+numpts[i]-1): >> FTvolume[i] = FTvolume[i] + binv[j]*dr[j] >> FTden[i] = FTden[i] + binv[j]*dr[j]*denav[j] >> FTP[i] = FTP[i] + binv[j]*dr[j]*pav[j]**0.6 >> for i in range(nc2): >> FTvolume[i] = FTvolume[i] + FTvolume[i+nc2] >> FTden[i] = FTden[i] + FTden[i+nc2] >> FTP[i] = FTP[i] + FTP[i+nc2] >> print FTvolume >> print FTden >> print FTP >> # >> # don't really need to reset the positions >> # but can be useful if we modify to plot in min B surface, say >> # >> >> newPoints = vtk.vtkPoints() >> denout = zeros(ncells) >> for i in range(0,nc2): >> xi = r2[cellpointer[i],0] >> yi = r2[cellpointer[i],1] >> zi = r2[cellpointer[i],2] >> denout[i] = b[cellpointer[i]] >> print i,xi,yi,zi,denout[i] >> newPoints.InsertPoint(i,xi,yi,zi) >> >> print newPoints >> >> >> pdo.SetPoints(newPoints) >> >> # >> # add computed arrays >> # >> >> arrFTV = DA.numpyTovtkDataArray(FTvolume[0:nc2],'Flux Tube Volume') >> pdo.GetPointData().AddArray(arrFTV) >> print 'added stuff' >> arrFTden = DA.numpyTovtkDataArray(FTden[0:nc2],'Flux Tube Mass') >> pdo.GetPointData().AddArray(arrFTden) >> >> arrFTP = DA.numpyTovtkDataArray(FTP[0:nc2],'Flux Tube Entropy') >> pdo.GetPointData().AddArray(arrFTP) >> _______________________________________________ >> Paraview-developers mailing list >> Paraview-developers at paraview.org >> http://public.kitware.com/mailman/listinfo/paraview-developers >> > > > _______________________________________________ > Paraview-developers mailing list > Paraview-developers at paraview.org > http://public.kitware.com/mailman/listinfo/paraview-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From utkarsh.ayachit at kitware.com Wed Oct 29 12:20:04 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Oct 2014 12:20:04 -0400 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: <20141017162323.GD5747@megas.kitwarein.com> <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> <20141020154332.GB7304@megas.kitwarein.com> Message-ID: Simon, I am joining a little late to this conversation -- is this addressed yet? Utkarsh On Mon, Oct 20, 2014 at 11:57 AM, Su, Simon M CTR USARMY ARL (US) wrote: > Ben, > > Unfortunately, when I checked the CMakeCache.txt in the directory paraview/src/paraview-build after the cmake ran, I am still finding > > //Request building vtkIOXdmf3 > Module_vtkIOXdmf3:BOOL=OFF > > and Boost_NO_BOOST_CMAKE is none existence in the CMakeCache.txt > > I even tried both > -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > and > -DPV_EXTRA_CMAKE_ARGS:STRING="Module_vtkIOXdmf3:BOOL=ON Boost_NO_BOOST_CMAKE:BOOL=ON" > > thoughts? > > thanks > -simon > > ________________________________________ > From: Ben Boeckel [ben.boeckel at kitware.com] > Sent: Monday, October 20, 2014 11:43 AM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option > > On Mon, Oct 20, 2014 at 15:15:59 +0000, Su, Simon M CTR USARMY ARL (US) wrote: >> I ran cmake with >> >> -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" >> >> and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON >> -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable >> PV_EXTRA_CMAKE_ARGS >> >> It appears :STRING does the trick. > > Yep. This is a CMake parsing bug; the regular expression for this is too > greedy (it allows '=' in the variable name). Compare: > >> -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON > |-------------------------------------| |--| |-------------------------------| > variable type value > > versus: > >> -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON > |-----------------| |----| |--------------------------------------------------------| > variable type value > > this works: > >> -DSOME_PATH=C:/path/to/file > |-------| |-------------| > variable value > > because paths with '=' are very rare: > >> -DSOME_PATH=C:/path/to/file/with/=/sign > |---------| |-----------------| |---| > variable type value > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From utkarsh.ayachit at kitware.com Wed Oct 29 12:36:23 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Oct 2014 12:36:23 -0400 Subject: [Paraview] paraview performance In-Reply-To: References: Message-ID: That'd work. You can use the benchmark module [1] too to give you info at a finer granularity. Utkarsh [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.benchmark.html On Mon, Oct 27, 2014 at 12:12 PM, R C Bording wrote: > Hi, > Is there a rendering model that you have for testing the performance of > the paraview? > I have install paraview on our GPU cluster and would like validated it > someway other than > just putting timing calls around the Render command in the parallelSphere.py > script. > > Or is that sufficient? > > Cheers, > Chris B > > R. Christopher Bording > Supercomputing Team-iVEC at UWA > E: cbording at ivec.org > T: +61 8 6488 6905 > > 26 Dick Perry Avenue, > Technology Park > Kensington, Western Australia. > 6151 > > > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Wed Oct 29 12:37:46 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Wed, 29 Oct 2014 12:37:46 -0400 Subject: [Paraview] ScalarOpacityFunction property not set when saving python state In-Reply-To: References: Message-ID: That sounds like a bug to me. Utkarsh On Thu, Oct 23, 2014 at 11:26 AM, Scott Wittenburg wrote: > Hi all, > > Has anyone else noticed this recently? At the bottom of this email is an > example of some state I just saved, which seems to be missing the following > line: > > magnitudeDisplay.ScalarOpactiyFunction = splatterValuesPWF > > If this is a bug, I can enter a bug report. > > Cheers, > Scott > > > > # get color transfer function/color map for 'SplatterValues' > splatterValuesLUT = GetColorTransferFunction('SplatterValues') > splatterValuesLUT.RGBPoints = [0.0, 0.0, 0.0, 1.0, > 1211.3642578125, 0.0, 0.12549019607843137, > 1.0, > 1338.4827880859375, 0.00392156862745098, 1.0, > 0.0, > 1450.6461181640625, 1.0, 0.1568627450980392, > 0.0, > 2205.8794212053426, 1.0, 0.0, 0.0] > splatterValuesLUT.ColorSpace = 'HSV' > splatterValuesLUT.NanColor = [0.498039, 0.498039, 0.498039] > splatterValuesLUT.ScalarRangeInitialized = 1.0 > > # get opacity transfer function/opacity map for 'SplatterValues' > splatterValuesPWF = GetOpacityTransferFunction('SplatterValues') > splatterValuesPWF.Points = [0.0, 0.0, 0.5, 0.0, > 0.0, 0.0, 0.5, 0.0, > 1001.99267578125, 0.0, 0.5, 0.0, > 1293.617431640625, 1.0, 0.5, 0.0, > 1674.9727783203125, 0.0, 0.5, 0.0, > 2205.87939453125, 0.0, 0.5, 0.0] > splatterValuesPWF.ScalarRangeInitialized = 1 > > # ---------------------------------------------------------------- > # setup the visualization in view 'renderView1' > # ---------------------------------------------------------------- > > # show data from magnitude > magnitudeDisplay = Show(magnitude, renderView1) > # trace defaults for the display properties. > magnitudeDisplay.Representation = 'Volume' > magnitudeDisplay.ColorArrayName = ['POINTS', 'SplatterValues'] > magnitudeDisplay.LookupTable = splatterValuesLUT > magnitudeDisplay.ScalarOpacityUnitDistance = 0.8868099940416558 > magnitudeDisplay.Slice = 127 > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From simon.m.su.ctr at mail.mil Wed Oct 29 13:25:00 2014 From: simon.m.su.ctr at mail.mil (Su, Simon M CTR USARMY ARL (US)) Date: Wed, 29 Oct 2014 17:25:00 +0000 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: <20141017162323.GD5747@megas.kitwarein.com> <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> <20141020154332.GB7304@megas.kitwarein.com> , Message-ID: Hi Utkarsh, unfortunately I am still not able to pass both argument into ParaView superbuild cmake line using the -DPV_EXTRA_CMAKE_ARGS option that Ben suggested. Any help on this is much appreciated thanks -simon ________________________________________ From: Utkarsh Ayachit [utkarsh.ayachit at kitware.com] Sent: Wednesday, October 29, 2014 12:20 PM To: Su, Simon M CTR USARMY ARL (US) Cc: ben.boeckel at kitware.com; paraview at paraview.org Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option Simon, I am joining a little late to this conversation -- is this addressed yet? Utkarsh On Mon, Oct 20, 2014 at 11:57 AM, Su, Simon M CTR USARMY ARL (US) wrote: > Ben, > > Unfortunately, when I checked the CMakeCache.txt in the directory paraview/src/paraview-build after the cmake ran, I am still finding > > //Request building vtkIOXdmf3 > Module_vtkIOXdmf3:BOOL=OFF > > and Boost_NO_BOOST_CMAKE is none existence in the CMakeCache.txt > > I even tried both > -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > and > -DPV_EXTRA_CMAKE_ARGS:STRING="Module_vtkIOXdmf3:BOOL=ON Boost_NO_BOOST_CMAKE:BOOL=ON" > > thoughts? > > thanks > -simon > > ________________________________________ > From: Ben Boeckel [ben.boeckel at kitware.com] > Sent: Monday, October 20, 2014 11:43 AM > To: Su, Simon M CTR USARMY ARL (US) > Cc: paraview at paraview.org > Subject: Re: [Paraview] ParaView Superbuild - changing default Paraciew cmake option > > On Mon, Oct 20, 2014 at 15:15:59 +0000, Su, Simon M CTR USARMY ARL (US) wrote: >> I ran cmake with >> >> -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" >> >> and check it with ccmake. Looks like -DModule_vtkIOXdmf3:BOOL=ON >> -DBoost_NO_BOOST_CMAKE:BOOL=ON made it into the variable >> PV_EXTRA_CMAKE_ARGS >> >> It appears :STRING does the trick. > > Yep. This is a CMake parsing bug; the regular expression for this is too > greedy (it allows '=' in the variable name). Compare: > >> -DPV_EXTRA_CMAKE_ARGS=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON > |-------------------------------------| |--| |-------------------------------| > variable type value > > versus: > >> -DPV_EXTRA_CMAKE_ARGS:STRING=-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON > |-----------------| |----| |--------------------------------------------------------| > variable type value > > this works: > >> -DSOME_PATH=C:/path/to/file > |-------| |-------------| > variable value > > because paths with '=' are very rare: > >> -DSOME_PATH=C:/path/to/file/with/=/sign > |---------| |-----------------| |---| > variable type value > > --Ben > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From chaoyuan at yahoo.com Wed Oct 29 15:21:42 2014 From: chaoyuan at yahoo.com (Joe) Date: Wed, 29 Oct 2014 12:21:42 -0700 Subject: [Paraview] [Help!] Paraview GUI does not start (closes automatically) Message-ID: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> Hi all, I started using Paraview (4.2.0) about a couple months ago and it was working normally. I don't know exactly when this problem begin because I don't use Paraview everyday but now when I double click on Paraview.exe, no window pops up anymore. Using process monitor, I could see that Paraview.exe does a few things on my computer but I couldn't figure out what went wrong. I'm running Paraview 4.2.0 64-bit on Windows 7 Ultimate. I scanned my computer for virus and malware and got rid of whatever they found. But the problem remains. I don't know if this is relevant but I installed Qt 5.3.2 some time ago. I tried removing Qt and installed Paraview again but it didn't help. I also tried removing my antivirus program and installed Paraview again. It also did not help. Has anyone run into this problem before? Any thoughts on how this problem can be solved or how I can troubleshoot this? Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 29 16:33:38 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 29 Oct 2014 16:33:38 -0400 Subject: [Paraview] [Help!] Paraview GUI does not start (closes automatically) In-Reply-To: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> References: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> Message-ID: Try removing your paraview settings. On windows this should be at: %APPDATA%\ParaView\ParaView4.2.0.ini Elsewhere it is at: ~/.config/Paraview/ParaView4.2.0.ini David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 29, 2014 at 3:21 PM, Joe via ParaView wrote: > Hi all, > > I started using Paraview (4.2.0) about a couple months ago and it was > working normally. I don't know exactly when this problem begin because I > don't use Paraview everyday but now when I double click on Paraview.exe, no > window pops up anymore. Using process monitor, I could see that > Paraview.exe does a few things on my computer but I couldn't figure out > what went wrong. > > I'm running Paraview 4.2.0 64-bit on Windows 7 Ultimate. I scanned my > computer for virus and malware and got rid of whatever they found. But the > problem remains. > > I don't know if this is relevant but I installed Qt 5.3.2 some time > ago. I tried removing Qt and installed Paraview again but it didn't help. I > also tried removing my antivirus program and installed Paraview again. It > also did not help. > > Has anyone run into this problem before? Any thoughts on how this > problem can be solved or how I can troubleshoot this? > > Joe > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Oct 29 16:53:46 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 29 Oct 2014 16:53:46 -0400 Subject: [Paraview] ParaView Superbuild - changing default Paraciew cmake option In-Reply-To: References: <20141017162323.GD5747@megas.kitwarein.com> <20141018020600.GA2725@bronto-burt.dev.benboeckel.net> <20141020154332.GB7304@megas.kitwarein.com> Message-ID: <20141029205346.GA5560@megas.kitwarein.com> On Mon, Oct 20, 2014 at 15:57:26 +0000, Su, Simon M CTR USARMY ARL (US) wrote: > Unfortunately, when I checked the CMakeCache.txt in the directory > paraview/src/paraview-build after the cmake ran, I am still finding Sorry, this email went under my radar. > //Request building vtkIOXdmf3 > Module_vtkIOXdmf3:BOOL=OFF > > and Boost_NO_BOOST_CMAKE is none existence in the CMakeCache.txt > > I even tried both > -DPV_EXTRA_CMAKE_ARGS:STRING="-DModule_vtkIOXdmf3:BOOL=ON -DBoost_NO_BOOST_CMAKE:BOOL=ON" > and > -DPV_EXTRA_CMAKE_ARGS:STRING="Module_vtkIOXdmf3:BOOL=ON Boost_NO_BOOST_CMAKE:BOOL=ON" > > thoughts? Looking at the generated command line, it looks like the value is being put in as a single argument. Try separating it with a ';' instead of a space. --Ben From chaoyuan at yahoo.com Wed Oct 29 17:04:58 2014 From: chaoyuan at yahoo.com (Joe) Date: Wed, 29 Oct 2014 14:04:58 -0700 Subject: [Paraview] [Help!] Paraview GUI does not start (closes automatically) In-Reply-To: References: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> Message-ID: <1414616698.69091.YahooMailNeo@web126101.mail.ne1.yahoo.com> Thanks for the response, David. What you suggested did change the symptom a bit. After I remove the ini file, I was able to see the Paraview logo appear after I execute it, which I did not see prior to the removal. However, the window still doesn't show up. Is there anything else I can do? Joe On Wednesday, October 29, 2014 1:34 PM, David E DeMarle wrote: Try removing your paraview settings. On windows this should be at:%APPDATA%\ParaView\ParaView4.2.0.ini Elsewhere it is at: ~/.config/Paraview/ParaView4.2.0.ini David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 29, 2014 at 3:21 PM, Joe via ParaView wrote: Hi all, > > > I started using Paraview (4.2.0) about a couple months ago and it was working normally. I don't know exactly when this problem begin because I don't use Paraview everyday but now when I double click on Paraview.exe, no window pops up anymore. Using process monitor, I could see that Paraview.exe does a few things on my computer but I couldn't figure out what went wrong. > > > I'm running Paraview 4.2.0 64-bit on Windows 7 Ultimate. I scanned my computer for virus and malware and got rid of whatever they found. But the problem remains. > > > I don't know if this is relevant but I installed Qt 5.3.2 some time ago. I tried removing Qt and installed Paraview again but it didn't help. I also tried removing my antivirus program and installed Paraview again. It also did not help. > > > Has anyone run into this problem before? Any thoughts on how this problem can be solved or how I can troubleshoot this? > > >Joe > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.boeckel at kitware.com Wed Oct 29 19:11:10 2014 From: ben.boeckel at kitware.com (Ben Boeckel) Date: Wed, 29 Oct 2014 19:11:10 -0400 Subject: [Paraview] 550 Neither MX nor MTA found for domain:paraview.org In-Reply-To: References: Message-ID: <20141029231110.GA16209@bronto-burt.dev.benboeckel.net> On Wed, Oct 29, 2014 at 12:36:35 +0000, Anton Shterenlikht wrote: > Delivery to the following recipient failed permanently: > > paraview at paraview.org > > Technical details of permanent failure: > Google tried to deliver your message, but it was rejected by the relay > outbounds200.obsmtp.com by ou > tbounds200.obsmtp.com. [207.126.147.11]. > > The error that the other server returned was: > 550 Neither MX nor MTA found for domain:paraview.org - psmtp Odd; works here (also worked inside the firewall this morning): % dig -t MX paraview.org ; <<>> DiG 9.9.6-RedHat-9.9.6-3.fc22 <<>> -t MX paraview.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56901 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;paraview.org. IN MX ;; AUTHORITY SECTION: paraview.org. 3600 IN SOA dns1.name-services.com. info.name-services.com. 2002050701 10800 3600 604800 3600 ;; Query time: 323 msec ;; SERVER: XXX.XXX.XXX.XXX#53(XXX.XXX.XXX.XXX) ;; WHEN: Wed Oct 29 19:09:02 EDT 2014 ;; MSG SIZE rcvd: 104 > Now sending via a different mailer. > Hope this gets to the list It was received :) . --Ben From Hertzberg at Colorado.EDU Wed Oct 29 19:07:04 2014 From: Hertzberg at Colorado.EDU (Jean Hertzberg) Date: Wed, 29 Oct 2014 17:07:04 -0600 Subject: [Paraview] 4.2.0 stereo interlace problem Message-ID: Hi. I have not been able to get PV 4.2.0 to work in stereo interlace mode on my Windows 7 64 bit system. Default mode seems to be red-blue, and that works fine, but I get this error on startup when I specify -stereo-type=Interlace ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLCamera.cxx, line 167 vtkOpenGLCamera (000000000B119790): failed after Render 1 OpenGL errors detected 0 : (1282) Invalid operation PV 4.0.1 starts in interlace mode with no problem on the same system. Suggestions? I didn't see any known bugs regarding this. Jean Hertzberg Dept. Mechanical Engineering University of Colorado, Boulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Oct 29 19:26:27 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Wed, 29 Oct 2014 23:26:27 +0000 Subject: [Paraview] PV 4.2.0 Color legend disappearing Message-ID: In ParaView 4.2.0, I have found a few cases where the color legend disappears, and I can't get it back. Has anyone else seen this, and found a way to replicate it? Mind passing the voodoo on how to replicate this bug? Thanks, Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Wed Oct 29 20:51:00 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 30 Oct 2014 00:51:00 +0000 Subject: [Paraview] [EXTERNAL] 4.2.0 stereo interlace problem In-Reply-To: References: Message-ID: <9024e1abaf1b4f7188f7e4ef8200a927@ES05AMSNLNT.srn.sandia.gov> Jean, I just tried with PV 4.2.0, Linux Mesa (local server), Linux hardware rendering, and my local Windows 7 box (Kitware download), and they all worked with -stereo-type=Interlaced. At least I believe they worked, nothing crashed and the image looked good. (Note that the command is Interlaced, not interlace). Other than that, the only thing I can think of is to delete your config files. http://www.paraview.org/Wiki/ParaView_Settings_Files. Alan From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jean Hertzberg Sent: Wednesday, October 29, 2014 5:07 PM To: paraview at paraview.org Subject: [EXTERNAL] [Paraview] 4.2.0 stereo interlace problem Hi. I have not been able to get PV 4.2.0 to work in stereo interlace mode on my Windows 7 64 bit system. Default mode seems to be red-blue, and that works fine, but I get this error on startup when I specify -stereo-type=Interlace ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLCamera.cxx, line 167 vtkOpenGLCamera (000000000B119790): failed after Render 1 OpenGL errors detected 0 : (1282) Invalid operation PV 4.0.1 starts in interlace mode with no problem on the same system. Suggestions? I didn't see any known bugs regarding this. Jean Hertzberg Dept. Mechanical Engineering University of Colorado, Boulder -------------- next part -------------- An HTML attachment was scrubbed... URL: From chaoyuan at yahoo.com Wed Oct 29 22:27:38 2014 From: chaoyuan at yahoo.com (Joe) Date: Wed, 29 Oct 2014 19:27:38 -0700 Subject: [Paraview] [Help!] Paraview GUI does not start (closes automatically) In-Reply-To: <1414616698.69091.YahooMailNeo@web126101.mail.ne1.yahoo.com> References: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> <1414616698.69091.YahooMailNeo@web126101.mail.ne1.yahoo.com> Message-ID: <1414636058.49514.YahooMailNeo@web126101.mail.ne1.yahoo.com> David, The problem is now solved. It appears that ParaView does not work with Python 3? Is this true? While I tried calling ParaView from Maltab, I got error message like this: File "C:\Python34\Lib\site.py", line 176 file = sys.stderr) ^ SyntaxError: invalid syntax which according to a post on Stack Overflow, indicates an error occurring when trying to run Python 3 script using Python 2 interpreter. I then removed Python path from PATH variable and also removed PYTHONPATH variable and ParaView was working again. So is it true that ParaView is not compatible with Python 3? Joe On Wednesday, October 29, 2014 2:04 PM, Joe wrote: Thanks for the response, David. What you suggested did change the symptom a bit. After I remove the ini file, I was able to see the Paraview logo appear after I execute it, which I did not see prior to the removal. However, the window still doesn't show up. Is there anything else I can do? Joe On Wednesday, October 29, 2014 1:34 PM, David E DeMarle wrote: Try removing your paraview settings. On windows this should be at:%APPDATA%\ParaView\ParaView4.2.0.ini Elsewhere it is at: ~/.config/Paraview/ParaView4.2.0.ini David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 29, 2014 at 3:21 PM, Joe via ParaView wrote: Hi all, > > > I started using Paraview (4.2.0) about a couple months ago and it was working normally. I don't know exactly when this problem begin because I don't use Paraview everyday but now when I double click on Paraview.exe, no window pops up anymore. Using process monitor, I could see that Paraview.exe does a few things on my computer but I couldn't figure out what went wrong. > > > I'm running Paraview 4.2.0 64-bit on Windows 7 Ultimate. I scanned my computer for virus and malware and got rid of whatever they found. But the problem remains. > > > I don't know if this is relevant but I installed Qt 5.3.2 some time ago. I tried removing Qt and installed Paraview again but it didn't help. I also tried removing my antivirus program and installed Paraview again. It also did not help. > > > Has anyone run into this problem before? Any thoughts on how this problem can be solved or how I can troubleshoot this? > > >Joe > >_______________________________________________ >Powered by www.kitware.com > >Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > >Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > >Follow this link to subscribe/unsubscribe: >http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.demarle at kitware.com Wed Oct 29 22:36:51 2014 From: dave.demarle at kitware.com (David E DeMarle) Date: Wed, 29 Oct 2014 22:36:51 -0400 Subject: [Paraview] [Help!] Paraview GUI does not start (closes automatically) In-Reply-To: <1414636058.49514.YahooMailNeo@web126101.mail.ne1.yahoo.com> References: <1414610502.63426.YahooMailNeo@web126105.mail.ne1.yahoo.com> <1414616698.69091.YahooMailNeo@web126101.mail.ne1.yahoo.com> <1414636058.49514.YahooMailNeo@web126101.mail.ne1.yahoo.com> Message-ID: Glad you got it working. And yes it is true that ParaView does not yet support Python 3. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Wed, Oct 29, 2014 at 10:27 PM, Joe wrote: > David, > > The problem is now solved. It appears that ParaView does not work with > Python 3? Is this true? > > While I tried calling ParaView from Maltab, I got error message like > this: > File "C:\Python34\Lib\site.py", line 176 > file = sys.stderr) > ^ > SyntaxError: invalid syntax > > which according to a post on Stack Overflow, indicates an error > occurring when trying to run Python 3 script using Python 2 interpreter. > > I then removed Python path from PATH variable and also removed > PYTHONPATH variable and ParaView was working again. > > So is it true that ParaView is not compatible with Python 3? > > Joe > > > On Wednesday, October 29, 2014 2:04 PM, Joe wrote: > > > Thanks for the response, David. > > What you suggested did change the symptom a bit. After I remove the ini > file, I was able to see the Paraview logo appear after I execute it, which > I did not see prior to the removal. > > However, the window still doesn't show up. Is there anything else I can > do? > > Joe > > > On Wednesday, October 29, 2014 1:34 PM, David E DeMarle < > dave.demarle at kitware.com> wrote: > > > Try removing your paraview settings. > On windows this should be at: > %APPDATA%\ParaView\ParaView4.2.0.ini > > Elsewhere it is at: > ~/.config/Paraview/ParaView4.2.0.ini > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > On Wed, Oct 29, 2014 at 3:21 PM, Joe via ParaView > wrote: > > Hi all, > > I started using Paraview (4.2.0) about a couple months ago and it was > working normally. I don't know exactly when this problem begin because I > don't use Paraview everyday but now when I double click on Paraview.exe, no > window pops up anymore. Using process monitor, I could see that > Paraview.exe does a few things on my computer but I couldn't figure out > what went wrong. > > I'm running Paraview 4.2.0 64-bit on Windows 7 Ultimate. I scanned my > computer for virus and malware and got rid of whatever they found. But the > problem remains. > > I don't know if this is relevant but I installed Qt 5.3.2 some time > ago. I tried removing Qt and installed Paraview again but it didn't help. I > also tried removing my antivirus program and installed Paraview again. It > also did not help. > > Has anyone run into this problem before? Any thoughts on how this > problem can be solved or how I can troubleshoot this? > > Joe > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbording at ivec.org Wed Oct 29 23:29:53 2014 From: cbording at ivec.org (R C Bording) Date: Thu, 30 Oct 2014 11:29:53 +0800 Subject: [Paraview] HPC paraview In-Reply-To: <544E6049.6000003@lbl.gov> References: <544E6049.6000003@lbl.gov> Message-ID: <7FA1ABBE-0A92-4FE2-B68A-525941A98DE3@ivec.org> HI Burlen, Thanks again. Is there and easy way to verify that Paraview is using the GPU ours are TESLA C2075? Should I need to change the "MOD"(?) setting so it is rendering rather than compute? R. Christopher Bording Supercomputing Team-iVEC at UWA E: cbording at ivec.org T: +61 8 6488 6905 26 Dick Perry Avenue, Technology Park Kensington, Western Australia. 6151 On 27/10/2014, at 11:10 PM, Burlen Loring wrote: > Hi Christopher, > > Are you by any chance logged in with ssh X11 forwarding (ssh -X ...)? It seems the error you report comes up often in that context. X forwarding would not be the right way to run PV on your cluster. > > Depending on how your cluster is setup you may need to start up the xserver before launching PV, and make sure to close it after PV exits. IUn that scenario your xorg.conf would specify the nvidia driver and a screen for each gpu which you would refernece in the shell used to start PV through the DISPLAY variable. If you already have x11 running and screens configured then it's just a matter of setting the display variable correctly. When there are multiple GPU's per node then you'd need to set the display using mpi rank modulo the number of gpus per node. > > I'm not sure it matters that much but I don't think that you want --use-offscreen-rendering option. > > Burlen > > On 10/26/2014 10:23 PM, R C Bording wrote: >> Hi, >> Managed to get a "working version of Paraview-4.2.0.1" on our GPU cluster but when I try to run the >> parallelSphere.py script on more than one node it just hangs. Work like it is supposed to up to 12 cores on a single node. I am still trying work out if I a running on the GPU "tesla- C2070). >> >> Here is the list of cake configurations >> >> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >> -DParaView_FROM_GIT=OFF \ >> -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ >> -DENABLE_boost=ON \ >> -DENABLE_cgns=OFF \ >> -DENABLE_ffmpeg=ON \ >> -DENABLE_fontconfig=ON \ >> -DENABLE_freetype=ON \ >> -DENABLE_hdf5=ON \ >> -DENABLE_libxml2=ON \ >> -DENABLE_matplotlib=ON \ >> -DENABLE_mesa=OFF \ >> -DENABLE_mpi=ON \ >> -DENABLE_numpy=ON \ >> -DENABLE_osmesa=OFF \ >> -DENABLE_paraview=ON \ >> -DENABLE_png=ON \ >> -DENABLE_python=ON \ >> -DENABLE_qhull=ON \ >> -DENABLE_qt=ON \ >> -DENABLE_silo=ON \ >> -DENABLE_szip=ON \ >> -DENABLE_visitbridge=ON \ >> -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ >> -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ >> -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ >> -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >> -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >> -DUSE_SYSTEM_mpi=ON \ >> -DUSE_SYSTEM_python=OFF \ >> -DUSE_SYSTEM_qt=OFF \ >> -DUSE_SYSTEM_zlib=OFF ' >> >> The goal is to be able to support batch rendering on the whole cluster ~96 nodes. >> >> Also do I need set another environment variable in my Paraview module to make the Xlib >> warning go away? >> >> [cbording at f100 Paraview]$ mpirun -n 12 pvbatch --use-offscreen-rendering parallelSphere.py >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >> >> Is this related to my not being able to run across multiple nodes? >> >> R. Christopher Bording >> Supercomputing Team-iVEC at UWA >> E: cbording at ivec.org >> T: +61 8 6488 6905 >> >> 26 Dick Perry Avenue, >> Technology Park >> Kensington, Western Australia. >> 6151 >> >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbording at ivec.org Wed Oct 29 23:31:10 2014 From: cbording at ivec.org (R C Bording) Date: Thu, 30 Oct 2014 11:31:10 +0800 Subject: [Paraview] paraview performance In-Reply-To: References: Message-ID: Hi Utkarsh, Is there simple way to see if my installation of ParaView done using the ParaViewSuperbuild is configure with the correct gl libs to run on the GPUs. Should I need to install a version with Mesa to benchmark against or is there a way to that without installing a second version? Do the log files show if Paraview is rendering on Hardware or software? Cheers, Chris B. R. Christopher Bording Supercomputing Team-iVEC at UWA E: cbording at ivec.org T: +61 8 6488 6905 26 Dick Perry Avenue, Technology Park Kensington, Western Australia. 6151 On 30/10/2014, at 12:36 AM, Utkarsh Ayachit wrote: > That'd work. You can use the benchmark module [1] too to give you info > at a finer granularity. > > Utkarsh > > [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.benchmark.html > > On Mon, Oct 27, 2014 at 12:12 PM, R C Bording wrote: >> Hi, >> Is there a rendering model that you have for testing the performance of >> the paraview? >> I have install paraview on our GPU cluster and would like validated it >> someway other than >> just putting timing calls around the Render command in the parallelSphere.py >> script. >> >> Or is that sufficient? >> >> Cheers, >> Chris B >> >> R. Christopher Bording >> Supercomputing Team-iVEC at UWA >> E: cbording at ivec.org >> T: +61 8 6488 6905 >> >> 26 Dick Perry Avenue, >> Technology Park >> Kensington, Western Australia. >> 6151 >> >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian.butcher at oist.jp Thu Oct 30 05:39:49 2014 From: christian.butcher at oist.jp (Christian Butcher) Date: Thu, 30 Oct 2014 18:39:49 +0900 Subject: [Paraview] Installing Paraview with system IceT Message-ID: Running ccmake to build the Makefile for Paraview-4.2.0 informs me (when I set "VTK_USE_SYSTEM_ICET=yes") that it can't find icetConfig.cmake or icet-config.cmake "CMake Error at VTK/CMake/vtkModuleMacros.cmake:830 (find_package): By not providing "Findicet.cmake" in By not providing "Findicet.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "icet", but CMake did not find one. Could not find a package configuration file provided by "icet" with any of the following names: icetConfig.cmake icet-config.cmake Add the installation prefix of "icet" to CMAKE_PREFIX_PATH or set "icet_DIR" to a directory containing one of the above files. If "icet" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): ThirdParty/IceT/CMakeLists.txt:58 (vtk_module_third_party)" Installation of IceT-2.1.0 (appears to be the same version as packaged with PV) provided a IceTConfig.cmake file in /usr/lib. Construction of a symbolic link from /usr/lib/icetConfig.cmake -> /usr/lib/IceTConfig.cmake moves me past my first error (when I specify cmake option "icet_DIR=/usr/lib") but then ccmake complains that "CMake Error at VTK/CmakeLists.txt:480 (export) export given target "IceTCore" which is not built by this project. CMake Error at CMakeLists.txt:774 (export): export given target "IceTCore" which is not built by this project." Google searches suggest I should attempt to modify some file to use IMPORT statements, but I have no previous experience constructing CMakeList or .cmake configuration files. Any help setting this up (or confirmation that Paraview can be built with IceT as a system library) would be appreciated. From dkxls23 at gmail.com Thu Oct 30 08:24:56 2014 From: dkxls23 at gmail.com (Armin Wehrfritz) Date: Thu, 30 Oct 2014 14:24:56 +0200 Subject: [Paraview] PV 4.2.0 Color legend disappearing In-Reply-To: References: Message-ID: <54522E18.7000700@gmail.com> I have experienced it too, but cannot reproduce it! For me it happened so far only in a client-server setup. When I grab the surface (HDF5/XDMF files; 2D unstructured cells) and rotate or move it, the legend comes back, but will disappear as soon as I release the surface again. When copying the very same data to my local machine and visualizing it in a local ParaView session, everything works fine. Very odd indeed! My workstation: openSUSE 13.1 ParaView 4.2.0 Intel Core i7-4800QM QC Processor NVIDIA Quadro K2100M Graphics Card -Armin On 10/30/2014 01:26 AM, Scott, W Alan wrote: > In ParaView 4.2.0, I have found a few cases where the color legend > disappears, and I can?t get it back. Has anyone else seen this, and > found a way to replicate it? Mind passing the voodoo on how to > replicate this bug? > Thanks, > Alan > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From bloring at lbl.gov Thu Oct 30 13:40:00 2014 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 30 Oct 2014 10:40:00 -0700 Subject: [Paraview] HPC paraview In-Reply-To: <7FA1ABBE-0A92-4FE2-B68A-525941A98DE3@ivec.org> References: <544E6049.6000003@lbl.gov> <7FA1ABBE-0A92-4FE2-B68A-525941A98DE3@ivec.org> Message-ID: <545277F0.7000606@lbl.gov> to verify make a small job on 1 node. In the shell you are starting pvserver in, after you've done all the environment settings you need to to setup for paraview, run "glxinfo" and look for the gl vendor, gl version and gl renderer strings. these should give you info about your tesla. that can be done from your batch script or at the command prompt. some systems like cray mpiexec command (aprun) runs the program on a different set of nodes than the batch script itself, so for a system like that run "aprun -n 1 glxinfo". On 10/29/2014 08:29 PM, R C Bording wrote: > HI Burlen, > Thanks again. Is there and easy way to verify that Paraview is > using the GPU ours are TESLA C2075? > > Should I need to change the "MOD"(?) setting so it is rendering rather > than compute? > > R. Christopher Bording > Supercomputing Team-iVEC at UWA > E: cbording at ivec.org > T: +61 8 6488 6905 > > 26 Dick Perry Avenue, > Technology Park > Kensington, Western Australia. > 6151 > > > > > > On 27/10/2014, at 11:10 PM, Burlen Loring wrote: > >> Hi Christopher, >> >> Are you by any chance logged in with ssh X11 forwarding (ssh -X ...)? >> It seems the error you report comes up often in that context. X >> forwarding would not be the right way to run PV on your cluster. >> >> Depending on how your cluster is setup you may need to start up the >> xserver before launching PV, and make sure to close it after PV >> exits. IUn that scenario your xorg.conf would specify the nvidia >> driver and a screen for each gpu which you would refernece in the >> shell used to start PV through the DISPLAY variable. If you already >> have x11 running and screens configured then it's just a matter of >> setting the display variable correctly. When there are multiple GPU's >> per node then you'd need to set the display using mpi rank modulo the >> number of gpus per node. >> >> I'm not sure it matters that much but I don't think that you want >> --use-offscreen-rendering option. >> >> Burlen >> >> On 10/26/2014 10:23 PM, R C Bording wrote: >>> Hi, >>> Managed to get a "working version of Paraview-4.2.0.1" on our GPU >>> cluster but when I try to run the >>> parallelSphere.py script on more than one node it just hangs. Work >>> like it is supposed to up to 12 cores on a single node. I am still >>> trying work out if I a running on the GPU "tesla- C2070). >>> >>> Here is the list of cake configurations >>> >>> IBS_TOOL_CONFIGURE='-DCMAKE_BUILD_TYPE=Release \ >>> -DParaView_FROM_GIT=OFF \ >>> -DParaView_URL=$MYGROUP/vis/src/ParaView-v4.2.0-source.tar.gz \ >>> -DENABLE_boost=ON \ >>> -DENABLE_cgns=OFF \ >>> -DENABLE_ffmpeg=ON \ >>> -DENABLE_fontconfig=ON \ >>> -DENABLE_freetype=ON \ >>> -DENABLE_hdf5=ON \ >>> -DENABLE_libxml2=ON \ >>> -DENABLE_matplotlib=ON \ >>> -DENABLE_mesa=OFF \ >>> -DENABLE_mpi=ON \ >>> -DENABLE_numpy=ON \ >>> -DENABLE_osmesa=OFF \ >>> -DENABLE_paraview=ON \ >>> -DENABLE_png=ON \ >>> -DENABLE_python=ON \ >>> -DENABLE_qhull=ON \ >>> -DENABLE_qt=ON \ >>> -DENABLE_silo=ON \ >>> -DENABLE_szip=ON \ >>> -DENABLE_visitbridge=ON \ >>> -DMPI_CXX_LIBRARIES:STRING="$MPI_HOME/lib/libmpi_cxx.so" \ >>> -DMPI_C_LIBRARIES:STRING="$MPI_HOME/lib/libmpi.so" \ >>> -DMPI_LIBRARY:FILEPATH="$MPI_HOME/lib/libmpi_cxx.so" \ >>> -DMPI_CXX_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >>> -DMPI_C_INCLUDE_PATH:STRING="$MPI_HOME/include" \ >>> -DUSE_SYSTEM_mpi=ON \ >>> -DUSE_SYSTEM_python=OFF \ >>> -DUSE_SYSTEM_qt=OFF \ >>> -DUSE_SYSTEM_zlib=OFF ' >>> >>> The goal is to be able to support batch rendering on the whole >>> cluster ~96 nodes. >>> >>> Also do I need set another environment variable in my Paraview >>> module to make the Xlib >>> warning go away? >>> >>> [cbording at f100 Paraview]$ mpirun -n 12 pvbatch >>> --use-offscreen-rendering parallelSphere.py >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> Xlib: extension "NV-GLX" missing on display "localhost:50.0". >>> >>> Is this related to my not being able to run across multiple nodes? >>> >>> R. Christopher Bording >>> Supercomputing Team-iVEC at UWA >>> E: cbording at ivec.org >>> T: +61 8 6488 6905 >>> >>> 26 Dick Perry Avenue, >>> Technology Park >>> Kensington, Western Australia. >>> 6151 >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Powered bywww.kitware.com >>> >>> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> http://public.kitware.com/mailman/listinfo/paraview >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bloring at lbl.gov Thu Oct 30 13:41:40 2014 From: bloring at lbl.gov (Burlen Loring) Date: Thu, 30 Oct 2014 10:41:40 -0700 Subject: [Paraview] PV 4.2.0 Color legend disappearing In-Reply-To: References: Message-ID: <54527854.7040109@lbl.gov> yep I've seen that and a hosty of other flakeyness that I haven't had time to make bug reports about. using 4.1 for now. On 10/29/2014 04:26 PM, Scott, W Alan wrote: > In ParaView 4.2.0, I have found a few cases where the color legend > disappears, and I can?t get it back. Has anyone else seen this, and > found a way to replicate it? Mind passing the voodoo on how to > replicate this bug? > Thanks, > Alan > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwelland at anl.gov Thu Oct 30 14:14:43 2014 From: mwelland at anl.gov (Welland, Michael J.) Date: Thu, 30 Oct 2014 18:14:43 +0000 Subject: [Paraview] Integrate over a volume - integrating over surfaces? Message-ID: Hello, When I try to apply the 'Integrate variable' over a 3D object I get a strange (wrong) answer. In my simulation results the integral even changes in time, while the variable does not. I tried a simple cube with a constant function value of '1' everywhere, for which the integral is apparently zero. Am I missing something? I have had reasonable results in 2D, is there something with 3D I should be aware of? Cube function (PVD /VTU) attached. Thanks, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: u.pvd Type: application/octet-stream Size: 163 bytes Desc: u.pvd URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: u000000.vtu Type: application/octet-stream Size: 205932 bytes Desc: u000000.vtu URL: From utkarsh.ayachit at kitware.com Thu Oct 30 14:46:25 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Thu, 30 Oct 2014 14:46:25 -0400 Subject: [Paraview] Installing Paraview with system IceT In-Reply-To: References: Message-ID: Building ParaView with system IceT hasn't been tried/tested before. I suspect it would need some tinkering/patching to get working. Utkarsh On Thu, Oct 30, 2014 at 5:39 AM, Christian Butcher wrote: > Running ccmake to build the Makefile for Paraview-4.2.0 informs me > (when I set "VTK_USE_SYSTEM_ICET=yes") that it can't find > icetConfig.cmake or icet-config.cmake > > > "CMake Error at VTK/CMake/vtkModuleMacros.cmake:830 (find_package): > By not providing "Findicet.cmake" in By not providing > "Findicet.cmake" in CMAKE_MODULE_PATH this project has > asked CMake to find a package configuration file provided by "icet", but > CMake did not find one. > > Could not find a package configuration file provided by "icet" with any of > the following names: > > icetConfig.cmake > icet-config.cmake > > Add the installation prefix of "icet" to CMAKE_PREFIX_PATH or set > "icet_DIR" to a directory containing one of the above files. If "icet" > provides a separate development package or SDK, be sure it has been > installed. > Call Stack (most recent call first): > ThirdParty/IceT/CMakeLists.txt:58 (vtk_module_third_party)" > > > > Installation of IceT-2.1.0 (appears to be the same version as packaged > with PV) provided a IceTConfig.cmake file in /usr/lib. > > Construction of a symbolic link from > > /usr/lib/icetConfig.cmake -> /usr/lib/IceTConfig.cmake > > moves me past my first error (when I specify cmake option > "icet_DIR=/usr/lib") but then ccmake complains that > > "CMake Error at VTK/CmakeLists.txt:480 (export) > export given target "IceTCore" which is not built by this project. > CMake Error at CMakeLists.txt:774 (export): > export given target "IceTCore" which is not built by this project." > > Google searches suggest I should attempt to modify some file to use > IMPORT statements, but I have no previous experience constructing > CMakeList or .cmake configuration files. > > Any help setting this up (or confirmation that Paraview can be built > with IceT as a system library) would be appreciated. > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From cchukw1 at tigers.lsu.edu Thu Oct 30 17:29:42 2014 From: cchukw1 at tigers.lsu.edu (Chukwudi Chukwudozie) Date: Thu, 30 Oct 2014 16:29:42 -0500 Subject: [Paraview] ExtractSubset not working well in pvpython Message-ID: Hi, I have a structured grid computational domain of size 800,2,800. I want to extract the information along a line and so I do the following in my python script. ExtractSubset0 = ExtractSubset(guiName="ExtractSubset0",IncludeBoundary=0,VOI=[399, 399, 0, 0, 0, 799], SampleRateK=1, SampleRateJ=1, SampleRateI=1) data = servermanager.Fetch(ExtractSubset0) numPoints=data.GetNumberOfPoints() However, when I plot the information on that line, I see it has only extracted information between 0-399 in the z-coordinate direction. I even printed numPoints to confirm how much information is extracted and I get "numPoints=400". I am using PV 3.98.0. Any help on this will be appreciated. -- Chukwudi Chukwudozie cchukw1 at tigers.lsu.edu Craft and Hawkins Department of Petroleum Engineering Louisiana State University Patrick F. Taylor Hall (CEBA) Room 3429 Baton Rouge LA, 70803 Cell:3373546822 Office: 2255786064 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvanmoer at illinois.edu Thu Oct 30 17:57:15 2014 From: mvanmoer at illinois.edu (Vanmoer, Mark W) Date: Thu, 30 Oct 2014 21:57:15 +0000 Subject: [Paraview] Shapefiles? Message-ID: <7F781841FF1E044388AFA42B70703A7A8A0089EC@CHIMBX6.ad.uillinois.edu> Hi ParaView, I found this thread: www.paraview.org/pipermail/paraview/2012-December/027026.html indicating vtkGDALVectorReader would be added to mainline ParaView, and I do see an option load DEMs, but are ESRI ShapeFiles supported? I can't get any .shp files to be recognized or load. There's an earlier thread from 2011 discussing vtkgis_vector_reader, is that still the recommended ShapeFile loader? Thanks, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From wascott at sandia.gov Thu Oct 30 19:34:54 2014 From: wascott at sandia.gov (Scott, W Alan) Date: Thu, 30 Oct 2014 23:34:54 +0000 Subject: [Paraview] [EXTERNAL] Re: PV 4.2.0 Color legend disappearing In-Reply-To: <54522E18.7000700@gmail.com> References: <54522E18.7000700@gmail.com> Message-ID: <995d5188886344f4a72e423862a9434c@ES05AMSNLNT.srn.sandia.gov> Yep, that's the bug. I have seen it local server. Anyone else have any ideas how to replicate it? If anyone does see it, mind writing a state file and sending to me? It's a long shot, but maybe that will help us figure out what is going on. Thanks, Alan -----Original Message----- From: Armin Wehrfritz [mailto:dkxls23 at gmail.com] Sent: Thursday, October 30, 2014 6:25 AM To: Scott, W Alan; paraview at paraview.org Subject: [EXTERNAL] Re: [Paraview] PV 4.2.0 Color legend disappearing I have experienced it too, but cannot reproduce it! For me it happened so far only in a client-server setup. When I grab the surface (HDF5/XDMF files; 2D unstructured cells) and rotate or move it, the legend comes back, but will disappear as soon as I release the surface again. When copying the very same data to my local machine and visualizing it in a local ParaView session, everything works fine. Very odd indeed! My workstation: openSUSE 13.1 ParaView 4.2.0 Intel Core i7-4800QM QC Processor NVIDIA Quadro K2100M Graphics Card -Armin On 10/30/2014 01:26 AM, Scott, W Alan wrote: > In ParaView 4.2.0, I have found a few cases where the color legend > disappears, and I can't get it back. Has anyone else seen this, and > found a way to replicate it? Mind passing the voodoo on how to > replicate this bug? > Thanks, > Alan > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From furutaka.kazuyoshi at jaea.go.jp Fri Oct 31 00:29:49 2014 From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka) Date: Fri, 31 Oct 2014 13:29:49 +0900 (JST) Subject: [Paraview] "Annotate Time" filter in slice view? Message-ID: <20141031.132949.379518051.furutaka.kazuyoshi@jaea.go.jp> Dear ParaView experts, How can I use the "Annotate Time" source in Slice View? With a slice view, selecting it from the 'Sources' menu creates a render view and the source is displayed there... Or, are there any ways to show current Time in slice view? I'm using ParaView ver.4.2.0 on linux and windows PCs. Thanks in advance. Kazuyoshi -- Kazuyoshi Furutaka furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp From utkarsh.ayachit at kitware.com Fri Oct 31 00:57:39 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 31 Oct 2014 00:57:39 -0400 Subject: [Paraview] "Annotate Time" filter in slice view? In-Reply-To: <20141031.132949.379518051.furutaka.kazuyoshi@jaea.go.jp> References: <20141031.132949.379518051.furutaka.kazuyoshi@jaea.go.jp> Message-ID: This indeed is a missing feature in the Slice View. Please feel free to add a feature request to the bug tracker. Cleaning up the Slice View is on our todo list for near future. Utkarsh On Fri, Oct 31, 2014 at 12:29 AM, Kazuyoshi Furutaka wrote: > Dear ParaView experts, > > How can I use the "Annotate Time" source in Slice View? > With a slice view, selecting it from the 'Sources' menu > creates a render view and the source is displayed there... > > Or, are there any ways to show current Time in slice view? > > I'm using ParaView ver.4.2.0 on linux and windows PCs. > > Thanks in advance. > > Kazuyoshi > -- > Kazuyoshi Furutaka > furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview From michael.grabietz at img-online.de Fri Oct 31 01:59:40 2014 From: michael.grabietz at img-online.de (Michael Grabietz) Date: Fri, 31 Oct 2014 06:59:40 +0100 Subject: [Paraview] Structured Grid: strange view of surface+edges Message-ID: <5453254C.5000405@img-online.de> Hello, I have a structured grid which seems to be well formed. If I load the vtk file with ParaView 4.2 or 4.1 some strange lines appear if the display mode surface+edges is selected. See the attached screen shot. For the strange lines/edges no corresponding lines in the wireframe model can be found. The modes surface, wireframe or points are looking good. I checked the data again and again. I cannot find any issue in the structured grid. I have attached the vtk file and some screenshots. I also viewed the grid with a small self-written python application using VTK 6.1.0. It shows the same behaviour as ParaView. At the moment I do not have any idea how to go on. Any help is appreciated. Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: surface+edges_2.jpg Type: image/jpeg Size: 125009 bytes Desc: not available URL: -------------- next part -------------- # vtk DataFile Version 3.0 vtk output ASCII DATASET STRUCTURED_GRID DIMENSIONS 21 19 1 POINTS 399 float 521.142 0 164.25 572.07 0 164.25 622.998 0 164.25 673.925 0 164.25 724.853 0 164.25 775.78 0 164.25 826.708 0 164.25 877.636 0 164.25 928.563 0 164.25 979.491 0 164.25 1030.42 0 164.25 1081.35 0 164.25 1132.27 0 164.25 1183.2 0 164.25 1234.13 0 164.25 1285.06 0 164.25 1335.98 0 164.25 1386.91 0 164.25 1437.84 0 164.25 1488.77 0 164.25 1539.69 0 164.25 521.142 446.332 164.25 572.07 446.332 164.25 622.998 446.332 164.25 673.925 446.332 164.25 724.853 446.332 164.25 775.78 446.332 164.25 826.708 446.332 164.25 877.636 446.332 164.25 928.563 446.332 164.25 979.491 446.332 164.25 1030.42 446.332 164.25 1081.35 446.332 164.25 1132.27 446.332 164.25 1183.2 446.332 164.25 1234.13 446.332 164.25 1285.06 446.332 164.25 1335.98 446.332 164.25 1386.91 446.332 164.25 1437.84 446.332 164.25 1488.77 446.332 164.25 1539.69 446.332 164.25 466.689 738.05 158 523.497 738.05 158 580.305 738.05 158 637.113 738.05 158 693.921 738.05 158 750.729 738.05 158 807.536 738.05 158 864.344 738.05 158 921.152 738.05 158 977.96 738.05 158 1034.77 738.05 158 1091.58 738.05 158 1148.38 738.05 158 1205.19 738.05 158 1262 738.05 158 1318.81 738.05 158 1375.62 738.05 158 1432.42 738.05 158 1489.23 738.05 158 1546.04 738.05 158 1602.85 738.05 158 411.408 1034.2 150.125 474.186 1034.2 150.125 536.963 1034.2 150.125 599.741 1034.2 150.125 662.518 1034.2 150.125 725.296 1034.2 150.125 788.074 1034.2 150.125 850.851 1034.2 150.125 913.629 1034.2 150.125 976.407 1034.2 150.125 1039.18 1034.2 150.125 1101.96 1034.2 150.125 1164.74 1034.2 150.125 1227.52 1034.2 150.125 1290.29 1034.2 150.125 1353.07 1034.2 150.125 1415.85 1034.2 150.125 1478.63 1034.2 150.125 1541.41 1034.2 150.125 1604.18 1034.2 150.125 1666.96 1034.2 150.125 356.976 1325.8 143.25 425.632 1325.8 143.25 494.288 1325.8 143.25 562.943 1325.8 143.25 631.599 1325.8 143.25 700.254 1325.8 143.25 768.91 1325.8 143.25 837.566 1325.8 143.25 906.221 1325.8 143.25 974.877 1325.8 143.25 1043.53 1325.8 143.25 1112.19 1325.8 143.25 1180.84 1325.8 143.25 1249.5 1325.8 143.25 1318.16 1325.8 143.25 1386.81 1325.8 143.25 1455.47 1325.8 143.25 1524.12 1325.8 143.25 1592.78 1325.8 143.25 1661.43 1325.8 143.25 1730.09 1325.8 143.25 339.852 1417.54 141.391 410.357 1417.54 141.391 480.862 1417.54 141.391 551.367 1417.54 141.391 621.871 1417.54 141.391 692.376 1417.54 141.391 762.881 1417.54 141.391 833.386 1417.54 141.391 903.891 1417.54 141.391 974.396 1417.54 141.391 1044.9 1417.54 141.391 1115.41 1417.54 141.391 1185.91 1417.54 141.391 1256.42 1417.54 141.391 1326.92 1417.54 141.391 1397.42 1417.54 141.391 1467.93 1417.54 141.391 1538.43 1417.54 141.391 1608.94 1417.54 141.391 1679.44 1417.54 141.391 1749.95 1417.54 141.391 346.891 1621.62 137.257 419.253 1621.62 137.257 491.615 1621.62 137.257 563.977 1621.62 137.257 636.339 1621.62 137.257 708.701 1621.62 137.257 781.063 1621.62 137.257 853.425 1621.62 137.257 925.787 1621.62 137.257 998.149 1621.62 137.257 1070.51 1621.62 137.257 1142.87 1621.62 137.257 1215.23 1621.62 137.257 1287.6 1621.62 137.257 1359.96 1621.62 137.257 1432.32 1621.62 137.257 1504.68 1621.62 137.257 1577.04 1621.62 137.257 1649.41 1621.62 137.257 1721.77 1621.62 137.257 1794.13 1621.62 137.257 346.936 1621.95 137.25 419.292 1621.95 137.25 491.648 1621.95 137.25 564.004 1621.95 137.25 636.36 1621.95 137.25 708.716 1621.95 137.25 781.073 1621.95 137.25 853.429 1621.95 137.25 925.785 1621.95 137.25 998.141 1621.95 137.25 1070.5 1621.95 137.25 1142.85 1621.95 137.25 1215.21 1621.95 137.25 1287.57 1621.95 137.25 1359.92 1621.95 137.25 1432.28 1621.95 137.25 1504.63 1621.95 137.25 1576.99 1621.95 137.25 1649.35 1621.95 137.25 1721.7 1621.95 137.25 1794.06 1621.95 137.25 409.784 2086.65 122.625 473.905 2086.65 122.625 538.026 2086.65 122.625 602.147 2086.65 122.625 666.269 2086.65 122.625 730.39 2086.65 122.625 794.511 2086.65 122.625 858.632 2086.65 122.625 922.753 2086.65 122.625 986.874 2086.65 122.625 1050.99 2086.65 122.625 1115.12 2086.65 122.625 1179.24 2086.65 122.625 1243.36 2086.65 122.625 1307.48 2086.65 122.625 1371.6 2086.65 122.625 1435.72 2086.65 122.625 1499.84 2086.65 122.625 1563.96 2086.65 122.625 1628.08 2086.65 122.625 1692.21 2086.65 122.625 475.101 2569.6 113.75 530.664 2569.6 113.75 586.226 2569.6 113.75 641.789 2569.6 113.75 697.351 2569.6 113.75 752.914 2569.6 113.75 808.477 2569.6 113.75 864.039 2569.6 113.75 919.602 2569.6 113.75 975.164 2569.6 113.75 1030.73 2569.6 113.75 1086.29 2569.6 113.75 1141.85 2569.6 113.75 1197.41 2569.6 113.75 1252.98 2569.6 113.75 1308.54 2569.6 113.75 1364.1 2569.6 113.75 1419.67 2569.6 113.75 1475.23 2569.6 113.75 1530.79 2569.6 113.75 1586.35 2569.6 113.75 551.169 3132.04 114.87 596.764 3132.04 114.87 642.36 3132.04 114.87 687.955 3132.04 114.87 733.551 3132.04 114.87 779.146 3132.04 114.87 824.741 3132.04 114.87 870.337 3132.04 114.87 915.932 3132.04 114.87 961.527 3132.04 114.87 1007.12 3132.04 114.87 1052.72 3132.04 114.87 1098.31 3132.04 114.87 1143.91 3132.04 114.87 1189.5 3132.04 114.87 1235.1 3132.04 114.87 1280.7 3132.04 114.87 1326.29 3132.04 114.87 1371.89 3132.04 114.87 1417.48 3132.04 114.87 1463.08 3132.04 114.87 551.501 3134.5 114.875 597.053 3134.5 114.875 642.605 3134.5 114.875 688.157 3134.5 114.875 733.708 3134.5 114.875 779.26 3134.5 114.875 824.812 3134.5 114.875 870.364 3134.5 114.875 915.916 3134.5 114.875 961.468 3134.5 114.875 1007.02 3134.5 114.875 1052.57 3134.5 114.875 1098.12 3134.5 114.875 1143.68 3134.5 114.875 1189.23 3134.5 114.875 1234.78 3134.5 114.875 1280.33 3134.5 114.875 1325.88 3134.5 114.875 1371.43 3134.5 114.875 1416.99 3134.5 114.875 1462.54 3134.5 114.875 567.419 3252.2 115.578 610.885 3252.2 115.578 654.352 3252.2 115.578 697.818 3252.2 115.578 741.284 3252.2 115.578 784.75 3252.2 115.578 828.216 3252.2 115.578 871.682 3252.2 115.578 915.148 3252.2 115.578 958.614 3252.2 115.578 1002.08 3252.2 115.578 1045.55 3252.2 115.578 1089.01 3252.2 115.578 1132.48 3252.2 115.578 1175.94 3252.2 115.578 1219.41 3252.2 115.578 1262.88 3252.2 115.578 1306.34 3252.2 115.578 1349.81 3252.2 115.578 1393.28 3252.2 115.578 1436.74 3252.2 115.578 642.081 3804.25 118.875 680.909 3804.25 118.875 719.736 3804.25 118.875 758.563 3804.25 118.875 797.39 3804.25 118.875 836.218 3804.25 118.875 875.045 3804.25 118.875 913.872 3804.25 118.875 952.699 3804.25 118.875 991.527 3804.25 118.875 1030.35 3804.25 118.875 1069.18 3804.25 118.875 1108.01 3804.25 118.875 1146.84 3804.25 118.875 1185.66 3804.25 118.875 1224.49 3804.25 118.875 1263.32 3804.25 118.875 1302.14 3804.25 118.875 1340.97 3804.25 118.875 1379.8 3804.25 118.875 1418.63 3804.25 118.875 743.75 4556 122.5 776.26 4556 122.5 808.771 4556 122.5 841.281 4556 122.5 873.791 4556 122.5 906.302 4556 122.5 938.812 4556 122.5 971.322 4556 122.5 1003.83 4556 122.5 1036.34 4556 122.5 1068.85 4556 122.5 1101.36 4556 122.5 1133.87 4556 122.5 1166.38 4556 122.5 1198.89 4556 122.5 1231.41 4556 122.5 1263.92 4556 122.5 1296.43 4556 122.5 1328.94 4556 122.5 1361.45 4556 122.5 1393.96 4556 122.5 743.75 4794.4 122.5 774.783 4794.4 122.5 805.816 4794.4 122.5 836.849 4794.4 122.5 867.881 4794.4 122.5 898.914 4794.4 122.5 929.947 4794.4 122.5 960.98 4794.4 122.5 992.013 4794.4 122.5 1023.05 4794.4 122.5 1054.08 4794.4 122.5 1085.11 4794.4 122.5 1116.14 4794.4 122.5 1147.18 4794.4 122.5 1178.21 4794.4 122.5 1209.24 4794.4 122.5 1240.28 4794.4 122.5 1271.31 4794.4 122.5 1302.34 4794.4 122.5 1333.37 4794.4 122.5 1364.41 4794.4 122.5 743.75 4827.31 122.5 774.783 4827.31 122.5 805.816 4827.31 122.5 836.849 4827.31 122.5 867.881 4827.31 122.5 898.914 4827.31 122.5 929.947 4827.31 122.5 960.98 4827.31 122.5 992.013 4827.31 122.5 1023.05 4827.31 122.5 1054.08 4827.31 122.5 1085.11 4827.31 122.5 1116.14 4827.31 122.5 1147.18 4827.31 122.5 1178.21 4827.31 122.5 1209.24 4827.31 122.5 1240.28 4827.31 122.5 1271.31 4827.31 122.5 1302.34 4827.31 122.5 1333.37 4827.31 122.5 1364.41 4827.31 122.5 743.75 4929.28 122.5 774.783 4929.28 122.5 805.816 4929.28 122.5 836.849 4929.28 122.5 867.881 4929.28 122.5 898.914 4929.28 122.5 929.947 4929.28 122.5 960.98 4929.28 122.5 992.013 4929.28 122.5 1023.05 4929.28 122.5 1054.08 4929.28 122.5 1085.11 4929.28 122.5 1116.14 4929.28 122.5 1147.18 4929.28 122.5 1178.21 4929.28 122.5 1209.24 4929.28 122.5 1240.28 4929.28 122.5 1271.31 4929.28 122.5 1302.34 4929.28 122.5 1333.37 4929.28 122.5 1364.41 4929.28 122.5 743.75 5000 122.5 774.783 5000 122.5 805.816 5000 122.5 836.849 5000 122.5 867.881 5000 122.5 898.914 5000 122.5 929.947 5000 122.5 960.98 5000 122.5 992.013 5000 122.5 1023.05 5000 122.5 1054.08 5000 122.5 1085.11 5000 122.5 1116.14 5000 122.5 1147.18 5000 122.5 1178.21 5000 122.5 1209.24 5000 122.5 1240.28 5000 122.5 1271.31 5000 122.5 1302.34 5000 122.5 1333.37 5000 122.5 1364.41 5000 122.5 From nawijn at gmail.com Fri Oct 31 05:20:07 2014 From: nawijn at gmail.com (Marco Nawijn) Date: Fri, 31 Oct 2014 10:20:07 +0100 Subject: [Paraview] Structured Grid: strange view of surface+edges In-Reply-To: <5453254C.5000405@img-online.de> References: <5453254C.5000405@img-online.de> Message-ID: Hi Michael, Just for your information. I tried the file with Paraview 4.2.0 on 64 bit linux and see no such artifacts. So the file itself seems to be fine. Regards, Marco On Fri, Oct 31, 2014 at 6:59 AM, Michael Grabietz < michael.grabietz at img-online.de> wrote: > Hello, > > I have a structured grid which seems to be well formed. If I load the vtk > file with ParaView 4.2 or 4.1 some strange lines appear if the display mode > surface+edges is selected. See the attached screen shot. For the strange > lines/edges no corresponding lines in the wireframe model can be found. The > modes surface, wireframe or points are looking good. I checked the data > again and again. I cannot find any issue in the structured grid. I have > attached the vtk file and some screenshots. > > I also viewed the grid with a small self-written python application using > VTK 6.1.0. It shows the same behaviour as ParaView. > > At the moment I do not have any idea how to go on. Any help is appreciated. > > Michael > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From burlen.loring at gmail.com Fri Oct 31 11:48:43 2014 From: burlen.loring at gmail.com (Burlen Loring) Date: Fri, 31 Oct 2014 08:48:43 -0700 Subject: [Paraview] help with stereoscopic 3d Message-ID: <5453AF5B.9070005@gmail.com> I can save an animation/screenshot without issue, however when I select option for stereoscopic 3d left/right big gaps appear in the volume rendering. image below. Does anyone have any insight into why this is happeing, or can suggest a workaround? I'm using 256 cores, the dataset is a large image volume and I need the cores for the memory. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: adjifiih.png Type: image/png Size: 373027 bytes Desc: not available URL: From utkarsh.ayachit at kitware.com Fri Oct 31 13:48:37 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 31 Oct 2014 13:48:37 -0400 Subject: [Paraview] Structured Grid: strange view of surface+edges In-Reply-To: References: <5453254C.5000405@img-online.de> Message-ID: Same for me -- I cannot reproduce the problem. It could potentially be a driver/OpenGL issue? Utkarsh On Fri, Oct 31, 2014 at 5:20 AM, Marco Nawijn wrote: > Hi Michael, > > Just for your information. I tried the file with Paraview 4.2.0 on 64 bit > linux > and see no such artifacts. So the file itself seems to be fine. > > Regards, > > Marco > > > On Fri, Oct 31, 2014 at 6:59 AM, Michael Grabietz > wrote: >> >> Hello, >> >> I have a structured grid which seems to be well formed. If I load the vtk >> file with ParaView 4.2 or 4.1 some strange lines appear if the display mode >> surface+edges is selected. See the attached screen shot. For the strange >> lines/edges no corresponding lines in the wireframe model can be found. The >> modes surface, wireframe or points are looking good. I checked the data >> again and again. I cannot find any issue in the structured grid. I have >> attached the vtk file and some screenshots. >> >> I also viewed the grid with a small self-written python application using >> VTK 6.1.0. It shows the same behaviour as ParaView. >> >> At the moment I do not have any idea how to go on. Any help is >> appreciated. >> >> Michael >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > From utkarsh.ayachit at kitware.com Fri Oct 31 14:34:48 2014 From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit) Date: Fri, 31 Oct 2014 14:34:48 -0400 Subject: [Paraview] [EXTERNAL] 4.2.0 stereo interlace problem In-Reply-To: <9024e1abaf1b4f7188f7e4ef8200a927@ES05AMSNLNT.srn.sandia.gov> References: <9024e1abaf1b4f7188f7e4ef8200a927@ES05AMSNLNT.srn.sandia.gov> Message-ID: Just pushed a fix for this. Patch attached. Utkarsh On Wed, Oct 29, 2014 at 8:51 PM, Scott, W Alan wrote: > Jean, > > > > I just tried with PV 4.2.0, Linux Mesa (local server), Linux hardware > rendering, and my local Windows 7 box (Kitware download), and they all > worked with ?stereo-type=Interlaced. At least I believe they worked, > nothing crashed and the image looked good. (Note that the command is > Interlaced, not interlace). Other than that, the only thing I can think of > is to delete your config files. > http://www.paraview.org/Wiki/ParaView_Settings_Files. > > > > Alan > > > > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jean > Hertzberg > Sent: Wednesday, October 29, 2014 5:07 PM > To: paraview at paraview.org > Subject: [EXTERNAL] [Paraview] 4.2.0 stereo interlace problem > > > > Hi. > > I have not been able to get PV 4.2.0 to work in stereo interlace mode on my > Windows 7 64 bit system. Default mode seems to be red-blue, and that works > fine, but I get this error on startup when I specify ?stereo-type=Interlace > > > > ERROR: In > C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLCamera.cxx, > line 167 > > vtkOpenGLCamera (000000000B119790): failed after Render 1 OpenGL errors > detected > > 0 : (1282) Invalid operation > > > > PV 4.0.1 starts in interlace mode with no problem on the same system. > > Suggestions? I didn?t see any known bugs regarding this. > > > > Jean Hertzberg > > > > Dept. Mechanical Engineering > > University of Colorado, Boulder > > > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-BUG-15093-Fixed-issue-with-stereo-rendering.patch Type: text/x-patch Size: 11844 bytes Desc: not available URL: