Minutes of Telecon 09 02 2010

Attendees

  • Jean-Pierre Aubagnac
  • Andrew Woolf
  • Dominic Lowe
  • Frédéric Guillaud
  • John Schattel
  • Bruce Wright
  • Ethan Davis

Agenda:

  • 1) Review actions from last week
  • 2) Discuss SVN setup
  • 3) Discuss Huddle
  • 4) Discuss Frascati
  • 5) Discuss Use Cases (main item)
  • 6) Next meeting
  • 7) AOB

1) Review actions from last week
  • Action A8/Dominic Lowe to write and publish EA/SVN integration documentation DONE
  • Action A9/Andrew Woolf to flesh out this use case further using real example from polar year. NOT DONE, Remains OPEN
  • Action A10/Chris Little to send email to Řystein Godřym, Norway for further information/ideas for polar year use case. Email sent but Chris not present to dicusss. Keep OPEN
  • Action A11/Jeremy Tandy: Jeremy to see whether to merge (or split) hazard usecases (including fire/flood/hurricane etc). DONE (general revision of use cases)
  • Action A12/ Marie-Francoise to organise next telecon in 2 weeks. DONE

2) Discuss SVN setup
  • STFC (AW, DL) propose to manage the editing of any UML model (in response to group decisions) to avoid multiple versions of the model being worked on. Propose to coordinate modelling through DL.
  • Everyone has access to the model, but controls are on editing process.
  • Relevant discussion:
    • JS - will DL be sole owner of the model?
    • AW - everyone will have read write access but by agreement won't edit it. So if Dom on vacation, someone else can edit the model.
    • JS - Ok with that.
    • All - No objections.
  • DECISION D2: The UML model will be created and edited by STFC (DL), but will be available for anyone to check out and read.
  • DL described the Enterprise architect/SVN document which is available here: *https://svn.opengeospatial.org/ogc-projects/sp/meteo.dwg/Conceptual_Modelling/trunk/EA_Userguide/MetOcean_EA_instructions.doc

3) Discuss Huddle
  • DECISION D3: Stop using Huddle and use OGC twiki as focus for conceptual modelling.
  • ACTION A13: DL transfer minutes from huddle to twiki.

4) Discuss Frascati
  • Not many people on telecon attending Frascati TC.
  • ACTION A14: AW to follow up by email to see if a CM meeting in Frascati is feasible.

5) Discussion and review of use cases
  • u1. Use case describing future aviation scenarios derived from NNEW.
    • JT (by email): Could Aaron et al pull together an over-arching use case about flight planning based on the NNEW stuff & suggestions here?
    • ACTION A15/ Aaron not present, Action on AW to follow up by email.
  • u2. Use case describing current aviation operational meteorology services.
  • u3. Use-bcase describing routine operational forecasting activity at national weather service in support of severe weather warning service.
    • JT (by email): Could PT flesh out these use cases?
    • ACTION A16: Pete T not present, Action on AW to follow up use cases 2 and 3 by email with PT.
    • FG has sent another use case around operational forecasting (3)
    • ACTION A17: FG to add details of his op forecasting use case onto twiki.
  • u4. Use case describing use of multi-model ensemble forecasting to reduce of mitigate impacts of landfalling hurricane
    • Note, John has added FIRE Weather support USE CASE which could be alternative emergency response use case.
  • u 5. Use-case describing winter maintenance of highways infrastructure. * Probably ok for now
  • u6. Use-case describing seasonal forecasting for agriculture in India ... very light-weight at the moment, would be happy for any volunteer to take it further * ?any takers? No.
  • u7. Use-case describing climate impact assessment for economic development in sub-saharan Africa ... * JT has asked Ben Domenico to forward this to some of his colleagues who might be able to help
  • u8. Use-case describing meteorology in support of Emergency Response ... lots of concepts here, but no use-case. * JT (by email) Wonder if there is a use-case from the other end of the water-use spectrum (not enough) from all the WRON work in Australia? * ACTION A18: Andrew to follow up on hydrology use case (possibly re WRON work in australia)
  • u 9. Use case describing sustained environmental science campaign e.g. International Polar Year * See open actions A9 and A10.
  • u10.Automated Steering of High-resolution Local Weather Forecast Models
  • General Use case discussion:
    • ED suggests possible training/case-study use case.
    • All, Proceed on 2 fronts:
      • a) add details to usecases
      • b) start identifying data types and structures for conceptual models.
      • ACTION A19: AW: Put on twiki guidance about how to identify datatypes
      • ACTION A20: ALL Review use cases, add detail by next telecon
      • ACTION A21: ALL Begin to identify data types on use cases by next telecon

6) Next meeting
  • Jeremy away in 2 weeks time
  • Andrew to chair. 23 Feb.

7) AOB
  • No.

Summary of new actions and decisions from this meeting:

  • ACTION A13: DL transfer minutes from huddle to twiki.
  • ACTION A14: AW to follow up by email to see if a CM meeting in Frascati is feasible.
  • ACTION A15: AW to follow up use case 1 wiht AB by email.
  • ACTION A16: AW to follow up use cases 2 and 3 by email with PT.
  • ACTION A17: FG to add details of his op forecasting use case onto twiki.
  • ACTION A18: Andrew to follow up on hydrology use case (possibly re WRON work in australia)
  • ACTION A19: AW: Put on twiki guidance about how to identify datatypes
  • ACTION A20: ALL Review use cases, add detail by next telecon.
  • ACTION A21: ALL Begin to identify data types on use cases by next telecon.

  • DECISION D2: The UML model will be created and edited by STFC (DL), but will be available for anyone to check out and read.
  • DECISION D3: Stop using Huddle and use OGC twiki as focus for conceptual modelling.

-- DominicLowe - 09 Feb 2010
Topic revision: r2 - 10 Feb 2010, DominicLowe
 

This site is powered by FoswikiThe information you supply is used for OGC purposes only. We will never pass your contact details to any third party without your prior consent.
If you enter content here you are agreeing to the OGC privacy policy.

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding OGC Public Wiki? Send feedback