BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
klroesner
Obsidian | Level 7

Hello World,

We have a problem executing a CAS action: sequence.pathing . Does anyone know what the error message means? The program appears to be correct.

 

/*Dokumentation Action Set: Sequence Action Set */
/* https://documentation.sas.com/?docsetId=casanpg&docsetVersion=8.3&docsetTarget=n0gse7erokgd4un1gvqzehse1fkg.htm&locale=en*/


/* Libname */
cas seq;
libname mycas cas caslib=PowerUserDM;


/* What CAS sessions do I have running? */
cas _all_ list;


/* Zugriff auf die Daten über print */
proc print data=mycas.VP_SEQUENCE_DATA (obs=5);
run;


/*Reduktion der Daten für diesen Test */
data mycas.VP_SEQUENCE_DATA_tmp promote ; 
            set mycas.VP_SEQUENCE_DATA (obs = 10000); 
run;

/* Sequenzanalyse */
proc cas;                                                       
   sequence.pathing / table={caslib="PowerUserDM" name="VP_SEQUENCE_DATA_tmp"} 
                      item="EREIGNIS_ANONYM"
                      time="ZEIT"
                      tran="VS_VERS_NR_ANONYM"
                      casOutSequTranMap={caslib="casuser" name="casouttable", replace=true}
                      casout={caslib="casuser" name="versicherten_sequence", replace=true}
                      ;
   run;
quit;

cas seq terminate;

Log:

 

OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
75    
76    *----------------------------------------------------NICHT Lauffähiges Programm mit "proc cas pathing" auf artifiziellen
76  ! Daten----------------------------------------------------;
77    
78    
79    /*Dokumentation Action Set: Sequence Action Set */
80    /* https://documentation.sas.com/?docsetId=casanpg&docsetVersion=8.3&docsetTarget=n0gse7erokgd4un1gvqzehse1fkg.htm&locale=en*/
81    
82    
83    /* Libname */
84    cas seq;
NOTE: The session SEQ connected successfully to Cloud Analytic Services rviap0v02.dst.tk-inline.net using port 5570. The UUID is 
      544a6756-aa54-ad44-85c3-a8c0db933ac5. The user is P226526 and the active caslib is CASUSERHDFS(P226526).
NOTE: The SAS option SESSREF was updated with the value SEQ.
NOTE: The SAS macro _SESSREF_ was updated with the value SEQ.
NOTE: The session is using 4 workers.
85    libname mycas cas caslib=PowerUserDM;
NOTE: Libref MYCAS was successfully assigned as follows: 
      Engine:        CAS 
      Physical Name: 544a6756-aa54-ad44-85c3-a8c0db933ac5
86    
87    
88    /* What CAS sessions do I have running? */
89    cas _all_ list;
NOTE: Session SEQ is ACTIVE using port 5570 and host rviap0v02.dst.tk-inline.net for user P226526. The session UUID is 
      544a6756-aa54-ad44-85c3-a8c0db933ac5.
90    
91    
92    /* Zugriff auf die Daten über print */
93    proc print data=mycas.VP_SEQUENCE_DATA (obs=5);
94    run;
NOTE: The PROCEDURE PRINT printed page 2.
NOTE:  Verwendet wurde: PROZEDUR PRINT - (Gesamtverarbeitungszeit):
      real time           1.57 seconds
      cpu time            0.18 seconds
      
95    
96    
97    /*Reduktion der Daten für diesen Test */
98    data mycas.VP_SEQUENCE_DATA_tmp promote ;
99                set mycas.VP_SEQUENCE_DATA (obs = 10000);
100   run;
NOTE: There were 10000 observations read from the data set MYCAS.VP_SEQUENCE_DATA.
NOTE: The data set MYCAS.VP_SEQUENCE_DATA_TMP has 10000 observations and 3 variables.
NOTE: The data set WORK.PROMOTE has 10000 observations and 3 variables.
NOTE:  Verwendet wurde: DATA statement - (Gesamtverarbeitungszeit):
      real time           0.22 seconds
      cpu time            0.05 seconds
      
101   
102   /* Sequenzanalyse */
103   proc cas;
104      sequence.pathing / table={caslib="PowerUserDM" name="VP_SEQUENCE_DATA_tmp"}
105                         item="EREIGNIS_ANONYM"
106                         time="ZEIT"
107                         tran="VS_VERS_NR_ANONYM"
108                         casOutSequTranMap={caslib="casuser" name="casouttable", replace=true}
109                         casout={caslib="casuser" name="versicherten_sequence", replace=true}
110                         ;
111      run;
NOTE: Active Session now SEQ.
NOTE: Added action set 'sequence'.
ERROR: Connection failed. Server returned: Session reconnect failed: Could not find the specified session.
112   quit;
NOTE:  Verwendet wurde: PROZEDUR CAS - (Gesamtverarbeitungszeit):
      real time           46.16 seconds
      cpu time            1.89 seconds
      
113   
114   cas seq terminate;
NOTE: Libref MYCAS has been deassigned.
NOTE: Deletion of the session SEQ was successful.
NOTE: The default CAS session SEQ identified by SAS option SESSREF= was terminated. Use the OPTIONS statement to set the SESSREF= 
      option to an active session.
NOTE: Request to TERMINATE completed for session SEQ.
115   *----------------------------------------------------ENDE NICHT Lauffähiges Programm mit "proc cas pathing" auf artifiziellen
115 !  Daten----------------------------------------------------;
116   
117   OPTIONS NONOTES NOSTIMER NOSOURCE NOSYNTAXCHECK;
130   
1 ACCEPTED SOLUTION

Accepted Solutions
klroesner
Obsidian | Level 7

Hello,

We have an answer from the technical support. The CAS action works as designed. The action must always be called with constraints such as minimal support, otherwise it leads to exploding data growth.

 

Cheers, Klaus

View solution in original post

6 REPLIES 6
AnnaBrown
Community Manager

Hi @klroesner,

 

Thanks for your question! If you haven't already, I suggest opening a track with Technical Support for this scenario. Check out this page for information on other ways to contact Tech Support.

 

Anna

 

 

 

klroesner
Obsidian | Level 7
Hi Anna, I‘ve allready opened a Ticket.

Thanks, Klaus
AnnaBrown
Community Manager

Excellent, thanks for responding back! Feel free to post any resolution you find as other community members may run into the same problem.

 

Anna

klroesner
Obsidian | Level 7

Hi Anna, the ticket is now at the SAS Global Support. It seems to be a problem with the CAS Action sequence.pathing.

The CAS Action has an enormous consumption of memory:

 

80 Observation -> 6 GB RAM
95 Observation -> 27,75 GB RAM
97 Observation -> 103, GB RAM
98 Observation -> game over and the error occurs

 

 Klaus

klroesner
Obsidian | Level 7

Hello,

We have an answer from the technical support. The CAS action works as designed. The action must always be called with constraints such as minimal support, otherwise it leads to exploding data growth.

 

Cheers, Klaus

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
How to choose a machine learning algorithm

Use this tutorial as a handy guide to weigh the pros and cons of these commonly used machine learning algorithms.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 1769 views
  • 2 likes
  • 2 in conversation