Fast Analysis IC310 ToO Feb Mar 2024 P062

From my_wiki
Revision as of 08:35, 5 June 2024 by Daniel.morcuende (talk | contribs) (Data-taking information)
Jump to: navigation, search

Fast analysis IC310 ToO P062 (March 2024)

General information

  • Name of the source: IC 310
  • Brief description of the source:
    • Object type : AGN radio galaxy
    • Redshift (z) : 0.0189
    • Other relevant information: Observations triggered LHAASO ATel #16513, 0.5 CU > 1 TeV (6th and 7th March 2024). VERITAS followup ATel #16535 (0.15 Crab units in 2 hours, 10th - 13th March 2024). LHAASO reported renewed activity in ATel #16540 (1.3 C.U. above 1 TeV in 19th March)
    • RA: 03 16 43.0 (hh mm ss), Dec: +41 19 29 (dd mm ss)
    • RA, Dec in deg (ICRS):

See also general wiki page of NGC1275 and IC310

  • Analysis by:
    • Daniel Morcuende (IAA-CSIC - dmorcuende@iaa.es)

Data-taking information

'2024-03-10': [17018, 17019, 17020, 17021, 17022, 17023]

Dl1 checks 20240310 event tagging.png

  • Joint observations with MAGIC? : No

Problems with wrong event tagging

Checking runs one by one in the DL1 check files like: https://www.lst1.iac.es/datacheck/dl1/v0.10/20240310/pdf/datacheck_dl1_LST-1.Run17020.pdf we can see when the event tagging went south. We filter out affected subruns as follows:

  • Run 17018: not usable at all (event tagging spoiled from the beginning of the run)

Check event rates run17018.png

  • Run 17019: not usable at all (event tagging spoiled from the beginning of the run)

Check event rates run17019.png

  • Run 17020: usable up to subrun ~68

Check event rates run17020.png

  • Run 17021: usable up to subrun ~95

Check event rates run17021.png

  • Run 17022: the whole run seems OK

Check event rates run17022.png

  • Run 17023: usable up to subrun ~74

Check event rates run17023.png

General analysis information

  • source-independent analysis
  • lstchain v0.10.7

Monte Carlo information

  • All-sky MC production used: 20240131_allsky_v0.10.5_all_dec_base
    • Declination line (training): dec_2276

DL1 data

LSTOSA standard production (v0.10/tailcut84) of DL1b run-wise merged files.

/fefs/aswg/data/real/DL1/YYYYMMDD/v0.10/tailcut84/dl1_LST-1.Run?????.h5

Random forest

Source declination is 12.3 deg. Two closest MC declination tracks are 9.31 deg and 22.76 deg. To avoid problems with a declination track with lower culmination than that of the data. I choose the 22.76 deg MC declination path which is the closest one to the source towards La Palma latitude value (28.8 deg)

/fefs/aswg/data/models/AllSky/20240131_allsky_v0.10.5_all_dec_base/dec_2276

DL2 data

Config file:


Files in:

/fefs/aswg/workspace/daniel.morcuende/data/real/DL2/PKS1725/dec_2276

DL3 data & IRF

 "EventSelector": {
   "filters": {
     "intensity": [50, Infinity],
     "width": [0, Infinity],
     "length": [0, Infinity],
     "r": [0, 1],
     "wl": [0.01, 1],
     "leakage_intensity_width_2": [0, 1],
     "event_type": [32, 32]
   }
 },
 "DL3Cuts": {
   "min_event_p_en_bin": 100,
   "min_gh_cut": 0.1,
   "max_gh_cut": 0.95,
   "min_theta_cut": 0.0,
   "max_theta_cut": 0.2,
   "fill_theta_cut": 0.2,
   "allowed_tels": [1]
 },
  • 70 % efficiency for both gammaness and theta gamma-ray selection cuts
  • Point-like IRF

High-level analysis

  • Gammapy 1.1
  • 1D analysis (point-like IRF)

Analysis Results

Theta2 plot

Settings (from explore DL2 notebook):

  • Theta2 cut for signal extraction < 0.02 deg2
  • Tight global cut gammaness > 0.95
  • 3 off positions
  • E > 500 GeV
  • Time effective: 1.8 h


  • 2024-03-10

Theta2 ic310 20240310 dmorcuende.png

No significant excess at energies below

Significance map

Spectral results

Light curve