Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

model.deploy to table and s.table.loadTable don't work well together #280

Open
smatton opened this issue Feb 19, 2020 · 4 comments
Open

Comments

@smatton
Copy link

smatton commented Feb 19, 2020

If I deploy a model to table using,
model.deploy(path='/path/to/dir', output_format='table')
it produces 3 tables

modelname.sashdat
modelname_weights.sashdat
modelname_weights_attr.sashdat

If I try to load these tables with

s.table.loadTable it will complain that it can't find modelname.ATTRS.sashdat , if I rename the attributes table to what it expects it will work.

modeldetect = s.table.loadTable(caslib='scz', path='detectmobile/Model_M43t70.sashdat', loadattrs=True)
modeldetectname = s.table.loadTable(caslib='scz',casout={'name':'mobiledetect'}, path='detectmobile/Model_M43t70_weights.sashdat')

@sasxianhu
Copy link
Contributor

@smatton
Copy link
Author

smatton commented Feb 19, 2020

I can use those, but shouldn't the naming conventions be consistent across API's?

@sasxianhu
Copy link
Contributor

sasxianhu commented Feb 19, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants