Problem 1311 - Null Files for G4EMLOW6.23
Summary: Null Files for G4EMLOW6.23
Status: RESOLVED INVALID
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/electromagnetic/lowenergy (show other problems)
Version: 9.5
Hardware: All All
: P5 trivial
Assignee: Sebastien Incerti
URL:
Depends on:
Blocks:
 
Reported: 2012-05-08 23:25 CEST by John Lucido
Modified: 2012-05-09 23:30 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description John Lucido 2012-05-08 23:25:10 CEST
Hi,

I was trying to test my user codes as I moved them from 4.9.5_b01 to 4.9.5_p01, and linking with the data in G4EMLOW6.23 instead of G4EMLOW6.22. The old version was working, and there were no compilation errors. When I ran my user code installation test, I got the following output to my err stream:


-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : em0003
      issued by : G4AugerData::LoadData
Missing/home/jlucido/GEANT4/geant4.9.5_p01/DATA/G4EMLOW6.23/auger/au-tr-pr-6.dat
*** Fatal Exception *** core dump ***
-------- EEEE -------- G4Exception-END --------- EEEE -------


*** G4Exception: Aborting execution ***


I looked in the directory listed above, and found that this file exists but is zero bytes.

Also, when I tried to run the program with the old data files, it gave me a version error (ie, it required 6.23).

Does anyone know a fix to this problem?

Thanks,

John Lucido
Comment 1 John Lucido 2012-05-08 23:26:16 CEST
Note: most of the other Auger data files are not empty, just the ones with numbers between 1 and 9.
Comment 2 Sebastien Incerti 2012-05-09 11:15:29 CEST
Hi John,

Thanks for this bug report.

In order to verify the file content of G4EMLOW6.23, I just downloaded again this dataset from:
http://geant4.web.cern.ch/geant4/support/download.shtml

I did not find the empty Auger files your are listing. 

Maybe you could simply download again this dataset ?

Sebastien Incerti
Comment 3 John Lucido 2012-05-09 23:30:57 CEST
The problem was not with the files, but with the alias in my .bashrc file. Fixing that seems to have fixed the "bug".