action order on same field
See original GitHub issueHello, I am confused by following in docs:
For the above, given that there are conflicting commands, the more conservative is given preference. For example: REMOVE > BLANK > REPLACE > JITTER/KEEP/ADD … If I specify to blank a header and remove it, it will be removed If I specify to replace a header and blank it, it will be blanked
Also
Most of the time, you won’t need to specify remove, because it is the default
But at the same time there is an example of
ADD PatientIdentityRemoved Yes
REMOVE ALL
KEEP PixelData
Here I naturally make assumption that ALL
means ALL
, so each field is removed, and according to rules quoted above, REMOVE
rules over KEEP
, so tag kinda has to be removed.
How does it work? How is PixelData
expected to be kept?
In my usecase I want to drop all information except for certain tags, part of them I want to keep, part of them I want to replace with my custom func. I don’t want to manage full set of DICOM tags, but rather remove all and preserve only certain subset. How?
Issue Analytics
- State:
- Created 2 years ago
- Comments:23 (23 by maintainers)
Top GitHub Comments
Haha definitely! It’s probably not the best example - they always used colored balls in bags as examples in statistics courses, so I’m not sure I did it justice 😆
Closed with #198