Hi Jérôme,<br><br>Thanks for your answer.<br>It helps, but the pvsm file stored contains really every ParaView settings.<br><br>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?<br>
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.<br>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.<br>
Currently, the only additional important information I see is the increment at which filters have to be applied.<br><br>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, ...)<br>
I'm gonna do some experiments to see what can be cleaned or not.<br><br><br>I thank you again for your help.<br>Regards,<br><br>Pierre<br><br><br><br><div class="gmail_quote">2009/1/24 Jérôme <span dir="ltr"><<a href="mailto:jerome.velut@gmail.com">jerome.velut@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
When I use "Save state", I have this result. Isn't it the case for you?<br>
My pvsm files contain the user parameters and pipelines (except maybe<br>
the writer, but I used to use "Save data" from the file menu, so they<br>
are not really in the pipeline..)<br>
<br>
Regards,<br>
Jerome<br>
<br>
2009/1/24 Pierre JUILLARD <<a href="mailto:pierre.juillard@gmail.com">pierre.juillard@gmail.com</a>>:<br>
<div><div></div><div class="Wj3C7c">> Hi all,<br>
><br>
><br>
> I am wondering if it is possible to export a ParaView session in a file,<br>
> which could then be loaded back for execution.<br>
> I mean is there a way to save all user choices of the session pipeline, such<br>
> that it could be executed again once reloaded in ParaView?<br>
> The result file produced could be close to a pvsm file, but with user values<br>
> for each user inputs needed to set readers filters, and writters working. It<br>
> would describe the chain of plugins that was previously run, as well as all<br>
> their input data.<br>
><br>
> I thank you in advance for your help.<br>
> Cheers,<br>
><br>
><br>
> Pierre<br>
><br>
</div></div>> _______________________________________________<br>
> ParaView mailing list<br>
> <a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
> <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
><br>
><br>
</blockquote></div><br>