Hi, There have been a lot of rendering improvements between 4.4 and 5.2 so you'll definitely want to use 5.2 for the best performance. Also, 5.2 has a lot of Catalyst and Live improvements. You shouldn't need to output images or Cinema data bases in order to get the Live functionality.
Andy On Tue, Jan 3, 2017 at 3:38 AM, 张驭洲 <[email protected]> wrote: > > Hi Andy, > > Thanks for your reply! Now I can run the CxxFullExample, but I've > encountered some more problems about it. > > 1.The CxxFullExample has a 70x60x44 unstructured grid, and it runs > relatively quickly. A truncated sample output of Timer Log is as follows: > > RenderView::Update, 0.161069 seconds > PVTrivialProducer::GatherInformation, 0.051133 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.336371 seconds > FullRes Data Migration, 0.336246 seconds > Still Render, 0.034509 seconds > RenderView::Update, 0.149692 seconds > PVTrivialProducer::GatherInformation, 0.051577 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.322268 seconds > FullRes Data Migration, 0.322144 seconds > Still Render, 0.033618 seconds > RenderView::Update, 0.156578 seconds > PVTrivialProducer::GatherInformation, 0.051578 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.342933 seconds > FullRes Data Migration, 0.342809 seconds > Still Render, 0.033976 seconds > > However, after I modified the grid to a 700x60x44 one and nothing else > were modified, it became fairly slow when running. Also, a truncated sample > output of Timer Log: > > RenderView::Update, 1.48987 seconds > PVTrivialProducer::GatherInformation, 0.493497 seconds > vtkSMRepresentationProxy::GetRepresente, 2.44198 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.480933 seconds > FullRes Data Migration, 0.480786 seconds > Still Render, 0.116726 seconds > OpenGL Dev Render, 0.020361 seconds > RenderView::Update, 1.51507 seconds > PVTrivialProducer::GatherInformation, 0.493821 seconds > vtkSMRepresentationProxy::GetRepresente, 2.47383 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.481844 seconds > FullRes Data Migration, 0.481686 seconds > Still Render, 0.116896 seconds > OpenGL Dev Render, 0.020697 seconds > RenderView::Update, 1.50415 seconds > PVTrivialProducer::GatherInformation, 0.491896 seconds > vtkSMRepresentationProxy::GetRepresente, 2.44277 seconds > vtkSMDataDeliveryManager: Deliver Geome, 0.474105 seconds > FullRes Data Migration, 0.473959 seconds > Still Render, 0.114223 seconds > OpenGL Dev Render, 0.020254 seconds > > Comparing the two outputs, I find that the time spent in some processes > became about 10 times longer, as the dataset became 10 times larger, but > some other processes didn't take 10 times longer time. The biggest > difference is vtkSMRepresentationProxy::GetRepresente, which takes more > than 2.4s per frame in the bigger dataset example while in the smaller > dataset example it takes less than 0.01s per frame. I don't know what the > program does in the vtkSMRepresentationProxy::GetRepresente method. > Actually I only know about Still Render. Could you please give me a brief > introduction to these items? And, as Catalyst is designed for in situ > visualization of very large dataset, is there any method to make the > example run faster? > > 2.When I create Catelyst Python scripts in the ParaView GUI, I have to > enable all of the *Live Visualization, Output to Cinema *and *Output > rendering components i.e. views *options to get live visualization of the > simulation in the PV GUI, but under this setting, it generates lots of > pictures, which I don't need. If I don't enable either of *Output to > Cinema *or *Output rendering components i.e. views, *I could not get the > live visualization, and of course no picture is generated. But what's the > function of the *Live Visualization *option? > > All of the above are situations in the PV 4.4.0 in the client-server mode. > As for PV 5.2, I have some problems in using it in the client-server mode. > Hope you can help me. Thank you again! > > -Zhang > > -----原始邮件----- > *发件人:* "Andy Bauer" <[email protected]> > *发送时间:* 2017年1月2日 星期一 > *收件人:* "张驭洲" <[email protected]> > *抄送:* "[email protected]" <[email protected]> > *主题:* Re: [Paraview] How to start the Catalyst example: CxxFullExample > > Hi, > > The Catalyst examples have been moved to the ParaView source repo. I'd > recommend using the newest version of ParaView as well as Catalyst since > there have been a lot of improvements since PV 4.4. > > For the CxxFullExample, if you've built it with Catalyst enabled you can > run it as you've done as well as pass in Catalyst Python scripts to use > through command line arguments. > > Andy > > On Fri, Dec 30, 2016 at 10:08 PM, 张驭洲 <[email protected]> wrote: > >> >> >> Hello everyone, >> >> I'm learning the ParaView Catalyst by starting at the CxxFullExample, >> which is one of the Catalyst examples from https://github.com/Kitware/Par >> aViewCatalystExampleCode-MOVED-. I have compiled and built it and got >> the CxxFullExample executable. It is said that it's a full example of a >> simulation code interfacing with Catalyst, but I don't know how to execute >> it. I typed "./CxxFullExample" in the command line under the build >> directory of the example and nothing happened. I read the Chapter 2 of the >> Catalyst User's Guide and found what's mainly discussed is about creating >> ParaView Catalyst scripts in ParaView. It is said that to create ParaView >> Catalyst scripts in ParaView, I must have a representative dataset, and the >> Appendix 7.1.2 of the guide has a script that can be used to create the >> dataset. I managed to get lots of files named "filename_x_x.vtu" and >> "filename_x.pvtu"(x is a number) by typing "./CxxFullExample ./pvpython >> python.py"(python.py i s the script from the appendix 7.1.2 of the user's >> guide) in the command line under the bin directory of ParaView 4.4.0. Then >> I followed the section 2.2 of the user's guide with one of the file I >> generated above, only to get another script. Actually, what I want is a >> condition shown at www.kitware.com/blog/home/post/722, but after read >> the section 2.3 of the user's guide, I'm still unable to implement it. How >> should I organize the Catalyst enabled simulation and ParaView? Can it work >> in the client-server mode? Can I get it to work without much knowledge of >> Python? Maybe I'm on the wrong way of learning Catalyst, if so, you can >> ignore my questions and just tell me the right way. Thanks a lot! >> >> -Zhang >> >> >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects 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: >> 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 Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
