For Developers

This section is for ARTS developers. It covers build configuration, implementation, maintenance, and validation. See Guide for interface guidance and Mathematics and physical concepts for mathematics and physical theory.

Consider it a collection of notes and documentation for developers. Each page explains a specific topic in various detail. It is expected that you use these sections to learn about particular topics in ARTS development. It contains direct code examples and explanations of how to add new features and how to use existing features.

• ARTS Classes and Structs
  • Use of std::formatter<T>
• Errors inside the C++ code
  • Use of macros in debug.h
• Matpack
  • Sparse matrices
  • Multidimensional data
  • Multidimensional views
  • Interpolation in ARTS
  • Sorted grids
  • Gridded data
  • Band matrices
• Workspace
  • Workspace agendas
  • Workspace groups
  • Workspace methods
  • Workspace options
  • Workspace variables
  • Short-forms for naming workspace variables
• Plot Modules for GUI Integration
  • Overview
  • Design Pattern
  • Usage Examples
  • Future Enhancements
• Editor modules for GUI integration
  • Overview
  • Design Pattern
  • Dispatch and Fallback
  • Editor Guidelines
  • Adding a new editor
  • Examples and References
• Plot GUI architecture
  • Overview
  • Main components
  • Flow
  • Editors integration
  • Workspace methods interface
  • Extending the GUI
• Documentation
  • Choosing a documentation section
  • Examples folder
  • The Workspace documentation
• XML IO
  • The xml_io_stream
  • Templated overloads of xml_io_stream
• Adding new species to ARTS
  • To add a species
  • To add an isotopologue
  • To add a predefined model
• ARTS 2 Feature-Port Status
  • Status terms
  • Initial audit snapshot
  • Confirmed implementation gaps
  • Active coverage gaps
  • Deferred beyond this first pass
  • Updating this page
• ARTS 2 Features Not Intended for ARTS 3
  • ARTS 2 scripting language and executable
  • Always-3D geometry, not atmosphere modes
  • No global Stokes or Jacobian switches
  • No formal cloudbox
  • Composite fields and fewer workspace variables
  • Sensor representation
  • Scattering data representation
  • Failure and validation behavior
  • ARTS 2 checks retired by these decisions
  • Legacy choices that remain
  • Open questions, not design decisions
  • Port-review checklist
• T-matrix implementation and validation
  • Port and reference tests
  • Native particle-habit integration
  • MC azimuthally random particle reproduction
• Heating-rate reference tests
• DISORT implementation and validation
• Implementation array layouts
  • Numerical behavior and limitations
  • Validation scope
• Surface emissivity integration
• Radiative-transfer implementation