-
Notifications
You must be signed in to change notification settings - Fork 2
doc: Add extended migration guide #363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
12de712
doc: Add extended migration guide
AlejandroFernandezLuces 97810f4
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 7e30b78
chore: adding changelog file 363.miscellaneous.md [dependabot-skip]
pyansys-ci-bot 77d8d27
fix: Pre-commit
AlejandroFernandezLuces 1ca7134
Merge branch 'doc/migration-guide' of https://github.com/ansys/ansys-…
AlejandroFernandezLuces 932b41c
fix: Vale
AlejandroFernandezLuces b7a3846
fix: Vale warnings
AlejandroFernandezLuces 4eca2b4
fix: Vale warnings
AlejandroFernandezLuces 2975177
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces 4a91e01
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces 9be5646
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces 8005b38
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces bfa6f50
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces bf17548
Apply suggestions from code review
AlejandroFernandezLuces 69b025f
Merge branch 'main' into doc/migration-guide
AlejandroFernandezLuces 6d30c70
fix: Doc review suggestions
AlejandroFernandezLuces 2a61348
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 0963bd4
fix: Vale
AlejandroFernandezLuces 1ab170c
Merge branch 'doc/migration-guide' of https://github.com/ansys/ansys-…
AlejandroFernandezLuces File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Doc: Add extended migration guide |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,217 @@ | ||
| .. _ref_migration_guide: | ||
|
|
||
| Migration | ||
| ######### | ||
|
|
||
| This section helps you migrate from PyVista plotters to the Ansys Tools Visualization Interface plotters. | ||
| It consists of two major topics: | ||
|
|
||
| - `Code migration`_ | ||
| - `Documentation configuration migration`_ | ||
|
|
||
| Code migration | ||
| ============== | ||
| This topic explains how to migrate from PyVista plotters to the new Ansys Tools Visualization Interface plotters. Because cases vary greatly, it provides a few examples that cover the most common scenarios. | ||
|
|
||
| Replace PyVista plotter code with Ansys Tools Visualization Interface plotter code | ||
| ---------------------------------------------------------------------------------- | ||
| If you only need to plot simple PyVista meshes, you can directly replace your PyVista plotter code with the Ansys Tools Visualization Interface plotter code. | ||
| On top of common PyVista functionalities, the Ansys Tools Visualization Interface plotter provides additional interactivity such as view buttons and mesh slicing. | ||
|
|
||
| The following code shows how to do the plotter code replacement: | ||
|
|
||
| - PyVista code: | ||
|
|
||
| .. code-block:: python | ||
| import pyvista as pv | ||
| # Create a PyVista mesh | ||
| mesh = pv.Cube() | ||
| # Create a plotter | ||
| pl = pv.Plotter() | ||
| # Add the mesh to the plotter | ||
| pl.add_mesh(mesh) | ||
| # Show the plotter | ||
| pl.show() | ||
| - Ansys Tools Visualization Interface code: | ||
|
|
||
| .. code-block:: python | ||
| import pyvista as pv | ||
| from ansys.tools.visualization_interface import Plotter | ||
| # Create a PyVista mesh | ||
| mesh = pv.Cube() | ||
| # Create a plotter | ||
| pl = Plotter() | ||
| # Add the mesh to the plotter | ||
| pl.plot(mesh) | ||
| # Show the plotter | ||
| pl.show() | ||
| Convert your custom meshes to objects usable by the Ansys Tools Visualization Interface plotter | ||
| ----------------------------------------------------------------------------------------------- | ||
|
|
||
| Your custom object must have a method that returns a PyVista mesh and a method that exposes a ``name`` or ``id`` attribute of your object: | ||
|
|
||
| .. code-block:: python | ||
| class CustomObject: | ||
| def __init__(self): | ||
| self.name = "CustomObject" | ||
| self.mesh = pv.Cube(center=(1, 1, 0)) | ||
| def get_mesh(self): | ||
| return self.mesh | ||
| def name(self): | ||
| return self.name | ||
| You then need to create a :class:`~ansys.tools.visualization_interface.types.mesh_object_plot.MeshObjectPlot` instance that relates the PyVista mesh with your custom object: | ||
|
|
||
| .. code-block:: python | ||
| from ansys.tools.visualization_interface import MeshObjectPlot | ||
| custom_object = CustomObject() | ||
| mesh_object_plot = MeshObjectPlot( | ||
| custom_object=custom_object, | ||
| mesh=custom_object.get_mesh(), | ||
| ) | ||
| With this, you can use the Ansys Tools Visualization Interface plotter to visualize your custom object. It enables interactivity such as picking and hovering. | ||
|
|
||
|
|
||
| Customize the PyVista backend | ||
| ----------------------------- | ||
|
|
||
| You can customize the backend of the Ansys Tools Visualization Interface plotter to enable or turn off certain functionalities. The following code shows how to enable picking: | ||
|
|
||
| .. code-block:: python | ||
| from ansys.tools.visualization_interface import Plotter | ||
| from ansys.tools.visualization_interface.backends import PyVistaBackend | ||
| backend = PyVistaBackend(allow_picking=True) | ||
| # Create a plotter | ||
| pl = Plotter(backend=backend) | ||
| # Add the MeshObjectPlot instance to the plotter | ||
| pl.plot(mesh_object_plot) | ||
| # Show the plotter | ||
| pl.show() | ||
| If you want to customize the backend even more, you can create your own backend by inheriting from the :class:`~ansys.tools.visualization_interface.backends.pyvista.PyVistaBackendInterface` class | ||
| and implementing the required methods: | ||
|
|
||
| .. code-block:: python | ||
| @abstractmethod | ||
| def plot_iter(self, plottable_object: Any, name_filter: str = None, **plotting_options): | ||
| """Plot one or more compatible objects to the plotter. | ||
| Parameters | ||
| ---------- | ||
| plottable_object : Any | ||
| One or more objects plot. | ||
| name_filter : str, default: None. | ||
| Regular expression with the desired name or names to include in the plotter. | ||
| **plotting_options : dict, default: None | ||
| Keyword arguments. For allowable keyword arguments, see the | ||
| :meth:`Plotter.add_mesh <pyvista.Plotter.add_mesh>` method. | ||
| """ | ||
| pass | ||
| @abstractmethod | ||
| def plot(self, plottable_object: Any, name_filter: str = None, **plotting_options): | ||
| """Plot a single object to the plotter. | ||
| Parameters | ||
| ---------- | ||
| plottable_object : Any | ||
| Object to plot. | ||
| name_filter : str | ||
| Regular expression with the desired name or names to include in the plotter. | ||
| **plotting_options : dict, default: None | ||
| Keyword arguments. For allowable keyword arguments, see the | ||
| :meth:`Plotter.add_mesh <pyvista.Plotter.add_mesh>` method. | ||
| """ | ||
| pass | ||
| The rest of the methods are implemented for you. This ensures that while you can customize what you need for plotting, | ||
| the rest of the functionalities still work as expected. For more information, see the backend documentation. If you | ||
| need to even go further, you can create your own plotter by inheriting from the :class:`~ansys.tools.visualization_interface.backends._base.BaseBackend` class and implementing the required methods, | ||
| although this may break existing features. | ||
|
|
||
| Customize the picker or hover behavior | ||
| -------------------------------------- | ||
| You can customize the picker of the Ansys Tools Visualization Interface plotter to decide what happens when you pick or hover over an object. | ||
| For example, if you want to print the name of the picked object, you can do it as described in the :ref:`sphx_glr_examples_00-basic-pyvista-examples_custom_picker.py` example. | ||
|
|
||
| Use the PyVista Qt backend | ||
| -------------------------- | ||
| You can use the PyVista Qt backend with the Ansys Tools Visualization Interface plotter. To do this, you must set the PyVista backend to Qt | ||
| before creating the plotter: | ||
|
|
||
| .. code-block:: python | ||
| cube = pv.Cube() | ||
| pv_backend = PyVistaBackend(use_qt=True, show_qt=True) | ||
| pl = Plotter(backend=pv_backend) | ||
| pl.plot(cube) | ||
| pl.backend.enable_widgets() | ||
| pv_backend.scene.show() | ||
| You can then integrate the plotter into a PyQt or PySide app by disabling the ``show_qt`` parameter. | ||
| For more information about this, see the `PyVista documentation <https://qtdocs.pyvista.org/>`_. | ||
|
|
||
|
|
||
| Documentation configuration migration | ||
| ===================================== | ||
|
|
||
| This topic explains how to migrate from the PyVista documentation configuration to the new Ansys Tools Visualization Interface documentation configuration. | ||
|
|
||
| 1. Add environment variables for documentation: | ||
|
|
||
| .. code-block:: python | ||
| os.environ["PYANSYS_VISUALIZER_DOC_MODE"] = "true" | ||
| os.environ["PYANSYS_VISUALIZER_HTML_BACKEND"] = "true" | ||
| 2. Use PyVista DynamicScraper: | ||
|
|
||
| .. code-block:: python | ||
| from pyvista.plotting.utilities.sphinx_gallery import DynamicScraper | ||
| sphinx_gallery_conf = { | ||
| "image_scrapers": (DynamicScraper()), | ||
| } | ||
| 3. Add PyVista viewer directive to extensions: | ||
|
|
||
| .. code-block:: python | ||
| extensions = ["pyvista.ext.viewer_directive"] | ||
| 4. Make sure you are executing the notebook cells: | ||
|
|
||
| .. code-block:: python | ||
| nbsphinx_execute = "always" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,8 @@ | ||
| (?i)Ansys | ||
| pytest | ||
| unhovered | ||
| unhovered | ||
|
|
||
| t.M | ||
| a.P | ||
| e.B | ||
| r.A |
Binary file not shown.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.