Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
I did some experimentation and found that once I split the IDF file into two halves (in a text editor) I was able to save each half separately in the IDF Editor without issue. This is a workable solution for me at this time.
When I recombine the two halves that as saved by IDF Editor, the error occurs again. The issue may be related to file length, or some limit on number of objects?
| | 2 | No.2 Revision |
I did some experimentation and found that once I split the IDF file into two halves (in a text editor) I was able to save each half separately in the IDF Editor without issue. This is a workable solution for me at this time.
When I recombine the two halves that as were saved by IDF Editor, the error occurs again. The issue may be related to file length, or some limit on number of objects?
| | 3 | No.3 Revision |
I did some experimentation and found that once I split the IDF file into two halves (in a text editor) I was able to save each half separately in the IDF Editor without issue. This is a workable solution for me at this time.
When I recombine the two halves that were saved by IDF Editor, the error occurs again. The issue may be related again.
@JasonGlazer identified that the problem was due to file length, or some limit on IDF editor running out of memory since there were a huge number of objects?schedule:compact objects in the file. Solution was to edit the .IDD file to reduce the number of fields allocated to each one of these, to a number that will be enough for all the schedule:compact objects you want to have, but not so many that IDFEditor runs out of memory. Refer to comments below from Jason for further info.
| | 4 | No.4 Revision |
I did some experimentation and found that once I split the IDF file into two halves (in a text editor) I was able to save each half separately in the IDF Editor without issue. This is a workable solution for me at this time.
When I recombine the two halves that were saved by IDF Editor, the error occurs again.
@JasonGlazer identified that the problem was due to IDF editor running out of memory since there were a huge number of schedule:compact objects in the file. Solution was to edit the .IDD file to reduce the number of fields allocated to each one of these, to a number that will be enough for all fields to accommodate each of the schedule:compact objects you want to have, will have (i.e. define it with enough fields for the longest schedule:compact object you think you will ever need), but not so many that IDFEditor runs out of memory. Refer to comments below from Jason for further info.
