NatLabRockies / NatLabRockies/SAM
Azimuth tracking results differ with one and two subarrays
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 486
- Forks
- 219
- Avg merge
- 10h 10m
- Merged PRs (30d)
- 2
Description
Potential bug with either tracking or subarrays or MPPT inputs
Steps to reproduce the behavior:
- Use SAM 2025.4.16 or later
- Open SAM file here
- Run all cases
- Compare inputs and outputs
Input comparison
Output comparison
Expect results to be the same
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 by opening the attached SAM_2126.zip in SAM 2025.4.16 or later and running all cases. Compare the inputs and outputs for one and two subarrays, then trace whether tracking, subarrays, or MPPT inputs cause the discrepancy; done when equivalent cases produce the same results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100