OneLab GUI with .brep files - how to
Related to #1732 (closed).
Dear Christophe,
Thank you for your clarification and this helps a lot. I didn't think it was obvious from the documentation that there is such an intricate relation between .geo files and OpenCASCADE ("occ") kernel. It seems to me that one could in .geo file use occ kernel, its full potential, to create geometry. However, such a geometry could not always be saved as a .geo or .geo_unrolled file. With Python API, this is very clear. If one uses occ kernel, the geometry must be (to capture all features) saved in the .brep or .step file. None of them is human-friendly, but this is no problem as the Python API could have a human-friendly input file to create an occ geometry that gets saved in one of these files.
I used occ kernel and saved geometry to .brep files. I have noticed that the behaviour of OneLab GUI seems different for .geo and .brep files. Geometry from the .geo file seems to be loaded by default if one opens .pro file with the same name. However, the .brep files are not loaded in such a default way (well, at least not for me). I am wondering what is the recommended way of opening a model defined in .pro and .brep files in OneLab GUI. Should we use the merge feature or add a line in .pro file to load the .brep file, or there is a better way?
Many thanks and all the best, Mariusz