Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
That message is generated by the convertESOMTR program that is used as a post processing step to convert to IP units in the main results file that reports outputs for each timestep. It indicates that no timestep based outputs were actually generated for the file. I would suggest that you look at the .ERR file and see if any severe or fatal error messages are shown and if there are, try fixing those.
| | 2 | No.2 Revision |
That message is generated by the convertESOMTR program that is used as a post processing step to convert to IP units in the main results file that reports outputs for each timestep. timestep into IP units. It indicates that no timestep based outputs were actually generated for the file. I would suggest that you look at the .ERR file and see if any severe or fatal error messages are shown and if there are, try fixing those.
| | 3 | No.3 Revision |
That message is generated by the convertESOMTR program that is used as a post processing step to convert the main results file that reports outputs for each timestep into IP units. It indicates that no timestep based outputs were actually generated for the file. I would suggest that you look at the .ERR file and see if any severe or fatal error messages are shown and if there are, try fixing those.
If you are using EP-Launch you can prevent convertESOMTR from even running by going to VIEW .. OPTIONS .. MISCELLANEOUS and unchecking Convert ESO/MTR to IP Units. This might help you get to the .ERR file. It is an error in the IDF file and that is causing the problem in the ESO file which trips up convertESOMTR. If you fix the IDF file error you can probably recheck that option and it should run ok.
An issue about convertESOMTR not handling a broken ESO file was posted and is being worked on with this pull request on GitHub which should be included in the next version of EnergyPlus.
