Project-MONAI / Project-MONAI/MONAI

TensorBoardImageHandler for multiple branches

Open
#6,081 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Contribution wanted enhancement
Dominant language
Python
Stars
8.7k
Forks
1.6k
Avg merge
5d 1h
Merged PRs (30d)
20

Description

Is your feature request related to a problem? Please describe.
I have a problem using TensorBoardImageHandeler in 2 ways. I have have code snippet below. First, during each epoch, the index of the image is not fixed, so I always get new image and corresponding label and output.

Second, if I tried to add extra images, there is no way to point to with other labels. In case here, I want to change NC to NP branch.

        TensorBoardImageHandler(log_dir=log_dir, 
                                max_channels = 3,
                                batch_transform=from_engine(keys=["image", "label"]),
                                output_transform=from_engine_hovernet(keys=["pred"], nested_key=HoVerNetBranch.NC.value),
                               )

Describe the solution you'd like
Ideally , the image will be fixed to specific index, and I am able to point to different tag names for the handler, so extra branches can be incorporated.

Thanks A lot!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the TensorBoardImageHandler entry point and trace how images, labels, outputs, and tags are selected across epochs. Define the expected behavior for a fixed image index and for separate tags or branches, then add coverage for both requested use cases before verifying the handler output.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
data-visualization, machine-learning
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.