Skip to content

Undersirable cutouts when using max_invdepth_vizu = min(inverse_depth.max(), 1 / 0.1) ; min_invdepth_vizu = max(1 / 250, inverse_depth.min()) .....but clipping to inverse_depth.max() and max_invdepth_vizu = min(inverse_depth.max(), 1 / 0.1) min_invdepth_vizu = max(1 / 250, inverse_depth.min()) works better  #85

@Jaykumaran

Description

@Jaykumaran

clipped to [0.1m;250m] range works bad when there are extreme cases like transparent image and foggy image outliers,

Input:

foggy4

Magma Cmap:
foggy4inverse_depth_cmap

 max_invdepth_vizu  = inverse_depth.max()
min_invdepth_vizu =  inverse_depth.min()

foggy4inverse_depth_bnw

 max_invdepth_vizu  = min(inverse_depth.max(), 1 / 0.1)
min_invdepth_vizu = max(1 / 250, inverse_depth.min())

foggy4inverse_depth_bnw

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions