[Paraview] [EXTERNAL] Is anyone using the Extra Headlight in ParaView?

David E DeMarle dave.demarle at kitware.com
Thu Aug 17 13:37:23 EDT 2017


Yes please do provide a mockup when you get a chance. I think I see your
idea but a picture is worth a million lines of code.



David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Aug 17, 2017 at 1:34 PM, Timothy Dwight Dunn <
timothy.dunn at colorado.edu> wrote:

> Actually I was just talking about this in a Paraview tutorial I gave this
> morning at a conference. I would prefer to kill the hard coded light
> allowing the ability to add in general lights that the user can design and
> setup. In addition to save a conf out for the setup to be used as a
> default. I normally set things up in Paraview export what I need pop them
> in a CG app so that I can light them with so much more control but this is
> often difficult at best to impossible as the norm due to complexity of the
> scene. If we could get more and better light control, especially with
> Osprey then I'd be a very happy camper.
>
> Just to make really difficult make sure the lights interact with
> objects/layers as desired by the user, including volumeterics. This is a
> common thing to do in CG apps. Light objects A,B,C with light rig1, object
> D,E with light rig2 and object F with light rig3 .... The easiest way to do
> this is to have a panel for each light, or for paraview the gui controls
> with a check box list for each available layer which can
> activate/deactivate each light per layer. OK this makes sense in my head
> but I don't think I'm explaining it well do to conference exhaustion. If
> desired I can do a mock up gui layout image of what I'm trying to describe.
>
>
> Tim Dunn
> Scientific\Data Visualization & Visual Analytics for;
> CIRES - Earth Lab-Analytics Hub
> CU Research Computing (CURC)
> Center for Research Data and Digital Scholarship (CRDDS)
> tdunn at colorado.edu
>
> On Thu, Aug 17, 2017 at 11:16 AM, Scott, W Alan <wascott at sandia.gov>
> wrote:
>
>> No objection here.  Only thought I have is that the lights may be setup
>> by default slightly differently for 2d and 3d.  We may want a “headlight”
>> for 2d.
>>
>>
>>
>>
>>
>> Alan
>>
>>
>>
>> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *David
>> E DeMarle
>> *Sent:* Thursday, August 17, 2017 7:35 AM
>> *To:* paraview at paraview.org
>> *Subject:* [EXTERNAL] [Paraview] Is anyone using the Extra Headlight in
>> ParaView?
>>
>>
>>
>> By default, Paraview illuminates the scene with a vtkLightKit
>> <http://www.vtk.org/doc/release/5.0/html/a01682.html>. You can however
>> add an extra headlight. I am about to add a more general capability which
>> lets you add any number and any kind of light, including the headlight.
>> When I do that, the semi-hardcoded extra headlight becomes redundant. I
>> would like to remove it to streamline both the code and the UI.
>>
>> Are there any objections to me doing that?
>>
>> David E DeMarle
>> Kitware, Inc.
>> Principal Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909 <(518)%20881-4909>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170817/ed2872de/attachment.html>


More information about the ParaView mailing list