XANSYS Message: 18524 [Go back to message list] [bookmark on del.icio.us]
No rating yet Subject: Re: Save your work Author: Martin Liddle Date: 2000-11-30 15:26:00In article <1F630DA3C567D411AA4F00508B693BC62CDF74@e... on.se>, Jason Mareno (EUS) writes > If you are not into manually creating input files, but do not wish > to keep db files, consider the LGWRITE command. This will 'build' > an input file (text file) for you by extracting your command > history from the db file (specify essential commands only). You > can recover your complete database (geom + FEA entities) easily in > the future by using /INPUT.
Thanks. I am aware of the LGWRITE command. Its fine if you are smart enough to do things in a nice orderly fashion. Sadly my model development process doesn't usually work like that. I save a succession of .db files as I develop a model. If I hit problems with booleans, changes in modelling strategy etc I often rename a saved db file to file.db and resume from that. I just find it hard enough to develop models without worrying about archiving them at the same time.
> This works for big 3D models that originate from CAD and are meshed > in the GUI. I store basic db info this way, but keep all of my > load and solution commands as a separate file.
That matches my approach.
>Usually my models > are generated in the GUI, then run in batch using an input file to > specify load/solution stuff. We generate enough jpegs that I'm > comfortable deleting rst file after a few months - if I really need > it, it can be re-run.
I back things up on to DAT tape and keep them longer.
> Note that you must also keep the parent CAD file (parasolid, IGES, > whatever) for this to work - one of the first lines in the log file > will be an import command to bring in your CAD geometry.
Agreed.
> If you're a real disk miser, you can often compress the essential > log file to ~15% of its already small size.