Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in Model Evaluation Metrics #32

Open
sandersson94 opened this issue Nov 9, 2021 · 2 comments
Open

Bug in Model Evaluation Metrics #32

sandersson94 opened this issue Nov 9, 2021 · 2 comments

Comments

@sandersson94
Copy link

Describe the bug
Hello! Please forgive me if I am wrong!

In Evaluation metrics box [33] in 4-model.ipynb max_y should be reference to true.shape[1] rather than true.shape[0]

https://github.com/wri/sentinel-tree-cover/blob/master/notebooks/4-model.ipynb?short_path=af94e1f#L1269

https://github.com/wri/sentinel-tree-cover/blob/master/notebooks/4-model.ipynb?short_path=af94e1f#L1292

@sandersson94
Copy link
Author

Ah - it's irrelevant since the axis is the same length. Ignore this!

@sandersson94
Copy link
Author

I wanted to share a concern with the function used for Evaluation Metric: compute_f1_score_at_tolerance

Could the evaluation metric unjustly reward over-prediction of trees?

Here is an example where I have a prediction with 38 pixels of trees, vs a ground truth of 12 pixels with trees. Here the metric shows 100% precision (12 tp and 0 fp), even though there is not a coregistration error, but instead a commission error. The commission error is not picked up by the modified Evaluation Metric.

image

I hope you consider this useful!

Best regards,
Simon

@sandersson94 sandersson94 reopened this Nov 9, 2021
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

No branches or pull requests

1 participant