Pytroll motives

A rationale for the Pytroll development

Produce what users needs

  • Unexpected needs
    • User requests are unpredictable and development time potentially long
      • Calls for a flexible development and production system!
    • Own software development is needed in order to be able to create highly specialized products

Produce what users needs

  • Users unaware of possibilities
    • Users have insufficient knowledge of technical capabilities of current and future sensors and instruments within their field
    • Satellite SW development needs to be planning ahead as users have limited capability to foresee the usage of future satellite data types

Produce what users needs

  • Enable users to discover existing data
    • Inability for users to efficiently discover data means resources are wasted when users spend time retrieving data elsewhere
    • Inability to efficiently query meta-data and geographical coverage means users waste time retrieving and filtering away unneeded datasets

Short version: Skip this

Produce what users needs

  • Integrate externally developed software gracefully
    • Satellite data processing is dependent on third party software packages. These needs to be integrated in a consistent way in order to limit development effort
    • A consistent integration approach allows for sharing of package integrators between institutes saving duplicate development costs

Produce what users needs

  • Interface for internally developed software
    • Operational implementation of SW developed within a research project may require a major re-write.
    • This extra cost does not add any value for the end user.
    • With a well defined interface for a scientific core the development efforts to bring an application into production will be very limited

Short version: Skip this

Rapid development response

  • Short article-to-production time
    • Quicker response times
    • More products
  • Crisis handling
    • Rapid prototyping and production integration allows for usage of satellite products in case of crisis (e.g. volcanic eruptions)

Production system resilience

  • High reliability and timeliness
    • Software development of high quality is needed
  • Inter institution backup of key data sources
    • Backup of locally received data and derived products
    • Full coverage from EUMETCast will not happen in a foreseeable future.

Efficient resource usage

  • Sharing of software components removes duplicate software development efforts
  • Sharing of processing intense products reduces energy consumption and resource usage on configuration and maintenance

Pytroll adding value for satellite users

  • Collaboration
  • Sharing data
  • Sharing knowledge and experience
  • More and better products to the users
  • Minimising costs
Pytroll motives - Google Slides