Parallel Experiment Auto-Numbering is a feature in Signals Notebook that enables administrators to implement a global numbering system for parallel experiments. This functionality helps organizations avoid duplicate naming by ensuring that parallel experiment numbers are consecutive across the entire system, regardless of which notebook contains the experiment. This article explains how to configure and use the system-wide auto-numbering feature for parallel experiments.
Solution:
Understanding Parallel Experiment Auto-Numbering
The auto-numbering feature for parallel experiments provides:
- System-wide consecutive numbering for all parallel experiments
- Independence from notebook location or organization
- Consistent naming patterns across the organization
- Prevention of duplicate experiment IDs
Enabling System-Wide Auto-Numbering for Parallel Experiments
- Log in to Signals Configuration with administrator privileges
- Click on the System Objects smart folder from the home page
- Select "Parallel Experiment" from the list of system objects
- Click on "Auto Numbering" to access the Parallel Experiment Auto Numbering page
- Check the "Enable global auto numbering for Parallel Experiments" checkbox
- Set the "Starting Parallel Experiment ID" value (default is 1)
- If you set a value higher than the last used number, the sequence will continue from the new higher number
- If you set a value lower than the last used number, the system will prevent you from saving the changes
- Click the "Save Settings" button to apply the configuration
Key Behaviors of System-Wide Auto-Numbering
- Next in Sequence: The system uses the maximum of either "last allocated number + 1" or the next starting number
- Number Ranges: When system-wide auto-numbering is enabled, number ranges defined in templates are ignored
- New Experiments: When a parallel experiment is created from a template or copied, it receives a new auto-generated name
- Moved Experiments: When a parallel experiment is moved between notebooks, it maintains its current name
System-Wide Auto-Numbering vs. Default Naming Methodology
| Feature | System-Wide Auto-Numbering Enabled | Default Naming Methodology |
|---|---|---|
| Numbering Scope | Numbers are consecutive across the entire system | Numbers follow notebook-specific or template-specific sequences |
| Template Impact | Template formatting is preserved, but numbers remain sequential | Template formatting and numbering follow template-specific sequences |
| Moving Experiments | Original name is preserved | Original name is preserved |
| Uniqueness | Guarantees system-wide unique IDs | May allow duplicate IDs across different notebooks |
Benefits of System-Wide Auto-Numbering
- Prevents Duplicate Names: Ensures each parallel experiment has a unique identifier across the system
- Simplifies Tracking: Makes it easier to track and reference parallel experiments regardless of location
- Supports Compliance: Helps meet regulatory requirements for unique identification of experimental data
- Improves Searchability: Facilitates finding specific parallel experiments by their unique ID
- Enhances Reporting: Provides consistent identifiers for use in reports and data analysis
Considerations Before Implementation
- Existing Experiments: Enabling auto-numbering does not rename existing parallel experiments
- Sequence Continuity: Consider starting with a number higher than any existing manual numbers to avoid confusion
- User Training: Ensure users understand that they cannot control the numbering when auto-numbering is enabled
- Template Design: Review templates to ensure they work well with auto-generated names
- Sub-Experiment Numbering: Consider how parallel experiment numbering relates to sub-experiment numbering
Best Practices
- Plan Before Implementation: Carefully consider your organization's naming requirements before enabling system-wide auto-numbering
- Documentation: Document your auto-numbering configuration decisions for reference
- Regular Audits: Periodically review experiment names to ensure the system is functioning as expected
- Consistent Approach: Consider using auto-numbering for all system objects (notebooks, experiments, parallel experiments) for consistency
By properly configuring parallel experiment auto-numbering, organizations can maintain consistent and unique experiment identification across their Signals Notebook environment, supporting traceability and compliance requirements while simplifying data management.
Comments
0 comments
Article is closed for comments.