From: Matthew Worcester (mworcest@hep.uchicago.edu)
Date: Wed Oct 26 2005 - 11:30:44 CDT
Hi Tim,
I like this idea. The only problem would be excessive size, causing quota
and checkout time problems. The gzipped G4NDL3.7 library tarball is 27.3
MB. Unless I am confused, I do see a Gd peak, altough the peak appears to
be more around 9-10 MeV. I am running a no Gd-scint job to compare.
Plots later this afternoon.
Matt
On Wed, 26 Oct 2005, Bolton, Tim wrote:
> Another idea (maybe a bad one) would be put the entire G4NDL content
into rat cvs. There is an environmental to redefine this for running G4
that could be reset in a config file. This would the Gd-enhanced model
could always be made to work independent of getting write access to g4
directories.
>
> I would insist that the Gd enhancement is not optional-- once it works
it is the ONLY way we should be running the simulation.
>
> Matt. Any evidence for Gd gamma ray emissions in a job yet?
>
> TB
>
> Tim Bolton
> Professor
> High Energy Physics Group
> Kansas State University
> tbolton@ksu.edu
> 785-532-1664
>
> ________________________________
>
> From: Stan Seibert [mailto:volsung@physics.utexas.edu]
> Sent: Wed 10/26/2005 9:12 AM
> To: Matthew Worcester
> Cc: bw_sim@hep.uchicago.edu
> Subject: Re: new Gd capture code
>
>
>
> On Oct 26, 2005, at 1:07 AM, Matthew Worcester wrote:
>
>> The other big piece is the n+Gd data tables, now kept in data/
>> neutron. I used ENDFB-VI 300K for the cross-section data. When
>> the rat.cc dependency is made the tables should copy automatically
>> to your G4NDL directory, in which G4 will read them. Note that
>> this does add files directly to your Geant4 release, which means
>> you will need write privledges there. The files are copied by a
>> simple shell script in data/neutron. Thus, if you only want to
>> copy the files once by hand, you can easily remove the source of
>> that script from your Makefile and source it yourself.
>
> My vote would be to make this copy operation occur on a separate make
> target. For example, only if you type:
>
> make installdata
>
> or something like that. That way you avoid surprising the user,
> especially since I expect most will not have write access to the
> GEANT4 data directory. I can modify the configure script and the
> install instructions to remind the user to do this (or ask someone
> with appropriate access to do it).
>
> Does this sound reasonable?
>
> ---
> Stan Seibert
>
>
>
>
This archive was generated by hypermail 2.1.6 : Thu Oct 27 2005 - 00:01:02 CDT