Editing Dicom package

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
The {{Forge|dicom}} package is part of the [[Octave Forge]] project.  The package is currently maintained by John Donoghue.
+
The {{Forge|dicom}} package is part of the [[Octave Forge]] project.  The package is at an early development stage and it is maintained by Andy Buckle with contributions by Judd Storrs and Kris Thielemans.
  
= What is the aim of this package? =
+
== What is the aim of this package? ==
 
Digital communications in medicine (DICOM) is an information standard. Originally created for image transfer, the standard now deals with an large range of medical data. See http://medical.nema.org/ for more info.
 
Digital communications in medicine (DICOM) is an information standard. Originally created for image transfer, the standard now deals with an large range of medical data. See http://medical.nema.org/ for more info.
  
This package provides functions to read and write DICOM files. The functions in the package are intended to have similar usage as
+
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as
 
the dicom functions in the Matlab Image Processing Toolbox. In Octave they are separate: most image package users will not use dicom, and its dependency might be considered troublesome.
 
the dicom functions in the Matlab Image Processing Toolbox. In Octave they are separate: most image package users will not use dicom, and its dependency might be considered troublesome.
  
= Installation =
+
== Platforms ==
  
== package requirements ==
+
{{Warning|The information of this section needs be reviewed (June 2019).}}
 +
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.
 +
*mingw
 +
**Ben Lindner's Octave 3.2.4 and the mingw build environment (gcc 4.4.0): dicom package 0.1.1 does not build against this older version of the Octave API.
 +
**Tatsuro/Nitzan's Octave 3.4.3 and mingw build environment (gcc 4.5.2): gdcm and dicom package build OK. Get segfault in ntdll.dll when one of the dicom*.oct files calls something from a gdcm*.dll.
 +
**mxe-octave: dicom and gdcm distributed as part of the installed package.
 +
*Cygwin: Panic when oct file called (or maybe when oct file uses gdcm dll). Need to try rebaseall
  
The {{Forge|dicom}} package requires the [[http://gdcm.sourceforge.net/wiki/index.php/Main_Page GDCM]] libraries and include files to be installed in order to compile.
+
==Supporting library==
 +
[http://gdcm.sourceforge.net/wiki/index.php/Main_Page GDCM]. You can usually get this via your package manager, e.g. on Ubuntu
  
for fedora: yum install gdcm-devel
+
sudo apt-get install libgdcm2.0
  
for ubuntu: apt install libgdcm-dev
+
Alternatively, build it yourself. Get the source with git.
  
 +
git clone https://git.code.sf.net/p/gdcm/gdcm
  
== octave installation ==
+
cmake and g++ are required. create a gdcmbin directory parallel to the gdcm-2-0 directory. Change to gdcmbin and then run cmake (Linux/cygwin).
  
From octave commmand line:
+
> mkdir gdcmbin
 +
> ls
 +
gdcmbin gdcm-2-0
 +
> cd gdcmbin
 +
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/
  
>> pkg install -forge dicom
+
This creates a Makefile in your gdcmbin directory. You can easily edit cmake options with "make edit_cache", for example to build applications like gdcmdump. "make help" is also very useful.
  
== Using it ==
+
make install
  
Load it before any usage:
+
On my system, I also had to add this to my ~/.bashrc.
  
  >> pkg load dicom
+
  export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
  
 +
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]
  
=Features=
+
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0
The following functions are available:
+
mingw32-make all
 +
 
 +
On Cygwin gdcm 2.0.18 (and maybe some other versions) may have a problem with newer cmake. This kludge persuades cmake to define WIN32.
 +
 
 +
cmake -DGDCM_BUILD_SHARED_LIBS=ON -DCMAKE_CXX_COMPILER=g++.exe -DCMAKE_LEGACY_CYGWIN_WIN32=1 ../gdcm-2.0.18/
 +
 
 +
==Features==
 +
All of these still need work, but they exist, and are usable to some extent.
 
*dicomdict (load different dict - file follows same format as Matlab's)
 
*dicomdict (load different dict - file follows same format as Matlab's)
*dicominfo (load metadata into octave struct)
+
*dicominfo (load metadata into octave struct. possible bug in SQ loading)
*dicomdisp (Display the structure of a dicom file)
 
 
*dicomlookup (keyword <-> tag)
 
*dicomlookup (keyword <-> tag)
 
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)
 
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)
Line 41: Line 60:
 
*dicomuid (generate a DICOM unique id)
 
*dicomuid (generate a DICOM unique id)
 
*isdicom (verify if a file is a DICOM formatted file)
 
*isdicom (verify if a file is a DICOM formatted file)
*dicomanon(anonomize a file)
 
*dicomfind(find an attribute in a file or dicom struct)
 
*dicomupdate(Update an attribute value in a dicom struct)
 
  
 +
==Todo==
 +
 +
*dicomanon
 +
 +
==Questions==
 +
I don't have a Matlab license available. I would like to make this package compatible with the dicom functions in Matlab's image processing toolbox, as far as possible.
 +
 +
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?
 +
**matlab reads the data from the dicom file as if it's a raw block of numbers (and then converts if necessary). We think that current Octave/dicom behaviour is compatible with matlab.
 +
*I would like people to try m-files that worked with Matlab to let me know of problems.
 +
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.
 +
**More than one sample per pixel
 +
**Colour
 +
**Float types
 +
*DA (date) VR: does Matlab turn them into a string?
 +
*if the user supplies metadata (eg HighBit?, BitsStored?) that describe the type of the pixels and this is not in agreement with the type of the image matrix supplied, does Matlab
 +
**silently convert the image pixel type to match the metadata?
 +
**silently convert the metadata to match the pixel type?
 +
**error and do nothing?
 +
 +
== Answered ==
 +
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence.Item_1.DoseUnits(as Matlab)
 +
*What does dicominfo do when a tag is not in its dictionary? Answer: assign to a field like Private_3243_0010 (as Matlab)
  
= See also =
+
== See also ==
 
* {{Forge|dicom}} at [[Octave Forge]].
 
* {{Forge|dicom}} at [[Octave Forge]].
 
* [https://sourceforge.net/projects/gdcm/ Grassroots DICOM].
 
* [https://sourceforge.net/projects/gdcm/ Grassroots DICOM].
  
[[Category:Octave Forge]][[Category:Packages]]
+
[[Category:Octave Forge]]

Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Template used on this page: