Charts, Heatmaps & Tables

Where it lives and how it is laid out

Results is the bar-chart entry in the left navigation rail, at /results. The page is stacked top to bottom:

• Run the working project — the Run the project button for the project currently open. The engine checks the project first, and an error that stops the run is listed here. It leads the page because everything below it is what that action produced; Running a Simulation & the Production Tab covers running in full.

• The run selector, on the same line as the button — a Choose a job dropdown and a Follow latest run tick box, or, while a cloud run is open, the report's Run to preview dropdown. The stale badge follows the button when the run on screen no longer matches the project (below).

• The results body — a fixed-width chart list on the left and the report workspace on the right: the run's PDF report under the documents' header, a tab per document with Download PDF beside them, its menu holding the rest and the project's other files (Reporting & Export). On the tender dossier, permit and Consuel tabs, the column of the chart list holds that document's own panel instead.

The chart list keeps its width so the names never truncate; the report absorbs the rest of the window. Below about 900 pixels of width — a phone, or a narrow side-by-side window — the two stack instead, with the chart list on top and its own scrollbar.

Selecting a run puts its id in the address bar, so /results/cloud/<job-id> is a shareable link to exactly the results you are looking at.

While the project open in this tab has no successful run, the Results icon in the rail is red and its tooltip reads Calculation: The calculation has not been run. The flag speaks for the open project, not for the run on screen: it clears as soon as a run of that project succeeds, and stays clear while you go on editing — saying that the numbers no longer match is the stale badge's job (below). Open, import or start a project that has not been run in this browser and the flag comes back, even though Follow latest run still takes Results to the newest run of the session, which is then the previous project's. A saved project you have run reads as calculated again when you reopen it, in this tab or another tab of the same browser, even after the tab that ran it was closed; opening one of its cloud runs from the account page (Cloud runs: the job history) counts too. The record belongs to the browser: in another browser or on another computer, the flag shows until you run the project, or open one of its cloud runs, there.

The report beside the list

The view's canvas is the run's PDF report, with the documents' header above it and its theme panel. The header's tabs hold the project's other documents — the tender dossier, the town-hall permit and the Consuel dossier. The menu beside Download PDF holds the report's signature file and the financial projection's Excel workbook, and the projection's KPI strip sits under the preview (The multi-year financial projection). Reporting & Export covers the workspace in full.

While the run on screen is on its way — queued, running, or its results still loading — a loading mark takes the report's place and says what it waits for. The chart list keeps the rows of the run it last showed and nothing else on the page moves; the new run's report, charts and figures land together. A run that fails says why in the report's place.

The chart list is the report's outline. Clicking a chart's name scrolls the report to that chart's page and highlights the row. A chart the report does not print (unticked, nothing to show for the run, or a page the report never carries) leaves the pages where they are and says so over the preview. The tick box beside the name is untouched by that — it only edits the print list.

Choosing which run you are looking at

Because the web app submits runs as jobs, this page always shows one particular run — not "the current state of the project". Two things decide which: the run selector and the stale badge.

The run selector

• Choose a job — a dropdown of every run tracked in this browser session, each entry reading <job-id> · Succeeded (or Queued / Running / Failed). Picking one navigates to its results.

• Follow latest run — when ticked, the page re-targets the newest successful run as results land, so an edit-then-recompute loop keeps showing the freshest numbers without a click. It is on by default. A deep link to a specific run is never hijacked on arrival, and picking an older run by hand simply stays put.

The report always describes the run the tab shows; the documents' header above it has no run choice of its own.

While a cloud run is open, the selector gives way to the report's Run to preview dropdown: Latest run, then the succeeded runs this browser session tracks, each named by its id and the time it was submitted. Latest run follows the newest run that succeeded; picking a run pins it — the tab shows it and stops following newer ones — and choosing Latest run again brings the tab back to the newest run (Choosing which run the report describes). A run still queued or running has no report yet, so the dropdown reads Latest run while the report's place says where the run is: a queued cloud run says Queued — pickup typically ≤ 5 s, a running one Running…. On the free plan, where paying customers' runs go first, a queued run says Queued — on the free plan, runs start once no paying customer’s run is waiting instead (Paying customers' work goes first).

Beside the selector, small chips describe the run: from save <name> (and its version) when the run was submitted from a stored save.

The stale badge

A finished run is a photograph, not a live view. As soon as what it was computed from no longer matches what you have now, an amber badge appears right after Run the project. The badge names what drifted:

The badge carries no button of its own: Run the project, right before it, submits the project as it stands now and takes you to the new run's results. A run that carries no evidence on an axis — an old job from before a stamp existed — is never flagged on that axis, so the badge stays quiet rather than crying wolf.

The chart list, panel by panel

Header

The list is headed Charts, with the reminder (tick to include in the PDF).

Under it, Show all pages decides which pages the list shows. Unticked — the default — it lists only the pages of the PDF on screen, its table of contents: the charts it prints and its other pages. Ticked, it lists every page the report can hold, those the PDF on screen does not print greyed out: the rows to tick a chart back into the report from. Your choice is kept in your settings. The box shows once a run is on the tab; while a tutorial runs, the list shows every page whatever the box says.

Category sections

Charts are grouped into collapsible families, always in this order. A family appears only when the run has at least one chart in it:

Clicking a family header collapses or expands it; the arrow flips between ▼ and ▸. Collapse state is per browser session and is not saved with the project.

Chart rows and the include-in-PDF tick box

Each row is a tick box (tooltip Include in PDF) followed by the chart's name as a button (tooltip Show chart: …). Clicking the name scrolls the report to that chart's page; the row is highlighted. By default every chart is ticked.

The tick boxes are stored in the project, so a report layout you curate survives a save, a reload and a hand-off to a colleague — and the exported PDF really does drop what you untick. If no project is open the boxes render disabled with the note Load a working project to store the include-in-PDF choices in it.

Two rows carry no tick box — the two point-of-view pictures, which the report prints whenever the project carries them (Summary and picture pages).

The rows of Report pages, the system pages under System and grid and the Carbon balance page under Financial carry a locked box, ticked while the report on screen holds the page: such a page is in the report whenever the project has what it shows. Its tooltip says why — This page is always part of the PDF report and cannot be removed. for the cover, the simulation disclaimer and the site plan, Added to the PDF report automatically whenever the project has the data this page needs. for the rest. Clicking the page's name scrolls the report to it, like a chart's (tooltip Show page: …).

The financial projection prints more than one page — its yearly bars, then its year-by-year table and, when the run has them, the pages detailing its incentives and taxes (Taxes, incentives and tender settlement) — and each page has a row of its own under Financial, in the order the report prints them: Financial projection (the yearly bars), Multi-year financial summary (the table), then whichever of French incentives (EDF OA), IFER, Tax computation, year by year and CRE tender settlement, year by year the run has. Each has its own tick box, so you can leave one page out and keep the others. Clicking a row's name scrolls the report to its page (tooltip Show page: …).

How the mode and system type filter the list

On top of "did the run produce it", two project settings remove rows:

• Full export projects drop the consumption block, the self-consumption block, the production/consumption summary and First-year financials — there is no consumption or self-consumption to show in that mode.

• Off-grid solar pumping shows the four pumping charts, headed by its Solar pumping page, and DC grid shows the two DC-grid charts, headed by its DC grid page; each family appears only in its own mode. Both of these off-grid-like system types also drop the grid-economics families (consumption, self-consumption, financial and battery), except the three carbon charts, which stay meaningful off grid, and the bill of materials: an off-grid array has modules, cables and a mounting structure to order like any other.

A chart the list drops is not printed in the report either, whatever data the run has for it.

Three self-consumption rows also rename themselves with the mode. In self-consumption + storage they read Self-consumption and Total storage and Self-consumption and Storage per month; in the modes that sell, they read Self-consumption and total grid, Self-consumption and Total export and Self-consumption and Export per month.

Series toggles on the Analysis header

The Analysis charts overlay several series at once. Small colour-coded tick boxes on the Analysis family header let you decide which are drawn (tooltip Show/hide “…”):

• Loss / Export (red) — the loss-or-export curve; the label reads Loss in self-consumption + storage mode and Export otherwise.

• Battery (brown) — the battery charge level; offered only in self-consumption + storage mode.

• Self-cons. (green) — the self-consumption curve.

The consumption and production series are always drawn and have no toggle. In Full export mode every toggle is hidden — only production is meaningful there. The choices are stored in the project and are honoured by the engine when it draws the charts and the PDF.

The chart catalogue

The following catalogue lists every chart the app can offer, family by family and in the order the list shows them. Charts marked heatmap render a 365 × time-of-day grid (see Heatmaps: how to read them); the rest are line, bar or pie charts unless noted. Rows tagged [page] are not engine charts: the report prints the financial projection as described in The multi-year financial projection, and the others as pages of their own (Summary and picture pages).

Analysis

Consumption

Self-consumption

Production

Losses and shading

System and grid

These charts depend on the system type and on the matching feature being configured.

Battery

Financial

Heatmaps: how to read them

A large share of the catalogue is heatmaps — a rectangular grid where each cell is one moment of one day, coloured by a value. They all share the same layout, so once you can read one you can read them all:

• Vertical axis (rows): the day of the year, top (January) to bottom (December). Month initials (J F M A M J J A S O N D) label the left edge, set at mid-month, with ticks at the first of each month.

• Horizontal axis (columns): the time of day, 0h to 24h, labelled every six hours. Fine-cadence maps (sub-hourly slots) add unlabelled minor ticks every two hours. The hours are the site's local time, summer time included: the time zone the project's consumption data were recorded in (French legal time for Enedis data), else the legal time of the place where the site lies. The same clock lays out the consumption profiles, the peak and off-peak hours and the months of every total.

• Colour: the value in that cell, decoded by the colour-scale legend under the plot.

Most heatmaps use a sequential viridis ramp (dark = low, bright = high). The net-flow maps use a diverging ramp centred on zero, so charge and discharge read as opposite colours with white in the middle, and the clear-sky ratio diverges the same way around 1.0. The legend labels tell you the exact scale for each map:

The loss diagram

The Loss diagram is the single most important diagnostic chart. It draws the loss cascade as a waterfall of horizontal bars, one row per stage, from plane-of-array irradiance at the top down to energy delivered at the grid meter at the bottom. The first and last rows are full green bars — the energy you start with and the energy that reaches the meter, in kWh. Every row between them draws only the slice that stage removes, placed at the level where it happens, so the bars step down the page like a staircase. Each row's label names the stage and its share in percent. Red slices are losses modelled by PVGIS, orange ones the pvSpline losses you set (soiling, mismatch, AC cabling…) and teal ones gains such as transposition or the bifacial rear side; the legend lists only the colours the diagram uses. Module conversion (STC) is the modules' rated efficiency — not a loss you can reduce.

The rows follow the engine's canonical loss order — POA irradiance → shading → module physics → DC wiring → inverter → AC/grid. The Loss cascade card on the Production tab (Running a Simulation & the Production Tab) lists the same losses, but in its own row order, so match stages by name rather than by position.

The difference between the two is what you can do with them. The card on Production is editable — you set the loss percentages there. This chart is the run's own answer, fixed at the moment the engine computed it, and it is what goes into the report.

Its kWh figures are year 1 at the project's exceedance percentile (Probabilistic production (P50/P75/P90/P99)): at the default P90, the bottom bar is the figure of the Annual production · P90 tile on Production. The stage percentages are the same whatever the percentile.

Batch study — scenario comparison

Batch study — scenario comparison is your batch study (Batch Simulation & Scenario Sweeps) as one page of the report. The engine draws it, like the charts above, from the study stored in the project the run was computed from — the Batch tab stores a finished study in the open project (The study in the project and in the report) — so the page is that project's own study, never a study from another project.

The page is one annotated chart:

• every completed scenario is a marker in the column of its swept value (or of its run order on the Index (order) axis), labelled with its name and score where the label fits; failed scenarios are left off;

• a verdict block names the best scenario on the plotted metric — Best NPV, its name and value and, when you pinned a baseline, the gap to it (… vs baseline · … %);

• the baseline is a hollow marker with a reference line through it and a baseline: … — … chip;

• each column is headed by its value, with the number of scenarios in it and the range of their scores beneath (3 scenarios · … – …);

• a scenario far outside the rest sits on the edge of the axis, noted as 1 scenario past the axis, drawn on its edge;

• when the page has just two columns and their ranges do not meet, the gap between them is called out: No overlap — … ranks entirely above … on …;

• a caption at the foot gives the run's shape, for example 3 scenarios · 1 failed · best (NPV): large — 12000 € · plot: NPV vs Battery capacity (kWh), beside a legend for the best, baseline and scenario markers.

The axes are the ones last picked under the Batch tab's chart (X axis:, Y axis:), and the baseline is the row starred with Set as baseline in its results grid; sorting that grid changes nothing here. The metric is NPV unless you chose another; on IRR (%), DSCR min or LLCR, scenarios without that figure are left off. When nothing can be plotted — on DSCR min, for example, for a study whose scenarios carry no debt — the page reads No numeric data to plot for this axis. The caption always names the NPV winner while the verdict block names the best on the plotted metric, so on another axis the two can differ. There is no scenario cap: a long study makes a busier page, not a clipped one.

The row is listed whenever a project is open — last under Financial, except for off-grid pumping and DC-grid projects — and its include-in-PDF tick box works like any chart's. Until the run on screen carries a study, the report has no page for it. If the open project stores one already, the run was computed before it: storing it changed the project, so the run is stale too (see the stale badge above) — run the project again and the new run carries the page. Otherwise, run a batch on the Batch tab first (Batch Simulation & Scenario Sweeps).

The multi-year financial projection

Financial projection is the data table behind the money charts: a year-by-year projection over the project's operating lifetime, from the run's own figures. The report prints it on two pages (Reporting & Export); its Excel export sits in the menu beside Download PDF above the report, and its headline strip under the preview.

Rows and columns

The first column is Year: row 0 is the installation year, then one row per operating year, closed by two summary rows — Tot. (total) and Avg. (yearly average). For a per-year flow, Tot. is the column's sum and Avg. is that sum over the number of operating years; for the already-cumulative columns (cumulative cash flow, NPV, cumulative cash flow at today's prices) Tot. is the final value and Avg. is that value spread over the operating years; for the escalation column Tot. is the last year's rate and Avg. is year 1's.

Columns the project does not use are dropped rather than shown as zeros; if the capacity charge is identical before and after PV, the "before" column disappears and the remaining one is simply labelled Capacity charge. Which capacity columns exist follows the Granularity of the GRID PRICING card (The project's consumption-rate and grid-pricing cards): at None there is none; at Subscription no overshoot is billed, so the charge is the same before and after PV and only Capacity charge shows; the before/after pair appears only at TURPE + peak-shaving or Net metering, when the system changes the overshoot penalty.

The exact column set depends on the mode. A self-consumption project gets the wide table (escalation, bills and capacity charges before and after, savings, subsidy, maintenance, storage and EV costs, then the results block); in Self-consumption + export it also carries PV export, the surplus sold, while a run that simulates storage — Self-consumption + storage with a virtual bank or a physical pack, or an off-grid site — stores its surplus and has no sale column. A Full export project gets a narrower table built around PV export. The full list is in Financial projection: columns.

The KPI strip

A single line under the preview states the run's headline money figures, for example Payback: 8.6 years · IRR: 8 % (before tax) · LCOE: 0.048 €/kWh (P90). Each part appears only when it has a value:

• Payback — the payback period to a tenth of a year (when the cumulative cash flow crosses zero, read between the two year-ends), in the interface language: 8.6 years, 12,8 ans. A project that has not paid back by the end of its horizon reads >25 years for a 25-year horizon. The part is left out when the run gives no payback or a zero one — the cumulative cash flow is already at zero in the installation year, which happens only when none of the investment comes from your own funds: a project with no investment, or one financed at a Loan share of 100 %.

• IRR — the equity internal rate of return, on your own funds after loan repayments, to the nearest whole percent: the IRR the PDF report and the workbook headline too. When a loan makes it differ from the project IRR, on the whole installation cost, it is tagged (equity). It is tagged (before tax) when corporate tax is switched on with a non-zero rate (both IRRs are pre-tax returns). When the run books tax — a tax rate, or tax credits alone — the same IRR after tax follows it, for example IRR: 8 % (before tax), 6 % after tax.

• LCOE — levelised cost of energy, to three decimals per kWh in your currency.

• A (P75) / (P90) / (P99) tag when the run was sized at a conservative exceedance percentile.

Taxes, incentives and tender settlement

What the financial model adds to the table, the report prints with it, each block behind its own tick box in the chart list and only when the run has it, so a simple project shows none of them (Reporting & Export):

• Taxes and incentives — a column beside the headline figures of the bar-chart page: the project IRR and the equity IRR after tax, the corporate tax over the projection, the IFER over the projection, the VAT paid on the installation when it is not recoverable, the grants and incentives received and the tax credits.

• French incentives (EDF OA) — a page on the EDF OA contract the run booked from the CRE grid (Incentives): whether it was booked or why not, the grid's identifier and dates, the connection request date, the tariff and contract length, the self-consumption prime and how it is paid, the yearly cap and the tariff's revaluation, with a link to the CRE's published source. This is the line a study quotes to say which quarter's rates it used.

• IFER — the rates the run used and the year-one amount, or why none was booked: under the EDF OA text, or at the top of the first table page when it is the only text.

• Tax computation, year by year — a page with the table: taxable income, losses used and carried forward, the tax before credits, the credits used and the tax, per year.

• CRE tender settlement, year by year — for a tender bid, a page with the table: the reference price applied each year, the reference revenue, the market sales (with a monthly M0), the complement, the management premium and what the plant receives, under a line naming the settlement options in use.

The Excel workbook carries the same blocks, in the same words, on a sheet of its own (Exporting the financial table and the bill of materials).

The calculation legend

The Excel workbook carries a calculation legend under the table's summary rows: one line per column, with the column header and the formula behind it, so a reader can audit the numbers. The PDF's table page carries none.

Exporting the table

Export tables (XLSX) sits in the menu beside Download PDF above the report, under From this run. Like the strip, it describes the run chosen at the top of the page — the run the report previews too (Choosing which run the report describes). It asks the engine for the run's workbook and downloads it as <job-id>-tables.xlsx. The button reads Preparing the workbook… while it works. If the engine has no such route, the page says The XLSX export is not available on this engine. For a cloud run it is the workbook rendered with the run, so its summary rows — words, units and figures — are in the language the page used when the run was started.

Summary and picture pages

Six rows of the list are not engine charts, yet the report prints each of them as a page of its own:

• Production / consumption summary — the energy-flow diagram: PV, house, grid and, when the project has them, battery and vehicle, with their annual energies, the savings each flow brings and the self-consumption and coverage rates. Printed whenever the run moved any energy, except in Full export mode, which has no consumption side to describe.

• Bankability — DSCR / LLCR + sensitivity — the four coverage figures (DSCR year 1, DSCR min, average DSCR, LLCR) under the yield percentile they were sized on, and the one-at-a-time sensitivity table, the base case first. Printed for a financed project only.

• Bill of materials — the project's purchase list, drawn from its wiring and components: the system components with their quantity, unit, unit cost and line total, then the conductors by size, metal and insulation with their run count and total length, and the material total. It is headed with the electrical code the conductors were sized under and closed by the note that its figures are indicative pre-design values. A long bill runs on over as many pages as it needs. Printed whenever the project has something to bill, off-grid pumping and DC-grid projects included; like the rest of the report it describes the project the run was computed from, whereas Bill of materials (CSV) and Bill of materials (XLSX), in the menu beside Download PDF, follow the open project (Exporting the financial table and the bill of materials).

• Ground light across the row pitch — the agrivoltaic transect, printed when an agrivoltaic array ran.

• Horizon panorama (3-D sweep POV) and Near shading render (sun POV) — the two point-of-view pictures, with the measured skyline drawn over the panorama and the sun's position and shaded fraction under the render. They are taken on the 3-D view, which writes them into the project (The 3D Earth Site View); the report prints them from the project the run was computed from, so a picture taken after the run reaches the report from the next run.

The first four keep their include-in-PDF tick box, like any chart; the two pictures have none and print whenever the project carries them. Clicking any of the six rows brings its page into view. A row the report has no page for — a page that has nothing to show for this run — leaves the report where it is and says so over the preview: “…” has no page in this report.

The debt-coverage ratios also ride the summary rows of the Excel workbook (The multi-year financial projection).

Getting a chart out

There is no per-chart download: the report is the way out for a finished document. Untick what you do not want, export the PDF (Reporting & Export) and lift a single chart from it with your PDF viewer — or zoom the preview onto its page and take a screenshot. The financial projection also leaves as numbers, through its Export tables (XLSX) button (The multi-year financial projection).

How results reach the report

The tick boxes in the chart list are the report's contents page. The workspace renders the PDF for the run it previews, with exactly the charts you left ticked, in the theme you chose; Reporting & Export covers the preview, the theme editor, printing, the tender dossier, the permit package and the Consuel dossier. Untick a chart here and it is gone from the exported file — the exclusion is carried in the project. A cloud run's report was rendered when the run was computed, so a change here reaches its PDF from the next run.

Field reference

Run selector

Chart list

Analysis series toggles

Consumption and production are always drawn and have no toggle. All three toggles are stored in the project and take effect from the next run.

Financial projection: export

Financial projection: columns

Columns the project does not use are omitted rather than shown empty.

Heatmap colour-scale legends