Tree Preset Feature
The Tree Preset feature allows you to define a hierarchical structure of parts that will be automatically created when a new run is initiated. This feature is particularly useful for experiments that require a consistent structure of parts and subparts.
Overview
When creating a sample type, you can define a tree preset that specifies how parts should be organized in a hierarchical structure. This preset will be applied automatically when creating a new run with that sample type, saving time and ensuring consistency across similar experiments.
How to Use Tree Presets
Defining a Tree Preset
To define a tree preset:
Navigate to the Sample Type management section
Create a new Sample Type or edit an existing one
In the Tree Preset field, enter your hierarchical structure using the format described below
Tree Preset Format
The tree preset uses a simple text-based format where:
Each line represents a parent part
Numbers separated by colons (
:) represent the hierarchy levelsThe first number is always 1 (representing a single parent part)
Subsequent numbers represent the number of children at each level
Example Format
This example will create:
One parent part with 3 children, each with 2 children (creating a total of 1 + 3 + 6 = 10 parts)
One parent part with 2 children (creating a total of 1 + 2 = 3 parts)
More Complex Example
This will create 4 parent parts, where:
The first parent has 3 children, each with 3 children
The second parent has 2 children, each with 2 children
The third parent has 2 children, each with 3 children
The fourth parent has 2 children, each with 2 children
Validation Rules
The system validates tree presets to ensure they can create valid part structures:
Each line must have the correct format (numbers separated by colons)
All values must be valid positive integers
Empty lines are ignored
If the validation fails, the system will display error messages indicating the issues that need to be corrected.
Benefits of Using Tree Presets
Consistency: Ensures that similar experiments have the same part structure
Efficiency: Saves time by automatically creating complex part hierarchies
Accuracy: Reduces the risk of human error when manually creating parts
Standardization: Helps maintain standard protocols across different runs
Best Practices
Keep your tree presets as simple as possible while meeting your experimental needs
Use consistent patterns across similar sample types
Test your tree presets with a sample run before using them in production
Document the meaning of each level in your organization's standard operating procedures
Limitations
Tree presets only define the hierarchical structure, not the properties of individual parts
Once parts are created, modifying the tree preset will not affect existing runs
Very complex hierarchies may be difficult to represent and maintain in the text format