Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
otb
otb
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 191
    • Issues 191
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 14
    • Merge Requests 14
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Registry
    • Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Main Repositories
  • otbotb
  • Merge Requests
  • !286

Merged
Opened Nov 09, 2018 by Jordi Inglada@jinglada
  • Report abuse
Report abuse

Add class probability output for RF classifiers

Summary

Add an output to the ImageClassifier application providing an image with the probability of each class for each pixel.

Rationale

The image has as many channels as the number of classes and each channel stores the probability of a class in the order of the labels. Only the implementation for SharkRF has been done.

Implementation Details

Classes and files

Many files and classes are touched, since the approach is to add a tag which indicates if a particular ML model knows how to output the probabilities. It is the same approach used for the confidence map. Therefore, all ML models have now this tag.

The ClassificationFilter has a new output containing the probability map.

Applications

The ImageClassifier application has a new parameter "probamap" to activate the output. The number of classes has to be given also, since not all models store the number of classes.

Additional notes

Copyright

The copyright owner is COPYRIGHT OWNER (OR OWNER'S AGENT) and has signed the ORFEO ToolBox Contributor License Agreement.


Check before merging:

  • All discussions are resolved
  • At least 2 👍 votes from core developers, no 👎 vote.
  • The feature branch is (reasonably) up-to-date with the base branch
  • Dashboard is green
  • Copyright owner has signed the ORFEO ToolBox Contributor License Agreement
Edited Jan 08, 2019 by Jordi Inglada
  • Discussion 27
  • Commits 7
  • Changes 38
Assignee
No assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: orfeotoolbox/otb!286

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.