Comments (4)
Deleting those with the Markups module causes Slicer to crash as well
from slicetracker.
Deleting those with the Markups module causes Slicer to crash as well
I guess this is it. Can you create a small self-contained script to reproduce the problem, and submit a bug on Slicer mantis, if reproducible in the nightly build?
For the purposes of this project, I would not delete intermediate result, especially since it might be needed later on to go back and compare. Results for all steps should be maintained in some data structure.
from slicetracker.
Ok, I will keep this in mind.
You are right, we should maybe keep all data, but then we need to think about namings.
For instance, retrying a registration would then cause, that the registration result selector would list the same "seriesnumber:seriesdescription".
So holding ALL data requires a better naming:
Maybe something like "seriesnumber:seriesdescription_Retry_1"...
from slicetracker.
We don't delete the "old" targets
from slicetracker.
Related Issues (20)
- Zframe registration HOT 2
- Add flexibility to define expected series description of pre-procedural T2 image
- Dicom tag not recognized HOT 8
- Build errors HOT 2
- Timestamps for all data received/stored HOT 2
- Printable template sheet for calculated template holes
- Provide functionality for segmenting preop image in SliceTracker
- Consider using Elastix registration as an alternative registration solution HOT 1
- Four-Up Quantitative layout for displaying displacement charts
- Add registration result confirmation dialog logging who approved the result HOT 1
- SliceTracker breaks when running quick mode after automatic segmentation in Intraop HOT 6
- (maybe) bugs, that need to be checked (found during prospective evaluation) HOT 2
- Assigned series type uses the module settings pattern instead of fixed type
- IncomingDataMessageBox doesn't remember checkbox state HOT 1
- If empty volumes were produced during failing registration, filename must not show up in results.json
- DisplacementChartPlugin not visible when going through whole workflow
- Automatic Segmentation validation dialog problem when new images received
- slicer.dicomDatabase is sometimes not initialized while indexing input DICOM
- New case button is disabled until case directory is populated
- SliceTracker does not work on 4.11.20200930 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from slicetracker.