Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for a resolution matrix #1155

Open
weaverba137 opened this issue Jul 19, 2024 · 1 comment
Open

Support for a resolution matrix #1155

weaverba137 opened this issue Jul 19, 2024 · 1 comment

Comments

@weaverba137
Copy link
Member

This is an enhancement suggestion, and a place to discuss the issues involved. Previously this idea was hand-written in a notebook, so not as accessible.

The resolution matrix as defined in Bolton & Schlegel (2010) has a number of useful properties:

  • It is an extension of the idea of a line-spread function, i.e. the uncertainty associated with the spectral_axis.
  • It reduces convolution and deconvolution to matrix multiplication. For example, model spectra can be convolved via the resolution matrix for comparison to the data (the extracted spectrum).
  • It simplifies the process of resampling a spectrum to a different spectral_axis.

Discussion is welcome. In particular, opinions on whether this should be included in the core specutils, or implemented as survey-specific subclasses of specutils objects. The latter will probably happen anyway, at least at first.

It would also be interesting to compare implementations. I know of DESI's (Guy et al. 2024), but would be interested to hear of others.

@jehturner
Copy link
Member

Just an off-hand comment... Although it might not be as relevant in specutils, there are probably applications for tracking spatial resolution as well (?), so I would be wary of a scheme that's difficult to generalize. Maybe consider whether the new attribute(s) could also go in NDData in some form and how different axes would be addressed? Of course spatial resolution may be less stable & harder to characterize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants