Building models with SAS Enterprise Miner, SAS Factory Miner, SAS Visual Data Mining and Machine Learning or just with programming

Decision Tree Node Rules: Cutting of variables on output

Reply
Contributor
Posts: 31

Decision Tree Node Rules: Cutting of variables on output

In the Decision Tree  "Node Rules", it looks like my output is being cut off.

 

Example:

 

***** 

Node = 74

If color is ONE OF:  blue, purple, green, yellow, red, ora

***

 

It is clear that "ora" is being cut off and should say "orange", and I am uncertain what the value of the variable is in my output.  How can I determine all the values of the variable the tree used for the path?

 

 

SAS Employee
Posts: 122

Re: Decision Tree Node Rules: Cutting of variables on output

Go to Results --> View-->Model-->Variable Importance, the column "Number of Splitting rules" indicates which ones are used in splitting your tree. Those with 0 are not used. For the line truncation condition, you can go to project start up windows to reset "option linesize=300". Default is 256 which is cutting you off. 300 is just idea. Make sure you don't set this number to be too big. Hope this helps. Jason Xin
Contributor
Posts: 31

Re: Decision Tree Node Rules: Cutting of variables on output

I understand which VARIABLES are being used. It is not showing all the VALUES of the variables. How do I change the line size? What do you mean by "project startup windows"? Is that the only way to see the values of the variables?
SAS Employee
Posts: 122

Re: Decision Tree Node Rules: Cutting of variables on output

I see what you mean. Sorry I misunderstood you.

Could you go to Results -->Results --> View-->Scoring-->Score Code? You can see specific cuts of all the variables used to build branches.
If you go back to the PROJECT, select on the project name. Look at the configuration panel below. You should see two boxes Project Start Code (I mis-said it startup) and Project Macro Variables. Both have a little button box to its right. Click on the one for the Start Code. That will give you like a SAS Editor window where you can type as if you are doing BASE coding. You can just insert "options linesize=300.". Run it and check the log to make sure there is no error. The effect is within this EM project. Since part of your original question is Orange is cut short ORA. That indicates the default linesize of 256 is too short.
Contributor
Posts: 31

Re: Decision Tree Node Rules: Cutting of variables on output

Thanks, I will look at the score code.

When I tried the other option to insert "options linesize=300.", I got the following error: LINESIZE must be between 64 and 256.
SAS Employee
Posts: 122

Re: Decision Tree Node Rules: Cutting of variables on output

Let me check with my 'backend' to see if there are other ideas why it is chopped off. I don't want to send you to mess around with cfg files easily. But you cfg file may be capping you. Jason Xin
Ask a Question
Discussion stats
  • 5 replies
  • 344 views
  • 0 likes
  • 2 in conversation