|Message: Re: GEANT4 optical processes units||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Mon, 05 Nov 2012 19:59:34 GMT, Gumplinger Peter wrote:
> [ Adam Glaser wrote: ] > > I am creating a physics list with modified optical photon processes from > > those already offered in GEANT4 but have a simple usability question. In > > the tissue optics community, optical photons are generally thought of in > > terms of the wavelength (nm or um) and optical absorption/scattering a > > thought of as attenuation coefficients (inverse length) as opposed to > > attenuation lengths.[...]
> As you know the material properties are provided to Geant4 in terms of > property tables. The existing code is written such that it expects > photon energy (and not wavelength) and attenuation lengths (distance). > The input to the tables - to the receiving program - are just numbers. > The units are just numbers as well, so I don't know how you (the > program) can recognize the units. One would have to add something to the > class that holds the units alone - do you see what I mean
Hi, Peter. I think that Adam's units issue could be encapsulated by providing an alternative set of registration functions (AddProperty...), or even just additional magic property name strings. For those cases, the code would take the user's input array, apply the necessary math (e.g., 1./x), and copy the results into a new array of the form expected by the optical processes.
Obviously, such code needs to know (or to prescribe, as you do now) _what_ units are being supplied in the arrays, since GEANT4 doesn't have smart "dimensional values".
-- Michael Kelsey