similar to: outcome of big rsync. Puzzling

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

RoR-ers, I''ve bumped into an issue with ruby and ssl. I''m trying to run a rake command which aborts because it cannot find openssl.rb. I followed these steps: - mkdir /rho; chown phor /rho - wget ftp://ftp.ruby-lang.org/pub/ruby/1.8/ruby-1.8.7-p72.tar.bz2 - tar jxf ruby-1.8.7-p72.tar.bz2 - cd ruby-1.8.7-p72 - vi ext/Setup and uncomment these lines: bigdecimal curses

I picked up some data from the nearest hospital to take to the specialist at the next one, with whom I had an appt.; it came on a CD, which is marked "DICOM Volume with GE Centricity Viewer." When I put the CD into a drive, Fedora 11 auto-mounts it, and fails to find the autorun.exe, which is right there in plain sight. (F11 knows it exists, and asks whether to run it, and then

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

I have the following "show.html.erb" script, and I get as an output TWO images since I use a method to draw an image. How can I HIDE the RESOURCE image? Thanks. Here is the script: <canvas id="line" height="512" width="512"> </canvas> <p id="notice"><%= notice %></p> <p> <b> Name </b> <%=

Everyone, I wanted to report that the aeskulap dicom viewer available on the nux.dextop repositories is now working with the lastest kernel update : kernel.x86_64 3.10.0-957.5.1.el7. Thanks much to everyone!!! -- Greg Ennis

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

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.dicom (v0.2.4) is now available for download from CRAN. This is a major revision and improvement that replaces the previous DICOM package. New features include: * Increased speed * Uploading only header information (for restricted memory situations) * Reading implicit value representations (VR's) * Parsing SequenceItem tags (undefined lengths are allowed) *

The first release of oro.dicom (v0.2.4) is now available for download from CRAN. This is a major revision and improvement that replaces the previous DICOM package. New features include: * Increased speed * Uploading only header information (for restricted memory situations) * Reading implicit value representations (VR's) * Parsing SequenceItem tags (undefined lengths are allowed) *

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

isoconfig.sys file below - Only change from past is adding stuff after the bz28.7 kernel. DEFAULT vesamenu.c32 Prompt 0 menu color screen 37;40 #80ffffff #00000000 menu color border 30;44 #40000000 #00000000 menu color title 1;33;44 #c0fdd017 #00000000 menu color unsel 37;44 #90ffffff #00000000 menu color hotkey 1;37;44 #ffffffff #00000000 menu color sel 7;37;40

On Tue, Sep 24, 2013 at 10:21 PM, Aris Adamantiadis <aris at 0xbadc0de.be> wrote: [snip] > I've worked this week on an alternative key exchange mechanism, in > reaction to the whole NSA leaks and claims over cryptographic backdoors > and/or cracking advances. The key exchange is in my opinion the most > critical defense against passive eavesdropping attacks. > I believe

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

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

Hi all, Since the vault for 7.3.1611 has been cleared out last sunday (20170207) - why is that? - I'm using git to download a "SRPM", or more accurately, its contents. However, using git has one major drawback: It is missing checksums for the files. Are there any plans to provide checksums for the files in git so I can be sure that what I download is actually not tampered with?

On Tue, 2006-02-21 at 14:58 -0800, rsync2eran@tromer.org wrote: > A year ago we discussed the strength of the MD4 hash used by rsync and > librsync, and one of the points mentioned was that only collision > attacks are known on MD4. Could you please forward this into the bug tracker so it's not lost? -- Martin -------------- next part -------------- A non-text attachment was