Skip to content
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: Check for valid qform before calculating change #466

Merged
merged 2 commits into from Feb 27, 2020

Conversation

@effigies
Copy link
Collaborator

effigies commented Feb 26, 2020

This is a follow-up to #365. We were running into the case where valid_qform was False, and thus qform was an unbound variable, but trying to compare the new qform to the old qform.

This bug was introduced in 92e63fe, first released in 0.10.3. As this was included in fMRIPrep as of poldracklab/fmriprep@b6d1e51, this bug is expected to affect versions 1.5.0-20.0.0 of fMRIPrep.

Fixes #465.

@effigies effigies added this to the 1.1.8 milestone Feb 26, 2020
@pull-assistant

This comment has been minimized.

Copy link

pull-assistant bot commented Feb 26, 2020

Score: 1.00

Best reviewed: commit by commit


Optimal code review plan

     FIX: Check for valid qform before calculating change

     TEST: Test bad qform and no good affines

Powered by Pull Assistant. Last update 2878576 ... 579c819. Read the comment docs.

@pep8speaks

This comment has been minimized.

Copy link

pep8speaks commented Feb 26, 2020

Hello @effigies, Thank you for updating!

Cheers! There are no style issues detected in this Pull Request. 🍻 To test for issues locally, pip install flake8 and then run flake8 niworkflows.

Comment last updated at 2020-02-26 17:35:11 UTC
@effigies effigies force-pushed the effigies:fix/unbound_qform branch from 53c7ea2 to 2878576 Feb 26, 2020
@effigies

This comment has been minimized.

Copy link
Collaborator Author

effigies commented Feb 26, 2020

Hard one to test. I don't know how to create a file that doesn't have a valid qform. I've asked the submitter to send me their header, and maybe we can do something there.

@effigies effigies force-pushed the effigies:fix/unbound_qform branch from d2440f9 to 579c819 Feb 26, 2020
@effigies

This comment has been minimized.

Copy link
Collaborator Author

effigies commented Feb 26, 2020

@effigies effigies changed the base branch from master to maint/1.1.x Feb 26, 2020
Copy link
Contributor

oesteban left a comment

Looks great!

@effigies effigies merged commit 6794a8b into nipreps:maint/1.1.x Feb 27, 2020
7 checks passed
7 checks passed
Codacy/PR Quality Review Up to standards. A positive pull request.
Details
ci/circleci: build Your tests passed on CircleCI!
Details
ci/circleci: build_docs Your tests passed on CircleCI!
Details
ci/circleci: get_data Your tests passed on CircleCI!
Details
ci/circleci: test_package Your tests passed on CircleCI!
Details
ci/circleci: test_pytest Your tests passed on CircleCI!
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
effigies added a commit to poldracklab/fmriprep that referenced this pull request Feb 27, 2020
20.0.1 (February 27, 2020)

Bug-fix release in 20.0.x series.

This release includes fixes for rare images with invalid qform matrices and some minor
improvements in report readability and inclusion of common templates in the Docker image.

  * FIX: Handle qforms with invalid quaternions (nipreps/niworkflows#466)
  * FIX: update niworkflows location (#2005)
  * ENH: Display errors as summary/details elements in reports (nipreps/niworkflows#464)
  * DOC: Add ``--fs-subjects-dir`` usage to slurm example (#2003)
  * CI: Test that Docker image can run a common set of output spaces without network access (#1997)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

3 participants
You can’t perform that action at this time.