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.
What are custom solutions?
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.
Packages and the package editor
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"
The Package Editor
There are two major elements to a package:
- Workflows: A workflow is a pre-determined set of procedures and settings that ensure that procedures are carried out in exactly the same way each time. For more on workflows, see "About Workflows".
- Categories: In a package, workflows are organized into categories. You can group workflows into categories in any way that makes sense for your organization; however, a workflow can be included in only one category. The same workflow cannot be included in more than one category.
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 view
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
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"
Tips for working with packages
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
- Organize your files so that they are easy to update and maintain. For example, you may want to create a single folder for resources used in your workflows. Then, within that folder, create specific folders for related items, such as quant methods, images, and spectra files. Then, keep the folder in the same location and keep the file names the same. You can then use the Update commands in the Workflow Editor to quickly update all of the workflow's dependencies.
- Keep your workflows as simple as possible. For example, the Embedded Workflow tile is a powerful tool, but it adds greater complexity to your project. Whenever the embedded workflow is updated, you will need to manually update every other workflow that uses it.