Open drvdputt opened 1 year ago
Yeah, guess
pretty much is required to change the model, since it is a warm-up to fit
. And fit
can be a prelude to another fit
, e.g. on the next spectrum over in the cube. We can leave this open for a while, but I think a better approach is to tweak Features
so it gives indication about:
Features
, which can go in features.meta['history']
or similar. Updated when: read from yaml (which one), guessed with a spectrum (mention which guess model, and which spectrum/instrument(s)), fitted to a spectrum, etc. Feature
's FWHM line values.
In our current design, the model details, fit settings and fit results are put together in the Model class. This brings some complexity with it:
Alternative design
Possible issues with this:
We're not going to change this now, since we really need to get PAHFIT running. But I really wanted to write this down, and we should keep this type of redesign in mind if we run into more symptoms of the same underlying conceptual problem.