Using convert_lib to convert Vitamin-J+ (211) group data shows error
YuanHu-PKU-KIT opened this issue · 11 comments
I'm tring to use convert_lib to convert Vitamin-J+ (211) group data, but it shows error as follow:
*** stack smashing detected ***: <unknown> terminated Aborted (core dumped)
I have located that this error occurs between binLib->close() function and gammaLib->close() function in ASCIILib.c, but I don't know how this error occurs and how to fix it. Please enlighten me if you have a clue about this.
Thanks for reporting this. While I'm not sure exactly what is causing this problem, it is probably a good idea to check the format of the original file to ensure that it's still compatible with ALARA's parsers.
What is the format of this file?
The file is an eaf format data file of EAF2010 database. I also tried to convert the 175 group data (also eaf format), and it worked. But with the 211 group data, it will show error.
Here are the first 20 line of the file I used:
The input of converting data is:
convert_lib eaflib alaralib EAF2010/eaf_n_gxs_211_flt_20100 EAF2010/eaf_dec_20100 EAF2010/eaf_2010_211
I changed the array length of follows:
char emission[64]; -> char emission[128]; in ALARALib::appendIdx() function of ALARALib.c file
char buffer[64]; -> char buffer[128]; in ALARALib::LibIdx::LibIdx() function of LibIdx.c file
and it could convert the 211 group data and run activation calculations now.
ALARA has not been tested with more recent versions of the EAF format libraries. I am interested in your experience with these results and encourage you to compare some sample results with this library and older libraries. @moatazharb had some experience with this here a few years ago
I try to calculate natural Iron @1g/cc activation under DONES neutron spectrum with ALARA and fispact2 based on EAF 2010 database. The ALARA results are around 10~20% lower than fispact2, and some isotopes are also missing in ALARA results. And I also found that the results of dose from ALARA are generally 1000 times lower than fispact. Is this normal?
This may be due to the fact that the format of EAF 2010 libraries is not the same as the previous format and may not be compatible with ALARA. If you have information about the changes between these two libraries, we could consider updates to ALARA to support the newer EAF libraries.
The format of fendlg-2.0_175 and eaf_n_gxs_211_flt_20100 seems the same, expect the energy group change from 175 to 211. That's why I thought EAF 2010 library could be used directly.
This is the (n,γ) cross section for H1 in fendlg-2.0_175:
This is the (n,γ) cross section for H1 in eaf_n_gxs_211_flt_20100:
Do you get better results, matching your FISPACT calculations now? Please submit the code change as a PR if so.
If not, then the problem may occur in some specific cross-sections in the file, and perhaps related to different reaction pathways that are available in newer versions of the cross-sections. I wish we had made an issue at the time. Do @moatazharb or @makeclean remember this better than me?
I checked again and I found I made a mistake about FISPACT calculation, I used wrong spectrum. I recalculated natural Iron @1g/cc activation based on the right spectrum with FISPACT, and the results show that ALARA results (both total activaty and total decay heat) are around 5~10% higher than FISPACT, which depends on the cooling time. I'm not sure if this result is acceptable.
And still, some isotopes are missing in ALARA results. And I also found that the results of dose from ALARA are generally 1000 times lower than fispact. If the ALARA dose results time 1000, the results will also be around 5% higher than FISPACT. So is this mean that the ALARA dose results have a different unit instead of Sv/hr (the shown dose unit are Sv/h in both ALARA and FISPACT output) ?
I changed a few about the code, but I don't know how to submit the code change as PR, I am new to github.
I want to do more calculations to benchmark ALARA and FISPACT, maybe you expert could give me some advice?