Revision history [back]

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 inputs. 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

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 run separate DOE-2 runs instead of one run with a series of parametric changes.

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 inputs. 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:

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 run separate DOE-2 runs instead of one run with a series of parametric changes.

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 inputs. 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

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 run make separate DOE-2 runs instead of making one large run with a series of parametric changes.

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 inputs. 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

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.

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.200.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.