Member Junction
    Preparing search index...

    The training delegation every in-process caller uses: one production deps builder, one train-by-pipeline entry point and one retrain-from-snapshot entry point, so the Train operation, the Train action, auto-train, the pipeline builder and the rigs train (and retrain) the same way.

    Index

    Constructors

    Methods

    • Build the TrainingEngine's production dependency bundle from a per-call provider + user. Trained model files and Training Snapshot files go to the one storage provider PS_STORAGE_PROVIDER names (default "Local File System"), each recorded as an MJ: Files row; the scoring side reads a model file through the provider its row names (StorageProviderArtifactLoader). The snapshot store and the artifact store share one PredictiveStudioStorage, and the engine has the artifact store resolve it before anything of the run is written, so a provider not configured on this server refuses the run before training.

      The Record Changes history the as-of assembly replays is left to the engine's default: a complete-read RunViewRecordHistoryReader over the same dataAccess. The locked holdout is always the one the bound protocol declares (date-carved, seeded-random or rolling-origin). Snapshots are found by content hash through the same provider and user. A unit pipeline reads the Evaluation Protocol it is bound to through the same provider and user and trains through the trainer (MJSidecarTrainer over the process-shared sidecar).

      Parameters

      • provider: IMetadataProvider

        the owning provider for data access / multi-provider correctness

      • user: UserInfo

        the acting user threaded through every entity op for isolation/audit

      Returns Promise<TrainingDeps>