broncodev/gmsh-inp: Some routines that I use to create XML files (.feb) from Gmsh. It uses the .inp export from Gmsh

Some routines that I use to create XML files (.feb) from Gmsh. It uses the .inp export from Gmsh

broncodev 85839004ee fixed typo on inp_feb_replace_children_by_tag (prevented replacement)		пре 5 година
.gitignore	1867030fd4 Takes a .feb file and modifies NodeSet structures according to a .inp	пре 5 година
ChangeLog	1867030fd4 Takes a .feb file and modifies NodeSet structures according to a .inp	пре 5 година
README	e706b0229e Expanded README	пре 5 година
check_path.org	a7211f1826 added import headers, optional printing of info, got rid of getroot	пре 5 година
geo2secinp.org	a7211f1826 added import headers, optional printing of info, got rid of getroot	пре 5 година
gmsh_geo2inp_3d.org	a7211f1826 added import headers, optional printing of info, got rid of getroot	пре 5 година
gmshinp2feb.org	85839004ee fixed typo on inp_feb_replace_children_by_tag (prevented replacement)	пре 5 година
inpdigest.org	a7211f1826 added import headers, optional printing of info, got rid of getroot	пре 5 година

		
				README
			
				I created this code, because I needed to process meshes from Gmsh, and there was no .inp parser available. Firstly, I could not get gmshpy (from Gmsh) to run with my office's computer (not my equipment) to test it. The closest that I found were pyFEBio and abapy. The first one did read .inp, but it was not parsing my Gmsh .inp files correctly. The developer told me that keeping the package was in his wish list. I did not find a way to get abapy to read my .inp (seems towards creation from scratch; I could be wrong). I must say that I didn't really think of testing meshio, and I should have. Alas, it didn't work when I ran =mesh = meshio.read(filename)= (https://github.com/nschloe/meshio/issues/249). By that time, I had already done this little project.

Serve yourselves, and enjoy.