This README file contains LICENSING and usage information for the dcm2trip conversion tool, part of the RobuR Toolkit project. Please, read the licensing agreement carefully: by obtaining/installing a copy of the above mentioned software, you accept the terms of the agreement. ### USAGE ############################################################## dcm2trip executable works on Intel systems under the Linux operating system. Usage: dcm2trip DICOM_RT_STRUCTURE_FILE DICOM_CT_IMAGES_DIRECTORY dcm2trip takes 2 parameters: the RTStructure file and a directory containing all and only the DICOM encoded slices of a CT set. For dcm2trip to function with any DICOM CT dataset the DICOM Toolkit by OFFIS e.V. must be installed on the system (see section on "input data"). As output dcm2trip produces 3 files called cube.hed (CT header), cube.ctx (CT data) and cube.vdx (contours). The vdx file must be manually edited before usage (see section on "output data"). ### INPUT DATA ######################################################### Internally dcm2trip uses the little-endian implicit-VR transfer syntax as defined by DICOM standard and works on "raw" dicom streams (without preamble nor meta-header). To convert files using other formats the DICOM Toolkit by OFFIS e.V. must be installed (the executables, not the library). It can be downloaded from "http://dicom.offis.de/dcmtk.php.en". ### CONVERSIONS ######################################################## dcm2trip will perform conversions automatically if the DICOM Toolkit is available. If a user wishes to convert files manually, the command to use is: $ dcmconv +ti -e -F original_file_name new_file_name ### OUTPUT DATA ######################################################## The vdx files produced by dcm2trip usually report incorrect information about the "type" of a contour (volume of interest), since this information cannot be obtained from the DICOM data. This may interfere with TRiP's functioning. The vdx files must be edited manually with a text editor. Lines beginning with the keyword "voi" indicate VOIs. dcm2trip assigns "type 1" to all VOIs. Instead VOI types should be: 1 for the target 2 for the OARs 10 for the external contour ### KNOWN ISSUES ####################################################### Many! The current version of this program is still based on demonstrative code that was not meant for release. It has been released in advance in the hope that it can be of help for researchers in the particle therapy field. If a dataset cannot be processed correctly it is most likely due to a bug: please wait for the official release. ROIs that have more than one polygon per slice are treated incorrectly. A workaround is being introduced for the upcoming official release. For the time being please, split such entities into separate ROIs. It is possible to contact the author to suggest "test datasets". Please send an email to Filippo.Ammazzalorso@med.uni-marburg.de (NOTE: Write before withOUT attachments and you'll get an ftp address to upload your DICOM data). ### LICENSING ########################################################## The RobuR Toolkit Development Group Binary Code License Agreement This license agreement applies to the RobuR Toolkit libraries and the derived tools distributed in binary form, unless otherwise specified. Copyright (c) 2008-2010, the RobuR Toolkit Development Group All rights reserved. Use in binary form, without modification, is permitted provided that the following conditions are met: 1. The software was obtained though a licensed channel, along with this license agreement in its full form. 2. All published materials making use of this software must display an acknowledgement explicitely mentioning the "RobuR Toolkit" and/or the "Marburg Particle Therapy Center". 3. Neither the name of the RobuR Toolkit Development Group nor the names of its members or their affiliations may be used to endorse or promote products making use this software without specific prior written permission. 4. Where interfaces to third-part applications/data formats are provided, it is responsability of the user to use them in compliance to the licensing terms chosen by the respective copyright holders. Redistribution and modification are NOT permitted. THIS SOFTWARE IS PROVIDED BY THE ROBUR TOOLKIT DEVELOPMENT GROUP ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ROBUR TOOLKIT DEVELOPMENT GROUP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.