Bundle and share workflows using the Package Editor and open and run packages using the Operator interface.
This page offers a brief overview of using packages and the Operator interface in OMNIC Paradigm software to develop and run custom solutions. When available, follow the links to find more detailed information about using specific features.
With custom solutions in OMNIC Paradigm software, you can design and bundle workflows for other operators to use.
A developer designs workflows and bundles them with all their required files into Packages and then shares the packages as RDEP files.
An Administrator then opens the packages so that the workflows can be run using the Operator interface.
A package is an organized collection of workflows that can be easily shared. When you bundle workflows into a package, the package includes all of the files and information necessary to run the workflow on another system, including any reference spectra, images, and QNT files.
When you create and export a package, an Administrator at another site can open the package in the Operator interface so that users can run all of the included workflows.
For details on creating and exporting packages, see "Create or Edit a Package".
There are two major elements to a package:
When you export a package, all of the required files used in the workflows are packaged as well, ensuring that operators have all the files they need to run the workflows when they open the package.
The Operator interface is used for running workflows loaded from packages and for managing packages. After opening a package, operators are presented with a simplified interface designed to run the package workflows.
The Operator Administrator can control which workflows are available by opening or deleting packages.
The Operator interface is similar to OMNIC Paradigm software's touchscreen interface but presents only workflows from opened packages.
An Operator Administrator can open, update, and delete packages using the administrator controls. For details on opening and deleting packages, see "Operator Administrator".
When creating workflows and packages, it can be challenging to keep track of dependencies, such as quant methods and embedded workflows. The following tips may help you manage your files and ensure your workflows are up to date and easy to maintain.
You can create a new package or open and edit an existing package with the Package Editor.
Before you create a package, you will need at least one workflow. For more on creating and using workflows, see "About Workflows".
Packages can be created only in the Desktop interface of OMNIC Paradigm software.
There are a few important factors to consider when organizing your workflows and categories in packages.
Consider the following example:
Is displayed as :
You can open and edit a package either from the Packages pane on the dashboard or from a saved RDEP file.
The Package Editor includes several tools for updating workflows and their associated files.
When you add a workflow to a package, the workflow file is copied to the package. Any updates apply only to this package copy and are not reflected in the original file or any other packages that have copied the workflow file.
To keep the workflow files and their associated files (such as images or QNT files) synchronized, you must update them in the Workflow Editor manually. To avoid unexpected behaviors or results, you may want to update the workflow directly using the Workflow Editor and then use only the Update Workflow command in the Package Editor.
|Update Workflow||Reloads the selected workflows and updates any changes, including any files included in the workflow (for example, changed image files)|
|Update Embedded||Updates any workflows embedded using the Embedded Workflow tile.|
|Update Quant||Reloads any .QNT files that were included in the workflows.|
|Update Image||Reloads any image files used in the workflows.|
Use the Run command to test the package before exporting it. By running the package, you can view and run categories and workflows as they will be shown in the Operator interface.
Note: When you run the package, if you run any workflows that collect data, the measurements are added to your database just as if you ran the workflow normally.
You can set a workflow to run automatically using Auto Run. If automatic running is enabled, the workflow will run without any operator input. The workflows will run in the background while you use the software. If a workflow is running in the background, the operator will need to wait for it to complete before running another workflow.
You can set workflows to auto run only if they do not require any user input.
If multiple workflows are scheduled to run with Auto Run, they are added to a queue. For example, if one workflow runs every hour and another every two hours, they will both run on the overlapping hours and will not interfere with one another.
The workflow will run automatically after the package is opened in the Operator interface.
Use the Administrator controls in the Operator interface to manage packages, to change the Administrator password, and to return to the Desktop interface.
To access the administrator controls, select Administrator from the menu in the Operator interface and enter the correct password. The default password is Password. The Administrator should change the password immediately after installing the software.
Use the Package Maintenance tab in the Administrator view to manage packages.
Opening a package loads the package categories and workflows into the Operator interface. Once the package is opened, operators can select categories and run workflows. Any workflows set to run automatically will begin running as scheduled.
When you open a new package, new categories and workflows are added to the categories and workflows from previously opened packages. For example, if the administrator opens "Package A" and then later opens "Package B", the operator will see the categories and workflows from both packages.
When you open a package with the same name as a previously opened package, the package is updated.
For example, if you have already opened a package called "Package A" in the past, when you open a new package that is also called "Package A", the new package replaces the previous package.
Deleting a package removes that package's categories and workflows from the Operator interface.
Use the Change Password tab to change the password for the Operator Administrator.