Log in Sign up

4Projects and versions

In brief

A project represents one installation site. Several versions can be created in it, for example for different planning states. With every simulation, the state of the version is saved read-only; each result thus belongs traceably to exactly one input.

A version contains all objects and project settings such as the time zone and base map. The project area (Ch. 5), map overlays and the balance of simulation tokens apply to all versions of a project.

4.1 How to

  1. In the dashboard, choose "New Project", enter "Project Name *" (required) and optionally "Description", then "Create Project". This uses one project token; the project receives 30 simulation tokens and the working version "Version 1".
  2. Set the project area in the editor (Ch. 5); until then, most menus are locked.
  3. Save changes with "Save". There is no automatic saving; "Revert" discards everything since the last save.
  4. For a further planning state, choose "Duplicate" or "New Version" in "Versions & Results" (table below).
  5. After a simulation, the report can be reached via "Versions & Results" at the read-only version. Work continues in the working version; if a simulated state is to become the starting point of a new plan, its version is duplicated.
Action Result
"Duplicate" copy of the current state; with unsaved changes you are asked first whether to save, and the copy contains them either way. Always editable; the copy of a read-only version has no object locks
"New Version" version without objects; takes over time zone, sources of the elevation data, base map and module types
"Create blank version" (project overview) like "New Version": version without objects, with the project settings, metadata and custom module types of the working version
"Delete" removes the version; for a version with a result, also the simulation with all results, irreversibly

4.2 Read-only versions

After every successful simulation, the server saves the state at the start as the read-only version "‹version name› · Sim-Backup DD.MM. hh:mm", which carries the result, even if the browser was closed during the calculation. This keeps it traceable which state a result was calculated with: inputs and report match, even if the working version is changed afterwards. The working version remains editable (Ch. 12). Batch analyses and worst-case combinations also create such versions (Ch. 13). Only the name and notes can be changed.

If a simulated state is to be edited further and no suitable working version is available, for example because it has since been changed or deleted, the read-only version is opened and copied with "Duplicate". The copy is editable.

4.3 Demo project

A demo project is possible once per account via "Create Demo Project" without a project token and has 2 simulation tokens. It calculates with the same methodology and temporal resolution as regular projects, with the quantity limits of the plan (Ch. 3). The report carries the watermark "DEMO" on every page and in the PDF. If simulation tokens are bought, it becomes a regular project; the watermark is then also removed from reports already calculated.

4.4 Locking objects

PV areas, groups of observation points, obstacles, excluded areas and measurements can be protected against moving and editing with the "Lock" button (padlock) on their object card. The lock is saved with the version and has no influence on the simulation. It also applies when "Objects movable" is switched on in the project settings (Ch. 5).

4.5 Trash

"Move project to trash" moves a project. There it can be restored for 30 days with all versions, results and tokens; after that, or with "Delete permanently", it is deleted together with its simulations, terrain models and overlays.

4.6 Points to note

  • The project name cannot be changed after creation; nor can the project area.
  • Deleting: The last version of a project and a version with a running simulation cannot be deleted.
  • Storage: Every version occupies storage; projects in the trash continue to count until they are permanently deleted. From 95 % usage, new simulations and PDFs can fail (Ch. 3).
  • No refund: Neither the trash nor permanent deletion refunds project or simulation tokens. Deleting a demo project does not restore the allowance.
  • Projects can neither be copied nor shared with other accounts; PDF and Excel exports can be passed on (Ch. 14).