<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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"'>Hello Lis,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I suppose you are right on the step-size parameter thing since tweaking NVIDIA’s multi-sampling/anti-aliasing option on both Windows and Linux systems does not seem to bring any change to the quality. On Linux, performing Extract Subset@ROI sufficiently significant will result in a superior image quality whereas on Windows, ROI has no effect over quality. Of course, committing ROI implicates data loss, thus not a viable solution either, especially when Windows has no such predicament. Furthermore, it still does not explain why the different behavior/quality coming from the same ParaView version (or different versions for that matter). It does however, affect the Color Map Editor’s color palette – noisy color spectrum/gradient with the AA on NVIDIA control panel set to naught. If this step-size property is the answer, where can I find it and how much work is required? For the record, the problem is concerning still-image quality, not the one during interaction (which is expected to be in low-resolution).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Den</span><b><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.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'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lisa Avila [mailto:lisa.avila@kitware.com] <br><b>Sent:</b> 06 February 2014 10:01 PM<br><b>To:</b> Den Fairol<br><b>Cc:</b> paraview@paraview.org<br><b>Subject:</b> Re: [Paraview] Revisiting aliasing effect<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hello Den,<o:p></o:p></p></div><p class=MsoNormal>This actually has nothing to do with NVIDIA antialiasing and probably everything to do with the step size used on the mapper. Most likely the issue is related to the automatic trade-off of quality to ensure performance (depending on the mapper being used it will increase step size, decrease the size of the generated image, and/or decrease the volume size in order to meet the desired update rate). So either you are not seeing the "final" image (which should fill in with better quality than the interactive image) or for some reason the image is taking so long that the mapper thinks that's the best it can do within its allocated time slice. Do you see a change in image quality when you stop rotating? Are you having performance issue while rotating?<br><br>Lisa<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Jan 30, 2014 at 2:45 AM, Den Fairol <<a href="mailto:den.fairol@infovalley.net.my" target="_blank">den.fairol@infovalley.net.my</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi, <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I’m a little confused regarding the inconsistent behavior of ParaView (v4.x), specifically the quality of its volume rendering representation. The Smart/GPU renderer for Windows version is slightly inferior to its RayCast renderer counterpart whereas for the Unix/Linux version, it is kind of like something you’d expect from a ‘B’ horror movie (see attachment for Smart/GPU-based rendered images). It is mentioned here: <a href="http://www.paraview.org/pipermail/paraview/2011-June/022062.html" target="_blank">http://www.paraview.org/pipermail/paraview/2011-June/022062.html</a> & <a href="http://www.paraview.org/pipermail/paraview/2010-June/017961.html" target="_blank">http://www.paraview.org/pipermail/paraview/2010-June/017961.html</a> that anti-aliasing (AA) is disabled by default. Then how could the Windows (Windows 7, NVIDIA Quadro 600 + driver v320.xx) version persist to appear so smooth despite setting NVIDIA’s Control Panel AA handling to ‘Off’? Conversely, changing the same option in Linux (Ubuntu 12.04, NVIDIA Quadro K5000 + driver v304.xx/v319.xx/v331.xx) to ‘Override-application’ adds nothing to the quality. As of now, RayCasting is may not be a viable solution since it induces substantial latency overhead.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Den<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<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>Follow this link to subscribe/unsubscribe:<br><a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>