No Code Model Deployment

Models can be uploaded from an authorised repository, deployed to a Flow and used in a Job without code changes or platform-level interventions. Model developers and model users manage the entire process via the UI.

TRAC’s RTL VALIDATIONS

LOCAL RUNTIME (OPTIONAL)

Does the code execute in the IDE using the trac runtime (Python) package and local data inputs? If so, it will pass the next step.

PRESENCE (ON IMPORT)

Does the model code contain a properly constructed function which declares its schema to the platform?

COMPATIBILITY (BUILD FLOW)

Does the proposed placing of a model in the Flow enable the input data requirements defined in the schema, to be satisfied?

CONFORMITY (RUN JOB)

Does the code perform in line with the declared schema when executed on the platform using the trac runtime service?

SELF-GENERATING UI

A model can be used to launch a simple Job or be deployed into a Flow. The UI needed to complete these actions are automatically generated using the model schema, so no platform level actions are required to make a model available in the front-end.

THREE PARTS OF A MODEL SCHEMA

  • INPUTS: The attribute names and schemas of the input data the model needs in order to run.

  • PARAMETERS: Additional inputs to be provided via the UI as part of the Job configuration process.

  • OUTPUTS: The attribute names and schemas of all the data the model generates when it runs