The US National Science Foundation 4m Daniel K. Inouye Solar Telescope (DKIST) on Haleakala, Maui is the largest solar telescope in the world. DKIST’s superb resolution and polarimetric sensitivity will enable astronomers to explore the origins of solar magnetism, the mechanisms of coronal heating and drivers of flares and coronal mass ejections. DKIST operates as a coronagraph at infrared wavelengths, providing crucial measurements of the magnetic field in the corona. During its Operations Commissioning Phase, DKIST has already conducted a significant number of shared-risk observations for community researchers. The complex raw data are calibrated by the DKIST Data Center located in Boulder and distributed to the science community. We’ll present examples of science results and discuss lessons learned. Ongoing instrument development efforts include, an upgrade of the single-conjugate adaptive optics system to a multi-conjugate AO, the implementation of image slicers for the DL-NIRSP instrument and development of infrared detectors the DL- and CRYO-NIRSP instruments.
KEYWORDS: Control software, Software development, Control systems, Observatories, Process control, Peer review, Operating systems, Industry, Engineering, Standards development
The National Science Foundation’s Daniel K. Inouye Solar Telescope (DKIST) is a 4-meter solar observatory in operation at Haleakalā, Hawaii. The High-Level Software (HLS) group develops and maintains software and control systems for the observatory. During the nearly 20 yearlong observatory construction phase we utilized the Concurrent Versioning System (CVS) as the revision control component of our software configuration management process. As we transitioned into the observatory operations phase, we began looking at using a more modern revision control system that would offer more flexibility and control for software development going forward. Through our long-term planning process, the decision was made to transition from CVS to the Git revision control system. In this paper we describe the motivation to move from CVS to Git for software revision control at DKIST and explain the planning involved to ensure a smooth transition. We will review challenges faced, planning steps involved, migration results, and look at lessons learned from the process. We conclude by sharing initial feedback from the team on the experience thus far using Git.
Access to the requested content is limited to institutions that have purchased or subscribe to SPIE eBooks.
You are receiving this notice because your organization may not have SPIE eBooks access.*
*Shibboleth/Open Athens users─please
sign in
to access your institution's subscriptions.
To obtain this item, you may purchase the complete book in print or electronic format on
SPIE.org.
INSTITUTIONAL Select your institution to access the SPIE Digital Library.
PERSONAL Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.