[Equest-users] pdl file blows up

Wed Apr 17 09:44:47 PDT 2019

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<mailto:nicholas.caton at se.com>

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

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

From: Equest-users <equest-users-bounces at lists.onebuilding.org> On Behalf Of Lapierre, Patrick via Equest-users
Sent: Wednesday, April 17, 2019 8:48 AM
To: Jones, Christopher <Christopher.r.Jones at wsp.com>
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] pdl file blows up

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]<https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.bpa.ca%2F&data=02%7C01%7CNicholas.Caton%40se.com%7Cb2bfd90154734fc387eb08d6c33b5a76%7C6e51e1adc54b4b39b5980ffe9ae68fef%7C0%7C0%7C636911057081663579&sdata=p3bRn5XYbN33B%2FZxRwybwuiGc6XRtu4sdhvv8F%2FfXoU%3D&reserved=0>

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

De : Equest-users <equest-users-bounces at lists.onebuilding.org<mailto:equest-users-bounces at lists.onebuilding.org>> De la part de Jones, Christopher via Equest-users
Envoyé : 17 avril 2019 09:38
À : equest-users at lists.onebuilding.org<mailto: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.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 255 bytes
Desc: image003.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 8477 bytes
Desc: image004.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 1706 bytes
Desc: image005.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1860 bytes
Desc: image006.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 7120 bytes
Desc: oledata.mso
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20190417/ad6608fc/attachment.obj>