Fix composable blueprints

[kaspermarstal]

The Composable blueprints in ContinuousRegistration/Submissions/ComposableBlueprints are not working. This is due to two issues:

• SuperElastix cannot find the included path. We should add logic to SuperElastix that resolves the path the included blueprint. The included path should be the path relative to the blueprint that includes it. SuperElastix should use provide the full path to the included blueprint to the boost loader.
• SuperElastix has gained additional components in recent weeks. This means the criteria in the composable blueprints would previously be enough to specify a unique component, but now it is not. We should more criteria to these blueprints. The "NameOfClass" criterion might be enough to solve this issue.

[N-Dekker]

@kaspermarstal

The included path should be the path relative to the blueprint that includes it.

So this one does not need to be supported, right?

"./ContinuousRegistration/Submissions/ComposableBlueprints/Composables/ITKv4_base.json"

In ContinuousRegistration\Submissions\ComposableBlueprints\ITKv4_SyN_ANTsNC.json

[N-Dekker]

The existing approach appears to assume that ContinuousRegistration is a subdirectory of the current working directory. Is that a problem?

[N-Dekker]

Does the merge of pull request #350 solve this issue, or is it still necessary to implement "the second bullet" of this issue?

[kaspermarstal]

Yes, that is still necessary. Two composable blueprints at the leaderboard still have N/A results :(

[N-Dekker]

@kaspermarstal

Two composable blueprints at the leaderboard still have N/A results

So these two json files still need to be adjusted, right?

1. https://github.com/SuperElastix/SuperElastix/blob/develop/ContinuousRegistration/Submissions/ComposableBlueprints/AffineTransform.json
2. https://github.com/SuperElastix/SuperElastix/blob/develop/ContinuousRegistration/Submissions/ComposableBlueprints/BSplineTransformPOPI.json

Where can I find the error messages on the server? Or do you know how to fix them already?

[FBerendsen]

I have a case where the relative paths are not working correctly (i.e. in the bash scripts generated by CRC to run locally); the call looks like this:
> [relative_path_a]/SuperElastix --conf [relative_path_b]/blueprint_with_relative_includes.json [...]
It is working if I cd to [relative_path_a] and correct [relative_path_b] accordingly.

Originally posted by @FBerendsen in #350 (comment)

[FBerendsen]

Correction:
It is working if I cd to [relative_path_b] and correct [relative_path_a] accordingly.

[N-Dekker]

@FBerendsen With 7508a1f the paths of the included json files are either absolute, or relative to the path of the including json file. The current working directory (cd) should not matter, when finding the included json files. Are you sure it does?