Question-and-Answer Resource for the Building Energy Modeling Community
Get s tarted with the Help page

# Access eQuest macro processor via command line?

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?

edit retag close merge delete

Sort by » oldest newest most voted

more

( 2019-03-28 19:38:05 -0600 )edit

After focusing on the *.BDL output files, I started to notice a file fort.22. This looks similar ... I found there was a statement like this halfway through my BDL:

##write


Evidently, I needed to put this at the entry point to my program, ie. the beginning of the INP file. The fort.22 file has a clean version of the BDL output file. Aside from line numbers in the first few columns, I think is exactly what I'm looking for.

On second look: This is still not correct, or perhaps there is a bug with DOEBDL. My BDL output file will show keyword expressions, a la {...}. However, in the fort.22 output file, these expressions are replaced with just the open curly brace, {, with no inner content. I also get snippets of library in unexpected places.

more