#Paraview plugins code#

Ideally we would implement the ESim Vis tool by a combination of ParaView3 plug-in and app-specific configuration files (rather than creating a custom application that implements the pqMainWindowCore class). The graphics view for this application are represented by 2D plots. We (Sandia) are embarking on a project which will use ParaView3, or at the least ParaView3 components to create a custom application for visualizing electrical waveform results from circuit simulators. making ParaView look and feel like a 2D waveform analysis tool but getting all the 3D goodies under the hood It should also be straightforward to plug experimental views into ParaView.Įlectrical Simulation (ESim Vis) a.k.a. Also, as we dive further into the infovis world, views will also become a common component to implement in VTK. The current ability of ParaView 2 to load in a new reader or filter is invaluable, and ParaView 3 needs to replicate this ability. It also provides a simple deployment mechanism for friendly customers. This allows the developer to easily experiment with the new unit or apply the unit to some data to perform a particular task. It is very convenient to simply wrap the unit up in a ParaView plugin and use it within that framework rather than write some temporary scaffolding code.

#Paraview plugins code#

Oftentimes developers, such as myself ( User:kmorel), want to experiment with VTK code they are working with. This is because, for a certain operation, the analyst needs to see the same view into the data every time. In the future, they may even need custom 3D widgets that sweep radially.Īlso, for ease of use, many of the 'filter' operations must set up viewing parameters like camera coordinates and display properties. The custom filters will have to present and work with these cylindrical coordinates. The big portion of the customization is that, because the Goodyear analysts work with tires, it is often convenient to parametrize the models radially. The filters themselves will be composites of existing filters, new custom C++ filters, and composites of existing and new filters. The toolbar will have custom images for each filter. These filters will be accessible through the application menu and with a toolbar. After talking with Illana Iskovitz at Goodyear, we have agreed that the best we to do this is with a ParaView plugin rather than an entire vertical application. Goodyear is planning on using ParaView to replace their legacy visualization tools. Once the InfoVis work is integrated into VTK/ParaView, there will be many opportunities for plugging in new views, and the ParaView community at large will be interested in doing just this. The comparative and uncertainty visualizations on the horizon also have potentially similar needs. The Mohr's circle work could also have benefited greatly with a simple deployment platform rather than having to build an entire application from the ground up. Furthermore, Prism is not an isolated use case. If we had the appropriate multiview and plugin capability during the initial Prism work, we may have been able to cull a significant amount of development work. There is also a linking of the simultaneous 3D geometry view and phase-space plot that allows selections to be consistent between them.Īlthough most, if not all, the Prism functionality will eventually migrate into ParaView, let us take this as an example of trying to develop and deploy a new feature involving multiple and custom views. Perhaps most important is the custom view that Prism supports that shows data in a phase-space plot. It also has some custom filters to process the SESAME data and Exodus data for presentation. Prism has a custom reader to read in data from SESAME files. Let us consider everything we need to implement the Prism functionality. Although the focused user interface will be missing, the basic functionality will be present and coupled with the rest of the functionality of ParaView.

Thus, we are trying very hard to absorb the functionality of Prism into ParaView. We all know that the Prism vertical application will not have funding for support in the next fiscal year. I encourage everyone to add their own use cases, but let us limit them to real users with real needs so that we can manage the scope of our design. This section captures the use cases for ParaView plugins. 1.5 Electrical Simulation (ESim Vis) a.k.a.