Open celiotine opened 1 month ago
use_interp_values
to exclude that the slight change in primary mass during its CC don't move the secondary out of the problematic regime, which might be tight.Sure, here is the evolution re-evolving from oRLO2. The outcome is similar to above:
With use_interp_values = True
:
Re-evolved from oRLO2 w/ use_interp_values = False
:
The SN type for the secondary in both cases is CCSN.
OK, thanks. Do we save the interpolation class for the compact object formation? If so, is this the same as well?
I cannot find a way to access the CO interpolation class from the history?
@celiotine would you be able to check if this is still an issue, once the IF interpolator fix is implemented?
Yeah I can do this, will update once completed.
When running with
use_interp_values = True
in the SN settings, there is incorrect handling of some remnant masses. Specifically, these objects are either being misclassified as BHs or are assigned incorrect remnant masses. An example binary where this behavior is present is:Quest .ini file path:
/projects/b1119/cliotine/dev_general/debugging/params_Monica.ini
This is the behavior when running with
use_interp_values = True
(S2 BH is way too low mass or is actually a NS):This is the behavior when running with
use_interp_values = False
(S2 BH looks fine):