Sophie

Sophie

distrib > Mandriva > 2010.0 > i586 > media > contrib-release > by-pkgid > ed05dc5f357c49fdded780f52b150dce > files > 17

ploticus-2.41-2mdv2010.0.i586.rpm

<html>
<head>
<!-- This file has been generated by unroff 1.0, 03/11/09 12:56:12. -->
<!-- Do not edit! -->
<STYLE TYPE="text/css">
<!--
        A:link{text-decoration:none}
        A:visited{text-decoration:none}
        A:active{text-decoration:none}
        OL,UL,P,BODY,TD,TR,TH,FORM { font-family: arial,helvetica,sans-serif;; font-size:small; color: #333333; }

        H1 { font-size: x-large; font-family: arial,helvetica,sans-serif; }
        H2 { font-size: large; font-family: arial,helvetica,sans-serif; }
        H3 { font-size: medium; font-family: arial,helvetica,sans-serif; }
        H4 { font-size: small; font-family: arial,helvetica,sans-serif; }
-->
</STYLE>
<title>ploticus: xautorange and yautorange attributes</title>
<body bgcolor=D0D0EE vlink=0000FF>
<br>
<br>
<center>
<table cellpadding=2 bgcolor=FFFFFF width=550><tr>
<td>
  <table cellpadding=2 width=550><tr>
  <td><br><h2>xautorange and yautorange attributes</h2></td>
  <td align=right>
  <small>
  <a href="../doc/welcome.html"><img src="../doc/ploticus.gif" border=0></a><br>
  Version 2.41 Mar2009
     </small><br><a href="../doc/scripthome.html">Scripts</a>
  <td></tr></table>
</td></tr>
<td>
<br>
<br>

<title>Manual page for xautorange_and_yautorange_attributes(PL)</title>
</head>
<body>

<h2>Usage</h2>
<tt>xautorange:  datafield=</tt><i>dfields</i><tt>  </tt><i>other settings..</i>
<br>
or..<tt> </tt>
<br>
<tt>yautorange:  datafield=</tt><i>dfields</i><tt>  </tt><i>other settings..</i>

<br><br><br>

<h2>Automatic axis range determination</h2>
<b>xautorange</b> and <b>yautorange</b> are attributes of
<a href="areadef.html">
 proc areadef
</a>
that allow axis range to be automatically determined based on the range of the data.<tt> </tt>
See also gallery examples 
<a href="../gallery/scatterplot10.htm">
 scatterplot10,
</a>
<a href="../gallery/stockday.htm">
 stockday,
</a>
and 
<a href="../gallery/mouse.htm">
 mouse.<tt> </tt>
</a>

<br><br><br>
<h2>Examples</h2>
Example: <tt>xautorange: datafield=2 nearest=month margin=31</tt>
<p>
Example: <tt>xautorange: datafield=1 nearest=monday</tt>
<p>
Example: <tt>yautorange: datafield=3,4,5,6,7  selectrows=@@sex = f</tt>

<br><br><br>

<h2>Settings</h2>
The <tt>datafield</tt> setting <b>must</b> be specified, and it must be leftmost.<tt> </tt>
All other settings are optional and should default to reasonable behavior.<tt> </tt>

<br><br>

<p>
<tt>datafield=</tt><i>dfields</i>
<dl>
<dt> <dd>
This setting must be given first (to the left of any other).<tt> </tt>
It specifies one or more data fields that will be scanned to 
automatically find minima and maxima.<tt> </tt>
<i>dfields</i> may be a single 
<a href="attributetypes.html#dfield">
 dfield
</a>
or a comma-delimited list of several dfields with no embedded space.<tt> </tt>
Unless a <tt>combomode=</tt> setting is used, all fields will be treated independently
when searching for a minima and maxima.<tt> </tt>
Invalid or non-existant dfields will be silently ignored, but there must be at least one valid dfield.  
Support for multiple fields contributed by Paul Totten.<tt> </tt>
<br>
Example: <tt>yautorange  datafield=2</tt>
<br>
Example: <tt>yautorange  datafield=2,4,5</tt>

<br><br>

</dl>
<p>
<tt>combomode=stack | combomode=hilo</tt>
<dl>
<dt> <dd>
If specified, an alternate method of min/max determination is used with multiple <tt>datafield</tt>s.<tt> </tt>
<br>
<tt>stack</tt> = sum the data field contents (useful when generating stacked bar graphs).<tt> </tt>
<br>
<tt>hilo</tt> = take the sum and difference of data field contents; useful when 
ranging on two fields, and one data field will be driving error bars.<tt> </tt>


<br><br>
</dl>
<p>
<a name=nearest></a>
<tt>nearest=</tt><i>s</i>
<dl>
<dt> <dd>
Set the min and max to fall on round boundaries.<tt> </tt>
For instance, <tt>nearest=10</tt> can be used to ensure that the axis min and max will always fall at 
an even multiple of 10.  <tt>nearest=month</tt> ensures that the axis min and max will fall on an even
month boundary.<tt> </tt>
<dt><dd><p>
With numeric data, <i>s</i> can be any number greater than zero.  
For date, time, and datetime data <i>s</i> is a controlled vocabulary (see below).<tt> </tt>
If plotting numeric data and <tt>nearest</tt> is not specified, a reasonable <i>s</i> will be selected.<tt> </tt>
If plotting date, time, or datetime data and <tt>nearest</tt> is not specified, <tt>datematic</tt> will be used
(previously to 2.31 <tt>exact</tt> was the default).<tt> </tt>
<dt><dd><p>
Example: <tt>nearest=100</tt> and the data range from 23 to 1162, the plot's range will be 0 to 1200.<tt> </tt>
<dt><dd><p>
Possible values for <tt>nearest</tt> are shown below.  
For each, the applicable data types are shown in parentheses.<tt> </tt>
<pre>
nearest=   range min and max will be set to:
--------  ---------------------------------
0.1       the nearest multiple of 0.1 (numeric data)
10        the nearest multiple of 10 (numeric)
1000      the nearest multiple of 100 (numeric)
(etc... any number value can be used for numeric data)

exact     the exact min and max as found in the data (any data type)

datematic  a reasonable default will be used (date, time, datetime)
minute    the nearest 1 minute boundary (time data) 
Nminute   the nearest N minute boundary (time data)*
second    the nearest 1 second boundary (time data) 
Nsecond   the nearest N second boundary (time data)*
hour      the nearest 1 hour boundary (time, datetime)
3hour     the nearest 3 hour boundary (time, datetime)
6hour     the nearest 6 hour boundary (time, datetime)
12hour    the nearest 12 hour boundary (time, datetime)
day       the nearest day boundary (datetime)
sunday    the nearest Sunday (date, datetime)
monday    the nearest Monday (date, datetime)
month     the nearest month boundary (date, datetime)
quarter   the nearest 3 month boundary (date, datetime)
3month    same as quarter
year      the nearest year boundary (date, datetime)
2year     the nearest 2 year boundary (date, datetime)
5year     the nearest 5 year boundary (date, datetime)
10year    the nearest 10 year boundary (date, datetime)

* N is a one or two digit integer and must go into 60 evenly
</pre>

<br><br>

</dl>
<p>
<tt>margin=</tt><i>m</i> 
<dl>
<dt> <dd>
If specified, <i>m</i> basic units will be added to the
maxima and also subtracted from the minima, before considering <tt>nearest</tt>.  
This may be used to guarantee margins at each end of the range.<tt> </tt>
(Basic units are days for <tt>date</tt> and <tt>datetime</tt> scaletypes; and 
minutes for <tt>time</tt>.)

<br><br>

</dl>
<p>
<tt>incmult=</tt><i>h</i> 
<dl>
<dt> <dd>
a more automatic way to get the equivalent of <tt>margin</tt> with numeric data.  
If specified, the default scale increment (same as used by proc axis stubs: inc) 
will be used for the margin.  <i>h</i> can be set to 1 to use the increment
as is, or it can be set to a value such as 2 to double it.  
The default <i>h</i> is 1.0.<tt> </tt>
The low end of the range will not dip below zero if data are all positive.  
<br>
Example: <tt>yautorange  datafield=2  incmult=2.0</tt>

<br><br>

</dl>
<p>
<tt>lowfix=</tt><i>lowval</i> 
<dl>
<dt> <dd>
If specified, the minima will always be <i>lowval</i>.<tt> </tt>
This is useful when you want only the maxima to be automatically set based on data.<tt> </tt>
<br>
Example: <tt>yautorange:  datafield=2  lowfix=0</tt>

<br><br>

</dl>
<p>
<tt>hifix=</tt><i>hival</i> 
<dl>
<dt> <dd>
If specified, the maxima will always be <i>hival</i>.<tt> </tt>
This is useful when you want only the minima to be automatically set based on data.<tt> </tt>

<br><br>

</dl>
<p>
<tt>mininit=</tt><i>lowval</i>
<dl>
<dt> <dd>
Like <tt>lowfix</tt> but is overridden by encountered data values less than <i>lowval</i>.<tt> </tt>
Useful for example if you want your axis min to be zero except when there is an occasional
negative data value. (2.30+)

<br><br>

</dl>
<p>
<tt>maxinit=</tt><i>hival</i>
<dl>
<dt> <dd>
Like <tt>hifix</tt> but is overridden by encountered data values greater than <i>hival</i>. (2.30+)

<br><br>

</dl>
<p>
<tt>numformat=</tt><i>printfspec</i> 
<dl>
<dt> <dd>
This allows user control over the internal string-based representation of minima and maxima for numerics.  
Default is <tt>%g</tt> which handles scientific-notation values and non-extreme numerics.  
Try <tt>%f</tt> if your data include extreme numerics that aren't in scientific notation.<tt> </tt>

<br><br>

</dl>
<p>
<tt>selectrows=</tt><i>conditional expression</i>
<dl>
<dt> <dd>
This allows a
<a href="select.html">
 select expression
</a>
to be applied in order to select data rows to be tested when
scanning for minima and maxima.<tt> </tt>
If specified, this setting must be the last (rightmost) on the line, and 
will have embedded spaces, unlike the other settings.  See example below.<tt> </tt>

<br><br><br>

</dl>
<h2>Variables that are set by autorange</h2>
<p>
<b>DATAXMIN</b>, <b>DATAXMAX</b>
<dl>
<dt> <dd>
The actual minima and maxima of the data field when ranging in X.  
Different from XMIN and XMAX in that these do not include any margin.<tt> </tt>
</dl>
<p>
<b>DATAYMIN</b>, <b>DATAYMAX</b>
<dl>
<dt> <dd>
The actual minima and maxima of the data field when ranging in Y.  
Different from YMIN and YMAX in that these do not include any margin.<tt> </tt>


<br>
<br>
</td></tr>
<td align=right>
<a href="../doc/welcome.html">
<img src="../doc/ploticus.gif" border=0></a><br><small>data display engine &nbsp; <br>
<a href="../doc/Copyright.html">Copyright Steve Grubb</a>
<br>
<br>
<center>
<img src="../gallery/all.gif"> 
</center>
</td></tr>
</table>
<br>
<center>
<table><tr><td>
Ploticus is hosted at http://ploticus.sourceforge.net</td><td> &nbsp; </td><td>
<a href="http://sourceforge.net/projects/ploticus"><img src="http://sflogo.sourceforge.net/sflogo.php?group_id=38453&type=12" 
width="120" height="30" border="0" 
alt="Get ploticus data display engine at SourceForge.net. Fast, secure and Free Open Source software downloads" /></a>
</td></tr></table>


</center>
</dl>
<p><hr>
Markup created by <em>unroff</em> 1.0,&#160;<tt> </tt>&#160;<tt> </tt>March 11, 2009.
</body>
</html>