Q1 What was the biggest technical challenges to be able to participate in S2S/TIGGE projects at the beginning? What could improve next time?

Challenges:

• conversion to required GRIB2 format is a challenge, specially from NetCDF for example
• fixed reforecast production
• numerous S2S parameters 

Ideas for improvement next time:

• conversion tools could be shared among the centres (using NetCDF)
  • even within one organisation links to other projects and sharing of tools are important (KMA, BoM, CMA..)
• conversion tools from ECMWF should be shared
  • new tools always welcomed (e.g. to convert to required accumulated sums since the forecast start)

Q2 What are the biggest challenges in the current production phase to ensure long-term minimal effort operations? How could the data archive centres support you more in that role?

Challenges:

• conversion scripts upgrade following model's upgrades
  • sometimes even preventing to continue contribution to archive
    • => official project support stressing its importance  is helpful to find resources inside organisation
• any operational issue can impact products for archives (which has not highest priorities)
• fixed forecast computation is big job after each model upgrade (CPU, storage..)
• TIGGE high resolution is really needed?
  • who is using it?  (limited domain with high res?)
    • some stats could help to understand if it is used

Q3 How could we improve cooperation between data providers and archiving centres (how to communicate/automate tasks/implement checking tools/test/implement model upgrades etc)?

User survey summary

User survey summary - preliminary findings summarising examples of comments from the user survey (only issues not acknowledgements)