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.

Sign up for GitHub

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

Jump to bottom

Cycle 4: Specreduce and other spectrocopy work (Pickering) #381

Merged
merged 2 commits into from
May 6, 2024
Merged

Cycle 4: Specreduce and other spectrocopy work (Pickering) #381

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4dc37e2
draft of specreduce cycle4 proposal
tepickering Feb 29, 2024
6f33af1
remove travel from budget, per request
tepickering Mar 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
28 changes: 28 additions & 0 deletions finance/proposal-calls/cycle4/pickering_specreduce.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
### Title

Development, Coordination, and Community Engagement involving specreduce and other spectroscopy-related tools by Timothy Pickering

### Project Team
Timothy Pickering

### Project Description
This is to continue specreduce development and outreach that was carried out in previous cycles.

### Project / Work
Some specific areas that we expect to tackle during the coming cycle include:

* Generic manual wavelength calibration classes (i.e. analogs to "identify" from iraf, should use previous specreduce tools for this where possible)
* Automatic wavelength calibration using existing templates (i.e. "reidentify", or "full template" from pypeit)
* Improved WCS tools and expanded examples of their use within spectroscopic contexts
* Support for / workflows with multi-object spectrographs
* Support for fiber-based spectrographs, both single and multi-object as well as fiber-based IFUs
Comment on lines +14 to +18
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will these result in PRs to specutils, specreduce, both, or none?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will these result in PRs to specutils, specreduce, both, or none?

specreduce definitely, specutils possibly if it would make the most sense in specific cases. gwcs is another possibility if more attention is given to its spectroscopy-related functionality.

* Continued/expanded outreach to observatories and software projects (e.g. PypeIt) to improve integration and workflows
* Expand outreach to and collaboration with EPRV spectroscopy community

### Approximate Budget
Currency: US $46000

- Salary: US $46000 ($23000/yr based on 4 hours/week for 48 weeks at current contracted rate of $120/hour)

### Period of Performance
2 years starting May 2024