<br><font size=2 face="sans-serif">Hi Utkarsh,</font>
<br>
<br><font size=2 face="sans-serif">If we want to push the demand-driven
logic to the end, choosing the arrays to load could be implicit on the
readers : they will depend on the arrays needed down the pipeline.</font>
<br><font size=2 face="sans-serif">The obvious drawback of this approach
is that having several arrays availbale for the representation to color
by is very handy, instead of re-executing the whole pipeline each time
you change the array to color by, but this demand-driven logic could help
when memory is limited.</font>
<br>
<br><font size=2 face="sans-serif">Best,</font>
<br><font size=2 face="sans-serif">Stephane<br>
<br>
<br>
</font>
<table>
<tr valign=top>
<td rowspan=2><font size=2 face="sans-serif"> </font><img src=cid:_1_0AEC50800AEC4C980044542AC12578A9><font size=2 face="sans-serif">
</font>
<td><font size=1 face="sans-serif"> </font>
<tr valign=top>
<td><font size=1 color=#ff8100 face="Arial"><b>Stephane PLOIX</b></font><font size=1 color=#ff8100 face="Arial"><b><br>
Pilote Opérationnel - Visualisation scientifique</b></font><font size=1 color=#0062e1 face="Arial"><br>
EDF - R&D<br>
SINETICS<br>
1, Av du Général de Gaulle<br>
92140 Clamart</font><font size=1 color=#0062e1 face="sans-serif"><br>
</font>
<br><font size=1 color=#0062e1 face="Arial"><b>stephane.ploix@edf.fr</b></font>
<br><font size=1 color=#0062e1 face="Arial">Tél. : +33 (0) 1 47 65 51
10</font>
<tr>
<td valign=top><font size=2 face="sans-serif"> </font><img src=cid:_1_0A8C18600A8C14780044542AC12578A9><font size=2 face="sans-serif">
</font>
<td><font size=1 color=#0062e1 face="Arial">Un geste simple pour l'environnement,
n'imprimez ce message que si vous en avez l'utilité.</font></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>utkarsh.ayachit@kitware.com</b>
</font>
<br><font size=1 face="sans-serif">Envoyé par : paraview-bounces@paraview.org</font>
<p><font size=1 face="sans-serif">07/06/2011 19:44</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">A</font></div>
<td><font size=1 face="sans-serif">samuelkey@bresnan.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">paraview@paraview.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Objet</font></div>
<td><font size=1 face="sans-serif">Re: [Paraview] Concept: A world without
the Apply button</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Sam,<br>
<br>
Please note that this proposal does not preclude the user from<br>
choosing which array to load from the reader's properties panel. That<br>
indeed will be supported. This proposal in fact allows you go back the<br>
reader change it's array selection, and then go the properties panel<br>
for a contour filter connected downstream (for example) and choose the<br>
array to contour by as the newly selected array without having to<br>
execute any of the reader/intermediate filters until you have setup<br>
the full pipeline. After which, you hit "Execute". That's when
the<br>
reader will actually read the data. Currently, before you can choose<br>
the array to contour with, you have to hit "Apply" so that the
reader<br>
will produce the newly selected array. Then alone will it be reflected<br>
on the contour panel.<br>
<br>
Also, changing parameters on filters will have no immediate effect per<br>
say. The new proposal is not simply "auto-apply". You have to
hit<br>
"Execute" before the filters will be executed, so you can tweak<br>
parameters to your hearts contents before triggering any execution<br>
(similar to the Apply mechanism).<br>
<br>
Utkarsh<br>
<br>
On Tue, Jun 7, 2011 at 1:31 PM, Samuel Key <samuelkey@bresnan.net>
wrote:<br>
> All--<br>
><br>
> Technical reasons aside, my own simulation efforts (software that
relies on<br>
> ParaView for post-processing) span a great variety of solid and structural<br>
> mechanics applications. The software is not a single-formulation,<br>
> single-solution, one-off problem solver.<br>
><br>
> Put briefly, I find the "Apply" button exceptionally useful.<br>
><br>
> The EnSight-formatted results files produced contain a surfeit (excess)
of<br>
> simulation results for any one application. I use the "Apply"
button on<br>
> loading results files for several purposes:<br>
><br>
> 1) Load only results that are most useful to the current problem or<br>
> application.<br>
><br>
> 2) Limit the results I examine to those relevant to the phase st hand:<br>
> i) Phase 1. Are the results OK (BC's OK? Energy Balance
OK? Loading OK?)<br>
> ii) Phase 2. Which result describes the response most
effectively?<br>
> iii) Phase 3. Presentation animations and figures for communicating.<br>
><br>
> 3) Frequent tuning of various filters to refine the display of the
results<br>
> being studied.<br>
><br>
> 4) Last but not least, limit the results being examined at any one
session<br>
> to avoid the MS O/S crashing PV because of the MS O/S limits on resources<br>
> usable.<br>
><br>
> Thanks for the opportunity to express my support for ParaView and
its<br>
> exceptional versatility and effectiveness as a post-processing tool.<br>
><br>
> Sam Key<br>
><br>
> On 6/7/2011 8:56 AM, Moreland, Kenneth wrote:<br>
>><br>
>> One thing that strikes me about this proposal, is that it relies
a lot on<br>
>> VTK readers/filters providing the necessary meta data, particularly
about<br>
>> fields. For example, the elevation filter would have to
report in its<br>
>> meta data that it will be adding a scalar field named Elevation.
That<br>
>> sounds easy enough to implement, but would have to be independently
added<br>
>> for all readers/filters. This would be especially problematic
for<br>
>> user-provided plugins.<br>
>><br>
>> Is there a way to mitigate the issues with the meta data mismatching
what<br>
>> is actually generated? Perhaps there could be a check to
make sure that<br>
>> the data generated matches the meta data previously reported and
issue a<br>
>> warning if there are any mismatches. This would not solve
the problem per<br>
>> se, but would quickly alert developers to problems and make it
easier to<br>
>> debug.<br>
>><br>
>> -Ken<br>
>><br>
>> **** Kenneth Moreland<br>
>> *** Sandia National Laboratories<br>
>> ***********<br>
>> *** *** *** email: kmorel@sandia.gov<br>
>> ** *** ** phone: (505) 844-8919<br>
>> *** web: http://www.cs.unm.edu/~kmorel<br>
>><br>
>><br>
>><br>
>><br>
>> On 6/1/11 1:30 PM, "Utkarsh Ayachit"<utkarsh.ayachit@kitware.com>
wrote:<br>
>><br>
>>> Folks,<br>
>>><br>
>>> I have been investigating the ability to create pipelines
in ParaView<br>
>>> without having to hit Apply at every single stage in the pipeline.<br>
>>> This would make it much easier to deal with really large data
in a<br>
>>> usage scenario where the scientist is fairly familiar with
the<br>
>>> visualization pipeline he's interested in setting up.<br>
>>><br>
>>> Following the recent changes to the ParaView ServerManager,
the<br>
>>> ServerManager level requirement that filters need to be updated
before<br>
>>> connecting has disappeared. However, we still need to "Apply"
to get<br>
>>> updated information about arrays etc.<br>
>>><br>
>>> After a couple on discussions with Berk and Dave, I've consolidated<br>
>>> the thoughts on a Wiki page. If any one has any thoughts to
share, it<br>
>>> would be great.<br>
>>><br>
>>><br>
>>> http://www.paraview.org/ParaView3/index.php/No-Apply_Mechanism_for_Creatin<br>
>>> g_Pipelines<br>
>>><br>
>>> Note that this is merely a concept. We have no plans of implementing<br>
>>> it in near future (3.12/4.0).<br>
>>><br>
>>> Utkarsh<br>
>>> _______________________________________________<br>
>>> Powered by www.kitware.com<br>
>>><br>
>>> Visit other Kitware open-source projects at<br>
>>> http://www.kitware.com/opensource/opensource.html<br>
>>><br>
>>> Please keep messages on-topic and check the ParaView Wiki
at:<br>
>>> http://paraview.org/Wiki/ParaView<br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> http://www.paraview.org/mailman/listinfo/paraview<br>
>>><br>
>><br>
>> _______________________________________________<br>
>> Powered by www.kitware.com<br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> http://www.kitware.com/opensource/opensource.html<br>
>><br>
>> Please keep messages on-topic and check the ParaView Wiki at:<br>
>> http://paraview.org/Wiki/ParaView<br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> http://www.paraview.org/mailman/listinfo/paraview<br>
>><br>
><br>
_______________________________________________<br>
Powered by www.kitware.com<br>
<br>
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<br>
<br>
Follow this link to subscribe/unsubscribe:<br>
http://www.paraview.org/mailman/listinfo/paraview<br>
</font></tt>
<br><font face="monospace"><br>
<br>
<br>
Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.<br>
<br>
Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.<br>
<br>
Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.<br>
____________________________________________________<br>
<br>
This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.<br>
<br>
If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.<br>
<br>
E-mail communication cannot be guaranteed to be timely secure, error or virus-free.</font>