also: [OATC Wiki

 Home|OpenMI AssociationTechnical Committee]

Date: September 7 - 10, 2009

Venue:[BAW|http://www.http://www.BAW.de/], Hamburg, Germany

h1. Participants:


[~s.vanecek@dhi.cz], DHI (s.vanecek@dhi.cz)

Daniele Andreis,Universita` di Trento,(daniele.andreis@gmail.com)

Roger Moore, on Mo + Tu (rvm@ceh.ac.uk)

Imran Younas on Mo + Tu (imun@ceh.ac.uk)

Stephen Morris on Mo + Tu (smorris@butford.co.uk)

[~harper], Wallingford Software (adrian.harper@wallingfordsoftware.com)

[~hummel], Deltares (stef.hummel@deltares.nl)

[~don], Deltares (gennadii.donchyts@deltares.nl) Mo -

  Wed
[~peter_schade], Bundesanstalt fuer Wasserbau (peter.schade@baw.de)

[~jgr@dhigroup.com], DHI (jgr@dhigroup.com)

[~Gregersen@LicTek.dk], LicTek on Mo (afternoon) + Tu (Gregersen@LicTek.dk)

Apologies:

[~jnh@dhigroup.com], DHI (jnh@dhigroup.com)

[~rob.knapen@wur.nl], Alterra, Wageningen UR (Rob.Knapen@wur.nl)

[~onnoroos], Alterra (Onno.Roosenschoon@wur.nl)

[~moovida], Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com)

h1. Documents:

[http://www.openmi.org/

]
[http://sourceforge.net/projects/openmi

]
wiki.openmi.org

h1. Table of contents

{toc}


h1. 1. Minutes from previous OATC

 meeting


h1. 2. Documentation (most important)

Primary about C# based on this prepare Java

h2. 2.1

 Standard


h3. Automatic using Enterprise Architect


h3. Modified 1.4

 documentation


h3. Changes in standard from 1.4

h2. 2.2 Model

 migration


h3. From 1.4

h3. For the new model (modified existing documentation)


h3. Changes compare to previous version


h2. 2.3 SDK


h3. Components migrated to the 2.0


h3. Automatic generated EA


h3. Changes 1.4


h2. 2.4 Tools


h3. Modified 1.4 documentation


h2. 2.5 GUI

Progress as of 26/08/09
* Simple C# River example
** Has been largley rewritten to conform with version 2
** Uses base classes that hide some of drudgery of implementation, see (in namespace Oatc.OpenMI.Examples.ModelComponents.SimpleCSharpRiver.Wrapper)

*** class ItemBase {}

*** class OutputItemBase : ItemBase {}

*** class OutputItemDoubleBase: OutputItemBase{}

*** class InputItemBase : ItemBase {}

*** class InputItemDoubleBase : InputItemBase {}

*** class InputFlowItem : InputItemDoubleBase {}

*** class OutputFlowItem : OutputItemDoubleBase {}

*** class LinkableComponent  : ILinkableComponent, IDisposable {}

*** class RiverModelLinkableComponent : LinkableComponent {}

** These have many TODO's which indicate Standard queries and unimplemented features.

* UI Editor

** Largly Rewritten, still much to do, currently ....

*** Add/Remove Models

*** Composition Save, Open & Reload

*** New opr format valid

 for
**** models
**** exchange items (including decorators) examples under ??\Examples\ModelComponents\SimpleCSharpRiver\Data\Rivers

*** New Link

 dialog
**** Allows adding of decorators via factories (3rd party factories still to do)
*** New run dialog
**** Run, Abort & Reload
**** Real time update of model status via events
**** Basic Log info
*** Unit Tests
**** Completed
***** Stand alone Simple C# river
***** Two Simple C# rivers in series (Unidirectional)
**** Todo
***** Two Simple C# rivers in series (Unidirectional) with 1 decorator
***** Two Simple C# rivers in series (Unidirectional) with 2 decorators
***** Two Simple C# rivers in series (Bidirectional)

{color:#ff0000}{*}STANDARD SUGGESTIONS{*}{color}
* OMI XML
** allow missing xmlns?
*  IIdentifier/IDescribable
** Should be merged together\!
*** string IDescribable.UniqueId { get; }
****   /// Unique with respect to instantiated class type i.e.
  /// String unique = instantiated.Getype() + instantiated.UniqueId;
  /// UI's will use these for persistance, hence new component
  /// releases should maintain UniqueId value backwards compatability

*** string IDescribable.Caption { get; set; }
****   /// Short description.
  /// Suitable for displaying via a UI.
  /// Suitable for translation (hence set)
  /// NOTE: If passed back into component, might be changed, use UniqueId

*** string IDescribable.Description { get; set }
****   /// Longer, more generic, description.
  /// Suitable for displaying via a UI as additiona info.
  /// Suitable for translation (hence set)
  /// NOTE: If passed back into component, might be changed, use UniqueId
** Newname IDescribes ?
* IArgument
** Add
*** string IArgument.ValueViaString { get; set; }
**** /// Allows UI to persist values (e.g. too/from opr file)
/// without knowing anything about their type
*** bool IArgument.IsValid(out IDescribable\[\] reasons);
****   /// Used by UI to determine whether user has to
  /// change/set the value
  /// Returned reasons can be displayed by UI in ignorance
  /// If true returned, reasons will be treated as warnings
  /// if false returned, resaons will be treated as a mixture of errors and warnings,
  /// the Caption should make clear whether a Error or a Warning. UI will display
  /// in order, so typically errors first warnings lator etc.
** Redundant
***  bool IArgument.IsRequired { get; }
**** /// IsValid(...) always returns false until set
*** &nbsp;IList<object> IArgument.GetPossibleValues();&nbsp;
*** &nbsp;string IArgument.Characteristics { get; }
* IExchangeItemEventArgs
** Only two members
*** IExchangeItem \_exchangeItem;
** and either of following
*** string \_information;
*** IDescribable\[\] \_information
** &nbsp;&nbsp; /// UI can then serve information up in a dumb way
&nbsp;&nbsp; /// Derived classes&nbsp; (in SDK not STandard) can have
&nbsp;&nbsp; /// additional members such as \_hasElementsChanged
&nbsp;&nbsp; /// if wanted, but keep minimal in standard

h2. 2.6 Test cases


h2. 2.7 General introduction


h2. 2.8 Linux

h1. 3. Review of the implementation


h2. 3.1	SDK + standard


h2. 3.2	Already migrated model


h2. 3.3	Running of the connected models from GUI


h2. 3.4	Pending tasks

h1. 4 Plan of the Ver. 2.0 release


h2. 4.1	Alpha for review (documentation, announced on the OpenMI Web)


h2. 4.2	Beta + new release of the documentation


h2. 4.3	 Final delivery \-\+ text for the Life project report


h1. 5	Necessary changes to the Standard

Sugested based on the implementation. Only if really needed \!\!\!\!\!\!

h1. 6 Public talk

We need to discuss extend of the meeting and more detail agenda. Our primary focus for the meeting need to be create progress especially in the version 2.0 documentation. In the week starting 24.8 we need to indicate content of the planed talks - provide to the Peter enough time to invite peoples.