Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gv2gxl(1) [centos man page]

GXL2GV,GV2GXL(1)					      General Commands Manual						  GXL2GV,GV2GXL(1)

NAME
gxl2gv,gv2gxl - GXL-GV converters SYNOPSIS
gxl2gv [ -gd? ] [ -ooutfile ] [ files ] gv2gxl [ -gd? ] [ -ooutfile ] [ files ] DESCRIPTION
gxl2gv converts between graphs represented in GXL and in the GV language. Unless a conversion type is specified using a flag, gxl2gv will deduce the type of conversion from the suffix of the input file, a ".gv" suffix causing a conversion from GV to GXL, and a ".gxl" suffix causing a conversion from GXL to GV. If no suffix is available, e.g. when the input is from a pipe, and no flags are used then gxl2gv assumes the type of the input file from its executable name so that gxl2gv converts from GXL to GV, and gv2gxl converts from GV to GXL. GXL supports a much richer graph model than GV. gxl2gv will attempt to map GXL constructs into the analogous GV construct when this is pos- sible. If not, the GXL information is stored as an attribute. The intention is that applying gxl2gv|gv2gxl is semantically equivalent to the identity operator. OPTIONS
The following options are supported: -g The command name and input file extensions are ignored, the input is taken as a GV file and a GXL file is generated. -d The command name and input file extensions are ignored, the input is taken as a GXL file and a GV file is generated. -? Prints usage information and exits. -o outfile If specified, the output will be written into the file outfile. Otherwise, output is written to standard out. OPERANDS
The following operand is supported: files Names of files containing 1 or more graphs in GXL or GV. If no files operand is specified, the standard input will be used. RETURN CODES
Both gxl2gv and gv2gxl return 0 if there were no problems during conversion; and non-zero if any error occurred. BUGS
gxl2gv will only convert in one direction even if given multiple files with varying suffixes. The conversion can only handle one graph per GXL file. There are some GXL constructs which gxl2gv cannot handle. AUTHORS
Krishnam Pericherla <kp@research.att.com> Emden R. Gansner <erg@research.att.com> SEE ALSO
dot(1), libgraph(3), libagraph(3), neato(1), twopi(1) 20 December 2002 GXL2GV,GV2GXL(1)

Check Out this Related Man Page

BCOMPS(1)						      General Commands Manual							 BCOMPS(1)

NAME
bcomps - biconnected components filter for graphs SYNOPSIS
bcomps [ -stvx? ] [ -ooutfile ] [ files ] DESCRIPTION
bcomps decomposes graphs into their biconnected components, printing the components to standard output. OPTIONS
The following options are supported: -s No output graph is printed. Implies the -v flag. -t Print the underlying block-cutvertex tree. -x Each biconnected component is printed as a separate root graph. -v Prints number of blocks and cutvertices. -o outfile If specified, each root graph will be written to a different file with the names derived from outfile. In particular, if both -o and -x flags are used, then each block is written to a different file. If outfile does not have a suffix, the nth block of the ith graph is written to outfile_n_i. However, the 0th block of the 0th graph is written to outfile. If outfile has a suffix, i.e., has the form base.sfx, then the files will have the same name as above, except appended with .sfx. The block-cutvertex tree of ith graph is written to outfile_n_T, with an appended suffix if specified. By default, each input graph is printed, with each block given as a subgraph whose name is a concatenation of the name of the input graph, the string "_bcc_" and the number of the block. OPERANDS
The following operand is supported: files Names of files containing 1 or more graphs in dot format. If no files operand is specified, the standard input will be used. RETURN CODES
bcomps returns 0 if all the input graphs are biconnected; and non-zero if any graph has multiple blocks, or any error occurred. BUGS
It is possible, though unlikely, that the names used for connected components and their subgraphs may conflict with existing subgraph names. AUTHORS
Emden R. Gansner <erg@research.att.com> SEE ALSO
ccomps(1), gc(1), dot(1), gvpr(1), gvcolor(1), acyclic(1), sccmap(1), tred(1), libgraph(3) 18 November 2003 BCOMPS(1)
Man Page