File: node94.html

package info (click to toggle)
scalapack-doc 1.5-11
  • links: PTS
  • area: main
  • in suites: bullseye, buster, stretch
  • size: 10,336 kB
  • ctags: 4,931
  • sloc: makefile: 47; sh: 18
file content (68 lines) | stat: -rw-r--r-- 3,188 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Order of Arguments</TITLE>
<META NAME="description" CONTENT="Order of Arguments">
<META NAME="keywords" CONTENT="slug">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<LINK REL=STYLESHEET HREF="slug.css">
</HEAD>
<BODY LANG="EN" >
 <A NAME="tex2html3363" HREF="node95.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="http://www.netlib.org/utk/icons/next_motif.gif"></A> <A NAME="tex2html3361" HREF="node92.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="http://www.netlib.org/utk/icons/up_motif.gif"></A> <A NAME="tex2html3355" HREF="node93.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="http://www.netlib.org/utk/icons/previous_motif.gif"></A> <A NAME="tex2html3365" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="http://www.netlib.org/utk/icons/contents_motif.gif"></A> <A NAME="tex2html3366" HREF="node190.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="http://www.netlib.org/utk/icons/index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME="tex2html3364" HREF="node95.html">Option Arguments</A>
<B>Up:</B> <A NAME="tex2html3362" HREF="node92.html">Design and Documentation of </A>
<B> Previous:</B> <A NAME="tex2html3356" HREF="node93.html">Structure of the Documentation</A>
<BR> <P>
<H2><A NAME="SECTION04462000000000000000">Order of Arguments</A></H2>
                        <A NAME="subsecargorder">&#160;</A>
<P>
Arguments<A NAME="3393">&#160;</A>
of a ScaLAPACK routine appear in the
following order:
<P>
<UL>
<LI> arguments specifying options,
<LI> problem dimensions,
<LI> array or scalar arguments defining
       the input data; some of them may be
       overwritten by results,
<LI> other array or scalar arguments returning results,
<LI> work arrays (and associated array dimensions), and
<LI> diagnostic argument INFO.
<P>
</UL>
<P>
Note that not every category is present in each of the routines.
<P>
When defining each of these categories
of arguments, ScaLAPACK distinguishes
between <B>local</B> and <B>global</B>
data. On entry to a ScaLAPACK routine,
<B>local input</B> arguments<A NAME="3399">&#160;</A><A NAME="3400">&#160;</A>
may have different values on each 
process in the process grid.  Similarly,
<B>local output</B> arguments<A NAME="3402">&#160;</A><A NAME="3403">&#160;</A>
may be assigned different values on
different processes in the process
grid on exit from the ScaLAPACK routine.
<P>
<B>Global input</B> arguments<A NAME="3405">&#160;</A><A NAME="3406">&#160;</A>
must have the same value on each process in
the process grid on entry to a ScaLAPACK 
routine.  If this is not the case, most 
routines will call <TT>PXERBLA</TT> and return.
<B>Global output</B> 
arguments<A NAME="3409">&#160;</A><A NAME="3410">&#160;</A>
are assigned the same value on all processes
in the process grid on exit from a ScaLAPACK
routine.
<P>
<BR> <HR>
<P><ADDRESS>
<I>Susan Blackford <BR>
Tue May 13 09:21:01 EDT 1997</I>
</ADDRESS>
</BODY>
</HTML>