-
Updated
Sep 30, 2020 - JavaScript
dicom
Here are 372 public repositories matching this topic...
-
Updated
Oct 4, 2020 - JavaScript
-
Updated
Sep 29, 2020 - JavaScript
-
Updated
Sep 29, 2020 - Python
-
Updated
Oct 3, 2020 - C#
-
Updated
Sep 30, 2020 - JavaScript
-
Updated
Oct 1, 2020 - C++
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Oct 2, 2020 - C++
-
Updated
Oct 2, 2020 - C++
-
Updated
May 1, 2020 - Python
-
Updated
Sep 20, 2020 - Java
-
Updated
Sep 26, 2020 - Python
-
Updated
Sep 24, 2020 - C++
The current Transfer Options page leaves a bit to be desired. I propose that these aspects are improved:
- There isn't a way to enable a transfer syntax regardless of the SOP class (or at least for those already admitting at least one transfer syntax). This means that allowing a transfer syntax requires looking up every applicable SOP class.
- The "Select All" and "Deselect All" will check and
-
Updated
Oct 1, 2020 - JavaScript
-
Updated
Sep 15, 2020 - C++
Allow the user of dicom_object to take the element from the object, removing it in the process.
For in-memory objects, this can translate to less data copying.
/// <document please>
pub fn take_element(&mut self, tag: Tag) -> Result<InMemElement<D>> {
todo!()
}
/// <document please>
pub fn take_element_by_name(&mut self, name: &str) -> Result<InM-
Updated
Sep 30, 2020 - JavaScript
At the moment, standard codes used require manual typing of the code tuple, such as here. This is error-prone and long. Instead, we should use the #defined constants, as done in dcmsr: https://github.com/commontk/DCMTK/blob/patched-DCMTK-3.6.3_20180205/dcmsr/include/dcmtk/dcmsr/codes/dcm.h#L51.
It would be also i
-
Updated
Apr 7, 2020 - JavaScript
-
Updated
Apr 19, 2019 - Python
Improve this page
Add a description, image, and links to the dicom topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the dicom topic, visit your repo's landing page and select "manage topics."
There are all sorts of odd or even non-conformant DICOMs out in the world.
When we encounter parser failures on a DICOM (for both the current and the in progress rewrite), it would be good to be able to toggle a debug mode flag that can help us better dig into parsing failures and provide helpful information. Ideally if this information is not PHI (e.g. just DICOM tags, other general info), it