Revision history [back]

I have some BDL input files (*.INP) with heavy macro usage (##include, ##setl). When I load one in eQuest into a new project, it runs the macro processor and saves the pre-processed INP file with my new project name. Then I can see how all the macros evaluated.

I want to know if there is a way to achieve this same effect via command line or DLL calls, that is, without opening eQuest GUI to create a new project. This way I can check how my macros were processed, edit the pre-processed BDL code if I like, and run the file with DOE2 command line.

Any ideas?

I have some BDL input files (*.INP) with heavy macro usage (##include, ##setl). ##set1). When I load one in eQuest into a new project, it runs the macro processor and saves the pre-processed INP file with my new project name. Then I can see how all the macros evaluated.

I want to know if there is a way to achieve this same effect via command line or DLL calls, that is, without opening eQuest GUI to create a new project. This way I can check how my macros were processed, edit the pre-processed BDL code if I like, and run the file with DOE2 command line.

Any ideas?

I have some BDL input files (*.INP) with heavy macro usage (##include, ##set1). When I load one in eQuest into a new project, it runs the macro processor and saves the pre-processed INP file with my new project name. Then I can see how all the macros evaluated.

I want to know if there is a way to achieve this same effect via command line or DLL calls, that is, without opening eQuest GUI to create a new project. This way I can check how my macros were processed, edit the pre-processed BDL code if I like, and run the file with DOE2 command line.

To clarify the original question, I want the result to be a new INP file that can be opened directly with eQuest.

Any ideas?