Eduardo Pinho

> @Enet4 my problem is that I don't see where there is any slicing occurring? With the current setup, slicing is expected to be done after the decoding, when turning...

Sounds unlikely. The discussions suggest that there isn't a trivial fix. Consider using `gulp-mocha` 3 in the mean time.

With #604, the DICOM data sender used by the Move SCP has been made more efficient. Could you try again with the upstream `dev` version?

You may need to enable more transfer options in the archive. In the Dicoogle management page, open Transfer Options and ensure that the transfer syntaxes are enabled for the intended...

As of version 0.6: ```rust use dicom::encoding::submit_transfer_syntax; submit_transfer_syntax_ele!( "1.3.46.670589.33.1.4.1", "CT-Private-ELE", Codec::EncapsulatedPixelData(None, None) ); ```

#408 provides a solution, although it will continue to be true that `write_datset` does no transcoding.

Related: #352

For what it's worth, we were able to use RapiPdf in Node.js with something like this: ```javascript const fs = require('fs'); const jsdom = require('jsdom'); const virtualConsole = new jsdom.VirtualConsole();...

> However, there is a problem for nifti-rs because a few fields already have getter-like functions with the same name. For example, `NiftiHeader::dim` is a `[u16;8]` and `NiftiHeader::dim()` returns a...

Coincidently, one of the ideas that I've had at the back of my head for a while was a "lazy" NIfTI volume implementation, which would not pull all of the...