intro story D-Flow FM

 

D-Flow Flexible Mesh

D-Flow Flexible Mesh (D-Flow FM) is the new software engine for hydrodynamical simulations on unstructured grids in 1D-2D-3D. Together with the familiar curvilinear meshes from Delft3D 4, the unstructured grid can consist of triangles, pentagons (etc.) and 1D channel networks, all in one single mesh. It combines proven technology from the hydrodynamic engines of Delft3D 4 and SOBEK 2 and adds flexible administration, resulting in:

  • Easier 1D-2D-3D model coupling, intuitive setup of boundary conditions and meteorological forcings (amongst others).
  • More flexible 2D gridding in delta regions, river junctions, harbours, intertidal flats and more.
  • High performance by smart use of multicore architectures, and grid computing clusters.
An overview of the current developments can be found here.
 
The D-Flow FM - team would be delighted if you would participate in discussions on the generation of meshes, the specification of boundary conditions, the running of computations, and all kinds of other relevant topics. Feel free to share your smart questions and/or brilliant solutions! 

 

=======================================================
We have launched a new website (still under construction so expect continuous improvements) and a new forum dedicated to Delft3D Flexible Mesh.

Please follow this link to the new forum: 
/web/delft3dfm/forum

Post your questions, issues, suggestions, difficulties related to our Delft3D Flexible Mesh Suite on the new forum.

=======================================================

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ
Cohesive sediments & muddy systems

 


Message Boards

The sizing for Product backlog items is not a good idea during Sprint Plann

LT
Leanpitch Tech, modified 16 Days ago.

The sizing for Product backlog items is not a good idea during Sprint Plann

Jedi Knight Posts: 103 Join Date: 10/1/20 Recent Posts
The sizing for Product backlog items is not a good idea during Sprint PlanningScrum doesn't prescribe how you estimate. The development team cannot size the Product Backlog Items if they do not understand it. Sizing of the Product Backlog Items is focused on understanding the requirements.If you try to understand the requirements of the current Sprint during Sprint planning, there might be unknowns that would crop up, dependencies, lack of clarity of requirements, etc. If this is the case, the team cannot "commit" on achieving the sprint goal.  Hence, the sizing for Product backlog items is not a good idea during Sprint Planning but done better during Product Backlog Refinement.Having said that, if the team gets new information from the product owner about the scope of the Product Backlog Item during sprint planning, they can change the size based on their refined understanding. But the focus of Sprint Planning is not to Size the Product Backlog Items. Coaching agile transitions