Difference: ALMACalMSCreation (10 vs. 11)

Revision 112019-10-09 - DirkPetry

Line: 1 to 1

META TOPICPARENT	name="WebHome"

Procedure for creating ALMA MSs upon user request

Changed:

<
<

(version 2019-10-01)

>
>

(version 2019-10-09)

Procedure for creating ALMA MSs upon user request

Line: 62 to 62

AOG should not be contacted in case of Cycle 0 projects.

Added:

>
>

Check for presence of QA0_PASS data

Before contacting AOG, it should also be verified that there is actually calibrated data which we can offer to the user, i.e. there are QA0_PASS EBs in the archive.

This step was integrated in the the call to triggerCalMSCreation.sh described in the following section.

Create email to AOG after receipt of a request via helpdesk

For each requested MOUS, the assigned EU ARC personnel should send one email to AOG via the special script "triggerCalMSCreation".

Line: 90 to 97

runs the script

Changed:

<
<

triggerCalMSCreation "" ""

>
>

triggerCalMSCreation.sh "" ""

Example:

Line: 146 to 153

AOG is running a cronjob on an AOG machine to look for new triggers once per hour.

Added:

>
>

In case there are no QA0_PASS data, the script triggerCalMSCreation.sh will terminate with this message:

   ERROR: No QA0_PASS data found for this MOUS. Please double-check MOUS UID.
                    If confirmed, please inform the user that ALMA cannot offer calibrated data for this MOUS.

and not contact AOG.

Prevention of duplicate triggers

Once AOG has completely processed a trigger, AOG removes the corresponding trigger file from /opsw/work/datadelivery/stagecalmsTriggers .

View topic | History: r13 < r12 < r11 < r10 | More topic actions...