similar to: Significant updates to medical imaging packages: TractoR and RNiftyReg

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, The current version of my RNiftyReg package is failing to compile on CRAN's Solaris testbed, but I don't have access to a Solaris system to debug on, and Googling the error hasn't been very helpful. The error is CC -library=stlport4 -I/home/ripley/R/cc/include -DNDEBUG -DNDEBUG -DRNIFTYREG -I/usr/local/include -KPIC -O -xlibmil -xtarget=native -nofstore -c niftyreg.cpp

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

Dear all, In R-devel (2011-09-23 r57050), I'm running into a serious problem with seek()ing on connections opened with gzfile(). A warning is generated and the file position does not seek to the requested location. It doesn't seem to occur all the time - I tried to create a small example file to illustrate it, but the problem didn't occur. However, it can be seen with a file I use for

The following code seems to contain an inconsistency in the behavior of vapply(). Am I missing something here? ## This function assumes v is a 3d vector, beta a scalar. f3d <- function(v,beta) { v+beta } ## This expression applies f3d to a vector of scalars, and ## specifies the template 'array(10,3)' for the return value. dat <- vapply(seq(0,1,length=10), function(beta) {

Dear all, Is there a way to force R CMD INSTALL to ignore ~/.Rprofile and similar? I presume it sources these startup files for a reason, but I've found that it can cause confusion or problems. In particular, my ~/.Rprofile loads a few packages which I very frequently use, but this stops me from installing new versions of their dependencies; viz. $ R CMD INSTALL tractor.base * installing to

Dear all, I recognise the reason for strongly discouraging use of printf() and similar C functions in R packages, but I wonder what people do in practice about third-party code which may be littered with such calls. I maintain a package (RNiftyReg) which provides an R interface to a third-party library which contains hundreds of calls to printf(...), fprintf(stderr,...) and similar. It seems to

Dear all, I have a simple front-end program which uses the APIs described in section 8 of "Writing R Extensions" to deviate from the standard R behaviour in fairly minor ways. However, I'm having some difficulty getting it to link reliably across different platforms. R CMD LINK seemed like it would help, but I've had difficulty finding many real-world examples online. I've

Dear all, For an open-source project that I'm working on (1), which uses R for all its heavy lifting but includes a wrapper shell script, I was hoping to find a way to capture all warnings (and, in fact, errors too), and handle them in my own way. I realise I can do this for a single expression using something like: > f <- function(w) print(w$message) >

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

dcemriS4: A package for medical image anlaysis The dcemriS4 package is a major update, and S4 implementation, of the dcemri package.? All previous functionality has been replicated, for DCE-MRI and DWI, with specific emphasis on cancer imaging applications.? Additional major features include: ? o S4 classes for NIfTI and Analyze data formats that merges header and data information o

dcemriS4: A package for medical image anlaysis The dcemriS4 package is a major update, and S4 implementation, of the dcemri package.? All previous functionality has been replicated, for DCE-MRI and DWI, with specific emphasis on cancer imaging applications.? Additional major features include: ? o S4 classes for NIfTI and Analyze data formats that merges header and data information o

I'm trying to impute data using the mi package, but after running through almost the entire first round of imputations (which takes quite a while), it throws this error (I'll include the whole output prior to the error for context). Does anyone know what is causing it, or how I can fix it? More specifically, how can I tell what is throwing the error so I know what to fix? Is

Dear all, The version of readBin() in R-devel includes a use of match(), through `%in%`, which can affect its performance significantly. By using primitives instead of the rather expensive call to match(), I reduce the time spent inside readBin() by more than 30% in some of my code (part of the tractor.base package). A simple patch that does this is given below. This passes "make

Dear all, As of the current R alpha release, I'm seeing timezone-related warnings on installing any package (including the recommended ones), which I haven't seen before. For example, [~/Documents/Source/R-alpha]$ bin/R CMD INSTALL ~/git/tractor/lib/reportr * installing to library '/Users/jon/Documents/Source/R-alpha/library' * installing *source* package 'reportr' ...

On 2019-08-16 08:10, Bernd Niedergesäß wrote: > I am a software developer myself. We develop a Radio Automation System/Broadcasting. Hence we are using the reference encoders. > > For OGG there is LUCKILY still the admin interface working to update meta data mid-stream. > That is why my post is related to the other ogg based formats: FLAC and OPUS! > > Tractor Pro is btw not

MITTWOCH 30. MAI STARTET DIE HAUSSE! Firma: TALKTECH TELEMEDIA (OYQ.F) Kurzel: WKN: 278-104 (OYQ.F) ISIN: US8742781045 Preis: 0.81 (+50% in 1 tag) 3T Prognose: 3 Overall I believe this to be a good work and worth the money if you wish to be introduced to Windows Workflow Foundation. Singer A Pedal - Impecable ! Lote De Dos Frascos Antiguos De Vidrio. This is not your average computer text which