A summary of replicates contained in a Skyline document is available by clicking the "replicates" link in the Document Summary
The Replicate List
provides annotation details and sample information for each replicate.
For graphical views that incorporate replicate data, see the following documentation:
Sample File Scoped Chromatograms
Skyline can extract and store chromatogram-style data that is scoped to a raw data file. Examples include keeping track of the pressure or voltage traces recorded by the instrument during its data acquisition. This topic describes how to access the sample-file scoped chromatogram data within Panorama.
Chromatogram Data Storage
Users import raw data files as normal into Skyline. Skyline automatically inspects them and extracts whatever pressure traces or other time-series data is available, and stores it in its SKYD chromatogram file format. When these Skyline files are imported into Panorama, this information is stored in the targetedms.SampleFileChromInfo table. No additional user action is needed to include the chromatogram data.
User Interface Access
Users will be able to go to the replicate list for a given Skyline document and click to see details, including the plots of the time-series data.
The targetedms.SampleFileChromInfo table is exposed for API-based access. Developers can view the table by selecting (Admin) > Developer Links > Schema Browser
Targeted MS Chromatogram Crawler
Administrators can obtain a listing of chromatograms stored on their site via a crawler which will check each container and list chromatograms found. This assists admins in locating chromatograms that can be deleted from the database.
- Select (Admin) > Site > Admin Console.
- Click Settings.
- Under Configuration, click Targeted MS Chromatogram Crawler.
- Click Start Crawl.
- You will see the pipeline progress.
- When the status shows as complete, click the word COMPLETE to see the crawl log.
- The log will begin with key statuses, show you a per-container record of the crawling completed, and conclude with a "Crawl summary by Skyline document counts."
: For each container crawled, the job will log the number of chromatograms that have byte offsets in the DB (which will be zero for non-Panorama folders or Panorama folders which have no imported Skyline files, or which were all imported before we started storing byte indices). It will iterate through all of the Skyline files in the container and inspect five chromatograms (the most typical problem will be that the server can’t find a SKYD file, so there’s little benefit to check out every chromatogram in each file). It will report the status for the chromatograms it inspects:
- No data available at all: the server never had a SKYD file when it loaded data.
- dbOnly: DB contains bytes, but not offset so impossible to retrieve directly from file.
- diskOnly: DB does not contain bytes, but does have indices and data was retrieved successfully from file.
- noSkydResolved: DB contains bytes and offset, but we can't resolve the SKYD path, perhaps because the S3 bucket is no longer configured.
- skydMissing: DB contains bytes and offset, but we can't find the SKYD file that's referenced.
- mismatch: Both DB-based and file-based bytes available, but they do not match.
- match: Both DB-based and file-based bytes available, and they do match.
- skipped: we hit our limit of 5 for the current file and didn’t examine the rest.