[MOAB-dev] ReadCGM Behaviour

[Tim Tautges]

If you followed the MOAB model of things, the reader would shut down the 
CGM instance when it was done.  However, CGM sometimes (all times?) 
doesn't gracefully start up / shut down multiple times in a process, and 
by design doesn't support multiple instances alive at the same time.  So 
that's why the CGM instance remains alive after reading is done.

Why the reader leaves the model in CGM when it's done reading isn't 
clear.  Ideally, it should be deleted, with that being controlled by a 
reader option (defaulted to delete).  I guess there could also be an 
option determining whether CGM is shut down after the read is done, but 
I'm not sure what the proper default should be in that case.

- tim

On 11/19/2014 01:15 PM, shriwise wrote:
> Hi all,
>
> I've run into this a couple of times and I'd like to know if there is a
> reason for this behaviour that I'm unaware of . When loading a .sat file
> using moab's load_file call, the geometry remains in the CGM instance.
> So if a user is to load a separate file or the same file again, the moab
> instance will retrieve a duplicate mesh of the original file loaded. Was
> this intentional?
>
> This can be mitigated by going into cgm and deleting the geometry
> manually, but requires programs to link to cgm as well...
>
>
> Cheers,
>

-- 
Timothy J. Tautges
Manager, Directed Meshing
Phone: 608-354-1459
timothy.tautges at cd-adapco.com