Re: [EnergyPlus_Support] Re: IMF files & EP Macro

I have attached my input/outputs.

What I have done so far:

Ran EP macro with INP files for M27,M51,M91,M182,Q21,Q23,Q25,Q29, but the M factor is thickness of material, so the name of the material being the same caused their to be an error
I then setup a Je+ parameter to run the M27,M51,M91,M182,Q21, as well as a Je+ parameter to run the 0,90,180,270, while using a EP Macro IMF Referencing INP files for the materials property phase change Q21,Q23,Q25,Q29 DSC data.
Ran a test, but only had 32 jobs validate rather then the expected 68, then the sim results and sim job index did not show the 68 runs per sim.

Any ideas would be very appreciated, thanks to both Jean and Linda for your help so far and thanks DR YI for creating JE+

Many thanks

Jeremiah D. Crossett

CleanTech Analytics

503-688-8951

www.cleantechanalytics.com

This document may contain valuable information proprietary to CleanTech Analytics which is private and confidential. It may not be shared, copied, stored or transmitted in any form without the prior written consent of CleanTech Analytics

On Sun, May 13, 2012 at 10:34 PM, Jean marais <jeannieboef@xxxxxxxxx> wrote:

Hi Jeremiah,

Did you get it to work?

1) Macro functionallity
I don't know Je+. What Linda described as a dummy imf is what I usually use. The imf is "expanded" into just one idf. That means, every txt file that you "include" is written into the same idf. I don't think this is right for you.

2) How I think Je+ works
Having absolutely no idea, I suspect that Je+ wants an idf with everything in it except your PCM object block of code. Then you have that PCM object block of code loaded into the idf. For each parametric run Je+ loads a different PCM block of code. So I think all that Je+ needs is the txt files to be ending with imf and one "master" idf (possibly with imf extension) with all the other normal code in it.

3) Alternatively, e+ has a parametric preprocessor. You can define a parameter as
Contruction, PCM, ! object , object name
$MyParameterObject, ! field 1
bla bla, ! field 2
bla bla, ! field 3
bla; ! field 4

and then a parametric object which describes how many times and what you want to change this...something like

ParameterObject,
MyParameterObject, !parameter object name
myFirstPara, Field 1
mySecondPara, Field 2
my3rdPara; Field 3

What happens is e+ then makes 3 distict idfs where $MyParameterObject is using myFirstPara in the 1rst idf, and mySecondPara in the second and so on.

You'll have to check the syntax...I'm just making this up so you get the idea.

Then from eplaunch you can run these simulations and it will run as many in parallel (one simulation for every available processor on a multi-procecor computer).

I suspect Je+ does something similar and somehow mixes the macro and parametric functionallities, where the parameter object is not possible in the macro dummy file as the parametric preprocessor runs only after macro and idf expansion.

Let us know how you get on.

Regards,

Jean