pdl file blows up

4 posts / 0 new
Last post

I am wondering if anyone knows why the .pdl file blows up occasionally. It hasn't happened to me before yesterday. eQuest became slower and slower eventually hanging the computer. The .pdl file had grown to 1.8 GB. Didn't help to delete the file. I uninstalled and reinstalled eQuest in order to move ahead.

Christopher R Jones, P.Eng.
T+ 1 416-644-0252

[cid:image001.png at 01D4F501.43A116B0]

Jones, Christopher2's picture
Joined: 2017-10-12
Reputation: 0

Hi Christopher,

I've had this happen on occasion when I repeatedly load and reload the same
model for some reason or another (e.g. manually editing the INP or PRD
files and reopening the model to see the changes within eQuest). The file
sizes seem to max out at 4.5 GB. I find the solution is to delete *both *large
PDL files (projectname.PDL and ~reinitializ.PDL) and then reopen the model.
If that doesn't work, try deleting everything but the .PD2, .INP, and .PRD
files.

Kind regards,
Calvin

On Wed, Apr 17, 2019 at 9:38 AM Jones, Christopher via Equest-users <

--
*Calvin Chu, EIT*
Energy Modeler
646-780-5536 | cchu at brightpower.com
www.brightpower.com

11 Hanover Square, 21st Floor
New York, NY 10005

Anonymous's picture
Anonymous

>From my past experiences, the .pdl file only grows from successive load/save operations on a model, as if it's only a input/output log file.
When it grows out of proportion, it does slow the model and usually deleting it usually solves the issue for me.

If it doesn't work I'd say keep only the .pd2 and .inp files and try to reopen it.

[Bouthillette Parizeau]

Patrick Lapierre_ing. BEMP
D?veloppement durable et Efficacit? ?nerg?tique
plapierre at bpa.ca | t: 5143833747x2807

De : Equest-users > De la part de Jones, Christopher via Equest-users
Envoy? : 17 avril 2019 09:38
? : equest-users at lists.onebuilding.org
Objet : [Equest-users] pdl file blows up

I am wondering if anyone knows why the .pdl file blows up occasionally. It hasn't happened to me before yesterday. eQuest became slower and slower eventually hanging the computer. The .pdl file had grown to 1.8 GB. Didn't help to delete the file. I uninstalled and reinstalled eQuest in order to move ahead.

Christopher R Jones, P.Eng.
T+ 1 416-644-0252

[cid:image003.png at 01D4F502.454BEB10]

Avertissement / Disclaimer

Les informations contenues dans le courriel que vous venez de recevoir, y compris les pi?ces jointes, sont destin?es ? l?usage exclusif de la (ou des) personne(s) identifi?e(s) comme destinataires et sont confidentielles. Si vous n?en ?tes pas le destinataire, soyez avis? que tout usage en est interdit. Si vous avez re?u ce courriel par erreur, veuillez le retourner ? l?exp?diteur et le supprimer compl?tement de votre syst?me informatique.

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived.

Patrick Lapierre's picture
Joined: 2015-01-28
Reputation: 0

I?m nodding my head.

Pretty sure the ?L? in PDL is ?log.? I?ve never seen harm come of deleting the PDL, and that normally does fix things right up.

Separate from monster PDL?s, it is as not common in this age where >4Gb of system ram is the norm (not suggesting a causality), but on rare occasion I have observed eQuest maxing out my system resources (via task manager) and eating up all of my memory, again typically resolved with a reboot, fresh cup of coffee, and a few stretches for good measure to get the kinks out. Hindsight 20/20: such headaches born of model size and complexity are oftentimes avoidable with the pursuit of simpler models (i.e. multipliers, simpler geometries, judicious application of powerful but sometimes weighty expressions/parametrization) ? never a bad idea so it bears repeating, though I recognize this is commonly non-constructive advice by the time problems of model complexity/size come to full realization.

~Nick

[cid:image003.png at 01D4F512.F2735C50]
Nick Caton, P.E., BEMP
Senior Energy Engineer
Regional Energy Engineering Manager
Energy and Sustainability Services
Energy Performance Contracting

D
M
F
E

913 . 564 . 6361
785 . 410 . 3317
913 . 564 . 6380
nicholas.caton at se.com

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[cid:image004.png at 01D4F512.F2735C50]

Nicholas Caton2's picture
Offline
Joined: 2019-03-25
Reputation: 0