Anti-pattern is used for setting bg-roi-depth-range; it is handling multiple data-types when it must only handle a single type.
How Has This Been Tested?
Locally and Travis
What Was Done?
Replaced --autoset-depth-range with --manual-set-depth-range.
--manual-set-depth-range: is set to False by default. It must be set to True in order for the inputted bg-roi-depth-range to be used to compute the ROI.
Automatically computing a new --bg-roi-depth-range unless --manual-set-depth-range is given in the CLI, or if manual_set_depth_range is set to True in the given config.yaml.
Breaking Changes
None
Checklists
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
Issue being fixed or feature implemented
Issue stated in #125.
bg-roi-depth-range; it is handling multiple data-types when it must only handle a single type.How Has This Been Tested?
Locally and Travis
What Was Done?
--autoset-depth-rangewith--manual-set-depth-range.--manual-set-depth-range: is set to False by default. It must be set to True in order for the inputtedbg-roi-depth-rangeto be used to compute the ROI.--bg-roi-depth-rangeunless--manual-set-depth-rangeis given in the CLI, or ifmanual_set_depth_rangeis set to True in the givenconfig.yaml.Breaking Changes
None
Checklists