similar to: oro.dicom released (replaces DICOM)

Hello, I have the following problem. After a PACS upgrade in our hospital, the dynamic 3D images acquired after contrast media injection with a 3T Philips MRI are all saved in a single 4D file instead of a series of 2D images containing multiple 3D images over time. I used to convert this series of 2D dicom images in the format nfti with oro.dicom. However, I am no longer able to make oro.dicom

The first release of oro.nifti (v0.1.3) is a bundle of functions and capabilities from the dcemriS4 package. * This package is able to read/write both NIfTI and Analyze data formats for medical imaging. * S4 classes are available and numerous methods exist to visualize and interact with these data formats. * NIfTI extensions are allowed both as input and output. * With the XML package installed

The first release of oro.nifti (v0.1.3) is a bundle of functions and capabilities from the dcemriS4 package. * This package is able to read/write both NIfTI and Analyze data formats for medical imaging. * S4 classes are available and numerous methods exist to visualize and interact with these data formats. * NIfTI extensions are allowed both as input and output. * With the XML package installed

CRAN (and crantastic) updates this week New packages ------------ * apcluster (1.0.1) Ulrich Bodenhofer http://crantastic.org/packages/apcluster The apcluster package implements Frey's and Dueck's Affinity Propagation clustering in R. The algorithms are analogous to the Matlab code published by Frey and Dueck. * BioPhysConnectoR (1.6-1) Franziska Hoffgaard

The package DICOM is a first attempt at a set of routines to import and summarize medical imaging data that conforms to the DICOM standard. This is now the industry standard for a wide variety of medical imaging equipment (e.g., PET, MRI, CT, etc.). Please see http://medical.nema.org for more information about the DICOM standard. A simple list structure holds the separate header and image

The package DICOM is a first attempt at a set of routines to import and summarize medical imaging data that conforms to the DICOM standard. This is now the industry standard for a wide variety of medical imaging equipment (e.g., PET, MRI, CT, etc.). Please see http://medical.nema.org for more information about the DICOM standard. A simple list structure holds the separate header and image

I have received the following error for my package oro.nifti under "CRAN checks" for r-devel-linux-ix86; i.e., http://www.r-project.org/nosvn/R.check/r-devel-linux-ix86/oro.nifti-00check.html - using R version 2.12.0 Under development (unstable) (2010-06-12 r52259) - using platform: i686-pc-linux-gnu (32-bit) - using session charset: UTF-8 - checking for file

dcemri 0.10 has been released on CRAN "dcemri" is (to the best of my knowledge) the first public-domain software package for the quantitative analysis of dynamic contrast-enhanced MRI (DCE-MRI) and diffusion-weighted MRI (DW-MRI or DWI). Data import and export is availble for ANALYZE or NIfTI data formats (sorry, no DICOM). Images are stored in neurological format regardless of the

dcemri 0.10 has been released on CRAN "dcemri" is (to the best of my knowledge) the first public-domain software package for the quantitative analysis of dynamic contrast-enhanced MRI (DCE-MRI) and diffusion-weighted MRI (DW-MRI or DWI). Data import and export is availble for ANALYZE or NIfTI data formats (sorry, no DICOM). Images are stored in neurological format regardless of the

Hello there! I hope there is someone out there who is using the DICOM package. When Im trying to read my a DICOM file (MRI-data) I always get this error: > dicom.info("~/myfile") Error in readBin(fid, integer(), length, size = 1) : invalid value of 'n' The DICOM files that come with the DICOM package work just fine. I already tried both endian options. I can view my

Dear all, The "tractor.base" package has recently been added to CRAN. This package provides functions to read, write, visualise and manipulate magnetic resonance images. The standard Analyze, NIfTI and DICOM file formats are supported (read-only for DICOM), and all metadata is stored with the image data internally. The code can be used to visualise image slices or maximum intensity

Dear all, The "tractor.base" package has recently been added to CRAN. This package provides functions to read, write, visualise and manipulate magnetic resonance images. The standard Analyze, NIfTI and DICOM file formats are supported (read-only for DICOM), and all metadata is stored with the image data internally. The code can be used to visualise image slices or maximum intensity

Hello, All: Do you know of any capability to substitute more then one byte in an object of class Raw? Consider the following: > let4 <- paste(letters[1:4], collapse='') > (let4Raw <- charToRaw(let4)) [1] 61 62 63 64 > (let. <- sub('bc', '--', let4Raw)) [1] "61" "62" "63" "64" > # no

Hi., I integrate dicom in my rails application that purpose i install RMagick gem then the following errors are came. C:\Ruby187\bin>gem install RMagick Temporarily enhancing PATH to include DevKit... Building native extensions. This could take a while... ERROR: Error installing RMagick: ERROR: Failed to build gem native extension. C:/Ruby187/bin/ruby.exe extconf.rb checking

Everyone, Have any of you had any luck getting aeskulap to work with Centos7. We have just migrated some desktops from Fedora 20 to Centos. but aeskulap is not in the centos 7 repos. aeskulap was a decent dicom viewer and was able to connect to our pacs server. If there are other viewers that any of you have used I would be interested in the dialog of what you have used and any difficulties

The first release of "RNiftyReg", an R package for registration (alignment and resampling) of medical images, is now available on CRAN [1]. It may also be useful for other 3D array-like data sets. RNiftyReg is built on top of the NiftyReg library [2], and is written in a mixture of C, C++ and R. It currently supports 3D rigid-body and affine registration, and support for 2D and nonlinear

The first release of "RNiftyReg", an R package for registration (alignment and resampling) of medical images, is now available on CRAN [1]. It may also be useful for other 3D array-like data sets. RNiftyReg is built on top of the NiftyReg library [2], and is written in a mixture of C, C++ and R. It currently supports 3D rigid-body and affine registration, and support for 2D and nonlinear

Dear all, There have been some recent major updates to the TractoR and RNiftyReg packages, which are available for medical image analysis applications. If you use R for these purposes, I hope you will find the updates useful. RNiftyReg is an image registration package, which provides a clean R-like interface to the NiftyReg library developed at University College London [1]. It is aimed at

Dear all, There have been some recent major updates to the TractoR and RNiftyReg packages, which are available for medical image analysis applications. If you use R for these purposes, I hope you will find the updates useful. RNiftyReg is an image registration package, which provides a clean R-like interface to the NiftyReg library developed at University College London [1]. It is aimed at

Hello, I hope all is well. I am hoping someone can help me with a problem that I am certain is user error? The configuration details below work in all my other environments including integration, development and qa. However, the production servers give the following error: unable to find server during initialization. When I telnet to the memcached box from the server having the problem and run