Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Scheduling Units Failure and Re-submission

It is possible that a task after observing has failedan observing session fails. This can be either due to not meeting matching the requirements specified in the tasks or due to external circumstances (e.g. observing conditions poor). This requires the FoP to:

  • set the corresponding SU to 
    Status
    colourRed
    titlefailed
    (see procedure below)
  • evaluate if repeating the failed observing session described by the failed SU is within the policy for the project (i.e. check priority and if the failed session was already a repetition)
  • if possible, add more tasks to the SU

...

  • ; to this aim new tasks can be added in a SU by

...

  • using in the "Scheduling Unit - Details" menu and then clicking on the 'paper-and-

...

  • pencil' icon next to the "Task Details" section. 
  • if possible repeat the process of specification and submission by generating a copy of the SU draft; to this aim copy the failed blueprint of the SU to a (renamed) draft SU and blueprint it. In this case, make sure that the new SU does not retain any fixed timeslot from the failed copy. Also, make sure that

...

  • any archived data related to the failed SU to be removed from the LTA

...

  • via opening a ticket in the Helpdesk (project users) or directly cleaning up the archive (for SDCO operators).

In order to set a SU explicitly to

Status
colourRed
titlefailed
the following procedure can be used:

...

  • To confirm the change, we click the 'Patch' button at the bottom of the page.
  • Now, the SU will be set to
    Status
    colourRed
    titlefailed
    , and any related (also pinned) data to the SU will be deleted, or have to be deleted manually if the SU was set to failed before the associated cleanup task has run.
  • If data were archived, we need to open a Helpdesk ticket for them to be removed from the LTAan LTA cleanup action can be requested by project users via opening a ticket in the Helpdesk or directly performed by SDCO operators.

This concludes the Observation Specifications description. However, this is not where the responsibilities of the FoP end, as after the observation was successful the FoP has to do the Reporting.

...