- Feb 02, 2005
-
-
Christophe Geuzaine authored
- added new "spectral" colormap (truncated hsv) - added GUI button for elliptic mesh + geometry coherence - added GMSH_MAJOR_VERSION, GMSH_MINOR_VERSION and GMSH_PATCH_VERSION in the parser
-
- Jan 20, 2005
-
-
Christophe Geuzaine authored
allow negative line loop number in surface definitions
-
- Jan 16, 2005
-
-
Christophe Geuzaine authored
-
Christophe Geuzaine authored
- fixed the "unix socket name is one character short" problem on MacOS and AIX. Unfortunately, this required the client code to be slightly modified as well (and as a consequence, old versions of getdp will for example not work with new versions of Gmsh on MacOs and AIX). But it's better to do things "the right way" (TM) for people who want to connect using different languages (Perl, Python). - moved the GmshServer stuff in its own class - added missing rules in parser makefile (so that the parser gets rebuilt automatically when one changes Gmsh.y or Gmsh.l)
-
- Jan 14, 2005
-
-
Christophe Geuzaine authored
new "AliasWithOptions" command
-
- Jan 13, 2005
-
-
Christophe Geuzaine authored
- renamed "Duplicate View" into "Alias View" (suggested by Philippe; less confusing since "Duplicate" implies that we actually copy the data, which is not what we are doing) - added general "on the fly" tranformation matrix option. This allows for very efficient visualization of aliased datasets with non-destructive rotations, symmetries, etc.
-
- Jan 08, 2005
-
-
Christophe Geuzaine authored
- removed all the crappy STL code and rewrote it using JF's POLY_rep class - generalized POLY_rep so that we can use the polygonal discretization as a surface mesh, and mesh in 3D afterwards. I.e., we can now take an input triangulation (a single surface in STL format, multiple surfaces in STL format, one or more surfaces defined using the new "Discrete Surface" commands), and generate a 3D mesh that uses it. We could in theory even mix triangulated and "normal" surfaces in the same geometry, but nothing is done at the moment to ensure that the mesh at the interfaces would match (if it does, it actually works very nicely) - new STL mesh output format to export a surface mesh as a STL file - added an option to the GEO output routine to save the surface mesh as discrete surfaces associated with the geometrical surfaces - added STL and Text output formats for post-processing views (the text output allows for example to exploit plugin-generated data in gnuplot) - generalized Plugin(Evaluate): * can loop automatically over all the timestep and/or components * can do operations using data from an external view - if the 2 views are based on the same grid, the plugin does the evaluation very efficiently - if the 2 views are based on differenet grids, the plugin automatically interpolates the external view data onto the grid of the current view - added new Rand() function in MathEval - default colormap is now # 2 (the Matlab "Jet" colormap)
-
- Jan 02, 2005
-
-
Christophe Geuzaine authored
add special token "Today" to return the current date
-
- Jan 01, 2005
-
-
Christophe Geuzaine authored
copyright update
-
- Dec 30, 2004
-
-
Christophe Geuzaine authored
bulletproof parse_string and skip_until so that we don't crash and simply report the error + use Msg instead of YY_FATAL_ERROR in YY_INPUT
-
Christophe Geuzaine authored
Fixed all (well, most) string memory leaks in the parser. I've run automated tests on all the demos and benchmarks, and I did not see anything suspicious (no crashes, double frees, etc.) ****************************************************************** ****************************************************************** *********** Pretty please, please give this version ************** *********** a try, especially on files with lots of ************** *********** loops, includes, arrays of variables, ************** *********** etc., and report any problems. Thanks! ************** ****************************************************************** ******************************************************************
-
Christophe Geuzaine authored
don't need UpdateViewsInGUI in parser anymore
-
Christophe Geuzaine authored
better test for invalid For/EndFor loops
-
Christophe Geuzaine authored
-
- Dec 27, 2004
-
-
Christophe Geuzaine authored
more robust "Delete Empty Views"
-
Christophe Geuzaine authored
my last commit also fixed several problems in For/EndFor loops: - the body of the loop was executed at least once, even if the test was always false (e.g. For (1:-1:1) ) - the body could be executed one extra time when using optional step values - the for loops didn't work with negative step values
-
Christophe Geuzaine authored
- new parser function GetValue("text", default_value) to query a value interactively in a script - added a nice example using this (to compute slices automatically): demos/multislice.script
-
- Dec 26, 2004
-
-
Christophe Geuzaine authored
- new "Delete Empty Views" command - new View.MinX, View.MinY, View.MinZ, View.MaxX, View.MaxY, View.MaxZ options - added example on how to do simple volume visualization
-
- Dec 17, 2004
-
-
Christophe Geuzaine authored
- fix cast in a couple of error msg - more fixes in elliptic algorithm (surf->TrsfVertices and surf->Vertices were incomplete)
-
- Dec 13, 2004
-
-
Christophe Geuzaine authored
one can now specify a TIME list of values in parsed views to give the values of the time (or whatever) steps (like in ascii/binary views)
-
- Nov 25, 2004
-
-
Christophe Geuzaine authored
- Added a bunch of colormaps from: Color Theory and Modeling for Computer Graphics, Visualization, and Multimedia Applications Haim Levkowitz University of Massachusetts Lowell Lowell, Massachusetts, USA - Increased max size of colormap to 1024 - Small cleanup in parser+plugin
-
Jean-François Remacle authored
-
Christophe Geuzaine authored
This patch fixes an old design flaw in the post-processing module, namely that we used a list of Post_View objects instead of a list of pointers to Post_View objects in CTX.post.list. This had many annoying consequences, in particular the fact that we needed to be extra careful every time the list was reallocated (as pointers to the list elements would become invalid). I tried very hard to change the code everywhere it should be changed, but I might have missed something. Please let me know if you see anything suspicious (like a crash when you duplicate/remove/combine/... post-processing views).
-
- Nov 19, 2004
-
-
Christophe Geuzaine authored
fixed error checking code to work also with adaptive views.
-
- Nov 09, 2004
-
-
Christophe Geuzaine authored
cleanup (and remove 2 shift/reduce conflicts in parser)
-
Jean-François Remacle authored
-
- Nov 01, 2004
-
-
Christophe Geuzaine authored
-
- Oct 20, 2004
-
-
Jean-François Remacle authored
New high order interpolation. JFR
-
- Oct 16, 2004
-
-
Christophe Geuzaine authored
forgot to commit this
-
- Sep 18, 2004
-
-
Christophe Geuzaine authored
generalized the "spatial" Combine so that we can also combine by view name
-
Christophe Geuzaine authored
cleaned up View->Combine by defining a new option (to determine if we should remove the original views after a "Combine" or not)
-
- Sep 16, 2004
-
-
Christophe Geuzaine authored
speedup view removal (only call UpdateViewsInGUI once per group of deletions)
-
- Aug 28, 2004
-
-
Christophe Geuzaine authored
- set glBlendEquation explicitly - make parser
-
- Jul 02, 2004
-
-
Christophe Geuzaine authored
force a buffer flush when we abort the parser due to too many errors
-
Christophe Geuzaine authored
- All extrusion commands now return a list of 2 numbers (instead of 1): the first, as before, is the number of the "top" of the extruded region (i.e., a point for extrude point, a line for extrude line, ...), the second is the number of the "body" of the extruded region (i.e., a line for extrude point, a surface for extrude line, ...). - "Extrude Surface" now always creates a new volume (automatically), EVEN WHEN THERE IS NO LAYERS SPECIFICATION. This makes it consistent with "Extrude Point" and "Extrude Line", which always create new curves and surfaces, respectively. Important Note: you will have to modify your old .geo files to avoid duplicate volume definitions if you use "Extrude Surface" without extruding the mesh (i.e., without the "Layers" command). These duplicate volumes would be harmless, but they would srew up your physical volume definitions later on... * Solution 1: use the new volumes (recommended). To do this, just remove your old extra volume definitions and let Gmsh create the extruded volumes for you. (To retrieve the volume number created by Gmsh, use "aa[] = Extrude Surface {...};;": the volume number is "aa[1]".) * Solution 2: keep the old volumes. a) clean way: retrieve the new volume number (aa[] = Extrude Surface {...};;) and delete the new volume with "Delete { Volume aa[1]; }" b) dirty (but handy) way: since, in order to create the new volumes with the less impact possible, Gmsh uses "low" numbers (actually, forcing "Geometry.OldNewreg=0") for the new volumes, just remove all "low number volumes". For example, if you have 4 "Extrude Surface" in your file, you can then just do "Delete{ Volume {1:4}; }" Voila :-)
-
- Jul 01, 2004
-
-
Christophe Geuzaine authored
bulletproof FindCurve/Surface + uniformize error messages
-
- Jun 08, 2004
-
-
Christophe Geuzaine authored
add @. after color specs in Fl_Browser: otherwise strings that start with a digit don't get printed
-
- May 31, 2004
-
-
Christophe Geuzaine authored
- set VectorType to Displacement in Plugin(StreamLines) - shout when a plugin option/name does not exist
-
- May 30, 2004
-
-
Christophe Geuzaine authored
new BoundingBox command to force the computation of the bounding box (useful when there is no geometry and we don't include/merge any views)
-
- May 29, 2004
-
-
Christophe Geuzaine authored
- generalized vertex arrays to handle quads - added missing Ellispe ... Plane ... in parser
-