About WendyCzika

XCND · ‎11-20-2023

Thanks Wendy!

WendyCzika · ‎09-27-2023

Please reach out to SAS Technical Support for help with this error https://support.sas.com/en/technical-support.html

WendyCzika · ‎09-07-2023

Yes, the 1st, 3rd, and 4th bullets are all ways of scoring new data where the target is unknown. Hope that helps!

WendyCzika · ‎02-17-2023

Can you check that the variable you have assigned the role of Target on the Data tab has a Level other than Interval? If it's an interval target, you need to use Linear Regression instead of Logistic Regression. If that's not the issue, you can right-click on the Logistic Regression node, select Log, and see if there is a more informative error message in there. Hope that helps, Wendy

WendyCzika · ‎11-04-2022

In transaction data used by the Association, Market Basket, Path Analysis, and Time Series nodes in EM, each observation represents a product that a customer has purchased, so multiple observations per customer (which is the ID variable), which is different than the typical structure of data used for predictive modeling.

saz1 · ‎09-13-2022

hello, did you manage to find how to resolve this problem?

KJazem · ‎09-12-2022

A quick follow-up. I tried inputting categorical variables into my LSTM model, and it errored out saying only target variables can be nominals. Encoding the products into integers gave me terrible results. Not sure what can be done in this case.

WendyCzika · ‎08-10-2022

You should be able to use the SCORE statement to create a data set with the predicted values for the training data: https://go.documentation.sas.com/doc/en/emhpprcref/15.2/emhpprcref_hpforest_syntax08.htm Or you can use the SAVE statement to create an analytic store ("astore") file that allows you to score new data using that generated file in HP4SCORE: https://go.documentation.sas.com/doc/en/emhpprcref/15.2/emhpprcref_hpforest_syntax07.htm and https://go.documentation.sas.com/doc/en/emhpprcref/15.2/emhpprcref_hp4score_toc.htm Hope that helps.

WendyCzika · ‎06-24-2022

Also for future issues in Model Manager, the Decisioning Community might be better suited to help you: https://communities.sas.com/t5/Decisioning/bd-p/decisioning

WendyCzika · ‎06-24-2022

To facilitate getting the information we need in order to debug this problem, can you please work with SAS Technical Support for this issue? https://support.sas.com/en/technical-support.html Thank you!

WendyCzika · ‎04-18-2022

You might find some helpful tips for improving the gradient boosting model here: https://communities.sas.com/t5/SAS-Communities-Library/Quick-tips-for-setting-your-Gradient-Boosting-node-properties-in/ta-p/513600

WendyCzika · ‎04-05-2022

A couple other things that could cause differences: the metadata: make sure it is the same in both EM and Model Studio if the data is big in Model Studio, the Batch Code node is sampling by default. Might have to make adjustments to that. Another option would be to use the Score Code Import node in Model Studio after using a Score node in EM to accumulate all the score code from a flow.

sbxkoenk · ‎04-01-2022

Thanks @WendyCzika . It's probably as simple as that indeed. This is one to remember ! @1dsspntdSSsr : I hope you haven't given up yet and that this suggestion / solution will still come in handy. Thanks, Koen

WendyCzika · ‎03-31-2022

My guess is that it's related to partitioning of the data. In EM, did you partition your data?

MariaD · ‎03-10-2022

Hi @iamy Did you resolve this issue? We're working on a fraud model developed on SAS Miner. Our objective is to use the PMML score node with the final model and then import it directly into FICO Blaze. There is any limitation on this process? Do we need to convert (or translate) the PMML generated by EM to import in FICO Blaze? Regards,

Online Status	Offline
Date Last Visited	‎01-15-2025 07:42 PM