Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

After working on EnergyPlus source code for a few month, I decided to answer my own question and put down a few other notes here that might be helpful for others (Thanks again to Jason for his helpful reply):

  1. After copying all the required files including EPL-RUN.bat to the Products\Debug folder, the first issue was resolved and the energyplus.exe file started working properly. Every time a change is made in the source code, the Visual Studio (VS) should build a new executable file by right clicking on the energyplus project within VS and selecting build.

  2. Jason's reply is comprehensive, I'd say.

  3. The issue with MSCOMCTL.OCX was due to not having administrative access. After copying the missing files to Windows folder with administrative access, the issue was resolved.

Additional notes: -All the source files are under the energypluslib project and Source Files folder. Depending on what you are trying to change, you can find the related C++ module there.

-Every time a change is made in one of the modules in source code, the VS only compiles the modules related to that change and it doesn't compile everything. Unless there is a change in one of the header files.

-Make sure you rename the input file and also the weather file to "in" as it is explained in Step 10. Such as in.idf and in.epw.

-The outputs will be stored under the Product folder and they will be overwritten every time E+ is run. If EP-launch is used, the outputs will be stored where ever the inputs files are.

-If you don't want to use the EP-launch and IDF Editor, you can still change the details such as run period, warmup period, and etc. by editing the text file of your input. energyplus.exe will be run based on these changes.

I added new sections to some of the modules within source code and now I can store some new outputs from E+ in a text file. Please let me know if you are working on similar projects and I'd be more than happy to share my experience on that!

After working on EnergyPlus source code for a few month, I decided to answer my own question and put down a few other notes here that might be helpful for others (Thanks again to Jason for his helpful reply):

  1. After copying all the required files including EPL-RUN.bat to the Products\Debug folder, the first issue was resolved and the energyplus.exe file started working properly. Every time a change is made in the source code, the Visual Studio (VS) should build a new executable file by right clicking on the energyplus project within VS and selecting build.

  2. Jason's reply is comprehensive, I'd say.

  3. The issue with MSCOMCTL.OCX was due to not having administrative access. After copying the missing files to Windows folder with administrative access, the issue was resolved.

Additional notes: -All

  • All the source files are under the energypluslib project and Source Files folder. Depending on what you are trying to change, you can find the related C++ module there.

    -Every

  • Every time a change is made in one of the modules in source code, the VS only compiles the modules related to that change and it doesn't compile everything. Unless there is a change in one of the header files.

    -Make

  • Make sure you rename the input file and also the weather file to "in" *in* as it is explained in Step 10. Such as in.idf and and in.epw.

-The outputs will be stored under the Product folder and they will be overwritten every time E+ is run. If EP-launch is used, the outputs will be stored where ever the inputs files are.

-If

  • If you don't want to use the EP-launch and IDF Editor, you can still change the details such as run period, warmup period, and etc. by editing the text file of your input. energyplus.exe will be run based on these changes.

I added new sections to some of the modules within source code and now I can store some new outputs from E+ in a text file. Please let me know if you are working on similar projects and I'd be more than happy to share my experience on that!

After working on EnergyPlus source code for a few month, I decided to answer my own question and put down a few other notes here that might be helpful for others (Thanks again to Jason for his helpful reply):

  1. After copying all the required files including EPL-RUN.bat to the Products\Debug folder, the first issue was resolved and the energyplus.exe file started working properly. Every time a change is made in the source code, the Visual Studio (VS) should build a new executable file by right clicking on the energyplus project within VS and selecting build.

  2. Jason's reply is comprehensive, I'd say.

  3. The issue with MSCOMCTL.OCX was due to not having administrative access. After copying the missing files to Windows folder with administrative access, the issue was resolved.

Additional notes:

  • All the source files are under the energypluslib project and Source Files folder. Depending on what you are trying to change, you can find the related C++ module there.

  • Every time a change is made in one of the modules in source code, the VS only compiles the modules related to that change and it doesn't compile everything. Unless there is a change in one of the header files.

  • Make sure you rename the input file and also the weather file to *in* as it is explained in Step 10. Such as in.idf and in.epw.

-The

  • The outputs will be stored under the Product folder and they will be overwritten every time E+ is run. If EP-launch is used, the outputs will be stored where ever the inputs files are.

    • If you don't want to use the EP-launch and IDF Editor, you can still change the details such as run period, warmup period, and etc. by editing the text file of your input. energyplus.exe will be run based on these changes.

    I added new sections to some of the modules within source code and now I can store some new outputs from E+ in a text file. Please let me know if you are working on similar projects and I'd be more than happy to share my experience on that!