sassoftware / sassoftware/python-sasctl
Error using SASCTL to register a Python model to MM in Viya 4
@jlwalke2 y travaille déjà.
Depuis le 6/1/2023.
- Langage dominant
- Python
- Étoiles
- 52
- Forks
- 45
- Merge moyen
- 23 h 38 min
- PR mergées (30 j)
- 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
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.