<div dir="ltr">Hello,<br><div><div><div><div><div><br></div><div>@Tim:<br></div>Thanks for the nice tips regarding to queue systems and signals on HPC clusters, I wasn't aware of that. I'll look into it on our local cluster, and we have a stop/restart method in our library, so it could work !<br></div><div><br></div><div>@Andy:<br></div><div>Indeed I was aware of the UserData member, I already used it in fact. <br>Do you have something specific in mind, when you say that there may be a simple hack for the live connection to pass information from the GUI back to Catalyst ? The main interest I see with using a plugin is to have flexibility regarding what the user can provide to the simulation. He could directly use the option format we define in the library and define those as graphical elements in the plugin.<br>I'll definitely have at look at the code behind the Catalyst GUI, I guess the answer is behind.<br></div><div>Thanks you !<br><br></div><div>Best regards,<br></div><div>Alexandre Ancel <br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 2, 2015 at 6:47 PM, Andy Bauer <span dir="ltr"><<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, it should be doable in ParaView through a plugin. The vtkCPDataDescription class has a UserData member that is a vtkFieldData pointer which can be used to pass information back and forth between the Catalyst pipelines and the adaptor. It's also Python wrapped so it's available in the Catalyst Python pipeline scripts as well. In the adaptor you would have to know how to process that data to your computational steering on the simulation side (i.e. take the Catalyst input). There may be a simple hack for the live connection to pass information from the GUI back to Catalyst in which case you might not even need a plugin. Otherwise, you should probably look at the code for the live connection (i.e. the stuff under the Catalyst GUI menu) to see how to pass other information back and forth between the GUI and Catalyst.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 2, 2015 at 12:02 PM, Tim Gallagher <span dir="ltr"><<a href="mailto:tim.gallagher@gatech.edu" target="_blank">tim.gallagher@gatech.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:times new roman,new york,times,serif;font-size:12pt;color:#000000">Hi Alexandre,<br><br>I don't know if this is possible or not with Catalyst, hopefully somebody else comes along to answer that. <br><br>But, we did this in our code using signal handling and POSIX signals (see <a href="http://man7.org/linux/man-pages/man7/signal.7.html" target="_blank">http://man7.org/linux/man-pages/man7/signal.7.html</a>). We define 3 behaviors in our code -- reload the input file and change simulation behavior accordingly; create a restart file at the next available chance and keep running; create a restart file and exit immediately. We use SIGUSR1 and SIGUSR2 for the first two options and then we use SIGTERM for the last behavior. This is helpful because most queue systems on HPC clusters will send SIGTERM 60 seconds before your wall-time is about to run out, so catching that signal and using it to write a restart file and exit means we always get our data right before our job runs out of time.<br><br>Signals can be sent locally using `kill` or can be sent through PBS using `qsig`. It works quite nicely.<br><br>Tim<br><br><hr><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><b>From: </b>"Alexandre Ancel" <<a href="mailto:alexandre.ancel@cemosis.fr" target="_blank">alexandre.ancel@cemosis.fr</a>><br><b>To: </b>"paraview" <<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>><br><b>Sent: </b>Wednesday, December 2, 2015 11:47:59 AM<br><b>Subject: </b>[Paraview] Catalyst: simulation steering during In-Situ visualization<div><div><br><br><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><span><span></span></span>Hello,<br></div><span><span><br></span></span></div><span><span>We are currently using Catalyst for In-Situ visualization in the context of our finite element library and it is working very well.<br><br></span></span></div><span><span>We would like to implement simulation steering while using Catalyst.<br></span></span></div><span><span>The idea would consist in having a ParaView plugin that we load in the ParaView client. Within the code of this plugin, we would like to send data to the simulation code to modify its behavior.<br><br></span></span></div><span><span>First question: Is it possible to do so ? <br></span></span></div><span><span>Then, How would the whole process be run ?<br></span></span></div><span><span>The ideal scenario would be the following:<br></span></span></div><span><span>- Launch ParaView & connect to the distant pverver</span></span><span><span> & enable Catalyst<br></span></span></div></div><span><span>- Load the plugin in ParaView<br></span></span></div><span><span>- Launch the simulation<br></span></span></div><span><span>- Receive data until timestep N then stop the simulation<br></span></span></div><span><span>- Send data to the simulation through the loaded plugin<br clear="all"></span></span><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>- Continue with the simulation<br></div><div>Would it be possible to do so ? If yes, could you give me keypoints about how to do this ?<br><br></div><div>Thanks in advance for your answers,<br><br></div><div>Best regards,<br></div><div>Alexandre Ancel<br></div><div><br>-- <br><div><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><div dir="ltr"><font face="courier new, monospace">Alexandre Ancel <br>Docteur, Ingénieur de recherche / Phd, Research Engineer<br></font><div>
<font face="courier new, monospace"><a href="http://www.cemosis.fr" target="_blank">Ce<font color="#888888">mosis</font></a> - <a href="mailto:alexandre.ancel@cemosis.fr" target="_blank">alexandre.ancel@cemosis.fr</a></font></div><div><font face="courier new, monospace">Tel: +33 (0)3 68 8</font><span><font color="#888888"><font face="courier new, monospace"><b>5 02 06</b></font></font></span></div>
<div><font face="courier new, monospace">IRMA - 7, rue René Descartes</font></div><div><font face="courier new, monospace">67 000 Strasbourg, France<br></font></div></div></font></span></div></div></div></div>
</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br></div></div>_______________________________________________<br>Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br><br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br><br>Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br><br>Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" target="_blank">http://markmail.org/search/?q=ParaView</a><br><br>Follow this link to subscribe/unsubscribe:<br><a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br></div><br></div></div><br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><div dir="ltr"><font face="courier new, monospace">Alexandre Ancel <br>Docteur, Ingénieur de recherche / Phd, Research Engineer<br></font><div>
<font face="courier new, monospace"><a href="http://www.cemosis.fr" target="_blank">Ce<font color="#888888">mosis</font></a> - <a href="mailto:alexandre.ancel@cemosis.fr" target="_blank">alexandre.ancel@cemosis.fr</a></font></div><div><font face="courier new, monospace">Tel: +33 (0)3 68 8</font><span><font color="#888888"><font face="courier new, monospace"><b>5 02 06</b></font></font></span></div>
<div><font face="courier new, monospace">IRMA - 7, rue René Descartes</font></div><div><font face="courier new, monospace">67 000 Strasbourg, France<br></font></div></div></font></span></div></div></div></div>
</div>