[Paraview-developers] [EXTERNAL] Re: FAA

Cory Quammen cory.quammen at kitware.com
Thu Jan 5 16:03:56 EST 2017


Alan,

Apologies, I should have said "next ParaView release" instead of
5.2.1! There are no *firm* plans as of now for a 5.2.1 release. Let's
fix [1] first and then we'll determine whether a patch release will be
made before 5.3.

Sorry for the confusion!

Cory

[1] https://gitlab.kitware.com/paraview/paraview/issues/17091


On Thu, Jan 5, 2017 at 3:52 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Thanks Cory - your scalar bar was on my list, but we ran out of time.  Good to hear, let me know when I can start testing.
>
> OK, to be clear.  Our fix will be rolled at in a 5.2.1 tag, and we will put new Linux binaries out on the website?  Or, replace all downloads?
>
> alan
>
>> -----Original Message-----
>> From: Cory Quammen [mailto:cory.quammen at kitware.com]
>> Sent: Thursday, January 5, 2017 1:26 PM
>> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Cc: Scott, W Alan <wascott at sandia.gov>; paraview-
>> developers at paraview.org
>> Subject: [EXTERNAL] Re: [Paraview-developers] FAA
>>
>> The new scalar bar is coming along. Some text rendering changes
>> necessitated some baseline changes that I am working through now. Then I'll
>> add a test with Alan's list of ranges to test that he sent me a while and work
>> through that. Then we should be ready. I wouldn't merge until after a 5.2.1 is
>> tagged, though.
>>
>> Cory
>>
>> On Tue, Jan 3, 2017 at 11:01 PM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>> > Last minute I decided to punt on making FXAA the default as it showed
>> > some issues with SurfaceLIC. Also, the way we were thinking, to turn
>> > it on without affecting testing was going to be unnecessarily
>> > complicated. Since we were changing all baselines when the new scalar
>> > bar changes land (ETA, Cory?), it would have been a better time to
>> > change the default.
>> >
>> > Utkarsh
>> >
>> > On Tue, Jan 3, 2017 at 9:47 PM, Scott, W Alan <wascott at sandia.gov>
>> wrote:
>> >> Utkarsh/ Cory,
>> >>
>> >> Why wasn’t Anti-Aliasing turned on by default on PV 5.2.0?  Wasn’t
>> >> that the plan?  I assume we need to make sure it gets turned on by
>> default...
>> >>
>> >>
>> >>
>> >> Thanks,
>> >>
>> >>
>> >>
>> >> Alan
>> >>
>> >>
>> >>
>> >> --------------------------------------------------------
>> >>
>> >> W. Alan Scott
>> >>
>> >> ParaView Support Manager
>> >>
>> >>
>> >>
>> >> SAIC
>> >>
>> >> Sandia National Laboratories, MS 0822
>> >>
>> >> Org 9326 - Building 880 A1-K
>> >>
>> >> (505) 284-0932   FAX (505) 284-5619
>> >>
>> >> ---------------------------------------------------------
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> Powered by www.kitware.com
>> >>
>> >> Visit other Kitware open-source projects at
>> >> http://www.kitware.com/opensource/opensource.html
>> >>
>> >> Search the list archives at:
>> >> http://markmail.org/search/?q=Paraview-developers
>> >>
>> >> Follow this link to subscribe/unsubscribe:
>> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Search the list archives at:
>> > http://markmail.org/search/?q=Paraview-developers
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.


More information about the Paraview-developers mailing list