hfact uses wrong loss power index
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 27
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 33
Description
This will only work for the selected scaling if the loss power index is (1-0.31), so really just the IPB98 scalings in this case
Originally posted by @chris-ashe in #4396
@chris-ashe please feel free to update the title and issue body since you know what the actual issue is
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in process/models/physics/confinement_time.py around lines 953-966 and trace how hfact selects the loss power index for each scaling. Compare the selected-scaling logic with the IPB98 case described in the issue. Done means hfact uses the appropriate loss power index rather than assuming 1-0.31.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100