-
Notifications
You must be signed in to change notification settings - Fork 437
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: Viz test correction #1374
FIX: Viz test correction #1374
Conversation
Fix typos and formatting in .rst files and Python examples' documentations: - Fix typos in files. - Replace tabs for two white spaces. - Fix errors in citation and DIPY internal cross-refs. - Add missing cross-refs (e.g. Aganj MRM 2010). - Add links where necessary (ISBI HARDI Contest 2013 and FreeSurfer). - Fix LaTeX math formatting errors. - Make the example/DIPY code object markdown consistent (inverted commas). - Capitalize the acronym long names' first/corresponding letters (e.g. Constrained Spherical Deconvolution). - Capitalize acronyms (e.g. FA). - Make the writing of terms consistent in terms of uppercase/lowercase (e.g. b0 vs. B0; cospus callosum vs. Corpus Callosum, etc.). - Use the [NameYear] convention for citations. - Place all citations under a 'References' section, and use the subsection markdown for the section. - Use inverted commas consistently to reference code objects. - Make the b-value units consistent across files (s/mm^2). - Create and include missing figures for 'reconst_fwdti.py'. - Write DIPY instead of any of its variants in the documentation. - Link the first appearance of dipy in every file (use dipy_).
Use the reST syntax to highlight code blocks in README.rst when describing the DIPY installation commands.
…void "Permission Error: [WinError 32]" on windows
…vtkSmartVolumeMapper
Because of this line, I get this error on python 2.7 :
This syntax is authorized in python 3.6. I do not see how I can manage that. Indeed, the recorder files need to be closed before the end of this |
|
While at it, can you describe what you've recorded for |
While testing your patch, I realized that using protocol=-1 in |
Regarding the |
Because
Otherwise, ok for pickle and comment on test @MarcCote |
Codecov Report
@@ Coverage Diff @@
## master #1374 +/- ##
==========================================
- Coverage 87.04% 87.01% -0.04%
==========================================
Files 228 228
Lines 29077 29086 +9
Branches 3129 3131 +2
==========================================
- Hits 25311 25310 -1
- Misses 3059 3068 +9
- Partials 707 708 +1
Continue to review full report at Codecov.
|
LGTM |
dipy/viz/window.py
Outdated
@@ -514,7 +514,7 @@ def _stop_recording_and_close(obj, evt): | |||
self.iren.Start() | |||
# Deleting this object is the unique way | |||
# to close the file. | |||
del recorder | |||
recorder = None |
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.
In the _stop_recording_and_close
shouldn't we have something like:
if (recorder):
recorder.stop()
to prevent crash because of nullref?
Or is it that that scenario won't happen?
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.
From what I understand self.iren.Start()
is blocking until the user closes the window at which point the ExitEvents are handled before releasing the block. So, it should happen that recorder is None inside _stop_recording_and_close
.
But, yeah, we could add the check to be on the safe side because something VTK still surprises me :P.
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.
FIX: Viz test correction
The goal of this PR is to update some tests for VTK 7.1.x. This PR:
it should resolve #1282.
Can you have a look and test it @ranveeraggarwal @MarcCote @dmreagan?