The new VisItBridge secondary goal was to provide an integrated build with ParaView. This allows developers to easily add more VisItReaders or even to add VisItReaders into plugins. The wrapping of each reader is now done automatically be auto generating the VTK class at configure time. The reason for this lower level interfacing was to reduce the number of VisIt dependencies, eliminate the need for runtime loading of readers, and have faster access to the underlying VTK data. ![]() The VisItBridge now interfaces with the avtFileFormat to create a VTK pipeline object that emulates the VisIt database loading process. The VisIt developers have provided a consistent interface both for database plugin via the avtFileFormat interface. VisIt IO components are called database plugins. Hence porting functionality from one to the other is fairly straight forward and potentially very beneficial as both applications have large, publicly available, thoroughly tested code bases. However, in general there are more similarities than differences. There are a number of subtle differences in the internal workings of the two applications. Like ParaView, VisIt is a scientific data visualization application based on VTK and Qt. The motivation for the bridge is to allow ParaView to make use of VisIt's IO components, and to explore the re-usable capabilities of VisIt and its underlying pipeline library, avt. This article describes the Visit Database Bridge ParaView plugin.
0 Comments
Leave a Reply. |