qat.qlmaas

Submitting a job to a Qaptiva Access server

QLMaaS provides classes to connect to a Qaptiva Access server and defining a remote stack:

qat.qlmaas.QLMaaSConnection

Foremost interface for communicating with the QLMaaS server

qat.qlmaas.generators.QLMaaSGenerator

Interface for management of a remote Generator

qat.qlmaas.plugins.QLMaaSPlugin

Interface for management of a remote Plugin

qat.qlmaas.qpus.QLMaaSQPU

Interface for management of a remote QPU

qat.qlmaas.result.AsyncResult

High level class to manage a pending result

Classes QLMaaSQPU and QLMaaSPlugin are used to manage QPUs and Plugins defined on the server side. The object could be piped using the syntax PLUGIN | ... | PLUGIN | QPU to build a computation stack defined on the server side

Warning

Please note that a stack can’t be composed of both remote and local plugins / qpus

Getting information from the server

Classes QLMaaSConnection (using the method get_jobs_info()) and AsyncResult (using the method get_info()) can be used to get information on a list of jobs or a specific job.

All these meta data are wrapped in a data structure called JobInfo. A standard use of QLMaaS doesn’t require to instanciate these objects manually.

Getting the job ID on the server

Qaptiva Access is designed to create processes on the server side. Retrieving the Qaptiva Access job ID from this process can be useful in many cases (e.g., to log information about the job).

The function get_job_id() is used to extract a job ID from a Qaptiva Access process. An exemple can be seen in the API reference of get_job_id().

qat.qlmaas.job_id.get_job_id()

Extract the job Qaptiva Access job ID from a process