K-3D Forums

Seven Degrees of Freedom

1. 

   LevelFour
   Member

   Greetings,

   We are considering to dedicate a significant development initiative to create an extensive data visualization plug-in using K3D as the platform (also considering Blender). The objective is to establish a logic chain where data sets and specialized methods (graph layout, cartographic projections, charting patterns, etc.) are applied to render complex information visualization scenes. Our goal is to create a suite of python methods which can be chained together as a procedural model using a node-link approach.

   Based on our evaluation it is not clear to what extent the K3D interface is extensible for this purpose. Although it is very clear the Visualization Pipeline architecture is exactly suited to the goal. We'd be grateful if someone can explain the suitability of implementing a node-link approach which can establish a basic scene (generated from data) with property injection via node links to set the position, size, shape, material of a given object. The requirement would be to enhance the current connection interface provided in the node property editor, to be a more visual node-link diagram similar to the Blender node-link editor.

   The concept use case would be: user selects composition nodes such as CSV import, assign variables, set primitives, and links operator nodes to apply visual properties based on the variables, e.g. spheres are positioned, sized, and colored based on a data value.

   We'd very much appreciate any brainstorming on the approach as if it appears feasible, we would very much look forward to contributing our open source project back to the K3D community.

   Cheers,

   JB

   Posted 4 months ago #
2. 

   Timothy Shead
   Moderator

   JB:

   We're always interested to collaborate on new functionality for K-3D! In this case, I'm not sure that I understand what you're trying to do, it would be helpful to hear more about your problem domain. In particular, it isn't clear to me whether you're wanting to visualize the pipeline as a node-link diagram, use the pipeline to create a node-link diagram, use a graph to create a pipeline, or some combination of all three ;)

   Cheers,
   Tim

   Posted 4 months ago #
3. 

   LevelFour
   Member

   Hi Tim,

   Thanks for the query. Let me try to clarify...

   The idea is that a node-link approach is used to create the visualization scene, hence using a node-link approach as the primary means of creating data driven objects and assigning properties to those objects. A node-based visualization development environment similar to source binder:

   http://sourcebinder.org/

   We create a suite of specialized nodes ranging from CSV import, KML import, geographic projections, proportional size functions, etc. These nodes are added to a node-link edit environment (as determined by the analyst) and connected for assigning properties, etc. We have hundreds of specialized visualization methods that we would port as nodes/operators.

   We understand that this logic can already be done in the current K3D implementation, but since the node-property logic is likely to be very complex, we feel this implementation is most ideal for ease of use since the intended end user will be an analyst.

   Make sense?

   JB

   Posted 4 months ago #
4. 

   Timothy Shead
   Moderator

   JB:

   Sounds reasonable, I think that all of this is a good fit for K-3D - we have the flexibility in the data structures, pipeline, and rendering to accomodate your data, sources, and modifiers today. What's missing is the visual, drag-and-drop pipeline interface. Of course, having a better way to visualize / interact-with the pipeline is not a new idea for us. We've had a couple of false starts at a panel to display the pipeline. If you haven't already, you might take a look at the "Pipeline Panel", which provides a limited, non-interactive visualization for the pipeline.

   So it sounds to me as if the direct pipeline manipulation is all that's really lacking, or am I missing something else?

   Cheers,
   Tim

   Posted 4 months ago #
5. 

   LevelFour
   Member

   Tim,

   You got it. Well, sounds like this is a fit... We're ready to rally up the team to get started - we'll basically be focusing on two areas: the direct pipeline manipulation interface and the specialized vis plug-ins. We're pretty clear on how to handle the vis side, but we could use some guidance for the best approach for a node-link/pipeline panel. We'd be grateful if you could offer some pointers for best approach, etc. I hope our work will be useful to the project...

   Best,

   JB

   Posted 4 months ago #

RSS feed for this topic

Reply

You must log in to post.