Order of INF_MICRO_FLX differs from that of MICRO_E

Report any suspected bugs and unexpected behavior here
Post Reply
AntonTravleev
Posts: 1
Joined: Thu Oct 10, 2019 3:11 pm
Security question 1: No
Security question 2: 19

Order of INF_MICRO_FLX differs from that of MICRO_E

Post by AntonTravleev » Thu Oct 10, 2019 3:23 pm

In Serpent2 (tested with 2.1.29 and 2.1.31) *_res.m file, the order of INF_MICRO_FLX and B1_MICRO_FLX entries differs from the order of the respective energy boundaries in MICRO_E.

I faced this problem when working with the serpentTools Python package so I raised an issue there. However, I believe this is the Serpent issue, at least this behaviour is described neither in Manual nor at the Wiki.

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

Re: Order of INF_MICRO_FLX differs from that of MICRO_E

Post by Jaakko Leppänen » Fri Oct 11, 2019 5:17 pm

You are right. Changing line 1754 of matlaboutput.c from :

Code: Select all

                fprintf(fp, "%12.5E ", RDB[ptr + n]);
to:

Code: Select all

                fprintf(fp, "%12.5E ", RDB[ptr + nmg - n - 1]);
should do the trick.
- Jaakko

Post Reply