Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Segmentation configuration file fix #482

Merged
merged 2 commits into from
Mar 3, 2020
Merged

Segmentation configuration file fix #482

merged 2 commits into from
Mar 3, 2020

Conversation

eschnider
Copy link
Contributor

Status

READY

Description

The --evaluation_units parameter was located under [EVALUATION], instead of [SEGMENTATION] in two of the provided config files. So when using these files, the parameter is not read out, and the default value foreground is used instead.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • My code follows the code style of this project.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Todos

  • Tests
  • Documentation

Impacted Areas in Application

List general components of the application that this PR will affect:

  • Config files

the evaluation_units parameter actually belongs to the segmentation parameters, not evaluation parameters
@wyli wyli merged commit 6c61333 into NifTK:dev Mar 3, 2020
@eschnider eschnider deleted the patch-1 branch March 3, 2020 14:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants