Smithsonian / Smithsonian/layup
layup orbitfit printing out to screen and log file
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 2
- Avg merge
- 1d 43m
- Merged PRs (30d)
- 58
Description
it seems like the log is going to both to standard output and the log. I think we really want it only going to the log only.
2026-08-31 13:51:45,338 - layup.orbitfit - 28371 - INFO - Processing 4135 rows for ['1979 HP']
2026-08-31 13:51:47,891 - layup.orbitfit - 28371 - INFO - Data has been written to ./demo_orbitfit_output.csv
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 running the layup orbitfit command and tracing its logging setup, using the sample INFO messages as the observable behavior. Done means orbitfit writes these messages to the log file without also printing them to standard output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100