You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the fluxin file lacks one float, it can still read it with the last value being zero, or repeated. For example, ALARA will read this file perfectly fine, for a 175-group flux, while it lacks one datapoint, and fill the last value with zero.
Is this a feature request to allow ALARA to read files that are short on data? I think one problem may be that if you have multiple locations and they are all short data from one group, then the data will be wrong. The first data from point 2 will be loaded as the last data for point 1, etc...
sorry for the late reply, I think ALARA should error and say something like the fluxin values are inconsistent with the energy groups. Unless there's a specific reason it's designed this way..?
If the fluxin file lacks one float, it can still read it with the last value being zero, or repeated. For example, ALARA will read this file perfectly fine, for a 175-group flux, while it lacks one datapoint, and fill the last value with zero.
After some testing, it seems like moving the eof check to after the reading statement solves this problem.
The text was updated successfully, but these errors were encountered: