-
Notifications
You must be signed in to change notification settings - Fork 25
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 deformation in fields container animate #582
Conversation
Codecov Report
@@ Coverage Diff @@
## master #582 +/- ##
==========================================
- Coverage 87.08% 87.06% -0.02%
==========================================
Files 68 68
Lines 7455 7453 -2
==========================================
- Hits 6492 6489 -3
- Misses 963 964 +1 |
@@ -517,6 +517,11 @@ def animate(self, save_as=None, deform_by=None, scale_factor=1.0, **kwargs): | |||
# Define the field extraction using the fields_container and indices | |||
extract_field_op = dpf.core.operators.utility.extract_field(self) | |||
|
|||
loop_over = self.get_time_scoping() | |||
frequencies = self.time_freq_support.time_frequencies |
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.
@PProfizi I don't understand this changes, it means that we can't animate if we don't have a time freq support?
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.
@cbellot000 That was already the case, I just moved this up. Right now the animation is based on the TimeFreqSupport, yes.
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.
to add in the US to handle having no time freq support and to be able to create an animator with a mesh + a fields container
An error has been found in the computation of the deformation field.