Gecko [ fernandoquevedodop.com ]

Name	Size	Permission
LicBSD.txt	1.76 KB	-rw-r--r--
Licbzip2.txt	1.7 KB	-rw-r--r--
Licgd.txt	2.2 KB	-rw-r--r--
Licpcre.txt	1.02 KB	-rw-r--r--
Licpng.txt	2.36 KB	-rw-r--r--
Licunzip.txt	1.29 KB	-rw-r--r--
Liczlib.txt	1.68 KB	-rw-r--r--
Readme.html	3.53 KB	-rw-r--r--
acknow.html	8.21 KB	-rw-r--r--
alias.html	10.18 KB	-rw-r--r--
analogo.gif	567 B	-rw-r--r--
anlgdocs.css	147 B	-rw-r--r--
args.html	9.26 KB	-rw-r--r--
bara8.gif	50 B	-rw-r--r--
barb1.gif	67 B	-rw-r--r--
barb32.gif	165 B	-rw-r--r--
barb8.gif	100 B	-rw-r--r--
barc8.gif	145 B	-rw-r--r--
bard8.gif	76 B	-rw-r--r--
bare8.gif	142 B	-rw-r--r--
barf8.gif	76 B	-rw-r--r--
barg8.gif	175 B	-rw-r--r--
barh8.gif	194 B	-rw-r--r--
bari8.gif	103 B	-rw-r--r--
barj8.gif	185 B	-rw-r--r--
basiccmd.html	7.88 KB	-rw-r--r--
cache.html	9.51 KB	-rw-r--r--
compout.html	6.14 KB	-rw-r--r--
custom.html	2.72 KB	-rw-r--r--
debug.html	6.93 KB	-rw-r--r--
defns.html	7.26 KB	-rw-r--r--
dns.html	6.36 KB	-rw-r--r--
domfile.html	4.16 KB	-rw-r--r--
errors.html	16.22 KB	-rw-r--r--
faq.html	49.66 KB	-rw-r--r--
favicon.ico	1.05 KB	-rw-r--r--
form.html	23.35 KB	-rw-r--r--
helpers.html	1.74 KB	-rw-r--r--
hierreps.html	7.86 KB	-rw-r--r--
include.html	13.8 KB	-rw-r--r--
indx.html	37.54 KB	-rw-r--r--
logfile.html	17.3 KB	-rw-r--r--
logfmt.html	17.78 KB	-rw-r--r--
lowmem.html	3.91 KB	-rw-r--r--
mailing.html	8 KB	-rw-r--r--
map.html	3.22 KB	-rw-r--r--
meaning.html	1.82 KB	-rw-r--r--
othreps.html	17.35 KB	-rw-r--r--
output.html	22.66 KB	-rw-r--r--
quickref.html	40.12 KB	-rw-r--r--
reports.html	15.05 KB	-rw-r--r--
start.html	2.15 KB	-rw-r--r--
startmac.html	3.66 KB	-rw-r--r--
startpc.html	4.29 KB	-rw-r--r--
startux.html	5.67 KB	-rw-r--r--
syntax.html	7.1 KB	-rw-r--r--
timereps.html	7.53 KB	-rw-r--r--
update.html	25.37 KB	-rw-r--r--
wasnew1.html	5.5 KB	-rw-r--r--
wasnew2.html	7.79 KB	-rw-r--r--
wasnew3.html	12.48 KB	-rw-r--r--
wasnew4.html	10.67 KB	-rw-r--r--
wasnew5.html	16.28 KB	-rw-r--r--
webworks.html	13.78 KB	-rw-r--r--
whatsnew.html	4.32 KB	-rw-r--r--

Code Editor : hierreps.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<link rel=stylesheet type="text/css" href="anlgdocs.css">
<LINK REL="SHORTCUT ICON" HREF="favicon.ico">
<title>Readme for analog -- hierarchical reports</title>
</head>

<body>
[ <a href="Readme.html">Top</a> | <a href="custom.html">Up</a> |
<a href="othreps.html">Prev</a> | <a href="domfile.html">Next</a> |
<a href="map.html">Map</a> | <a href="indx.html">Index</a> ]
<h1><img src="analogo.gif" alt=""> Analog 6.0:
Hierarchical reports</h1>
<hr size=2 noshade>

Some of the non-time reports have a hierarchical (or tree) structure:
so, for example, each domain in the Domain Report can have subdomains
listed under it, which in turn can have sub-subdomains, and so on. This
section describes commands for managing hierarchical reports.

First, you need to be able to control what gets listed in the reports.
For this you need to use the <kbd>SUB</kbd> family of commands. So, for
example, the command
<kbd>
SUBDIR /~sret1/*
</kbd>
would ensure that the Directory Report would not only contain an entry for
the sum of my files, but also one for each of my subdirectories, something
like this:
<pre>
29,111: /~sret1/
10,234: /~sret1/analog/
 5,179: /~sret1/backgammon/
11,908: /~steve/
</pre>
You can have more than one <kbd>*</kbd> in the command. For example
<pre>
SUBDOMAIN *.*
</pre>
would list the whole Domain Report two levels deep.

If you specify a <kbd>SUB</kbd> command, all the intermediate levels are
included automatically. So, for example, after
<pre>
SUBDOMAIN statslab.cam.ac.uk
</pre>
<kbd>cam.ac.uk</kbd> and <kbd>ac.uk</kbd> will be included in the Domain
Report too, and after <kbd>*.*.ac.uk</kbd>, <kbd>*.ac.uk</kbd> will be
included.

Here are examples of the other four <kbd>SUB</kbd> commands:
<pre>
SUBTYPE *.gz # in the File Type Report
SUBBROW */* # e.g. Netscape/4 in the Browser Summary
SUBBROW Netscape/*.* # add minor version numbers for Netscape
REFDIR http://search.yahoo.com/* # Referring Site Report
SUBORG *.aol.com # Organisation Report
SUBORG *.*.com # Break down all .com's
</pre>

<a name="subdomtwoarg">The</a> <kbd>SUBDOMAIN</kbd> command (but none of the
others) can include a second
argument describing the subdomain. For example
<pre>
SUBDOMAIN cam.ac.uk 'University of Cambridge'
</pre>
Then that subdomain will be listed with its translation in the Domain Report.
You can also have numerical subdomains: e.g.,
<pre>
SUBDOMAIN 131.111 'University of Cambridge'
</pre>
If you sort the subdomains alphabetically, the numerical ones will also be
sorted alphabetically, not numerically. I don't think this will cause any
problems.

One other use for the <kbd>SUBDIR</kbd> command is if you have used the
second argument to the <kbd><a href="logfile.html#secondarg">LOGFILE</a></kbd>
command. Suppose you have translated files like <kbd>/index.html</kbd> into
<kbd>http://www.mycompany.com/index.html</kbd>. Then the command
<pre>
SUBDIR http://* # or
SUBDIR http://*/*
</pre>
would be appropriate to make the Directory Report look right.

<hr size=1 noshade>
<a name="SUBFLOOR">The</a> <a name="SUBSORTBY">lower</a> levels of each report
have <kbd>FLOOR</kbd> and <kbd>SORTBY</kbd>
commands which work exactly the same as those we have
<a href="othreps.html#SORTBY">already seen</a> for the
top level. These commands are <kbd>SUBDIRFLOOR</kbd>, <kbd>SUBDOMFLOOR</kbd>,
<kbd>SUBORGFLOOR</kbd>,
<kbd>SUBTYPEFLOOR</kbd>, <kbd>SUBBROWFLOOR</kbd> and <kbd>REFDIRFLOOR</kbd>;
and <kbd>SUBDIRSORTBY</kbd>, <kbd>SUBDOMSORTBY</kbd>, <kbd>SUBORGSORTBY</kbd>,
<kbd>SUBTYPESORTBY</kbd>, <kbd>SUBBROWSORTBY</kbd> and <kbd>REFDIRSORTBY</kbd>.

A sub-item is listed in a hierarchical report only if it is above the
sub-<kbd>FLOOR</kbd>, and it is included with a <kbd>SUB</kbd> command,
and it is not excluded because of an
<a href="include.html#outputexcludes"><kbd>INCLUDE</kbd> or
<kbd>EXCLUDE</kbd></a> command, and its immediate parent is listed. For
example, specifying
<pre>
SUBDIR /*/*/
SUBDIRFLOOR -3r
SUBDIRSORTBY REQUESTS
</pre>
would list the three subdirectories with most requests under each directory.
<kbd>SUBDIRFLOOR 1:r</kbd> would have listed any subdirectory with at least
1% of the maximum number of requests of any top level directory.

<a name="ARGSFLOOR">The</a> <a name="ARGSSORTBY">three</a> file reports
(Request Report, Redirection Report and Failure
Report) and the three referrer reports (Referrer Report, Redirected Referrer
Report and Failed Referrer Report) are not fully hierarchical, but they do
list <a href="args.html">search arguments</a> together under the file to which
they refer (provided that the arguments have been read in: see the
<kbd><a href="args.html#ARGSINCLUDE">ARGSINCLUDE</a></kbd> command).
So they have
similar sub-<kbd>FLOOR</kbd> and sub-<kbd>SORTBY</kbd> commands, namely
<kbd>REQARGSFLOOR</kbd>, <kbd>REDIRARGSFLOOR</kbd>, <kbd>FAILARGSFLOOR</kbd>,
<kbd>REFARGSFLOOR</kbd>, <kbd>REDIRREFARGSFLOOR</kbd> and
<kbd>FAILREFARGSFLOOR</kbd>; and <kbd>REQARGSSORTBY</kbd>,
<kbd>REDIRARGSSORTBY</kbd>, <kbd>FAILARGSSORTBY</kbd>,
<kbd>REFARGSSORTBY</kbd>, <kbd>REDIRREFARGSSORTBY</kbd> and
<kbd>FAILREFARGSSORTBY</kbd>. The same
applies to the Operating System Report with its subdivisions of operating
systems: it has <kbd>SUBOSFLOOR</kbd> and <kbd>SUBOSSORTBY</kbd>.
<hr size=1 noshade>
The lower levels of a hierarchical report temporarily interrupt the top
level, and even though they are indented, this can sometimes make it look as
if the report is out of order. If you have a lot of sub-items, for example in
the Referrer Report if there are a lot of search arguments, then including the
<a href="othreps.html#othCOLS"><kbd>N</kbd> column</a> can help to make it
clearer again.
<hr size=1 noshade>
<a name="CHARTEXPAND">Sometimes one item</a> in the
<a href="othreps.html#CHART">pie chart</a> takes up most of the pie. In this
case, you can elect to plot its sub-items on the chart instead, by using the
<kbd>*CHARTEXPAND</kbd> family of commands. For example
<pre>
OSCHARTEXPAND Windows
</pre>
will use Windows 98, Windows NT etc. as wedges in the pie chart, instead of
accumulating all the Windows versions together in one wedge.
The complete list of these commands is
<kbd>DIRCHARTEXPAND</kbd>, <kbd>DOMCHARTEXPAND</kbd>,
<kbd>ORGCHARTEXPAND</kbd>, <kbd>TYPECHARTEXPAND</kbd>,
<kbd>BROWCHARTEXPAND</kbd>, <kbd>OSCHARTEXPAND</kbd>,
<kbd>REQCHARTEXPAND</kbd>, <kbd>REDIRCHARTEXPAND</kbd>,
<kbd>FAILCHARTEXPAND</kbd>, <kbd>REFCHARTEXPAND</kbd>,
<kbd>REDIRREFCHARTEXPAND</kbd>, <kbd>FAILREFCHARTEXPAND</kbd> and
<kbd>REFSITECHARTEXPAND</kbd>. The <kbd>CHARTEXPAND</kbd> commands can take a
comma-separated list (without spaces) as an argument, but not wildcards.

Just as for top-level items, sub-items will only be included if they are listed
in the main table for the report. And so if an item does not have any
sub-items listed, it will not be expanded, even if you asked for it to be.
This means that you may need to use the appropriate
<a href="hierreps.html"><kbd>SUB</kbd></a> commands or
<a href="#SUBFLOOR"><kbd>SUBFLOOR</kbd></a> commands to make sure that the
sub-items do get listed. For example
<pre>
SUBDOMAIN *.com
DOMCHARTEXPAND .com
</pre>

Also, sub-items will only appear on the pie chart if they are large enough to
get on in their own right. Note that if an item has any sub-items listed, and
is expanded, then the item itself will no longer appear on the chart, only
any sub-items which are large enough.

<hr size=2 noshade>
Go to the <a href="http://www.analog.cx/">analog home page</a>.

<address>Stephen Turner
 19 December 2004</address>
Need help with analog? <a href="mailing.html">Use the analog-help
mailing list</a>.

[ <a href="Readme.html">Top</a> | <a href="custom.html">Up</a> |
<a href="othreps.html">Prev</a> | <a href="domfile.html">Next</a> |
<a href="map.html">Map</a> | <a href="indx.html">Index</a> ]
</body> </html>

${this.title}

Code Editor : hierreps.html