Wednesday 11 October, 14:00-15:00 Project time:  BlueJeans #103047236

Attendees:

Agenda:

  • Logistics: bootcamp dinner, refreshments
  • Finalize goals
  • Discussion of candidate tasks
  • Identification of relevant datasets for candidate tasks
  • Collecting results of bootcamp.  Is a repository in the lsst organization doable?
  • AOB

Minutes:

Logistics:

There will be no banquet, but we will try to facilitate outings for meals.

Goals:

We have agreed as they stand.

Tasks:

KB: I need to understand where to tell people to start.

KSK: Should we go from Merlin's chart

SR: The chart is great, but we need to come up with a list of a few things where we can make real progress on them.

MFL: gain and linearity are a great place to start by comparing different methods.

MFL: Use the stack to reduce data from the group in France.

SR: We can get a long way toward convincing people to move toward using DM tools by showing that the results coming from the stack agree with the analysis coming out of the camera tools.

Pre-bootcamp checklist:

Simon already has a task to start filling this out.
SR: we should all fill it out together  SK: that's great.  I'll give it a start. 

Data:

  • Steve Ritz can you choose runs to use?  They will need both Fe55 and flats at various illumination.  It seems reasonable to look at data from the same sensors in each run (I don't know if multiple rafts have been run through).  Merlin mentions it might be interesting to have available both "good" and "bad" data, so we get a sense of the dynamic range of these effects. 
  • No labels

2 Comments

  1. I added more references, and expanded the first task. I'd be happy to go over this in our next call. Feedback welcome in the meantime. The second item needs more detail than can fit in a table, and I will set up a separate confluence page for it later this week. The third item does not need any expansion, I think – we just need to confirm how we want to capture the bread crumbs. I'd appreciate revisiting that in our call this week, too. Thanks.

  2. I communicated the runs to use in Slack.