I will try as soon as the regular work is done and I can shut down the pacs for a couple of minute as I am offsite and can pull of this test at home
Posts by blub_smile
-
-
Here you go
Code -
Hi Marcel
Works with .17d and the beta you linked just fine - so bug was introduced later
-
Ok, will test it tonight.
OT: I think N2/NKI is the perfect compression as it provides a compression that is actually fast (because u said it is threaded) compared to JPEG.
-
When I query CC via "PatientStudy only" it does not work.
It does however work via "Study root" - any chance to get that work via "Study root" - CLI maybe? -
Hi
I am trying to get on my PACS missing studies from one of our workstations. The workstation just runs a dicom viewer (ClearCanvas).
Evertime I use "Get local missing patients" I get an "lost remote dicom association" error. Bit when I query the remote host on the "Study/Patient root" level
the query works fine.Is the local missing patient function only working between Conquest servers?
-
Ha!
Funny question - I only tried the lastest beta 3a for a large move of images !
Which versions do you want me to test? - in which order?
-
Hi
Those were NKI "n2"
-
Hi
I just did some more testing in my production environment and I did get an error "restarted dead server after error 7" when I was transfering a large study of 1400 images - but it always crashed below 100 images during sending.
Debug log:
-
Hi
Forwarding is working now, thx
-
Hi, just did a quick test but it did not forward anything - so seems still broken
-
Hi
Forwarding still seems to be broken - I just gave it a try and neither drag'n drop did work nor forwarding images from a DICOM source
-
Hi
Is there a way to delete a study based on the Accession Number via CLI? - I need to delete quite some studies and that seems to be the easiest way
-
Yep I also noticed the intermittent GUI freeze when doing a "rebuild database" operation
-
Hi
In the last days I did some testing for transfer speeds.
My data is stored as NKI N2 and I noticed that when I send it as uncompressed I get 70-100 images/s.
From J2K lossless stored data sending as uncompressed is much slower - around 20 images/sSo what makes NKI compression so fast?
-
Ok afetr some quick test:
JpegLS = 12,2 IMages/s - so much better but still not as fast as N2.
Now we just have to wait for the DICOM viewers to work with JpegLS
PS: Just noticed that in the beta the export converters are not working - any idea when that will be fixed?
-
Ok, thx. Then we will wait for JpegLS
-
Hi
Why can't it be done via multihreading? -
Hi
OK here we go:
Study of 852 images from uncompressed via drag'n-drop to GUI:
Conquest 1.4.17 storage set to jk: 151s -> 5,6/images/s
Conquest 1.4.19 beta storage set to jk: 182s -> 4,6/images/s
Comparison to 1.4.17 storage as n2: 40s -> 21/sOK I admit that it is not as slow as I thought but in general I am suprised how slow J2K lossless is in storage...
Machine is a Xeon 12 core 3Ghz 32GB RAM. Source was SSD destination was a 8 Disk RAID with 7200rpm.
CPU Utilization was like 8% max.Is there no way of speeding up J2K compression on fast machines?
-
Hi
I just gave the new version a quick try and I noticed that J2K lossless compression seems to be arkward slow - without real measurement I would guess like 2 images/s.
Is that a known limitation of the new compression alghorithm?