Skip to content

Do we want to clean up and/or partition the training imagery set at all? #14

@zhrandell

Description

@zhrandell

A question occurs to me . . . as of now, we have lumped ALL our training imagery together into a single dataset. From the perspective of trying to increase UIE efficacy in terms of color, etc., a couple of questions occurred to me. Specifically, @keenanjohnson, do you think there'd be any value in removing extraneous instances from our imagery, and/or partionining our data based on broad substrate condition?

For example, a quick review of the images revealed instances of photos that may be a bit too bright, or where the ROV is too close to the seafloor, or where the ROV is too far up above the seafloor (approximate examples of these are below . . . the "too bright" images aren't really that bad, but the "too close" or "too far from the seafloor" examples could potentially be removed).

Image Image Image

What do you think? Could the UIE trained model potentially benefit from removing these extraneous instances?

Second question - could we benefit at all from partitioning the dataset? For example, about 3/5th of our imagery are from relatively flat areas, and then ~ 2/5 are from the Elliott Bay Marina breakwater, where the breakwater riprap causes extensive depth variation to appear in these images (e.g., instances where the ROV is high up above the seafloor). Would it be worth testing a "flat, relatively soft sediment model", and a "breakwater riprap with lots of depth variation" model? The thinking here is that perhaps a model trained specifically on, e.g., breakwater riprap structure, may provide more consistent results when applied to unseen imagery.

Image

All of these points broadly fall under the category of "things we can start to play with now that we can train our own models," per #13!

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