sassoftware / sassoftware/python-sasctl

Error using SASCTL to register a Python model to MM in Viya 4

Open
#136 1 comment 0 reactions 2 assignees View on GitHub

@jlwalke2 is already working on this.

Since Jan 6, 2023.

bug
Dominant language
Python
Stars
52
Forks
45
Avg merge
23h 38m
Merged PRs (30d)
2

Description

Describe the issue
SASCTL 1.7.3 can register a simple Python model to MM in Viya 4, but when trying to execute a Scoring Task it produces an error.

To Reproduce
import pandas as pd
from sasctl import Session, register_model, publish_model
from sklearn.linear_model import LogisticRegression

Load the Iris data set and split into features and target.

df = pd.read_csv('Data/iris.csv')
X = df.drop('species', axis=1)
y = df.species.astype('category')

Fit a sci-kit learn model

model = LogisticRegression()
model.fit(X, y)

with Session('budsprod.viyamtes.com', 'gegrab', 'XXXXX', verify_ssl=False):
model_name = 'Iris Regression2'

# Register the model in Model Manager

register_model(model,
model_name,
input=X, # Use X to determine model inputs
project='Iris2', # Register in "Iris" project
force=True) # Create project if it doesn't exist

Expected behavior
The Scoring Task in MM should execute and score on a sample set of records. The error received in MM:

NOTE: Created package _076796cfb3ca459eb8a285e3cd30c38 in data set "casuser(gegrab)"._076796cfb3ca459eb8a285e3cd30c38.
NOTE: Execution succeeded. No rows affected.
NOTE: Running 'modelPublishing' action set with 0 workers.
NOTE: Execution of model 'TempModel_781437f5-15be-3842-99a0-eea05a45c6ba ' succeeded.
ERROR: There is no session-scope table Test_3_Iris_Regression2_v1_0_2022_11_04_14_42_49_output in caslib gegrab_s of Cloud Analytic Services.
NOTE: Cloud Analytic Services dropped table TempModel_781437f5-15be-3842-99a0-eea05a45c6ba**

Stack Trace
If you're experiencing an exception, include the full stack trace and error message.

Version
What version of sasctl are you using? 1.7.3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.