Either the study panels should be expanded by default, or there should be an option to open all panels.

• color editor is not working
• thumbnails not rendering

• saving cropping tool state
• changing camera's center of rotation to be the cropping bounds center
  • this won't make sense if there is geometry/uncropped labelmaps
• reset crop doesn't trigger a render when crop tool is not enabled

1. Load Sample Data -> Abdomen-MRI
2. Click 3 dots and "Delete Patient"
3. Get errors, more errors on loading Abdomen-MRI again

vue.runtime.esm.js:619 [Vue warn]: Cannot delete reactive property on undefined, null, or primitive value: undefined
warn	@	vue.runtime.esm.js:619
del	@	vue-composition-api.mjs:1077
_delete	@	useDoubleRecord.ts:54
(anonymous)	@	common.ts:22
removeData	@	view-configs.ts:27
(anonymous)	@	pinia.esm-browser.js:1305
(anonymous)	@	datasets-images.ts:95
deleteData	@	datasets-images.ts:94
(anonymous)	@	pinia.esm-browser.js:1305
store.<computed>	@	pinia.esm-browser.js:887
deleteVolume	@	datasets-dicom.ts:263
(anonymous)	@	pinia.esm-browser.js:1305
store.<computed>	@	pinia.esm-browser.js:887
(anonymous)	@	datasets-dicom.ts:282
deleteStudy	@	datasets-dicom.ts:281
(anonymous)	@	pinia.esm-browser.js:1305
store.<computed>	@	pinia.esm-browser.js:887
(anonymous)	@	datasets-dicom.ts:298
deletePatient	@	datasets-dicom.ts:297

After #116, window & level syncing is no longer working. We need to add extra sync code to synchronize the window/level in the store.

@aylward if you have any details you'd like to add, feel free to.

Right now, deleting a dicom dataset does not delete the in-memory files for it.

Quad view should be default, rather than axial primary.

A module panel should be only shown if necessary (i.e., if there are parameters/options that the user must specify every time it is run).

Module panels should only appear once their corresponding tool has been selected in the toolbar.

As a clinician, I'ed like to visit a website and

• Authenticate
• Browse, search, sort DICOM data on my PACS system
• View DICOM data in VolView

@timthirion

Need a cleaner widget infrastructure that supports:

• serializing and restoring measurements
• sufficient hooks for a rich array of widget functionality
• versioned serialization format

We would like to add a bidim tool.

Users would like to undo/redo paint operations.

UX needed for changing label colors.

We want to support the ability to jump to the slice associated with a measurement.

Is this an okay step constant? Should the step constant be computed from the min/max of the pixel range?

Ensure that deleting data doesn't result in an empty parent element.

Examples:

• Deleting the last study should delete the series
• Deleting the last series should delete the dataset

Seems it was broken by this update: 9024d9e

At the bottom of the About window, include a link to the ParaView Medical github account, issue tracker, and kitware support page

Could be done using icons or word Github (or github logo), Issue Tracker (or bug icon), and Support (or wrench/phone icon).

Support link is https://www.kitware.com/what-we-offer/

To reproduce:

1. Load geometry + volume
2. Change the shift of the color transfer function
3. Change geometry colorBy

What we expect: the geometry color changes, and the colormap stays the same.

What actually happens: colormap shift resets.

In addition to flipping the light position, there should be a fixed/moving light option.

Fixed/moving are perhaps confusing terms. How about a three-way toggle, or menu choice: "Lighting: ( ) anterior ( ) posterior ( ) camera"

s

TBD, but should be an FDA-ready software process.

@timthirion

Creation of widgets can be found in widgetProvider. We can probably add a new optional parameter that is a widget's serialized state.

The widget constructor is where we can pass in initial widget state. We will have to add an optional method that subclasses must implement if they want to accept serialized state.

There isn't any way to save widget state in paraview-medical (yet), but you can check out the ruler's onWidgetChange. This gives you an idea of what the widgetState object looks like. In our importState method (or whatever we name it), simply need to update the widget state to match the serialized state.

In addition to saving view configurations, we would want to save tools and labelmaps.

Painting should not reset the camera in 3D view.

I want to try to move to the vue composition api so that logic can be centralized and easier to test/reason about.

• world-space brush
• lerp between points
• can't click once to erase on axial view with abdomen mri dataset in certain spots. Probably an issue with the determining of whether to paint?
• auto-show annotations pane

We will need to update vtk.js once Kitware/vtk-js#2506 lands, since the root cause is due to a bug in the widget manager.

When dicom rescale values are provided, every slice should default to the provided dicom rescale values.

Note: this does mean the non-axial slices have window/level values based on the current slice's rescale values. Changing W/L in the non-axial slices will change the W/L in the axial slice, setting it to "manual W/L" mode.

The 3D view store is extraneous. It's purpose is to store the configuration for the 3D view, which should be handled by the view config store instead.

It would be useful to allow users to download/install a local copy of VolView as a desktop application (via Electron). This will pair nicely with integration with external python scripts for inference, segmentation, etc.

Expected behavior:

1. Load two images
2. Set crosshairs on first image
3. Switch images
4. have crosshairs following mouse on new image

Current behavior:
After 1-3, crosshairs do not follow mouse on new image

We want to support cropping the volume in both the 2D and 3D views.

Repro steps:

• Load a local dicom dataset, and load the Abdomen-MRI sample dataset
• expand all studies to show the thumbnails for each volume
• Some thumbnails will not render

The immediate cause is due to file being undefined on this line: https://github.com/KitwareMedical/VolView/blob/master/src/io/dicom.ts#L138

• Need to ensure that the paint widget remounts properly.

@aylward

Currently the state saving only saves data. The next step is to save the view layout and configuration.

When loading STL or VTP files (ex: ConeSources generated from Paraview), the interface freezes and the following logs show in the debug console:

[Vue warn]: Error in getter for watcher "function () {

            // preventing the watch callback being call in the same execution

            if (running_1) {

                return;

            }

            try {

                running_1 = true;

                source(registerCleanup);

            }

            finally {

                running_1 = false;

            }

        }": "TypeError: curImageMetadata.value is undefined"

found in

---> <VtkTwoView> at src/components/VtkTwoView.vue
       <LayoutGrid> at src/components/LayoutGrid.vue... (1 recursive calls)
         <VMain>
           <VApp>
             <DragAndDrop> at src/components/DragAndDrop.vue
               <App> at src/components/App.vue
                 <Root> vue.runtime.esm.js:619

TypeError: curImageMetadata.value is undefined
    node_modules index.js:9051
    getter_1 vue-composition-api.mjs:1301
    get VueJS
    node_modules chunk-vendors.js:148968
    flushQueue vue-composition-api.mjs:1186
    node_modules chunk-vendors.js:148876
    VueJS 5
    fallbackFlush vue-composition-api.mjs:1193
    queueFlushJob vue-composition-api.mjs:1204
    node_modules chunk-vendors.js:148967
    VueJS 9
    setterHandler vue-composition-api.mjs:932
    set vue-composition-api.mjs:686
    useSceneBuilder useSceneBuilder.ts:44
    applyCb vue-composition-api.mjs:1372
    node_modules chunk-vendors.js:148968
    flushQueue vue-composition-api.mjs:1186
    node_modules chunk-vendors.js:148876
    VueJS 5

This issue can be reproduced directly on the VolView demo. I have trouble understanding where the error comes from, but I assume it's not related to the files I'm using, since I can load them in PVGlance.

Problem: when selecting a layout, camera settings reset. This is undesired behavior.

Expected: when selecting a layout, the views should visually remain the same.

This issue stems from the view components generating their own IDs. Instead, IDs should be provided by the layout, allowing for view config persistence.

The module panel shouldn't appear until data that is required by that module has been loaded.

Given a DICOMWeb host (ie http://localhost:8042/dicom-web) and studyInstanceUID, seriesInstanceUID, sopInstanceUID tuple, load the instance in the viewer.

@timthirion

Ideally this will be a polygonal representation, as mixed volumes in vtk.js is not yet supported.

Only way to generate the previews is to switch to "non-dicom images" and then switch back to the specified patient.

Instead of transforming scene objects into image-space, transform the camera to make the scene look like image space. This has the added benefit of avoiding the extra work of transforming each dataset.

When panning or zooming, resize-to-fit should be disabled until it is reset via (1) a button, or (2) switching datasets.

We can use Alexis' more robust labeling code for the 2D views.

This allows users to see that there are sample datasets they can immediately click on to view.