2215 questions found.

Page 34 / 45

Colors with this number of vertices, or fewer, are merged into other colors. Alias: minColourVertices. Minimum value: 1....
Read full answer See technical action

Communities with this number of vertices, or fewer, are merged into other communities. Minimum value: 1....
Read full answer See technical action

specifies the list of integers to indicate which inputs variable list columns belong to different name spaces....
Read full answer See technical action

specifies the approximate number of vertices desired in the nBody graph. If maxDepth is specified, nBody= is the maximum number of vertices desired. Default: 0. Minimum value: 1....
Read full answer See technical action

Small colors are merged into bigger colors until this number of colors remain. Alias: nColours. Minimum value: 1....
Read full answer See technical action

Small communities are merged into bigger communities until this number of communities remain. Minimum value: 1....
Read full answer See technical action

specifies that for all cells, the body nearest to the cells center of mass is to be identified. See the _NearestCenter_ column in the casOut table. Alias: nearestCentre. Default: FALSE....
Read full answer See technical action

specifies the maximum number of iterations the layout algorithms can perform. Alias: niterations. Default: 100. Range: 1–2000....
Read full answer See technical action

specifies that colors are not needed. Alias: noColour. Default: FALSE....
Read full answer See technical action

specifies that coordinates of the color structural graphs are not needed. _XCoord_, _YCoord_, ... etc. in the vertices3= table, and the _SourceX_, _TargetY_, ... etc. in the edges3= table are not needed. Default: FALSE....
Read full answer See technical action

specifies that coordinates of the community structural graphs are not needed. _XCoord_, _YCoord_, ... etc. in the vertices3= table, and the _SourceX_, _TargetY_, ... etc. in the edges3= table are not needed. Default: FALSE....
Read full answer See technical action

specifies that coordinates of the hypergroup graphs are not needed. Default: FALSE....
Read full answer See technical action

specifies during graph partitioning pendant nodes are not to be initially excluded in layouts. Determining layouts without pendants can result in better quality layouts, but it requires an extra layout with them put back in. Default: FALSE....
Read full answer See technical action

the default copyVars varlist are all columns that are not in the inputs, groupBy, weight, or frequency varlists- noVars indicates you want that default to be no columns. Default: FALSE....
Read full answer See technical action

specifies the number of shortest paths put into the ShortestPaths table. These are the shortest paths from vertex=, and if vertex2= is specified, from vertex2=. Alias: nSP. Default: 1000. Minimum value: 1....
Read full answer See technical action

specifies the number of threads to use on each machine in the server. By default, the server uses one thread for each CPU that is licensed to use SAS software. Range: 0–64....
Read full answer See technical action

specifies that the inputs varlist variables have numeric values, can be integer or real numbers. Alias: numLabels. Default: FALSE....
Read full answer See technical action

specifies the maximum number of threads any worker is allowed to run. Range: 0–64....
Read full answer See technical action

specifies that output tables will be created if and only if their name is specified. Default: FALSE....
Read full answer See technical action

specifies the way the nBody layout algorithm executes: unthreaded, threaded, threaded and gridded, or not at all. 0: do not use nBody layout. -1: nongridded nonthreaded nBody algorithm used. -2: nongridded nonthreaded synchronized update nBody algorithm used. >=1 nongridded threaded (parallel= threa...
Read full answer See technical action

specifies that for each graph, issue to the journal the number of vertices, edges and, if applicable, properties of the edges. Default: FALSE....
Read full answer See technical action

specifies the angle for centrality are to be in radians rather than degrees. Default: FALSE....
Read full answer See technical action

specifies that the vertices5= and edges5= tables should contain records only for vertices that are reachable from vertex= . Default: FALSE....
Read full answer See technical action

specifies the input table was produced by a previous Hypergroup run as an output Edges table. Reading this is faster. Default: FALSE....
Read full answer See technical action

specifies whether stress, closeness, and betweenness centrality are scaled or not and, for these centralities, whether those of the most central vertices have values are at or near 1, or at or near 0. CENTRAL0 specifies stress, closeness, and betweenness centralities are to be scaled so that the mos...
Read full answer See technical action

specifies the coordinates are to be scaled so they lie within frame as per width= length= and height=, also governed by margin=. Default: FALSE....
Read full answer See technical action

specifies the type of separator graph partitioning uses. EDGES specifies the graph partition separator is edges. Alias: ARCS. HYBRID specifies the graph partition separator is vertices at some stages, and edges at others. VERTICES specifies the graph partition separator is vertices. Alias: NODES....
Read full answer See technical action

specifies the output table containing shortest paths for Analytics of Vertices based upon Vertex= and Vertex2=, if specified. For more information about specifying the shortestPaths parameter, see the common casouttable parameter....
Read full answer See technical action

specifies when the graph is directed that vertex=, vertexNumber=, or vertexNumeric= is the start of shortest paths, not their destination. Default: FALSE....
Read full answer See technical action

specifies to sort the bodies within a bodyCell by their importances. Alias: sortImportances. Default: FALSE....
Read full answer See technical action

If there are weights or frequencies, the i-th weight and frequency is associated with the edge originating at the i-th inputs variable value. If sourcePinned is not specified, the i-th weight and frequency is associated with the edge directed toward the (i+1)-th inputs variable value. Default: FALSE...
Read full answer See technical action

specifies that the data has standardized labels format, i.e. inputs varlist variables have integer values 0 1 2..., or 1 2 3.... Alias: stdLabels. Default: FALSE....
Read full answer See technical action

Start from Community Structural Graph, adding vertices and edges, to get entire graph layout. Default: FALSE....
Read full answer See technical action

specifies which type of structural graphs are needed. BOTH specifies that both the color and community structural graphs are needed. COLOUR specifies that the colour structural graph is needed. Alias: COLOR. COMMUNITY specifies that the community structural graph is needed. NONE specifies that no st...
Read full answer See technical action

specifies the table containing input data. For more information about specifying the table parameter, see the common castable parameter....
Read full answer See technical action

specifies the layout algorithms are to determine coordinates for vertices in 3-dimensions. Default: FALSE....
Read full answer See technical action

specifies the (0,0) or (0,0,0) point of the frame is at the top left rather than the bottom left. Needed sometimes so 0 degrees is vertically upwards. Default: FALSE....
Read full answer See technical action

When reading a table that was previously a Edges= output table, read AllGraphs coordinates rather than redetermine them. Default: FALSE....
Read full answer See technical action

When reading a table that was previously a Edges= output table, read colors rather than redetermine them. Alias: useColours. Default: FALSE....
Read full answer See technical action

When reading a table that was previously a Edges= output table, read communities rather than redetermine them. Alias: useComms. Default: FALSE....
Read full answer See technical action

When reading a table that was previously a Edges= output table, read coordinates rather than redetermine a layout. Default: FALSE....
Read full answer See technical action

When reading a table that was previously a Edges= output table, read vertice sizes rather than reading a verticesIn= table. Alias: useVSizes. Default: FALSE....
Read full answer See technical action

specifies the vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Alias: vertex1....
Read full answer See technical action

specifies the second vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables....
Read full answer See technical action

specifies the nameSpace of the second vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Aliases: v2ns, vns2. Default: -1. Minimum value: 0....
Read full answer See technical action

specifies the when standardizedLabels is specified, vertex2Number specifies the second vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Alias: vertexNumber2. Minimum value: 0....
Read full answer See technical action

when numericLabels is specified, vertex2Numeric specifies the second vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Alias: vertexNumeric2....
Read full answer See technical action

specifies that Analytics of Vertices are to be performed. Results will be put into the vertices5= and edges5= tables. Default: FALSE....
Read full answer See technical action

specifies the nameSpace of the vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Aliases: vns, v1ns, vns1. Default: -1. Minimum value: 0....
Read full answer See technical action

when standardizedLabels is specified, vertexNumber specifies the vertex that Analytics of Vertices are to be performed upon. Results will be put into the vertices5= and edges5= tables. Aliases: vertex1Number, vertexNumber1. Minimum value: 0....
Read full answer See technical action
Copyright © WeAreCAS 2014-2026
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. WeAreCAS is an independent community site and is not affiliated with SAS Institute Inc.