[ ] create example in documentation for refinement based a polygon
[ ] create example in documentation for refinement based on bathymetry, including polygon (to avoid refinement on open boundary) >> more information required
[ ] add rgfgrid-based grid generation from hydrodynamic course as a meshkernel notebook (includes base grid, refinement, splines etc): n:\Projects\11209500\11209671\B. Measurements and calculations\01_Updated_course_materials\02_exercises\ (Exercise 1 to 4), base on stenderts notebook (p:\11210154-arem-noregret\hydro\modelbuilder\grid\original_curvilinear_UTM\grid_polygons.ipynb
[ ] meshkernel logo
Other:
[ ] product demo for dsc/haf departments: examples of applications in projects including which mk-features used (gtsm (almost), mb destine?, mb guycarpenter? (not yet), mb gtsm rivers?, mb fmcourse, mb hackathon bonaire, mb saba?, mb arabiangulf, hydrolib-core, hydromt_delft3dfm, dhydamo?, more hco/haf?)
[ ] ugridpy: also maintain z-values and crs from file
[ ] GTSM: global base grid, bathy+gradient refinement, cut landpart with ldb (incl drypoints), example script with some issues
[ ] 1D2D connected like GTSM+rivers
[ ] DCSM: bathy+polygonen refinement, cut landpart with ldb+depth (drypoints with matlab, details at JG?)
[ ] RMM: multiblock rivers, curvigrid generation based on splines, triangles in estuaries, squares in seapart. For the second, we need a to divide a polygon in equal length parts, part of meshkernel?
[ ] D-HYDRO course materials workflow
[ ] tutorial materials from manual
[ ] RGFGRID functions overview, manual edits like in edit>reg/irreg
[ ] create unittests of all workflows to make sure behaviour is tested and future changes do not result in undesired behaviour
[x] merge with additional grid (merge nodes on top of each other) >> mesh2d_merge_nodes
[ ] is not entirely solved by improving polygon deletion, since we have fjords in norway where emodnet has (wet) bathymetry but the landboundary does not include them
[ ] test ridge refinement (implemented in GRIDEDIT-502)
[ ] the mesh2d_refine_based_on_gridded_samples() API now supports multiple dtypes (https://github.com/Deltares/MeshKernelPy/issues/146). Check if gtsm refinement with meshkernelpy is possible with coarsefac 4 >> short/float distinction >> test gtsm memory consumtion for two dtypes (with release)
Next release (5.0.*):
Later:
Documentation:
Other:
Related issues:
connect_cells
separately (without refining)?p:\dflowfm\maintenance\JIRA\06000-06999\06548\meshkernel_interp.py
, can be used to interpolate bathy to?Workflows:
DCSM steps:
mesh2d_delete_small_flow_edges_and_small_triangles
(https://github.com/Deltares/dfm_tools/issues/812#issuecomment-2044437915)mesh2d_delete_hanging_edges
mesh2d_merge_nodes
Test GTSM-specific new features (JV):
mesh2d_refine_based_on_gridded_samples()
API now supports multiple dtypes (https://github.com/Deltares/MeshKernelPy/issues/146). Check if gtsm refinement with meshkernelpy is possible with coarsefac 4 >> short/float distinction >> test gtsm memory consumtion for two dtypes (with release)Release 3.0.0:
xugrid.ugrid.ugrid1d.Ugrid1d.meshkernel
andxugrid.ugrid.ugrid2d.Ugrid2d.meshkernel
both callmk.MeshKernel(is_geographic=False)
so that now failsmk 4.1.0 (released 2024-02-15):
Meshkernelpy 4.2.0: