If I do not understand wrongly your concern, you can achieve updating the aggregated table correctly applying parameters in the filter of the aggregated table. this should keep them synchronized. ... View more

Hello,   You want to display the legend, but hide the name of the grouping variable?   A workaround might be to create a duplicate of the grouping variable and rename it to something like "_", which would give you a legend like this:   ... View more

Not to my knowledge. This code: cas mySession; libname x cas caslib="casuser"; %put NOTE: %qsysfunc(pathname(x)); proc cas; session.sessionID; quit; Produces this output in the log:   0 %put NOTE: %qsysfunc(pathname(x)); NOTE: f67a5830-2590-a14b-b399-958a8299e619 81 proc cas; 82 session.sessionID; 83 quit; NOTE: Active Session now MYSESSION. {MYSESSION:Sun Jun 13 14:28:33 2021=f67a5830-2590-a14b-b399-958a8299e619} NOTE: PROCEDURE CAS used (Total process time): So you can see that PATHNAME is returning the UUID of the CAS session, not the caslib. Right-clicking on the library in SAS Studio and choosing Properties will show the same results.  Unless there are caslib librefs in your SAS session that were automatically assigned by the SAS Administrator, you would have to have assigned them in your code. Librefs assigned with the CASLIB _ALL_ ASSIGN; statement will automatically match the caslib name. And for librefs individually assigned with LIBNAME statements, the association should be self-evident in the code...  May the SAS be with you! Mark       ... View more

Hi Carus,   Thank you for the quick reply! Unfortunately, I do not have access to the server, so I'm afraid that I cannot use that option. ... View more

I see, thank you for the help!  ... View more

VA utilizes SAS Viya actions behind the scenes. The one responsible for detecting communities is named Hypergroup. The related documentation is here and should contain additional information and examples. This action is also utilized for determining the graph layout for the non-geographical view.   Hope this helps! Regards, Falko ... View more

Hi @joeFurbee,   Thank you for the quick reply!   Based on your suggestions, I've tested the following fit-settings:   dc_model.fit(data = train, mini_batch_size = 32, max_epochs = 6, lr = 0.001, log_level = 2) Using max_epochs = 6 and mini_batch_size = 32, the fit runs without any errors.   dc_model.fit(data = train, mini_batch_size = 8, max_epochs = 6, lr = 0.001, log_level = 2) The fit also runs without any errors using max_epochs = 6 and mini_batch_size = 8.   So far, everything seems to point towards the possibility that the SAS Viya-environment I'm using is unable to handle things beyond a certain load, thereby resulting in the error (that's the feeling I'm getting at least).   Thank you,   Jian     ... View more