Difference between revisions of "C-WAYS Fall work"

From CoolWiki
Jump to navigationJump to search
(Created page with " =Sep 6, 2012= file:email20120906.txt - email from luisa with tasks and timeline questions from here on out Notes from telecon: *if you can get your image assessements i...")
 
m
Line 12: Line 12:
 
* in any case, we need to get moving on the photometry on the spitzer images in the next 2-3 weeks.
 
* in any case, we need to get moving on the photometry on the spitzer images in the next 2-3 weeks.
  
==SED task==
+
=SED task - given 9/6/12, due 9/13/12=
  
 
here is the list of SEDs to make more or less by hand.
 
here is the list of SEDs to make more or less by hand.

Revision as of 23:56, 7 September 2012

Sep 6, 2012

File:Email20120906.txt - email from luisa with tasks and timeline questions from here on out

Notes from telecon:

  • if you can get your image assessements into the google doc in the next few days, i'll look at them all on monday and see if we can drop anything obviously bad.
  • i will pick a good set of seds tonight - 10 objects for everyone to make to show that they can do it, they can understand the concepts involved. those 10 will be picked to start training your brain on 'good' and 'bad' seds. those seds due next thursday.
  • bob will lead the edu poster; lauren will lead the sci poster. first drafts of those abstracts also due next thursday.
  • we will start looking at my seds and weeding based on those seds for the subset that survive the image weeding process starting next thursday, hopefully to be done in a week or at most 2.
  • not sure what to do re: optical data. do we have access to new data from HI (any of the telescopes)? or should we try PTF? or just go with what we have from last year as a place to start?
  • in any case, we need to get moving on the photometry on the spitzer images in the next 2-3 weeks.

SED task - given 9/6/12, due 9/13/12

here is the list of SEDs to make more or less by hand.

i tried to pick a range of shapes, range of kinds of data, range of new/known, etc. some of these will have optical data (of two different kinds!), as well as NIR (2mass) data, WISE, and sometimes Spitzer data. i recommend doing them in this order, or at least trying to interpret them in this order, because i buried some tricky ones in here.

guidelines:

  • start with your notes from july and the full catalog i gave you (at least i think i gave you) that has ALL the bands currently in my master DB, optical through 70 um. if you can't find it, it's still here:

http://web.ipac.caltech.edu/staff/rebull/working/tuesAMsourcelists/

  • fall back on the Units page to look for a first pass at explanations and steps (see especially section 3.3)
  • rely on the Central wavelengths and zero points page to look up wavelengths and zero points
  • don't forget that AB magnitudes are different than Vega magnitudes.
  • email questions when you have them; we can't necessarily save them all for next thursday if they are showstopping issues!
  • when you are ready to interpret the SEDs (either as you go along or all at once after making these), you want to look for things that look like the 'template' SEDs (see [here] or my talk from july). things that don't look like the template, or things that don't have enough data to decide if they look like the template, or things that are missing bands.. those are the ones you want to note as "junk" or "check" or "wth?" etc.
  • when you set about interpreting these, you want to incorporate the knowledge we have already accumulated to this point. why are they in the short list of things we care about? (separate from "why did luisa put them in the list for us to do?" :) what i mean is "are they previously identified objects and/or are they objects xavier's color selection picked out?") what did we already note about these objects in the images?

ok, so, please try making SEDs for the objects with the following internal numbers:

  • 373
  • 1364
  • 1410
  • 1491
  • 1563
  • 483
  • 826
  • 1547
  • 1399
  • 1261
  • 1535

hopefully this will not be TOO painful. . . :)