bamg2geo(1rheolef)
π bamg2geo β the glow-up your bamg mesh deserves π
okay so bestie, you know that whole rheolef thing? this is one of its little helper cuties, living in section 1rheolef of the manual. she's not complicated, she's just essential, and honestly? she ate. let's get into it. π
β¨ NAME β¨
bamg2geo β convert bamg mesh in geo format (rheolef-7.2)
like. that's the whole job. she takes your bamg mesh and she makes it geo. no cap. π
πΈ SYNOPSIS πΈ
bamg2geo [options] file[.bamg] file[.dmn]
π¦ DESCRIPTION π¦
So here's the tea. bamg2geo takes a .bamg file and turns it into a .geo file. That's the entire personality and honestly, respect. π
The output goes to standard output, so if you were expecting a surprise file to appear, no bestie, you gotta redirect it yourself. Redirect is the moment, redirect is the vibe. β¨
Now, the .dmn file β this one matters. The bamg mesh generator uses numbers as domain labels instead of names (a little chaotic of it, ngl), so the .dmn file is what tells us what those numbers are actually called. It's the translator. It's the friend who explains what the group chat is talking about. π«Ά
And when no files are provided at all? Standard input gets used. lowkey iconic behaviour. π
π EXAMPLES π
okay here's the whole pipeline, served fresh:
bamg -g toto.bamgcad -o toto.bamg
bamg2geo toto.bamg toto.dmn > toto.geo
see how she reads toto.bamg and toto.dmn, then pours everything into toto.geo? chef's kiss. π
π THE BAMG CAD FILE π
The .bamgcad file describes the boundary of the mesh geometry. That's it, that's her whole job. Here's a basic example so you can see the shape of it:
MeshVersionFormatted
0
Dimension
2
Vertices
4
0 0 1
1 0 2
1 1 3
0 1 4
Edges
4
1 2 101
2 3 102
3 4 103
4 1 104
hVertices
0.1 0.1 0.1 0.1
and if you need more on that, go see bamg(1). iykyk. π
π DOMAIN NAME FILE π
So the .dmn file defines the boundary domain names used by Rheolef β because bamg is out here using numeric labels for domains like it's above naming things. π Here's an example:
EdgeDomainNames
4
bottom
right
top
left
but wait, there's more, because she can also specify additional vertices domain:
EdgeDomainNames
4
bottom
right
top
left
VertexDomainNames
4
left_bottom
right_bottom
right_top
left_top
and the vertex domain names? genuinely useful for some special boundary conditions. not me being obsessed with a domain name file but here we are. β
π OPTIONS π
-cartesian-rz-zr
Specifies the coordinate system, bestie. The default is cartesian, while -rz and -zr denote some axisymmetric coordinate systems. And just so you know β recall that most of Rheolef codes are coordinate-system independent, and the coordinate system is specified in the geometry file .geo. so like, don't stress about it living here forever. it's a passing vibe. β¨
π§ IMPLEMENTATION π§
This documentation has been generated from file main/sbin/bamg2geo.cc
(that's the source of truth, she's the main character, the rest of us are just reading her diary.) π
π AUTHOR π
Pierre Saramito <Pierre.Saramito@imag.fr>
π₯ COPYRIGHT π₯
Copyright (C) 2000-2018 Pierre Saramito <Pierre.Saramito@imag.fr> GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
okay important real talk for one sec: NO WARRANTY, fr fr. free software means you can change it and redistribute it, but nobody's coming to save you if it goes sideways. that's just the deal. π«Ά
and that's the whole page, bestie!! π this one came from rheolef, Version 7.2, and she's filed under bamg2geo(1rheolef) β go forth and convert your meshes, you absolute icon. ππ π
π¦ where this page comes from
- debian trixie: rheolef 7.2-4 Β· GPL-3.0-or-later
- ubuntu noble: rheolef 7.2-3build5 Β· GPL-3.0-or-later
- ubuntu questing: rheolef 7.2-4build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms