Configure a folder’s setup: base point, levels, PSETs

A Folder’s setup defines what every model in that Folder should contain: an expected base point, expected levels, expected PSETs and properties, and a reference model for grids. Models are then compared with those values, using the tolerance you entered. This page walks through the “Folder setup” dialog section by section. Each section has its own rules.

Prerequisites

• A Folder already exists in the current project. If not, create one with New folder, or import some from your computer with Import PC folders.
• Setup is set Folder by Folder, from the row menu in the list.

Open and fill in the setup

1. Open Setup

   In the Folders list, open the three-dot menu at the end of the row. Click Setup, between “Edit” and “Delete”. The “Folder setup” dialog opens.

2. Expected base point

   Enter the coordinates the base point of each model in the Folder should have, then set the “Unit” and the “Tolerance (m)”. An axis left blank is not compared. That is not the same as “0”. The tolerance applies to coordinates and to level elevations.

3. Expected levels

   Click Add a level for each expected level. While the list is empty, the dialog shows “No expected level defined”. A level is matched on its IfcName. The elevation only checks the height when it is filled in; left blank, only the name counts. Extra levels in a model are not penalised. To drop a row, use Remove this level.

4. Expected PSETs and properties

   Write one PSET per entry, or PSET.Property to require a specific property inside that PSET. What comes before the first dot is the PSET, and the rest is the property. Example: Pset_WallCommon, Pset_WallCommon.FireRating. These are compared with each model’s actual values (PSET column).

   Entries can be separated by a line break, a comma, a semicolon or a tab, so you can paste a spreadsheet column or an inline list straight from a specification document.

   Import appends the content of a .txt or .csv file to what you typed without erasing it, and duplicates are dropped automatically. Example downloads a sample file (.txt, one entry per line) to adapt. A preview shows the count, for instance “1 PSET · 1 property”; while nothing is entered it reads “No expected PSET or property yet.”

5. Reference model (grids)

   Pick the reference model in the list, or leave “None”. Each model’s grid in the Folder is compared with the grid of this model: offset per axis (same tag, e.g. “A”, “1”), rotation and estimated X/Y shift, within the setup tolerance. It helps when the base point tells nothing, as with Tekla or Geomensura models whose base point is at 0. A model converted before 28/09 must be relaunched for its grid to be read. The message “Reference model saved” confirms your choice.

6. Save

   Click Save. The message “Setup saved” confirms it went through.

Copy the setup from another Folder

Instead of retyping everything, pick a Folder under “Copy from another Folder” (the list reads “Choose a Folder…”), then click Copy: the copy takes the other Folder’s setup as is (base point, levels, PSETs and properties) and replaces this one. It applies immediately. It does not go through Save. Copying from a Folder with no setup is refused, because it would wipe yours for nothing. The message “Setup copied” confirms the copy.

What can go wrong

Most problems come down to a missing setup on the source Folder, a failed save, or a file that cannot be read, and each of them shows a short message in the dialog that you can match with the entries below.

“That Folder has no setup to copy, yours was left untouched.”

The source Folder has no setup, and SeveUp App refuses the copy rather than wipe yours for nothing, so nothing changed on your side. Pick another source Folder. Or enter the values by hand.

“Could not copy the setup”

The copy failed for a reason the message does not detail. Run it again with Copy. If it keeps failing, re-enter the sections by hand.

“Could not save the setup”

The setup was not saved. Click Save again. If the message comes back, report it to the SeveUp team along with the name of the Folder.

“Setup saved, but expected PSETs and properties were not stored: the server does not support them yet.”

The setup is saved, except for the list of expected PSETs and properties, which the server does not support yet. So do not expect a PSET comparison while this message appears.

“Could not read that file”

Importing a PSET list failed while reading the file. The expected format is .txt or .csv, one entry per line. Download Example, adapt it, then import it again.

“Could not save the reference model”

Your choice of reference model was not saved. Pick it again in the list. If the message persists, report it to the SeveUp team.

A model’s grid is not read

A model converted before 28/09 must be relaunched for its grid to be read. Rerun its conversion, then go back to the comparison.

FAQ

What is a Folder’s setup for?

It describes the values expected for every model in the Folder: base point, levels, PSETs and properties, and a reference model for grids. Models are compared with those expectations.

How do I copy the setup from one Folder to another?

Open the Setup of the destination Folder, pick the source under “Copy from another Folder”, then click Copy; the destination setup is replaced right away, without going through Save.

What does the tolerance (m) in the setup mean?

It is expressed in meters and applies to the base point coordinates as well as to level elevations. The reference model’s grid comparison also uses the setup tolerance.

What happens if I leave a coordinate or an elevation blank?

A blank coordinate is not compared; it does not mean 0. A blank level elevation does not check the height: only the level’s name counts.

Are extra levels in a model penalised?

No. An expected level is matched on its IfcName, and additional levels in a model are not penalised.

How do I enter expected PSETs and properties from a spreadsheet?

Paste the column directly: line break, comma, semicolon and tab all work as separators. You can also use Import with a .txt or .csv file.