Skip to content

Commit c2452dd

Browse files
authored
Merge pull request #395 from kbwestfall/cycle4_spec_workshop
Cycle 4 Funding: Spectroscopy Development Busy Week
2 parents 592fed6 + d8761e2 commit c2452dd

File tree

1 file changed

+83
-0
lines changed

1 file changed

+83
-0
lines changed
Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
### Title
2+
3+
Spectroscopy Development Busy Week
4+
5+
### Project Team
6+
7+
Kyle Westfall (UCO), Tim Pickering (MMT), Kelle Cruz (Hunter), Debora
8+
Pelliccia (UCO), Ricky O'Steen (STScI), Camilla Pacifici (STScI),
9+
Timothy Ellsworth-Bowers (Lowell), Stephanie Juneau (NOIRLab), [others
10+
welcome!]
11+
12+
### Project Description
13+
14+
In Nov 2023, we held a workshop at NOIRLab to discuss spectroscopy
15+
software, identify needs, and begin projects to address them; see our
16+
[report](https://docs.google.com/document/d/10i3VXiQE2AUF7EVSJ8-jm1nTMaRhudYUVq409b3daOo/edit?usp=sharing).
17+
18+
Since then, we've held monthly meetings where we continue the discussion
19+
and touch base on progress in an effort to maintain momentum. Although
20+
this effort has led to a number of specutils/specreduce PRs (both at the
21+
workshop and since), it remains difficult for us as a group to find time
22+
to make significant progress on the development goals we identified.
23+
Here, we propose to provide travel support for the attendees of one busy
24+
week, focused on final development pushes toward specutils/specreduce
25+
PRs. The idea is that, instead of funding small fractions of an FTE for
26+
a few people, we can support short bursts of collective effort from many
27+
people. These efforts will directly support development priorities in
28+
specutils and specreduce.
29+
30+
### Project / Work
31+
32+
The specific deliverables of this busy week are currently TBD.
33+
Possibilities include:
34+
35+
- Comparison of multiple wavelength-calibration algorithms pulled
36+
existing pipelines (DRAGONS, BANZAI, pypeit), and incorporated into
37+
specreduce.
38+
39+
- Similar work can be done for other algorithms, including sky
40+
subtraction, source extraction, coadding, flux calibration, etc.
41+
42+
- End-to-end example reduction performed using specreduce with a
43+
long-slit dataset
44+
45+
- Addition of algorithms specific to fiber-based spectrographs
46+
47+
Significant planning will go into the timing of the workshop and each
48+
development goal. We expect to support 4-6 groups of 3-5 people each,
49+
with each group having a specific deliverable that can reasonably be
50+
achieved during the busy week. Broader discussions about priorities and
51+
longer terms goals are inevitable, but the focus of the week will be to
52+
complete a goal that directly benefits from a focused collective effort.
53+
54+
Comments and advice on how to actually achieve the above are welcome!
55+
56+
### Approximate Budget
57+
58+
At minimum, the budget should support catering for lunches and coffee
59+
breaks during the busy week. A rough estimate is $4000, assuming ~$40
60+
per person per day for 20 attendess and a 5-day busy week. In this
61+
minimum funding scenario, all attendees would be reimbursed for their
62+
other meals (breakfast, dinner), hotel, and airfare by their home
63+
institutions.
64+
65+
At maximum, the budget would additionally provide full travel support
66+
for the attendees (airfare, hotel, meals). A rough estimate is $60k,
67+
assuming $3000 per person for a 5-day busy week and a US-domestic flight
68+
for 20 attendees.
69+
70+
The budget therefore ranges from $4k - $64k.
71+
72+
The extent of this range largely depends on the number of attendees and
73+
the level of travel reimbursement provided. Note that I haven't
74+
included venue rental fees in this estimate, under the assumption that
75+
the busy week can be hosted at someone's home institution at no cost
76+
(e.g., we could host it at UCO/UCSC in Santa Cruz).
77+
78+
### Period of Performance
79+
80+
This budget request is for a single 1 week meeting to happen within the
81+
year following when the project is approved.
82+
83+

0 commit comments

Comments
 (0)