Wiki Markup |
---|
{scrollbar}
See |
...
also: [OATC Wiki |
...
Minues are under construction, expected to be completed January 22
...
Home|OpenMI AssociationTechnical Committee] (!) Minues are under construction, expected to be completed January 22(!) h5. Date: January 13-15, |
...
2008 h5. Venue: [University of Trento|http://www.unitn.it] and Riccardo Rigon, Italy ([Location and hotel information for OATC meeting no 21 |
...
Participants:
...
]) h5. Participants: [~gregersen@lictek.dk], DHI / LicTek (gregersen@lictek.dk) (chairman of the meeting) |
...
[~harper], Wallingford Software (adrian.harper@wallingfordsoftware.com) |
...
[~hummel], Deltares (stef.hummel@deltares.nl) |
...
[~don] (Gena), Deltares (gennadii.donchyts@deltares.nl) |
...
Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com) |
...
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE) |
...
Silvia Franceshi,Universita` di Trento h5. Apologies: |
...
[~onnoroos], Alterra (Onno.Roosenschoon@wur.nl) |
...
[~gijsber], Deltares (Peter.Gijsbers@deltares.nl) |
...
[~rob.knapen@wur.nl], Alterra (Rob.Knapen@wur.nl) |
...
Jon Goodall, Univ South Carolina (goodall@engr.sc.edu) |
...
Lars Ekebjærg, DHI, (lce@dhigroup.com) |
...
h5. Documents: |
...
[http://www.openmi.org/ |
...
] [http://sourceforge.net/projects/openmi |
...
] wiki.openmi.org |
...
h1. Table of contents |
...
Table of Contents |
---|
Agenda
1. Minutes from previous OATC meeting
2. Maintenance and support
2.1 Reported bugs
(GOTO bug list on SourceForge)
2.2 Help issues
(GOTO help issues on SourceForge).
2.3 Discussion issues
(GOTO discussion issues on SourceForge)
3. OpenMI 2.0 Issues
3.1 Use cases
.
3.2 OpenMI 2.0 architecture
3.3 Development and release road map
...
4. OATC Procedures
5. www.OpenMI.org and wiki.OpenMI.org
6. Miscellaneous issues
6.1 OpenMI goes Linux
The following lines describe the development status of the linux portation of
- the OpenMI environment
- and an OpenMI compliant model.
6.1.1. Porting the OpenMI environment
- the OpenMI standard v. 1.4.0, ... done
- the SDK v 1.4.1, ... done
- the commandline v 1.4.1, ... done
- configuration editor v 1.4.1 (Mono 2.0 needed), ... under construction
6.1.2. Porting the Fortran Code from Compaq to ifort on Windows
Generation of an ifort gei.win.dll and a main program and running the 31 test cases. ... done
6.1.3.Porting the ifort Code from Windows to Linux
Linux ifort compilation of the BAW engine gei.xe.dll on a 64bit system. ... done
6.1.4. Porting GEIWrapper to Linux
Portation of GEIWrapper (the C#-Wrapper around the engine gei.xe.dll) ... done
6.1.5. Porting WLDelftWrapper to Linux
Original strategy: It could be reasonable to port the OpenMI compliant WLDelftWrapper to Linux (Deltares). Alternatively, Deltares could offer a Linux engine and the information how to access it from a Windows WLDelftWrapper.
New: Meanwhile fast multicore pc cpus made a linux WLDelftWrapper less important for the BAW, see 6.1.7.
6.1.6. Test of a composition
- composition with commandline in batch mode ... done
- generation of a composition in configuration editor ... under construction
6.1.7. Test System
The BAW test system is a linux workstation with one Intel Xeon Dual Core Processor and SLED 10. We use the 64 bit instead of the planned 32 bit mode, since our workstations as well as our hpc cluster work in 64bit mode.
Peter Schade
7. Tasks and unresolved issues
All tasks are handled by sourceForge. GOTO: OpenMI Tasks on source forge
...
{toc} h1. Agenda h1. 1. Minutes from previous OATC meeting {color blue} *Minutes* There were no comments to the minutes from last meeting {color} {include: 2. Maintenance and support} h1. 3. OpenMI 2.0 Issues h4. 3.1 Use cases [GOTO use cases|OpenMI Use Cases] {color:blue}.{color} h4. 3.2 OpenMI 2.0 architecture h5. h4. 3.3 Development and release road map {include: 3. OpenMI Java and OpenMI .net synchronization} h1. 4. OATC Procedures h4. h1. 5. www.OpenMI.org and wiki.OpenMI.org h4. h1. 6. Miscellaneous issues h4. h4. 6.1 OpenMI goes Linux The following lines describe the development status of the linux portation of - the OpenMI environment - and an OpenMI compliant model. 6.1.1. Porting the OpenMI environment - the OpenMI standard v. 1.4.0, ... done - the SDK v 1.4.1, ... done - the commandline v 1.4.1, ... done - configuration editor v 1.4.1 (Mono 2.0 needed), ... under construction 6.1.2. Porting the Fortran Code from Compaq to ifort on Windows Generation of an ifort gei.win.dll and a main program and running the 31 test cases. ... done 6.1.3.Porting the ifort Code from Windows to Linux Linux ifort compilation of the BAW engine gei.xe.dll on a 64bit system. ... done 6.1.4. Porting GEIWrapper to Linux Portation of GEIWrapper (the C#-Wrapper around the engine gei.xe.dll) ... done 6.1.5. Porting WLDelftWrapper to Linux Original strategy: It could be reasonable to port the OpenMI compliant WLDelftWrapper to Linux (Deltares). Alternatively, Deltares could offer a Linux engine and the information how to access it from a Windows WLDelftWrapper. New: Meanwhile fast multicore pc cpus made a linux WLDelftWrapper less important for the BAW, see 6.1.7. 6.1.6. Test of a composition - composition with commandline in batch mode ... done - generation of a composition in configuration editor ... under construction 6.1.7. Test System The BAW test system is a linux workstation with one Intel Xeon Dual Core Processor and SLED 10. We use the 64 bit instead of the planned 32 bit mode, since our workstations as well as our hpc cluster work in 64bit mode. Peter Schade h1. 7. Tasks and unresolved issues All tasks are handled by sourceForge. GOTO: [OpenMI Tasks on source forge|http://sourceforge.net/pm/task.php?group_id=136874&set=custom&group_project_id=54144&_assigned_to=0&_status=1&SUBMIT=Browse] h1. 8. Any other business |