Collections Tree

The Collections Tree holds the project's shared resources: the saved views, the classification schemes everything else is logged against, and the files kept in the project folder. Nothing here is a piece of geometry in the 3D view — these are the lists and libraries the rest of the project draws on. It is the Collections tab of the left panel.

Branches

The branches appear in this order and are always present.

Branch	What it holds	Right-click reference
Viewpoint	Saved camera positions.	Viewpoint
Scenes	Saved visibility states of the 3D view.	Scenes
Facies	The project's facies scheme.	Facies and classification lists
Associations	Facies associations, each listing its facies.	Facies and classification lists
Grainsize	The grain-size scale used down a log.	Facies and classification lists
Generic Classes	User-defined classification lists, each with its own entries.	Facies and classification lists
Base Contacts	The kinds of contact at the base of a log unit.	Facies and classification lists
Lithologies	The lithology scheme.	Facies and classification lists
Sed Structures	Sedimentary structures.	Facies and classification lists
Fill Patterns	The fill patterns log units are drawn with.	Facies and classification lists
Palaeo	Fossils and other palaeontological entries.	Facies and classification lists
Contacts	Named contacts (picked boundaries), each with a contact type, shared project-wide. Called Picks in earlier versions.	Contacts, Units and Intervals
Units	Named stratigraphic units, the intervals between contacts.	Contacts, Units and Intervals
Intervals	Named spans between a younger and an older contact, which a log's beds, geobodies and orientations can belong to. Called Correlations in earlier versions.	Contacts, Units and Intervals
Sets	The discontinuity sets orientations are tagged with, each with an optional joint strength.	Sets
Camera Calibrations	Camera and lens calibration profiles from SfM and photogrammetry imports.	Camera Calibrations
Icons	The SVG icon library used for logged features.	Icons
Log Templates	The templates controlling how a log is drawn.	Log Templates
Correlation Panels	Reserved for saved panel layouts; not populated in this release.	Log Templates
Backups	The project's backup files, grouped by year and month.	Backups
HTML	The project's web pages and its virtual field guides.	HTML / Field Guides
PYTHON	The scripts in the project's PYTHON folder.	PYTHON
Reports	The analysis reports in the project's Reports folder.	Reports
Sky Boxes	Sky backgrounds and environment maps.	Sky Boxes
Colour Maps	The colour ramps attributes are coloured by.	Colour Maps
MPCDI	Multi-projector display configurations and their viewports.	MPCDI
Transforms	Coordinate transforms saved from a georeferencing or alignment, ready to apply to other data.	Transforms
Stress Tensors	The project's stress states, each with its principal stresses and failure parameters; one is active.	Stress Tensors
Rock Materials	Intact rock materials: UCS, mi, modulus and unit weight.	Rock Materials
Geotechnical Domains	Rock masses with their classification inputs and results: RMR89, Q, GSI, Hoek-Brown.	Geotechnical Domains
Analysis Runs	A record of every Slope Stability and Block Size run, flagged when a set it read has changed.	Analysis Runs
Recycle	The project's RECYCLING folder: files deleted from the tree.	Recycle

Shared menus

Most of these branches are reference lists and share one group menu and one item menu, listed on the Standard Item and Group Menus page.

How the branches behave

• Three branches mirror a folder rather than the project database: HTML, PYTHON and Recycle are read from disk each time the tree is refreshed, and Reports is read from the project's Reports folder. A file added or removed outside VRGS appears or disappears on the next refresh.
• Adding an entry. New on a branch header adds an entry of that branch's type; for viewpoints and scenes it captures the current 3D view.
• Editing an entry. Select it and change its name, colour, symbol or icon in the Properties panel. Entries in the classification lists have no editor of their own.
• Sharing a scheme. Export and Import on a branch header write and read a library file, so a facies scheme or icon set can be reused across projects.
• Double-click an HTML page, script or report to open it in its editor; a viewpoint or scene to apply it.
• Deleting. Most entries are deleted outright. Files under HTML and Reports are recycled into the RECYCLING folder instead, so a mistake is recoverable.

The behaviours common to all three trees are on the Project Trees overview.