refasystems.blogg.se

This software should be usable both within and outside of ParaView. Modular: The software will be modular so that various visualization suites can be implemented separately but also work together. Safe: The software must preserve data integrity and precision.ĭynamic: The software must enable a dynamic link between external processing software and visualization libraries. PVGeo library to work well with other Python libraries by following theĮxtendable: This software will harness the established and robust visualization platforms ParaView and VTK, extend their functionality, and remain open-source for contributions and integration into other Python powered geoscientific processing suites. ObsPy, EarthPy, pyFLOWGO, GeoNotebook, and more.

Python is an accessible language,Įasy to learn, and popular among geoscientists using packages like: SimPEG, The VTKPythonAlgorithmBase class in Python. Rapid development of readers, sources, filters, and writers: instantiations of PVGeo module takes advantage of functionality by Kitware that facilitates the Programming languages like C++, learning new libraries to create interactive GUIĬomponents, and building the plugins into the ParaView source code. Programming endeavor, including creating CMakeLists, developing in lower level Unfortunately, theĭevelopment of plugins for the ParaView software platform may imply an ambitious In that PVGeo contains many base classes for developers to inheritįunctionality to aid in the development of new features. This development framework also focuses heavily on the open source paradigm This would allow for users of PVGeo to be able to use all of the functionalityĪs plugins in ParaView with interactive user menus or outside of ParaView beĪble to integrate with there existing data processing suites using Python and ParaView or outside in other Python environments with the VTK Python library. In developing the PVGeo repository, we decided to follow a framework ofĭevelopment that generates various sets of tools that can be used within If you are looking to build a plugin for the binary release, you may want to look at this Kitware blog.Project Structure  The Plugin Framework  If you or your team need more complex images, do not hesitate to contact Kitware for help. DVTK_MODULE_ENABLE_VTK_GUISupportQtQuick=NO The VTK image is built with a reasonable configuration that could cover most usecases cmake -GNinja DCMAKE_INSTALL_PREFIX=/opt/paraview/install The ParaView image is built with reasonable configuration that should cover most usecases cmake -GNinja Graphical testing is supported using Xvfb and mesa. Run: xvfb-run ctest -j 2 -output-on-failure || xvfb-run ctest -j 1 -rerun-failed -VV Resulting CI in github Technicalities If: _request.draft = falseĬontainer: kitware/paraview-for-ci:$/build If you are using github, your ci.yml file may look like: Resulting CI in gitlab How to use on github xvfb-run ctest -j 2 -output-on-failure || xvfb-run ctest -j 1 -rerun-failed -VV cmake -DCMAKE_PREFIX_PATH=/opt/paraview/install/ -DBUILD_TESTING=ON -DCMAKE_BUILD_TYPE=Release. gitlab-ci.yml file may look like: build-plugin: To get started, you can have a look at the two examples repositories: So we are very happy to introduce vtk-for-ci and paraview-for-ci dockerhub repositories.īy using these docker images, you will be able to very easily build and test your projects. This is especially true since the improvements of the testing framework in both VTK and ParaView in their respective upcoming releases.ĭocker is the solution we choose for this and is a de-facto standard in many communities.

This is why we think that providing tools for the community in order to be able to build and test ParaView plugins, ParaView based applications, VTK dependent modules and VTK based applications will help all these projects grow. It has always been complex for these kind of project to be able to build and run test easily and efficiently in the development process.īuilding the whole of VTK or ParaView is just not possible on every single MR/PR. In the VTK/ParaView ecosystem, there are a number of projects that rely on VTK and ParaView as dependency and are not part of VTK/ParaView per se, eg Flow3D, Salome, Themys, F3D, PVGeo, vtk-dicom, pyvista, vedo, meshio, slicer, CTK, cmb, ttk.