3D lat example request

Report all good and bad behavior here
Tian
Posts: 18
Joined: Mon Mar 10, 2014 1:19 pm
Security question 1: No
Security question 2: 92

Re: 3D lat example request

Post by Tian » Mon Jun 02, 2014 4:11 pm

I am sorry, a mistake. Here it is, just a simple one.
Attachments
Assemblyburnupdep.tar.gz
(2.6 KiB) Downloaded 982 times

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: 3D lat example request

Post by Jaakko Leppänen » Mon Jun 02, 2014 5:04 pm

It looks like the error is on line 1001 of collectresults.c:

Code: Select all

AddStat(1E-6*norm*fiss*fE/fmass, ptr, i);
It should be:

Code: Select all

AddStat(1E-6*norm*fE/fmass, ptr, i);
This should not affect any other results.
- Jaakko

Tian
Posts: 18
Joined: Mon Mar 10, 2014 1:19 pm
Security question 1: No
Security question 2: 92

Re: 3D lat example request

Post by Tian » Fri Jun 06, 2014 10:55 am

Sorry, for the segmentation fault I discussed with the IT administrator who in charge of compiling serpent. She told me she have to do a special version for me to enable debugging option and may cost lot of work and time, and also may bring trouble to other users of institute. Thus she suggested me probably you may help me to test the input, which I already uploaded, Could you probably bothering do me a favor to test it? Or I have to test it by myself to check where the mistake is? The version I use is serpent 2.1.20 oimpi.

Thank you very much for your help and sorry for such a request.

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: 3D lat example request

Post by Jaakko Leppänen » Sun Jun 08, 2014 12:24 pm

Running the code in debug mode doesn't require anything else than changing one line in the Makefile from:

#CFLAGS += -DDEBUG

to:

CFLAGS += -DDEBUG

and recompiling the code. Discovering bugs and problems is an essential part of beta-testing, and it therefore makes a lot of sense to have executables for both non-debug and debug version of the code. This way, you can immediately rerun the calculation with the debug version if a problem like this comes up.

Segmentation faults are difficult also because they can be related to memory leakages, and may not be reproducable in another system. I tried running your lat11 input, and didn't get any error.
- Jaakko

Tian
Posts: 18
Joined: Mon Mar 10, 2014 1:19 pm
Security question 1: No
Security question 2: 92

Re: 3D lat example request

Post by Tian » Mon Jun 09, 2014 12:35 pm

Thanks for your kind. Then I will try to discuss with our IT to check what exactly wrong.

Tian
Posts: 18
Joined: Mon Mar 10, 2014 1:19 pm
Security question 1: No
Security question 2: 92

Re: 3D lat example request

Post by Tian » Tue Jun 10, 2014 11:44 am

Here is the running result of serpent 2.1.20 oimpi with 10 nodes

Code: Select all

Calculating DT neutron majorant cross section:

   0% complete
  79% complete
 100% complete

Clearing results and statistics...
OK.

Sampling initial source...
OK.

***** Tue Jun 10 10:39:29 2014 (seed = 1402389545, MPI task = 0, OMP thread = 4)

Fatal error in function Score:

Pointer error: value 0 below minimum = 837 (rea)

Simulation aborted.
Neither IT technician or me has any idea of this error, what might be the reason of this?

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: 3D lat example request

Post by Jaakko Leppänen » Tue Jun 10, 2014 12:52 pm

OK, so now that the calculation was run in debug mode, the code printed out a pointer error with function name instead of segmentation fault. The problem is probably related to this:

http://ttuki.vtt.fi/serpent/viewtopic.php?f=25&t=2038
- Jaakko

Post Reply