cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
hemagso
‎03-09-2018
  • 3 Posts
  • 0 Likes Given
  • 0 Solutions
  • 0 Likes Received

Grid processing in SAS Miner never starts

by Calcite | Level 5 in Administration and Deployment
‎01-29-2018 12:55 PM
‎01-29-2018 12:55 PM
Hello,   I am currently having a problem with my company SAS Miner deployment. After creating a diagram and running it, the first steps of the diagram (Data Source creation and Data Partition) run almost immediatly, but the modelling nodes (More specifically, Gradient Boosting Tasks) don't start at all.    They keep SAS Miner busy, with a running icon over each node, but listing the active jobs on the grid server (Using LSF bjobs or even unix ps over each server) returns nothing. The grid server name never appear below the node.   Sometimes, after hours (And I mean, 5 or 6 hours) the processing starts and proceeds as normal. The problem is affecting some users on my organization but not all.   Have anyone had any similar issues? Any help would be appreciatted. ... View more

Re: Segmentation Violation in Task ARBOR

by Calcite | Level 5 in SAS Data Science
‎01-04-2017 08:42 AM
‎01-04-2017 08:42 AM
Thank you Rick! We tested on the new version of SAS and this resolved the issue. ... View more

Segmentation Violation in Task ARBOR

by Calcite | Level 5 in SAS Data Science
‎12-28-2016 07:04 AM
‎12-28-2016 07:04 AM
Hello, I am using SAS Enterprise Miner (Version 13.2) to develop gradient boosting models (Using the Arbor Procedure).   I am stumbling on a error that seems to be input dependent, and I am have not been able to determine what conditions can cause it. When I run the procedure on the full dataset (1570 features and 75k sample size) I get a Segmentation Violation error:   Segmentation Violation In Task [ ARBOR (2 ] SptGbmClearInitialF+0x00350 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor spt376+0x00150 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor spt380+0x00320 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor ArbDbu1GetNodes+0x003b0 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor ArbTaskInputVbuf+0x001fc - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor arb188+0x00b54 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor arb184+0x0067c - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor arb191+0x002f0 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor spt308+0x00d9c - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor zipstmt+0x0109c - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor zipok+0x000c4 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor yspproc+0x00830 - /sas92/bin/SASFoundation/9.2/sasexe/sasxshel ziparse+0x000cc - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor sasarbor+0x000a4 - /sas92/bin/SASFoundation/9.2/sasexe/sasarbor vvtentr+0x00130 - /sas92/bin/SASFoundation/9.2/sasexe/sas ___makecontext_v2+0x00108 - /lib/sparcv9/libc.so.1 NOTE: PROCEDURE ARBOR used (Total process time): real time 1:17.30 cpu time 21.01 seconds NOTE: 821765 kilobytes of physical memory. NOTE: Will use 75000 out of 75000 training cases. NOTE: Using memory pool with 841420800 bytes. NOTE: The SAS System stopped processing this step because of errors. NOTE: There were 75000 observations read from the data set WORK.K_CLST_A1_75. I had limited success in droping some features to make the code execute, but the process is guesswork based and cumbersome on my team (As we have to guess which feature may be causing the problem). Besides, I don't even know if this is a true solution.   I tried to reproduce the error on Dummy data, as I can't disclose the real dataset that is causing the problem, to no avail. I have a binary target and only interval inputs, and I am using the following parameters in the procedure:   MAXDEPTH: 2 NITERATIONS: 50 TRAINPROPORTION: 0.6 SHRINKAGE: 0.1 EXHAUSTIVE: 5000 Thanks in advance ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎03-09-2018 03:27 AM
Quick links