Cycle 4: Specreduce and other spectrocopy work (Pickering) #381
Conversation
|
Please remove travel from this request. Since SPIE is coming up soon, I would recommend opening an issue (separate from Cycle 4) for that request. |
done and done. |
|
While obviously we'd love to fund this for the full amount listed, if we need to squeeze the budget is there a minimum number of hours that would make sense? |
|
Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0) |
| * 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 |
There was a problem hiding this comment.
Will these result in PRs to specutils, specreduce, both, or none?
There was a problem hiding this comment.
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.
i was traveling so didn't get a chance to follow up on this. i would say 1 hr/week would be kind of the bare minimum to cover maintainer duties with no extra development time. i can amend my proposal to say this if there's time and it would be useful. |
|
Hi Tim, I'm writing on behalf of Astropy's Finance Committee regarding the outcome of your funding request. I will shortly open a new issue to track the progress. We are pleased to be able to let you know that, following consultation with the community, we are able to approve this request. We can currently fund the Year 1 amount of $5,760 (US) to carry out the project. Funding beyond this amount will be contingent upon the availability of funds. (We will be using the full budgets of all of the approved requests to craft future grant and funding proposals.) We assume you will be using this full year 1 budget, if that is not the case please contact us immediately. Ana Gabela and I will be your contacts on the Finance Committee to facilitate this award. Please get in touch with us if you have any questions or concerns. Please do not reach out to NumFOCUS directly. In addition, new to this funding cycle, is the assignment of a COTR (Contracting Officer's Technical Representative) to each funded project. This concept is borrowed from government funding agencies, although it is to be stressed that Astropy's goal is to make the COTR role as low-overhead as possible. The COTR’s primary responsibility is to make sure the work is happening at the expected pace and, if necessary, to be a liaison between the funded project and the Finance Committee or CoCo. The COTR for your project will be assigned shortly and we’ll also be sending out more details about how we see this working. The next steps are:
Congratulations --- we are really looking forward to seeing you put these funds to good use! Kelle, on behalf of the Astropy Finance Committee |
Proposal to continue on with specreduce and other astropy-related spectroscopy efforts.