-
Notifications
You must be signed in to change notification settings - Fork 123
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
FIX: Add animation using DPF animate() #1599
Conversation
Please add one of the following labels to add this contribution to the Release Notes 👇 |
Codecov Report
@@ Coverage Diff @@
## main #1599 +/- ##
==========================================
+ Coverage 79.52% 82.92% +3.39%
==========================================
Files 44 44
Lines 7151 7151
==========================================
+ Hits 5687 5930 +243
+ Misses 1464 1221 -243 |
@GuillemBarroso there is something going on with the doc build. It doesn't finish! |
Hm... It did finish when I built it locally this morning! |
I dont think it works:
|
These warnings were added in VTK 9.2.2 and are harmless. PyVista needs to suppress these by adding an option in extract_edges to warn if edges are renumbered. |
So I guess it should be fixed upstream. By the way, we should probably consider upgrading VTK. @GuillemBarroso realised we are a couple of releases behind. Maybe when Pyvista fixes the warnings?? |
I've only seen that in the latest VTK v9.2.2 Let me check the workflows to see which one is getting installed. |
Yea, it's Either something changed upstream (and pyvista hasn't made a new release lately), or we need to fix something. Depending on how annoying it is, we can get a patch release out soon. About to finally drop a minor release. |
Have you used a newly created python env?? |
After plenty of re-runs, now it works. It didn't make sense to fail. There are some merge conflicts which after fixed will re-trigger the workflows... let's see if we are more lucky now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Good job @GuillemBarroso !
Yes! I always do. Just in case I have tried again, and I get the same message: "No matching distribution found for vtk==9.0.3" |
It's there on PyPI. I bet your issue is the release doesn't have a Python 3.10 wheel. See: |
@GuillemBarroso if you are using conda just create a new python environment using |
Co-authored-by: German <[email protected]>
Thanks @germa89. I was using Python venv as recommended in the dev guide. Now I have just installed conda and I was able to install the doc requirements. Thanks. |
Investigating issue #1579.
🐞 Problem
Locally, the documentation shows the correct animation. However, it looks like it is not able to display it properly in the deployed documentation.
This PR attempts to use the
.animate()
method from DPF in order to have the animation properly displayed in the documentation.Changes:
composite_dcb.py
:.animate()
method.requrements_docs.txt
:vtk
dependency to version 9.2.2. An error was found whenpip install -r requrements/requirements_docs.txt
complaining about not finding version 9.0.3.💡 Conclusion
The animation using
.animate()
is different from the one generated usingpv.Plotter()
. It only shows the displacements instead of the cohesive damage.First, we would need to confirm that the
.animate()
Gif is properly displayed in the documentation. Then, I will create an issue to further investigate how to display the cohesive damage using.animate()
.