The outdoor temperature each month runs at decides most of a year's energy. Town, under Location on the Energy station, chooses where those temperatures come from, and Climate profile beneath it names the profile in use and its source.
- 1
If the project has no location yet, choose one on Cycle under Project location: search Where is the project? and pick its Weather station.
- 2
On Energy, choose Town and pick the Project location row at the top of the list. A new analysis starts there when the project has a location.
- 3
Choose Expected · typical weather for what the plant is expected to use, or Upper bound · design-high for a conservative figure.
Expected consumption
Each month's hours are spread over the range of temperatures the weather station's monthly statistics give: its average daily dry bulb, their standard deviation and the mean daily range, laid over the day with a standard daily profile. The cycle is solved at every 0.5 K of that spread, and the month is their sum. The result is what the plant is expected to use in a typical year.
It needs the station's monthly statistics and the daily profile from Kelvin's reference library. When either is missing, the page says so and runs at the design-high temperatures instead, as an upper bound.
An upper bound at design-high temperatures
Every hour of a month runs at that month's design dry bulb, not its mean. The result is more than the plant is expected to use, and the annual energy, the annual cost and the compressor energy carry the words upper bound.
Preset cities, other towns and custom profiles
- The eight preset capital cities (Brisbane, Sydney, Melbourne, Perth, Adelaide, Darwin, Hobart and Canberra) carry monthly design temperatures only, so they give an upper bound. The sheet names their source.
- To use another town, type its name in Town and choose its Look up row to search Kelvin's regional climate library. A town it finds loads as a custom profile. If the town isn't there, Kelvin says so and doesn't guess its temperatures.
- Custom profile takes a design temperature for each of the twelve months. A month left empty isn't assumed, so there are no annual figures until all twelve are entered. Each figure runs as that month's design temperature, so a custom profile gives an upper bound too.
- Save as profile keeps a custom set of temperatures to use again from Load saved profile.
- With pads on, a custom profile also asks for one Relative humidity for every month.
When the project's location changes
A saved analysis keeps the monthly temperatures it was run with. If the project's location has changed since, the page says so. Choose Project location in Town to apply the current one.
Note
Kelvin never fills a missing month, a missing town or a missing weather station with a guess. With no temperatures there are no annual figures, and the page says what is missing.