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] SEG/RTSTRUCT names do not auto-populate as a grouping in Segmentation list #3426

Closed
03shek opened this issue May 29, 2023 · 1 comment
Assignees
Labels
Bug Verified Bug reported, reproducible, and verified. Duplicate

Comments

@03shek
Copy link

03shek commented May 29, 2023

Describe the Bug

RTSTRUCT/SEG name is not auto-populated as the name of that collapsible segmentation grouping after loading a RTSTRUCT/SEG.

Steps to Reproduce

  1. Load a study with RTSTRUCT or SEG that has a name. https://v3-demo.ohif.org/viewer?StudyInstanceUIDs=1.2.840.113619.2.290.3.3767434740.226.1600859119.501

  2. Double-click the RTSTRUCT (named "Contours on PET") to load it. Click YES when prompted.

  3. RTSTRUCT/SEG ROIs are populated in the Segmentation list, but the RTSTRUCT/SEG name is not auto-populated as the name of that collapsible grouping.
    image

  4. Another example study, but with multiple SEGS
    image

The current behavior

RTSTRUCT/SEG name ("Contours on PET") does not auto-populate as the name of a collapsible segmentation grouping after loading a RTSTRUCT/SEG. User must manually rename that segmentation grouping to keep track of which RTSTRUCT/SEG has been opened.

The expected behavior

RTSTRUCT/SEG name should auto-populate as the name of that collapsible segmentation grouping after loading a RTSTRUCT/SEG.

OS

Windows 10

Node version

16.14.0

Browser

Chrome 111.0.0

@03shek 03shek added Awaiting Reproduction Can we reproduce the reported bug? Community: Report 🐛 labels May 29, 2023
@jbocce jbocce added Bug Verified Bug reported, reproducible, and verified. and removed Awaiting Reproduction Can we reproduce the reported bug? labels Jun 20, 2023
@jbocce
Copy link
Collaborator

jbocce commented Jun 26, 2023

This issue and #3421 will be addressed by the same change. For now I will keep both open so that each reporter can verify/comment on the ultimate fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Verified Bug reported, reproducible, and verified. Duplicate
Projects
None yet
Development

No branches or pull requests

4 participants