U td5`@sRdZddlmZddlmZmZdZGdddeeZGdddeZd d Z d S) a Drawing routines to draw graphs. This module contains routines to draw graphs on: - Cairo surfaces (L{DefaultGraphDrawer}) - Matplotlib axes (L{MatplotlibGraphDrawer}) It also contains routines to send an igraph graph directly to (U{Cytoscape}) using the (U{CytoscapeRPC plugin}), see L{CytoscapeGraphDrawer}. L{CytoscapeGraphDrawer} can also fetch the current network from Cytoscape and convert it to igraph format. )warn)AbstractGraphDrawerAbstractXMLRPCDrawer)CytoscapeGraphDrawer__plot__csBeZdZdZdfdd ZdddZdd d Zed dZZ S)ra=Graph drawer that sends/receives graphs to/from Cytoscape using CytoscapeRPC. This graph drawer cooperates with U{Cytoscape} using U{CytoscapeRPC}. You need to install the CytoscapeRPC plugin first and start the XML-RPC server on a given port (port 9000 by default) from the appropriate Plugins submenu in Cytoscape. Graph, vertex and edge attributes are transferred to Cytoscape whenever possible (i.e. when a suitable mapping exists between a Python type and a Cytoscape type). If there is no suitable Cytoscape type for a Python type, the drawer will use a string attribute on the Cytoscape side and invoke C{str()} on the Python attributes. If an attribute to be created on the Cytoscape side already exists with a different type, an underscore will be appended to the attribute name to resolve the type conflict. You can use the C{network_id} attribute of this class to figure out the network ID of the last graph drawn with this drawer. http://localhost:9000/Cytoscapecst|dd|_dS)zfConstructs a Cytoscape graph drawer using the XML-RPC interface of Cytoscape at the given URL.Z CytoscapeN)super__init__ network_id)selfurl __class__M/home/sam/Atlas/atlas_env/lib/python3.8/site-packages/igraph/drawing/graph.pyr /szCytoscapeGraphDrawer.__init__Network from igraphTc OsFddlm}|rtdt|j}|s^z||d}Wqh|k rZtd||}YqhXn ||}||_d|kr|d} t| tr|j | } nt t | } dd| D} | || ggg} |D],\} } | d| | | d | | q||| d| d d g||g|d} d |kr||d |}d | d }|j||fdd|| d| d|j|| ft tt |n ||t|}|D]}|||g\}}|d}|dkrqz*||kr|||kr|d7}qWn|k r0YnX|||||iqt|}| D]h}||j |\}}t!ddt| |D}||kr|"||kr|d7}q|#|||dq\t|$}|%D]f}||j&|\}}t!ddt| |D}||kr0|'||kr0|d7}q |(|||qdS)a,Sends the given graph to Cytoscape as a new network. @param name: the name of the network in Cytoscape. @param create_view: whether to create a view for the network in Cytoscape.The default is C{True}. @keyword node_ids: specifies the identifiers of the nodes to be used in Cytoscape. This must either be the name of a vertex attribute or a list specifying the identifiers, one for each node in the graph. The default is C{None}, which simply uses the vertex index for each vertex.r)FaultOPositional arguments to plot functions are ignored and will be deprecated soon.FznCytoscapeRPC too old, cannot create network without view. Consider upgrading CytoscapeRPC to use this feature.node_idscSsg|] }t|qSr)str).0 identifierrrr asz-CytoscapeGraphDrawer.draw..unknownlayoutdg?T)Zkeep_aspect_ratiog@N_css|]}|ddk r|VqdSrNrrpairrrr s z,CytoscapeGraphDrawer.draw..css|]}|ddk r|VqdSrrrrrrr!s )) xmlrpc.clientrrDeprecationWarningserviceZ createNetworkr isinstancervslistrangeZvcountZ createNodesZ get_edgelistappendZ createEdgesZecountZ is_directedZ ensure_layoutZfit_into translateZsetNodesPositionszipZperformDefaultLayoutsetZgetNetworkAttributeNames attributesinfer_cytoscape_typeZgetNetworkAttributeTypeZaddNetworkAttributesgetNodeAttributeNamesZvertex_attributesdictZgetNodeAttributeTypeZaddNodeAttributesgetEdgeAttributeNamesZedge_attributesesZgetEdgeAttributeTypeZaddEdgeAttributes)r graphnameZ create_viewargskwdsrcyr rZ edgelistsZv1Zv2Zedge_idsrsizeZ attr_namesattrZcy_typevaluevaluesrrrdraw5s                   zCytoscapeGraphDrawer.drawNFcsvddlm}|j}|}d|kr0|dd}ttt|ddd}|dkr\tddkrn| }nLfd d | D}|st d nt |d krt d |d}||}||} t |t | } } ||} |} i}| D]}|dkr|sq|||}dd t|D}||dd t||D}dg| }t||D]\}}|||<q^|||<q|}i}|D]}|dkr|sq||| }dd t|D}||dd t| |D}dg| }t||D]\}}|||<q|||<qtddt|D}~g}| D],}|}|||d||dfq2~ || ||| ||dS)agFetches the network with the given name from Cytoscape. When fetching networks from Cytoscape, the C{canonicalName} attributes of vertices and edges are not converted by default. Use the C{keep_canonical_names} parameter to retrieve these attributes as well. @param name: the name of the network in Cytoscape. @param directed: whether the network is directed. @param keep_canonical_names: whether to keep the C{canonicalName} vertex/edge attributes that are added automatically by Cytoscape @return: an appropriately constructed igraph L{Graph}.r)Graph .N)rz8CytoscapeGraphDrawer requires Cytoscape-RPC 1.3 or newercsg|]\}}|kr|qSrrrkvr4rrrsz.CytoscapeGraphDrawer.fetch..zno such network: %rrz*more than one network exists with name: %rZ canonicalNamecSsg|]\}}|r|qSrrridxokrrrrscSsg|]\}}|r|qSrrrr4rHrrrrscSsg|]\}}|r|qSrrrFrrrrscSsg|]\}}|r|qSrrrIrrrrscss|]\}}||fVqdSNrrBrrrr!sz-CytoscapeGraphDrawer.fetch..)directed graph_attrs vertex_attrs edge_attrs)Zigraphr=r$versionsplittuplemapintNotImplementedErrorZ getNetworkIDZgetNetworkListitems ValueErrorlenZgetNodesZgetEdgesZgetNetworkAttributesr/ZnodesHaveAttribute enumerateZgetNodesAttributesr+r1ZedgesHaveAttributeZgetEdgesAttributesr0r))r r4rKZkeep_canonical_namesr=r7rOr ZverticesedgesnmrLZvertex_attr_namesrM attr_nameZhas_attrfilteredr;attrsrGr:Zedge_attr_namesrNZvertex_name_indexZ edge_listedgepartsrrErfetchs               "zCytoscapeGraphDrawer.fetchcCsndd|D}tdd|Dr(d|fStdd|DrBd|fStdd|Dr\d |fSd d d|DfS) aReturns a Cytoscape type that can be used to represent all the values in C{values} and an appropriately converted copy of C{values} that is suitable for an XML-RPC call. Note that the string type in Cytoscape is used as a catch-all type; if no other type fits, attribute values will be converted to string and then posted to Cytoscape. C{None} entries are allowed in C{values}, they will be ignored on the Cytoscape side. cSsg|]}|dk rt|qSrJ)typerr:rrrrsz=CytoscapeGraphDrawer.infer_cytoscape_type..css|]}|tkVqdSrJ)boolrtrrrr!sz.ZBOOLEANcss|]}t|ttfVqdSrJ) issubclassrSrerrrr!sZINTEGERcss|]}t|tVqdSrJ)rgfloatrerrrr!sZFLOATINGSTRINGcSs"g|]}t|tst|n|qSr)r%rrcrrrrs)all)r;typesrrrr. s z)CytoscapeGraphDrawer.infer_cytoscape_type)r)rT)NFF) __name__ __module__ __qualname____doc__r r<ra staticmethodr. __classcell__rrr rrs  t arcs*eZdZdZdfdd ZddZZS)GephiGraphStreamingDraweraGraph drawer that sends a graph to a file-like object (e.g., socket, URL connection, file) using the Gephi graph streaming format. The Gephi graph streaming format is a simple JSON-based format that can be used to post mutations to a graph (i.e. node and edge additions, removals and updates) to a remote component. For instance, one can open up Gephi (U{http://www.gephi.org}), install the Gephi graph streaming plugin and then send a graph from igraph straight into the Gephi window by using C{GephiGraphStreamingDrawer} with the appropriate URL where Gephi is listening. The C{connection} property exposes the L{GephiConnection} that the drawer uses. The drawer also has a property called C{streamer} which exposes the underlying L{GephiGraphStreamer} that is responsible for generating the JSON objects, encoding them and writing them to a file-like object. If you want to customize the encoding process, this is the object where you can tweak things to your taste. Ncs6tddlm}m}|p&||||_||_dS)aBConstructs a Gephi graph streaming drawer that will post graphs to the given Gephi connection. If C{conn} is C{None}, the remaining arguments of the constructor are forwarded intact to the constructor of L{GephiConnection} in order to create a connection. This means that any of the following are valid: - C{GephiGraphStreamingDrawer()} will construct a drawer that connects to workspace 0 of the local Gephi instance on port 8080. - C{GephiGraphStreamingDrawer(workspace=2)} will connect to workspace 2 of the local Gephi instance on port 8080. - C{GephiGraphStreamingDrawer(port=1234)} will connect to workspace 0 of the local Gephi instance on port 1234. - C{GephiGraphStreamingDrawer(host="remote", port=1234, workspace=7)} will connect to workspace 7 of the Gephi instance on host C{remote}, port 1234. - C{GephiGraphStreamingDrawer(url="http://remote:1234/workspace7)} is the same as above, but with an explicit URL. r)GephiGraphStreamerGephiConnectionN)rr Zigraph.remote.gephirsrt connectionstreamer)r connr5r6rsrtr rrr 7s z"GephiGraphStreamingDrawer.__init__cOs,|rtdt|jj||j|dddS)a9Draws (i.e. sends) the given graph to the destination of the drawer using the Gephi graph streaming API. The following keyword arguments are allowed: - C{encoder} lets one specify an instance of C{json.JSONEncoder} that will be used to encode the JSON objects. rencoder)rxN)rr#rvpostruget)r r3r5r6rrrr<Us zGephiGraphStreamingDrawer.draw)N)rlrmrnror r<rqrrr rrr$srrcOs:ddlm}|d||||}|j|f||dS)a$Plots the graph to the given Cairo context or matplotlib Axes. The visual style of vertices and edges can be modified at three places in the following order of precedence (lower indices override higher indices): 1. Keyword arguments of this function (or of L{plot()} which is passed intact to C{Graph.__plot__()}. 2. Vertex or edge attributes, specified later in the list of keyword arguments. 3. igraph-wide plotting defaults (see L{igraph.config.Configuration}) 4. Built-in defaults. E.g., if the C{vertex_size} keyword attribute is not present, but there exists a vertex attribute named C{size}, the sizes of the vertices will be specified by that attribute. Besides the usual self-explanatory plotting parameters (C{context}, C{bbox}, C{palette}), it accepts the following keyword arguments: - C{autocurve}: whether to use curves instead of straight lines for multiple edges on the graph plot. This argument may be C{True} or C{False}; when omitted, C{True} is assumed for graphs with less than 10.000 edges and C{False} otherwise. - C{drawer_factory}: a subclass of L{AbstractCairoGraphDrawer} which will be used to draw the graph. You may also provide a function here which takes two arguments: the Cairo context to draw on and a bounding box (an instance of L{BoundingBox}). If this keyword argument is missing, igraph will use the default graph drawer which should be suitable for most purposes. It is safe to omit this keyword argument unless you need to use a specific graph drawer. - C{keep_aspect_ratio}: whether to keep the aspect ratio of the layout that igraph calculates to place the nodes. C{True} means that the layout will be scaled proportionally to fit into the bounding box where the graph is to be drawn but the aspect ratio will be kept the same (potentially leaving empty space next to, below or above the graph). C{False} means that the layout will be scaled independently along the X and Y axis in order to fill the entire bounding box. The default is C{False}. - C{layout}: the layout to be used. If not an instance of L{Layout}, it will be passed to L{layout} to calculate the layout. Note that if you want a deterministic layout that does not change with every plot, you must either use a deterministic layout function (like L{GraphBase.layout_circle}) or calculate the layout in advance and pass a L{Layout} object here. - C{margin}: the top, right, bottom, left margins as a 4-tuple. If it has less than 4 elements or is a single float, the elements will be re-used until the length is at least 4. - C{mark_groups}: whether to highlight some of the vertex groups by colored polygons. This argument can be one of the following: - C{False}: no groups will be highlighted - C{True}: only valid if the object plotted is a L{VertexClustering} or L{VertexCover}. The vertex groups in the clutering or cover will be highlighted such that the i-th group will be colored by the i-th color from the current palette. If used when plotting a graph, it will throw an error. - A dict mapping tuples of vertex indices to color names. The given vertex groups will be highlighted by the given colors. - A list containing pairs or an iterable yielding pairs, where the first element of each pair is a list of vertex indices and the second element is a color. - A L{VertexClustering} or L{VertexCover} instance. The vertex groups in the clustering or cover will be highlighted such that the i-th group will be colored by the i-th color from the current palette. In place of lists of vertex indices, you may also use L{VertexSeq} instances. In place of color names, you may also use color indices into the current palette. C{None} as a color name will mean that the corresponding group is ignored. - C{vertex_size}: size of the vertices. The corresponding vertex attribute is called C{size}. The default is 10. Vertex sizes are measured in the unit of the Cairo context on which igraph is drawing. - C{vertex_color}: color of the vertices. The corresponding vertex attribute is C{color}, the default is red. Colors can be specified either by common X11 color names (see the source code of L{igraph.drawing.colors} for a list of known colors), by 3-tuples of floats (ranging between 0 and 255 for the R, G and B components), by CSS-style string specifications (C{#rrggbb}) or by integer color indices of the specified palette. - C{vertex_frame_color}: color of the frame (i.e. stroke) of the vertices. The corresponding vertex attribute is C{frame_color}, the default is black. See C{vertex_color} for the possible ways of specifying a color. - C{vertex_frame_width}: the width of the frame (i.e. stroke) of the vertices. The corresponding vertex attribute is C{frame_width}. The default is 1. Vertex frame widths are measured in the unit of the Cairo context on which igraph is drawing. - C{vertex_shape}: shape of the vertices. Alternatively it can be specified by the C{shape} vertex attribute. Possibilities are: C{square}, {circle}, {triangle}, {triangle-down} or C{hidden}. See the source code of L{igraph.drawing} for a list of alternative shape names that are also accepted and mapped to these. - C{vertex_label}: labels drawn next to the vertices. The corresponding vertex attribute is C{label}. - C{vertex_label_dist}: distance of the midpoint of the vertex label from the center of the corresponding vertex. The corresponding vertex attribute is C{label_dist}. - C{vertex_label_color}: color of the label. Corresponding vertex attribute: C{label_color}. See C{vertex_color} for color specification syntax. - C{vertex_label_size}: font size of the label, specified in the unit of the Cairo context on which we are drawing. Corresponding vertex attribute: C{label_size}. - C{vertex_label_angle}: the direction of the line connecting the midpoint of the vertex with the midpoint of the label. This can be used to position the labels relative to the vertices themselves in conjunction with C{vertex_label_dist}. Corresponding vertex attribute: C{label_angle}. The default is C{-math.pi/2}. - C{vertex_order}: drawing order of the vertices. This must be a list or tuple containing vertex indices; vertices are then drawn according to this order. - C{vertex_order_by}: an alternative way to specify the drawing order of the vertices; this attribute is interpreted as the name of a vertex attribute, and vertices are drawn such that those with a smaller attribute value are drawn first. You may also reverse the order by passing a tuple here; the first element of the tuple should be the name of the attribute, the second element specifies whether the order is reversed (C{True}, C{False}, C{"asc"} and C{"desc"} are accepted values). - C{edge_color}: color of the edges. The corresponding edge attribute is C{color}, the default is red. See C{vertex_color} for color specification syntax. - C{edge_curved}: whether the edges should be curved. Positive numbers correspond to edges curved in a counter-clockwise direction, negative numbers correspond to edges curved in a clockwise direction. Zero represents straight edges. C{True} is interpreted as 0.5, C{False} is interpreted as 0. The default is 0 which makes all the edges straight. - C{edge_width}: width of the edges in the default unit of the Cairo context on which we are drawing. The corresponding edge attribute is C{width}, the default is 1. - C{edge_arrow_size}: arrow size of the edges. The corresponding edge attribute is C{arrow_size}, the default is 1. - C{edge_arrow_width}: width of the arrowhead on the edge. The corresponding edge attribute is C{arrow_width}, the default is 1. - C{edge_order}: drawing order of the edges. This must be a list or tuple containing edge indices; edges are then drawn according to this order. - C{edge_order_by}: an alternative way to specify the drawing order of the edges; this attribute is interpreted as the name of an edge attribute, and edges are drawn such that those with a smaller attribute value are drawn first. You may also reverse the order by passing a tuple here; the first element of the tuple should be the name of the attribute, the second element specifies whether the order is reversed (C{True}, C{False}, C{"asc"} and C{"desc"} are accepted values). r)DrawerDirectoryZdrawer_factoryN)Zigraph.drawingr{popresolver<)r backendcontextr5r6r{Zdrawerrrrris@ rN) rowarningsrZigraph.drawing.baseclassesrr__all__rrrrrrrrs E