Difference between revisions of "TRAN02"
(→Proposal) |
(Fix typos and add some info for joint observations.) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 6: | Line 6: | ||
Coordinates differ case to case. They will be computed and given by the Transient Handler (TH). <br> | Coordinates differ case to case. They will be computed and given by the Transient Handler (TH). <br> | ||
| − | When an observable alert is received, an alert notification | + | When an observable alert is received, an alert notification will be visible in TCU. If the notification is accepted, a structure configuration with the target coordinates will be created in the TCU database and they can be used to schedule observations. |
| + | |||
| + | For any question regarding observation, ask the Burst Advocate (BA) on duty (names available [https://www.lst1.iac.es/operations/transients/burst_advocates/ here]), or write on the slack channel ''#lst1-alert-followup''. | ||
=== Observational settings/limits === | === Observational settings/limits === | ||
| − | The observational limits are part of the TH algorithm that defines if the source is observable or not. If the source | + | The observational limits are part of the TH algorithm that defines if the source is observable or not. If the source fulfills these parameters it will be considered observable: |
*Max Zenith: 70deg (preferred <60deg) | *Max Zenith: 70deg (preferred <60deg) | ||
| Line 18: | Line 20: | ||
*Night Sky: dark/twilight | *Night Sky: dark/twilight | ||
| − | Joint observation with MAGIC is preferable, when possible. | + | Joint observation with MAGIC is preferable, when possible. Since the transient handlers of MAGIC and LST are independent, and also with slightly different criteria, the joint observations should be coordinates by the LST shift crew with the MAGIC one. |
=== Extensions === | === Extensions === | ||
| − | If the Real Time Analysis shows more than 3sigma, extend for 3h. | + | If the Real Time Analysis shows more than 3sigma, extend for 3h and alert the BA on duty. |
| − | |||
=== Automatic procedure === | === Automatic procedure === | ||
When an alert is tagged as observable within 1h from when is received, TCU will automatically schedule the observation and repoint/configure the telescope at the scheduled time. | When an alert is tagged as observable within 1h from when is received, TCU will automatically schedule the observation and repoint/configure the telescope at the scheduled time. | ||
Latest revision as of 08:12, 10 July 2023
Proposal[edit]
Proposal: TRANS02:Gamma-ray burst observations
PI: Alice Donini (alice.donini@inaf.it)
Source:
Coordinates differ case to case. They will be computed and given by the Transient Handler (TH).
When an observable alert is received, an alert notification will be visible in TCU. If the notification is accepted, a structure configuration with the target coordinates will be created in the TCU database and they can be used to schedule observations.
For any question regarding observation, ask the Burst Advocate (BA) on duty (names available here), or write on the slack channel #lst1-alert-followup.
Observational settings/limits[edit]
The observational limits are part of the TH algorithm that defines if the source is observable or not. If the source fulfills these parameters it will be considered observable:
- Max Zenith: 70deg (preferred <60deg)
- Wobbles: standard
- Night Sky: dark/twilight
Joint observation with MAGIC is preferable, when possible. Since the transient handlers of MAGIC and LST are independent, and also with slightly different criteria, the joint observations should be coordinates by the LST shift crew with the MAGIC one.
Extensions[edit]
If the Real Time Analysis shows more than 3sigma, extend for 3h and alert the BA on duty.
Automatic procedure[edit]
When an alert is tagged as observable within 1h from when is received, TCU will automatically schedule the observation and repoint/configure the telescope at the scheduled time.
