<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I would say proceed with caution. Using antialiasing only on client side used to be our solution, but it turns out antialiasing screws up other stuff, too, and
we eventually threw up our hands and got rid of it. I definitely remember picking as an issue that cropped up. I think there were others, but I don’t remember them all. I think transparency (depth peeling) was one.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Ken<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> David E DeMarle [mailto:dave.demarle@kitware.com]
<br>
<b>Sent:</b> Tuesday, July 12, 2016 2:32 PM<br>
<b>To:</b> Utkarsh Ayachit <utkarsh.ayachit@kitware.com><br>
<b>Cc:</b> Scott, W Alan <wascott@sandia.gov>; Moreland, Kenneth <kmorel@sandia.gov>; paraview-developers@paraview.org<br>
<b>Subject:</b> Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">As long as it doesn't affect selection, sounds pretty snazzy.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
21 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: 518-881-4909<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jul 12, 2016 at 4:27 PM, Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">While the technical arguments are indeed sound, we tend to get asked<br>
about this quite periodically. What do folks think about using AA by<br>
default for builtin or client-side render and not when compositing?<br>
This way, 2D charts, for example, will always have AA turned on --<br>
just a nice little perk.<br>
<br>
Utkarsh<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
On Tue, Jul 5, 2016 at 10:08 PM, Scott, W Alan <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>> wrote:<br>
> OK, much better pushback. I would say AA (either the hack mentioned below<br>
> or real) probably isn’t worth a non-trivial software change at this point.<br>
> We should keep it on the table for future work.<br>
><br>
><br>
><br>
> Alan<br>
><br>
><br>
><br>
> From: Moreland, Kenneth<br>
> Sent: Friday, July 01, 2016 7:58 PM<br>
><br>
><br>
> To: Scott, W Alan <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>>; David E DeMarle<br>
> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>><br>
> Cc: <a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a><br>
> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA<br>
><br>
><br>
><br>
> OK, let me rephrase my pushback. There are several technical hurtles to<br>
> implement this feature. We know how to achive this effect, but it requires a<br>
> non-trivial change to the rendering system that will take significant<br>
> development cycles, add complexity to the rendering system, and potentially<br>
> destabilize several features relying on the rendering. Plus, this is all<br>
> happening in the middle of a push for other (more important) rendering<br>
> features (OpenGL2, OpenSWR, Ospray, IndeX).<br>
><br>
><br>
><br>
> We turned off antialiasing in ParaView years ago because it caused way more<br>
> problems than it was worth. The question is, do you really think it is<br>
> important enough now to have a software push for it?<br>
><br>
><br>
><br>
> -Ken<br>
><br>
><br>
><br>
> From: Walter Scott <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>><br>
> Date: Friday, July 1, 2016 at 12:12 PM<br>
> To: Kenneth Moreland <<a href="mailto:kmorel@sandia.gov">kmorel@sandia.gov</a>>, David E DeMarle<br>
> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>><br>
> Cc: "<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>" <<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>><br>
> Subject: RE: [Paraview-developers] [EXTERNAL] Re: Remind me - AA<br>
><br>
><br>
><br>
> Makes sense. But…<br>
><br>
><br>
><br>
> 1) Make it 2X – i.e., 4 times the pixels, if the user asks for better<br>
> images when lines are visible. Default off. You want better images, it<br>
> will be slower (when lines are visible).<br>
><br>
> 2) We do it (when rendering off screen) all the time when making movies<br>
> for the power wall. I don’t see this as an issue…<br>
><br>
> 3) Have the line widths automatically written 2X requested width.<br>
> Thus, when it shrinks by 2, you get normal, poor man’s AA lines.<br>
><br>
><br>
><br>
> Alan<br>
><br>
><br>
><br>
> From: Moreland, Kenneth<br>
> Sent: Friday, July 01, 2016 9:20 AM<br>
> To: Scott, W Alan <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>>; David E DeMarle<br>
> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>><br>
> Cc: <a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a><br>
> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA<br>
><br>
><br>
><br>
> Reason 1: Increasing the resolution 2X increases the compositing overhead by<br>
> up to 4. Increasing the resolution 4X increases the compositing time by up<br>
> to 16. It can be a noticeable difference when rendering interactively.<br>
><br>
><br>
><br>
> Reason 2: There can be technical difficulties in rendering images that<br>
> large. You are likely to have a rendering context of the original<br>
> resolution. To render such large images with images/movies, it renders image<br>
> tiles and stitches them together. This adds further overhead and<br>
> complication in rendering.<br>
><br>
><br>
><br>
> Reason 3: Line width is measured in pixels. Changing the resolution of the<br>
> image in this way will change the perceived line width.<br>
><br>
><br>
><br>
> -Ken<br>
><br>
><br>
><br>
> From: Paraview-developers <<a href="mailto:paraview-developers-bounces@paraview.org">paraview-developers-bounces@paraview.org</a>> on<br>
> behalf of Walter Scott <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>><br>
> Date: Thursday, June 30, 2016 at 7:48 PM<br>
> To: David E DeMarle <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>><br>
> Cc: "<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>" <<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>><br>
> Subject: Re: [Paraview-developers] [EXTERNAL] Re: Remind me - AA<br>
><br>
><br>
><br>
> OK, why can’t we do that? Have a mode that internally runs 2X or 4X<br>
> resolution, does the compositing, and then shrinks back to what the user<br>
> wants? Only turn it on when 3d lines are in the image?<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> From: David E DeMarle [mailto:<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>]<br>
> Sent: Thursday, June 30, 2016 7:46 PM<br>
> To: Scott, W Alan <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>><br>
> Cc: <a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a><br>
> Subject: [EXTERNAL] Re: [Paraview-developers] Remind me - AA<br>
><br>
><br>
><br>
><br>
> Antialiasing confuses depth compositing.<br>
><br>
> Better to save out images/movies at 4x resolution and resample outside of<br>
> paraview.<br>
><br>
><br>
> On Thursday, June 30, 2016, Scott, W Alan <<a href="mailto:wascott@sandia.gov">wascott@sandia.gov</a>> wrote:<br>
><br>
> Why can’t we turn anti alias lines on? I am doing a feature edges, and it<br>
> looks horrible.<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
> Alan<br>
><br>
><br>
><br>
> --------------------------------------------------------<br>
><br>
> W. Alan Scott<br>
><br>
> ParaView Support Manager<br>
><br>
><br>
><br>
> SAIC<br>
><br>
> Sandia National Laboratories, MS 0822<br>
><br>
> Org 9326 - Building 880 A1-K<br>
><br>
> <a href="tel:%28505%29%20284-0932">(505) 284-0932</a> FAX <a href="tel:%28505%29%20284-5619">
(505) 284-5619</a><br>
><br>
> ---------------------------------------------------------<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> David E DeMarle<br>
> Kitware, Inc.<br>
> R&D Engineer<br>
> 21 Corporate Drive<br>
> Clifton Park, NY 12065-8662<br>
> Phone: <a href="tel:518-881-4909">518-881-4909</a><br>
><br>
><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Search the list archives at:<br>
> <a href="http://markmail.org/search/?q=Paraview-developers" target="_blank">http://markmail.org/search/?q=Paraview-developers</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">
http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>