About WendyCzika

WendyCzika · ‎04-20-2015

You need to also license Credit Scoring for SAS Enterprise Miner to be able to access the Scorecard node and the other Credit Scoring tools.

WendyCzika · ‎04-17-2015

The Score node is available from the Assess tab of the SAS Enterprise Miner node toolbar. Is that the one you mean?

WendyCzika · ‎04-16-2015

Yes as Reeza says, you would need to do something like the following inside the DATA step: ... begin_date = '26JUN2016'd; end_date='03JUL2016'd; call symput("start",begin_date); call symput("end", end_date); ... run; Then after the DATA step, the macro variables start and end are available to use with the actual dates in them.

WendyCzika · ‎03-23-2015

I think that is all correct. If you click on the SAS Code node, then click on the ellipsis button for Exported Data from the Properties panel, you can see from there whether your variable is being picked up correctly. Click on the row for TRAIN, then the Properties... button. On the Variables tab, you should see your new variable listed as a Target. I'm guessing it's the case that the Text Parsing node only displays variables with a particular role, but not sure why you wouldn't see it for Decision Tree. Anyway, confirming that it shows up here is the first step.

WendyCzika · ‎03-18-2015

You can try changing the properties Minimum Categorical Size and Leaf Size both to 1, and/or increasing the Significance Level property for splitting.

WendyCzika · ‎03-11-2015

Yes there seems to be some sort of limit around 2000 variables in the UI. I tried changing various properties - Significance Level (to 1), Leaf Size (to 1), and Exhaustive (to a very large number), turning off all p-value adjustments... but it still only shows around 2000 inputs for me as well in the Split Node dialog.

WendyCzika · ‎03-09-2015

Can you check in the Variables dialog for the Decision Tree node that all the variables you are expecting to see are set as Input?

WendyCzika · ‎12-17-2014

I assume you are using the property Import Tree Model=Yes, and selecting your tree model data set from the previous Decision Tree node, correct? If so, you can use an alternative approach to allow you to make interactive changes to a previously created tree: 1) Open the Interactive Tree application (so set Import Tree Model=No) 2) Click on the root node (should be the only node) and select Action>Paste Saved Tree... from the main menu 3) Select the TreeX_emtree data set from the Emws folder that contained your original tree, with TreeX being the original Decison Tree node 4) You should now see the previous tree structure, and you can make additional interactive changes. Hope that works for you.

WendyCzika · ‎12-12-2014

You can set the Maximum Branch property (under Splitting Rule) to 3 in the Decision Tree node.

WendyCzika · ‎12-08-2014

If I'm understanding correctly, I don't think you want to use Drop=Y in either of these situations. That is removing the variable from the data set for all subsequent nodes. For the two target situation, as long as you are not using Target1 as an input when modeling Target2 and vice-versa, you can set them both as Target variables, then in the modeling nodes, set Use=Yes to the one you want to use as the target and Use=No to the other. If you do want to use them as inputs when modeling the other one, you can use a Metadata node to change the two targets between target/input and input/target, if that makes sense. For the other situation where you want to keep variables but not include them in the model, you can either set them as Role=Rejected to begin with, or as Role=Input with Use=No in whatever nodes you want to exclude them from.

WendyCzika · ‎11-26-2014

It looks like you should use sampsio.assocs for the data= option on the PROC ASSOC statement instead of dmassoc. Hope that helps, Wendy

WendyCzika · ‎11-21-2014

I think this discussion might help you: It shows how you can use the SAS Code node to save out your exported training data (all rows). If that doesn't help, let us know!

WendyCzika · ‎11-21-2014

Also, from that Properties window that you show above, if you click on the Variables tab, then check the box for Label, you will see that "Predicted: ..." is the label for the column P_target that Miguel mentioned. In that Explore view of the table, it is showing the label not the column name so that's why you weren't seeing it as the P_target name.

WendyCzika · ‎11-20-2014

Yes in that case you can use the Chi-Square Statistic reported in StatExplore. Usually it is used in the opposite way though - you want to keep the inputs associated with the target

WendyCzika · ‎11-19-2014

You can use the StatExplore node (on the Explore tab) to calculate correlations between an interval target and interval inputs.

Online Status	Offline
Date Last Visited	Friday