Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

Description of the problem

Images

Resolution

2024-05-10

Run1736

2024-05010

Run17387,

MAGIC lidar event.

High intensity laser beams are emmitted priodically. Its scatterd light is detected by LST.

image-20240823-003358.png

image-20240823-004846.png

report as “lidar-like events”. These runs are categolize “low quality runs” instead of “anomaly runs”.

2024-05-17

Run17131

A bright light illuminate camera.

image-20240823-004013.png

report as “car-flash like events” in the category of “low quality runs”.

2024-06-10

Run17740, 17741

Bright light continuously iluminate telescope. The bright light is sometime come from the domitory, and sometime caused in the air as a airglow.

image-20240823-004419.png

image-20240823-004619.png

report as “bright light” in the category of “low quality runs”.

2024-05-06

Run1733

All event is tagged into three categories: Flat Field (FF), Pedestal, cosmic. However, this tagging can sometimes fail. It suddenly malfunctions during observation. It seems to occur when there are bright events like LIDAR or car flash.

image-20240823-004944.pngimage-20240823-004951.png

Notice it to exparts and report as “wrog enent tagging in the category of “anomaly runs”.

2024-05-14

Run17409

Calibration run

image-20240823-005413.png

Exclude from the daily check report.

2024-07-07

star trails forms circle on the camera, when the telescope looking near the zenith.

image-20240826-040714.png

this is nomarl. no need to report.

2024-06-23

Run 17779

staraight-line image of star trails.

image-20240826-041004.pngimage-20240826-041012.png

if observation is drift scan, this is nomal. if not , telescope may lost target position. report it to experts.

2024-05-05

run 17310

if tracking get wrong, or the telescope lost the target postion, the start track can be like a shooting star.

image-20240826-041318.png

repro it to experts

2024-06-12

when Pedecal run has a trouble, hole DL1 files of this night were affected.

image-20240826-041520.png

This should be written in the report.

2024-06-13

Run17778

Wrong setting caused by stereo trigger test.

image-20240826-041719.png

explain it in the comment.

2024-08-26

Run18676-18691

FF charge values are about 60 pe in all RUNs which is lower than that in the past. In particular, the last two RUNs are even lower.

FF rel. time values for many pixels are high in all RUNs.

20240826-muraishi.png

explain it in the comment.

This is caused by faild calibration, which is performed at begingin of the observation. The reason of this failure is unknown.

2024-08-29

Run18728,18732

The telescope altitude anomaly and the change in the cosmic fraction (>10pe) seem to have occurred at the same time.

20240829-muraishi.png

explain it in the comment.

2024-08-26,

every observation

part of FF events are tagged as comsimc. This is constanty happening.

nothing to do.

  • No labels