🥅 Add registration guardrails

[shnizzedy]

Fixes

Recreation of #1789 by @shnizzedy
Related to FCP-INDI/TheWay#8 by @shnizzedy

Description

QC checks registration steps and either crashes or changes the random seed and retries the step.

Thresholds are specified in the pipeline config

C-PAC/CPAC/resources/configs/pipeline_config_default.yml

Lines 587 to 597 in b9a7ad0

	registration_workflows:
	# Minimum QC values to allow a run to complete post-registration
	# Set any metric empty (like "Dice:") or to None to disable that guardrail
	# Default thresholds adopted from XCP-Engine
	# (https://github.com/PennLINC/xcpEngine/blob/397ab6cf/designs/cbf_all.dsn#L66)
	quality_thresholds:
	Dice: 0.8
	Jaccard: 0.9
	CrossCorr: 0.7
	Coverage: 0.8

Technical details

Guardrails strategy

For a node that calculates a warp:

1. Make a clone with an incremented seed.
2. Put a guardrail on each of those two nodes, with the retry node raising a BadRegistrationError on QC failure.
3. For each output, use a sequence of Nipype Merge and Select utility nodes to choose which node's outputs to used based on the failure status of the first-try node's guardrail.
   

I've got some (I think) good ideas to abstract the guardrails further so the installation can be simpler in the future, but that'll be after 1.8.5 (if ever).

Also

• Changes random.log with a single logged seed to random.tsv with a logged seed per try (to record the incremented seed for any retries that succeed where the first try failed)
• Adds fallback forkable option for BBR where
  • Off does no BBR;
  • On does one BBR attempt with one seed-incremented retry;
  • fallback does one BBR attempt, falling back to no-BBR on failure
• 🔧 Add fail_fast to expose Nipype's stop_on_first_crash #1816

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I updated the changelog.
• I added or updated documentation (📝 Document registration guardrails fcp-indi.github.io#293, in progress).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[shnizzedy]

Making this a draft again after a convo w/ Greg; going to do BBR on its own first, then this configurable to

1. Do second run only on failure
2. Choose better reg between two runs
3. Don't guardrail