Guide
Results and deliverables
A finished run holds its deliverables, a report on how it went and, when you are satisfied, your acceptance.
Find the outputs
Open a dataset from Projects. Its Outputs tab lists every file of the version you are looking at, with Download all; its Quality tab holds the report and the delivery review; its Versions tab holds each version’s run details. In the workspace, the cross-sections, volumes and comparisons you order are tabs of the bottom dock under the cloud.
| Tab | What it holds |
|---|---|
| Outputs (dataset page) | Every file the run wrote, in folders, as it is written. |
| Sections (bottom dock) | The cross-sections you have ordered from the run, with their files. |
| Volumes (bottom dock) | The volumes you have measured on the run. |
| Compare (bottom dock) | The height differences you have measured against an earlier run. |
| Versions, run details: Steps | Each step in the order it ran, with its time and the points that passed through it. |
| Versions, run details: Log | What happened to the run, and when. |
| Quality: Report | A summary of what the run found, and the delivery review described below. |
On the Outputs tab you can search by file name or format. Each folder can be folded, and the folder of viewer tiles starts folded. A file that the run chose not to make is listed under not produced, with the reason: a terrain model from a file with no ground, for example.
To look at a deliverable over the cloud, open the Outputs panel in the workspace; see the rail and its panels.
Review a delivery
Before you accept, open the dataset’s Quality tab. The Delivery acceptance panel at the top gathers the evidence in one place.
- The facts: the run, its source files, the horizontal and vertical coordinate systems, the linear units and when it finished.
- Requested products: each is marked Delivered, Not produced (with the reason the data could not support it) or Missing.
- Checks: the run finished, the requested products, files available, the coordinate system, the units and the positional accuracy, each marked pass, warning, fail or for information.
The panel states the facts; it does not decide. Whether the delivery meets your survey’s requirements is for you to judge.
Accept a delivery
Accepting records that a run stands as the delivery for its survey. It is always your act: the console never accepts a run for you, and a rerun is never accepted automatically.
Open a finished dataset
A dataset in review shows Accept delivery as its main action. A ready one offers Accept without review under …. Only a finished version can be accepted.
Read the question
The question says that this version becomes the delivery for the dataset, and that an earlier accepted version made from it by reprocessing loses its mark.
Look at any warnings
If the run has quality warnings, they are listed in the panel. You must tick I reviewed these warnings and accept this delivery before the button works.
Choose Accept delivery
Not yet closes the panel and changes nothing. After you accept, the dataset shows Delivered, on its page and in Projects.
If the quality review could not be loaded, the panel says Quality review unavailable and offers Retry quality review. Accept stays off until it loads, so that you never accept without having seen the warnings.
A run that has saved class edits is accepted from its edits, after the deliverables are updated; see correcting classifications.
Quality warnings
A run can finish and still carry warnings about its data. The header’s Details button shows how many. Choose it, and the popover shows Completed with quality warnings and a count. Choose that to open the Report. A run with none says Quality report available.
- Quality warnings are the ones to review. They come from the run’s report and appear in the order the run gave them. The accept panel lists the same ones.
- For information lists notes about how software draws the data, not about the data itself. A large projected coordinate is the usual one. You have nothing to review in these.
A warning is not a failure. It is a place to look before you sign the delivery off.
Superseded runs
Processing a survey again, whether with another preset or template or with saved class edits, makes a new run linked to the first. The new run’s Details say reprocessed from and name the first.
When a later run stands in the place of an earlier one that has not been accepted, the earlier run shows a Superseded mark with a link to the later run, and its Details say superseded by. The earlier run is still there and still downloadable.
Open the run you want to stand as the delivery and accept it. That run takes the accepted mark and the other loses it. The accept panel names the later run if one stands in its place, so you know what you are changing.
Download the files
- One file. On Deliverables, select its name.
- Everything the run wrote. Choose Download all. You get one archive of the whole set.
- A handoff package. Under Handoff package, tick the cross-sections, volumes and comparisons you want to add, then choose Download package. It holds every file the run delivered, the ticked results, and a manifest of each file’s size, checksum and producing operation, with the run’s source, coordinate system and acceptance.
- Sections, volumes and comparisons. Each has its own files in its tab.
- After class edits. The Deliverables list belongs to the original run, and its button reads Download original run files. The accepted edits and the deliverables made from them are in Download accepted corrected delivery.
How long things are kept
Your outputs are kept for a period, and the Usage page states it under Outputs kept for. Sections, volumes and comparisons show a kept until date next to their files. Past that date the files are removed. A comparison keeps its figures as the record.
The uploaded survey is kept for reprocessing until the date in the run’s Details, which reads Reprocessing possible until. After that date it says the input has expired. Upload the file again to process it again.
Allowances and the Usage page
Usage in the navigation shows the meter for the current period.
- Points: how many points your organisation has used this period, against its allowance, with how many are left.
- Runs metered, Data in and Compute: the facts under the points.
- Uploads this period: how much you have uploaded against the upload allowance, and the largest single file.
- Your allowances: points each month, runs at once, the largest single survey, storage, the largest single file, uploads each month and how long outputs are kept. A limit that nothing applies is left out.
- Jobs behind the number: each run, cross-section, volume, extraction and comparison that was metered, with its points, data and compute, and when it finished.
A job is metered when it reaches a final state. A run still going is not in the numbers yet. A volume or a comparison reads the whole run, so it is metered like a run.
Need more? Email us and tell us what you are working on.