[Equest-users] Saving Schedules to Library

[Paul Diglio]

Instead of 'snippets' for the .inp file has anyone tried entering data directly 
into the eQ_Lib.dat file?  It seems that it would be handy to have custom VRV 
curve fits are part of the library we use every day.  


Paul Diglio




________________________________
From: Nick Caton <ncaton at smithboucher.com>
To: Pasha Korber-Gonzalez <pasha.pkconsulting at gmail.com>; Richard Auffermann 
<rauffermann at dagherengineering.com>
Cc: equest-users at lists.onebuilding.org
Sent: Mon, June 13, 2011 4:11:45 PM
Subject: Re: [Equest-users] Saving Schedules to Library

 
To Pasha’s concerns – I am personally very comfortable with the import function 
placing things in the appropriate locations, but that is based solely on my own 
personal investigation and tinkering with the program when I first explored the 
possiblities.  I’ve yet to come across any issues, but until you do feel 
comfortable, you can always import to a copy of your actual project to verify 
the result before proceeding.  Constructions end up listed with existing 
constructions, annual/week/day schedules end up with their counterparts, and so 
forth as far as I’ve been able to tell.
 
Order of systems where OA-FROM-SYSTEM is in play is an independent and isolated 
quirk of the eQuest/DOE2 that you may have to deal with even if you don’t use 
importing, and neither is it terribly difficult to resolve once it’s brought to 
your attention (likely on trying to simulate).  I guess I’m just saying that 
this particular issue isn’t a reason to avoid importing where it can save time… 

 
That said, while I have imported portions of airside/waterside systems into new 
projects for modification/use, I have *always* built DOAS systems “from scratch” 
on a project-by-project basis, when I am modeling them distinct from the systems 
served.  Importing an independent DOAS and its components would be a tricky 
endeavor, to be sure...  I will likely consider importing DOAS setups more 
viable and time-efficient if/when an independent DOAS system type defined in 
future versions of eQuest/DOE2.  

 
To Richard – creating an .inp snippet of simpler items like a schedules or 
constructions becomes time-efficient the very first time you import into another 
project, I promise ;)!  Once you have a smallish library of re-useable 
constructions/schedules, you will be able to transform multiple 5-to-30 minute 
exercises into a matter of a few clicks.  
 
To be clear, that’s no reason to go cataloguing a library of everything you 
“might” use in the future (that would quickly become time-inefficient), but 
building your library from past projects as the need arises is probably the 
balanced approach.  For example… “Ah, I wish I had a schedule to describe this 
photocell/timer-controlled exterior lighting… Wait!  I did that legwork for an 
earlier model!  *open/copy/paste/save/import*  Life is good!”  If your memory 
isn’t razor sharp, the other “ideal” time to catalogue .inp snippets would be at 
the conclusion of a project, while the model is fresh in your mind, to identify 
what items required research/legwork you’d like to avoid in the future.
 
Generally – any development of DOE2/eQuest is welcome in my eyes, great or 
small, and .  I trust where both “difficult” and “simple” developments are on 
the table, the priorities of addressing fundamental limitations against user 
interface improvements will be weighed appropriately against the resources that 
become available.  I’m just counting myself lucky to be modeling in an era that 
doesn’t require punch cards and ticker tape =)!
 
~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:Pasha Korber-Gonzalez [mailto:pasha.pkconsulting at gmail.com] 
Sent: Monday, June 13, 2011 1:32 PM
To: Richard Auffermann
Cc: Nick Caton; Paul Riemer; equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Saving Schedules to Library
 
If I had to bet on the developers including that function soon, I would say 
you'd be luckier to bet that your grandkids will see that feature...here's why:
 
The great developers of eQuest are by foundation HVAC designers---they are not 
software developers or programmers by trade or even family tree.  ;)
 
Therefore this is how it goes for most simulators who are using eQuest today.   
If I had the chance to talk to Jeff & Steve and guys I would be more inclined to 
ask them to quickly develop a way that VRV systems and DOAS systems can be 
easily modeled in DOE-2.2/eQuest, RATHER than ask them to spend thier valuable 
development time creating a library function in eQuest.
 
If you had your 'druthers' which would you choose?
 
That's also why some of the other basic functions in eQuest, (i.e. it looks like 
a spreadsheet, but doesn't act like one...) are not further developed or 
available either.  There is more than enough work to be done to just get the 
guts of DOE-2.2 working to support the industry for what it needs, rather that 
improve upon the administrative tools in eQuest itself.
 
It's a funny situation, but remember that this whole building simulation things 
is literally a new frontier that we are all discovering an we are still only in 
it's infancy.
 
Pasha  :)
On Mon, Jun 13, 2011 at 12:25 PM, Richard Auffermann 
<rauffermann at dagherengineering.com> wrote:
Thanks Everyone,
 
I just spent some time generating a few schedules and testing things out, this 
could really cut down time once everything is set up. While this has impressive 
capabilities like bring in an entire second building, it is overly complicated 
for doing the simple things, like importing a schedule or construction that you 
will use for every model.
 
I just find it weird and a bit of a tease to have the ‘Save to Library’ option 
present but not actually usable, are they ever going to include that 
functionality? 

 
Richard Auffermann
Design Engineer
DAGHER ENGINEERING,PLLC
29 Broadway, New York, NY 10006
T. 212.480.2591 x122
F. 212.480.2654
rauffermann at dagherengineering.com
www.dagherengineering.com
 
Save Trees, Consider the Environment. Please print only when necessary.
 
This email and any attachments may contain confidential or proprietary 
information and use or distribution is strictly prohibited. If you are not the 
intended recipient, please notify us and delete.  Dagher Engineering, PLLC has 
no responsibility for errors or discrepancies that may occur in the electronic 
transmission of data.
 
 
From:Nick Caton [mailto:ncaton at smithboucher.com] 
Sent: Monday, June 13, 2011 1:25 PM
To: Paul Riemer; Pasha Korber-Gonzalez; Richard Auffermann 

Cc: equest-users at lists.onebuilding.org
Subject:RE: [Equest-users] Saving Schedules to Library 
 
The import function really is the cat’s meow ;).  It’s a great timesaver, even 
if you do need to break out your text editor (once only!).
 
See attached thread from a while ago where I walk everyone through the process, 
and touch on the possibilities.  

 
Starting a personal collection of .inp snippets (schedules, equipment, 
constructions, and so on) is a major mile marker on the path to becoming a great 
eQuest modeler – welcome to the club =).
 
~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 Paul Riemer
Sent: Monday, June 13, 2011 12:07 PM
To: 'Pasha Korber-Gonzalez'; Richard Auffermann
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Saving Schedules to Library
 
Collectively, we have previously suggested to create snippet text.inp files and 
then use the Import command rather than copy paste within a text editor.   So 
you might have a library of inp files for things like constructions, schedules, 
hourly reports, and utility rates (but you can reference saved ones within the 
wizard too).  Of course some things are order dependent like your OA source 
system being ahead of your destination system so if you want a DOAS snippet, you 
may need to manually place that within in the project .inp file.
 
If you like having an inp snippet library then you might also try carrying the 
parametric run description (prd) file from project to project.
 
Paul Riemer, PE, LEED AP
DUNHAM
 
From:equest-users-bounces at lists.onebuilding.org 
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Pasha 
Korber-Gonzalez
Sent: Monday, June 13, 2011 11:36 AM
To: Richard Auffermann
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Saving Schedules to Library
 
At this point in time....Yes, that is the best that we can do as far as I 
know.   I had a client once who told me they were using, or pulling in thier own 
company's "library" data info, but I don't know if this was in the formal sense 
of using the Libraries in eQuest or if they created a seprate file that could be 
read by thier eQuest files to pull in the equipment info they wanted.
 
The only way I know of and use right now is the copy paste method in the input 
file....
 
Pasha
On Mon, Jun 13, 2011 at 9:44 AM, Richard Auffermann 
<rauffermann at dagherengineering.com> wrote:
I am generating schedules for my model and was hoping to save them so I do not 
have to recreate them all the time. There is an option to “Save to Library” but 
it is greyed out and cannot be selected. I looked in the archive and the only 
emails on this topic say that you can only save the text from the input file and 
copy this into new models. Is this the best we can do?
 
Richard Auffermann
Design Engineer
DAGHER ENGINEERING, PLLC
29 Broadway, New York, NY 10006
T. 212.480.2591 x122
F. 212.480.2654
rauffermann at dagherengineering.com
www.dagherengineering.com
 
Save Trees, Consider the Environment. Please print only when necessary.
 
This email and any attachments may contain confidential or proprietary 
information and use or distribution is strictly prohibited. If you are not the 
intended recipient, please notify us and delete.  Dagher Engineering, PLLC has 
no responsibility for errors or discrepancies that may occur in the electronic 
transmission of data.
 

_______________________________________________
Equest-users mailing list
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
To unsubscribe from this mailing list send  a blank message to 
EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110613/1f477c1d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110613/1f477c1d/attachment.jpeg>