60 likes | 201 Views
ALMA Integrated Computing Team Coordination & Planning Meeting #1 Santiago, 17-19 April 2013. Coping with multiple APDM versions as of Cycle 2 A Bridger / M Chavan. Cycle 1-3 Calendar (approx.). Most likely, every Cycle will need a different APDM version. Critical phases.
E N D
ALMA Integrated Computing TeamCoordination & Planning Meeting #1Santiago, 17-19 April 2013 Coping with multiple APDM versionsas of Cycle 2 A Bridger / M Chavan
Cycle 1-3 Calendar (approx.) Most likely, every Cycle will need a different APDM version
Critical phases Cycle 1 and 2 ObsProjects based on different APDM versions co-exist in the Archive Cycle 1 and 2 SchedBlocks based on different APDM versions co-exist in the Archive
Strategy, on-line SW • Science Observing Block • Compiled with Cycle 1 APDMs • Process only Cycle 1 SBs, ObsProjects • CSV Observing Block • At some point (before science SB submission), compiled with Cycle 2 APDMs • Process only Cycle 2 SBs, ObsProjects This is a new requirement for the Scheduler
Strategy, off-line SW • OT • Needs parallel OT client distributions, servers • Archive • Harvesting must (potentially) be per APDM version • Project Tracker, SLT, Ph1M, AQUA (?) • Must read APDMs of any version • Depending on APDM change, can't use Castor
Conclusions • Supporting DDT proposals is more complex than we thought • On-line software copes with one APDM version at the time • Off-line software: multi-APDM versions (backwards compatible) • Transparent to Operations/CSV