Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Hi Vitor,
It is hard to know why jEPlus has stopped. As the journal shows it is at the start of collecting simulation results, what outputs are EnergyPlus producing in your project? If each job producing a lot of data, e.g. with hourly outputs, then the collection process can be quite long. I noticed that you are running the project on V: drive. Is this a network drive? If it is, and your output files are large, it will substantially lengthen the simulation time.
To your questions: 1. If each simulation takes more than 10 minutes, it will need 5 days to go through 2800 jobs on a 4-core i5. How complex is your model? If it is not particularly heavy, my suspicion is on the V: drive. Try to reduce the output from E+ as much as you can and then test a few on your local drive.
Hmm, there is a switch to let jEPlus skip jobs whose results are already in the output folder. However, this switch has been disabled in the GUI. If you cannot find a way to make the project run faster, I can give you a version to allow this feature.
Yes, jEPlus doesn't really need a lot of memory. As long as it is not using up to the limit, allocating more will no difference.
Cheers,
Yi
| | 2 | No.2 Revision |
Hi Vitor,
It is hard to know why jEPlus has stopped. As the journal shows it is at the start of collecting simulation results, what outputs are EnergyPlus producing in your project? If each job producing a lot of data, e.g. with hourly outputs, then the collection process can be quite long. I noticed that you are running the project on V: drive. Is this a network drive? If it is, and your output files are large, it will substantially lengthen the simulation time.
To your questions:
1. questions:
If each simulation takes more than 10 minutes, it will need 5 days to go through 2800 jobs on a 4-core i5. How complex is your model? If it is not particularly heavy, my suspicion is on the V: drive. Try to reduce the output from E+ as much as you can and then test a few on your local drive.
Hmm, there is a switch to let jEPlus skip jobs whose results are already in the output folder. However, this switch has been disabled in the GUI. If you cannot find a way to make the project run faster, I can give you a version to allow this feature.
Yes, jEPlus doesn't really need a lot of memory. As long as it is not using up to the limit, allocating more will no difference.
Cheers,
Yi
