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
Rebuilder outputs x and y values to make a histogram for B0 values (#B0_dist in res.csv). The range of the x values for this output is set internally. When including alternative starting conditions (when "# Conduct projections with multiple starting values" equals yes) Ive noticed that the x range of potential outputs for B0 can be truncated. This means that multiple unique B0 values can be bunched up at the ends of the range of x values for the histogram. This results in a stacking of multiple unique B0 values. This makes the results appear incorrect, but based on some tests and looking at the histograms for Tmin-Yinit and Tmax-Yinit, which are also rebuilder output, the B0 histogram appears correct, just reported out with a poor range for the x values.
The fix to this would be to go into the fortran code for rebuilder, and confirm the issue. I am not currently planning to do that, as thus far it seems to be a reporting issue and not an actual bug. Im noting this issue here in hopes it may help others who notice this as well.
The text was updated successfully, but these errors were encountered:
Rebuilder outputs x and y values to make a histogram for B0 values (#B0_dist in res.csv). The range of the x values for this output is set internally. When including alternative starting conditions (when "# Conduct projections with multiple starting values" equals yes) Ive noticed that the x range of potential outputs for B0 can be truncated. This means that multiple unique B0 values can be bunched up at the ends of the range of x values for the histogram. This results in a stacking of multiple unique B0 values. This makes the results appear incorrect, but based on some tests and looking at the histograms for Tmin-Yinit and Tmax-Yinit, which are also rebuilder output, the B0 histogram appears correct, just reported out with a poor range for the x values.
The fix to this would be to go into the fortran code for rebuilder, and confirm the issue. I am not currently planning to do that, as thus far it seems to be a reporting issue and not an actual bug. Im noting this issue here in hopes it may help others who notice this as well.
The text was updated successfully, but these errors were encountered: