ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM...

7
ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao Saito (JAO AM) Daniel Espada (JAO Interim Deputy AM)

Transcript of ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM...

Page 1: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ALMA Integrated Computing Team

Coordination & Planning Meeting #3 Socorro, 17-19 June 2014

New AM organization and improving the acceptance procedure

Masao Saito (JAO AM)

Daniel Espada (JAO Interim Deputy AM)

Page 2: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

2013.12 – 2014.4

AM: Masao Saito

Deputy AM: Itziar de Gregorio

2014.5 – 2014.6

AM: Masao Saito

Interim Deputy AM: Daniel Espada

2014.7 – 2014.8

Interim AM: Daniel Espada

Acceptance Management Organization

Page 3: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

Acceptance Since CPM#2

Cycle 2 started on time thanks to all of you!! Acceptance Procedure is established. TRR/ACRV held on Friday 11 am (CLT)

Acceptance Branch Acceptance Date Observatory Milestone

A10.2R 2013-12-02 Cycle 2 APRC

201403-CYCLE2-OFF 2014-03-28 Cycle 2 SB generationstart of Cycle 2

201404-CYCLE2-ON 2014-05-30 start of Cycle 2

201405-CYCLE2-OFF 2014-05-23 start of Cycle 2

201406-CYCLE2-OFF 2014-06-27 start of Cycle 2

Page 4: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

1. Integrated Acceptance Calendar: Our Foundation1. Schedule, Scope is clearer than before.

2. Better requirements deadline is given

3. BUT, IT IS NOT EASY TO UNDERSTAND AT A FIRST LOOK

2. Acceptance wiki: Focal point of each acceptance1. Better organized, documents, structures etc.

3. SSG wiki:1. Clear responsibility for each subsystem scientist in each

subsystem

4. AM-RM meeting/regular contact1. Less miscommunication between ICT and JAO science

5. SEQM meeting1. Better quality control for the overall process

Improvement Efforts since CPM#2

Page 5: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

Robust process After TRR, the software is tested internally before going public.

After ACRV, the software goes public (e.g. source catalogue) ARC deployment

Invite ARC contacts to TRR to share deployment info. Kanban

Very successful to track status of ICT-tickets. Pipeline Heuristics (originally not in the JAO acceptance)

AM accepts the software with SciOPS approval New Subsystem

Dashboard (Stuartt), Integrated Reporting (Lars)

New things in the acceptance after CPM#2

Page 6: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

Bugs are well followed in Kanban if labeled correctly.

Acceptance Status

Acceptance Branch SubmittedAcceptedIn progress

Implemented, Verifying

Resolved, Validating

Closed

201403-CYCLE2-OFF 1 4 3 210

201404-CYCLE2-ON 3 2 5 207

201405-CYCLE2-OFF 2 3 13 108

201406-CYCLE2-OFF 2 5 20 15

Page 7: ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao.

ICT-CPM3 17-19 June 2014

Too many PRTSIR tickets assigned to softwareNew procedure is underway

Science Portal RequirementToO triger etc. needed every cycle start.

Pipeline infrastructurePipeline developer team proposed a reasonable

procedure.

ARC deploymentDetailed Procedure is needed. Separate discussion.

Remaining Issues