This document outlines a Ph.D. proposal to examine the use of workflow engines and coupling frameworks in developing hydrologic modeling systems. Specifically, it will develop hydrologic models within the TRIDENT workflow engine and OpenMI coupling framework to evaluate their capabilities for building community modeling systems. The research will include developing component models, building sample workflows, and testing models on three sites. The goal is to contribute optimized hydrologic modeling tools and assess the suitability of these approaches for collaborative hydrologic modeling.

1. Ph.D. Proposal March 1st ,2010 The role of Workflow Engine and Coupling Framework in the Development of Hydrologic Modeling System Presenter: Bo Lu Advisor: Dr. Michael Piasecki Department of Civil, Architectural & Environmental Engineering Drexel University

4. Tank Model

5. Soil Water Assessment Tool(SWAT)

6. Systeme Hydrologique Europeen(SHE) …

7. High-performance computing technologies have been developed.

8. GRID

9. CLOUD …A current focus is on the development of holistic-view-models that incorporate hydrologic process with chemical, physical, and biological processes.

12. emphasizing on sharing methods, model codes and data.

14. broadening the usage of legacy models/codes.

18. BABEL: a language-interoperability tool generating “glue codes” that bridge the communication between component models written in different programming languages.

19. Ccaffeine: a Graphical User Interface(GUI) for linking component models.

21. The Invisible Modelling Environment(TIME)

22. Open Modeling Interface and environment(OpenMI)…

24. a data-driven procedure.

26. a web service(or a set of web services) accessing online data or invoking remote modeling.

27. a service distributing computations in high-performance computing environment.What are workflow engines? software applications that can facilitate composing, executing, archiving and sharing scientific workflows.

29. Construct and add a CMS within the context of the CUAHSI Hydrologic Information System(HIS)

30. Focus

31. Make efforts to build up hydrologic modeling systems by adopting the TRIDENT workflow engine and the OpenMI coupling framework.

32. Provide an environment for designing models that can seamlessly integrate the components of data accessing, data preparation, model execution, and model result analysis via TRIDENT.

33. Contribute to the community by providing with optional models for carrying out hydrologic modeling tasks.

35. To which level can they facilitate and promote community modeling and to what level do these systems lend themselves for a successful implementation as a CMS?

36. Specific Questions

37. When modularizing an existing model into OpenMI and TRIDENT, will its performance be affected?

38. In which of these two environments will the same model perform better?

39. Is either approach really suitable for creating a CMS, or should approaches currently being taken by systems such as CSDMS be favored?

41. Create a library of component models, so-called activities in TRIDENT, for hydrologic modeling and model pre-/post- processing.

42. Establish a standard definition system of variable data types in the TRIDENT.

43. Build up workflow sequences that represent two distinct hydrologic models:

44. Penn State Integrated Hydrologic Model(PIHM)

45. A hydrologic model integrated by component models simulating separated hydrologic processes

48. GridNexus(Brown et al.,2005)

49. Triana(Taylor et al.,2003)

50. Kepler(Ludäscher et al.,2006)

51. Pegasus(Deelman et al.,2005)

52. TRIDENT(Microsoft,2009)

53. Taverna(Oinn et al.,2004)

54. Most workflow engines support:

55. high-performance computing, parallel or concurrent execution, and distributed computations in the GRID environment.

56. Capturing provenance. Provenance specifies who, how, what and which resources are used in the workflow, and describes the derivation flow of data products.

57. Sharing workflow through publication mechanisms or repositories. For example, publishing workflow on the myExperiment web site (http://www.myexperiment.org)

58. Composing workflow via the drag-and-drop manner on a GUI. Output of one workflow can be mapped to input of multiple components.

62. Spatial Modeling Environment (SME, Maxwell and Coastanza,1994)

63. Modular Modeling System (MMS, Leavesley et al.,1996)

64. Dynamic Information Architecture System(DIAS, Campbell et al.,1998)

65. Interactive Component Modeling System(ICMS, Reed et al.,1999)

66. Tarsier(Watson et al.,2001)

67. Object Modeling System(OMS,David et al.,2002)

68. The Invisible ModellingEnvironment(TIME, Rahman et al.,2003)

69. ModCom(Hillyer et al.,2003)

70. Earth System Modeling Framework(ESMF, Hill et al.,2004)

71. Open Modeling Interface and environment(OpenMI, Gregersen et al.,2005)

73. Object-oriented architecture.

74. Standard interfaces or protocols for modularizing models.

75. A set of development tools or classes that facilitate standardizing legacy codes.

76. A workbench for model linkage, execution and management. A visual canvas is mostly provided that allows linking models by the drag-and-drop manner.

77. An extensible library of core components that encapsulate scientific algorithms and methods.

79. Managing workflows, ativities,users,workflow provenance

81. Scheduling workflow execution

82. Loading/running workflows from local/remote database

83. Loading/running workflows from local/remote database

84. Loading/running workflows from local/remote database

85. Running multiple workflows on different nodes of a server clusterTRIDENT SQL DATABASE

87. Standard Interfaces (C#, JAVA)

88. Development support tools

89. Spatial data operations

90. Wrapper

91. small tools for reading/writing XML files, converting calendar…

92. Configuration Editor: GUI for linking and running models

93. request-reply mechanism

94. GetValues method

95. On a time step basis

99. Data Processing Library

100. Hydrologic Model Library

103. PIHM in OpenMI

112. Terrain ProcessingRaw DEM( 1176*883 cells) Sink filled DEM Flow Direction Strahler Network order Flow Accumulation Watershed and River Network (.shp) Stream order Stream Raster Watershed Grid

114. Elements contains pointers to TSRs

120. Water balance check

121. Modelled & Observed runoff comparison

122. Data Requirements

123. Geospatial data( DEM, land cover, soil).

124. Driving force: precipitation, temperature, relative humidity, solar radiation, vapor pressure, wind velocity.

126. 0.08 sq.km, located in the Valley and Ridge physiographic province of central Pennsylvania.

127. Upstream channel is ephemeral.

128. 44 wells for measuring soil moisture; 4 gages.

130. approximately 4,962 sq.km, located in Southeastern Pennsylvania.

131. approximately 209 km in length from its headwaters at Tuscarora Springs to its mouth at the Delaware River.

132. mean annual temperature: 11 °C

134. approximately 12,600 sq.km, located mostly in Iowa and partially in Minnesota .

135. approximately 483 km in total length from its headwaters at Dodge county, Minnesota, to its confluence with the Iowa River.

136. average annual temperature: 7-10 °C

137. average annual precipitation: 600-900 mm

139. Thank you!