Author |
Message |
Dr. Wieland Beckert (wbeckert)
New member Username: wbeckert
Post Number: 2 Registered: 07-2003
| Posted on Tuesday, August 01, 2006 - 07:21 am: | |
While doing a quite complex 1D analysis with Flexpde 5.10 I noticed, that the *.dbg file, which is written by Flexpde, becomes extremely large (2GByte and more). After some time my disc drive is full and the session chrashs. Is there any option to turn the writing of the *.dbg file off? Thank you very much. |
Dr. Wieland Beckert (wbeckert)
Junior Member Username: wbeckert
Post Number: 3 Registered: 07-2003
| Posted on Thursday, August 03, 2006 - 11:46 am: | |
Sorry, I've finally found the reason for the huge *.dbg file: I had excessively coupled and deeply nested dependencies in the "material" parameters. After hiding them from the symbolic interpreter by masking them with PASSIVE() operator, the *.dbg-file shrinked to 200 MB. Nevertheless I think it could be reasonable to have an option to turn the *.dbg file off since it tends to become very large in complicated analyses. |
Robert G. Nelson (rgnelson)
Moderator Username: rgnelson
Post Number: 668 Registered: 06-2003
| Posted on Thursday, August 03, 2006 - 07:02 pm: | |
Somewhere along the chain of version 5 releases, we decided to default the printing of resultant computation expressions for reference. In our test problems, the files were of modest size. It didn't occur to us that in some cases the output files would get so huge. We will fix this in the next maintenance release.
|
Robert G. Nelson (rgnelson)
Moderator Username: rgnelson
Post Number: 669 Registered: 06-2003
| Posted on Thursday, August 03, 2006 - 08:17 pm: | |
I have posted a developmental copy of version 5.0.12 for Windows at www.pdesolutions.com/download/xfpde5012x2win.exe This is a self-extracting archive containing only flexpde5.exe, it is not a full install. (If you need a different platform, let me know) This version supresses the listing of computation formulas. You can get them back by including SELECT DEBUG(FORMULAS) in your script. If your problem still generates large DBG files, send me the script. There may be a residual debug statement somewhere.
|