Skip to content

Releases: fsenf/SynSatiPy

v1.0.1b - GOES-ABI Support and Enhanced Testing

15 Aug 09:44
Compare
Choose a tag to compare

SynSatiPy v1.0.1b Release

This beta release introduces significant new capabilities and improvements to SynSatiPy, including support for a new satellite instrument and enhanced testing infrastructure.

🛰️ New Instrument Support

  • GOES-ABI Integration: Added full support for GOES-16/17 Advanced Baseline Imager (ABI) with all 16 spectral channels
  • Multi-instrument Architecture: Implemented generic instrument loading system supporting both MSG-SEVIRI and GOES-ABI

🧪 Enhanced Testing & Quality

  • Parametrized Testing: New pytest-based test suite covering both SEVIRI and ABI instruments
  • Automated Test Runner: Bash script for comprehensive testing including unit tests and Jupyter notebook execution
  • Improved Error Handling: Specific exception types throughout the codebase

📚 Documentation & Code Quality

  • NumPy-style Docstrings: Comprehensive documentation following NumPy conventions
  • Code Refactoring: Better modularity with generic variable naming and improved organization
  • API Improvements: Enhanced function parameter documentation and clearer interfaces

🔧 Technical Improvements

  • Better File Processing: Improved filename pattern matching, sorting, and symbolic link support
  • Enhanced Data Handling: Better pressure calculation, humidity clipping, and coordinate handling
  • Performance Optimizations: Streamlined instrument loading and memory management

📋 Full Details

See CHANGELOG.md for complete details of all changes.

Initial Release of SynSatiPy

16 Apr 08:11
Compare
Choose a tag to compare

SynSatiPy is a python interface that allows to read atmospheric 3d data and derived synthetic satellite imagery from this data. It used the RTTOV library and builds on its class-based approach.

Current Features:

  • several model input interfaces exist:

    • ICON with flavors "ifces2", "ocrestra"
    • ERA5 data
    • direct input of xarray datasets (with correct variable naming and units)
    • regional cutouts + cutouts based on zenith angle possible
  • observational sensors:

    • only SEVIRI currently
  • workflow aspects:

    • lazy data handling with dask
    • chunking of input data from memory efficiency
    • netcdf4 data output