https://wiki.octave.org/wiki/api.php?action=feedcontributions&user=Andybuckle&feedformat=atomOctave - User contributions [en]2019-11-18T18:39:25ZUser contributionsMediaWiki 1.33.0https://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=422Dicom package2012-01-03T15:57:22Z<p>Andybuckle: /* Platforms */</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Contributors: Judd Storrs, Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*Cygwin: Panic when oct file called (or maybe when oct file uses gdcm dll). Need to try rebaseall<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
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.<br />
<br />
cmake -DGDCM_BUILD_SHARED_LIBS=ON -DCMAKE_CXX_COMPILER=g++.exe -DCMAKE_LEGACY_CYGWIN_WIN32=1 ../gdcm-2.0.18/<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
<br />
== Answered ==<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence.Item_1.DoseUnits(as Matlab)<br />
*What does dicominfo do when a tag is not in its dictionary? Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=421Dicom package2012-01-03T15:56:35Z<p>Andybuckle: /* Platforms */ cygwin status update</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Contributors: Judd Storrs, Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*Panic when oct file called (or maybe when oct file uses gdcm dll). Need to try rebaseall<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
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.<br />
<br />
cmake -DGDCM_BUILD_SHARED_LIBS=ON -DCMAKE_CXX_COMPILER=g++.exe -DCMAKE_LEGACY_CYGWIN_WIN32=1 ../gdcm-2.0.18/<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
<br />
== Answered ==<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence.Item_1.DoseUnits(as Matlab)<br />
*What does dicominfo do when a tag is not in its dictionary? Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=420Dicom package2012-01-03T13:55:22Z<p>Andybuckle: /* Supporting library */ cygwin cmake define WIN32</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Contributors: Judd Storrs, Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*cygwin: gdcm 2.0.18-19 does not build. link error in gdcmMSFF.<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
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.<br />
<br />
cmake -DGDCM_BUILD_SHARED_LIBS=ON -DCMAKE_CXX_COMPILER=g++.exe -DCMAKE_LEGACY_CYGWIN_WIN32=1 ../gdcm-2.0.18/<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
<br />
== Answered ==<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence.Item_1.DoseUnits(as Matlab)<br />
*What does dicominfo do when a tag is not in its dictionary? Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=418Dicom package2012-01-02T16:03:01Z<p>Andybuckle: tidied questions section a bit</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Contributors: Judd Storrs, Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*cygwin: gdcm 2.0.18-19 does not build. link error in gdcmMSFF.<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
<br />
== Answered ==<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence.Item_1.DoseUnits(as Matlab)<br />
*What does dicominfo do when a tag is not in its dictionary? Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=417Dicom package2012-01-02T15:54:58Z<p>Andybuckle: added historic contributor</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Contributors: Judd Storrs, Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*cygwin: gdcm 2.0.18-19 does not build. link error in gdcmMSFF.<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary. Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?(as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=416Dicom package2012-01-02T15:52:36Z<p>Andybuckle: progress getting it working on various platforms</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
== Platforms ==<br />
*Linux. Tested on OpenSuSE 11.4 and Ubuntu. No known issues. GDCM is required: see below.<br />
*mingw <br />
**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.<br />
**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.<br />
*cygwin: gdcm 2.0.18-19 does not build. link error in gdcmMSFF.<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary. Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?(as Matlab)<br />
<br />
== See also ==<br />
* {{Forge|dicom}} at [[Octave Forge]].<br />
* [http://sourceforge.net/projects/gdcm/ Grassroots DICOM].<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=376Dicom package2011-12-21T08:25:59Z<p>Andybuckle: link to auto-docs</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
Auto-generated docs from the current package: {{Forge|dicom}}<br />
<br />
== What is the aim of this package? ==<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
==Supporting library==<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
==Features==<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
==Todo==<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
==Questions==<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary. Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?(as Matlab)<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=374Dicom package2011-12-20T23:59:47Z<p>Andybuckle: merged recent changes</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
=== What is the aim of this package? ===<br />
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.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
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.<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary. Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?(as Matlab)<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=373Dicom package2011-12-20T23:55:49Z<p>Andybuckle: intro to dicom</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
Digital communications in medicine (DICOM) is an information standard. This package deals with loading DICOM files. Originally created for image transfer, the standard now deals with an large range of medical data. In Matlab the functions are in the image package. In Octave they are separate: most image package users will not use dicom, and its dependency might be considered troublesome.<br />
<br />
=== What is the aim of this package? ===<br />
DICOM ('Digital Imaging and Communication in Medicine') is a standard for transfering and storing medical data. See http://medical.nema.org/ for more info.<br />
<br />
This package provides functions to read and (eventually) write DICOM files. The functions in the package are intended to have similar usage as<br />
the dicom functions in the Matlab Image Processing Toolbox.<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager, e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. possible bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
*isdicom<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**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. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary. Answer: assign to a field like Private_3243_0010 (as Matlab)<br />
*dicominfo: Items in sequences are not necessarily the same, so are stored as nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?(as Matlab)<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=368Dicom package2011-12-20T21:12:17Z<p>Andybuckle: /* Todo */</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager,e e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. nasty bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
*dicomwrite<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**matlab reads the data from the dicom file as if it's a raw block of numbers (and then converts if necessary). Therefore, current Octave/dicom behaviour is compatible with matlab. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary: skip it or give error? I was wondering about turning the tag into a variable name, something like Tag_3243_0010. (Matlab 6.5 (2002): Private__3243_0010)<br />
*dicominfo: Items in sequences are not necessarily the same, so cannot be stored in arrays of structs. (Matlab 6.5 (2002): makes nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?)<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=367Dicom package2011-12-20T21:11:47Z<p>Andybuckle: /* Features */ remove dicomwrite</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager,e e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. nasty bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**matlab reads the data from the dicom file as if it's a raw block of numbers (and then converts if necessary). Therefore, current Octave/dicom behaviour is compatible with matlab. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary: skip it or give error? I was wondering about turning the tag into a variable name, something like Tag_3243_0010. (Matlab 6.5 (2002): Private__3243_0010)<br />
*dicominfo: Items in sequences are not necessarily the same, so cannot be stored in arrays of structs. (Matlab 6.5 (2002): makes nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?)<br />
<br />
[[Category:OctaveForge]]<br />
[[Category:Packages]]</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Code&diff=184Code2011-11-30T20:24:42Z<p>Andybuckle: /* Digital communications in medicine (DICOM) */ remove stuff that has been moved to a separate page</p>
<hr />
<div>==Chaos and fractal contributions and toolboxes==<br />
*Francesco Potortì's fractal programs (Octave, GPL): http://fly.cnuce.cnr.it/software/#fractals<br />
<br />
==Econometrics==<br />
*Michael Creel's Econometrics notes and octave files: http://pareto.uab.es/mcreel/Econometrics/ (try the Econometrics/MyOctaveFiles directory too)<br />
* Ludwig Kanzler's Econometric software (much of it adapted to Octave):<br />
**http://www2.gol.com/users/kanzler/index.htm#L.%20Kanzler:%20Software<br />
**Licence: "All rights reserved", Unfree for distributing modified versions<br />
<br />
==Communications Toolbox==<br />
OctaveForge now contains a fairly complete implementation of a Matlab R13 compatible communications toolbox http://octave.sourceforge.net/communications/index.html. This includes<br />
*Random signal creation/analysis<br />
*Source coding (Quantization, Compand)<br />
*Block coding (BCH, Reed-Solomon)<br />
*Modulations (QASK, PSK, etc)<br />
*Galois fields of even order [i.e. GF(2^m) ]<br />
<br />
With a recent version of the OctaveForge installed (version 20030602 or later), online help is available with the command<br />
octave:1> comms info<br />
<br />
There are still functions missing or with limitations, and the documentation is not complete. You are therefore welcome to send patches.<br />
<br />
===Various Communications-Related Octave Code===<br />
*Simulate multipath fading channels: http://zeidler.ucsd.edu/~sct/code/20060112_multipath/<br />
*Signal processing package in [http://octave.sourceforge.net/signal/index.html OctaveForge]<br />
*Wavelets: try Wavelab developed by David Donoho et al. at http://www-stat.stanford.edu/~wavelab/. For more information, see [[Wavelab on Octave]].<br />
* Peter Kovesi's functions for computer vision and image processing: http://www.csse.uwa.edu.au/~pk/Research/MatlabFns/<br />
<br />
===Data Formats===<br />
A collection of various signal data formats can be found [http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/eeg/ here]. Many formats are supported by the [http://biosig.sf.net/ BIOSIG]-toolbox for Octave and Matlab.<br />
<br />
===Speech and Signal Processing Links===<br />
The following packages contain routines that can be made to work with Octave. Sometimes a little effort is required.<br />
<br />
*OctaveForge contains a sizable collection of signal and image processing routines<br />
*Alois Schloegl's Time series analysis toolbox is also available at OctaveForge<br />
*Mike Brookes' Voice Box (http://www.ee.ic.ac.uk/hp/staff/dmb/voicebox/voicebox.html)<br />
*University of Sheffield's Matlab Auditory and Speech Demos (http://www.dcs.shef.ac.uk/~martin/MAD/docs/mad.htm)<br />
*Malcolm Slaney's Auditory Toolbox (http://rvl4.ecn.purdue.edu/~malcolm/interval/1998-010/)<br />
*Philip Loizou's COLEA speech analysis toolbox (http://www.utdallas.edu/~loizou/speech/colea.htm)<br />
*Levant Arslans's Speech Processing Toolbox (http://cslr.colorado.edu/software/rspl.html)<br />
*John Hansen's Additive noise sources (http://cslr.colorado.edu/software/rspl.html)<br />
*Dennis Brown's SPCtools (ftp://svr-ftp.eng.cam.ac.uk/pub/comp.speech/tools/spctools) has code for AR and ARMA modelling, particularly in the spcline subdirectory (Note that the version at mathworks is slightly older).<br />
*Steve Niu's AUDI (ftp://ftp.mathworks.com/pub/contrib/v4/systemid/audidemo.tar) and Arthur Jutan's recursivels (ftp://ftp.mathworks.com/pub/contrib/v4/control/recursivels.tar) for ARMA modelling. AUDI worked well enough for me with a bit of fiddling. Haven't tried recursivels.<br />
*Peter Assmann's Track Draw (http://www.utdallas.edu/~assmann/TRACKDRAW/trackdraw.html) has code for a klatt synthesizer<br />
*Time-Frequency Tool box (http://www-isis.enst.fr/Applications/tftb/iutsn.univ-nantes.fr/auger/tftb.html) from CNRS & Rice has code for AM/FM modulation amongst other cool stuff<br />
*Christophe Couvreur's octave (ftp://ftp.mathworks.com/pub/contrib/v5/signal/octave.tar) has filterbank stuff. Of course the plotting doesn't work, but with a bit of fiddling, you can get, 1/3 octave and 1 octave filter banks to work.<br />
*Mathworks signal processing contributions directories for Matlab 4 (http://www.mathworks.com/support/ftp/signalssv4.shtml) and Matlab 5 (http://www.mathworks.com/support/ftp/signalssv5.shtml)<br />
*University of Vienna's Linear Time-Frequency Toolbox (http://www.univie.ac.at/nuhag-php/ltfat)<br />
<br />
The following used to be available:<br />
<br />
*Kuo, et. al.'s Speech Signal Processing and Recognition tools (SSPR). A number of the other tools are archived at the same site (http://www.eeng.dcu.ie/~speech5/matspeech.html).<br />
<br />
Other Software:<br />
<br />
*ESPS has been open sourced (BSD license) and is available at http://www.speech.kth.se/software/. Finally we will have a decent pitch tracker!<br />
<br />
==Digital communications in medicine (DICOM)==<br />
There is a DICOM package hosted on sourceforge: [[dicom | more information]].<br />
<br />
== Fixed point toolbox ==<br />
(initial announcement can be found [http://www.octave.org/octave-lists/archive/help-octave.2004/msg01274.html here], with the corresponding thread)<br />
<br />
When implementing algorithms in hardware, it is common to reduce the accuracy of the representation of numbers to a smaller number of bits. This allows much lower complexity in the hardware, at the cost of accuracy and potential overflow problems. Such representations are known as fixed point.<br />
<br />
OctaveForge now contains [http://octave.sourceforge.net/Fixedpoint/index.html a toolbox] to perform such fixed point calculations. This toolbox supplies a fixed point type that allows Octave to model the effects of such a reduction in accuracy of the representation of numbers. The major advantage of this toolbox is that with correctly written Octave scripts, the same code can be used to test both fixed and floating point representations of numbers.<br />
<br />
What it does is create several new user types for fixed point scalar, complex scalars, matrices and complex matrices, and the corresponding operators on these types. As this code was first written against 2.1.50 there is no capabilities at this time for NDArray operations with this code, however I'm not sure this is a problem.<br />
<br />
A typical use of the toolbox might be something like<br />
<br />
n = 2;<br />
a = rand (n, n);<br />
b = rand (n, n);<br />
<br />
## Create fixed-point version with 1 bit before decimal and 5 after.<br />
af = fixed (1, 5, a);<br />
bf = fixed (1, 5, b);<br />
<br />
c = myfunc (a, b);<br />
cf = myfunc (af, bf);<br />
<br />
function y = myfunc (a, b)<br />
y = a * b;<br />
endfunction<br />
<br />
where as you can see the underlying function myfunc is unchanged, while it is called with either floating or fixed point types. The case above is for fixed-point values with 1-bit before the decimal point and 5 after, and for me gave a result of<br />
<br />
octave:8> c<br />
c =<br />
<br />
0.98105 0.94436<br />
0.82622 0.30831<br />
<br />
octave:9> cf<br />
cf =<br />
<br />
0.93750 0.90625<br />
0.78125 0.25000<br />
<br />
which clearly shows the loss of precision of a fixed-point algorithm with only 6-bits of precision in a matrix multiply. One gotcha in this toolbox is the use of the concatenation operator "[ ]" which will implicitly reconvert fixed-point values back to floating-point, with Octave 2.1.57 or earlier. This is due to an internal limitation of octave that was removed in Octave 2.1.58. So for the best experience it is suggested you use this toolbox with octave 2.1.58 or later.<br />
<br />
This package is only available with recent versions of OctaveForge (20040707 or later). With the package installed online help is available with the command<br />
octave:1> fixedpoint info<br />
<br />
As this package is relatively new, all feedback on its use would be most welcome.<br />
<br />
Matlab also recently introduced a [http://www.mathworks.com/products/fixed Fixed Point Toolbox]. The Octave toolbox has been written independently of the Matlab toolbox and doesn't follow the same syntax. This might change in the future, if the author (DavidBateman) can be bothered to put the effort into making the required changes. Mathworks [http://www.mathworks.com/access/helpdesk/help/pdf_doc/fixedpoint/FPTUG.pdf documentation] for their fixed point toolbox also includes a generic discussion of fixed point numbers that might be a useful addition to the documentation supplied with Octave itself. Another short introduction to fixed point arithmetics is [http://home.earthlink.net/~yatescr/fp.pdf this].<br />
<br />
==Adding a quadl like integrator to octave==<br />
<br />
quadl is an adaptive quadrature function available in MATLAB (from version 6 I think). It is very fast and accurate and surprisingly it's a small m-file. The algorithm is based on works by Prof. Walter Gander.<br />
<br />
Prof. Gander has two m files in his web page http://www.inf.ethz.ch/personal/gander/ which implement his algorithm along with a paper describing the algorithm.<br />
<br />
I have not delved deeply into the subject, but the adaptlobe.m function looks equivalent to quadl. Compatibility with MATLAB could be achieved by writing a small quadl wrapper function which simply calles adaptlobe, or by changing adabtlobe's name to quadl.<br />
<br />
I have contacted Prof. Gander to allow for distribution of his m-files in octave-forge.<br />
<br />
quadl, from the above source is now incorporated into octave-forge-2004-02-12. <br />
<br />
==Model transformation tools==<br />
http://mtt.sourceforge.net<br />
<br />
A set of tools for modelling dynamic physical systems using the bond-graph methodology and transforming these models into representations suitable for analysis, control and simulation. These tools use, and generate m files for, GNU Octave.<br />
<br />
==Optimisation==<br />
There is a variety of code in the octave-forge optimization package http://octave.sourceforge.net/optim/index.html<br />
<br />
==Parallelism ==<br />
Operating Octave remotely and in parallel<br />
*distributed linear algebra from octave command line via [http://icl.cs.utk.edu/netsolve/index.html GridSolve]<br />
*OctaveForge has a parallel octave, allowing remote commands and data transfer<br />
*OctaveServer allows net connections to Octave<br />
*MPI toolbox for Octave http://atc.ugr.es/javier-bin/mpitb (This is included in a live CD ParallelKnoppix http://pareto.uab.es/mcreel/ParallelKnoppix/ which you can use without installation or configuration)<br />
<br />
==Statistics ==<br />
===Statistics Functions===<br />
<br />
*[ http://www.maths.lth.se/matstat/stixbox/ Stixbox] supports Octave. It has a variety of functions not available in octave/octave-forge such as bootstrap and jackknife estimators and a variety of qq plots. GPL.<br />
<br />
*[http://www.statsci.org/matlab/statbox.html Statbox] has some regression functions which are not in Octave. Don't know license or Octave compatibility.<br />
<br />
*[http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/NaN/ NaN-toolbox] A statistic-toolbox for Octave and Matlab®. It handles data with and without MISSING VALUES. More background information is provided in [http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/NaN/README.TXT README]<br />
<br />
*[http://www.cepremap.cnrs.fr/dynare/ Dynare] is a pre-processor and a collection of MATLAB or SCILAB routines which solve non--linear models with forward looking variables. Cannot find any insight about the license terms, but some code is derived work from GPL code, e.g., [https://www.cepremap.cnrs.fr/websvn/filedetails.php?repname=repos+1&path=%2Fdynare_v3%2Fmatlab%2Fkernel_density_estimate.m&rev=6&sc=1]. The code is adapted from Anders Holtsberg's matlab toolbox (stixbox).<br />
<br />
===Multivariate kernel density estimation===<br />
<br />
*[http://www.ics.uci.edu/~ihler/code/kde.shtml Kernel Density Estimation Toolbox] LGPL<br />
<br />
*[http://www.maths.lth.se/matstat/wafo/documentation/wafodoc/wafo/kdetools/index.html wafo/kdetools] GPL<br />
<br />
*A google search for epanechnikov at the r-project.org site returns several R packages on this subject. They all should be GPL compatible. [http://www.google.com/search?hl=en&lr=&q=Epanechnikov+site%3Ar-project.org&btnG=Search]<br />
<br />
*[http://astrostatistics.psu.edu/statcodes/sc_density.html sc_density]<br />
<br />
*[http://www.cs.waikato.ac.nz/~ml/weka/ Weka] is written in Java, again, don't know how difficult... look for a file called LWL.java<br />
<br />
*[http://ltilib.sourceforge.net/doc/homepage/index.shtml LTI-Lib] is an object oriented library with algorithms and data structures frequently used in image processing and computer vision. LGPL<br />
<br />
==Symbolic==<br />
===Symbolic Manipulation===<br />
Octave is a matrix algebra tool, not a symbolic algebra tool, so it cannot perform symbolic operations, such as finding the derivative of sine(x) with respect to x<br />
<br />
y = derivative('sin(x)','x'); # Not available in Octave<br />
<br />
The below mentioned GiNaC will add symbolic functionality to octave.<br />
<br />
===Octave interfaces to GiNaC===<br />
There are two Octave interfaces to GiNaC[1] available<br />
<br />
*gino -- http://www.sourceforge.net/projects/mtt (download) provides an Octave interface to GiNaC via ginsh <br />
<br />
octave:1> df = g_diff ( "sin(x)" , "x" )<br />
df = cos(x)<br />
octave:2> x = pi; eval ( df );<br />
ans = -1<br />
<br />
*OctaveForge provides direct access to GiNaC in the [http://octave.sourceforge.net/index/navsymbolic.html symbolic package]. Here is a http://wiki.octave.org/wiki.pl?OctaveForgeGNCIntro short tutorial] to get you started.<br />
<br />
===Numerical methods===<br />
In some instances, Octave can give reasonable results using numerical methods<br />
<br />
*Octave supports numerical derivatives: <br />
<br />
t = linspace(0,6,100);<br />
y = sin(t);<br />
dydt = diff(y) ./ diff(t)<br />
*OctaveForge has other numerical derivative functions.<br />
<br />
===Symbolic algebra systems===<br />
Software other than Octave may be more useful for work involving symbolic manipulations<br />
<br />
Free software<br />
*Axiom: http://www.nongnu.org/axiom/<br />
<br />
*GiNaC/ginsh: http://www.ginac.de<br />
<br />
*Maxima: http://maxima.sourceforge.net<br />
<br />
*Yacas: http://yacas.sourceforge.net<br />
<br />
Non-free software<br />
*Maple: http://www.maplesoft.com<br />
<br />
*Reduce: http://www.uni-koeln.de/REDUCE<br />
<br />
Note that most of these systems (and Octave!) may be used from within TeXmacs http://www.texmacs.org<br />
<br />
A list of some other scientific software is available at http://sal.kachinatech.com/</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Dicom_package&diff=183Dicom package2011-11-30T20:21:27Z<p>Andybuckle: move stuff from "code" page</p>
<hr />
<div>At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager,e e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. nasty bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
*dicomwrite (only does some 2D int types, ATM. No metadata control, yet)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**matlab reads the data from the dicom file as if it's a raw block of numbers (and then converts if necessary). Therefore, current Octave/dicom behaviour is compatible with matlab. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary: skip it or give error? I was wondering about turning the tag into a variable name, something like Tag_3243_0010. (Matlab 6.5 (2002): Private__3243_0010)<br />
*dicominfo: Items in sequences are not necessarily the same, so cannot be stored in arrays of structs. (Matlab 6.5 (2002): makes nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?)</div>Andybucklehttps://wiki.octave.org/wiki/index.php?title=Code&diff=182Code2011-11-30T20:17:48Z<p>Andybuckle: /* Digital communications in medicine (DICOM) */ link to new separate page for DICOM. I think it clutters this page up.</p>
<hr />
<div>==Chaos and fractal contributions and toolboxes==<br />
*Francesco Potortì's fractal programs (Octave, GPL): http://fly.cnuce.cnr.it/software/#fractals<br />
<br />
==Econometrics==<br />
*Michael Creel's Econometrics notes and octave files: http://pareto.uab.es/mcreel/Econometrics/ (try the Econometrics/MyOctaveFiles directory too)<br />
* Ludwig Kanzler's Econometric software (much of it adapted to Octave):<br />
**http://www2.gol.com/users/kanzler/index.htm#L.%20Kanzler:%20Software<br />
**Licence: "All rights reserved", Unfree for distributing modified versions<br />
<br />
==Communications Toolbox==<br />
OctaveForge now contains a fairly complete implementation of a Matlab R13 compatible communications toolbox http://octave.sourceforge.net/communications/index.html. This includes<br />
*Random signal creation/analysis<br />
*Source coding (Quantization, Compand)<br />
*Block coding (BCH, Reed-Solomon)<br />
*Modulations (QASK, PSK, etc)<br />
*Galois fields of even order [i.e. GF(2^m) ]<br />
<br />
With a recent version of the OctaveForge installed (version 20030602 or later), online help is available with the command<br />
octave:1> comms info<br />
<br />
There are still functions missing or with limitations, and the documentation is not complete. You are therefore welcome to send patches.<br />
<br />
===Various Communications-Related Octave Code===<br />
*Simulate multipath fading channels: http://zeidler.ucsd.edu/~sct/code/20060112_multipath/<br />
*Signal processing package in [http://octave.sourceforge.net/signal/index.html OctaveForge]<br />
*Wavelets: try Wavelab developed by David Donoho et al. at http://www-stat.stanford.edu/~wavelab/. For more information, see [[Wavelab on Octave]].<br />
* Peter Kovesi's functions for computer vision and image processing: http://www.csse.uwa.edu.au/~pk/Research/MatlabFns/<br />
<br />
===Data Formats===<br />
A collection of various signal data formats can be found [http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/eeg/ here]. Many formats are supported by the [http://biosig.sf.net/ BIOSIG]-toolbox for Octave and Matlab.<br />
<br />
===Speech and Signal Processing Links===<br />
The following packages contain routines that can be made to work with Octave. Sometimes a little effort is required.<br />
<br />
*OctaveForge contains a sizable collection of signal and image processing routines<br />
*Alois Schloegl's Time series analysis toolbox is also available at OctaveForge<br />
*Mike Brookes' Voice Box (http://www.ee.ic.ac.uk/hp/staff/dmb/voicebox/voicebox.html)<br />
*University of Sheffield's Matlab Auditory and Speech Demos (http://www.dcs.shef.ac.uk/~martin/MAD/docs/mad.htm)<br />
*Malcolm Slaney's Auditory Toolbox (http://rvl4.ecn.purdue.edu/~malcolm/interval/1998-010/)<br />
*Philip Loizou's COLEA speech analysis toolbox (http://www.utdallas.edu/~loizou/speech/colea.htm)<br />
*Levant Arslans's Speech Processing Toolbox (http://cslr.colorado.edu/software/rspl.html)<br />
*John Hansen's Additive noise sources (http://cslr.colorado.edu/software/rspl.html)<br />
*Dennis Brown's SPCtools (ftp://svr-ftp.eng.cam.ac.uk/pub/comp.speech/tools/spctools) has code for AR and ARMA modelling, particularly in the spcline subdirectory (Note that the version at mathworks is slightly older).<br />
*Steve Niu's AUDI (ftp://ftp.mathworks.com/pub/contrib/v4/systemid/audidemo.tar) and Arthur Jutan's recursivels (ftp://ftp.mathworks.com/pub/contrib/v4/control/recursivels.tar) for ARMA modelling. AUDI worked well enough for me with a bit of fiddling. Haven't tried recursivels.<br />
*Peter Assmann's Track Draw (http://www.utdallas.edu/~assmann/TRACKDRAW/trackdraw.html) has code for a klatt synthesizer<br />
*Time-Frequency Tool box (http://www-isis.enst.fr/Applications/tftb/iutsn.univ-nantes.fr/auger/tftb.html) from CNRS & Rice has code for AM/FM modulation amongst other cool stuff<br />
*Christophe Couvreur's octave (ftp://ftp.mathworks.com/pub/contrib/v5/signal/octave.tar) has filterbank stuff. Of course the plotting doesn't work, but with a bit of fiddling, you can get, 1/3 octave and 1 octave filter banks to work.<br />
*Mathworks signal processing contributions directories for Matlab 4 (http://www.mathworks.com/support/ftp/signalssv4.shtml) and Matlab 5 (http://www.mathworks.com/support/ftp/signalssv5.shtml)<br />
*University of Vienna's Linear Time-Frequency Toolbox (http://www.univie.ac.at/nuhag-php/ltfat)<br />
<br />
The following used to be available:<br />
<br />
*Kuo, et. al.'s Speech Signal Processing and Recognition tools (SSPR). A number of the other tools are archived at the same site (http://www.eeng.dcu.ie/~speech5/matspeech.html).<br />
<br />
Other Software:<br />
<br />
*ESPS has been open sourced (BSD license) and is available at http://www.speech.kth.se/software/. Finally we will have a decent pitch tracker!<br />
<br />
==Digital communications in medicine (DICOM)==<br />
There is a DICOM package hosted on sourceforge: [[dicom | more information]].<br />
<br />
At an early development stage. [http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/ octave-forge svn]<br />
*Maintainer: Andy Buckle [http://sourceforge.net/sendmessage.php?touser=1760416contact] <br />
*Currently worked on by: Kris Thielemans<br />
<br />
===Supporting library===<br />
[http://sourceforge.net/apps/mediawiki/gdcm/index.php?title=Main_Page GCDM]. You can usually get this via your package manager,e e.g. on Ubuntu<br />
<br />
sudo apt-get install libgdcm2.0<br />
<br />
Alternatively, build it yourself. Get the source with subversion.<br />
<br />
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/branches/gdcm-2-0<br />
<br />
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).<br />
<br />
> mkdir gdcmbin<br />
> ls<br />
gdcmbin gdcm-2-0<br />
> cd gdcmbin<br />
> cmake -DGDCM_BUILD_SHARED_LIBS=ON ../gdcm-2-0/<br />
<br />
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.<br />
<br />
make install<br />
<br />
On my system, I also had to add this to my ~/.bashrc.<br />
<br />
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib<br />
<br />
Mingw32 is similar. Get openSSL: [http://www.slproweb.com/products/Win32OpenSSL.html Win32 Openssl v1.0.0a Light]<br />
<br />
cmake -G "MinGW Makefile" -DGDCM_BUILD_SHARED_LIBS=ON ..\gdcm-2-0<br />
mingw32-make all<br />
<br />
===Features===<br />
All of these still need work, but they exist, and are usable to some extent.<br />
*dicomdict (load different dict - file follows same format as Matlab's)<br />
*dicominfo (load metadata into octave struct. nasty bug in SQ loading)<br />
*dicomlookup (keyword <-> tag)<br />
*dicomread (load pixel data, 2D or 3D int types. Does not yield colormaps, yet.)<br />
*dicomwrite (only does some 2D int types, ATM. No metadata control, yet)<br />
<br />
===Todo===<br />
<br />
*dicomanon<br />
*dicomuid<br />
<br />
===Questions===<br />
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.<br />
<br />
*Octave (and Matlab) stores images (y,x) and DICOM is intrinsically (x,y). Does Matlab transpose images when it loads them?<br />
**matlab reads the data from the dicom file as if it's a raw block of numbers (and then converts if necessary). Therefore, current Octave/dicom behaviour is compatible with matlab. <br />
*I would like people to try m-files that worked with Matlab to let me know of problems.<br />
*(not necessarily) Matlab related: I need examples of odd DICOM files. I have plenty with complex metadata, but I need some with unusual images.<br />
**More than one sample per pixel<br />
**Colour<br />
**Float types <br />
*DA (date) VR: does Matlab turn them into a string?<br />
*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<br />
**silently convert the image pixel type to match the metadata?<br />
**silently convert the metadata to match the pixel type?<br />
**error and do nothing? <br />
*What does dicominfo do when a tag is not in its dictionary: skip it or give error? I was wondering about turning the tag into a variable name, something like Tag_3243_0010. (Matlab 6.5 (2002): Private__3243_0010)<br />
*dicominfo: Items in sequences are not necessarily the same, so cannot be stored in arrays of structs. (Matlab 6.5 (2002): makes nested structs like dcm.RTDoseROISequence?.Item_1.DoseUnits?)<br />
<br />
== Fixed point toolbox ==<br />
(initial announcement can be found [http://www.octave.org/octave-lists/archive/help-octave.2004/msg01274.html here], with the corresponding thread)<br />
<br />
When implementing algorithms in hardware, it is common to reduce the accuracy of the representation of numbers to a smaller number of bits. This allows much lower complexity in the hardware, at the cost of accuracy and potential overflow problems. Such representations are known as fixed point.<br />
<br />
OctaveForge now contains [http://octave.sourceforge.net/Fixedpoint/index.html a toolbox] to perform such fixed point calculations. This toolbox supplies a fixed point type that allows Octave to model the effects of such a reduction in accuracy of the representation of numbers. The major advantage of this toolbox is that with correctly written Octave scripts, the same code can be used to test both fixed and floating point representations of numbers.<br />
<br />
What it does is create several new user types for fixed point scalar, complex scalars, matrices and complex matrices, and the corresponding operators on these types. As this code was first written against 2.1.50 there is no capabilities at this time for NDArray operations with this code, however I'm not sure this is a problem.<br />
<br />
A typical use of the toolbox might be something like<br />
<br />
n = 2;<br />
a = rand (n, n);<br />
b = rand (n, n);<br />
<br />
## Create fixed-point version with 1 bit before decimal and 5 after.<br />
af = fixed (1, 5, a);<br />
bf = fixed (1, 5, b);<br />
<br />
c = myfunc (a, b);<br />
cf = myfunc (af, bf);<br />
<br />
function y = myfunc (a, b)<br />
y = a * b;<br />
endfunction<br />
<br />
where as you can see the underlying function myfunc is unchanged, while it is called with either floating or fixed point types. The case above is for fixed-point values with 1-bit before the decimal point and 5 after, and for me gave a result of<br />
<br />
octave:8> c<br />
c =<br />
<br />
0.98105 0.94436<br />
0.82622 0.30831<br />
<br />
octave:9> cf<br />
cf =<br />
<br />
0.93750 0.90625<br />
0.78125 0.25000<br />
<br />
which clearly shows the loss of precision of a fixed-point algorithm with only 6-bits of precision in a matrix multiply. One gotcha in this toolbox is the use of the concatenation operator "[ ]" which will implicitly reconvert fixed-point values back to floating-point, with Octave 2.1.57 or earlier. This is due to an internal limitation of octave that was removed in Octave 2.1.58. So for the best experience it is suggested you use this toolbox with octave 2.1.58 or later.<br />
<br />
This package is only available with recent versions of OctaveForge (20040707 or later). With the package installed online help is available with the command<br />
octave:1> fixedpoint info<br />
<br />
As this package is relatively new, all feedback on its use would be most welcome.<br />
<br />
Matlab also recently introduced a [http://www.mathworks.com/products/fixed Fixed Point Toolbox]. The Octave toolbox has been written independently of the Matlab toolbox and doesn't follow the same syntax. This might change in the future, if the author (DavidBateman) can be bothered to put the effort into making the required changes. Mathworks [http://www.mathworks.com/access/helpdesk/help/pdf_doc/fixedpoint/FPTUG.pdf documentation] for their fixed point toolbox also includes a generic discussion of fixed point numbers that might be a useful addition to the documentation supplied with Octave itself. Another short introduction to fixed point arithmetics is [http://home.earthlink.net/~yatescr/fp.pdf this].<br />
<br />
==Adding a quadl like integrator to octave==<br />
<br />
quadl is an adaptive quadrature function available in MATLAB (from version 6 I think). It is very fast and accurate and surprisingly it's a small m-file. The algorithm is based on works by Prof. Walter Gander.<br />
<br />
Prof. Gander has two m files in his web page http://www.inf.ethz.ch/personal/gander/ which implement his algorithm along with a paper describing the algorithm.<br />
<br />
I have not delved deeply into the subject, but the adaptlobe.m function looks equivalent to quadl. Compatibility with MATLAB could be achieved by writing a small quadl wrapper function which simply calles adaptlobe, or by changing adabtlobe's name to quadl.<br />
<br />
I have contacted Prof. Gander to allow for distribution of his m-files in octave-forge.<br />
<br />
quadl, from the above source is now incorporated into octave-forge-2004-02-12. <br />
<br />
==Model transformation tools==<br />
http://mtt.sourceforge.net<br />
<br />
A set of tools for modelling dynamic physical systems using the bond-graph methodology and transforming these models into representations suitable for analysis, control and simulation. These tools use, and generate m files for, GNU Octave.<br />
<br />
==Optimisation==<br />
There is a variety of code in the octave-forge optimization package http://octave.sourceforge.net/optim/index.html<br />
<br />
==Parallelism ==<br />
Operating Octave remotely and in parallel<br />
*distributed linear algebra from octave command line via [http://icl.cs.utk.edu/netsolve/index.html GridSolve]<br />
*OctaveForge has a parallel octave, allowing remote commands and data transfer<br />
*OctaveServer allows net connections to Octave<br />
*MPI toolbox for Octave http://atc.ugr.es/javier-bin/mpitb (This is included in a live CD ParallelKnoppix http://pareto.uab.es/mcreel/ParallelKnoppix/ which you can use without installation or configuration)<br />
<br />
==Statistics ==<br />
===Statistics Functions===<br />
<br />
*[ http://www.maths.lth.se/matstat/stixbox/ Stixbox] supports Octave. It has a variety of functions not available in octave/octave-forge such as bootstrap and jackknife estimators and a variety of qq plots. GPL.<br />
<br />
*[http://www.statsci.org/matlab/statbox.html Statbox] has some regression functions which are not in Octave. Don't know license or Octave compatibility.<br />
<br />
*[http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/NaN/ NaN-toolbox] A statistic-toolbox for Octave and Matlab®. It handles data with and without MISSING VALUES. More background information is provided in [http://www.dpmi.tu-graz.ac.at/~schloegl/matlab/NaN/README.TXT README]<br />
<br />
*[http://www.cepremap.cnrs.fr/dynare/ Dynare] is a pre-processor and a collection of MATLAB or SCILAB routines which solve non--linear models with forward looking variables. Cannot find any insight about the license terms, but some code is derived work from GPL code, e.g., [https://www.cepremap.cnrs.fr/websvn/filedetails.php?repname=repos+1&path=%2Fdynare_v3%2Fmatlab%2Fkernel_density_estimate.m&rev=6&sc=1]. The code is adapted from Anders Holtsberg's matlab toolbox (stixbox).<br />
<br />
===Multivariate kernel density estimation===<br />
<br />
*[http://www.ics.uci.edu/~ihler/code/kde.shtml Kernel Density Estimation Toolbox] LGPL<br />
<br />
*[http://www.maths.lth.se/matstat/wafo/documentation/wafodoc/wafo/kdetools/index.html wafo/kdetools] GPL<br />
<br />
*A google search for epanechnikov at the r-project.org site returns several R packages on this subject. They all should be GPL compatible. [http://www.google.com/search?hl=en&lr=&q=Epanechnikov+site%3Ar-project.org&btnG=Search]<br />
<br />
*[http://astrostatistics.psu.edu/statcodes/sc_density.html sc_density]<br />
<br />
*[http://www.cs.waikato.ac.nz/~ml/weka/ Weka] is written in Java, again, don't know how difficult... look for a file called LWL.java<br />
<br />
*[http://ltilib.sourceforge.net/doc/homepage/index.shtml LTI-Lib] is an object oriented library with algorithms and data structures frequently used in image processing and computer vision. LGPL<br />
<br />
==Symbolic==<br />
===Symbolic Manipulation===<br />
Octave is a matrix algebra tool, not a symbolic algebra tool, so it cannot perform symbolic operations, such as finding the derivative of sine(x) with respect to x<br />
<br />
y = derivative('sin(x)','x'); # Not available in Octave<br />
<br />
The below mentioned GiNaC will add symbolic functionality to octave.<br />
<br />
===Octave interfaces to GiNaC===<br />
There are two Octave interfaces to GiNaC[1] available<br />
<br />
*gino -- http://www.sourceforge.net/projects/mtt (download) provides an Octave interface to GiNaC via ginsh <br />
<br />
octave:1> df = g_diff ( "sin(x)" , "x" )<br />
df = cos(x)<br />
octave:2> x = pi; eval ( df );<br />
ans = -1<br />
<br />
*OctaveForge provides direct access to GiNaC in the [http://octave.sourceforge.net/index/navsymbolic.html symbolic package]. Here is a http://wiki.octave.org/wiki.pl?OctaveForgeGNCIntro short tutorial] to get you started.<br />
<br />
===Numerical methods===<br />
In some instances, Octave can give reasonable results using numerical methods<br />
<br />
*Octave supports numerical derivatives: <br />
<br />
t = linspace(0,6,100);<br />
y = sin(t);<br />
dydt = diff(y) ./ diff(t)<br />
*OctaveForge has other numerical derivative functions.<br />
<br />
===Symbolic algebra systems===<br />
Software other than Octave may be more useful for work involving symbolic manipulations<br />
<br />
Free software<br />
*Axiom: http://www.nongnu.org/axiom/<br />
<br />
*GiNaC/ginsh: http://www.ginac.de<br />
<br />
*Maxima: http://maxima.sourceforge.net<br />
<br />
*Yacas: http://yacas.sourceforge.net<br />
<br />
Non-free software<br />
*Maple: http://www.maplesoft.com<br />
<br />
*Reduce: http://www.uni-koeln.de/REDUCE<br />
<br />
Note that most of these systems (and Octave!) may be used from within TeXmacs http://www.texmacs.org<br />
<br />
A list of some other scientific software is available at http://sal.kachinatech.com/</div>Andybuckle