TMT common software update

TMT Common Software (CSW). CSW consists of software services and library code that is used by developers to create the subsystems and components that participate in the software system. CSW also defines the types of components that can be constructed and their functional roles in the software system. TMT CSW has recently passed its preliminary design review. The unique features of CSW include its use of multiple, open-source products as the basis for services, and an approach that works to reduce the amount of CSW-provided infrastructure code. Considerable prototyping was completed during this phase to mitigate risk with results that demonstrate the validity of this design approach and the selected service implementation products. This paper describes the latest design of TMT CSW, key features, and results from the prototyping effort

Benchmark density functional theory calculations for nano-scale conductance

We present a set of benchmark calculations for the Kohn-Sham elastic transmission function of five representative single-molecule junctions. The transmission functions are calculated using two different density functional theory (DFT) methods, namely an ultrasoft pseudopotential plane wave code in combination with maximally localized Wannier functions, and the norm-conserving pseudopotential code Siesta which applies an atomic orbital basis set. For all systems we find that the Siesta transmission functions converge toward the plane-wave result as the Siesta basis is enlarged. Overall, we find that an atomic basis with double-zeta and polarization is sufficient (and in some cases even necessary) to ensure quantitative agreement with the plane-wave calculation. We observe a systematic down shift of the Siesta transmission functions relative to the plane-wave results. The effect diminishes as the atomic orbital basis is enlarged, however, the convergence can be rather slow.Comment: 10 pages, 7 figure

Control and monitoring of the SPS proton and ion extractions

For the fixed target program of the SPS, protons and ions are accelerated and extracted towards seven target stations in the NORTH and WEST experimental areas. These extractions range from 106 Lead ions to 1013 protons with durations of 5 or 2.5 s and are controlled by a closed loop system. The intensity monitoring for this system is done with fast screens observed with Photo Multipliers and Secondary Emission Monitors sampled every 100 µs. Along the beam lines, the intensities of the extracted beams are monitored with fast screens at 100 ns intervals. Time and frequency domain information are extracted for diagnosis from the acquired data. A slower observation system, with a 1 ms sampling interval, is also available for assessing the evolution of the centre of charge, the intensity and the losses along the beam lines during an extraction

TMT Approach to Observatory Software Development Process

The purpose of the Observatory Software System (OSW) is to integrate all software and hardware components of the Thirty Meter Telescope (TMT) to enable observations and data capture; thus it is a complex software system that is defined by four principal software subsystems: Common Software (CSW), Executive Software (ESW), Data Management System (DMS) and Science Operations Support System (SOSS), all of which have interdependencies with the observatory control systems and data acquisition systems. Therefore, the software development process and plan must consider dependencies to other subsystems, manage architecture, interfaces and design, manage software scope and complexity, and standardize and optimize use of resources and tools. Additionally, the TMT Observatory Software will largely be developed in India through TMT’s workshare relationship with the India TMT Coordination Centre (ITCC) and use of Indian software industry vendors, which adds complexity and challenges to the software development process, communication and coordination of activities and priorities as well as measuring performance and managing quality and risk. The software project management challenge for the TMT OSW is thus a multi-faceted technical, managerial, communications and interpersonal relations challenge. The approach TMT is using to manage this multifaceted challenge is a combination of establishing an effective geographically distributed software team (Integrated Product Team) with strong project management and technical leadership provided by the TMT Project Office (PO) and the ITCC partner to manage plans, process, performance, risk and quality, and to facilitate effective communications; establishing an effective cross-functional software management team composed of stakeholders, OSW leadership and ITCC leadership to manage dependencies and software release plans, technical complexities and change to approved interfaces, architecture, design and tool set, and to facilitate effective communications; adopting an agile-based software development process across the observatory to enable frequent software releases to help mitigate subsystem interdependencies; defining concise scope and work packages for each of the OSW subsystems to facilitate effective outsourcing of software deliverables to the ITCC partner, and to enable performance monitoring and risk management. At this stage, the architecture and high-level design of the software system has been established and reviewed. During construction each subsystem will have a final design phase with reviews, followed by implementation and testing. The results of the TMT approach to the Observatory Software development process will only be preliminary at the time of the submittal of this paper, but it is anticipated that the early results will be a favorable indication of progress