#J2k support pdf
> I tried gdcmconv.exe as you suggested, its > VMNHHHXDMA763HOB9B3YGAKLPK3C0K27J8SMJ8AFT.EX.DCM > copied these files from the repository from the database.
#J2k support software
> proprietary software reads these files fine. > To my knowledge, the software that comes with the > FAP4元WSQA1TNTMY5KQZTGAKLPK3C1927J8SMJ8AFT.EX.DCM > with the other file sent you on Sep 28th: > That file works fine, but the problem I mentioned was > system, only during the export does it garantee that the > There is no requirement for the file format used internally
> vendor for documentation about this file format, but this > a valid DICOM (see Pixel Spacing for example). > No I told this is not (even close) a J2K/DICOM file. On Thu, 10/2/08, Mathieu Malaterre wrote: I have tried both DICOM export as well as directly copying the files, both seem to have problem in reading.īy any chance you have some documentation on the JPEG2000 decoder? Thanks for your help. I see pixel spacing to be 0.0302, but what's wrong that (spacing b/n slices in mm)? Also, TransferSyntacUID is '1.2.840.10008.1.2.4.91'. > And then you'll be able to read clean_j2k.dcm > $ gdcmconv -j2k -force -i buggy_j2k.dcm -o > J2K, but the bug could be easily handled, simply > No your problem was different, it was indeed a bug > has the same problem as this person's and if > You might remember about issues with my JPEG > updated this directory with the recent GDCM through SVN). > (Note: ignore the 2.0.8 dir listing in the log, I \.\.\.\Programs\gdcm-2.0.8\Source\MediaStorageAndFileFormat\gdcmJPEG2000Codec.cxx, > -j2k -force -i e:\Madhu\temp\orig.DCM -o > E:\Madhu\Software\GDCM\bin\debug>gdcmconv > I got the recent trunk for GDCM and here is the error log > failing (you can try with the example I already sent you). > I tried gdcmconv.exe as you suggested, its still > 'VMNHHHXDMA763HOB9B3YGAKLPK3C0K27J8SMJ8AFT.EX.DCM' > VMNHHHXDMA763HOB9B3YGAKLPK3C0K27J8SMJ8AFT.EX.DCM -o out.dcm > - On Thu, 10/2/08, Mathieu Malaterre wrote: I directly copied these files from the repository from the database. > To my knowledge, the software that comes with the proprietary software reads these files fine. > That file works fine, but the problem I mentioned was with the other file sent you on Sep 28th: FAP4元WSQA1TNTMY5KQZTGAKLPK3C1927J8SMJ8AFT.EX.DCM On Thu, at 4:33 PM, Madhusudhanan Balasubramanian System, only during the export does it garantee that the file will be There is no requirement for the file format used internally in a PACS Vendor for documentation about this file format, but this is not a This is not evenĪ valid DICOM (see Pixel Spacing for example). No I told this is not (even close) a J2K/DICOM file. > And then you'll be able to read clean_j2k.dcm almost > $ gdcmconv -j2k -force -i buggy_j2k.dcm -o clean_j2k.dcm > J2K, but the bug could be easily handled, simply do: > No your problem was different, it was indeed a bug in GDCM > has the same problem as this person's and if it could be > You might remember about issues with my JPEG 2000 > - On Wed, 10/1/08, Mathieu Malaterre wrote: > (Note: ignore the 2.0.8 dir listing in the log, I updated this directory with the recent GDCM through SVN).
\.\.\.\Programs\gdcm-2.0.8\Source\MediaStorageAndFileFormat\gdcmJPEG2000Codec.cxx, line 151 > option o with value 'e:\Madhu\temp\clean.DCM' > option i with value 'e:\Madhu\temp\orig.DCM' > E:\Madhu\Software\GDCM\bin\debug>gdcmconv -j2k -force -i e:\Madhu\temp\orig.DCM -o e:\Madhu\temp\clean.DCM I got the recent trunk for GDCM and here is the error log from gdcmconv: > I tried gdcmconv.exe as you suggested, its still failing (you can try with the example I already sent you). On Thu, at 3:58 PM, Madhusudhanan Balasubramanian Option i with value 'VMNHHHXDMA763HOB9B3YGAKLPK3C0K27J8SMJ8AFT.EX.DCM' VMNHHHXDMA763HOB9B3YGAKLPK3C0K27J8SMJ8AFT.EX.DCM -o out.dcm