I was using CSV logs for quick testing of the systems mentioned in the discussion about HeSDs, when I noticed that the output for BSE_Supernovae looks quite nice for the first few columns (data type, physical unit, and column name are aligned) but breaks down for Unbound. There seems to be a mismatch between the characters assigned for the column name and the corresponding data value. Of course, this is irrelevant whenever the file is read, as the comma delimiters still work... but I'm raising the issue in case it is simple enough to fix without too much effort.
Note: I briefly looked at BSE_RLOF and the issue seems to be there as well, but for RLOF(1)>MT, RLOF(2)>MT, Merger, and CEE>MT. Perhaps it is a more widespread issue.
That aside, the binding energy (BSE_Common_Envelopes) seems to go crazy for those same systems (as shown in the CSV files, at least). Of course, I don't think it makes sense to look at those columns after a SN episode, but it is pretty odd to suddenly see something like 455684824239092931467039630704766552312498880512.000000000000000 (possibly a memory waste as well?).
I was using CSV logs for quick testing of the systems mentioned in the discussion about HeSDs, when I noticed that the output for
BSE_Supernovaelooks quite nice for the first few columns (data type, physical unit, and column name are aligned) but breaks down forUnbound. There seems to be a mismatch between the characters assigned for the column name and the corresponding data value. Of course, this is irrelevant whenever the file is read, as the comma delimiters still work... but I'm raising the issue in case it is simple enough to fix without too much effort.Note: I briefly looked at
BSE_RLOFand the issue seems to be there as well, but forRLOF(1)>MT,RLOF(2)>MT,Merger, andCEE>MT. Perhaps it is a more widespread issue.That aside, the binding energy (
BSE_Common_Envelopes) seems to go crazy for those same systems (as shown in the CSV files, at least). Of course, I don't think it makes sense to look at those columns after a SN episode, but it is pretty odd to suddenly see something like455684824239092931467039630704766552312498880512.000000000000000(possibly a memory waste as well?).