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

Flexible via specification for xform_brain / shortest_bridging_seq #43

Merged
merged 9 commits into from
Apr 16, 2020

Conversation

jefferis
Copy link
Contributor

@jefferis jefferis commented Apr 16, 2020

In this case via does not have to specify the complete path from sample to reference. This means that it can be used to insist on a particular set of registrations when a range of paths are possible. See #44

* works ok
* still doesn't solve all issues with FAFB14um node
* still feels like we need special handling of scaling transforms (should effectively have weight 0 or minimally reciprocal edge weight 0)
* relax tests to reflect presence of vpath attribute
* sometimes you want to come back to the sample spave via a given brain
* revealed by recursive calls to shortest_bridging_seq
* NB this effectively retires the bridging_sequence option in favour of shortest_bridging_seq in all situations
* note that bridging_sequence required all via steps to be specified
* also prints messages about selected path for transformation
* much more extensive testing
* note that I factored out a small function to avoid repeatedly 
  constructing the bridging graph
* this is also simplified combining paths across the graph
* r cmd check on travis complained
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 70.393% when pulling adceec6 on feature/via-shortest-path into 8896489 on master.

@jefferis jefferis merged commit 38c5e3c into master Apr 16, 2020
@jefferis jefferis deleted the feature/via-shortest-path branch June 9, 2023 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants