input files

[JosephG]

I've tried it myself but most of the input files seem to be in a custom format, i.e. non-text files, so I haven't been able to do it either.

[PCully]

Thanks Joseph,

I haven't tried this myself but due to the different files that compose a <VE> project I don't think this would be possible (I certainly wouldn't recommend it). Best thing to do is use the interface in <VE> to make sure you have set up the model exactly as you want.

Now if you had some comments on ease of use of the <VE> interface that would be a different story...we're always open to new ideas on ways to make <VE> easier/faster/more efficient to use.

Any feedback always welcome,
Phil

[JosephG]

The only file I've been able to directly edit is the ApPro files; I had a project where I had several thousand lines in the daily profiles text file, all to compose an overall annual file. The lines for daily profiles were created by a script in VBA. It was quite handy since I had formula-based profiles that needed to refer to room occupancy (which was continuously variable and isn't available as a variable in the 'formula' environment), so if I couldn't refer to occupancy, I just had a new formula at each timestep, resulting in a day with 30 formula lines. Because it was script generated, I could also change setpoints and which variables were used, re-run the script, and reload into ApPro a new set of profiles quickly and easily.

It would be very handy if all input files were text format since it would enhance data entry and simplify troubleshooting. For example, if I want to check that the ground temperature is set properly, I have to check every surface to ensure that a profile has been applied, and check which profile was applied. Error-checking in IESVE is quite time-consuming and is the biggest cause of error in my experience. There's too much clicking involved to check everything. I like the 'export room data', just wish it contained more information as described above. Did you notice that it doesn't include the "furniture mass factor" ?

Obviously there's a lot I'd do differently because I'm a different person, but, having said that, if there's interest from IES I'm sure many users here could come up with several new ideas. Myself, the way I see it, I'd be happy if the existing features all worked as advertised, and then maybe some new bells and whistles would be nice. For example, nowhere in any manual is it stated, but you cannot have more than 20 heat recovery units in ApHVAC... why?

[macleodd]

The limitation on 20 heat recovery units in ApacheHVAC has been removed for v6.0.

The number of modules that store their data in text form is quite limited - in addition to ApPro (the easiest format to understand), there is really only Apache Systems (.asd), Constructions/ApCDB (.dfa and .mat) and Weather/ApLocate (.wea).
You should be aware that IES may refuse to provide support where a model has had manual changes to text data.

Regards Donald

[JosephG]

That's good to know. Now, has the ApHVAC bug with malfunctioning proportional control of radiators also been fixed? Currently (last I checked), you can only control radiators with thermostatic-type control, which is inadequate.

http://www.iesve.com/Support/Knowledge- ... sectionId=