- Jan 23, 2014
-
-
Christophe Geuzaine authored
-
- Jan 20, 2014
-
-
Francois Henrotte authored
-
- Jan 16, 2014
-
-
Christophe Geuzaine authored
-
- Jan 14, 2014
-
-
Maxime Graulich authored
-
- Jan 13, 2014
-
-
Maxime Graulich authored
-
Maxime Graulich authored
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Jan 10, 2014
-
-
Maxime Graulich authored
-
- Dec 10, 2013
-
-
Jonathan Lambrechts authored
-
- Dec 03, 2013
-
-
Christophe Geuzaine authored
and Python onelab clients. WARNING WARNING WARNING: This is a major change -- all our onelab-enabled .geo and .pro files will need to be (slightly...) modified. What's new: 1. The name of a onelab variable (in the onelab database) is no more constructed from the name of the corresponding GetDP/Gmsh variable. One now needs to specify the onelab name explicitely, using the "Name" attribute. The "Name" is the actual name of the parameter in the onelab database, i.e., it also includes the path. This makes the "Path" attribute obsolete (it has no effect anymore). The "Legend" attribute can still be used (and it can be useful in edge cases, e.g. when you want a "/" in the name of a onelab paramater), but in most cases it's not necessary. 2. When a DefineConstant[] & co is used and no Name is given (e.g. DefineConstant[a=2]), no onelab parameter is created. This allows to provide default values to internal parameters without polluting the database. Why did we change? 1. The new syntax matches what we do in Python, where specifying a name is mandatory (there's no way around this in Python, as onelab cannot guess the name of a Python variable to which a onelab parameter value will be assigned). The change will prevent common mistakes where two parameters with the same label actually correspond to 2 different onelab parameters, due to a change in local getdp/gmsh variable name (which would change the onelab name automatically) 2. The new syntax allows to nicely decouple onelab parameters from internal variables with default values, that we don't want in the onelab database.
-
- Oct 28, 2013
-
-
Thomas Toulorge authored
Added maxDistToStraight to MElement. High order mesh optimization: fixed bug with length scale, worked on one-by-one strategy.
-
- Oct 22, 2013
-
-
Maxime Graulich authored
-
- Oct 21, 2013
-
-
Maxime Graulich authored
-
- Oct 18, 2013
-
-
Thomas Toulorge authored
Added local surface parametrization for high-order mesh optimization, worked on one-by-one strategy
-
- Oct 16, 2013
-
-
Thomas Toulorge authored
Improvements to high-order mesh generation: worked on parametric coordinates for optimization (to be completed), changed fast curving algorithm to sweep over faces
-
- Oct 15, 2013
-
-
Maxime Graulich authored
-
- Oct 08, 2013
-
-
Gauthier Becker authored
Fix the MhexahedronN::getFaceVertices() that now returns the nodes of the face (oriented such a way that an MQuadrangleN can be defined from these vertices) Fix a typo reported by Martin Hautefeuille
-
- Oct 07, 2013
-
-
Maxime Graulich authored
-
- Oct 04, 2013
-
-
Christophe Geuzaine authored
-
- Oct 03, 2013
-
-
Thomas Toulorge authored
Added capability to fix invalid p1 surface meshes to OptHOM. Changed 1-by-1 optimization strategy (to be cleaned up).
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Oct 01, 2013
-
-
Maxime Graulich authored
-
- Sep 30, 2013
-
-
Francois Henrotte authored
-
- Sep 27, 2013
-
-
Christophe Geuzaine authored
No commit message
-
Christophe Geuzaine authored
-
- Sep 19, 2013
-
-
Maxime Graulich authored
No commit message
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Sep 18, 2013
-
-
Christophe Geuzaine authored
-
Maxime Graulich authored
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Sep 17, 2013
-
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Sep 16, 2013
-
-
Maxime Graulich authored
-
Maxime Graulich authored
-
- Sep 13, 2013
-
-
Thomas Toulorge authored
-
Maxime Graulich authored
-