Problem
Delay fitting is implemented in the library layer but not exposed through the CLI configuration system:
- DCE:
fit_model() in osipy/dce/fitting.py accepts fit_delay (bool) and uses _DelayAwareModel with default bounds (0.0, 60.0), but DCEFittingConfig has no corresponding fields.
- DSC: Delay maps are computed and exported (
osipy/dsc/parameters/maps.py), but there is no config to control delay-related behavior.
Users cannot enable or configure delay fitting through YAML config files or the CLI.
Proposal
Add the missing delay-related fields to the Pydantic config classes:
DCEFittingConfig: add fit_delay: bool = False and delay_bounds: tuple[float, float] = (0.0, 60.0)
- Wire these fields through the runner (
osipy/cli/runner.py) so they are passed to fit_model()
- Add equivalent fields to DSC config if applicable
Affected code
osipy/cli/config.py — DCEFittingConfig, DSCPipelineYAML
osipy/cli/runner.py — where config values are passed to fitting functions
🤖 Generated with Claude Code
Problem
Delay fitting is implemented in the library layer but not exposed through the CLI configuration system:
fit_model()inosipy/dce/fitting.pyacceptsfit_delay(bool) and uses_DelayAwareModelwith default bounds(0.0, 60.0), butDCEFittingConfighas no corresponding fields.osipy/dsc/parameters/maps.py), but there is no config to control delay-related behavior.Users cannot enable or configure delay fitting through YAML config files or the CLI.
Proposal
Add the missing delay-related fields to the Pydantic config classes:
DCEFittingConfig: addfit_delay: bool = Falseanddelay_bounds: tuple[float, float] = (0.0, 60.0)osipy/cli/runner.py) so they are passed tofit_model()Affected code
osipy/cli/config.py—DCEFittingConfig,DSCPipelineYAMLosipy/cli/runner.py— where config values are passed to fitting functions🤖 Generated with Claude Code