[Equest-users] 65000 character limit
The Watt Doctors - Dave Weigel
Dave.Weigel at thewattdoctors.com
Sat Oct 6 13:46:44 PDT 2012
Thank you Nick and Mike!
I also heard from Jeff Hirsch - “The next release coming very soon will address this issue.”
Best to all,
Dave
From: Nick Caton
Sent: Friday, October 05, 2012 3:58 PM
To: The Watt Doctors - Dave Weigel
Cc: Mike Busman
Subject: RE: [Equest-users] 65000 character limit
Awesome - sounds like you’ve got a plan of action!
Extra thought: It’s been my experience for “necessary simplification” that you can come off a lot more professional if you make a point to emphasis your “command-decision making” abilities rather than highlight the inherent limits of your tools-of-choice. Making the call to simplify is primarily part of your modeling expertise – the eQuest limits capped at tens-of-thousands of elements are merely a supporting factoid ;).
I didn’t intentionally not copy the list by the way … feel free to forward this along if you like =).
Best wishes!
~Nick
NICK CATON, P.E.
SENIOR ENGINEER
Smith & Boucher Engineers
25501 west valley parkway, suite 200
olathe, ks 66061
direct 913.344.0036
fax 913.345.0617
www.smithboucher.com
From: The Watt Doctors - Dave Weigel [mailto:Dave.Weigel at thewattdoctors.com]
Sent: Friday, October 05, 2012 1:09 PM
To: Nick Caton
Cc: Mike Busman
Subject: Re: [Equest-users] 65000 character limit
As always, thanks tons Nick.
You too, Mike.
I can do some severe simplifying as you and Michael have suggested. I’ll back off of adding zones and avoid the spreadsheet tab until my 3-D rendering matches the elevations and I can spin it around. The owner will have his pretty rendering to show off.
I now have a valid reason to simplify, which I can show him on-screen by reproducing the error.
By the way, I also received an e-mail from Jeff Hirsch that said, “The next release coming very soon will address this issue.” I’ll share that with the users’ group in just a bit.
Dave
From: Nick Caton
Sent: Friday, October 05, 2012 12:52 PM
To: Busman, Michael R ; Dave Weigel
Subject: RE: [Equest-users] 65000 character limit
I recall running into this myself. You are looking at a problem of sheer quantities (too many elements).
If I’m not mistaken, I’ve run into this issue in detailed mode in the past and the model would actually simulate just fine – I just couldn’t use the spreadsheet views for edits thereafter as I’d get a similar error (program didn’t freeze/crash out – might be OS related).
All told, if you’re still in wizards, you’re in a good place to re-evaluate options to simplify your model, as Michael is suggesting. Perhaps you can use multipliers to repeat a floor/space, or a series of windows or other elements could be merged into a acceptable single ‘equivalent’ for modeling purposes. Because you’re getting this error on opening the spreadsheet view under the building shell tab, you will almost certainly find your solution by reducing the quantity of surfaces, windows, doors, spaces, floors, shells, or any combination thereof. If this specifically is occurs upon/after selecting one of your windows in the component tree or 3D view, it may follow your solution should target reducing door/window quantities first.
Attached discussion addressed a different problem for another project with size concerns, and touched on some extra thoughts regarding model simplification – may be of interest for further reading. There’s more discussions in the archives on the topic if you’re looking for more.
~Nick
NICK CATON, P.E.
SENIOR ENGINEER
Smith & Boucher Engineers
25501 west valley parkway, suite 200
olathe, ks 66061
direct 913.344.0036
fax 913.345.0617
www.smithboucher.com
From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Busman, Michael R
Sent: Friday, October 05, 2012 10:03 AM
To: Dave Weigel; equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] 65000 character limit
Dave,
I have never encountered this error before so I can only speculate that there is a limit on the input data. Looking at the screen shot, it appears that each individual window is being defined. By extension that would probably mean each individual space is also being defined. Unless there is a compelling reason for such complexity, I generally try to limit complexity to what is necessary to reasonably represent the building construction, systems, and operations. For example, if it is not really necessary to define every window, I would define the glazing as a % of the gross wall area by compass orientation if that level of simplification will still work for your modeling requirements.
Just my 2 cents worth.
My best,
Mike
Michael R. Busman, CEM
Lead Project Engineer II
Chevron Energy Solutions
A Division of Chevron U.S.A., Inc.
145 S. State College Blvd.
Brea, CA 92821
Direct 714-671-3561
Fax 714-671-3438
eFax 866-420-0335 (Include my Full Name followed by "CAI:MHTZ" on Cover Sheet)
Mobile 310-387-2083
mbusman at chevron.com
From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Dave Weigel
Sent: Friday, October 05, 2012 7:47 AM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] 65000 character limit
Greetings,
Here's the error message (screen shot attached too): "Selection list exceeds maximum length of 65,500 characters (72,692 required). Notify program support representative."
Once it appears, there is no way to continue or quit eQuest. Windows task manager - end process - is necessary.
It happens when spreadsheet mode is selected under building shell in the Wizard. We're not quite ready to switch to detailed edit mode. We are really close to finishing this model, have we gone over the limit in shell / space complexity?
It's kind of scary, please share any experience or hints.
Thank you all,
Dave
David R. Weigel, PE
Managing Member
1189 Golden Circle SW, Lilburn GA 30047
678-353-6941 office 901-619-1716 cell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121006/852f5425/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121006/852f5425/attachment-0002.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 17052 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121006/852f5425/attachment-0002.gif>
More information about the Equest-users
mailing list