GithubHelp home page GithubHelp logo

Comments (8)

Nitesh639 avatar Nitesh639 commented on June 14, 2024 2

@ceiag Go with this link.
I have a strong feeling you will get some output files. Don't change the config.json file.

from niffler.

pradeeban avatar pradeeban commented on June 14, 2024

The log means, the folder does not have any valid DICOM files. I know you have a file with the .dcm extension in that folder. But the file must be invalid (i.e., not a DICOM file).

Can you please try to reproduce the issue with a publicly available DICOM file such as the ones in https://www.cancerimagingarchive.net/collections/?

Then if you can still reproduce it, please point me to one such DICOM file so that I can further debug this issue.

I tried to reproduce with the below configuration with the same Niffler version as yours.

{
"DICOMHome": "/Users/Pradeeban/Desktop/op",
"OutputDirectory": "png",
"Depth": 0,
"SplitIntoChunks": 1,
"PrintImages": true,
"CommonHeadersOnly": false,
"PublicHeadersOnly": true,
"SpecificHeadersOnly": false,
"UseProcesses": 0,
"FlattenedToLevel": "patient",
"is16Bit":false,
"SendEmail": true,
"YourEmail": "[email protected]"
}

I cannot reproduce the issue. Even when a DICOM file that has some issues were used, this is the log that is thrown:

$ cat ImageExtractor.out
INFO:root:------- Values Initialization DONE -------
INFO:root:Number of dicom files: 1
DEBUG:root:Loaded the first file successfully
WARNING:pydicom:Expected sequence item with tag (fffe, e000) at file position 0x14
WARNING:pydicom:Expected sequence item with tag (fffe, e000) at file position 0x14
WARNING:pydicom:Expected sequence item with tag (fffe, e000) at file position 0x14
WARNING:pydicom:Expected sequence item with tag (fffe, e000) at file position 0x14
INFO:root:Chunk 0 Number of fields per file : 48
INFO:root:Start processing Images
ERROR:root:Unable to convert the pixel data: one of Pixel Data, Float Pixel Data or Double Float Pixel Data must be present in the dataset
ERROR:root:1 out of 1 dicom images have failed extraction
INFO:root:Chunk run time: 0.11768984794616699 seconds!
INFO:root:Generating final metadata file
INFO:root:Generating final mapping file
INFO:root:Total run time: 0.15414905548095703 seconds!
Pradeebans-MacBook-Pro:png pradeeban$ tree
.
├── ImageExtractor.out
├── ImageExtractor.pickle
├── extracted-images
├── failed-dicom
│   ├── 1
│   │   └── 1.2.276.0.28.3.194080963160286.12.3612.2018102319423250000.dcm
│   ├── 2
│   ├── 3
│   ├── 4
│   └── 5
├── mapping.csv
├── maps
│   └── mapping_0.csv
├── meta
│   └── metadata_0.csv
└── metadata.csv

9 directories, 7 files

On the other hand, if I instead use a fake DICOM file (for example, create a text file and store it as test.dcm under the folder), I get the message that you get (which simply states there is no real DICOM files present).

from niffler.

Nitesh639 avatar Nitesh639 commented on June 14, 2024

ImageExtractor.py is working properly. @ceiag make sure you are use .dcm file format not .DCM format.
This thing also cause error because we are only detect .dcm files.
https://github.com/Emory-HITI/Niffler/blob/master/modules/png-extraction/ImageExtractor.py#L334

from niffler.

Nitesh639 avatar Nitesh639 commented on June 14, 2024

@pradeeban, I think we should be add some examples of .dicom(.dcm format) images.

from niffler.

pradeeban avatar pradeeban commented on June 14, 2024

@Nitesh639 I will include the links to TCIA to download sample files. We shouldn't duplicate DICOM files in the repository. Git repositories should avoid binary files.

Also, in practice, whoever uses the Niffler PNG Extraction should have access to DICOM files (as Niffler is a domain-specific radiology software). I understand sample DICOM files will be helpful for situations such as Google Summer of Code contributors.

from niffler.

Nitesh639 avatar Nitesh639 commented on June 14, 2024

OK.

from niffler.

ceiag avatar ceiag commented on June 14, 2024

Thanks All for the replies.

Yep looks like something isn't right my end, even after downloading a publicly available dicom dataset from https://www.cancerimagingarchive.net/collections/ it's still not detecting .dcm files in the target directory.

from niffler.

pradeeban avatar pradeeban commented on June 14, 2024

Closing this issue since @Nitesh639 has given sample files to run without even changing the configurations. This should help you get started, when you are not familiar with Niffler.

from niffler.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.