comment on

This also currently lives on GitHub at https://github.com/PDLPorters/pdl/blob/master/Example/doc-pp. It helps me see at a glance what PP parameters get data from each other, but the principle should be widely applicable:

use strict;
use warnings;
use PDL::PP;
use Graph;
use GraphViz2;

my $g = Graph->new; # should really be hypergraph but GraphViz2 not do
+ yet
for my $r (@{$PDL::PP::deftbl}) {
  for my $t (@{$r->{targets}}) {
    $g->add_edge($t, $_) for map s/_//gr, @{$r->{conditions}||[]};
  }
}
my ($fmt) = $ARGV[0] =~ /\.([^.]+)$/;
$g->set_graph_attribute(graphviz=>{graph=>{rankdir=>'LR'}});
GraphViz2->from_graph($g)->run(format=>$fmt,output_file=>$ARGV[0]);

=head1 NAME

doc-pp - Generate graph of pp_def key dependencies with graphviz

=head1 SYNOPSIS

  doc-pp deps.svg

=head1 DESCRIPTION

Uses L<Graph> and L<GraphViz2> to visualise the dependencies between
keys in L<PDL::PP/pp_def>.
[download]

In reply to Generate graphviz visualisation of interrelationships between variables using Graph and GraphViz2 by etj

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks