POSYDON-code / POSYDON-code/POSYDON

[BUG]: Another Binary Step Exceeded Allotted Time: 120

Open
#741 2 comments 0 reactions 1 assignee View on GitHub

@maxbriel is already working on this.

Since Oct 30, 2025.

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

Description

Describe the bug
A binary reaching:
RuntimeError: Binary Step Exceeded Allotted Time: 120

To Reproduce

from posydon.binary_evol.binarystar import BinaryStar, SingleStar
from posydon.binary_evol.simulationproperties import SimulationProperties
from posydon.popsyn.io import simprop_kwargs_from_ini


sim_kwargs = simprop_kwargs_from_ini('run_0.ini', verbose=True)
metallicity = {'metallicity':0.1, 'verbose':True}

sim_kwargs['step_HMS_HMS'][1].update(metallicity)
sim_kwargs['step_CO_HeMS'][1].update(metallicity)
sim_kwargs['step_CO_HMS_RLO'][1].update(metallicity)
sim_kwargs['step_CO_HeMS_RLO'][1].update(metallicity)
sim_kwargs['step_detached'][1].update(metallicity)
sim_kwargs['step_disrupted'][1].update(metallicity)
sim_kwargs['step_merged'][1].update(metallicity)
sim_kwargs['step_initially_single'][1].update(metallicity)

sim_pop = SimulationProperties(**sim_kwargs)

sim_pop.load_steps(verbose=True)

star_1 = SingleStar(**{'mass':  7.082482087008959 , 'state': 'H-rich_Core_H_burning','metallicity':0.1,
                'natal_kick_array': [38.32237608078092, 6.0368730380460205, 1.848568130755055,6.2160086037434565]})
star_2 = SingleStar(**{'mass': 2.6379543729221413 , 'state': 'H-rich_Core_H_burning','metallicity':0.1,
                'natal_kick_array': [None, None, None, None]})
binary = BinaryStar(star_1, star_2, **{'time': 0.0,  'state': 'detached',  'event': 'ZAMS', 
                        'orbital_period': 115.08514438464961 ,'eccentricity': 0.0}, properties = sim_pop)

binary.evolve()

You might have to rerun the binary, based on the secondary kick.

Expected behavior
Should probably reach max_time, since the secondary is very 2.7 Msun at after the first star becoming a NS.

POSYDON Version:
V2.2 PR

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.