Is there a published description of IES VE files?
-
MatthewSteen
- VE Graduate
- Posts: 51
- Joined: Mon Nov 17, 2014 5:43 pm
- Location: Denver, CO, USA
Is there a published description of IES VE files?
I'm looking for a reference describing each file in an IES VE model, e.g. MIT, MTD, MWF, etc. Does one exist? If not, this would be a helpful addition to the documentation for those of us trying who want to understand the software better. For comparison, EnergyPlus provides a nice summary of all the associated model files.
Building Performance Engineer | Ambient Energy | http://ambient-e.com/
Q+A Resource for the Building Energy Modeling Community | https://unmethours.com/questions/
Q+A Resource for the Building Energy Modeling Community | https://unmethours.com/questions/
Re: Is there a published description of IES VE files?
Hi Matthew,
I can see why you would want this but such a list is not publicly available as we don't encourage users to attempt to manipulate project files and bypass the VE interfaces which is more likely to result in invalid modelling inputs and project corruptions.
I hope that makes sense to you and if you have any specific query regarding any project files then you are free to contact IES Technical Support and we can try to assist further.
Phil
I can see why you would want this but such a list is not publicly available as we don't encourage users to attempt to manipulate project files and bypass the VE interfaces which is more likely to result in invalid modelling inputs and project corruptions.
I hope that makes sense to you and if you have any specific query regarding any project files then you are free to contact IES Technical Support and we can try to assist further.
Phil
IES Worldwide Technical Support
Re: Is there a published description of IES VE files?
Phil,
I'd echo this request. Of course I understand where you're coming from, though I'd say if you really don't want people to mess with the files, then they should just all be binary or hiden from the user somehow. However I'd really not reccomend this. For example, the profiles are all in text files and I've found this very useful to manipulate outside of the VE since CSV files or similar can be modified easily and then copied in. Similarly there are some files that control the HVAC file libraries that have been useful for me to edit.
Matthew, the only way I've found these things our are by trial and error. For the vast majority of the time I've only needed to edit the loads spreadsheets externally, otherwise it's best to work within the VE. But if you feel like experimenting, be sure they are just on test models!
Ben
I'd echo this request. Of course I understand where you're coming from, though I'd say if you really don't want people to mess with the files, then they should just all be binary or hiden from the user somehow. However I'd really not reccomend this. For example, the profiles are all in text files and I've found this very useful to manipulate outside of the VE since CSV files or similar can be modified easily and then copied in. Similarly there are some files that control the HVAC file libraries that have been useful for me to edit.
Matthew, the only way I've found these things our are by trial and error. For the vast majority of the time I've only needed to edit the loads spreadsheets externally, otherwise it's best to work within the VE. But if you feel like experimenting, be sure they are just on test models!
Ben