Message: Density difference in the new DICOM example - potential bug Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Density difference in the new DICOM example - potential bug 

Forum: Medical Applications
Date: 17 Mar, 2018
From: Adam Geva <Adam Geva>

Hello,

In the DICOM example, using DCMTK. in the method DicomDetectorConstruction::ReadVoxelDensities, we are setting all density diffs to be -1:

  char* part = getenv( "DICOM_CHANGE_MATERIAL_DENSITY" );
  G4double densityDiff = -1.;
  if( part ) densityDiff = G4UIcommand::ConvertToDouble(part);

  std::map<G4int,G4double> densityDiffs;
  for( size_t ii = 0; ii < thePhantomMaterialsOriginal.size(); ii++ ){
    densityDiffs[ii] = densityDiff; //currently all materials with same step
  }

Then, inside the nested loops, we have:

  if( densityDiff != -1. ) continue; 

This essentially forces all voxels that belong to a specific base material to be in the same bin. Is that a bug or am I missing something? Thank you!

Adam

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 Feedback: Re: Density difference in the new DICOM example - potential bug   (Pedro Arce - 19 Mar, 2018)
 Add Message Add Message
to: "Density difference in the new DICOM example - potential bug"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]