facebookresearch / facebookresearch/detectron2

Visualizations on W&B

Open
#3,404 10 comments 3 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
34.7k
Forks
7.9k
PR merge metrics
No merged PRs in 30d

Description

## 🚀 Feature
Allow visualization of training progress using media panels and tables.

## Motivation & Examples
This is based on this [issue](https://github.com/facebookresearch/detectron2/issues/774).
I'm an engineer at W&B and I've been working with object detection tasks. I regularly use some of the following visualizations on W&B dashboards. Would the following features be useful to other detection users? I'd like to know what the maintainers think.
### **Bounding box & Segmentation maps debugger**

W&B supports interactive media panels, where you can track how training progresses by adjusting the steps, confidence scores, and classes of predictions in real-time.
![ezgif com-gif-maker (2)](https://user-images.githubusercontent.com/15766192/130792944-77c59dbd-861b-4161-9c62-5f71e44bac7e.gif)

Try it live [here](https://wandb.ai/cayush/ert/runs/xc4m2xip?workspace=user-cayush)

The Media panel also supports debugging segmentation maps.
![semantic segmentation (1)](https://user-images.githubusercontent.com/15766192/130792997-887b706c-13b2-4f18-8e7b-10ded88debfa.gif)

### Dataset visualization and versioning

With W&B tables, you can visualize, query, and filter your datasets in your browser.

Quickly compare results across different training epochs, datasets, hyperparameter choices, model architectures etc. For example, [take a look at this comparison of two models on the same test images →](https://wandb.ai/stacey/evalserver_answers_2/artifacts/results/eval_Daenerys/c2290abd3d7274f00ad8/files/eval_results.table.json#b6dae62d4f00d31eeebf$eval_Bob)

Screen Shot 2021-04-29 at 8 55 25 PM (1)

**Model versioning and DAGs**
![ezgif com-gif-maker (1) (1)](https://user-images.githubusercontent.com/15766192/130798266-0647a420-f5bd-442e-b556-d022f65fbdf3.gif)

We can have the user set

- the model logging period
- and the desired metric they'd like to optimize.

Based on that, we'll log models after every `model logging period` with alias `best` if the current model performs best on the `desired metric`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.