One possible strategy could be defining Material, Layers and Construction
in textpad and save as .inp file. Later based on project requirement you
can actually import this to the eQuest.
You can also add the constructions/layers/materials to your eQuest library file (eQ_lib.dat). If you are not use to working with the library file, I suggest you confirm all constructions via a 'shoe box' model before you implement them in an actual project. I have included a sample library entry for your benefit.
Material
$LIBRARY-ENTRY Steel Wall Mat 2B Stucco MAT 90.1 04 Steel Wall
$Steel Wall Mat 2B Stucco,
TYPE=PROPERTIES TH=0.0833 COND=0.4167 DENS=116 S-H=0.2 ..
Layer
$LIBRARY-ENTRY 90.1 Steel Framed Wall 5B Lay LA ETC Code Walls
MAT=("Steel Wall Mat 5B Stucco",
"Steel Wall Mat 5B Rigid Foam", "Steel Wall Mat 5B Vary Insul",
"Steel Wall Mat 5B plywd 5/8", "Steel Wall Mat 5B Assembly",
"Steel Wall Mat 5B GypBd 1/2")
TH=( &D, &D, {.00001} ) ..
Construction
$LIBRARY-ENTRY 90.1 Steel Framed Wall 5B Cons CONSTRUCTION ETC Code Walls
TYPE = LAYERS
LAYERS = "90.1 Steel Framed Wall 5B Lay" ..
Are there any rules to make a new library entry? For example, in your case,
can I use the name "Daniel Stucco" instead of "Steel Wall Mat 2B Stucco"??
I am looking forward to your response.
As far as I know, eQuest limits the number of characters you can use for an input. I am unaware of what the character limit is. Additionally, certain characters are not allowed to be used in the code as a name, i.e. $,.. ,etc.
To answer your question more simply, you can use whatever name you want as long as the name also works when created manually in the detailed interface.
For a more detailed answer, please reference page 25 of the following link:
http://doe2.com/download/DOE-22/DOE22Vol1-Basics.pdf
Actually, I already tried it on DOE 2.2 many times. I even sent email to
DOE 2.2 developers but I got no response from them.
Below is the original email. I also put it on this email list several days
ago:
"I need some help with my DOE library user defined entry. I created a new
entry called "Daniel" in test.dat. And I also used this entry in my input
file. But when I run DOE 2.2 to simulate the input file. I failed. What the
problem could be? Is there any rules that I should follow to create a new
entry?
One possible strategy could be defining Material, Layers and Construction
in textpad and save as .inp file. Later based on project requirement you
can actually import this to the eQuest.
Hope this helps!
You can also add the constructions/layers/materials to your eQuest library file (eQ_lib.dat). If you are not use to working with the library file, I suggest you confirm all constructions via a 'shoe box' model before you implement them in an actual project. I have included a sample library entry for your benefit.
Material
$LIBRARY-ENTRY Steel Wall Mat 2B Stucco MAT 90.1 04 Steel Wall
$Steel Wall Mat 2B Stucco,
TYPE=PROPERTIES TH=0.0833 COND=0.4167 DENS=116 S-H=0.2 ..
Layer
$LIBRARY-ENTRY 90.1 Steel Framed Wall 5B Lay LA ETC Code Walls
MAT=("Steel Wall Mat 5B Stucco",
"Steel Wall Mat 5B Rigid Foam", "Steel Wall Mat 5B Vary Insul",
"Steel Wall Mat 5B plywd 5/8", "Steel Wall Mat 5B Assembly",
"Steel Wall Mat 5B GypBd 1/2")
TH=( &D, &D, {.00001} ) ..
Construction
$LIBRARY-ENTRY 90.1 Steel Framed Wall 5B Cons CONSTRUCTION ETC Code Walls
TYPE = LAYERS
LAYERS = "90.1 Steel Framed Wall 5B Lay" ..
Thanks,
David Griffin
Hi David,
Are there any rules to make a new library entry? For example, in your case,
can I use the name "Daniel Stucco" instead of "Steel Wall Mat 2B Stucco"??
I am looking forward to your response.
Thanks,
--
Daniel Shen
As far as I know, eQuest limits the number of characters you can use for an input. I am unaware of what the character limit is. Additionally, certain characters are not allowed to be used in the code as a name, i.e. $,.. ,etc.
To answer your question more simply, you can use whatever name you want as long as the name also works when created manually in the detailed interface.
For a more detailed answer, please reference page 25 of the following link:
http://doe2.com/download/DOE-22/DOE22Vol1-Basics.pdf
Thanks,
David Griffin
Hi David,
Actually, I already tried it on DOE 2.2 many times. I even sent email to
DOE 2.2 developers but I got no response from them.
Below is the original email. I also put it on this email list several days
ago:
"I need some help with my DOE library user defined entry. I created a new
entry called "Daniel" in test.dat. And I also used this entry in my input
file. But when I run DOE 2.2 to simulate the input file. I failed. What the
problem could be? Is there any rules that I should follow to create a new
entry?
I am looking forward to your help.
Thanks,"
Attached are the screen shots:
*1)User library file*
[image: Inline image 4]
*2)Input file:*
[image: Inline image 3]
*3)DOE2.2 interface*
[image: Inline image 2]
*4)Error message:*
[image: Inline image 1]
--
Daniel Shen