Re: [Paraview] Using ParaviewWeb examples
Hi Tom, The ParaviewWeb examples always live in a sub-directory of the component they illustrate - so here, this is the Composite example, so '..' just refers to 'Composite'. If you look in the left menu, you can see that 'Composite' is grouped into ' Component/Native'. That's the directory it's in. '../../BackgroundColor' is a sibling directory to 'Composite', so it will also be in ' Component/Native' Generally you can follow the '..' out from the example sub-directory and figure out where you are. Hope that helps, Aron On Mon, Feb 19, 2018 at 2:38 PM, Sgouros, Thomas wrote: > Hello all: > > When I see a Paraviewweb example like this (from Composite.html): > > import CompositeComponent from '..'; > import BGColorComponent from '../../BackgroundColor'; > > Where should I look for BackgroundColor and CompositeComponent? I feel > sure I could find them eventually, but is there another search algorithm > besides brute force? > > Thank you, > > -Tom > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > https://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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Using ParaviewWeb examples
I think you're looking for the setup doc: https://kitware.github.io/paraviewweb/docs/setup.html It gives you a sample webpack config. Nearly all the paraviewweb dependencies are contained in kw-websuite, as documented on that page. The examples as they stand use a bit of magic, you are right, so they can be embedded in the documentation pages. AFAIK, we don't have an install option to make a stand-alone example. Regards, Aron On Mon, Feb 19, 2018 at 3:59 PM, Sgouros, Thomas wrote: > Thank you. it would be great also to have pointers to normalize.css, and > the webpack and package configs for these examples. They are more like > puzzles than examples in their current state, with the challenge to find > all the missing pieces and guess how to put them together. Am I missing > some intro that steps me through those parts? Or is there a way to see the > whole example laid out with those other pieces? Maybe an npm install option > that will give me these examples on my disk? > > I see fragments of examples on this page: https://kitware.github. > io/paraviewweb/docs/import.html , but apparently it is not enough for me. > > Thank you, > > -Tom > > On Mon, Feb 19, 2018 at 2:48 PM, Aron Helser > wrote: > >> Hi Tom, >> The ParaviewWeb examples always live in a sub-directory of the component >> they illustrate - so here, this is the Composite example, so '..' just >> refers to 'Composite'. >> If you look in the left menu, you can see that 'Composite' is grouped >> into ' Component/Native'. That's the directory it's in. >> '../../BackgroundColor' >> is a sibling directory to 'Composite', so it will also be in ' >> Component/Native' >> >> Generally you can follow the '..' out from the example sub-directory and >> figure out where you are. >> >> Hope that helps, >> Aron >> >> On Mon, Feb 19, 2018 at 2:38 PM, Sgouros, Thomas < >> thomas_sgou...@brown.edu> wrote: >> >>> Hello all: >>> >>> When I see a Paraviewweb example like this (from Composite.html): >>> >>> import CompositeComponent from '..'; >>> import BGColorComponent from '../../BackgroundColor'; >>> >>> Where should I look for BackgroundColor and CompositeComponent? I feel >>> sure I could find them eventually, but is there another search algorithm >>> besides brute force? >>> >>> Thank you, >>> >>> -Tom >>> >>> ___ >>> Powered by www.kitware.com >>> >>> Visit other Kitware open-source projects at >>> http://www.kitware.com/opensource/opensource.html >>> >>> Please keep messages on-topic and check the ParaView Wiki at: >>> http://paraview.org/Wiki/ParaView >>> >>> Search the list archives at: http://markmail.org/search/?q=ParaView >>> >>> Follow this link to subscribe/unsubscribe: >>> https://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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Conversion error
Hi Nitisha, It's hard to know what the problem might be without knowing what steps you are taking to convert the files - please provide some more details. I would guess it's a problem in the conversion software, not ParaView. Regards, Aron On Mon, Mar 19, 2018 at 5:50 PM, Nitisha Ahuja wrote: > Hello all, > I am facing an issue in which, I am trying to convert post.out files from > Converge into paraview files. For few files I get the following error > : > > I am not sure whether this is the right place to ask this question, as the > problem can be in my software too. > > But if anyone knows what could be the reason behind failure in conversion > of these file, please let me know. > > P.S.. I see this error on some random files. > > Best regards > Nitisha > > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > https://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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] ParaView-Superbuild Win10 Errors
Jamil, Make sure you scroll up and find the first error - ninja is a parallel build system, so the build will continue on other threads after the first error. Then maybe you can solve that first error, and others will be fixed. It looks like an earlier error caused 'quat.lib' not to be built, but it's hard to tell -Aron On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich wrote: > Hi Shawn, > > thanks a lot for the tip, configuring worked with the Visual Studio 12.0 > compiler! Now I am getting a lot of build errors though. > > C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning > C4244: '=' : conversion from 'double' to 'float', possible loss of data > [255/256] Linking C shared library bin\hdf5.dll >Creating library bin\hdf5.lib and object bin\hdf5.exp > [256/256] Linking C shared library bin\hdf5_hl.dll >Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp > ninja: build stopped: subcommand failed. > > LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' > [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll > [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri > nt_messages.dir\vrpn_print_messages.C.obj > [5/97] Building CXX object client_src\CMakeFiles\ff_clien > t.dir\ff_client.C.obj > [6/97] Building CXX object client_src\CMakeFiles\phan_cli > ent.dir\phan_client.C.obj > [7/97] Building CXX object client_src\CMakeFiles\printval > s.dir\printvals.C.obj > ninja: build stopped: subcommand failed. > CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 > (message): > Failed with exit code 1 > > These are some examples. My it be possible that the ninja version is not > suited either? Do you know what ninja version you were building the > superbuild with? > > Thanks a lot, > Jamil > > (P.s. Sorry Shawn for my posting mistake) > > 2018-03-27 16:07 GMT+02:00 Shawn Waldon : > >> Hi Jamil, >> >> Please keep replies CCed to the mailing list (Reply All) so others can >> contribute to the discussion (or find answers to their own problems later >> in the archives). >> >> We use the most recent release of ninja on most of our build machines (so >> that one should work). I'm not sure why you are getting that error >> messages from what you have included... maybe others on the list can chime >> in or you can give more details. >> >> Shawn >> >> On Tue, Mar 27, 2018 at 6:40 AM, Jamil Goettlich < >> jamil.goettl...@gmail.com> wrote: >> >>> Hi Shawn, >>> >>> thanks a lot for the tip, configuring worked with the Visual Studio 12.0 >>> compiler! Now I am getting a lot of build errors though. >>> >>> C:\Tools\paraview\superbuild\hdf5\src\src\H5Ztrans.c(1135) : warning >>> C4244: '=' : conversion from 'double' to 'float', possible loss of data >>> [255/256] Linking C shared library bin\hdf5.dll >>>Creating library bin\hdf5.lib and object bin\hdf5.exp >>> [256/256] Linking C shared library bin\hdf5_hl.dll >>>Creating library bin\hdf5_hl.lib and object bin\hdf5_hl.exp >>> ninja: build stopped: subcommand failed. >>> >>> LINK : fatal error LNK1104: cannot open file 'quat\quat.lib' >>> [3/97] Linking CXX shared library gpsnmealib\gpsnmea.dll >>> [4/97] Building CXX object client_src\CMakeFiles\vrpn_pri >>> nt_messages.dir\vrpn_print_messages.C.obj >>> [5/97] Building CXX object client_src\CMakeFiles\ff_clien >>> t.dir\ff_client.C.obj >>> [6/97] Building CXX object client_src\CMakeFiles\phan_cli >>> ent.dir\phan_client.C.obj >>> [7/97] Building CXX object client_src\CMakeFiles\printval >>> s.dir\printvals.C.obj >>> ninja: build stopped: subcommand failed. >>> CMake Error at C:/Tools/paraview/superbuild/sb-vrpn-build.cmake:43 >>> (message): >>> Failed with exit code 1 >>> >>> These are some examples. My it be possible that the ninja version is not >>> suited either? Do you know what ninja version you were building the >>> superbuild with? >>> >>> Thanks a lot, >>> Jamil >>> >>> 2018-03-26 17:21 GMT+02:00 Shawn Waldon : >>> Hi Jamil, I'm not sure if this will get you all the way to a build, but here are some pointers: We build with the visual studio compiler but use the Ninja generator since it is significantly faster than VS. VS 2017 may not work. Our binaries are built with 2013 right now and we plan to move to 2015 after the current release cycle. If you want what you are building to be compatible with the Kitware binaries, you will need to use 2013. Also, I believe there are compiler errors if you use 2017 right now. To build with Ninja and VS compilers, you need to be in a visual studio command prompt rather than a normal shell (it sets a bunch of environment vars, which I think is what is missing in your last example). To convert a normal command prompt you run (example is for VS2015, your path may differ) 'C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/vcvarsall.bat x64' in your shell and it will set the environment variables for you
Re: [Paraview] ParaView-Superbuild Win10 Errors
I don't know how or why vrpn is used by paraview, so I'll have to defer to others... On Wed, Mar 28, 2018 at 8:23 AM, Jamil Goettlich wrote: > Hi Aron, > > thank you for the reply. Youre right, there was an error way at the > beginning concerning quat.lib. > It seems like linking vrpn.lib failed because quat.lib cannot be > recognized. > Here is the full error (Using Win10, Compiler Visual Studio12.0 (cl.exe), > ninja build system. > Also, I enabled VRPN_USE_HID and disabled VRPN_USE_LOCAL_HIDAPI). > > [157/254] Linking CXX shared library vrpn.dll > FAILED: vrpn.dll vrpn.lib > cmd.exe /C "cd . && C:\KermsInstalls\cmake\bin\cmake.exe -E vs_link_dll > --intdir=CMakeFiles\vrpn.dir --manifests -- > C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe > /nologo CMakeFiles\vrpn.dir\vrpn_Analog.C.obj > CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj > CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj > CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj > CMakeFiles\vrpn.dir\vrpn_Button.C.obj > CMakeFiles\vrpn.dir\vrpn_Connection.C.obj > CMakeFiles\vrpn.dir\vrpn_Dial.C.obj > CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj > CMakeFiles\vrpn.dir\vrpn_FileController.C.obj > CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj > CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj > CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj > CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj > CMakeFiles\vrpn.dir\vrpn_Imager.C.obj > CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj > CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj > CMakeFiles\vrpn.dir\vrpn_Poser.C.obj > CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj > CMakeFiles\vrpn.dir\vrpn_Serial.C.obj > CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj > CMakeFiles\vrpn.dir\vrpn_Shared.C.obj > CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj > CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj > CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib > /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib > ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib > shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && > cd ." > LINK: command "C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\link.exe /nologo > CMakeFiles\vrpn.dir\vrpn_Analog.C.obj > CMakeFiles\vrpn.dir\vrpn_Analog_Output.C.obj > CMakeFiles\vrpn.dir\vrpn_Auxiliary_Logger.C.obj > CMakeFiles\vrpn.dir\vrpn_BaseClass.C.obj > CMakeFiles\vrpn.dir\vrpn_Button.C.obj > CMakeFiles\vrpn.dir\vrpn_Connection.C.obj > CMakeFiles\vrpn.dir\vrpn_Dial.C.obj > CMakeFiles\vrpn.dir\vrpn_FileConnection.C.obj > CMakeFiles\vrpn.dir\vrpn_FileController.C.obj > CMakeFiles\vrpn.dir\vrpn_ForceDevice.C.obj > CMakeFiles\vrpn.dir\vrpn_Forwarder.C.obj > CMakeFiles\vrpn.dir\vrpn_ForwarderController.C.obj > CMakeFiles\vrpn.dir\vrpn_FunctionGenerator.C.obj > CMakeFiles\vrpn.dir\vrpn_Imager.C.obj > CMakeFiles\vrpn.dir\vrpn_LamportClock.C.obj > CMakeFiles\vrpn.dir\vrpn_Mutex.C.obj > CMakeFiles\vrpn.dir\vrpn_Poser.C.obj > CMakeFiles\vrpn.dir\vrpn_RedundantTransmission.C.obj > CMakeFiles\vrpn.dir\vrpn_Serial.C.obj > CMakeFiles\vrpn.dir\vrpn_SerialPort.C.obj > CMakeFiles\vrpn.dir\vrpn_Shared.C.obj > CMakeFiles\vrpn.dir\vrpn_SharedObject.C.obj > CMakeFiles\vrpn.dir\vrpn_Sound.C.obj CMakeFiles\vrpn.dir\vrpn_Text.C.obj > CMakeFiles\vrpn.dir\vrpn_Tracker.C.obj /out:vrpn.dll /implib:vrpn.lib > /pdb:vrpn.pdb /dll /version:0.0 /machine:x64 /INCREMENTAL:NO quat\quat.lib > ws2_32.lib winmm.lib kernel32.lib user32.lib gdi32.lib winspool.lib > shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib > /MANIFEST /MANIFESTFILE:vrpn.dll.manifest" failed (exit code 1181) with > the following output: > LINK : fatal error LNK1181: cannot open input file 'quat\quat.lib' > [158/254] Linking CXX shared library gpsnmealib\gpsnmea.dll > > I checked for quat.lib but there is only quat.dll in the superbuild > folder. Is there a flag to set for building the quat library statically or > to tell vrpn to look for a dll? > > Thank a lot > Jamil > > 2018-03-27 20:24 GMT+02:00 Aron Helser : > >> Jamil, >> Make sure you scroll up and find the first error - ninja is a parallel >> build system, so the build will continue on other threads after the first >> error. Then maybe you can solve that first error, and others will be fixed. >> >> It looks like an earlier error caused 'quat.lib' not to be built, but >> it's hard to tell >> -Aron >> >> On Tue, Mar 27, 2018 at 10:37 AM, Jamil Goettlich < >> jamil.goettl...@gmail.com> wrote: >> >>> Hi Shawn, >>> >>> thanks a lot for the tip, configuring worked with t
Re: [Paraview] How to interrupt macros/Python script ?
How does the debugger interact with python scripts in ParaView? In debugging stand-alone scripts, I'll often insert: import pdb; pdb.set_trace() to trigger the debugger. I suspect you might be able to use 'rdbg' and use that connection? -Aron On Fri, Mar 30, 2018 at 4:36 AM, Mathieu Westphal < mathieu.westp...@kitware.com> wrote: > Hello Miguel, > > The simplest way to do that, especially when debugging, is to raise an > error. > > raise ValueError() > > Best regards, > > Mathieu Westphal > > On Fri, Mar 30, 2018 at 8:52 AM, Miguel Aguirre > wrote: > >> Hello, >> >> >> >> I’m testing some macros and Python Shell scripts. One of them requires an >> iteration: it places the slice plane at several positions in order to >> integrate values at each position. However, I found that once the >> macro/script is executed, it is impossible to stop it (which annoys the >> debugging process). I already tested "exit()" command in the Python Shell >> but it does not works. There is way to interrupt the process? >> >> >> >> Thanks in advance. >> >> Miguel Angel AGUIRRE >> >> ___ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> https://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 > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > https://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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] How to setup the version number of an XML plugin ?
Hi! Looking here: https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Embedding_Python_Source_as_Modules it seems like you can specify the version number with CMakeLists.txt, but not with the XML file. HTH, Aron On Mon, Jun 11, 2018 at 3:57 AM, LB wrote: > Hi, > > I've defined a plugin that gathers a set of python programmable filters > into an XML file. > > How can I setup in this XML file the version number that ParaView displays > in the plugin manager window ? > > Regards, > > Loïc > > ___ > Powered by www.kitware.com > > ParaView discussion is moving! Please visit https://discourse.paraview. > org/ for future posts. > > Visit other Kitware open-source projects at http://www.kitware.com/ > opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Search the list archives at: http://markmail.org/search/?q=ParaView > > Follow this link to subscribe/unsubscribe: > https://public.kitware.com/mailman/listinfo/paraview > > ___ Powered by www.kitware.com ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts. Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: https://public.kitware.com/mailman/listinfo/paraview
