intro story 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.




Sub groups
D-Flow Flexible Mesh

Cohesive sediments & muddy systems


Message Boards

Pair programming

priya impex, modified 1 Month ago.

Pair programming

Jedi Master Posts: 274 Join Date: 10/15/20 Recent Posts
Pair programmingPair programming is a strong tool kit in extreme programming’s tool box.  Two programmers works on same workstation one wearing a driver’s hat and the other one wearing an observer’s hat, exchange  their roles at frequent intervals of time that they agree upon, steer the program to its conclusion. The dual perspective on same problem is at the core of this technique. Tough there are two brains working on same problem, they should have a conscientious to collaborate and not to compete. While the implementation is on its way, the same is being reviewed as its being written. So it saves a big time on future defects and code review requirements while engaging two people on same task.
It’s important to have some house rules for any such collaboration happening to achieve a task to its done state. Team work is as challenging as much its efficient. Still there’s no need of a handbook for these rules. It’s the best practices that learned during the journey. We inspect and adapt, we discard few rules as we feel them redundant or destructive for our goals and form new ones to make our pair programming more fruitful.To list an example of such rule, we sometimes get carried away in the midst of the task that we start feeling possessive to hand over the precious piece of code that we are coding, to the pairing person. This slowly sweeps in the division of the module that we are coding. This obviously kills the very purpose of pair programming. We do have time bounding to make the perspective neutral. Switching may at first seem inefficient but would reaps on as it continues. <!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-->Devops Online Training