Thanks for your answers.
Yes, the batch mode seems to use the same random seed, when it is called
multiple times in a row. But the seed (also for the batch mode) changes,
when the GUI is started.
Is that intended?
Best regards
Andreas
On 05/03/2011 09:55 AM, Andreas Puettmann wrote:
On 05/03/2011 01:26 AM, Geordie McBain wrote:
Hello. I believe Gmsh's meshing algorithms are random, so even
repeating identically the meshing and saving options might give you a
different mesh.
Ah OK, thank you for your hints. I noticed now that indeed none of the
results I sent is deterministic.
However, I can reproduce the exact same .msh file when I do not use
the GUI but run the mesher in batch mode:
$ gmsh -3 column.geo
The console output tells me that in both cases (GUI and batch) the
same (?) Delaunay algorithm is used. So why does the GUI based
approach include a random element, while the batch mode obviously does
not? What is the difference between them? Maybe one of the developers
can shed some light on that?
Andreas
--
Dipl.-Ing. Andreas Puettmann
German Research School for
Simulation Sciences GmbH
c/o Institute of Bio- and Geosciences 1
52425 Jülich | Germany
Tel +49 2461 61 5541
Fax +49 2461 61 3870
Web www.grs-sim.de
Members: Forschungszentrum Jülich GmbH | RWTH Aachen University
Registered in the commercial register of the local court of
Düren (Amtsgericht Düren) under registration number HRB 5268
Registered office: Jülich
Executive board: Prof. Marek Behr, Ph.D | Dr. Norbert Drewes
_______________________________________________
gmsh mailing list
[email protected]
http://www.geuz.org/mailman/listinfo/gmsh
