[doe 2.1e] parametric setup

asked 2016-09-17 00:12:51 -0500

ngkhanh
2156 ●1 ●3 ●12

updated 2016-09-18 13:10:55 -0500

I'm trying to setup parametric for air change value as follows:

INPUT LOADS  ..   
PARAMETER PAIR = 0.2 ..   
....   
AIR-CHANGES/HR       =PAIR TIMES 2.0  
END ..  
COMPUTE LOADS ..  
COMPUTE SYSTEMS ..  
COMPUTE PLANT ..  
PARAMETRIC-INPUT FOR LOADS ..  
PARAMETER AIR-CHANGES/HR    =1.0 
END ..   
COMPUTE LOADS ..    
COMPUTE SYSTEMS ..  
COMPUTE PLANT ..   
STOP ..

It runs two times but the second run is not updated with new air-change/hr value. What's wrong with my syntax?
Have any script/program to automatically export doe 2.1e report to BEPS ?

edit retag flag offensive close merge delete

Comments

@Joe Huang, this one's for you!

__AmirRoth__ ( 2016-09-17 09:28:51 -0500 )edit

add a comment

answered 2016-09-20 17:03:42 -0500

Joe Huang
2712 ●4 ●13

updated 2016-09-20 17:10:26 -0500

Thanks to Amir for bringing this to my attention, as I haven't been paying much attention to Unmet Hours the past several months.

I actually stopped using PARAMETER in DOE-2 a long time ago, because I find that macros can do the same thing and are much more flexible.

In answer to your question above, I think that when DOEBDL interprets PARAMETRIC-INPUT, it will just do a sequential substitution for the items called out as PARAMETERs in the original base input file. Since you have defined PAIR as a PARAMETER, I think you should continue to operate on that keyword (PAIR) rather than to create a new PARAMETER in the PARAMETRIC-INPUT FOR LOADS, i.e., you should try:

PARAMETRIC-INPUT FOR LOADS ..

PARAMETER PAIR = 0.5

By the way, macro inputs for doing the same thing would be:

##set1 PAIR 0.20 (first run)

##set1 PAIR 0.50 (second run)

later

AIR-CHANGES/HR = #[ PAIR[] * 2.0]

I don't think macros will work with PARAMETRIC-INPUT, but I've never liked that feature anyway, because I'd much rather create and make separate DOE-2 runs instead of making one large run with a series of parametric changes that I would then have to parse to get the results I want.

edit flag offensive delete link

Comments

@Joe Huang Have any pathway to parse the BEPS report from many files to a csv or excel file ? Thank

ngkhanh ( 2016-09-21 20:46:43 -0500 )edit

Sure, since DOE-2 output files are ASCII text files, I've been writing awk scripts for decades to parse the output for what I want and then direct that to a summary text file for which each DOE-2 run is represented by a single line with the run name, followed by the annual electricity usage by end-use, and then the gas usage by end-use. I use awk because that's what I learned in the early 80's,but I'm sure other scripts like Python can work as well. What my post-processing awk scripts do is to look for a unique pattern, ,like "BEPU - ", etc., and then start counting lines.

Joe Huang ( 2016-09-21 21:21:58 -0500 )edit

Sorry. Ran out of space on the last comment. I will respond as an answer on your other question about how to do parametric runs in DOE-2, in which I'll show examples of the awk scripts I use to pre-process the input files and post-process the output files. I've promised to do that for a DOE-2 user group anyway. My main message would be *Learn awk and conquer the world ! :-):-)

Joe Huang ( 2016-09-21 21:25:02 -0500 )edit

@Joe Huang: Thank you very much. Would you insert here or need a new question on unmethours for parsing doe2 result ? Hopefully, someone did it with Python or Ruby :))

ngkhanh ( 2016-09-21 21:42:19 -0500 )edit

I'd like to jump in and add: I've been developing some similar stuff with Python, specifically with mind to extract select outputs from doe2.2/2.3 borne SIM files. I'm actually wrestling in the present with re-tooling (breaking & rebuilding) a previously working script to generate a CSV in a format compliant wtih dview for easy visualizations. Would be happy to compare notes sometime to see how others are accomplishing similar tasks - maybe we can learn from each other!