Contents Menu Expand Light mode Dark mode Auto light/dark mode
GMT Software And Controls
Light Logo Dark Logo
GMT Software And Controls
  • Release Notes
    • Release 2
    • Release 1
  • Architecture and Design
    • 1. Introduction
    • 2. Requirements Overview
      • 2.1. Requirements Document Tree Structure
      • 2.2. Level 3 SWCS Requirements
        • 2.2.1. Functional and Performance Requirements
        • 2.2.2. General Requirements
    • 3. Overall Architecture
      • 3.1. Organization
      • 3.2. Domains of Control
      • 3.3. Software Development
      • 3.4. Software Deployment
      • 3.5. Controls Hierarchy
      • 3.6. Health and Supervision
      • 3.7. Frameworks
      • 3.8. Modules: Subsystem, Packages, Components
      • 3.9. Instrument Software and Controls Integration
    • 4. Observatory Operation System
      • 4.1. Operations Overview
      • 4.2. Operations Deployment
      • 4.3. Operations Subsystems
      • 4.4. Operations User Interface
      • 4.5. Observing Tools
      • 4.6. Scheduling System
      • 4.7. Sequencer
      • 4.8. Laser AO Operations Safety
      • 4.9. Quality Monitoring System
      • 4.10. Data Archiving System
      • 4.11. Data Processing System
    • 5. Telescope Control System
      • 5.1. Subsystems
      • 5.2. Degrees of Freedom
      • 5.3. Requirements on TCS, Pointing, Tracking & Guiding
      • 5.4. Pointing Kernel
        • 5.4.1. Telescope Pointing Software Libraries
        • 5.4.2. Workflow: Tracking, Pointing, and Guiding
        • 5.4.3. Coordinate Systems and Transformation Flow
        • 5.4.4. Virtual Telescopes and the Telescope Pointing Model
      • 5.5. Wavefront Control System
        • 5.5.1. Natural Seeing Observing Mode
        • 5.5.2. Natural Guide Star Adaptive Optics (NGSAO)
        • 5.5.3. Laser Tomographic Adaptive Optics (LTAO)
        • 5.5.4. Natural-Guidestar Ground Layer Adaptive Optics (NGLAO)
    • 6. Observatory Services
      • 6.1. Service Architecture
      • 6.2. Common Services
        • 6.2.1. Engineering User Interface Service
        • 6.2.2. Command Execution Service
        • 6.2.3. System Supervisor Service
        • 6.2.4. Telemetry Service
        • 6.2.5. Alarm Service
        • 6.2.6. Logging Service
        • 6.2.7. Networking Infrastructure Service
        • 6.2.8. Configuration Service
        • 6.2.9. On-Line Documentation Service
    • 7. Frameworks
      • 7.1. Domain Engineering
      • 7.2. Framework Usage / Code Generation
      • 7.3. Core Framework
      • 7.4. Device Control Framework
      • 7.5. Persistence Framework
      • 7.6. Data Processing Framework
      • 7.7. Time Distribution Framework
      • 7.8. User Interface Framework
      • 7.9. I/O Framework
    • 8. Platform
      • 8.1. Computing Platform
      • 8.2. Field Device Interface Technology
      • 8.3. Time Distribution System
      • 8.4. Distributed Communications - Middleware
      • 8.5. Networking
      • 8.6. Software Development Platform
    • 9. Process
      • 9.1. Systems and Software Engineering
      • 9.2. Software Development Process
    • 10. Software and Control Risks
    • 11. Bibliography
  • Software and Controls Standards
  • Software Development
    • 1. Installing the SDK
    • 2. gds documentation
    • 3. grs documentation
    • 4. Model specification guide document
    • 5. Model-language mapping
      • 5.1. Mapping between the Model Definition Files and C++ source code
      • 5.2. Mapping between the Model Definition Files and Coffeescript source code
    • 6. OCS Test Guidelines
    • 7. Core Services user guide
    • 8. ISample Example
    • 9. HDK example
    • 10. I/O Framework user guide
    • 11. EtherCAT
  • Data Products
    • 1. Software and Controls Data Product Specifications II
    • 2. Software and Controls FITS Keyword Dictionary
  • Software and Controls Acronyms and Definitions
Back to top

5. Model-language mapping#

The code generator translates the Model Definition Files to actual source code of the selected target languages.

Currently, the supported languages for code generation are C++, Coffee Script and Python. In the following sections, the mapping from the Model Definition Files to each one of these languages is described.

  • 5.1. Mapping between the Model Definition Files and C++ source code
  • 5.2. Mapping between the Model Definition Files and Coffeescript source code
Next
5.1. Mapping between the Model Definition Files and C++ source code
Previous
4. Model specification guide document
Copyright © 2024, contributors
Made with Sphinx and @pradyunsg's Furo