Importing your own data
Two CSV imports exist, both mapped by column name rather than position, and both with a sample you can download and open:
| weather-sample.csv | An hourly weather year. One row per hour (8 760 for a full year, up to 5 years in one
file) with a header row; the cells cut with commas, semicolons or tabs, a decimal comma read
where the comma is not the delimiter. Dry bulb °C is required; add wet bulb °C or
relative humidity, as a percentage or a fraction. A solar column (GHI, W/m²) feeds solar gains
in building simulation. After upload you pick which of your columns is which — the names in
the sample are only a suggestion.
Hourly, and only hourly. A timestamp column is optional. Written year first ( YYYY-MM-DD HH:MM) it is checked: a run counts every row as one hour, so a
half-hourly or daily file is refused rather than run at the wrong length. Without one the rows
are taken as consecutive hours from 1 January.
Real values. Every number has to be finite, and a temperature between −90 and 60 °C — a column in °F, or a logger's marker for a missing reading (99.9, −999), is named and refused. A row with a cell that cannot be read at all ( n/a, an empty
cell) is left out and keeps its place in the calendar, so the hours after it do not move up;
the import's report counts the rows read and skipped and names the first 20 by
row and column.
Who may import. An account on a plan that can simulate (not a workspace viewer). The year is that account's own — up to 25 at a time — until it is deleted. |
| loads-sample.csv | Hourly room loads for load-following control, when you would rather supply them than have
them derived from outdoor temperature. Cooling kW in the first column, optional heating kW in
the second; a header row is skipped automatically. An hour's figure is read as the duty that
holds the room on its setpoint — the cooling setpoint for a cooling hour, the heating
setpoint for a heating one — so a room left unserved drifts and settles instead of running
away (hourlyLoadsKw). |