Skip to content

tolerant bracket size selection#2113

Merged
cbentejac merged 2 commits into
developfrom
dev/tolerantBracketCount
Jul 17, 2023
Merged

tolerant bracket size selection#2113
cbentejac merged 2 commits into
developfrom
dev/tolerantBracketCount

Conversation

@servantftransperfect

Copy link
Copy Markdown
Contributor

Bracket size selection is now tolerant to at most two spurious image in the images list.

rule : (Bracket size * countGroupsWithThisSize) >= totalImages - 2

In addition to comparing the exposure levels of the sorted input images
to determine whether a new exposure group must be created, this commit
adds a detection based on the path of the image: if the directory
containing the current image is not the same as the one of the previous
image, then we assume the dataset is different, and there is no point
in comparing the current image's exposure level with the previous one's.

Instead, we directly create a new exposure group.

In cases where images from different datasets have very similar
exposure levels, this prevents having outliers identified as being part
of the current exposure group.

@cbentejac cbentejac left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a detection for new exposure groups based on the path of the images to correctly handle cases where the outlier(s) might have an exposure level that would be coherent with the current exposure group, thus causing an erroneous bracket detection.

For example, if an outlier's exposure level is (22.0, 10.6, 200) and it gets sorted before a dataset whose first image has an exposure level of (22.0, 10.2, 200), both images would be put into the same exposure group unless we use the path information that's available.

@cbentejac cbentejac merged commit 26dee73 into develop Jul 17, 2023
@cbentejac cbentejac deleted the dev/tolerantBracketCount branch July 17, 2023 16:23
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