The First Gmsh Workshop took place in Braives, on September 15-16, 2011
Programme
Thursday September 15
- Christophe's talk about Gmsh
- Workshop1 (STL remeshing)
- Workshop2 (Ocean meshing)
- Workshop3 (Post-processing with plugins)
- Frédéric Dubois's talk about LMGC90
Friday September 16
Afternoon roundtable topics and ideas for future developments:
- Interface
-
switch to single window GUI, with lateral sidebar like firefox or acrobat... Switch to Qt? Many want a sexier interface ;-)done in r13720 (yes! finally the much hated menu window is gone ;-) -
multiple instances when opening files from CL ("gmsh file.geo ; gmsh file2.geo") -> name of the model in the menu window?done in r13720 -
abstract GUI so we can automate some of its creation (for new options)done in r13720 : we can now add new options through onelab (some work to be done on this -- need ideas) -
have an "expert" GUI for the full list of options (cf. about:config in firefox)done in r14606 -
try to reduce the levels in the Geometry/Mesh/Solve/Post menus to 2 (two), e.g. "Add->New Planar Surface"sorta solved; needs consensus on what to do -
user-defined buttons linking to scriptsdone -
add more doc in the GUI (popups, help, if possible automatically)partially solved with new Help->Current Options -
integrate message output it in the main windowdone cf. r9960 -
favorite buttons with last 10 commands?not really necessary anymore since options can be interfaced in the tree; should add something like .gmsh-favorites? -
show only options relevant to the current mode?not really necessary anymore with user-definable GUI -
think about the link with ONELAB solver interfacedone : all solver interfaces are now based on Onelab! -
need to make new features section on web site/wiki more prominentdone in wiki + new tutorials t10.geo - t13.geo Axes: better chose the edges on which to put the tics- merge message output with command line prompt (python? .geo ? cf. gmsh_server)
- make it easier to change options for several views at once (cf. link view, but by selecting several views in the list)
- appear in different places ("Visibility"). Some find this confusing.
- Axes should scale the scale independently of the axis, i.e., we should not scale the coordinates on the axes when we apply a transformation which is just for viewing
- set min/max tic independently of their position on the axis
-
- Infrastructure
-
mailing list for developerscf. http://onelab.info/mailman/listinfo/gmsh-dev gmsh-dev@onelab.info -
Benchmarks: ctest, ...ctest is there: need to add more tests! -
Distribute Python and doc python; "pyinstaller" ?... make a release with pythonENABLE_BUILD_DYNAMIC and ENABLE_WRAP_PYTHON - Doc API !
- have 2 layers of bindings: user (set/get only with "id" GEntity interface) and developer (access to pointers)
-
- Geometry
- Nonlinear transform on mesh+geom (coord change for visu only)
- Force same visa transform for geo/mesh/post
- Mesh
-
write msh: try to get consensus on MSH3 (main feature: no duplication of elements -> physical lists)see bug #94 (closed) -
allow no renumbering of mesh exportwill be done in MSH3 -
when creating compounds, make old entities invisiblemaybe not a good idea, as compounds are not visualizable at the moment until they're meshed. As an alternative, you can use the Hide command: see t12.geofixed by r11058 -
make accessible in GUI Gaetan's levelset stuffPlugin(CutMesh) - Clipping add another option cap elements -- see bug #29
- change status of control points so they can be made invisible
-
- Solver
-
Merge GetDP and GMSH ;-)can be done with onelab (cf. iPad project) -
dofManager: too slowSerialize like in GetDP after pre-processing; cf. Nicolas' work. - DG multi-physic: different closures for different conservation laws
- Rewrite LinearSystem -> abstract matrix/vector classes like in GetDP
-
- Post-processing
-
Pipeline of plugins/options, re-usable (script-foo)done using onelab string with kind "macros" - Load options multi-fields: reload specific options for each field
- Movies: link with ffmpeg?
- MathEval for vector Fields and complex numbers: see bug #136
- restore dynamically loadable plugins
- classify/sort the plugins by category
- Plugin that allows to compute a volume of a given meshed region (already possible if you have a .pos but, directly from the mesh)
- show relevant plugins according to context
-
Please file the most relevant issues in the bug tracking system
Group photo
