You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PAHFIT can currently not work without specifying an instrument pack. This is a problem for cases where there is no reasonable instrument.
Example use case: seeing how a PAHFIT decomposition behaves, when fitted to a theoretical dust feature spectrum, for which the resolution of the grid is an arbitrary choice.
Perhaps a sort of 'trivial' instrument pack can be set up, with a fixed resolution and a user-specified range. At a minimum, it should be possible to read an instrument pack from the working directory of the user. They could then make a copy of a trivial instrument pack example, and adjust the wavelength range and resolution as needed
The text was updated successfully, but these errors were encountered:
I have some notes about a custom Instrument class, which users can use to craft their own simple instrument packs, if they so desire. This is a good idea down the road, and will be especially powerful with Model.tabulate: fit a (physical) model, then "reproject" it into a different instrument space. This is probably also a good reason to allow the instrument keyword to co-exist with (and override) the sp.meta['instrument']Spectrum1D information.
PAHFIT can currently not work without specifying an instrument pack. This is a problem for cases where there is no reasonable instrument.
Example use case: seeing how a PAHFIT decomposition behaves, when fitted to a theoretical dust feature spectrum, for which the resolution of the grid is an arbitrary choice.
Perhaps a sort of 'trivial' instrument pack can be set up, with a fixed resolution and a user-specified range. At a minimum, it should be possible to read an instrument pack from the working directory of the user. They could then make a copy of a trivial instrument pack example, and adjust the wavelength range and resolution as needed
The text was updated successfully, but these errors were encountered: