COSMIC silently drops systems

[nsabrams]

I'm having an issue where some systems don't make it through evolution. In the bcm table there are some systems with a first row, but not a last row. This is similar to the issue I raised with metallicity being outside of the range, but I'm not sure what's going wrong here. I've attached the initC file and I'm using the default BSEDict.

initC_fail.csv

[nsabrams]

FYI here's the system specifically that's failing

305_in_initC_fail.csv

[TomWagg]

@nsabrams I can't seem to reproduce this with v3.7.5 - is that the same version you're using? When I run binary 305 from this initC I still get a full bpp and bcm output.

[nsabrams]

@TomWagg I'm indeed using v3.7.5. Here's the larger call if that's helpful

`self.BSEDict = {
"pts1": 0.001, "pts2": 0.01, "pts3": 0.02, "zsun": 0.014, "windflag": 3,
"eddlimflag": 0, "neta": 0.5, "bwind": 0.0, "hewind": 0.5, "beta": 0.125,
"xi": 0.5, "acc2": 1.5, "LBV_flag": 1, "alpha1": 1.0, "lambdaf": 0.0,
"ceflag": 1, "cekickflag": 2, "cemergeflag": 1, "cehestarflag": 0,
"qcflag": 5,
"qcrit_array": [0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0],
"kickflag": 5, "sigma": 265.0, "bhflag": 1, "bhsigmafrac": 1.0,
"sigmadiv": -20.0, "ecsn": 2.25, "ecsn_mlow": 1.6, "aic": 1, "ussn": 1,
"polar_kick_angle": 90.0,
"natal_kick_array": [[-100.0, -100.0, -100.0, -100.0, 0.0], [-100.0, -100.0, -100.0, -100.0, 0.0]],
"mm_mu_ns": 400.0, "mm_mu_bh": 200.0, "remnantflag": 4,
"fryer_mass_limit": 0, "mxns": 3.0, "rembar_massloss": 0.5,
"wd_mass_lim": 1, "maltsev_mode": 0, "maltsev_fallback": 0.5,
"maltsev_pf_prob": 0.1, "pisn": -2, "ppi_co_shift": 0.0,
"ppi_extra_ml": 0.0, "bhspinflag": 0, "bhspinmag": 0.0, "grflag": 1,
"eddfac": 10, "gamma": -2, "don_lim": -1, "acc_lim": -1, "tflag": 1,
"ST_tide": 1,
"fprimc_array": [2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0,2.0/21.0],
"ifflag": 1, "wdflag": 1, "epsnov": 0.001, "bdecayfac": 1,
"bconst": 3000, "ck": 1000, "rejuv_fac": 1.0, "rejuvflag": 0,
"bhms_coll_flag": 0, "htpmb": 1, "ST_cr": 1, "rtmsflag": 0
}

self.z_solar = 0.02
binary_pop = InitialBinaryTable.InitialBinaries(m1=m1s, m2=m2s, porb=porbs,
ecc=eccs, tphysf=[10logAge/1e6]len(m1s),
kstar1=kstar1s, kstar2=kstar2s, metallicity=[self.z_solar10metallicity]*len(m1s))

bpp, bcm, initC, kick_info = Evolve.evolve(initialbinarytable=binary_pop, BSEDict=self.BSEDict)
`
I haven't included the definition of m1, m2 etc since they're from SPISEA tables, but I can paste that in if it's helfpul too.

If you're not able to reproduce it, what could I produce that could help debug it?

[nsabrams]

After switching the BSEDict zsun to 0.02 this binary no longer failed. Here's another one I've run into that's failing though

failed_binary.csv
initC_fail.csv