Michael & Christian,

Thanks for your emails. I've been doing some other things, but am returning to this question. Michael, I am attempting to use the solution you proposed: http://public.kitware.com/pipermail/paraview/2013-June/028596.html

However, when I try to adapt this to use ExodusII instead of Xdmf, I crash Paraview. I copied the code from the above link, and simply replaced 'Xdmf' with 'ExodusII'. When I try to load my xml file into paraview using the plug-in manager, that's when I cause the crash. I've successfully loaded the plugin in its un-modified form (e.g. the Xdmf form), so I must not be modifying the code correctly. I'm sure it's something exceedingly simple (I've tried replacing class=vtkExodusIIReader with class=vtkExodusReader for example), but I don't know what I'm doing wrong.

Here is my code:

<ParaViewPlugin>
<ServerManagerConfiguration>
  <ProxyGroup name="sources">
<SourceProxy name="EXODUSRrefresh" base_proxygroup="sources"
base_proxyname="ExodusIIReader" class="vtkExodusIIReader">
      <Property name="Refresh" command="Modified"
panel_widget="command_button"/>
      <Hints>
        <ReaderFactory extensions="e" file_description="ExodusII Reader
(Refresh button)" />
      </Hints>
    </SourceProxy>
  </ProxyGroup>
  </ServerManagerConfiguration>
  <ParaViewReaders>
    <Reader name="ReaderWithButton" />
  </ParaViewReaders>
</ParaViewPlugin>

Any help from anyone would be appreciated!

Alex

On 05/05/2015 01:07 AM, Schlottke, Michael wrote:
Hi Alex,

there is a thread from around 2 years ago that proposed a couple of solutions. Especially if you are using a custom reader plugin this provides for a clean and user-friendly approach:

http://public.kitware.com/pipermail/paraview/2013-June/028588.html
http://public.kitware.com/pipermail/paraview/2013-June/028596.html (this is the solution we use)

Regards,

Michael

On 05 May 2015, at 09:12 , Christian Richter <[email protected] <mailto:[email protected]>> wrote:

Hi Alex,

I'm using a little python macro to refresh the fileNames Property of all readers in the Pipeline. It is located here:
https://github.com/richti83/ParaView_Reader_for_LIGGGHTS/blob/master/python_macros/update.py

Feel free to use this as a starting point.

Best,
Christian.

Am 5/5/2015 um 12:08 AM schrieb Alex Lindsay:
Hi all,

I am doing something that most other modellers do: I am visualizing a file in my pipeline browser, but I ran a new simulation and now the file I am viewing should have changed. What is the best way to reload the file/get the new data from the file? So far my google searches have yielded this <http://www.cfd-online.com/Forums/openfoam-paraview/78129-update-data-paraview.html#post446239> as the best result, but it seems quite clumsy.

I've seen in other places people recommend clicking on "update gui", but I don't see that button available anywhere in my version of paraview.

Refresh times also doesn't seem to work.

As you can tell, I'm a new paraview user!

Thanks,
Alex


_______________________________________________
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

Search the list archives at:http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

--

<signatur.png>

Dipl.-Ing. Christian Richter
Lehrstuhl für Materialflusstechnik
Institut für Logistik und Materialflusstechnik (ILM)
Fakultät für Maschinenbau (FMB)

Otto-von-Guericke-Universität Magdeburg
Universitätsplatz 2
D-39106 Magdeburg
Gebäude 10, Raum 213

University Magdeburg “Otto-von-Guericke”
Department of Material Handling
Institute of Logistics and Material Handling Systems (ILM)
Faculty for Mechanical Engineering (FMB)

E-Mail: [email protected]
Tel.: +49 (0)391/5976687-4
Fax: +49 (0)391/5976687-5
URL: http://www.ilm.ovgu.de
Der Inhalt dieser E-Mail ist vertraulich und ausschließlich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
_______________________________________________
Powered by www.kitware.com <http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>

Search the list archives at: http://markmail.org/search/?q=ParaView <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

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects 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

Reply via email to