![]() ImageType = (filename, imageTypeField) # looks like "DERIVED\PRIMARY\OP\OP\DERIVED"ĭixonType = imageType. Uid = uids.split() # all of these UIDs have the same ImageType (at least so far as I tested)įilename = (uid) ImageTypeField = '0008,0008' # DICOM field corresponding to ImageType ![]() Uids = volNode.GetAttribute('DICOM.instanceUIDs') # empty for non DICOM volumes # Loop over all volumes, renaming only if DICOM and if node name matches r"imageType \d" ShNode.GetDataNodesInBranch(sceneItemID,c,'vtkMRMLScalarVolumeNode') # If volume is not a DICOM volume, then it is left unchanged # substitutes the "imageType N" with the Dixon type ("F","W","OP", or "IP") def rename_dixon_dicom_volumes(volNodes=None): That is, it will take a name like “501: Legs_T1_Dixon - imageType 3” and change it to “501: Legs_T1_Dixon - F” if it is a “Fat” image, which is much more informative than “imageType 3”, when imageType 3 could be paired with any of the Dixon image types. Just in case it is useful to others in the future, the Python function below (pasteable at the Slicer Python interactor prompt) will take automatically named scalar volumes loaded from Dixon DICOM series and tag them with the type of image they are (“F”, “W”, “IP”, or “OP”). I look at the script repository all the time, and still sometimes miss when it already has the pieces I need to solve my problem. Thanks for any insight/help you can provide! Alternatively, is there a way I can incorporate the image type into the name of the imported volume? For example, if instead of “Image Type 1” being appended to the node name, could “Image Type W” be appended? The DICOM Metadata browser shows the (0008,0008) ImageType field as “ DERIVED, PRIMARY, W, W, DERIVED” for the Water images (or “ DERIVED, PRIMARY, OP, OP, DERIVED” for the OP images, etc.). My question therefore is how Slicer assigns the order, and whether there is a way I can enforce a consistent ordering for Dixon images. These slabs were all acquired on the same scanner in the same imaging session, but somehow the Slicer ordering of Image Types for each one is unique! We have DICOM data from one patient imaging session where the whole lower half of the body was acquired in 4 slabs, each a Dixon set of 4 images. Horos consistenly loads the water and fat pair first (in one series), then the OP series, then the IP series. The R packages oro.dicom and oro.nifti 1 provide the ability to import and visualise medical images that have been stored as DICOM 2 or ANALYZE/NIfTI 3 files. ![]() Dixon images involve 4 series, a water image (W), a fat image (F), and two raw images from which the water and fat images are derived, one referred to as the in-phase (IP) and the other referred to as the opposite-phase (OP). Slicer correctly identifies that there are 4 image types, but does not order them in a consistent way. Hello, I am importing DICOM Dixon images and am getting inconsistent ordering of the image types.
0 Comments
Leave a Reply. |