Skip to content
No result to preview.

Click in-app to access the full platform documentation for your version of DataRobot.

Predictions > Portable prediction methods > Scoring Code

Scoring Code

Availability information

Contact your DataRobot representative for information on enabling the Scoring Code feature.

The Scoring Code feature exports Scoring Code for qualifying Leaderboard models, allowing you to use DataRobot-generated models outside the platform.

For more information, see the Scoring Code considerations.

The following sections describe how to work with Scoring Code:

Topic Describes
Scoring Code overview Scoring Code, how you download it, and how to score with it.
Download Scoring Code from the Leaderboard Downloading and configuring Scoring Code from the Leaderboard.
Download Scoring Code from a deployment Downloading and configuring Scoring Code from a deployment.
Download time series Scoring Code Downloading and configuring Scoring Code for a time series project.
Scoring at the command line Syntax for scoring with embedded CLI.
Scoring Code usage examples Examples showing how to use the Scoring Code JAR to score from the CLI and in a Java project.
JAR structure The contents of the Scoring Code JAR package.
Generate Java models in an existing project Retraining models that were created before the Scoring Code feature was enabled.
Backward-compatible Java API Using Scoring Code with models created on different versions of DataRobot.
Scoring Code JAR integrations Deploying DataRobot Scoring Code on an external platform.

Feature considerations

Consider the following when working with Scoring Code:

  • Using Scoring Code in production requires additional development efforts to implement model management and model monitoring, which the DataRobot API provides out of the box.

  • Exportable Java Scoring Code requires extra RAM during model building. As a result, to use this feature, you should keep your training dataset under 8GB. Projects larger than 8GB may fail due to memory issues. If you get an out-of-memory error, decrease the sample size and try again. The memory requirement does not apply during model scoring. During scoring, the only limitation on the dataset is the RAM of the machine on which the Scoring Code is run.

Model support

  • Scoring Code is available for models containing only supported built-in tasks. It is not available for custom models or models containing one or more custom tasks.

  • Scoring Code is not supported in multilabel projects.

  • Keras models do not support Scoring Code by default; however, support can be enabled by having an administrator activate the Enable Scoring Code Support for Keras Models feature flag. If enabled, note that these models are not compatible with Scoring Code for Android and Snowflake.

Additional instances in which Scoring Code generation is not available include:

  • Naive Bayes

  • Text tokenization involving the MeCab tokenizer

  • Visual AI and Location AI

Time series support

  • The following time series capabilities are not supported for Scoring Code:

    • Row-based / irregular data
    • Nowcasting (single forecast point)
    • Intramonth seasonality
    • Time series blenders
    • Autoexpansion
    • EWMA (Exponentially Weighted Moving Average)

  • Scoring Code is not supported in time series binary classification projects.

  • Scoring Code is not typically supported in time series anomaly detection models; however, it is supported for IsolationForest and some XGBoost-based anomaly detection model blueprints. For a list of supported time series blueprints, see the Time series blueprints with Scoring Code support note.

Time series blueprints with Scoring Code support

The following blueprints typically support Scoring Code:

  • AUTOARIMA with Fixed Error Terms
  • ElasticNet Regressor (L2 / Gamma Deviance) using Linearly Decaying Weights with Forecast Distance Modeling
  • ElasticNet Regressor (L2 / Gamma Deviance) with Forecast Distance Modeling
  • ElasticNet Regressor (L2 / Poisson Deviance) using Linearly Decaying Weights with Forecast Distance Modeling
  • ElasticNet Regressor (L2 / Poisson Deviance) with Forecast Distance Modeling
  • Eureqa Generalized Additive Model (250 Generations)
  • Eureqa Generalized Additive Model (250 Generations) (Gamma Loss)
  • Eureqa Generalized Additive Model (250 Generations) (Poisson Loss)
  • Eureqa Regressor (Quick Search: 250 Generations)
  • eXtreme Gradient Boosted Trees Regressor
  • eXtreme Gradient Boosted Trees Regressor (Gamma Loss)
  • eXtreme Gradient Boosted Trees Regressor (Poisson Loss)
  • eXtreme Gradient Boosted Trees Regressor with Early Stopping
  • eXtreme Gradient Boosted Trees Regressor with Early Stopping (Fast Feature Binning)
  • eXtreme Gradient Boosted Trees Regressor with Early Stopping (Gamma Loss)
  • eXtreme Gradient Boosted Trees Regressor with Early Stopping (learning rate =0.06) (Fast Feature Binning)
  • eXtreme Gradient Boosting on ElasticNet Predictions
  • eXtreme Gradient Boosting on ElasticNet Predictions (Poisson Loss)
  • Light Gradient Boosting on ElasticNet Predictions
  • Light Gradient Boosting on ElasticNet Predictions (Gamma Loss)
  • Light Gradient Boosting on ElasticNet Predictions (Poisson Loss)
  • Performance Clustered Elastic Net Regressor with Forecast Distance Modeling
  • Performance Clustered eXtreme Gradient Boosting on Elastic Net Predictions
  • RandomForest Regressor
  • Ridge Regressor using Linearly Decaying Weights with Forecast Distance Modeling
  • Ridge Regressor with Forecast Distance Modeling
  • Vector Autoregressive Model (VAR) with Fixed Error Terms
  • IsolationForest Anomaly Detection with Calibration (time series)
  • Anomaly Detection with Supervised Learning (XGB) and Calibration (time series)

While the blueprints listed above support Scoring Code, there are situations when Scoring Code is unavailable:

  • Scoring Code might not be available for some models generated using Feature Discovery.
  • Consistency issues can occur for non day-level calendars when the event is not in the dataset; therefore, Scoring Code is unavailable.
  • Consistency issues can occur when inferring the forecast point in situations with a non-zero blind history; however, Scoring Code is still available in this scenario.
  • Scoring Code might not be available for some models that use text tokenization involving the MeCab tokenizer.
  • Differences in rolling sum computation can cause consistency issues in projects with a weight feature and models trained on feature lists with weighted std or weighted mean.
Time series Scoring Code capabilities

The following capabilities are currently supported for time series Scoring Code:

The following time series capabilities are not supported for Scoring Code:

  • Row-based / irregular data
  • Nowcasting (single forecast point)
  • Intramonth seasonality
  • Time series blenders
  • Autoexpansion
  • EWMA (Exponentially Weighted Moving Average)

Prediction Explanations support

Consider the following when working with Prediction Explanations for Scoring Code:

  • To download Prediction Explanations with Scoring Code, you must select Include Prediction Explanations during Leaderboard download or Deployment download. This option is not available for Legacy download.

  • Scoring Code doesn't support Prediction Explanations for time series models.

  • Scoring Code only supports XEMP-based prediction explanations. SHAP-based prediction explanations aren't supported.

Updated December 28, 2022
Back to top