How fitteia/onefit-engine works
OneFit Engine is a Raku fitting core exposed through a CLI and an optional Cro HTTP service. Its principal workflow is to receive a fit definition and experimental data, run nonlinear fitting, and produce plots or portable fit descriptions. The README documents major capabilities but no source excerpts were supplied, so internal call relationships are limited to documented workflow links; module assignments reflect the repository tree, not inspected implementations.
Main entry points: OneFit.rakumod Fit engine · onefite CLI · Import.rakumod Data import · Grammars.rakumod Model expressions
Components 16
User entry points
- CLI
bin/onefite - HTTP service
bin/onefite
Fit inputs
- Data import
lib/OneFit/Engine/Import.rakumod - Model expressions
lib/OneFit/Engine/Grammars.rakumod - Model functions
lib/OneFit/Engine/Functions.rakumod - Function aliases
lib/OneFit/Engine/Agrs.rakumod - Fit parameters
lib/OneFit/Engine/Parameters.rakumod
Fit runtime
- Fit engine
lib/OneFit.rakumod - Fit conditions
lib/OneFit/Condition.rakumod - Batch fitting
lib/OneFit/Batch.rakumod - CERNLIB MINUIT
Fit results
- Plots
lib/OneFit/Engine/Graphs.rakumod - Plot axes
lib/OneFit/Engine/Axes.rakumod - JSON/SAV descriptions
lib/OneFit/SAV.rakumod - Output archives
lib/OneFit/Engine/Archive.rakumod
Other components
- Fit user
Connections 9
- Fit user → CLI: runs fit
README.md - Fit user → HTTP service: uploads fit
README.md - CLI → Data import: loads data
README.md - CLI → Model expressions: defines models
README.md - CLI → Fit engine: runs fit
README.md - HTTP service → Fit engine: runs fit
README.md - Fit engine → CERNLIB MINUIT: fits with
README.md - Fit engine → Plots: produces plots
README.md - Fit engine → JSON/SAV descriptions: saves descriptions
README.md