Home_intro

intro story DELWAQ

DELWAQ

DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

How testing should be done within sprint to avoid spill overs?

PI
priya impex, modified 1 Month ago.

How testing should be done within sprint to avoid spill overs?

Jedi Master Posts: 293 Join Date: 10/15/20 Recent Posts
Development teams unable to complete PBIs because of pending testing activities.Majority of the times, Development teams unable to complete PBIs because of pending testing activities. If you move to Scrum and still follow traditional testing practices, it doesn’t add value but pulls agility down. Chances are that there will be water falling inside the sprint because of traditional development practices of handovers.Testers waste time in creating and validating test cases than the product. One way to reduce that is to start using Specification by Example where in the Development team and Product Owner together comes up with examples for PBIs and the features will be built only with those examples.It eliminates the possibility of bugs and errors in business functions. Also, testers can start automating when programmers start with coding and there by reducing the possibility of hand overs. Devops Online Training