ls files and storege

How to backup and/or replicate your PacsOne Server database for redunancy and fault tolerance?
Post Reply
diegog
Posts:36
Joined:Sat Feb 25, 2012 12:01 pm
Contact:
ls files and storege

Post by diegog » Tue Apr 09, 2013 4:57 pm

Hi, I need some help with an storage issue that is taking 30% of the total storage.
After some time of pacsone connected to an MRI we realize pacsone is creating ls files (about 200 kb) together with original dicom files (500 kb).
We didn't set up a LTA becouse we don't want to move the files, just back up them.
How we can store originally data received in lossless dicom compressed without dupplication.
Pacsone must work in this way?
Ls + DICOM is common?
Thanks to answer
Diego

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Wed Apr 10, 2013 4:51 pm

The "*.ls" files are the output of the JPEG-Lossless compression from the optional Post-Receive Dicom Image Compression feature, which is used for optimizing the delivery of Dicom images to the web-based image viewers since the Dicom images are pre-compressed before the viewers request for them.

Those Post-Receive compressed images are intended to speed-up the delivery of Dicom images to the web-based image viewers, as PacsOne will deliver the pre-compressed images to the viewers instead of the original versions if the compressed versions are available. However, PacsOne Server cannot dictate to store all received Dicom images in a pre-determined Dicom compression transfer syntax, because it has to be negotiated between the sending and receiving Dicom application (PacsOne in this case). That's the reason why you cannot make PacsOne Server to always store received original Dicom images in a pre-determined Dicom compression transfer syntax such as the JPEG Lossless compression.

diegog
Posts:36
Joined:Sat Feb 25, 2012 12:01 pm
Contact:

Post by diegog » Wed Apr 10, 2013 6:30 pm

Thanks for your answer.
How can I auto-erase ls files or configure the system do not create them.
Pacsone is working with Medream/Medreport viewer.
Also is forwarding studies to another central PACS system (in preferred compressed syntax).
We need to send compress images (for bandwidth reason) but not store them. Any solution or recommended configuration to save storage space?
Thanks
Diego

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Fri Apr 12, 2013 4:16 pm

You can disable the Post-Receive Image Compression feature from the configuration settings when you click on the Edit URL link displayed for that Source AE under the Dicom AE page.

If you want to send compressed Dicom images to a remote AE, you need to configure one of the Dicom compression transfer syntaxes, e.g., JPEG Lossless, etc, as the Preferrred Transfer Syntax for that remote AE from the Dicom AE table.

diegog
Posts:36
Joined:Sat Feb 25, 2012 12:01 pm
Contact:

Post by diegog » Sun Apr 14, 2013 7:56 am

Thanks, did it and is working!
Two more questions regarding LS:
1-It is possible to store in compressed mode without having LS+native images (duplicated)?
2- It is possible to erase ls images without problems in the database?

Thanks

Diego

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Mon Apr 15, 2013 4:34 pm

1. As indicated in the previous posts, the Dicom transfer syntax (compressed or not) used to store the received images is negotiated by both the sending and receiving (PacsOne Server in this case) Dicom applications, so you cannot dictate beforehand exactly which Dicom compression transfer syntax will be used to store the received Dicom images.

2. You can feel free to delete all the "*.ls" files, since they are merely used to speed up the delivery of Dicom images to the web-based image viewers, i.e., if you delete the "*.ls" files, PacsOne will send the original Dicom images to the web-based Dicom image viewers instead of the pre-compressed versions ("*.ls"), which may take longer to deliver but will not affect the functionality.

Post Reply