[Paraview-developers] PointSprite plugin

[Biddiscombe, John A.]

It'll be ready for a gerrit branch in a week or two I guess and should be stable enough for release to the general public just before Christmas - that's the internship deadline - so it's also our final aim point.

To answer the question about the 1D transfer function - I think most of this can go away. The colours can be done using scalarsToColours and the radius can be done with the new Gaussian piecewise function, the other stuff was put in by Stephane to interface between the various classes and the gui. It was a bit overengineered and should be simplified greatly. I understand the painter chain much better now and the twoscalars to colours stuff for opacity+rgb can also be moved into core. I will make an effort between now and Christmas to clean all this up and get in in. 
I have another plugin for our neuron rendering which reuses much of the same set of classes for the per vertex opacity stuff, so it is something that's on my todo list anyway. 

note to self : Might need to do some more work on the coloropacityeditor panel to handle the point sprite controls.

JB

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 21 October 2013 18:31
To: Biddiscombe, John A.
Cc: David E DeMarle; ParaView Developers; Waldin Nicholas
Subject: Re: [Paraview-developers] PointSprite plugin

Thanks for the update, John. Do you have an estimate for when you expect these changes to go in?

Utkarsh


On Mon, Oct 21, 2013 at 11:31 AM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> I'm sorry, I missed this thread.
>
>
>
> Don't touch it yet.
>
>
>
> We have an intern here at CSCS (Nicholas), who is upgrading the 
> transfer function editing in paraview to support the visit widgets as 
> part of the core. We are using them to handle gradient opacity editing 
> in volume rendering, but by moving the widgets into qt/components we 
> are able to use them in paraview main rather than a plugin. Moving the 
> point sprites into core will now be easy. We have made a new 
> vtkAbstractPiecewise function class and an extra vtkGaussianPiecewise 
> function which allows the user to switch between the (extremely poor) 
> transfer function in paraview now and the new (much spiffier) gaussian 
> one. This stuff is almost ready for a branch on gerrit, but there are 
> some bugs in the parallel histogram display for the gradient we need 
> to address. The gradient stuff is working for raycast (hoorah, even on 
> mesa), and texture3D, but not on the GPU volume renderer (does it support gradient?).
>
> Once this is ready, we will move to the 2D transfer functions which 
> are not present yet, but I had working some years ago for the texture 
> mapper - and I need/want for the raytrace mapper.
>
>
>
> It is our plan to push this out as a core paraview addition and not as 
> plugin stuff. We'll do a video to demonstrate the features and a 
> gerrit branch.
>
>
>
> I was under the impression that Marcus at kitware had done a whole 
> load of new spritey stuff for chemistry viz, so there's no need to 
> drag out the old point sprite stuff maybe? anyway, integrating the 
> point sprite wil be much easier soon, so wait a bit.
>
>
>
> JB
>
>
>
>
>
>
>
> From: paraview-developers-bounces at paraview.org
> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David E 
> DeMarle
> Sent: 21 October 2013 17:15
> To: Utkarsh Ayachit
> Cc: ParaView Developers
> Subject: Re: [Paraview-developers] PointSprite plugin
>
>
>
> I'ld like to add:
>
> + Anybody object to promoting the core rendering functionality to VTK?
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Mon, Oct 21, 2013 at 11:09 AM, Utkarsh Ayachit 
> <utkarsh.ayachit at kitware.com> wrote:
>
> John (and other users/developers of the PointSprite plugin),
>
> I was trying to address up some of the issues with the point sprites 
> and I see a potential for cleanup and hence I wanted to get your
> thoughts:
>
> + What are vtk1DTransferFunction and its subclasses needed? Can't we
> simply use vtkPiecewiseFunction?
>
> + Can we replace the VisIt transfer function editor UI used for
> editing the opacity and radius transfer functions to be similar to 
> what the color map editor panel uses for opacity transfer function? If 
> we do this, will there be any essential functionality that will be 
> missed?
>
> Utkarsh
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>