We have plans to implement exactly what you want, in Python, for the next release. Currently, the state is the only way to do this.
-berk On Sat, Jan 24, 2009 at 7:32 AM, Pierre JUILLARD <[email protected]> wrote: > Hi Jérôme, > > Thanks for your answer. > It helps, but the pvsm file stored contains really every ParaView settings. > > I am going to study closely its content: do you know if some data are > optional in the sense, if there is no value in the pvsm file, a default > value considered instead by ParaView? > Actually, I'm not interested in most of the data in the pvsm file I saved > because I would like then start from a pvsm file to execute ParaView in > batch, and save the results in vtk xml file for instance. > Thus, the only data which would be kept are nearly all related to the > filters used, and only them. For other settings, defaut values are ok: they > do not actually to be set. > Currently, the only additional important information I see is the increment > at which filters have to be applied. > > As I foresee to write then the pvsm file from another application, I would > like to simplify it as much as possible. I have tried "cleaning" the > obtained pvsm file, keeping only the tags related to the filters I have been > using, but it doesn't work well: when loaded back, ParaView hangs on the > screen "Create View" (3D View, 2D View, ...) > I'm gonna do some experiments to see what can be cleaned or not. > > > I thank you again for your help. > Regards, > > Pierre > > > > 2009/1/24 Jérôme <[email protected]> >> >> Hi, >> >> When I use "Save state", I have this result. Isn't it the case for you? >> My pvsm files contain the user parameters and pipelines (except maybe >> the writer, but I used to use "Save data" from the file menu, so they >> are not really in the pipeline..) >> >> Regards, >> Jerome >> >> 2009/1/24 Pierre JUILLARD <[email protected]>: >> > Hi all, >> > >> > >> > I am wondering if it is possible to export a ParaView session in a file, >> > which could then be loaded back for execution. >> > I mean is there a way to save all user choices of the session pipeline, >> > such >> > that it could be executed again once reloaded in ParaView? >> > The result file produced could be close to a pvsm file, but with user >> > values >> > for each user inputs needed to set readers filters, and writters >> > working. It >> > would describe the chain of plugins that was previously run, as well as >> > all >> > their input data. >> > >> > I thank you in advance for your help. >> > Cheers, >> > >> > >> > Pierre >> > >> > _______________________________________________ >> > ParaView mailing list >> > [email protected] >> > http://www.paraview.org/mailman/listinfo/paraview >> > >> > > > > _______________________________________________ > ParaView mailing list > [email protected] > http://www.paraview.org/mailman/listinfo/paraview > > _______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview
