Business Context
An IT department maps server dependencies. Some servers (like gateways) belong to multiple subsystems. The goal is to identify these 'bridge' servers (Overlap) and analyze the network at different zoom levels (Resolution).
Data Preparation
Creation of a network with a central node connecting two distinct clusters and self-links representing internal processes.
Copied!
| 1 | DATA mycas.server_links; INPUT src $ dst $ weight; DATALINES; |
| 2 | Srv1 Srv2 5 |
| 3 | Srv2 Srv3 5 |
| 4 | Srv1 Srv3 5 |
| 5 | Gate1 Srv3 2 |
| 6 | Gate1 Srv4 2 |
| 7 | Srv4 Srv5 5 |
| 8 | Srv5 Srv6 5 |
| 9 | Srv4 Srv6 5 |
| 10 | Srv1 Srv1 1 |
| 11 | ; RUN; |
Étapes de réalisation
1
Run detection with Overlap calculation and multiple resolutions.
Copied!
| 1 | PROC CAS; |
| 2 | network.community / |
| 3 | links={name="server_links"} |
| 4 | selfLinks=TRUE |
| 5 | resolutionList={0.5, 1.0, 1.5} |
| 6 | outLevel={name="resolution_levels", replace=true} |
| 7 | outOverlap={name="server_overlap", replace=true}; |
| 8 | QUIT; |
2
Inspect bridge nodes.
Copied!
| 1 | PROC PRINT DATA=mycas.server_overlap; RUN; |
Expected Result
The `server_overlap` table should show 'Gate1' having membership intensity in both the 'Srv1-3' cluster and the 'Srv4-6' cluster. The `resolution_levels` table should show different community structures for the requested resolution values (0.5, 1.0, 1.5).