POSYDON-code/POSYDON

[BUG]: Inconsistent Kicks during testing

Open

#764 opened on Nov 13, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (35 forks)auto 404
P1 - high prioritybughelp wanted

Repository metrics

Stars
 (42 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug When testing binaries it seems like the kick parameters are not being properly passed along to the SN step, so that binary outcomes may differ each time they are run, even when kick values are provided. This is a problem even for the validation binaries.

To Reproduce Run the validation binaries twice - the outcomes will be slightly different

Expected behavior The validation binaries ought to produce the exact same binary evolution results every time

POSYDON Version: Version 2.2

Additional context Add any other context about the problem here.

Contributor guide

Research direction
Investigate the kick parameter passing mechanism in the validation binary tests to ensure reproducible outcomes. Check if random seed or parameter propagation is inconsistent.
Tech stack
python
Domain
backendtesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60