warnings.log
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue names only warnings.log and does not identify a source file, test, fitting entry point, or target parameters. Start by locating where fitting is performed and where warnings.log is written; clarify which fit should be saved and define completion criteria before changing anything.
Written by the indexing model from the issue text.
Description
find good parameters to save the fit into warnings.log
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from FireDynamics/LEDSmokeAnalysis
-
Use Vertical Images Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FireDynamics/LEDSmokeAnalysis#133 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
FireDynamics/LEDSmokeAnalysis#132 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
FireDynamics/LEDSmokeAnalysis#115 ·
-
Fix error that nonlinear parameters might be required in config_analysis even for linear analysis Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
FireDynamics/LEDSmokeAnalysis#110 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
FireDynamics/LEDSmokeAnalysis#105 ·
All issues in FireDynamics/LEDSmokeAnalysis
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100