DC2 KickoffDC2 is the second in a sequence of 3 Data Challenges. It is a 55 day simulation of the GLAST sky incorporating:
This increased detail and improvements of the detector simulation, event classification analysis, and the sky results in a much broader range of analysis options and data types than have been made available in previous data challenges and science tools checkouts. Links to Key Information: (linked from DC2 navbars???)
Data Challenge II Workshop
|
Data Challenge II Kickoff Meeting |
** Please let us know you are planning to attend! ** |
|
|
||||||||
|
|
||||||||
|
|
||||||||
|
|
To install the current DC2 code release for your platform (Red Hat Enterprise Linux 3, Scientific Linux 4, Macintosh, or Windows), go to:
Need buttons for: FT1, FT2 (Pointing Livetime
For an introduction to the types of LAT data, see LAT Data Products and FITS Files by David Band.
Definition of LAT Event Summary File (FT1) (for DC2) -need to copy current?? (for archive)??? -David, Masa???
Glast Data Server's LAT Data - DC2 Summary Ntuple - same data different formats for those who want to see the full set of events or who want to view them in an event display or want to do their analysis in ROOT.
GLAST Science Support Center - to access the following "precut" FT1 data, go to
GSSC's DC2 Data Access site:
- LAT Photon data
- All sky data files (data from the entire sky in ~1 week chunks)
- LAT Pointing History and Livetime data file - (popup to anchored frame in David's ???doc. Seth???Julie ???)
- Livetime cubes
- GBM Burst data
- Source Catalog
- DC2 Pulsar Ephemeris
- Galactic Diffuse Emission Model
Note: You can access either TCut EventClass A or TCut EventClass B data from this site.
Also see: Using the Glast Data Server
??? DC2 Data Portal (Preliminary). Welcome to the DC2 data portal. DC2 data represents 55 days of simulated data. The easiest way to get started is to use the pre generated data sets.
Welcome to the DC2 data portal. DC2 data represents 55 days of simulated data. The easiest way to get started is to use the pre generated data sets.
The following servers allow you to create your own custom datasets, with selected events, cuts, columns. They also allow you to access the full root-trees (digi, recon) and browse the data using the event display.
Astro Data Server (allows to select events by time, region in sky, etc).
Pruner (allows you to filter the Merit tuples by applying cuts, and selecting selected columns)
Peeler (allows you to select full root trees for specific events)
Note: EventClassA and EventClassB are the Quality flags mentioned on the Data Server page. … users choose ‘A’ or ‘B’ (what are they? and what do I do with that knowledge?)
BACKTRACK on the following: http://www-glast.slac.stanford.edu/software/AnaGroup/atwood-2006Jan9-DC2.pdf
You can download a copy of these TCut definitions from here (so no need to cut and paste from this page)
// required cuts for all event classes
TCut DC2Trigger="(GltWord&10)>0&&(GltWord!=35)";
TCut DC2Filter="FilterStatus_HI==0";
TCut DC2PrefilterCal="CalEnergyRaw>5&&CalCsIRLn>4";
TCut DC2AcdVeto="(AcdCornerDoca>-5&&AcdCornerDoca<50&&CTBTkrLATEdge<100)||((AcdActiveDist3D>0 || AcdRibbonActDist>0)&&Tkr1SSDVeto<2)";
// filter out high energy electrons (old definition)
// TCut DC2ElectronVeto="((min(abs(Tkr1XDir),abs(Tkr1YDir)) < .01 &&
// Tkr1DieEdge < 10 && AcdActiveDist3D > 0 && AcdActDistTileEnergy > .2) ||
//(Tkr1SSDVeto < 2 && AcdActiveDist3D > -3 && AcdActDistTileEnergy > .3) ||
//( AcdActiveDist3D >(-30 + 30*(Tkr1FirstLayer-2)))) && CTBBestEnergy > 5000";
// filter out high energy electrons
TCut DC2ElectronVeto="((min(abs(Tkr1XDir),abs(Tkr1YDir)) < .01 && Tkr1DieEdge < 10 && AcdActiveDist3D > 0 && AcdActDistTileEnergy > .2) || (Tkr1SSDVeto < 7 && AcdActiveDist3D > -3 && AcdActDistTileEnergy > .15) || ( AcdActiveDist3D >(-30 + 30*(Tkr1FirstLayer-2)))) && (CTBGAM+0.17*CTBBestLogEnergy)<1.75";
//filter out some events at low-med energy where the Track 2 starts higher up
//than Track 1.
TCut DC2AnotherVeto="(Tkr1FirstLayer - Tkr2FirstLayer) < 0 && Tkr2FirstLayer > 2 && Tkr2TkrHDoca>10 && (CTBGAM+0.16*CTBBestLogEnergy)<1.32 ";
//Heavy Ion Filter
TCut HeavyIonVeto = "CTBBestEnergy>1000 && (((CalTransRms-1.5)*Tkr1ToTTrAve)<5)&&CTBGAM>0.5";
//Anti-correlated filter
TCut AntiCorrVeto = "CTBBestEnergy<500&&((CalCsIRLn+2.5*Tkr1CoreHC/Tkr1Hits)<8 || (Tkr1CoreHC/Tkr1Hits)<0.03)";
//Cosmic proton filter
TCut ProtonVeto = "Tkr1FirstLayer<6&&AcdActiveDist3D>-80 && ((AcdActDistTileEnergy + AcdActiveDist3D/100)>1)";
//Global Ribbon Extension and AcdCornerDoca Extension
TCut GlobalRibbonVeto = "(AcdRibbonEnergy>0.2 && AcdRibbonActDist > -10) || (AcdCornerDoca >-5 && AcdCornerDoca<50 &&CTBTkrLATEdge<200)";
TCut DC2Vetos = DC2AcdVeto||DC2ElectronVeto||DC2AnotherVeto||HeavyIonVeto||AntiCorrVeto||ProtonVeto||GlobalRibbonVeto;
//------------------------------------------------------------------
//These are handy to use to make pruned tuples.
TCut Basic="CTBCORE>0.1&&CTBBestEnergyProb>0.1&&CTBGAM>0.";
TCut ratecut="CTBBestZDir<-0.3&&CTBBestEnergy>100";
//-------------------------------------------------------------
// Use one of the following to select an event class.
TCut DC2Base1="CTBCORE>0.1&&CTBBestEnergyProb>0.3&&CTBGAM>0.35";
TCut DC2Base2="CTBCORE>0.1&&CTBBestEnergyProb>0.1&&CTBGAM>0.55";
TCut DC2Base3="CTBCORE>0.35&&CTBBestEnergyProb>0.35&&CTBGAM>0.50";
// Final Analysis Classes
TCut GoodEvent1=(DC2Base1&&DC2Trigger&&DC2Filter&&DC2PrefilterCal)&&!DC2Vetos;
TCut GoodEvent2=(DC2Base2&&DC2Trigger&&DC2Filter&&DC2PrefilterCal)&&!DC2Vetos;
TCut GoodEvent3=(DC2Base3&&DC2Trigger&&DC2Filter&&DC2PrefilterCal)&&!DC2Vetos;
// For DC2 we propose using the GoodEvent1 and GoodEvent3 analysis classes.
// This allows the data to be divided into a set of nested event classes.
TCut EventClassA = GoodEvent3;
TCut EventClassB = GoodEvent1&&!GoodEvent3;
The effect of the trigger and filter settings on trigger and downlink rates is discussed in this confluence space. For DC2 we have decided to use configuration (2) for the trigger setting. This requires either a tracker (3-in a row) or a cal hi trigger and also requires for Tkr triggers, that either the acd throttle bit is not set or cal-lo is set. For the onboard filter we require that FilterStatus_HI==0.
Mailing List; Confluence Forum;
General Information DC2 Planning Outline Steve Ritz's DC1-DC2 Plan Steering Committee Meetings Schedule
DC-2 DataCurrent merit ntuple (GR v7r0p2)Pipeline StatusFTP access to MC runsGLAST data server
Communications DC-2 e-mail list archives
(need GLAST user ID/password)Confluence pages
Useful Information LAT Analysis/Calibration Group
Last updated by: Chuck Patterson 02/27/2006 |
Note: Test link: for page review purposes only.
http://glast-ground.slac.stanford.edu/workbook/science-tools/pages/DC2/dc2_Kickoff.htm