POSYDON-code / POSYDON-code/POSYDON

[BUG]: Failed binaries in stop at condition in step MESA

Open
#555 5 comments 0 reactions 2 assignees View on GitHub

@sgossage is already working on this.

Since May 29, 2025.

bug
Dominant language
Python
Stars
45
Forks
37
Avg merge
8d 20h
Merged PRs (30d)
5

Description

Describe the bug
I have run populations with max time of 100Myr using the NN interpolation method for HMS-HMS and keep getting failed binaries in mass ranges of 5-7 M_sun.

The error output is this:
Traceback (most recent call last):
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/popsyn/binarypopulation.py", line 328, in _safe_evolve
binary.evolve()
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/binary_evol/binarystar.py", line 222, in evolve
self.run_step()
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/binary_evol/binarystar.py", line 249, in run_step
next_step(self)
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/binary_evol/MESA/step_mesa.py", line 1651, in call
super().call(binary)
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/binary_evol/MESA/step_mesa.py", line 339, in call
self.stop_at_condition(binary,
File "/blue/jeffrey.andrews/kasdaglie/POSYDON/posydon/binary_evol/MESA/step_mesa.py", line 1066, in stop_at_condition
v_before = property_history[i]
~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range

To Reproduce
Failed Binary Initial Conditions:
S1 mass: 5.742705404717135
S2 mass: 6.728080259146756
S1 state: H-rich_Core_H_burning
S2 state: H-rich_Core_H_burning
orbital period: 84.29257755578446
eccentricity: 0.4264794095625973
binary state: detached
binary event: detached
S1 natal kick array: [None None None None]
S2 natal kick array: [nan nan nan nan]

Expected behavior

Screenshots

POSYDON Version:
Current development with extended v2 grid

System Configuration (please complete the following information):
HPC scheduler [e.g., SLURM]

Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.