similar to: dicom viewer for Centos 7 and pacs servers

Displaying 20 results from an estimated 10000 matches similar to: "dicom viewer for Centos 7 and pacs servers"

2019 Feb 15
1
Aeskulap & kernel.x86_64 3.10.0-957.5.1.el7
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
2011 Dec 01
0
pb with 4D dicom data and oro.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
2006 May 12
1
DICOM package wont read my DICOM files
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
2018 Dec 30
1
[Fwd: Centos 7.6 and Aeskulap]
On 12/28/18 6:38 AM, Gregory P. Ennis wrote: > > > I tried to compile aeskulap on Centos 7.6 by using the commands ./configure followed by > > make which resulted in the following errors : > > Attempting to build this way is next to pointless and will likely show > you errors completely unrelated to why the package won't properly build. > > > make[4]: ***
2018 Dec 28
3
[Fwd: Centos 7.6 and Aeskulap]
Everyone, Apparently, aeskulap is broken during the upgrade fro 7.5 to 7.6, and is no longer available in the epel repos. I had some difficulty having it function, and during the debug process I decided to do a yum remove, but when I tried a yum install to reinstall it, aeskulap was no longer present. This problem may also affect other modules. I have placed a bug report :
2009 Aug 06
10
GE centricity viewer??
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
2018 Dec 15
2
[Fwd: Centos 7.6 and Aeskulap]
Everyone, Apparently, aeskulap is broken during the upgrade fro 7.5 to 7.6, and is no longer available in the epel repos. I had some difficulty having it function, and during the debug process I decided to do a yum remove, but when I tried a yum install to reinstall it, aeskulap was no longer present. This problem may also affect other modules. I have placed a bug report :
2018 Dec 28
0
[Fwd: Centos 7.6 and Aeskulap]
On 12/28/18 6:38 AM, Gregory P. Ennis wrote: > >> I tried to compile aeskulap on Centos 7.6 by using the commands ./configure followed by >> make which resulted in the following errors : > > Attempting to build this way is next to pointless and will likely show > you errors completely unrelated to why the package won't properly build. > >> make[4]: ***
2010 Mar 12
0
oro.dicom released (replaces 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) *
2010 Mar 12
0
oro.dicom released (replaces 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) *
2018 Dec 27
0
[Fwd: Centos 7.6 and Aeskulap]
Everyone, Apparently, aeskulap is broken during the upgrade fro 7.5 to 7.6, and is no longer available in the epel repos. I had some difficulty having it function, and during the debug process I decided to do a yum remove, but when I tried a yum install to reinstall it, aeskulap was no longer present. This problem may also affect other modules. I have placed a bug report :
2018 Dec 28
2
[Fwd: Centos 7.6 and Aeskulap]
> I tried to compile aeskulap on Centos 7.6 by using the commands ./configure followed by > make which resulted in the following errors : Attempting to build this way is next to pointless and will likely show you errors completely unrelated to why the package won't properly build. > make[4]: *** [dimoimg.o] Error 1 > make[4]: Leaving directory
2005 Aug 22
0
New CRAN package: DICOM
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
2005 Aug 22
0
New CRAN package: DICOM
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
2010 May 19
4
Installing K-Pacs under WINE
Hi, I would like to install K-Pacs (www.k-pacs.net) under WINE. If I open the K-pacs installer ("Installer V1.6.0 English.exe"), I receive the following error: wine: cannot find L"C:\\windows\\system32\\Installer.exe" I am using the latest version of Ubuntu & Wine. Any idea what the problem might be? I'm new to Ubuntu & have not used WINE before (so there is a big
2011 Nov 16
0
Dicom integration
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
2018 Sep 12
2
openl2tp.org compared to openvpn
Everyone, I am needing to set up a secure channel with another office in order to pass some dicom files back and forth. The remote office is microsoft shop. I have initially looked at openvpn, but the microsoft shop has requested that we use openl2tp in that they already have this running. Since openl2tp is not part of the centos repositories, does anyone have good or bad experiences with
2006 May 15
1
PDF viewer?
Hi, I'm looking for a usable PDF viewer with CentOS 4.3. On my previous install (Slack running XFCE with a handful of GNOME libs), I used Evince, which is just great. Looks like this is an Achilles' heel in CentOS, as I tested three available PDF viewers (ggv, gsview, acroread) with various PDF documents downloaded from the internet (which all display perfectly with Evince): either the
2013 Jul 17
1
picture viewers
Ok, I give up. After the last month or so, gwenview takes literally five minutes or so to come up, gagging because I have nepomuk turned off in kde. Today, it just will not come up at all, even trying gwenview pic.jpg. Are there any other ->light weight<- image viewers in the standard repositories, including epel? I DO NOT WANT OR NEED a "semantic desktop" (aka bloat, suitable for
2018 Dec 05
0
7.5 -> 7.6 problems
On Wed, 5 Dec 2018 at 10:17, Gregory P. Ennis <PoMec at pomec.net> wrote: > > To all, > > I started the process of updating some of our systems from 7.5 to 7.6. > Most of the servers had no problems, but several of the desktops had > some difficulties. I was required to perform several yum commands to > update as much as possible in the format of yum update a* then b*