Tetra Chromeleon Agent FAQ

How does the Chromeleon Data Agent work?

The Tetra Chromeleon Agent interacts with Chromeleon through Chromeleon 7 SDK. Internally, it contains three tasks: scanning, generation, and upload.

  • Scanning: Agent scans the Data Vault selected by the user from Management Console to detect any new or updated injections. If so, the Agent records the Injection URLs to an internal SQLite database.
  • Generation: based on Scanning results, the Agent fetches the Injection and its related data, and then serializes the data as JSON files to a local folder.
  • Upload: the Agent uploads the JSON files to Tetra Data Lake. After the file is uploaded successfully, the file is removed to save disk space.

Which data items are fetched from Chromeleon?

Tetra Chromeleon Agent extracts the injection and the data associated with it. Here is a brief summary of the data items extracted from Chromeleon.

  • Injection
  • Sequence
  • Instrument Method
  • Processing Method
  • MsRawItem
  • Peak
  • Signal
  • Chromatogram
  • Spectral Field
  • Spectrum
  • Audit Trail

Does the Tetra Chromeleon Data Agent have limitations?

Limitation from Chromeleon SDK:

  1. The Tetra Chromeleon Agent directly references Chromeleon SDK, the Agent inherits the limitation of Chromelon SDK. Since the Chromeleon SDK is a 32-bit component, it that only can consume 2 GB of Memory.

  2. All of the data items fetched from Chromeleon SDK through a class called ItemFactory are thread static. It has an internal caching mechanism to hold the objects it fetches.

The combination of the two limitations above could result in an Out Of Memory issue. The Chromeleon Data Agent handles this by processing by the batch to reduce the mitigate this issue.

The current release (version 1.0.0) can process a Data Vault that contains up to 1 million injections.


Did this page help you?