Ensure all images are compressed with JPEG-LS Lossless

[Björn Albers]

I want to make sure that dcm4chee-arc-light stores everything with JPEG-LS Lossless compression.

This is what worked so far in LDAP:

1. Delete every compression rule except "JPEG LS Lossless"
2. Remove the attribute "dcmProperty: SendingApplicationEntityTitle=JPEG_LS" from the compression rule above
3. Remove these unwanted transfer syntaxes from all entries with objectClass=dicomTransferCapability:

      - 1.2.840.10008.1.2.4.50                                                                                                                                                  

      - 1.2.840.10008.1.2.4.51                                                                                                                                                  

      - 1.2.840.10008.1.2.4.57                                                                                                                                                  

      - 1.2.840.10008.1.2.4.70                                                                                                                                                  

      - 1.2.840.10008.1.2.4.81                                                                                                                                                  

      - 1.2.840.10008.1.2.4.90                                                                                                                                                  

      - 1.2.840.10008.1.2.4.91                                                                                                                                                  

      - 1.2.840.10008.1.2.5 

Yah, Problem solved :)

Step 3 requires to update several hundred object - no problem with a little shell.

But I wonder if my strategy is right.

In dcm4chee v2 I had to update just a few settings (jmx-console: service=StoreScp).

Is this the "right" way? Are there any other LDAP-settings to consider?

Thanks in advance,

Björn

PS: LDAP makes automatisation much easier which is a big plus for the "new" dcm4chee.

[vrinda...@j4care.com]

Hello,

- The sample-config.ldif provides 5 types of compression rules for testing purposes only.  If your requirement is that archive stores everything with JPEG-LS Lossless compression, you could as well store the objects with JPEG_LS (or any other as per your requirement) as Sending AE title. Having multiple compression rules is for the case when different modalities are storing objects to archive with different compression types; hence this provision was given in sample-config.ldif

- The dicom Transfer Capabilities is not related with the compression rules but only indicates the transfer capabilities accepted by the archive.

[Björn Albers]

Hello Vrinda,

thanks for the response.

I want to avoid that the archive does not store images with different compression than JPEG-LS Lossless.

That's why I removed the transfer capabilities.

It this the only way to ensure this or is there a "centralized" setting hidden somewhere to whitelist transfer capabilities?

Like I said: my approach works and solves our requirement.

I just want to know if this is the official way of doing this.

Björn

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/28INY7PxA3E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[vrinda...@j4care.com]

Hello,

To avoid that the archive does not store images with different compression than JPEG-LS Lossless - as your application needs; it can be done by having just one compression rule (as you have done) or having other compression rules as well (as in sample-config.ldif) with different SendingApplicationEntityTitle against dcmProperty LDAP attribute

The transfer capabilities are not related in anyway to the compression rules; hence doesn't require to be deleted.

To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.

[Björn Albers]

No, this does not work.

The compression rules only apply to uncompressed images (explicit little endian).

When I send images with JPEG 2000 lossless compression then those images will be stored with JPEG 2000 lossless compression, tested with dcm4chee-arc-light 5.9.0.

There is no magic conversion happening in the background.

So if I want to avoid JPEG 2000 I have to configure dcm4chee to not accept it, right?

However, to my understanding this is no bug - this is how the whole transfer syntax negotiation works in DICOM.

To unsubscribe from this group and all its topics, send an email to dcm4che+unsubscribe@googlegroups.com.

[Gunter Zeilinger]

You are right. If you want to avoid accepting compressed images other than JPEG-LS Lossless, you have to remove the Transfer Syntaxes for other compression codecs - hopefully a future version of the UI will made that more convenient, than currently it is using a LDAP browser. But I would not remove JPEG Baseline (1.2.840.10008.1.2.4.50) which is quite common for Multiframe US and XA modalities. According DICOM, a Storage SCU is also not required to offer the default TS in that case!

Gunter

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+unsubscribe@googlegroups.com.

[Matthew Hill]

A simple global rule "Accept only " and a (short!) list of TransferSyntax UIDS would be nice.

Just have to beware what you hook up to the PACS... If they can't send JPEG-LS Lossless, you would need to have the right one (as in US,XA and mpegs) or at least implicit and then compress on arrival.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

[Björn Albers]

Thanks, Gunter.

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

[Burninator03]

Can I make changes to LDAP configuration and apply without stopping and starting the docker container?  While using Apache Directory Studio, the changes aren't going into effect until I restart.

Tim

[Gunter Zeilinger]

You may trigger a reload of the configuration by Reload Archive Configuration, e.g.:

$ curl -X POST http://localhost:8080/dcm4chee-arc/ctrl/reload

There is also  Reload button in the Control Panel in the UI ( http://localhost:8080/dcm4chee-arc/ui/#/ctrl ), which just invokes that HTTP POST request.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+unsubscribe@googlegroups.com.

[Burninator03]

Awesome!  Thank you!

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.