ima extension), load them into a database that is then shown to the user in the DICOM browser. Note that the DICOM indexer in Slicer implements recursive checking of a directory tree, analyzing all file contents (DICOM files don’t use any specific file extension, so you cannot assume that all DICOM files have. Parsing gigabytes of data can be completely normal. I think it is a reasonable expectations from users to be able to select a directory that contains the relevant data. Recursively check when the user selects a directory, and assume they inputted a proper directory, which could crash the program as I mentioned. Simply enable the “Apply” button, assuming the user inputted a proper directory, and only check when the button is clicked. Nevertheless, I thought about two potential solutions, and am having a dilemma of which two of the following methods I should take: However, checking the folder size is no more efficient than the recursive check. I would want to check the size of that directory first, to make sure the user did not select the wrong folder (which could potentially contain terabytes of irrelevant files, and recursively checking an enormous directory to see whether each filename ends with the aforementioned two extensions would be too intensive most likely crash the program without saving any data). When the user selects a directory, I would like to recursively check whether the selected directory contains any. However, I would like to give the user a choice to select a directory containing DICOMs. The user only has to input a volume and press the button.
I am developing a segmentation module called “PhantomSegmenter” which would automatically segment phantoms.
0 kommentar(er)
