[Equest-users] Equest freeze and Spreadsheet refresh error

[Chakraborty, Jude]

Thanks Nick/Aaron,

 

I think going back simplifying the model with weighted zones instead of
the architectural space types (which I had originally modeled with) will
be the best option. Hopefully this will help. I know splitting the model
is another option I can try, but then again, that's an untouched
territory as far as my equest skills are concerned. I will keep you
posted on that.

 

Thanks again,

Jude.

 

Judhajit Chakraborty

Built Ecology Specialist

405 Howard Street

Suite 500            

San Francisco CA 94105

T.   +1 415 398 3833

D.  +1 415 402 5815

F.   +1 415 433 5311

E. judhajit.chakraborty at wspfk.com
<mailto:judhajit.chakraborty at wspfk.com> 

W. built-ecology.com <http://www.built-ecology.com/> 

 

 

A specialist service of WSP Flack + Kurtz

 

From: Nick Caton [mailto:ncaton at smithboucher.com] 
Sent: Friday, October 21, 2011 2:05 PM
To: Dahlstrom, Aaron; Chakraborty, Jude;
equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] Equest freeze and Spreadsheet refresh error

 

Jude/Aaron,

 

When I've run into this circumstance I've taken it as great
justification to go back and simplify the model.  If that's not out of
the question considering your timeline and requirements for accuracy, I
would definitely advise carefully assessing whether you can define
things in a simpler fashion.  Attached recent discussion with James
Chueh seems to parallel your situation and may help you brainstorm a few
ideas.  

 

I've never done this due to sheer model size (only on smaller projects),
but I have advocated "splitting the model" for time-efficiency, and that
may be a good strategy for you in this instance.  Look for an importing
mini guide thread I posted in the archives.

 

The concept is to build up parallel model files that are intentionally
structured/named in a fashion to be import-able into each other.  You
may find splitting your building in two will be functionally manageable
with the eQuest interface, and if/when you need to model both halves of
the building together you can go through the importing hoops.  Before
going far down this path I would personally give this strategy a test
run to be sure the importing feature doesn't cause unique issues due to
model size... uncharted territory!

 

~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
Dahlstrom, Aaron
Sent: Friday, October 21, 2011 3:28 PM
To: Chakraborty, Jude; equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Equest freeze and Spreadsheet refresh error

 

We have definitely have had models that were so large we couldn't make
changes in the spreadsheet view.

It's tedious but one option is to make any changes needed in the dialog
boxes.

 

AD

 

Aaron Dahlstrom , PE, LEED(r) AP

In Posse - A subsidiary of AKF| 1500 Walnut Street, Suite 1414,
Philadelphia, PA 19102 

d: 215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF:
215-735-7290

e: ADahlstrom at in-posse.com | in posse web: www.in-posse.com
<http://www.in-posse.com/>  | akf web: www.akfgroup.com
<http://www.akfgroup.com/> 

 

 

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of
Chakraborty, Jude
Sent: Friday, October 21, 2011 1:41 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Equest freeze and Spreadsheet refresh error

 

Dear all,

 

I am trying to model a high rise 25 floor courthouse building with
multiple shells (12) and  many zones (near 500). I have used floor
multipliers where I could to make the model simpler but it ended up with
60,000 lines and about 7500 components. The .bdl file doesn't show any
error and I have also run a default simulation, which took its time but
gave results without any errors. 

 

Now in the detailed interface, equest freezes whenever I try to make
changes on anything or create a new schedule. Also when I go to the
building shell spreadsheet, it shows this "Spreadsheet refresh error"
with the following text "Selection list exceeds maximum length of 65,500
characters (98,339required). Notify program support representative". 

 

Does it mean that I need to reduce number of spaces/zones or divide my
building into two separate files? Any idea how to solve this problem?

 

Thanks,

Jude.

 

 

 

 


This e-mail may contain information that is confidential, privileged or
otherwise protected from disclosure. If you are not an intended
recipient of this e-mail, do not duplicate or redistribute it by any
means. Please delete it and any attachments and notify the sender that
you have received it in error. Unintended recipients are prohibited from
taking action on the basis of information in this e-mail. E-mail
messages may contain computer viruses or other defects, may not be
accurately replicated on other systems, or may be intercepted, deleted
or interfered without the knowledge of the sender or the intended
recipient. If you are not comfortable with the risks associated with
e-mail messages, you may decide not to use e-mail to communicate with In
Posse. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20111021/b0278e49/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2605 bytes
Desc: image002.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20111021/b0278e49/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20111021/b0278e49/attachment-0002.jpeg>