From ketan at ci.uchicago.edu Fri May 6 10:26:03 2011 From: ketan at ci.uchicago.edu (ketan at ci.uchicago.edu) Date: Fri, 6 May 2011 10:26:03 -0500 (CDT) Subject: [Swift-commit] r4450 - www/cookbook Message-ID: <20110506152603.B88969CFC7@svn.ci.uchicago.edu> Author: ketan Date: 2011-05-06 10:26:03 -0500 (Fri, 06 May 2011) New Revision: 4450 Modified: www/cookbook/cookbook-asciidoc.html www/cookbook/cookbook-asciidoc.txt Log: Modified: www/cookbook/cookbook-asciidoc.html =================================================================== --- www/cookbook/cookbook-asciidoc.html 2011-05-04 22:17:58 UTC (rev 4449) +++ www/cookbook/cookbook-asciidoc.html 2011-05-06 15:26:03 UTC (rev 4450) @@ -1079,18 +1079,24 @@

3.1. Beagle

Swift is now installed on Beagle as a module. Swift supports a Coasters based, -PBS-enabled computing environment for Beagle. To get started with Swift on -Beagle follow the steps outlined below:

+computing environment for Beagle. A detailed Swift documentation is maintained +[[here]. To get started +with Swift on Beagle follow the steps outlined below:

step 1. Load the Swift module on Beagle as follows: module load swift

-

step 2. Create a Swift specific folder where all your Swift related work will -stay. (say, mkdir swift-lab)

-

step 3. To get started with an example, copy the folder at -/home/ketan/labs/catsn.works to the above created swift-lab. (cp -r -/home/ketan/catsn.works ~/swift-lab).

-

step 4. From the sites file: catsn.works/beagle-coaster.xml, change the path -of swift.workdir to your preferred location (say to ~/swift-lab/swift.workdir) -and the project name to the one you are part of.

-

step 5. Run the example using following commandline: swift -config cf -tc.file tc -sites.file beagle-coaster-1.xml catsn.swift -n=1

+

step 2. Create and change to a directory where your Swift related work will +stay. (say, mkdir swift-lab, followed by, cd swift-lab)

+

step 3. To get started with a simple example running /bin/cat to read an input file data.txt and write to an output file f.nnn.out, copy the folder at /home/ketan/labs/catsn to the above directory. (cp -r /home/ketan/catsn . followed by cd catsn).

+

step 4. In the sites file: beagle-coaster.xml, make the following two +changes: 1) change the path of workdirectory to your preferred location +(say to /lustre/beagle/$USER/swift-lab/swift.workdir) and 2) Change the +project name to your project (CI-CCR000013) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs.

+

step 5. Run the example using following commandline (also found in run.sh): +swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1 +. You can further change the value of -n to any arbitrary number to run that +many number of concurrent cat

+

step 6. Check the output in the generated outdir directory (ls outdir)

Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes will get fast prioritized execution. Good for small tests

@@ -1477,7 +1483,7 @@ Modified: www/cookbook/cookbook-asciidoc.txt =================================================================== --- www/cookbook/cookbook-asciidoc.txt 2011-05-04 22:17:58 UTC (rev 4449) +++ www/cookbook/cookbook-asciidoc.txt 2011-05-06 15:26:03 UTC (rev 4450) @@ -488,24 +488,31 @@ Beagle ~~~~~~ Swift is now installed on Beagle as a module. Swift supports a Coasters based, -PBS-enabled computing environment for Beagle. To get started with Swift on -Beagle follow the steps outlined below: +computing environment for Beagle. A detailed Swift documentation is maintained +[[http://www.ci.uchicago.edu/swift/docs/index.php][here]]. To get started +with Swift on Beagle follow the steps outlined below: *step 1.* Load the Swift module on Beagle as follows: +module load swift+ -*step 2.* Create a Swift specific folder where all your Swift related work will -stay. (say, +mkdir swift-lab+) +*step 2.* Create and change to a directory where your Swift related work will +stay. (say, +mkdir swift-lab+, followed by, +cd swift-lab+) -*step 3.* To get started with an example, copy the folder at -+/home/ketan/labs/catsn.works+ to the above created swift-lab. (+cp -r -/home/ketan/catsn.works ~/swift-lab+). +*step 3.* To get started with a simple example running +/bin/cat+ to read an input file +data.txt+ and write to an output file +f.nnn.out+, copy the folder at +/home/ketan/labs/catsn+ to the above directory. (+cp -r /home/ketan/catsn .+ followed by +cd catsn+). -*step 4.* From the sites file: +catsn.works/beagle-coaster.xml+, change the path -of swift.workdir to your preferred location (say to +~/swift-lab/swift.workdir+) -and the project name to the one you are part of. +*step 4.* In the sites file: +beagle-coaster.xml+, make the following two +changes: *1)* change the path of +workdirectory+ to your preferred location +(say to +/lustre/beagle/$USER/swift-lab/swift.workdir+) and *2)* Change the +project name to your project (+CI-CCR000013+) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs. -*step 5.* Run the example using following commandline: +swift -config cf -tc.file tc -sites.file beagle-coaster-1.xml catsn.swift -n=1+ +*step 5.* Run the example using following commandline (also found in run.sh): ++swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1+ +. You can further change the value of +-n+ to any arbitrary number to run that +many number of concurrent +cat+ +*step 6.* Check the output in the generated +outdir+ directory (+ls outdir+) + Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes will get fast prioritized execution. Good for small tests From tga at ci.uchicago.edu Fri May 6 16:17:29 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Fri, 6 May 2011 16:17:29 -0500 (CDT) Subject: [Swift-commit] r4452 - SwiftApps/SwiftR/Swift/exec Message-ID: <20110506211729.AE71C9CFC7@svn.ci.uchicago.edu> Author: tga Date: 2011-05-06 16:17:29 -0500 (Fri, 06 May 2011) New Revision: 4452 Modified: SwiftApps/SwiftR/Swift/exec/start-swift Log: improved error message when swift fails to start correctly. Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-06 19:49:43 UTC (rev 4451) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-06 21:17:29 UTC (rev 4452) @@ -565,6 +565,7 @@ # Standard clenuup actions function stdcleanup_start { # don't accept any more requests: unlink fifo from filesystem + echo stdcleanup_start 1&>2 if [ -p requestpipe ]; then rm requestpipe fi @@ -727,9 +728,17 @@ exitcode=$? # Do any cleanup if swift exits in this manner if [ "$exitcode" != 0 ]; then - echo "error: Swift exited unexpectedly with $exitcode" > resultpipe & - echopid=$! - sleep 5 - kill $echopid &> /dev/null + echo "error: Swift exited unexpectedly with return code $exitcode" + if [ "$keepdir" = TRUE ]; then + echo "See logs in $trundir for more information" + else + echo "Turn on keep work option to retain logs" + fi + + ( echo "error: swift exited unexpectedly with return code $exitcode" > resultpipe + echopid=$! + sleep 5 + kill $echopid + ) &> /dev/null & fi From tga at ci.uchicago.edu Fri May 6 16:53:34 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Fri, 6 May 2011 16:53:34 -0500 (CDT) Subject: [Swift-commit] r4453 - in SwiftApps/SwiftR/Swift: . exec Message-ID: <20110506215334.68BAE9CFC7@svn.ci.uchicago.edu> Author: tga Date: 2011-05-06 16:53:34 -0500 (Fri, 06 May 2011) New Revision: 4453 Modified: SwiftApps/SwiftR/Swift/DESCRIPTION SwiftApps/SwiftR/Swift/exec/start-swift Log: New version. Modified: SwiftApps/SwiftR/Swift/DESCRIPTION =================================================================== --- SwiftApps/SwiftR/Swift/DESCRIPTION 2011-05-06 21:17:29 UTC (rev 4452) +++ SwiftApps/SwiftR/Swift/DESCRIPTION 2011-05-06 21:53:34 UTC (rev 4453) @@ -1,12 +1,12 @@ Package: Swift Type: Package Title: R interface to Swift parallel scripting languaage -Version: 0.2.3 -Date: 2011-04-20 +Version: 0.2.4 +Date: 2011-05-06 Author: Michael Wilde Maintainer: Michael Wilde Description: Routines to invoke R functions on remote resources through Swift. License: Apache License LazyLoad: yes -Packaged: 2011-04-20; Tim Armstrong +Packaged: 2011-05-06; Tim Armstrong Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-06 21:17:29 UTC (rev 4452) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-06 21:53:34 UTC (rev 4453) @@ -735,7 +735,7 @@ echo "Turn on keep work option to retain logs" fi - ( echo "error: swift exited unexpectedly with return code $exitcode" > resultpipe + ( echo "error: swift exited unexpectedly with return code $exitcode" > resultpipe & echopid=$! sleep 5 kill $echopid From ketan at ci.uchicago.edu Fri May 6 18:21:32 2011 From: ketan at ci.uchicago.edu (ketan at ci.uchicago.edu) Date: Fri, 6 May 2011 18:21:32 -0500 (CDT) Subject: [Swift-commit] r4454 - www/cookbook Message-ID: <20110506232132.58E189CFCB@svn.ci.uchicago.edu> Author: ketan Date: 2011-05-06 18:21:32 -0500 (Fri, 06 May 2011) New Revision: 4454 Modified: www/cookbook/cookbook-asciidoc.html www/cookbook/cookbook-asciidoc.txt Log: Modified: www/cookbook/cookbook-asciidoc.html =================================================================== --- www/cookbook/cookbook-asciidoc.html 2011-05-06 21:53:34 UTC (rev 4453) +++ www/cookbook/cookbook-asciidoc.html 2011-05-06 23:21:32 UTC (rev 4454) @@ -1074,10 +1074,116 @@
-

3. Swift on Diverse Infrastructures

+

3. Coasters

+

Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters.

+

Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were:

+
+
+
<execution provider="coaster" jobmanager="local:pbs"/>
+<profile namespace="globus" key="project">CI-CCR000013</profile>
+
+<!-- Note that the following is going to be defunct in the new version (0.93+) and replaced by
+"ProviderAttributes" key and may not work in the future Swift versions-->
+
+<!--<profile namespace="globus" key="ppn">24:cray:pack</profile>-->
+
+<profile namespace="globus" key="providerAttributes">
+pbs.aprun
+pbs.mpp=true
+</profile>
+
+<profile namespace="globus" key="workersPerNode">24</profile>
+<profile namespace="globus" key="maxTime">100000</profile>
+
+<profile namespace="globus" key="lowOverallocation">100</profile>
+<profile namespace="globus" key="highOverallocation">100</profile>
+
+<profile namespace="globus" key="slots">20</profile>
+<profile namespace="globus" key="nodeGranularity">5</profile>
+<profile namespace="globus" key="maxNodes">5</profile>
+<profile namespace="karajan" key="jobThrottle">20.00</profile>
+<profile namespace="karajan" key="initialScore">10000</profile>
+

The following table briefly describes the elements on the coasters setup:

+
+ +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
profile key brief description

slots

How many maximum LRM jobs/worker blocks are allowed

workersPerNode

How many coaster workers to run per execution node

nodeGranularity

Each worker block uses a number of nodes that is a multiple of this number

lowOverallocation

How many times larger than the job walltime should a block’s walltime be if all jobs are 1s long

highOverallocation

How many times larger than the job walltime should a block’s walltime be if all jobs are infinitely long

workersPerNode

How many coaster workers to run per execution node reserve How many seconds to reserve in a block’s walltime for starting/shutdown operations

maxnodes

The maximum number of nodes allowed in a block

maxtime

The maximum number of walltime allowed for a block coaster service

jobThrottle

the number of concurrent jobs allowed on a site

+
-

3.1. Beagle

+

3.1. For Advanced Users

+

One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters.

+
+
+

3.2. Coaster providers: local, ssh, pbs

+

Settings and examples for different coaster providers mechanisms.

+
+
+
+
+

4. Swift on Diverse Infrastructures

+
+
+

4.1. Beagle

Swift is now installed on Beagle as a module. Swift supports a Coasters based, computing environment for Beagle. A detailed Swift documentation is maintained [[here]. To get started @@ -1101,7 +1207,7 @@ will get fast prioritized execution. Good for small tests

-

3.2. PADS

+

4.2. PADS

Swift on PADS To execute your Swift script on the PADS cluster use this command:

@@ -1127,7 +1233,7 @@ </config>
-

3.3. OSG

+

4.3. OSG

This section describes how to get Swift running on the OSG Grid. We will use a manual coaster setup to get Swift running on OSG.

Coaster setup on OSG

The following figure shows an abstract scheme for the manual coasters setup on @@ -1140,7 +1246,7 @@

In the following steps, we will go through the process of manually setting

-

3.4. Bionimbus

+

4.4. Bionimbus

This section explains a step by step procedure on getting Swift running on the Bionimbus cloud. We will use the manual coasters configuration on the Bionimbus cloud.

@@ -1214,100 +1320,6 @@
-

4. Coasters

-
-

Coasters were introduced in Swift v0.6 as an experimental feature. In many -applications, Swift performance can be greatly enhanced by the use of CoG -coasters. CoG coasters provide a low-overhead job submission and file transfer -mechanism suited for the execution of short jobs (on the order of a few -seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters.

-

Following is a nice coasters setup case-study where sites.xml coaster settings were:

-
-
-
<execution provider="coaster" jobmanager="local:pbs"/>
-<profile namespace="globus" key="project">CI-CCR000013</profile>
-<profile namespace="globus" key="ppn">24:cray:pack</profile>
-<profile namespace="globus" key="workersPerNode">24</profile>
-<profile namespace="globus" key="maxTime">100000</profile>
-<profile namespace="globus" key="lowOverallocation">100</profile>
-<profile namespace="globus" key="highOverallocation">100</profile>
-<profile namespace="globus" key="slots">20</profile>
-<profile namespace="globus" key="nodeGranularity">5</profile>
-<profile namespace="globus" key="maxNodes">5</profile>
-<profile namespace="karajan" key="jobThrottle">20.00</profile>
-<profile namespace="karajan" key="initialScore">10000</profile>
-

The following table briefly describes the elements on the coasters setup:

-
- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
profile key brief description

slots

How many maximum LRM jobs/worker blocks are allowed

workersPerNode

How many coaster workers to run per execution node

nodeGranularity

Each worker block uses a number of nodes that is a multiple of this number

lowOverallocation

How many times larger than the job walltime should a block’s walltime be if all jobs are 1s long

highOverallocation

How many times larger than the job walltime should a block’s walltime be if all jobs are infinitely long

workersPerNode

How many coaster workers to run per execution node reserve How many seconds to reserve in a block’s walltime for starting/shutdown operations

maxnodes

The maximum number of nodes allowed in a block

maxtime

The maximum number of walltime allowed for a block coaster service

jobThrottle

the number of concurrent jobs allowed on a site

-
-
-

4.1. For Advanced Users

-

One of the main reason that one would initially deviate from coaster -defaults into more complex pool entries is to force jobs to fit into some -site-imposed constraint. For instance a typical submission to the experimental -queue requires a user to request upto 3 nodes for under 1 hour. This setup -could be achieved with a careful tuning of coaters parameters.

-
-
-

4.2. Coaster providers: local, ssh, pbs

-

Settings and examples for different coaster providers mechanisms.

-
-
-
-

5. Debugging Swift

Swift errors are logged in several places:

@@ -1483,7 +1495,7 @@ Modified: www/cookbook/cookbook-asciidoc.txt =================================================================== --- www/cookbook/cookbook-asciidoc.txt 2011-05-06 21:53:34 UTC (rev 4453) +++ www/cookbook/cookbook-asciidoc.txt 2011-05-06 23:21:32 UTC (rev 4454) @@ -61,8 +61,12 @@ Setting up to run Swift ~~~~~~~~~~~~~~~~~~~~~~~~ This is simple. We will be using a pre-compiled version of Swift that can be -downloaded from link:http://www.ci.uchicago.edu/swift/downloads/index.php[here]. +downloaded from link:http://www.ci.uchicago.edu/swift/downloads/index.php[here]. Download and untar the latest precompiled version as follows: +---- +$ tar xf swift-0.92.1.tar.gz +---- + Environment Setup ^^^^^^^^^^^^^^^^^^ @@ -480,8 +484,118 @@ login1$ ---- +Coasters +-------- +Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters. +//**Include neat diagrams.** +Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were: +[xml] +source~~~~ + +CI-CCR000013 + + + + + + +pbs.aprun +pbs.mpp=true + + +24 +100000 + +100 +100 + +20 +5 +5 +20.00 +10000 +source~~~~ + +The following table briefly describes the elements on the coasters setup: +[width="70%", cols="^3,10", options="header"] +|============================================================================================= +|profile key | brief description +|slots | How many maximum LRM jobs/worker blocks are allowed +|workersPerNode | How many coaster workers to run per execution node +|nodeGranularity | Each worker block uses a number of nodes that is a multiple of this number +|lowOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are 1s long +|highOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are infinitely long +|workersPerNode | How many coaster workers to run per execution node reserve How many seconds to reserve in a block's walltime for starting/shutdown operations +|maxnodes | The maximum number of nodes allowed in a block +|maxtime | The maximum number of walltime allowed for a block coaster service +|jobThrottle |the number of concurrent jobs allowed on a site +|============================================================================================== + +// +//For Beginners +//~~~~~~~~~~~~~~ +//Coasters for beginners. Usage of existing, prebuilt templates. +// +//For Intermediate Users +//~~~~~~~~~~~~~~~~~~~~~~~ +//Coasters for intermediate users. +// +//Using gensites +//^^^^^^^^^^^^^^^ +//Usage of gensites to generate your own sites +//configurations. +// +// +// + +For Advanced Users +~~~~~~~~~~~~~~~~~~ + +//Coasters for advanced users. Getting your hands dirty. + +One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters. + +//How to run Swift under different Coasters configurations +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +// +//Manual +//^^^^^^^ +//Todo +// +//Passive +//^^^^^^^^ +//Todo +// +//Persistent +//^^^^^^^^^^^ +//Todo +// +//Summary of Differences Between different Coaster types +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +//A tabular representations of highlights of different coaster setups +// +// +//Data Management +// + +Coaster providers: local, ssh, pbs +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Settings and examples for different coaster providers mechanisms. + + + Swift on Diverse Infrastructures --------------------------------- @@ -489,7 +603,7 @@ ~~~~~~ Swift is now installed on Beagle as a module. Swift supports a Coasters based, computing environment for Beagle. A detailed Swift documentation is maintained -[[http://www.ci.uchicago.edu/swift/docs/index.php][here]]. To get started +[[http://www.ci.uchicago.edu/swift/docs/index.php][here]]. To get started with Swift on Beagle follow the steps outlined below: *step 1.* Load the Swift module on Beagle as follows: +module load swift+ @@ -654,104 +768,7 @@ //~~~~~~~~ //Swift on Magellan // -Coasters --------- -Coasters were introduced in Swift v0.6 as an experimental feature. In many -applications, Swift performance can be greatly enhanced by the use of CoG -coasters. CoG coasters provide a low-overhead job submission and file transfer -mechanism suited for the execution of short jobs (on the order of a few -seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters. -//**Include neat diagrams.** -Following is a nice coasters setup case-study where sites.xml coaster settings were: - -[xml] -source~~~~ - -CI-CCR000013 -24:cray:pack -24 -100000 -100 -100 -20 -5 -5 -20.00 -10000 -source~~~~ - -The following table briefly describes the elements on the coasters setup: -[width="70%", cols="^3,10", options="header"] -|============================================================================================= -|profile key | brief description -|slots | How many maximum LRM jobs/worker blocks are allowed -|workersPerNode | How many coaster workers to run per execution node -|nodeGranularity | Each worker block uses a number of nodes that is a multiple of this number -|lowOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are 1s long -|highOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are infinitely long -|workersPerNode | How many coaster workers to run per execution node reserve How many seconds to reserve in a block's walltime for starting/shutdown operations -|maxnodes | The maximum number of nodes allowed in a block -|maxtime | The maximum number of walltime allowed for a block coaster service -|jobThrottle |the number of concurrent jobs allowed on a site -|============================================================================================== - -// -//For Beginners -//~~~~~~~~~~~~~~ -//Coasters for beginners. Usage of existing, prebuilt templates. -// -//For Intermediate Users -//~~~~~~~~~~~~~~~~~~~~~~~ -//Coasters for intermediate users. -// -//Using gensites -//^^^^^^^^^^^^^^^ -//Usage of gensites to generate your own sites -//configurations. -// -// -// - -For Advanced Users -~~~~~~~~~~~~~~~~~~ - -//Coasters for advanced users. Getting your hands dirty. - -One of the main reason that one would initially deviate from coaster -defaults into more complex pool entries is to force jobs to fit into some -site-imposed constraint. For instance a typical submission to the experimental -queue requires a user to request upto 3 nodes for under 1 hour. This setup -could be achieved with a careful tuning of coaters parameters. - -//How to run Swift under different Coasters configurations -//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -// -//Manual -//^^^^^^^ -//Todo -// -//Passive -//^^^^^^^^ -//Todo -// -//Persistent -//^^^^^^^^^^^ -//Todo -// -//Summary of Differences Between different Coaster types -//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -//A tabular representations of highlights of different coaster setups -// -// -//Data Management -// - -Coaster providers: local, ssh, pbs -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Settings and examples for different coaster providers mechanisms. - Debugging Swift --------------- Swift errors are logged in several places: From tga at ci.uchicago.edu Mon May 9 09:22:31 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 09:22:31 -0500 (CDT) Subject: [Swift-commit] r4455 - SwiftApps/SwiftR Message-ID: <20110509142231.1A8BF9CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 09:22:30 -0500 (Mon, 09 May 2011) New Revision: 4455 Modified: SwiftApps/SwiftR/Makefile Log: Don't fail build if svn fails. Modified: SwiftApps/SwiftR/Makefile =================================================================== --- SwiftApps/SwiftR/Makefile 2011-05-06 23:21:32 UTC (rev 4454) +++ SwiftApps/SwiftR/Makefile 2011-05-09 14:22:30 UTC (rev 4455) @@ -45,7 +45,7 @@ rm $(TBALL) $(TBALL): Swift/inst/swift/bin/swift $(PKG_FILES) Makefile - if [ -d .svn -a -x "`which svn`" ]; then svn info > Swift/svninfo; fi + - if [ -d .svn -a -x "`which svn`" ]; then svn info > Swift/svninfo; fi R CMD build Swift From tga at ci.uchicago.edu Mon May 9 09:22:54 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 09:22:54 -0500 (CDT) Subject: [Swift-commit] r4456 - in SwiftApps/SwiftR: . Swift/exec config config/pbs config/pbs4hr Message-ID: <20110509142254.B982C9CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 09:22:54 -0500 (Mon, 09 May 2011) New Revision: 4456 Added: SwiftApps/SwiftR/config/ SwiftApps/SwiftR/config/pbs/ SwiftApps/SwiftR/config/pbs/cf SwiftApps/SwiftR/config/pbs/sites.xml SwiftApps/SwiftR/config/pbs/tc SwiftApps/SwiftR/config/pbs4hr/ SwiftApps/SwiftR/config/pbs4hr/cf SwiftApps/SwiftR/config/pbs4hr/sites.xml SwiftApps/SwiftR/config/pbs4hr/tc Modified: SwiftApps/SwiftR/Swift/exec/start-swift Log: Adding in some custom config files that work for PADS - 1 hr jobs and 4 hr jobs. Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 14:22:30 UTC (rev 4455) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 14:22:54 UTC (rev 4456) @@ -15,7 +15,7 @@ # Look for: # Passive queue processor initialized. Callback URI is http://140.221.8.62:55379 - for try in $($SEQ 1 20); do + for try in $($SEQ 1 120); do uriline=$(grep "Passive queue processor initialized. Callback URI is" $out 2> /dev/null) if [ "_$uriline" = _ ]; then sleep 1 Added: SwiftApps/SwiftR/config/pbs/cf =================================================================== --- SwiftApps/SwiftR/config/pbs/cf (rev 0) +++ SwiftApps/SwiftR/config/pbs/cf 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,8 @@ +wrapperlog.always.transfer=false +sitedir.keep=false +execution.retries=0 +lazy.errors=false +status.mode=provider +use.provider.staging=false +provider.staging.pin.swiftfiles=false +#throttle.host.submit=1 Added: SwiftApps/SwiftR/config/pbs/sites.xml =================================================================== --- SwiftApps/SwiftR/config/pbs/sites.xml (rev 0) +++ SwiftApps/SwiftR/config/pbs/sites.xml 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,17 @@ + + + + + 3600 + 1 + 128 + 1 + 1 + 1.27 + 10000 + fast + /scratch/local/tga + + /gpfs/pads/scratch/tga + + Added: SwiftApps/SwiftR/config/pbs/tc =================================================================== --- SwiftApps/SwiftR/config/pbs/tc (rev 0) +++ SwiftApps/SwiftR/config/pbs/tc 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,2 @@ +fork bashlocal /bin/bash null null null +pbs bash /bin/bash null null GLOBUS::maxwalltime="0:55:00" Added: SwiftApps/SwiftR/config/pbs4hr/cf =================================================================== --- SwiftApps/SwiftR/config/pbs4hr/cf (rev 0) +++ SwiftApps/SwiftR/config/pbs4hr/cf 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,8 @@ +wrapperlog.always.transfer=false +sitedir.keep=false +execution.retries=0 +lazy.errors=false +status.mode=provider +use.provider.staging=false +provider.staging.pin.swiftfiles=false +#throttle.host.submit=1 Added: SwiftApps/SwiftR/config/pbs4hr/sites.xml =================================================================== --- SwiftApps/SwiftR/config/pbs4hr/sites.xml (rev 0) +++ SwiftApps/SwiftR/config/pbs4hr/sites.xml 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,21 @@ + + + + + + + 14400 + 1 + 128 + 1 + 1 + 1.27 + 10000 + short + /scratch/local/tga + + /gpfs/pads/scratch/tga + + Added: SwiftApps/SwiftR/config/pbs4hr/tc =================================================================== --- SwiftApps/SwiftR/config/pbs4hr/tc (rev 0) +++ SwiftApps/SwiftR/config/pbs4hr/tc 2011-05-09 14:22:54 UTC (rev 4456) @@ -0,0 +1,3 @@ +fork bashlocal /bin/bash null null null +pbs bash /bin/bash null null GLOBUS::maxWallTime="03:55:00" + From tga at ci.uchicago.edu Mon May 9 09:27:44 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 09:27:44 -0500 (CDT) Subject: [Swift-commit] r4457 - SwiftApps/SwiftR Message-ID: <20110509142744.AC9A19CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 09:27:44 -0500 (Mon, 09 May 2011) New Revision: 4457 Modified: SwiftApps/SwiftR/IMMEDIATE-TODO Log: Added note about todo for custom config Modified: SwiftApps/SwiftR/IMMEDIATE-TODO =================================================================== --- SwiftApps/SwiftR/IMMEDIATE-TODO 2011-05-09 14:22:54 UTC (rev 4456) +++ SwiftApps/SwiftR/IMMEDIATE-TODO 2011-05-09 14:27:44 UTC (rev 4457) @@ -20,6 +20,19 @@ - Beagle - Sarah Kenny FMRI +MED: +-- Have a more user-friendly way to specify some of the more common + custom setups: + - E.g. PBS with Dynamic submission of jobs of various lengths + - other batch schedulers + + This informs specifying + - job walltimes + - queue + - staging mechanism + - etc + We also need robust defaults + MED: -- Feedback from queue to let user know if job waiting in batch queue From tga at ci.uchicago.edu Mon May 9 13:05:15 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 13:05:15 -0500 (CDT) Subject: [Swift-commit] r4458 - in SwiftApps/SwiftR: . Swift/R Swift/exec perftools Message-ID: <20110509180515.505C59CFCB@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 13:05:15 -0500 (Mon, 09 May 2011) New Revision: 4458 Modified: SwiftApps/SwiftR/IMMEDIATE-TODO SwiftApps/SwiftR/Swift/R/Workers.R SwiftApps/SwiftR/Swift/exec/start-swift SwiftApps/SwiftR/Swift/exec/start-swift-daemon SwiftApps/SwiftR/perftools/parselog.py Log: Changing swiftInit so that it doesn't return until the workers have been launched ok. This should allow better error handling, and should allow users to type their ssh passwords. still to be done: test more thoroughly, throw error from swiftInit if workers don't start up ok Modified: SwiftApps/SwiftR/IMMEDIATE-TODO =================================================================== --- SwiftApps/SwiftR/IMMEDIATE-TODO 2011-05-09 14:27:44 UTC (rev 4457) +++ SwiftApps/SwiftR/IMMEDIATE-TODO 2011-05-09 18:05:15 UTC (rev 4458) @@ -16,6 +16,10 @@ startup code for one of libraries HIGH: +-- sometimes the server crashes after servicing first request( + only observer when running locally and on sge) + +HIGH: -- Benchmark ideas - Beagle - Sarah Kenny FMRI @@ -47,8 +51,10 @@ MED: -- Support generic swift sites.xml and tc.data files for power users +-- Note: support is added, but need to consider either: + a) guidelines for how to write the file + b) templates or auto-generation. - MED: -- automated tests Modified: SwiftApps/SwiftR/Swift/R/Workers.R =================================================================== --- SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 14:27:44 UTC (rev 4457) +++ SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 18:05:15 UTC (rev 4458) @@ -207,8 +207,8 @@ # the user if there was a problem with the workers out <- system(cmdString, intern=TRUE) if (length(out) != 2) - stop(paste("Unexpected output from start-swift: '", out, "'", - "Launching may have failed")) + stop(paste("Unexpected output from start-swift: '", + paste(out, collapse="\n"), "'", "Launching may have failed")) pid <- out[[1]] workdir <- out[[2]] cat("Started worker manager with pid ", pid, "\n") @@ -228,7 +228,7 @@ addHook() # Sleep to give start-swift time to set up fifos,etc - Sys.sleep(2) + #Sys.sleep(2) return (invisible(output)) } Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 14:27:44 UTC (rev 4457) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 18:05:15 UTC (rev 4458) @@ -45,11 +45,11 @@ IDLETIMEOUT=$((60*60*240)) # 10 days: FIXME: make this a command line arg - echo "Starting to launch ssh workers on hosts: $hosts" for host in $(echo $hosts); do timestamp=$(date "+%Y.%m%d.%H%M%S") random=$(awk "BEGIN {printf \"%0.5d\", $RANDOM}") ID=$timestamp.$random + echo "Starting to launch worker on host: $host" # FIXME: make logging an argument; set false by default # fixme:send worker.pl to remote host via stdin or scp. if ssh $host /bin/sh -c \'"mkdir -p $LOGDIR"\' @@ -66,7 +66,7 @@ echo "Error sending file to $host" fi else - echo "Error contacting $host" + echo "Error contacting $host or creating directory $LOGDIR on host" fi @@ -74,6 +74,10 @@ echo Started workers from ssh processes $sshpids echo $sshpids > $sshpidfile + if [ "$doack" = TRUE ]; then + echo done > ackfifo + doack=FALSE + fi } @@ -369,6 +373,10 @@ if [ $succ -eq 0 ] then echo Started workers from batch job $(cat $jobidfile) + if [ "$doack" = TRUE ]; then + echo done > ackfifo + doack=FALSE + fi else echo Batch queue submission failed, exiting. stdcleanup_start @@ -525,6 +533,7 @@ # Setup a working directory if [ "$workdir" = NONE ] then + doack=FALSE trundir=$(mktemp -d $rundir.XXXX) # FIXME: check success if [ "$?" != "0" ] then @@ -532,6 +541,7 @@ exit 1 fi else + doack=TRUE # let -daemon script know when we are done echo Working in $workdir trundir=$workdir mkdir -p $workdir @@ -581,6 +591,10 @@ rm $SUBMIT_FILE fi fi + if [ "$doack" = TRUE ]; then + echo done > ackfifo + doack=FALSE + fi } echo Running in $trundir "(linked to $rundir)" @@ -641,7 +655,10 @@ trap onexit $TRAPEVENTS exitcmd=onexit - + if [ "$doack" = TRUE ]; then + echo done > ackfifo + doack=FALSE + fi elif [ $server = ssh ]; then if [ $cores -eq 0 ]; then @@ -666,6 +683,7 @@ #echo Based on $rpfile: terminating process process group $rpgid on $rhost echo Shutting down worker processes on $rhost ssh $rhost sh -c \'"kill -s TERM -- -$rpgid &>/dev/null"\' + echo Shut down worker process on $rhost done if [ "_$sshpids$starterpid$coasterservicepid" != _ ]; then echo kill $sshpids $starterpid $coasterservicepid >& /dev/null Modified: SwiftApps/SwiftR/Swift/exec/start-swift-daemon =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift-daemon 2011-05-09 14:27:44 UTC (rev 4457) +++ SwiftApps/SwiftR/Swift/exec/start-swift-daemon 2011-05-09 18:05:15 UTC (rev 4458) @@ -13,6 +13,10 @@ mkdir -p $tmp/$USER/SwiftR workdir=$(mktemp -d $tmp/$USER/SwiftR/swift.XXXX) + +ackfifo=$workdir/ackfifo +mkfifo $ackfifo + if [ "$?" != "0" ] then echo "Could not create temporary directory under $tmp/$USER/SwiftR" @@ -25,6 +29,9 @@ $ssscript "$@" -d $workdir 1>&2 & childpid=$! - echo ${childpid} echo ${workdir} + +# Wait for subprocess to let us know its ready +cat $ackfifo > /dev/null +rm $ackfifo Modified: SwiftApps/SwiftR/perftools/parselog.py =================================================================== --- SwiftApps/SwiftR/perftools/parselog.py 2011-05-09 14:27:44 UTC (rev 4457) +++ SwiftApps/SwiftR/perftools/parselog.py 2011-05-09 18:05:15 UTC (rev 4458) @@ -109,7 +109,8 @@ exec_events = log_iter("vdl:execute") -basetime = datetime.datetime(2011, 3, 18, 13, 22, 52, 231*1000) +#basetime = datetime.datetime(2011, 3, 18, 13, 22, 52, 231*1000) +basetime = datetime.datetime(2011, 3, 28, 19, 39, 25, 707*1000) exec_events = list(time_converted(exec_events, basetime)) starts = [(t, priority, type, message, message.split()[1]) @@ -125,11 +126,26 @@ print s, e def to_s(td): - return float(td.seconds) + float(td.microseconds) / 1000000.0 + return td.days * 24 * 60 * 60 + float(td.seconds) + float(td.microseconds) / 1000000.0 -paired = [(i, s[0], e[0]) for i,s,e in zip(range(len(starts)), starts, ends)] +paired = [(s[0], e[0], to_s(e[0]) - to_s(s[0])) + for s,e in zip(starts, ends) + if to_s(s[0]) > 20600] + #if to_s(s[0]) > 300] +paired.sort(key=itemgetter(2)) +paired.reverse() +paired = [(i, s, e, d ) for i, (s,e,d) in zip(range(len(paired)), paired)] +print paired import pylab -for i, s, e in paired: +for i, s, e, diff in paired: pylab.plot((to_s(s), to_s(e)), (i, i), 'r') +pylab.xlabel("time (s)") +pylab.ylabel("number of active bootstrap tasks.") + pylab.show() + +pylab.hist([t[3] for t in paired], bins=20) +pylab.xlabel("time (s)") +pylab.ylabel("# tasks") +pylab.show() From tga at ci.uchicago.edu Mon May 9 13:48:40 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 13:48:40 -0500 (CDT) Subject: [Swift-commit] r4459 - in SwiftApps/SwiftR/Swift: R exec Message-ID: <20110509184840.DF3CF9CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 13:48:40 -0500 (Mon, 09 May 2011) New Revision: 4459 Modified: SwiftApps/SwiftR/Swift/R/Workers.R SwiftApps/SwiftR/Swift/exec/start-swift SwiftApps/SwiftR/Swift/exec/start-swift-daemon Log: Ironing out some rough edges with ssh. Modified: SwiftApps/SwiftR/Swift/R/Workers.R =================================================================== --- SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 18:05:15 UTC (rev 4458) +++ SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 18:48:40 UTC (rev 4459) @@ -202,16 +202,15 @@ "--tc.file", shQuote(tc.file), "--sites.file", shQuote(sites.file)) } - # launch asynchronously - # for now, we will rely on the shell script's output to inform - # the user if there was a problem with the workers + # launch server. out <- system(cmdString, intern=TRUE) - if (length(out) != 2) + if (length(out) != 3 && length(out) != 2) { stop(paste("Unexpected output from start-swift: '", paste(out, collapse="\n"), "'", "Launching may have failed")) + + } pid <- out[[1]] workdir <- out[[2]] - cat("Started worker manager with pid ", pid, "\n") output <- list() output$pid <- pid @@ -219,18 +218,29 @@ output$workdir <- workdir output$cores <- cores output$nodes <- nodes + + if (length(out) == 2) { + # didn't get status message + killWorkerProcess(output, quiet=T) + stop("swiftInit failed: no status message from start-swift\n") + } + stat <- out[[3]] + if (stat == "ok") { + cat("Started worker manager with pid ", pid, "\n") + # store worker info + .swift.workers[[length(.swift.workers) + 1]] <<- output + # add hook to ensure child process will be killed when + # this process exits + addHook() - # store worker info - .swift.workers[[length(.swift.workers) + 1]] <<- output + # Sleep to give start-swift time to set up fifos,etc - # add hook to ensure child process will be killed when - # this process exits - addHook() - - # Sleep to give start-swift time to set up fifos,etc - #Sys.sleep(2) - - return (invisible(output)) + return (invisible(output)) + } + else { + killWorkerProcess(output, quiet=T) + stop(paste("swiftInit failed with error:", stat)) + } } swiftShutdown <- function(handle=NULL, all=FALSE) { @@ -263,12 +273,18 @@ } # shut down all worker processes using kill for (worker in workers) { + killWorkerProcess(worker) + } +} + +killWorkerProcess <- function (worker, quiet=F) { + if (! quiet) { cat(paste("Terminating worker", worker$pid, "of type", - worker$server, "\n")) - cmdString <- file.path(.find.package("Swift"), "exec/killtree &> /dev/null ") - killCmd <- paste(cmdString, worker$pid) - system(killCmd, wait=FALSE) + worker$server, "\n")) } + cmdString <- file.path(.find.package("Swift"), "exec/killtree &> /dev/null ") + killCmd <- paste(cmdString, worker$pid) + system(killCmd, wait=FALSE) } workerCount <- function (server) { Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 18:05:15 UTC (rev 4458) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 18:48:40 UTC (rev 4459) @@ -2,6 +2,9 @@ export TRAPEVENTS="EXIT 1 2 3 15" # Signals and conditions to trap +# * expands to nothing if no match +shopt -s nullglob + # Set the umask to prevent any access by other users: # there is no reason why any other user should need to look at # the temporary files, etc that we create @@ -44,7 +47,7 @@ # mkdir -p $LOGDIR # is done with the ssh command, below IDLETIMEOUT=$((60*60*240)) # 10 days: FIXME: make this a command line arg - + sshpids= for host in $(echo $hosts); do timestamp=$(date "+%Y.%m%d.%H%M%S") random=$(awk "BEGIN {printf \"%0.5d\", $RANDOM}") @@ -71,12 +74,17 @@ done - - echo Started workers from ssh processes $sshpids - echo $sshpids > $sshpidfile - if [ "$doack" = TRUE ]; then - echo done > ackfifo - doack=FALSE + if [ "$sshpids" = "" ]; then + echo No ssh workers successfully launched + if [ "$doack" = TRUE ]; then + echo 'Error: no ssh workers launched' > ackfifo + fi + else + echo Started workers from ssh processes $sshpids + echo $sshpids > $sshpidfile + if [ "$doack" = TRUE ]; then + echo ok > ackfifo + fi fi } @@ -374,11 +382,13 @@ then echo Started workers from batch job $(cat $jobidfile) if [ "$doack" = TRUE ]; then - echo done > ackfifo - doack=FALSE + echo ok > ackfifo fi else echo Batch queue submission failed, exiting. + if [ "$doack" = TRUE ]; then + echo 'Error: no ssh workers launched' > ackfifo + fi stdcleanup_start stdcleanup_end exit 1 @@ -575,7 +585,6 @@ # Standard clenuup actions function stdcleanup_start { # don't accept any more requests: unlink fifo from filesystem - echo stdcleanup_start 1&>2 if [ -p requestpipe ]; then rm requestpipe fi @@ -591,10 +600,6 @@ rm $SUBMIT_FILE fi fi - if [ "$doack" = TRUE ]; then - echo done > ackfifo - doack=FALSE - fi } echo Running in $trundir "(linked to $rundir)" @@ -627,6 +632,9 @@ } trap onexit $TRAPEVENTS exitcmd=onexit + if [ "$doack" = TRUE ]; then + echo ok > ackfifo + fi elif [ $server = local ]; then if [ $cores -eq 0 ]; then @@ -656,8 +664,7 @@ trap onexit $TRAPEVENTS exitcmd=onexit if [ "$doack" = TRUE ]; then - echo done > ackfifo - doack=FALSE + echo ok > ackfifo fi elif [ $server = ssh ]; then @@ -675,9 +682,10 @@ stdcleanup_start coasterservicepid="" # null: saved in case we go back to using coaster servers trap - $TRAPEVENTS - sshpids=$(cat $sshpidfile) + sshpids=$(cat $sshpidfile 2> /dev/null) + # echo Terminating worker processes $sshpids, starter $starterpid - for rpfile in $(ls -1 remotepid.*); do + for rpfile in $(echo remotepid.*); do rpgid=$(grep PGID= $rpfile | sed -e 's/PGID=//') rhost=$(echo $rpfile | sed -e 's/remotepid.//') #echo Based on $rpfile: terminating process process group $rpgid on $rhost Modified: SwiftApps/SwiftR/Swift/exec/start-swift-daemon =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift-daemon 2011-05-09 18:05:15 UTC (rev 4458) +++ SwiftApps/SwiftR/Swift/exec/start-swift-daemon 2011-05-09 18:48:40 UTC (rev 4459) @@ -33,5 +33,12 @@ echo ${workdir} # Wait for subprocess to let us know its ready -cat $ackfifo > /dev/null +res=`cat $ackfifo` rm $ackfifo +if [ "$res" = ok ]; then + echo $res + exit 0; +else + echo $res + exit 1 +fi From tga at ci.uchicago.edu Mon May 9 14:01:07 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 14:01:07 -0500 (CDT) Subject: [Swift-commit] r4460 - in SwiftApps/SwiftR/Swift: R exec Message-ID: <20110509190107.2C28D9CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 14:01:06 -0500 (Mon, 09 May 2011) New Revision: 4460 Modified: SwiftApps/SwiftR/Swift/R/Workers.R SwiftApps/SwiftR/Swift/exec/start-swift Log: tweaks for error cases. Modified: SwiftApps/SwiftR/Swift/R/Workers.R =================================================================== --- SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 18:48:40 UTC (rev 4459) +++ SwiftApps/SwiftR/Swift/R/Workers.R 2011-05-09 19:01:06 UTC (rev 4460) @@ -203,7 +203,7 @@ } # launch server. - out <- system(cmdString, intern=TRUE) + out <- suppressWarnings(system(cmdString, intern=TRUE)) if (length(out) != 3 && length(out) != 2) { stop(paste("Unexpected output from start-swift: '", paste(out, collapse="\n"), "'", "Launching may have failed")) @@ -226,7 +226,7 @@ } stat <- out[[3]] if (stat == "ok") { - cat("Started worker manager with pid ", pid, "\n") + cat("Started worker manager with pid", pid, "\n") # store worker info .swift.workers[[length(.swift.workers) + 1]] <<- output # add hook to ensure child process will be killed when Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 18:48:40 UTC (rev 4459) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:01:06 UTC (rev 4460) @@ -129,6 +129,9 @@ if [ _$GLOBUS_HOSTNAME = _ ]; then echo GLOBUS_HOSTNAME must be set to worker-reachable address of submit host for pbsf server mode. usage + if [ "$doack" = TRUE ]; then + echo ok > ackfifo + fi stdcleanup_start stdcleanup_end exit 1 @@ -387,7 +390,7 @@ else echo Batch queue submission failed, exiting. if [ "$doack" = TRUE ]; then - echo 'Error: no ssh workers launched' > ackfifo + echo "Error: batch submission failed: qsub returned $succ" > ackfifo fi stdcleanup_start stdcleanup_end From tga at ci.uchicago.edu Mon May 9 14:31:44 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 14:31:44 -0500 (CDT) Subject: [Swift-commit] r4461 - SwiftApps/SwiftR/Swift/exec Message-ID: <20110509193144.8E0819CFD0@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 14:31:44 -0500 (Mon, 09 May 2011) New Revision: 4461 Modified: SwiftApps/SwiftR/Swift/exec/start-swift Log: stop redundant signal with custom config Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:01:06 UTC (rev 4460) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:31:44 UTC (rev 4461) @@ -630,6 +630,7 @@ # have already set up tc.data and sites.xml files, just set #onexit function onexit { + trap - $TRAPEVENTS stdcleanup_start stdcleanup_end } From tga at ci.uchicago.edu Mon May 9 14:41:27 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Mon, 9 May 2011 14:41:27 -0500 (CDT) Subject: [Swift-commit] r4462 - SwiftApps/SwiftR/Swift/exec Message-ID: <20110509194127.CB16A9CFCB@svn.ci.uchicago.edu> Author: tga Date: 2011-05-09 14:41:27 -0500 (Mon, 09 May 2011) New Revision: 4462 Modified: SwiftApps/SwiftR/Swift/exec/start-swift Log: Bugfix: don't print unnecessary error message when swift is terminated. Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:31:44 UTC (rev 4461) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:41:27 UTC (rev 4462) @@ -633,6 +633,7 @@ trap - $TRAPEVENTS stdcleanup_start stdcleanup_end + exit 0 } trap onexit $TRAPEVENTS exitcmd=onexit From tga at ci.uchicago.edu Tue May 10 11:31:36 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Tue, 10 May 2011 11:31:36 -0500 (CDT) Subject: [Swift-commit] r4463 - in SwiftApps/SwiftR/Swift: R exec Message-ID: <20110510163136.B6F5C9CC99@svn.ci.uchicago.edu> Author: tga Date: 2011-05-10 11:31:36 -0500 (Tue, 10 May 2011) New Revision: 4463 Modified: SwiftApps/SwiftR/Swift/R/Apply.R SwiftApps/SwiftR/Swift/exec/rserver.swift SwiftApps/SwiftR/Swift/exec/start-swift Log: Refactored so that there is a response fifo created per request, to enable concurrent apply calls. Need to work out what is still preventing concurrent requests. Modified: SwiftApps/SwiftR/Swift/R/Apply.R =================================================================== --- SwiftApps/SwiftR/Swift/R/Apply.R 2011-05-09 19:41:27 UTC (rev 4462) +++ SwiftApps/SwiftR/Swift/R/Apply.R 2011-05-10 16:31:36 UTC (rev 4463) @@ -98,7 +98,7 @@ swiftServerDir = getWorkerDir(server) requestPipeName=file.path(swiftServerDir,"requestpipe") - resultPipeName=file.path(swiftServerDir,"resultpipe") + resultPipeName=file.path(reqdir,"resultpipe") # Try sending: this function will cause error if it fails sendServiceRequest(requestPipeName, reqdir, server, timeout=timeout) @@ -209,6 +209,9 @@ options(.swift.requestid=requestid) reqdir = file.path(requestdirbase, sprintf("R%.7d",requestid)) dir.create(reqdir,recursive=TRUE,showWarnings=FALSE,mode=kDIR_MODE) + + # Create a fifo that we can block on to get a response + system(paste("mkfifo", shQuote(file.path(reqdir, "resultpipe")))) return (reqdir) } Modified: SwiftApps/SwiftR/Swift/exec/rserver.swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/rserver.swift 2011-05-09 19:41:27 UTC (rev 4462) +++ SwiftApps/SwiftR/Swift/exec/rserver.swift 2011-05-10 16:31:36 UTC (rev 4463) @@ -14,17 +14,19 @@ stdout=@stout stderr=@sterr; } -app ack (external e[]) -{ -# bash "-c" "echo SIGNAL DONE >/dev/tty; echo done > /tmp/SwiftR/swiftserver/resultpipe"; - bashlocal "-c" @strcat("echo done > ",resultPipeName); -} - app passivate () { bash "-c" "echo dummy swift job;"; } +process_async(string runDir) { + external wait[]; + wait = apply(runDir); + + string resultPipeName = @strcat(runDir,"/resultpipe"); + fprintf(resultPipeName, "%kdone\n", wait); +} + (external e[]) apply (string runDir) { RData rcalls[] ; @@ -48,29 +50,16 @@ string pipedir = @arg("pipedir"); global string requestPipeName = @strcat(pipedir,"/requestpipe"); -global string resultPipeName = @strcat(pipedir,"/resultpipe"); iterate serially { boolean done; string dir; - # FIXME: read swiftserver dir via @args trace("top of loop: rserver waiting for input on", requestPipeName); dir = readData(requestPipeName); # Reads direct from this local pipe. Assumes Swift started in right dir. + if (dir=="done") { done=true; } else { done=false;} trace("rserver: got dir", dir); - external wait[]; - wait = apply(dir); - - if (dir=="done") { done=true; } else { done=false;} - - # file f<"/tmp/SwiftR/swiftserver/resultpipe">; - # f = writeData("completed\n"); # Doesnt work: runs as soon as the block is entered. - # want: tracef("%k completed\n", "my/responsepipe.fifo", wait); - # %k waits for wait to be fully closed; then sends formatted string to specified file(doing open, write, close). - - // ack(wait); - - fprintf(resultPipeName, "%kdone\n", wait); - + # fork off thread + process_async(dir); } until (done); Modified: SwiftApps/SwiftR/Swift/exec/start-swift =================================================================== --- SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-09 19:41:27 UTC (rev 4462) +++ SwiftApps/SwiftR/Swift/exec/start-swift 2011-05-10 16:31:36 UTC (rev 4463) @@ -617,8 +617,7 @@ # needed, and to copy in the R prelude for the R server processes (to # include for example the OpenMx library) NOTE: Both were done in older version of this script. -# rm -f requestpipe resultpipe -mkfifo requestpipe resultpipe +mkfifo requestpipe out=swift.stdouterr touch $out @@ -766,7 +765,8 @@ echo "Turn on keep work option to retain logs" fi - ( echo "error: swift exited unexpectedly with return code $exitcode" > resultpipe & + # TODO: resultpipe used togo somewhere need to handle some other way + ( echo "error: swift exited unexpectedly with return code $exitcode" > swift.error & echopid=$! sleep 5 kill $echopid From wozniak at ci.uchicago.edu Wed May 11 10:44:21 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Wed, 11 May 2011 10:44:21 -0500 (CDT) Subject: [Swift-commit] r4464 - trunk/src/org/griphyn/vdl/engine Message-ID: <20110511154421.035A79CFC8@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-11 10:44:20 -0500 (Wed, 11 May 2011) New Revision: 4464 Modified: trunk/src/org/griphyn/vdl/engine/Karajan.java Log: Unused import Modified: trunk/src/org/griphyn/vdl/engine/Karajan.java =================================================================== --- trunk/src/org/griphyn/vdl/engine/Karajan.java 2011-05-10 16:31:36 UTC (rev 4463) +++ trunk/src/org/griphyn/vdl/engine/Karajan.java 2011-05-11 15:44:20 UTC (rev 4464) @@ -11,7 +11,6 @@ import java.util.Collection; import java.util.HashMap; import java.util.HashSet; -import java.util.Iterator; import java.util.Map; import java.util.Set; import java.util.StringTokenizer; @@ -202,7 +201,7 @@ } private void processTypes(Program prog, VariableScope scope) throws CompilationException { - Types types = prog.getTypes(); + Types types = prog.getTypes(); if (types != null) { for (int i = 0; i < types.sizeOfTypeArray(); i++) { Type theType = types.getTypeArray(i); From wozniak at ci.uchicago.edu Wed May 11 10:45:03 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Wed, 11 May 2011 10:45:03 -0500 (CDT) Subject: [Swift-commit] r4465 - trunk/src/org/griphyn/vdl/karajan Message-ID: <20110511154503.6C1419CFC8@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-11 10:45:03 -0500 (Wed, 11 May 2011) New Revision: 4465 Modified: trunk/src/org/griphyn/vdl/karajan/Loader.java Log: Drop unused variable Modified: trunk/src/org/griphyn/vdl/karajan/Loader.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/Loader.java 2011-05-11 15:44:20 UTC (rev 4464) +++ trunk/src/org/griphyn/vdl/karajan/Loader.java 2011-05-11 15:45:03 UTC (rev 4465) @@ -193,7 +193,7 @@ arguments.add("-rlog:resume=" + ap.getStringValue(ARG_RESUME)); } ec.setArguments(arguments); - long start = System.currentTimeMillis(); + // long start = System.currentTimeMillis(); new HangChecker(stack).start(); ec.start(stack); ec.waitFor(); From hategan at ci.uchicago.edu Thu May 12 16:16:07 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Thu, 12 May 2011 16:16:07 -0500 (CDT) Subject: [Swift-commit] r4466 - trunk/src/org/griphyn/vdl/mapping Message-ID: <20110512211607.B56469CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-12 16:16:03 -0500 (Thu, 12 May 2011) New Revision: 4466 Modified: trunk/src/org/griphyn/vdl/mapping/RootDataNode.java Log: formatting Modified: trunk/src/org/griphyn/vdl/mapping/RootDataNode.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/RootDataNode.java 2011-05-11 15:45:03 UTC (rev 4465) +++ trunk/src/org/griphyn/vdl/mapping/RootDataNode.java 2011-05-12 21:16:03 UTC (rev 4466) @@ -45,7 +45,7 @@ while(i.hasNext()) { Map.Entry entry = (Map.Entry) i.next(); Object v = entry.getValue(); - if(v instanceof DSHandle && !( (DSHandle)v).isClosed()) { + if(v instanceof DSHandle && !((DSHandle) v).isClosed()) { waitingMapperParam = (DSHandle) v; waitingMapperParam.addListener(this); return; From hategan at ci.uchicago.edu Thu May 12 16:17:42 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Thu, 12 May 2011 16:17:42 -0500 (CDT) Subject: [Swift-commit] r4467 - in trunk/src/org/griphyn/vdl: karajan mapping Message-ID: <20110512211742.7D31D9CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-12 16:17:41 -0500 (Thu, 12 May 2011) New Revision: 4467 Modified: trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java Log: a better (hopefully) implementation of listeners Modified: trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java 2011-05-12 21:16:03 UTC (rev 4466) +++ trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java 2011-05-12 21:17:41 UTC (rev 4467) @@ -11,7 +11,6 @@ import org.globus.cog.karajan.stack.VariableNotFoundException; import org.globus.cog.karajan.stack.VariableStack; -import org.globus.cog.karajan.workflow.ExecutionException; import org.globus.cog.karajan.workflow.events.EventTargetPair; import org.globus.cog.karajan.workflow.futures.FutureEvaluationException; import org.globus.cog.karajan.workflow.futures.FutureIterator; @@ -19,18 +18,17 @@ import org.globus.cog.karajan.workflow.futures.FutureListener; import org.globus.cog.karajan.workflow.futures.FutureNotYetAvailable; import org.globus.cog.karajan.workflow.futures.ListenerStackPair; -import org.globus.cog.util.CopyOnWriteArrayList; import org.griphyn.vdl.mapping.DSHandle; import org.griphyn.vdl.mapping.DSHandleListener; public class ArrayIndexFutureList implements FutureList, DSHandleListener { private ArrayList keys; - private Map values; + private Map values; private boolean closed; - private CopyOnWriteArrayList listeners; + private ArrayList listeners; private FutureEvaluationException exception; - public ArrayIndexFutureList(DSHandle handle, Map values) { + public ArrayIndexFutureList(DSHandle handle, Map values) { this.values = values; keys = new ArrayList(); handle.addListener(this); @@ -93,7 +91,7 @@ public synchronized void addModificationAction(FutureListener target, VariableStack stack) { if (listeners == null) { - listeners = new CopyOnWriteArrayList(); + listeners = new ArrayList(); } listeners.add(new ListenerStackPair(target, stack)); @@ -102,22 +100,20 @@ } } - private synchronized void notifyListeners() { - if (listeners == null) { - return; + private void notifyListeners() { + ArrayList l; + synchronized (this) { + if (listeners == null) { + return; + } + + l = listeners; + listeners = null; } - Iterator i = listeners.iterator(); - try { - while (i.hasNext()) { - ListenerStackPair etp = i.next(); - i.remove(); - etp.listener.futureModified(this, etp.stack); - } + for (ListenerStackPair lsp : l) { + lsp.listener.futureModified(this, lsp.stack); } - finally { - listeners.release(); - } } public EventTargetPair[] getListenerEvents() { Modified: trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java 2011-05-12 21:16:03 UTC (rev 4466) +++ trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java 2011-05-12 21:17:41 UTC (rev 4467) @@ -4,10 +4,10 @@ package org.griphyn.vdl.karajan; import java.util.LinkedList; +import java.util.List; import org.globus.cog.karajan.stack.VariableNotFoundException; import org.globus.cog.karajan.stack.VariableStack; -import org.globus.cog.karajan.workflow.events.EventBus; import org.globus.cog.karajan.workflow.events.EventTargetPair; import org.globus.cog.karajan.workflow.futures.Future; import org.globus.cog.karajan.workflow.futures.FutureEvaluationException; @@ -62,20 +62,21 @@ } } - private synchronized void notifyListeners() { - if (listeners == null) { - return; + private void notifyListeners() { + List l; + synchronized(this) { + if (listeners == null) { + return; + } + + l = listeners; + listeners = null; + } + + for (ListenerStackPair lsp : l) { + WaitingThreadsMonitor.removeThread(lsp.stack); + lsp.listener.futureModified(DSHandleFutureWrapper.this, lsp.stack); } - while (!listeners.isEmpty()) { - final ListenerStackPair etp = listeners.removeFirst(); - WaitingThreadsMonitor.removeThread(etp.stack); - EventBus.post(new Runnable() { - public void run() { - etp.listener.futureModified(DSHandleFutureWrapper.this, etp.stack); - } - }); - } - listeners = null; } public synchronized int listenerCount() { Modified: trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java 2011-05-12 21:16:03 UTC (rev 4466) +++ trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java 2011-05-12 21:17:41 UTC (rev 4467) @@ -3,23 +3,18 @@ */ package org.griphyn.vdl.mapping; -import org.griphyn.vdl.karajan.Loader; - import java.util.ArrayList; import java.util.Collection; import java.util.HashMap; -import java.util.Iterator; -import java.util.LinkedList; import java.util.List; import java.util.Map; import org.apache.log4j.Logger; +import org.griphyn.vdl.karajan.Loader; +import org.griphyn.vdl.karajan.VDL2FutureException; import org.griphyn.vdl.type.Field; import org.griphyn.vdl.type.Type; import org.griphyn.vdl.type.Types; - -import org.griphyn.vdl.karajan.VDL2FutureException; - import org.griphyn.vdl.util.VDL2Config; @@ -573,17 +568,25 @@ } } - protected synchronized void notifyListeners() { - if (listeners != null) { - for (DSHandleListener listener : listeners) { - if (logger.isDebugEnabled()) { - logger.debug("Notifying listener \"" + listener - + "\" about \"" + getIdentifyingString() + "\""); - } - listener.handleClosed(this); + protected void notifyListeners() { + List l; + + synchronized(this) { + if (listeners == null) { + return; } + + l = listeners; listeners = null; } + + for (DSHandleListener listener : l) { + if (logger.isDebugEnabled()) { + logger.debug("Notifying listener \"" + listener + + "\" about \"" + getIdentifyingString() + "\""); + } + listener.handleClosed(this); + } } public String getIdentifier() { From hategan at ci.uchicago.edu Thu May 12 16:22:48 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Thu, 12 May 2011 16:22:48 -0500 (CDT) Subject: [Swift-commit] r4468 - trunk/src/org/griphyn/vdl/karajan/lib Message-ID: <20110512212248.7B5F19CFCB@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-12 16:22:39 -0500 (Thu, 12 May 2011) New Revision: 4468 Modified: trunk/src/org/griphyn/vdl/karajan/lib/AppStageins.java Log: logging adjustment Modified: trunk/src/org/griphyn/vdl/karajan/lib/AppStageins.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/AppStageins.java 2011-05-12 21:17:41 UTC (rev 4467) +++ trunk/src/org/griphyn/vdl/karajan/lib/AppStageins.java 2011-05-12 21:22:39 UTC (rev 4468) @@ -20,7 +20,7 @@ public class AppStageins extends AbstractSequentialWithArguments { static Logger logger = Logger.getLogger(AppStageins.class); - + public static final Arg JOBID = new Arg.Positional("jobid"); public static final Arg FILES = new Arg.Positional("files"); public static final Arg DIR = new Arg.Positional("dir"); @@ -50,7 +50,9 @@ .getDir() + "/" + file.getName(); String relpath = path.startsWith("/") ? path.substring(1) : path; - logger.debug("will stage in: " + relpath + " via: " + protocol); + if (logger.isDebugEnabled()) { + logger.debug("will stage in: " + relpath + " via: " + protocol); + } ArgUtil.getChannelReturn(stack, STAGEIN).append( makeList(protocol + "://" + file.getHost() + "/" + path, TypeUtil.toString(DIR.getValue(stack)) + "/" + relpath)); From lgadelha at ci.uchicago.edu Thu May 12 19:24:49 2011 From: lgadelha at ci.uchicago.edu (lgadelha at ci.uchicago.edu) Date: Thu, 12 May 2011 19:24:49 -0500 (CDT) Subject: [Swift-commit] r4469 - in provenancedb: . apps/oops Message-ID: <20110513002449.D802C9CCA4@svn.ci.uchicago.edu> Author: lgadelha Date: 2011-05-12 19:24:49 -0500 (Thu, 12 May 2011) New Revision: 4469 Modified: provenancedb/apps/oops/oops_extractor.sh provenancedb/pql_functions.sql provenancedb/prov-init.sql provenancedb/prov-to-sql.sh provenancedb/swift-prov-import-all-logs Log: Schema update. Modified: provenancedb/apps/oops/oops_extractor.sh =================================================================== --- provenancedb/apps/oops/oops_extractor.sh 2011-05-12 21:22:39 UTC (rev 4468) +++ provenancedb/apps/oops/oops_extractor.sh 2011-05-13 00:24:49 UTC (rev 4469) @@ -4,9 +4,10 @@ # PROVDB_HOME=~/provenancedb -PROTESTS_HOME=/gpfs/pads/oops/aashish/CASP +PROTESTS_HOME=/gpfs/pads/oops/aashish/CASP9 IMPORT_HOME=~/protests +cp $PROVDB_HOME/etc/provenance.config.ci $PROVDB_HOME/etc/provenance.config source $PROVDB_HOME/etc/provenance.config # provdb_imported records runs already imported to the provenance database @@ -39,13 +40,11 @@ LOG_FILENAME=$(ls *-*-*-*.log) WORKFLOW_ID=$(echo "select id from run where log_filename like '%$LOG_FILENAME%'" | $SQLCMD -t | awk '{print $1}') cd $IMPORT_HOME/swift-logs - echo "insert into annot_run_text (run_id, name, value) values ('$WORKFLOW_ID','oops_run_id','$OOPS_RUN_ID');" | $SQLCMD + $SQLCMD -c "insert into a_run_t (run_id, name, value) values ('$WORKFLOW_ID','oops_run_id','$OOPS_RUN_ID');" #extracts scientific parameters given as input to the workflow in file *.params. - echo "select file.id,file.filename from process, dataset_production, dataset_containment, file where process.id=dataset_production.process_id and dataset_production.dataset_id=out_id and file.id=dataset_containment.in_id and filename like '%.params' and process.name='PrepLoop' and process.run_id='$WORKFLOW_ID';" > query.sql; + $SQLCMD -t -A -F " " -c "select file.id,file.name from proc, ds_out, ds_cont, file where proc.id=ds_out.proc_id and ds_out.ds_id=out_id and file.id=ds_cont.in_id and file.name like '%.params' and proc.name='PrepLoop' and proc.run_id='$WORKFLOW_ID';" -o result.txt - $SQLCMD -t -A -F " " -f query.sql -o result.txt - DATASET_ID=$(awk '{if (NR==1) print $1}' result.txt) FILENAME=$(awk '{if (NR==1) print $2}' result.txt | sed 's/file:\/\/localhost\///g') @@ -55,26 +54,24 @@ NAME=$(echo $line | awk 'BEGIN { FS = "=" }; {print $1}') RIGHT=$(echo $line | awk 'BEGIN { FS = "=" }; {print $2}') if [ "$NAME" = "SAMPLE RANGE" ]; then - echo "insert into annot_dataset_text values ('$DATASET_ID', 'sample_range', '$RIGHT');" | $SQLCMD + $SQLCMD -c "insert into a_ds_t values ('$DATASET_ID', 'sample_range', '$RIGHT');" fi if [ "$NAME" = "RESTRAIN DISTANCE" ]; then VALUE1=$(echo $RIGHT | awk 'BEGIN { FS = "," }; {print $1}') VALUE2=$(echo $line | awk 'BEGIN { FS = "=" }; {print $2}' | awk 'BEGIN { FS = "," }; {print $2}') - echo "insert into annot_dataset_numeric values ('$DATASET_ID', 'restrain_distance_1', $VALUE1);" | $SQLCMD - echo "insert into annot_dataset_numeric values ('$DATASET_ID', 'restrain_distance_2', $VALUE2);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n values ('$DATASET_ID', 'restrain_distance_1', $VALUE1);" + $SQLCMD -c "insert into a_ds_n values ('$DATASET_ID', 'restrain_distance_2', $VALUE2);" fi if [ "$NAME" = "MAXIMUM NUMBER OF STEPS" ]; then - echo "insert into annot_dataset_numeric values ('$DATASET_ID', 'maximum_number_of_steps', $RIGHT);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n values ('$DATASET_ID', 'maximum_number_of_steps', $RIGHT);" fi done < $FILENAME #extracts length of the fasta sequence given as input to the workflow in file *.fasta. cd $IMPORT_HOME/swift-logs - echo "select file.id,file.filename from process, dataset_production, dataset_containment, file where process.id=dataset_production.process_id and dataset_production.dataset_id=out_id and file.id=dataset_containment.in_id and filename like '%.fasta' and process.name='PrepLoop' and process.run_id='$WORKFLOW_ID';" > query.sql; + $SQLCMD -t -A -F " " -c "select file.id,file.name from proc, ds_out, ds_cont, file where proc.id=ds_out.proc_id and ds_out.ds_id=out_id and file.id=ds_cont.in_id and file.name like '%.fasta' and proc.name='PrepLoop' and proc.run_id='$WORKFLOW_ID';" -o result.txt - $SQLCMD -t -A -F " " -f query.sql -o result.txt - DATASET_ID=$(awk '{if (NR==1) print $1}' result.txt) FILENAME=$(awk '{if (NR==1) print $2}' result.txt | sed 's/file:\/\/localhost\///g') @@ -82,7 +79,7 @@ if [ -n "$FILENAME" ]; then SEQLENGTH=$(awk '{if (NR==2) print $1}' $FILENAME | wc -c) - echo "insert into annot_dataset_numeric values ('$DATASET_ID', 'fasta_sequence_length', $SEQLENGTH);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n values ('$DATASET_ID', 'fasta_sequence_length', $SEQLENGTH);" fi # extracts scientific parameters given as output by the workflow in *.log. @@ -99,10 +96,8 @@ cd $IMPORT_HOME/swift-logs - echo "select file.id,file.filename from process, dataset_production, dataset_containment, file where process.id=dataset_production.process_id and dataset_production.dataset_id=out_id and file.id=dataset_containment.in_id and filename like '%.log' and process.name='LoopModel' and process.run_id='$WORKFLOW_ID';" > query.sql; + $SQLCMD -t -A -F " " -c "select file.id,file.name from proc, ds_out, ds_cont, file where proc.id=ds_out.proc_id and ds_out.ds_id=out_id and file.id=ds_cont.in_id and file.name like '%.log' and proc.name='LoopModel' and proc.run_id='$WORKFLOW_ID';" -o result.txt - $SQLCMD -t -A -F " " -f query.sql -o result.txt - cd $PROTESTS_HOME/$k/$i while read dataset filename; do @@ -110,28 +105,28 @@ while read token1 token2 token3 token4; do if [ "$token2" = "(Initial Energy:" ]; then initialenergy=$(echo $token3 | awk 'BEGIN { FS = "\)" }; {print $1}') - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'initial_energy', $initialenergy);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'initial_energy', $initialenergy);" fi if [ "$token1" = "Total" ] && [ "$token2" = "Function" ] && [ "$token3" = "Evaluations:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'total_function_evaluations', $token4);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'total_function_evaluations', $token4);" fi if [ "$token1" = "Increasing" ] && [ "$token2" = "transitions:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'accepted_increasing_transitions', $token3);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'accepted_increasing_transitions', $token3);" fi if [ "$token1" = "Decreasing" ] && [ "$token2" = "transitions:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'accepted_decreasing_transitions', $token3);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'accepted_decreasing_transitions', $token3);" fi if [ "$token1" = "Rejected" ] && [ "$token2" = "transitions:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'rejected_transitions', $token3);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'rejected_transitions', $token3);" fi if [ "$token1" = "Final" ] && [ "$token2" = "Energy:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'final_energy', $token3);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'final_energy', $token3);" fi if [ "$token1" = "Final" ] && [ "$token2" = "Temp:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'final_temp', $token3);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'final_temp', $token3);" fi if [ "$token1" = "Total" ] && [ "$token2" = "Running" ] && [ "$token3" = "Time:" ]; then - echo "insert into annot_dataset_numeric (dataset_id, name, value) values ('$dataset', 'total_running_time', $token4);" | $SQLCMD + $SQLCMD -c "insert into a_ds_n (ds_id, name, value) values ('$dataset', 'total_running_time', $token4);" fi done < $FILENAME done < $IMPORT_HOME/swift-logs/result.txt Modified: provenancedb/pql_functions.sql =================================================================== --- provenancedb/pql_functions.sql 2011-05-12 21:22:39 UTC (rev 4468) +++ provenancedb/pql_functions.sql 2011-05-13 00:24:49 UTC (rev 4469) @@ -4,37 +4,158 @@ -- SQL Functions -- lists variations in a parameter's value across workflows, for parameters that are in-memory variables +drop view in_mem_in cascade; -CREATE OR REPLACE FUNCTION compare_run_by_parameter(param_name VARCHAR) -RETURNS TABLE ( - run_id VARCHAR, - param_name VARCHAR, - value VARCHAR -) -AS $$ - SELECT process.workflow_id, ds_usage.param_name, variable.value - FROM variable, ds_usage, process - WHERE variable.id=ds_usage.dataset_id AND ds_usage.process_id=process.id AND - ds_usage.param_name=$1 - GROUP BY process.workflow_id, ds_usage.param_name, variable.value; -$$ LANGUAGE SQL; +create view in_mem_in as + select proc.run_id, proc.id as proc_id, + proc.name as proc_name, ds_in.ds_id, + ds_in.param, in_mem.value + from proc, ds_in, in_mem + where proc.id=ds_in.proc_id and ds_in.ds_id=in_mem.id; +drop view in_mem_out cascade; + +create view in_mem_out as + select proc.run_id, proc.id as proc_id, + proc.name as proc_name, ds_out.ds_id, + ds_out.param, in_mem.value + from proc, ds_out, in_mem + where proc.id=ds_out.proc_id and ds_out.ds_id=in_mem.id; + +drop view in_mem_use cascade; + +create view in_mem_use as + select * from in_mem_in + union + select * from in_mem_out; + +drop view file_in cascade; + +create view file_in as + select proc.run_id, proc.id as proc_id, + proc.name as proc_name, ds_in.ds_id, + ds_in.param, file.name as value + from proc, ds_in, file + where proc.id=ds_in.proc_id and ds_in.ds_id=file.id; + +drop view file_out cascade; + +create view file_out as + select proc.run_id, proc.id as proc_id, + proc.name as proc_name, ds_out.ds_id, + ds_out.param, file.name as value + from proc, ds_out, file + where proc.id=ds_out.proc_id and ds_out.ds_id=file.id; + +drop view file_use cascade; + +create view file_use as + select * from file_in + union + select * from file_out; + +drop view ds_use cascade; + +create view ds_use as + select * from in_mem_use + union + select * from file_use; + +drop view a_t cascade; + +create view a_t as + select run.id, a_run_t.name, a_run_t.value + from run, a_run_t + where run.id=a_run_t.run_id + union + select proc.run_id, a_proc_t.name, a_proc_t.value + from proc, a_proc_t + where proc.id=a_proc_t.proc_id + union + select ds_use.run_id, a_ds_t.name, a_ds_t.value + from ds_use, a_ds_t + where ds_use.ds_id=a_ds_t.ds_id; + +drop view a_n cascade; + +create view a_n as + select run.id, a_run_n.name, a_run_n.value + from run, a_run_n + where run.id=a_run_n.run_id + union + select proc.run_id, a_proc_n.name, a_proc_n.value + from proc, a_proc_n + where proc.id=a_proc_n.proc_id + union + select ds_use.run_id, a_ds_n.name, a_ds_n.value + from ds_use, a_ds_n + where ds_use.ds_id=a_ds_n.ds_id; + + + + +drop type compare_run_by_parameter_type cascade; +create type compare_run_by_parameter_type as (run_id varchar, param varchar, value varchar); + +create or replace function compare_run_by_parameter(param_name varchar) +returns setof compare_run_by_parameter_type +as $$ + select run_id, param, value + from ds_use + where param=$1; +$$ language sql; + +-- PostgreSQL >= 9.0 +-- CREATE OR REPLACE FUNCTION compare_run_by_parameter(param_name VARCHAR) +-- RETURNS TABLE ( +-- run_id VARCHAR, +-- param VARCHAR, +-- value VARCHAR +-- ) +-- AS $$ +-- SELECT proc.run_id, ds_out.param, in_mem.value +-- FROM in_mem, ds_out, proc +-- WHERE in_mem.id=ds_out.ds_id AND ds_out.proc_id=proc.id AND +-- ds_out.param=$1 +-- GROUP BY proc.run_id, ds_out.param, in_mem.value +-- UNION +-- SELECT proc.run_id, ds_in.param, in_mem.value +-- FROM in_mem, ds_in, proc +-- WHERE in_mem.id=ds_in.ds_id AND ds_in.proc_id=proc.id AND +-- ds_in.param=$1 +-- GROUP BY proc.run_id, ds_in.param, in_mem.value +--$$ LANGUAGE SQL; + +DROP TYPE compare_run_by_parameter_type2; +CREATE TYPE compare_run_by_parameter_type2 AS (run_id VARCHAR, param1 VARCHAR, value1 VARCHAR, param2 VARCHAR, value2 VARCHAR); + CREATE OR REPLACE FUNCTION compare_run_by_parameter(param_name1 VARCHAR, param_name2 VARCHAR) -RETURNS TABLE ( - workflow_id VARCHAR, - param_name1 VARCHAR, - value1 VARCHAR, - param_name2 VARCHAR, - value2 VARCHAR -) +RETURNS SETOF compare_run_by_parameter_type2 AS $$ SELECT * FROM compare_run_by_parameter($1) as t INNER JOIN compare_run_by_parameter($2) as s - USING (workflow_id); + USING (run_id); $$ LANGUAGE SQL; +--CREATE OR REPLACE FUNCTION compare_run_by_parameter(param_name1 VARCHAR, param_name2 VARCHAR) +--RETURNS TABLE ( +-- workflow_id VARCHAR, +-- param_name1 VARCHAR, +-- value1 VARCHAR, +-- param_name2 VARCHAR, +-- value2 VARCHAR +--) +--AS $$ +-- SELECT * +-- FROM compare_run_by_parameter($1) as t +-- INNER JOIN +-- compare_run_by_parameter($2) as s +-- USING (workflow_id); +--$$ LANGUAGE SQL; + + CREATE OR REPLACE FUNCTION compare_run_by_parameter(param_name1 VARCHAR, param_name2 VARCHAR, param_name3 VARCHAR) RETURNS TABLE ( workflow_id VARCHAR, @@ -80,6 +201,7 @@ WHERE workflow.id=annot_wf_num.id and annot_wf_num.name=$1 $$ LANGUAGE SQL; + CREATE OR REPLACE FUNCTION compare_run_by_annot_txt(name VARCHAR) RETURNS TABLE ( workflow_id VARCHAR, @@ -100,6 +222,7 @@ WHERE workflow.id=annot_wf_txt.id and annot_wf_txt.name=$1 $$ LANGUAGE SQL; + CREATE OR REPLACE FUNCTION compare_run_by_annot_bool(name VARCHAR) RETURNS TABLE ( workflow_id VARCHAR, @@ -121,6 +244,7 @@ WHERE workflow.id=annot_wf_bool.id and annot_wf_bool.name=$1 $$ LANGUAGE SQL; + -- correlate a parameter with workflow runtime statistics CREATE OR REPLACE FUNCTION correlate_param_runtime(param_name VARCHAR) RETURNS TABLE ( @@ -137,16 +261,7 @@ process.workflow_id=workflow.id AND ds_usage.param_name=$1 $$ LANGUAGE SQL; --- lists distinct processes by name in a workflow -CREATE OR REPLACE FUNCTION process_names(wf_id VARCHAR) -RETURNS SETOF VARCHAR AS $$ - SELECT DISTINCT(process.name) - FROM process - WHERE process.workflow_id=$1; -$$ LANGUAGE SQL; - -- recursive query to find ancestor entities in a provenance graph - CREATE OR REPLACE FUNCTION ancestors(varchar) RETURNS SETOF varchar AS $$ WITH RECURSIVE anc(ancestor,descendant) AS ( @@ -159,8 +274,8 @@ SELECT ancestor FROM anc $$ LANGUAGE SQL; + -- compare(, - CREATE OR REPLACE FUNCTION compare_run(VARIADIC args VARCHAR[]) RETURNS SETOF RECORD AS $$ DECLARE @@ -198,38 +313,3 @@ $$ LANGUAGE plpgsql; -CREATE OR REPLACE FUNCTION compare_run_print(VARIADIC args VARCHAR[]) -RETURNS VARCHAR AS $$ -DECLARE - i INTEGER; - q VARCHAR; - selectq VARCHAR; - fromq VARCHAR; - property VARCHAR; - property_type VARCHAR; - function_name VARCHAR; -BEGIN - selectq := 'SELECT *'; - FOR i IN array_lower(args, 1)..array_upper(args, 1) LOOP - property_type := split_part(args[i], '=', 1); - property := split_part(args[i], '=', 2); - CASE property_type - WHEN 'param_name' THEN - function_name := 'compare_run_by_parameter'; - WHEN 'annot_num' THEN - function_name := 'compare_run_by_annot_num'; - WHEN 'annot_txt' THEN - function_name := 'compare_run_by_annot_txt'; - WHEN 'annot_bool' THEN - function_name := 'compare_run_by_annot_bool'; - END CASE; - IF i = 1 THEN - fromq := function_name || '(''' || property || ''') as t' || i; - ELSE - fromq := fromq || ' INNER JOIN ' || function_name || '(''' || property || ''') as t' || i || ' USING (workflow_id)'; - END IF; - END LOOP; - q := selectq || ' FROM ' || fromq; - RETURN q; -END; -$$ LANGUAGE plpgsql; Modified: provenancedb/prov-init.sql =================================================================== --- provenancedb/prov-init.sql 2011-05-12 21:22:39 UTC (rev 4468) +++ provenancedb/prov-init.sql 2011-05-13 00:24:49 UTC (rev 4469) @@ -1,24 +1,25 @@ -- this is the schema definition used for the main relational provenance -- implementation (in both sqlite3 and postgres) - + drop table run cascade; -drop table process cascade; -drop table app_invocation cascade; -drop table app_execution cascade; -drop table runtime_info cascade; -drop table dataset cascade; +drop table proc cascade; +drop table app_inv cascade; +drop table app_exec cascade; +drop table rt_info cascade; +drop table ds cascade; drop table file cascade; -drop table in_memory cascade; -drop table dataset_containment cascade; -drop table dataset_consumption cascade; -drop table dataset_production cascade; -drop table annot_dataset_numeric cascade; -drop table annot_dataset_text cascade; -drop table annot_process_numeric cascade; -drop table annot_process_text cascade; -drop table annot_run_numeric cascade; -drop table annot_run_text cascade; +drop table in_mem cascade; +drop table ds_cont cascade; +drop table ds_in cascade; +drop table ds_out cascade; +drop table a_ds_n cascade; +drop table a_ds_t cascade; +drop table a_proc_n cascade; +drop table a_proc_t cascade; +drop table a_run_n cascade; +drop table a_run_t cascade; + -- run stores information about each script run log that has -- been seen by the importer: the log filename, swift version and import -- status. @@ -28,7 +29,8 @@ (id varchar(256) primary key, log_filename varchar(2048), swift_version varchar(16), - final_state varchar(16), + cog_version varchar(16), + final_state varchar(16), start_time numeric, duration numeric ); @@ -39,7 +41,7 @@ -- must be the case that the specific type table -- has an entry for this process. -- process types: internal, rootthread, execute, function, compound, scope, operator -create table process +create table proc (id varchar(256) primary key, type varchar(16), name varchar(256), -- in the case of an execute this refers to the transformation name in tc.data @@ -50,9 +52,9 @@ -- this gives information about each execute. -- each execute is identified by a unique URI. other information from -- swift logs is also stored here. an execute is an OPM process. -create table app_invocation - (id varchar(256) primary key references process (id) on delete cascade, - procedure_name varchar(256), -- name of the app procedure that invokes the transformation +create table app_inv + (id varchar(256) primary key references proc (id) on delete cascade, + proc_name varchar(256), -- name of the app procedure that invokes the transformation start_time numeric, duration numeric, final_state varchar(16), @@ -62,9 +64,9 @@ -- this gives information about each execute2, which is an attempt to -- perform an execution. the execute2 id is tied to per-execution-attempt -- information such as wrapper logs -create table app_execution +create table app_exec (id varchar(256) primary key, - app_invocation_id varchar(256) references app_invocation (id) on delete cascade, + app_inv_id varchar(256) references app_inv (id) on delete cascade, start_time numeric, duration numeric, final_state varchar(16), @@ -73,26 +75,26 @@ -- app execution runtime info extracted from the /proc filesystem (assumes the app executed -- in a Linux host) -create table runtime_info - ( app_execution_id varchar(256) references app_execution (id) on delete cascade, +create table rt_info + ( app_exec_id varchar(256) references app_exec (id) on delete cascade, tstamp numeric, cpu_usage numeric, max_phys_mem numeric, - max_virtual_mem numeric, - io_read_bytes numeric, - io_write_bytes numeric, - primary key (app_execution_id, tstamp) + max_virt_mem numeric, + io_read numeric, + io_write numeric, + primary key (app_exec_id, tstamp) ); -- ds stores all dataset identifiers. -create table dataset +create table ds (id varchar(256) primary key ); -- file stores the filename mapped to each dataset. create table file - ( id varchar(256) primary key references dataset (id) on delete cascade, - filename varchar(2048) + ( id varchar(256) primary key references ds (id) on delete cascade, + name varchar(2048) ); -- dataset_values stores the value for each dataset which is known to have @@ -100,8 +102,8 @@ -- to expose that value as an SQL type other than a string, and so (for -- example) SQL numerical operations should not be expected to work, even -- though the user knows that a particular dataset stores a numeric value. -create table in_memory - ( id varchar(256) primary key references dataset (id) on delete cascade, +create table in_mem + ( id varchar(256) primary key references ds (id) on delete cascade, value varchar(2048) ); @@ -112,9 +114,9 @@ -- constructors and accessors, rather than, or in addition to, -- a containment hierarchy. The relationship (such as array index or -- structure member name) should also be stored in this table. -create table dataset_containment - ( out_id varchar(256) references dataset (id) on delete cascade, - in_id varchar(256) references dataset (id) on delete cascade, +create table ds_cont + ( out_id varchar(256) references ds (id) on delete cascade, + in_id varchar(256) references ds (id) on delete cascade, primary key (out_id,in_id) ); @@ -123,98 +125,99 @@ -- in SwiftScript terms, the input and output parameters for each -- application procedure invocation; in OPM terms, the artificts which are -- input to and output from each process that is a Swift execution -create table dataset_consumption - (process_id varchar(256) references process(id) on delete cascade, - dataset_id varchar(256) references dataset(id) on delete cascade, - param_name varchar(256), -- the name of the parameter in this execute that +create table ds_in + (proc_id varchar(256) references proc(id) on delete cascade, + ds_id varchar(256) references ds(id) on delete cascade, + param varchar(256), -- the name of the parameter in this execute that -- this dataset was bound to. sometimes this must -- be contrived (for example, in positional varargs) - primary key (process_id,dataset_id,param_name) + primary key (proc_id,ds_id,param) ); -create table dataset_production - (process_id varchar(256) references process(id) on delete cascade, - dataset_id varchar(256) references dataset(id) on delete cascade, - param_name varchar(256), -- the name of the parameter in this execute that +create table ds_out + (proc_id varchar(256) references proc(id) on delete cascade, + ds_id varchar(256) references ds(id) on delete cascade, + param varchar(256), -- the name of the parameter in this execute that -- this dataset was bound to. sometimes this must -- be contrived (for example, in positional varargs) - primary key (process_id,dataset_id,param_name) + primary key (proc_id,ds_id,param) ); --- annotations -create table annot_dataset_numeric - ( dataset_id varchar(256) references dataset (id) on delete cascade, +-- annotations (_n: numeric, _t: text) +create table a_ds_n + ( ds_id varchar(256) references ds (id) on delete cascade, name varchar(256), value numeric, - primary key (dataset_id, name) + primary key (ds_id, name) ); -create table annot_dataset_text - ( dataset_id varchar(256) references dataset (id) on delete cascade, +create table a_ds_t + ( ds_id varchar(256) references ds (id) on delete cascade, name varchar(256), value varchar(2048), - primary key (dataset_id, name) + primary key (ds_id, name) ); -create table annot_process_numeric - ( process_id varchar(256) references process (id) on delete cascade, - name varchar(256), - value numeric, - primary key (process_id, name) +create table a_proc_n + ( proc_id varchar(256) references proc (id) on delete cascade, + name varchar(256), + value numeric, + primary key (proc_id, name) ); -create table annot_process_text - ( process_id varchar(256) references process (id) on delete cascade, - name varchar(256), - value varchar(2048), - primary key (process_id, name) +create table a_proc_t + ( proc_id varchar(256) references proc (id) on delete cascade, + name varchar(256), + value varchar(2048), + primary key (proc_id, name) ); -create table annot_run_numeric +create table a_run_n ( run_id varchar(256) references run (id) on delete cascade, - name varchar(256), - value numeric, + name varchar(256), + value numeric, primary key (run_id, name) ); -create table annot_run_text +create table a_run_t ( run_id varchar(256) references run (id) on delete cascade, - name varchar(256), - value varchar(2048), + name varchar(256), + value varchar(2048), primary key (run_id, name) ); -create view provenance_graph as - select process_id as parent,dataset_id as child from dataset_production +create view pgraph_edge as + select proc_id as parent,ds_id as child from ds_out union - select dataset_id as parent,process_id as child from dataset_consumption + select ds_id as parent,proc_id as child from ds_in union - select out_id as parent,in_id as child from dataset_containment; + select out_id as parent,in_id as child from ds_cont; +-- continue renaming from here CREATE VIEW run_date AS - SELECT id, log_filename, swift_version, final_state, + SELECT id, log_filename, swift_version, cog_version, final_state, to_timestamp(start_time) as start_time, duration FROM run; -CREATE VIEW annot_text AS +CREATE VIEW a_t AS SELECT * - FROM annot_run_text + FROM a_run_t UNION SELECT * - FROM annot_dataset_text + FROM a_ds_t UNION SELECT * - FROM annot_process_text; + FROM a_proc_t; -CREATE VIEW annot_numeric AS +CREATE VIEW a_n AS SELECT * - FROM annot_run_numeric + FROM a_run_n UNION SELECT * - FROM annot_dataset_numeric + FROM a_ds_n UNION SELECT * - FROM annot_process_numeric; + FROM a_proc_n; Modified: provenancedb/prov-to-sql.sh =================================================================== --- provenancedb/prov-to-sql.sh 2011-05-12 21:22:39 UTC (rev 4468) +++ provenancedb/prov-to-sql.sh 2011-05-13 00:24:49 UTC (rev 4469) @@ -8,23 +8,21 @@ export WF="${RUNID}" echo Generating SQL for $RUNID -rm -f tmp-u.sql tmp-ds.sql tmp-p.sql tmp-e.sql tmp-e2.sql tmp-dsu.sql tmp-dsc.sql tmp-f.sql tmp-v.sql tmp-import.sql import.sql extrainfo.sql fields.txt runtime.sql - # this gives a distinction between the root process for a workflow and the # workflow itself. perhaps better to model the workflow as a process -echo "INSERT INTO process (id, type, name, run_id) VALUES ('${WFID}0', 'rootthread', '$RUNID', '$WF');" > tmp-p.sql +$SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('${WFID}0', 'rootthread', '$RUNID', '$WF');" while read time duration thread localthread endstate tr_name scratch; do - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$thread', 'execute', '$tr_name', '$WF');" >> tmp-p.sql - echo "INSERT INTO app_invocation (id, start_time, duration, final_state, scratch) VALUES ('$thread', $time, $duration, '$endstate', '$scratch');" >> tmp-e.sql + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$thread', 'execute', '$tr_name', '$WF');" + $SQLCMD -c "INSERT INTO app_inv (id, start_time, duration, final_state, scratch) VALUES ('$thread', $time, $duration, '$endstate', '$scratch');" done < execute.global.event while read start_time duration globalid id endstate thread site scratch; do # cut off the last component of the thread, so that we end up at the # parent thread id which should correspond with the execute-level ID inv_id="$WFID$(echo $thread | sed 's/-[^-]*$//')" - echo "INSERT INTO app_execution (id, app_invocation_id, start_time, duration, final_state, site) VALUES ('$globalid', '$inv_id', $start_time, $duration, '$endstate', '$site');" >> tmp-e2.sql + $SQLCMD -c "INSERT INTO app_exec (id, app_inv_id, start_time, duration, final_state, site) VALUES ('$globalid', '$inv_id', $start_time, $duration, '$endstate', '$site');" done < execute2.global.event while read col1 col2 col3 col4 col5 thread name lhs rhs result; do @@ -42,22 +40,22 @@ result=$(echo $result | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$lhs');" >> tmp-ds.sql - echo "INSERT INTO dataset (id) VALUES ('$rhs');" >> tmp-ds.sql - echo "INSERT INTO dataset (id) VALUES ('$result');" >> tmp-ds.sql - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$operatorid', 'operator', '$name', '$WF');" >> tmp-p.sql - echo "INSERT INTO dataset_consumption (process_id, dataset_id, param_name) VALUES ('$operatorid', '$lhs', 'lhs');" >> tmp-dsu.sql - echo "INSERT INTO dataset_consumption (process_id, dataset_id, param_name) VALUES ('$operatorid', '$rhs', 'rhs');" >> tmp-dsu.sql - echo "INSERT INTO dataset_production (process_id, dataset_id, param_name) VALUES ('$operatorid', '$result', 'result');" >> tmp-dsu.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$lhs');" + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$rhs');" + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$result');" + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$operatorid', 'operator', '$name', '$WF');" + $SQLCMD -c "INSERT INTO ds_in (proc_id, ds_id, param) VALUES ('$operatorid', '$lhs', 'lhs');" + $SQLCMD -c "INSERT INTO ds_in (proc_id, ds_id, param) VALUES ('$operatorid', '$rhs', 'rhs');" + $SQLCMD -c "INSERT INTO ds_out (proc_id, ds_id, param) VALUES ('$operatorid', '$result', 'result');" done < operators.txt while read id name output; do if [ $version -le 3726 ]; then output=$(echo $output | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$output');" >> tmp-ds.sql - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$id', 'function', '$name', '$WF');" >> tmp-p.sql - echo "INSERT INTO dataset_production (process_id, dataset_id, param_name) VALUES ('$id', '$output', 'result');" >> tmp-dsu.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$output');" + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$id', 'function', '$name', '$WF');" + $SQLCMD -c "INSERT INTO ds_out (proc_id, ds_id, param) VALUES ('$id', '$output', 'result');" done < functions.txt while read id value; do @@ -67,13 +65,13 @@ value=$(echo $value | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$value');" >> tmp-ds.sql - echo "INSERT INTO dataset_consumption (process_id, dataset_id, param_name) VALUES ('$id', '$value', 'undefined');" >> tmp-dsu.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$value');" + $SQLCMD -c "INSERT INTO ds_in (proc_id, ds_id, param) VALUES ('$id', '$value', 'undefined');" done < function-inputs.txt while read thread appname; do - echo "UPDATE app_invocation SET procedure_name='$appname' WHERE id='$thread';" >> tmp-e.sql + $SQLCMD -c "UPDATE app_inv SET proc_name='$appname' WHERE id='$thread';" done < invocation-procedure-names.txt while read outer inner; do @@ -83,9 +81,9 @@ inner=$(echo $inner | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$outer');" >> tmp-ds.sql - echo "INSERT INTO dataset (id) VALUES ('$inner');" >> tmp-ds.sql - echo "INSERT INTO dataset_containment (out_id, in_id) VALUES ('$outer', '$inner');" >> tmp-dsc.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$outer');" + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$inner');" + $SQLCMD -c "INSERT INTO ds_cont (out_id, in_id) VALUES ('$outer', '$inner');" done < tie-containers.txt while read dataset filename; do @@ -94,8 +92,8 @@ dataset=$(echo $dataset | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$dataset');" >> tmp-ds.sql - echo "INSERT INTO file (id, filename) VALUES ('$dataset', '$filename');" >> tmp-f.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$dataset');" + $SQLCMD -c "INSERT INTO file (id, name) VALUES ('$dataset', '$filename');" done < dataset-filenames.txt while read dataset value; do @@ -104,13 +102,13 @@ dataset=$(echo $dataset | sed -e 's/tag:benc at ci.uchicago.edu,2008:swift://g') fi - echo "INSERT INTO dataset (id) VALUES ('$dataset');" >> tmp-ds.sql - echo "INSERT INTO in_memory (id, value) VALUES ('$dataset', '$value');" >> tmp-v.sql + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$dataset');" + $SQLCMD -c "INSERT INTO in_mem (id, value) VALUES ('$dataset', '$value');" done < dataset-values.txt while read start duration wfid rest; do - echo "UPDATE run SET start_time=$start WHERE id='$WF';" >> tmp-u.sql - echo "UPDATE run SET duration=$duration WHERE id='$WF';" >> tmp-u.sql + $SQLCMD -c "UPDATE run SET start_time=$start WHERE id='$WF';" + $SQLCMD -c "UPDATE run SET duration=$duration WHERE id='$WF';" done < workflow.event @@ -118,20 +116,20 @@ while read start duration thread final_state procname ; do if [ "$duration" != "last-event-line" ]; then compoundid=$WFID$thread - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$compoundid', 'compound', '$procname', '$WF');" >> tmp-p.sql + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$compoundid', 'compound', '$procname', '$WF');" fi done < compound.event while read start duration thread final_state procname ; do if [ "$duration" != "last-event-line" ]; then fqid=$WFID$thread - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$fqid', 'internal', '$procname', '$WF');" >> tmp-p.sql + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$fqid', 'internal', '$procname', '$WF');" fi done < internalproc.event while read t ; do thread="${WFID}$t" - echo "INSERT INTO process (id, type, name, run_id) VALUES ('$thread', 'scope', 'scope', '$WF');" >> tmp-p.sql + $SQLCMD -c "INSERT INTO proc (id, type, name, run_id) VALUES ('$thread', 'scope', 'scope', '$WF');" done < scopes.txt while read thread direction dataset variable rest; do @@ -141,57 +139,46 @@ fi if [ "$direction" == "input" ] ; then - table=dataset_consumption + table=ds_in else - table=dataset_production + table=ds_out fi - - echo "INSERT INTO dataset (id) VALUES ('$dataset');" >> tmp-ds.sql - echo "INSERT INTO $table (process_id, dataset_id, param_name) VALUES ('$thread', '$dataset', '$variable');" >> tmp-dsu.sql + + EXISTING=$($SQLCMD --tuples-only -c "select count(*) from ds where ds.id='$dataset';") + + if [ "$EXISTING" -eq "0" ]; then + $SQLCMD -c "INSERT INTO ds (id) VALUES ('$dataset');" + fi + $SQLCMD -c "INSERT INTO $table (proc_id, ds_id, param) VALUES ('$thread', '$dataset', '$variable');" done < tie-data-invocs.txt -cat tmp-ds.sql | sort | uniq >> import.sql -cat tmp-f.sql | sort | uniq >> import.sql -cat tmp-v.sql | sort | uniq >> import.sql -cat tmp-p.sql | sort | uniq >> import.sql -cat tmp-e.sql | sort | uniq >> import.sql -cat tmp-e2.sql | sort | uniq >> import.sql -cat tmp-dsu.sql | sort | uniq >> import.sql -cat tmp-dsc.sql | sort | uniq >> import.sql -cat tmp-import.sql | sort | uniq >> import.sql -cat tmp-u.sql | sort | uniq >> import.sql -echo Sending SQL to DB - -$SQLCMD < import.sql - -while read execute2_id extrainfo; do - echo $extrainfo | awk -F ";" '{ for (i = 1; i <= NF; i++) - print $i +if [ -f extrainfo.txt ]; then + while read execute2_id extrainfo; do + echo $extrainfo | awk -F ";" '{ for (i = 1; i <= NF; i++) + print $i }' | awk -F "=" '{ print $1 " " $2 }' | awk -F ":" '{ print $1 " " $2 }' > fields.txt - id=$($SQLCMD --tuples-only -c "select app_invocation_id from app_execution where id='$execute2_id';" | awk '{print $1}') - while read name type value; do - if [ "$type" = "num" ]; then - echo "INSERT INTO annot_process_numeric (id, name, value) VALUES ('$id', '$name', $value);" >> extrainfo.sql - fi - if [ "$type" = "txt" ]; then - echo "INSERT INTO annot_process_text (id, name, value) VALUES ('$id', '$name', '$value');" >> extrainfo.sql - fi - done < fields.txt -done < extrainfo.txt + id=$($SQLCMD --tuples-only -c "select app_inv_id from app_exec where id='$execute2_id';" | awk '{print $1}') + while read name type value; do + if [ "$type" = "num" ]; then + $SQLCMD -c "INSERT INTO a_proc_n (id, name, value) VALUES ('$id', '$name', $value);" + fi + if [ "$type" = "txt" ]; then + $SQLCMD -c "INSERT INTO a_proc_t (id, name, value) VALUES ('$id', '$name', '$value');" + fi + done < fields.txt + done < extrainfo.txt +fi -$SQLCMD < extrainfo.sql +if [ -f runtime.txt ]; then + while read execute2_id runtime; do + timestamp=$(echo $runtime | awk -F "," '{print $1}' | awk -F ":" '{print $2}') + cpu_usage=$(echo $runtime | awk -F "," '{print $2}' | awk -F ":" '{print $2}') + max_phys_mem=$(echo $runtime | awk -F "," '{print $3}' | awk -F ":" '{print $2}') + max_virtual_mem=$(echo $runtime | awk -F "," '{print $4}' | awk -F ":" '{print $2}') + io_read_bytes=$(echo $runtime | awk -F "," '{print $5}' | awk -F ":" '{print $2}') + io_write_bytes=$(echo $runtime | awk -F "," '{print $6}' | awk -F ":" '{print $2}') + $SQLCMD -c "INSERT INTO runtime_info (app_execution_id, tstamp, cpu_usage, max_phys_mem, max_virtual_mem, io_read_bytes, io_write_bytes) VALUES ('$execute2_id', $timestamp, $cpu_usage, $max_phys_mem, $max_virtual_mem, $io_read_bytes, $io_write_bytes);" + done < runtime.txt +fi -while read execute2_id runtime; do - timestamp=$(echo $runtime | awk -F "," '{print $1}' | awk -F ":" '{print $2}') - cpu_usage=$(echo $runtime | awk -F "," '{print $2}' | awk -F ":" '{print $2}') - max_phys_mem=$(echo $runtime | awk -F "," '{print $3}' | awk -F ":" '{print $2}') - max_virtual_mem=$(echo $runtime | awk -F "," '{print $4}' | awk -F ":" '{print $2}') - io_read_bytes=$(echo $runtime | awk -F "," '{print $5}' | awk -F ":" '{print $2}') - io_write_bytes=$(echo $runtime | awk -F "," '{print $6}' | awk -F ":" '{print $2}') - echo "INSERT INTO runtime_info (app_execution_id, tstamp, cpu_usage, max_phys_mem, max_virtual_mem, io_read_bytes, io_write_bytes) VALUES ('$execute2_id', $timestamp, $cpu_usage, $max_phys_mem, $max_virtual_mem, $io_read_bytes, $io_write_bytes);" >> runtime.sql -done < runtime.txt - -$SQLCMD < runtime.sql - -echo Finished sending SQL to DB - +echo Finished sending SQL to DB \ No newline at end of file Modified: provenancedb/swift-prov-import-all-logs =================================================================== --- provenancedb/swift-prov-import-all-logs 2011-05-12 21:22:39 UTC (rev 4468) +++ provenancedb/swift-prov-import-all-logs 2011-05-13 00:24:49 UTC (rev 4469) @@ -11,7 +11,7 @@ source $PROVDIR/etc/provenance.config export PATH=$PROVDIR:$PATH -# this generates a file with pairs like: +# this generates a file with tuples like: # swift-plot-log $LOGREPO everylog-vs-versions.data @@ -55,7 +55,7 @@ export WF="${RUNID}" - echo "INSERT INTO run (id, log_filename, swift_version, final_state) VALUES ('$WF','$filename','$version','$wfstatus');" | $SQLCMD + $SQLCMD -c "INSERT INTO run (id, log_filename, swift_version, cog_version, final_state) VALUES ('$WF','$filename','$version', '', '$wfstatus');" echo version $version in log file $filename echo ============= will import ============= From hategan at ci.uchicago.edu Fri May 13 15:19:45 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Fri, 13 May 2011 15:19:45 -0500 (CDT) Subject: [Swift-commit] r4470 - trunk/src/org/griphyn/vdl/karajan Message-ID: <20110513201945.77D809CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-13 15:19:45 -0500 (Fri, 13 May 2011) New Revision: 4470 Modified: trunk/src/org/griphyn/vdl/karajan/VDSTaskTransformer.java Log: reformatted Modified: trunk/src/org/griphyn/vdl/karajan/VDSTaskTransformer.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/VDSTaskTransformer.java 2011-05-13 00:24:49 UTC (rev 4469) +++ trunk/src/org/griphyn/vdl/karajan/VDSTaskTransformer.java 2011-05-13 20:19:45 UTC (rev 4470) @@ -132,10 +132,10 @@ String s = spec.getDirectory()+"/"+executable; l.set(0,s); } - } catch(IOException ioe) { + } + catch(IOException ioe) { throw new KarajanRuntimeException("Could not determine wrapper invocation mode", ioe); } - } protected abstract void applyTCEntry(Task task, Contact[] contacts); From hategan at ci.uchicago.edu Fri May 13 15:21:23 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Fri, 13 May 2011 15:21:23 -0500 (CDT) Subject: [Swift-commit] r4471 - in trunk/src/org/griphyn/vdl/karajan: . lib lib/cache Message-ID: <20110513202123.ADC2B9CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-13 15:21:23 -0500 (Fri, 13 May 2011) New Revision: 4471 Modified: trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java trunk/src/org/griphyn/vdl/karajan/FuturePairIterator.java trunk/src/org/griphyn/vdl/karajan/lib/FileCopier.java trunk/src/org/griphyn/vdl/karajan/lib/ThrottledParallelFor.java trunk/src/org/griphyn/vdl/karajan/lib/cache/File.java Log: updated to reflect removal of checked exception in Future.getValue() Modified: trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/ArrayIndexFutureList.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -84,7 +84,7 @@ return closed; } - public Object getValue() throws VariableNotFoundException { + public Object getValue() { return this; } Modified: trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/DSHandleFutureWrapper.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -33,7 +33,7 @@ return handle.isClosed(); } - public synchronized Object getValue() throws VariableNotFoundException { + public synchronized Object getValue() { Object value = handle.getValue(); if (value instanceof RuntimeException) { throw (RuntimeException) value; Modified: trunk/src/org/griphyn/vdl/karajan/FuturePairIterator.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/FuturePairIterator.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/FuturePairIterator.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -89,7 +89,7 @@ return array.isClosed(); } - public Object getValue() throws VariableNotFoundException { + public Object getValue() { return this; } Modified: trunk/src/org/griphyn/vdl/karajan/lib/FileCopier.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/FileCopier.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/lib/FileCopier.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -106,7 +106,7 @@ actions(); } - public Object getValue() throws ExecutionException { + public Object getValue() { return null; } Modified: trunk/src/org/griphyn/vdl/karajan/lib/ThrottledParallelFor.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/ThrottledParallelFor.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/lib/ThrottledParallelFor.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -285,7 +285,7 @@ public void fail(FutureEvaluationException e) { } - public Object getValue() throws ExecutionException { + public Object getValue() { return null; } Modified: trunk/src/org/griphyn/vdl/karajan/lib/cache/File.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/cache/File.java 2011-05-13 20:19:45 UTC (rev 4470) +++ trunk/src/org/griphyn/vdl/karajan/lib/cache/File.java 2011-05-13 20:21:23 UTC (rev 4471) @@ -175,7 +175,7 @@ public void fail(FutureEvaluationException e) { } - public Object getValue() throws ExecutionException { + public Object getValue() { return null; } From hategan at ci.uchicago.edu Fri May 13 18:11:48 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Fri, 13 May 2011 18:11:48 -0500 (CDT) Subject: [Swift-commit] r4472 - trunk/src/org/griphyn/vdl/mapping Message-ID: <20110513231148.6D9F49CCC9@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-13 18:11:48 -0500 (Fri, 13 May 2011) New Revision: 4472 Modified: trunk/src/org/griphyn/vdl/mapping/RootDataNode.java Log: fixed issue where odd exception would be thrown when using dependent mapper params Modified: trunk/src/org/griphyn/vdl/mapping/RootDataNode.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/RootDataNode.java 2011-05-13 20:21:23 UTC (rev 4471) +++ trunk/src/org/griphyn/vdl/mapping/RootDataNode.java 2011-05-13 23:11:48 UTC (rev 4472) @@ -58,9 +58,13 @@ } try { mapper = MapperFactory.getMapper(desc, params); + getField().setName(PARAM_PREFIX.getStringValue(mapper)); + // initialized means that this data has its mapper initialized + // this should be called before checkInputs because the latter + // may trigger calls to things that try to access this data node's + // mapper + initialized(); checkInputs(); - getField().setName(PARAM_PREFIX.getStringValue(mapper)); - initialized(); } catch (InvalidMapperException e) { throw new RuntimeException("InvalidMapperException caught in mapper initialization", e); @@ -202,10 +206,11 @@ public Mapper getMapper() { - if(initialized) { + if (initialized) { return mapper; - } else { - assert(waitingMapperParam != null); + } + else { + assert (waitingMapperParam != null); throw new VDL2FutureException(waitingMapperParam); } } @@ -220,6 +225,7 @@ } private void initialized() { - initialized=true; + initialized = true; + waitingMapperParam = null; } } From hategan at ci.uchicago.edu Fri May 13 18:12:32 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Fri, 13 May 2011 18:12:32 -0500 (CDT) Subject: [Swift-commit] r4473 - in trunk/src/org/griphyn/vdl: karajan/lib karajan/lib/swiftscript mapping Message-ID: <20110513231232.49F729CCC9@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-13 18:12:32 -0500 (Fri, 13 May 2011) New Revision: 4473 Modified: trunk/src/org/griphyn/vdl/karajan/lib/SwiftArg.java trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java trunk/src/org/griphyn/vdl/mapping/MappingParam.java Log: nicer representation of data in toString() Modified: trunk/src/org/griphyn/vdl/karajan/lib/SwiftArg.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/SwiftArg.java 2011-05-13 23:11:48 UTC (rev 4472) +++ trunk/src/org/griphyn/vdl/karajan/lib/SwiftArg.java 2011-05-13 23:12:32 UTC (rev 4473) @@ -22,7 +22,7 @@ public abstract class SwiftArg extends Arg { public static final Logger logger = Logger.getLogger(SwiftArg.class); - + public SwiftArg(String name, int index) { super(name, index); } Modified: trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java 2011-05-13 23:11:48 UTC (rev 4472) +++ trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java 2011-05-13 23:12:32 UTC (rev 4473) @@ -65,22 +65,27 @@ for (int i = 0; i < args.length; i++) { DSHandle handle = args[i]; VDLFunction.waitFor(stack, handle); - if(i!=0) buf.append(", "); + if (i != 0) { + buf.append(", "); + } buf.append(args[i]); } traceLogger.warn(buf); return null; } - public DSHandle swiftscript_strcat(VariableStack stack) - throws ExecutionException { - logger.debug(stack); + public DSHandle swiftscript_strcat(VariableStack stack) throws ExecutionException { + if (logger.isDebugEnabled()) { + logger.debug(stack); + } Object[] args = SwiftArg.VARGS.asArray(stack); int provid = VDLFunction.nextProvenanceID(); StringBuffer buf = new StringBuffer(); + for (int i = 0; i < args.length; i++) { buf.append(TypeUtil.toString(args[i])); } + DSHandle handle = new RootDataNode(Types.STRING); handle.setValue(buf.toString()); handle.closeShallow(); Modified: trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java 2011-05-13 23:11:48 UTC (rev 4472) +++ trunk/src/org/griphyn/vdl/mapping/AbstractDataNode.java 2011-05-13 23:12:32 UTC (rev 4473) @@ -85,24 +85,36 @@ * text description. */ public String toString() { - if (this.value != null && !(this.value instanceof Exception)) { - // special handling for ints... - if (this.getType().equals(Types.INT)) { - try { - Number n = (Number) this.getValue(); - return String.valueOf(n.intValue()); - } - catch (ClassCastException e) { - throw new RuntimeException( - "Internal type error. Value is not a Number for " - + getDisplayableName() + getPathFromRoot()); - } - } - else { - return this.value.toString(); - } + return toDisplayableString(); + } + + private String toDisplayableString() { + StringBuilder sb = new StringBuilder(); + sb.append(getDisplayableName()); + Path p = getPathFromRoot(); + if (!p.isEmpty()) { + sb.append("."); + sb.append(p.toString()); } - return getIdentifyingString(); + sb.append(":"); + sb.append(getType()); + sb.append(" = "); + if (value == null) { + sb.append("?"); + } + else if (value instanceof Throwable) { + sb.append(value.getClass().getName()); + } + else { + sb.append(value); + } + if (closed) { + sb.append(" - Closed"); + } + else { + sb.append(" - Open"); + } + return sb.toString(); } public String getIdentifyingString() { @@ -152,7 +164,7 @@ prefix = getRoot().getParam("prefix"); } if (prefix == null) { - prefix = "unnamed SwiftScript value"; + prefix = "?"; } return prefix; } Modified: trunk/src/org/griphyn/vdl/mapping/MappingParam.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/MappingParam.java 2011-05-13 23:11:48 UTC (rev 4472) +++ trunk/src/org/griphyn/vdl/mapping/MappingParam.java 2011-05-13 23:12:32 UTC (rev 4473) @@ -44,7 +44,7 @@ if (value instanceof DSHandle) { DSHandle handle = (DSHandle) value; checkHandle(handle); - return handle.toString(); + return handle.getValue().toString(); } else if (value == null) { if (!defSet) { @@ -65,7 +65,7 @@ if (value instanceof DSHandle) { DSHandle handle = (DSHandle) value; checkHandle(handle); - return handle.toString(); + return handle.getValue().toString(); } else if (value == null) { if (!defSet) { @@ -102,15 +102,17 @@ converted to a String as appropriate. */ public String getStringValue(Mapper mapper) { Object value = getValue(mapper); - if (value == null) + if (value == null) { return null; + } return String.valueOf(value); } public String getStringValue(Map params) { Object value = getValue(params); - if (value == null) + if (value == null) { return null; + } return String.valueOf(value); } From tga at ci.uchicago.edu Fri May 6 14:49:44 2011 From: tga at ci.uchicago.edu (tga at ci.uchicago.edu) Date: Fri, 6 May 2011 14:49:44 -0500 (CDT) Subject: [Swift-commit] r4451 - in SwiftApps/SwiftR: . design Message-ID: <20110506194944.0CFA59CFCB@svn.ci.uchicago.edu> Author: tga Date: 2011-05-06 14:49:43 -0500 (Fri, 06 May 2011) New Revision: 4451 Added: SwiftApps/SwiftR/design/ SwiftApps/SwiftR/design/coaster_worker.svg SwiftApps/SwiftR/design/localhost-modules.svg SwiftApps/SwiftR/design/worker-modules.svg Log: Rough sketches of SwiftR design Added: SwiftApps/SwiftR/design/coaster_worker.svg =================================================================== --- SwiftApps/SwiftR/design/coaster_worker.svg (rev 0) +++ SwiftApps/SwiftR/design/coaster_worker.svg 2011-05-06 19:49:43 UTC (rev 4451) @@ -0,0 +1,800 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + SwiftR - modules on worker machine + Coaster worker(number i of n) + Swift/exec/EvalRBatchPersistent.sh + Swift/exec/SwiftRServer.R + Runs Starts if worker directory not presentie. if worker not running yet + + R Worker Directory (one per coaster worker) + toR.fifo(named pipe) + fromR.fifo(named pipe) <temp_directory>/SwiftR/Rworkers/worker.<worker_process_id>/<worker_number>/ + + + Creates + + + Locations of:R call batchexported data R result batch Completionmessage + Coasters data storage + call batch 14(R data file) + call batch 42(R data file) + exported data(R data file) + exported data(R data file) + + Data staged toand from client + result batch 14(R data file) + + + + + Writes + Reads Persistent worker process to avoid startup overhead for each request + Added: SwiftApps/SwiftR/design/localhost-modules.svg =================================================================== --- SwiftApps/SwiftR/design/localhost-modules.svg (rev 0) +++ SwiftApps/SwiftR/design/localhost-modules.svg 2011-05-06 19:49:43 UTC (rev 4451) @@ -0,0 +1,1555 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + swiftInit()(Swift/R/Workers.R) Swift Server Launcher(Swift/exec/start-swift-daemon) Runs synchronously with system(), providing server parameters Swift server working directory and process idof monitor process Swift Server Monitor(Swift/exec/start-swift) Forks off script, providing server parameters + + Swift Server(Swift/exec/rserver.swift) Starts up + + Server working directory Createsand cleans up + swiftShutdown()(Swift/R/Workers.R) + Sends shutdown signal + + + + R Workspace(Swift/R/*.R) + + requestpipe(named pipe) + responsepipe(named pipe) Completion message Wait for request Request dir path + swiftapply()(Swift/R/Apply.R) + Wait for completion message + Completion message + + Request directory(one per apply call) + + + + call batch n + + + + call batch 1(R data file) + + + + + result batch n + + + + result batch 1(R data file) + + + write out functions and data and export manifest read apply results + + + Request dir path + + + + write results read request Swift manages a number of worker processes, dispatching requests for them to process.See worker managementdiagram for more info. SwiftR components running on local machine + swiftExport()(Swift/R/Export.R) + Temp storage + export manifest(text file) + + + exported(R data file) + exported (R data file) write data + read exporteddata files + Added: SwiftApps/SwiftR/design/worker-modules.svg =================================================================== --- SwiftApps/SwiftR/design/worker-modules.svg (rev 0) +++ SwiftApps/SwiftR/design/worker-modules.svg 2011-05-06 19:49:43 UTC (rev 4451) @@ -0,0 +1,788 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + SwiftR worker management (except manually configured servers) + Swift Server Monitor(Swift/exec/start-swift) + Swift Server(Swift/exec/rserver.swift) + + Request directory(one per apply call) + + + call batch n + + + + call batch 1(R data file) + + + + + result batch n + + + + result batch 1(R data file) + + + Temp storage + export manifest(text file) + R data file + R data file + + Starts up + + Coasters manager + Coaster worker + Coaster worker + Coaster worker + Start by forking, ssh, batch job, etcwith coaster URL + + + register as worker + + + + task to run + + + + + + data staging + + + + Coaster service URL + + From ketan at ci.uchicago.edu Sat May 14 22:34:27 2011 From: ketan at ci.uchicago.edu (ketan at ci.uchicago.edu) Date: Sat, 14 May 2011 22:34:27 -0500 (CDT) Subject: [Swift-commit] r4474 - in text: . escience11submission Message-ID: <20110515033427.758059CCB3@svn.ci.uchicago.edu> Author: ketan Date: 2011-05-14 22:34:27 -0500 (Sat, 14 May 2011) New Revision: 4474 Added: text/escience11submission/ text/escience11submission/IEEEabrv.bib text/escience11submission/IEEEexample.bib text/escience11submission/IEEEfull.bib text/escience11submission/IEEEtran.bst text/escience11submission/IEEEtran.cls text/escience11submission/IEEEtran2.tar.gz text/escience11submission/IEEEtranBST1.tar.gz text/escience11submission/IEEEtranS.bst text/escience11submission/IEEEtran_HOWTO.pdf text/escience11submission/IEEEtran_bst_HOWTO.pdf text/escience11submission/README text/escience11submission/bare_adv.tex text/escience11submission/bare_conf.tex text/escience11submission/bare_jrnl.tex text/escience11submission/bare_jrnl_compsoc.tex text/escience11submission/changelog.txt text/escience11submission/escience2011.aux text/escience11submission/escience2011.bbl text/escience11submission/escience2011.blg text/escience11submission/escience2011.log text/escience11submission/escience2011.pdf text/escience11submission/escience2011.tex Log: Added escience11 submission based on OOPS-SC09 Added: text/escience11submission/IEEEabrv.bib =================================================================== --- text/escience11submission/IEEEabrv.bib (rev 0) +++ text/escience11submission/IEEEabrv.bib 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,447 @@ + +IEEEabrv.bib +V1.12 (2007/01/11) +Copyright (c) 2002-2007 by Michael Shell +See: http://www.michaelshell.org/ +for current contact information. + +BibTeX bibliography string definitions of the ABBREVIATED titles of +IEEE journals and magazines and online publications. + +This file is designed for bibliography styles that require +abbreviated titles and is not for use in bibliographies that +require full-length titles. + +Support sites: +http://www.michaelshell.org/tex/ieeetran/ +http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +and/or +http://www.ieee.org/ + +Special thanks to Laura Hyslop and ken Rawson of IEEE for their help +in obtaining the information needed to compile this file. Also, +Volker Kuhlmann and Moritz Borgmann kindly provided some corrections +and additions. + +************************************************************************* +Legal Notice: +This code is offered as-is without any warranty either expressed or +implied; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE! +User assumes all risk. +In no event shall IEEE or any contributor to this code be liable for +any damages or losses, including, but not limited to, incidental, +consequential, or any other damages, resulting from the use or misuse +of any information contained here. + +All comments are the opinions of their respective authors and are not +necessarily endorsed by the IEEE. + +This work is distributed under the LaTeX Project Public License (LPPL) +( http://www.latex-project.org/ ) version 1.3, and may be freely used, +distributed and modified. A copy of the LPPL, version 1.3, is included +in the base LaTeX documentation of all distributions of LaTeX released +2003/12/01 or later. +Retain all contribution notices and credits. +** Modified files should be clearly indicated as such, including ** +** renaming them and changing author support contact information. ** + +File list of work: IEEEabrv.bib, IEEEfull.bib, IEEEexample.bib, + IEEEtran.bst, IEEEtranS.bst, IEEEtranSA.bst, + IEEEtranN.bst, IEEEtranSN.bst, IEEEtran_bst_HOWTO.pdf +************************************************************************* + + +USAGE: + +\bibliographystyle{mybstfile} +\bibliography{IEEEabrv,mybibfile} + +where the IEEE titles in the .bib database entries use the strings +defined here. e.g., + + + journal = IEEE_J_AC, + + +to yield "{IEEE} Trans. Automat. Contr." + + +IEEE uses abbreviated journal titles in their bibliographies - +this file is suitable for work that is to be submitted to the IEEE. + + +For work that requires full-length titles, you should use the full +titles provided in the companion file, IEEEfull.bib. + + +** NOTES ** + + 1. Journals have been grouped according to subject in order to make it + easier to locate and extract the definitions for related journals - + as most works use references that are confined to a single topic. + Magazines are listed in straight alphabetical order. + + 2. String names are closely based on IEEE's own internal acronyms. + + 3. Abbreviations follow IEEE's style. + + 4. Older, out-of-print IEEE titles are included (but not including titles + dating prior to IEEE's formation from the IRE and AIEE in 1963). + + 5. The following NEW/current journal definitions have been disabled because + their abbreviations have not yet been verified: + + STRING{IEEE_J_CBB = "{IEEE/ACM} Trans. Comput. Biology Bioinformatics"} + STRING{IEEE_J_CJECE = "Canadian J. Elect. Comput. Eng."} + STRING{IEEE_J_DSC = "{IEEE} Trans. Dependable Secure Comput."} + STRING{IEEE_O_DSO = "{IEEE} Distrib. Syst. Online"} + + 6. The following OLD journal definitions have been disabled because + their abbreviations have not yet been found/verified: + + STRING{IEEE_J_BCTV = "{IEEE} Trans. Broadcast Television Receivers"} + STRING{IEEE_J_EWS = "{IEEE} Trans. Eng. Writing Speech"} + +If you know what the proper abbreviation is for a string in #5 or #6 above, +email me and I will correct them in the next release. + + + + + +IEEE Journals + + + +aerospace and military + at STRING{IEEE_J_AES = "{IEEE} Trans. Aerosp. Electron. Syst."} + at STRING{IEEE_J_ANE = "{IEEE} Trans. Aerosp. Navig. Electron."} + at STRING{IEEE_J_ANNE = "{IEEE} Trans. Aeronaut. Navig. Electron."} + at STRING{IEEE_J_AS = "{IEEE} Trans. Aerosp."} + at STRING{IEEE_J_AIRE = "{IEEE} Trans. Airborne Electron."} + at STRING{IEEE_J_MIL = "{IEEE} Trans. Mil. Electron."} + + + +autos, transportation and vehicles (non-aerospace) + at STRING{IEEE_J_ITS = "{IEEE} Trans. Intell. Transp. Syst."} + at STRING{IEEE_J_VT = "{IEEE} Trans. Veh. Technol."} + at STRING{IEEE_J_VC = "{IEEE} Trans. Veh. Commun."} + + + +circuits, signals, systems, audio and controls + at STRING{IEEE_J_SPL = "{IEEE} Signal Process. Lett."} + at STRING{IEEE_J_ASSP = "{IEEE} Trans. Acoust., Speech, Signal Process."} + at STRING{IEEE_J_AU = "{IEEE} Trans. Audio"} + at STRING{IEEE_J_AUEA = "{IEEE} Trans. Audio Electroacoust."} + at STRING{IEEE_J_AC = "{IEEE} Trans. Autom. Control"} + at STRING{IEEE_J_CAS = "{IEEE} Trans. Circuits Syst."} + at STRING{IEEE_J_CASVT = "{IEEE} Trans. Circuits Syst. Video Technol."} + at STRING{IEEE_J_CASI = "{IEEE} Trans. Circuits Syst. {I}"} + at STRING{IEEE_J_CASII = "{IEEE} Trans. Circuits Syst. {II}"} +in 2004 CASI and CASII renamed part title to CASI_RP and CASII_EB, respectively. + at STRING{IEEE_J_CASI_RP = "{IEEE} Trans. Circuits Syst. {I}"} + at STRING{IEEE_J_CASII_EB = "{IEEE} Trans. Circuits Syst. {II}"} + at STRING{IEEE_J_CT = "{IEEE} Trans. Circuit Theory"} + at STRING{IEEE_J_CST = "{IEEE} Trans. Control Syst. Technol."} + at STRING{IEEE_J_SP = "{IEEE} Trans. Signal Process."} + at STRING{IEEE_J_SU = "{IEEE} Trans. Sonics Ultrason."} + at STRING{IEEE_J_SAP = "{IEEE} Trans. Speech Audio Process."} + at STRING{IEEE_J_UE = "{IEEE} Trans. Ultrason. Eng."} + at STRING{IEEE_J_UFFC = "{IEEE} Trans. Ultrason., Ferroelectr., Freq. Control"} + + + +communications + at STRING{IEEE_J_COML = "{IEEE} Commun. Lett."} + at STRING{IEEE_J_JSAC = "{IEEE} J. Sel. Areas Commun."} + at STRING{IEEE_J_COM = "{IEEE} Trans. Commun."} + at STRING{IEEE_J_COMT = "{IEEE} Trans. Commun. Technol."} + at STRING{IEEE_J_WCOM = "{IEEE} Trans. Wireless Commun."} + + + +components, packaging and manufacturing + at STRING{IEEE_J_ADVP = "{IEEE} Trans. Adv. Packag."} + at STRING{IEEE_J_CHMT = "{IEEE} Trans. Compon., Hybrids, Manuf. Technol."} + at STRING{IEEE_J_CPMTA = "{IEEE} Trans. Compon., Packag., Manuf. Technol. {A}"} + at STRING{IEEE_J_CPMTB = "{IEEE} Trans. Compon., Packag., Manuf. Technol. {B}"} + at STRING{IEEE_J_CPMTC = "{IEEE} Trans. Compon., Packag., Manuf. Technol. {C}"} + at STRING{IEEE_J_CAPT = "{IEEE} Trans. Compon. Packag. Technol."} + at STRING{IEEE_J_CAPTS = "{IEEE} Trans. Compon. Packag. Technol."} + at STRING{IEEE_J_CPART = "{IEEE} Trans. Compon. Parts"} + at STRING{IEEE_J_EPM = "{IEEE} Trans. Electron. Packag. Manuf."} + at STRING{IEEE_J_MFT = "{IEEE} Trans. Manuf. Technol."} + at STRING{IEEE_J_PHP = "{IEEE} Trans. Parts, Hybrids, Packag."} + at STRING{IEEE_J_PMP = "{IEEE} Trans. Parts, Mater., Packag."} + + + +CAD + at STRING{IEEE_J_TCAD = "{IEEE} J. Technol. Comput. Aided Design"} + at STRING{IEEE_J_CAD = "{IEEE} Trans. Comput.-Aided Design Integr. Circuits Syst."} + + + +coding, data, information, knowledge + at STRING{IEEE_J_IT = "{IEEE} Trans. Inf. Theory"} + at STRING{IEEE_J_KDE = "{IEEE} Trans. Knowl. Data Eng."} + + + +computers, computation, networking and software + at STRING{IEEE_J_C = "{IEEE} Trans. Comput."} + at STRING{IEEE_J_CAL = "{IEEE} Comput. Archit. Lett."} +disabled till definition is verified +STRING{IEEE_J_DSC = "{IEEE} Trans. Dependable Secure Comput."} + at STRING{IEEE_J_ECOMP = "{IEEE} Trans. Electron. Comput."} + at STRING{IEEE_J_EVC = "{IEEE} Trans. Evol. Comput."} + at STRING{IEEE_J_FUZZ = "{IEEE} Trans. Fuzzy Syst."} + at STRING{IEEE_J_IFS = "{IEEE} Trans. Inf. Forensics Security"} + at STRING{IEEE_J_MC = "{IEEE} Trans. Mobile Comput."} + at STRING{IEEE_J_NET = "{IEEE/ACM} Trans. Netw."} + at STRING{IEEE_J_NN = "{IEEE} Trans. Neural Netw."} + at STRING{IEEE_J_PDS = "{IEEE} Trans. Parallel Distrib. Syst."} + at STRING{IEEE_J_SE = "{IEEE} Trans. Softw. Eng."} + + + +computer graphics, imaging, and multimedia + at STRING{IEEE_J_JDT = "{IEEE/OSA} J. Display Technol."} + at STRING{IEEE_J_IP = "{IEEE} Trans. Image Process."} + at STRING{IEEE_J_MM = "{IEEE} Trans. Multimedia"} + at STRING{IEEE_J_VCG = "{IEEE} Trans. Vis. Comput. Graphics"} + + + +cybernetics, ergonomics, robots, man-machine, and automation + at STRING{IEEE_J_ASE = "{IEEE} Trans. Autom. Sci. Eng."} + at STRING{IEEE_J_JRA = "{IEEE} J. Robot. Autom."} + at STRING{IEEE_J_HFE = "{IEEE} Trans. Hum. Factors Electron."} + at STRING{IEEE_J_MMS = "{IEEE} Trans. Man-Mach. Syst."} + at STRING{IEEE_J_PAMI = "{IEEE} Trans. Pattern Anal. Mach. Intell."} +in 1989 JRA became RA +in August 2004, RA split into ASE and RO + at STRING{IEEE_J_RA = "{IEEE} Trans. Robot. Autom."} + at STRING{IEEE_J_RO = "{IEEE} Trans. Robot."} + at STRING{IEEE_J_SMC = "{IEEE} Trans. Syst., Man, Cybern."} + at STRING{IEEE_J_SMCA = "{IEEE} Trans. Syst., Man, Cybern. {A}"} + at STRING{IEEE_J_SMCB = "{IEEE} Trans. Syst., Man, Cybern. {B}"} + at STRING{IEEE_J_SMCC = "{IEEE} Trans. Syst., Man, Cybern. {C}"} + at STRING{IEEE_J_SSC = "{IEEE} Trans. Syst. Sci. Cybern."} + + + +earth, wind, fire and water + at STRING{IEEE_J_GE = "{IEEE} Trans. Geosci. Electron."} + at STRING{IEEE_J_GRS = "{IEEE} Trans. Geosci. Remote Sens."} + at STRING{IEEE_J_GRSL = "{IEEE} Geosci. Remote Sens. Lett."} + at STRING{IEEE_J_OE = "{IEEE} J. Ocean. Eng."} + + + +education, engineering, history, IEEE, professional +disabled till definition is verified +STRING{IEEE_J_CJECE = "Canadian J. Elect. Comput. Eng."} + at STRING{IEEE_J_PROC = "Proc. {IEEE}"} + at STRING{IEEE_J_EDU = "{IEEE} Trans. Educ."} + at STRING{IEEE_J_EM = "{IEEE} Trans. Eng. Manag."} +disabled till definition is verified +STRING{IEEE_J_EWS = "{IEEE} Trans. Eng. Writing Speech"} + at STRING{IEEE_J_PC = "{IEEE} Trans. Prof. Commun."} + + + +electromagnetics, antennas, EMI, magnetics and microwave + at STRING{IEEE_J_AWPL = "{IEEE} Antennas Wireless Propag. Lett."} + at STRING{IEEE_J_MGWL = "{IEEE} Microw. Guided Wave Lett."} +IEEE seems to want "Compon." here, not "Comp." + at STRING{IEEE_J_MWCL = "{IEEE} Microw. Wireless Compon. Lett."} + at STRING{IEEE_J_AP = "{IEEE} Trans. Antennas Propag."} + at STRING{IEEE_J_EMC = "{IEEE} Trans. Electromagn. Compat."} + at STRING{IEEE_J_MAG = "{IEEE} Trans. Magn."} + at STRING{IEEE_J_MTT = "{IEEE} Trans. Microw. Theory Tech."} + at STRING{IEEE_J_RFI = "{IEEE} Trans. Radio Freq. Interference"} + at STRING{IEEE_J_TJMJ = "{IEEE} Transl. J. Magn. Jpn."} + + + +energy and power + at STRING{IEEE_J_EC = "{IEEE} Trans. Energy Convers."} + at STRING{IEEE_J_PEL = "{IEEE} Power Electron. Lett."} + at STRING{IEEE_J_PWRAS = "{IEEE} Trans. Power App. Syst."} + at STRING{IEEE_J_PWRD = "{IEEE} Trans. Power Del."} + at STRING{IEEE_J_PWRE = "{IEEE} Trans. Power Electron."} + at STRING{IEEE_J_PWRS = "{IEEE} Trans. Power Syst."} + + + +industrial, commercial and consumer + at STRING{IEEE_J_APPIND = "{IEEE} Trans. Appl. Ind."} + at STRING{IEEE_J_BC = "{IEEE} Trans. Broadcast."} +disabled till definition is verified +STRING{IEEE_J_BCTV = "{IEEE} Trans. Broadcast Television Receivers"} + at STRING{IEEE_J_CE = "{IEEE} Trans. Consum. Electron."} + at STRING{IEEE_J_IE = "{IEEE} Trans. Ind. Electron."} + at STRING{IEEE_J_IECI = "{IEEE} Trans. Ind. Electron. Contr. Instrum."} + at STRING{IEEE_J_IA = "{IEEE} Trans. Ind. Appl."} + at STRING{IEEE_J_IGA = "{IEEE} Trans. Ind. Gen. Appl."} + at STRING{IEEE_J_IINF = "{IEEE} Trans. Ind. Informat."} + at STRING{IEEE_J_PSE = "{IEEE} J. Product Safety Eng."} + + + +instrumentation and measurement + at STRING{IEEE_J_IM = "{IEEE} Trans. Instrum. Meas."} + + + +insulation and materials + at STRING{IEEE_J_JEM = "{IEEE/TMS} J. Electron. Mater."} + at STRING{IEEE_J_DEI = "{IEEE} Trans. Dielectr. Electr. Insul."} + at STRING{IEEE_J_EI = "{IEEE} Trans. Electr. Insul."} + + + +mechanical + at STRING{IEEE_J_MECH = "{IEEE/ASME} Trans. Mechatronics"} + at STRING{IEEE_J_MEMS = "J. Microelectromech. Syst."} + + + +medical and biological + at STRING{IEEE_J_BME = "{IEEE} Trans. Biomed. Eng."} +Note: The B-ME journal later dropped the hyphen and became the BME. + at STRING{IEEE_J_B-ME = "{IEEE} Trans. Bio-Med. Eng."} + at STRING{IEEE_J_BMELC = "{IEEE} Trans. Bio-Med. Electron."} +disabled till definition is verified +STRING{IEEE_J_CBB = "{IEEE/ACM} Trans. Comput. Biology Bioinformatics"} + at STRING{IEEE_J_ITBM = "{IEEE} Trans. Inf. Technol. Biomed."} + at STRING{IEEE_J_ME = "{IEEE} Trans. Med. Electron."} + at STRING{IEEE_J_MI = "{IEEE} Trans. Med. Imag."} + at STRING{IEEE_J_NB = "{IEEE} Trans. Nanobiosci."} + at STRING{IEEE_J_NSRE = "{IEEE} Trans. Neural Syst. Rehabil. Eng."} + at STRING{IEEE_J_RE = "{IEEE} Trans. Rehabil. Eng."} + + + + optics, lightwave and photonics + at STRING{IEEE_J_PTL = "{IEEE} Photon. Technol. Lett."} + at STRING{IEEE_J_JLT = "J. Lightw. Technol."} + + + +physics, electrons, nanotechnology, nuclear and quantum electronics + at STRING{IEEE_J_EDL = "{IEEE} Electron Device Lett."} + at STRING{IEEE_J_JQE = "{IEEE} J. Quantum Electron."} + at STRING{IEEE_J_JSTQE = "{IEEE} J. Sel. Topics Quantum Electron."} + at STRING{IEEE_J_ED = "{IEEE} Trans. Electron Devices"} + at STRING{IEEE_J_NANO = "{IEEE} Trans. Nanotechnol."} + at STRING{IEEE_J_NS = "{IEEE} Trans. Nucl. Sci."} + at STRING{IEEE_J_PS = "{IEEE} Trans. Plasma Sci."} + + + +reliability +IEEE seems to want "Mat." here, not "Mater." + at STRING{IEEE_J_DMR = "{IEEE} Trans. Device Mater. Rel."} + at STRING{IEEE_J_R = "{IEEE} Trans. Rel."} + + + +semiconductors, superconductors, electrochemical and solid state + at STRING{IEEE_J_ESSL = "{IEEE/ECS} Electrochem. Solid-State Lett."} + at STRING{IEEE_J_JSSC = "{IEEE} J. Solid-State Circuits"} + at STRING{IEEE_J_ASC = "{IEEE} Trans. Appl. Supercond."} + at STRING{IEEE_J_SM = "{IEEE} Trans. Semicond. Manuf."} + + + +sensors + at STRING{IEEE_J_SENSOR = "{IEEE} Sensors J."} + + + +VLSI + at STRING{IEEE_J_VLSI = "{IEEE} Trans. {VLSI} Syst."} + + + + + + +IEEE Magazines + + + + at STRING{IEEE_M_AES = "{IEEE} Aerosp. Electron. Syst. Mag."} + at STRING{IEEE_M_HIST = "{IEEE} Ann. Hist. Comput."} + at STRING{IEEE_M_AP = "{IEEE} Antennas Propag. Mag."} + at STRING{IEEE_M_ASSP = "{IEEE} {ASSP} Mag."} + at STRING{IEEE_M_CD = "{IEEE} Circuits Devices Mag."} + at STRING{IEEE_M_CAS = "{IEEE} Circuits Syst. Mag."} + at STRING{IEEE_M_COM = "{IEEE} Commun. Mag."} + at STRING{IEEE_M_COMSOC = "{IEEE} Commun. Soc. Mag."} + at STRING{IEEE_M_CIM = "{IEEE} Comput. Intell. Mag."} +CSEM changed to CSE in 1999 + at STRING{IEEE_M_CSE = "{IEEE} Comput. Sci. Eng."} + at STRING{IEEE_M_CSEM = "{IEEE} Comput. Sci. Eng. Mag."} + at STRING{IEEE_M_C = "{IEEE} Computer"} + at STRING{IEEE_M_CAP = "{IEEE} Comput. Appl. Power"} + at STRING{IEEE_M_CGA = "{IEEE} Comput. Graph. Appl."} + at STRING{IEEE_M_CONC = "{IEEE} Concurrency"} + at STRING{IEEE_M_CS = "{IEEE} Control Syst. Mag."} + at STRING{IEEE_M_DTC = "{IEEE} Des. Test. Comput."} + at STRING{IEEE_M_EI = "{IEEE} Electr. Insul. Mag."} + at STRING{IEEE_M_ETR = "{IEEE} ElectroTechnol. Rev."} + at STRING{IEEE_M_EMB = "{IEEE} Eng. Med. Biol. Mag."} + at STRING{IEEE_M_EMR = "{IEEE} Eng. Manag. Rev."} + at STRING{IEEE_M_EXP = "{IEEE} Expert"} + at STRING{IEEE_M_IA = "{IEEE} Ind. Appl. Mag."} + at STRING{IEEE_M_IM = "{IEEE} Instrum. Meas. Mag."} + at STRING{IEEE_M_IS = "{IEEE} Intell. Syst."} + at STRING{IEEE_M_IC = "{IEEE} Internet Comput."} + at STRING{IEEE_M_ITP = "{IEEE} {IT} Prof."} + at STRING{IEEE_M_MICRO = "{IEEE} Micro"} + at STRING{IEEE_M_MW = "{IEEE} Microw. Mag."} + at STRING{IEEE_M_MM = "{IEEE} Multimedia"} + at STRING{IEEE_M_NET = "{IEEE} Netw."} +IEEE's editorial manual lists "Pers. Commun.", +but "Personal Commun. Mag." seems to be what is used in the journals + at STRING{IEEE_M_PCOM = "{IEEE} Personal Commun. Mag."} + at STRING{IEEE_M_POT = "{IEEE} Potentials"} +CAP and PER merged to form PE in 2003 + at STRING{IEEE_M_PE = "{IEEE} Power Energy Mag."} + at STRING{IEEE_M_PER = "{IEEE} Power Eng. Rev."} + at STRING{IEEE_M_PVC = "{IEEE} Pervasive Comput."} + at STRING{IEEE_M_RA = "{IEEE} Robot. Autom. Mag."} + at STRING{IEEE_M_SAP = "{IEEE} Security Privacy"} + at STRING{IEEE_M_SP = "{IEEE} Signal Process. Mag."} + at STRING{IEEE_M_S = "{IEEE} Softw."} + at STRING{IEEE_M_SPECT = "{IEEE} Spectr."} + at STRING{IEEE_M_TS = "{IEEE} Technol. Soc. Mag."} + at STRING{IEEE_M_VT = "{IEEE} Veh. Technol. Mag."} + at STRING{IEEE_M_WC = "{IEEE} Wireless Commun. Mag."} + at STRING{IEEE_M_TODAY = "Today's Engineer"} + + + + + + +IEEE Online Publications + + + + at STRING{IEEE_O_CSTO = "{IEEE} Commun. Surveys Tuts."} +disabled till definition is verified +STRING{IEEE_O_DSO = "{IEEE} Distrib. Syst. Online"} + + + + + +-- +EOF Added: text/escience11submission/IEEEexample.bib =================================================================== --- text/escience11submission/IEEEexample.bib (rev 0) +++ text/escience11submission/IEEEexample.bib 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,1190 @@ + +IEEEexample.bib +V1.12 (2007/01/11) +Copyright (c) 2002-2007 by Michael Shell +See: http://www.michaelshell.org/ +for current contact information. + +This is an example BibTeX database for the official IEEEtran.bst +BibTeX style file. + +Some entries call strings that are defined in the IEEEabrv.bib file. +Therefore, IEEEabrv.bib should be loaded prior to this file. +Usage: + +\bibliographystyle{./IEEEtran} +\bibliography{./IEEEabrv,./IEEEexample} + + +Support sites: +http://www.michaelshell.org/tex/ieeetran/ +http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +and/or +http://www.ieee.org/ + +************************************************************************* +Legal Notice: +This code is offered as-is without any warranty either expressed or +implied; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE! +User assumes all risk. +In no event shall IEEE or any contributor to this code be liable for +any damages or losses, including, but not limited to, incidental, +consequential, or any other damages, resulting from the use or misuse +of any information contained here. + +All comments are the opinions of their respective authors and are not +necessarily endorsed by the IEEE. + +This work is distributed under the LaTeX Project Public License (LPPL) +( http://www.latex-project.org/ ) version 1.3, and may be freely used, +distributed and modified. A copy of the LPPL, version 1.3, is included +in the base LaTeX documentation of all distributions of LaTeX released +2003/12/01 or later. +Retain all contribution notices and credits. +** Modified files should be clearly indicated as such, including ** +** renaming them and changing author support contact information. ** + +File list of work: IEEEabrv.bib, IEEEfull.bib, IEEEexample.bib, + IEEEtran.bst, IEEEtranS.bst, IEEEtranSA.bst, + IEEEtranN.bst, IEEEtranSN.bst, IEEEtran_bst_HOWTO.pdf +************************************************************************* + + +Note that, because the example references were taken from actual IEEE +publications, these examples do not always contain the full amount +of information that may be desirable (for use with other BibTeX styles). +In particular, full names (not abbreviated with initials) should be +entered whenever possible as some (non-IEEE) bibliography styles use +full names. IEEEtran.bst will automatically abbreviate when it encounters +full names. + + + + +references for the IEEEtran.bst documentation +IEEEtran homepage + at electronic{IEEEhowto:IEEEtranpage, + author = "Michael Shell", + title = "{IEEE}tran Homepage", + url = "http://www.michaelshell.org/tex/ieeetran/", + year = "2007" +} + + +the distribution site for IEEEtran.bst + at electronic{IEEEexample:shellCTANpage, + author = "Michael Shell", + title = "{IEEE}tran Webpage on {CTAN}", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/", + year = "2007" +} + + +the IEEE website +sort key is needed for sorting styles + at electronic{IEEEexample:IEEEwebsite, + title = "The {IEEE} Website", + url = "http://www.ieee.org/", + year = "2007", + key = "IEEE" +} + + +The BibTeX user's guide. +The filename could have been put in the URL instead. But, there might +be other interesting things for the user in the same directory - and +the filename might change before the directory that contains it. + at electronic{IEEEexample:bibtexuser, + author = "Oren Patashnik", + title = "{{\BibTeX}}ing", + howpublished = "{btxdoc.pdf}", + url = "http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/", + month = feb, + year = "1988" +} + + +The BibTeX style designer's guide. + at electronic{IEEEexample:bibtexdesign, + author = "Oren Patashnik", + title = "Designing {{\BibTeX}} Styles", + howpublished = "{btxhak.pdf}", + url = "http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/", + month = feb, + year = "1988" +} + + +A comprehensive BibTeX tutorial. + at electronic{IEEEexample:tamethebeast, + author = "Nicolas Markey", + title = "Tame the BeaST --- The B to X of {{\BibTeX}}", + url = "http://tug.ctan.org/tex-archive/info/bibtex/tamethebeast/", + month = oct, + year = "2005" +} + + +The BibTeX Tips and FAQ guide. + at electronic{IEEEexample:bibtexFAQ, + author = "David Hoadley and Michael Shell", + title = "{{\BibTeX}} Tips and {FAQ}", + howpublished = "{btxFAQ.pdf}", + url = "http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/", + month = jan, + year = "2007" +} + + +The TeX FAQ + at electronic{IEEEexample:texfaq, + author = "Robin Fairbairns", + title = "The {{\TeX}} {FAQ}", + url = "http://www.tex.ac.uk/cgi-bin/texfaq2html/", + month = jan, + year = "2007" +} + + +A BibTeX Guide via Examples. + at electronic{IEEEexample:bibtexguide, + author = "Ki-Joo Kim", + title = "A {{\BibTeX}} Guide via Examples", + howpublished = "{bibtex\_guide.pdf}", + url = "http://www.geocities.com/kijoo2000/", + month = apr, + year = "2004" +} + + +TeX User Group Bibliography Archive + at electronic{IEEEexample:beebe_archive, + author = "Nelson H. F. Beebe", + title = "{{\TeX}} User Group Bibliography Archive", + url = "http://www.math.utah.edu:8080/pub/tex/bib/index-table.html", + month = aug, + year = "2006" +} + +The natbib.sty package. + at electronic{ctan:natbib, + author = "Patrick W. Daly", + title = "The natbib.sty package", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/natbib/", + month = sep, + year = "2006" +} + +The url.sty package. + at electronic{IEEEexample:urlsty, + author = "Donald Arseneau", + title = "The url.sty Package", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/misc/", + month = jun, + year = "2005", +} + + +The hyperref.sty package. + at electronic{IEEEexample:hyperrefsty, + author = "Sebastian Rahtz and Heiko Oberdiek", + title = "The hyperref.sty Package", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/hyperref/", + month = nov, + year = "2006", +} + + +The breakurl.sty package. + at electronic{IEEEexample:breakurl, + author = "Vilar Camara Neto", + title = "The breakurl.sty Package", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/breakurl/", + month = aug, + year = "2006", +} + + +The Babel package. + at electronic{IEEEexample:babel, + author = "Johannes Braams", + title = "The Babel Package", + url = "http://www.ctan.org/tex-archive/macros/latex/required/babel/", + month = nov, + year = "2005", +} + + +The multibib package. + at electronic{IEEEexample:multibibsty, + author = "Thorsten Hansen", + title = "The multibib.sty package", + url = "http://www.ctan.org/tex-archive/macros/latex/contrib/multibib/", + month = jan, + year = "2004" +} + + +The biblatex package. + at electronic{IEEEexample:biblatex, + author = "Philipp Lehman", + title = "The biblatex package", + url = "http://www.ctan.org/tex-archive/macros/latex/exptl/biblatex/", + month = jan, + year = "2007" +} + + + +The three most common and typical types of references used in +IEEE publications: + +an article in a journal +Note the use of the IEEE_J_EDL string, defined in the IEEEabrv.bib file, +for the journal name. IEEEtran.bst defines the BibTeX standard three +letter month codes per IEEE style. +From the June 2002 issue of "IEEE Transactions on Electron Devices", +page 996, reference #16. + at article{IEEEexample:article_typical, + author = "S. Zhang and C. Zhu and J. K. O. Sin and P. K. T. Mok", + title = "A Novel Ultrathin Elevated Channel Low-temperature + Poly-{Si} {TFT}", + journal = IEEE_J_EDL, + volume = "20", + month = nov, + year = "1999", + pages = "569-571" +} + + +journal article using et al. +The (five) authors are actually: F. Delorme, S. Slempkes, G. Alibert, +B. Rose, J. Brandon +The month (July) was not given here. +From the September 1998 issue of "IEEE Journal on Selected Areas in +Communications", page 1257, reference #28. + at article{IEEEexample:articleetal, + author = "F. Delorme and others", + title = "Butt-jointed {DBR} Laser With 15 {nm} Tunability Grown + in Three {MOVPE} Steps", + journal = "Electron. Lett.", + volume = "31", + number = "15", + year = "1995", + pages = "1244-1245" +} + + +a paper in a conference proceedings +"conference" can be used as an alias for "inproceedings" +From the June 2002 issue of "Journal of Microelectromechanical Systems", +page 205, reference #16. + at inproceedings{IEEEexample:conf_typical, + author = "R. K. Gupta and S. D. Senturia", + title = "Pull-in Time Dynamics as a Measure of Absolute Pressure", + booktitle = "Proc. {IEEE} International Workshop on + Microelectromechanical Systems ({MEMS}'97)", + address = "Nagoya, Japan", + month = jan, + year = "1997", + pages = "290-294" +} + + +a book +From the May 2002 issue of "IEEE Transactions on Magnetics", +page 1466, reference #4. + at book{IEEEexample:book_typical, + author = "B. D. Cullity", + title = "Introduction to Magnetic Materials", + publisher = "Addison-Wesley", + address = "Reading, MA", + year = "1972" +} + + + + +Other examples + +journal article with large page numbers, IEEE will divide numbers 5 digits +or longer into groups of three with small spaces between them. Page ranges +can be separated via either "-" or "--", IEEEtran.bst will automatically +convert the separator dash(es) to "--". +Authors and/or IEEE do not always provide/use the journal number, but it +was used in this case. IEEEtran.bst can be configured to ignore journal +numbers if desired. +From the August 2000 issue of "IEEE Photonics Technology Letters", +page 1039, reference #11. + at article{IEEEexample:articlelargepages, + author = "A. Castaldini and A. Cavallini and B. Fraboni + and P. Fernandez and J. Piqueras", + title = "Midgap Traps Related to Compensation Processes in + {CdTe} Alloys", + journal = "Phys. Rev. B.", + volume = "56", + number = "23", + year = "1997", + pages = "14897-14900" +} + + +journal article with dual months +use the BibTeX "#" concatenation operator +From the March 2002 issue of "IEEE Transactions on Mechatronics", +page 21, reference #8. + at article{IEEEexample:articledualmonths, + author = "Y. Okada and K. Dejima and T. Ohishi", + title = "Analysis and Comparison of {PM} Synchronous Motor and + Induction Motor Type Magnetic Bearings", + journal = IEEE_J_IA, + volume = "31", + month = sep # "/" # oct, + year = "1995", + pages = "1047-1053" +} + + +journal article to be published as a misc entry type +date information like month and year is optional +However, the article form like that below may be a better approach. +From the May 2002 issue of "IEEE Journal of Selected Areas in +Communication", page 725, reference #3. + at misc{IEEEexample:TBPmisc, + author = "M. Coates and A. Hero and R. Nowak and B. Yu", + title = "Internet Tomography", + howpublished = IEEE_M_SP, + month = may, + year = "2002", + note = "to be published" +} + + +journal article to be published as an article entry type +year is required, so if absent, use the year field to hold +the "submitted for publication" in order to avoid a warning for +the missing year field. +From the June 2002 issue of "IEEE Transactions on Information Theory", +page 1461, reference #21. + at article{IEEEexample:TBParticle, + author = "N. Kahale and R. Urbanke", + title = "On the Minimum Distance of Parallel and Serially + Concatenated Codes", + journal = IEEE_J_IT, + year = "submitted for publication" +} + + + + + +book with editor and no author +From the June 2002 issue of "IEEE Transactions on Information Theory", +page 1725, reference #1. + at book{IEEEexample:bookwitheditor, + editor = "J. C. Candy and G. C. Temes", + title = "Oversampling Delta-Sigma Data Converters Theory, + Design and Simulation", + publisher = "{IEEE} Press.", + address = "New York", + year = "1992" +} + + +book with edition, author and editor +Note that the standard BibTeX styles do not support book entries with both +author and editor fields, but IEEEtran.bst does. +The standard BibTeX way of specifying the edition is to use capitalized +ordinal words such as "First", "Second", etc. Most .bst files can convert +up to about "Fifth" into the format needed. IEEEtran.bst can convert up +to "Tenth" to the "Arabic ordinal" form IEEE uses (e.g., "10th"). For +editions over the tenth, it is best to use the "Arabic ordinal" form for +IEEE related work (e.g., "101st") +Note how "Jr." has to be entered. +From the May 2002 issue of "Journal of Lightwave Technology", page 856, +reference #17. + at book{IEEEexample:book, + author = "S. M. Metev and V. P. Veiko", + editor = "Osgood, Jr., R. M.", + title = "Laser Assisted Microtechnology", + edition = "Second", + publisher = "Springer-Verlag", + address = "Berlin, Germany", + year = "1998" +} + + +book with series and volume +From the January 2000 issue of "IEEE Transactions on Communications", +page 11, reference #31. + at book{IEEEexample:bookwithseriesvolume, + editor = "J. Breckling", + title = "The Analysis of Directional Time Series: Applications to + Wind Speed and Direction", + series = "Lecture Notes in Statistics", + publisher = "Springer", + address = "Berlin, Germany", + year = "1989", + volume = "61" +} + + +inbook with chapter number. The pages field could also have been given. +The chapter number could be changed to something else such as a section +number via the type field: type = "sec.". +From the May 2002 issue of "IEEE Transactions on Circuits and Systems---I: +Fundamental Applications and Theory", page 638, reference #22. + at inbook{IEEEexample:inbook, + author = "H. E. Rose", + title = "A Course in Number Theory", + publisher = "Oxford Univ. Press", + address = "New York, NY", + year = "1988", + chapter = "3" +} + + +inbook with pages and note. The language field is not set to Russian +because the title is presented here in its translated, English, form. +From the May 2002 issue of "IEEE Transactions on Magnetics", page 1533, +reference #5. + at inbook{IEEEexample:inbookpagesnote, + author = "B. K. Bul", + title = "Theory Principles and Design of Magnetic Circuits", + publisher = "Energia Press", + address = "Moscow", + year = "1964", + pages = "464", + note = "(in Russian)" +} + + + + + +incollection with author and editor +From the May 2002 issue of "Journal of Lightwave Technology", +page 807, reference #7. + at incollection{IEEEexample:incollection, + author = "W. V. Sorin", + editor = "D. Derickson", + title = "Optical Reflectometry for Component Characterization", + booktitle = "Fiber Optic Test and Measurement", + publisher = "Prentice-Hall", + address = "Englewood Cliffs, NJ", + year = "1998" +} + + +incollection with series +From the April 2000 issue of "IEEE Transactions on Communication", +page 609, reference #3. + at incollection{IEEEexample:incollectionwithseries, + author = "J. B. Anderson and K. Tepe", + title = "Properties of the Tailbiting {BCJR} Decoder", + booktitle = "Codes, Systems and Graphical Models", + series = "{IMA} Volumes in Mathematics and Its Applications", + publisher = "Springer-Verlag", + address = "New York", + year = "2000" + +} + + +incollection with author, editor, chapter and pages +From the January 2000 issue of "IEEE Transactions on Communications", +page 16, reference #9. + at incollection{IEEEexample:incollection_chpp, + author = "P. Hedelin and P. Knagenhjelm and M. Skoglund", + editor = "W. B. Kleijn and K. K. Paliwal", + title = "Theory for Transmission of Vector Quantization Data", + booktitle = "Speech Coding and Synthesis", + publisher = "Elsevier Science", + address = "Amsterdam, The Netherlands", + year = "1995", + chapter = "10", + pages = "347-396" +} + + +incollection with a large number of authors, some authors/journals will +use et al. for so many names. IEEEtran.bst can be configured to do this +if desired, or "R. M. A. Dawson and others" can be used instead. +Note that IEEE may not include the publisher for incollection entries - +IEEEtran.bst will not issue a warning if the publisher is missing for +incollections - but other .bst files often will. +From the June 2002 issue of "IEEE Transactions on Electron Devices", +page 996, reference #12. + at incollection{IEEEexample:incollectionmanyauthors, + author = "R. M. A. Dawson and Z. Shen and D. A. Furst and + S. Connor and J. Hsu and M. G. Kane and R. G. Stewart and + A. Ipri and C. N. King and P. J. Green and R. T. Flegal + and S. Pearson and W. A. Barrow and E. Dickey and K. Ping + and C. W. Tang and S. Van. Slyke and + F. Chen and J. Shi and J. C. Sturm and M. H. Lu", + title = "Design of an Improved Pixel for a Polysilicon + Active-Matrix Organic {LED} Display", + booktitle = "{SID} Tech. Dig.", + volume = "29", + year = "1998", + pages = "11-14" +} + + + + + +A Motorola data book as a manual +It is somewhat unusual to include the data book part number. +in the title. It might be more correct to put this information +in the howpublished field instead. +From the December 2000 issue of "IEEE Transactions on Communications", +page 1986, reference #10. + at manual{IEEEexample:motmanual, + title = "{FLEXChip} Signal Processor ({MC68175/D})", + organization = "Motorola", + year = "1996" +} + + +same reference, but using IEEEtran's howpublished extension + at manual{IEEEexample:motmanualhowpub, + title = "{FLEXChip} Signal Processor", + howpublished = "{MC68175/D}", + organization = "Motorola", + year = "1996" +} + + + + +conference paper with an address and days. Some journals capitalize the +letters in "Globecom", this one did not. +From the May 2002 issue of "IEEE Transactions on Communications", +page 697, reference #12. + at inproceedings{IEEEexample:confwithadddays, + author = "M. S. Yee and L. Hanzo", + title = "Radial Basis Function Decision Feedback Equaliser + Assisted Burst-by-burst Adaptive Modulation", + booktitle = "Proc. {IEEE} Globecom '99", + address = "Rio de Janeiro, Brazil", + month = dec # " 5--9,", + year = "1999", + pages = "2183-2187" +} + + +conference paper with volume number. A conference proceedings with a vol +number is a little uncommon, note that the vol number is placed +before the address in the formatted bibliography entry +From the April 2002 issue of "IEEE/ACM Transactions on Networking", +page 181, reference #26. + at inproceedings{IEEEexample:confwithvolume, + author = "M. Yajnik and S. B. Moon and J. Kurose and D. Towsley", + title = "Measurement and Modeling of the Temporal Dependence in + Packet Loss", + booktitle = "Proc. {IEEE} {INFOCOM}'99", + volume = "1", + address = "New York, NY", + month = mar, + year = "1999", + pages = "345-352" +} + + +conference paper with a paper number, the type field can be used to +override the word "paper", e.g., type = "postdeadline paper". A type +can be given even without a paper field. +Also, IEEEtran.bst can be configured to ignore paper numbers and types. +From the May 2002 issue of "Journal of Lightwave Technology", +page 807, reference #4. + at inproceedings{IEEEexample:confwithpaper, + author = "M. Wegmuller and J. P. von der Weid and P. Oberson + and N. Gisin", + title = "High Resolution Fiber Distributed Measurements With + Coherent {OFDR}", + booktitle = "Proc. {ECOC}'00", + year = "2000", + paper = "11.3.4", + pages = "109" +} + + +conference paper with a postdeadline type paper, the paper field is +optional. +From the August 2000 issue of "IEEE Photonics Technology Letters", +page 1087, reference #12. + at inproceedings{IEEEexample:confwithpapertype, + author = "B. Mikkelsen and G. Raybon and R.-J. Essiambre and + K. Dreyer and Y. Su. and L. E. Nelson and J. E. Johnson + and G. Shtengel and A. Bond and D. G. Moodie and + A. D. Ellis", + title = "160 {Gbit/s} Single-channel Transmission Over 300 km + Nonzero-dispersion Fiber With Semiconductor Based + Transmitter and Demultiplexer", + booktitle = "Proc. {ECOC}'99", + year = "1999", + paper = "2-3", + type = "postdeadline paper", + pages = "28-29" +} + + +presented at a conference +intype overrides the default "in" and causes the booktitle not to be +emphasized (rendered in italics). +From the February 2002 issue of "IEEE/ACM Transactions on Networking", +page 163, reference #6. + at inproceedings{IEEEexample:presentedatconf, + author = "S. G. Finn and M. M{\'e}dard and R. A. Barry", + title = "A Novel Approach to Automatic Protection Switching + Using Trees", + intype = "presented at the", + booktitle = "Proc. Int. Conf. Commun.", + year = "1997" +} + + + + + +master's thesis, often the University name will be abbreviated and the +state or country will be included in the address. The type field can +used to override the default type "Master's thesis" +From the June 2002 issue of "IEEE Transactions on Microelectromechanical +Systems", page 186, reference #11. + at mastersthesis{IEEEexample:masters, + author = "Nin C. Loh", + title = "High-Resolution Micromachined Interferometric + Accelerometer", + school = "Massachusetts Institute of Technology", + address = "Cambridge", + year = "1992" +} + + +master's thesis with a type field +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 391, reference #12. + at mastersthesis{IEEEexample:masterstype, + author = "A. Karnik", + title = "Performance of {TCP} Congestion Control with Rate + Feedback: {TCP/ABR} and Rate Adaptive {TCP/IP}", + school = "Indian Institute of Science", + type = "M. Eng. thesis", + address = "Bangalore, India", + month = jan, + year = "1999" +} + + + + + +Ph.D. dissertation with a URL field, the university is abbreviated +From the October 2001 issue of "IEEE/ACM Transactions on Networking", +page 590, reference #11. + at phdthesis{IEEEexample:phdurl, + author = "Q. Li", + title = "Delay Characterization and Performance Control of + Wide-area Networks", + school = "Univ. of Delaware", + address = "Newark", + month = may, + year = "2000", + url = "http://www.ece.udel.edu/~qli" +} + + + + + +technical report +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 490, reference #15. + at techreport{IEEEexample:techrep, + author = "R. Jain and K. K. Ramakrishnan and D. M. Chiu", + title = "Congestion Avoidance in Computer Networks with a + Connectionless Network Layer", + institution = "Digital Equipment Corporation", + address = "MA", + number = "DEC-TR-506", + month = aug, + year = "1987" +} + + +technical report with type +for those times when "Tech. Rep." needs to be modified +From the February 2001 issue of "IEEE/ACM Transactions on Networking", +page 46, reference #8. + at techreport{IEEEexample:techreptype, + author = "J. Padhye and V. Firoiu and D. Towsley", + title = "A Stochastic Model of {TCP} {R}eno Congestion Avoidance + and Control", + institution = "Univ. of Massachusetts", + address = "Amherst, MA", + type = "CMPSCI Tech. Rep.", + number = "99-02", + year = "1999" +} + + +technical report with type +for those times when "Tech. Rep." needs to be modified +This reference did not have an address. +From the January 2000 issue of "IEEE Transactions on Communications", +page 117, reference #6. + at techreport{IEEEexample:techreptypeii, + author = "D. Middleton and A. D. Spaulding", + title = "A Tutorial Review of Elements of Weak Signal Detection + in Non-{G}aussian {EMI} Environments", + institution = "National Telecommunications and Information + Administration ({NTIA}), U.S. Dept. of Commerce", + type = "NTIA Report", + number = "86-194", + month = may, + year = "1986" +} + + + + + +an unpublished work +for unpublished types, the note field is required. IEEE usually +just uses the word "unpublished" for the note. +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 391, reference #16. + at unpublished{IEEEexample:unpublished, + author = "T. J. Ott and N. Aggarwal", + title = "{TCP} over {ATM}: {ABR} or {UBR}", + note = "Unpublished" +} + + + + + +electronic with a howpublished information field +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 391, reference #7. + at electronic{IEEEexample:electronhowinfo, + author = "V. Jacobson", + title = "Modified {TCP} Congestion Avoidance Algorithm", + howpublished = "end2end-interest mailing list", + url = "ftp://ftp.isi.edu/end2end/end2end-interest-1990.mail", + month = apr, + year = "1990" +} + + +electronic with a howpublished information field +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 418, reference #31. + at electronic{IEEEexample:electronhowinfo2, + author = "V. Valloppillil and K. W. Ross", + title = "Cache Array Routing Protocol v1.1", + howpublished = "Internet draft", + url = "http://ds1.internic.net/internet-drafts/draft-vinod-carp-v1-03.txt", + year = "1998" +} + + +electronic with an organization and address +From the February 2002 issue of "IEEE/ACM Transactions on Networking", +page 114, reference #15. + at electronic{IEEEexample:electronorgadd, + author = "D. H. Lorenz and A. Orda", + title = "Optimal Partition of {QoS} Requirements on Unicast + Paths and Multicast Trees", + organization = "Dept. Elect. Eng., Technion", + address = "Haifa, Israel", + url = "ftp://ftp.technion.ac.il/pub/supported/ee/Network/lor.mopq98.ps", + month = jul, + year = "1998" +} + + + + + +U.S. patent +Use the type field to override the patent type. e.g., +type = "Patent Application" +The address is that of the assignee. Note that IEEE does not +display the assignee, the address, and only displays one date. +(if year is not present, the filed dates are used.) However, this +information should be entered as other BibTeX styles may use it. +alternatively, nationality could be entered as "U.S." +From the April 2000 issue of "IEEE Transactions on Communications", +page 542, reference #6. + at patent{IEEEexample:uspat, + author = "Ronald E. Sorace and Victor S. Reinhardt and + Steven A. Vaughn", + assignee = "Hughes Aircraft Company", + address = "Los Angeles, CA", + title = "High-Speed Digital-to-{RF} Converter", + nationality = "United States", + number = "5668842", + dayfiled = "28", + monthfiled = feb, + yearfiled = "1995", + day = "16", + month = sep, + year = "1997" +} + + +Japanese Patent +From the April 2000 issue of "IEEE Transactions on Communications", +page 556, reference #6. + at patent{IEEEexample:jppat, + author = "U. Hideki", + title = "Quadrature Modulation Circuit", + nationality = "Japanese", + number = "152932/92", + day = "20", + month = may, + year = "1992" +} + + +French Patent request, the language field must be entered in lower case +as this is the option name Babel uses. The nationality field needs to be +capitalized. Because this is a patent request, the date filed fields are +used while the date fields are left empty/missing. In other countries, +the words "Patent Application", etc. are used instead. +From the April 2000 issue of "IEEE Transactions on Communications", +page 556, reference #9. + at patent{IEEEexample:frenchpatreq, + author = "F. Kowalik and M. Isard", + title = "Estimateur d'un D{\'e}faut de Fonctionnement + d'un Modulateur en Quadrature et {\'E}tage de Modulation + l'Utilisant", + language = "french", + nationality = "French", + type = "Patent Request", + number = "9500261", + dayfiled = "11", + monthfiled = jan, + yearfiled = "1995" +} + + + + + +a periodical +From the April 2001 issue of "IEEE/ACM Transactions on Networking", +page 160, reference #1. +sort key is needed for sorting styles + at periodical{IEEEexample:periodical, + title = IEEE_M_PCOM # ", Special Issue on Wireless {ATM}", + volume = "3", + month = aug, + year = "1996", + key = "IEEE" +} + + + + + +standard, IEEE does not use the address for standards, but it is good +to provide one for BibTeX styles that use it. +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 451, reference #2. + at standard{IEEEexample:standard, + title = "Wireless {LAN} Medium Access Control {(MAC)} and + Physical Layer {(PHY)} Specification", + organization = "IEEE", + address = "Piscataway, NJ", + number = "802.11", + year = "1997" +} + + +standard with type and revision, the type overrides the word standard +(or std.). Here a standard number is not available and a revision number +is used. +From the August 2000 issue of "IEEE Photonics Technology Letters", +page 1048, reference #13. + at standard{IEEEexample:standardproposed, + title = "Fiber Channel Physical Interface ({FC-PI})", + institution = "NCITS", + address = "Washington, DC", + type = "Working Draft Proposed Standard", + revision = "5.2", + year = "1999" +} + + +standard draft as a misc with author +From the May 2002 issue of "IEEE Journal of Selected Areas in +Communication", page 725, reference #16. + at misc{IEEEexample:draftasmisc, + author = "I. Widjaja and A. Elwalid", + title = "{MATE}: {MPLS} Adaptive Traffic Engineering", + howpublished = "IETF Draft", + year = "1999" +} + + + + + +misc for a techreport like reference +techreport is not perfectly suitable because this entry lacks +an institution field +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 490, reference #22. + at misc{IEEEexample:miscforum, + author = "L. Roberts", + title = "Enhanced Proportional Rate Control Algorithm {PRCA}", + howpublished = "{ATM} Forum Contribution 94-0735R1", + month = aug, + year = "1994" +} + + +misc for a white paper +From the August 2001 issue of "IEEE/ACM Transactions on Networking", +page 478, reference #4 - Note that the reference there (improperly?) +used the author field for "Cisco". + at misc{IEEEexample:whitepaper, + title = "Advanced {QoS} Services for the Intelligent Internet", + howpublished = "White Paper", + organization = "Cisco", + month = may, + year = "1997" +} + + +misc for a data sheet +From the November 2000 issue of "IEEE Photonics Technology Letters", +page 1551, reference #6. + at misc{IEEEexample:datasheet, + title = "{PDCA12-70} Data Sheet", + organization = "Opto Speed SA", + address = "Mezzovico, Switzerland" +} + + + + + +Other unusual references + +a private communication as a misc entry type +sometimes the designation "personal communication" is used instead +From the June 2002 issue of "IEEE Transactions on Information Theory", +page 1725, reference #16. + at misc{IEEEexample:private, + author = "S. Konyagin", + howpublished = "private communication", + year = "1998" +} + + +an internet request for comments (RFC) as a misc entry type +It would also be nice to add a URL to these types of things. +RFCs can also be handled as electronic references. +From the April 2002 issue of "IEEE/ACM Transactions on Networking", +page 181, reference #14. + at misc{IEEEexample:miscrfc, + author = "K. K. Ramakrishnan and S. Floyd", + title = "A Proposal to Add Explicit Congestion + Notification ({ECN}) to {IP}", + howpublished = "RFC 2481", + month = jan, + year = "1999" +} + + +a software package as a manual +From the June 2002 issue of "IEEE/ASME Journal of Microelectromechanical +Systems", page 205, reference #20. +Sometimes they put the version/release information in the title. + at manual{IEEEexample:softmanual, + title = "SaberDesigner Reference Manual", + organization = "Analogy, Inc.", + address = "Beaverton, OR", + year = "1998", + note = "Release 4.3" +} + + +a software package as an electronic reference +From the February 2003 issue of "IEEE/ACM Transactions on Networking", +page 46, reference #24. If there is no author or organization, a sorting +key is required for sorting styles. It might be a good idea to include +month and year fields as well. + at electronic{IEEEexample:softonline, + title = "Ucb/lbnl/vint Network Simulator---ns (Version 2)", + url = "http://www-mash.cs.berkeley.edu/ns/", + key = "ns" +} + + +misc for a German regulation +In German, the first letters of nouns are capitalized, so we do so here. +From the June 2002 issue of "IEEE Journal in Selected Areas in +Communication", page 892, reference #9. + at misc{IEEEexample:miscgermanreg, + title = "{M}essung von {S}t{\"o}rfeldern an {A}nlagen + und {L}eitungen der {T}elekommunikation im + {F}requenzbereich 9 {kHz} bis 3 {GHz}", + language = "german", + howpublished = "{M}e{\ss}vorschrift {R}eg {TP} {MV} 05", + organization = "Regulierungsbeh{\"o}rde f{\"u}r {T}elekommunikation und + {P}ost ({R}eg {TP})" +} + + + +Ways to handle things like CCSDS's Blue Books +journal article with a URL. However, this is not a very good approach +because the Blue Books are not really journals and the author field has +to be abused. +From the June 2002 issue of "IEEE Transactions on Information Theory", +page 1461, reference #7. + at article{IEEEexample:bluebookarticle, + author = "{Consulative Committee for Space Data Systems (CCSDS)}", + title = "Telemetry Channel Coding", + journal = "Blue Book", + number = "4", + year = "1999", + url = "http://www.ccsds.org/documents/pdf/CCSDS-101.0-B-4.pdf" +} + + +CCSDS's Blue Book handled as a book +However, it is not a good idea to have to use the author field for +an organization (done here because the book entry type requires an +author field). + at book{IEEEexample:bluebookbook, + author = "{Consulative Committee for Space Data Systems (CCSDS)}", + title = "Telemetry Channel Coding", + series = "Blue Book", + number = "4", + publisher = "{CCSDS}", + address = "Newport Beach, {CA}", + year = "1999", + url = "http://www.ccsds.org/documents/pdf/CCSDS-101.0-B-4.pdf" +} + + +CCSDS's Blue Book handled as a manual +This is a much better approach, but uses the howpublished field. + at manual{IEEEexample:bluebookmanual, + title = "Telemetry Channel Coding", + howpublished = "ser. Blue Book, No. 4", + organization = "Consulative Committee for Space Data Systems (CCSDS)", + address = "Newport Beach, CA", + year = "1999", + url = "http://www.ccsds.org/documents/pdf/CCSDS-101.0-B-4.pdf" +} + + + +CCSDS's Blue Book handled as a standard +Probably the best approach for this particular case because the work +is standard related. Note that IEEE does not display the address for +standards. + at standard{IEEEexample:bluebookstandard, + title = "Telemetry Channel Coding", + howpublished = "ser. Blue Book, No. 4", + organization = "Consulative Committee for Space Data Systems (CCSDS)", + address = "Newport Beach, CA", + type = "Recommendation for Space Data System Standard", + number = "101.0-B-4", + month = May, + year = "1999", + url = "http://www.ccsds.org/documents/pdf/CCSDS-101.0-B-4.pdf" +} + + + + + + + + +An example of a IEEEtran control entry which can change some IEEEtran.bst +settings. An entry like this must be cited via \bstctlcite{} command +before the first real \cite{}. The same entry key cannot be called twice +(just like multiple \cite{} of the same entry key place only one entry +in the bibliography.) +The available control fields are: + +CTLuse_article_number +"no" turns off the display of the number for articles. +"yes" enables + +CTLuse_paper +"no" turns off the display of the paper and type fields in inproceedings. +"yes" enables + +CTLuse_forced_etal +"no" turns off the forced use of "et al." +"yes" enables + +CTLmax_names_forced_etal +The maximum number of names that can be present beyond which an "et al." +usage is forced. Be sure that CTLnames_show_etal (below) +is not greater than this value! + +CTLnames_show_etal +The number of names that will be shown with a forced "et al.". +Must be less than or equal to CTLmax_names_forced_etal + +CTLuse_alt_spacing +"no" turns off the alternate interword spacing for entries with URLs. +"yes" enables + +CTLalt_stretch_factor +If alternate interword spacing for entries with URLs is enabled, this is +the interword spacing stretch factor that will be used. For example, the +default "4" here means that the interword spacing in entries with URLs can +stretch to four times normal. Does not have to be an integer. + +CTLdash_repeated_names +"no" turns off the "dashification" of repeated (i.e., identical to those +of the previous entry) names. IEEE normally does this. +"yes" enables + +CTLname_format_string +The name format control string as explained in the BibTeX style hacking +guide. +IEEE style "{f.~}{vv~}{ll}{, jj}" is the default, + +CTLname_latex_cmd +A LaTeX command that each name will be fed to (e.g., "\textsc"). +Leave empty if no special font is desired for the names. +The default is empty. + +CTLname_url_prefix +The prefix text used before URLs. +The default is "[Online]. Available:" A space will be inserted after this +text. If this space is not wanted, just use \relax at the end of the +prefix text. + + +Those fields that are not to be changed can be left out. + at IEEEtranBSTCTL{IEEEexample:BSTcontrol, + CTLuse_article_number = "yes", + CTLuse_paper = "yes", + CTLuse_forced_etal = "no", + CTLmax_names_forced_etal = "10", + CTLnames_show_etal = "1", + CTLuse_alt_spacing = "yes", + CTLalt_stretch_factor = "4", + CTLdash_repeated_names = "yes", + CTLname_format_string = "{f.~}{vv~}{ll}{, jj}", + CTLname_latex_cmd = "", + CTLname_url_prefix = "[Online]. Available:" +} + + Added: text/escience11submission/IEEEfull.bib =================================================================== --- text/escience11submission/IEEEfull.bib (rev 0) +++ text/escience11submission/IEEEfull.bib 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,419 @@ + +IEEEfull.bib +V1.12 (2007/01/11) +Copyright (c) 2002-2007 by Michael Shell +See: http://www.michaelshell.org/ +for current contact information. + +BibTeX bibliography string definitions of the FULL titles of +IEEE journals and magazines and online publications. + +This file is designed for bibliography styles that require +full-length titles and is not for use in bibliographies that +abbreviate titles. + +Support sites: +http://www.michaelshell.org/tex/ieeetran/ +http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +and/or +http://www.ieee.org/ + +Special thanks to Laura Hyslop and ken Rawson of IEEE for their help +in obtaining the information needed to compile this file. Also, +Volker Kuhlmann and Moritz Borgmann kindly provided some corrections +and additions. + +************************************************************************* +Legal Notice: +This code is offered as-is without any warranty either expressed or +implied; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE! +User assumes all risk. +In no event shall IEEE or any contributor to this code be liable for +any damages or losses, including, but not limited to, incidental, +consequential, or any other damages, resulting from the use or misuse +of any information contained here. + +All comments are the opinions of their respective authors and are not +necessarily endorsed by the IEEE. + +This work is distributed under the LaTeX Project Public License (LPPL) +( http://www.latex-project.org/ ) version 1.3, and may be freely used, +distributed and modified. A copy of the LPPL, version 1.3, is included +in the base LaTeX documentation of all distributions of LaTeX released +2003/12/01 or later. +Retain all contribution notices and credits. +** Modified files should be clearly indicated as such, including ** +** renaming them and changing author support contact information. ** + +File list of work: IEEEabrv.bib, IEEEfull.bib, IEEEexample.bib, + IEEEtran.bst, IEEEtranS.bst, IEEEtranSA.bst, + IEEEtranN.bst, IEEEtranSN.bst, IEEEtran_bst_HOWTO.pdf +************************************************************************* + + +USAGE: + +\bibliographystyle{mybstfile} +\bibliography{IEEEfull,mybibfile} + +where the IEEE titles in the .bib database entries use the strings +defined here. e.g., + + + journal = IEEE_J_AC, + + +to yield "{IEEE} Transactions on Automatic Control" + + +WARNING: IEEE uses abbreviated journal titles in their bibliographies! +Because this file provides the full titles, you should NOT use this file +for work that is to be submitted to the IEEE. + +For IEEE work, you should use the abbreviated titles provided in the +companion file, IEEEabrv.bib. + + +** NOTES ** + + 1. Journals have been grouped according to subject in order to make it + easier to locate and extract the definitions for related journals - + as most works use references that are confined to a single topic. + Magazines are listed in straight alphabetical order. + + 2. String names are closely based on IEEE's own internal acronyms. + + 3. Older, out-of-print IEEE titles are included (but not including titles + dating prior to IEEE's formation from the IRE and AIEE in 1963). + + + + + + +IEEE Journals + + + +aerospace and military + at STRING{IEEE_J_AES = "{IEEE} Transactions on Aerospace and Electronic Systems"} + at STRING{IEEE_J_ANE = "{IEEE} Transactions on Aerospace and Navigational Electronics"} + at STRING{IEEE_J_ANNE = "{IEEE} Transactions on Aeronautical and Navigational Electronics"} + at STRING{IEEE_J_AS = "{IEEE} Transactions on Aerospace"} + at STRING{IEEE_J_AIRE = "{IEEE} Transactions on Airborne Electronics"} + at STRING{IEEE_J_MIL = "{IEEE} Transactions on Military Electronics"} + + + +autos, transportation and vehicles (non-aerospace) + at STRING{IEEE_J_ITS = "{IEEE} Transactions on Intelligent Transportation Systems"} + at STRING{IEEE_J_VT = "{IEEE} Transactions on Vehicular Technology"} + at STRING{IEEE_J_VC = "{IEEE} Transactions on Vehicular Communications"} + + + +circuits, signals, systems, audio and controls + at STRING{IEEE_J_SPL = "{IEEE} Signal Processing Letters"} + at STRING{IEEE_J_ASSP = "{IEEE} Transactions on Acoustics, Speech, and Signal Processing"} + at STRING{IEEE_J_AU = "{IEEE} Transactions on Audio"} + at STRING{IEEE_J_AUEA = "{IEEE} Transactions on Audio and Electroacoustics"} + at STRING{IEEE_J_AC = "{IEEE} Transactions on Automatic Control"} + at STRING{IEEE_J_CAS = "{IEEE} Transactions on Circuits and Systems"} + at STRING{IEEE_J_CASVT = "{IEEE} Transactions on Circuits and Systems for Video Technology"} + at STRING{IEEE_J_CASI = "{IEEE} Transactions on Circuits and Systems---Part {I}: Fundamental Theory and Applications"} + at STRING{IEEE_J_CASII = "{IEEE} Transactions on Circuits and Systems---Part {II}: Analog and Digital Signal Processing"} +in 2004 CASI and CASII renamed part title to CASI_RP and CASII_EB, respectively. + at STRING{IEEE_J_CASI_RP = "{IEEE} Transactions on Circuits and Systems---Part {I}: Regular Papers"} + at STRING{IEEE_J_CASII_EB = "{IEEE} Transactions on Circuits and Systems---Part {II}: Express Briefs"} + at STRING{IEEE_J_CT = "{IEEE} Transactions on Circuit Theory"} + at STRING{IEEE_J_CST = "{IEEE} Transactions on Control Systems Technology"} + at STRING{IEEE_J_SP = "{IEEE} Transactions on Signal Processing"} + at STRING{IEEE_J_SU = "{IEEE} Transactions on Sonics and Ultrasonics"} + at STRING{IEEE_J_SAP = "{IEEE} Transactions on Speech and Audio Processing"} + at STRING{IEEE_J_UE = "{IEEE} Transactions on Ultrasonics Engineering"} + at STRING{IEEE_J_UFFC = "{IEEE} Transactions on Ultrasonics, Ferroelectrics, and Frequency Control"} + + + +communications + at STRING{IEEE_J_COML = "{IEEE} Communications Letters"} + at STRING{IEEE_J_JSAC = "{IEEE} Journal on Selected Areas in Communications"} + at STRING{IEEE_J_COM = "{IEEE} Transactions on Communications"} + at STRING{IEEE_J_COMT = "{IEEE} Transactions on Communication Technology"} + at STRING{IEEE_J_WCOM = "{IEEE} Transactions on Wireless Communications"} + + + +components, packaging and manufacturing + at STRING{IEEE_J_ADVP = "{IEEE} Transactions on Advanced Packaging"} + at STRING{IEEE_J_CHMT = "{IEEE} Transactions on Components, Hybrids and Manufacturing Technology"} + at STRING{IEEE_J_CPMTA = "{IEEE} Transactions on Components, Packaging and Manufacturing Technology---Part {A}"} + at STRING{IEEE_J_CPMTB = "{IEEE} Transactions on Components, Packaging and Manufacturing Technology---Part {B}: Advanced Packaging"} + at STRING{IEEE_J_CPMTC = "{IEEE} Transactions on Components, Packaging and Manufacturing Technology---Part {C}: Manufacturing"} + at STRING{IEEE_J_CAPT = "{IEEE} Transactions on Components and Packaging Technology"} + at STRING{IEEE_J_CAPTS = "{IEEE} Transactions on Components and Packaging Technologies"} + at STRING{IEEE_J_CPART = "{IEEE} Transactions on Component Parts"} + at STRING{IEEE_J_EPM = "{IEEE} Transactions on Electronics Packaging Manufacturing"} + at STRING{IEEE_J_MFT = "{IEEE} Transactions on Manufacturing Technology"} + at STRING{IEEE_J_PHP = "{IEEE} Transactions on Parts, Hybrids and Packaging"} + at STRING{IEEE_J_PMP = "{IEEE} Transactions on Parts, Materials and Packaging"} + + + +CAD + at STRING{IEEE_J_TCAD = "{IEEE} Journal on Technology in Computer Aided Design"} + at STRING{IEEE_J_CAD = "{IEEE} Transactions on Computer-Aided Design of Integrated Circuits and Systems"} + + + +coding, data, information, knowledge + at STRING{IEEE_J_IT = "{IEEE} Transactions on Information Theory"} + at STRING{IEEE_J_KDE = "{IEEE} Transactions on Knowledge and Data Engineering"} + + + +computers, computation, networking and software + at STRING{IEEE_J_C = "{IEEE} Transactions on Computers"} + at STRING{IEEE_J_CAL = "{IEEE} Computer Architecture Letters"} + at STRING{IEEE_J_DSC = "{IEEE} Transactions on Dependable and Secure Computing"} + at STRING{IEEE_J_ECOMP = "{IEEE} Transactions on Electronic Computers"} + at STRING{IEEE_J_EVC = "{IEEE} Transactions on Evolutionary Computation"} + at STRING{IEEE_J_FUZZ = "{IEEE} Transactions on Fuzzy Systems"} + at STRING{IEEE_J_IFS = "{IEEE} Transactions on Information Forensics and Security"} + at STRING{IEEE_J_MC = "{IEEE} Transactions on Mobile Computing"} + at STRING{IEEE_J_NET = "{IEEE/ACM} Transactions on Networking"} + at STRING{IEEE_J_NN = "{IEEE} Transactions on Neural Networks"} + at STRING{IEEE_J_PDS = "{IEEE} Transactions on Parallel and Distributed Systems"} + at STRING{IEEE_J_SE = "{IEEE} Transactions on Software Engineering"} + + + +computer graphics, imaging, and multimedia + at STRING{IEEE_J_JDT = "{IEEE/OSA} Journal of Display Technology"} + at STRING{IEEE_J_IP = "{IEEE} Transactions on Image Processing"} + at STRING{IEEE_J_MM = "{IEEE} Transactions on Multimedia"} + at STRING{IEEE_J_VCG = "{IEEE} Transactions on Visualization and Computer Graphics"} + + + +cybernetics, ergonomics, robots, man-machine, and automation + at STRING{IEEE_J_ASE = "{IEEE} Transactions on Automation Science and Engineering"} + at STRING{IEEE_J_JRA = "{IEEE} Journal of Robotics and Automation"} + at STRING{IEEE_J_HFE = "{IEEE} Transactions on Human Factors in Electronics"} + at STRING{IEEE_J_MMS = "{IEEE} Transactions on Man-Machine Systems"} + at STRING{IEEE_J_PAMI = "{IEEE} Transactions on Pattern Analysis and Machine Intelligence"} +in 1989 JRA became RA +in August 2004, RA split into ASE and RO + at STRING{IEEE_J_RA = "{IEEE} Transactions on Robotics and Automation"} + at STRING{IEEE_J_RO = "{IEEE} Transactions on Robotics"} + at STRING{IEEE_J_SMC = "{IEEE} Transactions on Systems, Man, and Cybernetics"} + at STRING{IEEE_J_SMCA = "{IEEE} Transactions on Systems, Man, and Cybernetics---Part {A}: Systems and Humans"} + at STRING{IEEE_J_SMCB = "{IEEE} Transactions on Systems, Man, and Cybernetics---Part {B}: Cybernetics"} + at STRING{IEEE_J_SMCC = "{IEEE} Transactions on Systems, Man, and Cybernetics---Part {C}: Applications and Reviews"} + at STRING{IEEE_J_SSC = "{IEEE} Transactions on Systems Science and Cybernetics"} + + + +earth, wind, fire and water + at STRING{IEEE_J_GE = "{IEEE} Transactions on Geoscience Electronics"} + at STRING{IEEE_J_GRS = "{IEEE} Transactions on Geoscience and Remote Sensing"} + at STRING{IEEE_J_GRSL = "{IEEE} Geoscience and Remote Sensing Letters"} + at STRING{IEEE_J_OE = "{IEEE} Journal of Oceanic Engineering"} + + + +education, engineering, history, IEEE, professional + at STRING{IEEE_J_CJECE = "Canadian Journal of Electrical and Computer Engineering"} + at STRING{IEEE_J_PROC = "Proceedings of the {IEEE}"} + at STRING{IEEE_J_EDU = "{IEEE} Transactions on Education"} + at STRING{IEEE_J_EM = "{IEEE} Transactions on Engineering Management"} + at STRING{IEEE_J_EWS = "{IEEE} Transactions on Engineering Writing and Speech"} + at STRING{IEEE_J_PC = "{IEEE} Transactions on Professional Communication"} + + + +electromagnetics, antennas, EMI, magnetics and microwave + at STRING{IEEE_J_AWPL = "{IEEE} Antennas and Wireless Propagation Letters"} + at STRING{IEEE_J_MGWL = "{IEEE} Microwave and Guided Wave Letters"} + at STRING{IEEE_J_MWCL = "{IEEE} Microwave and Wireless Components Letters"} + at STRING{IEEE_J_AP = "{IEEE} Transactions on Antennas and Propagation"} + at STRING{IEEE_J_EMC = "{IEEE} Transactions on Electromagnetic Compatibility"} + at STRING{IEEE_J_MAG = "{IEEE} Transactions on Magnetics"} + at STRING{IEEE_J_MTT = "{IEEE} Transactions on Microwave Theory and Techniques"} + at STRING{IEEE_J_RFI = "{IEEE} Transactions on Radio Frequency Interference"} + at STRING{IEEE_J_TJMJ = "{IEEE} Translation Journal on Magnetics in Japan"} + + + +energy and power + at STRING{IEEE_J_EC = "{IEEE} Transactions on Energy Conversion"} + at STRING{IEEE_J_PEL = "{IEEE} Power Electronics Letters"} + at STRING{IEEE_J_PWRAS = "{IEEE} Transactions on Power Apparatus and Systems"} + at STRING{IEEE_J_PWRD = "{IEEE} Transactions on Power Delivery"} + at STRING{IEEE_J_PWRE = "{IEEE} Transactions on Power Electronics"} + at STRING{IEEE_J_PWRS = "{IEEE} Transactions on Power Systems"} + + + +industrial, commercial and consumer + at STRING{IEEE_J_APPIND = "{IEEE} Transactions on Applications and Industry"} + at STRING{IEEE_J_BC = "{IEEE} Transactions on Broadcasting"} + at STRING{IEEE_J_BCTV = "{IEEE} Transactions on Broadcast and Television Receivers"} + at STRING{IEEE_J_CE = "{IEEE} Transactions on Consumer Electronics"} + at STRING{IEEE_J_IE = "{IEEE} Transactions on Industrial Electronics"} + at STRING{IEEE_J_IECI = "{IEEE} Transactions on Industrial Electronics and Control Instrumentation"} + at STRING{IEEE_J_IA = "{IEEE} Transactions on Industry Applications"} + at STRING{IEEE_J_IGA = "{IEEE} Transactions on Industry and General Applications"} + at STRING{IEEE_J_IINF = "{IEEE} Transactions on Industrial Informatics"} + at STRING{IEEE_J_PSE = "{IEEE} Journal of Product Safety Engineering"} + + + +instrumentation and measurement + at STRING{IEEE_J_IM = "{IEEE} Transactions on Instrumentation and Measurement"} + + + +insulation and materials + at STRING{IEEE_J_JEM = "{IEEE/TMS} Journal of Electronic Materials"} + at STRING{IEEE_J_DEI = "{IEEE} Transactions on Dielectrics and Electrical Insulation"} + at STRING{IEEE_J_EI = "{IEEE} Transactions on Electrical Insulation"} + + + +mechanical + at STRING{IEEE_J_MECH = "{IEEE/ASME} Transactions on Mechatronics"} + at STRING{IEEE_J_MEMS = "{IEEE/ASME} Journal of Microelectromechanical Systems"} + + + +medical and biological + at STRING{IEEE_J_BME = "{IEEE} Transactions on Biomedical Engineering"} +Note: The B-ME journal later dropped the hyphen and became the BME. + at STRING{IEEE_J_B-ME = "{IEEE} Transactions on Bio-Medical Engineering"} + at STRING{IEEE_J_BMELC = "{IEEE} Transactions on Bio-Medical Electronics"} + at STRING{IEEE_J_CBB = "{IEEE/ACM} Transactions on Computational Biology and Bioinformatics"} + at STRING{IEEE_J_ITBM = "{IEEE} Transactions on Information Technology in Biomedicine"} + at STRING{IEEE_J_ME = "{IEEE} Transactions on Medical Electronics"} + at STRING{IEEE_J_MI = "{IEEE} Transactions on Medical Imaging"} + at STRING{IEEE_J_NB = "{IEEE} Transactions on NanoBioscience"} + at STRING{IEEE_J_NSRE = "{IEEE} Transactions on Neural Systems and Rehabilitation Engineering"} + at STRING{IEEE_J_RE = "{IEEE} Transactions on Rehabilitation Engineering"} + + + +optics, lightwave and photonics + at STRING{IEEE_J_PTL = "{IEEE} Photonics Technology Letters"} + at STRING{IEEE_J_JLT = "{IEEE/OSA} Journal of Lightwave Technology"} + + + +physics, electrons, nanotechnology, nuclear and quantum electronics + at STRING{IEEE_J_EDL = "{IEEE} Electron Device Letters"} + at STRING{IEEE_J_JQE = "{IEEE} Journal of Quantum Electronics"} + at STRING{IEEE_J_JSTQE = "{IEEE} Journal of Selected Topics in Quantum Electronics"} + at STRING{IEEE_J_ED = "{IEEE} Transactions on Electron Devices"} + at STRING{IEEE_J_NANO = "{IEEE} Transactions on Nanotechnology"} + at STRING{IEEE_J_NS = "{IEEE} Transactions on Nuclear Science"} + at STRING{IEEE_J_PS = "{IEEE} Transactions on Plasma Science"} + + + +reliability + at STRING{IEEE_J_DMR = "{IEEE} Transactions on Device and Materials Reliability"} + at STRING{IEEE_J_R = "{IEEE} Transactions on Reliability"} + + + +semiconductors, superconductors, electrochemical and solid state + at STRING{IEEE_J_ESSL = "{IEEE/ECS} Electrochemical and Solid-State Letters"} + at STRING{IEEE_J_JSSC = "{IEEE} Journal of Solid-State Circuits"} + at STRING{IEEE_J_ASC = "{IEEE} Transactions on Applied Superconductivity"} + at STRING{IEEE_J_SM = "{IEEE} Transactions on Semiconductor Manufacturing"} + + + +sensors + at STRING{IEEE_J_SENSOR = "{IEEE} Sensors Journal"} + + + +VLSI + at STRING{IEEE_J_VLSI = "{IEEE} Transactions on Very Large Scale Integration ({VLSI}) Systems"} + + + + + + +IEEE Magazines + + + + at STRING{IEEE_M_AES = "{IEEE} Aerospace and Electronics Systems Magazine"} + at STRING{IEEE_M_HIST = "{IEEE} Annals of the History of Computing"} + at STRING{IEEE_M_AP = "{IEEE} Antennas and Propagation Magazine"} + at STRING{IEEE_M_ASSP = "{IEEE} {ASSP} Magazine"} + at STRING{IEEE_M_CD = "{IEEE} Circuits and Devices Magazine"} + at STRING{IEEE_M_CAS = "{IEEE} Circuits and Systems Magazine"} + at STRING{IEEE_M_COM = "{IEEE} Communications Magazine"} + at STRING{IEEE_M_COMSOC = "{IEEE} Communications Society Magazine"} + at STRING{IEEE_M_CIM = "{IEEE} Computational Intelligence Magazine"} +CSEM changed to CSE in 1999 + at STRING{IEEE_M_CSE = "{IEEE} Computing in Science and Engineering"} + at STRING{IEEE_M_CSEM = "{IEEE} Computational Science and Engineering Magazine"} + at STRING{IEEE_M_C = "{IEEE} Computer"} + at STRING{IEEE_M_CAP = "{IEEE} Computer Applications in Power"} + at STRING{IEEE_M_CGA = "{IEEE} Computer Graphics and Applications"} + at STRING{IEEE_M_CONC = "{IEEE} Concurrency"} + at STRING{IEEE_M_CS = "{IEEE} Control Systems Magazine"} + at STRING{IEEE_M_DTC = "{IEEE} Design and Test of Computers"} + at STRING{IEEE_M_EI = "{IEEE} Electrical Insulation Magazine"} + at STRING{IEEE_M_ETR = "{IEEE} ElectroTechnology Review"} + at STRING{IEEE_M_EMB = "{IEEE} Engineering in Medicine and Biology Magazine"} + at STRING{IEEE_M_EMR = "{IEEE} Engineering Management Review"} + at STRING{IEEE_M_EXP = "{IEEE} Expert"} + at STRING{IEEE_M_IA = "{IEEE} Industry Applications Magazine"} + at STRING{IEEE_M_IM = "{IEEE} Instrumentation and Measurement Magazine"} + at STRING{IEEE_M_IS = "{IEEE} Intelligent Systems"} + at STRING{IEEE_M_IC = "{IEEE} Internet Computing"} + at STRING{IEEE_M_ITP = "{IEEE} {IT} Professional"} + at STRING{IEEE_M_MICRO = "{IEEE} Micro"} + at STRING{IEEE_M_MW = "{IEEE} Microwave Magazine"} + at STRING{IEEE_M_MM = "{IEEE} Multimedia"} + at STRING{IEEE_M_NET = "{IEEE} Network"} + at STRING{IEEE_M_PCOM = "{IEEE} Personal Communications Magazine"} + at STRING{IEEE_M_POT = "{IEEE} Potentials"} +CAP and PER merged to form PE in 2003 + at STRING{IEEE_M_PE = "{IEEE} Power and Energy Magazine"} + at STRING{IEEE_M_PER = "{IEEE} Power Engineering Review"} + at STRING{IEEE_M_PVC = "{IEEE} Pervasive Computing"} + at STRING{IEEE_M_RA = "{IEEE} Robotics and Automation Magazine"} + at STRING{IEEE_M_SAP = "{IEEE} Security and Privacy"} + at STRING{IEEE_M_SP = "{IEEE} Signal Processing Magazine"} + at STRING{IEEE_M_S = "{IEEE} Software"} + at STRING{IEEE_M_SPECT = "{IEEE} Spectrum"} + at STRING{IEEE_M_TS = "{IEEE} Technology and Society Magazine"} + at STRING{IEEE_M_VT = "{IEEE} Vehicular Technology Magazine"} + at STRING{IEEE_M_WC = "{IEEE} Wireless Communications Magazine"} + at STRING{IEEE_M_TODAY = "Today's Engineer"} + + + + + + +IEEE Online Publications + + + + at STRING{IEEE_O_CSTO = "{IEEE} Communications Surveys and Tutorials"} + at STRING{IEEE_O_DSO = "{IEEE} Distributed Systems Online"} + + + + + +-- +EOF Added: text/escience11submission/IEEEtran.bst =================================================================== --- text/escience11submission/IEEEtran.bst (rev 0) +++ text/escience11submission/IEEEtran.bst 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,2417 @@ +%% +%% IEEEtran.bst +%% BibTeX Bibliography Style file for IEEE Journals and Conferences (unsorted) +%% Version 1.12 (2007/01/11) +%% +%% Copyright (c) 2003-2007 Michael Shell +%% +%% Original starting code base and algorithms obtained from the output of +%% Patrick W. Daly's makebst package as well as from prior versions of +%% IEEE BibTeX styles: +%% +%% 1. Howard Trickey and Oren Patashnik's ieeetr.bst (1985/1988) +%% 2. Silvano Balemi and Richard H. Roy's IEEEbib.bst (1993) +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and/or +%% http://www.ieee.org/ +%% +%% For use with BibTeX version 0.99a or later +%% +%% This is a numerical citation style. +%% +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEabrv.bib, IEEEfull.bib, IEEEexample.bib, +%% IEEEtran.bst, IEEEtranS.bst, IEEEtranSA.bst, +%% IEEEtranN.bst, IEEEtranSN.bst, IEEEtran_bst_HOWTO.pdf +%%************************************************************************* +% +% +% Changelog: +% +% 1.00 (2002/08/13) Initial release +% +% 1.10 (2002/09/27) +% 1. Corrected minor bug for improperly formed warning message when a +% book was not given a title. Thanks to Ming Kin Lai for reporting this. +% 2. Added support for CTLname_format_string and CTLname_latex_cmd fields +% in the BST control entry type. +% +% 1.11 (2003/04/02) +% 1. Fixed bug with URLs containing underscores when using url.sty. Thanks +% to Ming Kin Lai for reporting this. +% +% 1.12 (2007/01/11) +% 1. Fixed bug with unwanted comma before "et al." when an entry contained +% more than two author names. Thanks to Pallav Gupta for reporting this. +% 2. Fixed bug with anomalous closing quote in tech reports that have a +% type, but without a number or address. Thanks to Mehrdad Mirreza for +% reporting this. +% 3. Use braces in \providecommand in begin.bib to better support +% latex2html. TeX style length assignments OK with recent versions +% of latex2html - 1.71 (2002/2/1) or later is strongly recommended. +% Use of the language field still causes trouble with latex2html. +% Thanks to Federico Beffa for reporting this. +% 4. Added IEEEtran.bst ID and version comment string to .bbl output. +% 5. Provide a \BIBdecl hook that allows the user to execute commands +% just prior to the first entry. +% 6. Use default urlstyle (is using url.sty) of "same" rather than rm to +% better work with a wider variety of bibliography styles. +% 7. Changed month abbreviations from Sept., July and June to Sep., Jul., +% and Jun., respectively, as IEEE now does. Thanks to Moritz Borgmann +% for reporting this. +% 8. Control entry types should not be considered when calculating longest +% label width. +% 9. Added alias www for electronic/online. +% 10. Added CTLname_url_prefix control entry type. + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% DEFAULTS FOR THE CONTROLS OF THE BST STYLE %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +% These are the defaults for the user adjustable controls. The values used +% here can be overridden by the user via IEEEtranBSTCTL entry type. + +% NOTE: The recommended LaTeX command to invoke a control entry type is: +% +%\makeatletter +%\def\bstctlcite{\@ifnextchar[{\@bstctlcite}{\@bstctlcite[@auxout]}} +%\def\@bstctlcite[#1]#2{\@bsphack +% \@for\@citeb:=#2\do{% +% \edef\@citeb{\expandafter\@firstofone\@citeb}% +% \if at filesw\immediate\write\csname #1\endcsname{\string\citation{\@citeb}}\fi}% +% \@esphack} +%\makeatother +% +% It is called at the start of the document, before the first \cite, like: +% \bstctlcite{IEEEexample:BSTcontrol} +% +% IEEEtran.cls V1.6 and later does provide this command. + + + +% #0 turns off the display of the number for articles. +% #1 enables +FUNCTION {default.is.use.number.for.article} { #1 } + + +% #0 turns off the display of the paper and type fields in @inproceedings. +% #1 enables +FUNCTION {default.is.use.paper} { #1 } + + +% #0 turns off the forced use of "et al." +% #1 enables +FUNCTION {default.is.forced.et.al} { #0 } + +% The maximum number of names that can be present beyond which an "et al." +% usage is forced. Be sure that num.names.shown.with.forced.et.al (below) +% is not greater than this value! +% Note: There are many instances of references in IEEE journals which have +% a very large number of authors as well as instances in which "et al." is +% used profusely. +FUNCTION {default.max.num.names.before.forced.et.al} { #10 } + +% The number of names that will be shown with a forced "et al.". +% Must be less than or equal to max.num.names.before.forced.et.al +FUNCTION {default.num.names.shown.with.forced.et.al} { #1 } + + +% #0 turns off the alternate interword spacing for entries with URLs. +% #1 enables +FUNCTION {default.is.use.alt.interword.spacing} { #1 } + +% If alternate interword spacing for entries with URLs is enabled, this is +% the interword spacing stretch factor that will be used. For example, the +% default "4" here means that the interword spacing in entries with URLs can +% stretch to four times normal. Does not have to be an integer. Note that +% the value specified here can be overridden by the user in their LaTeX +% code via a command such as: +% "\providecommand\BIBentryALTinterwordstretchfactor{1.5}" in addition to +% that via the IEEEtranBSTCTL entry type. +FUNCTION {default.ALTinterwordstretchfactor} { "4" } + + +% #0 turns off the "dashification" of repeated (i.e., identical to those +% of the previous entry) names. IEEE normally does this. +% #1 enables +FUNCTION {default.is.dash.repeated.names} { #1 } + + +% The default name format control string. +FUNCTION {default.name.format.string}{ "{f.~}{vv~}{ll}{, jj}" } + + +% The default LaTeX font command for the names. +FUNCTION {default.name.latex.cmd}{ "" } + + +% The default URL prefix. +FUNCTION {default.name.url.prefix}{ "[Online]. Available:" } + + +% Other controls that cannot be accessed via IEEEtranBSTCTL entry type. + +% #0 turns off the terminal startup banner/completed message so as to +% operate more quietly. +% #1 enables +FUNCTION {is.print.banners.to.terminal} { #1 } + + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% FILE VERSION AND BANNER %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION{bst.file.version} { "1.12" } +FUNCTION{bst.file.date} { "2007/01/11" } +FUNCTION{bst.file.website} { "http://www.michaelshell.org/tex/ieeetran/bibtex/" } + +FUNCTION {banner.message} +{ is.print.banners.to.terminal + { "-- IEEEtran.bst version" " " * bst.file.version * + " (" * bst.file.date * ") " * "by Michael Shell." * + top$ + "-- " bst.file.website * + top$ + "-- See the " quote$ * "IEEEtran_bst_HOWTO.pdf" * quote$ * " manual for usage information." * + top$ + } + { skip$ } + if$ +} + +FUNCTION {completed.message} +{ is.print.banners.to.terminal + { "" + top$ + "Done." + top$ + } + { skip$ } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%% +%% STRING CONSTANTS %% +%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {bbl.and}{ "and" } +FUNCTION {bbl.etal}{ "et~al." } +FUNCTION {bbl.editors}{ "eds." } +FUNCTION {bbl.editor}{ "ed." } +FUNCTION {bbl.edition}{ "ed." } +FUNCTION {bbl.volume}{ "vol." } +FUNCTION {bbl.of}{ "of" } +FUNCTION {bbl.number}{ "no." } +FUNCTION {bbl.in}{ "in" } +FUNCTION {bbl.pages}{ "pp." } +FUNCTION {bbl.page}{ "p." } +FUNCTION {bbl.chapter}{ "ch." } +FUNCTION {bbl.paper}{ "paper" } +FUNCTION {bbl.part}{ "pt." } +FUNCTION {bbl.patent}{ "Patent" } +FUNCTION {bbl.patentUS}{ "U.S." } +FUNCTION {bbl.revision}{ "Rev." } +FUNCTION {bbl.series}{ "ser." } +FUNCTION {bbl.standard}{ "Std." } +FUNCTION {bbl.techrep}{ "Tech. Rep." } +FUNCTION {bbl.mthesis}{ "Master's thesis" } +FUNCTION {bbl.phdthesis}{ "Ph.D. dissertation" } +FUNCTION {bbl.st}{ "st" } +FUNCTION {bbl.nd}{ "nd" } +FUNCTION {bbl.rd}{ "rd" } +FUNCTION {bbl.th}{ "th" } + + +% This is the LaTeX spacer that is used when a larger than normal space +% is called for (such as just before the address:publisher). +FUNCTION {large.space} { "\hskip 1em plus 0.5em minus 0.4em\relax " } + +% The LaTeX code for dashes that are used to represent repeated names. +% Note: Some older IEEE journals used something like +% "\rule{0.275in}{0.5pt}\," which is fairly thick and runs right along +% the baseline. However, IEEE now uses a thinner, above baseline, +% six dash long sequence. +FUNCTION {repeated.name.dashes} { "------" } + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% PREDEFINED STRING MACROS %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +MACRO {jan} {"Jan."} +MACRO {feb} {"Feb."} +MACRO {mar} {"Mar."} +MACRO {apr} {"Apr."} +MACRO {may} {"May"} +MACRO {jun} {"Jun."} +MACRO {jul} {"Jul."} +MACRO {aug} {"Aug."} +MACRO {sep} {"Sep."} +MACRO {oct} {"Oct."} +MACRO {nov} {"Nov."} +MACRO {dec} {"Dec."} + + + +%%%%%%%%%%%%%%%%%% +%% ENTRY FIELDS %% +%%%%%%%%%%%%%%%%%% + +ENTRY + { address + assignee + author + booktitle + chapter + day + dayfiled + edition + editor + howpublished + institution + intype + journal + key + language + month + monthfiled + nationality + note + number + organization + pages + paper + publisher + school + series + revision + title + type + url + volume + year + yearfiled + CTLuse_article_number + CTLuse_paper + CTLuse_forced_etal + CTLmax_names_forced_etal + CTLnames_show_etal + CTLuse_alt_spacing + CTLalt_stretch_factor + CTLdash_repeated_names + CTLname_format_string + CTLname_latex_cmd + CTLname_url_prefix + } + {} + { label } + + + + +%%%%%%%%%%%%%%%%%%%%%%% +%% INTEGER VARIABLES %% +%%%%%%%%%%%%%%%%%%%%%%% + +INTEGERS { prev.status.punct this.status.punct punct.std + punct.no punct.comma punct.period + prev.status.space this.status.space space.std + space.no space.normal space.large + prev.status.quote this.status.quote quote.std + quote.no quote.close + prev.status.nline this.status.nline nline.std + nline.no nline.newblock + status.cap cap.std + cap.no cap.yes} + +INTEGERS { longest.label.width multiresult nameptr namesleft number.label numnames } + +INTEGERS { is.use.number.for.article + is.use.paper + is.forced.et.al + max.num.names.before.forced.et.al + num.names.shown.with.forced.et.al + is.use.alt.interword.spacing + is.dash.repeated.names} + + +%%%%%%%%%%%%%%%%%%%%%% +%% STRING VARIABLES %% +%%%%%%%%%%%%%%%%%%%%%% + +STRINGS { bibinfo + longest.label + oldname + s + t + ALTinterwordstretchfactor + name.format.string + name.latex.cmd + name.url.prefix} + + + + +%%%%%%%%%%%%%%%%%%%%%%%%% +%% LOW LEVEL FUNCTIONS %% +%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {initialize.controls} +{ default.is.use.number.for.article 'is.use.number.for.article := + default.is.use.paper 'is.use.paper := + default.is.forced.et.al 'is.forced.et.al := + default.max.num.names.before.forced.et.al 'max.num.names.before.forced.et.al := + default.num.names.shown.with.forced.et.al 'num.names.shown.with.forced.et.al := + default.is.use.alt.interword.spacing 'is.use.alt.interword.spacing := + default.is.dash.repeated.names 'is.dash.repeated.names := + default.ALTinterwordstretchfactor 'ALTinterwordstretchfactor := + default.name.format.string 'name.format.string := + default.name.latex.cmd 'name.latex.cmd := + default.name.url.prefix 'name.url.prefix := +} + + +% This IEEEtran.bst features a very powerful and flexible mechanism for +% controlling the capitalization, punctuation, spacing, quotation, and +% newlines of the formatted entry fields. (Note: IEEEtran.bst does not need +% or use the newline/newblock feature, but it has been implemented for +% possible future use.) The output states of IEEEtran.bst consist of +% multiple independent attributes and, as such, can be thought of as being +% vectors, rather than the simple scalar values ("before.all", +% "mid.sentence", etc.) used in most other .bst files. +% +% The more flexible and complex design used here was motivated in part by +% IEEE's rather unusual bibliography style. For example, IEEE ends the +% previous field item with a period and large space prior to the publisher +% address; the @electronic entry types use periods as inter-item punctuation +% rather than the commas used by the other entry types; and URLs are never +% followed by periods even though they are the last item in the entry. +% Although it is possible to accommodate these features with the conventional +% output state system, the seemingly endless exceptions make for convoluted, +% unreliable and difficult to maintain code. +% +% IEEEtran.bst's output state system can be easily understood via a simple +% illustration of two most recently formatted entry fields (on the stack): +% +% CURRENT_ITEM +% "PREVIOUS_ITEM +% +% which, in this example, is to eventually appear in the bibliography as: +% +% "PREVIOUS_ITEM," CURRENT_ITEM +% +% It is the job of the output routine to take the previous item off of the +% stack (while leaving the current item at the top of the stack), apply its +% trailing punctuation (including closing quote marks) and spacing, and then +% to write the result to BibTeX's output buffer: +% +% "PREVIOUS_ITEM," +% +% Punctuation (and spacing) between items is often determined by both of the +% items rather than just the first one. The presence of quotation marks +% further complicates the situation because, in standard English, trailing +% punctuation marks are supposed to be contained within the quotes. +% +% IEEEtran.bst maintains two output state (aka "status") vectors which +% correspond to the previous and current (aka "this") items. Each vector +% consists of several independent attributes which track punctuation, +% spacing, quotation, and newlines. Capitalization status is handled by a +% separate scalar because the format routines, not the output routine, +% handle capitalization and, therefore, there is no need to maintain the +% capitalization attribute for both the "previous" and "this" items. +% +% When a format routine adds a new item, it copies the current output status +% vector to the previous output status vector and (usually) resets the +% current (this) output status vector to a "standard status" vector. Using a +% "standard status" vector in this way allows us to redefine what we mean by +% "standard status" at the start of each entry handler and reuse the same +% format routines under the various inter-item separation schemes. For +% example, the standard status vector for the @book entry type may use +% commas for item separators, while the @electronic type may use periods, +% yet both entry handlers exploit many of the exact same format routines. +% +% Because format routines have write access to the output status vector of +% the previous item, they can override the punctuation choices of the +% previous format routine! Therefore, it becomes trivial to implement rules +% such as "Always use a period and a large space before the publisher." By +% pushing the generation of the closing quote mark to the output routine, we +% avoid all the problems caused by having to close a quote before having all +% the information required to determine what the punctuation should be. +% +% The IEEEtran.bst output state system can easily be expanded if needed. +% For instance, it is easy to add a "space.tie" attribute value if the +% bibliography rules mandate that two items have to be joined with an +% unbreakable space. + +FUNCTION {initialize.status.constants} +{ #0 'punct.no := + #1 'punct.comma := + #2 'punct.period := + #0 'space.no := + #1 'space.normal := + #2 'space.large := + #0 'quote.no := + #1 'quote.close := + #0 'cap.no := + #1 'cap.yes := + #0 'nline.no := + #1 'nline.newblock := +} + +FUNCTION {std.status.using.comma} +{ punct.comma 'punct.std := + space.normal 'space.std := + quote.no 'quote.std := + nline.no 'nline.std := + cap.no 'cap.std := +} + +FUNCTION {std.status.using.period} +{ punct.period 'punct.std := + space.normal 'space.std := + quote.no 'quote.std := + nline.no 'nline.std := + cap.yes 'cap.std := +} + +FUNCTION {initialize.prev.this.status} +{ punct.no 'prev.status.punct := + space.no 'prev.status.space := + quote.no 'prev.status.quote := + nline.no 'prev.status.nline := + punct.no 'this.status.punct := + space.no 'this.status.space := + quote.no 'this.status.quote := + nline.no 'this.status.nline := + cap.yes 'status.cap := +} + +FUNCTION {this.status.std} +{ punct.std 'this.status.punct := + space.std 'this.status.space := + quote.std 'this.status.quote := + nline.std 'this.status.nline := +} + +FUNCTION {cap.status.std}{ cap.std 'status.cap := } + +FUNCTION {this.to.prev.status} +{ this.status.punct 'prev.status.punct := + this.status.space 'prev.status.space := + this.status.quote 'prev.status.quote := + this.status.nline 'prev.status.nline := +} + + +FUNCTION {not} +{ { #0 } + { #1 } + if$ +} + +FUNCTION {and} +{ { skip$ } + { pop$ #0 } + if$ +} + +FUNCTION {or} +{ { pop$ #1 } + { skip$ } + if$ +} + + +% convert the strings "yes" or "no" to #1 or #0 respectively +FUNCTION {yes.no.to.int} +{ "l" change.case$ duplicate$ + "yes" = + { pop$ #1 } + { duplicate$ "no" = + { pop$ #0 } + { "unknown boolean " quote$ * swap$ * quote$ * + " in " * cite$ * warning$ + #0 + } + if$ + } + if$ +} + + +% pushes true if the single char string on the stack is in the +% range of "0" to "9" +FUNCTION {is.num} +{ chr.to.int$ + duplicate$ "0" chr.to.int$ < not + swap$ "9" chr.to.int$ > not and +} + +% multiplies the integer on the stack by a factor of 10 +FUNCTION {bump.int.mag} +{ #0 'multiresult := + { duplicate$ #0 > } + { #1 - + multiresult #10 + + 'multiresult := + } + while$ +pop$ +multiresult +} + +% converts a single character string on the stack to an integer +FUNCTION {char.to.integer} +{ duplicate$ + is.num + { chr.to.int$ "0" chr.to.int$ - } + {"noninteger character " quote$ * swap$ * quote$ * + " in integer field of " * cite$ * warning$ + #0 + } + if$ +} + +% converts a string on the stack to an integer +FUNCTION {string.to.integer} +{ duplicate$ text.length$ 'namesleft := + #1 'nameptr := + #0 'numnames := + { nameptr namesleft > not } + { duplicate$ nameptr #1 substring$ + char.to.integer numnames bump.int.mag + + 'numnames := + nameptr #1 + + 'nameptr := + } + while$ +pop$ +numnames +} + + + + +% The output routines write out the *next* to the top (previous) item on the +% stack, adding punctuation and such as needed. Since IEEEtran.bst maintains +% the output status for the top two items on the stack, these output +% routines have to consider the previous output status (which corresponds to +% the item that is being output). Full independent control of punctuation, +% closing quote marks, spacing, and newblock is provided. +% +% "output.nonnull" does not check for the presence of a previous empty +% item. +% +% "output" does check for the presence of a previous empty item and will +% remove an empty item rather than outputing it. +% +% "output.warn" is like "output", but will issue a warning if it detects +% an empty item. + +FUNCTION {output.nonnull} +{ swap$ + prev.status.punct punct.comma = + { "," * } + { skip$ } + if$ + prev.status.punct punct.period = + { add.period$ } + { skip$ } + if$ + prev.status.quote quote.close = + { "''" * } + { skip$ } + if$ + prev.status.space space.normal = + { " " * } + { skip$ } + if$ + prev.status.space space.large = + { large.space * } + { skip$ } + if$ + write$ + prev.status.nline nline.newblock = + { newline$ "\newblock " write$ } + { skip$ } + if$ +} + +FUNCTION {output} +{ duplicate$ empty$ + 'pop$ + 'output.nonnull + if$ +} + +FUNCTION {output.warn} +{ 't := + duplicate$ empty$ + { pop$ "empty " t * " in " * cite$ * warning$ } + 'output.nonnull + if$ +} + +% "fin.entry" is the output routine that handles the last item of the entry +% (which will be on the top of the stack when "fin.entry" is called). + +FUNCTION {fin.entry} +{ this.status.punct punct.no = + { skip$ } + { add.period$ } + if$ + this.status.quote quote.close = + { "''" * } + { skip$ } + if$ +write$ +newline$ +} + + +FUNCTION {is.last.char.not.punct} +{ duplicate$ + "}" * add.period$ + #-1 #1 substring$ "." = +} + +FUNCTION {is.multiple.pages} +{ 't := + #0 'multiresult := + { multiresult not + t empty$ not + and + } + { t #1 #1 substring$ + duplicate$ "-" = + swap$ duplicate$ "," = + swap$ "+" = + or or + { #1 'multiresult := } + { t #2 global.max$ substring$ 't := } + if$ + } + while$ + multiresult +} + +FUNCTION {capitalize}{ "u" change.case$ "t" change.case$ } + +FUNCTION {emphasize} +{ duplicate$ empty$ + { pop$ "" } + { "\emph{" swap$ * "}" * } + if$ +} + +FUNCTION {do.name.latex.cmd} +{ name.latex.cmd + empty$ + { skip$ } + { name.latex.cmd "{" * swap$ * "}" * } + if$ +} + +% IEEEtran.bst uses its own \BIBforeignlanguage command which directly +% invokes the TeX hyphenation patterns without the need of the Babel +% package. Babel does a lot more than switch hyphenation patterns and +% its loading can cause unintended effects in many class files (such as +% IEEEtran.cls). +FUNCTION {select.language} +{ duplicate$ empty$ 'pop$ + { language empty$ 'skip$ + { "\BIBforeignlanguage{" language * "}{" * swap$ * "}" * } + if$ + } + if$ +} + +FUNCTION {tie.or.space.prefix} +{ duplicate$ text.length$ #3 < + { "~" } + { " " } + if$ + swap$ +} + +FUNCTION {get.bbl.editor} +{ editor num.names$ #1 > 'bbl.editors 'bbl.editor if$ } + +FUNCTION {space.word}{ " " swap$ * " " * } + + +% Field Conditioners, Converters, Checkers and External Interfaces + +FUNCTION {empty.field.to.null.string} +{ duplicate$ empty$ + { pop$ "" } + { skip$ } + if$ +} + +FUNCTION {either.or.check} +{ empty$ + { pop$ } + { "can't use both " swap$ * " fields in " * cite$ * warning$ } + if$ +} + +FUNCTION {empty.entry.warn} +{ author empty$ title empty$ howpublished empty$ + month empty$ year empty$ note empty$ url empty$ + and and and and and and + { "all relevant fields are empty in " cite$ * warning$ } + 'skip$ + if$ +} + + +% The bibinfo system provides a way for the electronic parsing/acquisition +% of a bibliography's contents as is done by ReVTeX. For example, a field +% could be entered into the bibliography as: +% \bibinfo{volume}{2} +% Only the "2" would show up in the document, but the LaTeX \bibinfo command +% could do additional things with the information. IEEEtran.bst does provide +% a \bibinfo command via "\providecommand{\bibinfo}[2]{#2}". However, it is +% currently not used as the bogus bibinfo functions defined here output the +% entry values directly without the \bibinfo wrapper. The bibinfo functions +% themselves (and the calls to them) are retained for possible future use. +% +% bibinfo.check avoids acting on missing fields while bibinfo.warn will +% issue a warning message if a missing field is detected. Prior to calling +% the bibinfo functions, the user should push the field value and then its +% name string, in that order. + +FUNCTION {bibinfo.check} +{ swap$ duplicate$ missing$ + { pop$ pop$ "" } + { duplicate$ empty$ + { swap$ pop$ } + { swap$ pop$ } + if$ + } + if$ +} + +FUNCTION {bibinfo.warn} +{ swap$ duplicate$ missing$ + { swap$ "missing " swap$ * " in " * cite$ * warning$ pop$ "" } + { duplicate$ empty$ + { swap$ "empty " swap$ * " in " * cite$ * warning$ } + { swap$ pop$ } + if$ + } + if$ +} + + +% IEEE separates large numbers with more than 4 digits into groups of +% three. IEEE uses a small space to separate these number groups. +% Typical applications include patent and page numbers. + +% number of consecutive digits required to trigger the group separation. +FUNCTION {large.number.trigger}{ #5 } + +% For numbers longer than the trigger, this is the blocksize of the groups. +% The blocksize must be less than the trigger threshold, and 2 * blocksize +% must be greater than the trigger threshold (can't do more than one +% separation on the initial trigger). +FUNCTION {large.number.blocksize}{ #3 } + +% What is actually inserted between the number groups. +FUNCTION {large.number.separator}{ "\," } + +% So as to save on integer variables by reusing existing ones, numnames +% holds the current number of consecutive digits read and nameptr holds +% the number that will trigger an inserted space. +FUNCTION {large.number.separate} +{ 't := + "" + #0 'numnames := + large.number.trigger 'nameptr := + { t empty$ not } + { t #-1 #1 substring$ is.num + { numnames #1 + 'numnames := } + { #0 'numnames := + large.number.trigger 'nameptr := + } + if$ + t #-1 #1 substring$ swap$ * + t #-2 global.max$ substring$ 't := + numnames nameptr = + { duplicate$ #1 nameptr large.number.blocksize - substring$ swap$ + nameptr large.number.blocksize - #1 + global.max$ substring$ + large.number.separator swap$ * * + nameptr large.number.blocksize - 'numnames := + large.number.blocksize #1 + 'nameptr := + } + { skip$ } + if$ + } + while$ +} + +% Converts all single dashes "-" to double dashes "--". +FUNCTION {n.dashify} +{ large.number.separate + 't := + "" + { t empty$ not } + { t #1 #1 substring$ "-" = + { t #1 #2 substring$ "--" = not + { "--" * + t #2 global.max$ substring$ 't := + } + { { t #1 #1 substring$ "-" = } + { "-" * + t #2 global.max$ substring$ 't := + } + while$ + } + if$ + } + { t #1 #1 substring$ * + t #2 global.max$ substring$ 't := + } + if$ + } + while$ +} + + +% This function detects entries with names that are identical to that of +% the previous entry and replaces the repeated names with dashes (if the +% "is.dash.repeated.names" user control is nonzero). +FUNCTION {name.or.dash} +{ 's := + oldname empty$ + { s 'oldname := s } + { s oldname = + { is.dash.repeated.names + { repeated.name.dashes } + { s 'oldname := s } + if$ + } + { s 'oldname := s } + if$ + } + if$ +} + +% Converts the number string on the top of the stack to +% "numerical ordinal form" (e.g., "7" to "7th"). There is +% no artificial limit to the upper bound of the numbers as the +% least significant digit always determines the ordinal form. +FUNCTION {num.to.ordinal} +{ duplicate$ #-1 #1 substring$ "1" = + { bbl.st * } + { duplicate$ #-1 #1 substring$ "2" = + { bbl.nd * } + { duplicate$ #-1 #1 substring$ "3" = + { bbl.rd * } + { bbl.th * } + if$ + } + if$ + } + if$ +} + +% If the string on the top of the stack begins with a number, +% (e.g., 11th) then replace the string with the leading number +% it contains. Otherwise retain the string as-is. s holds the +% extracted number, t holds the part of the string that remains +% to be scanned. +FUNCTION {extract.num} +{ duplicate$ 't := + "" 's := + { t empty$ not } + { t #1 #1 substring$ + t #2 global.max$ substring$ 't := + duplicate$ is.num + { s swap$ * 's := } + { pop$ "" 't := } + if$ + } + while$ + s empty$ + 'skip$ + { pop$ s } + if$ +} + +% Converts the word number string on the top of the stack to +% Arabic string form. Will be successful up to "tenth". +FUNCTION {word.to.num} +{ duplicate$ "l" change.case$ 's := + s "first" = + { pop$ "1" } + { skip$ } + if$ + s "second" = + { pop$ "2" } + { skip$ } + if$ + s "third" = + { pop$ "3" } + { skip$ } + if$ + s "fourth" = + { pop$ "4" } + { skip$ } + if$ + s "fifth" = + { pop$ "5" } + { skip$ } + if$ + s "sixth" = + { pop$ "6" } + { skip$ } + if$ + s "seventh" = + { pop$ "7" } + { skip$ } + if$ + s "eighth" = + { pop$ "8" } + { skip$ } + if$ + s "ninth" = + { pop$ "9" } + { skip$ } + if$ + s "tenth" = + { pop$ "10" } + { skip$ } + if$ +} + + +% Converts the string on the top of the stack to numerical +% ordinal (e.g., "11th") form. +FUNCTION {convert.edition} +{ duplicate$ empty$ 'skip$ + { duplicate$ #1 #1 substring$ is.num + { extract.num + num.to.ordinal + } + { word.to.num + duplicate$ #1 #1 substring$ is.num + { num.to.ordinal } + { "edition ordinal word " quote$ * edition * quote$ * + " may be too high (or improper) for conversion" * " in " * cite$ * warning$ + } + if$ + } + if$ + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% LATEX BIBLIOGRAPHY CODE %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {start.entry} +{ newline$ + "\bibitem{" write$ + cite$ write$ + "}" write$ + newline$ + "" + initialize.prev.this.status +} + +% Here we write out all the LaTeX code that we will need. The most involved +% code sequences are those that control the alternate interword spacing and +% foreign language hyphenation patterns. The heavy use of \providecommand +% gives users a way to override the defaults. Special thanks to Javier Bezos, +% Johannes Braams, Robin Fairbairns, Heiko Oberdiek, Donald Arseneau and all +% the other gurus on comp.text.tex for their help and advice on the topic of +% \selectlanguage, Babel and BibTeX. +FUNCTION {begin.bib} +{ "% Generated by IEEEtran.bst, version: " bst.file.version * " (" * bst.file.date * ")" * + write$ newline$ + preamble$ empty$ 'skip$ + { preamble$ write$ newline$ } + if$ + "\begin{thebibliography}{" longest.label * "}" * + write$ newline$ + "\providecommand{\url}[1]{#1}" + write$ newline$ + "\csname url at samestyle\endcsname" + write$ newline$ + "\providecommand{\newblock}{\relax}" + write$ newline$ + "\providecommand{\bibinfo}[2]{#2}" + write$ newline$ + "\providecommand{\BIBentrySTDinterwordspacing}{\spaceskip=0pt\relax}" + write$ newline$ + "\providecommand{\BIBentryALTinterwordstretchfactor}{" + ALTinterwordstretchfactor * "}" * + write$ newline$ + "\providecommand{\BIBentryALTinterwordspacing}{\spaceskip=\fontdimen2\font plus " + write$ newline$ + "\BIBentryALTinterwordstretchfactor\fontdimen3\font minus \fontdimen4\font\relax}" + write$ newline$ + "\providecommand{\BIBforeignlanguage}[2]{{%" + write$ newline$ + "\expandafter\ifx\csname l@#1\endcsname\relax" + write$ newline$ + "\typeout{** WARNING: IEEEtran.bst: No hyphenation pattern has been}%" + write$ newline$ + "\typeout{** loaded for the language `#1'. Using the pattern for}%" + write$ newline$ + "\typeout{** the default language instead.}%" + write$ newline$ + "\else" + write$ newline$ + "\language=\csname l@#1\endcsname" + write$ newline$ + "\fi" + write$ newline$ + "#2}}" + write$ newline$ + "\providecommand{\BIBdecl}{\relax}" + write$ newline$ + "\BIBdecl" + write$ newline$ +} + +FUNCTION {end.bib} +{ newline$ "\end{thebibliography}" write$ newline$ } + +FUNCTION {if.url.alt.interword.spacing} +{ is.use.alt.interword.spacing + {url empty$ 'skip$ {"\BIBentryALTinterwordspacing" write$ newline$} if$} + { skip$ } + if$ +} + +FUNCTION {if.url.std.interword.spacing} +{ is.use.alt.interword.spacing + {url empty$ 'skip$ {"\BIBentrySTDinterwordspacing" write$ newline$} if$} + { skip$ } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%%%% +%% LONGEST LABEL PASS %% +%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {initialize.longest.label} +{ "" 'longest.label := + #1 'number.label := + #0 'longest.label.width := +} + +FUNCTION {longest.label.pass} +{ type$ "ieeetranbstctl" = + { skip$ } + { number.label int.to.str$ 'label := + number.label #1 + 'number.label := + label width$ longest.label.width > + { label 'longest.label := + label width$ 'longest.label.width := + } + { skip$ } + if$ + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%% +%% FORMAT HANDLERS %% +%%%%%%%%%%%%%%%%%%%%% + +%% Lower Level Formats (used by higher level formats) + +FUNCTION {format.address.org.or.pub.date} +{ 't := + "" + year empty$ + { "empty year in " cite$ * warning$ } + { skip$ } + if$ + address empty$ t empty$ and + year empty$ and month empty$ and + { skip$ } + { this.to.prev.status + this.status.std + cap.status.std + address "address" bibinfo.check * + t empty$ + { skip$ } + { punct.period 'prev.status.punct := + space.large 'prev.status.space := + address empty$ + { skip$ } + { ": " * } + if$ + t * + } + if$ + year empty$ month empty$ and + { skip$ } + { t empty$ address empty$ and + { skip$ } + { ", " * } + if$ + month empty$ + { year empty$ + { skip$ } + { year "year" bibinfo.check * } + if$ + } + { month "month" bibinfo.check * + year empty$ + { skip$ } + { " " * year "year" bibinfo.check * } + if$ + } + if$ + } + if$ + } + if$ +} + + +FUNCTION {format.names} +{ 'bibinfo := + duplicate$ empty$ 'skip$ { + this.to.prev.status + this.status.std + 's := + "" 't := + #1 'nameptr := + s num.names$ 'numnames := + numnames 'namesleft := + { namesleft #0 > } + { s nameptr + name.format.string + format.name$ + bibinfo bibinfo.check + 't := + nameptr #1 > + { nameptr num.names.shown.with.forced.et.al #1 + = + numnames max.num.names.before.forced.et.al > + is.forced.et.al and and + { "others" 't := + #1 'namesleft := + } + { skip$ } + if$ + namesleft #1 > + { ", " * t do.name.latex.cmd * } + { s nameptr "{ll}" format.name$ duplicate$ "others" = + { 't := } + { pop$ } + if$ + t "others" = + { " " * bbl.etal emphasize * } + { numnames #2 > + { "," * } + { skip$ } + if$ + bbl.and + space.word * t do.name.latex.cmd * + } + if$ + } + if$ + } + { t do.name.latex.cmd } + if$ + nameptr #1 + 'nameptr := + namesleft #1 - 'namesleft := + } + while$ + cap.status.std + } if$ +} + + + + +%% Higher Level Formats + +%% addresses/locations + +FUNCTION {format.address} +{ address duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% author/editor names + +FUNCTION {format.authors}{ author "author" format.names } + +FUNCTION {format.editors} +{ editor "editor" format.names duplicate$ empty$ 'skip$ + { ", " * + get.bbl.editor + capitalize + * + } + if$ +} + + + +%% date + +FUNCTION {format.date} +{ + month "month" bibinfo.check duplicate$ empty$ + year "year" bibinfo.check duplicate$ empty$ + { swap$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + "there's a month but no year in " cite$ * warning$ } + if$ + * + } + { this.to.prev.status + this.status.std + cap.status.std + swap$ 'skip$ + { + swap$ + " " * swap$ + } + if$ + * + } + if$ +} + +FUNCTION {format.date.electronic} +{ month "month" bibinfo.check duplicate$ empty$ + year "year" bibinfo.check duplicate$ empty$ + { swap$ + { pop$ } + { "there's a month but no year in " cite$ * warning$ + pop$ ")" * "(" swap$ * + this.to.prev.status + punct.no 'this.status.punct := + space.normal 'this.status.space := + quote.no 'this.status.quote := + cap.yes 'status.cap := + } + if$ + } + { swap$ + { swap$ pop$ ")" * "(" swap$ * } + { "(" swap$ * ", " * swap$ * ")" * } + if$ + this.to.prev.status + punct.no 'this.status.punct := + space.normal 'this.status.space := + quote.no 'this.status.quote := + cap.yes 'status.cap := + } + if$ +} + + + +%% edition/title + +% Note: IEEE considers the edition to be closely associated with +% the title of a book. So, in IEEEtran.bst the edition is normally handled +% within the formatting of the title. The format.edition function is +% retained here for possible future use. +FUNCTION {format.edition} +{ edition duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + convert.edition + status.cap + { "t" } + { "l" } + if$ change.case$ + "edition" bibinfo.check + "~" * bbl.edition * + cap.status.std + } + if$ +} + +% This is used to format the booktitle of a conference proceedings. +% Here we use the "intype" field to provide the user a way to +% override the word "in" (e.g., with things like "presented at") +% Use of intype stops the emphasis of the booktitle to indicate that +% we no longer mean the written conference proceedings, but the +% conference itself. +FUNCTION {format.in.booktitle} +{ booktitle "booktitle" bibinfo.check duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + select.language + intype missing$ + { emphasize + bbl.in " " * + } + { intype " " * } + if$ + swap$ * + cap.status.std + } + if$ +} + +% This is used to format the booktitle of collection. +% Here the "intype" field is not supported, but "edition" is. +FUNCTION {format.in.booktitle.edition} +{ booktitle "booktitle" bibinfo.check duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + select.language + emphasize + edition empty$ 'skip$ + { ", " * + edition + convert.edition + "l" change.case$ + * "~" * bbl.edition * + } + if$ + bbl.in " " * swap$ * + cap.status.std + } + if$ +} + +FUNCTION {format.article.title} +{ title duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + "t" change.case$ + } + if$ + "title" bibinfo.check + duplicate$ empty$ 'skip$ + { quote.close 'this.status.quote := + is.last.char.not.punct + { punct.std 'this.status.punct := } + { punct.no 'this.status.punct := } + if$ + select.language + "``" swap$ * + cap.status.std + } + if$ +} + +FUNCTION {format.article.title.electronic} +{ title duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + "t" change.case$ + } + if$ + "title" bibinfo.check + duplicate$ empty$ + { skip$ } + { select.language } + if$ +} + +FUNCTION {format.book.title.edition} +{ title "title" bibinfo.check + duplicate$ empty$ + { "empty title in " cite$ * warning$ } + { this.to.prev.status + this.status.std + select.language + emphasize + edition empty$ 'skip$ + { ", " * + edition + convert.edition + status.cap + { "t" } + { "l" } + if$ + change.case$ + * "~" * bbl.edition * + } + if$ + cap.status.std + } + if$ +} + +FUNCTION {format.book.title} +{ title "title" bibinfo.check + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + select.language + emphasize + } + if$ +} + + + +%% journal + +FUNCTION {format.journal} +{ journal duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + select.language + emphasize + } + if$ +} + + + +%% how published + +FUNCTION {format.howpublished} +{ howpublished duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% institutions/organization/publishers/school + +FUNCTION {format.institution} +{ institution duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + +FUNCTION {format.organization} +{ organization duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + +FUNCTION {format.address.publisher.date} +{ publisher "publisher" bibinfo.warn format.address.org.or.pub.date } + +FUNCTION {format.address.publisher.date.nowarn} +{ publisher "publisher" bibinfo.check format.address.org.or.pub.date } + +FUNCTION {format.address.organization.date} +{ organization "organization" bibinfo.check format.address.org.or.pub.date } + +FUNCTION {format.school} +{ school duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% volume/number/series/chapter/pages + +FUNCTION {format.volume} +{ volume empty.field.to.null.string + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + bbl.volume + status.cap + { capitalize } + { skip$ } + if$ + swap$ tie.or.space.prefix + "volume" bibinfo.check + * * + cap.status.std + } + if$ +} + +FUNCTION {format.number} +{ number empty.field.to.null.string + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + status.cap + { bbl.number capitalize } + { bbl.number } + if$ + swap$ tie.or.space.prefix + "number" bibinfo.check + * * + cap.status.std + } + if$ +} + +FUNCTION {format.number.if.use.for.article} +{ is.use.number.for.article + { format.number } + { "" } + if$ +} + +% IEEE does not seem to tie the series so closely with the volume +% and number as is done in other bibliography styles. Instead the +% series is treated somewhat like an extension of the title. +FUNCTION {format.series} +{ series empty$ + { "" } + { this.to.prev.status + this.status.std + bbl.series " " * + series "series" bibinfo.check * + cap.status.std + } + if$ +} + + +FUNCTION {format.chapter} +{ chapter empty$ + { "" } + { this.to.prev.status + this.status.std + type empty$ + { bbl.chapter } + { type "l" change.case$ + "type" bibinfo.check + } + if$ + chapter tie.or.space.prefix + "chapter" bibinfo.check + * * + cap.status.std + } + if$ +} + + +% The intended use of format.paper is for paper numbers of inproceedings. +% The paper type can be overridden via the type field. +% We allow the type to be displayed even if the paper number is absent +% for things like "postdeadline paper" +FUNCTION {format.paper} +{ is.use.paper + { paper empty$ + { type empty$ + { "" } + { this.to.prev.status + this.status.std + type "type" bibinfo.check + cap.status.std + } + if$ + } + { this.to.prev.status + this.status.std + type empty$ + { bbl.paper } + { type "type" bibinfo.check } + if$ + " " * paper + "paper" bibinfo.check + * + cap.status.std + } + if$ + } + { "" } + if$ +} + + +FUNCTION {format.pages} +{ pages duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + duplicate$ is.multiple.pages + { + bbl.pages swap$ + n.dashify + } + { + bbl.page swap$ + } + if$ + tie.or.space.prefix + "pages" bibinfo.check + * * + cap.status.std + } + if$ +} + + + +%% technical report number + +FUNCTION {format.tech.report.number} +{ number "number" bibinfo.check + this.to.prev.status + this.status.std + cap.status.std + type duplicate$ empty$ + { pop$ + bbl.techrep + } + { skip$ } + if$ + "type" bibinfo.check + swap$ duplicate$ empty$ + { pop$ } + { tie.or.space.prefix * * } + if$ +} + + + +%% note + +FUNCTION {format.note} +{ note empty$ + { "" } + { this.to.prev.status + this.status.std + punct.period 'this.status.punct := + note #1 #1 substring$ + duplicate$ "{" = + { skip$ } + { status.cap + { "u" } + { "l" } + if$ + change.case$ + } + if$ + note #2 global.max$ substring$ * "note" bibinfo.check + cap.yes 'status.cap := + } + if$ +} + + + +%% patent + +FUNCTION {format.patent.date} +{ this.to.prev.status + this.status.std + year empty$ + { monthfiled duplicate$ empty$ + { "monthfiled" bibinfo.check pop$ "" } + { "monthfiled" bibinfo.check } + if$ + dayfiled duplicate$ empty$ + { "dayfiled" bibinfo.check pop$ "" * } + { "dayfiled" bibinfo.check + monthfiled empty$ + { "dayfiled without a monthfiled in " cite$ * warning$ + * + } + { " " swap$ * * } + if$ + } + if$ + yearfiled empty$ + { "no year or yearfiled in " cite$ * warning$ } + { yearfiled "yearfiled" bibinfo.check + swap$ + duplicate$ empty$ + { pop$ } + { ", " * swap$ * } + if$ + } + if$ + } + { month duplicate$ empty$ + { "month" bibinfo.check pop$ "" } + { "month" bibinfo.check } + if$ + day duplicate$ empty$ + { "day" bibinfo.check pop$ "" * } + { "day" bibinfo.check + month empty$ + { "day without a month in " cite$ * warning$ + * + } + { " " swap$ * * } + if$ + } + if$ + year "year" bibinfo.check + swap$ + duplicate$ empty$ + { pop$ } + { ", " * swap$ * } + if$ + } + if$ + cap.status.std +} + +FUNCTION {format.patent.nationality.type.number} +{ this.to.prev.status + this.status.std + nationality duplicate$ empty$ + { "nationality" bibinfo.warn pop$ "" } + { "nationality" bibinfo.check + duplicate$ "l" change.case$ "united states" = + { pop$ bbl.patentUS } + { skip$ } + if$ + " " * + } + if$ + type empty$ + { bbl.patent "type" bibinfo.check } + { type "type" bibinfo.check } + if$ + * + number duplicate$ empty$ + { "number" bibinfo.warn pop$ } + { "number" bibinfo.check + large.number.separate + swap$ " " * swap$ * + } + if$ + cap.status.std +} + + + +%% standard + +FUNCTION {format.organization.institution.standard.type.number} +{ this.to.prev.status + this.status.std + organization duplicate$ empty$ + { pop$ + institution duplicate$ empty$ + { "institution" bibinfo.warn } + { "institution" bibinfo.warn " " * } + if$ + } + { "organization" bibinfo.warn " " * } + if$ + type empty$ + { bbl.standard "type" bibinfo.check } + { type "type" bibinfo.check } + if$ + * + number duplicate$ empty$ + { "number" bibinfo.check pop$ } + { "number" bibinfo.check + large.number.separate + swap$ " " * swap$ * + } + if$ + cap.status.std +} + +FUNCTION {format.revision} +{ revision empty$ + { "" } + { this.to.prev.status + this.status.std + bbl.revision + revision tie.or.space.prefix + "revision" bibinfo.check + * * + cap.status.std + } + if$ +} + + +%% thesis + +FUNCTION {format.master.thesis.type} +{ this.to.prev.status + this.status.std + type empty$ + { + bbl.mthesis + } + { + type "type" bibinfo.check + } + if$ +cap.status.std +} + +FUNCTION {format.phd.thesis.type} +{ this.to.prev.status + this.status.std + type empty$ + { + bbl.phdthesis + } + { + type "type" bibinfo.check + } + if$ +cap.status.std +} + + + +%% URL + +FUNCTION {format.url} +{ url empty$ + { "" } + { this.to.prev.status + this.status.std + cap.yes 'status.cap := + name.url.prefix " " * + "\url{" * url * "}" * + punct.no 'this.status.punct := + punct.period 'prev.status.punct := + space.normal 'this.status.space := + space.normal 'prev.status.space := + quote.no 'this.status.quote := + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%% +%% ENTRY HANDLERS %% +%%%%%%%%%%%%%%%%%%%% + + +% Note: In many journals, IEEE (or the authors) tend not to show the number +% for articles, so the display of the number is controlled here by the +% switch "is.use.number.for.article" +FUNCTION {article} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.journal "journal" bibinfo.check "journal" output.warn + format.volume output + format.number.if.use.for.article output + format.pages output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {book} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + author empty$ + { format.editors "author and editor" output.warn } + { format.authors output.nonnull } + if$ + name.or.dash + format.book.title.edition output + format.series output + author empty$ + { skip$ } + { format.editors output } + if$ + format.address.publisher.date output + format.volume output + format.number output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {booklet} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {electronic} +{ std.status.using.period + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.date.electronic output + format.article.title.electronic output + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {inbook} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + author empty$ + { format.editors "author and editor" output.warn } + { format.authors output.nonnull } + if$ + name.or.dash + format.book.title.edition output + format.series output + format.address.publisher.date output + format.volume output + format.number output + format.chapter output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {incollection} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.in.booktitle.edition "booktitle" output.warn + format.series output + format.editors output + format.address.publisher.date.nowarn output + format.volume output + format.number output + format.chapter output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {inproceedings} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.in.booktitle "booktitle" output.warn + format.series output + format.editors output + format.volume output + format.number output + publisher empty$ + { format.address.organization.date output } + { format.organization "organization" bibinfo.check output + format.address.publisher.date output + } + if$ + format.paper output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {manual} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.book.title.edition "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {mastersthesis} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.master.thesis.type output.nonnull + format.school "school" bibinfo.warn output + format.address "address" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {misc} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title output + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.pages output + format.date output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {patent} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title output + format.patent.nationality.type.number output + format.patent.date output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {periodical} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.editors output + name.or.dash + format.book.title "title" output.warn + format.series output + format.volume output + format.number output + format.organization "organization" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {phdthesis} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.phd.thesis.type output.nonnull + format.school "school" bibinfo.warn output + format.address "address" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {proceedings} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.editors output + name.or.dash + format.book.title "title" output.warn + format.series output + format.volume output + format.number output + publisher empty$ + { format.address.organization.date output } + { format.organization "organization" bibinfo.check output + format.address.publisher.date output + } + if$ + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {standard} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.book.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization.institution.standard.type.number output + format.revision output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {techreport} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.institution "institution" bibinfo.warn output + format.address "address" bibinfo.check output + format.tech.report.number output.nonnull + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {unpublished} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.date output + format.note "note" output.warn + format.url output + fin.entry + if.url.std.interword.spacing +} + + +% The special entry type which provides the user interface to the +% BST controls +FUNCTION {IEEEtranBSTCTL} +{ is.print.banners.to.terminal + { "** IEEEtran BST control entry " quote$ * cite$ * quote$ * " detected." * + top$ + } + { skip$ } + if$ + CTLuse_article_number + empty$ + { skip$ } + { CTLuse_article_number + yes.no.to.int + 'is.use.number.for.article := + } + if$ + CTLuse_paper + empty$ + { skip$ } + { CTLuse_paper + yes.no.to.int + 'is.use.paper := + } + if$ + CTLuse_forced_etal + empty$ + { skip$ } + { CTLuse_forced_etal + yes.no.to.int + 'is.forced.et.al := + } + if$ + CTLmax_names_forced_etal + empty$ + { skip$ } + { CTLmax_names_forced_etal + string.to.integer + 'max.num.names.before.forced.et.al := + } + if$ + CTLnames_show_etal + empty$ + { skip$ } + { CTLnames_show_etal + string.to.integer + 'num.names.shown.with.forced.et.al := + } + if$ + CTLuse_alt_spacing + empty$ + { skip$ } + { CTLuse_alt_spacing + yes.no.to.int + 'is.use.alt.interword.spacing := + } + if$ + CTLalt_stretch_factor + empty$ + { skip$ } + { CTLalt_stretch_factor + 'ALTinterwordstretchfactor := + "\renewcommand{\BIBentryALTinterwordstretchfactor}{" + ALTinterwordstretchfactor * "}" * + write$ newline$ + } + if$ + CTLdash_repeated_names + empty$ + { skip$ } + { CTLdash_repeated_names + yes.no.to.int + 'is.dash.repeated.names := + } + if$ + CTLname_format_string + empty$ + { skip$ } + { CTLname_format_string + 'name.format.string := + } + if$ + CTLname_latex_cmd + empty$ + { skip$ } + { CTLname_latex_cmd + 'name.latex.cmd := + } + if$ + CTLname_url_prefix + missing$ + { skip$ } + { CTLname_url_prefix + 'name.url.prefix := + } + if$ + + + num.names.shown.with.forced.et.al max.num.names.before.forced.et.al > + { "CTLnames_show_etal cannot be greater than CTLmax_names_forced_etal in " cite$ * warning$ + max.num.names.before.forced.et.al 'num.names.shown.with.forced.et.al := + } + { skip$ } + if$ +} + + +%%%%%%%%%%%%%%%%%%% +%% ENTRY ALIASES %% +%%%%%%%%%%%%%%%%%%% +FUNCTION {conference}{inproceedings} +FUNCTION {online}{electronic} +FUNCTION {internet}{electronic} +FUNCTION {webpage}{electronic} +FUNCTION {www}{electronic} +FUNCTION {default.type}{misc} + + + +%%%%%%%%%%%%%%%%%% +%% MAIN PROGRAM %% +%%%%%%%%%%%%%%%%%% + +READ + +EXECUTE {initialize.controls} +EXECUTE {initialize.status.constants} +EXECUTE {banner.message} + +EXECUTE {initialize.longest.label} +ITERATE {longest.label.pass} + +EXECUTE {begin.bib} +ITERATE {call.type$} +EXECUTE {end.bib} + +EXECUTE{completed.message} + + +%% That's all folks, mds. Added: text/escience11submission/IEEEtran.cls =================================================================== --- text/escience11submission/IEEEtran.cls (rev 0) +++ text/escience11submission/IEEEtran.cls 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,4702 @@ +%% +%% IEEEtran.cls 2007/03/05 version V1.7a +%% +%% +%% This is the official IEEE LaTeX class for authors of the Institute of +%% Electrical and Electronics Engineers (IEEE) Transactions journals and +%% conferences. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ +%% +%% Based on the original 1993 IEEEtran.cls, but with many bug fixes +%% and enhancements (from both JVH and MDS) over the 1996/7 version. +%% +%% +%% Contributors: +%% Gerry Murray (1993), Silvano Balemi (1993), +%% Jon Dixon (1996), Peter N"uchter (1996), +%% Juergen von Hagen (2000), and Michael Shell (2001-2007) +%% +%% +%% Copyright (c) 1993-2000 by Gerry Murray, Silvano Balemi, +%% Jon Dixon, Peter N"uchter, +%% Juergen von Hagen +%% and +%% Copyright (c) 2001-2007 by Michael Shell +%% +%% Current maintainer (V1.3 to V1.7): Michael Shell +%% See: +%% http://www.michaelshell.org/ +%% for current contact information. +%% +%% Special thanks to Peter Wilson (CUA) and Donald Arseneau +%% for allowing the inclusion of the \@ifmtarg command +%% from their ifmtarg LaTeX package. +%% +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%% +%% Major changes to the user interface should be indicated by an +%% increase in the version numbers. If a version is a beta, it will +%% be indicated with a BETA suffix, i.e., 1.4 BETA. +%% Small changes can be indicated by appending letters to the version +%% such as "IEEEtran_v14a.cls". +%% In all cases, \Providesclass, any \typeout messages to the user, +%% \IEEEtransversionmajor and \IEEEtransversionminor must reflect the +%% correct version information. +%% The changes should also be documented via source comments. +%%************************************************************************* +%% +% +% Available class options +% e.g., \documentclass[10pt,conference]{IEEEtran} +% +% *** choose only one from each category *** +% +% 9pt, 10pt, 11pt, 12pt +% Sets normal font size. The default is 10pt. +% +% conference, journal, technote, peerreview, peerreviewca +% determines format mode - conference papers, journal papers, +% correspondence papers (technotes), or peer review papers. The user +% should also select 9pt when using technote. peerreview is like +% journal mode, but provides for a single-column "cover" title page for +% anonymous peer review. The paper title (without the author names) is +% repeated at the top of the page after the cover page. For peer review +% papers, the \IEEEpeerreviewmaketitle command must be executed (will +% automatically be ignored for non-peerreview modes) at the place the +% cover page is to end, usually just after the abstract (keywords are +% not normally used with peer review papers). peerreviewca is like +% peerreview, but allows the author names to be entered and formatted +% as with conference mode so that author affiliation and contact +% information can be easily seen on the cover page. +% The default is journal. +% +% draft, draftcls, draftclsnofoot, final +% determines if paper is formatted as a widely spaced draft (for +% handwritten editor comments) or as a properly typeset final version. +% draftcls restricts draft mode to the class file while all other LaTeX +% packages (i.e., \usepackage{graphicx}) will behave as final - allows +% for a draft paper with visible figures, etc. draftclsnofoot is like +% draftcls, but does not display the date and the word "DRAFT" at the foot +% of the pages. If using one of the draft modes, the user will probably +% also want to select onecolumn. +% The default is final. +% +% letterpaper, a4paper +% determines paper size: 8.5in X 11in or 210mm X 297mm. CHANGING THE PAPER +% SIZE WILL NOT ALTER THE TYPESETTING OF THE DOCUMENT - ONLY THE MARGINS +% WILL BE AFFECTED. In particular, documents using the a4paper option will +% have reduced side margins (A4 is narrower than US letter) and a longer +% bottom margin (A4 is longer than US letter). For both cases, the top +% margins will be the same and the text will be horizontally centered. +% For final submission to IEEE, authors should use US letter (8.5 X 11in) +% paper. Note that authors should ensure that all post-processing +% (ps, pdf, etc.) uses the same paper specificiation as the .tex document. +% Problems here are by far the number one reason for incorrect margins. +% IEEEtran will automatically set the default paper size under pdflatex +% (without requiring a change to pdftex.cfg), so this issue is more +% important to dvips users. Fix config.ps, config.pdf, or ~/.dvipsrc for +% dvips, or use the dvips -t papersize option instead as needed. See the +% testflow documentation +% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/testflow +% for more details on dvips paper size configuration. +% The default is letterpaper. +% +% oneside, twoside +% determines if layout follows single sided or two sided (duplex) +% printing. The only notable change is with the headings at the top of +% the pages. +% The default is oneside. +% +% onecolumn, twocolumn +% determines if text is organized into one or two columns per page. One +% column mode is usually used only with draft papers. +% The default is twocolumn. +% +% compsoc +% Use the format of the IEEE Computer Society. +% +% romanappendices +% Use the "Appendix I" convention when numbering appendices. IEEEtran.cls +% now defaults to Alpha "Appendix A" convention - the opposite of what +% v1.6b and earlier did. +% +% captionsoff +% disables the display of the figure/table captions. Some IEEE journals +% request that captions be removed and figures/tables be put on pages +% of their own at the end of an initial paper submission. The endfloat +% package can be used with this class option to achieve this format. +% +% nofonttune +% turns off tuning of the font interword spacing. Maybe useful to those +% not using the standard Times fonts or for those who have already "tuned" +% their fonts. +% The default is to enable IEEEtran to tune font parameters. +% +% +%---------- +% Available CLASSINPUTs provided (all are macros unless otherwise noted): +% \CLASSINPUTbaselinestretch +% \CLASSINPUTinnersidemargin +% \CLASSINPUToutersidemargin +% \CLASSINPUTtoptextmargin +% \CLASSINPUTbottomtextmargin +% +% Available CLASSINFOs provided: +% \ifCLASSINFOpdf (TeX if conditional) +% \CLASSINFOpaperwidth (macro) +% \CLASSINFOpaperheight (macro) +% \CLASSINFOnormalsizebaselineskip (length) +% \CLASSINFOnormalsizeunitybaselineskip (length) +% +% Available CLASSOPTIONs provided: +% all class option flags (TeX if conditionals) unless otherwise noted, +% e.g., \ifCLASSOPTIONcaptionsoff +% point size options provided as a single macro: +% \CLASSOPTIONpt +% which will be defined as 9, 10, 11, or 12 depending on the document's +% normalsize point size. +% also, class option peerreviewca implies the use of class option peerreview +% and classoption draft implies the use of class option draftcls + + + + + +\ProvidesClass{IEEEtran}[2007/03/05 V1.7a by Michael Shell] +\typeout{-- See the "IEEEtran_HOWTO" manual for usage information.} +\typeout{-- http://www.michaelshell.org/tex/ieeetran/} +\NeedsTeXFormat{LaTeX2e} + +% IEEEtran.cls version numbers, provided as of V1.3 +% These values serve as a way a .tex file can +% determine if the new features are provided. +% The version number of this IEEEtrans.cls can be obtained from +% these values. i.e., V1.4 +% KEEP THESE AS INTEGERS! i.e., NO {4a} or anything like that- +% (no need to enumerate "a" minor changes here) +\def\IEEEtransversionmajor{1} +\def\IEEEtransversionminor{7} + +% These do nothing, but provide them like in article.cls +\newif\if at restonecol +\newif\if at titlepage + + +% class option conditionals +\newif\ifCLASSOPTIONonecolumn \CLASSOPTIONonecolumnfalse +\newif\ifCLASSOPTIONtwocolumn \CLASSOPTIONtwocolumntrue + +\newif\ifCLASSOPTIONoneside \CLASSOPTIONonesidetrue +\newif\ifCLASSOPTIONtwoside \CLASSOPTIONtwosidefalse + +\newif\ifCLASSOPTIONfinal \CLASSOPTIONfinaltrue +\newif\ifCLASSOPTIONdraft \CLASSOPTIONdraftfalse +\newif\ifCLASSOPTIONdraftcls \CLASSOPTIONdraftclsfalse +\newif\ifCLASSOPTIONdraftclsnofoot \CLASSOPTIONdraftclsnofootfalse + +\newif\ifCLASSOPTIONpeerreview \CLASSOPTIONpeerreviewfalse +\newif\ifCLASSOPTIONpeerreviewca \CLASSOPTIONpeerreviewcafalse + +\newif\ifCLASSOPTIONjournal \CLASSOPTIONjournaltrue +\newif\ifCLASSOPTIONconference \CLASSOPTIONconferencefalse +\newif\ifCLASSOPTIONtechnote \CLASSOPTIONtechnotefalse + +\newif\ifCLASSOPTIONnofonttune \CLASSOPTIONnofonttunefalse + +\newif\ifCLASSOPTIONcaptionsoff \CLASSOPTIONcaptionsofffalse + +\newif\ifCLASSOPTIONcompsoc \CLASSOPTIONcompsocfalse + +\newif\ifCLASSOPTIONromanappendices \CLASSOPTIONromanappendicesfalse + + +% class info conditionals + +% indicates if pdf (via pdflatex) output +\newif\ifCLASSINFOpdf \CLASSINFOpdffalse + + +% V1.6b internal flag to show if using a4paper +\newif\if at IEEEusingAfourpaper \@IEEEusingAfourpaperfalse + + + +% IEEEtran class scratch pad registers +% dimen +\newdimen\@IEEEtrantmpdimenA +\newdimen\@IEEEtrantmpdimenB +% count +\newcount\@IEEEtrantmpcountA +\newcount\@IEEEtrantmpcountB +% token list +\newtoks\@IEEEtrantmptoksA + +% we use \CLASSOPTIONpt so that we can ID the point size (even for 9pt docs) +% as well as LaTeX's \@ptsize to retain some compatability with some +% external packages +\def\@ptsize{0} +% LaTeX does not support 9pt, so we set \@ptsize to 0 - same as that of 10pt +\DeclareOption{9pt}{\def\CLASSOPTIONpt{9}\def\@ptsize{0}} +\DeclareOption{10pt}{\def\CLASSOPTIONpt{10}\def\@ptsize{0}} +\DeclareOption{11pt}{\def\CLASSOPTIONpt{11}\def\@ptsize{1}} +\DeclareOption{12pt}{\def\CLASSOPTIONpt{12}\def\@ptsize{2}} + + + +\DeclareOption{letterpaper}{\setlength{\paperheight}{11in}% + \setlength{\paperwidth}{8.5in}% + \@IEEEusingAfourpaperfalse + \def\CLASSOPTIONpaper{letter}% + \def\CLASSINFOpaperwidth{8.5in}% + \def\CLASSINFOpaperheight{11in}} + + +\DeclareOption{a4paper}{\setlength{\paperheight}{297mm}% + \setlength{\paperwidth}{210mm}% + \@IEEEusingAfourpapertrue + \def\CLASSOPTIONpaper{a4}% + \def\CLASSINFOpaperwidth{210mm}% + \def\CLASSINFOpaperheight{297mm}} + +\DeclareOption{oneside}{\@twosidefalse\@mparswitchfalse + \CLASSOPTIONonesidetrue\CLASSOPTIONtwosidefalse} +\DeclareOption{twoside}{\@twosidetrue\@mparswitchtrue + \CLASSOPTIONtwosidetrue\CLASSOPTIONonesidefalse} + +\DeclareOption{onecolumn}{\CLASSOPTIONonecolumntrue\CLASSOPTIONtwocolumnfalse} +\DeclareOption{twocolumn}{\CLASSOPTIONtwocolumntrue\CLASSOPTIONonecolumnfalse} + +% If the user selects draft, then this class AND any packages +% will go into draft mode. +\DeclareOption{draft}{\CLASSOPTIONdrafttrue\CLASSOPTIONdraftclstrue + \CLASSOPTIONdraftclsnofootfalse} +% draftcls is for a draft mode which will not affect any packages +% used by the document. +\DeclareOption{draftcls}{\CLASSOPTIONdraftfalse\CLASSOPTIONdraftclstrue + \CLASSOPTIONdraftclsnofootfalse} +% draftclsnofoot is like draftcls, but without the footer. +\DeclareOption{draftclsnofoot}{\CLASSOPTIONdraftfalse\CLASSOPTIONdraftclstrue + \CLASSOPTIONdraftclsnofoottrue} +\DeclareOption{final}{\CLASSOPTIONdraftfalse\CLASSOPTIONdraftclsfalse + \CLASSOPTIONdraftclsnofootfalse} + +\DeclareOption{journal}{\CLASSOPTIONpeerreviewfalse\CLASSOPTIONpeerreviewcafalse + \CLASSOPTIONjournaltrue\CLASSOPTIONconferencefalse\CLASSOPTIONtechnotefalse} + +\DeclareOption{conference}{\CLASSOPTIONpeerreviewfalse\CLASSOPTIONpeerreviewcafalse + \CLASSOPTIONjournalfalse\CLASSOPTIONconferencetrue\CLASSOPTIONtechnotefalse} + +\DeclareOption{technote}{\CLASSOPTIONpeerreviewfalse\CLASSOPTIONpeerreviewcafalse + \CLASSOPTIONjournalfalse\CLASSOPTIONconferencefalse\CLASSOPTIONtechnotetrue} + +\DeclareOption{peerreview}{\CLASSOPTIONpeerreviewtrue\CLASSOPTIONpeerreviewcafalse + \CLASSOPTIONjournalfalse\CLASSOPTIONconferencefalse\CLASSOPTIONtechnotefalse} + +\DeclareOption{peerreviewca}{\CLASSOPTIONpeerreviewtrue\CLASSOPTIONpeerreviewcatrue + \CLASSOPTIONjournalfalse\CLASSOPTIONconferencefalse\CLASSOPTIONtechnotefalse} + +\DeclareOption{nofonttune}{\CLASSOPTIONnofonttunetrue} + +\DeclareOption{captionsoff}{\CLASSOPTIONcaptionsofftrue} + +\DeclareOption{compsoc}{\CLASSOPTIONcompsoctrue} + +\DeclareOption{romanappendices}{\CLASSOPTIONromanappendicestrue} + + +% default to US letter paper, 10pt, twocolumn, one sided, final, journal +\ExecuteOptions{letterpaper,10pt,twocolumn,oneside,final,journal} +% overrride these defaults per user requests +\ProcessOptions + + + +% Computer Society conditional execution command +\long\def\@IEEEcompsoconly#1{\relax\ifCLASSOPTIONcompsoc\relax#1\relax\fi\relax} +% inverse +\long\def\@IEEEnotcompsoconly#1{\relax\ifCLASSOPTIONcompsoc\else\relax#1\relax\fi\relax} +% compsoc conference +\long\def\@IEEEcompsocconfonly#1{\relax\ifCLASSOPTIONcompsoc\ifCLASSOPTIONconference\relax#1\relax\fi\fi\relax} +% compsoc not conference +\long\def\@IEEEcompsocnotconfonly#1{\relax\ifCLASSOPTIONcompsoc\ifCLASSOPTIONconference\else\relax#1\relax\fi\fi\relax} + + +% IEEE uses Times Roman font, so we'll default to Times. +% These three commands make up the entire times.sty package. +\renewcommand{\sfdefault}{phv} +\renewcommand{\rmdefault}{ptm} +\renewcommand{\ttdefault}{pcr} + +\@IEEEcompsoconly{\typeout{-- Using IEEE Computer Society mode.}} + +% V1.7 compsoc nonconference papers, use Palatino/Palladio as the main text font, +% not Times Roman. +\@IEEEcompsocnotconfonly{\renewcommand{\rmdefault}{ppl}} + +% enable Times/Palatino main text font +\normalfont\selectfont + + + + + +% V1.7 conference notice message hook +\def\@IEEEconsolenoticeconference{\typeout{}% +\typeout{** Conference Paper **}% +\typeout{Before submitting the final camera ready copy, remember to:}% +\typeout{}% +\typeout{ 1. Manually equalize the lengths of two columns on the last page}% +\typeout{ of your paper;}% +\typeout{}% +\typeout{ 2. Ensure that any PostScript and/or PDF output post-processing}% +\typeout{ uses only Type 1 fonts and that every step in the generation}% +\typeout{ process uses the appropriate paper size.}% +\typeout{}} + + +% we can send console reminder messages to the user here +\AtEndDocument{\ifCLASSOPTIONconference\@IEEEconsolenoticeconference\fi} + + +% warn about the use of single column other than for draft mode +\ifCLASSOPTIONtwocolumn\else% + \ifCLASSOPTIONdraftcls\else% + \typeout{** ATTENTION: Single column mode is not typically used with IEEE publications.}% + \fi% +\fi + + +% V1.7 improved paper size setting code. +% Set pdfpage and dvips paper sizes. Conditional tests are similar to that +% of ifpdf.sty. Retain within {} to ensure tested macros are never altered, +% even if only effect is to set them to \relax. +% if \pdfoutput is undefined or equal to relax, output a dvips special +{\@ifundefined{pdfoutput}{\AtBeginDvi{\special{papersize=\CLASSINFOpaperwidth,\CLASSINFOpaperheight}}}{% +% pdfoutput is defined and not equal to \relax +% check for pdfpageheight existence just in case someone sets pdfoutput +% under non-pdflatex. If exists, set them regardless of value of \pdfoutput. +\@ifundefined{pdfpageheight}{\relax}{\global\pdfpagewidth\paperwidth +\global\pdfpageheight\paperheight}% +% if using \pdfoutput=0 under pdflatex, send dvips papersize special +\ifcase\pdfoutput +\AtBeginDvi{\special{papersize=\CLASSINFOpaperwidth,\CLASSINFOpaperheight}}% +\else +% we are using pdf output, set CLASSINFOpdf flag +\global\CLASSINFOpdftrue +\fi}} + +% let the user know the selected papersize +\typeout{-- Using \CLASSINFOpaperwidth\space x \CLASSINFOpaperheight\space +(\CLASSOPTIONpaper)\space paper.} + +\ifCLASSINFOpdf +\typeout{-- Using PDF output.} +\else +\typeout{-- Using DVI output.} +\fi + + +% The idea hinted here is for LaTeX to generate markleft{} and markright{} +% automatically for you after you enter \author{}, \journal{}, +% \journaldate{}, journalvol{}, \journalnum{}, etc. +% However, there may be some backward compatibility issues here as +% well as some special applications for IEEEtran.cls and special issues +% that may require the flexible \markleft{}, \markright{} and/or \markboth{}. +% We'll leave this as an open future suggestion. +%\newcommand{\journal}[1]{\def\@journal{#1}} +%\def\@journal{} + + + +% pointsize values +% used with ifx to determine the document's normal size +\def\@IEEEptsizenine{9} +\def\@IEEEptsizeten{10} +\def\@IEEEptsizeeleven{11} +\def\@IEEEptsizetwelve{12} + + + +% FONT DEFINITIONS (No sizexx.clo file needed) +% V1.6 revised font sizes, displayskip values and +% revised normalsize baselineskip to reduce underfull vbox problems +% on the 58pc = 696pt = 9.5in text height we want +% normalsize #lines/column baselineskip (aka leading) +% 9pt 63 11.0476pt (truncated down) +% 10pt 58 12pt (exact) +% 11pt 52 13.3846pt (truncated down) +% 12pt 50 13.92pt (exact) +% + +% we need to store the nominal baselineskip for the given font size +% in case baselinestretch ever changes. +% this is a dimen, so it will not hold stretch or shrink +\newdimen\@IEEEnormalsizeunitybaselineskip +\@IEEEnormalsizeunitybaselineskip\baselineskip + +\ifx\CLASSOPTIONpt\@IEEEptsizenine +\typeout{-- This is a 9 point document.} +\def\normalsize{\@setfontsize{\normalsize}{9}{11.0476pt}}% +\setlength{\@IEEEnormalsizeunitybaselineskip}{11.0476pt}% +\normalsize +\abovedisplayskip 1.5ex plus3pt minus1pt% +\belowdisplayskip \abovedisplayskip% +\abovedisplayshortskip 0pt plus3pt% +\belowdisplayshortskip 1.5ex plus3pt minus1pt +\def\small{\@setfontsize{\small}{8.5}{10pt}} +\def\footnotesize{\@setfontsize{\footnotesize}{8}{9pt}} +\def\scriptsize{\@setfontsize{\scriptsize}{7}{8pt}} +\def\tiny{\@setfontsize{\tiny}{5}{6pt}} +% sublargesize is the same as large - 10pt +\def\sublargesize{\@setfontsize{\sublargesize}{10}{12pt}} +\def\large{\@setfontsize{\large}{10}{12pt}} +\def\Large{\@setfontsize{\Large}{12}{14pt}} +\def\LARGE{\@setfontsize{\LARGE}{14}{17pt}} +\def\huge{\@setfontsize{\huge}{17}{20pt}} +\def\Huge{\@setfontsize{\Huge}{20}{24pt}} +\fi + + +% Check if we have selected 10 points +\ifx\CLASSOPTIONpt\@IEEEptsizeten +\typeout{-- This is a 10 point document.} +\def\normalsize{\@setfontsize{\normalsize}{10}{12.00pt}}% +\setlength{\@IEEEnormalsizeunitybaselineskip}{12pt}% +\normalsize +\abovedisplayskip 1.5ex plus4pt minus2pt% +\belowdisplayskip \abovedisplayskip% +\abovedisplayshortskip 0pt plus4pt% +\belowdisplayshortskip 1.5ex plus4pt minus2pt +\def\small{\@setfontsize{\small}{9}{10pt}} +\def\footnotesize{\@setfontsize{\footnotesize}{8}{9pt}} +\def\scriptsize{\@setfontsize{\scriptsize}{7}{8pt}} +\def\tiny{\@setfontsize{\tiny}{5}{6pt}} +% sublargesize is a tad smaller than large - 11pt +\def\sublargesize{\@setfontsize{\sublargesize}{11}{13.4pt}} +\def\large{\@setfontsize{\large}{12}{14pt}} +\def\Large{\@setfontsize{\Large}{14}{17pt}} +\def\LARGE{\@setfontsize{\LARGE}{17}{20pt}} +\def\huge{\@setfontsize{\huge}{20}{24pt}} +\def\Huge{\@setfontsize{\Huge}{24}{28pt}} +\fi + + +% Check if we have selected 11 points +\ifx\CLASSOPTIONpt\@IEEEptsizeeleven +\typeout{-- This is an 11 point document.} +\def\normalsize{\@setfontsize{\normalsize}{11}{13.3846pt}}% +\setlength{\@IEEEnormalsizeunitybaselineskip}{13.3846pt}% +\normalsize +\abovedisplayskip 1.5ex plus5pt minus3pt% +\belowdisplayskip \abovedisplayskip% +\abovedisplayshortskip 0pt plus5pt% +\belowdisplayshortskip 1.5ex plus5pt minus3pt +\def\small{\@setfontsize{\small}{10}{12pt}} +\def\footnotesize{\@setfontsize{\footnotesize}{9}{10.5pt}} +\def\scriptsize{\@setfontsize{\scriptsize}{8}{9pt}} +\def\tiny{\@setfontsize{\tiny}{6}{7pt}} +% sublargesize is the same as large - 12pt +\def\sublargesize{\@setfontsize{\sublargesize}{12}{14pt}} +\def\large{\@setfontsize{\large}{12}{14pt}} +\def\Large{\@setfontsize{\Large}{14}{17pt}} +\def\LARGE{\@setfontsize{\LARGE}{17}{20pt}} +\def\huge{\@setfontsize{\huge}{20}{24pt}} +\def\Huge{\@setfontsize{\Huge}{24}{28pt}} +\fi + + +% Check if we have selected 12 points +\ifx\CLASSOPTIONpt\@IEEEptsizetwelve +\typeout{-- This is a 12 point document.} +\def\normalsize{\@setfontsize{\normalsize}{12}{13.92pt}}% +\setlength{\@IEEEnormalsizeunitybaselineskip}{13.92pt}% +\normalsize +\abovedisplayskip 1.5ex plus6pt minus4pt% +\belowdisplayskip \abovedisplayskip% +\abovedisplayshortskip 0pt plus6pt% +\belowdisplayshortskip 1.5ex plus6pt minus4pt +\def\small{\@setfontsize{\small}{10}{12pt}} +\def\footnotesize{\@setfontsize{\footnotesize}{9}{10.5pt}} +\def\scriptsize{\@setfontsize{\scriptsize}{8}{9pt}} +\def\tiny{\@setfontsize{\tiny}{6}{7pt}} +% sublargesize is the same as large - 14pt +\def\sublargesize{\@setfontsize{\sublargesize}{14}{17pt}} +\def\large{\@setfontsize{\large}{14}{17pt}} +\def\Large{\@setfontsize{\Large}{17}{20pt}} +\def\LARGE{\@setfontsize{\LARGE}{20}{24pt}} +\def\huge{\@setfontsize{\huge}{22}{26pt}} +\def\Huge{\@setfontsize{\Huge}{24}{28pt}} +\fi + + +% V1.6 The Computer Modern Fonts will issue a substitution warning for +% 24pt titles (24.88pt is used instead) increase the substitution +% tolerance to turn off this warning +\def\fontsubfuzz{.9pt} +% However, the default (and correct) Times font will scale exactly as needed. + + +% warn the user in case they forget to use the 9pt option with +% technote +\ifCLASSOPTIONtechnote% + \ifx\CLASSOPTIONpt\@IEEEptsizenine\else% + \typeout{** ATTENTION: Technotes are normally 9pt documents.}% + \fi% +\fi + + +% V1.7 +% Improved \textunderscore to provide a much better fake _ when used with +% OT1 encoding. Under OT1, detect use of pcr or cmtt \ttfamily and use +% available true _ glyph for those two typewriter fonts. +\def\@IEEEstringptm{ptm} % Times Roman family +\def\@IEEEstringppl{ppl} % Palatino Roman family +\def\@IEEEstringphv{phv} % Helvetica Sans Serif family +\def\@IEEEstringpcr{pcr} % Courier typewriter family +\def\@IEEEstringcmtt{cmtt} % Computer Modern typewriter family +\DeclareTextCommandDefault{\textunderscore}{\leavevmode +\ifx\f at family\@IEEEstringpcr\string_\else +\ifx\f at family\@IEEEstringcmtt\string_\else +\ifx\f at family\@IEEEstringptm\kern 0em\vbox{\hrule\@width 0.5em\@height 0.5pt\kern -0.3ex}\else +\ifx\f at family\@IEEEstringppl\kern 0em\vbox{\hrule\@width 0.5em\@height 0.5pt\kern -0.3ex}\else +\ifx\f at family\@IEEEstringphv\kern -0.03em\vbox{\hrule\@width 0.62em\@height 0.52pt\kern -0.33ex}\kern -0.03em\else +\kern 0.09em\vbox{\hrule\@width 0.6em\@height 0.44pt\kern -0.63pt\kern -0.42ex}\kern 0.09em\fi\fi\fi\fi\fi\relax} + + + + +% set the default \baselinestretch +\def\baselinestretch{1} +\ifCLASSOPTIONdraftcls + \def\baselinestretch{1.5}% default baselinestretch for draft modes +\fi + + +% process CLASSINPUT baselinestretch +\ifx\CLASSINPUTbaselinestretch\@IEEEundefined +\else + \edef\baselinestretch{\CLASSINPUTbaselinestretch} % user CLASSINPUT override + \typeout{** ATTENTION: Overriding \string\baselinestretch\space to + \baselinestretch\space via \string\CLASSINPUT.} +\fi + +\normalsize % make \baselinestretch take affect + + + + +% store the normalsize baselineskip +\newdimen\CLASSINFOnormalsizebaselineskip +\CLASSINFOnormalsizebaselineskip=\baselineskip\relax +% and the normalsize unity (baselinestretch=1) baselineskip +% we could save a register by giving the user access to +% \@IEEEnormalsizeunitybaselineskip. However, let's protect +% its read only internal status +\newdimen\CLASSINFOnormalsizeunitybaselineskip +\CLASSINFOnormalsizeunitybaselineskip=\@IEEEnormalsizeunitybaselineskip\relax +% store the nominal value of jot +\newdimen\IEEEnormaljot +\IEEEnormaljot=0.25\baselineskip\relax + +% set \jot +\jot=\IEEEnormaljot\relax + + + + +% V1.6, we are now going to fine tune the interword spacing +% The default interword glue for Times under TeX appears to use a +% nominal interword spacing of 25% (relative to the font size, i.e., 1em) +% a maximum of 40% and a minimum of 19%. +% For example, 10pt text uses an interword glue of: +% +% 2.5pt plus 1.49998pt minus 0.59998pt +% +% However, IEEE allows for a more generous range which reduces the need +% for hyphenation, especially for two column text. Furthermore, IEEE +% tends to use a little bit more nominal space between the words. +% IEEE's interword spacing percentages appear to be: +% 35% nominal +% 23% minimum +% 50% maximum +% (They may even be using a tad more for the largest fonts such as 24pt.) +% +% for bold text, IEEE increases the spacing a little more: +% 37.5% nominal +% 23% minimum +% 55% maximum + +% here are the interword spacing ratios we'll use +% for medium (normal weight) +\def\@IEEEinterspaceratioM{0.35} +\def\@IEEEinterspaceMINratioM{0.23} +\def\@IEEEinterspaceMAXratioM{0.50} + +% for bold +\def\@IEEEinterspaceratioB{0.375} +\def\@IEEEinterspaceMINratioB{0.23} +\def\@IEEEinterspaceMAXratioB{0.55} + + +% command to revise the interword spacing for the current font under TeX: +% \fontdimen2 = nominal interword space +% \fontdimen3 = interword stretch +% \fontdimen4 = interword shrink +% since all changes to the \fontdimen are global, we can enclose these commands +% in braces to confine any font attribute or length changes +\def\@@@IEEEsetfontdimens#1#2#3{{% +\setlength{\@IEEEtrantmpdimenB}{\f at size pt}% grab the font size in pt, could use 1em instead. +\setlength{\@IEEEtrantmpdimenA}{#1\@IEEEtrantmpdimenB}% +\fontdimen2\font=\@IEEEtrantmpdimenA\relax +\addtolength{\@IEEEtrantmpdimenA}{-#2\@IEEEtrantmpdimenB}% +\fontdimen3\font=-\@IEEEtrantmpdimenA\relax +\setlength{\@IEEEtrantmpdimenA}{#1\@IEEEtrantmpdimenB}% +\addtolength{\@IEEEtrantmpdimenA}{-#3\@IEEEtrantmpdimenB}% +\fontdimen4\font=\@IEEEtrantmpdimenA\relax}} + +% revise the interword spacing for each font weight +\def\@@IEEEsetfontdimens{{% +\mdseries +\@@@IEEEsetfontdimens{\@IEEEinterspaceratioM}{\@IEEEinterspaceMAXratioM}{\@IEEEinterspaceMINratioM}% +\bfseries +\@@@IEEEsetfontdimens{\@IEEEinterspaceratioB}{\@IEEEinterspaceMAXratioB}{\@IEEEinterspaceMINratioB}% +}} + +% revise the interword spacing for each font shape +% \slshape is not often used for IEEE work and is not altered here. The \scshape caps are +% already a tad too large in the free LaTeX fonts (as compared to what IEEE uses) so we +% won't alter these either. +\def\@IEEEsetfontdimens{{% +\normalfont +\@@IEEEsetfontdimens +\normalfont\itshape +\@@IEEEsetfontdimens +}} + +% command to revise the interword spacing for each font size (and shape +% and weight). Only the \rmfamily is done here as \ttfamily uses a +% fixed spacing and \sffamily is not used as the main text of IEEE papers. +\def\@IEEEtunefonts{{\selectfont\rmfamily +\tiny\@IEEEsetfontdimens +\scriptsize\@IEEEsetfontdimens +\footnotesize\@IEEEsetfontdimens +\small\@IEEEsetfontdimens +\normalsize\@IEEEsetfontdimens +\sublargesize\@IEEEsetfontdimens +\large\@IEEEsetfontdimens +\LARGE\@IEEEsetfontdimens +\huge\@IEEEsetfontdimens +\Huge\@IEEEsetfontdimens}} + +% if the nofonttune class option is not given, revise the interword spacing +% now - in case IEEEtran makes any default length measurements, and make +% sure all the default fonts are loaded +\ifCLASSOPTIONnofonttune\else +\@IEEEtunefonts +\fi + +% and again at the start of the document in case the user loaded different fonts +\AtBeginDocument{\ifCLASSOPTIONnofonttune\else\@IEEEtunefonts\fi} + + + +% V1.6 +% LaTeX is a little to quick to use hyphenations +% So, we increase the penalty for their use and raise +% the badness level that triggers an underfull hbox +% warning. The author may still have to tweak things, +% but the appearance will be much better "right out +% of the box" than that under V1.5 and prior. +% TeX default is 50 +\hyphenpenalty=750 +% If we didn't adjust the interword spacing, 2200 might be better. +% The TeX default is 1000 +\hbadness=1350 +% IEEE does not use extra spacing after punctuation +\frenchspacing + +% V1.7 increase this a tad to discourage equation breaks +\binoppenalty=1000 % default 700 +\relpenalty=800 % default 500 + + +% margin note stuff +\marginparsep 10pt +\marginparwidth 20pt +\marginparpush 25pt + + +% if things get too close, go ahead and let them touch +\lineskip 0pt +\normallineskip 0pt +\lineskiplimit 0pt +\normallineskiplimit 0pt + +% The distance from the lower edge of the text body to the +% footline +\footskip 0.4in + +% normally zero, should be relative to font height. +% put in a little rubber to help stop some bad breaks (underfull vboxes) +\parskip 0ex plus 0.2ex minus 0.1ex + +\parindent 1.0em + +\topmargin -49.0pt +\headheight 12pt +\headsep 0.25in + +% use the normal font baselineskip +% so that \topskip is unaffected by changes in \baselinestretch +\topskip=\@IEEEnormalsizeunitybaselineskip +\textheight 58pc % 9.63in, 696pt +% Tweak textheight to a perfect integer number of lines/page. +% The normal baselineskip for each document point size is used +% to determine these values. +\ifx\CLASSOPTIONpt\@IEEEptsizenine\textheight=63\@IEEEnormalsizeunitybaselineskip\fi % 63 lines/page +\ifx\CLASSOPTIONpt\@IEEEptsizeten\textheight=58\@IEEEnormalsizeunitybaselineskip\fi % 58 lines/page +\ifx\CLASSOPTIONpt\@IEEEptsizeeleven\textheight=52\@IEEEnormalsizeunitybaselineskip\fi % 52 lines/page +\ifx\CLASSOPTIONpt\@IEEEptsizetwelve\textheight=50\@IEEEnormalsizeunitybaselineskip\fi % 50 lines/page + + +\columnsep 1pc +\textwidth 43pc % 2 x 21pc + 1pc = 43pc + + +% the default side margins are equal +\if at IEEEusingAfourpaper +\oddsidemargin 14.32mm +\evensidemargin 14.32mm +\else +\oddsidemargin 0.680in +\evensidemargin 0.680in +\fi +% compensate for LaTeX's 1in offset +\addtolength{\oddsidemargin}{-1in} +\addtolength{\evensidemargin}{-1in} + + + +% adjust margins for conference mode +\ifCLASSOPTIONconference + \topmargin -0.25in + % we retain the reserved, but unused space for headers + \addtolength{\topmargin}{-\headheight} + \addtolength{\topmargin}{-\headsep} + \textheight 9.25in % The standard for conferences (668.4975pt) + % Tweak textheight to a perfect integer number of lines/page. + \ifx\CLASSOPTIONpt\@IEEEptsizenine\textheight=61\@IEEEnormalsizeunitybaselineskip\fi % 61 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizeten\textheight=56\@IEEEnormalsizeunitybaselineskip\fi % 56 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizeeleven\textheight=50\@IEEEnormalsizeunitybaselineskip\fi % 50 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizetwelve\textheight=48\@IEEEnormalsizeunitybaselineskip\fi % 48 lines/page +\fi + + +% compsoc conference +\ifCLASSOPTIONcompsoc +\ifCLASSOPTIONconference + % compsoc conference use a larger value for columnsep + \columnsep 0.375in + % compsoc conferences want 1in top margin, 1.125in bottom margin + \topmargin 0in + \addtolength{\topmargin}{-6pt}% we tweak this a tad to better comply with top of line stuff + % we retain the reserved, but unused space for headers + \addtolength{\topmargin}{-\headheight} + \addtolength{\topmargin}{-\headsep} + \textheight 8.875in % (641.39625pt) + % Tweak textheight to a perfect integer number of lines/page. + \ifx\CLASSOPTIONpt\@IEEEptsizenine\textheight=58\@IEEEnormalsizeunitybaselineskip\fi % 58 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizeten\textheight=53\@IEEEnormalsizeunitybaselineskip\fi % 53 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizeeleven\textheight=48\@IEEEnormalsizeunitybaselineskip\fi % 48 lines/page + \ifx\CLASSOPTIONpt\@IEEEptsizetwelve\textheight=46\@IEEEnormalsizeunitybaselineskip\fi % 46 lines/page + \textwidth 6.5in + % the default side margins are equal + \if at IEEEusingAfourpaper + \oddsidemargin 22.45mm + \evensidemargin 22.45mm + \else + \oddsidemargin 1in + \evensidemargin 1in + \fi + % compensate for LaTeX's 1in offset + \addtolength{\oddsidemargin}{-1in} + \addtolength{\evensidemargin}{-1in} +\fi\fi + + + +% draft mode settings override that of all other modes +% provides a nice 1in margin all around the paper and extra +% space between the lines for editor's comments +\ifCLASSOPTIONdraftcls + % want 1in from top of paper to text + \setlength{\topmargin}{-\headsep}% + \addtolength{\topmargin}{-\headheight}% + % we want 1in side margins regardless of paper type + \oddsidemargin 0in + \evensidemargin 0in + % set the text width + \setlength{\textwidth}{\paperwidth}% + \addtolength{\textwidth}{-2.0in}% + \setlength{\textheight}{\paperheight}% + \addtolength{\textheight}{-2.0in}% + % digitize textheight to be an integer number of lines. + % this may cause the bottom margin to be off a tad + \addtolength{\textheight}{-1\topskip}% + \divide\textheight by \baselineskip% + \multiply\textheight by \baselineskip% + \addtolength{\textheight}{\topskip}% +\fi + + + +% process CLASSINPUT inner/outer margin +% if inner margin defined, but outer margin not, set outer to inner. +\ifx\CLASSINPUTinnersidemargin\@IEEEundefined +\else + \ifx\CLASSINPUToutersidemargin\@IEEEundefined + \edef\CLASSINPUToutersidemargin{\CLASSINPUTinnersidemargin} + \fi +\fi + +\ifx\CLASSINPUToutersidemargin\@IEEEundefined +\else + % if outer margin defined, but inner margin not, set inner to outer. + \ifx\CLASSINPUTinnersidemargin\@IEEEundefined + \edef\CLASSINPUTinnersidemargin{\CLASSINPUToutersidemargin} + \fi + \setlength{\oddsidemargin}{\CLASSINPUTinnersidemargin} + \ifCLASSOPTIONtwoside + \setlength{\evensidemargin}{\CLASSINPUToutersidemargin} + \else + \setlength{\evensidemargin}{\CLASSINPUTinnersidemargin} + \fi + \addtolength{\oddsidemargin}{-1in} + \addtolength{\evensidemargin}{-1in} + \setlength{\textwidth}{\paperwidth} + \addtolength{\textwidth}{-\CLASSINPUTinnersidemargin} + \addtolength{\textwidth}{-\CLASSINPUToutersidemargin} + \typeout{** ATTENTION: Overriding inner side margin to \CLASSINPUTinnersidemargin\space and + outer side margin to \CLASSINPUToutersidemargin\space via \string\CLASSINPUT.} +\fi + + + +% process CLASSINPUT top/bottom text margin +% if toptext margin defined, but bottomtext margin not, set bottomtext to toptext margin +\ifx\CLASSINPUTtoptextmargin\@IEEEundefined +\else + \ifx\CLASSINPUTbottomtextmargin\@IEEEundefined + \edef\CLASSINPUTbottomtextmargin{\CLASSINPUTtoptextmargin} + \fi +\fi + +\ifx\CLASSINPUTbottomtextmargin\@IEEEundefined +\else + % if bottomtext margin defined, but toptext margin not, set toptext to bottomtext margin + \ifx\CLASSINPUTtoptextmargin\@IEEEundefined + \edef\CLASSINPUTtoptextmargin{\CLASSINPUTbottomtextmargin} + \fi + \setlength{\topmargin}{\CLASSINPUTtoptextmargin} + \addtolength{\topmargin}{-1in} + \addtolength{\topmargin}{-\headheight} + \addtolength{\topmargin}{-\headsep} + \setlength{\textheight}{\paperheight} + \addtolength{\textheight}{-\CLASSINPUTtoptextmargin} + \addtolength{\textheight}{-\CLASSINPUTbottomtextmargin} + % in the default format we use the normal baselineskip as topskip + % we only need 0.7 of this to clear typical top text and we need + % an extra 0.3 spacing at the bottom for descenders. This will + % correct for both. + \addtolength{\topmargin}{-0.3\@IEEEnormalsizeunitybaselineskip} + \typeout{** ATTENTION: Overriding top text margin to \CLASSINPUTtoptextmargin\space and + bottom text margin to \CLASSINPUTbottomtextmargin\space via \string\CLASSINPUT.} +\fi + + + + + + + +% LIST SPACING CONTROLS + +% Controls the amount of EXTRA spacing +% above and below \trivlist +% Both \list and IED lists override this. +% However, \trivlist will use this as will most +% things built from \trivlist like the \center +% environment. +\topsep 0.5\baselineskip + +% Controls the additional spacing around lists preceded +% or followed by blank lines. IEEE does not increase +% spacing before or after paragraphs so it is set to zero. +% \z@ is the same as zero, but faster. +\partopsep \z@ + +% Controls the spacing between paragraphs in lists. +% IEEE does not increase spacing before or after paragraphs +% so this is also zero. +% With IEEEtran.cls, global changes to +% this value DO affect lists (but not IED lists). +\parsep \z@ + +% Controls the extra spacing between list items. +% IEEE does not put extra spacing between items. +% With IEEEtran.cls, global changes to this value DO affect +% lists (but not IED lists). +\itemsep \z@ + +% \itemindent is the amount to indent the FIRST line of a list +% item. It is auto set to zero within the \list environment. To alter +% it, you have to do so when you call the \list. +% However, IEEE uses this for the theorem environment +% There is an alternative value for this near \leftmargini below +\itemindent -1em + +% \leftmargin, the spacing from the left margin of the main text to +% the left of the main body of a list item is set by \list. +% Hence this statement does nothing for lists. +% But, quote and verse do use it for indention. +\leftmargin 2em + +% we retain this stuff from the older IEEEtran.cls so that \list +% will work the same way as before. However, itemize, enumerate and +% description (IED) could care less about what these are as they +% all are overridden. +\leftmargini 2em +%\itemindent 2em % Alternative values: sometimes used. +%\leftmargini 0em +\leftmarginii 1em +\leftmarginiii 1.5em +\leftmarginiv 1.5em +\leftmarginv 1.0em +\leftmarginvi 1.0em +\labelsep 0.5em +\labelwidth \z@ + + +% The old IEEEtran.cls behavior of \list is retained. +% However, the new V1.3 IED list environments override all the +% @list stuff (\@listX is called within \list for the +% appropriate level just before the user's list_decl is called). +% \topsep is now 2pt as IEEE puts a little extra space around +% lists - used by those non-IED macros that depend on \list. +% Note that \parsep and \itemsep are not redefined as in +% the sizexx.clo \@listX (which article.cls uses) so global changes +% of these values DO affect \list +% +\def\@listi{\leftmargin\leftmargini \topsep 2pt plus 1pt minus 1pt} +\let\@listI\@listi +\def\@listii{\leftmargin\leftmarginii\labelwidth\leftmarginii% + \advance\labelwidth-\labelsep \topsep 2pt} +\def\@listiii{\leftmargin\leftmarginiii\labelwidth\leftmarginiii% + \advance\labelwidth-\labelsep \topsep 2pt} +\def\@listiv{\leftmargin\leftmarginiv\labelwidth\leftmarginiv% + \advance\labelwidth-\labelsep \topsep 2pt} +\def\@listv{\leftmargin\leftmarginv\labelwidth\leftmarginv% + \advance\labelwidth-\labelsep \topsep 2pt} +\def\@listvi{\leftmargin\leftmarginvi\labelwidth\leftmarginvi% + \advance\labelwidth-\labelsep \topsep 2pt} + + +% IEEE uses 5) not 5. +\def\labelenumi{\theenumi)} \def\theenumi{\arabic{enumi}} + +% IEEE uses a) not (a) +\def\labelenumii{\theenumii)} \def\theenumii{\alph{enumii}} + +% IEEE uses iii) not iii. +\def\labelenumiii{\theenumiii)} \def\theenumiii{\roman{enumiii}} + +% IEEE uses A) not A. +\def\labelenumiv{\theenumiv)} \def\theenumiv{\Alph{enumiv}} + +% exactly the same as in article.cls +\def\p at enumii{\theenumi} +\def\p at enumiii{\theenumi(\theenumii)} +\def\p at enumiv{\p at enumiii\theenumiii} + +% itemized list label styles +\def\labelitemi{$\scriptstyle\bullet$} +\def\labelitemii{\textbf{--}} +\def\labelitemiii{$\ast$} +\def\labelitemiv{$\cdot$} + + + +% **** V1.3 ENHANCEMENTS **** +% Itemize, Enumerate and Description (IED) List Controls +% *************************** +% +% +% IEEE seems to use at least two different values by +% which ITEMIZED list labels are indented to the right +% For The Journal of Lightwave Technology (JLT) and The Journal +% on Selected Areas in Communications (JSAC), they tend to use +% an indention equal to \parindent. For Transactions on Communications +% they tend to indent ITEMIZED lists a little more--- 1.3\parindent. +% We'll provide both values here for you so that you can choose +% which one you like in your document using a command such as: +% setlength{\IEEEilabelindent}{\IEEEilabelindentB} +\newdimen\IEEEilabelindentA +\IEEEilabelindentA \parindent + +\newdimen\IEEEilabelindentB +\IEEEilabelindentB 1.3\parindent +% However, we'll default to using \parindent +% which makes more sense to me +\newdimen\IEEEilabelindent +\IEEEilabelindent \IEEEilabelindentA + + +% This controls the default amount the enumerated list labels +% are indented to the right. +% Normally, this is the same as the paragraph indention +\newdimen\IEEEelabelindent +\IEEEelabelindent \parindent + +% This controls the default amount the description list labels +% are indented to the right. +% Normally, this is the same as the paragraph indention +\newdimen\IEEEdlabelindent +\IEEEdlabelindent \parindent + +% This is the value actually used within the IED lists. +% The IED environments automatically set its value to +% one of the three values above, so global changes do +% not have any effect +\newdimen\IEEElabelindent +\IEEElabelindent \parindent + +% The actual amount labels will be indented is +% \IEEElabelindent multiplied by the factor below +% corresponding to the level of nesting depth +% This provides a means by which the user can +% alter the effective \IEEElabelindent for deeper +% levels +% There may not be such a thing as correct "standard IEEE" +% values. What IEEE actually does may depend on the specific +% circumstances. +% The first list level almost always has full indention. +% The second levels I've seen have only 75% of the normal indentation +% Three level or greater nestings are very rare. I am guessing +% that they don't use any indentation. +\def\IEEElabelindentfactori{1.0} % almost always one +\def\IEEElabelindentfactorii{0.75} % 0.0 or 1.0 may be used in some cases +\def\IEEElabelindentfactoriii{0.0} % 0.75? 0.5? 0.0? +\def\IEEElabelindentfactoriv{0.0} +\def\IEEElabelindentfactorv{0.0} +\def\IEEElabelindentfactorvi{0.0} + +% value actually used within IED lists, it is auto +% set to one of the 6 values above +% global changes here have no effect +\def\IEEElabelindentfactor{1.0} + +% This controls the default spacing between the end of the IED +% list labels and the list text, when normal text is used for +% the labels. +\newdimen\IEEEiednormlabelsep +\IEEEiednormlabelsep 0.6em + +% This controls the default spacing between the end of the IED +% list labels and the list text, when math symbols are used for +% the labels (nomenclature lists). IEEE usually increases the +% spacing in these cases +\newdimen\IEEEiedmathlabelsep +\IEEEiedmathlabelsep 1.2em + +% This controls the extra vertical separation put above and +% below each IED list. IEEE usually puts a little extra spacing +% around each list. However, this spacing is barely noticeable. +\newskip\IEEEiedtopsep +\IEEEiedtopsep 2pt plus 1pt minus 1pt + + +% This command is executed within each IED list environment +% at the beginning of the list. You can use this to set the +% parameters for some/all your IED list(s) without disturbing +% global parameters that affect things other than lists. +% i.e., renewcommand{\IEEEiedlistdecl}{\setlength{\labelsep}{5em}} +% will alter the \labelsep for the next list(s) until +% \IEEEiedlistdecl is redefined. +\def\IEEEiedlistdecl{\relax} + +% This command provides an easy way to set \leftmargin based +% on the \labelwidth, \labelsep and the argument \IEEElabelindent +% Usage: \IEEEcalcleftmargin{width-to-indent-the-label} +% output is in the \leftmargin variable, i.e., effectively: +% \leftmargin = argument + \labelwidth + \labelsep +% Note controlled spacing here, shield end of lines with % +\def\IEEEcalcleftmargin#1{\setlength{\leftmargin}{#1}% +\addtolength{\leftmargin}{\labelwidth}% +\addtolength{\leftmargin}{\labelsep}} + +% This command provides an easy way to set \labelwidth to the +% width of the given text. It is the same as +% \settowidth{\labelwidth}{label-text} +% and useful as a shorter alternative. +% Typically used to set \labelwidth to be the width +% of the longest label in the list +\def\IEEEsetlabelwidth#1{\settowidth{\labelwidth}{#1}} + +% When this command is executed, IED lists will use the +% IEEEiedmathlabelsep label separation rather than the normal +% spacing. To have an effect, this command must be executed via +% the \IEEEiedlistdecl or within the option of the IED list +% environments. +\def\IEEEusemathlabelsep{\setlength{\labelsep}{\IEEEiedmathlabelsep}} + +% A flag which controls whether the IED lists automatically +% calculate \leftmargin from \IEEElabelindent, \labelwidth and \labelsep +% Useful if you want to specify your own \leftmargin +% This flag must be set (\IEEEnocalcleftmargintrue or \IEEEnocalcleftmarginfalse) +% via the \IEEEiedlistdecl or within the option of the IED list +% environments to have an effect. +\newif\ifIEEEnocalcleftmargin +\IEEEnocalcleftmarginfalse + +% A flag which controls whether \IEEElabelindent is multiplied by +% the \IEEElabelindentfactor for each list level. +% This flag must be set via the \IEEEiedlistdecl or within the option +% of the IED list environments to have an effect. +\newif\ifIEEEnolabelindentfactor +\IEEEnolabelindentfactorfalse + + +% internal variable to indicate type of IED label +% justification +% 0 - left; 1 - center; 2 - right +\def\@IEEEiedjustify{0} + + +% commands to allow the user to control IED +% label justifications. Use these commands within +% the IED environment option or in the \IEEEiedlistdecl +% Note that changing the normal list justifications +% is nonstandard and IEEE may not like it if you do so! +% I include these commands as they may be helpful to +% those who are using these enhanced list controls for +% other non-IEEE related LaTeX work. +% itemize and enumerate automatically default to right +% justification, description defaults to left. +\def\IEEEiedlabeljustifyl{\def\@IEEEiedjustify{0}}%left +\def\IEEEiedlabeljustifyc{\def\@IEEEiedjustify{1}}%center +\def\IEEEiedlabeljustifyr{\def\@IEEEiedjustify{2}}%right + + + + +% commands to save to and restore from the list parameter copies +% this allows us to set all the list parameters within +% the list_decl and prevent \list (and its \@list) +% from overriding any of our parameters +% V1.6 use \edefs instead of dimen's to conserve dimen registers +% Note controlled spacing here, shield end of lines with % +\def\@IEEEsavelistparams{\edef\@IEEEiedtopsep{\the\topsep}% +\edef\@IEEEiedlabelwidth{\the\labelwidth}% +\edef\@IEEEiedlabelsep{\the\labelsep}% +\edef\@IEEEiedleftmargin{\the\leftmargin}% +\edef\@IEEEiedpartopsep{\the\partopsep}% +\edef\@IEEEiedparsep{\the\parsep}% +\edef\@IEEEieditemsep{\the\itemsep}% +\edef\@IEEEiedrightmargin{\the\rightmargin}% +\edef\@IEEEiedlistparindent{\the\listparindent}% +\edef\@IEEEieditemindent{\the\itemindent}} + +% Note controlled spacing here +\def\@IEEErestorelistparams{\topsep\@IEEEiedtopsep\relax% +\labelwidth\@IEEEiedlabelwidth\relax% +\labelsep\@IEEEiedlabelsep\relax% +\leftmargin\@IEEEiedleftmargin\relax% +\partopsep\@IEEEiedpartopsep\relax% +\parsep\@IEEEiedparsep\relax% +\itemsep\@IEEEieditemsep\relax% +\rightmargin\@IEEEiedrightmargin\relax% +\listparindent\@IEEEiedlistparindent\relax% +\itemindent\@IEEEieditemindent\relax} + + +% v1.6b provide original LaTeX IED list environments +% note that latex.ltx defines \itemize and \enumerate, but not \description +% which must be created by the base classes +% save original LaTeX itemize and enumerate +\let\LaTeXitemize\itemize +\let\endLaTeXitemize\enditemize +\let\LaTeXenumerate\enumerate +\let\endLaTeXenumerate\endenumerate + +% provide original LaTeX description environment from article.cls +\newenvironment{LaTeXdescription} + {\list{}{\labelwidth\z@ \itemindent-\leftmargin + \let\makelabel\descriptionlabel}} + {\endlist} +\newcommand*\descriptionlabel[1]{\hspace\labelsep + \normalfont\bfseries #1} + + +% override LaTeX's default IED lists +\def\itemize{\@IEEEitemize} +\def\enditemize{\@endIEEEitemize} +\def\enumerate{\@IEEEenumerate} +\def\endenumerate{\@endIEEEenumerate} +\def\description{\@IEEEdescription} +\def\enddescription{\@endIEEEdescription} + +% provide the user with aliases - may help those using packages that +% override itemize, enumerate, or description +\def\IEEEitemize{\@IEEEitemize} +\def\endIEEEitemize{\@endIEEEitemize} +\def\IEEEenumerate{\@IEEEenumerate} +\def\endIEEEenumerate{\@endIEEEenumerate} +\def\IEEEdescription{\@IEEEdescription} +\def\endIEEEdescription{\@endIEEEdescription} + + +% V1.6 we want to keep the IEEEtran IED list definitions as our own internal +% commands so they are protected against redefinition +\def\@IEEEitemize{\@ifnextchar[{\@@IEEEitemize}{\@@IEEEitemize[\relax]}} +\def\@IEEEenumerate{\@ifnextchar[{\@@IEEEenumerate}{\@@IEEEenumerate[\relax]}} +\def\@IEEEdescription{\@ifnextchar[{\@@IEEEdescription}{\@@IEEEdescription[\relax]}} +\def\@endIEEEitemize{\endlist} +\def\@endIEEEenumerate{\endlist} +\def\@endIEEEdescription{\endlist} + + +% DO NOT ALLOW BLANK LINES TO BE IN THESE IED ENVIRONMENTS +% AS THIS WILL FORCE NEW PARAGRAPHS AFTER THE IED LISTS +% IEEEtran itemized list MDS 1/2001 +% Note controlled spacing here, shield end of lines with % +\def\@@IEEEitemize[#1]{% + \ifnum\@itemdepth>3\relax\@toodeep\else% + \ifnum\@listdepth>5\relax\@toodeep\else% + \advance\@itemdepth\@ne% + \edef\@itemitem{labelitem\romannumeral\the\@itemdepth}% + % get the labelindentfactor for this level + \advance\@listdepth\@ne% we need to know what the level WILL be + \edef\IEEElabelindentfactor{\csname IEEElabelindentfactor\romannumeral\the\@listdepth\endcsname}% + \advance\@listdepth-\@ne% undo our increment + \def\@IEEEiedjustify{2}% right justified labels are default + % set other defaults + \IEEEnocalcleftmarginfalse% + \IEEEnolabelindentfactorfalse% + \topsep\IEEEiedtopsep% + \IEEElabelindent\IEEEilabelindent% + \labelsep\IEEEiednormlabelsep% + \partopsep 0ex% + \parsep 0ex% + \itemsep 0ex% + \rightmargin 0em% + \listparindent 0em% + \itemindent 0em% + % calculate the label width + % the user can override this later if + % they specified a \labelwidth + \settowidth{\labelwidth}{\csname labelitem\romannumeral\the\@itemdepth\endcsname}% + \@IEEEsavelistparams% save our list parameters + \list{\csname\@itemitem\endcsname}{% + \@IEEErestorelistparams% override any list{} changes + % to our globals + \let\makelabel\@IEEEiedmakelabel% v1.6b setup \makelabel + \IEEEiedlistdecl% let user alter parameters + #1\relax% + % If the user has requested not to use the + % labelindent factor, don't revise \labelindent + \ifIEEEnolabelindentfactor\relax% + \else\IEEElabelindent=\IEEElabelindentfactor\labelindent% + \fi% + % Unless the user has requested otherwise, + % calculate our left margin based + % on \IEEElabelindent, \labelwidth and + % \labelsep + \ifIEEEnocalcleftmargin\relax% + \else\IEEEcalcleftmargin{\IEEElabelindent}% + \fi}\fi\fi}% + + +% DO NOT ALLOW BLANK LINES TO BE IN THESE IED ENVIRONMENTS +% AS THIS WILL FORCE NEW PARAGRAPHS AFTER THE IED LISTS +% IEEEtran enumerate list MDS 1/2001 +% Note controlled spacing here, shield end of lines with % +\def\@@IEEEenumerate[#1]{% + \ifnum\@enumdepth>3\relax\@toodeep\else% + \ifnum\@listdepth>5\relax\@toodeep\else% + \advance\@enumdepth\@ne% + \edef\@enumctr{enum\romannumeral\the\@enumdepth}% + % get the labelindentfactor for this level + \advance\@listdepth\@ne% we need to know what the level WILL be + \edef\IEEElabelindentfactor{\csname IEEElabelindentfactor\romannumeral\the\@listdepth\endcsname}% + \advance\@listdepth-\@ne% undo our increment + \def\@IEEEiedjustify{2}% right justified labels are default + % set other defaults + \IEEEnocalcleftmarginfalse% + \IEEEnolabelindentfactorfalse% + \topsep\IEEEiedtopsep% + \IEEElabelindent\IEEEelabelindent% + \labelsep\IEEEiednormlabelsep% + \partopsep 0ex% + \parsep 0ex% + \itemsep 0ex% + \rightmargin 0em% + \listparindent 0em% + \itemindent 0em% + % calculate the label width + % We'll set it to the width suitable for all labels using + % normalfont 1) to 9) + % The user can override this later + \settowidth{\labelwidth}{9)}% + \@IEEEsavelistparams% save our list parameters + \list{\csname label\@enumctr\endcsname}{\usecounter{\@enumctr}% + \@IEEErestorelistparams% override any list{} changes + % to our globals + \let\makelabel\@IEEEiedmakelabel% v1.6b setup \makelabel + \IEEEiedlistdecl% let user alter parameters + #1\relax% + % If the user has requested not to use the + % IEEElabelindent factor, don't revise \IEEElabelindent + \ifIEEEnolabelindentfactor\relax% + \else\IEEElabelindent=\IEEElabelindentfactor\IEEElabelindent% + \fi% + % Unless the user has requested otherwise, + % calculate our left margin based + % on \IEEElabelindent, \labelwidth and + % \labelsep + \ifIEEEnocalcleftmargin\relax% + \else\IEEEcalcleftmargin{\IEEElabelindent}% + \fi}\fi\fi}% + + +% DO NOT ALLOW BLANK LINES TO BE IN THESE IED ENVIRONMENTS +% AS THIS WILL FORCE NEW PARAGRAPHS AFTER THE IED LISTS +% IEEEtran description list MDS 1/2001 +% Note controlled spacing here, shield end of lines with % +\def\@@IEEEdescription[#1]{% + \ifnum\@listdepth>5\relax\@toodeep\else% + % get the labelindentfactor for this level + \advance\@listdepth\@ne% we need to know what the level WILL be + \edef\IEEElabelindentfactor{\csname IEEElabelindentfactor\romannumeral\the\@listdepth\endcsname}% + \advance\@listdepth-\@ne% undo our increment + \def\@IEEEiedjustify{0}% left justified labels are default + % set other defaults + \IEEEnocalcleftmarginfalse% + \IEEEnolabelindentfactorfalse% + \topsep\IEEEiedtopsep% + \IEEElabelindent\IEEEdlabelindent% + % assume normal labelsep + \labelsep\IEEEiednormlabelsep% + \partopsep 0ex% + \parsep 0ex% + \itemsep 0ex% + \rightmargin 0em% + \listparindent 0em% + \itemindent 0em% + % Bogus label width in case the user forgets + % to set it. + % TIP: If you want to see what a variable's width is you + % can use the TeX command \showthe\width-variable to + % display it on the screen during compilation + % (This might be helpful to know when you need to find out + % which label is the widest) + \settowidth{\labelwidth}{Hello}% + \@IEEEsavelistparams% save our list parameters + \list{}{\@IEEErestorelistparams% override any list{} changes + % to our globals + \let\makelabel\@IEEEiedmakelabel% v1.6b setup \makelabel + \IEEEiedlistdecl% let user alter parameters + #1\relax% + % If the user has requested not to use the + % labelindent factor, don't revise \IEEElabelindent + \ifIEEEnolabelindentfactor\relax% + \else\IEEElabelindent=\IEEElabelindentfactor\IEEElabelindent% + \fi% + % Unless the user has requested otherwise, + % calculate our left margin based + % on \IEEElabelindent, \labelwidth and + % \labelsep + \ifIEEEnocalcleftmargin\relax% + \else\IEEEcalcleftmargin{\IEEElabelindent}\relax% + \fi}\fi} + +% v1.6b we use one makelabel that does justification as needed. +\def\@IEEEiedmakelabel#1{\relax\if\@IEEEiedjustify 0\relax +\makebox[\labelwidth][l]{\normalfont #1}\else +\if\@IEEEiedjustify 1\relax +\makebox[\labelwidth][c]{\normalfont #1}\else +\makebox[\labelwidth][r]{\normalfont #1}\fi\fi} + + +% VERSE and QUOTE +% V1.7 define environments with newenvironment +\newenvironment{verse}{\let\\=\@centercr + \list{}{\itemsep\z@ \itemindent -1.5em \listparindent \itemindent + \rightmargin\leftmargin\advance\leftmargin 1.5em}\item\relax} + {\endlist} +\newenvironment{quotation}{\list{}{\listparindent 1.5em \itemindent\listparindent + \rightmargin\leftmargin \parsep 0pt plus 1pt}\item\relax} + {\endlist} +\newenvironment{quote}{\list{}{\rightmargin\leftmargin}\item\relax} + {\endlist} + + +% \titlepage +% provided only for backward compatibility. \maketitle is the correct +% way to create the title page. +\newif\if at restonecol +\def\titlepage{\@restonecolfalse\if at twocolumn\@restonecoltrue\onecolumn + \else \newpage \fi \thispagestyle{empty}\c at page\z@} +\def\endtitlepage{\if at restonecol\twocolumn \else \newpage \fi} + +% standard values from article.cls +\arraycolsep 5pt +\arrayrulewidth .4pt +\doublerulesep 2pt + +\tabcolsep 6pt +\tabbingsep 0.5em + + +%% FOOTNOTES +% +%\skip\footins 10pt plus 4pt minus 2pt +% V1.6 respond to changes in font size +% space added above the footnotes (if present) +\skip\footins 0.9\baselineskip plus 0.4\baselineskip minus 0.2\baselineskip + +% V1.6, we need to make \footnotesep responsive to changes +% in \baselineskip or strange spacings will result when in +% draft mode. Here is a little LaTeX secret - \footnotesep +% determines the height of an invisible strut that is placed +% *above* the baseline of footnotes after the first. Since +% LaTeX considers the space for characters to be 0.7/baselineskip +% above the baseline and 0.3/baselineskip below it, we need to +% use 0.7/baselineskip as a \footnotesep to maintain equal spacing +% between all the lines of the footnotes. IEEE often uses a tad +% more, so use 0.8\baselineskip. This slightly larger value also helps +% the text to clear the footnote marks. Note that \thanks in IEEEtran +% uses its own value of \footnotesep which is set in \maketitle. +{\footnotesize +\global\footnotesep 0.8\baselineskip} + + +\skip\@mpfootins = \skip\footins +\fboxsep = 3pt +\fboxrule = .4pt +% V1.6 use 1em, then use LaTeX2e's \@makefnmark +% Note that IEEE normally *left* aligns the footnote marks, so we don't need +% box resizing tricks here. +\long\def\@makefntext#1{\parindent 1em\indent\hbox{\@makefnmark}#1}% V1.6 use 1em +% V1.7 compsoc does not use superscipts for footnote marks +\ifCLASSOPTIONcompsoc +\def\@IEEEcompsocmakefnmark{\hbox{\normalfont\@thefnmark.\ }} +\long\def\@makefntext#1{\parindent 1em\indent\hbox{\@IEEEcompsocmakefnmark}#1} +\fi + +% IEEE does not use footnote rules +\def\footnoterule{} + +% V1.7 for compsoc, IEEE uses a footnote rule only for \thanks. We devise a "one-shot" +% system to implement this. +\newif\if at IEEEenableoneshotfootnoterule +\@IEEEenableoneshotfootnoterulefalse +\ifCLASSOPTIONcompsoc +\def\footnoterule{\relax\if at IEEEenableoneshotfootnoterule +\kern-5pt +\hbox to \columnwidth{\hfill\vrule width 0.5\columnwidth height 0.4pt\hfill} +\kern4.6pt +\global\@IEEEenableoneshotfootnoterulefalse +\else +\relax +\fi} +\fi + +% V1.6 do not allow LaTeX to break a footnote across multiple pages +\interfootnotelinepenalty=10000 + +% V1.6 discourage breaks within equations +% Note that amsmath normally sets this to 10000, +% but LaTeX2e normally uses 100. +\interdisplaylinepenalty=2500 + +% default allows section depth up to /paragraph +\setcounter{secnumdepth}{4} + +% technotes do not allow /paragraph +\ifCLASSOPTIONtechnote + \setcounter{secnumdepth}{3} +\fi +% neither do compsoc conferences +\@IEEEcompsocconfonly{\setcounter{secnumdepth}{3}} + + +\newcounter{section} +\newcounter{subsection}[section] +\newcounter{subsubsection}[subsection] +\newcounter{paragraph}[subsubsection] + +% used only by IEEEtran's IEEEeqnarray as other packages may +% have their own, different, implementations +\newcounter{IEEEsubequation}[equation] + +% as shown when called by user from \ref, \label and in table of contents +\def\theequation{\arabic{equation}} % 1 +\def\theIEEEsubequation{\theequation\alph{IEEEsubequation}} % 1a (used only by IEEEtran's IEEEeqnarray) +\ifCLASSOPTIONcompsoc +% compsoc is all arabic +\def\thesection{\arabic{section}} +\def\thesubsection{\thesection.\arabic{subsection}} +\def\thesubsubsection{\thesubsection.\arabic{subsubsection}} +\def\theparagraph{\thesubsubsection.\arabic{paragraph}} +\else +\def\thesection{\Roman{section}} % I +% V1.7, \mbox prevents breaks around - +\def\thesubsection{\mbox{\thesection-\Alph{subsection}}} % I-A +% V1.7 use I-A1 format used by IEEE rather than I-A.1 +\def\thesubsubsection{\thesubsection\arabic{subsubsection}} % I-A1 +\def\theparagraph{\thesubsubsection\alph{paragraph}} % I-A1a +\fi + +% From Heiko Oberdiek. Because of the \mbox in \thesubsection, we need to +% tell hyperref to disable the \mbox command when making PDF bookmarks. +% This done already with hyperref.sty version 6.74o and later, but +% it will not hurt to do it here again for users of older versions. +\@ifundefined{pdfstringdefPreHook}{\let\pdfstringdefPreHook\@empty}{}% +\g at addto@macro\pdfstringdefPreHook{\let\mbox\relax} + + +% Main text forms (how shown in main text headings) +% V1.6, using \thesection in \thesectiondis allows changes +% in the former to automatically appear in the latter +\ifCLASSOPTIONcompsoc + \ifCLASSOPTIONconference% compsoc conference + \def\thesectiondis{\thesection.} + \def\thesubsectiondis{\thesectiondis\arabic{subsection}.} + \def\thesubsubsectiondis{\thesubsectiondis\arabic{subsubsection}.} + \def\theparagraphdis{\thesubsubsectiondis\arabic{paragraph}.} + \else% compsoc not conferencs + \def\thesectiondis{\thesection} + \def\thesubsectiondis{\thesectiondis.\arabic{subsection}} + \def\thesubsubsectiondis{\thesubsectiondis.\arabic{subsubsection}} + \def\theparagraphdis{\thesubsubsectiondis.\arabic{paragraph}} + \fi +\else% not compsoc + \def\thesectiondis{\thesection.} % I. + \def\thesubsectiondis{\Alph{subsection}.} % B. + \def\thesubsubsectiondis{\arabic{subsubsection})} % 3) + \def\theparagraphdis{\alph{paragraph})} % d) +\fi + +% just like LaTeX2e's \@eqnnum +\def\theequationdis{{\normalfont \normalcolor (\theequation)}}% (1) +% IEEEsubequation used only by IEEEtran's IEEEeqnarray +\def\theIEEEsubequationdis{{\normalfont \normalcolor (\theIEEEsubequation)}}% (1a) +% redirect LaTeX2e's equation number display and all that depend on +% it, through IEEEtran's \theequationdis +\def\@eqnnum{\theequationdis} + + + +% V1.7 provide string macros as article.cls does +\def\contentsname{Contents} +\def\listfigurename{List of Figures} +\def\listtablename{List of Tables} +\def\refname{References} +\def\indexname{Index} +\def\figurename{Fig.} +\def\tablename{TABLE} +\@IEEEcompsocconfonly{\def\figurename{Figure}\def\tablename{Table}} +\def\partname{Part} +\def\appendixname{Appendix} +\def\abstractname{Abstract} +% IEEE specific names +\def\IEEEkeywordsname{Index Terms} +\def\IEEEproofname{Proof} + + +% LIST OF FIGURES AND TABLES AND TABLE OF CONTENTS +% +\def\@pnumwidth{1.55em} +\def\@tocrmarg{2.55em} +\def\@dotsep{4.5} +\setcounter{tocdepth}{3} + +% adjusted some spacings here so that section numbers will not easily +% collide with the section titles. +% VIII; VIII-A; and VIII-A.1 are usually the worst offenders. +% MDS 1/2001 +\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}} +\def\l at section#1#2{\addpenalty{\@secpenalty}\addvspace{1.0em plus 1pt}% + \@tempdima 2.75em \begingroup \parindent \z@ \rightskip \@pnumwidth% + \parfillskip-\@pnumwidth {\bfseries\leavevmode #1}\hfil\hbox to\@pnumwidth{\hss #2}\par% + \endgroup} +% argument format #1:level, #2:labelindent,#3:labelsep +\def\l at subsection{\@dottedtocline{2}{2.75em}{3.75em}} +\def\l at subsubsection{\@dottedtocline{3}{6.5em}{4.5em}} +% must provide \l@ defs for ALL sublevels EVEN if tocdepth +% is such as they will not appear in the table of contents +% these defs are how TOC knows what level these things are! +\def\l at paragraph{\@dottedtocline{4}{6.5em}{5.5em}} +\def\l at subparagraph{\@dottedtocline{5}{6.5em}{6.5em}} +\def\listoffigures{\section*{\listfigurename}\@starttoc{lof}} +\def\l at figure{\@dottedtocline{1}{0em}{2.75em}} +\def\listoftables{\section*{\listtablename}\@starttoc{lot}} +\let\l at table\l at figure + + +%% Definitions for floats +%% +%% Normal Floats +\floatsep 1\baselineskip plus 0.2\baselineskip minus 0.2\baselineskip +\textfloatsep 1.7\baselineskip plus 0.2\baselineskip minus 0.4\baselineskip +\@fptop 0pt plus 1fil +\@fpsep 0.75\baselineskip plus 2fil +\@fpbot 0pt plus 1fil +\def\topfraction{0.9} +\def\bottomfraction{0.4} +\def\floatpagefraction{0.8} +% V1.7, let top floats approach 90% of page +\def\textfraction{0.1} + +%% Double Column Floats +\dblfloatsep 1\baselineskip plus 0.2\baselineskip minus 0.2\baselineskip + +\dbltextfloatsep 1.7\baselineskip plus 0.2\baselineskip minus 0.4\baselineskip +% Note that it would be nice if the rubber here actually worked in LaTeX2e. +% There is a long standing limitation in LaTeX, first discovered (to the best +% of my knowledge) by Alan Jeffrey in 1992. LaTeX ignores the stretchable +% portion of \dbltextfloatsep, and as a result, double column figures can and +% do result in an non-integer number of lines in the main text columns with +% underfull vbox errors as a consequence. A post to comp.text.tex +% by Donald Arseneau confirms that this had not yet been fixed in 1998. +% IEEEtran V1.6 will fix this problem for you in the titles, but it doesn't +% protect you from other double floats. Happy vspace'ing. + +\@dblfptop 0pt plus 1fil +\@dblfpsep 0.75\baselineskip plus 2fil +\@dblfpbot 0pt plus 1fil +\def\dbltopfraction{0.8} +\def\dblfloatpagefraction{0.8} +\setcounter{dbltopnumber}{4} + +\intextsep 1\baselineskip plus 0.2\baselineskip minus 0.2\baselineskip +\setcounter{topnumber}{2} +\setcounter{bottomnumber}{2} +\setcounter{totalnumber}{4} + + + +% article class provides these, we should too. +\newlength\abovecaptionskip +\newlength\belowcaptionskip +% but only \abovecaptionskip is used above figure captions and *below* table +% captions +\setlength\abovecaptionskip{0.5\baselineskip} +\setlength\belowcaptionskip{0pt} +% V1.6 create hooks in case the caption spacing ever needs to be +% overridden by a user +\def\@IEEEfigurecaptionsepspace{\vskip\abovecaptionskip\relax}% +\def\@IEEEtablecaptionsepspace{\vskip\abovecaptionskip\relax}% + + +% 1.6b revise caption system so that \@makecaption uses two arguments +% as with LaTeX2e. Otherwise, there will be problems when using hyperref. +\def\@IEEEtablestring{table} + +\ifCLASSOPTIONcompsoc +% V1.7 compsoc \@makecaption +\ifCLASSOPTIONconference% compsoc conference +\long\def\@makecaption#1#2{% +% test if is a for a figure or table +\ifx\@captype\@IEEEtablestring% +% if a table, do table caption +\normalsize\begin{center}{\normalfont\sffamily\normalsize {#1.}~ #2}\end{center}% +\@IEEEtablecaptionsepspace +% if not a table, format it as a figure +\else +\@IEEEfigurecaptionsepspace +\setbox\@tempboxa\hbox{\normalfont\sffamily\normalsize {#1.}~ #2}% +\ifdim \wd\@tempboxa >\hsize% +% if caption is longer than a line, let it wrap around +\setbox\@tempboxa\hbox{\normalfont\sffamily\normalsize {#1.}~ }% +\parbox[t]{\hsize}{\normalfont\sffamily\normalsize \noindent\unhbox\@tempboxa#2}% +% if caption is shorter than a line, center +\else% +\hbox to\hsize{\normalfont\sffamily\normalsize\hfil\box\@tempboxa\hfil}% +\fi\fi} +\else% nonconference compsoc +\long\def\@makecaption#1#2{% +% test if is a for a figure or table +\ifx\@captype\@IEEEtablestring% +% if a table, do table caption +\normalsize\begin{center}{\normalfont\sffamily\normalsize #1}\\{\normalfont\sffamily\normalsize #2}\end{center}% +\@IEEEtablecaptionsepspace +% if not a table, format it as a figure +\else +\@IEEEfigurecaptionsepspace +\setbox\@tempboxa\hbox{\normalfont\sffamily\normalsize {#1.}~ #2}% +\ifdim \wd\@tempboxa >\hsize% +% if caption is longer than a line, let it wrap around +\setbox\@tempboxa\hbox{\normalfont\sffamily\normalsize {#1.}~ }% +\parbox[t]{\hsize}{\normalfont\sffamily\normalsize \noindent\unhbox\@tempboxa#2}% +% if caption is shorter than a line, left justify +\else% +\hbox to\hsize{\normalfont\sffamily\normalsize\box\@tempboxa\hfil}% +\fi\fi} +\fi + +\else% traditional noncompsoc \@makecaption +\long\def\@makecaption#1#2{% +% test if is a for a figure or table +\ifx\@captype\@IEEEtablestring% +% if a table, do table caption +\footnotesize\begin{center}{\normalfont\footnotesize #1}\\{\normalfont\footnotesize\scshape #2}\end{center}% +\@IEEEtablecaptionsepspace +% if not a table, format it as a figure +\else +\@IEEEfigurecaptionsepspace +% 3/2001 use footnotesize, not small; use two nonbreaking spaces, not one +\setbox\@tempboxa\hbox{\normalfont\footnotesize {#1.}~~ #2}% +\ifdim \wd\@tempboxa >\hsize% +% if caption is longer than a line, let it wrap around +\setbox\@tempboxa\hbox{\normalfont\footnotesize {#1.}~~ }% +\parbox[t]{\hsize}{\normalfont\footnotesize\noindent\unhbox\@tempboxa#2}% +% if caption is shorter than a line, center if conference, left justify otherwise +\else% +\ifCLASSOPTIONconference \hbox to\hsize{\normalfont\footnotesize\hfil\box\@tempboxa\hfil}% +\else \hbox to\hsize{\normalfont\footnotesize\box\@tempboxa\hfil}% +\fi\fi\fi} +\fi + + + +% V1.7 disable captions class option, do so in a way that retains operation of \label +% within \caption +\ifCLASSOPTIONcaptionsoff +\long\def\@makecaption#1#2{\vspace*{2em}\footnotesize\begin{center}{\footnotesize #1}\end{center}% +\let\@IEEEtemporiglabeldefsave\label +\let\@IEEEtemplabelargsave\relax +\def\label##1{\gdef\@IEEEtemplabelargsave{##1}}% +\setbox\@tempboxa\hbox{#2}% +\let\label\@IEEEtemporiglabeldefsave +\ifx\@IEEEtemplabelargsave\relax\else\label{\@IEEEtemplabelargsave}\fi} +\fi + + +% V1.7 define end environments with \def not \let so as to work OK with +% preview-latex +\newcounter{figure} +\def\thefigure{\@arabic\c at figure} +\def\fps at figure{tbp} +\def\ftype at figure{1} +\def\ext at figure{lof} +\def\fnum at figure{\figurename~\thefigure} +\def\figure{\@float{figure}} +\def\endfigure{\end at float} +\@namedef{figure*}{\@dblfloat{figure}} +\@namedef{endfigure*}{\end at dblfloat} +\newcounter{table} +\ifCLASSOPTIONcompsoc +\def\thetable{\arabic{table}} +\else +\def\thetable{\@Roman\c at table} +\fi +\def\fps at table{tbp} +\def\ftype at table{2} +\def\ext at table{lot} +\def\fnum at table{\tablename~\thetable} +% V1.6 IEEE uses 8pt text for tables +% to default to footnotesize, we hack into LaTeX2e's \@floatboxreset and pray +\def\table{\def\@floatboxreset{\reset at font\footnotesize\@setminipage}\@float{table}} +\def\endtable{\end at float} +% v1.6b double column tables need to default to footnotesize as well. +\@namedef{table*}{\def\@floatboxreset{\reset at font\footnotesize\@setminipage}\@dblfloat{table}} +\@namedef{endtable*}{\end at dblfloat} + + + + +%% +%% START OF IEEEeqnarry DEFINITIONS +%% +%% Inspired by the concepts, examples, and previous works of LaTeX +%% coders and developers such as Donald Arseneau, Fred Bartlett, +%% David Carlisle, Tony Liu, Frank Mittelbach, Piet van Oostrum, +%% Roland Winkler and Mark Wooding. +%% I don't make the claim that my work here is even near their calibre. ;) + + +% hook to allow easy changeover to IEEEtran.cls/tools.sty error reporting +\def\@IEEEclspkgerror{\ClassError{IEEEtran}} + +\newif\if at IEEEeqnarraystarform% flag to indicate if the environment was called as the star form +\@IEEEeqnarraystarformfalse + +\newif\if at advanceIEEEeqncolcnt% tracks if the environment should advance the col counter +% allows a way to make an \IEEEeqnarraybox that can be used within an \IEEEeqnarray +% used by IEEEeqnarraymulticol so that it can work properly in both +\@advanceIEEEeqncolcnttrue + +\newcount\@IEEEeqnnumcols % tracks how many IEEEeqnarray cols are defined +\newcount\@IEEEeqncolcnt % tracks how many IEEEeqnarray cols the user actually used + + +% The default math style used by the columns +\def\IEEEeqnarraymathstyle{\displaystyle} +% The default text style used by the columns +% default to using the current font +\def\IEEEeqnarraytextstyle{\relax} + +% like the iedlistdecl but for \IEEEeqnarray +\def\IEEEeqnarraydecl{\relax} +\def\IEEEeqnarrayboxdecl{\relax} + +% \yesnumber is the opposite of \nonumber +% a novel concept with the same def as the equationarray package +% However, we give IEEE versions too since some LaTeX packages such as +% the MDWtools mathenv.sty redefine \nonumber to something else. +\providecommand{\yesnumber}{\global\@eqnswtrue} +\def\IEEEyesnumber{\global\@eqnswtrue} +\def\IEEEnonumber{\global\@eqnswfalse} + + +\def\IEEEyessubnumber{\global\@IEEEissubequationtrue\global\@eqnswtrue% +\if at IEEEeqnarrayISinner% only do something inside an IEEEeqnarray +\if at IEEElastlinewassubequation\addtocounter{equation}{-1}\else\setcounter{IEEEsubequation}{1}\fi% +\def\@currentlabel{\p at IEEEsubequation\theIEEEsubequation}\fi} + +% flag to indicate that an equation is a sub equation +\newif\if at IEEEissubequation% +\@IEEEissubequationfalse + +% allows users to "push away" equations that get too close to the equation numbers +\def\IEEEeqnarraynumspace{\hphantom{\if at IEEEissubequation\theIEEEsubequationdis\else\theequationdis\fi}} + +% provides a way to span multiple columns within IEEEeqnarray environments +% will consider \if at advanceIEEEeqncolcnt before globally advancing the +% column counter - so as to work within \IEEEeqnarraybox +% usage: \IEEEeqnarraymulticol{number cols. to span}{col type}{cell text} +\long\def\IEEEeqnarraymulticol#1#2#3{\multispan{#1}% +% check if column is defined +\relax\expandafter\ifx\csname @IEEEeqnarraycolDEF#2\endcsname\@IEEEeqnarraycolisdefined% +\csname @IEEEeqnarraycolPRE#2\endcsname#3\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\csname @IEEEeqnarraycolPOST#2\endcsname% +\else% if not, error and use default type +\@IEEEclspkgerror{Invalid column type "#2" in \string\IEEEeqnarraymulticol.\MessageBreak +Using a default centering column instead}% +{You must define IEEEeqnarray column types before use.}% +\csname @IEEEeqnarraycolPRE at IEEEdefault\endcsname#3\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\csname @IEEEeqnarraycolPOST at IEEEdefault\endcsname% +\fi% +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by #1\relax\fi} + +% like \omit, but maintains track of the column counter for \IEEEeqnarray +\def\IEEEeqnarrayomit{\omit\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by 1\relax\fi} + + +% provides a way to define a letter referenced column type +% usage: \IEEEeqnarraydefcol{col. type letter/name}{pre insertion text}{post insertion text} +\def\IEEEeqnarraydefcol#1#2#3{\expandafter\def\csname @IEEEeqnarraycolPRE#1\endcsname{#2}% +\expandafter\def\csname @IEEEeqnarraycolPOST#1\endcsname{#3}% +\expandafter\def\csname @IEEEeqnarraycolDEF#1\endcsname{1}} + + +% provides a way to define a numerically referenced inter-column glue types +% usage: \IEEEeqnarraydefcolsep{col. glue number}{glue definition} +\def\IEEEeqnarraydefcolsep#1#2{\expandafter\def\csname @IEEEeqnarraycolSEP\romannumeral #1\endcsname{#2}% +\expandafter\def\csname @IEEEeqnarraycolSEPDEF\romannumeral #1\endcsname{1}} + + +\def\@IEEEeqnarraycolisdefined{1}% just a macro for 1, used for checking undefined column types + + +% expands and appends the given argument to the \@IEEEtrantmptoksA token list +% used to build up the \halign preamble +\def\@IEEEappendtoksA#1{\edef\@@IEEEappendtoksA{\@IEEEtrantmptoksA={\the\@IEEEtrantmptoksA #1}}% +\@@IEEEappendtoksA} + +% also appends to \@IEEEtrantmptoksA, but does not expand the argument +% uses \toks8 as a scratchpad register +\def\@IEEEappendNOEXPANDtoksA#1{\toks8={#1}% +\edef\@@IEEEappendNOEXPANDtoksA{\@IEEEtrantmptoksA={\the\@IEEEtrantmptoksA\the\toks8}}% +\@@IEEEappendNOEXPANDtoksA} + +% define some common column types for the user +% math +\IEEEeqnarraydefcol{l}{$\IEEEeqnarraymathstyle}{$\hfil} +\IEEEeqnarraydefcol{c}{\hfil$\IEEEeqnarraymathstyle}{$\hfil} +\IEEEeqnarraydefcol{r}{\hfil$\IEEEeqnarraymathstyle}{$} +\IEEEeqnarraydefcol{L}{$\IEEEeqnarraymathstyle{}}{{}$\hfil} +\IEEEeqnarraydefcol{C}{\hfil$\IEEEeqnarraymathstyle{}}{{}$\hfil} +\IEEEeqnarraydefcol{R}{\hfil$\IEEEeqnarraymathstyle{}}{{}$} +% text +\IEEEeqnarraydefcol{s}{\IEEEeqnarraytextstyle}{\hfil} +\IEEEeqnarraydefcol{t}{\hfil\IEEEeqnarraytextstyle}{\hfil} +\IEEEeqnarraydefcol{u}{\hfil\IEEEeqnarraytextstyle}{} + +% vertical rules +\IEEEeqnarraydefcol{v}{}{\vrule width\arrayrulewidth} +\IEEEeqnarraydefcol{vv}{\vrule width\arrayrulewidth\hfil}{\hfil\vrule width\arrayrulewidth} +\IEEEeqnarraydefcol{V}{}{\vrule width\arrayrulewidth\hskip\doublerulesep\vrule width\arrayrulewidth} +\IEEEeqnarraydefcol{VV}{\vrule width\arrayrulewidth\hskip\doublerulesep\vrule width\arrayrulewidth\hfil}% +{\hfil\vrule width\arrayrulewidth\hskip\doublerulesep\vrule width\arrayrulewidth} + +% horizontal rules +\IEEEeqnarraydefcol{h}{}{\leaders\hrule height\arrayrulewidth\hfil} +\IEEEeqnarraydefcol{H}{}{\leaders\vbox{\hrule width\arrayrulewidth\vskip\doublerulesep\hrule width\arrayrulewidth}\hfil} + +% plain +\IEEEeqnarraydefcol{x}{}{} +\IEEEeqnarraydefcol{X}{$}{$} + +% the default column type to use in the event a column type is not defined +\IEEEeqnarraydefcol{@IEEEdefault}{\hfil$\IEEEeqnarraymathstyle}{$\hfil} + + +% a zero tabskip (used for "-" col types) +\def\@IEEEeqnarraycolSEPzero{0pt plus 0pt minus 0pt} +% a centering tabskip (used for "+" col types) +\def\@IEEEeqnarraycolSEPcenter{1000pt plus 0pt minus 1000pt} + +% top level default tabskip glues for the start, end, and inter-column +% may be reset within environments not always at the top level, e.g., \IEEEeqnarraybox +\edef\@IEEEeqnarraycolSEPdefaultstart{\@IEEEeqnarraycolSEPcenter}% default start glue +\edef\@IEEEeqnarraycolSEPdefaultend{\@IEEEeqnarraycolSEPcenter}% default end glue +\edef\@IEEEeqnarraycolSEPdefaultmid{\@IEEEeqnarraycolSEPzero}% default inter-column glue + + + +% creates a vertical rule that extends from the bottom to the top a a cell +% Provided in case other packages redefine \vline some other way. +% usage: \IEEEeqnarrayvrule[rule thickness] +% If no argument is provided, \arrayrulewidth will be used for the rule thickness. +\newcommand\IEEEeqnarrayvrule[1][\arrayrulewidth]{\vrule\@width#1\relax} + +% creates a blank separator row +% usage: \IEEEeqnarrayseprow[separation length][font size commands] +% default is \IEEEeqnarrayseprow[0.25\normalbaselineskip][\relax] +% blank arguments inherit the default values +% uses \skip5 as a scratch register - calls \@IEEEeqnarraystrutsize which uses more scratch registers +\def\IEEEeqnarrayseprow{\relax\@ifnextchar[{\@IEEEeqnarrayseprow}{\@IEEEeqnarrayseprow[0.25\normalbaselineskip]}} +\def\@IEEEeqnarrayseprow[#1]{\relax\@ifnextchar[{\@@IEEEeqnarrayseprow[#1]}{\@@IEEEeqnarrayseprow[#1][\relax]}} +\def\@@IEEEeqnarrayseprow[#1][#2]{\def\@IEEEeqnarrayseprowARGONE{#1}% +\ifx\@IEEEeqnarrayseprowARGONE\@empty% +% get the skip value, based on the font commands +% use skip5 because \IEEEeqnarraystrutsize uses \skip0, \skip2, \skip3 +% assign within a bogus box to confine the font changes +{\setbox0=\hbox{#2\relax\global\skip5=0.25\normalbaselineskip}}% +\else% +{\setbox0=\hbox{#2\relax\global\skip5=#1}}% +\fi% +\@IEEEeqnarrayhoptolastcolumn\IEEEeqnarraystrutsize{\skip5}{0pt}[\relax]\relax} + +% creates a blank separator row, but omits all the column templates +% usage: \IEEEeqnarrayseprowcut[separation length][font size commands] +% default is \IEEEeqnarrayseprowcut[0.25\normalbaselineskip][\relax] +% blank arguments inherit the default values +% uses \skip5 as a scratch register - calls \@IEEEeqnarraystrutsize which uses more scratch registers +\def\IEEEeqnarrayseprowcut{\multispan{\@IEEEeqnnumcols}\relax% span all the cols +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\@ifnextchar[{\@IEEEeqnarrayseprowcut}{\@IEEEeqnarrayseprowcut[0.25\normalbaselineskip]}} +\def\@IEEEeqnarrayseprowcut[#1]{\relax\@ifnextchar[{\@@IEEEeqnarrayseprowcut[#1]}{\@@IEEEeqnarrayseprowcut[#1][\relax]}} +\def\@@IEEEeqnarrayseprowcut[#1][#2]{\def\@IEEEeqnarrayseprowARGONE{#1}% +\ifx\@IEEEeqnarrayseprowARGONE\@empty% +% get the skip value, based on the font commands +% use skip5 because \IEEEeqnarraystrutsize uses \skip0, \skip2, \skip3 +% assign within a bogus box to confine the font changes +{\setbox0=\hbox{#2\relax\global\skip5=0.25\normalbaselineskip}}% +\else% +{\setbox0=\hbox{#2\relax\global\skip5=#1}}% +\fi% +\IEEEeqnarraystrutsize{\skip5}{0pt}[\relax]\relax} + + + +% draws a single rule across all the columns optional +% argument determines the rule width, \arrayrulewidth is the default +% updates column counter as needed and turns off struts +% usage: \IEEEeqnarrayrulerow[rule line thickness] +\def\IEEEeqnarrayrulerow{\multispan{\@IEEEeqnnumcols}\relax% span all the cols +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\@ifnextchar[{\@IEEEeqnarrayrulerow}{\@IEEEeqnarrayrulerow[\arrayrulewidth]}} +\def\@IEEEeqnarrayrulerow[#1]{\leaders\hrule height#1\hfil\relax% put in our rule +% turn off any struts +\IEEEeqnarraystrutsize{0pt}{0pt}[\relax]\relax} + + +% draws a double rule by using a single rule row, a separator row, and then +% another single rule row +% first optional argument determines the rule thicknesses, \arrayrulewidth is the default +% second optional argument determines the rule spacing, \doublerulesep is the default +% usage: \IEEEeqnarraydblrulerow[rule line thickness][rule spacing] +\def\IEEEeqnarraydblrulerow{\multispan{\@IEEEeqnnumcols}\relax% span all the cols +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\@ifnextchar[{\@IEEEeqnarraydblrulerow}{\@IEEEeqnarraydblrulerow[\arrayrulewidth]}} +\def\@IEEEeqnarraydblrulerow[#1]{\relax\@ifnextchar[{\@@IEEEeqnarraydblrulerow[#1]}% +{\@@IEEEeqnarraydblrulerow[#1][\doublerulesep]}} +\def\@@IEEEeqnarraydblrulerow[#1][#2]{\def\@IEEEeqnarraydblrulerowARG{#1}% +% we allow the user to say \IEEEeqnarraydblrulerow[][] +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\@IEEEeqnarrayrulerow[\arrayrulewidth]% +\else% +\@IEEEeqnarrayrulerow[#1]\relax% +\fi% +\def\@IEEEeqnarraydblrulerowARG{#2}% +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\\\IEEEeqnarrayseprow[\doublerulesep][\relax]% +\else% +\\\IEEEeqnarrayseprow[#2][\relax]% +\fi% +\\\multispan{\@IEEEeqnnumcols}% +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\def\@IEEEeqnarraydblrulerowARG{#1}% +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\@IEEEeqnarrayrulerow[\arrayrulewidth]% +\else% +\@IEEEeqnarrayrulerow[#1]% +\fi% +} + +% draws a double rule by using a single rule row, a separator (cutting) row, and then +% another single rule row +% first optional argument determines the rule thicknesses, \arrayrulewidth is the default +% second optional argument determines the rule spacing, \doublerulesep is the default +% usage: \IEEEeqnarraydblrulerow[rule line thickness][rule spacing] +\def\IEEEeqnarraydblrulerowcut{\multispan{\@IEEEeqnnumcols}\relax% span all the cols +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\@ifnextchar[{\@IEEEeqnarraydblrulerowcut}{\@IEEEeqnarraydblrulerowcut[\arrayrulewidth]}} +\def\@IEEEeqnarraydblrulerowcut[#1]{\relax\@ifnextchar[{\@@IEEEeqnarraydblrulerowcut[#1]}% +{\@@IEEEeqnarraydblrulerowcut[#1][\doublerulesep]}} +\def\@@IEEEeqnarraydblrulerowcut[#1][#2]{\def\@IEEEeqnarraydblrulerowARG{#1}% +% we allow the user to say \IEEEeqnarraydblrulerow[][] +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\@IEEEeqnarrayrulerow[\arrayrulewidth]% +\else% +\@IEEEeqnarrayrulerow[#1]% +\fi% +\def\@IEEEeqnarraydblrulerowARG{#2}% +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\\\IEEEeqnarrayseprowcut[\doublerulesep][\relax]% +\else% +\\\IEEEeqnarrayseprowcut[#2][\relax]% +\fi% +\\\multispan{\@IEEEeqnnumcols}% +% advance column counter only if the IEEEeqnarray environment wants it +\if at advanceIEEEeqncolcnt\global\advance\@IEEEeqncolcnt by \@IEEEeqnnumcols\relax\fi% +\def\@IEEEeqnarraydblrulerowARG{#1}% +\ifx\@IEEEeqnarraydblrulerowARG\@empty% +\@IEEEeqnarrayrulerow[\arrayrulewidth]% +\else% +\@IEEEeqnarrayrulerow[#1]% +\fi% +} + + + +% inserts a full row's worth of &'s +% relies on \@IEEEeqnnumcols to provide the correct number of columns +% uses \@IEEEtrantmptoksA, \count0 as scratch registers +\def\@IEEEeqnarrayhoptolastcolumn{\@IEEEtrantmptoksA={}\count0=1\relax% +\loop% add cols if the user did not use them all +\ifnum\count0<\@IEEEeqnnumcols\relax% +\@IEEEappendtoksA{&}% +\advance\count0 by 1\relax% update the col count +\repeat% +\the\@IEEEtrantmptoksA%execute the &'s +} + + + +\newif\if at IEEEeqnarrayISinner % flag to indicate if we are within the lines +\@IEEEeqnarrayISinnerfalse % of an IEEEeqnarray - after the IEEEeqnarraydecl + +\edef\@IEEEeqnarrayTHEstrutheight{0pt} % height and depth of IEEEeqnarray struts +\edef\@IEEEeqnarrayTHEstrutdepth{0pt} + +\edef\@IEEEeqnarrayTHEmasterstrutheight{0pt} % default height and depth of +\edef\@IEEEeqnarrayTHEmasterstrutdepth{0pt} % struts within an IEEEeqnarray + +\edef\@IEEEeqnarrayTHEmasterstrutHSAVE{0pt} % saved master strut height +\edef\@IEEEeqnarrayTHEmasterstrutDSAVE{0pt} % and depth + +\newif\if at IEEEeqnarrayusemasterstrut % flag to indicate that the master strut value +\@IEEEeqnarrayusemasterstruttrue % is to be used + + + +% saves the strut height and depth of the master strut +\def\@IEEEeqnarraymasterstrutsave{\relax% +\expandafter\skip0=\@IEEEeqnarrayTHEmasterstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEmasterstrutdepth\relax% +% remove stretchability +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% save values +\edef\@IEEEeqnarrayTHEmasterstrutHSAVE{\the\dimen0}% +\edef\@IEEEeqnarrayTHEmasterstrutDSAVE{\the\dimen2}} + +% restores the strut height and depth of the master strut +\def\@IEEEeqnarraymasterstrutrestore{\relax% +\expandafter\skip0=\@IEEEeqnarrayTHEmasterstrutHSAVE\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEmasterstrutDSAVE\relax% +% remove stretchability +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% restore values +\edef\@IEEEeqnarrayTHEmasterstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEmasterstrutdepth{\the\dimen2}} + + +% globally restores the strut height and depth to the +% master values and sets the master strut flag to true +\def\@IEEEeqnarraystrutreset{\relax% +\expandafter\skip0=\@IEEEeqnarrayTHEmasterstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEmasterstrutdepth\relax% +% remove stretchability +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% restore values +\xdef\@IEEEeqnarrayTHEstrutheight{\the\dimen0}% +\xdef\@IEEEeqnarrayTHEstrutdepth{\the\dimen2}% +\global\@IEEEeqnarrayusemasterstruttrue} + + +% if the master strut is not to be used, make the current +% values of \@IEEEeqnarrayTHEstrutheight, \@IEEEeqnarrayTHEstrutdepth +% and the use master strut flag, global +% this allows user strut commands issued in the last column to be carried +% into the isolation/strut column +\def\@IEEEeqnarrayglobalizestrutstatus{\relax% +\if at IEEEeqnarrayusemasterstrut\else% +\xdef\@IEEEeqnarrayTHEstrutheight{\@IEEEeqnarrayTHEstrutheight}% +\xdef\@IEEEeqnarrayTHEstrutdepth{\@IEEEeqnarrayTHEstrutdepth}% +\global\@IEEEeqnarrayusemasterstrutfalse% +\fi} + + + +% usage: \IEEEeqnarraystrutsize{height}{depth}[font size commands] +% If called outside the lines of an IEEEeqnarray, sets the height +% and depth of both the master and local struts. If called inside +% an IEEEeqnarray line, sets the height and depth of the local strut +% only and sets the flag to indicate the use of the local strut +% values. If the height or depth is left blank, 0.7\normalbaselineskip +% and 0.3\normalbaselineskip will be used, respectively. +% The optional argument can be used to evaluate the lengths under +% a different font size and styles. If none is specified, the current +% font is used. +% uses scratch registers \skip0, \skip2, \skip3, \dimen0, \dimen2 +\def\IEEEeqnarraystrutsize#1#2{\relax\@ifnextchar[{\@IEEEeqnarraystrutsize{#1}{#2}}{\@IEEEeqnarraystrutsize{#1}{#2}[\relax]}} +\def\@IEEEeqnarraystrutsize#1#2[#3]{\def\@IEEEeqnarraystrutsizeARG{#1}% +\ifx\@IEEEeqnarraystrutsizeARG\@empty% +{\setbox0=\hbox{#3\relax\global\skip3=0.7\normalbaselineskip}}% +\skip0=\skip3\relax% +\else% arg one present +{\setbox0=\hbox{#3\relax\global\skip3=#1\relax}}% +\skip0=\skip3\relax% +\fi% if null arg +\def\@IEEEeqnarraystrutsizeARG{#2}% +\ifx\@IEEEeqnarraystrutsizeARG\@empty% +{\setbox0=\hbox{#3\relax\global\skip3=0.3\normalbaselineskip}}% +\skip2=\skip3\relax% +\else% arg two present +{\setbox0=\hbox{#3\relax\global\skip3=#2\relax}}% +\skip2=\skip3\relax% +\fi% if null arg +% remove stretchability, just to be safe +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% dimen0 = height, dimen2 = depth +\if at IEEEeqnarrayISinner% inner does not touch master strut size +\edef\@IEEEeqnarrayTHEstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEstrutdepth{\the\dimen2}% +\@IEEEeqnarrayusemasterstrutfalse% do not use master +\else% outer, have to set master strut too +\edef\@IEEEeqnarrayTHEmasterstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEmasterstrutdepth{\the\dimen2}% +\edef\@IEEEeqnarrayTHEstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEstrutdepth{\the\dimen2}% +\@IEEEeqnarrayusemasterstruttrue% use master strut +\fi} + + +% usage: \IEEEeqnarraystrutsizeadd{added height}{added depth}[font size commands] +% If called outside the lines of an IEEEeqnarray, adds the given height +% and depth to both the master and local struts. +% If called inside an IEEEeqnarray line, adds the given height and depth +% to the local strut only and sets the flag to indicate the use +% of the local strut values. +% In both cases, if a height or depth is left blank, 0pt is used instead. +% The optional argument can be used to evaluate the lengths under +% a different font size and styles. If none is specified, the current +% font is used. +% uses scratch registers \skip0, \skip2, \skip3, \dimen0, \dimen2 +\def\IEEEeqnarraystrutsizeadd#1#2{\relax\@ifnextchar[{\@IEEEeqnarraystrutsizeadd{#1}{#2}}{\@IEEEeqnarraystrutsizeadd{#1}{#2}[\relax]}} +\def\@IEEEeqnarraystrutsizeadd#1#2[#3]{\def\@IEEEeqnarraystrutsizearg{#1}% +\ifx\@IEEEeqnarraystrutsizearg\@empty% +\skip0=0pt\relax% +\else% arg one present +{\setbox0=\hbox{#3\relax\global\skip3=#1}}% +\skip0=\skip3\relax% +\fi% if null arg +\def\@IEEEeqnarraystrutsizearg{#2}% +\ifx\@IEEEeqnarraystrutsizearg\@empty% +\skip2=0pt\relax% +\else% arg two present +{\setbox0=\hbox{#3\relax\global\skip3=#2}}% +\skip2=\skip3\relax% +\fi% if null arg +% remove stretchability, just to be safe +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% dimen0 = height, dimen2 = depth +\if at IEEEeqnarrayISinner% inner does not touch master strut size +% get local strut size +\expandafter\skip0=\@IEEEeqnarrayTHEstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEstrutdepth\relax% +% add it to the user supplied values +\advance\dimen0 by \skip0\relax% +\advance\dimen2 by \skip2\relax% +% update the local strut size +\edef\@IEEEeqnarrayTHEstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEstrutdepth{\the\dimen2}% +\@IEEEeqnarrayusemasterstrutfalse% do not use master +\else% outer, have to set master strut too +% get master strut size +\expandafter\skip0=\@IEEEeqnarrayTHEmasterstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEmasterstrutdepth\relax% +% add it to the user supplied values +\advance\dimen0 by \skip0\relax% +\advance\dimen2 by \skip2\relax% +% update the local and master strut sizes +\edef\@IEEEeqnarrayTHEmasterstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEmasterstrutdepth{\the\dimen2}% +\edef\@IEEEeqnarrayTHEstrutheight{\the\dimen0}% +\edef\@IEEEeqnarrayTHEstrutdepth{\the\dimen2}% +\@IEEEeqnarrayusemasterstruttrue% use master strut +\fi} + + +% allow user a way to see the struts +\newif\ifIEEEvisiblestruts +\IEEEvisiblestrutsfalse + +% inserts an invisible strut using the master or local strut values +% uses scratch registers \skip0, \skip2, \dimen0, \dimen2 +\def\@IEEEeqnarrayinsertstrut{\relax% +\if at IEEEeqnarrayusemasterstrut +% get master strut size +\expandafter\skip0=\@IEEEeqnarrayTHEmasterstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEmasterstrutdepth\relax% +\else% +% get local strut size +\expandafter\skip0=\@IEEEeqnarrayTHEstrutheight\relax% +\expandafter\skip2=\@IEEEeqnarrayTHEstrutdepth\relax% +\fi% +% remove stretchability, probably not needed +\dimen0\skip0\relax% +\dimen2\skip2\relax% +% dimen0 = height, dimen2 = depth +% allow user to see struts if desired +\ifIEEEvisiblestruts% +\vrule width0.2pt height\dimen0 depth\dimen2\relax% +\else% +\vrule width0pt height\dimen0 depth\dimen2\relax\fi} + + +% creates an invisible strut, useable even outside \IEEEeqnarray +% if \IEEEvisiblestrutstrue, the strut will be visible and 0.2pt wide. +% usage: \IEEEstrut[height][depth][font size commands] +% default is \IEEEstrut[0.7\normalbaselineskip][0.3\normalbaselineskip][\relax] +% blank arguments inherit the default values +% uses \dimen0, \dimen2, \skip0, \skip2 +\def\IEEEstrut{\relax\@ifnextchar[{\@IEEEstrut}{\@IEEEstrut[0.7\normalbaselineskip]}} +\def\@IEEEstrut[#1]{\relax\@ifnextchar[{\@@IEEEstrut[#1]}{\@@IEEEstrut[#1][0.3\normalbaselineskip]}} +\def\@@IEEEstrut[#1][#2]{\relax\@ifnextchar[{\@@@IEEEstrut[#1][#2]}{\@@@IEEEstrut[#1][#2][\relax]}} +\def\@@@IEEEstrut[#1][#2][#3]{\mbox{#3\relax% +\def\@IEEEstrutARG{#1}% +\ifx\@IEEEstrutARG\@empty% +\skip0=0.7\normalbaselineskip\relax% +\else% +\skip0=#1\relax% +\fi% +\def\@IEEEstrutARG{#2}% +\ifx\@IEEEstrutARG\@empty% +\skip2=0.3\normalbaselineskip\relax% +\else% +\skip2=#2\relax% +\fi% +% remove stretchability, probably not needed +\dimen0\skip0\relax% +\dimen2\skip2\relax% +\ifIEEEvisiblestruts% +\vrule width0.2pt height\dimen0 depth\dimen2\relax% +\else% +\vrule width0.0pt height\dimen0 depth\dimen2\relax\fi}} + + +% enables strut mode by setting a default strut size and then zeroing the +% \baselineskip, \lineskip, \lineskiplimit and \jot +\def\IEEEeqnarraystrutmode{\IEEEeqnarraystrutsize{0.7\normalbaselineskip}{0.3\normalbaselineskip}[\relax]% +\baselineskip=0pt\lineskip=0pt\lineskiplimit=0pt\jot=0pt} + + + +\def\IEEEeqnarray{\@IEEEeqnarraystarformfalse\@IEEEeqnarray} +\def\endIEEEeqnarray{\end at IEEEeqnarray} + +\@namedef{IEEEeqnarray*}{\@IEEEeqnarraystarformtrue\@IEEEeqnarray} +\@namedef{endIEEEeqnarray*}{\end at IEEEeqnarray} + + +% \IEEEeqnarray is an enhanced \eqnarray. +% The star form defaults to not putting equation numbers at the end of each row. +% usage: \IEEEeqnarray[decl]{cols} +\def\@IEEEeqnarray{\relax\@ifnextchar[{\@@IEEEeqnarray}{\@@IEEEeqnarray[\relax]}} +\def\@@IEEEeqnarray[#1]#2{% + % default to showing the equation number or not based on whether or not + % the star form was involked + \if at IEEEeqnarraystarform\global\@eqnswfalse + \else% not the star form + \global\@eqnswtrue + \fi% if star form + \@IEEEissubequationfalse% default to no subequations + \@IEEElastlinewassubequationfalse% assume last line is not a sub equation + \@IEEEeqnarrayISinnerfalse% not yet within the lines of the halign + \@IEEEeqnarraystrutsize{0pt}{0pt}[\relax]% turn off struts by default + \@IEEEeqnarrayusemasterstruttrue% use master strut till user asks otherwise + \IEEEvisiblestrutsfalse% diagnostic mode defaults to off + % no extra space unless the user specifically requests it + \lineskip=0pt\relax + \lineskiplimit=0pt\relax + \baselineskip=\normalbaselineskip\relax% + \jot=\IEEEnormaljot\relax% + \mathsurround\z@\relax% no extra spacing around math + \@advanceIEEEeqncolcnttrue% advance the col counter for each col the user uses, + % used in \IEEEeqnarraymulticol and in the preamble build + \stepcounter{equation}% advance equation counter before first line + \setcounter{IEEEsubequation}{0}% no subequation yet + \def\@currentlabel{\p at equation\theequation}% redefine the ref label + \IEEEeqnarraydecl\relax% allow a way for the user to make global overrides + #1\relax% allow user to override defaults + \let\\\@IEEEeqnarraycr% replace newline with one that can put in eqn. numbers + \global\@IEEEeqncolcnt\z@% col. count = 0 for first line + \@IEEEbuildpreamble #2\end\relax% build the preamble and put it into \@IEEEtrantmptoksA + % put in the column for the equation number + \ifnum\@IEEEeqnnumcols>0\relax\@IEEEappendtoksA{&}\fi% col separator for those after the first + \toks0={##}% + % advance the \@IEEEeqncolcnt for the isolation col, this helps with error checking + \@IEEEappendtoksA{\global\advance\@IEEEeqncolcnt by 1\relax}% + % add the isolation column + \@IEEEappendtoksA{\tabskip\z at skip\bgroup\the\toks0\egroup}% + % advance the \@IEEEeqncolcnt for the equation number col, this helps with error checking + \@IEEEappendtoksA{&\global\advance\@IEEEeqncolcnt by 1\relax}% + % add the equation number col to the preamble + \@IEEEappendtoksA{\tabskip\z at skip\hb at xt@\z@\bgroup\hss\the\toks0\egroup}% + % note \@IEEEeqnnumcols does not count the equation col or isolation col + % set the starting tabskip glue as determined by the preamble build + \tabskip=\@IEEEBPstartglue\relax + % begin the display alignment + \@IEEEeqnarrayISinnertrue% commands are now within the lines + $$\everycr{}\halign to\displaywidth\bgroup + % "exspand" the preamble + \span\the\@IEEEtrantmptoksA\cr} + +% enter isolation/strut column (or the next column if the user did not use +% every column), record the strut status, complete the columns, do the strut if needed, +% restore counters to correct values and exit +\def\end at IEEEeqnarray{\@IEEEeqnarrayglobalizestrutstatus&\@@IEEEeqnarraycr\egroup% +\if at IEEElastlinewassubequation\global\advance\c at IEEEsubequation\m at ne\fi% +\global\advance\c at equation\m at ne% +$$\@ignoretrue} + +% need a way to remember if last line is a subequation +\newif\if at IEEElastlinewassubequation% +\@IEEElastlinewassubequationfalse + +% IEEEeqnarray uses a modifed \\ instead of the plain \cr to +% end rows. This allows for things like \\*[vskip amount] +% This "cr" macros are modified versions those for LaTeX2e's eqnarray +% the {\ifnum0=`} braces must be kept away from the last column to avoid +% altering spacing of its math, so we use & to advance to the next column +% as there is an isolation/strut column after the user's columns +\def\@IEEEeqnarraycr{\@IEEEeqnarrayglobalizestrutstatus&% save strut status and advance to next column + {\ifnum0=`}\fi + \@ifstar{% + \global\@eqpen\@M\@IEEEeqnarrayYCR + }{% + \global\@eqpen\interdisplaylinepenalty \@IEEEeqnarrayYCR + }% +} + +\def\@IEEEeqnarrayYCR{\@testopt\@IEEEeqnarrayXCR\z at skip} + +\def\@IEEEeqnarrayXCR[#1]{% + \ifnum0=`{\fi}% + \@@IEEEeqnarraycr + \noalign{\penalty\@eqpen\vskip\jot\vskip #1\relax}}% + +\def\@@IEEEeqnarraycr{\@IEEEtrantmptoksA={}% clear token register + \advance\@IEEEeqncolcnt by -1\relax% adjust col count because of the isolation column + \ifnum\@IEEEeqncolcnt>\@IEEEeqnnumcols\relax + \@IEEEclspkgerror{Too many columns within the IEEEeqnarray\MessageBreak + environment}% + {Use fewer \string &'s or put more columns in the IEEEeqnarry column\MessageBreak + specifications.}\relax% + \else + \loop% add cols if the user did not use them all + \ifnum\@IEEEeqncolcnt<\@IEEEeqnnumcols\relax + \@IEEEappendtoksA{&}% + \advance\@IEEEeqncolcnt by 1\relax% update the col count + \repeat + % this number of &'s will take us the the isolation column + \fi + % execute the &'s + \the\@IEEEtrantmptoksA% + % handle the strut/isolation column + \@IEEEeqnarrayinsertstrut% do the strut if needed + \@IEEEeqnarraystrutreset% reset the strut system for next line or IEEEeqnarray + &% and enter the equation number column + % is this line needs an equation number, display it and advance the + % (sub)equation counters, record what type this line was + \if at eqnsw% + \if at IEEEissubequation\theIEEEsubequationdis\addtocounter{equation}{1}\stepcounter{IEEEsubequation}% + \global\@IEEElastlinewassubequationtrue% + \else% display a standard equation number, initialize the IEEEsubequation counter + \theequationdis\stepcounter{equation}\setcounter{IEEEsubequation}{0}% + \global\@IEEElastlinewassubequationfalse\fi% + \fi% + % reset the eqnsw flag to indicate default preference of the display of equation numbers + \if at IEEEeqnarraystarform\global\@eqnswfalse\else\global\@eqnswtrue\fi + \global\@IEEEissubequationfalse% reset the subequation flag + % reset the number of columns the user actually used + \global\@IEEEeqncolcnt\z@\relax + % the real end of the line + \cr} + + + + + +% \IEEEeqnarraybox is like \IEEEeqnarray except the box form puts everything +% inside a vtop, vbox, or vcenter box depending on the letter in the second +% optional argument (t,b,c). Vbox is the default. Unlike \IEEEeqnarray, +% equation numbers are not displayed and \IEEEeqnarraybox can be nested. +% \IEEEeqnarrayboxm is for math mode (like \array) and does not put the vbox +% within an hbox. +% \IEEEeqnarrayboxt is for text mode (like \tabular) and puts the vbox within +% a \hbox{$ $} construct. +% \IEEEeqnarraybox will auto detect whether to use \IEEEeqnarrayboxm or +% \IEEEeqnarrayboxt depending on the math mode. +% The third optional argument specifies the width this box is to be set to - +% natural width is the default. +% The * forms do not add \jot line spacing +% usage: \IEEEeqnarraybox[decl][pos][width]{cols} +\def\IEEEeqnarrayboxm{\@IEEEeqnarraystarformfalse\@IEEEeqnarrayboxHBOXSWfalse\@IEEEeqnarraybox} +\def\endIEEEeqnarrayboxm{\end at IEEEeqnarraybox} +\@namedef{IEEEeqnarrayboxm*}{\@IEEEeqnarraystarformtrue\@IEEEeqnarrayboxHBOXSWfalse\@IEEEeqnarraybox} +\@namedef{endIEEEeqnarrayboxm*}{\end at IEEEeqnarraybox} + +\def\IEEEeqnarrayboxt{\@IEEEeqnarraystarformfalse\@IEEEeqnarrayboxHBOXSWtrue\@IEEEeqnarraybox} +\def\endIEEEeqnarrayboxt{\end at IEEEeqnarraybox} +\@namedef{IEEEeqnarrayboxt*}{\@IEEEeqnarraystarformtrue\@IEEEeqnarrayboxHBOXSWtrue\@IEEEeqnarraybox} +\@namedef{endIEEEeqnarrayboxt*}{\end at IEEEeqnarraybox} + +\def\IEEEeqnarraybox{\@IEEEeqnarraystarformfalse\ifmmode\@IEEEeqnarrayboxHBOXSWfalse\else\@IEEEeqnarrayboxHBOXSWtrue\fi% +\@IEEEeqnarraybox} +\def\endIEEEeqnarraybox{\end at IEEEeqnarraybox} + +\@namedef{IEEEeqnarraybox*}{\@IEEEeqnarraystarformtrue\ifmmode\@IEEEeqnarrayboxHBOXSWfalse\else\@IEEEeqnarrayboxHBOXSWtrue\fi% +\@IEEEeqnarraybox} +\@namedef{endIEEEeqnarraybox*}{\end at IEEEeqnarraybox} + +% flag to indicate if the \IEEEeqnarraybox needs to put things into an hbox{$ $} +% for \vcenter in non-math mode +\newif\if at IEEEeqnarrayboxHBOXSW% +\@IEEEeqnarrayboxHBOXSWfalse + +\def\@IEEEeqnarraybox{\relax\@ifnextchar[{\@@IEEEeqnarraybox}{\@@IEEEeqnarraybox[\relax]}} +\def\@@IEEEeqnarraybox[#1]{\relax\@ifnextchar[{\@@@IEEEeqnarraybox[#1]}{\@@@IEEEeqnarraybox[#1][b]}} +\def\@@@IEEEeqnarraybox[#1][#2]{\relax\@ifnextchar[{\@@@@IEEEeqnarraybox[#1][#2]}{\@@@@IEEEeqnarraybox[#1][#2][\relax]}} + +% #1 = decl; #2 = t,b,c; #3 = width, #4 = col specs +\def\@@@@IEEEeqnarraybox[#1][#2][#3]#4{\@IEEEeqnarrayISinnerfalse % not yet within the lines of the halign + \@IEEEeqnarraymasterstrutsave% save current master strut values + \@IEEEeqnarraystrutsize{0pt}{0pt}[\relax]% turn off struts by default + \@IEEEeqnarrayusemasterstruttrue% use master strut till user asks otherwise + \IEEEvisiblestrutsfalse% diagnostic mode defaults to off + % no extra space unless the user specifically requests it + \lineskip=0pt\relax% + \lineskiplimit=0pt\relax% + \baselineskip=\normalbaselineskip\relax% + \jot=\IEEEnormaljot\relax% + \mathsurround\z@\relax% no extra spacing around math + % the default end glues are zero for an \IEEEeqnarraybox + \edef\@IEEEeqnarraycolSEPdefaultstart{\@IEEEeqnarraycolSEPzero}% default start glue + \edef\@IEEEeqnarraycolSEPdefaultend{\@IEEEeqnarraycolSEPzero}% default end glue + \edef\@IEEEeqnarraycolSEPdefaultmid{\@IEEEeqnarraycolSEPzero}% default inter-column glue + \@advanceIEEEeqncolcntfalse% do not advance the col counter for each col the user uses, + % used in \IEEEeqnarraymulticol and in the preamble build + \IEEEeqnarrayboxdecl\relax% allow a way for the user to make global overrides + #1\relax% allow user to override defaults + \let\\\@IEEEeqnarrayboxcr% replace newline with one that allows optional spacing + \@IEEEbuildpreamble #4\end\relax% build the preamble and put it into \@IEEEtrantmptoksA + % add an isolation column to the preamble to stop \\'s {} from getting into the last col + \ifnum\@IEEEeqnnumcols>0\relax\@IEEEappendtoksA{&}\fi% col separator for those after the first + \toks0={##}% + % add the isolation column to the preamble + \@IEEEappendtoksA{\tabskip\z at skip\bgroup\the\toks0\egroup}% + % set the starting tabskip glue as determined by the preamble build + \tabskip=\@IEEEBPstartglue\relax + % begin the alignment + \everycr{}% + % use only the very first token to determine the positioning + % this stops some problems when the user uses more than one letter, + % but is probably not worth the effort + % \noindent is used as a delimiter + \def\@IEEEgrabfirstoken##1##2\noindent{\let\@IEEEgrabbedfirstoken=##1}% + \@IEEEgrabfirstoken#2\relax\relax\noindent + % \@IEEEgrabbedfirstoken has the first token, the rest are discarded + % if we need to put things into and hbox and go into math mode, do so now + \if at IEEEeqnarrayboxHBOXSW \leavevmode \hbox \bgroup $\fi% + % use the appropriate vbox type + \if\@IEEEgrabbedfirstoken t\relax\vtop\else\if\@IEEEgrabbedfirstoken c\relax% + \vcenter\else\vbox\fi\fi\bgroup% + \@IEEEeqnarrayISinnertrue% commands are now within the lines + \ifx#3\relax\halign\else\halign to #3\relax\fi% + \bgroup + % "exspand" the preamble + \span\the\@IEEEtrantmptoksA\cr} + +% carry strut status and enter the isolation/strut column, +% exit from math mode if needed, and exit +\def\end at IEEEeqnarraybox{\@IEEEeqnarrayglobalizestrutstatus% carry strut status +&% enter isolation/strut column +\@IEEEeqnarrayinsertstrut% do strut if needed +\@IEEEeqnarraymasterstrutrestore% restore the previous master strut values +% reset the strut system for next IEEEeqnarray +% (sets local strut values back to previous master strut values) +\@IEEEeqnarraystrutreset% +% ensure last line, exit from halign, close vbox +\crcr\egroup\egroup% +% exit from math mode and close hbox if needed +\if at IEEEeqnarrayboxHBOXSW $\egroup\fi} + + + +% IEEEeqnarraybox uses a modifed \\ instead of the plain \cr to +% end rows. This allows for things like \\[vskip amount] +% This "cr" macros are modified versions those for LaTeX2e's eqnarray +% For IEEEeqnarraybox, \\* is the same as \\ +% the {\ifnum0=`} braces must be kept away from the last column to avoid +% altering spacing of its math, so we use & to advance to the isolation/strut column +% carry strut status into isolation/strut column +\def\@IEEEeqnarrayboxcr{\@IEEEeqnarrayglobalizestrutstatus% carry strut status +&% enter isolation/strut column +\@IEEEeqnarrayinsertstrut% do strut if needed +% reset the strut system for next line or IEEEeqnarray +\@IEEEeqnarraystrutreset% +{\ifnum0=`}\fi% +\@ifstar{\@IEEEeqnarrayboxYCR}{\@IEEEeqnarrayboxYCR}} + +% test and setup the optional argument to \\[] +\def\@IEEEeqnarrayboxYCR{\@testopt\@IEEEeqnarrayboxXCR\z at skip} + +% IEEEeqnarraybox does not automatically increase line spacing by \jot +\def\@IEEEeqnarrayboxXCR[#1]{\ifnum0=`{\fi}% +\cr\noalign{\if at IEEEeqnarraystarform\else\vskip\jot\fi\vskip#1\relax}} + + + +% starts the halign preamble build +\def\@IEEEbuildpreamble{\@IEEEtrantmptoksA={}% clear token register +\let\@IEEEBPcurtype=u%current column type is not yet known +\let\@IEEEBPprevtype=s%the previous column type was the start +\let\@IEEEBPnexttype=u%next column type is not yet known +% ensure these are valid +\def\@IEEEBPcurglue={0pt plus 0pt minus 0pt}% +\def\@IEEEBPcurcolname{@IEEEdefault}% name of current column definition +% currently acquired numerically referenced glue +% use a name that is easier to remember +\let\@IEEEBPcurnum=\@IEEEtrantmpcountA% +\@IEEEBPcurnum=0% +% tracks number of columns in the preamble +\@IEEEeqnnumcols=0% +% record the default end glues +\edef\@IEEEBPstartglue{\@IEEEeqnarraycolSEPdefaultstart}% +\edef\@IEEEBPendglue{\@IEEEeqnarraycolSEPdefaultend}% +% now parse the user's column specifications +\@@IEEEbuildpreamble} + + +% parses and builds the halign preamble +\def\@@IEEEbuildpreamble#1#2{\let\@@nextIEEEbuildpreamble=\@@IEEEbuildpreamble% +% use only the very first token to check the end +% \noindent is used as a delimiter as \end can be present here +\def\@IEEEgrabfirstoken##1##2\noindent{\let\@IEEEgrabbedfirstoken=##1}% +\@IEEEgrabfirstoken#1\relax\relax\noindent +\ifx\@IEEEgrabbedfirstoken\end\let\@@nextIEEEbuildpreamble=\@@IEEEfinishpreamble\else% +% identify current and next token type +\@IEEEgetcoltype{#1}{\@IEEEBPcurtype}{1}% current, error on invalid +\@IEEEgetcoltype{#2}{\@IEEEBPnexttype}{0}% next, no error on invalid next +% if curtype is a glue, get the glue def +\if\@IEEEBPcurtype g\@IEEEgetcurglue{#1}{\@IEEEBPcurglue}\fi% +% if curtype is a column, get the column def and set the current column name +\if\@IEEEBPcurtype c\@IEEEgetcurcol{#1}\fi% +% if curtype is a numeral, acquire the user defined glue +\if\@IEEEBPcurtype n\@IEEEprocessNcol{#1}\fi% +% process the acquired glue +\if\@IEEEBPcurtype g\@IEEEprocessGcol\fi% +% process the acquired col +\if\@IEEEBPcurtype c\@IEEEprocessCcol\fi% +% ready prevtype for next col spec. +\let\@IEEEBPprevtype=\@IEEEBPcurtype% +% be sure and put back the future token(s) as a group +\fi\@@nextIEEEbuildpreamble{#2}} + + +% executed just after preamble build is completed +% warn about zero cols, and if prevtype type = u, put in end tabskip glue +\def\@@IEEEfinishpreamble#1{\ifnum\@IEEEeqnnumcols<1\relax +\@IEEEclspkgerror{No column specifiers declared for IEEEeqnarray}% +{At least one column type must be declared for each IEEEeqnarray.}% +\fi%num cols less than 1 +%if last type undefined, set default end tabskip glue +\if\@IEEEBPprevtype u\@IEEEappendtoksA{\tabskip=\@IEEEBPendglue}\fi} + + +% Identify and return the column specifier's type code +\def\@IEEEgetcoltype#1#2#3{% +% use only the very first token to determine the type +% \noindent is used as a delimiter as \end can be present here +\def\@IEEEgrabfirstoken##1##2\noindent{\let\@IEEEgrabbedfirstoken=##1}% +\@IEEEgrabfirstoken#1\relax\relax\noindent +% \@IEEEgrabfirstoken has the first token, the rest are discarded +% n = number +% g = glue (any other char in catagory 12) +% c = letter +% e = \end +% u = undefined +% third argument: 0 = no error message, 1 = error on invalid char +\let#2=u\relax% assume invalid until know otherwise +\ifx\@IEEEgrabbedfirstoken\end\let#2=e\else +\ifcat\@IEEEgrabbedfirstoken\relax\else% screen out control sequences +\if0\@IEEEgrabbedfirstoken\let#2=n\else +\if1\@IEEEgrabbedfirstoken\let#2=n\else +\if2\@IEEEgrabbedfirstoken\let#2=n\else +\if3\@IEEEgrabbedfirstoken\let#2=n\else +\if4\@IEEEgrabbedfirstoken\let#2=n\else +\if5\@IEEEgrabbedfirstoken\let#2=n\else +\if6\@IEEEgrabbedfirstoken\let#2=n\else +\if7\@IEEEgrabbedfirstoken\let#2=n\else +\if8\@IEEEgrabbedfirstoken\let#2=n\else +\if9\@IEEEgrabbedfirstoken\let#2=n\else +\ifcat,\@IEEEgrabbedfirstoken\let#2=g\relax +\else\ifcat a\@IEEEgrabbedfirstoken\let#2=c\relax\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi +\if#2u\relax +\if0\noexpand#3\relax\else\@IEEEclspkgerror{Invalid character in column specifications}% +{Only letters, numerals and certain other symbols are allowed \MessageBreak +as IEEEeqnarray column specifiers.}\fi\fi} + + +% identify the current letter referenced column +% if invalid, use a default column +\def\@IEEEgetcurcol#1{\expandafter\ifx\csname @IEEEeqnarraycolDEF#1\endcsname\@IEEEeqnarraycolisdefined% +\def\@IEEEBPcurcolname{#1}\else% invalid column name +\@IEEEclspkgerror{Invalid column type "#1" in column specifications.\MessageBreak +Using a default centering column instead}% +{You must define IEEEeqnarray column types before use.}% +\def\@IEEEBPcurcolname{@IEEEdefault}\fi} + + +% identify and return the predefined (punctuation) glue value +\def\@IEEEgetcurglue#1#2{% +% ! = \! (neg small) -0.16667em (-3/18 em) +% , = \, (small) 0.16667em ( 3/18 em) +% : = \: (med) 0.22222em ( 4/18 em) +% ; = \; (large) 0.27778em ( 5/18 em) +% ' = \quad 1em +% " = \qquad 2em +% . = 0.5\arraycolsep +% / = \arraycolsep +% ? = 2\arraycolsep +% * = 1fil +% + = \@IEEEeqnarraycolSEPcenter +% - = \@IEEEeqnarraycolSEPzero +% Note that all em values are referenced to the math font (textfont2) fontdimen6 +% value for 1em. +% +% use only the very first token to determine the type +% this prevents errant tokens from getting in the main text +% \noindent is used as a delimiter here +\def\@IEEEgrabfirstoken##1##2\noindent{\let\@IEEEgrabbedfirstoken=##1}% +\@IEEEgrabfirstoken#1\relax\relax\noindent +% get the math font 1em value +% LaTeX2e's NFSS2 does not preload the fonts, but \IEEEeqnarray needs +% to gain access to the math (\textfont2) font's spacing parameters. +% So we create a bogus box here that uses the math font to ensure +% that \textfont2 is loaded and ready. If this is not done, +% the \textfont2 stuff here may not work. +% Thanks to Bernd Raichle for his 1997 post on this topic. +{\setbox0=\hbox{$\displaystyle\relax$}}% +% fontdimen6 has the width of 1em (a quad). +\@IEEEtrantmpdimenA=\fontdimen6\textfont2\relax% +% identify the glue value based on the first token +% we discard anything after the first +\if!\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=-0.16667\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if,\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=0.16667\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if:\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=0.22222\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if;\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=0.27778\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if'\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=1\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if"\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=2\@IEEEtrantmpdimenA\edef#2{\the\@IEEEtrantmpdimenA}\else +\if.\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=0.5\arraycolsep\edef#2{\the\@IEEEtrantmpdimenA}\else +\if/\@IEEEgrabbedfirstoken\edef#2{\the\arraycolsep}\else +\if?\@IEEEgrabbedfirstoken\@IEEEtrantmpdimenA=2\arraycolsep\edef#2{\the\@IEEEtrantmpdimenA}\else +\if *\@IEEEgrabbedfirstoken\edef#2{0pt plus 1fil minus 0pt}\else +\if+\@IEEEgrabbedfirstoken\edef#2{\@IEEEeqnarraycolSEPcenter}\else +\if-\@IEEEgrabbedfirstoken\edef#2{\@IEEEeqnarraycolSEPzero}\else +\edef#2{\@IEEEeqnarraycolSEPzero}% +\@IEEEclspkgerror{Invalid predefined inter-column glue type "#1" in\MessageBreak +column specifications. Using a default value of\MessageBreak +0pt instead}% +{Only !,:;'"./?*+ and - are valid predefined glue types in the\MessageBreak +IEEEeqnarray column specifications.}\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi\fi} + + + +% process a numerical digit from the column specification +% and look up the corresponding user defined glue value +% can transform current type from n to g or a as the user defined glue is acquired +\def\@IEEEprocessNcol#1{\if\@IEEEBPprevtype g% +\@IEEEclspkgerror{Back-to-back inter-column glue specifiers in column\MessageBreak +specifications. Ignoring consecutive glue specifiers\MessageBreak +after the first}% +{You cannot have two or more glue types next to each other\MessageBreak +in the IEEEeqnarray column specifications.}% +\let\@IEEEBPcurtype=a% abort this glue, future digits will be discarded +\@IEEEBPcurnum=0\relax% +\else% if we previously aborted a glue +\if\@IEEEBPprevtype a\@IEEEBPcurnum=0\let\@IEEEBPcurtype=a%maintain digit abortion +\else%acquire this number +% save the previous type before the numerical digits started +\if\@IEEEBPprevtype n\else\let\@IEEEBPprevsavedtype=\@IEEEBPprevtype\fi% +\multiply\@IEEEBPcurnum by 10\relax% +\advance\@IEEEBPcurnum by #1\relax% add in number, \relax is needed to stop TeX's number scan +\if\@IEEEBPnexttype n\else%close acquisition +\expandafter\ifx\csname @IEEEeqnarraycolSEPDEF\expandafter\romannumeral\number\@IEEEBPcurnum\endcsname\@IEEEeqnarraycolisdefined% +\edef\@IEEEBPcurglue{\csname @IEEEeqnarraycolSEP\expandafter\romannumeral\number\@IEEEBPcurnum\endcsname}% +\else%user glue not defined +\@IEEEclspkgerror{Invalid user defined inter-column glue type "\number\@IEEEBPcurnum" in\MessageBreak +column specifications. Using a default value of\MessageBreak +0pt instead}% +{You must define all IEEEeqnarray numerical inter-column glue types via\MessageBreak +\string\IEEEeqnarraydefcolsep \space before they are used in column specifications.}% +\edef\@IEEEBPcurglue{\@IEEEeqnarraycolSEPzero}% +\fi% glue defined or not +\let\@IEEEBPcurtype=g% change the type to reflect the acquired glue +\let\@IEEEBPprevtype=\@IEEEBPprevsavedtype% restore the prev type before this number glue +\@IEEEBPcurnum=0\relax%ready for next acquisition +\fi%close acquisition, get glue +\fi%discard or acquire number +\fi%prevtype glue or not +} + + +% process an acquired glue +% add any acquired column/glue pair to the preamble +\def\@IEEEprocessGcol{\if\@IEEEBPprevtype a\let\@IEEEBPcurtype=a%maintain previous glue abortions +\else +% if this is the start glue, save it, but do nothing else +% as this is not used in the preamble, but before +\if\@IEEEBPprevtype s\edef\@IEEEBPstartglue{\@IEEEBPcurglue}% +\else%not the start glue +\if\@IEEEBPprevtype g%ignore if back to back glues +\@IEEEclspkgerror{Back-to-back inter-column glue specifiers in column\MessageBreak +specifications. Ignoring consecutive glue specifiers\MessageBreak +after the first}% +{You cannot have two or more glue types next to each other\MessageBreak +in the IEEEeqnarray column specifications.}% +\let\@IEEEBPcurtype=a% abort this glue +\else% not a back to back glue +\if\@IEEEBPprevtype c\relax% if the previoustype was a col, add column/glue pair to preamble +\ifnum\@IEEEeqnnumcols>0\relax\@IEEEappendtoksA{&}\fi +\toks0={##}% +% make preamble advance col counter if this environment needs this +\if at advanceIEEEeqncolcnt\@IEEEappendtoksA{\global\advance\@IEEEeqncolcnt by 1\relax}\fi +% insert the column defintion into the preamble, being careful not to expand +% the column definition +\@IEEEappendtoksA{\tabskip=\@IEEEBPcurglue}% +\@IEEEappendNOEXPANDtoksA{\begingroup\csname @IEEEeqnarraycolPRE}% +\@IEEEappendtoksA{\@IEEEBPcurcolname}% +\@IEEEappendNOEXPANDtoksA{\endcsname}% +\@IEEEappendtoksA{\the\toks0}% +\@IEEEappendNOEXPANDtoksA{\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\csname @IEEEeqnarraycolPOST}% +\@IEEEappendtoksA{\@IEEEBPcurcolname}% +\@IEEEappendNOEXPANDtoksA{\endcsname\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\endgroup}% +\advance\@IEEEeqnnumcols by 1\relax%one more column in the preamble +\else% error: non-start glue with no pending column +\@IEEEclspkgerror{Inter-column glue specifier without a prior column\MessageBreak +type in the column specifications. Ignoring this glue\MessageBreak +specifier}% +{Except for the first and last positions, glue can be placed only\MessageBreak +between column types.}% +\let\@IEEEBPcurtype=a% abort this glue +\fi% previous was a column +\fi% back-to-back glues +\fi% is start column glue +\fi% prev type not a +} + + +% process an acquired letter referenced column and, if necessary, add it to the preamble +\def\@IEEEprocessCcol{\if\@IEEEBPnexttype g\else +\if\@IEEEBPnexttype n\else +% we have a column followed by something other than a glue (or numeral glue) +% so we must add this column to the preamble now +\ifnum\@IEEEeqnnumcols>0\relax\@IEEEappendtoksA{&}\fi%col separator for those after the first +\if\@IEEEBPnexttype e\@IEEEappendtoksA{\tabskip=\@IEEEBPendglue\relax}\else%put in end glue +\@IEEEappendtoksA{\tabskip=\@IEEEeqnarraycolSEPdefaultmid\relax}\fi% or default mid glue +\toks0={##}% +% make preamble advance col counter if this environment needs this +\if at advanceIEEEeqncolcnt\@IEEEappendtoksA{\global\advance\@IEEEeqncolcnt by 1\relax}\fi +% insert the column definition into the preamble, being careful not to expand +% the column definition +\@IEEEappendNOEXPANDtoksA{\begingroup\csname @IEEEeqnarraycolPRE}% +\@IEEEappendtoksA{\@IEEEBPcurcolname}% +\@IEEEappendNOEXPANDtoksA{\endcsname}% +\@IEEEappendtoksA{\the\toks0}% +\@IEEEappendNOEXPANDtoksA{\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\csname @IEEEeqnarraycolPOST}% +\@IEEEappendtoksA{\@IEEEBPcurcolname}% +\@IEEEappendNOEXPANDtoksA{\endcsname\relax\relax\relax\relax\relax% +\relax\relax\relax\relax\relax\endgroup}% +\advance\@IEEEeqnnumcols by 1\relax%one more column in the preamble +\fi%next type not numeral +\fi%next type not glue +} + + +%% +%% END OF IEEEeqnarry DEFINITIONS +%% + + + + +% set up the running headings, this complex because of all the different +% modes IEEEtran supports +\if at twoside + \ifCLASSOPTIONtechnote + \def\ps at headings{% + \def\@oddhead{\hbox{}\scriptsize\leftmark \hfil \thepage} + \def\@evenhead{\scriptsize\thepage \hfil \leftmark\hbox{}} + \ifCLASSOPTIONdraftcls + \ifCLASSOPTIONdraftclsnofoot + \def\@oddfoot{}\def\@evenfoot{}% + \else + \def\@oddfoot{\scriptsize\@date\hfil DRAFT} + \def\@evenfoot{\scriptsize DRAFT\hfil\@date} + \fi + \else + \def\@oddfoot{}\def\@evenfoot{} + \fi} + \else % not a technote + \def\ps at headings{% + \ifCLASSOPTIONconference + \def\@oddhead{} + \def\@evenhead{} + \else + \def\@oddhead{\hbox{}\scriptsize\rightmark \hfil \thepage} + \def\@evenhead{\scriptsize\thepage \hfil \leftmark\hbox{}} + \fi + \ifCLASSOPTIONdraftcls + \def\@oddhead{\hbox{}\scriptsize\rightmark \hfil \thepage} + \def\@evenhead{\scriptsize\thepage \hfil \leftmark\hbox{}} + \ifCLASSOPTIONdraftclsnofoot + \def\@oddfoot{}\def\@evenfoot{}% + \else + \def\@oddfoot{\scriptsize\@date\hfil DRAFT} + \def\@evenfoot{\scriptsize DRAFT\hfil\@date} + \fi + \else + \def\@oddfoot{}\def\@evenfoot{}% + \fi} + \fi +\else % single side +\def\ps at headings{% + \ifCLASSOPTIONconference + \def\@oddhead{} + \def\@evenhead{} + \else + \def\@oddhead{\hbox{}\scriptsize\leftmark \hfil \thepage} + \def\@evenhead{} + \fi + \ifCLASSOPTIONdraftcls + \def\@oddhead{\hbox{}\scriptsize\leftmark \hfil \thepage} + \def\@evenhead{} + \ifCLASSOPTIONdraftclsnofoot + \def\@oddfoot{} + \else + \def\@oddfoot{\scriptsize \@date \hfil DRAFT} + \fi + \else + \def\@oddfoot{} + \fi + \def\@evenfoot{}} +\fi + + +% title page style +\def\ps at IEEEtitlepagestyle{\def\@oddfoot{}\def\@evenfoot{}% +\ifCLASSOPTIONconference + \def\@oddhead{}% + \def\@evenhead{}% +\else + \def\@oddhead{\hbox{}\scriptsize\leftmark \hfil \thepage}% + \def\@evenhead{\scriptsize\thepage \hfil \leftmark\hbox{}}% +\fi +\ifCLASSOPTIONdraftcls + \def\@oddhead{\hbox{}\scriptsize\leftmark \hfil \thepage}% + \def\@evenhead{\scriptsize\thepage \hfil \leftmark\hbox{}}% + \ifCLASSOPTIONdraftclsnofoot\else + \def\@oddfoot{\scriptsize \@date\hfil DRAFT}% + \def\@evenfoot{\scriptsize DRAFT\hfil \@date}% + \fi +\else + % all non-draft mode footers + \if at IEEEusingpubid + % for title pages that are using a pubid + % do not repeat pubid if using peer review option + \ifCLASSOPTIONpeerreview + \else + \footskip 0pt% + \ifCLASSOPTIONcompsoc + \def\@oddfoot{\hss\normalfont\scriptsize\raisebox{-1.5\@IEEEnormalsizeunitybaselineskip}[0ex][0ex]{\@IEEEpubid}\hss}% + \def\@evenfoot{\hss\normalfont\scriptsize\raisebox{-1.5\@IEEEnormalsizeunitybaselineskip}[0ex][0ex]{\@IEEEpubid}\hss}% + \else + \def\@oddfoot{\hss\normalfont\footnotesize\raisebox{1.5ex}[1.5ex]{\@IEEEpubid}\hss}% + \def\@evenfoot{\hss\normalfont\footnotesize\raisebox{1.5ex}[1.5ex]{\@IEEEpubid}\hss}% + \fi + \fi + \fi +\fi} + + +% peer review cover page style +\def\ps at IEEEpeerreviewcoverpagestyle{% +\def\@oddhead{}\def\@evenhead{}% +\def\@oddfoot{}\def\@evenfoot{}% +\ifCLASSOPTIONdraftcls + \ifCLASSOPTIONdraftclsnofoot\else + \def\@oddfoot{\scriptsize \@date\hfil DRAFT}% + \def\@evenfoot{\scriptsize DRAFT\hfil \@date}% + \fi +\else + % non-draft mode footers + \if at IEEEusingpubid + \footskip 0pt% + \ifCLASSOPTIONcompsoc + \def\@oddfoot{\hss\normalfont\scriptsize\raisebox{-1.5\@IEEEnormalsizeunitybaselineskip}[0ex][0ex]{\@IEEEpubid}\hss}% + \def\@evenfoot{\hss\normalfont\scriptsize\raisebox{-1.5\@IEEEnormalsizeunitybaselineskip}[0ex][0ex]{\@IEEEpubid}\hss}% + \else + \def\@oddfoot{\hss\normalfont\footnotesize\raisebox{1.5ex}[1.5ex]{\@IEEEpubid}\hss}% + \def\@evenfoot{\hss\normalfont\footnotesize\raisebox{1.5ex}[1.5ex]{\@IEEEpubid}\hss}% + \fi + \fi +\fi} + + +% start with empty headings +\def\rightmark{}\def\leftmark{} + + +%% Defines the command for putting the header. \footernote{TEXT} is the same +%% as \markboth{TEXT}{TEXT}. +%% Note that all the text is forced into uppercase, if you have some text +%% that needs to be in lower case, for instance et. al., then either manually +%% set \leftmark and \rightmark or use \MakeLowercase{et. al.} within the +%% arguments to \markboth. +\def\markboth#1#2{\def\leftmark{\@IEEEcompsoconly{\sffamily}\MakeUppercase{#1}}% +\def\rightmark{\@IEEEcompsoconly{\sffamily}\MakeUppercase{#2}}} +\def\footernote#1{\markboth{#1}{#1}} + +\def\today{\ifcase\month\or + January\or February\or March\or April\or May\or June\or + July\or August\or September\or October\or November\or December\fi + \space\number\day, \number\year} + + + + +%% CITATION AND BIBLIOGRAPHY COMMANDS +%% +%% V1.6 no longer supports the older, nonstandard \shortcite and \citename setup stuff +% +% +% Modify Latex2e \@citex to separate citations with "], [" +\def\@citex[#1]#2{% + \let\@citea\@empty + \@cite{\@for\@citeb:=#2\do + {\@citea\def\@citea{], [}% + \edef\@citeb{\expandafter\@firstofone\@citeb\@empty}% + \if at filesw\immediate\write\@auxout{\string\citation{\@citeb}}\fi + \@ifundefined{b@\@citeb}{\mbox{\reset at font\bfseries ?}% + \G at refundefinedtrue + \@latex at warning + {Citation `\@citeb' on page \thepage \space undefined}}% + {\hbox{\csname b@\@citeb\endcsname}}}}{#1}} + +% V1.6 we create hooks for the optional use of Donald Arseneau's +% cite.sty package. cite.sty is "smart" and will notice that the +% following format controls are already defined and will not +% redefine them. The result will be the proper sorting of the +% citation numbers and auto detection of 3 or more entry "ranges" - +% all in IEEE style: [1], [2], [5]--[7], [12] +% This also allows for an optional note, i.e., \cite[mynote]{..}. +% If the \cite with note has more than one reference, the note will +% be applied to the last of the listed references. It is generally +% desired that if a note is given, only one reference is listed in +% that \cite. +% Thanks to Mr. Arseneau for providing the required format arguments +% to produce the IEEE style. +\def\citepunct{], [} +\def\citedash{]--[} + +% V1.7 default to using same font for urls made by url.sty +\AtBeginDocument{\csname url at samestyle\endcsname} + +% V1.6 class files should always provide these +\def\newblock{\hskip .11em\@plus.33em\@minus.07em} +\let\@openbib at code\@empty + + +% Provide support for the control entries of IEEEtran.bst V1.00 and later. +% V1.7 optional argument allows for a different aux file to be specified in +% order to handle multiple bibliographies. For example, with multibib.sty: +% \newcites{sec}{Secondary Literature} +% \bstctlcite[@auxoutsec]{BSTcontrolhak} +\def\bstctlcite{\@ifnextchar[{\@bstctlcite}{\@bstctlcite[@auxout]}} +\def\@bstctlcite[#1]#2{\@bsphack + \@for\@citeb:=#2\do{% + \edef\@citeb{\expandafter\@firstofone\@citeb}% + \if at filesw\immediate\write\csname #1\endcsname{\string\citation{\@citeb}}\fi}% + \@esphack} + +% V1.6 provide a way for a user to execute a command just before +% a given reference number - used to insert a \newpage to balance +% the columns on the last page +\edef\@IEEEtriggerrefnum{0} % the default of zero means that + % the command is not executed +\def\@IEEEtriggercmd{\newpage} + +% allow the user to alter the triggered command +\long\def\IEEEtriggercmd#1{\long\def\@IEEEtriggercmd{#1}} + +% allow user a way to specify the reference number just before the +% command is executed +\def\IEEEtriggeratref#1{\@IEEEtrantmpcountA=#1% +\edef\@IEEEtriggerrefnum{\the\@IEEEtrantmpcountA}}% + +% trigger command at the given reference +\def\@IEEEbibitemprefix{\@IEEEtrantmpcountA=\@IEEEtriggerrefnum\relax% +\advance\@IEEEtrantmpcountA by -1\relax% +\ifnum\c at enumiv=\@IEEEtrantmpcountA\relax\@IEEEtriggercmd\relax\fi} + + +\def\@biblabel#1{[#1]} + +% compsoc journals left align the reference numbers +\@IEEEcompsocnotconfonly{\def\@biblabel#1{[#1]\hfill}} + +% controls bib item spacing +\def\IEEEbibitemsep{0pt plus .5pt} + +\@IEEEcompsocconfonly{\def\IEEEbibitemsep{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}} + + +\def\thebibliography#1{\section*{\refname}% + \addcontentsline{toc}{section}{\refname}% + % V1.6 add some rubber space here and provide a command trigger + \footnotesize\@IEEEcompsocconfonly{\small}\vskip 0.3\baselineskip plus 0.1\baselineskip minus 0.1\baselineskip% + \list{\@biblabel{\@arabic\c at enumiv}}% + {\settowidth\labelwidth{\@biblabel{#1}}% + \leftmargin\labelwidth + \advance\leftmargin\labelsep\relax + \itemsep \IEEEbibitemsep\relax + \usecounter{enumiv}% + \let\p at enumiv\@empty + \renewcommand\theenumiv{\@arabic\c at enumiv}}% + \let\@IEEElatexbibitem\bibitem% + \def\bibitem{\@IEEEbibitemprefix\@IEEElatexbibitem}% +\def\newblock{\hskip .11em plus .33em minus .07em}% +% originally: +% \sloppy\clubpenalty4000\widowpenalty4000% +% by adding the \interlinepenalty here, we make it more +% difficult, but not impossible, for LaTeX to break within a reference. +% IEEE almost never breaks a reference (but they do it more often with +% technotes). You may get an underfull vbox warning around the bibliography, +% but the final result will be much more like what IEEE will publish. +% MDS 11/2000 +\ifCLASSOPTIONtechnote\sloppy\clubpenalty4000\widowpenalty4000\interlinepenalty100% +\else\sloppy\clubpenalty4000\widowpenalty4000\interlinepenalty500\fi% + \sfcode`\.=1000\relax} +\let\endthebibliography=\endlist + + + + +% TITLE PAGE COMMANDS +% +% +% \IEEEmembership is used to produce the sublargesize italic font used to indicate author +% IEEE membership. compsoc uses a large size sans slant font +\def\IEEEmembership#1{{\@IEEEnotcompsoconly{\sublargesize}\normalfont\@IEEEcompsoconly{\sffamily}\textit{#1}}} + + +% \IEEEauthorrefmark{} produces a footnote type symbol to indicate author affiliation. +% When given an argument of 1 to 9, \IEEEauthorrefmark{} follows the standard LaTeX footnote +% symbol sequence convention. However, for arguments 10 and above, \IEEEauthorrefmark{} +% reverts to using lower case roman numerals, so it cannot overflow. Do note that you +% cannot use \footnotemark[] in place of \IEEEauthorrefmark{} within \author as the footnote +% symbols will have been turned off to prevent \thanks from creating footnote marks. +% \IEEEauthorrefmark{} produces a symbol that appears to LaTeX as having zero vertical +% height - this allows for a more compact line packing, but the user must ensure that +% the interline spacing is large enough to prevent \IEEEauthorrefmark{} from colliding +% with the text above. +% V1.7 make this a robust command +\DeclareRobustCommand*{\IEEEauthorrefmark}[1]{\raisebox{0pt}[0pt][0pt]{\textsuperscript{\footnotesize\ensuremath{\ifcase#1\or *\or \dagger\or \ddagger\or% + \mathsection\or \mathparagraph\or \|\or **\or \dagger\dagger% + \or \ddagger\ddagger \else\textsuperscript{\expandafter\romannumeral#1}\fi}}}} + + +% FONT CONTROLS AND SPACINGS FOR CONFERENCE MODE AUTHOR NAME AND AFFILIATION BLOCKS +% +% The default font styles for the author name and affiliation blocks (confmode) +\def\@IEEEauthorblockNstyle{\normalfont\@IEEEcompsocnotconfonly{\sffamily}\sublargesize\@IEEEcompsocconfonly{\large}} +\def\@IEEEauthorblockAstyle{\normalfont\@IEEEcompsocnotconfonly{\sffamily}\@IEEEcompsocconfonly{\itshape}\normalsize\@IEEEcompsocconfonly{\large}} +% The default if the user does not use an author block +\def\@IEEEauthordefaulttextstyle{\normalfont\@IEEEcompsocnotconfonly{\sffamily}\sublargesize} + +% spacing from title (or special paper notice) to author name blocks (confmode) +% can be negative +\def\@IEEEauthorblockconfadjspace{-0.25em} +% compsoc conferences need more space here +\@IEEEcompsocconfonly{\def\@IEEEauthorblockconfadjspace{0.75\@IEEEnormalsizeunitybaselineskip}} + +% spacing between name and affiliation blocks (confmode) +% This can be negative. +% IEEE doesn't want any added spacing here, but I will leave these +% controls in place in case they ever change their mind. +% Personally, I like 0.75ex. +%\def\@IEEEauthorblockNtopspace{0.75ex} +%\def\@IEEEauthorblockAtopspace{0.75ex} +\def\@IEEEauthorblockNtopspace{0.0ex} +\def\@IEEEauthorblockAtopspace{0.0ex} +% baseline spacing within name and affiliation blocks (confmode) +% must be positive, spacings below certain values will make +% the position of line of text sensitive to the contents of the +% line above it i.e., whether or not the prior line has descenders, +% subscripts, etc. For this reason it is a good idea to keep +% these above 2.6ex +\def\@IEEEauthorblockNinterlinespace{2.6ex} +\def\@IEEEauthorblockAinterlinespace{2.75ex} + +% This tracks the required strut size. +% See the \@IEEEauthorhalign command for the actual default value used. +\def\@IEEEauthorblockXinterlinespace{2.7ex} + +% variables to retain font size and style across groups +% values given here have no effect as they will be overwritten later +\gdef\@IEEESAVESTATEfontsize{10} +\gdef\@IEEESAVESTATEfontbaselineskip{12} +\gdef\@IEEESAVESTATEfontencoding{OT1} +\gdef\@IEEESAVESTATEfontfamily{ptm} +\gdef\@IEEESAVESTATEfontseries{m} +\gdef\@IEEESAVESTATEfontshape{n} + +% saves the current font attributes +\def\@IEEEcurfontSAVE{\global\let\@IEEESAVESTATEfontsize\f at size% +\global\let\@IEEESAVESTATEfontbaselineskip\f at baselineskip% +\global\let\@IEEESAVESTATEfontencoding\f at encoding% +\global\let\@IEEESAVESTATEfontfamily\f at family% +\global\let\@IEEESAVESTATEfontseries\f at series% +\global\let\@IEEESAVESTATEfontshape\f at shape} + +% restores the saved font attributes +\def\@IEEEcurfontRESTORE{\fontsize{\@IEEESAVESTATEfontsize}{\@IEEESAVESTATEfontbaselineskip}% +\fontencoding{\@IEEESAVESTATEfontencoding}% +\fontfamily{\@IEEESAVESTATEfontfamily}% +\fontseries{\@IEEESAVESTATEfontseries}% +\fontshape{\@IEEESAVESTATEfontshape}% +\selectfont} + + +% variable to indicate if the current block is the first block in the column +\newif\if at IEEEprevauthorblockincol \@IEEEprevauthorblockincolfalse + + +% the command places a strut with height and depth = \@IEEEauthorblockXinterlinespace +% we use this technique to have complete manual control over the spacing of the lines +% within the halign environment. +% We set the below baseline portion at 30%, the above +% baseline portion at 70% of the total length. +% Responds to changes in the document's \baselinestretch +\def\@IEEEauthorstrutrule{\@IEEEtrantmpdimenA\@IEEEauthorblockXinterlinespace% +\@IEEEtrantmpdimenA=\baselinestretch\@IEEEtrantmpdimenA% +\rule[-0.3\@IEEEtrantmpdimenA]{0pt}{\@IEEEtrantmpdimenA}} + + +% blocks to hold the authors' names and affilations. +% Makes formatting easy for conferences +% +% use real definitions in conference mode +% name block +\def\IEEEauthorblockN#1{\relax\@IEEEauthorblockNstyle% set the default text style +\gdef\@IEEEauthorblockXinterlinespace{0pt}% disable strut for spacer row +% the \expandafter hides the \cr in conditional tex, see the array.sty docs +% for details, probably not needed here as the \cr is in a macro +% do a spacer row if needed +\if at IEEEprevauthorblockincol\expandafter\@IEEEauthorblockNtopspaceline\fi +\global\@IEEEprevauthorblockincoltrue% we now have a block in this column +%restore the correct strut value +\gdef\@IEEEauthorblockXinterlinespace{\@IEEEauthorblockNinterlinespace}% +% input the author names +#1% +% end the row if the user did not already +\crcr} +% spacer row for names +\def\@IEEEauthorblockNtopspaceline{\cr\noalign{\vskip\@IEEEauthorblockNtopspace}} +% +% affiliation block +\def\IEEEauthorblockA#1{\relax\@IEEEauthorblockAstyle% set the default text style +\gdef\@IEEEauthorblockXinterlinespace{0pt}%disable strut for spacer row +% the \expandafter hides the \cr in conditional tex, see the array.sty docs +% for details, probably not needed here as the \cr is in a macro +% do a spacer row if needed +\if at IEEEprevauthorblockincol\expandafter\@IEEEauthorblockAtopspaceline\fi +\global\@IEEEprevauthorblockincoltrue% we now have a block in this column +%restore the correct strut value +\gdef\@IEEEauthorblockXinterlinespace{\@IEEEauthorblockAinterlinespace}% +% input the author affiliations +#1% +% end the row if the user did not already +\crcr} +% spacer row for affiliations +\def\@IEEEauthorblockAtopspaceline{\cr\noalign{\vskip\@IEEEauthorblockAtopspace}} + + +% allow papers to compile even if author blocks are used in modes other +% than conference or peerreviewca. For such cases, we provide dummy blocks. +\ifCLASSOPTIONconference +\else + \ifCLASSOPTIONpeerreviewca\else + % not conference or peerreviewca mode + \def\IEEEauthorblockN#1{#1}% + \def\IEEEauthorblockA#1{#1}% + \fi +\fi + + + +% we provide our own halign so as not to have to depend on tabular +\def\@IEEEauthorhalign{\@IEEEauthordefaulttextstyle% default text style + \lineskip=0pt\relax% disable line spacing + \lineskiplimit=0pt\relax% + \baselineskip=0pt\relax% + \@IEEEcurfontSAVE% save the current font + \mathsurround\z@\relax% no extra spacing around math + \let\\\@IEEEauthorhaligncr% replace newline with halign friendly one + \tabskip=0pt\relax% no column spacing + \everycr{}% ensure no problems here + \@IEEEprevauthorblockincolfalse% no author blocks yet + \def\@IEEEauthorblockXinterlinespace{2.7ex}% default interline space + \vtop\bgroup%vtop box + \halign\bgroup&\relax\hfil\@IEEEcurfontRESTORE\relax ##\relax + \hfil\@IEEEcurfontSAVE\@IEEEauthorstrutrule\cr} + +% ensure last line, exit from halign, close vbox +\def\end at IEEEauthorhalign{\crcr\egroup\egroup} + +% handle bogus star form +\def\@IEEEauthorhaligncr{{\ifnum0=`}\fi\@ifstar{\@@IEEEauthorhaligncr}{\@@IEEEauthorhaligncr}} + +% test and setup the optional argument to \\[] +\def\@@IEEEauthorhaligncr{\@testopt\@@@IEEEauthorhaligncr\z at skip} + +% end the line and do the optional spacer +\def\@@@IEEEauthorhaligncr[#1]{\ifnum0=`{\fi}\cr\noalign{\vskip#1\relax}} + + + +% flag to prevent multiple \and warning messages +\newif\if at IEEEWARNand +\@IEEEWARNandtrue + +% if in conference or peerreviewca modes, we support the use of \and as \author is a +% tabular environment, otherwise we warn the user that \and is invalid +% outside of conference or peerreviewca modes. +\def\and{\relax} % provide a bogus \and that we will then override + +\renewcommand{\and}[1][\relax]{\if at IEEEWARNand\typeout{** WARNING: \noexpand\and is valid only + when in conference or peerreviewca}\typeout{modes (line \the\inputlineno).}\fi\global\@IEEEWARNandfalse} + +\ifCLASSOPTIONconference% +\renewcommand{\and}[1][\hfill]{\end{@IEEEauthorhalign}#1\begin{@IEEEauthorhalign}}% +\fi +\ifCLASSOPTIONpeerreviewca +\renewcommand{\and}[1][\hfill]{\end{@IEEEauthorhalign}#1\begin{@IEEEauthorhalign}}% +\fi + + +% page clearing command +% based on LaTeX2e's \cleardoublepage, but allows different page styles +% for the inserted blank pages +\def\@IEEEcleardoublepage#1{\clearpage\if at twoside\ifodd\c at page\else +\hbox{}\thispagestyle{#1}\newpage\if at twocolumn\hbox{}\thispagestyle{#1}\newpage\fi\fi\fi} + + +% user command to invoke the title page +\def\maketitle{\par% + \begingroup% + \normalfont% + \def\thefootnote{}% the \thanks{} mark type is empty + \def\footnotemark{}% and kill space from \thanks within author + \let\@makefnmark\relax% V1.7, must *really* kill footnotemark to remove all \textsuperscript spacing as well. + \footnotesize% equal spacing between thanks lines + \footnotesep 0.7\baselineskip%see global setting of \footnotesep for more info + % V1.7 disable \thanks note indention for compsoc + \@IEEEcompsoconly{\long\def\@makefntext##1{\parindent 1em\noindent\hbox{\@makefnmark}##1}}% + \normalsize% + \ifCLASSOPTIONpeerreview + \newpage\global\@topnum\z@ \@maketitle\@IEEEstatictitlevskip\@IEEEaftertitletext% + \thispagestyle{IEEEpeerreviewcoverpagestyle}\@thanks% + \else + \if at twocolumn% + \ifCLASSOPTIONtechnote% + \newpage\global\@topnum\z@ \@maketitle\@IEEEstatictitlevskip\@IEEEaftertitletext% + \else + \twocolumn[\@maketitle\@IEEEdynamictitlevspace\@IEEEaftertitletext]% + \fi + \else + \newpage\global\@topnum\z@ \@maketitle\@IEEEstatictitlevskip\@IEEEaftertitletext% + \fi + \thispagestyle{IEEEtitlepagestyle}\@thanks% + \fi + % pullup page for pubid if used. + \if at IEEEusingpubid + \enlargethispage{-\@IEEEpubidpullup}% + \fi + \endgroup + \setcounter{footnote}{0}\let\maketitle\relax\let\@maketitle\relax + \gdef\@thanks{}% + % v1.6b do not clear these as we will need the title again for peer review papers + % \gdef\@author{}\gdef\@title{}% + \let\thanks\relax} + + + +% V1.7 parbox to format \@IEEEcompsoctitleabstractindextext +\long\def\@IEEEcompsoctitleabstractindextextbox#1{\parbox{0.915\textwidth}{#1}} + +% formats the Title, authors names, affiliations and special paper notice +% THIS IS A CONTROLLED SPACING COMMAND! Do not allow blank lines or unintentional +% spaces to enter the definition - use % at the end of each line +\def\@maketitle{\newpage +\begin{center}% +\ifCLASSOPTIONtechnote% technotes + {\bfseries\large\@IEEEcompsoconly{\sffamily}\@title\par}\vskip 1.3em{\lineskip .5em\@IEEEcompsoconly{\sffamily}\@author + \@IEEEspecialpapernotice\par{\@IEEEcompsoconly{\vskip 1.5em\relax + \@IEEEcompsoctitleabstractindextextbox{\@IEEEcompsoctitleabstractindextext}\par + \hfill\@IEEEcompsocdiamondline\hfill\hbox{}\par}}}\relax +\else% not a technote + \vskip0.2em{\Huge\@IEEEcompsoconly{\sffamily}\@IEEEcompsocconfonly{\normalfont\normalsize\vskip 2\@IEEEnormalsizeunitybaselineskip + \bfseries\Large}\@title\par}\vskip1.0em\par% + % V1.6 handle \author differently if in conference mode + \ifCLASSOPTIONconference% + {\@IEEEspecialpapernotice\mbox{}\vskip\@IEEEauthorblockconfadjspace% + \mbox{}\hfill\begin{@IEEEauthorhalign}\@author\end{@IEEEauthorhalign}\hfill\mbox{}\par}\relax + \else% peerreviewca, peerreview or journal + \ifCLASSOPTIONpeerreviewca + % peerreviewca handles author names just like conference mode + {\@IEEEcompsoconly{\sffamily}\@IEEEspecialpapernotice\mbox{}\vskip\@IEEEauthorblockconfadjspace% + \mbox{}\hfill\begin{@IEEEauthorhalign}\@author\end{@IEEEauthorhalign}\hfill\mbox{}\par + {\@IEEEcompsoconly{\vskip 1.5em\relax + \@IEEEcompsoctitleabstractindextextbox{\@IEEEcompsoctitleabstractindextext}\par\hfill + \@IEEEcompsocdiamondline\hfill\hbox{}\par}}}\relax + \else% journal or peerreview + {\lineskip.5em\@IEEEcompsoconly{\sffamily}\sublargesize\@author\@IEEEspecialpapernotice\par + {\@IEEEcompsoconly{\vskip 1.5em\relax + \@IEEEcompsoctitleabstractindextextbox{\@IEEEcompsoctitleabstractindextext}\par\hfill + \@IEEEcompsocdiamondline\hfill\hbox{}\par}}}\relax + \fi + \fi +\fi\end{center}} + + + +% V1.7 Computer Society "diamond line" which follows index terms for nonconference papers +\def\@IEEEcompsocdiamondline{\vrule depth 0pt height 0.5pt width 4cm\hspace{7.5pt}% +\raisebox{-3.5pt}{\fontfamily{pzd}\fontencoding{U}\fontseries{m}\fontshape{n}\fontsize{11}{12}\selectfont\char70}% +\hspace{7.5pt}\vrule depth 0pt height 0.5pt width 4cm\relax} + +% V1.7 standard LateX2e \thanks, but with \itshape under compsoc. Also make it a \long\def +% We also need to trigger the one-shot footnote rule +\def\@IEEEtriggeroneshotfootnoterule{\global\@IEEEenableoneshotfootnoteruletrue} + + +\long\def\thanks#1{\footnotemark + \protected at xdef\@thanks{\@thanks + \protect\footnotetext[\the\c at footnote]{\@IEEEcompsoconly{\itshape + \protect\@IEEEtriggeroneshotfootnoterule\relax}\ignorespaces#1}}} +\let\@thanks\@empty + +% V1.7 allow \author to contain \par's. This is needed to allow \thanks to contain \par. +\long\def\author#1{\gdef\@author{#1}} + + +% in addition to setting up IEEEitemize, we need to remove a baselineskip space above and +% below it because \list's \pars introduce blank lines because of the footnote struts. +\def\@IEEEsetupcompsocitemizelist{\def\labelitemi{$\bullet$}% +\setlength{\IEEElabelindent}{0pt}\setlength{\parskip}{0pt}% +\setlength{\partopsep}{0pt}\setlength{\topsep}{0.5\baselineskip}\vspace{-1\baselineskip}\relax} + + +% flag for fake non-compsoc \IEEEcompsocthanksitem - prevents line break on very first item +\newif\if at IEEEbreakcompsocthanksitem \@IEEEbreakcompsocthanksitemfalse + +\ifCLASSOPTIONcompsoc +% V1.7 compsoc bullet item \thanks +% also, we need to redefine this to destroy the argument in \@IEEEdynamictitlevspace +\long\def\IEEEcompsocitemizethanks#1{\relax\@IEEEbreakcompsocthanksitemfalse\footnotemark + \protected at xdef\@thanks{\@thanks + \protect\footnotetext[\the\c at footnote]{\itshape\protect\@IEEEtriggeroneshotfootnoterule + {\let\IEEEiedlistdecl\relax\protect\begin{IEEEitemize}[\protect\@IEEEsetupcompsocitemizelist]\ignorespaces#1\relax + \protect\end{IEEEitemize}}\protect\vspace{-1\baselineskip}}}} +\DeclareRobustCommand*{\IEEEcompsocthanksitem}{\item} +\else +% non-compsoc, allow for dual compilation via rerouting to normal \thanks +\long\def\IEEEcompsocitemizethanks#1{\thanks{#1}} +% redirect to "pseudo-par" \hfil\break\indent after swallowing [] from \IEEEcompsocthanksitem[] +\DeclareRobustCommand{\IEEEcompsocthanksitem}{\@ifnextchar [{\@IEEEthanksswallowoptionalarg}% +{\@IEEEthanksswallowoptionalarg[\relax]}} +% be sure and break only after first item, be sure and ignore spaces after optional argument +\def\@IEEEthanksswallowoptionalarg[#1]{\relax\if at IEEEbreakcompsocthanksitem\hfil\break +\indent\fi\@IEEEbreakcompsocthanksitemtrue\ignorespaces} +\fi + + +% V1.6b define the \IEEEpeerreviewmaketitle as needed +\ifCLASSOPTIONpeerreview +\def\IEEEpeerreviewmaketitle{\@IEEEcleardoublepage{empty}% +\ifCLASSOPTIONtwocolumn +\twocolumn[\@IEEEpeerreviewmaketitle\@IEEEdynamictitlevspace] +\else +\newpage\@IEEEpeerreviewmaketitle\@IEEEstatictitlevskip +\fi +\thispagestyle{IEEEtitlepagestyle}} +\else +% \IEEEpeerreviewmaketitle does nothing if peer review option has not been selected +\def\IEEEpeerreviewmaketitle{\relax} +\fi + +% peerreview formats the repeated title like the title in journal papers. +\def\@IEEEpeerreviewmaketitle{\begin{center}\@IEEEcompsoconly{\sffamily}% +\normalfont\normalsize\vskip0.2em{\Huge\@title\par}\vskip1.0em\par +\end{center}} + + + +% V1.6 +% this is a static rubber spacer between the title/authors and the main text +% used for single column text, or when the title appears in the first column +% of two column text (technotes). +\def\@IEEEstatictitlevskip{{\normalfont\normalsize +% adjust spacing to next text +% v1.6b handle peer review papers +\ifCLASSOPTIONpeerreview +% for peer review papers, the same value is used for both title pages +% regardless of the other paper modes + \vskip 1\baselineskip plus 0.375\baselineskip minus 0.1875\baselineskip +\else + \ifCLASSOPTIONconference% conference + \vskip 1\baselineskip plus 0.375\baselineskip minus 0.1875\baselineskip% + \else% + \ifCLASSOPTIONtechnote% technote + \vskip 1\baselineskip plus 0.375\baselineskip minus 0.1875\baselineskip% + \else% journal uses more space + \vskip 2.5\baselineskip plus 0.75\baselineskip minus 0.375\baselineskip% + \fi + \fi +\fi}} + + +% V1.6 +% This is a dynamically determined rigid spacer between the title/authors +% and the main text. This is used only for single column titles over two +% column text (most common) +% This is bit tricky because we have to ensure that the textheight of the +% main text is an integer multiple of \baselineskip +% otherwise underfull vbox problems may develop in the second column of the +% text on the titlepage +% The possible use of \IEEEpubid must also be taken into account. +\def\@IEEEdynamictitlevspace{{% + % we run within a group so that all the macros can be forgotten when we are done + \long\def\thanks##1{\relax}%don't allow \thanks to run when we evaluate the vbox height + \long\def\IEEEcompsocitemizethanks##1{\relax}%don't allow \IEEEcompsocitemizethanks to run when we evaluate the vbox height + \normalfont\normalsize% we declare more descriptive variable names + \let\@IEEEmaintextheight=\@IEEEtrantmpdimenA%height of the main text columns + \let\@IEEEINTmaintextheight=\@IEEEtrantmpdimenB%height of the main text columns with integer # lines + % set the nominal and minimum values for the title spacer + % the dynamic algorithm will not allow the spacer size to + % become less than \@IEEEMINtitlevspace - instead it will be + % lengthened + % default to journal values + \def\@IEEENORMtitlevspace{2.5\baselineskip}% + \def\@IEEEMINtitlevspace{2\baselineskip}% + % conferences and technotes need tighter spacing + \ifCLASSOPTIONconference%conference + \def\@IEEENORMtitlevspace{1\baselineskip}% + \def\@IEEEMINtitlevspace{0.75\baselineskip}% + \fi + \ifCLASSOPTIONtechnote%technote + \def\@IEEENORMtitlevspace{1\baselineskip}% + \def\@IEEEMINtitlevspace{0.75\baselineskip}% + \fi% + % get the height that the title will take up + \ifCLASSOPTIONpeerreview + \settoheight{\@IEEEmaintextheight}{\vbox{\hsize\textwidth \@IEEEpeerreviewmaketitle}}% + \else + \settoheight{\@IEEEmaintextheight}{\vbox{\hsize\textwidth \@maketitle}}% + \fi + \@IEEEmaintextheight=-\@IEEEmaintextheight% title takes away from maintext, so reverse sign + % add the height of the page textheight + \advance\@IEEEmaintextheight by \textheight% + % correct for title pages using pubid + \ifCLASSOPTIONpeerreview\else + % peerreview papers use the pubid on the cover page only. + % And the cover page uses a static spacer. + \if at IEEEusingpubid\advance\@IEEEmaintextheight by -\@IEEEpubidpullup\fi + \fi% + % subtract off the nominal value of the title bottom spacer + \advance\@IEEEmaintextheight by -\@IEEENORMtitlevspace% + % \topskip takes away some too + \advance\@IEEEmaintextheight by -\topskip% + % calculate the column height of the main text for lines + % now we calculate the main text height as if holding + % an integer number of \normalsize lines after the first + % and discard any excess fractional remainder + % we subtracted the first line, because the first line + % is placed \topskip into the maintext, not \baselineskip like the + % rest of the lines. + \@IEEEINTmaintextheight=\@IEEEmaintextheight% + \divide\@IEEEINTmaintextheight by \baselineskip% + \multiply\@IEEEINTmaintextheight by \baselineskip% + % now we calculate how much the title spacer height will + % have to be reduced from nominal (\@IEEEREDUCEmaintextheight is always + % a positive value) so that the maintext area will contain an integer + % number of normal size lines + % we change variable names here (to avoid confusion) as we no longer + % need \@IEEEINTmaintextheight and can reuse its dimen register + \let\@IEEEREDUCEmaintextheight=\@IEEEINTmaintextheight% + \advance\@IEEEREDUCEmaintextheight by -\@IEEEmaintextheight% + \advance\@IEEEREDUCEmaintextheight by \baselineskip% + % this is the calculated height of the spacer + % we change variable names here (to avoid confusion) as we no longer + % need \@IEEEmaintextheight and can reuse its dimen register + \let\@IEEECOMPENSATElen=\@IEEEmaintextheight% + \@IEEECOMPENSATElen=\@IEEENORMtitlevspace% set the nominal value + % we go with the reduced length if it is smaller than an increase + \ifdim\@IEEEREDUCEmaintextheight < 0.5\baselineskip\relax% + \advance\@IEEECOMPENSATElen by -\@IEEEREDUCEmaintextheight% + % if the resulting spacer is too small back out and go with an increase instead + \ifdim\@IEEECOMPENSATElen<\@IEEEMINtitlevspace\relax% + \advance\@IEEECOMPENSATElen by \baselineskip% + \fi% + \else% + % go with an increase because it is closer to the nominal than a decrease + \advance\@IEEECOMPENSATElen by -\@IEEEREDUCEmaintextheight% + \advance\@IEEECOMPENSATElen by \baselineskip% + \fi% + % set the calculated rigid spacer + \vspace{\@IEEECOMPENSATElen}}} + + + +% V1.6 +% we allow the user access to the last part of the title area +% useful in emergencies such as when a different spacing is needed +% This text is NOT compensated for in the dynamic sizer. +\let\@IEEEaftertitletext=\relax +\long\def\IEEEaftertitletext#1{\def\@IEEEaftertitletext{#1}} + +% V1.7 provide a way for users to enter abstract and keywords +% into the onecolumn title are. This text is compensated for +% in the dynamic sizer. +\let\@IEEEcompsoctitleabstractindextext=\relax +\long\def\IEEEcompsoctitleabstractindextext#1{\def\@IEEEcompsoctitleabstractindextext{#1}} +% V1.7 provide a way for users to get the \@IEEEcompsoctitleabstractindextext if +% not in compsoc journal mode - this way abstract and keywords can be placed +% in their conventional position if not in compsoc mode. +\def\IEEEdisplaynotcompsoctitleabstractindextext{% +\ifCLASSOPTIONcompsoc% display if compsoc conf +\ifCLASSOPTIONconference\@IEEEcompsoctitleabstractindextext\fi +\else% or if not compsoc +\@IEEEcompsoctitleabstractindextext\fi} + + +% command to allow alteration of baselinestretch, but only if the current +% baselineskip is unity. Used to tweak the compsoc abstract and keywords line spacing. +\def\@IEEEtweakunitybaselinestretch#1{{\def\baselinestretch{1}\selectfont +\global\@tempskipa\baselineskip}\ifnum\@tempskipa=\baselineskip% +\def\baselinestretch{#1}\selectfont\fi\relax} + + +% abstract and keywords are in \small, except +% for 9pt docs in which they are in \footnotesize +% Because 9pt docs use an 8pt footnotesize, \small +% becomes a rather awkward 8.5pt +\def\@IEEEabskeysecsize{\small} +\ifx\CLASSOPTIONpt\@IEEEptsizenine + \def\@IEEEabskeysecsize{\footnotesize} +\fi + +% compsoc journals use \footnotesize, compsoc conferences use normalsize +\@IEEEcompsoconly{\def\@IEEEabskeysecsize{\footnotesize}} +\@IEEEcompsocconfonly{\def\@IEEEabskeysecsize{\normalsize}} + + + + +% V1.6 have abstract and keywords strip leading spaces, pars and newlines +% so that spacing is more tightly controlled. +\def\abstract{\normalfont + \if at twocolumn + \@IEEEabskeysecsize\bfseries\textit{\abstractname}---\relax + \else + \begin{center}\vspace{-1.78ex}\@IEEEabskeysecsize\textbf{\abstractname}\end{center}\quotation\@IEEEabskeysecsize + \fi\@IEEEgobbleleadPARNLSP} +% V1.6 IEEE wants only 1 pica from end of abstract to introduction heading when in +% conference mode (the heading already has this much above it) +\def\endabstract{\relax\ifCLASSOPTIONconference\vspace{0ex}\else\vspace{1.34ex}\fi\par\if at twocolumn\else\endquotation\fi + \normalfont\normalsize} + +\def\IEEEkeywords{\normalfont + \if at twocolumn + \@IEEEabskeysecsize\bfseries\textit{\IEEEkeywordsname}---\relax + \else + \begin{center}\@IEEEabskeysecsize\textbf{\IEEEkeywordsname}\end{center}\quotation\@IEEEabskeysecsize + \fi\@IEEEgobbleleadPARNLSP} +\def\endIEEEkeywords{\relax\ifCLASSOPTIONtechnote\vspace{1.34ex}\else\vspace{0.67ex}\fi + \par\if at twocolumn\else\endquotation\fi% + \normalfont\normalsize} + +% V1.7 compsoc keywords index terms +\ifCLASSOPTIONcompsoc + \ifCLASSOPTIONconference% compsoc conference +\def\abstract{\normalfont + \begin{center}\@IEEEabskeysecsize\textbf{\large\abstractname}\end{center}\vskip 0.5\baselineskip plus 0.1\baselineskip minus 0.1\baselineskip + \if at twocolumn\else\quotation\fi\itshape\@IEEEabskeysecsize% + \par\@IEEEgobbleleadPARNLSP} +\def\IEEEkeywords{\normalfont\vskip 1.5\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip + \begin{center}\@IEEEabskeysecsize\textbf{\large\IEEEkeywordsname}\end{center}\vskip 0.5\baselineskip plus 0.1\baselineskip minus 0.1\baselineskip + \if at twocolumn\else\quotation\fi\itshape\@IEEEabskeysecsize% + \par\@IEEEgobbleleadPARNLSP} + \else% compsoc not conference +\def\abstract{\normalfont\@IEEEtweakunitybaselinestretch{1.15}\sffamily + \if at twocolumn + \@IEEEabskeysecsize\noindent\textbf{\abstractname}---\relax + \else + \begin{center}\vspace{-1.78ex}\@IEEEabskeysecsize\textbf{\abstractname}\end{center}\quotation\@IEEEabskeysecsize% + \fi\@IEEEgobbleleadPARNLSP} +\def\IEEEkeywords{\normalfont\@IEEEtweakunitybaselinestretch{1.15}\sffamily + \if at twocolumn + \@IEEEabskeysecsize\vskip 0.5\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip\noindent + \textbf{\IEEEkeywordsname}---\relax + \else + \begin{center}\@IEEEabskeysecsize\textbf{\IEEEkeywordsname}\end{center}\quotation\@IEEEabskeysecsize% + \fi\@IEEEgobbleleadPARNLSP} + \fi +\fi + + + +% gobbles all leading \, \\ and \par, upon finding first token that +% is not a \ , \\ or a \par, it ceases and returns that token +% +% used to strip leading \, \\ and \par from the input +% so that such things in the beginning of an environment will not +% affect the formatting of the text +\long\def\@IEEEgobbleleadPARNLSP#1{\let\@IEEEswallowthistoken=0% +\let\@IEEEgobbleleadPARNLSPtoken#1% +\let\@IEEEgobbleleadPARtoken=\par% +\let\@IEEEgobbleleadNLtoken=\\% +\let\@IEEEgobbleleadSPtoken=\ % +\def\@IEEEgobbleleadSPMACRO{\ }% +\ifx\@IEEEgobbleleadPARNLSPtoken\@IEEEgobbleleadPARtoken% +\let\@IEEEswallowthistoken=1% +\fi% +\ifx\@IEEEgobbleleadPARNLSPtoken\@IEEEgobbleleadNLtoken% +\let\@IEEEswallowthistoken=1% +\fi% +\ifx\@IEEEgobbleleadPARNLSPtoken\@IEEEgobbleleadSPtoken% +\let\@IEEEswallowthistoken=1% +\fi% +% a control space will come in as a macro +% when it is the last one on a line +\ifx\@IEEEgobbleleadPARNLSPtoken\@IEEEgobbleleadSPMACRO% +\let\@IEEEswallowthistoken=1% +\fi% +% if we have to swallow this token, do so and taste the next one +% else spit it out and stop gobbling +\ifx\@IEEEswallowthistoken 1\let\@IEEEnextgobbleleadPARNLSP=\@IEEEgobbleleadPARNLSP\else% +\let\@IEEEnextgobbleleadPARNLSP=#1\fi% +\@IEEEnextgobbleleadPARNLSP}% + + + + +% TITLING OF SECTIONS +\def\@IEEEsectpunct{:\ \,} % Punctuation after run-in section heading (headings which are + % part of the paragraphs), need little bit more than a single space + % spacing from section number to title +% compsoc conferences use regular period/space punctuation +\ifCLASSOPTIONcompsoc +\ifCLASSOPTIONconference +\def\@IEEEsectpunct{.\ } +\fi\fi + + +\def\@seccntformat#1{\csname the#1dis\endcsname\hskip 0.5em\relax} + +\ifCLASSOPTIONcompsoc +% compsoc journals need extra spacing +\ifCLASSOPTIONconference\else +\def\@seccntformat#1{\csname the#1dis\endcsname\hskip 1em\relax} +\fi\fi + +%v1.7 put {} after #6 to allow for some types of user font control +%and use \@@par rather than \par +\def\@sect#1#2#3#4#5#6[#7]#8{% + \ifnum #2>\c at secnumdepth + \let\@svsec\@empty + \else + \refstepcounter{#1}% + % load section label and spacer into \@svsec + \protected at edef\@svsec{\@seccntformat{#1}\relax}% + \fi% + \@tempskipa #5\relax + \ifdim \@tempskipa>\z@% tempskipa determines whether is treated as a high + \begingroup #6{\relax% or low level heading + \noindent % subsections are NOT indented + % print top level headings. \@svsec is label, #8 is heading title + % IEEE does not block indent the section title text, it flows like normal + {\hskip #3\relax\@svsec}{\interlinepenalty \@M #8\@@par}}% + \endgroup + \addcontentsline{toc}{#1}{\ifnum #2>\c at secnumdepth\relax\else + \protect\numberline{\csname the#1\endcsname}\fi#7}% + \else % printout low level headings + % svsechd seems to swallow the trailing space, protect it with \mbox{} + % got rid of sectionmark stuff + \def\@svsechd{#6{\hskip #3\relax\@svsec #8\@IEEEsectpunct\mbox{}}% + \addcontentsline{toc}{#1}{\ifnum #2>\c at secnumdepth\relax\else + \protect\numberline{\csname the#1\endcsname}\fi#7}}% + \fi%skip down + \@xsect{#5}} + + +% section* handler +%v1.7 put {} after #4 to allow for some types of user font control +%and use \@@par rather than \par +\def\@ssect#1#2#3#4#5{\@tempskipa #3\relax + \ifdim \@tempskipa>\z@ + %\begingroup #4\@hangfrom{\hskip #1}{\interlinepenalty \@M #5\par}\endgroup + % IEEE does not block indent the section title text, it flows like normal + \begingroup \noindent #4{\relax{\hskip #1}{\interlinepenalty \@M #5\@@par}}\endgroup + % svsechd swallows the trailing space, protect it with \mbox{} + \else \def\@svsechd{#4{\hskip #1\relax #5\@IEEEsectpunct\mbox{}}}\fi + \@xsect{#3}} + + +%% SECTION heading spacing and font +%% +% arguments are: #1 - sectiontype name +% (for \@sect) #2 - section level +% #3 - section heading indent +% #4 - top separation (absolute value used, neg indicates not to indent main text) +% If negative, make stretch parts negative too! +% #5 - (absolute value used) positive: bottom separation after heading, +% negative: amount to indent main text after heading +% Both #4 and #5 negative means to indent main text and use negative top separation +% #6 - font control +% You've got to have \normalfont\normalsize in the font specs below to prevent +% trouble when you do something like: +% \section{Note}{\ttfamily TT-TEXT} is known to ... +% IEEE sometimes REALLY stretches the area before a section +% heading by up to about 0.5in. However, it may not be a good +% idea to let LaTeX have quite this much rubber. +\ifCLASSOPTIONconference% +% IEEE wants section heading spacing to decrease for conference mode +\def\section{\@startsection{section}{1}{\z@}{1.5ex plus 1.5ex minus 0.5ex}% +{0.7ex plus 1ex minus 0ex}{\normalfont\normalsize\centering\scshape}}% +\def\subsection{\@startsection{subsection}{2}{\z@}{1.5ex plus 1.5ex minus 0.5ex}% +{0.7ex plus .5ex minus 0ex}{\normalfont\normalsize\itshape}}% +\else % for journals +\def\section{\@startsection{section}{1}{\z@}{3.0ex plus 1.5ex minus 1.5ex}% V1.6 3.0ex from 3.5ex +{0.7ex plus 1ex minus 0ex}{\normalfont\normalsize\centering\scshape}}% +\def\subsection{\@startsection{subsection}{2}{\z@}{3.5ex plus 1.5ex minus 1.5ex}% +{0.7ex plus .5ex minus 0ex}{\normalfont\normalsize\itshape}}% +\fi + +% for both journals and conferences +% decided to put in a little rubber above the section, might help somebody +\def\subsubsection{\@startsection{subsubsection}{3}{\parindent}{0ex plus 0.1ex minus 0.1ex}% +{0ex}{\normalfont\normalsize\itshape}}% +\def\paragraph{\@startsection{paragraph}{4}{2\parindent}{0ex plus 0.1ex minus 0.1ex}% +{0ex}{\normalfont\normalsize\itshape}}% + + +% compsoc +\ifCLASSOPTIONcompsoc +\ifCLASSOPTIONconference +% compsoc conference +\def\section{\@startsection{section}{1}{\z@}{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}% +{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}{\normalfont\large\bfseries}}% +\def\subsection{\@startsection{subsection}{2}{\z@}{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}% +{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}{\normalfont\sublargesize\bfseries}}% +\def\subsubsection{\@startsection{subsubsection}{3}{\z@}{1\baselineskip plus 0.25\baselineskip minus 0.25\baselineskip}% +{0ex}{\normalfont\normalsize\bfseries}}% +\def\paragraph{\@startsection{paragraph}{4}{2\parindent}{0ex plus 0.1ex minus 0.1ex}% +{0ex}{\normalfont\normalsize}}% +\else% compsoc journals +% use negative top separation as compsoc journals do not indent paragraphs after section titles +\def\section{\@startsection{section}{1}{\z@}{-3ex plus -2ex minus -1.5ex}% +{0.7ex plus 1ex minus 0ex}{\normalfont\large\sffamily\bfseries\scshape}}% +% Note that subsection and smaller may not be correct for the Computer Society, +% I have to look up an example. +\def\subsection{\@startsection{subsection}{2}{\z@}{-3.5ex plus -1.5ex minus -1.5ex}% +{0.7ex plus .5ex minus 0ex}{\normalfont\normalsize\sffamily\bfseries}}% +\def\subsubsection{\@startsection{subsubsection}{3}{\z@}{-2.5ex plus -1ex minus -1ex}% +{0.5ex plus 0.5ex minus 0ex}{\normalfont\normalsize\sffamily\itshape}}% +\def\paragraph{\@startsection{paragraph}{4}{2\parindent}{-0ex plus -0.1ex minus -0.1ex}% +{0ex}{\normalfont\normalsize}}% +\fi\fi + + + + +%% ENVIRONMENTS +% "box" symbols at end of proofs +\def\IEEEQEDclosed{\mbox{\rule[0pt]{1.3ex}{1.3ex}}} % for a filled box +% V1.6 some journals use an open box instead that will just fit around a closed one +\def\IEEEQEDopen{{\setlength{\fboxsep}{0pt}\setlength{\fboxrule}{0.2pt}\fbox{\rule[0pt]{0pt}{1.3ex}\rule[0pt]{1.3ex}{0pt}}}} +\ifCLASSOPTIONcompsoc +\def\IEEEQED{\IEEEQEDopen} % default to open for compsoc +\else +\def\IEEEQED{\IEEEQEDclosed} % otherwise default to closed +\fi + +% v1.7 name change to avoid namespace collision with amsthm. Also add support +% for an optional argument. +\def\IEEEproof{\@ifnextchar[{\@IEEEproof}{\@IEEEproof[\IEEEproofname]}} +\def\@IEEEproof[#1]{\par\noindent\hspace{2em}{\itshape #1: }} +\def\endIEEEproof{\hspace*{\fill}~\IEEEQED\par} + + +%\itemindent is set to \z@ by list, so define new temporary variable +\newdimen\@IEEEtmpitemindent +\def\@begintheorem#1#2{\@IEEEtmpitemindent\itemindent\topsep 0pt\rmfamily\trivlist% + \item[\hskip \labelsep{\indent\itshape #1\ #2:}]\itemindent\@IEEEtmpitemindent} +\def\@opargbegintheorem#1#2#3{\@IEEEtmpitemindent\itemindent\topsep 0pt\rmfamily \trivlist% +% V1.6 IEEE is back to using () around theorem names which are also in italics +% Thanks to Christian Peel for reporting this. + \item[\hskip\labelsep{\indent\itshape #1\ #2\ (#3):}]\itemindent\@IEEEtmpitemindent} +% V1.7 remove bogus \unskip that caused equations in theorems to collide with +% lines below. +\def\@endtheorem{\endtrivlist} + +% V1.6 +% display command for the section the theorem is in - so that \thesection +% is not used as this will be in Roman numerals when we want arabic. +% LaTeX2e uses \def\@thmcounter#1{\noexpand\arabic{#1}} for the theorem number +% (second part) display and \def\@thmcountersep{.} as a separator. +% V1.7 intercept calls to the section counter and reroute to \@IEEEthmcounterinsection +% to allow \appendix(ices} to override as needed. +% +% special handler for sections, allows appendix(ices) to override +\gdef\@IEEEthmcounterinsection#1{\arabic{#1}} +% string macro +\edef\@IEEEstringsection{section} + +% redefine the #1#2[#3] form of newtheorem to use a hook to \@IEEEthmcounterinsection +% if section in_counter is used +\def\@xnthm#1#2[#3]{% + \expandafter\@ifdefinable\csname #1\endcsname + {\@definecounter{#1}\@newctr{#1}[#3]% + \edef\@IEEEstringtmp{#3} + \ifx\@IEEEstringtmp\@IEEEstringsection + \expandafter\xdef\csname the#1\endcsname{% + \noexpand\@IEEEthmcounterinsection{#3}\@thmcountersep + \@thmcounter{#1}}% + \else + \expandafter\xdef\csname the#1\endcsname{% + \expandafter\noexpand\csname the#3\endcsname \@thmcountersep + \@thmcounter{#1}}% + \fi + \global\@namedef{#1}{\@thm{#1}{#2}}% + \global\@namedef{end#1}{\@endtheorem}}} + + + +%% SET UP THE DEFAULT PAGESTYLE +\ps at headings +\pagenumbering{arabic} + +% normally the page counter starts at 1 +\setcounter{page}{1} +% however, for peerreview the cover sheet is page 0 or page -1 +% (for duplex printing) +\ifCLASSOPTIONpeerreview + \if at twoside + \setcounter{page}{-1} + \else + \setcounter{page}{0} + \fi +\fi + +% standard book class behavior - let bottom line float up and down as +% needed when single sided +\ifCLASSOPTIONtwoside\else\raggedbottom\fi +% if two column - turn on twocolumn, allow word spacings to stretch more and +% enforce a rigid position for the last lines +\ifCLASSOPTIONtwocolumn +% the peer review option delays invoking twocolumn + \ifCLASSOPTIONpeerreview\else + \twocolumn + \fi +\sloppy +\flushbottom +\fi + + + + +% \APPENDIX and \APPENDICES definitions + +% This is the \@ifmtarg command from the LaTeX ifmtarg package +% by Peter Wilson (CUA) and Donald Arseneau +% \@ifmtarg is used to determine if an argument to a command +% is present or not. +% For instance: +% \@ifmtarg{#1}{\typeout{empty}}{\typeout{has something}} +% \@ifmtarg is used with our redefined \section command if +% \appendices is invoked. +% The command \section will behave slightly differently depending +% on whether the user specifies a title: +% \section{My appendix title} +% or not: +% \section{} +% This way, we can eliminate the blank lines where the title +% would be, and the unneeded : after Appendix in the table of +% contents +\begingroup +\catcode`\Q=3 +\long\gdef\@ifmtarg#1{\@xifmtarg#1QQ\@secondoftwo\@firstoftwo\@nil} +\long\gdef\@xifmtarg#1#2Q#3#4#5\@nil{#4} +\endgroup +% end of \@ifmtarg defs + + +% V1.7 +% command that allows the one time saving of the original definition +% of section to \@IEEEappendixsavesection for \appendix or \appendices +% we don't save \section here as it may be redefined later by other +% packages (hyperref.sty, etc.) +\def\@IEEEsaveoriginalsectiononce{\let\@IEEEappendixsavesection\section +\let\@IEEEsaveoriginalsectiononce\relax} + +% neat trick to grab and process the argument from \section{argument} +% we process differently if the user invoked \section{} with no +% argument (title) +% note we reroute the call to the old \section* +\def\@IEEEprocessthesectionargument#1{% +\@ifmtarg{#1}{% +\@IEEEappendixsavesection*{\appendixname~\thesectiondis}% +\addcontentsline{toc}{section}{\appendixname~\thesection}}{% +\@IEEEappendixsavesection*{\appendixname~\thesectiondis \\* #1}% +\addcontentsline{toc}{section}{\appendixname~\thesection: #1}}} + +% we use this if the user calls \section{} after +% \appendix-- which has no meaning. So, we ignore the +% command and its argument. Then, warn the user. +\def\@IEEEdestroythesectionargument#1{\typeout{** WARNING: Ignoring useless +\protect\section\space in Appendix (line \the\inputlineno).}} + + +% remember \thesection forms will be displayed in \ref calls +% and in the Table of Contents. +% The \sectiondis form is used in the actual heading itself + +% appendix command for one single appendix +% normally has no heading. However, if you want a +% heading, you can do so via the optional argument: +% \appendix[Optional Heading] +\def\appendix{\relax} +\renewcommand{\appendix}[1][]{\@IEEEsaveoriginalsectiononce\par + % v1.6 keep hyperref's identifiers unique + \gdef\theHsection{Appendix.A}% + % v1.6 adjust hyperref's string name for the section + \xdef\Hy at chapapp{appendix}% + \setcounter{section}{0}% + \setcounter{subsection}{0}% + \setcounter{subsubsection}{0}% + \setcounter{paragraph}{0}% + \gdef\thesection{A}% + \gdef\thesectiondis{}% + \gdef\thesubsection{\Alph{subsection}}% + \gdef\@IEEEthmcounterinsection##1{A} + \refstepcounter{section}% update the \ref counter + \@ifmtarg{#1}{\@IEEEappendixsavesection*{\appendixname}% + \addcontentsline{toc}{section}{\appendixname}}{% + \@IEEEappendixsavesection*{\appendixname~\\* #1}% + \addcontentsline{toc}{section}{\appendixname: #1}}% + % redefine \section command for appendix + % leave \section* as is + \def\section{\@ifstar{\@IEEEappendixsavesection*}{% + \@IEEEdestroythesectionargument}}% throw out the argument + % of the normal form +} + + + +% appendices command for multiple appendices +% user then calls \section with an argument (possibly empty) to +% declare the individual appendices +\def\appendices{\@IEEEsaveoriginalsectiononce\par + % v1.6 keep hyperref's identifiers unique + \gdef\theHsection{Appendix.\Alph{section}}% + % v1.6 adjust hyperref's string name for the section + \xdef\Hy at chapapp{appendix}% + \setcounter{section}{-1}% we want \refstepcounter to use section 0 + \setcounter{subsection}{0}% + \setcounter{subsubsection}{0}% + \setcounter{paragraph}{0}% + \ifCLASSOPTIONromanappendices% + \gdef\thesection{\Roman{section}}% + \gdef\thesectiondis{\Roman{section}}% + \@IEEEcompsocconfonly{\gdef\thesectiondis{\Roman{section}.}}% + \gdef\@IEEEthmcounterinsection##1{A\arabic{##1}} + \else% + \gdef\thesection{\Alph{section}}% + \gdef\thesectiondis{\Alph{section}}% + \@IEEEcompsocconfonly{\gdef\thesectiondis{\Alph{section}.}}% + \gdef\@IEEEthmcounterinsection##1{\Alph{##1}} + \fi% + \refstepcounter{section}% update the \ref counter + \setcounter{section}{0}% NEXT \section will be the FIRST appendix + % redefine \section command for appendices + % leave \section* as is + \def\section{\@ifstar{\@IEEEappendixsavesection*}{% process the *-form + \refstepcounter{section}% or is a new section so, + \@IEEEprocessthesectionargument}}% process the argument + % of the normal form +} + + + +% \IEEEPARstart +% Definition for the big two line drop cap letter at the beginning of the +% first paragraph of journal papers. The first argument is the first letter +% of the first word, the second argument is the remaining letters of the +% first word which will be rendered in upper case. +% In V1.6 this has been completely rewritten to: +% +% 1. no longer have problems when the user begins an environment +% within the paragraph that uses \IEEEPARstart. +% 2. auto-detect and use the current font family +% 3. revise handling of the space at the end of the first word so that +% interword glue will now work as normal. +% 4. produce correctly aligned edges for the (two) indented lines. +% +% We generalize things via control macros - playing with these is fun too. +% +% V1.7 added more control macros to make it easy for IEEEtrantools.sty users +% to change the font style. +% +% the number of lines that are indented to clear it +% may need to increase if using decenders +\def\@IEEEPARstartDROPLINES{2} +% minimum number of lines left on a page to allow a \@IEEEPARstart +% Does not take into consideration rubber shrink, so it tends to +% be overly cautious +\def\@IEEEPARstartMINPAGELINES{2} +% V1.7 the height of the drop cap is adjusted to match the height of this text +% in the current font (when \IEEEPARstart is called). +\def\@IEEEPARstartHEIGHTTEXT{T} +% the depth the letter is lowered below the baseline +% the height (and size) of the letter is determined by the sum +% of this value and the height of the \@IEEEPARstartHEIGHTTEXT in the current +% font. It is a good idea to set this value in terms of the baselineskip +% so that it can respond to changes therein. +\def\@IEEEPARstartDROPDEPTH{1.1\baselineskip} +% V1.7 the font the drop cap will be rendered in, +% can take zero or one argument. +\def\@IEEEPARstartFONTSTYLE{\bfseries} +% V1.7 any additional, non-font related commands needed to modify +% the drop cap letter, can take zero or one argument. +\def\@IEEEPARstartCAPSTYLE{\MakeUppercase} +% V1.7 the font that will be used to render the rest of the word, +% can take zero or one argument. +\def\@IEEEPARstartWORDFONTSTYLE{\relax} +% V1.7 any additional, non-font related commands needed to modify +% the rest of the word, can take zero or one argument. +\def\@IEEEPARstartWORDCAPSTYLE{\MakeUppercase} +% This is the horizontal separation distance from the drop letter to the main text. +% Lengths that depend on the font (e.g., ex, em, etc.) will be referenced +% to the font that is active when \IEEEPARstart is called. +\def\@IEEEPARstartSEP{0.15em} +% V1.7 horizontal offset applied to the left of the drop cap. +\def\@IEEEPARstartHOFFSET{0em} +% V1.7 Italic correction command applied at the end of the drop cap. +\def\@IEEEPARstartITLCORRECT{\/} + +% V1.7 compoc uses nonbold drop cap and small caps word style +\ifCLASSOPTIONcompsoc +\def\@IEEEPARstartFONTSTYLE{\mdseries} +\def\@IEEEPARstartWORDFONTSTYLE{\scshape} +\def\@IEEEPARstartWORDCAPSTYLE{\relax} +\fi + +% definition of \IEEEPARstart +% THIS IS A CONTROLLED SPACING AREA, DO NOT ALLOW SPACES WITHIN THESE LINES +% +% The token \@IEEEPARstartfont will be globally defined after the first use +% of \IEEEPARstart and will be a font command which creates the big letter +% The first argument is the first letter of the first word and the second +% argument is the rest of the first word(s). +\def\IEEEPARstart#1#2{\par{% +% if this page does not have enough space, break it and lets start +% on a new one +\@IEEEtranneedspace{\@IEEEPARstartMINPAGELINES\baselineskip}{\relax}% +% V1.7 move this up here in case user uses \textbf for \@IEEEPARstartFONTSTYLE +% which uses command \leavevmode which causes an unwanted \indent to be issued +\noindent +% calculate the desired height of the big letter +% it extends from the top of \@IEEEPARstartHEIGHTTEXT in the current font +% down to \@IEEEPARstartDROPDEPTH below the current baseline +\settoheight{\@IEEEtrantmpdimenA}{\@IEEEPARstartHEIGHTTEXT}% +\addtolength{\@IEEEtrantmpdimenA}{\@IEEEPARstartDROPDEPTH}% +% extract the name of the current font in bold +% and place it in \@IEEEPARstartFONTNAME +\def\@IEEEPARstartGETFIRSTWORD##1 ##2\relax{##1}% +{\@IEEEPARstartFONTSTYLE{\selectfont\edef\@IEEEPARstartFONTNAMESPACE{\fontname\font\space}% +\xdef\@IEEEPARstartFONTNAME{\expandafter\@IEEEPARstartGETFIRSTWORD\@IEEEPARstartFONTNAMESPACE\relax}}}% +% define a font based on this name with a point size equal to the desired +% height of the drop letter +\font\@IEEEPARstartsubfont\@IEEEPARstartFONTNAME\space at \@IEEEtrantmpdimenA\relax% +% save this value as a counter (integer) value (sp points) +\@IEEEtrantmpcountA=\@IEEEtrantmpdimenA% +% now get the height of the actual letter produced by this font size +\settoheight{\@IEEEtrantmpdimenB}{\@IEEEPARstartsubfont\@IEEEPARstartCAPSTYLE{#1}}% +% If something bogus happens like the first argument is empty or the +% current font is strange, do not allow a zero height. +\ifdim\@IEEEtrantmpdimenB=0pt\relax% +\typeout{** WARNING: IEEEPARstart drop letter has zero height! (line \the\inputlineno)}% +\typeout{ Forcing the drop letter font size to 10pt.}% +\@IEEEtrantmpdimenB=10pt% +\fi% +% and store it as a counter +\@IEEEtrantmpcountB=\@IEEEtrantmpdimenB% +% Since a font size doesn't exactly correspond to the height of the capital +% letters in that font, the actual height of the letter, \@IEEEtrantmpcountB, +% will be less than that desired, \@IEEEtrantmpcountA +% we need to raise the font size, \@IEEEtrantmpdimenA +% by \@IEEEtrantmpcountA / \@IEEEtrantmpcountB +% But, TeX doesn't have floating point division, so we have to use integer +% division. Hence the use of the counters. +% We need to reduce the denominator so that the loss of the remainder will +% have minimal affect on the accuracy of the result +\divide\@IEEEtrantmpcountB by 200% +\divide\@IEEEtrantmpcountA by \@IEEEtrantmpcountB% +% Then reequalize things when we use TeX's ability to multiply by +% floating point values +\@IEEEtrantmpdimenB=0.005\@IEEEtrantmpdimenA% +\multiply\@IEEEtrantmpdimenB by \@IEEEtrantmpcountA% +% \@IEEEPARstartfont is globaly set to the calculated font of the big letter +% We need to carry this out of the local calculation area to to create the +% big letter. +\global\font\@IEEEPARstartfont\@IEEEPARstartFONTNAME\space at \@IEEEtrantmpdimenB% +% Now set \@IEEEtrantmpdimenA to the width of the big letter +% We need to carry this out of the local calculation area to set the +% hanging indent +\settowidth{\global\@IEEEtrantmpdimenA}{\@IEEEPARstartfont +\@IEEEPARstartCAPSTYLE{#1\@IEEEPARstartITLCORRECT}}}% +% end of the isolated calculation environment +% add in the extra clearance we want +\advance\@IEEEtrantmpdimenA by \@IEEEPARstartSEP\relax% +% add in the optional offset +\advance\@IEEEtrantmpdimenA by \@IEEEPARstartHOFFSET\relax% +% V1.7 don't allow negative offsets to produce negative hanging indents +\@IEEEtrantmpdimenB\@IEEEtrantmpdimenA +\ifnum\@IEEEtrantmpdimenB < 0 \@IEEEtrantmpdimenB 0pt\fi +% \@IEEEtrantmpdimenA has the width of the big letter plus the +% separation space and \@IEEEPARstartfont is the font we need to use +% Now, we make the letter and issue the hanging indent command +% The letter is placed in a box of zero width and height so that other +% text won't be displaced by it. +\hangindent\@IEEEtrantmpdimenB\hangafter=-\@IEEEPARstartDROPLINES% +\makebox[0pt][l]{\hspace{-\@IEEEtrantmpdimenA}% +\raisebox{-\@IEEEPARstartDROPDEPTH}[0pt][0pt]{\hspace{\@IEEEPARstartHOFFSET}% +\@IEEEPARstartfont\@IEEEPARstartCAPSTYLE{#1\@IEEEPARstartITLCORRECT}% +\hspace{\@IEEEPARstartSEP}}}% +{\@IEEEPARstartWORDFONTSTYLE{\@IEEEPARstartWORDCAPSTYLE{\selectfont#2}}}} + + + + + + +% determines if the space remaining on a given page is equal to or greater +% than the specified space of argument one +% if not, execute argument two (only if the remaining space is greater than zero) +% and issue a \newpage +% +% example: \@IEEEtranneedspace{2in}{\vfill} +% +% Does not take into consideration rubber shrinkage, so it tends to +% be overly cautious +% Based on an example posted by Donald Arseneau +% Note this macro uses \@IEEEtrantmpdimenB internally for calculations, +% so DO NOT PASS \@IEEEtrantmpdimenB to this routine +% if you need a dimen register, import with \@IEEEtrantmpdimenA instead +\def\@IEEEtranneedspace#1#2{\penalty-100\begingroup%shield temp variable +\@IEEEtrantmpdimenB\pagegoal\advance\@IEEEtrantmpdimenB-\pagetotal% space left +\ifdim #1>\@IEEEtrantmpdimenB\relax% not enough space left +\ifdim\@IEEEtrantmpdimenB>\z@\relax #2\fi% +\newpage% +\fi\endgroup} + + + +% IEEEbiography ENVIRONMENT +% Allows user to enter biography leaving place for picture (adapts to font size) +% As of V1.5, a new optional argument allows you to have a real graphic! +% V1.5 and later also fixes the "colliding biographies" which could happen when a +% biography's text was shorter than the space for the photo. +% MDS 7/2001 +% V1.6 prevent multiple biographies from making multiple TOC entries +\newif\if at IEEEbiographyTOCentrynotmade +\global\@IEEEbiographyTOCentrynotmadetrue + +% biography counter so hyperref can jump directly to the biographies +% and not just the previous section +\newcounter{IEEEbiography} +\setcounter{IEEEbiography}{0} + +% photo area size +\def\@IEEEBIOphotowidth{1.0in} % width of the biography photo area +\def\@IEEEBIOphotodepth{1.25in} % depth (height) of the biography photo area +% area cleared for photo +\def\@IEEEBIOhangwidth{1.14in} % width cleared for the biography photo area +\def\@IEEEBIOhangdepth{1.25in} % depth cleared for the biography photo area + % actual depth will be a multiple of + % \baselineskip, rounded up +\def\@IEEEBIOskipN{4\baselineskip}% nominal value of the vskip above the biography + +\newenvironment{IEEEbiography}[2][]{\normalfont\@IEEEcompsoconly{\sffamily}\footnotesize% +\unitlength 1in\parskip=0pt\par\parindent 1em\interlinepenalty500% +% we need enough space to support the hanging indent +% the nominal value of the spacer +% and one extra line for good measure +\@IEEEtrantmpdimenA=\@IEEEBIOhangdepth% +\advance\@IEEEtrantmpdimenA by \@IEEEBIOskipN% +\advance\@IEEEtrantmpdimenA by 1\baselineskip% +% if this page does not have enough space, break it and lets start +% with a new one +\@IEEEtranneedspace{\@IEEEtrantmpdimenA}{\relax}% +% nominal spacer can strech, not shrink use 1fil so user can out stretch with \vfill +\vskip \@IEEEBIOskipN plus 1fil minus 0\baselineskip% +% the default box for where the photo goes +\def\@IEEEtempbiographybox{{\setlength{\fboxsep}{0pt}\framebox{% +\begin{minipage}[b][\@IEEEBIOphotodepth][c]{\@IEEEBIOphotowidth}\centering PLACE\\ PHOTO\\ HERE \end{minipage}}}}% +% +% detect if the optional argument was supplied, this requires the +% \@ifmtarg command as defined in the appendix section above +% and if so, override the default box with what they want +\@ifmtarg{#1}{\relax}{\def\@IEEEtempbiographybox{\mbox{\begin{minipage}[b][\@IEEEBIOphotodepth][c]{\@IEEEBIOphotowidth}% +\centering% +#1% +\end{minipage}}}}% end if optional argument supplied +% Make an entry into the table of contents only if we have not done so before +\if at IEEEbiographyTOCentrynotmade% +% link labels to the biography counter so hyperref will jump +% to the biography, not the previous section +\setcounter{IEEEbiography}{-1}% +\refstepcounter{IEEEbiography}% +\addcontentsline{toc}{section}{Biographies}% +\global\@IEEEbiographyTOCentrynotmadefalse% +\fi% +% one more biography +\refstepcounter{IEEEbiography}% +% Make an entry for this name into the table of contents +\addcontentsline{toc}{subsection}{#2}% +% V1.6 properly handle if a new paragraph should occur while the +% hanging indent is still active. Do this by redefining \par so +% that it will not start a new paragraph. (But it will appear to the +% user as if it did.) Also, strip any leading pars, newlines, or spaces. +\let\@IEEEBIOORGparCMD=\par% save the original \par command +\edef\par{\hfil\break\indent}% the new \par will not be a "real" \par +\settoheight{\@IEEEtrantmpdimenA}{\@IEEEtempbiographybox}% get height of biography box +\@IEEEtrantmpdimenB=\@IEEEBIOhangdepth% +\@IEEEtrantmpcountA=\@IEEEtrantmpdimenB% countA has the hang depth +\divide\@IEEEtrantmpcountA by \baselineskip% calculates lines needed to produce the hang depth +\advance\@IEEEtrantmpcountA by 1% ensure we overestimate +% set the hanging indent +\hangindent\@IEEEBIOhangwidth% +\hangafter-\@IEEEtrantmpcountA% +% reference the top of the photo area to the top of a capital T +\settoheight{\@IEEEtrantmpdimenB}{\mbox{T}}% +% set the photo box, give it zero width and height so as not to disturb anything +\noindent\makebox[0pt][l]{\hspace{-\@IEEEBIOhangwidth}\raisebox{\@IEEEtrantmpdimenB}[0pt][0pt]{% +\raisebox{-\@IEEEBIOphotodepth}[0pt][0pt]{\@IEEEtempbiographybox}}}% +% now place the author name and begin the bio text +\noindent\textbf{#2\ }\@IEEEgobbleleadPARNLSP}{\relax\let\par=\@IEEEBIOORGparCMD\par% +% 7/2001 V1.5 detect when the biography text is shorter than the photo area +% and pad the unused area - preventing a collision from the next biography entry +% MDS +\ifnum \prevgraf <\@IEEEtrantmpcountA\relax% detect when the biography text is shorter than the photo + \advance\@IEEEtrantmpcountA by -\prevgraf% calculate how many lines we need to pad + \advance\@IEEEtrantmpcountA by -1\relax% we compensate for the fact that we indented an extra line + \@IEEEtrantmpdimenA=\baselineskip% calculate the length of the padding + \multiply\@IEEEtrantmpdimenA by \@IEEEtrantmpcountA% + \noindent\rule{0pt}{\@IEEEtrantmpdimenA}% insert an invisible support strut +\fi% +\par\normalfont} + + + +% V1.6 +% added biography without a photo environment +\newenvironment{IEEEbiographynophoto}[1]{% +% Make an entry into the table of contents only if we have not done so before +\if at IEEEbiographyTOCentrynotmade% +% link labels to the biography counter so hyperref will jump +% to the biography, not the previous section +\setcounter{IEEEbiography}{-1}% +\refstepcounter{IEEEbiography}% +\addcontentsline{toc}{section}{Biographies}% +\global\@IEEEbiographyTOCentrynotmadefalse% +\fi% +% one more biography +\refstepcounter{IEEEbiography}% +% Make an entry for this name into the table of contents +\addcontentsline{toc}{subsection}{#1}% +\normalfont\@IEEEcompsoconly{\sffamily}\footnotesize\interlinepenalty500% +\vskip 4\baselineskip plus 1fil minus 0\baselineskip% +\parskip=0pt\par% +\noindent\textbf{#1\ }\@IEEEgobbleleadPARNLSP}{\relax\par\normalfont} + + +% provide the user with some old font commands +% got this from article.cls +\DeclareOldFontCommand{\rm}{\normalfont\rmfamily}{\mathrm} +\DeclareOldFontCommand{\sf}{\normalfont\sffamily}{\mathsf} +\DeclareOldFontCommand{\tt}{\normalfont\ttfamily}{\mathtt} +\DeclareOldFontCommand{\bf}{\normalfont\bfseries}{\mathbf} +\DeclareOldFontCommand{\it}{\normalfont\itshape}{\mathit} +\DeclareOldFontCommand{\sl}{\normalfont\slshape}{\@nomath\sl} +\DeclareOldFontCommand{\sc}{\normalfont\scshape}{\@nomath\sc} +\DeclareRobustCommand*\cal{\@fontswitch\relax\mathcal} +\DeclareRobustCommand*\mit{\@fontswitch\relax\mathnormal} + + +% SPECIAL PAPER NOTICE COMMANDS +% +% holds the special notice text +\def\@IEEEspecialpapernotice{\relax} + +% for special papers, like invited papers, the user can do: +% \IEEEspecialpapernotice{(Invited Paper)} before \maketitle +\def\IEEEspecialpapernotice#1{\ifCLASSOPTIONconference% +\def\@IEEEspecialpapernotice{{\sublargesize\textit{#1}\vspace*{1em}}}% +\else% +\def\@IEEEspecialpapernotice{{\\*[1.5ex]\sublargesize\textit{#1}}\vspace*{-2ex}}% +\fi} + + + + +% PUBLISHER ID COMMANDS +% to insert a publisher's ID footer +% V1.6 \IEEEpubid has been changed so that the change in page size and style +% occurs in \maketitle. \IEEEpubid must now be issued prior to \maketitle +% use \IEEEpubidadjcol as before - in the second column of the title page +% These changes allow \maketitle to take the reduced page height into +% consideration when dynamically setting the space between the author +% names and the maintext. +% +% the amount the main text is pulled up to make room for the +% publisher's ID footer +% IEEE uses about 1.3\baselineskip for journals, +% dynamic title spacing will clean up the fraction +\def\@IEEEpubidpullup{1.3\baselineskip} +\ifCLASSOPTIONtechnote +% for technotes it must be an integer of baselineskip as there can be no +% dynamic title spacing for two column mode technotes (the title is in the +% in first column) and we should maintain an integer number of lines in the +% second column +% There are some examples (such as older issues of "Transactions on +% Information Theory") in which IEEE really pulls the text off the ID for +% technotes - about 0.55in (or 4\baselineskip). We'll use 2\baselineskip +% and call it even. +\def\@IEEEpubidpullup{2\baselineskip} +\fi + +% V1.7 compsoc does not use a pullup +\ifCLASSOPTIONcompsoc +\def\@IEEEpubidpullup{0pt} +\fi + +% holds the ID text +\def\@IEEEpubid{\relax} + +% flag so \maketitle can tell if \IEEEpubid was called +\newif\if at IEEEusingpubid +\global\@IEEEusingpubidfalse +% issue this command in the page to have the ID at the bottom +% V1.6 use before \maketitle +\def\IEEEpubid#1{\def\@IEEEpubid{#1}\global\@IEEEusingpubidtrue} + + +% command which will pull up (shorten) the column it is executed in +% to make room for the publisher ID. Place in the second column of +% the title page when using \IEEEpubid +% Is smart enough not to do anything when in single column text or +% if the user hasn't called \IEEEpubid +% currently needed in for the second column of a page with the +% publisher ID. If not needed in future releases, please provide this +% command and define it as \relax for backward compatibility +% v1.6b do not allow command to operate if the peer review option has been +% selected because \IEEEpubidadjcol will not be on the cover page. +% V1.7 do nothing if compsoc +\def\IEEEpubidadjcol{\ifCLASSOPTIONcompsoc\else\ifCLASSOPTIONpeerreview\else +\if at twocolumn\if at IEEEusingpubid\enlargethispage{-\@IEEEpubidpullup}\fi\fi\fi\fi} + +% Special thanks to Peter Wilson, Daniel Luecking, and the other +% gurus at comp.text.tex, for helping me to understand how best to +% implement the IEEEpubid command in LaTeX. + + + +%% Lockout some commands under various conditions + +% general purpose bit bucket +\newsavebox{\@IEEEtranrubishbin} + +% flags to prevent multiple warning messages +\newif\if at IEEEWARNthanks +\newif\if at IEEEWARNIEEEPARstart +\newif\if at IEEEWARNIEEEbiography +\newif\if at IEEEWARNIEEEbiographynophoto +\newif\if at IEEEWARNIEEEpubid +\newif\if at IEEEWARNIEEEpubidadjcol +\newif\if at IEEEWARNIEEEmembership +\newif\if at IEEEWARNIEEEaftertitletext +\@IEEEWARNthankstrue +\@IEEEWARNIEEEPARstarttrue +\@IEEEWARNIEEEbiographytrue +\@IEEEWARNIEEEbiographynophototrue +\@IEEEWARNIEEEpubidtrue +\@IEEEWARNIEEEpubidadjcoltrue +\@IEEEWARNIEEEmembershiptrue +\@IEEEWARNIEEEaftertitletexttrue + + +%% Lockout some commands when in various modes, but allow them to be restored if needed +%% +% save commands which might be locked out +% so that the user can later restore them if needed +\let\@IEEESAVECMDthanks\thanks +\let\@IEEESAVECMDIEEEPARstart\IEEEPARstart +\let\@IEEESAVECMDIEEEbiography\IEEEbiography +\let\@IEEESAVECMDendIEEEbiography\endIEEEbiography +\let\@IEEESAVECMDIEEEbiographynophoto\IEEEbiographynophoto +\let\@IEEESAVECMDendIEEEbiographynophoto\endIEEEbiographynophoto +\let\@IEEESAVECMDIEEEpubid\IEEEpubid +\let\@IEEESAVECMDIEEEpubidadjcol\IEEEpubidadjcol +\let\@IEEESAVECMDIEEEmembership\IEEEmembership +\let\@IEEESAVECMDIEEEaftertitletext\IEEEaftertitletext + + +% disable \IEEEPARstart when in draft mode +% This may have originally been done because the pre-V1.6 drop letter +% algorithm had problems with a non-unity baselinestretch +% At any rate, it seems too formal to have a drop letter in a draft +% paper. +\ifCLASSOPTIONdraftcls +\def\IEEEPARstart#1#2{#1#2\if at IEEEWARNIEEEPARstart\typeout{** ATTENTION: \noexpand\IEEEPARstart + is disabled in draft mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEPARstartfalse} +\fi +% and for technotes +\ifCLASSOPTIONtechnote +\def\IEEEPARstart#1#2{#1#2\if at IEEEWARNIEEEPARstart\typeout{** WARNING: \noexpand\IEEEPARstart + is locked out for technotes (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEPARstartfalse} +\fi + + +% lockout unneeded commands when in conference mode +\ifCLASSOPTIONconference +% when locked out, \thanks, \IEEEbiography, \IEEEbiographynophoto, \IEEEpubid, +% \IEEEmembership and \IEEEaftertitletext will all swallow their given text. +% \IEEEPARstart will output a normal character instead +% warn the user about these commands only once to prevent the console screen +% from filling up with redundant messages +\def\thanks#1{\if at IEEEWARNthanks\typeout{** WARNING: \noexpand\thanks + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNthanksfalse} +\def\IEEEPARstart#1#2{#1#2\if at IEEEWARNIEEEPARstart\typeout{** WARNING: \noexpand\IEEEPARstart + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEPARstartfalse} + + +% LaTeX treats environments and commands with optional arguments differently. +% the actual ("internal") command is stored as \\commandname +% (accessed via \csname\string\commandname\endcsname ) +% the "external" command \commandname is a macro with code to determine +% whether or not the optional argument is presented and to provide the +% default if it is absent. So, in order to save and restore such a command +% we would have to save and restore \\commandname as well. But, if LaTeX +% ever changes the way it names the internal names, the trick would break. +% Instead let us just define a new environment so that the internal +% name can be left undisturbed. +\newenvironment{@IEEEbogusbiography}[2][]{\if at IEEEWARNIEEEbiography\typeout{** WARNING: \noexpand\IEEEbiography + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEbiographyfalse% +\setbox\@IEEEtranrubishbin\vbox\bgroup}{\egroup\relax} +% and make biography point to our bogus biography +\let\IEEEbiography=\@IEEEbogusbiography +\let\endIEEEbiography=\end at IEEEbogusbiography + +\renewenvironment{IEEEbiographynophoto}[1]{\if at IEEEWARNIEEEbiographynophoto\typeout{** WARNING: \noexpand\IEEEbiographynophoto + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEbiographynophotofalse% +\setbox\@IEEEtranrubishbin\vbox\bgroup}{\egroup\relax} + +\def\IEEEpubid#1{\if at IEEEWARNIEEEpubid\typeout{** WARNING: \noexpand\IEEEpubid + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEpubidfalse} +\def\IEEEpubidadjcol{\if at IEEEWARNIEEEpubidadjcol\typeout{** WARNING: \noexpand\IEEEpubidadjcol + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEpubidadjcolfalse} +\def\IEEEmembership#1{\if at IEEEWARNIEEEmembership\typeout{** WARNING: \noexpand\IEEEmembership + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEmembershipfalse} +\def\IEEEaftertitletext#1{\if at IEEEWARNIEEEaftertitletext\typeout{** WARNING: \noexpand\IEEEaftertitletext + is locked out when in conference mode (line \the\inputlineno).}\fi\global\@IEEEWARNIEEEaftertitletextfalse} +\fi + + +% provide a way to restore the commands that are locked out +\def\IEEEoverridecommandlockouts{% +\typeout{** ATTENTION: Overriding command lockouts (line \the\inputlineno).}% +\let\thanks\@IEEESAVECMDthanks% +\let\IEEEPARstart\@IEEESAVECMDIEEEPARstart% +\let\IEEEbiography\@IEEESAVECMDIEEEbiography% +\let\endIEEEbiography\@IEEESAVECMDendIEEEbiography% +\let\IEEEbiographynophoto\@IEEESAVECMDIEEEbiographynophoto% +\let\endIEEEbiographynophoto\@IEEESAVECMDendIEEEbiographynophoto% +\let\IEEEpubid\@IEEESAVECMDIEEEpubid% +\let\IEEEpubidadjcol\@IEEESAVECMDIEEEpubidadjcol% +\let\IEEEmembership\@IEEESAVECMDIEEEmembership% +\let\IEEEaftertitletext\@IEEESAVECMDIEEEaftertitletext} + + + +% need a backslash character for typeout output +{\catcode`\|=0 \catcode`\\=12 +|xdef|@IEEEbackslash{\}} + + +% hook to allow easy disabling of all legacy warnings +\def\@IEEElegacywarn#1#2{\typeout{** ATTENTION: \@IEEEbackslash #1 is deprecated (line \the\inputlineno). +Use \@IEEEbackslash #2 instead.}} + + +% provide for legacy commands +\def\authorblockA{\@IEEElegacywarn{authorblockA}{IEEEauthorblockA}\IEEEauthorblockA} +\def\authorblockN{\@IEEElegacywarn{authorblockN}{IEEEauthorblockN}\IEEEauthorblockN} +\def\authorrefmark{\@IEEElegacywarn{authorrefmark}{IEEEauthorrefmark}\IEEEauthorrefmark} +\def\PARstart{\@IEEElegacywarn{PARstart}{IEEEPARstart}\IEEEPARstart} +\def\pubid{\@IEEElegacywarn{pubid}{IEEEpubid}\IEEEpubid} +\def\pubidadjcol{\@IEEElegacywarn{pubidadjcol}{IEEEpubidadjcol}\IEEEpubidadjcol} +\def\QED{\@IEEElegacywarn{QED}{IEEEQED}\IEEEQED} +\def\QEDclosed{\@IEEElegacywarn{QEDclosed}{IEEEQEDclosed}\IEEEQEDclosed} +\def\QEDopen{\@IEEElegacywarn{QEDopen}{IEEEQEDopen}\IEEEQEDopen} +\def\specialpapernotice{\@IEEElegacywarn{specialpapernotice}{IEEEspecialpapernotice}\IEEEspecialpapernotice} + + + +% provide for legacy environments +\def\biography{\@IEEElegacywarn{biography}{IEEEbiography}\IEEEbiography} +\def\biographynophoto{\@IEEElegacywarn{biographynophoto}{IEEEbiographynophoto}\IEEEbiographynophoto} +\def\keywords{\@IEEElegacywarn{keywords}{IEEEkeywords}\IEEEkeywords} +\def\endbiography{\endIEEEbiography} +\def\endbiographynophoto{\endIEEEbiographynophoto} +\def\endkeywords{\endIEEEkeywords} + + +% provide for legacy IED commands/lengths when possible +\let\labelindent\IEEElabelindent +\def\calcleftmargin{\@IEEElegacywarn{calcleftmargin}{IEEEcalcleftmargin}\IEEEcalcleftmargin} +\def\setlabelwidth{\@IEEElegacywarn{setlabelwidth}{IEEEsetlabelwidth}\IEEEsetlabelwidth} +\def\usemathlabelsep{\@IEEElegacywarn{usemathlabelsep}{IEEEusemathlabelsep}\IEEEusemathlabelsep} +\def\iedlabeljustifyc{\@IEEElegacywarn{iedlabeljustifyc}{IEEEiedlabeljustifyc}\IEEEiedlabeljustifyc} +\def\iedlabeljustifyl{\@IEEElegacywarn{iedlabeljustifyl}{IEEEiedlabeljustifyl}\IEEEiedlabeljustifyl} +\def\iedlabeljustifyr{\@IEEElegacywarn{iedlabeljustifyr}{IEEEiedlabeljustifyr}\IEEEiedlabeljustifyr} + + + +% let \proof use the IEEEtran version even after amsthm is loaded +% \proof is now deprecated in favor of \IEEEproof +\AtBeginDocument{\def\proof{\@IEEElegacywarn{proof}{IEEEproof}\IEEEproof}\def\endproof{\endIEEEproof}} + +% V1.7 \overrideIEEEmargins is no longer supported. +\def\overrideIEEEmargins{% +\typeout{** WARNING: \string\overrideIEEEmargins \space no longer supported (line \the\inputlineno).}% +\typeout{** Use the \string\CLASSINPUTinnersidemargin, \string\CLASSINPUToutersidemargin \space controls instead.}} + + +\endinput + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% End of IEEEtran.cls %%%%%%%%%%%%%%%%%%%%%%%%%%%% +% That's all folks! + Added: text/escience11submission/IEEEtran2.tar.gz =================================================================== (Binary files differ) Property changes on: text/escience11submission/IEEEtran2.tar.gz ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: text/escience11submission/IEEEtranBST1.tar.gz =================================================================== (Binary files differ) Property changes on: text/escience11submission/IEEEtranBST1.tar.gz ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: text/escience11submission/IEEEtranS.bst =================================================================== --- text/escience11submission/IEEEtranS.bst (rev 0) +++ text/escience11submission/IEEEtranS.bst 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,2607 @@ +%% +%% IEEEtranS.bst +%% BibTeX Bibliography Style file +%% Sorting version of IEEEtran.bst +%% *** Not for normal IEEE work *** +%% Version 1.12 (2007/01/11) +%% +%% Copyright (c) 2003-2007 Michael Shell +%% +%% Original starting code base and algorithms obtained from the output of +%% Patrick W. Daly's makebst package as well as from prior versions of +%% IEEE BibTeX styles: +%% +%% 1. Howard Trickey and Oren Patashnik's ieeetr.bst (1985/1988) +%% 2. Silvano Balemi and Richard H. Roy's IEEEbib.bst (1993) +%% +%% Added sorting code is from plain.bst. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and/or +%% http://www.ieee.org/ +%% +%% For use with BibTeX version 0.99a or later +%% +%% This is a numerical citation style. +%% +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEabrv.bib, IEEEfull.bib, IEEEexample.bib, +%% IEEEtran.bst, IEEEtranS.bst, IEEEtranSA.bst, +%% IEEEtranN.bst, IEEEtranSN.bst, IEEEtran_bst_HOWTO.pdf +%%************************************************************************* +% +% +% Changelog: +% +% 1.10 (2002/09/27) Initial release +% +% 1.11 (2003/04/02) +% 1. Fixed bug with URLs containing underscores when using url.sty. Thanks +% to Ming Kin Lai for reporting this. +% +% 1.12 (2007/01/11) +% 1. Fixed bug with unwanted comma before "et al." when an entry contained +% more than two author names. Thanks to Pallav Gupta for reporting this. +% 2. Fixed bug with anomalous closing quote in tech reports that have a +% type, but without a number or address. Thanks to Mehrdad Mirreza for +% reporting this. +% 3. Use braces in \providecommand in begin.bib to better support +% latex2html. TeX style length assignments OK with recent versions +% of latex2html - 1.71 (2002/2/1) or later is strongly recommended. +% Use of the language field still causes trouble with latex2html. +% Thanks to Federico Beffa for reporting this. +% 4. Added IEEEtran.bst ID and version comment string to .bbl output. +% 5. Provide a \BIBdecl hook that allows the user to execute commands +% just prior to the first entry. +% 6. Use default urlstyle (is using url.sty) of "same" rather than rm to +% better work with a wider variety of bibliography styles. +% 7. Changed month abbreviations from Sept., July and June to Sep., Jul., +% and Jun., respectively, as IEEE now does. Thanks to Moritz Borgmann +% for reporting this. +% 8. Control entry types should not be considered when calculating longest +% label width. +% 9. Added alias www for electronic/online. +% 10. Added CTLname_url_prefix control entry type. + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% DEFAULTS FOR THE CONTROLS OF THE BST STYLE %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +% These are the defaults for the user adjustable controls. The values used +% here can be overridden by the user via IEEEtranBSTCTL entry type. + +% NOTE: The recommended LaTeX command to invoke a control entry type is: +% +%\makeatletter +%\def\bstctlcite{\@ifnextchar[{\@bstctlcite}{\@bstctlcite[@auxout]}} +%\def\@bstctlcite[#1]#2{\@bsphack +% \@for\@citeb:=#2\do{% +% \edef\@citeb{\expandafter\@firstofone\@citeb}% +% \if at filesw\immediate\write\csname #1\endcsname{\string\citation{\@citeb}}\fi}% +% \@esphack} +%\makeatother +% +% It is called at the start of the document, before the first \cite, like: +% \bstctlcite{IEEEexample:BSTcontrol} +% +% IEEEtran.cls V1.6 and later does provide this command. + + + +% #0 turns off the display of the number for articles. +% #1 enables +FUNCTION {default.is.use.number.for.article} { #1 } + + +% #0 turns off the display of the paper and type fields in @inproceedings. +% #1 enables +FUNCTION {default.is.use.paper} { #1 } + + +% #0 turns off the forced use of "et al." +% #1 enables +FUNCTION {default.is.forced.et.al} { #0 } + +% The maximum number of names that can be present beyond which an "et al." +% usage is forced. Be sure that num.names.shown.with.forced.et.al (below) +% is not greater than this value! +% Note: There are many instances of references in IEEE journals which have +% a very large number of authors as well as instances in which "et al." is +% used profusely. +FUNCTION {default.max.num.names.before.forced.et.al} { #10 } + +% The number of names that will be shown with a forced "et al.". +% Must be less than or equal to max.num.names.before.forced.et.al +FUNCTION {default.num.names.shown.with.forced.et.al} { #1 } + + +% #0 turns off the alternate interword spacing for entries with URLs. +% #1 enables +FUNCTION {default.is.use.alt.interword.spacing} { #1 } + +% If alternate interword spacing for entries with URLs is enabled, this is +% the interword spacing stretch factor that will be used. For example, the +% default "4" here means that the interword spacing in entries with URLs can +% stretch to four times normal. Does not have to be an integer. Note that +% the value specified here can be overridden by the user in their LaTeX +% code via a command such as: +% "\providecommand\BIBentryALTinterwordstretchfactor{1.5}" in addition to +% that via the IEEEtranBSTCTL entry type. +FUNCTION {default.ALTinterwordstretchfactor} { "4" } + + +% #0 turns off the "dashification" of repeated (i.e., identical to those +% of the previous entry) names. IEEE normally does this. +% #1 enables +FUNCTION {default.is.dash.repeated.names} { #1 } + + +% The default name format control string. +FUNCTION {default.name.format.string}{ "{f.~}{vv~}{ll}{, jj}" } + + +% The default LaTeX font command for the names. +FUNCTION {default.name.latex.cmd}{ "" } + + +% The default URL prefix. +FUNCTION {default.name.url.prefix}{ "[Online]. Available:" } + + +% Other controls that cannot be accessed via IEEEtranBSTCTL entry type. + +% #0 turns off the terminal startup banner/completed message so as to +% operate more quietly. +% #1 enables +FUNCTION {is.print.banners.to.terminal} { #1 } + + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% FILE VERSION AND BANNER %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION{bst.file.version} { "1.12" } +FUNCTION{bst.file.date} { "2007/01/11" } +FUNCTION{bst.file.website} { "http://www.michaelshell.org/tex/ieeetran/bibtex/" } + +FUNCTION {banner.message} +{ is.print.banners.to.terminal + { "-- IEEEtranS.bst version" " " * bst.file.version * + " (" * bst.file.date * ") " * "by Michael Shell." * + top$ + "-- " bst.file.website * + top$ + "-- See the " quote$ * "IEEEtran_bst_HOWTO.pdf" * quote$ * " manual for usage information." * + top$ + "** Sorting version - not for normal IEEE work." + top$ + } + { skip$ } + if$ +} + +FUNCTION {completed.message} +{ is.print.banners.to.terminal + { "" + top$ + "Done." + top$ + } + { skip$ } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%% +%% STRING CONSTANTS %% +%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {bbl.and}{ "and" } +FUNCTION {bbl.etal}{ "et~al." } +FUNCTION {bbl.editors}{ "eds." } +FUNCTION {bbl.editor}{ "ed." } +FUNCTION {bbl.edition}{ "ed." } +FUNCTION {bbl.volume}{ "vol." } +FUNCTION {bbl.of}{ "of" } +FUNCTION {bbl.number}{ "no." } +FUNCTION {bbl.in}{ "in" } +FUNCTION {bbl.pages}{ "pp." } +FUNCTION {bbl.page}{ "p." } +FUNCTION {bbl.chapter}{ "ch." } +FUNCTION {bbl.paper}{ "paper" } +FUNCTION {bbl.part}{ "pt." } +FUNCTION {bbl.patent}{ "Patent" } +FUNCTION {bbl.patentUS}{ "U.S." } +FUNCTION {bbl.revision}{ "Rev." } +FUNCTION {bbl.series}{ "ser." } +FUNCTION {bbl.standard}{ "Std." } +FUNCTION {bbl.techrep}{ "Tech. Rep." } +FUNCTION {bbl.mthesis}{ "Master's thesis" } +FUNCTION {bbl.phdthesis}{ "Ph.D. dissertation" } +FUNCTION {bbl.st}{ "st" } +FUNCTION {bbl.nd}{ "nd" } +FUNCTION {bbl.rd}{ "rd" } +FUNCTION {bbl.th}{ "th" } + + +% This is the LaTeX spacer that is used when a larger than normal space +% is called for (such as just before the address:publisher). +FUNCTION {large.space} { "\hskip 1em plus 0.5em minus 0.4em\relax " } + +% The LaTeX code for dashes that are used to represent repeated names. +% Note: Some older IEEE journals used something like +% "\rule{0.275in}{0.5pt}\," which is fairly thick and runs right along +% the baseline. However, IEEE now uses a thinner, above baseline, +% six dash long sequence. +FUNCTION {repeated.name.dashes} { "------" } + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% PREDEFINED STRING MACROS %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +MACRO {jan} {"Jan."} +MACRO {feb} {"Feb."} +MACRO {mar} {"Mar."} +MACRO {apr} {"Apr."} +MACRO {may} {"May"} +MACRO {jun} {"Jun."} +MACRO {jul} {"Jul."} +MACRO {aug} {"Aug."} +MACRO {sep} {"Sep."} +MACRO {oct} {"Oct."} +MACRO {nov} {"Nov."} +MACRO {dec} {"Dec."} + + + +%%%%%%%%%%%%%%%%%% +%% ENTRY FIELDS %% +%%%%%%%%%%%%%%%%%% + +ENTRY + { address + assignee + author + booktitle + chapter + day + dayfiled + edition + editor + howpublished + institution + intype + journal + key + language + month + monthfiled + nationality + note + number + organization + pages + paper + publisher + school + series + revision + title + type + url + volume + year + yearfiled + CTLuse_article_number + CTLuse_paper + CTLuse_forced_etal + CTLmax_names_forced_etal + CTLnames_show_etal + CTLuse_alt_spacing + CTLalt_stretch_factor + CTLdash_repeated_names + CTLname_format_string + CTLname_latex_cmd + CTLname_url_prefix + } + {} + { label } + + + + +%%%%%%%%%%%%%%%%%%%%%%% +%% INTEGER VARIABLES %% +%%%%%%%%%%%%%%%%%%%%%%% + +INTEGERS { prev.status.punct this.status.punct punct.std + punct.no punct.comma punct.period + prev.status.space this.status.space space.std + space.no space.normal space.large + prev.status.quote this.status.quote quote.std + quote.no quote.close + prev.status.nline this.status.nline nline.std + nline.no nline.newblock + status.cap cap.std + cap.no cap.yes} + +INTEGERS { longest.label.width multiresult nameptr namesleft number.label numnames } + +INTEGERS { is.use.number.for.article + is.use.paper + is.forced.et.al + max.num.names.before.forced.et.al + num.names.shown.with.forced.et.al + is.use.alt.interword.spacing + is.dash.repeated.names} + + +%%%%%%%%%%%%%%%%%%%%%% +%% STRING VARIABLES %% +%%%%%%%%%%%%%%%%%%%%%% + +STRINGS { bibinfo + longest.label + oldname + s + t + ALTinterwordstretchfactor + name.format.string + name.latex.cmd + name.url.prefix} + + + + +%%%%%%%%%%%%%%%%%%%%%%%%% +%% LOW LEVEL FUNCTIONS %% +%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {initialize.controls} +{ default.is.use.number.for.article 'is.use.number.for.article := + default.is.use.paper 'is.use.paper := + default.is.forced.et.al 'is.forced.et.al := + default.max.num.names.before.forced.et.al 'max.num.names.before.forced.et.al := + default.num.names.shown.with.forced.et.al 'num.names.shown.with.forced.et.al := + default.is.use.alt.interword.spacing 'is.use.alt.interword.spacing := + default.is.dash.repeated.names 'is.dash.repeated.names := + default.ALTinterwordstretchfactor 'ALTinterwordstretchfactor := + default.name.format.string 'name.format.string := + default.name.latex.cmd 'name.latex.cmd := + default.name.url.prefix 'name.url.prefix := +} + + +% This IEEEtran.bst features a very powerful and flexible mechanism for +% controlling the capitalization, punctuation, spacing, quotation, and +% newlines of the formatted entry fields. (Note: IEEEtran.bst does not need +% or use the newline/newblock feature, but it has been implemented for +% possible future use.) The output states of IEEEtran.bst consist of +% multiple independent attributes and, as such, can be thought of as being +% vectors, rather than the simple scalar values ("before.all", +% "mid.sentence", etc.) used in most other .bst files. +% +% The more flexible and complex design used here was motivated in part by +% IEEE's rather unusual bibliography style. For example, IEEE ends the +% previous field item with a period and large space prior to the publisher +% address; the @electronic entry types use periods as inter-item punctuation +% rather than the commas used by the other entry types; and URLs are never +% followed by periods even though they are the last item in the entry. +% Although it is possible to accommodate these features with the conventional +% output state system, the seemingly endless exceptions make for convoluted, +% unreliable and difficult to maintain code. +% +% IEEEtran.bst's output state system can be easily understood via a simple +% illustration of two most recently formatted entry fields (on the stack): +% +% CURRENT_ITEM +% "PREVIOUS_ITEM +% +% which, in this example, is to eventually appear in the bibliography as: +% +% "PREVIOUS_ITEM," CURRENT_ITEM +% +% It is the job of the output routine to take the previous item off of the +% stack (while leaving the current item at the top of the stack), apply its +% trailing punctuation (including closing quote marks) and spacing, and then +% to write the result to BibTeX's output buffer: +% +% "PREVIOUS_ITEM," +% +% Punctuation (and spacing) between items is often determined by both of the +% items rather than just the first one. The presence of quotation marks +% further complicates the situation because, in standard English, trailing +% punctuation marks are supposed to be contained within the quotes. +% +% IEEEtran.bst maintains two output state (aka "status") vectors which +% correspond to the previous and current (aka "this") items. Each vector +% consists of several independent attributes which track punctuation, +% spacing, quotation, and newlines. Capitalization status is handled by a +% separate scalar because the format routines, not the output routine, +% handle capitalization and, therefore, there is no need to maintain the +% capitalization attribute for both the "previous" and "this" items. +% +% When a format routine adds a new item, it copies the current output status +% vector to the previous output status vector and (usually) resets the +% current (this) output status vector to a "standard status" vector. Using a +% "standard status" vector in this way allows us to redefine what we mean by +% "standard status" at the start of each entry handler and reuse the same +% format routines under the various inter-item separation schemes. For +% example, the standard status vector for the @book entry type may use +% commas for item separators, while the @electronic type may use periods, +% yet both entry handlers exploit many of the exact same format routines. +% +% Because format routines have write access to the output status vector of +% the previous item, they can override the punctuation choices of the +% previous format routine! Therefore, it becomes trivial to implement rules +% such as "Always use a period and a large space before the publisher." By +% pushing the generation of the closing quote mark to the output routine, we +% avoid all the problems caused by having to close a quote before having all +% the information required to determine what the punctuation should be. +% +% The IEEEtran.bst output state system can easily be expanded if needed. +% For instance, it is easy to add a "space.tie" attribute value if the +% bibliography rules mandate that two items have to be joined with an +% unbreakable space. + +FUNCTION {initialize.status.constants} +{ #0 'punct.no := + #1 'punct.comma := + #2 'punct.period := + #0 'space.no := + #1 'space.normal := + #2 'space.large := + #0 'quote.no := + #1 'quote.close := + #0 'cap.no := + #1 'cap.yes := + #0 'nline.no := + #1 'nline.newblock := +} + +FUNCTION {std.status.using.comma} +{ punct.comma 'punct.std := + space.normal 'space.std := + quote.no 'quote.std := + nline.no 'nline.std := + cap.no 'cap.std := +} + +FUNCTION {std.status.using.period} +{ punct.period 'punct.std := + space.normal 'space.std := + quote.no 'quote.std := + nline.no 'nline.std := + cap.yes 'cap.std := +} + +FUNCTION {initialize.prev.this.status} +{ punct.no 'prev.status.punct := + space.no 'prev.status.space := + quote.no 'prev.status.quote := + nline.no 'prev.status.nline := + punct.no 'this.status.punct := + space.no 'this.status.space := + quote.no 'this.status.quote := + nline.no 'this.status.nline := + cap.yes 'status.cap := +} + +FUNCTION {this.status.std} +{ punct.std 'this.status.punct := + space.std 'this.status.space := + quote.std 'this.status.quote := + nline.std 'this.status.nline := +} + +FUNCTION {cap.status.std}{ cap.std 'status.cap := } + +FUNCTION {this.to.prev.status} +{ this.status.punct 'prev.status.punct := + this.status.space 'prev.status.space := + this.status.quote 'prev.status.quote := + this.status.nline 'prev.status.nline := +} + + +FUNCTION {not} +{ { #0 } + { #1 } + if$ +} + +FUNCTION {and} +{ { skip$ } + { pop$ #0 } + if$ +} + +FUNCTION {or} +{ { pop$ #1 } + { skip$ } + if$ +} + + +% convert the strings "yes" or "no" to #1 or #0 respectively +FUNCTION {yes.no.to.int} +{ "l" change.case$ duplicate$ + "yes" = + { pop$ #1 } + { duplicate$ "no" = + { pop$ #0 } + { "unknown boolean " quote$ * swap$ * quote$ * + " in " * cite$ * warning$ + #0 + } + if$ + } + if$ +} + + +% pushes true if the single char string on the stack is in the +% range of "0" to "9" +FUNCTION {is.num} +{ chr.to.int$ + duplicate$ "0" chr.to.int$ < not + swap$ "9" chr.to.int$ > not and +} + +% multiplies the integer on the stack by a factor of 10 +FUNCTION {bump.int.mag} +{ #0 'multiresult := + { duplicate$ #0 > } + { #1 - + multiresult #10 + + 'multiresult := + } + while$ +pop$ +multiresult +} + +% converts a single character string on the stack to an integer +FUNCTION {char.to.integer} +{ duplicate$ + is.num + { chr.to.int$ "0" chr.to.int$ - } + {"noninteger character " quote$ * swap$ * quote$ * + " in integer field of " * cite$ * warning$ + #0 + } + if$ +} + +% converts a string on the stack to an integer +FUNCTION {string.to.integer} +{ duplicate$ text.length$ 'namesleft := + #1 'nameptr := + #0 'numnames := + { nameptr namesleft > not } + { duplicate$ nameptr #1 substring$ + char.to.integer numnames bump.int.mag + + 'numnames := + nameptr #1 + + 'nameptr := + } + while$ +pop$ +numnames +} + + + + +% The output routines write out the *next* to the top (previous) item on the +% stack, adding punctuation and such as needed. Since IEEEtran.bst maintains +% the output status for the top two items on the stack, these output +% routines have to consider the previous output status (which corresponds to +% the item that is being output). Full independent control of punctuation, +% closing quote marks, spacing, and newblock is provided. +% +% "output.nonnull" does not check for the presence of a previous empty +% item. +% +% "output" does check for the presence of a previous empty item and will +% remove an empty item rather than outputing it. +% +% "output.warn" is like "output", but will issue a warning if it detects +% an empty item. + +FUNCTION {output.nonnull} +{ swap$ + prev.status.punct punct.comma = + { "," * } + { skip$ } + if$ + prev.status.punct punct.period = + { add.period$ } + { skip$ } + if$ + prev.status.quote quote.close = + { "''" * } + { skip$ } + if$ + prev.status.space space.normal = + { " " * } + { skip$ } + if$ + prev.status.space space.large = + { large.space * } + { skip$ } + if$ + write$ + prev.status.nline nline.newblock = + { newline$ "\newblock " write$ } + { skip$ } + if$ +} + +FUNCTION {output} +{ duplicate$ empty$ + 'pop$ + 'output.nonnull + if$ +} + +FUNCTION {output.warn} +{ 't := + duplicate$ empty$ + { pop$ "empty " t * " in " * cite$ * warning$ } + 'output.nonnull + if$ +} + +% "fin.entry" is the output routine that handles the last item of the entry +% (which will be on the top of the stack when "fin.entry" is called). + +FUNCTION {fin.entry} +{ this.status.punct punct.no = + { skip$ } + { add.period$ } + if$ + this.status.quote quote.close = + { "''" * } + { skip$ } + if$ +write$ +newline$ +} + + +FUNCTION {is.last.char.not.punct} +{ duplicate$ + "}" * add.period$ + #-1 #1 substring$ "." = +} + +FUNCTION {is.multiple.pages} +{ 't := + #0 'multiresult := + { multiresult not + t empty$ not + and + } + { t #1 #1 substring$ + duplicate$ "-" = + swap$ duplicate$ "," = + swap$ "+" = + or or + { #1 'multiresult := } + { t #2 global.max$ substring$ 't := } + if$ + } + while$ + multiresult +} + +FUNCTION {capitalize}{ "u" change.case$ "t" change.case$ } + +FUNCTION {emphasize} +{ duplicate$ empty$ + { pop$ "" } + { "\emph{" swap$ * "}" * } + if$ +} + +FUNCTION {do.name.latex.cmd} +{ name.latex.cmd + empty$ + { skip$ } + { name.latex.cmd "{" * swap$ * "}" * } + if$ +} + +% IEEEtran.bst uses its own \BIBforeignlanguage command which directly +% invokes the TeX hyphenation patterns without the need of the Babel +% package. Babel does a lot more than switch hyphenation patterns and +% its loading can cause unintended effects in many class files (such as +% IEEEtran.cls). +FUNCTION {select.language} +{ duplicate$ empty$ 'pop$ + { language empty$ 'skip$ + { "\BIBforeignlanguage{" language * "}{" * swap$ * "}" * } + if$ + } + if$ +} + +FUNCTION {tie.or.space.prefix} +{ duplicate$ text.length$ #3 < + { "~" } + { " " } + if$ + swap$ +} + +FUNCTION {get.bbl.editor} +{ editor num.names$ #1 > 'bbl.editors 'bbl.editor if$ } + +FUNCTION {space.word}{ " " swap$ * " " * } + + +% Field Conditioners, Converters, Checkers and External Interfaces + +FUNCTION {empty.field.to.null.string} +{ duplicate$ empty$ + { pop$ "" } + { skip$ } + if$ +} + +FUNCTION {either.or.check} +{ empty$ + { pop$ } + { "can't use both " swap$ * " fields in " * cite$ * warning$ } + if$ +} + +FUNCTION {empty.entry.warn} +{ author empty$ title empty$ howpublished empty$ + month empty$ year empty$ note empty$ url empty$ + and and and and and and + { "all relevant fields are empty in " cite$ * warning$ } + 'skip$ + if$ +} + + +% The bibinfo system provides a way for the electronic parsing/acquisition +% of a bibliography's contents as is done by ReVTeX. For example, a field +% could be entered into the bibliography as: +% \bibinfo{volume}{2} +% Only the "2" would show up in the document, but the LaTeX \bibinfo command +% could do additional things with the information. IEEEtran.bst does provide +% a \bibinfo command via "\providecommand{\bibinfo}[2]{#2}". However, it is +% currently not used as the bogus bibinfo functions defined here output the +% entry values directly without the \bibinfo wrapper. The bibinfo functions +% themselves (and the calls to them) are retained for possible future use. +% +% bibinfo.check avoids acting on missing fields while bibinfo.warn will +% issue a warning message if a missing field is detected. Prior to calling +% the bibinfo functions, the user should push the field value and then its +% name string, in that order. + +FUNCTION {bibinfo.check} +{ swap$ duplicate$ missing$ + { pop$ pop$ "" } + { duplicate$ empty$ + { swap$ pop$ } + { swap$ pop$ } + if$ + } + if$ +} + +FUNCTION {bibinfo.warn} +{ swap$ duplicate$ missing$ + { swap$ "missing " swap$ * " in " * cite$ * warning$ pop$ "" } + { duplicate$ empty$ + { swap$ "empty " swap$ * " in " * cite$ * warning$ } + { swap$ pop$ } + if$ + } + if$ +} + + +% IEEE separates large numbers with more than 4 digits into groups of +% three. IEEE uses a small space to separate these number groups. +% Typical applications include patent and page numbers. + +% number of consecutive digits required to trigger the group separation. +FUNCTION {large.number.trigger}{ #5 } + +% For numbers longer than the trigger, this is the blocksize of the groups. +% The blocksize must be less than the trigger threshold, and 2 * blocksize +% must be greater than the trigger threshold (can't do more than one +% separation on the initial trigger). +FUNCTION {large.number.blocksize}{ #3 } + +% What is actually inserted between the number groups. +FUNCTION {large.number.separator}{ "\," } + +% So as to save on integer variables by reusing existing ones, numnames +% holds the current number of consecutive digits read and nameptr holds +% the number that will trigger an inserted space. +FUNCTION {large.number.separate} +{ 't := + "" + #0 'numnames := + large.number.trigger 'nameptr := + { t empty$ not } + { t #-1 #1 substring$ is.num + { numnames #1 + 'numnames := } + { #0 'numnames := + large.number.trigger 'nameptr := + } + if$ + t #-1 #1 substring$ swap$ * + t #-2 global.max$ substring$ 't := + numnames nameptr = + { duplicate$ #1 nameptr large.number.blocksize - substring$ swap$ + nameptr large.number.blocksize - #1 + global.max$ substring$ + large.number.separator swap$ * * + nameptr large.number.blocksize - 'numnames := + large.number.blocksize #1 + 'nameptr := + } + { skip$ } + if$ + } + while$ +} + +% Converts all single dashes "-" to double dashes "--". +FUNCTION {n.dashify} +{ large.number.separate + 't := + "" + { t empty$ not } + { t #1 #1 substring$ "-" = + { t #1 #2 substring$ "--" = not + { "--" * + t #2 global.max$ substring$ 't := + } + { { t #1 #1 substring$ "-" = } + { "-" * + t #2 global.max$ substring$ 't := + } + while$ + } + if$ + } + { t #1 #1 substring$ * + t #2 global.max$ substring$ 't := + } + if$ + } + while$ +} + + +% This function detects entries with names that are identical to that of +% the previous entry and replaces the repeated names with dashes (if the +% "is.dash.repeated.names" user control is nonzero). +FUNCTION {name.or.dash} +{ 's := + oldname empty$ + { s 'oldname := s } + { s oldname = + { is.dash.repeated.names + { repeated.name.dashes } + { s 'oldname := s } + if$ + } + { s 'oldname := s } + if$ + } + if$ +} + +% Converts the number string on the top of the stack to +% "numerical ordinal form" (e.g., "7" to "7th"). There is +% no artificial limit to the upper bound of the numbers as the +% least significant digit always determines the ordinal form. +FUNCTION {num.to.ordinal} +{ duplicate$ #-1 #1 substring$ "1" = + { bbl.st * } + { duplicate$ #-1 #1 substring$ "2" = + { bbl.nd * } + { duplicate$ #-1 #1 substring$ "3" = + { bbl.rd * } + { bbl.th * } + if$ + } + if$ + } + if$ +} + +% If the string on the top of the stack begins with a number, +% (e.g., 11th) then replace the string with the leading number +% it contains. Otherwise retain the string as-is. s holds the +% extracted number, t holds the part of the string that remains +% to be scanned. +FUNCTION {extract.num} +{ duplicate$ 't := + "" 's := + { t empty$ not } + { t #1 #1 substring$ + t #2 global.max$ substring$ 't := + duplicate$ is.num + { s swap$ * 's := } + { pop$ "" 't := } + if$ + } + while$ + s empty$ + 'skip$ + { pop$ s } + if$ +} + +% Converts the word number string on the top of the stack to +% Arabic string form. Will be successful up to "tenth". +FUNCTION {word.to.num} +{ duplicate$ "l" change.case$ 's := + s "first" = + { pop$ "1" } + { skip$ } + if$ + s "second" = + { pop$ "2" } + { skip$ } + if$ + s "third" = + { pop$ "3" } + { skip$ } + if$ + s "fourth" = + { pop$ "4" } + { skip$ } + if$ + s "fifth" = + { pop$ "5" } + { skip$ } + if$ + s "sixth" = + { pop$ "6" } + { skip$ } + if$ + s "seventh" = + { pop$ "7" } + { skip$ } + if$ + s "eighth" = + { pop$ "8" } + { skip$ } + if$ + s "ninth" = + { pop$ "9" } + { skip$ } + if$ + s "tenth" = + { pop$ "10" } + { skip$ } + if$ +} + + +% Converts the string on the top of the stack to numerical +% ordinal (e.g., "11th") form. +FUNCTION {convert.edition} +{ duplicate$ empty$ 'skip$ + { duplicate$ #1 #1 substring$ is.num + { extract.num + num.to.ordinal + } + { word.to.num + duplicate$ #1 #1 substring$ is.num + { num.to.ordinal } + { "edition ordinal word " quote$ * edition * quote$ * + " may be too high (or improper) for conversion" * " in " * cite$ * warning$ + } + if$ + } + if$ + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +%% LATEX BIBLIOGRAPHY CODE %% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {start.entry} +{ newline$ + "\bibitem{" write$ + cite$ write$ + "}" write$ + newline$ + "" + initialize.prev.this.status +} + +% Here we write out all the LaTeX code that we will need. The most involved +% code sequences are those that control the alternate interword spacing and +% foreign language hyphenation patterns. The heavy use of \providecommand +% gives users a way to override the defaults. Special thanks to Javier Bezos, +% Johannes Braams, Robin Fairbairns, Heiko Oberdiek, Donald Arseneau and all +% the other gurus on comp.text.tex for their help and advice on the topic of +% \selectlanguage, Babel and BibTeX. +FUNCTION {begin.bib} +{ "% Generated by IEEEtranS.bst, version: " bst.file.version * " (" * bst.file.date * ")" * + write$ newline$ + preamble$ empty$ 'skip$ + { preamble$ write$ newline$ } + if$ + "\begin{thebibliography}{" longest.label * "}" * + write$ newline$ + "\providecommand{\url}[1]{#1}" + write$ newline$ + "\csname url at samestyle\endcsname" + write$ newline$ + "\providecommand{\newblock}{\relax}" + write$ newline$ + "\providecommand{\bibinfo}[2]{#2}" + write$ newline$ + "\providecommand{\BIBentrySTDinterwordspacing}{\spaceskip=0pt\relax}" + write$ newline$ + "\providecommand{\BIBentryALTinterwordstretchfactor}{" + ALTinterwordstretchfactor * "}" * + write$ newline$ + "\providecommand{\BIBentryALTinterwordspacing}{\spaceskip=\fontdimen2\font plus " + write$ newline$ + "\BIBentryALTinterwordstretchfactor\fontdimen3\font minus \fontdimen4\font\relax}" + write$ newline$ + "\providecommand{\BIBforeignlanguage}[2]{{%" + write$ newline$ + "\expandafter\ifx\csname l@#1\endcsname\relax" + write$ newline$ + "\typeout{** WARNING: IEEEtranS.bst: No hyphenation pattern has been}%" + write$ newline$ + "\typeout{** loaded for the language `#1'. Using the pattern for}%" + write$ newline$ + "\typeout{** the default language instead.}%" + write$ newline$ + "\else" + write$ newline$ + "\language=\csname l@#1\endcsname" + write$ newline$ + "\fi" + write$ newline$ + "#2}}" + write$ newline$ + "\providecommand{\BIBdecl}{\relax}" + write$ newline$ + "\BIBdecl" + write$ newline$ +} + +FUNCTION {end.bib} +{ newline$ "\end{thebibliography}" write$ newline$ } + +FUNCTION {if.url.alt.interword.spacing} +{ is.use.alt.interword.spacing + {url empty$ 'skip$ {"\BIBentryALTinterwordspacing" write$ newline$} if$} + { skip$ } + if$ +} + +FUNCTION {if.url.std.interword.spacing} +{ is.use.alt.interword.spacing + {url empty$ 'skip$ {"\BIBentrySTDinterwordspacing" write$ newline$} if$} + { skip$ } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%%%%% +%% LONGEST LABEL PASS %% +%%%%%%%%%%%%%%%%%%%%%%%% + +FUNCTION {initialize.longest.label} +{ "" 'longest.label := + #1 'number.label := + #0 'longest.label.width := +} + +FUNCTION {longest.label.pass} +{ type$ "ieeetranbstctl" = + { skip$ } + { number.label int.to.str$ 'label := + number.label #1 + 'number.label := + label width$ longest.label.width > + { label 'longest.label := + label width$ 'longest.label.width := + } + { skip$ } + if$ + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%%% +%% FORMAT HANDLERS %% +%%%%%%%%%%%%%%%%%%%%% + +%% Lower Level Formats (used by higher level formats) + +FUNCTION {format.address.org.or.pub.date} +{ 't := + "" + year empty$ + { "empty year in " cite$ * warning$ } + { skip$ } + if$ + address empty$ t empty$ and + year empty$ and month empty$ and + { skip$ } + { this.to.prev.status + this.status.std + cap.status.std + address "address" bibinfo.check * + t empty$ + { skip$ } + { punct.period 'prev.status.punct := + space.large 'prev.status.space := + address empty$ + { skip$ } + { ": " * } + if$ + t * + } + if$ + year empty$ month empty$ and + { skip$ } + { t empty$ address empty$ and + { skip$ } + { ", " * } + if$ + month empty$ + { year empty$ + { skip$ } + { year "year" bibinfo.check * } + if$ + } + { month "month" bibinfo.check * + year empty$ + { skip$ } + { " " * year "year" bibinfo.check * } + if$ + } + if$ + } + if$ + } + if$ +} + + +FUNCTION {format.names} +{ 'bibinfo := + duplicate$ empty$ 'skip$ { + this.to.prev.status + this.status.std + 's := + "" 't := + #1 'nameptr := + s num.names$ 'numnames := + numnames 'namesleft := + { namesleft #0 > } + { s nameptr + name.format.string + format.name$ + bibinfo bibinfo.check + 't := + nameptr #1 > + { nameptr num.names.shown.with.forced.et.al #1 + = + numnames max.num.names.before.forced.et.al > + is.forced.et.al and and + { "others" 't := + #1 'namesleft := + } + { skip$ } + if$ + namesleft #1 > + { ", " * t do.name.latex.cmd * } + { s nameptr "{ll}" format.name$ duplicate$ "others" = + { 't := } + { pop$ } + if$ + t "others" = + { " " * bbl.etal emphasize * } + { numnames #2 > + { "," * } + { skip$ } + if$ + bbl.and + space.word * t do.name.latex.cmd * + } + if$ + } + if$ + } + { t do.name.latex.cmd } + if$ + nameptr #1 + 'nameptr := + namesleft #1 - 'namesleft := + } + while$ + cap.status.std + } if$ +} + + + + +%% Higher Level Formats + +%% addresses/locations + +FUNCTION {format.address} +{ address duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% author/editor names + +FUNCTION {format.authors}{ author "author" format.names } + +FUNCTION {format.editors} +{ editor "editor" format.names duplicate$ empty$ 'skip$ + { ", " * + get.bbl.editor + capitalize + * + } + if$ +} + + + +%% date + +FUNCTION {format.date} +{ + month "month" bibinfo.check duplicate$ empty$ + year "year" bibinfo.check duplicate$ empty$ + { swap$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + "there's a month but no year in " cite$ * warning$ } + if$ + * + } + { this.to.prev.status + this.status.std + cap.status.std + swap$ 'skip$ + { + swap$ + " " * swap$ + } + if$ + * + } + if$ +} + +FUNCTION {format.date.electronic} +{ month "month" bibinfo.check duplicate$ empty$ + year "year" bibinfo.check duplicate$ empty$ + { swap$ + { pop$ } + { "there's a month but no year in " cite$ * warning$ + pop$ ")" * "(" swap$ * + this.to.prev.status + punct.no 'this.status.punct := + space.normal 'this.status.space := + quote.no 'this.status.quote := + cap.yes 'status.cap := + } + if$ + } + { swap$ + { swap$ pop$ ")" * "(" swap$ * } + { "(" swap$ * ", " * swap$ * ")" * } + if$ + this.to.prev.status + punct.no 'this.status.punct := + space.normal 'this.status.space := + quote.no 'this.status.quote := + cap.yes 'status.cap := + } + if$ +} + + + +%% edition/title + +% Note: IEEE considers the edition to be closely associated with +% the title of a book. So, in IEEEtran.bst the edition is normally handled +% within the formatting of the title. The format.edition function is +% retained here for possible future use. +FUNCTION {format.edition} +{ edition duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + convert.edition + status.cap + { "t" } + { "l" } + if$ change.case$ + "edition" bibinfo.check + "~" * bbl.edition * + cap.status.std + } + if$ +} + +% This is used to format the booktitle of a conference proceedings. +% Here we use the "intype" field to provide the user a way to +% override the word "in" (e.g., with things like "presented at") +% Use of intype stops the emphasis of the booktitle to indicate that +% we no longer mean the written conference proceedings, but the +% conference itself. +FUNCTION {format.in.booktitle} +{ booktitle "booktitle" bibinfo.check duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + select.language + intype missing$ + { emphasize + bbl.in " " * + } + { intype " " * } + if$ + swap$ * + cap.status.std + } + if$ +} + +% This is used to format the booktitle of collection. +% Here the "intype" field is not supported, but "edition" is. +FUNCTION {format.in.booktitle.edition} +{ booktitle "booktitle" bibinfo.check duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + select.language + emphasize + edition empty$ 'skip$ + { ", " * + edition + convert.edition + "l" change.case$ + * "~" * bbl.edition * + } + if$ + bbl.in " " * swap$ * + cap.status.std + } + if$ +} + +FUNCTION {format.article.title} +{ title duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + "t" change.case$ + } + if$ + "title" bibinfo.check + duplicate$ empty$ 'skip$ + { quote.close 'this.status.quote := + is.last.char.not.punct + { punct.std 'this.status.punct := } + { punct.no 'this.status.punct := } + if$ + select.language + "``" swap$ * + cap.status.std + } + if$ +} + +FUNCTION {format.article.title.electronic} +{ title duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + "t" change.case$ + } + if$ + "title" bibinfo.check + duplicate$ empty$ + { skip$ } + { select.language } + if$ +} + +FUNCTION {format.book.title.edition} +{ title "title" bibinfo.check + duplicate$ empty$ + { "empty title in " cite$ * warning$ } + { this.to.prev.status + this.status.std + select.language + emphasize + edition empty$ 'skip$ + { ", " * + edition + convert.edition + status.cap + { "t" } + { "l" } + if$ + change.case$ + * "~" * bbl.edition * + } + if$ + cap.status.std + } + if$ +} + +FUNCTION {format.book.title} +{ title "title" bibinfo.check + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + select.language + emphasize + } + if$ +} + + + +%% journal + +FUNCTION {format.journal} +{ journal duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + select.language + emphasize + } + if$ +} + + + +%% how published + +FUNCTION {format.howpublished} +{ howpublished duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% institutions/organization/publishers/school + +FUNCTION {format.institution} +{ institution duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + +FUNCTION {format.organization} +{ organization duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + +FUNCTION {format.address.publisher.date} +{ publisher "publisher" bibinfo.warn format.address.org.or.pub.date } + +FUNCTION {format.address.publisher.date.nowarn} +{ publisher "publisher" bibinfo.check format.address.org.or.pub.date } + +FUNCTION {format.address.organization.date} +{ organization "organization" bibinfo.check format.address.org.or.pub.date } + +FUNCTION {format.school} +{ school duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + cap.status.std + } + if$ +} + + + +%% volume/number/series/chapter/pages + +FUNCTION {format.volume} +{ volume empty.field.to.null.string + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + bbl.volume + status.cap + { capitalize } + { skip$ } + if$ + swap$ tie.or.space.prefix + "volume" bibinfo.check + * * + cap.status.std + } + if$ +} + +FUNCTION {format.number} +{ number empty.field.to.null.string + duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + status.cap + { bbl.number capitalize } + { bbl.number } + if$ + swap$ tie.or.space.prefix + "number" bibinfo.check + * * + cap.status.std + } + if$ +} + +FUNCTION {format.number.if.use.for.article} +{ is.use.number.for.article + { format.number } + { "" } + if$ +} + +% IEEE does not seem to tie the series so closely with the volume +% and number as is done in other bibliography styles. Instead the +% series is treated somewhat like an extension of the title. +FUNCTION {format.series} +{ series empty$ + { "" } + { this.to.prev.status + this.status.std + bbl.series " " * + series "series" bibinfo.check * + cap.status.std + } + if$ +} + + +FUNCTION {format.chapter} +{ chapter empty$ + { "" } + { this.to.prev.status + this.status.std + type empty$ + { bbl.chapter } + { type "l" change.case$ + "type" bibinfo.check + } + if$ + chapter tie.or.space.prefix + "chapter" bibinfo.check + * * + cap.status.std + } + if$ +} + + +% The intended use of format.paper is for paper numbers of inproceedings. +% The paper type can be overridden via the type field. +% We allow the type to be displayed even if the paper number is absent +% for things like "postdeadline paper" +FUNCTION {format.paper} +{ is.use.paper + { paper empty$ + { type empty$ + { "" } + { this.to.prev.status + this.status.std + type "type" bibinfo.check + cap.status.std + } + if$ + } + { this.to.prev.status + this.status.std + type empty$ + { bbl.paper } + { type "type" bibinfo.check } + if$ + " " * paper + "paper" bibinfo.check + * + cap.status.std + } + if$ + } + { "" } + if$ +} + + +FUNCTION {format.pages} +{ pages duplicate$ empty$ 'skip$ + { this.to.prev.status + this.status.std + duplicate$ is.multiple.pages + { + bbl.pages swap$ + n.dashify + } + { + bbl.page swap$ + } + if$ + tie.or.space.prefix + "pages" bibinfo.check + * * + cap.status.std + } + if$ +} + + + +%% technical report number + +FUNCTION {format.tech.report.number} +{ number "number" bibinfo.check + this.to.prev.status + this.status.std + cap.status.std + type duplicate$ empty$ + { pop$ + bbl.techrep + } + { skip$ } + if$ + "type" bibinfo.check + swap$ duplicate$ empty$ + { pop$ } + { tie.or.space.prefix * * } + if$ +} + + + +%% note + +FUNCTION {format.note} +{ note empty$ + { "" } + { this.to.prev.status + this.status.std + punct.period 'this.status.punct := + note #1 #1 substring$ + duplicate$ "{" = + { skip$ } + { status.cap + { "u" } + { "l" } + if$ + change.case$ + } + if$ + note #2 global.max$ substring$ * "note" bibinfo.check + cap.yes 'status.cap := + } + if$ +} + + + +%% patent + +FUNCTION {format.patent.date} +{ this.to.prev.status + this.status.std + year empty$ + { monthfiled duplicate$ empty$ + { "monthfiled" bibinfo.check pop$ "" } + { "monthfiled" bibinfo.check } + if$ + dayfiled duplicate$ empty$ + { "dayfiled" bibinfo.check pop$ "" * } + { "dayfiled" bibinfo.check + monthfiled empty$ + { "dayfiled without a monthfiled in " cite$ * warning$ + * + } + { " " swap$ * * } + if$ + } + if$ + yearfiled empty$ + { "no year or yearfiled in " cite$ * warning$ } + { yearfiled "yearfiled" bibinfo.check + swap$ + duplicate$ empty$ + { pop$ } + { ", " * swap$ * } + if$ + } + if$ + } + { month duplicate$ empty$ + { "month" bibinfo.check pop$ "" } + { "month" bibinfo.check } + if$ + day duplicate$ empty$ + { "day" bibinfo.check pop$ "" * } + { "day" bibinfo.check + month empty$ + { "day without a month in " cite$ * warning$ + * + } + { " " swap$ * * } + if$ + } + if$ + year "year" bibinfo.check + swap$ + duplicate$ empty$ + { pop$ } + { ", " * swap$ * } + if$ + } + if$ + cap.status.std +} + +FUNCTION {format.patent.nationality.type.number} +{ this.to.prev.status + this.status.std + nationality duplicate$ empty$ + { "nationality" bibinfo.warn pop$ "" } + { "nationality" bibinfo.check + duplicate$ "l" change.case$ "united states" = + { pop$ bbl.patentUS } + { skip$ } + if$ + " " * + } + if$ + type empty$ + { bbl.patent "type" bibinfo.check } + { type "type" bibinfo.check } + if$ + * + number duplicate$ empty$ + { "number" bibinfo.warn pop$ } + { "number" bibinfo.check + large.number.separate + swap$ " " * swap$ * + } + if$ + cap.status.std +} + + + +%% standard + +FUNCTION {format.organization.institution.standard.type.number} +{ this.to.prev.status + this.status.std + organization duplicate$ empty$ + { pop$ + institution duplicate$ empty$ + { "institution" bibinfo.warn } + { "institution" bibinfo.warn " " * } + if$ + } + { "organization" bibinfo.warn " " * } + if$ + type empty$ + { bbl.standard "type" bibinfo.check } + { type "type" bibinfo.check } + if$ + * + number duplicate$ empty$ + { "number" bibinfo.check pop$ } + { "number" bibinfo.check + large.number.separate + swap$ " " * swap$ * + } + if$ + cap.status.std +} + +FUNCTION {format.revision} +{ revision empty$ + { "" } + { this.to.prev.status + this.status.std + bbl.revision + revision tie.or.space.prefix + "revision" bibinfo.check + * * + cap.status.std + } + if$ +} + + +%% thesis + +FUNCTION {format.master.thesis.type} +{ this.to.prev.status + this.status.std + type empty$ + { + bbl.mthesis + } + { + type "type" bibinfo.check + } + if$ +cap.status.std +} + +FUNCTION {format.phd.thesis.type} +{ this.to.prev.status + this.status.std + type empty$ + { + bbl.phdthesis + } + { + type "type" bibinfo.check + } + if$ +cap.status.std +} + + + +%% URL + +FUNCTION {format.url} +{ url empty$ + { "" } + { this.to.prev.status + this.status.std + cap.yes 'status.cap := + name.url.prefix " " * + "\url{" * url * "}" * + punct.no 'this.status.punct := + punct.period 'prev.status.punct := + space.normal 'this.status.space := + space.normal 'prev.status.space := + quote.no 'this.status.quote := + } + if$ +} + + + + +%%%%%%%%%%%%%%%%%%%% +%% ENTRY HANDLERS %% +%%%%%%%%%%%%%%%%%%%% + + +% Note: In many journals, IEEE (or the authors) tend not to show the number +% for articles, so the display of the number is controlled here by the +% switch "is.use.number.for.article" +FUNCTION {article} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.journal "journal" bibinfo.check "journal" output.warn + format.volume output + format.number.if.use.for.article output + format.pages output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {book} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + author empty$ + { format.editors "author and editor" output.warn } + { format.authors output.nonnull } + if$ + name.or.dash + format.book.title.edition output + format.series output + author empty$ + { skip$ } + { format.editors output } + if$ + format.address.publisher.date output + format.volume output + format.number output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {booklet} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {electronic} +{ std.status.using.period + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.date.electronic output + format.article.title.electronic output + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {inbook} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + author empty$ + { format.editors "author and editor" output.warn } + { format.authors output.nonnull } + if$ + name.or.dash + format.book.title.edition output + format.series output + format.address.publisher.date output + format.volume output + format.number output + format.chapter output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {incollection} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.in.booktitle.edition "booktitle" output.warn + format.series output + format.editors output + format.address.publisher.date.nowarn output + format.volume output + format.number output + format.chapter output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {inproceedings} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.in.booktitle "booktitle" output.warn + format.series output + format.editors output + format.volume output + format.number output + publisher empty$ + { format.address.organization.date output } + { format.organization "organization" bibinfo.check output + format.address.publisher.date output + } + if$ + format.paper output + format.pages output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {manual} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.book.title.edition "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {mastersthesis} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.master.thesis.type output.nonnull + format.school "school" bibinfo.warn output + format.address "address" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {misc} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title output + format.howpublished "howpublished" bibinfo.check output + format.organization "organization" bibinfo.check output + format.address "address" bibinfo.check output + format.pages output + format.date output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {patent} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.article.title output + format.patent.nationality.type.number output + format.patent.date output + format.note output + format.url output + fin.entry + empty.entry.warn + if.url.std.interword.spacing +} + +FUNCTION {periodical} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.editors output + name.or.dash + format.book.title "title" output.warn + format.series output + format.volume output + format.number output + format.organization "organization" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {phdthesis} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.phd.thesis.type output.nonnull + format.school "school" bibinfo.warn output + format.address "address" bibinfo.check output + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {proceedings} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.editors output + name.or.dash + format.book.title "title" output.warn + format.series output + format.volume output + format.number output + publisher empty$ + { format.address.organization.date output } + { format.organization "organization" bibinfo.check output + format.address.publisher.date output + } + if$ + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {standard} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors output + name.or.dash + format.book.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.organization.institution.standard.type.number output + format.revision output + format.date output + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {techreport} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.howpublished "howpublished" bibinfo.check output + format.institution "institution" bibinfo.warn output + format.address "address" bibinfo.check output + format.tech.report.number output.nonnull + format.date "year" output.warn + format.note output + format.url output + fin.entry + if.url.std.interword.spacing +} + +FUNCTION {unpublished} +{ std.status.using.comma + start.entry + if.url.alt.interword.spacing + format.authors "author" output.warn + name.or.dash + format.article.title "title" output.warn + format.date output + format.note "note" output.warn + format.url output + fin.entry + if.url.std.interword.spacing +} + + +% The special entry type which provides the user interface to the +% BST controls +FUNCTION {IEEEtranBSTCTL} +{ is.print.banners.to.terminal + { "** IEEEtran BST control entry " quote$ * cite$ * quote$ * " detected." * + top$ + } + { skip$ } + if$ + CTLuse_article_number + empty$ + { skip$ } + { CTLuse_article_number + yes.no.to.int + 'is.use.number.for.article := + } + if$ + CTLuse_paper + empty$ + { skip$ } + { CTLuse_paper + yes.no.to.int + 'is.use.paper := + } + if$ + CTLuse_forced_etal + empty$ + { skip$ } + { CTLuse_forced_etal + yes.no.to.int + 'is.forced.et.al := + } + if$ + CTLmax_names_forced_etal + empty$ + { skip$ } + { CTLmax_names_forced_etal + string.to.integer + 'max.num.names.before.forced.et.al := + } + if$ + CTLnames_show_etal + empty$ + { skip$ } + { CTLnames_show_etal + string.to.integer + 'num.names.shown.with.forced.et.al := + } + if$ + CTLuse_alt_spacing + empty$ + { skip$ } + { CTLuse_alt_spacing + yes.no.to.int + 'is.use.alt.interword.spacing := + } + if$ + CTLalt_stretch_factor + empty$ + { skip$ } + { CTLalt_stretch_factor + 'ALTinterwordstretchfactor := + "\renewcommand{\BIBentryALTinterwordstretchfactor}{" + ALTinterwordstretchfactor * "}" * + write$ newline$ + } + if$ + CTLdash_repeated_names + empty$ + { skip$ } + { CTLdash_repeated_names + yes.no.to.int + 'is.dash.repeated.names := + } + if$ + CTLname_format_string + empty$ + { skip$ } + { CTLname_format_string + 'name.format.string := + } + if$ + CTLname_latex_cmd + empty$ + { skip$ } + { CTLname_latex_cmd + 'name.latex.cmd := + } + if$ + CTLname_url_prefix + missing$ + { skip$ } + { CTLname_url_prefix + 'name.url.prefix := + } + if$ + + + num.names.shown.with.forced.et.al max.num.names.before.forced.et.al > + { "CTLnames_show_etal cannot be greater than CTLmax_names_forced_etal in " cite$ * warning$ + max.num.names.before.forced.et.al 'num.names.shown.with.forced.et.al := + } + { skip$ } + if$ +} + + +%%%%%%%%%%%%%%%%%%% +%% ENTRY ALIASES %% +%%%%%%%%%%%%%%%%%%% +FUNCTION {conference}{inproceedings} +FUNCTION {online}{electronic} +FUNCTION {internet}{electronic} +FUNCTION {webpage}{electronic} +FUNCTION {www}{electronic} +FUNCTION {default.type}{misc} + + + +%%%%%%%%%%%%%%%%%% +%% MAIN PROGRAM %% +%%%%%%%%%%%%%%%%%% + +READ + +EXECUTE {initialize.controls} +EXECUTE {initialize.status.constants} +EXECUTE {banner.message} + + + +% BEGIN sort code based on that of plain.bst + +FUNCTION {sortify} +{ purify$ + "l" change.case$ +} + +INTEGERS { len } + +FUNCTION {chop.word} +{ 's := + 'len := + s #1 len substring$ = + { s len #1 + global.max$ substring$ } + { s } + if$ +} + +FUNCTION {sort.format.names} +{ 's := + #1 'nameptr := + "" + s num.names$ 'numnames := + numnames 'namesleft := + { namesleft #0 > } + { nameptr #1 > + { " " * } + { skip$ } + if$ + s nameptr "{vv{ } }{ll{ }}{ ff{ }}{ jj{ }}" format.name$ 't := + nameptr numnames = t "others" = and + { "et al" * } + { t sortify * } + if$ + nameptr #1 + 'nameptr := + namesleft #1 - 'namesleft := + } + while$ +} + +FUNCTION {sort.format.title} +{ 't := + "A " #2 + "An " #3 + "The " #4 t chop.word + chop.word + chop.word + sortify + #1 global.max$ substring$ +} + +FUNCTION {author.sort} +{ author empty$ + { key empty$ + { "to sort, need author or key in " cite$ * warning$ "" } + { key sortify } + if$ + } + { author sort.format.names } + if$ +} + +FUNCTION {author.editor.sort} +{ author empty$ + { editor empty$ + { key empty$ + { "to sort, need author, editor, or key in " cite$ * warning$ "" } + { key sortify } + if$ + } + { editor sort.format.names } + if$ + } + { author sort.format.names } + if$ +} + +FUNCTION {author.organization.sort} +{ author empty$ + { organization empty$ + { key empty$ + { "to sort, need author, organization, or key in " cite$ * warning$ "" } + { key sortify } + if$ + } + { "The " #4 organization chop.word sortify } + if$ + } + { author sort.format.names } + if$ +} + +FUNCTION {editor.organization.sort} +{ editor empty$ + { organization empty$ + { key empty$ + { "to sort, need editor, organization, or key in " cite$ * warning$ "" } + { key sortify } + if$ + } + { "The " #4 organization chop.word sortify } + if$ + } + { editor sort.format.names } + if$ +} + +FUNCTION {author.organization.institution.sort} +{ author empty$ + { organization empty$ + { institution empty$ + { key empty$ + { "to sort, need author, organization, institution or key in " cite$ * warning$ "" } + { key sortify } + if$ + } + { "The " #4 institution chop.word sortify } + if$ + } + { "The " #4 organization chop.word sortify } + if$ + } + { author sort.format.names } + if$ +} + + +FUNCTION {presort} +{ type$ "ieeetranbstctl" = + { key empty$ + { "_" } + { key sortify } + if$ + } + { type$ "book" = + type$ "inbook" = + or + { author.editor.sort } + { type$ "proceedings" = + type$ "periodical" = + or + { editor.organization.sort } + { type$ "manual" = + type$ "electronic" = + type$ "misc" = + or or + { author.organization.sort } + { type$ "standard" = + { author.organization.institution.sort } + { author.sort } + if$ + } + if$ + } + if$ + } + if$ + " " + * + type$ "patent" = + { year empty$ + { yearfiled } + { year } + if$ + } + { year } + if$ + empty.field.to.null.string sortify + * + " " + * + title empty.field.to.null.string + sort.format.title + * + } + if$ + #1 entry.max$ substring$ + 'sort.key$ := +} + +ITERATE {presort} + +SORT + +% END sort code based on that of plain.bst + + + +EXECUTE {initialize.longest.label} +ITERATE {longest.label.pass} + +EXECUTE {begin.bib} +ITERATE {call.type$} +EXECUTE {end.bib} + +EXECUTE{completed.message} + + +%% That's all folks, mds. Added: text/escience11submission/IEEEtran_HOWTO.pdf =================================================================== (Binary files differ) Property changes on: text/escience11submission/IEEEtran_HOWTO.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: text/escience11submission/IEEEtran_bst_HOWTO.pdf =================================================================== (Binary files differ) Property changes on: text/escience11submission/IEEEtran_bst_HOWTO.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: text/escience11submission/README =================================================================== --- text/escience11submission/README (rev 0) +++ text/escience11submission/README 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,144 @@ + +January 11, 2007 + + +IEEEtran.bst is the official BibTeX style for authors of the Institute of +Electrical and Electronics Engineers (IEEE) Transactions journals and +conferences. + +It also may have applications for other academic work such as theses and +technical reports. The alphanumeric and natbib variants extend the +applicability of the IEEEtran bibstyle family to the natural sciences +and beyond. + +The IEEEtran bibstyle is a very comprehensive BibTeX style which provides +many features beyond the standard BibTeX styles, including full support +for references of online documents, patents, periodicals and standards. +See the provided user manual for detailed usage information. + +The latest version of the IEEEtran BibTeX style can be found at CTAN: + +http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/bibtex/ + +as well as within IEEE's site: + +http://www.ieee.org/ + +Note that the packages at IEEE's site do not contain the natbib and +alphanumeric variants (e.g., IEEEtranN.bst, etc.) as these are not used +for IEEE related work. These files can be obtained on CTAN. + +For helpful tips, answers to frequently asked questions and other support, +visit the IEEEtran home page at my website: + +http://www.michaelshell.org/tex/ieeetran/ + + +Enjoy! + +Michael Shell +http://www.michaelshell.org/ + +******* +Version 1.12 (2007/01/11) changes: + + 1. Fixed bug with unwanted comma before "et al." when an entry contained + more than two author names. Thanks to Pallav Gupta for reporting this. + + 2. Fixed bug with anomalous closing quote in tech reports that have a + type, but without a number or address. Thanks to Mehrdad Mirreza for + reporting this. + + 3. Use braces in \providecommand in begin.bib to better support + latex2html. TeX style length assignments OK with recent versions + of latex2html - 1.71 (2002/2/1) or later is strongly recommended. + Use of the language field still causes trouble with latex2html. + Thanks to Federico Beffa for reporting this. + + 4. Added IEEEtran.bst ID and version comment string to .bbl output. + + 5. Provide a \BIBdecl hook that allows the user to execute commands + just prior to the first entry. + + 6. Use default urlstyle (is using url.sty) of "same" rather than rm to + better work with a wider variety of bibliography styles. + + 7. Changed month abbreviations from Sept., July and June to Sep., Jul., + and Jun., respectively, as IEEE now does. Thanks to Moritz Borgmann + for reporting this. + + 8. Control entry types should not be considered when calculating longest + label width. + + 9. Added alias www for electronic/online. + +10. Updated full and abbreviated journal name string definitions in + IEEEfull.bib and IEEEabrv.bib. + +11. New IEEEtranSA.bst, IEEEtranN.bst, and IEEEtranSN.bst variants for + alphanumeric citation tags and natbib compatibility. + + +********************************** Files ********************************** + +README - This file. + +IEEEtran_bst_HOWTO.pdf - The user manual. + +IEEEtran.bst - The standard IEEEtran BibTeX style file. For use + with IEEE work. + +IEEEtranS.bst - A version of IEEEtran.bst that sorts the entries. + Some IEEE conferences/publications may use/allow + sorted bibliographies. + +IEEEexample.bib - An example BibTeX database that contains the + references shown in the user manual. + +IEEEabrv.bib - String definitions for the abbreviated names of + IEEE journals. (For use with IEEE work.) + +IEEEfull.bib - String definitions for the full names of IEEE + journals. (Do not use for IEEE work.) + + +Carried on CTAN only, for non-IEEE related work: + +IEEEtranSA.bst - Like IEEEtranS.bst, but with alphanumeric citation + tags like alpha.bst. Not for normal IEEE use. + +EEEtranN.bst - Like IEEEtran.bst, but based on plainnat.bst and + is compatible with Patrick W. Daly's natbib + package. Not for normal IEEE use. + +IEEEtranSN.bst - Sorting version of IEEEtranN.bst. Not for normal + IEEE use + +*************************************************************************** +Legal Notice: +This code is offered as-is without any warranty either expressed or +implied; without even the implied warranty of MERCHANTABILITY or +FITNESS FOR A PARTICULAR PURPOSE! +User assumes all risk. +In no event shall IEEE or any contributor to this code be liable for +any damages or losses, including, but not limited to, incidental, +consequential, or any other damages, resulting from the use or misuse +of any information contained here. + +All comments are the opinions of their respective authors and are not +necessarily endorsed by the IEEE. + +This work is distributed under the LaTeX Project Public License (LPPL) +( http://www.latex-project.org/ ) version 1.3, and may be freely used, +distributed and modified. A copy of the LPPL, version 1.3, is included +in the base LaTeX documentation of all distributions of LaTeX released +2003/12/01 or later. +Retain all contribution notices and credits. +** Modified files should be clearly indicated as such, including ** +** renaming them and changing author support contact information. ** + +File list of work: IEEEtran_bst_HOWTO.pdf, IEEEtran.bst, IEEEtranS.bst, + IEEEtranSA.bst, IEEEtranN.bst, IEEEtranSN.bst, + IEEEexample.bib, IEEEabrv.bib, IEEEfull.bib + +*************************************************************************** Added: text/escience11submission/bare_adv.tex =================================================================== --- text/escience11submission/bare_adv.tex (rev 0) +++ text/escience11submission/bare_adv.tex 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,1100 @@ + +%% bare_adv.tex +%% V1.3 +%% 2007/01/11 +%% by Michael Shell +%% See: +%% http://www.michaelshell.org/ +%% for current contact information. +%% +%% This is a skeleton file demonstrating the advanced use of IEEEtran.cls +%% (requires IEEEtran.cls version 1.7 or later) with an IEEE Computer +%% Society journal paper. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ + +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%%************************************************************************* + +% *** Authors should verify (and, if needed, correct) their LaTeX system *** +% *** with the testflow diagnostic prior to trusting their LaTeX platform *** +% *** with production work. IEEE's font choices can trigger bugs that do *** +% *** not appear when using other class files. *** +% The testflow support page is at: +% http://www.michaelshell.org/tex/testflow/ + + + +% IEEEtran V1.7 and later provides for these CLASSINPUT macros to allow the +% user to reprogram some IEEEtran.cls defaults if needed. These settings +% override the internal defaults of IEEEtran.cls regardless of which class +% options are used. Do not use these unless you have good reason to do so as +% they can result in nonIEEE compliant documents. User beware. ;) +% +%\newcommand{\CLASSINPUTbaselinestretch}{1.0} % baselinestretch +%\newcommand{\CLASSINPUTinnersidemargin}{1in} % inner side margin +%\newcommand{\CLASSINPUToutersidemargin}{1in} % outer side margin +%\newcommand{\CLASSINPUTtoptextmargin}{1in} % top text margin +%\newcommand{\CLASSINPUTbottomtextmargin}{1in}% bottom text margin + + + +% Note that the a4paper option is mainly intended so that authors in +% countries using A4 can easily print to A4 and see how their papers will +% look in print - the typesetting of the document will not typically be +% affected with changes in paper size (but the bottom and side margins will). +% Use the testflow package mentioned above to verify correct handling of +% both paper sizes by the user's LaTeX system. +% +% Also note that the "draftcls" or "draftclsnofoot", not "draft", option +% should be used if it is desired that the figures are to be displayed in +% draft mode. +% +\documentclass[12pt,journal,compsoc]{IEEEtran} +% The Computer Society requires 12pt. +% If IEEEtran.cls has not been installed into the LaTeX system files, +% manually specify the path to it like: +% \documentclass[10pt,journal,compsoc]{../sty/IEEEtran} + + +% For Computer Society journals, IEEEtran defaults to the use of +% Palatino/Palladio as is done in IEEE Computer Society journals. +% To go back to Times Roman, you can use this code: +%\renewcommand{\rmdefault}{ptm}\selectfont + + + + + +% Some very useful LaTeX packages include: +% (uncomment the ones you want to load) + + + +% *** MISC UTILITY PACKAGES *** +% +%\usepackage{ifpdf} +% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional +% compilation based on whether the output is pdf or dvi. +% usage: +% \ifpdf +% % pdf code +% \else +% % dvi code +% \fi +% The latest version of ifpdf.sty can be obtained from: +% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ +% Also, note that IEEEtran.cls V1.7 and later provides a builtin +% \ifCLASSINFOpdf conditional that works the same way. +% When switching from latex to pdflatex and vice-versa, the compiler may +% have to be run twice to clear warning/error messages. + + + + + + +% *** CITATION PACKAGES *** +% +\ifCLASSOPTIONcompsoc + % IEEE Computer Society needs nocompress option + % requires cite.sty v4.0 or later (November 2003) + % \usepackage[nocompress]{cite} +\else + % normal IEEE + % \usepackage{cite} +\fi +% cite.sty was written by Donald Arseneau +% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package +% \cite{} output to follow that of IEEE. Loading the cite package will +% result in citation numbers being automatically sorted and properly +% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using +% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's +% \cite will automatically add leading space, if needed. Use cite.sty's +% noadjust option (cite.sty V3.8 and later) if you want to turn this off. +% cite.sty is already installed on most LaTeX systems. Be sure and use +% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does +% not currently provide for hyperlinked citations. +% The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ +% The documentation is contained in the cite.sty file itself. +% +% Note that some packages require special options to format as the Computer +% Society requires. In particular, Computer Society papers do not use +% compressed citation ranges as is done in typical IEEE papers +% (e.g., [1]-[4]). Instead, they list every citation separately in order +% (e.g., [1], [2], [3], [4]). To get the latter we need to load the cite +% package with the nocompress option which is supported by cite.sty v4.0 +% and later. Note also the use of a CLASSOPTION conditional provided by +% IEEEtran.cls V1.7 and later. + + + + + +% *** GRAPHICS RELATED PACKAGES *** +% +\ifCLASSINFOpdf + % \usepackage[pdftex]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../pdf/}{../jpeg/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} +\else + % or other class option (dvipsone, dvipdf, if not using dvips). graphicx + % will default to the driver specified in the system graphics.cfg if no + % driver is specified. + % \usepackage[dvips]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../eps/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.eps} +\fi +% graphicx was written by David Carlisle and Sebastian Rahtz. It is +% required if you want graphics, photos, etc. graphicx.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/graphics/ +% Another good source of documentation is "Using Imported Graphics in +% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or +% epslatex.pdf at: http://www.ctan.org/tex-archive/info/ +% +% latex, and pdflatex in dvi mode, support graphics in encapsulated +% postscript (.eps) format. pdflatex in pdf mode supports graphics +% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure +% that all non-photo figures use a vector format (.eps, .pdf, .mps) and +% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats +% which can result in "jaggedy"/blurry rendering of lines and letters as +% well as large increases in file sizes. +% +% You can find documentation about the pdfTeX application at: +% http://www.tug.org/applications/pdftex + + + +%\usepackage{ps4pdf} +% dvi->ps workflow is required to use such packages as psfrag.sty and +% pstricks.sty. However, Rolf Niepraschk's ps4pdf.sty provides a way to +% apply psfrag/pstricks effects to .eps figures and then get the resultant +% figures in .pdf form. Thus, providing an easier way for migrating from +% .eps to .pdf figures. After ps4pdf.sty loads, if: +% 1. producing .dvi output: the output file will consist ONLY of the +% figures (or other constructs encased within \PSforPDF commands) +% 2. producing .pdf output: pdflatex will look in the filename-pics.pdf +% file, where filename is the basename of the tex document, for the +% graphics (or other constructs encased within \PSforPDF commands). +% NOTE: If you ever change your figures, you must remember to remake +% the filename-pics.pdf file. +% +% This way you can do a: +% +% latex filename +% dvips -Ppdf -o filename-pics.ps filename.dvi +% ps2pdf filename-pics.ps filename-pics.pdf +% +% to produce a filename-pics.pdf graphics container that contains +% .pdf versions of the graphics with psfrag, pstricks, etc. features. +% Note that you will not typically be able to view the figures in +% filename-pics.ps because of an offset. However, you will be able to +% view them in filename-pics.pdf. Also, note that when ps4pdf is in effect +% with .dvi output, you may get harmless over/under full box warnings - +% ignore them. +% Then, run pdflatex: +% +% pdflatex filename +% +% to use pdflatex to make PDF output, automatically using the figures in +% filename-pics.pdf. Alternatively, you could use dvips -i option to +% obtain separate .pdf files for each figure: +% +% dvips -Ppdf -i -E -o fig filename +% +% then convert each figure to pdf via a command such as epstopdf and then +% use pdflatex with these pdf figures and then to dispense with ps4pdf. +% +% Remember to rerun through latex/dvips/ps2pdf if you ever change your +% figures so that filename-pics.pdf gets updated. +% ps4pdf requires David Kastrup's preview-latex and a recent LaTeX system +% (circa 2001 or later). The ps4pdf package and documentation can be +% obtained at: http://www.ctan.org/tex-archive/macros/latex/contrib/ps4pdf/ +% The preview-latex package and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/preview/ +% +% provide a bogus \PSforPDF, even when not loading pd4pdf. This way we can +% stop loading ps4pdf.sty if we choose to make separate .pdf versions of +% each of our figures. +\providecommand{\PSforPDF}[1]{#1} +% Note that in order for ps4pdf to work, all commands related to psfrag, +% pstricks, etc. must be called within the PSforPDF command. This applies +% even when *loading* via \usepackage psfrag.sty, etc. + + +%\PSforPDF{\usepackage{psfrag}} +% psfrag.sty was written by Craig Barratt, Michael C. Grant, and +% David Carlisle. It allows you to substitute LaTeX commands for text in +% imported EPS graphic files. In this way, LaTeX symbols can be placed into +% graphics that have been generated by other applications. You must use +% latex->dvips->ps2pdf workflow (not direct pdf output from pdflatex) if +% you wish to use this capability because it works via some PostScript +% tricks. Alternatively, the graphics could be processed as separate files +% via psfrag and dvips, then converted to PDF for inclusion in the main file +% which uses pdflatex. ps4pdf.sty (above) provides a way of doing this all +% at once within the main file. +% Docs are in "The PSfrag System" by Michael C. Grant and David Carlisle. +% There is also some information about using psfrag in "Using Imported +% Graphics in LaTeX2e" by Keith Reckdahl which documents the graphicx +% package (see above). The psfrag package and documentation can be obtained +% at: http://www.ctan.org/tex-archive/macros/latex/contrib/psfrag/ +% +% Note that the current version of psfrag does not "turn itself off" when +% running under pdf output. This will result in a harmless warning +% about a non-PDF \special. However, to silence this, a bogus psfrag +% command can be provided instead of loading psfrag.sty when PDF output +% is being used. Thus, a more complex alternative conditional loading scheme +% can be employed instead of the straightforword way above: +% +%\ifCLASSINFOpdf +% if outputting PDF, do not use or load psfrag.sty as current versions +% output a non-PDF special that generates a harmless, but annoying warning. +% Instead, we provide a bogus \psfrag command that does nothing with +% its arguments. This is a tad tricky because \psfrag can have up to six +% arguments four of which are optional: \psfrag{}[][][][]{} +% Code based on that in psfrag.sty +%\makeatletter +%\def\psfrag{\@ifstar{\@BOGUSpsfraga}{\@BOGUSpsfraga}} +%\def\@BOGUSpsfraga{\begingroup +% \@makeother\"\@makeother\*\@makeother\!\@makeother\~% +% \@makeother\:\@makeother\\\@makeother\%\@makeother\#% +% \@makeother\ \@BOGUSpsfragb} +%\def\@BOGUSpsfragb#1{\endgroup +% \@ifnextchar [{\@BOGUSpsfragc}% +% {\@BOGUSpsfrag}} +%\def\@BOGUSpsfragc[#1]{\@ifnextchar [{\@BOGUSpsfragd}% +% {\@BOGUSpsfrag}} +%\def\@BOGUSpsfragd[#1]{\@ifnextchar [{\@BOGUSpsfrage}% +% {\@BOGUSpsfrag}} +%\def\@BOGUSpsfrage[#1]{\@ifnextchar [{\@BOGUSpsfragf}% +% {\@BOGUSpsfrag}} +%\def\@BOGUSpsfragf[#1]{\@BOGUSpsfrag} +%\def\@BOGUSpsfrag#1{\ignorespaces} +%\makeatother +%\else +% using dvi output, load psfrag, but funnel it through PSforPDF +% as required by ps4pdf.sty +%\PSforPDF{\usepackage{psfrag}} +%\fi + + + + + +% *** MATH PACKAGES *** +% +%\usepackage[cmex10]{amsmath} +% A popular package from the American Mathematical Society that provides +% many useful and powerful commands for dealing with mathematics. If using +% it, be sure to load this package with the cmex10 option to ensure that +% only type 1 fonts will utilized at all point sizes. Without this option, +% it is possible that some math symbols, particularly those within +% footnotes, will be rendered in bitmap form which will result in a +% document that can not be IEEE Xplore compliant! +% +% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 +% thus preventing page breaks from occurring within multiline equations. Use: +%\interdisplaylinepenalty=2500 +% after loading amsmath to restore such page breaks as IEEEtran.cls normally +% does. amsmath.sty is already installed on most LaTeX systems. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ + + + + + +% *** SPECIALIZED LIST PACKAGES *** +%\usepackage{acronym} +% acronym.sty was written by Tobias Oetiker. This package provides tools for +% managing documents with large numbers of acronyms. (You don't *have* to +% use this package - unless you have a lot of acronyms, you may feel that +% such package management of them is bit of an overkill.) +% Do note that the acronym environment (which lists acronyms) will have a +% problem when used under IEEEtran.cls because acronym.sty relies on the +% description list environment - which IEEEtran.cls has customized for +% producing IEEE style lists. A workaround is to declared the longest +% label width via the IEEEtran.cls \IEEEiedlistdecl global control: +% +% \renewcommand{\IEEEiedlistdecl}{\IEEEsetlabelwidth{SONET}} +% \begin{acronym} +% +% \end{acronym} +% \renewcommand{\IEEEiedlistdecl}{\relax}% remember to reset \IEEEiedlistdecl +% +% instead of using the acronym environment's optional argument. +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/acronym/ + + +%\usepackage{algorithmic} +% algorithmic.sty was written by Peter Williams and Rogerio Brito. +% This package provides an algorithmic environment fo describing algorithms. +% You can use the algorithmic environment in-text or within a figure +% environment to provide for a floating algorithm. Do NOT use the algorithm +% floating environment provided by algorithm.sty (by the same authors) or +% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated +% algorithm float types and packages that provide these will not provide +% correct IEEE style captions. The latest version and documentation of +% algorithmic.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ +% There is also a support site at: +% http://algorithms.berlios.de/index.html +% Also of interest may be the (relatively newer and more customizable) +% algorithmicx.sty package by Szasz Janos: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ + + + + +% *** ALIGNMENT PACKAGES *** +% +%\usepackage{array} +% Frank Mittelbach's and David Carlisle's array.sty patches and improves +% the standard LaTeX2e array and tabular environments to provide better +% appearance and additional user controls. As the default LaTeX2e table +% generation code is lacking to the point of almost being broken with +% respect to the quality of the end results, all users are strongly +% advised to use an enhanced (at the very least that provided by array.sty) +% set of table tools. array.sty is already installed on most systems. The +% latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/tools/ + + +%\usepackage{mdwmath} +%\usepackage{mdwtab} +% Also highly recommended is Mark Wooding's extremely powerful MDW tools, +% especially mdwmath.sty and mdwtab.sty which are used to format equations +% and tables, respectively. The MDWtools set is already installed on most +% LaTeX systems. The lastest version and documentation is available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ + + +% IEEEtran contains the IEEEeqnarray family of commands that can be used to +% generate multiline equations as well as matrices, tables, etc., of high +% quality. + + +%\usepackage{eqparbox} +% Also of notable interest is Scott Pakin's eqparbox package for creating +% (automatically sized) equal width boxes - aka "natural width parboxes". +% Available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ + + + + + +% *** SUBFIGURE PACKAGES *** +%\ifCLASSOPTIONcompsoc +%\usepackage[tight,normalsize,sf,SF]{subfigure} +%\else +%\usepackage[tight,footnotesize]{subfigure} +%\fi +% subfigure.sty was written by Steven Douglas Cochran. This package makes it +% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE +% work, it is a good idea to load it with the tight package option to reduce +% the amount of white space around the subfigures. Computer Society papers +% use a larger font and \sffamily font for their captions, hence the +% additional options needed under compsoc mode. subfigure.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ +% subfigure.sty has been superceeded by subfig.sty. + + +%\ifCLASSOPTIONcompsoc +% \usepackage[caption=false]{caption} +% \usepackage[font=normalsize,labelfont=sf,textfont=sf]{subfig} +%\else +% \usepackage[caption=false]{caption} +% \usepackage[font=footnotesize]{subfig} +%\fi +% subfig.sty, also written by Steven Douglas Cochran, is the modern +% replacement for subfigure.sty. However, subfig.sty requires and +% automatically loads Axel Sommerfeldt's caption.sty which will override +% IEEEtran.cls handling of captions and this will result in nonIEEE style +% figure/table captions. To prevent this problem, be sure and preload +% caption.sty with its "caption=false" package option. This is will preserve +% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later +% (recommended due to many improvements over 1.2) of subfig.sty supports +% the caption=false option directly: +%\ifCLASSOPTIONcompsoc +% \usepackage[caption=false,font=normalsize,labelfont=sf,textfont=sf]{subfig} +%\else +% \usepackage[caption=false,font=footnotesize]{subfig} +%\fi +% +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ +% The latest version and documentation of caption.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ + + + + +% *** FLOAT PACKAGES *** +% +%\usepackage{fixltx2e} +% fixltx2e, the successor to the earlier fix2col.sty, was written by +% Frank Mittelbach and David Carlisle. This package corrects a few problems +% in the LaTeX2e kernel, the most notable of which is that in current +% LaTeX2e releases, the ordering of single and double column floats is not +% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a +% single column figure to be placed prior to an earlier double column +% figure. The latest version and documentation can be found at: +% http://www.ctan.org/tex-archive/macros/latex/base/ + + +%\usepackage{stfloats} +% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e +% the ability to do double column floats at the bottom of the page as well +% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in +% LaTeX2e). It also provides a command: +%\fnbelowfloat +% to enable the placement of footnotes below bottom floats (the standard +% LaTeX2e kernel puts them above bottom floats). This is an invasive package +% which rewrites many portions of the LaTeX2e float routines. It may not work +% with other packages that modify the LaTeX2e float routines. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ +% Documentation is contained in the stfloats.sty comments as well as in the +% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE +% does not allow \baselineskip to stretch. Authors submitting work to the +% IEEE should note that IEEE rarely uses double column equations and +% that authors should try to avoid such use. Do not be tempted to use the +% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does +% not format its papers in such ways. + + +%\ifCLASSOPTIONcaptionsoff +% \usepackage[nomarkers]{endfloat} +% \let\MYoriglatexcaption\caption +% \renewcommand{\caption}[2][\relax]{\MYoriglatexcaption[#2]{#2}} +%\fi +% endfloat.sty was written by James Darrell McCauley and Jeff Goldberg. +% This package may be useful when used in conjunction with IEEEtran.cls' +% captionsoff option. Some IEEE journals/societies require that submissions +% have lists of figures/tables at the end of the paper and that +% figures/tables without any captions are placed on a page by themselves at +% the end of the document. If needed, the draftcls IEEEtran class option or +% \CLASSINPUTbaselinestretch interface can be used to increase the line +% spacing as well. Be sure and use the nomarkers option of endfloat to +% prevent endfloat from "marking" where the figures would have been placed +% in the text. The two hack lines of code above are a slight modification of +% that suggested by in the endfloat docs (section 8.3.1) to ensure that +% the full captions always appear in the list of figures/tables - even if +% the user used the short optional argument of \caption[]{}. +% IEEE papers do not typically make use of \caption[]'s optional argument, +% so this should not be an issue. A similar trick can be used to disable +% captions of packages such as subfig.sty that lack options to turn off +% the subcaptions: +% For subfig.sty: +% \let\MYorigsubfloat\subfloat +% \renewcommand{\subfloat}[2][\relax]{\MYorigsubfloat[]{#2}} +% For subfigure.sty: +% \let\MYorigsubfigure\subfigure +% \renewcommand{\subfigure}[2][\relax]{\MYorigsubfigure[]{#2}} +% However, the above trick will not work if both optional arguments of +% the \subfloat/subfig command are used. Furthermore, there needs to be a +% description of each subfigure *somewhere* and endfloat does not add +% subfigure captions to its list of figures. Thus, the best approach is to +% avoid the use of subfigure captions (many IEEE journals avoid them anyway) +% and instead reference/explain all the subfigures within the main caption. +% The latest version of endfloat.sty and its documentation can obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/endfloat/ +% +% The IEEEtran \ifCLASSOPTIONcaptionsoff conditional can also be used +% later in the document, say, to conditionally put the References on a +% page by themselves. + + + + + +% *** PDF, URL AND HYPERLINK PACKAGES *** +% +%\usepackage{url} +% url.sty was written by Donald Arseneau. It provides better support for +% handling and breaking URLs. url.sty is already installed on most LaTeX +% systems. The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ +% Read the url.sty source comments for usage information. Basically, +% \url{my_url_here}. + + +% NOTE: PDF thumbnail features are not required in IEEE papers +% and their use requires extra complexity and work. +%\ifCLASSINFOpdf +% \usepackage[pdftex]{thumbpdf} +%\else +% \usepackage[dvips]{thumbpdf} +%\fi +% thumbpdf.sty and its companion Perl utility were written by Heiko Oberdiek. +% It allows the user a way to produce PDF documents that contain fancy +% thumbnail images of each of the pages (which tools like acrobat reader can +% utilize). This is possible even when using dvi->ps->pdf workflow if the +% correct thumbpdf driver options are used. thumbpdf.sty incorporates the +% file containing the PDF thumbnail information (filename.tpm is used with +% dvips, filename.tpt is used with pdftex, where filename is the base name of +% your tex document) into the final ps or pdf output document. An external +% utility, the thumbpdf *Perl script* is needed to make these .tpm or .tpt +% thumbnail files from a .ps or .pdf version of the document (which obviously +% does not yet contain pdf thumbnails). Thus, one does a: +% +% thumbpdf filename.pdf +% +% to make a filename.tpt, and: +% +% thumbpdf --mode dvips filename.ps +% +% to make a filename.tpm which will then be loaded into the document by +% thumbpdf.sty the NEXT time the document is compiled (by pdflatex or +% latex->dvips->ps2pdf). Users must be careful to regenerate the .tpt and/or +% .tpm files if the main document changes and then to recompile the +% document to incorporate the revised thumbnails to ensure that thumbnails +% match the actual pages. It is easy to forget to do this! +% +% Unix systems come with a Perl interpreter. However, MS Windows users +% will usually have to install a Perl interpreter so that the thumbpdf +% script can be run. The Ghostscript PS/PDF interpreter is also required. +% See the thumbpdf docs for details. The latest version and documentation +% can be obtained at. +% http://www.ctan.org/tex-archive/support/thumbpdf/ +% Be sure and use only version 3.8 (2005/07/06) or later of thumbpdf as +% earlier versions will not work properly with recent versions of pdfTeX +% (1.20a and later). + + +% NOTE: PDF hyperlink and bookmark features are not required in IEEE +% papers and their use requires extra complexity and work. +% *** IF USING HYPERREF BE SURE AND CHANGE THE EXAMPLE PDF *** +% *** TITLE/SUBJECT/AUTHOR/KEYWORDS INFO BELOW!! *** +\newcommand\MYhyperrefoptions{bookmarks=true,bookmarksnumbered=true, +pdfpagemode={UseOutlines},plainpages=false,pdfpagelabels=true, +colorlinks=true,linkcolor={black},citecolor={black},pagecolor={black}, +urlcolor={black}, +pdftitle={Bare Demo of IEEEtran.cls for Computer Society Journals},%.dvi->.ps->.pdf workflow if the respective packages/scripts are +% loaded/invoked with the correct driver options (dvips, etc.). +% As most IEEE papers use URLs sparingly (mainly in the references), this +% may not be as big an issue as with other publications. +% +% That said, recently Vilar Camara Neto introduced his breakurl.sty +% package which permits hyperref to easily break URLs even in dvi +% mode. Note that breakurl, unlike most other packages, must be loaded +% AFTER hyperref. The latest version of breakurl and its documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/breakurl/ +% breakurl.sty is not for use under pdflatex pdf mode. Versions 1.10 +% (September 23, 2005) and later are recommened to avoid bugs in earlier +% releases. +% +% The advanced features offer by hyperref.sty are not required for IEEE +% submission, so users should weigh these features against the added +% complexity of use. Users who wish to use hyperref *must* ensure that +% their hyperref version is 6.72u or later *and* IEEEtran.cls is version +% 1.6b or later. +% The package options above demonstrate how to enable PDF bookmarks +% (a type of table of contents viewable in Acrobat Reader) as well as +% PDF document information (title, subject, author and keywords) that is +% viewable in Acrobat reader's Document_Properties menu. PDF document +% information is also used extensively to automate the cataloging of PDF +% documents. The above set of options ensures that hyperlinks will not be +% colored in the text and thus will not be visible in the printed page, +% but will be active on "mouse over". USING COLORS OR OTHER HIGHLIGHTING +% OF HYPERLINKS CAN RESULT IN DOCUMENT REJECTION BY THE IEEE, especially if +% these appear on the "printed" page. IF IN DOUBT, ASK THE RELEVANT +% SUBMISSION EDITOR. You may need to add the option hypertexnames=false if +% you used duplicate equation numbers, etc., but this should not be needed +% in normal IEEE work. +% The latest version of hyperref and its documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/hyperref/ + + + + + +% *** Do not adjust lengths that control margins, column widths, etc. *** +% *** Do not use packages that alter fonts (such as pslatex). *** +% There should be no need to do such things with IEEEtran.cls V1.6 and later. +% (Unless specifically asked to do so by the journal or conference you plan +% to submit to, of course. ) + + +% correct bad hyphenation here +\hyphenation{op-tical net-works semi-conduc-tor} + + +\begin{document} +% +% paper title +% can use linebreaks \\ within to get better formatting as desired +\title{Bare Advanced Demo of IEEEtran.cls\\ for Computer Society Journals} +% +% +% author names and IEEE memberships +% note positions of commas and nonbreaking spaces ( ~ ) LaTeX will not break +% a structure at a ~ so this keeps an author's name from being broken across +% two lines. +% use \thanks{} to gain access to the first footnote area +% a separate \thanks must be used for each paragraph as LaTeX2e's \thanks +% was not built to handle multiple paragraphs +% +% +%\IEEEcompsocitemizethanks is a special \thanks that produces the bulleted +% lists the Computer Society journals use for "first footnote" author +% affiliations. Use \IEEEcompsocthanksitem which works much like \item +% for each affiliation group. When not in compsoc mode, +% \IEEEcompsocitemizethanks becomes like \thanks and +% \IEEEcompsocthanksitem becomes a line break with idention. This +% facilitates dual compilation, although admittedly the differences in the +% desired content of \author between the different types of papers makes a +% one-size-fits-all approach a daunting prospect. For instance, compsoc +% journal papers have the author affiliations above the "Manuscript +% received ..." text while in non-compsoc journals this is reversed. Sigh. + +\author{Michael~Shell,~\IEEEmembership{Member,~IEEE,} + John~Doe,~\IEEEmembership{Fellow,~OSA,} + and~Jane~Doe,~\IEEEmembership{Life~Fellow,~IEEE}% <-this % stops a space +\IEEEcompsocitemizethanks{\IEEEcompsocthanksitem M. Shell is with the Department +of Electrical and Computer Engineering, Georgia Institute of Technology, Atlanta, +GA, 30332.\protect\\ +% note need leading \protect in front of \\ to get a newline within \thanks as +% \\ is fragile and will error, could use \hfil\break instead. +E-mail: see http://www.michaelshell.org/contact.html +\IEEEcompsocthanksitem J. Doe and J. Doe are with Anonymous University.}% <-this % stops a space +\thanks{Manuscript received April 19, 2005; revised January 11, 2007.}} + +% note the % following the last \IEEEmembership and also \thanks - +% these prevent an unwanted space from occurring between the last author name +% and the end of the author line. i.e., if you had this: +% +% \author{....lastname \thanks{...} \thanks{...} } +% ^------------^------------^----Do not want these spaces! +% +% a space would be appended to the last name and could cause every name on that +% line to be shifted left slightly. This is one of those "LaTeX things". For +% instance, "\textbf{A} \textbf{B}" will typeset as "A B" not "AB". To get +% "AB" then you have to do: "\textbf{A}\textbf{B}" +% \thanks is no different in this regard, so shield the last } of each \thanks +% that ends a line with a % and do not let a space in before the next \thanks. +% Spaces after \IEEEmembership other than the last one are OK (and needed) as +% you are supposed to have spaces between the names. For what it is worth, +% this is a minor point as most people would not even notice if the said evil +% space somehow managed to creep in. + + + +% The paper headers +\markboth{Journal of \LaTeX\ Class Files,~Vol.~6, No.~1, January~2007}% +{Shell \MakeLowercase{\textit{et al.}}: Bare Advanced Demo of IEEEtran.cls for Journals} +% The only time the second header will appear is for the odd numbered pages +% after the title page when using the twoside option. +% +% *** Note that you probably will NOT want to include the author's *** +% *** name in the headers of peer review papers. *** +% You can use \ifCLASSOPTIONpeerreview for conditional compilation here if +% you desire. + + + +% The publisher's ID mark at the bottom of the page is less important with +% Computer Society journal papers as those publications place the marks +% outside of the main text columns and, therefore, unlike regular IEEE +% journals, the available text space is not reduced by their presence. +% If you want to put a publisher's ID mark on the page you can do it like +% this: +%\IEEEpubid{0000--0000/00\$00.00~\copyright~2007 IEEE} +% or like this to get the Computer Society new two part style. +%\IEEEpubid{\makebox[\columnwidth]{\hfill 0000--0000/00/\$00.00~\copyright~2007 IEEE}% +%\hspace{\columnsep}\makebox[\columnwidth]{Published by the IEEE Computer Society\hfill}} +% Remember, if you use this you must call \IEEEpubidadjcol in the second +% column for its text to clear the IEEEpubid mark (Computer Society jorunal +% papers don't need this extra clearance.) + + + +% use for special paper notices +%\IEEEspecialpapernotice{(Invited Paper)} + + + +% for Computer Society papers, we must declare the abstract and index terms +% PRIOR to the title within the \IEEEcompsoctitleabstractindextext IEEEtran +% command as these need to go into the title area created by \maketitle. +\IEEEcompsoctitleabstractindextext{% +\begin{abstract} +%\boldmath +The abstract goes here. +\end{abstract} +% IEEEtran.cls defaults to using nonbold math in the Abstract. +% This preserves the distinction between vectors and scalars. However, +% if the journal you are submitting to favors bold math in the abstract, +% then you can use LaTeX's standard command \boldmath at the very start +% of the abstract to achieve this. Many IEEE journals frown on math +% in the abstract anyway. In particular, the Computer Society does +% not want either math or citations to appear in the abstract. + +% Note that keywords are not normally used for peerreview papers. +\begin{IEEEkeywords} +Computer Society, IEEEtran, journal, \LaTeX, paper, template. +\end{IEEEkeywords}} + + +% make the title area +\maketitle + + +% To allow for easy dual compilation without having to reenter the +% abstract/keywords data, the \IEEEcompsoctitleabstractindextext text will +% not be used in maketitle, but will appear (i.e., to be "transported") +% here as \IEEEdisplaynotcompsoctitleabstractindextext when compsoc mode +% is not selected if conference mode is selected - because compsoc +% conference papers position the abstract like regular (non-compsoc) +% papers do! +\IEEEdisplaynotcompsoctitleabstractindextext +% \IEEEdisplaynotcompsoctitleabstractindextext has no effect when using +% compsoc under a non-conference mode. + + +% For peer review papers, you can put extra information on the cover +% page as needed: +% \ifCLASSOPTIONpeerreview +% \begin{center} \bfseries EDICS Category: 3-BBND \end{center} +% \fi +% +% For peerreview papers, this IEEEtran command inserts a page break and +% creates the second title. It will be ignored for other modes. +\IEEEpeerreviewmaketitle + + + +\section{Introduction} +% Computer Society journal papers do something a tad strange with the very +% first section heading (almost always called "Introduction"). They place it +% ABOVE the main text! IEEEtran.cls currently does not do this for you. +% However, You can achieve this effect by making LaTeX jump through some +% hoops via something like: +% +%\ifCLASSOPTIONcompsoc +% \noindent\raisebox{2\baselineskip}[0pt][0pt]% +% {\parbox{\columnwidth}{\section{Introduction}\label{sec:introduction}% +% \global\everypar=\everypar}}% +% \vspace{-1\baselineskip}\vspace{-\parskip}\par +%\else +% \section{Introduction}\label{sec:introduction}\par +%\fi +% +% Admittedly, this is a hack and may well be fragile, but seems to do the +% trick for me. Note the need to keep any \label that may be used right +% after \section in the above as the hack puts \section within a raised box. + + + +% The very first letter is a 2 line initial drop letter followed +% by the rest of the first word in caps (small caps for compsoc). +% +% form to use if the first word consists of a single letter: +% \IEEEPARstart{A}{demo} file is .... +% +% form to use if you need the single drop letter followed by +% normal text (unknown if ever used by IEEE): +% \IEEEPARstart{A}{}demo file is .... +% +% Some journals put the first two words in caps: +% \IEEEPARstart{T}{his demo} file is .... +% +% Here we have the typical use of a "T" for an initial drop letter +% and "HIS" in caps to complete the first word. +\IEEEPARstart{T}{his} demo file is intended to serve as a ``starter file'' +for IEEE Computer Society journal papers produced under \LaTeX\ using +IEEEtran.cls version 1.7 and later. +% You must have at least 2 lines in the paragraph with the drop letter +% (should never be an issue) +I wish you the best of success. + +\hfill mds + +\hfill January 11, 2007 + +\subsection{Subsection Heading Here} +Subsection text here. + +% needed in second column of first page if using \IEEEpubid +%\IEEEpubidadjcol + +\subsubsection{Subsubsection Heading Here} +Subsubsection text here. + + +% An example of a floating figure using the graphicx package. +% Note that \label must occur AFTER (or within) \caption. +% For figures, \caption should occur after the \includegraphics. +% Note that IEEEtran v1.7 and later has special internal code that +% is designed to preserve the operation of \label within \caption +% even when the captionsoff option is in effect. However, because +% of issues like this, it may be the safest practice to put all your +% \label just after \caption rather than within \caption{}. +% +% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class +% option should be used if it is desired that the figures are to be +% displayed while in draft mode. +% +%\begin{figure}[!t] +%\centering +%\includegraphics[width=2.5in]{myfigure} +% where an .eps filename suffix will be assumed under latex, +% and a .pdf suffix will be assumed for pdflatex; or what has been declared +% via \DeclareGraphicsExtensions. +%\caption{Simulation Results} +%\label{fig_sim} +%\end{figure} + +% Note that IEEE typically puts floats only at the top, even when this +% results in a large percentage of a column being occupied by floats. +% However, the Computer Society has been known to put floats at the bottom. + + +% An example of a double column floating figure using two subfigures. +% (The subfig.sty package must be loaded for this to work.) +% The subfigure \label commands are set within each subfloat command, the +% \label for the overall figure must come after \caption. +% \hfil must be used as a separator to get equal spacing. +% The subfigure.sty package works much the same way, except \subfigure is +% used instead of \subfloat. +% +%\begin{figure*}[!t] +%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}% +%\label{fig_first_case}} +%\hfil +%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}% +%\label{fig_second_case}}} +%\caption{Simulation results} +%\label{fig_sim} +%\end{figure*} +% +% Note that often IEEE papers with subfigures do not employ subfigure +% captions (using the optional argument to \subfloat), but instead will +% reference/describe all of them (a), (b), etc., within the main caption. + + +% An example of a floating table. Note that, for IEEE style tables, the +% \caption command should come BEFORE the table. Table text will default to +% \footnotesize as IEEE normally uses this smaller font for tables. +% The \label must come after \caption as always. +% +%\begin{table}[!t] +%% increase table row spacing, adjust to taste +%\renewcommand{\arraystretch}{1.3} +% if using array.sty, it might be a good idea to tweak the value of +% \extrarowheight as needed to properly center the text within the cells +%\caption{An Example of a Table} +%\label{table_example} +%\centering +%% Some packages, such as MDW tools, offer better commands for making tables +%% than the plain LaTeX2e tabular which is used here. +%\begin{tabular}{|c||c|} +%\hline +%One & Two\\ +%\hline +%Three & Four\\ +%\hline +%\end{tabular} +%\end{table} + + +% Note that IEEE does not put floats in the very first column - or typically +% anywhere on the first page for that matter. Also, in-text middle ("here") +% positioning is not used. Most IEEE journals use top floats exclusively. +% However, Computer Society journals sometimes do use bottom floats - bear +% this in mind when choosing appropriate optional arguments for the +% figure/table environments. +% Note that, LaTeX2e, unlike IEEE journals, places footnotes above bottom +% floats. This can be corrected via the \fnbelowfloat command of the +% stfloats package. + + + +\section{Conclusion} +The conclusion goes here. + + + + + +% if have a single appendix: +%\appendix[Proof of the Zonklar Equations] +% or +%\appendix % for no appendix heading +% do not use \section anymore after \appendix, only \section* +% is possibly needed + +% use appendices with more than one appendix +% then use \section to start each appendix +% you must declare a \section before using any +% \subsection or using \label (\appendices by itself +% starts a section numbered zero.) +% + + +\appendices +\section{Proof of the First Zonklar Equation} +Appendix one text goes here. + +% you can choose not to have a title for an appendix +% if you want by leaving the argument blank +\section{} +Appendix two text goes here. + + +% use section* for acknowledgement +\ifCLASSOPTIONcompsoc + % The Computer Society usually uses the plural form + \section*{Acknowledgments} +\else + % regular IEEE prefers the singular form + \section*{Acknowledgment} +\fi + + +The authors would like to thank... + + +% Can use something like this to put references on a page +% by themselves when using endfloat and the captionsoff option. +\ifCLASSOPTIONcaptionsoff + \newpage +\fi + + + +% trigger a \newpage just before the given reference +% number - used to balance the columns on the last page +% adjust value as needed - may need to be readjusted if +% the document is modified later +%\IEEEtriggeratref{8} +% The "triggered" command can be changed if desired: +%\IEEEtriggercmd{\enlargethispage{-5in}} + +% references section + +% can use a bibliography generated by BibTeX as a .bbl file +% BibTeX documentation can be easily obtained at: +% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/ +% The IEEEtran BibTeX style support page is at: +% http://www.michaelshell.org/tex/ieeetran/bibtex/ +%\bibliographystyle{IEEEtran} +% argument is your BibTeX string definitions and bibliography database(s) +%\bibliography{IEEEabrv,../bib/paper} +% +% manually copy in the resultant .bbl file +% set second argument of \begin to the number of references +% (used to reserve space for the reference number labels box) +\begin{thebibliography}{1} + +\bibitem{IEEEhowto:kopka} +H.~Kopka and P.~W. Daly, \emph{A Guide to {\LaTeX}}, 3rd~ed.\hskip 1em plus + 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999. + +\end{thebibliography} + +% biography section +% +% If you have an EPS/PDF photo (graphicx package needed) extra braces are +% needed around the contents of the optional argument to biography to prevent +% the LaTeX parser from getting confused when it sees the complicated +% \includegraphics command within an optional argument. (You could create +% your own custom macro containing the \includegraphics command to make things +% simpler here.) +%\begin{biography}[{\includegraphics[width=1in,height=1.25in,clip,keepaspectratio]{mshell}}]{Michael Shell} +% or if you just want to reserve a space for a photo: + +\begin{IEEEbiography}{Michael Shell} +Biography text here. +\end{IEEEbiography} + +% if you will not have a photo at all: +\begin{IEEEbiographynophoto}{John Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% insert where needed to balance the two columns on the last page with +% biographies +%\newpage + +\begin{IEEEbiographynophoto}{Jane Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% You can push biographies down or up by placing +% a \vfill before or after them. The appropriate +% use of \vfill depends on what kind of text is +% on the last page and whether or not the columns +% are being equalized. + +%\vfill + +% Can be used to pull up biographies so that the bottom of the last one +% is flush with the other column. +%\enlargethispage{-5in} + + + +% that's all folks +\end{document} + + Added: text/escience11submission/bare_conf.tex =================================================================== --- text/escience11submission/bare_conf.tex (rev 0) +++ text/escience11submission/bare_conf.tex 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,601 @@ + +%% bare_conf.tex +%% V1.3 +%% 2007/01/11 +%% by Michael Shell +%% See: +%% http://www.michaelshell.org/ +%% for current contact information. +%% +%% This is a skeleton file demonstrating the use of IEEEtran.cls +%% (requires IEEEtran.cls version 1.7 or later) with an IEEE conference paper. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ + +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%%************************************************************************* + +% *** Authors should verify (and, if needed, correct) their LaTeX system *** +% *** with the testflow diagnostic prior to trusting their LaTeX platform *** +% *** with production work. IEEE's font choices can trigger bugs that do *** +% *** not appear when using other class files. *** +% The testflow support page is at: +% http://www.michaelshell.org/tex/testflow/ + + + +% Note that the a4paper option is mainly intended so that authors in +% countries using A4 can easily print to A4 and see how their papers will +% look in print - the typesetting of the document will not typically be +% affected with changes in paper size (but the bottom and side margins will). +% Use the testflow package mentioned above to verify correct handling of +% both paper sizes by the user's LaTeX system. +% +% Also note that the "draftcls" or "draftclsnofoot", not "draft", option +% should be used if it is desired that the figures are to be displayed in +% draft mode. +% +\documentclass[conference]{IEEEtran} +% Add the compsoc option for Computer Society conferences. +% +% If IEEEtran.cls has not been installed into the LaTeX system files, +% manually specify the path to it like: +% \documentclass[conference]{../sty/IEEEtran} + + + + + +% Some very useful LaTeX packages include: +% (uncomment the ones you want to load) + + +% *** MISC UTILITY PACKAGES *** +% +%\usepackage{ifpdf} +% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional +% compilation based on whether the output is pdf or dvi. +% usage: +% \ifpdf +% % pdf code +% \else +% % dvi code +% \fi +% The latest version of ifpdf.sty can be obtained from: +% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ +% Also, note that IEEEtran.cls V1.7 and later provides a builtin +% \ifCLASSINFOpdf conditional that works the same way. +% When switching from latex to pdflatex and vice-versa, the compiler may +% have to be run twice to clear warning/error messages. + + + + + + +% *** CITATION PACKAGES *** +% +%\usepackage{cite} +% cite.sty was written by Donald Arseneau +% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package +% \cite{} output to follow that of IEEE. Loading the cite package will +% result in citation numbers being automatically sorted and properly +% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using +% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's +% \cite will automatically add leading space, if needed. Use cite.sty's +% noadjust option (cite.sty V3.8 and later) if you want to turn this off. +% cite.sty is already installed on most LaTeX systems. Be sure and use +% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does +% not currently provide for hyperlinked citations. +% The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ +% The documentation is contained in the cite.sty file itself. + + + + + + +% *** GRAPHICS RELATED PACKAGES *** +% +\ifCLASSINFOpdf + % \usepackage[pdftex]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../pdf/}{../jpeg/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} +\else + % or other class option (dvipsone, dvipdf, if not using dvips). graphicx + % will default to the driver specified in the system graphics.cfg if no + % driver is specified. + % \usepackage[dvips]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../eps/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.eps} +\fi +% graphicx was written by David Carlisle and Sebastian Rahtz. It is +% required if you want graphics, photos, etc. graphicx.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/graphics/ +% Another good source of documentation is "Using Imported Graphics in +% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or +% epslatex.pdf at: http://www.ctan.org/tex-archive/info/ +% +% latex, and pdflatex in dvi mode, support graphics in encapsulated +% postscript (.eps) format. pdflatex in pdf mode supports graphics +% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure +% that all non-photo figures use a vector format (.eps, .pdf, .mps) and +% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats +% which can result in "jaggedy"/blurry rendering of lines and letters as +% well as large increases in file sizes. +% +% You can find documentation about the pdfTeX application at: +% http://www.tug.org/applications/pdftex + + + + + +% *** MATH PACKAGES *** +% +%\usepackage[cmex10]{amsmath} +% A popular package from the American Mathematical Society that provides +% many useful and powerful commands for dealing with mathematics. If using +% it, be sure to load this package with the cmex10 option to ensure that +% only type 1 fonts will utilized at all point sizes. Without this option, +% it is possible that some math symbols, particularly those within +% footnotes, will be rendered in bitmap form which will result in a +% document that can not be IEEE Xplore compliant! +% +% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 +% thus preventing page breaks from occurring within multiline equations. Use: +%\interdisplaylinepenalty=2500 +% after loading amsmath to restore such page breaks as IEEEtran.cls normally +% does. amsmath.sty is already installed on most LaTeX systems. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ + + + + + +% *** SPECIALIZED LIST PACKAGES *** +% +%\usepackage{algorithmic} +% algorithmic.sty was written by Peter Williams and Rogerio Brito. +% This package provides an algorithmic environment fo describing algorithms. +% You can use the algorithmic environment in-text or within a figure +% environment to provide for a floating algorithm. Do NOT use the algorithm +% floating environment provided by algorithm.sty (by the same authors) or +% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated +% algorithm float types and packages that provide these will not provide +% correct IEEE style captions. The latest version and documentation of +% algorithmic.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ +% There is also a support site at: +% http://algorithms.berlios.de/index.html +% Also of interest may be the (relatively newer and more customizable) +% algorithmicx.sty package by Szasz Janos: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ + + + + +% *** ALIGNMENT PACKAGES *** +% +%\usepackage{array} +% Frank Mittelbach's and David Carlisle's array.sty patches and improves +% the standard LaTeX2e array and tabular environments to provide better +% appearance and additional user controls. As the default LaTeX2e table +% generation code is lacking to the point of almost being broken with +% respect to the quality of the end results, all users are strongly +% advised to use an enhanced (at the very least that provided by array.sty) +% set of table tools. array.sty is already installed on most systems. The +% latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/tools/ + + +%\usepackage{mdwmath} +%\usepackage{mdwtab} +% Also highly recommended is Mark Wooding's extremely powerful MDW tools, +% especially mdwmath.sty and mdwtab.sty which are used to format equations +% and tables, respectively. The MDWtools set is already installed on most +% LaTeX systems. The lastest version and documentation is available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ + + +% IEEEtran contains the IEEEeqnarray family of commands that can be used to +% generate multiline equations as well as matrices, tables, etc., of high +% quality. + + +%\usepackage{eqparbox} +% Also of notable interest is Scott Pakin's eqparbox package for creating +% (automatically sized) equal width boxes - aka "natural width parboxes". +% Available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ + + + + + +% *** SUBFIGURE PACKAGES *** +%\usepackage[tight,footnotesize]{subfigure} +% subfigure.sty was written by Steven Douglas Cochran. This package makes it +% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE +% work, it is a good idea to load it with the tight package option to reduce +% the amount of white space around the subfigures. subfigure.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ +% subfigure.sty has been superceeded by subfig.sty. + + + +%\usepackage[caption=false]{caption} +%\usepackage[font=footnotesize]{subfig} +% subfig.sty, also written by Steven Douglas Cochran, is the modern +% replacement for subfigure.sty. However, subfig.sty requires and +% automatically loads Axel Sommerfeldt's caption.sty which will override +% IEEEtran.cls handling of captions and this will result in nonIEEE style +% figure/table captions. To prevent this problem, be sure and preload +% caption.sty with its "caption=false" package option. This is will preserve +% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later +% (recommended due to many improvements over 1.2) of subfig.sty supports +% the caption=false option directly: +%\usepackage[caption=false,font=footnotesize]{subfig} +% +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ +% The latest version and documentation of caption.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ + + + + +% *** FLOAT PACKAGES *** +% +%\usepackage{fixltx2e} +% fixltx2e, the successor to the earlier fix2col.sty, was written by +% Frank Mittelbach and David Carlisle. This package corrects a few problems +% in the LaTeX2e kernel, the most notable of which is that in current +% LaTeX2e releases, the ordering of single and double column floats is not +% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a +% single column figure to be placed prior to an earlier double column +% figure. The latest version and documentation can be found at: +% http://www.ctan.org/tex-archive/macros/latex/base/ + + + +%\usepackage{stfloats} +% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e +% the ability to do double column floats at the bottom of the page as well +% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in +% LaTeX2e). It also provides a command: +%\fnbelowfloat +% to enable the placement of footnotes below bottom floats (the standard +% LaTeX2e kernel puts them above bottom floats). This is an invasive package +% which rewrites many portions of the LaTeX2e float routines. It may not work +% with other packages that modify the LaTeX2e float routines. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ +% Documentation is contained in the stfloats.sty comments as well as in the +% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE +% does not allow \baselineskip to stretch. Authors submitting work to the +% IEEE should note that IEEE rarely uses double column equations and +% that authors should try to avoid such use. Do not be tempted to use the +% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does +% not format its papers in such ways. + + + + + +% *** PDF, URL AND HYPERLINK PACKAGES *** +% +%\usepackage{url} +% url.sty was written by Donald Arseneau. It provides better support for +% handling and breaking URLs. url.sty is already installed on most LaTeX +% systems. The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ +% Read the url.sty source comments for usage information. Basically, +% \url{my_url_here}. + + + + + +% *** Do not adjust lengths that control margins, column widths, etc. *** +% *** Do not use packages that alter fonts (such as pslatex). *** +% There should be no need to do such things with IEEEtran.cls V1.6 and later. +% (Unless specifically asked to do so by the journal or conference you plan +% to submit to, of course. ) + + +% correct bad hyphenation here +\hyphenation{op-tical net-works semi-conduc-tor} + + +\begin{document} +% +% paper title +% can use linebreaks \\ within to get better formatting as desired +\title{Bare Demo of IEEEtran.cls for Conferences} + + +% author names and affiliations +% use a multiple column layout for up to three different +% affiliations +\author{\IEEEauthorblockN{Michael Shell} +\IEEEauthorblockA{School of Electrical and\\Computer Engineering\\ +Georgia Institute of Technology\\ +Atlanta, Georgia 30332--0250\\ +Email: http://www.michaelshell.org/contact.html} +\and +\IEEEauthorblockN{Homer Simpson} +\IEEEauthorblockA{Twentieth Century Fox\\ +Springfield, USA\\ +Email: homer at thesimpsons.com} +\and +\IEEEauthorblockN{James Kirk\\ and Montgomery Scott} +\IEEEauthorblockA{Starfleet Academy\\ +San Francisco, California 96678-2391\\ +Telephone: (800) 555--1212\\ +Fax: (888) 555--1212}} + +% conference papers do not typically use \thanks and this command +% is locked out in conference mode. If really needed, such as for +% the acknowledgment of grants, issue a \IEEEoverridecommandlockouts +% after \documentclass + +% for over three affiliations, or if they all won't fit within the width +% of the page, use this alternative format: +% +%\author{\IEEEauthorblockN{Michael Shell\IEEEauthorrefmark{1}, +%Homer Simpson\IEEEauthorrefmark{2}, +%James Kirk\IEEEauthorrefmark{3}, +%Montgomery Scott\IEEEauthorrefmark{3} and +%Eldon Tyrell\IEEEauthorrefmark{4}} +%\IEEEauthorblockA{\IEEEauthorrefmark{1}School of Electrical and Computer Engineering\\ +%Georgia Institute of Technology, +%Atlanta, Georgia 30332--0250\\ Email: see http://www.michaelshell.org/contact.html} +%\IEEEauthorblockA{\IEEEauthorrefmark{2}Twentieth Century Fox, Springfield, USA\\ +%Email: homer at thesimpsons.com} +%\IEEEauthorblockA{\IEEEauthorrefmark{3}Starfleet Academy, San Francisco, California 96678-2391\\ +%Telephone: (800) 555--1212, Fax: (888) 555--1212} +%\IEEEauthorblockA{\IEEEauthorrefmark{4}Tyrell Inc., 123 Replicant Street, Los Angeles, California 90210--4321}} + + + + +% use for special paper notices +%\IEEEspecialpapernotice{(Invited Paper)} + + + + +% make the title area +\maketitle + + +\begin{abstract} +%\boldmath +The abstract goes here. +\end{abstract} +% IEEEtran.cls defaults to using nonbold math in the Abstract. +% This preserves the distinction between vectors and scalars. However, +% if the conference you are submitting to favors bold math in the abstract, +% then you can use LaTeX's standard command \boldmath at the very start +% of the abstract to achieve this. Many IEEE journals/conferences frown on +% math in the abstract anyway. + +% no keywords + + + + +% For peer review papers, you can put extra information on the cover +% page as needed: +% \ifCLASSOPTIONpeerreview +% \begin{center} \bfseries EDICS Category: 3-BBND \end{center} +% \fi +% +% For peerreview papers, this IEEEtran command inserts a page break and +% creates the second title. It will be ignored for other modes. +\IEEEpeerreviewmaketitle + + + +\section{Introduction} +% no \IEEEPARstart +This demo file is intended to serve as a ``starter file'' +for IEEE conference papers produced under \LaTeX\ using +IEEEtran.cls version 1.7 and later. +% You must have at least 2 lines in the paragraph with the drop letter +% (should never be an issue) +I wish you the best of success. + +\hfill mds + +\hfill January 11, 2007 + +\subsection{Subsection Heading Here} +Subsection text here. + + +\subsubsection{Subsubsection Heading Here} +Subsubsection text here. + + +% An example of a floating figure using the graphicx package. +% Note that \label must occur AFTER (or within) \caption. +% For figures, \caption should occur after the \includegraphics. +% Note that IEEEtran v1.7 and later has special internal code that +% is designed to preserve the operation of \label within \caption +% even when the captionsoff option is in effect. However, because +% of issues like this, it may be the safest practice to put all your +% \label just after \caption rather than within \caption{}. +% +% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class +% option should be used if it is desired that the figures are to be +% displayed while in draft mode. +% +%\begin{figure}[!t] +%\centering +%\includegraphics[width=2.5in]{myfigure} +% where an .eps filename suffix will be assumed under latex, +% and a .pdf suffix will be assumed for pdflatex; or what has been declared +% via \DeclareGraphicsExtensions. +%\caption{Simulation Results} +%\label{fig_sim} +%\end{figure} + +% Note that IEEE typically puts floats only at the top, even when this +% results in a large percentage of a column being occupied by floats. + + +% An example of a double column floating figure using two subfigures. +% (The subfig.sty package must be loaded for this to work.) +% The subfigure \label commands are set within each subfloat command, the +% \label for the overall figure must come after \caption. +% \hfil must be used as a separator to get equal spacing. +% The subfigure.sty package works much the same way, except \subfigure is +% used instead of \subfloat. +% +%\begin{figure*}[!t] +%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}% +%\label{fig_first_case}} +%\hfil +%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}% +%\label{fig_second_case}}} +%\caption{Simulation results} +%\label{fig_sim} +%\end{figure*} +% +% Note that often IEEE papers with subfigures do not employ subfigure +% captions (using the optional argument to \subfloat), but instead will +% reference/describe all of them (a), (b), etc., within the main caption. + + +% An example of a floating table. Note that, for IEEE style tables, the +% \caption command should come BEFORE the table. Table text will default to +% \footnotesize as IEEE normally uses this smaller font for tables. +% The \label must come after \caption as always. +% +%\begin{table}[!t] +%% increase table row spacing, adjust to taste +%\renewcommand{\arraystretch}{1.3} +% if using array.sty, it might be a good idea to tweak the value of +% \extrarowheight as needed to properly center the text within the cells +%\caption{An Example of a Table} +%\label{table_example} +%\centering +%% Some packages, such as MDW tools, offer better commands for making tables +%% than the plain LaTeX2e tabular which is used here. +%\begin{tabular}{|c||c|} +%\hline +%One & Two\\ +%\hline +%Three & Four\\ +%\hline +%\end{tabular} +%\end{table} + + +% Note that IEEE does not put floats in the very first column - or typically +% anywhere on the first page for that matter. Also, in-text middle ("here") +% positioning is not used. Most IEEE journals/conferences use top floats +% exclusively. Note that, LaTeX2e, unlike IEEE journals/conferences, places +% footnotes above bottom floats. This can be corrected via the \fnbelowfloat +% command of the stfloats package. + + + +\section{Conclusion} +The conclusion goes here. + + + + +% conference papers do not normally have an appendix + + +% use section* for acknowledgement +\section*{Acknowledgment} + + +The authors would like to thank... + + + + + +% trigger a \newpage just before the given reference +% number - used to balance the columns on the last page +% adjust value as needed - may need to be readjusted if +% the document is modified later +%\IEEEtriggeratref{8} +% The "triggered" command can be changed if desired: +%\IEEEtriggercmd{\enlargethispage{-5in}} + +% references section + +% can use a bibliography generated by BibTeX as a .bbl file +% BibTeX documentation can be easily obtained at: +% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/ +% The IEEEtran BibTeX style support page is at: +% http://www.michaelshell.org/tex/ieeetran/bibtex/ +%\bibliographystyle{IEEEtran} +% argument is your BibTeX string definitions and bibliography database(s) +%\bibliography{IEEEabrv,../bib/paper} +% +% manually copy in the resultant .bbl file +% set second argument of \begin to the number of references +% (used to reserve space for the reference number labels box) +\begin{thebibliography}{1} + +\bibitem{IEEEhowto:kopka} +H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus + 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999. + +\end{thebibliography} + + + + +% that's all folks +\end{document} + + Added: text/escience11submission/bare_jrnl.tex =================================================================== --- text/escience11submission/bare_jrnl.tex (rev 0) +++ text/escience11submission/bare_jrnl.tex 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,745 @@ + +%% bare_jrnl.tex +%% V1.3 +%% 2007/01/11 +%% by Michael Shell +%% see http://www.michaelshell.org/ +%% for current contact information. +%% +%% This is a skeleton file demonstrating the use of IEEEtran.cls +%% (requires IEEEtran.cls version 1.7 or later) with an IEEE journal paper. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ + + + +% *** Authors should verify (and, if needed, correct) their LaTeX system *** +% *** with the testflow diagnostic prior to trusting their LaTeX platform *** +% *** with production work. IEEE's font choices can trigger bugs that do *** +% *** not appear when using other class files. *** +% The testflow support page is at: +% http://www.michaelshell.org/tex/testflow/ + + +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%%************************************************************************* + +% Note that the a4paper option is mainly intended so that authors in +% countries using A4 can easily print to A4 and see how their papers will +% look in print - the typesetting of the document will not typically be +% affected with changes in paper size (but the bottom and side margins will). +% Use the testflow package mentioned above to verify correct handling of +% both paper sizes by the user's LaTeX system. +% +% Also note that the "draftcls" or "draftclsnofoot", not "draft", option +% should be used if it is desired that the figures are to be displayed in +% draft mode. +% +\documentclass[journal]{IEEEtran} +% +% If IEEEtran.cls has not been installed into the LaTeX system files, +% manually specify the path to it like: +% \documentclass[journal]{../sty/IEEEtran} + + + + + +% Some very useful LaTeX packages include: +% (uncomment the ones you want to load) + + +% *** MISC UTILITY PACKAGES *** +% +%\usepackage{ifpdf} +% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional +% compilation based on whether the output is pdf or dvi. +% usage: +% \ifpdf +% % pdf code +% \else +% % dvi code +% \fi +% The latest version of ifpdf.sty can be obtained from: +% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ +% Also, note that IEEEtran.cls V1.7 and later provides a builtin +% \ifCLASSINFOpdf conditional that works the same way. +% When switching from latex to pdflatex and vice-versa, the compiler may +% have to be run twice to clear warning/error messages. + + + + + + +% *** CITATION PACKAGES *** +% +%\usepackage{cite} +% cite.sty was written by Donald Arseneau +% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package +% \cite{} output to follow that of IEEE. Loading the cite package will +% result in citation numbers being automatically sorted and properly +% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using +% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's +% \cite will automatically add leading space, if needed. Use cite.sty's +% noadjust option (cite.sty V3.8 and later) if you want to turn this off. +% cite.sty is already installed on most LaTeX systems. Be sure and use +% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does +% not currently provide for hyperlinked citations. +% The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ +% The documentation is contained in the cite.sty file itself. + + + + + + +% *** GRAPHICS RELATED PACKAGES *** +% +\ifCLASSINFOpdf + % \usepackage[pdftex]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../pdf/}{../jpeg/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} +\else + % or other class option (dvipsone, dvipdf, if not using dvips). graphicx + % will default to the driver specified in the system graphics.cfg if no + % driver is specified. + % \usepackage[dvips]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../eps/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.eps} +\fi +% graphicx was written by David Carlisle and Sebastian Rahtz. It is +% required if you want graphics, photos, etc. graphicx.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/graphics/ +% Another good source of documentation is "Using Imported Graphics in +% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or +% epslatex.pdf at: http://www.ctan.org/tex-archive/info/ +% +% latex, and pdflatex in dvi mode, support graphics in encapsulated +% postscript (.eps) format. pdflatex in pdf mode supports graphics +% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure +% that all non-photo figures use a vector format (.eps, .pdf, .mps) and +% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats +% which can result in "jaggedy"/blurry rendering of lines and letters as +% well as large increases in file sizes. +% +% You can find documentation about the pdfTeX application at: +% http://www.tug.org/applications/pdftex + + + + + +% *** MATH PACKAGES *** +% +%\usepackage[cmex10]{amsmath} +% A popular package from the American Mathematical Society that provides +% many useful and powerful commands for dealing with mathematics. If using +% it, be sure to load this package with the cmex10 option to ensure that +% only type 1 fonts will utilized at all point sizes. Without this option, +% it is possible that some math symbols, particularly those within +% footnotes, will be rendered in bitmap form which will result in a +% document that can not be IEEE Xplore compliant! +% +% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 +% thus preventing page breaks from occurring within multiline equations. Use: +%\interdisplaylinepenalty=2500 +% after loading amsmath to restore such page breaks as IEEEtran.cls normally +% does. amsmath.sty is already installed on most LaTeX systems. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ + + + + + +% *** SPECIALIZED LIST PACKAGES *** +% +%\usepackage{algorithmic} +% algorithmic.sty was written by Peter Williams and Rogerio Brito. +% This package provides an algorithmic environment fo describing algorithms. +% You can use the algorithmic environment in-text or within a figure +% environment to provide for a floating algorithm. Do NOT use the algorithm +% floating environment provided by algorithm.sty (by the same authors) or +% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated +% algorithm float types and packages that provide these will not provide +% correct IEEE style captions. The latest version and documentation of +% algorithmic.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ +% There is also a support site at: +% http://algorithms.berlios.de/index.html +% Also of interest may be the (relatively newer and more customizable) +% algorithmicx.sty package by Szasz Janos: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ + + + + +% *** ALIGNMENT PACKAGES *** +% +%\usepackage{array} +% Frank Mittelbach's and David Carlisle's array.sty patches and improves +% the standard LaTeX2e array and tabular environments to provide better +% appearance and additional user controls. As the default LaTeX2e table +% generation code is lacking to the point of almost being broken with +% respect to the quality of the end results, all users are strongly +% advised to use an enhanced (at the very least that provided by array.sty) +% set of table tools. array.sty is already installed on most systems. The +% latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/tools/ + + +%\usepackage{mdwmath} +%\usepackage{mdwtab} +% Also highly recommended is Mark Wooding's extremely powerful MDW tools, +% especially mdwmath.sty and mdwtab.sty which are used to format equations +% and tables, respectively. The MDWtools set is already installed on most +% LaTeX systems. The lastest version and documentation is available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ + + +% IEEEtran contains the IEEEeqnarray family of commands that can be used to +% generate multiline equations as well as matrices, tables, etc., of high +% quality. + + +%\usepackage{eqparbox} +% Also of notable interest is Scott Pakin's eqparbox package for creating +% (automatically sized) equal width boxes - aka "natural width parboxes". +% Available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ + + + + + +% *** SUBFIGURE PACKAGES *** +%\usepackage[tight,footnotesize]{subfigure} +% subfigure.sty was written by Steven Douglas Cochran. This package makes it +% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE +% work, it is a good idea to load it with the tight package option to reduce +% the amount of white space around the subfigures. subfigure.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ +% subfigure.sty has been superceeded by subfig.sty. + + + +%\usepackage[caption=false]{caption} +%\usepackage[font=footnotesize]{subfig} +% subfig.sty, also written by Steven Douglas Cochran, is the modern +% replacement for subfigure.sty. However, subfig.sty requires and +% automatically loads Axel Sommerfeldt's caption.sty which will override +% IEEEtran.cls handling of captions and this will result in nonIEEE style +% figure/table captions. To prevent this problem, be sure and preload +% caption.sty with its "caption=false" package option. This is will preserve +% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later +% (recommended due to many improvements over 1.2) of subfig.sty supports +% the caption=false option directly: +%\usepackage[caption=false,font=footnotesize]{subfig} +% +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ +% The latest version and documentation of caption.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ + + + + +% *** FLOAT PACKAGES *** +% +%\usepackage{fixltx2e} +% fixltx2e, the successor to the earlier fix2col.sty, was written by +% Frank Mittelbach and David Carlisle. This package corrects a few problems +% in the LaTeX2e kernel, the most notable of which is that in current +% LaTeX2e releases, the ordering of single and double column floats is not +% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a +% single column figure to be placed prior to an earlier double column +% figure. The latest version and documentation can be found at: +% http://www.ctan.org/tex-archive/macros/latex/base/ + + + +%\usepackage{stfloats} +% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e +% the ability to do double column floats at the bottom of the page as well +% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in +% LaTeX2e). It also provides a command: +%\fnbelowfloat +% to enable the placement of footnotes below bottom floats (the standard +% LaTeX2e kernel puts them above bottom floats). This is an invasive package +% which rewrites many portions of the LaTeX2e float routines. It may not work +% with other packages that modify the LaTeX2e float routines. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ +% Documentation is contained in the stfloats.sty comments as well as in the +% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE +% does not allow \baselineskip to stretch. Authors submitting work to the +% IEEE should note that IEEE rarely uses double column equations and +% that authors should try to avoid such use. Do not be tempted to use the +% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does +% not format its papers in such ways. + + +%\ifCLASSOPTIONcaptionsoff +% \usepackage[nomarkers]{endfloat} +% \let\MYoriglatexcaption\caption +% \renewcommand{\caption}[2][\relax]{\MYoriglatexcaption[#2]{#2}} +%\fi +% endfloat.sty was written by James Darrell McCauley and Jeff Goldberg. +% This package may be useful when used in conjunction with IEEEtran.cls' +% captionsoff option. Some IEEE journals/societies require that submissions +% have lists of figures/tables at the end of the paper and that +% figures/tables without any captions are placed on a page by themselves at +% the end of the document. If needed, the draftcls IEEEtran class option or +% \CLASSINPUTbaselinestretch interface can be used to increase the line +% spacing as well. Be sure and use the nomarkers option of endfloat to +% prevent endfloat from "marking" where the figures would have been placed +% in the text. The two hack lines of code above are a slight modification of +% that suggested by in the endfloat docs (section 8.3.1) to ensure that +% the full captions always appear in the list of figures/tables - even if +% the user used the short optional argument of \caption[]{}. +% IEEE papers do not typically make use of \caption[]'s optional argument, +% so this should not be an issue. A similar trick can be used to disable +% captions of packages such as subfig.sty that lack options to turn off +% the subcaptions: +% For subfig.sty: +% \let\MYorigsubfloat\subfloat +% \renewcommand{\subfloat}[2][\relax]{\MYorigsubfloat[]{#2}} +% For subfigure.sty: +% \let\MYorigsubfigure\subfigure +% \renewcommand{\subfigure}[2][\relax]{\MYorigsubfigure[]{#2}} +% However, the above trick will not work if both optional arguments of +% the \subfloat/subfig command are used. Furthermore, there needs to be a +% description of each subfigure *somewhere* and endfloat does not add +% subfigure captions to its list of figures. Thus, the best approach is to +% avoid the use of subfigure captions (many IEEE journals avoid them anyway) +% and instead reference/explain all the subfigures within the main caption. +% The latest version of endfloat.sty and its documentation can obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/endfloat/ +% +% The IEEEtran \ifCLASSOPTIONcaptionsoff conditional can also be used +% later in the document, say, to conditionally put the References on a +% page by themselves. + + + + + +% *** PDF, URL AND HYPERLINK PACKAGES *** +% +%\usepackage{url} +% url.sty was written by Donald Arseneau. It provides better support for +% handling and breaking URLs. url.sty is already installed on most LaTeX +% systems. The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ +% Read the url.sty source comments for usage information. Basically, +% \url{my_url_here}. + + + + + +% *** Do not adjust lengths that control margins, column widths, etc. *** +% *** Do not use packages that alter fonts (such as pslatex). *** +% There should be no need to do such things with IEEEtran.cls V1.6 and later. +% (Unless specifically asked to do so by the journal or conference you plan +% to submit to, of course. ) + + +% correct bad hyphenation here +\hyphenation{op-tical net-works semi-conduc-tor} + + +\begin{document} +% +% paper title +% can use linebreaks \\ within to get better formatting as desired +\title{Bare Demo of IEEEtran.cls for Journals} +% +% +% author names and IEEE memberships +% note positions of commas and nonbreaking spaces ( ~ ) LaTeX will not break +% a structure at a ~ so this keeps an author's name from being broken across +% two lines. +% use \thanks{} to gain access to the first footnote area +% a separate \thanks must be used for each paragraph as LaTeX2e's \thanks +% was not built to handle multiple paragraphs +% + +\author{Michael~Shell,~\IEEEmembership{Member,~IEEE,} + John~Doe,~\IEEEmembership{Fellow,~OSA,} + and~Jane~Doe,~\IEEEmembership{Life~Fellow,~IEEE}% <-this % stops a space +\thanks{M. Shell is with the Department +of Electrical and Computer Engineering, Georgia Institute of Technology, Atlanta, +GA, 30332 USA e-mail: (see http://www.michaelshell.org/contact.html).}% <-this % stops a space +\thanks{J. Doe and J. Doe are with Anonymous University.}% <-this % stops a space +\thanks{Manuscript received April 19, 2005; revised January 11, 2007.}} + +% note the % following the last \IEEEmembership and also \thanks - +% these prevent an unwanted space from occurring between the last author name +% and the end of the author line. i.e., if you had this: +% +% \author{....lastname \thanks{...} \thanks{...} } +% ^------------^------------^----Do not want these spaces! +% +% a space would be appended to the last name and could cause every name on that +% line to be shifted left slightly. This is one of those "LaTeX things". For +% instance, "\textbf{A} \textbf{B}" will typeset as "A B" not "AB". To get +% "AB" then you have to do: "\textbf{A}\textbf{B}" +% \thanks is no different in this regard, so shield the last } of each \thanks +% that ends a line with a % and do not let a space in before the next \thanks. +% Spaces after \IEEEmembership other than the last one are OK (and needed) as +% you are supposed to have spaces between the names. For what it is worth, +% this is a minor point as most people would not even notice if the said evil +% space somehow managed to creep in. + + + +% The paper headers +\markboth{Journal of \LaTeX\ Class Files,~Vol.~6, No.~1, January~2007}% +{Shell \MakeLowercase{\textit{et al.}}: Bare Demo of IEEEtran.cls for Journals} +% The only time the second header will appear is for the odd numbered pages +% after the title page when using the twoside option. +% +% *** Note that you probably will NOT want to include the author's *** +% *** name in the headers of peer review papers. *** +% You can use \ifCLASSOPTIONpeerreview for conditional compilation here if +% you desire. + + + + +% If you want to put a publisher's ID mark on the page you can do it like +% this: +%\IEEEpubid{0000--0000/00\$00.00~\copyright~2007 IEEE} +% Remember, if you use this you must call \IEEEpubidadjcol in the second +% column for its text to clear the IEEEpubid mark. + + + +% use for special paper notices +%\IEEEspecialpapernotice{(Invited Paper)} + + + + +% make the title area +\maketitle + + +\begin{abstract} +%\boldmath +The abstract goes here. +\end{abstract} +% IEEEtran.cls defaults to using nonbold math in the Abstract. +% This preserves the distinction between vectors and scalars. However, +% if the journal you are submitting to favors bold math in the abstract, +% then you can use LaTeX's standard command \boldmath at the very start +% of the abstract to achieve this. Many IEEE journals frown on math +% in the abstract anyway. + +% Note that keywords are not normally used for peerreview papers. +\begin{IEEEkeywords} +IEEEtran, journal, \LaTeX, paper, template. +\end{IEEEkeywords} + + + + + + +% For peer review papers, you can put extra information on the cover +% page as needed: +% \ifCLASSOPTIONpeerreview +% \begin{center} \bfseries EDICS Category: 3-BBND \end{center} +% \fi +% +% For peerreview papers, this IEEEtran command inserts a page break and +% creates the second title. It will be ignored for other modes. +\IEEEpeerreviewmaketitle + + + +\section{Introduction} +% The very first letter is a 2 line initial drop letter followed +% by the rest of the first word in caps. +% +% form to use if the first word consists of a single letter: +% \IEEEPARstart{A}{demo} file is .... +% +% form to use if you need the single drop letter followed by +% normal text (unknown if ever used by IEEE): +% \IEEEPARstart{A}{}demo file is .... +% +% Some journals put the first two words in caps: +% \IEEEPARstart{T}{his demo} file is .... +% +% Here we have the typical use of a "T" for an initial drop letter +% and "HIS" in caps to complete the first word. +\IEEEPARstart{T}{his} demo file is intended to serve as a ``starter file'' +for IEEE journal papers produced under \LaTeX\ using +IEEEtran.cls version 1.7 and later. +% You must have at least 2 lines in the paragraph with the drop letter +% (should never be an issue) +I wish you the best of success. + +\hfill mds + +\hfill January 11, 2007 + +\subsection{Subsection Heading Here} +Subsection text here. + +% needed in second column of first page if using \IEEEpubid +%\IEEEpubidadjcol + +\subsubsection{Subsubsection Heading Here} +Subsubsection text here. + + +% An example of a floating figure using the graphicx package. +% Note that \label must occur AFTER (or within) \caption. +% For figures, \caption should occur after the \includegraphics. +% Note that IEEEtran v1.7 and later has special internal code that +% is designed to preserve the operation of \label within \caption +% even when the captionsoff option is in effect. However, because +% of issues like this, it may be the safest practice to put all your +% \label just after \caption rather than within \caption{}. +% +% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class +% option should be used if it is desired that the figures are to be +% displayed while in draft mode. +% +%\begin{figure}[!t] +%\centering +%\includegraphics[width=2.5in]{myfigure} +% where an .eps filename suffix will be assumed under latex, +% and a .pdf suffix will be assumed for pdflatex; or what has been declared +% via \DeclareGraphicsExtensions. +%\caption{Simulation Results} +%\label{fig_sim} +%\end{figure} + +% Note that IEEE typically puts floats only at the top, even when this +% results in a large percentage of a column being occupied by floats. + + +% An example of a double column floating figure using two subfigures. +% (The subfig.sty package must be loaded for this to work.) +% The subfigure \label commands are set within each subfloat command, the +% \label for the overall figure must come after \caption. +% \hfil must be used as a separator to get equal spacing. +% The subfigure.sty package works much the same way, except \subfigure is +% used instead of \subfloat. +% +%\begin{figure*}[!t] +%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}% +%\label{fig_first_case}} +%\hfil +%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}% +%\label{fig_second_case}}} +%\caption{Simulation results} +%\label{fig_sim} +%\end{figure*} +% +% Note that often IEEE papers with subfigures do not employ subfigure +% captions (using the optional argument to \subfloat), but instead will +% reference/describe all of them (a), (b), etc., within the main caption. + + +% An example of a floating table. Note that, for IEEE style tables, the +% \caption command should come BEFORE the table. Table text will default to +% \footnotesize as IEEE normally uses this smaller font for tables. +% The \label must come after \caption as always. +% +%\begin{table}[!t] +%% increase table row spacing, adjust to taste +%\renewcommand{\arraystretch}{1.3} +% if using array.sty, it might be a good idea to tweak the value of +% \extrarowheight as needed to properly center the text within the cells +%\caption{An Example of a Table} +%\label{table_example} +%\centering +%% Some packages, such as MDW tools, offer better commands for making tables +%% than the plain LaTeX2e tabular which is used here. +%\begin{tabular}{|c||c|} +%\hline +%One & Two\\ +%\hline +%Three & Four\\ +%\hline +%\end{tabular} +%\end{table} + + +% Note that IEEE does not put floats in the very first column - or typically +% anywhere on the first page for that matter. Also, in-text middle ("here") +% positioning is not used. Most IEEE journals use top floats exclusively. +% Note that, LaTeX2e, unlike IEEE journals, places footnotes above bottom +% floats. This can be corrected via the \fnbelowfloat command of the +% stfloats package. + + + +\section{Conclusion} +The conclusion goes here. + + + + + +% if have a single appendix: +%\appendix[Proof of the Zonklar Equations] +% or +%\appendix % for no appendix heading +% do not use \section anymore after \appendix, only \section* +% is possibly needed + +% use appendices with more than one appendix +% then use \section to start each appendix +% you must declare a \section before using any +% \subsection or using \label (\appendices by itself +% starts a section numbered zero.) +% + + +\appendices +\section{Proof of the First Zonklar Equation} +Appendix one text goes here. + +% you can choose not to have a title for an appendix +% if you want by leaving the argument blank +\section{} +Appendix two text goes here. + + +% use section* for acknowledgement +\section*{Acknowledgment} + + +The authors would like to thank... + + +% Can use something like this to put references on a page +% by themselves when using endfloat and the captionsoff option. +\ifCLASSOPTIONcaptionsoff + \newpage +\fi + + + +% trigger a \newpage just before the given reference +% number - used to balance the columns on the last page +% adjust value as needed - may need to be readjusted if +% the document is modified later +%\IEEEtriggeratref{8} +% The "triggered" command can be changed if desired: +%\IEEEtriggercmd{\enlargethispage{-5in}} + +% references section + +% can use a bibliography generated by BibTeX as a .bbl file +% BibTeX documentation can be easily obtained at: +% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/ +% The IEEEtran BibTeX style support page is at: +% http://www.michaelshell.org/tex/ieeetran/bibtex/ +%\bibliographystyle{IEEEtran} +% argument is your BibTeX string definitions and bibliography database(s) +%\bibliography{IEEEabrv,../bib/paper} +% +% manually copy in the resultant .bbl file +% set second argument of \begin to the number of references +% (used to reserve space for the reference number labels box) +\begin{thebibliography}{1} + +\bibitem{IEEEhowto:kopka} +H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus + 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999. + +\end{thebibliography} + +% biography section +% +% If you have an EPS/PDF photo (graphicx package needed) extra braces are +% needed around the contents of the optional argument to biography to prevent +% the LaTeX parser from getting confused when it sees the complicated +% \includegraphics command within an optional argument. (You could create +% your own custom macro containing the \includegraphics command to make things +% simpler here.) +%\begin{biography}[{\includegraphics[width=1in,height=1.25in,clip,keepaspectratio]{mshell}}]{Michael Shell} +% or if you just want to reserve a space for a photo: + +\begin{IEEEbiography}{Michael Shell} +Biography text here. +\end{IEEEbiography} + +% if you will not have a photo at all: +\begin{IEEEbiographynophoto}{John Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% insert where needed to balance the two columns on the last page with +% biographies +%\newpage + +\begin{IEEEbiographynophoto}{Jane Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% You can push biographies down or up by placing +% a \vfill before or after them. The appropriate +% use of \vfill depends on what kind of text is +% on the last page and whether or not the columns +% are being equalized. + +%\vfill + +% Can be used to pull up biographies so that the bottom of the last one +% is flush with the other column. +%\enlargethispage{-5in} + + + +% that's all folks +\end{document} + + Added: text/escience11submission/bare_jrnl_compsoc.tex =================================================================== --- text/escience11submission/bare_jrnl_compsoc.tex (rev 0) +++ text/escience11submission/bare_jrnl_compsoc.tex 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,844 @@ + +%% bare_jrnl_compsoc.tex +%% V1.3 +%% 2007/01/11 +%% by Michael Shell +%% See: +%% http://www.michaelshell.org/ +%% for current contact information. +%% +%% This is a skeleton file demonstrating the use of IEEEtran.cls +%% (requires IEEEtran.cls version 1.7 or later) with an IEEE Computer +%% Society journal paper. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ + +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%%************************************************************************* + +% *** Authors should verify (and, if needed, correct) their LaTeX system *** +% *** with the testflow diagnostic prior to trusting their LaTeX platform *** +% *** with production work. IEEE's font choices can trigger bugs that do *** +% *** not appear when using other class files. *** +% The testflow support page is at: +% http://www.michaelshell.org/tex/testflow/ + + + + +% Note that the a4paper option is mainly intended so that authors in +% countries using A4 can easily print to A4 and see how their papers will +% look in print - the typesetting of the document will not typically be +% affected with changes in paper size (but the bottom and side margins will). +% Use the testflow package mentioned above to verify correct handling of +% both paper sizes by the user's LaTeX system. +% +% Also note that the "draftcls" or "draftclsnofoot", not "draft", option +% should be used if it is desired that the figures are to be displayed in +% draft mode. +% +% The Computer Society usually requires 12pt for submissions. +% +\documentclass[12pt,journal,compsoc]{IEEEtran} +% +% If IEEEtran.cls has not been installed into the LaTeX system files, +% manually specify the path to it like: +% \documentclass[12pt,journal,compsoc]{../sty/IEEEtran} + + + + + +% Some very useful LaTeX packages include: +% (uncomment the ones you want to load) + + +% *** MISC UTILITY PACKAGES *** +% +%\usepackage{ifpdf} +% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional +% compilation based on whether the output is pdf or dvi. +% usage: +% \ifpdf +% % pdf code +% \else +% % dvi code +% \fi +% The latest version of ifpdf.sty can be obtained from: +% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ +% Also, note that IEEEtran.cls V1.7 and later provides a builtin +% \ifCLASSINFOpdf conditional that works the same way. +% When switching from latex to pdflatex and vice-versa, the compiler may +% have to be run twice to clear warning/error messages. + + + + + + +% *** CITATION PACKAGES *** +% +\ifCLASSOPTIONcompsoc + % IEEE Computer Society needs nocompress option + % requires cite.sty v4.0 or later (November 2003) + % \usepackage[nocompress]{cite} +\else + % normal IEEE + % \usepackage{cite} +\fi +% cite.sty was written by Donald Arseneau +% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package +% \cite{} output to follow that of IEEE. Loading the cite package will +% result in citation numbers being automatically sorted and properly +% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using +% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's +% \cite will automatically add leading space, if needed. Use cite.sty's +% noadjust option (cite.sty V3.8 and later) if you want to turn this off. +% cite.sty is already installed on most LaTeX systems. Be sure and use +% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does +% not currently provide for hyperlinked citations. +% The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ +% The documentation is contained in the cite.sty file itself. +% +% Note that some packages require special options to format as the Computer +% Society requires. In particular, Computer Society papers do not use +% compressed citation ranges as is done in typical IEEE papers +% (e.g., [1]-[4]). Instead, they list every citation separately in order +% (e.g., [1], [2], [3], [4]). To get the latter we need to load the cite +% package with the nocompress option which is supported by cite.sty v4.0 +% and later. Note also the use of a CLASSOPTION conditional provided by +% IEEEtran.cls V1.7 and later. + + + + + +% *** GRAPHICS RELATED PACKAGES *** +% +\ifCLASSINFOpdf + % \usepackage[pdftex]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../pdf/}{../jpeg/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} +\else + % or other class option (dvipsone, dvipdf, if not using dvips). graphicx + % will default to the driver specified in the system graphics.cfg if no + % driver is specified. + % \usepackage[dvips]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../eps/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.eps} +\fi +% graphicx was written by David Carlisle and Sebastian Rahtz. It is +% required if you want graphics, photos, etc. graphicx.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/graphics/ +% Another good source of documentation is "Using Imported Graphics in +% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or +% epslatex.pdf at: http://www.ctan.org/tex-archive/info/ +% +% latex, and pdflatex in dvi mode, support graphics in encapsulated +% postscript (.eps) format. pdflatex in pdf mode supports graphics +% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure +% that all non-photo figures use a vector format (.eps, .pdf, .mps) and +% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats +% which can result in "jaggedy"/blurry rendering of lines and letters as +% well as large increases in file sizes. +% +% You can find documentation about the pdfTeX application at: +% http://www.tug.org/applications/pdftex + + + + + +% *** MATH PACKAGES *** +% +%\usepackage[cmex10]{amsmath} +% A popular package from the American Mathematical Society that provides +% many useful and powerful commands for dealing with mathematics. If using +% it, be sure to load this package with the cmex10 option to ensure that +% only type 1 fonts will utilized at all point sizes. Without this option, +% it is possible that some math symbols, particularly those within +% footnotes, will be rendered in bitmap form which will result in a +% document that can not be IEEE Xplore compliant! +% +% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 +% thus preventing page breaks from occurring within multiline equations. Use: +%\interdisplaylinepenalty=2500 +% after loading amsmath to restore such page breaks as IEEEtran.cls normally +% does. amsmath.sty is already installed on most LaTeX systems. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ + + + + + +% *** SPECIALIZED LIST PACKAGES *** +% +%\usepackage{algorithmic} +% algorithmic.sty was written by Peter Williams and Rogerio Brito. +% This package provides an algorithmic environment fo describing algorithms. +% You can use the algorithmic environment in-text or within a figure +% environment to provide for a floating algorithm. Do NOT use the algorithm +% floating environment provided by algorithm.sty (by the same authors) or +% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated +% algorithm float types and packages that provide these will not provide +% correct IEEE style captions. The latest version and documentation of +% algorithmic.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ +% There is also a support site at: +% http://algorithms.berlios.de/index.html +% Also of interest may be the (relatively newer and more customizable) +% algorithmicx.sty package by Szasz Janos: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ + + + + +% *** ALIGNMENT PACKAGES *** +% +%\usepackage{array} +% Frank Mittelbach's and David Carlisle's array.sty patches and improves +% the standard LaTeX2e array and tabular environments to provide better +% appearance and additional user controls. As the default LaTeX2e table +% generation code is lacking to the point of almost being broken with +% respect to the quality of the end results, all users are strongly +% advised to use an enhanced (at the very least that provided by array.sty) +% set of table tools. array.sty is already installed on most systems. The +% latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/tools/ + + +%\usepackage{mdwmath} +%\usepackage{mdwtab} +% Also highly recommended is Mark Wooding's extremely powerful MDW tools, +% especially mdwmath.sty and mdwtab.sty which are used to format equations +% and tables, respectively. The MDWtools set is already installed on most +% LaTeX systems. The lastest version and documentation is available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ + + +% IEEEtran contains the IEEEeqnarray family of commands that can be used to +% generate multiline equations as well as matrices, tables, etc., of high +% quality. + + +%\usepackage{eqparbox} +% Also of notable interest is Scott Pakin's eqparbox package for creating +% (automatically sized) equal width boxes - aka "natural width parboxes". +% Available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ + + + + + +% *** SUBFIGURE PACKAGES *** +%\ifCLASSOPTIONcompsoc +%\usepackage[tight,normalsize,sf,SF]{subfigure} +%\else +%\usepackage[tight,footnotesize]{subfigure} +%\fi +% subfigure.sty was written by Steven Douglas Cochran. This package makes it +% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE +% work, it is a good idea to load it with the tight package option to reduce +% the amount of white space around the subfigures. Computer Society papers +% use a larger font and \sffamily font for their captions, hence the +% additional options needed under compsoc mode. subfigure.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ +% subfigure.sty has been superceeded by subfig.sty. + + +%\ifCLASSOPTIONcompsoc +% \usepackage[caption=false]{caption} +% \usepackage[font=normalsize,labelfont=sf,textfont=sf]{subfig} +%\else +% \usepackage[caption=false]{caption} +% \usepackage[font=footnotesize]{subfig} +%\fi +% subfig.sty, also written by Steven Douglas Cochran, is the modern +% replacement for subfigure.sty. However, subfig.sty requires and +% automatically loads Axel Sommerfeldt's caption.sty which will override +% IEEEtran.cls handling of captions and this will result in nonIEEE style +% figure/table captions. To prevent this problem, be sure and preload +% caption.sty with its "caption=false" package option. This is will preserve +% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later +% (recommended due to many improvements over 1.2) of subfig.sty supports +% the caption=false option directly: +%\ifCLASSOPTIONcompsoc +% \usepackage[caption=false,font=normalsize,labelfont=sf,textfont=sf]{subfig} +%\else +% \usepackage[caption=false,font=footnotesize]{subfig} +%\fi +% +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ +% The latest version and documentation of caption.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ + + + + +% *** FLOAT PACKAGES *** +% +%\usepackage{fixltx2e} +% fixltx2e, the successor to the earlier fix2col.sty, was written by +% Frank Mittelbach and David Carlisle. This package corrects a few problems +% in the LaTeX2e kernel, the most notable of which is that in current +% LaTeX2e releases, the ordering of single and double column floats is not +% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a +% single column figure to be placed prior to an earlier double column +% figure. The latest version and documentation can be found at: +% http://www.ctan.org/tex-archive/macros/latex/base/ + + + +%\usepackage{stfloats} +% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e +% the ability to do double column floats at the bottom of the page as well +% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in +% LaTeX2e). It also provides a command: +%\fnbelowfloat +% to enable the placement of footnotes below bottom floats (the standard +% LaTeX2e kernel puts them above bottom floats). This is an invasive package +% which rewrites many portions of the LaTeX2e float routines. It may not work +% with other packages that modify the LaTeX2e float routines. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ +% Documentation is contained in the stfloats.sty comments as well as in the +% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE +% does not allow \baselineskip to stretch. Authors submitting work to the +% IEEE should note that IEEE rarely uses double column equations and +% that authors should try to avoid such use. Do not be tempted to use the +% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does +% not format its papers in such ways. + + + + +%\ifCLASSOPTIONcaptionsoff +% \usepackage[nomarkers]{endfloat} +% \let\MYoriglatexcaption\caption +% \renewcommand{\caption}[2][\relax]{\MYoriglatexcaption[#2]{#2}} +%\fi +% endfloat.sty was written by James Darrell McCauley and Jeff Goldberg. +% This package may be useful when used in conjunction with IEEEtran.cls' +% captionsoff option. Some IEEE journals/societies require that submissions +% have lists of figures/tables at the end of the paper and that +% figures/tables without any captions are placed on a page by themselves at +% the end of the document. If needed, the draftcls IEEEtran class option or +% \CLASSINPUTbaselinestretch interface can be used to increase the line +% spacing as well. Be sure and use the nomarkers option of endfloat to +% prevent endfloat from "marking" where the figures would have been placed +% in the text. The two hack lines of code above are a slight modification of +% that suggested by in the endfloat docs (section 8.3.1) to ensure that +% the full captions always appear in the list of figures/tables - even if +% the user used the short optional argument of \caption[]{}. +% IEEE papers do not typically make use of \caption[]'s optional argument, +% so this should not be an issue. A similar trick can be used to disable +% captions of packages such as subfig.sty that lack options to turn off +% the subcaptions: +% For subfig.sty: +% \let\MYorigsubfloat\subfloat +% \renewcommand{\subfloat}[2][\relax]{\MYorigsubfloat[]{#2}} +% For subfigure.sty: +% \let\MYorigsubfigure\subfigure +% \renewcommand{\subfigure}[2][\relax]{\MYorigsubfigure[]{#2}} +% However, the above trick will not work if both optional arguments of +% the \subfloat/subfig command are used. Furthermore, there needs to be a +% description of each subfigure *somewhere* and endfloat does not add +% subfigure captions to its list of figures. Thus, the best approach is to +% avoid the use of subfigure captions (many IEEE journals avoid them anyway) +% and instead reference/explain all the subfigures within the main caption. +% The latest version of endfloat.sty and its documentation can obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/endfloat/ +% +% The IEEEtran \ifCLASSOPTIONcaptionsoff conditional can also be used +% later in the document, say, to conditionally put the References on a +% page by themselves. + + + + +% *** PDF, URL AND HYPERLINK PACKAGES *** +% +%\usepackage{url} +% url.sty was written by Donald Arseneau. It provides better support for +% handling and breaking URLs. url.sty is already installed on most LaTeX +% systems. The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ +% Read the url.sty source comments for usage information. Basically, +% \url{my_url_here}. + + + + + +% *** Do not adjust lengths that control margins, column widths, etc. *** +% *** Do not use packages that alter fonts (such as pslatex). *** +% There should be no need to do such things with IEEEtran.cls V1.6 and later. +% (Unless specifically asked to do so by the journal or conference you plan +% to submit to, of course. ) + + +% correct bad hyphenation here +\hyphenation{op-tical net-works semi-conduc-tor} + + +\begin{document} +% +% paper title +% can use linebreaks \\ within to get better formatting as desired +\title{Bare Demo of IEEEtran.cls\\ for Computer Society Journals} +% +% +% author names and IEEE memberships +% note positions of commas and nonbreaking spaces ( ~ ) LaTeX will not break +% a structure at a ~ so this keeps an author's name from being broken across +% two lines. +% use \thanks{} to gain access to the first footnote area +% a separate \thanks must be used for each paragraph as LaTeX2e's \thanks +% was not built to handle multiple paragraphs +% +% +%\IEEEcompsocitemizethanks is a special \thanks that produces the bulleted +% lists the Computer Society journals use for "first footnote" author +% affiliations. Use \IEEEcompsocthanksitem which works much like \item +% for each affiliation group. When not in compsoc mode, +% \IEEEcompsocitemizethanks becomes like \thanks and +% \IEEEcompsocthanksitem becomes a line break with idention. This +% facilitates dual compilation, although admittedly the differences in the +% desired content of \author between the different types of papers makes a +% one-size-fits-all approach a daunting prospect. For instance, compsoc +% journal papers have the author affiliations above the "Manuscript +% received ..." text while in non-compsoc journals this is reversed. Sigh. + +\author{Michael~Shell,~\IEEEmembership{Member,~IEEE,} + John~Doe,~\IEEEmembership{Fellow,~OSA,} + and~Jane~Doe,~\IEEEmembership{Life~Fellow,~IEEE}% <-this % stops a space +\IEEEcompsocitemizethanks{\IEEEcompsocthanksitem M. Shell is with the Department +of Electrical and Computer Engineering, Georgia Institute of Technology, Atlanta, +GA, 30332.\protect\\ +% note need leading \protect in front of \\ to get a newline within \thanks as +% \\ is fragile and will error, could use \hfil\break instead. +E-mail: see http://www.michaelshell.org/contact.html +\IEEEcompsocthanksitem J. Doe and J. Doe are with Anonymous University.}% <-this % stops a space +\thanks{Manuscript received April 19, 2005; revised January 11, 2007.}} + +% note the % following the last \IEEEmembership and also \thanks - +% these prevent an unwanted space from occurring between the last author name +% and the end of the author line. i.e., if you had this: +% +% \author{....lastname \thanks{...} \thanks{...} } +% ^------------^------------^----Do not want these spaces! +% +% a space would be appended to the last name and could cause every name on that +% line to be shifted left slightly. This is one of those "LaTeX things". For +% instance, "\textbf{A} \textbf{B}" will typeset as "A B" not "AB". To get +% "AB" then you have to do: "\textbf{A}\textbf{B}" +% \thanks is no different in this regard, so shield the last } of each \thanks +% that ends a line with a % and do not let a space in before the next \thanks. +% Spaces after \IEEEmembership other than the last one are OK (and needed) as +% you are supposed to have spaces between the names. For what it is worth, +% this is a minor point as most people would not even notice if the said evil +% space somehow managed to creep in. + + + +% The paper headers +\markboth{Journal of \LaTeX\ Class Files,~Vol.~6, No.~1, January~2007}% +{Shell \MakeLowercase{\textit{et al.}}: Bare Demo of IEEEtran.cls for Computer Society Journals} +% The only time the second header will appear is for the odd numbered pages +% after the title page when using the twoside option. +% +% *** Note that you probably will NOT want to include the author's *** +% *** name in the headers of peer review papers. *** +% You can use \ifCLASSOPTIONpeerreview for conditional compilation here if +% you desire. + + + +% The publisher's ID mark at the bottom of the page is less important with +% Computer Society journal papers as those publications place the marks +% outside of the main text columns and, therefore, unlike regular IEEE +% journals, the available text space is not reduced by their presence. +% If you want to put a publisher's ID mark on the page you can do it like +% this: +%\IEEEpubid{0000--0000/00\$00.00~\copyright~2007 IEEE} +% or like this to get the Computer Society new two part style. +%\IEEEpubid{\makebox[\columnwidth]{\hfill 0000--0000/00/\$00.00~\copyright~2007 IEEE}% +%\hspace{\columnsep}\makebox[\columnwidth]{Published by the IEEE Computer Society\hfill}} +% Remember, if you use this you must call \IEEEpubidadjcol in the second +% column for its text to clear the IEEEpubid mark (Computer Society jorunal +% papers don't need this extra clearance.) + + + +% use for special paper notices +%\IEEEspecialpapernotice{(Invited Paper)} + + + +% for Computer Society papers, we must declare the abstract and index terms +% PRIOR to the title within the \IEEEcompsoctitleabstractindextext IEEEtran +% command as these need to go into the title area created by \maketitle. +\IEEEcompsoctitleabstractindextext{% +\begin{abstract} +%\boldmath +The abstract goes here. +\end{abstract} +% IEEEtran.cls defaults to using nonbold math in the Abstract. +% This preserves the distinction between vectors and scalars. However, +% if the journal you are submitting to favors bold math in the abstract, +% then you can use LaTeX's standard command \boldmath at the very start +% of the abstract to achieve this. Many IEEE journals frown on math +% in the abstract anyway. In particular, the Computer Society does +% not want either math or citations to appear in the abstract. + +% Note that keywords are not normally used for peerreview papers. +\begin{IEEEkeywords} +Computer Society, IEEEtran, journal, \LaTeX, paper, template. +\end{IEEEkeywords}} + + +% make the title area +\maketitle + + +% To allow for easy dual compilation without having to reenter the +% abstract/keywords data, the \IEEEcompsoctitleabstractindextext text will +% not be used in maketitle, but will appear (i.e., to be "transported") +% here as \IEEEdisplaynotcompsoctitleabstractindextext when compsoc mode +% is not selected if conference mode is selected - because compsoc +% conference papers position the abstract like regular (non-compsoc) +% papers do! +\IEEEdisplaynotcompsoctitleabstractindextext +% \IEEEdisplaynotcompsoctitleabstractindextext has no effect when using +% compsoc under a non-conference mode. + + +% For peer review papers, you can put extra information on the cover +% page as needed: +% \ifCLASSOPTIONpeerreview +% \begin{center} \bfseries EDICS Category: 3-BBND \end{center} +% \fi +% +% For peerreview papers, this IEEEtran command inserts a page break and +% creates the second title. It will be ignored for other modes. +\IEEEpeerreviewmaketitle + + + +\section{Introduction} +% Computer Society journal papers do something a tad strange with the very +% first section heading (almost always called "Introduction"). They place it +% ABOVE the main text! IEEEtran.cls currently does not do this for you. +% However, You can achieve this effect by making LaTeX jump through some +% hoops via something like: +% +%\ifCLASSOPTIONcompsoc +% \noindent\raisebox{2\baselineskip}[0pt][0pt]% +% {\parbox{\columnwidth}{\section{Introduction}\label{sec:introduction}% +% \global\everypar=\everypar}}% +% \vspace{-1\baselineskip}\vspace{-\parskip}\par +%\else +% \section{Introduction}\label{sec:introduction}\par +%\fi +% +% Admittedly, this is a hack and may well be fragile, but seems to do the +% trick for me. Note the need to keep any \label that may be used right +% after \section in the above as the hack puts \section within a raised box. + + + +% The very first letter is a 2 line initial drop letter followed +% by the rest of the first word in caps (small caps for compsoc). +% +% form to use if the first word consists of a single letter: +% \IEEEPARstart{A}{demo} file is .... +% +% form to use if you need the single drop letter followed by +% normal text (unknown if ever used by IEEE): +% \IEEEPARstart{A}{}demo file is .... +% +% Some journals put the first two words in caps: +% \IEEEPARstart{T}{his demo} file is .... +% +% Here we have the typical use of a "T" for an initial drop letter +% and "HIS" in caps to complete the first word. +\IEEEPARstart{T}{his} demo file is intended to serve as a ``starter file'' +for IEEE Computer Society journal papers produced under \LaTeX\ using +IEEEtran.cls version 1.7 and later. +% You must have at least 2 lines in the paragraph with the drop letter +% (should never be an issue) +I wish you the best of success. + +\hfill mds + +\hfill January 11, 2007 + +\subsection{Subsection Heading Here} +Subsection text here. + +% needed in second column of first page if using \IEEEpubid +%\IEEEpubidadjcol + +\subsubsection{Subsubsection Heading Here} +Subsubsection text here. + + +% An example of a floating figure using the graphicx package. +% Note that \label must occur AFTER (or within) \caption. +% For figures, \caption should occur after the \includegraphics. +% Note that IEEEtran v1.7 and later has special internal code that +% is designed to preserve the operation of \label within \caption +% even when the captionsoff option is in effect. However, because +% of issues like this, it may be the safest practice to put all your +% \label just after \caption rather than within \caption{}. +% +% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class +% option should be used if it is desired that the figures are to be +% displayed while in draft mode. +% +%\begin{figure}[!t] +%\centering +%\includegraphics[width=2.5in]{myfigure} +% where an .eps filename suffix will be assumed under latex, +% and a .pdf suffix will be assumed for pdflatex; or what has been declared +% via \DeclareGraphicsExtensions. +%\caption{Simulation Results} +%\label{fig_sim} +%\end{figure} + +% Note that IEEE typically puts floats only at the top, even when this +% results in a large percentage of a column being occupied by floats. +% However, the Computer Society has been known to put floats at the bottom. + + +% An example of a double column floating figure using two subfigures. +% (The subfig.sty package must be loaded for this to work.) +% The subfigure \label commands are set within each subfloat command, the +% \label for the overall figure must come after \caption. +% \hfil must be used as a separator to get equal spacing. +% The subfigure.sty package works much the same way, except \subfigure is +% used instead of \subfloat. +% +%\begin{figure*}[!t] +%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}% +%\label{fig_first_case}} +%\hfil +%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}% +%\label{fig_second_case}}} +%\caption{Simulation results} +%\label{fig_sim} +%\end{figure*} +% +% Note that often IEEE papers with subfigures do not employ subfigure +% captions (using the optional argument to \subfloat), but instead will +% reference/describe all of them (a), (b), etc., within the main caption. + + +% An example of a floating table. Note that, for IEEE style tables, the +% \caption command should come BEFORE the table. Table text will default to +% \footnotesize as IEEE normally uses this smaller font for tables. +% The \label must come after \caption as always. +% +%\begin{table}[!t] +%% increase table row spacing, adjust to taste +%\renewcommand{\arraystretch}{1.3} +% if using array.sty, it might be a good idea to tweak the value of +% \extrarowheight as needed to properly center the text within the cells +%\caption{An Example of a Table} +%\label{table_example} +%\centering +%% Some packages, such as MDW tools, offer better commands for making tables +%% than the plain LaTeX2e tabular which is used here. +%\begin{tabular}{|c||c|} +%\hline +%One & Two\\ +%\hline +%Three & Four\\ +%\hline +%\end{tabular} +%\end{table} + + +% Note that IEEE does not put floats in the very first column - or typically +% anywhere on the first page for that matter. Also, in-text middle ("here") +% positioning is not used. Most IEEE journals use top floats exclusively. +% However, Computer Society journals sometimes do use bottom floats - bear +% this in mind when choosing appropriate optional arguments for the +% figure/table environments. +% Note that, LaTeX2e, unlike IEEE journals, places footnotes above bottom +% floats. This can be corrected via the \fnbelowfloat command of the +% stfloats package. + + + +\section{Conclusion} +The conclusion goes here. + + + + + +% if have a single appendix: +%\appendix[Proof of the Zonklar Equations] +% or +%\appendix % for no appendix heading +% do not use \section anymore after \appendix, only \section* +% is possibly needed + +% use appendices with more than one appendix +% then use \section to start each appendix +% you must declare a \section before using any +% \subsection or using \label (\appendices by itself +% starts a section numbered zero.) +% + + +\appendices +\section{Proof of the First Zonklar Equation} +Appendix one text goes here. + +% you can choose not to have a title for an appendix +% if you want by leaving the argument blank +\section{} +Appendix two text goes here. + + +% use section* for acknowledgement +\ifCLASSOPTIONcompsoc + % The Computer Society usually uses the plural form + \section*{Acknowledgments} +\else + % regular IEEE prefers the singular form + \section*{Acknowledgment} +\fi + + +The authors would like to thank... + + +% Can use something like this to put references on a page +% by themselves when using endfloat and the captionsoff option. +\ifCLASSOPTIONcaptionsoff + \newpage +\fi + + + +% trigger a \newpage just before the given reference +% number - used to balance the columns on the last page +% adjust value as needed - may need to be readjusted if +% the document is modified later +%\IEEEtriggeratref{8} +% The "triggered" command can be changed if desired: +%\IEEEtriggercmd{\enlargethispage{-5in}} + +% references section + +% can use a bibliography generated by BibTeX as a .bbl file +% BibTeX documentation can be easily obtained at: +% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/ +% The IEEEtran BibTeX style support page is at: +% http://www.michaelshell.org/tex/ieeetran/bibtex/ +%\bibliographystyle{IEEEtran} +% argument is your BibTeX string definitions and bibliography database(s) +%\bibliography{IEEEabrv,../bib/paper} +% +% manually copy in the resultant .bbl file +% set second argument of \begin to the number of references +% (used to reserve space for the reference number labels box) +\begin{thebibliography}{1} + +\bibitem{IEEEhowto:kopka} +H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus + 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999. + +\end{thebibliography} + +% biography section +% +% If you have an EPS/PDF photo (graphicx package needed) extra braces are +% needed around the contents of the optional argument to biography to prevent +% the LaTeX parser from getting confused when it sees the complicated +% \includegraphics command within an optional argument. (You could create +% your own custom macro containing the \includegraphics command to make things +% simpler here.) +%\begin{biography}[{\includegraphics[width=1in,height=1.25in,clip,keepaspectratio]{mshell}}]{Michael Shell} +% or if you just want to reserve a space for a photo: + +\begin{IEEEbiography}{Michael Shell} +Biography text here. +\end{IEEEbiography} + +% if you will not have a photo at all: +\begin{IEEEbiographynophoto}{John Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% insert where needed to balance the two columns on the last page with +% biographies +%\newpage + +\begin{IEEEbiographynophoto}{Jane Doe} +Biography text here. +\end{IEEEbiographynophoto} + +% You can push biographies down or up by placing +% a \vfill before or after them. The appropriate +% use of \vfill depends on what kind of text is +% on the last page and whether or not the columns +% are being equalized. + +%\vfill + +% Can be used to pull up biographies so that the bottom of the last one +% is flush with the other column. +%\enlargethispage{-5in} + + + +% that's all folks +\end{document} + + Added: text/escience11submission/changelog.txt =================================================================== --- text/escience11submission/changelog.txt (rev 0) +++ text/escience11submission/changelog.txt 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,677 @@ + + + Changelog history of the IEEEtran LaTeX class. + 2007/03/05 + by Michael Shell (MDS) + http://www.michaelshell.org/ + + + +******* + 3/2007 V1.7a (MDS) changes: + + 1) Corrected problem of unwanted two column peer review title page format. + Thanks to Virgilio Rodriguez for reporting this bug. + + 2) "depreciated" -> "deprecated". Thanks to Virgilio Rodriguez for + suggesting this change. + + + +******* + 1/2007 V1.7 (MDS) changes: + + 1) New class option compsoc to support the IEEE Computer Society format. + + 2) New class option captionsoff disables the display of figure/table + captions. endfloat.sty is now mentioned in the docs. Thanks to Geoff + Walker for suggesting these changes. + + 3) Fixed compatibility issues with subfig.sty and caption.sty. Thanks to + Steven Douglas Cochran and Axel Sommerfeldt for suggesting this change. + + 4) New \CLASSINPUT, \CLASSOPTION and \CLASSINFO interface allows for more + user control and conditional compilation. + + 5) \ifcenterfigcaptions (\centerfigcaptionstrue, \centerfigcaptionsfalse), + \CMPARstart and \overrideIEEEmargins have been removed and no are + longer supported. The effect of \overrideIEEEmargins can be mimicked + via the more general \CLASSINPUT interface: + % US letter paper: + \newcommand{\CLASSINPUTinnersidemargin}{0.775in} + \newcommand{\CLASSINPUToutersidemargin}{0.585in} + % A4 paper: + \newcommand{\CLASSINPUTinnersidemargin}{17mm} + \newcommand{\CLASSINPUToutersidemargin}{11.647mm} + + 6) Several commands and environments have been deprecated in favor of + replacements with IEEE prefixes to better avoid potential future name + clashes with other packages. Legacy code retained to allow the use of + the obsolete forms (for now), but with a warning message to the console + during compilation: + \IEEEauthorblockA, \IEEEauthorblockN, \IEEEauthorrefmark, + \IEEEbiography, \IEEEbiographynophoto, \IEEEkeywords, \IEEEPARstart, + \IEEEproof, \IEEEpubid, \IEEEpubidadjcol, \IEEEQED, \IEEEQEDclosed, + \IEEEQEDopen, \IEEEspecialpapernotice. IEEEtran.cls now redefines + \proof in way to avoid problems with the amsthm.sty package. + For IED lists: + \IEEEiedlabeljustifyc, \IEEEiedlabeljustifyl, \IEEEiedlabeljustifyr, + \IEEEnocalcleftmargin, \IEEElabelindent, \IEEEsetlabelwidth, + \IEEEusemathlabelsep + + 7) These commands/lengths now require the IEEE prefix and do not have + legacy support: \IEEEnormaljot. + For IED lists: \ifIEEEnocalcleftmargin, \ifIEEEnolabelindentfactor, + \IEEEiedlistdecl, \IEEElabelindentfactor + + 8) \normalsizebaselineskip skip replaced by + \CLASSINFOnormalsizebaselineskip (nonrubber dimen) length. + Also, new \CLASSINFOnormalsizeunitybaselineskip (nonrubber dimen) + provided. + + 9) Now defaults to using Alpha numbering rather than Roman for appendices + numbering. This is because Alpha numbering is more common and avoids + problems with theorem numbering. \ifuseRomanappendices + (\useRomanappendicestrue, \useRomanappendicesfalse) is no longer + supported. Instead, use the new class option romanappendices if Roman + appendices numbering is desired. Thanks to Leonid Mirkin for reporting + the problem with theorems in appendices and suggesting changes. + +10) Improved paper size setting code for pdflatex. + +11) Better handling of theorem numbering when using the section counter + within the appendix(cies). Thanks to Leonid Mirkin for suggesting + this change. + +12) Fixed bug that caused equations at the end of theorems to be too + close to the line below them. + +13) Provided hook to conference mode console notice and changed notice to + better support conferences that use A4 paper. Thanks to Volker Kuhlmann + for suggesting this change. + +14) \IEEEauthorrefmark made robust to allow it to be used in \thanks + without a leading \protect + +15) Improved \textunderscore to provide a much better fake _ when used with + OT1 encoding. Under OT1, detect use of pcr or cmtt \ttfamily and use + available true _ glyph for those two typewriter fonts. + +16) Revised internal \@sect command to be more robust for users who employ + modified section heading formats. Thanks to Zarko F. Cucej for + suggesting this change. + +17) Improved \thesubsubsection definition to prevent breaks at the hyphen. + Thanks to Moritz Borgmann for suggesting this change. Thanks to + Dan Luecking and Heiko Oberdiek for explaining some of the various + alternatives and techniques to fix it. + +18) No longer provide \NAT at parse hack to get cite.sty to play (somewhat) + with hyperref.sty as this is already included in cite.sty version + 4.0 (2003-05-27) and later. + +19) At the beginning of document, set the default style of url.sty to be + the same as the current text font - as is done in IEEE journals. + +20) Corrected excessive line spacing in journal table captions. Thanks to + Moritz Borgmann for suggesting this change. + +21) Corrected \thesubsubsection to use the "I-A1" format IEEE uses rather + than "I-A.1" as was done before. Ditto for \theparagraph. Thanks to + Moritz Borgmann for suggesting this change. + +22) Enclose papersize specials within \AtBeginDvi in case someone wants + to make a format with IEEEtran. Thanks to Moritz Borgmann for + suggesting this change. + +23) Eliminated the small space after abstract and keywords dash as IEEE + now does. Thanks to Moritz Borgmann for suggesting this change. + +24) IEEEkeywords is no longer locked out in conference mode + +25) Increase defaults of \binoppenalty and \relpenalty to discourage + breaks within equations. Thanks to Moritz Borgmann for suggesting + this change. + +26) Support optional argument for IEEEproof. Thanks to Ingo Steinwart for + suggesting this change. Also, start a new \par with \IEEEproof. + +27) Add support for an optional argument to \bstctlcite. + +28) Changed \topfraction and \dbltopfraction from 1.0 to 0.9. Thanks to + Donald Arseneau for suggesting this change. + + +******* + 09/2005 V1.6c (MDS) changes: + + 1) Changed endfigure/endfloat definitions so as not to cause problems with + preview-LaTeX and other packages. Thanks to Stephan Heuel and David + Kastrup for reporting this problem. + + + +******* + 11/2002 V1.6b (MDS) changes: + + 1) Fixed problem with figure captions when using hyperref. Thanks to + Leandro Barajas and Michael Bassetti for reporting this bug. + + 2) Provide a fake nabib command \NAT at parse so that hyperref will not + interfere with the operation of cite.sty. However, as a result citation + numbers will not be hyperlinked. Also, natbib will not be able to work + with IEEEtran. However, this is perhaps the best solution until + cite.sty and hyperref.sty are able to co-exist with each other. + It easy enough to override the fake command via: + \makeatletter + \let\NAT at parse\undefined + \makeatother + + 3) Revised font selection method so as not to have problems when used + with setspace.sty. Thanks to Zhang Yan for reporting this bug. + + 4) Added \special to feed papersize to dvips. Thanks to Moritz Borgmann + for suggesting this feature. + + 5) In addition to the IEEE IED lists, the original IED style list + environments (as is done in article.cls) are now provided as + LaTeXitemize, LaTeXenumerate, and LaTeXdescription. Also, users can + now redefine \makelabel within IEEE IED list controls. There may be + some use for this in specialized applications. Thanks to Eli Barzilay + for suggesting this feature. + + 6) \table* now defaults to \footnotesize text like \table. + + 7) The draft modes now no longer force a pagebreak after the title. + Thanks to Christian Peel for suggesting this change. + + 8) New draftclsnofoot mode is like draftcls, but does not display the + date and the word "DRAFT" at the foot of the page. Thanks to + Christian Peel for suggesting this feature. + + 9) New peerreview and peerreviewca modes with \IEEEpeerreviewmaketitle + command allows for a "cover" titlepage for anonymous peer review. + Except for the cover titlepage, peerreview is much like journal mode. + peerreviewca is like peerreview, but allows the author names to be + entered and formatted as under conference mode so that author + affiliations and contact information can be easily seen on the cover + page. Thanks to Eric Benedict for suggesting this feature. + + + +******* + 7/2002 V1.6 (MDS) changes: + + 1) Added conference mode via conference option. Defaults to the + traditional journal mode. e.g., \documentclass[conference]{IEEEtran} + + 2) Added support for A4 paper via new a4paper option. Pdflatex's paper + size lengths are now automatically set to the proper paper size being + used. + + 3) Revised margins again. Page text is now horizontally centered. + Conference mode increases the top and bottom margins with the bottom + margin being slightly larger. For A4 paper, the top margin and text + typesetting will not change from those of US letter paper, but the side + margins will be smaller and the bottom margin will be larger than that + of US letter. All per IEEE specs. + + 4) Fixed footnote line spacing anomaly in draft mode. + Thanks to Alberto Rodriguez for reporting this bug. + + Also, slightly revised footnote and \thanks note spacing. + Set \interfootnotelinepenalty=10000 to prevent LaTeX + from breaking footnotes across multiple pages or columns. + + 5) Fixed bug that caused overwritten photo areas and sometimes anomalous + spacing when a new paragraph was started within a biography. Also, + the presence of \par's, new lines or spaces at the beginning of + abstract, keywords, biography, or biographynophoto will no longer + affect the first word spacing. + Thanks to Eric Durant for reporting this bug. + + The biography environment now does a better job in preventing + a biography photo area from being broken across pages or columns. + + 6) Fixed whitespace between \cite entries bug. i.e., + both \cite{einstein24, knuth84} and \cite{einstein24,knuth84} + are now valid. \cite is now a robust command as it should be. + IEEEtran now no longer defines the old non-standard \shortcite or + \citename. + + The base IEEEtran.cls does not sort citation numbers or produce ranges + for three or more consecutive numbers. However, V1.6 of IEEEtran.cls + now pre-defines the following format control macros to facilitate easy + use with Donald Arseneau's cite.sty package (tested with cite.sty V3.9): + + \def\citepunct{], [} + \def\citedash{]--[} + + cite.sty is standard on most LaTeX sytems and can be obtained from + www.ctan.org. Thanks to Donald Arseneau for creating cite.sty, + providing the required format arguments to produce the IEEE style + and designing a cite interface capable of handling the IEEE citation + style. + + Note: Historically, IEEE has wanted authors to "hardcode" symbolics. + (i.e., replace all \cite{} with fixed [x]). However, it now seems that + most electronic manuscript submissions to IEEE are in .pdf format, and + as such, do not require the LaTeX document reference numbers to be hard + coded. If an author is required to submit actual LaTeX files, I do + recommend that the bibliography file (.bbl) be copied into the .tex + document and the \bibliographystyle{} and \bibliography{} commands be + commented out so that the .tex file does not depend on (potentially + lengthy and/or confidential) external bibliography database files + + 7) Adjusted some spacing parameters. The spacing above and below equations + has been revised (to a typical IEEE value). \jot now has a decent value. + The title text is now exactly 24pt. (On a related note, \fontsubfuzz has + been increased to 0.9pt to prevent annoying font substitution warnings + when using the Computer Modern fonts that use the 24.88pt size.) + In V1.6, \small is now 8.5pt in 9pt docs because \footnotesize is 8pt. + For 9pt docs, you should probably go ahead and use \footnotesize when + you need text a little smaller than \normalsize. + The interword spacing has been adjusted to be extremely close to that + which IEEE uses. You can use a new class option, nofonttune, if you need + to disable the adjusting of the interword spacing. This adjustment and + an increase to \hyphenpenalty have greatly reduced the amount of + hyphenation in a typical paper. + The baselineskip for the normalsize fonts has been tweaked to reduce + underfull vboxes on journal paper columns with only paragraphs. + Conference mode does the same thing but by also tweaking the \textheight + slightly off 9.25in (IEEE spec) to ensure an integer number of lines per + page. Draft (also draftcls) mode has also been revised to reduce + underfull vbox warnings. However, draft mode can still produce underfull + vboxes (a direct result of the increase in line spacing and margins) if: + A non-normalsize font occupies an entire column (abstract and index + terms take up a whole column by themselves); or the beginning of a + section occurs near the end of a column and cannot be squeezed into the + bottom, etc. This is normal as draft mode's liberal spacings cannot + guarantee perfect formatting. + + 8) New biographynophoto environment for biographies without photos. + Usage: + + \begin{biographynophoto}{author name} + biography text here + \end{biographynophoto} + + 9) Fixed bug that produced multiple table of contents entries for papers + with more than one biography. Also, biography now works better with + hyperref. + +10) New \sublargesize font size command provides for 11pt text in a 10pt + document. (Needed for things like author names.) For documents not + using 10pt normal size text, \sublargesize is currently identical + to \large. + +11) New \IEEEmembership command to provide correct font to indicate IEEE + membership for journal papers. + +12) Fixed author name line overflow problem when in journal mode. This + problem had been introduced in V1.5 in my rush to get \and to work for + conferences. \and is unneeded (and invalid) in journal mode. For + conference mode, \and will work as expected and features an optional + spacing argument. i.e., \and[\hspace{5ex}] + \and will default (recommended) to using \hfill which will result in + equal spacing between author blocks. + +13) New \authorblockN, \authorblockA and \authorrefmark commands to + facilitate easy formatting of author names, affiliations and cross + reference symbols, respectively, when in conference mode. These + three commands are to be used only for conference papers. + In conference mode, \author text is placed within a modified tabular + environment (somewhat like article.cls). So, within \author in + conference mode, you should not try to enclose multiple \\ within an + environment or command (other than the argument braces of + \authorblockX{}). For example: + + \author{\authorblockN{{John Doe \\ Jane Doe}}} % WRONG! + + will generate an error. + + Note that font size/attribute changes will now persists across \\ + within \author. (But, not across author blocks nor across \and.) + However, with the new commands, there should be no need to alter any + font attributes within \author. All text sizing and spacing within + \author{} and the author block commands is per IEEE specs for both + conference and journal modes. (In conference mode, the author names + are only very slightly larger than the affiliations which are in normal + size.) For specialized applications you can alter the justification of + author lines by placing \hfill at the beginning or at the end of a line. + The interline spacing within \author is determined by the font + attributes that are in effect at the end of each line within author. + +14) Because the titles and author name blocks use different font + sizes/styles from the main text, it was possible that two column papers + with titles that span both columns (standard journal and conference + papers, but not technotes) with certain numbers of lines for the title + and authors' name/affiliations can cause underfull vbox problems + (paragraphs with large spacings between them) in the second column of + the main text on the title page - if there were no new sections, + equations or figures in this column (they would provide some needed + rubber spacing). The use of things like special paper notices and + publisher ID marks also affected this issue. The problem could not + happen in the first column because the first column has a rubber length + around the heading of the first section. Furthermore, problems seldom + occurred on pages after the first as the margins had been chosen not to + cause it with the popular font sizes. Rubber lengths after the author + names would not fix this problem. + Auto-calculating a "good" spacing after the title is a tad difficult + to do in LaTeX. However, I am pleased to report that V1.6 has this new + capability - "dynamically determined title spacing". IEEEtran will now + measure the height of all the title and author text in \maketitle + and then calculate a rigid (non-rubber) spacer to follow that meets + IEEE specs and also produces a \textheight on the title page that + ensures an integer number of normalsized lines on the rest of the page. + Single column papers, and two column papers with the title entirely in + column one (technotes) do not need dynamic rigid spacing and therefore + use standard rubber spacers. + + Note: This problem can still crop up if you use floats that span both + columns (i.e., figure*). It has been a decade+ long limitation with + LaTeX that the stretchable portion of \dbltextfloatsep is ignored. + If you get a problem with underful vbox warnings and paragraphs that + "are pulled apart" on page with a float that spans both columns, tweak + the space between the figure and the main text a little: + + \vskip 5pt + \end{figure*} + + If you can't find a value that fixes both columns, you are going to + have to put a rubber spacer somewhere in one or both of the columns. +15) Because of change #14 above, those of you using \pubid will, as of V1.6, + have to place it *before* \maketitle in order for it have the intended + affect. The dynamic spacer algorithm must see if you are using \pubid + when \maketitle is called. \pubidadjcol works as before except that it + now has additional logic to prevent it from doing anything if \pubid + was never called. + +16) In some unusual, non-standard circumstances, an author may desire to + alter the spacing after the title area or put some unusual text above + the main text. For instance, to stop a bad break when a new section + occurs right at the start of the second page. This is difficult to do + when the title spans both columns of two column text since LaTeX treats + such title text as a type of float. A new command, + \IEEEaftertitletext{}, gives access to the end of that produced by + \maketitle. The types of things that can go into \IEEEaftertitletext + are the same as those into \twocolumn[] - no \par, but \\ are OK. There + is no restriction on the range of spacings that can be used. e.g., + \IEEEaftertitletext{\vspace{-100pt}} will push the main text well into + the title and \IEEEaftertitletext{\vspace{100pt}} will push it far down + the page. You will have complete control. If used, place + \IEEEaftertitletext{} before \maketitle like \title and \author. + IEEEtran's dynamic title spacing intentionally does not take into + consideration the contents of \IEEEaftertitletext{} when determining + the spacer after the title area (otherwise it would try to second + guess you), so the user will have manually adjust the height of the + contents in \IEEEaftertitletext{} if the problem discussed in #14 above + should develop. A safe bet is to keep the height of contents of + \IEEEaftertitletext{} to integer multiples of \baselineskip, e.g., + \IEEEaftertitletext{\vspace{-1\baselineskip}} + + Because it can result in an IEEE nonstandard format, the use of + \IEEEaftertitletext{} is discouraged. Possible uses include (1) the use + of IEEEtran for non-IEEE work with different title spacing requirements, + or (2) as an emergency manual override if a problem should develop in + IEEEtran's automatic spacing algorithm. + +17) completely rewritten \PARstart to: + a. no longer have problems when the user begins an environment + within the paragraph that uses \PARstart. + b. auto-detect and use the current font family + c. revise handling of the space at the end of the first word so that + interword glue will now work as normal. + d. produce correctly aligned edges for the (two) indented lines. + + Because the current font family is now auto-detected, there is no + longer any need for \CMPARstart - it is now the same as \PARstart. + +18) There is now a new "open box" Q.E.D. symbol (\QEDopen) as well as the + original default (\QED) closed one (\QEDclosed). Some journals use + the open form. To make \proof use the open form, just do: + \renewcommand{\QED}{\QEDopen} + +19) Additional \typeout{} notices added to warn the user when unusual + settings/commands are detected or as reminders to avoid common errors + when in conference mode. + +20) IEEEtran now provides \abovecaptionskip and \belowcaptionskip skip + registers because article class provides them and some packages + may error if they are missing. However, IEEEtran only uses + \abovecaptionskip for actual caption spacing. + +21) Fixed bug that prevented users from redefining the section headings + to use arabic digits. Thanks to Richardt H. Wilkinson for reporting + this bug. + +22) Code cleaned up to be more efficient with the use of TeX registers; + removed some old LaTeX 2.09 code; revised option processing to + LaTeX2e standard; eliminated unwanted "phantom" spaces in some + environments. + +23) Added new \IEEEeqnarray, \IEEEeqnarraybox, \IEEEeqnarrayboxm and + \IEEEeqnarrayboxt environments to provide superior alternatives to the + standard LaTeX \eqnarray, \array and \tabular. Additional new support + commands include \IEEEeqnarraydecl, \IEEEeqnarrayboxdecl, + \IEEEeqnarraymathstyle, \IEEEeqnarraytextstyle, \yesnumber. + \IEEEnonumber, \IEEEyesnumber, \IEEEyessubnumber, \IEEEeqnarraynumspace, + \IEEEeqnarraymulticol, \IEEEeqnarrayomit, \IEEEeqnarraydefcol, + \IEEEeqnarraydefcolsep, \IEEEeqnarrayseprow, \IEEEeqnarrayseprowcut, + \IEEEeqnarrayrulerow, \IEEEeqnarraydblrulerowcut, + \IEEEeqnarraystrutmode, \IEEEeqnarraystrutsize, + \IEEEeqnarraystrutsizeadd, \IEEEvisiblestrutstrue, + \IEEEvisiblestrutsfalse and \IEEEstrut. + These are documented in the user's guide. + +24) V1.6 changed back to using () around theorem names (which are also now + in italics) as this is what IEEE is using now. Thanks to Christian Peel + for reporting this. Also, when section numbers are used as the first + part of theorem numbers, display them in arabic, not Roman. + +25) New \IEEEtriggeratref{X} command allows a page break to be triggered + just before the given reference number "X". This is most useful when + balancing the columns on the last page and a \newpage between references + is desired. \IEEEtriggercmd{X} allows a different command to be executed + at trigger. + + + +******* + 7/2001 V1.5 (MDS) changes: + + + 1) Fixed \and within \author bug: (! Misplaced \crcr. \endtabular ->\crcr) + Thanks to Rainer Dorsch for discovering and reporting that \and + did not work. + + 2) Fixed the biography environment so that if a biography's text is shorter + than the area allocated for the photo, a collision with the next + biography does not occur. You can now put real graphics (using the + graphicx package) into the biography photo box with a new optional + argument of the biography command! For example: + + \begin{biography}[{\includegraphics[width=1in,height=1.25in,clip, + keepaspectratio]{./tux.eps}}]{Linux Penguin} + + will use the specified graphic as the author's photo. The photo area is + exactly 1in wide by 1.25in high - as is done in IEEE Transactions. Try + to keep the same 4:5 aspect ratio if scanning/cropping your photos. + Note the need for the extra set of enclosing braces around the + \includegraphics. Without it, The LaTeX parser may get confused when it + sees the \includegraphics's brackets within the biography's optional + argument. Due to the length of the \includegraphics command, you may + wish to define your own shorthand form of it. I have not done so with + IEEEtran to prevent dependence on the graphicx package. If you do not + use the optional argument, or leave it empty, a standard frame box + with the words "Place Photo Here" will be used. If you want the space + to remain completely empty, you can do: + + \begin{biography}[\mbox{}]{The Invisible Man} + + The interface to biography's optional argument is into a + 1in X 1.25in minipage in which the argument text is centered both + horizontally and vertically: + + \begin{minipage}[b][1.25in][c]{1in}% + \centering + #1% + \end{minipage} + + Within the biography environment, \unitlength is set to 1in. + With this in mind, you can even design your own custom frameboxes. + For instance: + + \begin{biography}[\framebox(1,1.25){\parbox[][\height + ][c]{0.9in}{\centering PLACE\\ PHOTO\\ + HERE}}]{Author Name} + + will yield the same type of result as the default photo box. + + Thanks to Herbert Voss for discovering the collision bug, suggesting + the ability to handle graphics and providing some prototype code. + + + +******* + 3/2001 V1.4 (MDS) changes: + + + 1) New "draftcls" and "final" options have been added. + Thanks to Dragan Cvetkovic for suggesting an option like draftcls. + + 2) Documentation changes to reflect the fact that this IEEEtran.cls + is no longer beta test. + + 3) Slightly revised caption sizes. Figure and table captions are now + in \footnotesize, not \small as before. + + 4) Allow user to control figure caption justification. IEEEtran.cls + normally defaults to left justified as is done in Transactions. + However, for conferences, you may wish to issue the command: + \centerfigcaptionstrue + in the preamble. Short (less than one line long) figure captions + will then be centered. Multi-line figure captions will always be + properly left justified. V1.6: This is already done for you when + using the conference mode. + + + +******* + 1/2001 V1.3 + Michael Shell (MDS) made extensive changes and additions: + + + BUGS FIXED (and many others too numerous to mention!): + 1) Fixed improper alignment with itemized, enumerated and + description lists. Added new controls to these three + environments so that it is easy to get the alignment IEEE + uses. Furthermore, the itemize, enumerate and description lists + no longer force a new paragraph to begin at the end the list + (\par). (Sometimes lists are used within paragraphs.) + + 2) JVH's fixes now allow things like $\mathbf{N}(0,P(0))$ + to work properly without needing the extra braces: + ${\mathbf{N}}(0,P(0))$. There is no longer any dependence + on the "rawfonts" and "oldlfont" packages. Thanks Juergen! + + 3) Fixed underfull hbox errors and incorrect reference number + alignment when the number of references in the bibliography + exceeded 9 entries (which is almost every paper!). + + 4) Removed dependence on the LaTeX sizexx.clo files. + Now, 9pt documents should work correctly even on systems that + lack a size9.clo file. This is most often used in conjunction + with the option "technote" for "correspondence" papers like those + in IEEE Transactions on Information Theory. For virtually all + other papers, 10pt is used and so it is the default. + Some improper font sizes have been corrected. \footnotesize is + now 8pt in 9pt docs, so footnotes in technotes should be the + correct size now. + + 5) Added \interlinepenalty within the bibliography section to discourage + LaTeX from breaking within a reference. IEEE almost never breaks within + a reference and when they do it is usually in technotes + (correspondence papers). You may get an underfull vbox warning in the + bibliography indicating that the spacing just before the "REFERENCES" + section is larger than normal, but the final result will be more like + what IEEE will publish. See the comments in the BIBLIOGRAPHY section + around line 2034 below if you want to change this behavior. + + 6) No longer "blows up" when you use \paragraph and have a table + of contents. + + 7) Theorem environment changed, (but for V1.6, back to the old way, sigh). + + 8) Figure captions adjusted: IEEE left (not center) justifies + figure captions (for journals) and does not indent figure caption text. + + 9) Adjusted some spacings in the table of contents(TOC))/list-of-figures/ + list-of-tables so that section/table numbers will not so easily + collide with the titles. Section VIII was usually the worst offender. + Still doesn't right justify the section numbers, but neither does + article.cls (This must be why LaTeX likes the x.y.z section numbering + scheme unlike I, II, III, etc. of IEEE. ) + It may be "normal" as it is (left justified). sigh. + +10) Now uses "index terms" now as a heading instead of "keywords". + Furthermore, the "index terms" and "abstract" headings are in bold + italic. This is how IEEE does things. + +11) \thebibliography and \biography now put entries into + the table of contents for you. + +******* + + + + + + + ******* + 9/2000 (JVH) changes: (now designated as V1.2) + + made some corrections to get closer to LaTeX2e + 20000906 Juergen v.Hagen + vonhagen at ihefiji.etec.uni-karlsruhe.de + + Permission to redistribute granted as of December 2000. + ******* + + + + + + ******* + + 1996 (JWD) LaTeX2e version: (now designated as V1.1) + + In the most recent TeXhax digest, there was a request for a copy of + IEEEtrans.sty modified to work with LaTeX2e. I have a version I + modified to make it IEEEtrans.cls, which I have sent to the person + making the request and am now sending to you to consider posting to + the archives. + -- + Jon Dixon + dixonj at colorado.edu + http://spot.colorado.edu/~dixonj/ + +******* + + + + + +******* + + 30-August-1993 original LaTeX 2.09 version (IEEEtran.sty), + (now designated as V1.0): + + by Gerry Murray and Silvano Balemi + Automatic Control Lab, ETH Zurich, Switzerland + balemi at aut.ee.ethz.ch + +******* + + + Added: text/escience11submission/escience2011.aux =================================================================== --- text/escience11submission/escience2011.aux (rev 0) +++ text/escience11submission/escience2011.aux 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,34 @@ +\relax +\@writefile{toc}{\contentsline {section}{\numberline {I}Introduction}{1}} +\@writefile{toc}{\contentsline {section}{\numberline {II}Protein Structure Prediction Algorithm}{2}} +\@writefile{toc}{\contentsline {section}{\numberline {III}Computational Challenges in Protein Structure Prediction}{2}} +\@writefile{lof}{\contentsline {figure}{\numberline {1}{\ignorespaces OOPS ItFix data flow diagram, showing algorithm applied to multiple proteins concurrently, in multiple rounds.}}{3}} +\newlabel{fig:oops}{{1}{3}} +\@writefile{toc}{\contentsline {section}{\numberline {IV}Parallel Prediction Scripting}{3}} +\@writefile{toc}{\contentsline {section}{\numberline {V}Experience on Large Systems}{5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {V-A}}Usage Rates}{5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {V-B}}Parameter Sweeps}{5}} +\@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces The outputs of an initial test run on Intrepid are shown here for four representative proteins. Note that the protein???s native secondary structure was used as input, so a direct comparison to DeBartolo et al. is only relevant for $\alpha $-proteins, where ItFix effectively converges to the native secondary structure.}}{5}} +\newlabel{fig:test-outputs}{{2}{5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {V-C}}Data Analysis and Visualization}{5}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {V-D}}OOPS Experiments Conducted in Swift}{5}} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Table presenting results of running > 5000 simulations on alpha proteins using TeraGrid resources. The structures generated are better than those of DeBartolo et al. [13], and required significantly less computation. The lower images are the predicted structures (with helices in red and coil in green) overlaid with the native structures (colored orange).}}{6}} +\newlabel{fig:alpha-sim-res}{{3}{6}} +\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb at x \hbox {V-D}0a}Initial Test}{6}} +\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb at x \hbox {V-D}0b}Investigation of $\alpha $ Proteins}{6}} +\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb at x \hbox {V-D}0c}Investigation of $\beta $ Proteins}{6}} +\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb at x \hbox {V-D}0d}Replicate/compare DeBartolo et al. runs}{6}} +\@writefile{lof}{\contentsline {figure}{\numberline {4}{\ignorespaces Results of running eight proteins on 2 racks (8192 CPUS) on Argonne???s BG/P, Intrepid. Below are results from this investigation for T1af7. On the left is a scatter plot showing the correlation between our statistical energy potential and accuracy of the protein structures for the 985 simulations that ran to completion. On the right is an image showing the lowest RMSD structure. This table, plot and image were all automatically generated by our scripting mechanism, and the table is presented by a simple CGI script at our web site [2].}}{6}} +\newlabel{fig:bgprun}{{4}{6}} +\@writefile{lof}{\contentsline {figure}{\numberline {5}{\ignorespaces Sample result of a timing run on Ranger for varying values of Temperature Update Interval with Starting Temperature of 100.}}{6}} +\newlabel{fig:rangerplot}{{5}{6}} +\@writefile{toc}{\contentsline {paragraph}{\numberline {\unhbox \voidb at x \hbox {V-D}0e}Automatic Timing Runs}{6}} +\@writefile{toc}{\contentsline {section}{\numberline {VI}Related Work}{6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {VI-A}}Structure Prediction Approach}{6}} +\@writefile{toc}{\contentsline {subsection}{\numberline {\unhbox \voidb at x \hbox {VI-B}}Computing Approach}{7}} +\@writefile{toc}{\contentsline {section}{\numberline {VII}Future Work}{7}} +\bibcite{IEEEhowto:kopka}{1} +\@writefile{lof}{\contentsline {figure}{\numberline {6}{\ignorespaces Planned OOPS Environment}}{8}} +\newlabel{fig:oops-planned}{{6}{8}} +\@writefile{toc}{\contentsline {section}{\numberline {VIII}Conclusion}{8}} +\@writefile{toc}{\contentsline {section}{References}{8}} Added: text/escience11submission/escience2011.bbl =================================================================== Added: text/escience11submission/escience2011.blg =================================================================== --- text/escience11submission/escience2011.blg (rev 0) +++ text/escience11submission/escience2011.blg 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,48 @@ +This is BibTeX, Version 0.99d (TeX Live 2010) +Capacity: max_strings=35307, hash_size=35307, hash_prime=30011 +The top-level auxiliary file: escience2011.aux +I found no \citation commands---while reading file escience2011.aux +I found no \bibdata command---while reading file escience2011.aux +I found no \bibstyle command---while reading file escience2011.aux +You've used 0 entries, + 0 wiz_defined-function locations, + 83 strings with 498 characters, +and the built_in function-call counts, 0 in all, are: += -- 0 +> -- 0 +< -- 0 ++ -- 0 +- -- 0 +* -- 0 +:= -- 0 +add.period$ -- 0 +call.type$ -- 0 +change.case$ -- 0 +chr.to.int$ -- 0 +cite$ -- 0 +duplicate$ -- 0 +empty$ -- 0 +format.name$ -- 0 +if$ -- 0 +int.to.chr$ -- 0 +int.to.str$ -- 0 +missing$ -- 0 +newline$ -- 0 +num.names$ -- 0 +pop$ -- 0 +preamble$ -- 0 +purify$ -- 0 +quote$ -- 0 +skip$ -- 0 +stack$ -- 0 +substring$ -- 0 +swap$ -- 0 +text.length$ -- 0 +text.prefix$ -- 0 +top$ -- 0 +type$ -- 0 +warning$ -- 0 +while$ -- 0 +width$ -- 0 +write$ -- 0 +(There were 3 error messages) Added: text/escience11submission/escience2011.log =================================================================== --- text/escience11submission/escience2011.log (rev 0) +++ text/escience11submission/escience2011.log 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,422 @@ +This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) (format=pdflatex 2010.7.21) 14 MAY 2011 22:30 +entering extended mode + restricted \write18 enabled. + %&-line parsing enabled. +**escience2011.tex +(./escience2011.tex +LaTeX2e <2009/09/24> +Babel and hyphenation patterns for english, dumylang, nohyphenation, ge +rman-x-2009-06-19, ngerman-x-2009-06-19, ancientgreek, ibycus, arabic, armenian +, basque, bulgarian, catalan, pinyin, coptic, croatian, czech, danish, dutch, u +kenglish, usenglishmax, esperanto, estonian, farsi, finnish, french, galician, +german, ngerman, swissgerman, monogreek, greek, hungarian, icelandic, assamese, + bengali, gujarati, hindi, kannada, malayalam, marathi, oriya, panjabi, tamil, +telugu, indonesian, interlingua, irish, italian, kurmanji, lao, latin, latvian, + lithuanian, mongolian, mongolianlmc, bokmal, nynorsk, polish, portuguese, roma +nian, russian, sanskrit, serbian, slovak, slovenian, spanish, swedish, turkish, + turkmen, ukrainian, uppersorbian, welsh, loaded. +(./IEEEtran.cls +Document Class: IEEEtran 2007/03/05 V1.7a by Michael Shell +-- See the "IEEEtran_HOWTO" manual for usage information. +-- http://www.michaelshell.org/tex/ieeetran/ +\@IEEEtrantmpdimenA=\dimen102 +\@IEEEtrantmpdimenB=\dimen103 +\@IEEEtrantmpcountA=\count79 +\@IEEEtrantmpcountB=\count80 +\@IEEEtrantmptoksA=\toks14 +LaTeX Font Info: Try loading font information for OT1+ptm on input line 366. + +(/usr/local/texlive/2010/texmf-dist/tex/latex/psnfss/ot1ptm.fd +File: ot1ptm.fd 2001/06/04 font definitions for OT1/ptm. +) +-- Using 8.5in x 11in (letter) paper. +-- Using PDF output. +\@IEEEnormalsizeunitybaselineskip=\dimen104 +-- This is a 10 point document. +\CLASSINFOnormalsizebaselineskip=\dimen105 +\CLASSINFOnormalsizeunitybaselineskip=\dimen106 +\IEEEnormaljot=\dimen107 +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <5> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <5> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <7> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <7> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <8> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <8> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <9> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <9> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <10> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <10> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <11> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <11> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <12> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <12> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <17> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <17> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <20> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <20> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/n' in size <24> not available +(Font) Font shape `OT1/ptm/b/n' tried instead on input line 724. +LaTeX Font Info: Font shape `OT1/ptm/bx/it' in size <24> not available +(Font) Font shape `OT1/ptm/b/it' tried instead on input line 724. +\IEEEilabelindentA=\dimen108 +\IEEEilabelindentB=\dimen109 +\IEEEilabelindent=\dimen110 +\IEEEelabelindent=\dimen111 +\IEEEdlabelindent=\dimen112 +\IEEElabelindent=\dimen113 +\IEEEiednormlabelsep=\dimen114 +\IEEEiedmathlabelsep=\dimen115 +\IEEEiedtopsep=\skip41 +\c at section=\count81 +\c at subsection=\count82 +\c at subsubsection=\count83 +\c at paragraph=\count84 +\c at IEEEsubequation=\count85 +\abovecaptionskip=\skip42 +\belowcaptionskip=\skip43 +\c at figure=\count86 +\c at table=\count87 +\@IEEEeqnnumcols=\count88 +\@IEEEeqncolcnt=\count89 +\@IEEEtmpitemindent=\dimen116 +\c at IEEEbiography=\count90 +\@IEEEtranrubishbin=\box26 +) (/usr/local/texlive/2010/texmf-dist/tex/latex/algorithms/algorithmic.sty +Package: algorithmic 2009/08/24 v0.1 Document Style `algorithmic' + +(/usr/local/texlive/2010/texmf-dist/tex/latex/base/ifthen.sty +Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC) +) +(/usr/local/texlive/2010/texmf-dist/tex/latex/graphics/keyval.sty +Package: keyval 1999/03/16 v1.13 key=value parser (DPC) +\KV at toks@=\toks15 +) +\c at ALC@unique=\count91 +\c at ALC@line=\count92 +\c at ALC@rem=\count93 +\c at ALC@depth=\count94 +\ALC at tlm=\skip44 +\algorithmicindent=\skip45 +) +(./escience2011.aux) +\openout1 = `escience2011.aux'. + +LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 343. +LaTeX Font Info: ... okay on input line 343. +LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 343. +LaTeX Font Info: ... okay on input line 343. +LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 343. +LaTeX Font Info: ... okay on input line 343. +LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 343. +LaTeX Font Info: ... okay on input line 343. +LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 343. +LaTeX Font Info: ... okay on input line 343. +LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 343. +LaTeX Font Info: ... okay on input line 343. +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! + [1{/usr/local/texlive/2010/texmf-var/fonts/map/pdftex/updmap/pdftex.map} + + +] +LaTeX Font Info: Try loading font information for OT1+pcr on input line 524. + + (/usr/local/texlive/2010/texmf-dist/tex/latex/psnfss/ot1pcr.fd +File: ot1pcr.fd 2001/06/04 font definitions for OT1/pcr. +) +Overfull \hbox (42.0pt too wide) in paragraph at lines 550--550 +[]\OT1/pcr/m/n/10 ItFix(protein, nRounds=10, roundSize=300, secStr)[] + [] + + +Overfull \hbox (24.0pt too wide) in paragraph at lines 550--550 +[] \OT1/pcr/m/n/10 while not converged and roundNum < nRounds[] + [] + + +Overfull \hbox (6.0pt too wide) in paragraph at lines 550--550 +[] \OT1/pcr/m/n/10 models[j], structs[j] = Mcsa(p, secStr)[] + [] + + +Overfull \hbox (30.0pt too wide) in paragraph at lines 550--550 +[]\OT1/pcr/m/n/10 converged = checkConvergence(newSecStr, secStr)[] + [] + + +Overfull \hbox (12.0pt too wide) in paragraph at lines 550--550 +[] \OT1/pcr/m/n/10 initialConf=genRandConf(protein, secStr)[] + [] + + +Overfull \hbox (66.0pt too wide) in paragraph at lines 550--550 +[] \OT1/pcr/m/n/10 temp, stepsToUpdate, moveSet = GetInitialValues()[] + [] + +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <7> on input line 552. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <5> on input line 552. +[2] +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! + +Overfull \hbox (24.0pt too wide) in paragraph at lines 597--597 +[] \OT1/pcr/m/n/10 app (PDT structure) predict(Fasta protein) {[] + [] + + +Overfull \hbox (24.0pt too wide) in paragraph at lines 597--597 +[] \OT1/pcr/m/n/10 predict_structure @protein @structure;[] + [] + + +Overfull \hbox (6.0pt too wide) in paragraph at lines 597--597 +[] \OT1/pcr/m/n/10 structure[i] = predict(protein);[] + [] + +[3] +Overfull \hbox (36.0pt too wide) in paragraph at lines 640--640 +[]\OT1/pcr/m/n/10 app (MCSAOut out) mcsa (MCSAIn i, SecSeq secseq,[] + [] + + +Overfull \hbox (42.0pt too wide) in paragraph at lines 640--640 +[] \OT1/pcr/m/n/10 int jobnum, string cfgParams[])[] + [] + + +Overfull \hbox (6.0pt too wide) in paragraph at lines 640--640 +[] \OT1/pcr/m/n/10 oops_mcsa @i.fasta @secseq @i.pdb @out.pdt[] + [] + + +Overfull \hbox (12.0pt too wide) in paragraph at lines 640--640 +[] \OT1/pcr/m/n/10 @out.rmsd jobnum cfgParams stdout=@out.log;[] + [] + + +Overfull \hbox (48.0pt too wide) in paragraph at lines 653--653 +[]\OT1/pcr/m/n/10 app (file oParams) setTemps (file inParams, string[] + [] + + +Overfull \hbox (48.0pt too wide) in paragraph at lines 653--653 +[] \OT1/pcr/m/n/10 start, string update)[] + [] + + +Overfull \hbox (36.0pt too wide) in paragraph at lines 653--653 +[] \OT1/pcr/m/n/10 sed "-e" @strcat("s/@DIT@/",start,"/") "-e"[] + [] + + +Overfull \hbox (12.0pt too wide) in paragraph at lines 653--653 +[] \OT1/pcr/m/n/10 @inParams stdout=@oParams;[] + [] + + +Overfull \hbox (24.0pt too wide) in paragraph at lines 673--673 +[]\OT1/pcr/m/n/10 (string protein, MCSAIn mcsaIn, SecSeq secSeq,[] + [] + + +Overfull \hbox (18.0pt too wide) in paragraph at lines 673--673 +[] \OT1/pcr/m/n/10 string config [] = readData(editedParams);[] + [] + +Missing character: There is no ? in font pcrr7t! +Missing character: There is no ? in font pcrr7t! + +Overfull \hbox (24.0pt too wide) in paragraph at lines 707--707 +[]\OT1/pcr/m/n/10 ItFix(string protein, int nsim, int maxrounds,[] + [] + + +Overfull \hbox (18.0pt too wide) in paragraph at lines 707--707 +[] \OT1/pcr/m/n/10 d=outdir, p=protein, r=maxrounds,[] + [] + + +Overfull \hbox (6.0pt too wide) in paragraph at lines 707--707 +[] \OT1/pcr/m/n/10 SecSeq secseq[] on input line 770. +LaTeX Font Info: External font `cmex10' loaded for size +(Font) <6> on input line 770. +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +[5] +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! + [6] +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! +Missing character: There is no ? in font ptmr7t! + [7] + +** Conference Paper ** +Before submitting the final camera ready copy, remember to: + + 1. Manually equalize the lengths of two columns on the last page + of your paper; + + 2. Ensure that any PostScript and/or PDF output post-processing + uses only Type 1 fonts and that every step in the generation + process uses the appropriate paper size. + +[8] (./escience2011.aux) ) +Here is how much of TeX's memory you used: + 1135 strings out of 493747 + 18778 string characters out of 3143546 + 81643 words of memory out of 3000000 + 4473 multiletter control sequences out of 15000+200000 + 38165 words of font info for 73 fonts, out of 3000000 for 9000 + 717 hyphenation exceptions out of 8191 + 26i,8n,20p,3917b,291s stack positions out of 5000i,500n,10000p,200000b,50000s +{/usr/local/texlive/2010/texmf-dist/fonts/enc/dvips/b +ase/8r.enc} +Output written on escience2011.pdf (8 pages, 145878 bytes). +PDF statistics: + 72 PDF objects out of 1000 (max. 8388607) + 51 compressed objects within 1 object stream + 0 named destinations out of 1000 (max. 500000) + 1 words of extra memory for PDF output out of 10000 (max. 10000000) + Added: text/escience11submission/escience2011.pdf =================================================================== (Binary files differ) Property changes on: text/escience11submission/escience2011.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: text/escience11submission/escience2011.tex =================================================================== --- text/escience11submission/escience2011.tex (rev 0) +++ text/escience11submission/escience2011.tex 2011-05-15 03:34:27 UTC (rev 4474) @@ -0,0 +1,880 @@ +%% bare_conf.tex +%% V1.3 +%% 2007/01/11 +%% by Michael Shell +%% See: +%% http://www.michaelshell.org/ +%% for current contact information. +%% +%% This is a skeleton file demonstrating the use of IEEEtran.cls +%% (requires IEEEtran.cls version 1.7 or later) with an IEEE conference paper. +%% +%% Support sites: +%% http://www.michaelshell.org/tex/ieeetran/ +%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/ +%% and +%% http://www.ieee.org/ + +%%************************************************************************* +%% Legal Notice: +%% This code is offered as-is without any warranty either expressed or +%% implied; without even the implied warranty of MERCHANTABILITY or +%% FITNESS FOR A PARTICULAR PURPOSE! +%% User assumes all risk. +%% In no event shall IEEE or any contributor to this code be liable for +%% any damages or losses, including, but not limited to, incidental, +%% consequential, or any other damages, resulting from the use or misuse +%% of any information contained here. +%% +%% All comments are the opinions of their respective authors and are not +%% necessarily endorsed by the IEEE. +%% +%% This work is distributed under the LaTeX Project Public License (LPPL) +%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used, +%% distributed and modified. A copy of the LPPL, version 1.3, is included +%% in the base LaTeX documentation of all distributions of LaTeX released +%% 2003/12/01 or later. +%% Retain all contribution notices and credits. +%% ** Modified files should be clearly indicated as such, including ** +%% ** renaming them and changing author support contact information. ** +%% +%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex, +%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex +%%************************************************************************* + +% *** Authors should verify (and, if needed, correct) their LaTeX system *** +% *** with the testflow diagnostic prior to trusting their LaTeX platform *** +% *** with production work. IEEE's font choices can trigger bugs that do *** +% *** not appear when using other class files. *** +% The testflow support page is at: +% http://www.michaelshell.org/tex/testflow/ + + + +% Note that the a4paper option is mainly intended so that authors in +% countries using A4 can easily print to A4 and see how their papers will +% look in print - the typesetting of the document will not typically be +% affected with changes in paper size (but the bottom and side margins will). +% Use the testflow package mentioned above to verify correct handling of +% both paper sizes by the user's LaTeX system. +% +% Also note that the "draftcls" or "draftclsnofoot", not "draft", option +% should be used if it is desired that the figures are to be displayed in +% draft mode. +% +\documentclass[conference]{IEEEtran} +% Add the compsoc option for Computer Society conferences. +% +% If IEEEtran.cls has not been installed into the LaTeX system files, +% manually specify the path to it like: +% \documentclass[conference]{../sty/IEEEtran} + + + + + +% Some very useful LaTeX packages include: +% (uncomment the ones you want to load) + + +% *** MISC UTILITY PACKAGES *** +% +%\usepackage{ifpdf} +% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional +% compilation based on whether the output is pdf or dvi. +% usage: +% \ifpdf +% % pdf code +% \else +% % dvi code +% \fi +% The latest version of ifpdf.sty can be obtained from: +% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/ +% Also, note that IEEEtran.cls V1.7 and later provides a builtin +% \ifCLASSINFOpdf conditional that works the same way. +% When switching from latex to pdflatex and vice-versa, the compiler may +% have to be run twice to clear warning/error messages. + + + + + + +% *** CITATION PACKAGES *** +% +%\usepackage{cite} +% cite.sty was written by Donald Arseneau +% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package +% \cite{} output to follow that of IEEE. Loading the cite package will +% result in citation numbers being automatically sorted and properly +% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using +% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's +% \cite will automatically add leading space, if needed. Use cite.sty's +% noadjust option (cite.sty V3.8 and later) if you want to turn this off. +% cite.sty is already installed on most LaTeX systems. Be sure and use +% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does +% not currently provide for hyperlinked citations. +% The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/ +% The documentation is contained in the cite.sty file itself. + + + + + + +% *** GRAPHICS RELATED PACKAGES *** +% +\ifCLASSINFOpdf + % \usepackage[pdftex]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../pdf/}{../jpeg/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.pdf,.jpeg,.png} +\else + % or other class option (dvipsone, dvipdf, if not using dvips). graphicx + % will default to the driver specified in the system graphics.cfg if no + % driver is specified. + % \usepackage[dvips]{graphicx} + % declare the path(s) where your graphic files are + % \graphicspath{{../eps/}} + % and their extensions so you won't have to specify these with + % every instance of \includegraphics + % \DeclareGraphicsExtensions{.eps} +\fi +% graphicx was written by David Carlisle and Sebastian Rahtz. It is +% required if you want graphics, photos, etc. graphicx.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/graphics/ +% Another good source of documentation is "Using Imported Graphics in +% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or +% epslatex.pdf at: http://www.ctan.org/tex-archive/info/ +% +% latex, and pdflatex in dvi mode, support graphics in encapsulated +% postscript (.eps) format. pdflatex in pdf mode supports graphics +% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure +% that all non-photo figures use a vector format (.eps, .pdf, .mps) and +% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats +% which can result in "jaggedy"/blurry rendering of lines and letters as +% well as large increases in file sizes. +% +% You can find documentation about the pdfTeX application at: +% http://www.tug.org/applications/pdftex + + + + + +% *** MATH PACKAGES *** +% +%\usepackage[cmex10]{amsmath} +% A popular package from the American Mathematical Society that provides +% many useful and powerful commands for dealing with mathematics. If using +% it, be sure to load this package with the cmex10 option to ensure that +% only type 1 fonts will utilized at all point sizes. Without this option, +% it is possible that some math symbols, particularly those within +% footnotes, will be rendered in bitmap form which will result in a +% document that can not be IEEE Xplore compliant! +% +% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000 +% thus preventing page breaks from occurring within multiline equations. Use: +%\interdisplaylinepenalty=2500 +% after loading amsmath to restore such page breaks as IEEEtran.cls normally +% does. amsmath.sty is already installed on most LaTeX systems. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/ + + + + + +% *** SPECIALIZED LIST PACKAGES *** +% +\usepackage{algorithmic} +% algorithmic.sty was written by Peter Williams and Rogerio Brito. +% This package provides an algorithmic environment for describing algorithms. +% You can use the algorithmic environment in-text or within a figure +% environment to provide for a floating algorithm. Do NOT use the algorithm +% floating environment provided by algorithm.sty (by the same authors) or +% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated +% algorithm float types and packages that provide these will not provide +% correct IEEE style captions. The latest version and documentation of +% algorithmic.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/ +% There is also a support site at: +% http://algorithms.berlios.de/index.html +% Also of interest may be the (relatively newer and more customizable) +% algorithmicx.sty package by Szasz Janos: +% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/ + + +% *** ALIGNMENT PACKAGES *** +% +%\usepackage{array} +% Frank Mittelbach's and David Carlisle's array.sty patches and improves +% the standard LaTeX2e array and tabular environments to provide better +% appearance and additional user controls. As the default LaTeX2e table +% generation code is lacking to the point of almost being broken with +% respect to the quality of the end results, all users are strongly +% advised to use an enhanced (at the very least that provided by array.sty) +% set of table tools. array.sty is already installed on most systems. The +% latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/required/tools/ + +%\usepackage{mdwmath} +%\usepackage{mdwtab} +% Also highly recommended is Mark Wooding's extremely powerful MDW tools, +% especially mdwmath.sty and mdwtab.sty which are used to format equations +% and tables, respectively. The MDWtools set is already installed on most +% LaTeX systems. The lastest version and documentation is available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/ + +% IEEEtran contains the IEEEeqnarray family of commands that can be used to +% generate multiline equations as well as matrices, tables, etc., of high +% quality. + +%\usepackage{eqparbox} +% Also of notable interest is Scott Pakin's eqparbox package for creating +% (automatically sized) equal width boxes - aka "natural width parboxes". +% Available at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/ + + + +% *** SUBFIGURE PACKAGES *** +%\usepackage[tight,footnotesize]{subfigure} +% subfigure.sty was written by Steven Douglas Cochran. This package makes it +% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE +% work, it is a good idea to load it with the tight package option to reduce +% the amount of white space around the subfigures. subfigure.sty is already +% installed on most LaTeX systems. The latest version and documentation can +% be obtained at: +% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/ +% subfigure.sty has been superceeded by subfig.sty. + + + +%\usepackage[caption=false]{caption} +%\usepackage[font=footnotesize]{subfig} +% subfig.sty, also written by Steven Douglas Cochran, is the modern +% replacement for subfigure.sty. However, subfig.sty requires and +% automatically loads Axel Sommerfeldt's caption.sty which will override +% IEEEtran.cls handling of captions and this will result in nonIEEE style +% figure/table captions. To prevent this problem, be sure and preload +% caption.sty with its "caption=false" package option. This is will preserve +% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later +% (recommended due to many improvements over 1.2) of subfig.sty supports +% the caption=false option directly: +%\usepackage[caption=false,font=footnotesize]{subfig} +% +% The latest version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/ +% The latest version and documentation of caption.sty can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/ + + + + +% *** FLOAT PACKAGES *** +% +%\usepackage{fixltx2e} +% fixltx2e, the successor to the earlier fix2col.sty, was written by +% Frank Mittelbach and David Carlisle. This package corrects a few problems +% in the LaTeX2e kernel, the most notable of which is that in current +% LaTeX2e releases, the ordering of single and double column floats is not +% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a +% single column figure to be placed prior to an earlier double column +% figure. The latest version and documentation can be found at: +% http://www.ctan.org/tex-archive/macros/latex/base/ + + + +%\usepackage{stfloats} +% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e +% the ability to do double column floats at the bottom of the page as well +% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in +% LaTeX2e). It also provides a command: +%\fnbelowfloat +% to enable the placement of footnotes below bottom floats (the standard +% LaTeX2e kernel puts them above bottom floats). This is an invasive package +% which rewrites many portions of the LaTeX2e float routines. It may not work +% with other packages that modify the LaTeX2e float routines. The latest +% version and documentation can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/ +% Documentation is contained in the stfloats.sty comments as well as in the +% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE +% does not allow \baselineskip to stretch. Authors submitting work to the +% IEEE should note that IEEE rarely uses double column equations and +% that authors should try to avoid such use. Do not be tempted to use the +% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does +% not format its papers in such ways. + + + + + +% *** PDF, URL AND HYPERLINK PACKAGES *** +% +%\usepackage{url} +% url.sty was written by Donald Arseneau. It provides better support for +% handling and breaking URLs. url.sty is already installed on most LaTeX +% systems. The latest version can be obtained at: +% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/ +% Read the url.sty source comments for usage information. Basically, +% \url{my_url_here}. + + + + + +% *** Do not adjust lengths that control margins, column widths, etc. *** +% *** Do not use packages that alter fonts (such as pslatex). *** +% There should be no need to do such things with IEEEtran.cls V1.6 and later. +% (Unless specifically asked to do so by the journal or conference you plan +% to submit to, of course. ) + + +% correct bad hyphenation here +\hyphenation{op-tical net-works semi-conduc-tor} + + +\begin{document} +% +% paper title +% can use linebreaks \\ within to get better formatting as desired +\title{Towards Petascale ab initio Protein Folding through Parallel Scripting} + + +% author names and affiliations +% use a multiple column layout for up to three different +% affiliations +\author{\IEEEauthorblockN{Auth1} +\IEEEauthorblockA{An Institute\\ +A University\\ +An address\\ +Email:email at domain} +\and +\IEEEauthorblockN{Auth2} +\IEEEauthorblockA{An Institute\\ +A University\\ +An address\\ +Email:email at domain} +\and +\IEEEauthorblockN{Auth3} +\IEEEauthorblockA{An Institute\\ +A University\\ +An address\\ +Email:email at domain}} + +% conference papers do not typically use \thanks and this command +% is locked out in conference mode. If really needed, such as for +% the acknowledgment of grants, issue a \IEEEoverridecommandlockouts +% after \documentclass + +% for over three affiliations, or if they all won't fit within the width +% of the page, use this alternative format: +% +%\author{\IEEEauthorblockN{Michael Shell\IEEEauthorrefmark{1}, +%Homer Simpson\IEEEauthorrefmark{2}, +%James Kirk\IEEEauthorrefmark{3}, +%Montgomery Scott\IEEEauthorrefmark{3} and +%Eldon Tyrell\IEEEauthorrefmark{4}} +%\IEEEauthorblockA{\IEEEauthorrefmark{1}School of Electrical and Computer Engineering\\ +%Georgia Institute of Technology, +%Atlanta, Georgia 30332--0250\\ Email: see http://www.michaelshell.org/contact.html} +%\IEEEauthorblockA{\IEEEauthorrefmark{2}Twentieth Century Fox, Springfield, USA\\ +%Email: homer at thesimpsons.com} +%\IEEEauthorblockA{\IEEEauthorrefmark{3}Starfleet Academy, San Francisco, California 96678-2391\\ +%Telephone: (800) 555--1212, Fax: (888) 555--1212} +%\IEEEauthorblockA{\IEEEauthorrefmark{4}Tyrell Inc., 123 Replicant Street, Los Angeles, California 90210--4321}} + + + + +% use for special paper notices +%\IEEEspecialpapernotice{(Invited Paper)} + + + + +% make the title area +\maketitle + + +\begin{abstract} +%\boldmath +Petascale computers allow scientists and engineers not only to address old problems better, but also to consider new methods and new problems. We report here on work that both applies new methods and tackles new problems in the area of structural biology. The project combines an efficient protein structure prediction algorithm implemented in the Open Protein System (OOPS) system with the Swift parallel scripting system to enable the rapid and flexible composition of OOPS components into parallel program, and the high-performance execution of these programs on petascale computers. The result is a powerful computational laboratory environment for predicting protein secondary and tertiary structure, for further testing and refining OOPS, and for performing training and scaling tests that enable structure simulation to run on a wide variety of computing architectures with high efficiency. Comparison of before and after experiences within two laboratories at the University of Chi cago shows that this use of scripting enables achieving significant improvements in throughput, time-to-solution, and scientific productivity. For example, an undergraduate has recently been able to define and execute new protein folding simulations on thousands of processors. This approach both enables new applications for petascale computers, and provides an avenue for many more researchers to participate in the computational science aspects of structure prediction. +\end{abstract} +% IEEEtran.cls defaults to using nonbold math in the Abstract. +% This preserves the distinction between vectors and scalars. However, +% if the conference you are submitting to favors bold math in the abstract, +% then you can use LaTeX's standard command \boldmath at the very start +% of the abstract to achieve this. Many IEEE journals/conferences frown on +% math in the abstract anyway. + +% no keywords + + + + +% For peer review papers, you can put extra information on the cover +% page as needed: +% \ifCLASSOPTIONpeerreview +% \begin{center} \bfseries EDICS Category: 3-BBND \end{center} +% \fi +% +% For peerreview papers, this IEEEtran command inserts a page break and +% creates the second title. It will be ignored for other modes. +\IEEEpeerreviewmaketitle + + + +\section{Introduction} +To understand a living cell at the microscopic level, we must identify, characterize, and comprehend detailed interactions among sub-components. Decoding the genome has already transformed biology and medicine but is only the starting point of our research and methods, whose long-term goal is to begin with a set of genes identified in a biological process, provide the structure and function of the proteins, and identify their interactions and connections in signaling pathways. Success in this endeavor will lay the foundation for a new generation of therapeutics and drug design. This research agenda drives our interest in reliable, high-throughput methods for predicting protein structure from sequence and recognize docking partners. The availability of such methods will create a comprehensive resource for understanding these interactions and will eventually replace slower, empirical determinations. To this end, we have developed and continue to use, support, and enhance the O pen Protein Simulator (OOPS), a suite of C++ programs and libraries for predicting the structure and interaction of proteins and other large molecules [10]. OOPS has proven successful, through international challenges, such as CASP8, in predicting the structure of moderate size proteins [14]. As OOPS becomes more accurate and efficient, a number of related computational challenges emerge in our desire to tackle proteins of increasing size because current prediction methods have limited accuracy even for proteins on the order of 100 residues when homology-based information is minimal. To predict the structures of larger and multi-domain proteins, statistical sampling becomes a limiting factor, and thus we require significantly more computing resources. Second, we wish to generate more predictions, of higher, and known, quality, faster, and with less effort required of the users to enable greater focus on the primary intellectual challenges and less on the distracting but nece ssary efforts involved in performing increasingly parallel, large scale computations. This goal requires both more computing capacity and the ability to specify and execute new OOPS applications rapidly and easily. Third, progress towards the first two challenges requires the ability to use a wider range of more powerful computers and to reduce barriers to using new computing systems. In pursuit of these goals, we have sought to create a ???``protein prediction laboratory" enabling the rapid specification of complex protein prediction applications based on OOPS software. To this end, the cumbersome, inflexible, and manually intensive collection of ad hoc shell and Python scripts that had previously been used to drive OOPS have been replaced by the Swift [1] parallel scripting system. Swift provides a high-level syntax that provides for well-structured, abstract, location-independent scripts. The Swift runtime system also automates parallelization, data management, and error recovery, and supports execution on a wide variety of computer systems. This approach allows great flexibility in composing existing programs to address new requirements, to explore algorithmic variations, and to implement entirely new applications, such as new folding and docking algorithms, and replica exchange simulations with multiple order parameters. The present status report on our progress towards these goals describes the algorithms used by OOPS (Section 2), their computational structure and costs (Section 3), and the parallel scripting approach we employed to extend the power of OOPS (Section 4). Finally, we present in Section 5 results obtained by co-author G. Hocky, an undergraduate student at the University of Chicago, who sought to apply the OOPS Swift-based scripting framework to a range of protein structure prediction problems. These results are anecdotal, but suggestive of the power of the approach. + +%\subsection{Subsection Heading Here} +%Subsection text here. + + +%\subsubsection{Subsubsection Heading Here} +%Subsubsection text here. + + +% An example of a floating figure using the graphicx package. +% Note that \label must occur AFTER (or within) \caption. +% For figures, \caption should occur after the \includegraphics. +% Note that IEEEtran v1.7 and later has special internal code that +% is designed to preserve the operation of \label within \caption +% even when the captionsoff option is in effect. However, because +% of issues like this, it may be the safest practice to put all your +% \label just after \caption rather than within \caption{}. +% +% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class +% option should be used if it is desired that the figures are to be +% displayed while in draft mode. +% +%\begin{figure}[!t] +%\centering +%\includegraphics[width=2.5in]{myfigure} +% where an .eps filename suffix will be assumed under latex, +% and a .pdf suffix will be assumed for pdflatex; or what has been declared +% via \DeclareGraphicsExtensions. +%\caption{Simulation Results} +%\label{fig_sim} +%\end{figure} + +% Note that IEEE typically puts floats only at the top, even when this +% results in a large percentage of a column being occupied by floats. + + +% An example of a double column floating figure using two subfigures. +% (The subfig.sty package must be loaded for this to work.) +% The subfigure \label commands are set within each subfloat command, the +% \label for the overall figure must come after \caption. +% \hfil must be used as a separator to get equal spacing. +% The subfigure.sty package works much the same way, except \subfigure is +% used instead of \subfloat. +% +%\begin{figure*}[!t] +%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}% +%\label{fig_first_case}} +%\hfil +%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}% +%\label{fig_second_case}}} +%\caption{Simulation results} +%\label{fig_sim} +%\end{figure*} +% +% Note that often IEEE papers with subfigures do not employ subfigure +% captions (using the optional argument to \subfloat), but instead will +% reference/describe all of them (a), (b), etc., within the main caption. + + +% An example of a floating table. Note that, for IEEE style tables, the +% \caption command should come BEFORE the table. Table text will default to +% \footnotesize as IEEE normally uses this smaller font for tables. +% The \label must come after \caption as always. +% +%\begin{table}[!t] +%% increase table row spacing, adjust to taste +%\renewcommand{\arraystretch}{1.3} +% if using array.sty, it might be a good idea to tweak the value of +% \extrarowheight as needed to properly center the text within the cells +%\caption{An Example of a Table} +%\label{table_example} +%\centering +%% Some packages, such as MDW tools, offer better commands for making tables +%% than the plain LaTeX2e tabular which is used here. +%\begin{tabular}{|c||c|} +%\hline +%One & Two\\ +%\hline +%Three & Four\\ +%\hline +%\end{tabular} +%\end{table} + +\section{Protein Structure Prediction Algorithm} +The Open Protein Simulator (OOPS) is a set of open source applications for fast simulation of protein folding, docking and refinement. It uses the C++ protein library PL [3] for representing, moving, and calculating the energy of protein structures, and provides a set of useful analysis tools for evaluating the quality of predicted models. OOPS and its component ItFix algorithm have proven successful at predicting the structure of moderate-sized proteins [13]. +The iterative fixing (ItFix) protein structure determination algorithm used within OOPS takes as input a protein sequence, an initial secondary structure, a starting annealing temperature, and other parameters. If successful, it produces a protein structure as output. +Figure 1 shows the basic structure of the ItFix algorithm, which consists of multiple rounds. (The number of rounds is typically limited by a maximum and a convergence test.) At each round, it performs between 100 and 1000 independent, randomly seeded Monte-Carlo-based simulated annealing (MCSA) computations [10]. Then, it gathers statistical data about that round, specifically on the average origins or assignments of the secondary structures at each position in the sequence. Sometimes this analysis involves clustering of structures through various techniques. It then determines whether or not to stop sampling angles from certain secondary structure types at those positions, checks for convergence and, if convergence has not occurred, launches the next round with this information as a new input file. Additionally, at each analysis step, various plots are created from the output data, including average 3D atomic contact maps (and movies), RMSD (3D position accuracy) versus en ergy plots, and secondary structure prediction accuracy. +%\begin{algorithmic} +\begin{verbatim} + main(protein, secStr) +ItFix(protein, nRounds=10, roundSize=300, secStr) + +ItFix(protein, nRounds, roundSize, secStr) + roundNum=1 + while not converged and roundNum < nRounds + foreach j in 1..roundSize + models[j], structs[j] = Mcsa(p, secStr) + newSS = analyze(models, structs) +converged = checkConvergence(newSecStr, secStr) + s=newSecStr + roundNum++ + + MCSA(protein, secStr) + initialConf=genRandConf(protein, secStr) + E = energy(initialConf.model) + temp, stepsToUpdate, moveSet = GetInitialValues() + while (not converged) + position=chooseRandPosition() + model = move( position, moveSet ) + newE = energy(model) + model, E = accept_or_reject(E, newE,t) +if nstep mod steps == 0 then reduce(t) + nsteps++ + return model, struct +\end{verbatim} + +The MCSA application called by ItFix consists of a simulated annealing (SA) loop that iterates until it ``cools" sufficiently [10]. At each iteration, it rotates the $\varphi$/$\Psi$ backbone torsional angles in accordance with well-understood physical constraints, seeking moves that produce lower energy and more native-like structures. Thus, each iteration comprises first a move() and then the calculation of the energy of the new configuration, followed by acceptance or rejection of the move based on energy and a temperature-weighted probablity of accepting a higher-energy move. +ItFix and OOPS have unique characteristics that make them well-suited for high-throughput and rapid-response structure prediction and related operations such as simulating the docking configurations of large biomolecules. ItFix incorporates basic chemical principles and mimics a folding pathway to restrict its search space. It employs a highly conditional reduced molecular representation [16], which enables a broader and faster search [10]. In contrast, most other methods include all the atoms and consequently expend much computation time searching through side chain space. Most other algorithms also rely heavily on known structures or fragments (homologies, templates, etc.) [8, 31]. Their success rapidly diminishes as the amount of known information decreases. + +\section{Computational Challenges in Protein Structure Prediction} +The ItFix folding algorithm has reduced significantly the time required to predict a protein from sequence, relative to other methods of similar quality. However, in its current implementation, the algorithm still requires ~1000 CPU hours on a modern microprocessor for a medium-sized protein: more than a month. +Fortunately, the hierarchical structure in Figure 1 suggests obvious opportunities for parallel execution. First, the multiple independent invocations of MCSA can be executed in parallel; as each MCSA invocation runs for 0.5 to 3.0 hours, has a small memory footprint (10s of megabytes), and outputs small text files (compressible to < 1MB per MCSA simulation), this strategy is quite straightforward. Second, it may be possible to exploit parallelism within MCSA. Exploiting for now only the former opportunity, we have produced a code that can compute a single structure in a day on a 150-CPU cluster. + +While we plan to consider parallelization of MCSA in the future, that work has not been a priority because our observations of how ItFix and OOPS used in practice within the Freed and Sosnick labs suggest different challenges: +\begin{itemize} +\item Researchers often want to invoke ItFix many times at once for different proteins. Thus, even without parallelization of MCSA, we see large runs, involving hundreds of thousands of independent activities, with associated procedural challenges in terms of bookkeeping, error detection, restarting, and so forth. (See Figure X.) +\item The ItFix algorithm has several free parameters that are currently trained by chemical intuition and repeated trials. In order to best understand performance, researchers often want to run extensive benchmarks to evaluate algorithmic improvements. Again, the result is large runs involving many invocations of MCSA and other procedures. +\item Researchers often make changes to the computational structure???not at the lowest level of the MCSA application, but to things like convergence criteria. +\item Researchers also experiment with new applications of the OOPS framework, for example to crystal structure refinement and studies of biomolecular interactions. These applications do not change the basic MCSA building block, but do again involve the specification of new high-level structure. +\item Because computing demands always seem to exceed available resources, researchers frequently seek to make use of multiple computers, including local clusters and computers at NSF and DOE centers. +\end{itemize} + +These observations on how ItFix and OOPS are used suggest a need for mechanisms that allow for concise, readable specification of high-level structure that exposes opportunities for parallel execution; the robust management of large number of tasks; and the convenient dispatch of computation to multiple parallel computers, both local and remote. These considerations motivated our exploration of the use of the Swift parallel scripting system within OOPS. + +\begin{figure} +\begin{center} +\caption{OOPS ItFix data flow diagram, showing algorithm applied to multiple proteins concurrently, in multiple rounds.} +\label{fig:oops} +\end{center} + +\end{figure} + +\section{Parallel Prediction Scripting} +Swift [29] comprises: +\begin{enumerate} +\item a high-level, functional scripting language (???SwiftScript???), designed for expressing computations that invoke executable programs, with a dataflow model used to ensure that program invocations (???tasks???) are executed only when their input data is available; +\item a data model that allows for the mapping of file system structures (individual files, directories, etc.) into Swift language variables; and +\item a runtime system to manage the scheduling of tasks for execution, the dispatch of executable tasks to parallel computers, and the movement of data consumed and produced by those tasks. +\end{enumerate} + +\begin{verbatim} %figure 3: a simple swift example + app (PDT structure) predict(Fasta protein) { + predict_structure @protein @structure; + } + + foreach pfile, i in @arg("proteins") { + Fasta protein ; + PDT structure[]; + structure[i] = predict(protein); + } + +\end{verbatim} + +Figure 3 illustrates some basic Swift constructs. In brief: +\begin{itemize} +\item (L1-3) Defines an interface to an application program, predict\_structure. This interface maps from typed Swift variables to command-line program syntax. It expects a protein sequence specified in FASTA format and returns a structure prediction in the form of a ``trajectory" file in our ``PDT" format. +\item (L5-9) Invokes the procedure predict (and thus the predict\_structure program) in parallel, for each file listed in the command line argument ``proteins." +\end{itemize} + +Swift's dataflow model means that the multiple invocations of predict can run concurrently, as none is dependent on data produced by another. Swift's runtime system handles the dispatch of individual predict calls to an available computer, and the movement of the associated data to and from those computers. Thus, we are able in just eight lines to describe a potentially large amount of computing. +The Swift runtime system can deal with computations that involve many concurrent activities. By using two-level scheduling methods, as implemented for example in Falkon [24, 25], it has executed computations involving hundreds of thousands of tasks on supercomputers with tens of thousands of processors. (These methods first deploy task executors onto nodes and then stream tasks to those executors.) The Swift runtime system can also dispatch tasks to multiple computers, using Globus mechanisms [17] to overcome inevitable heterogeneities in authentication, job submission, and data movement methods. Swift implements various heuristics to decide where to send which task, and when. +When we first discussed combining OOPS with Swift, we sketched out simple pseudo-code examples, similar to Figure 1, of how we would use Swift programs to combine OOPS functions into high-performance applications. Our original conception has stood the test of time. While the integration of the OOPS framework with Swift demanded some extra initial development time, this investment has paid off. We have more concise and manageable programs; can run complex computations more easily and reliably; and are able to run our programs across many sites without modification. +To illustrate how we use Swift in OOPS, we present a simplified version of the basic ItFix program structure. The complete currently executing Swift script is available online [2]. +We leverage Swift data typing and mapping [20] to abstract input and outputs, group related items in structures, detect type errors, and map the simple logical structure to the specific data layout that we want to maintain in our archival storage repository. We first declare some useful atomic types to be simple files: for example, Fasta for the sequence being folded, and PDB, the known 3D structure, when available, for accuracy comparison. (Other such simple types are elided). Then we define some compound types, which as in other languages, are used to organize multiple related values. + +\begin{verbatim} +type Fasta; +type PDB; +... + +type MCSAIn { + Fasta fasta; + PDB pdb; + SecSeq secseq; + } + + type MCSAOut { + OOPSSecStr SecStr; + OOPSLog log; + OOPSEnergy Energy; + OOPSpdt pdt; + OOPSrmsd rmsd; + OOPSLibrary Library; +} +\end{verbatim} +We use app procedures to define Swift interfaces to application codes. For example, the Swift procedure mcsa defines an interface to the oops\_mcsa program (L19). Note how the procedure extracts components from the Swift procedure arguments and uses them to construct the arguments to oops\_mcsa (L20). + +\begin{verbatim} +app (MCSAOut out) mcsa (MCSAIn i, SecSeq secseq, + int jobnum, string cfgParams[]) +{ + oops_mcsa @i.fasta @secseq @i.pdb @out.pdt + @out.rmsd jobnum cfgParams stdout=@out.log; + } +\end{verbatim} + +We often also find it useful to define Swift interfaces to small utility functions. For example, in the following we use the Unix sed program to replace the values of science parameters in OOPS run configuration files. Any of the approximately 50 scientific parameters in about 8 configuration files can be dynamically set, and used in a parameter sweep, in this manner. In L22-24 below, we set parameters values that control the simulated annealing temperature ranges and descent rates. + +\begin{verbatim} +app (file oParams) setTemps (file inParams, string + start, string update) +{ + sed "-e" @strcat("s/@DIT@/",start,"/") "-e" + @strcat("s/@TUI@/",update,"/") + @inParams stdout=@oParams; + } + +\end{verbatim} + +Next, we define our parallel application logic. First, we specify how a single ItFix round is performed, via multiple concurrent calls to mcsa. The procedure singleRound (L25) sets various science configuration parameters (L28-29) and then uses a foreach statement (L30) to make the multiple calls to mcsa, accumulating the outputs in the array out. + +\begin{verbatim} +(MCSAOut out[]) singleRound +(string protein, MCSAIn mcsaIn, SecSeq secSeq, + int round, int nsim, string startTemp, + string tempUpdate) +{ +file inParams <@arg("params")>; + file editedParams = +setTemps(inParams, startTemp, tempUpdate); + string config [] = readData(editedParams); + +foreach sim in [0 : (nsim-1)] { + out[sim] = + mcsa(mcsaIn, secseq, sim, config);?? + } + } +\end{verbatim} + +The procedure ItFix (L35) implements the ItFix algorithm, calling singleRound repeatedly (and serially) (L48) until either convergence is detected (L51-52) or the specified rounds limit is reached (L52). + +\begin{verbatim} +ItFix(string protein, int nsim, int maxrounds, + string startTemp, string tempUpdate) +{ +OOPSIn oopsin ; + + string outdir = @arg("outdir"); + OOPSOut result[][] ; + SecSeq secseq[] ; + boolean converged[]; + external done[]; + secseq[0] = cpSecSeq(oopsin.secseq); + + iterate i { + (done[i], result[i]) = + singleRound(protein, oopsin, secseq[i], + i, nsim, startTemp, tempUpdate); + (converged[i], secseq[i+1]) = + analyzeRoundDir(protein, i, secseq[i], + done[i]); + } until ( converged[i] || (i==(maxrounds-1)) ); + } + +\end{verbatim} + +We can now provide the main program, in which we call may ItFix directly, to predict the structure of a single protein, or alternatively build up more complex programs. For example, the following program runs each of a set of protein sequences (from file plist), in up to maxrounds rounds: + +\begin{verbatim} +main_loop() +{ +int nsim = @toint(@arg("nsim"), 3); +int maxrounds = @toint(@arg("maxrounds", "3")); +string protein[] = readData(@arg("plist")); +foreach prot in protein { + ItFix(prot, nsim, maxrounds,"",""); + } +} +\end{verbatim} + +Thus, the simple code fragment in lines 54-62 above, given 10 proteins, nsim=1000, would, in each round of up to 3 rounds of prediction, execute $10 \times 1000 = 10,000$ simulations. The actual degree of parallelism is controlled by swift runtime settings and by the availability of processor resources. + +\section{Experience on Large Systems} +As the main work of our group is algorithm and method development, we are continually testing and evaluating the accuracy, spatial, and time performance of new codes. The OOPS code base is constantly evolving. Prior to deployment of our parallel scripting methods, it was virtually impossible to continually test evolving changes at scale. The methods described here make a new approach possible. +We are already using this framework to test some improvements to the ItFix algorithm. In this section we show some examples of what you can do in short main programs, once the core library routines above have been created and validated. + +\subsection{Usage Rates} +In the first two weeks of April 2009, just shortly after the ItFix Swift script was developed, the system has seen impressive use in pursuit of scientific inquiries by author Hocky: +ALCF Intrepid Blue Gene/P: +67178 jobs, 208,763 CPU hours +TeraGrid: +22495 jobs, 2397 CPU hours +Ranger: +17488 jobs, 1425 CPU hours +Over 100 GB of compressed science results data was produced from the Blue Gene runs alone. + +\subsection{Parameter Sweeps} +Given the library of Swift procedures defined above, the programmer can use flexible scripts to leverage many processors with relative ease, as in the following code. +\begin{verbatim} +int nsim = @toint(@arg("nsim"), 3); +int maxrounds = @toint(@arg("maxrounds", "3")); +string protein[] = readData(@arg("plist")); +string startT[] = readData(@arg("startT")); +string tUpdate[] = readData(@arg("tUpdate")); + +foreach prot in protein { + foreach sT in startT { + foreach tUp in tUpdate { + ItFix(prot, nsim, maxrounds, sT, tUp); + } + } +} + +\end{verbatim} + +This simple code fragment, given 10 proteins, nsim=1000, two starting temperatures and 5 update intervals, would, in each round of up to 3 rounds of prediction, execute $10 \times 1000 \times 2 \times 5 = 100,000$ simulations. On highly parallel systems such as the Argonne Intrepid BGP, this simple code fragment can fully utilize a substantial portion of the machine???s 163,840 processor cores. Similar code with a slightly more general parameterization of ItFix can sweep across any combination of settable parameters that govern the OOPS MCSA algorithm. + +\subsection{Data Analysis and Visualization} +We have integrated a range of visualization tools (e.g., PyMol for protein visualization; scatter plots of protein energy level vs. the root-mean-square distance (RMSD) of backbone atoms of the predicted structure to the known structure) into the framework via simple analysis scripts. These visualizations are a primary tool used by our labs to assess prediction quality. Analysis in the current script is accomplished by collectively summarizing round results from log files, generating diagnostic 2D secondary structure predictions, and calculating the lowest RMSD and predicted 3D models. Quantitative molecular accuracy results and molecular visualization are also produced in a web-based format (Figure 7). + +\subsection{OOPS Experiments Conducted in Swift} +As mentioned, the ItFix algorithm has several free parameters. Each individual folding simulation is a Monte Carlo Simulated Annealing (MCSA) procedure, meaning that the simulation is started at a Starting Temperature (ST) and after a Temperature Update Interval (TUI) the temperature is decreased based on a temperature scheduling algorithm [10]. The idea is to have a simulation that drives a molecule its lowest energy state, which in the case of proteins we call the native state. This occurs because in the MCSA loop, a structure is accepted only if it has a lower energy then the previous, or if it has a higher energy, on with a conditional probability decreasing with temperature. +We use a statistical scoring function as our measure of energy, and because our temperature units are arbitrary it is difficult to determine what values of ST and TUI will give the desired results. While the ItFix procedure as implemented in Debartolo et al. [13] is highly successful, the ST and TUI parameter space were not explored extensively. We wanted to know for that particular implementation, and for future implementations of ItFix, whether other combinations of these parameters can give comparable or better results while using less computer time. +Since we already had a flexible Swift framework implemented for running OOPS across multiple sites, it was simple to implement a parameter sweep workflow that explores this space and which leverages HPC resources to do so. This parameter sweep is essentially the program provided in Section 5.1. Figure 5 describes our use of HPC and results. + +\begin{figure} +\begin{center} +\caption{The outputs of an initial test run on Intrepid are shown here for four representative proteins. Note that the protein???s native secondary structure was used as input, so a direct comparison to DeBartolo et al. is only relevant for $\alpha$-proteins, where ItFix effectively converges to the native secondary structure.} +\label{fig:test-outputs} +\end{center} +\end{figure} +\paragraph{Initial Test} +In order to evaluate the performance of the ItFix algorithm, we chose proteins whose structures are well determined experimentally, and give as input to the ItFix algorithm the native secondary structure in addition to the amino acid sequence. In the method of DeBartolo et al., to generate predictions for publication, the ST was 100 and the TUI was 1000 and 2000 simulations were run for each protein. In our initial test, we ran short simulations on Argonne???s BG/P (Intrepid). For four proteins, we ran 150 simulations each of ST of 15 and 25 and TUI of 25, 50, and 100 (see Figure 4). +The results presented immediate information for further investigation. The four proteins we picked were representative, two contained only the $\alpha$-helical secondary structure unit, and two contained both $\alpha$ and $\beta$ motifs. For the $\alpha/\beta$ proteins the results were predictably bad. We knew from experience that a large amount of sampling must be done to get properly aligned $\beta$ structures. However, the results for $\alpha$ proteins were surprising. For all TUI ad ST combinations and in just 150 simulations, the results were nearly comparable to those published by DeBartolo et. al., while using two orders of magnitude less simulation. The obvious conclusion was that once a protein is assigned as $\alpha$ by the ItFix algorithm, we should consider running many short simulations rather than fewer long simulations. Two questions then remained: (a) can we use this method to generate predictions of higher accuracy than DeBartolo et al. with this method, and (b) what should we do about $\alpha$/$\beta$ and $\beta$ proteins? +\paragraph{Investigation of $\alpha$ Proteins} +Because we were running short simulations, this investigation was particularly fruitful. We used a mixture of Teragrid sites for these tests (Abe, QueenBee, and Ranger), where simulations all took 2-10 minutes. The results in this test were strong. Running approximately 5000 simulations for each of three alpha proteins yielded results better than those of DeBartolo et. al.[13].Additionally, for each protein the CPU time utilized was approximately 500 CPU-hours while that used in the ItFix protocol would take more than 2000 CPU-hours depending on system load, etc. + +\begin{figure} +\begin{center} +\caption{Table presenting results of running > 5000 simulations on alpha proteins using TeraGrid resources. The structures generated are better than those of DeBartolo et al. [13], and required significantly less computation. The lower images are the predicted structures (with helices in red and coil in green) overlaid with the native structures (colored orange).} +\label{fig:alpha-sim-res} +\end{center} +\end{figure} + +\paragraph{Investigation of $\beta$ Proteins} +Parameter sweep simulations for $\beta$ proteins demonstrated the anecdotal evidence described above; it is necessary to do a large amount of in-simulation sampling in addition to many parallel MCSA runs to generate a good ensemble of structure for $\beta$ or $\alpha$/$\beta$ targets. Since this was the case, we then decided to investigate the performance of Intrepid with our simulation framework for use in future folding investigations where large amounts of sampling are necessary. +\paragraph{Replicate/compare DeBartolo et al. runs} +In previous sections, we used our scripting framework to investigate properties of ItFix. Another thing we wish to learn is what resources will be useful for which kinds of future applications. One thing we would like to know is whether a resource such as a BG/P with many low-power processors can be useful for our types of studies. In Figure 6 we show that an ItFix investigation can be successfully and stably executed with Swift/Falkon. Though the runtimes are longer than would be expected on stock processors, the availability of thousands of processors and the stability of our system shows that use of Intrepid can be fruitful in future investigations. After this simulation we also successfully ran simulations with the exact protocol of DeBartolo et al. for T1mky and T1tif, results of which can be seen on our project web site [2]. + +\begin{figure} +\begin{center} +\caption{Results of running eight proteins on 2 racks (8192 CPUS) on Argonne???s BG/P, Intrepid. Below are results from this investigation for T1af7. On the left is a scatter plot showing the correlation between our statistical energy potential and accuracy of the protein structures for the 985 simulations that ran to completion. On the right is an image showing the lowest RMSD structure. This table, plot and image were all automatically generated by our scripting mechanism, and the table is presented by a simple CGI script at our web site [2].} +\label{fig:bgprun} +\end{center} +\end{figure} +\paragraph{Automatic Timing Runs} +To effectively utilize computational resources for Monte Carlo simulations, it is important to know how your algorithm scales with the amount of sampling that you wish to have done. With this framework, we can easily run loops over various parameters and test the scaling of our algorithm. We performed a simple test on the TeraGrid site Ranger, using three different ST values (25,50,100) and 4 different TUIs (50,100,200,500). A sample output can be seen in Figure 77. + +\begin{figure} +\begin{center} +\caption{Sample result of a timing run on Ranger for varying values of Temperature Update Interval with Starting Temperature of 100.} +\label{fig:rangerplot} +\end{center} +\end{figure} +\section{Related Work} +We discuss related work in both protein structure prediction and computing. +\subsection{Structure Prediction Approach} +Most folding algorithms rely heavily on known structures or fragments (homology- or template-based) and can be extremely successful [8, 31]. Their success, however, rapidly decreases as the amount of known information decreases [26]. Other methods take a physics-based approach [22], but are limited in their ability to predict large targets on short time scales. +Uniquely among known approaches to structure prediction, OOPS operates with minimal use of information derived from sequence similarity to proteins in the Protein Data Bank (PDB) [7]. OOPS derives its speed and accuracy from the use of a ``C$\beta$" model [10], an accurate statistical potential [16], and a search strategy involving iterative fixing of structure in multiple ???rounds??? of folding [13]. Since OOPS uses minimal homology information and a reduced representation, its success depends crucially on describing the protein physics correctly. Great effort has been devoted to the energy function, e.g., interactions are conditional on backbone geometry and the relative orientation of side chains. In 2007, its accuracy exceeded available all-atom potentials [16] by utilizing secondary structure dependence, and it has been significantly improved since then by including orientation-dependence [13]. Its homology-free secondary and tertiary structure predictions for small pr oteins rival or exceed homology-based methods with (expensive) explicit side chains, engendering optimism for continued progress. It also employs sequence homology for additional accuracy when appropriate. +Our algorithm can predict the structures of two sets of proteins with comparable accuracy for $\alpha$, $\alpha$/$\beta$, and $\beta$ proteins (DeBartolo et. al , [13] Table 2). These predictions are comparable in accuracy to the successful Rosetta fragment-based insertion algorithm, described in the papers from which the test sets are obtained [8, 19] +\subsection{Computing Approach} +Our computing approach builds on two related layers: the Swift parallel scripting system, and two-level scheduling, as implemented in Falkon and via the Swift ``coaster" mechanism. +Other approaches to high-level specification of loosely coupled scientific computations include MapReduce, DAGMan, Pegasus, BPEL,Taverna. Triana, Kepler, and Karajan. +MapReduce [12] supports the processing of key-value based data, using the Google File System. Swift targets various scientific applications that process heterogeneous data formats, and can schedule computations in a location-independent way. +Pegasus [15] and DAGMan [4] can also schedule large scale computations in Grid environments. DAGMan provides a workflow engine that manages Condor jobs organized as directed acyclic graphs (DAGs) in which each edge corresponds to an explicit task precedence. It has no knowledge of data flow, and in distributed environments works best with a higher-level, data-cognizant layer. DAGMan also lacks dynamic features such as iteration (which can result in large DAGs) and conditional execution. Pegasus is primarily a set of DAG transformers that can translate a workflow graph into a location-specific DAGMan input file; prune tasks for files that exist; select sites for jobs; and cluster jobs based on various criteria. A weakness is that planners must operate on an entire workflow statically, and execution sites cannot be changed after Pegasus processes a workflow, which can be long before a job runs, a strategy that may not work well in dynamic environments BPEL [1] has primarily be en applied in service composition and orchestration. A lack of support for iteration means that programs can be larger, although the problem is being addressed in its latest 2.0 specification. In addition, the complex XML specification is cumbersome to write compared with our compact scripting language. +Taverna [21], Triana [27], and Kepler [5] have also been applied in science problems. However, they do not abstract dataset types or provide location transparency. Data movement and Grid job submission all need to be explicitly specified and organized. Their support for multi-site Grid execution is also of limited scale. +As discussed earlier, Swift integrates Karajan [18]. Karajan provides the libraries and primitives for job scheduling, data transfer, and Grid job submission; Swift adds support for high-level abstract specification of large parallel computations, data abstraction, and workflow restart, and also (via Falkon) fast, reliable execution over multiple Grid sites. +Work related to Swift???s use of Falkon and coasters for lightweight scheduling includes IBM???s Kittyhawk project [6], Cope et al.'s work [11] on integrating lightweight scheduling in the Cobalt scheduling system, using the HTC-mode support in Cobalt. We have compared the performance of Falkon on the Blue Gene/P with those of Cope at al. and Peters et al. [23], and found at least one order of magnitude better performance, and several orders of magnitude better scalability. This improved performance and scalability of the middleware can translate into direct improvements in scalability and performance for applications, with finer grained task parallelism and reduced end-to-end application execution times. +\section{Future Work} +The work described here has come together over a fairly short period in Feb-April 2009. Its success has enabled us to chart the following enhancements, which our experience to date suggests are readily achievable. +While it was straightforward to code ItFix in Swift, the language and its runtime semantics are still young and evolving. We were eager to learn more about the language's completeness and usability through the experience of the kinds of real production usage as this project. Three aspects of language enhancement seem desirable from our OOPS scripting experience: 1) the need for polymorphism, so a superset data structure can receive the results of several similar but non-identical application program signatures; 2) the desirability of providing global variables so that, for example, all functions can be aware of application command line variables; and 3) an alternative to the Swift construct called ``external" variables, used to circumvent the systems inability to pass a very long list of data objects as a command line argument. All of these are now being considered for near-term enhancements to the language. +Scaling through hybrid parallelization. To improve the scaling of OOPS on systems such as the BG/P, with massive numbers of low-speed processors, we will turn OOPS into a hybrid HPC/MTC application???what we may term ``MPTC", for many parallel-task computing???by parallelizing the MCSA energy-computing function, in which profiling has shown that over 85\% of the time in OOPS is spent. We have designed a data structuring approach that will make this straightforward, opening the door to much greater scaling by using up to 1024 cores for a single MCSA prediction operation. +We can thus estimate the speeds we expect to achieve on our target petascale platforms. Folding 10 proteins with a fold size of 10 rounds and a round size of 1,000 MCSA simulations can utilize 100,000 CPUs working in parallel with no data dependencies and hence near-perfect scaling. If we devote between 4 and 16 cores to each Mcsa() function for the parallel computation of the energy of each configuration, we can effectively utilize 40,000 to 160,000 compute cores for this task, or 4,000 to 16,000 cores per protein. Realistically, even on petascale systems with 50K to 300K cores, most user jobs will run with allocations far less than the full system. Thus, this scale fits well for today's usage, and can expand to greater utilization, even for single proteins, as the parallelization of the energy computation increases. +Many-task data management. Loosely coupled parallel scripting, while productive for the developer, imposes a high performance burden on large scale systems. We address this issue with a collective I/O model for file-based many-task computing [28] that we have prototyped on the BG/P and which enables efficient distribution of input data files to computing nodes and gathering of output results from them. This approach broadcasts common input data, and uses efficient scatter/gather and caching techniques for input and output. +Comprehensive user environment. An OOPS ``run configurator" mechanism packaged for use both from a web-form-based interface as well as via a simple textual command specification will enable users to specify OOPS runs with no programming. The web interface will be runable locally by any user or community as a service of the OOPS workflow framework. +The collaboration environment will leverage the Computation Institute's Petascale Active Data Server (PADS): a 0.5PB storage system integrated with a 384-node cluster, with another 0.3PB of storage and ample RAM on the cluster nodes (NSF grant OCI-0821678). This facility will be ideal for ``stage-2" analysis (where stage-1 analysis is done on the target petascale systems themselves as part of the OOPS workflow, as described above). + +\begin{figure} +\begin{center} +\caption{Planned OOPS Environment} +\label{fig:oops-planned} +\end{center} +\end{figure} + +\section{Conclusion} +We have described the recent, rapid success in recoding an ad-hoc implementation of protein structure prediction by ``iterative fixing" and simulated annealing in the Swift parallel scripting language, and report on the progress, benfits, and remaining work needed to make this approach a highly-productive example of utilizing petascale systems to achieve greater scientific insights into important aspects of the structural and behavioral properties of large biomolecules. +We have identified remaining deficiencies in this approach and presented a plan for future work that addresses them. +In general, we believe our work shows, in part, the unsurprising conclusion that easier access to a greater level of computing resources means a larger lab in which to test more hypotheses, in less time, with less effort, and thus few distractions for scientists seeking to advance their science rather than to address the complexities of computing at this scale. +We believe our work demonstrates that once a basic set of procedures have been created, the Swift approach to parallel scripting can be productive; what we find most exciting is that short, compact concise scripts, which clearly show the science logic, can be automatically executed across diverse resource types, and can leverage large computational resources. Thus, we run much larger problems, and explore a large scientific space. It allows us to ask questions we could not ask before. +Another advantage of our script-based approach is that we have the future benefit of automated data provenance tracking [9, 30] within the workflow execution engine, as well as the ability to leverage multiple petascale execution resources within a single computation. +From our experience with the system to date, we believe that the new capability will accelerate the rate of discovery in the Freed and Sosnick labs, by increasing the rate at which we can improve the speed and accuracy of OOPS. A core science process in these labs is the enhancement in terms of predictive accuracy, speed, and functional capability of the Open Protein Simulator. Enabling many more lab members to perform more simulations, with larger Monte Carlo sample sets, and to easily test and compare the performance of the system across a range of parameter values, has proven its value already in terms of new insights into the behavior of our algorithms and the degree of simulation needed to converge on accurate predictions. +% use section* for acknowledgement +\section*{Acknowledgment} +This work was supported in part by the National Science Foundation under Grant OCI-0721939, by NASA Ames Research Center GSRP Grant Number NNA06CB89H; by the Mathematical, Information, and Computational Sciences Division subprogram of the Office of Advanced Scientific Computing Research, Office of Science, U.S. Dept. of Energy, under Contract DE-AC02-06CH11357; by NIH research (T.R.S. and K.F. F.) and training grants, and by the National Science Foundation through TeraGrid computing resources, by the ALCF, and the resources of the Open Science Grid. The authors would like to thank: The Swift Group, the Computation Institute, the ZeptoOS group and the Argonne Leadership Computing Facility. +% trigger a \newpage just before the given reference +% number - used to balance the columns on the last page +% adjust value as needed - may need to be readjusted if +% the document is modified later +%\IEEEtriggeratref{8} +% The "triggered" command can be changed if desired: +%\IEEEtriggercmd{\enlargethispage{-5in}} + +% references section + +% can use a bibliography generated by BibTeX as a .bbl file +% BibTeX documentation can be easily obtained at: +% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/ +% The IEEEtran BibTeX style support page is at: +% http://www.michaelshell.org/tex/ieeetran/bibtex/ +%\bibliographystyle{IEEEtran} +% argument is your BibTeX string definitions and bibliography database(s) +%\bibliography{IEEEabrv,../bib/paper} +% +% manually copy in the resultant .bbl file +% set second argument of \begin to the number of references +% (used to reserve space for the reference number labels box) +\begin{thebibliography}{1} + +\bibitem{IEEEhowto:kopka} +H.~Kopka and P.~W. Daly, \emph{A Guide to \LaTeX}, 3rd~ed.\hskip 1em plus + 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999. + +\end{thebibliography} + +% that's all folks +\end{document} + + From wozniak at ci.uchicago.edu Mon May 16 09:22:38 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 16 May 2011 09:22:38 -0500 (CDT) Subject: [Swift-commit] r4475 - trunk/src/org/griphyn/vdl/karajan/lib Message-ID: <20110516142238.B12489CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-16 09:22:38 -0500 (Mon, 16 May 2011) New Revision: 4475 Modified: trunk/src/org/griphyn/vdl/karajan/lib/Execute.java Log: Drop debugging line Modified: trunk/src/org/griphyn/vdl/karajan/lib/Execute.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/Execute.java 2011-05-15 03:34:27 UTC (rev 4474) +++ trunk/src/org/griphyn/vdl/karajan/lib/Execute.java 2011-05-16 14:22:38 UTC (rev 4475) @@ -51,7 +51,6 @@ scheduler.addJobStatusListener(this, task); setStack(task, stack); scheduler.enqueue(task, constraints); - System.out.println("Task is "+ task.getAttributeNames().toString() +" and constraints are "+constraints.toString()); } catch (CanceledReplicaException e) { if (logger.isDebugEnabled()) { From wozniak at ci.uchicago.edu Mon May 16 09:23:15 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 16 May 2011 09:23:15 -0500 (CDT) Subject: [Swift-commit] r4476 - trunk/src/org/griphyn/vdl/karajan/lib Message-ID: <20110516142315.E91189CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-16 09:23:15 -0500 (Mon, 16 May 2011) New Revision: 4476 Modified: trunk/src/org/griphyn/vdl/karajan/lib/Execute.java Log: Drop unused imports Modified: trunk/src/org/griphyn/vdl/karajan/lib/Execute.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/Execute.java 2011-05-16 14:22:38 UTC (rev 4475) +++ trunk/src/org/griphyn/vdl/karajan/lib/Execute.java 2011-05-16 14:23:15 UTC (rev 4476) @@ -5,8 +5,6 @@ import org.apache.log4j.Logger; import org.globus.cog.abstraction.impl.common.StatusEvent; -import org.globus.cog.abstraction.interfaces.Specification; -import org.globus.cog.abstraction.interfaces.JobSpecification; import org.globus.cog.abstraction.interfaces.Status; import org.globus.cog.abstraction.interfaces.Task; import org.globus.cog.karajan.arguments.Arg; @@ -15,7 +13,6 @@ import org.globus.cog.karajan.util.TypeUtil; import org.globus.cog.karajan.workflow.ExecutionException; import org.globus.cog.karajan.workflow.KarajanRuntimeException; -import org.globus.cog.karajan.workflow.events.EventBus; import org.globus.cog.karajan.workflow.futures.FutureVariableArguments; import org.globus.cog.karajan.workflow.nodes.grid.GridExec; import org.griphyn.vdl.karajan.lib.replication.CanceledReplicaException; From wozniak at ci.uchicago.edu Mon May 16 10:43:22 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 16 May 2011 10:43:22 -0500 (CDT) Subject: [Swift-commit] r4477 - trunk/tests Message-ID: <20110516154322.5E8789CD2E@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-16 10:43:22 -0500 (Mon, 16 May 2011) New Revision: 4477 Modified: trunk/tests/suite.sh Log: Test suite: Do not remove existing code trees; new -t option Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-16 14:23:15 UTC (rev 4476) +++ trunk/tests/suite.sh 2011-05-16 15:43:22 UTC (rev 4477) @@ -4,7 +4,7 @@ # The script will (optionally) checkout Swift, run several tests in a # subdirectory called run-DATE, and generate useful HTML output and -# tests.log +# tests.log . Tests are grouped into test GROUPs. # Usage: suite.sh * @@ -12,13 +12,16 @@ # Assuming your code is in /tmp/cog, where you # have the conventional cog/modules/swift configuration, # and you have done an ant dist, you can run -# suite.sh -a -c -g -p -s -o /tmp tests/groups/group-all-local.sh +# suite.sh -t -o /tmp tests/groups/group-all-local.sh # or cd into /tmp and run -# suite.sh -a -c -g -p -s cog/modules/swift/tests/groups/group-all-local.sh +# suite.sh -t cog/modules/swift/tests/groups/group-all-local.sh +# The -t option is "Tree mode"- as in, "test my existing source tree" # Run suite.sh -h for quick help # When something goes wrong, find and check tests.log or use -v -# Code is checked out into TOPDIR (PWD by default) (PATH is overridden) + +# The TOPDIR (PWD by default) is set with the -o option. +# Code is checked out into this directory or must already exist there. # The variables COG_VERSION and SWIFT_VERSION must be set for code checkout # e.g. COG_VERSION=branches/4.1.8, SWIFT_VERSION=branches/release-0.92 # Swift is compiled and installed in its source tree @@ -107,18 +110,19 @@ echo "suite.sh " echo "" echo "usage:" - printf "\t -a Do not run ant dist \n" - printf "\t -c Do not remove dist (clean) \n" - printf "\t -g Do not run grid tests \n" - printf "\t -h This message \n" - printf "\t -k Skip first N tests \n" - printf "\t -n Run N tests and quit \n" - printf "\t -p Do not build the package \n" - printf "\t -s Do not do a fresh svn checkout \n" - printf "\t -x Do not continue after a failure \n" - printf "\t -v Verbose (set -x, HTML comments) \n" - printf "\t -o output Location for output (TOPDIR) \n" - printf "\t GROUPLIST definition file \n" + printf "\t -a Do not run ant dist \n" + printf "\t -c Do not remove dist (clean) \n" + printf "\t -g Do not run grid tests \n" + printf "\t -h This message \n" + printf "\t -k Skip first N tests \n" + printf "\t -n Run N tests and quit \n" + printf "\t -p Do not build the package \n" + printf "\t -s Do not do a svn checkout \n" + printf "\t -t Tree mode (alias: -a,-c,-g,-p,-s) \n" + printf "\t -x Do not continue after a failure \n" + printf "\t -v Verbose (set -x, HTML comments) \n" + printf "\t -o output Location for cog and output \n" + printf "\t GROUP argument \n" } # Defaults: @@ -164,6 +168,13 @@ -s) SKIP_CHECKOUT=1 shift;; + -t) + # "Tree mode" + RUN_ANT=0 + CLEAN=0 + GRID_TESTS=0 + BUILD_PACKAGE=0 + SKIP_CHECKOUT=1 -x) ALWAYS_EXITONFAILURE=1 shift;; @@ -978,7 +989,6 @@ if [ "$SKIP_CHECKOUT" != "1" ]; then TESTNAME="Checkout CoG" start_row - test_exec rm -rf cog COG="https://cogkit.svn.sourceforge.net/svnroot/cogkit/$COG_VERSION/src/cog" test_exec svn co $COG end_row @@ -986,7 +996,6 @@ TESTNAME="Checkout Swift" start_row test_exec cd cog/modules - test_exec rm -rf swift test_exec svn co https://svn.ci.uchicago.edu/svn/vdl2/$SWIFT_VERSION swift end_row fi From davidk at ci.uchicago.edu Mon May 16 14:41:02 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Mon, 16 May 2011 14:41:02 -0500 (CDT) Subject: [Swift-commit] r4481 - trunk Message-ID: <20110516194102.A123A9CC94@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-16 14:41:02 -0500 (Mon, 16 May 2011) New Revision: 4481 Modified: trunk/build.xml Log: Updated build.xml to build docs Modified: trunk/build.xml =================================================================== --- trunk/build.xml 2011-05-16 19:38:01 UTC (rev 4480) +++ trunk/build.xml 2011-05-16 19:41:02 UTC (rev 4481) @@ -55,6 +55,8 @@ fixeol: change newlines to the unix standard. + docs: + Build Swift documentation from asciidoc txt files @@ -87,7 +89,6 @@ - @@ -261,6 +262,15 @@ + + + + + + + + + @@ -367,7 +377,7 @@ - + Swift ${version} From davidk at ci.uchicago.edu Tue May 17 10:29:13 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Tue, 17 May 2011 10:29:13 -0500 (CDT) Subject: [Swift-commit] r4482 - www Message-ID: <20110517152913.D1F619CD2E@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-17 10:29:13 -0500 (Tue, 17 May 2011) New Revision: 4482 Added: www/push_to.sh Log: Script to quickly copy web site Added: www/push_to.sh =================================================================== --- www/push_to.sh (rev 0) +++ www/push_to.sh 2011-05-17 15:29:13 UTC (rev 4482) @@ -0,0 +1,16 @@ +#!/bin/bash + +if [ -n "$1" ]; then + DESTINATION=$1 +else + echo Error: Specify directory to copy to + exit 1 +fi + +FILESTOCOPY="about bric-flow.jpg css downloads guides index.html links papers sitemap.xml apps bric-flow-thm.jpg dhtml.js images info main otherdoc push_to.sh shBrushVDL2.js style.css template_info + docs inc javadoc nostyle.css packages README.txt shCoreu.js support tests" + +for file in $FILESTOCOPY +do + cp -vpr $file $DESTINATION +done Property changes on: www/push_to.sh ___________________________________________________________________ Added: svn:executable + * From wozniak at ci.uchicago.edu Tue May 17 16:54:15 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Tue, 17 May 2011 16:54:15 -0500 (CDT) Subject: [Swift-commit] r4484 - trunk/tests/language/working Message-ID: <20110517215415.E69339CD2E@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-17 16:54:15 -0500 (Tue, 17 May 2011) New Revision: 4484 Modified: trunk/tests/language/working/006-procedure-invocation-with-assign.swift Log: Fix this test script Modified: trunk/tests/language/working/006-procedure-invocation-with-assign.swift =================================================================== --- trunk/tests/language/working/006-procedure-invocation-with-assign.swift 2011-05-17 15:30:41 UTC (rev 4483) +++ trunk/tests/language/working/006-procedure-invocation-with-assign.swift 2011-05-17 21:54:15 UTC (rev 4484) @@ -4,6 +4,5 @@ app { echo i stdout=@f; } } -int greetings; -file hw=echo(greetings); - +int greetings = 2; +file hw = echo(greetings); From ketan at ci.uchicago.edu Tue May 17 17:02:59 2011 From: ketan at ci.uchicago.edu (ketan at ci.uchicago.edu) Date: Tue, 17 May 2011 17:02:59 -0500 (CDT) Subject: [Swift-commit] r4485 - www/cookbook Message-ID: <20110517220259.3B8399CD2E@svn.ci.uchicago.edu> Author: ketan Date: 2011-05-17 17:02:58 -0500 (Tue, 17 May 2011) New Revision: 4485 Modified: www/cookbook/cookbook-asciidoc.html www/cookbook/cookbook-asciidoc.txt Log: updates on bionimbus howto Modified: www/cookbook/cookbook-asciidoc.html =================================================================== --- www/cookbook/cookbook-asciidoc.html 2011-05-17 21:54:15 UTC (rev 4484) +++ www/cookbook/cookbook-asciidoc.html 2011-05-17 22:02:58 UTC (rev 4485) @@ -587,15 +587,6 @@ Swift runtime system. For introductory material, consult the Swift tutorial found here.

-

Swift is a data-oriented coarse grained parallel scripting language that supports -dataset typing and mapping, dataset iteration, conditional branching, and -procedural composition.

-

Swift programs (or workflows) are written in a language called SwiftScript.

-

SwiftScript programs are dataflow oriented - they are primarily concerned with -processing (possibly large) collections of data files, by invoking programs to -do that processing. Swift handles execution of such programs on remote sites -by choosing sites, handling the staging of input and output files to and from -the chosen sites and remote execution of program code.

@@ -629,7 +620,11 @@

2.2. Setting up to run Swift

This is simple. We will be using a pre-compiled version of Swift that can be -downloaded from here.

+downloaded from here. Download and untar the latest precompiled version as follows:

+
+
+
$ tar xf swift-0.92.1.tar.gz
+

2.2.1. Environment Setup

The examples were tested with Java version 1.6. Make sure you do not already @@ -1186,7 +1181,7 @@

4.1. Beagle

Swift is now installed on Beagle as a module. Swift supports a Coasters based, computing environment for Beagle. A detailed Swift documentation is maintained -[[here]. To get started +[[here]. To get started with Swift on Beagle follow the steps outlined below:

step 1. Load the Swift module on Beagle as follows: module load swift

step 2. Create and change to a directory where your Swift related work will @@ -1495,7 +1490,7 @@

Modified: www/cookbook/cookbook-asciidoc.txt =================================================================== --- www/cookbook/cookbook-asciidoc.txt 2011-05-17 21:54:15 UTC (rev 4484) +++ www/cookbook/cookbook-asciidoc.txt 2011-05-17 22:02:58 UTC (rev 4485) @@ -15,18 +15,6 @@ introductory material, consult the Swift tutorial found link:http://www.ci.uchicago.edu/swift/guides/tutorial.php[here]. -Swift is a data-oriented coarse grained parallel scripting language that supports -dataset typing and mapping, dataset iteration, conditional branching, and -procedural composition. - -Swift programs (or workflows) are written in a language called SwiftScript. - -SwiftScript programs are dataflow oriented - they are primarily concerned with -processing (possibly large) collections of data files, by invoking programs to -do that processing. Swift handles execution of such programs on remote sites -by choosing sites, handling the staging of input and output files to and from -the chosen sites and remote execution of program code. - Swift Basics ------------ @@ -733,12 +721,16 @@ vary based on what ip you get for your Virtual Machine instance #On anywhere as long as provide the correct callback uri: here the -"http://140.221.9.110:42195" is the callback uri of previous ones +"http://140.221.9.110:35753" is the callback uri of previous ones -**step6.** Start the worker from the virtual machine -+worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the -coaster service is listening to the workers+ +**step6.** Copy the +worker.pl+ from gatewayx to the VM: +scp +swift-0.92/bin/worker.pl root at 10.101.8.50:/bin/+, you will be prompted for the +root password of the VM. +**step7.** Start the worker from the virtual machine ++worker.pl http://localhost:35753 tmp /tmp+ +where 35753 is the port where the coaster service is listening to the workers+ + .sites.xml for the above run [xml] From ketan at ci.uchicago.edu Tue May 17 17:04:56 2011 From: ketan at ci.uchicago.edu (ketan at ci.uchicago.edu) Date: Tue, 17 May 2011 17:04:56 -0500 (CDT) Subject: [Swift-commit] r4486 - www/cookbook Message-ID: <20110517220456.457C79CD2E@svn.ci.uchicago.edu> Author: ketan Date: 2011-05-17 17:04:55 -0500 (Tue, 17 May 2011) New Revision: 4486 Modified: www/cookbook/cookbook-asciidoc.html Log: updates on bionimbus howto Modified: www/cookbook/cookbook-asciidoc.html =================================================================== --- www/cookbook/cookbook-asciidoc.html 2011-05-17 22:02:58 UTC (rev 4485) +++ www/cookbook/cookbook-asciidoc.html 2011-05-17 22:04:55 UTC (rev 4486) @@ -1282,10 +1282,13 @@

root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will vary based on what ip you get for your Virtual Machine instance

#On anywhere as long as provide the correct callback uri: here the -"http://140.221.9.110:42195" is the callback uri of previous ones

-

step6. Start the worker from the virtual machine -worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the -coaster service is listening to the workers

+"http://140.221.9.110:35753" is the callback uri of previous ones

+

step6. Copy the worker.pl from gatewayx to the VM: scp +swift-0.92/bin/worker.pl root at 10.101.8.50:/bin/, you will be prompted for the +root password of the VM.

+

step7. Start the worker from the virtual machine +worker.pl http://localhost:35753 tmp /tmp +where 35753 is the port where the coaster service is listening to the workers+

sites.xml for the above run
From wozniak at ci.uchicago.edu Thu May 19 22:36:04 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Thu, 19 May 2011 22:36:04 -0500 (CDT) Subject: [Swift-commit] r4502 - in trunk/src/org/griphyn/vdl: karajan/lib mapping Message-ID: <20110520033604.D59089CD2E@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-19 22:36:04 -0500 (Thu, 19 May 2011) New Revision: 4502 Modified: trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java trunk/src/org/griphyn/vdl/mapping/DSHandle.java Log: Minor readability changes Modified: trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java 2011-05-20 03:32:49 UTC (rev 4501) +++ trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java 2011-05-20 03:36:04 UTC (rev 4502) @@ -463,18 +463,17 @@ } private void closeDeep(VariableStack stack, DSHandle handle, - WrapperMap hash) throws InvalidPathException, ExecutionException { + WrapperMap wrapperMap) + throws InvalidPathException, ExecutionException { handle.closeShallow(); - hash.close(handle); + wrapperMap.close(handle); try { - // Mark all leaves - Iterator it = handle.getFields(Path.CHILDREN).iterator(); - while (it.hasNext()) { - closeDeep(stack, (DSHandle) it.next(), hash); - } + // Mark all children + for (DSHandle child : handle.getFields(Path.CHILDREN)) + closeDeep(stack, child, wrapperMap); } catch (HandleOpenException e) { - throw new ExecutionException("Handle open in closeChildren",e); + throw new ExecutionException("Handle open in closeChildren", e); } } Modified: trunk/src/org/griphyn/vdl/mapping/DSHandle.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/DSHandle.java 2011-05-20 03:32:49 UTC (rev 4501) +++ trunk/src/org/griphyn/vdl/mapping/DSHandle.java 2011-05-20 03:36:04 UTC (rev 4502) @@ -48,7 +48,7 @@ * * @return a Collection of DSHandle objects */ - public Collection getFields(Path path) throws InvalidPathException, HandleOpenException; + public Collection getFields(Path path) throws InvalidPathException, HandleOpenException; public Object getValue(); From wozniak at ci.uchicago.edu Mon May 23 09:40:28 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 09:40:28 -0500 (CDT) Subject: [Swift-commit] r4503 - trunk/tests/providers/local-coasters Message-ID: <20110523144028.8C15B9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 09:40:27 -0500 (Mon, 23 May 2011) New Revision: 4503 Added: trunk/tests/providers/local-coasters/201-cp.check.sh trunk/tests/providers/local-coasters/201-cp.clean.sh trunk/tests/providers/local-coasters/201-cp.setup.sh trunk/tests/providers/local-coasters/201-cp.swift trunk/tests/providers/local-coasters/201-input-1.txt Log: Multi-job local Coasters test Added: trunk/tests/providers/local-coasters/201-cp.check.sh =================================================================== --- trunk/tests/providers/local-coasters/201-cp.check.sh (rev 0) +++ trunk/tests/providers/local-coasters/201-cp.check.sh 2011-05-23 14:40:27 UTC (rev 4503) @@ -0,0 +1,9 @@ +#!/bin/sh + +set -x + +COUNT=$( ls 201-output* | grep -c ) + +[[ ${COUNT} == 40 ]] || exit 1 + +exit 0 Property changes on: trunk/tests/providers/local-coasters/201-cp.check.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-coasters/201-cp.clean.sh =================================================================== --- trunk/tests/providers/local-coasters/201-cp.clean.sh (rev 0) +++ trunk/tests/providers/local-coasters/201-cp.clean.sh 2011-05-23 14:40:27 UTC (rev 4503) @@ -0,0 +1,7 @@ +#!/bin/sh + +set -x + +rm -rv 201-output-[12]-*.txt || exit 1 + +exit 0 Property changes on: trunk/tests/providers/local-coasters/201-cp.clean.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-coasters/201-cp.setup.sh =================================================================== --- trunk/tests/providers/local-coasters/201-cp.setup.sh (rev 0) +++ trunk/tests/providers/local-coasters/201-cp.setup.sh 2011-05-23 14:40:27 UTC (rev 4503) @@ -0,0 +1,12 @@ +#!/bin/sh + +set -x + +{ + uname -a + date +} > 201-input-1.txt + +cp -v 201-input-1.txt 201-input-2.txt + +exit 0 Property changes on: trunk/tests/providers/local-coasters/201-cp.setup.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-coasters/201-cp.swift =================================================================== --- trunk/tests/providers/local-coasters/201-cp.swift (rev 0) +++ trunk/tests/providers/local-coasters/201-cp.swift 2011-05-23 14:40:27 UTC (rev 4503) @@ -0,0 +1,24 @@ + +type file; + +app (file o) cp(file i) +{ + cp @i @o; +} + +file input1<"201-input-1.txt">; +file input2<"201-input-2.txt">; + +foreach i in [1:20] +{ + string s = @strcat("201-output-1-", i, ".txt"); + file output; + output = cp(input1); +} + +foreach j in [1:20] +{ + string s = @strcat("201-output-2-", j, ".txt"); + file output; + output = cp(input2); +} Property changes on: trunk/tests/providers/local-coasters/201-cp.swift ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-coasters/201-input-1.txt =================================================================== --- trunk/tests/providers/local-coasters/201-input-1.txt (rev 0) +++ trunk/tests/providers/local-coasters/201-input-1.txt 2011-05-23 14:40:27 UTC (rev 4503) @@ -0,0 +1,2 @@ +Linux wozniak-desktop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 x86_64 GNU/Linux +Tue Mar 22 14:02:02 CDT 2011 From wozniak at ci.uchicago.edu Mon May 23 09:44:47 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 09:44:47 -0500 (CDT) Subject: [Swift-commit] r4504 - trunk/tests Message-ID: <20110523144447.BD09D9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 09:44:47 -0500 (Mon, 23 May 2011) New Revision: 4504 Modified: trunk/tests/suite.sh Log: Rename out() to output_html() Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 14:40:27 UTC (rev 4503) +++ trunk/tests/suite.sh 2011-05-23 14:44:47 UTC (rev 4504) @@ -465,7 +465,7 @@ } # Create HTML output -out() { +output_html() { # echo $@ TYPE=$1 if [ "$TYPE" == "test" ]; then @@ -671,7 +671,7 @@ RESULT=$( result ) test_log - out test $SEQ "$LASTCMD" $RESULT $TEST_LOG + output_html test $SEQ "$LASTCMD" $RESULT $TEST_LOG check_bailout @@ -761,7 +761,7 @@ RESULT=$( result ) test_log LASTCMD="$@" - out test $SEQ "$LASTCMD" $RESULT $TEST_LOG + output_html test $SEQ "$LASTCMD" $RESULT $TEST_LOG check_bailout @@ -777,7 +777,7 @@ RESULT=$( result ) test_log - out test "$SYMBOL" "$LASTCMD" $RESULT + output_html test "$SYMBOL" "$LASTCMD" $RESULT check_bailout } @@ -894,7 +894,7 @@ test_exec rm -f castor*.jar *gt2ft*.jar ant.jar test_exec cd $TOPDIR test_exec tar -pczf $RUNDIR/swift-$DATE.tar.gz $SWIFT_HOME - out package "swift-$DATE.tar.gz" + output_html package "swift-$DATE.tar.gz" } # Generate the sites.sed file From wozniak at ci.uchicago.edu Mon May 23 09:49:21 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 09:49:21 -0500 (CDT) Subject: [Swift-commit] r4505 - trunk/tests/providers/local-coasters Message-ID: <20110523144921.EC9A59CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 09:49:21 -0500 (Mon, 23 May 2011) New Revision: 4505 Removed: trunk/tests/providers/local-coasters/201-input-1.txt Log: This file is actually created by the setup.sh script Deleted: trunk/tests/providers/local-coasters/201-input-1.txt =================================================================== --- trunk/tests/providers/local-coasters/201-input-1.txt 2011-05-23 14:44:47 UTC (rev 4504) +++ trunk/tests/providers/local-coasters/201-input-1.txt 2011-05-23 14:49:21 UTC (rev 4505) @@ -1,2 +0,0 @@ -Linux wozniak-desktop 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 x86_64 GNU/Linux -Tue Mar 22 14:02:02 CDT 2011 From wozniak at ci.uchicago.edu Mon May 23 09:55:03 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 09:55:03 -0500 (CDT) Subject: [Swift-commit] r4506 - trunk/tests Message-ID: <20110523145503.4F1B99CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 09:55:03 -0500 (Mon, 23 May 2011) New Revision: 4506 Modified: trunk/tests/suite.sh Log: Output cleanup Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 14:49:21 UTC (rev 4505) +++ trunk/tests/suite.sh 2011-05-23 14:55:03 UTC (rev 4506) @@ -579,7 +579,7 @@ if [ "$FILE" == "" ]; then BANNER_OUTPUT=$LOG else - BANNER_OUTPUT=$2 + BANNER_OUTPUT=$FILE fi { echo "" @@ -652,9 +652,9 @@ # Execute as part of test set # Equivalent to monitored_exec() (but w/o monitoring) test_exec() { - banner "$TEST (part $SEQ)" - echo "Executing $TEST (part $SEQ)" - pwd + # banner "$TEST (part $SEQ)" + # echo "Executing $TEST (part $SEQ)" + printf "\nExecuting: $@\n" >>$LOG rm -f $OUTPUT @@ -735,9 +735,6 @@ TIMEOUT=$1 shift - banner "$TEST (part $SEQ)" - echo "Executing $TEST (part $SEQ)" - START=$( date +%s ) process_exec "$@" & @@ -820,6 +817,7 @@ if [ -x $GROUP/$CLEANSCRIPT ]; then script_exec $GROUP/$CLEANSCRIPT "C" fi + echo } # Execute shell test case w/ setup, check, clean @@ -992,6 +990,8 @@ (( SKIP_COUNTER++ < SKIP_TESTS )) && continue TESTNAME=$( basename $TEST ) + + echo -e "\nTest case: $TESTNAME" cp -v $GROUP/$TESTNAME . TESTLINK=$TESTNAME From wozniak at ci.uchicago.edu Mon May 23 10:01:56 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 10:01:56 -0500 (CDT) Subject: [Swift-commit] r4507 - in trunk/tests: . html Message-ID: <20110523150156.AFF2F9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 10:01:56 -0500 (Mon, 23 May 2011) New Revision: 4507 Modified: trunk/tests/html/header.html trunk/tests/suite.sh Log: Change phrasing: "part" to "group" Modified: trunk/tests/html/header.html =================================================================== --- trunk/tests/html/header.html 2011-05-23 14:55:03 UTC (rev 4506) +++ trunk/tests/html/header.html 2011-05-23 15:01:56 UTC (rev 4507) @@ -10,9 +10,9 @@ td.failure {background: #ff6000; text-align: center;} tr.testline {background: #e0e0e0} - tr.part {background: #c0c0c0; - text-align: center; - font-size: large;} + tr.group {background: #c0c0c0; + text-align: center; + font-size: large;} Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 14:55:03 UTC (rev 4506) +++ trunk/tests/suite.sh 2011-05-23 15:01:56 UTC (rev 4507) @@ -502,14 +502,14 @@ html_table border 0 cellpadding 1 } -start_part() { - PART=$1 +start_group() { + G=$1 echo - echo $PART + echo $G echo - html_tr part + html_tr group html_th 3 - html "$PART" + html "$G" html_~th html_~tr } @@ -649,11 +649,9 @@ return $EXITCODE } -# Execute as part of test set +# Execute as part of test case # Equivalent to monitored_exec() (but w/o monitoring) test_exec() { - # banner "$TEST (part $SEQ)" - # echo "Executing $TEST (part $SEQ)" printf "\nExecuting: $@\n" >>$LOG @@ -870,8 +868,8 @@ SEQSAVE=$SEQ SEQ=$1 shift - banner "$TEST (part $SEQ)" - echo "Executing $TEST (part $SEQ)" + banner "$TEST (group $SEQ)" + echo "Executing $TEST (group $SEQ)" aexec "$@" ptest SEQ=$SEQSAVE @@ -1059,7 +1057,7 @@ start_test_results cd $TOPDIR -start_part "Prolog: Build" +start_group "Build" TESTLINK= EXITONFAILURE=true @@ -1123,7 +1121,7 @@ echo "GROUP: $GROUP" [ -d $GROUP ] || crash "Could not find GROUP: $GROUP" TITLE=$( group_title ) - start_part "Part $GROUPCOUNT: $TITLE" + start_group "Group $GROUPCOUNT: $TITLE" test_group (( GROUPCOUNT++ )) (( $TESTCOUNT >= $NUMBER_OF_TESTS )) && break @@ -1135,7 +1133,7 @@ exit 0 fi -TESTPART="Appendix G: Grid Tests" +TEST="Appendix G: Grid Tests" for TEST in `ls $TESTDIR/*.dtm $TESTDIR/*.swift`; do BN=`basename $TEST` From wozniak at ci.uchicago.edu Mon May 23 10:03:56 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 10:03:56 -0500 (CDT) Subject: [Swift-commit] r4508 - trunk/tests Message-ID: <20110523150356.15B5E9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 10:03:55 -0500 (Mon, 23 May 2011) New Revision: 4508 Modified: trunk/tests/suite.sh Log: Drop grid tests - these should now all be provider tests Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 15:01:56 UTC (rev 4507) +++ trunk/tests/suite.sh 2011-05-23 15:03:55 UTC (rev 4508) @@ -160,7 +160,6 @@ echo "usage:" printf "\t -a Do not run ant dist \n" printf "\t -c Do not remove dist (clean) \n" - printf "\t -g Do not run grid tests \n" printf "\t -h This message \n" printf "\t -k Skip first N tests \n" printf "\t -n Run N tests and quit \n" @@ -180,7 +179,6 @@ SKIP_TESTS=0 NUMBER_OF_TESTS=1000000 # Run all tests by default BUILD_PACKAGE=1 -GRID_TESTS=1 SKIP_CHECKOUT=0 ALWAYS_EXITONFAILURE=0 VERBOSE=0 @@ -195,9 +193,6 @@ -c) CLEAN=0 shift;; - -g) - GRID_TESTS=0 - shift;; -h) printhelp exit 0;; @@ -220,7 +215,6 @@ # "Tree mode" RUN_ANT=0 CLEAN=0 - GRID_TESTS=0 BUILD_PACKAGE=0 SKIP_CHECKOUT=1 shift;; @@ -1128,29 +1122,6 @@ (( $SHUTDOWN )) && break done -if [ $GRID_TESTS == "0" ]; then - footer - exit 0 -fi - -TEST="Appendix G: Grid Tests" - -for TEST in `ls $TESTDIR/*.dtm $TESTDIR/*.swift`; do - BN=`basename $TEST` - echo $BN - cp $TESTDIR/$BN . - - TESTNAME=${BN%.dtm} - TESTNAME=${TESTNAME%.swift} - TEST="$TESTNAME" - - ssexec "Compile" vdlc $BN - for ((i=0; $i<9; i=$i+1)); do - test_exec swift -sites.file ~/.vdl2/sites-grid.xml $TESTNAME.kml - done - test_exec swift -sites.file ~/.vdl2/sites-grid.xml $TESTNAME.kml -done - footer exit 0 From wozniak at ci.uchicago.edu Mon May 23 10:09:05 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 10:09:05 -0500 (CDT) Subject: [Swift-commit] r4509 - trunk/tests Message-ID: <20110523150905.EFF3E9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 10:09:05 -0500 (Mon, 23 May 2011) New Revision: 4509 Modified: trunk/tests/suite.sh Log: Improve output grouping Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 15:03:55 UTC (rev 4508) +++ trunk/tests/suite.sh 2011-05-23 15:09:05 UTC (rev 4509) @@ -619,7 +619,7 @@ PROG=$( basename $PROG ) fi - echo -e "\nExecuting: $PROG" + echo -e "Executing: $PROG" echo -e "\nExecuting: $@\n" >> $LOG rm -f $OUTPUT From wozniak at ci.uchicago.edu Mon May 23 10:11:21 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 10:11:21 -0500 (CDT) Subject: [Swift-commit] r4510 - trunk/tests Message-ID: <20110523151121.4B1AF9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 10:11:21 -0500 (Mon, 23 May 2011) New Revision: 4510 Modified: trunk/tests/suite.sh Log: Clean out some commented code Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 15:09:05 UTC (rev 4509) +++ trunk/tests/suite.sh 2011-05-23 15:11:21 UTC (rev 4510) @@ -460,7 +460,7 @@ # Create HTML output output_html() { - # echo $@ + TYPE=$1 if [ "$TYPE" == "test" ]; then @@ -470,13 +470,11 @@ # WIDTH=$( width "$LABEL" ) if [ "$RESULT" == "Passed" ]; then - # html "" html_td class "success" width 25 title "$CMD" html_a_href $TEST_LOG "$LABEL" else echo "FAILED" cat $RUNDIR/$TEST_LOG < /dev/null - # html "" html_td class "failure" width 25 title "$CMD" html_a_href $TEST_LOG $LABEL fi From wozniak at ci.uchicago.edu Mon May 23 11:55:53 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 11:55:53 -0500 (CDT) Subject: [Swift-commit] r4511 - trunk/tests/providers/local-coasters Message-ID: <20110523165553.94C6C9CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 11:55:53 -0500 (Mon, 23 May 2011) New Revision: 4511 Modified: trunk/tests/providers/local-coasters/201-cp.check.sh Log: Fix check script Modified: trunk/tests/providers/local-coasters/201-cp.check.sh =================================================================== --- trunk/tests/providers/local-coasters/201-cp.check.sh 2011-05-23 15:11:21 UTC (rev 4510) +++ trunk/tests/providers/local-coasters/201-cp.check.sh 2011-05-23 16:55:53 UTC (rev 4511) @@ -2,8 +2,8 @@ set -x -COUNT=$( ls 201-output* | grep -c ) +COUNT=$( ls 201-output* | wc -l ) -[[ ${COUNT} == 40 ]] || exit 1 +[[ $COUNT == 40 ]] || exit 1 exit 0 From wozniak at ci.uchicago.edu Mon May 23 11:58:32 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 11:58:32 -0500 (CDT) Subject: [Swift-commit] r4512 - trunk/tests Message-ID: <20110523165832.D1FF89CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 11:58:32 -0500 (Mon, 23 May 2011) New Revision: 4512 Modified: trunk/tests/suite.sh Log: Bug fix in exit code handling Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-23 16:55:53 UTC (rev 4511) +++ trunk/tests/suite.sh 2011-05-23 16:58:32 UTC (rev 4512) @@ -625,7 +625,7 @@ "$@" > $OUTPUT 2>&1 & PROCESS_INTERNAL_PID=$! trap "process_trap $PROCESS_INTERNAL_PID" SIGTERM - wait + wait $PROCESS_INTERNAL_PID EXITCODE=$? if [ "$EXITCODE" == "127" ]; then From wozniak at ci.uchicago.edu Mon May 23 12:03:09 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 12:03:09 -0500 (CDT) Subject: [Swift-commit] r4513 - trunk/tests/providers/local-pbs-coasters Message-ID: <20110523170309.DF1419CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 12:03:09 -0500 (Mon, 23 May 2011) New Revision: 4513 Added: trunk/tests/providers/local-pbs-coasters/crow/ Log: Adding From wozniak at ci.uchicago.edu Mon May 23 12:05:23 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 12:05:23 -0500 (CDT) Subject: [Swift-commit] r4514 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523170523.331609CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 12:05:23 -0500 (Mon, 23 May 2011) New Revision: 4514 Added: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh trunk/tests/providers/local-pbs-coasters/crow/001-catsn.setup.sh trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml trunk/tests/providers/local-pbs-coasters/crow/tc.template.data Log: Copy beagle tests into crow Copied: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/001-catsn.check.sh) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh 2011-05-23 17:05:23 UTC (rev 4514) @@ -0,0 +1,9 @@ +#!/bin/bash + +# Pseudo-code for now + +# for f in *.out.expected +# do +# assert *.out exists +# assert *.out == data.txt +# done Copied: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.setup.sh (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/001-catsn.setup.sh) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.setup.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.setup.sh 2011-05-23 17:05:23 UTC (rev 4514) @@ -0,0 +1,3 @@ +#!/bin/bash + +cp -v $GROUP/data.txt . || exit 1 Copied: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/001-catsn.swift) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift 2011-05-23 17:05:23 UTC (rev 4514) @@ -0,0 +1,15 @@ +type file; + +app (file o) cat (file i) +{ + cat @i stdout=@o; +} + +// string t = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"; +// string char[] = @strsplit(t, ""); + +file out[]; +foreach j in [1:@toint(@arg("n","10"))] { + file data<"data.txt">; + out[j] = cat(data); +} Copied: trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/sites.template.xml) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml 2011-05-23 17:05:23 UTC (rev 4514) @@ -0,0 +1,33 @@ + + + + + + + + + + 1 + 7200 + + + pbs.aprun;pbs.mpp;depth=24 + + 24 + 1 + 1 + 1 + batch + DEBUG + {wdir} + 5.99 + 10000 + _PROJECT_ + _QUEUE_ + {wdir} + + + + Copied: trunk/tests/providers/local-pbs-coasters/crow/tc.template.data (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/tc.template.data) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/tc.template.data (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/tc.template.data 2011-05-23 17:05:23 UTC (rev 4514) @@ -0,0 +1,7 @@ +beagle-pbs echo /bin/echo INSTALLED INTEL32::LINUX +beagle-pbs cat /bin/cat INSTALLED INTEL32::LINUX +beagle-pbs ls /bin/ls INSTALLED INTEL32::LINUX +beagle-pbs grep /bin/grep INSTALLED INTEL32::LINUX +beagle-pbs sort /bin/sort INSTALLED INTEL32::LINUX +beagle-pbs paste /bin/paste INSTALLED INTEL32::LINUX +beagle-pbs wc /usr/bin/wc INSTALLED INTEL32::LINUX From wozniak at ci.uchicago.edu Mon May 23 12:05:49 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 12:05:49 -0500 (CDT) Subject: [Swift-commit] r4515 - trunk/tests/providers/local-pbs-coasters/beagle Message-ID: <20110523170549.0C64C9CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 12:05:48 -0500 (Mon, 23 May 2011) New Revision: 4515 Modified: trunk/tests/providers/local-pbs-coasters/beagle/sites.template.xml Log: Remove reservation from site Modified: trunk/tests/providers/local-pbs-coasters/beagle/sites.template.xml =================================================================== --- trunk/tests/providers/local-pbs-coasters/beagle/sites.template.xml 2011-05-23 17:05:23 UTC (rev 4514) +++ trunk/tests/providers/local-pbs-coasters/beagle/sites.template.xml 2011-05-23 17:05:48 UTC (rev 4515) @@ -11,13 +11,15 @@ 7200 - pbs.aprun;pbs.mpp;depth=24;pbs.resources=advres=modFTDock.47 + pbs.aprun;pbs.mpp;depth=24 24 1 1 1 batch + DEBUG + {wdir} 5.99 10000 _PROJECT_ @@ -26,4 +28,6 @@ - + From wozniak at ci.uchicago.edu Mon May 23 12:07:39 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 12:07:39 -0500 (CDT) Subject: [Swift-commit] r4516 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523170739.873919CC94@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 12:07:39 -0500 (Mon, 23 May 2011) New Revision: 4516 Added: trunk/tests/providers/local-pbs-coasters/crow/data.txt Log: Copy in data file for test Copied: trunk/tests/providers/local-pbs-coasters/crow/data.txt (from rev 4503, trunk/tests/providers/local-pbs-coasters/beagle/data.txt) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/data.txt (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/data.txt 2011-05-23 17:07:39 UTC (rev 4516) @@ -0,0 +1 @@ +HELLO From wozniak at ci.uchicago.edu Mon May 23 14:44:29 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 14:44:29 -0500 (CDT) Subject: [Swift-commit] r4517 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523194429.E082B9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 14:44:29 -0500 (Mon, 23 May 2011) New Revision: 4517 Added: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.timeout Log: Long timeout on queued system Added: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.timeout =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.timeout (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.timeout 2011-05-23 19:44:29 UTC (rev 4517) @@ -0,0 +1 @@ +1000 From wozniak at ci.uchicago.edu Mon May 23 14:44:40 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 14:44:40 -0500 (CDT) Subject: [Swift-commit] r4518 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523194440.DBEE49CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 14:44:40 -0500 (Mon, 23 May 2011) New Revision: 4518 Added: trunk/tests/providers/local-pbs-coasters/crow/title.txt Log: Adding Added: trunk/tests/providers/local-pbs-coasters/crow/title.txt =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/title.txt (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/title.txt 2011-05-23 19:44:40 UTC (rev 4518) @@ -0,0 +1 @@ +Local PBS Coasters: Crow From wozniak at ci.uchicago.edu Mon May 23 14:45:54 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 14:45:54 -0500 (CDT) Subject: [Swift-commit] r4519 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523194554.890B39CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 14:45:54 -0500 (Mon, 23 May 2011) New Revision: 4519 Modified: trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml trunk/tests/providers/local-pbs-coasters/crow/tc.template.data Log: Working sites and tc for crow Modified: trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml 2011-05-23 19:44:40 UTC (rev 4518) +++ trunk/tests/providers/local-pbs-coasters/crow/sites.template.xml 2011-05-23 19:45:54 UTC (rev 4519) @@ -1,29 +1,27 @@ - + + - + 1 7200 - pbs.aprun;pbs.mpp;depth=24 + pbs.aprun;pbs.mpp;depth=6 - 24 + 6 1 1 1 - batch DEBUG {wdir} 5.99 10000 - _PROJECT_ - _QUEUE_ {wdir} Modified: trunk/tests/providers/local-pbs-coasters/crow/tc.template.data =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/tc.template.data 2011-05-23 19:44:40 UTC (rev 4518) +++ trunk/tests/providers/local-pbs-coasters/crow/tc.template.data 2011-05-23 19:45:54 UTC (rev 4519) @@ -1,7 +1,7 @@ -beagle-pbs echo /bin/echo INSTALLED INTEL32::LINUX -beagle-pbs cat /bin/cat INSTALLED INTEL32::LINUX -beagle-pbs ls /bin/ls INSTALLED INTEL32::LINUX -beagle-pbs grep /bin/grep INSTALLED INTEL32::LINUX -beagle-pbs sort /bin/sort INSTALLED INTEL32::LINUX -beagle-pbs paste /bin/paste INSTALLED INTEL32::LINUX -beagle-pbs wc /usr/bin/wc INSTALLED INTEL32::LINUX +crow echo /bin/echo INSTALLED INTEL32::LINUX +crow cat /bin/cat INSTALLED INTEL32::LINUX +crow ls /bin/ls INSTALLED INTEL32::LINUX +crow grep /bin/grep INSTALLED INTEL32::LINUX +crow sort /bin/sort INSTALLED INTEL32::LINUX +crow paste /bin/paste INSTALLED INTEL32::LINUX +crow wc /usr/bin/wc INSTALLED INTEL32::LINUX From wozniak at ci.uchicago.edu Mon May 23 14:49:32 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 14:49:32 -0500 (CDT) Subject: [Swift-commit] r4520 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523194932.97F839CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 14:49:32 -0500 (Mon, 23 May 2011) New Revision: 4520 Added: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.clean.sh Modified: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift Log: Fix up crow test scripts Modified: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh 2011-05-23 19:45:54 UTC (rev 4519) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.check.sh 2011-05-23 19:49:32 UTC (rev 4520) @@ -1,9 +1,8 @@ #!/bin/bash -# Pseudo-code for now +set -x -# for f in *.out.expected -# do -# assert *.out exists -# assert *.out == data.txt -# done +COUNT=$( ls catsn.*.out | wc -l ) +[[ $COUNT == 10 ]] || exit 1 + +exit 0 Added: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.clean.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.clean.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.clean.sh 2011-05-23 19:49:32 UTC (rev 4520) @@ -0,0 +1,7 @@ +#!/bin/bash + +set -x + +rm -v catsn.*.out || exit 1 + +exit 0 Property changes on: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.clean.sh ___________________________________________________________________ Added: svn:executable + * Modified: trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift 2011-05-23 19:45:54 UTC (rev 4519) +++ trunk/tests/providers/local-pbs-coasters/crow/001-catsn.swift 2011-05-23 19:49:32 UTC (rev 4520) @@ -5,9 +5,6 @@ cat @i stdout=@o; } -// string t = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"; -// string char[] = @strsplit(t, ""); - file out[]; foreach j in [1:@toint(@arg("n","10"))] { file data<"data.txt">; From wozniak at ci.uchicago.edu Mon May 23 14:50:41 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 14:50:41 -0500 (CDT) Subject: [Swift-commit] r4521 - trunk/tests/providers/local-pbs-coasters/beagle Message-ID: <20110523195041.DBDFB9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 14:50:41 -0500 (Mon, 23 May 2011) New Revision: 4521 Added: trunk/tests/providers/local-pbs-coasters/beagle/title.txt Log: Adding Added: trunk/tests/providers/local-pbs-coasters/beagle/title.txt =================================================================== --- trunk/tests/providers/local-pbs-coasters/beagle/title.txt (rev 0) +++ trunk/tests/providers/local-pbs-coasters/beagle/title.txt 2011-05-23 19:50:41 UTC (rev 4521) @@ -0,0 +1 @@ +Local PBS Coasters: Beagle From wozniak at ci.uchicago.edu Mon May 23 15:14:39 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 15:14:39 -0500 (CDT) Subject: [Swift-commit] r4522 - trunk/tests/providers/local-pbs-coasters/crow Message-ID: <20110523201439.7237C9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 15:14:39 -0500 (Mon, 23 May 2011) New Revision: 4522 Added: trunk/tests/providers/local-pbs-coasters/crow/big/ Log: Adding From wozniak at ci.uchicago.edu Mon May 23 15:43:21 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Mon, 23 May 2011 15:43:21 -0500 (CDT) Subject: [Swift-commit] r4523 - trunk/tests/providers/local-pbs-coasters/crow/big Message-ID: <20110523204321.A769C9CC9F@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-23 15:43:21 -0500 (Mon, 23 May 2011) New Revision: 4523 Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.check.sh trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.clean.sh trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.setup.sh trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.swift trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.timeout trunk/tests/providers/local-pbs-coasters/crow/big/cps.sh trunk/tests/providers/local-pbs-coasters/crow/big/data.txt trunk/tests/providers/local-pbs-coasters/crow/big/sites.template.xml trunk/tests/providers/local-pbs-coasters/crow/big/title.txt Log: Multi-node Crow test that can easily be made bigger Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.check.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.check.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.check.sh 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,9 @@ +#!/bin/sh + +set -x + +COUNT=$( ls 201-output* | wc -l ) + +[[ $COUNT == 40 ]] || exit 1 + +exit 0 Property changes on: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.check.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.clean.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.clean.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.clean.sh 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,7 @@ +#!/bin/sh + +set -x + +rm -rv 201-output-[12]-*.txt || exit 1 + +exit 0 Property changes on: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.clean.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.setup.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.setup.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.setup.sh 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,12 @@ +#!/bin/sh + +set -x + +{ + uname -a + date +} > 201-input-1.txt + +cp -v 201-input-1.txt 201-input-2.txt + +exit 0 Property changes on: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.setup.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.swift =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.swift (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.swift 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,24 @@ + +type file; + +app (file o) cps(file i, int s) +{ + cps @o @i s; +} + +file input1<"201-input-1.txt">; +file input2<"201-input-2.txt">; + +foreach i in [1:20] +{ + string s = @strcat("201-output-1-", i, ".txt"); + file output; + output = cps(input1, i); +} + +foreach j in [1:20] +{ + string s = @strcat("201-output-2-", j, ".txt"); + file output; + output = cps(input2, 10+j); +} Property changes on: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.swift ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.timeout =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.timeout (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/201-cps.timeout 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1 @@ +1000 Added: trunk/tests/providers/local-pbs-coasters/crow/big/cps.sh =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/cps.sh (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/cps.sh 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,9 @@ +#!/bin/sh + +DEST=$1 +SRC=$2 +DURATION=$3 + +sleep $DURATION +cp -v $SRC $DEST + Property changes on: trunk/tests/providers/local-pbs-coasters/crow/big/cps.sh ___________________________________________________________________ Added: svn:executable + * Copied: trunk/tests/providers/local-pbs-coasters/crow/big/data.txt (from rev 4516, trunk/tests/providers/local-pbs-coasters/crow/data.txt) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/data.txt (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/data.txt 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1 @@ +HELLO Added: trunk/tests/providers/local-pbs-coasters/crow/big/sites.template.xml =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/sites.template.xml (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/sites.template.xml 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1,29 @@ + + + + + + + + + 1 + 7200 + + + pbs.aprun;pbs.mpp;depth=6 + + 6 + 2 + 4 + 16 + DEBUG + {wdir} + 5.99 + 10000 + {wdir} + + + + Copied: trunk/tests/providers/local-pbs-coasters/crow/big/title.txt (from rev 4518, trunk/tests/providers/local-pbs-coasters/crow/title.txt) =================================================================== --- trunk/tests/providers/local-pbs-coasters/crow/big/title.txt (rev 0) +++ trunk/tests/providers/local-pbs-coasters/crow/big/title.txt 2011-05-23 20:43:21 UTC (rev 4523) @@ -0,0 +1 @@ +Local PBS Coasters: Crow big From hategan at ci.uchicago.edu Tue May 24 12:51:46 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Tue, 24 May 2011 12:51:46 -0500 (CDT) Subject: [Swift-commit] r4524 - trunk/src/org/griphyn/vdl/mapping Message-ID: <20110524175146.07AA09CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-24 12:51:45 -0500 (Tue, 24 May 2011) New Revision: 4524 Modified: trunk/src/org/griphyn/vdl/mapping/MappingParam.java Log: fix bug when passing int parameters to a mapper Modified: trunk/src/org/griphyn/vdl/mapping/MappingParam.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/MappingParam.java 2011-05-23 20:43:21 UTC (rev 4523) +++ trunk/src/org/griphyn/vdl/mapping/MappingParam.java 2011-05-24 17:51:45 UTC (rev 4524) @@ -3,6 +3,7 @@ import java.util.Map; import org.griphyn.vdl.karajan.VDL2FutureException; +import org.griphyn.vdl.type.Types; /** The MappingParam class provides helper methods to deal with * parameters to mappers. The basic usage pattern is to @@ -44,7 +45,12 @@ if (value instanceof DSHandle) { DSHandle handle = (DSHandle) value; checkHandle(handle); - return handle.getValue().toString(); + if (handle.getType().equals(Types.INT)) { + return Integer.valueOf(((Number) handle.getValue()).intValue()); + } + else { + return handle.getValue().toString(); + } } else if (value == null) { if (!defSet) { From skenny at ci.uchicago.edu Wed May 25 00:00:30 2011 From: skenny at ci.uchicago.edu (skenny at ci.uchicago.edu) Date: Wed, 25 May 2011 00:00:30 -0500 (CDT) Subject: [Swift-commit] r4525 - trunk/src/org/globus/swift/catalog/transformation Message-ID: <20110525050030.29F949CC6B@svn.ci.uchicago.edu> Author: skenny Date: 2011-05-25 00:00:26 -0500 (Wed, 25 May 2011) New Revision: 4525 Modified: trunk/src/org/globus/swift/catalog/transformation/File.java Log: cleaner warning for bad line in tc.data file Modified: trunk/src/org/globus/swift/catalog/transformation/File.java =================================================================== --- trunk/src/org/globus/swift/catalog/transformation/File.java 2011-05-24 17:51:45 UTC (rev 4524) +++ trunk/src/org/globus/swift/catalog/transformation/File.java 2011-05-25 05:00:26 UTC (rev 4525) @@ -1101,10 +1101,8 @@ i ] ) ); } catch ( ProfileParserException ppe ) { logger.warn( - "Parsing profiles on line " + - linecount + " " + ppe.getMessage() + - "at position " + - ppe.getPosition(), ppe); + "Warning: malformed tc.data file on line " + + linecount); } } From davidk at ci.uchicago.edu Wed May 25 13:20:23 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Wed, 25 May 2011 13:20:23 -0500 (CDT) Subject: [Swift-commit] r4526 - www Message-ID: <20110525182023.241179CC84@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-25 13:20:22 -0500 (Wed, 25 May 2011) New Revision: 4526 Modified: www/push_to.sh Log: Updated push_to script to explicitly list files to copy (so it doesn't copy scratch files, etc) Modified: www/push_to.sh =================================================================== --- www/push_to.sh 2011-05-25 05:00:26 UTC (rev 4525) +++ www/push_to.sh 2011-05-25 18:20:22 UTC (rev 4526) @@ -11,25 +11,100 @@ # Make sure we are calling this script in the same directory as the script is located pushd $(dirname $(readlink -f $0)) > /dev/null 2>&1 +# Long list of files to explicitly include follows +FILES=" +inc/footer.php +inc/home_sidebar.php +inc/papers_sidebar.php +inc/docs_sidebar.php +inc/about_sidebar.php +inc/downloads_sidebar.php +inc/support_sidebar.php +inc/header.php +inc/links_sidebar.php +inc/nav.php +inc/apps_sidebar.php +inc/side_content.php +shBrushVDL2.js +bric-flow-thm.jpg +about/index.php +links/index.php +template_info/template.php +docs/index.php +updatenodocs.sh +dhtml.js +index.html +style.css +papers/jogc_03.pdf +papers/HealthGrid-2007-VDL2Bric.submitted-revised.pdf +papers/challenge-editorial.pdf +papers/OpportunisticAlgoritmForSchedulingWokflows.pdf +papers/Chimera2002.pdf +papers/clag_paper.pdf +papers/Swift-SWF07.pdf +papers/GridResourcesForGADU.pdf +papers/sigmod-swf-vdl.pdf +papers/BioGrid2005.pdf +papers/ModelAndArchForDataCollab2003.pdf +papers/SwiftParallelScripting.pdf +papers/p57-zhao.pdf +papers/Kickstarting2006.pdf +papers/VirtualDataInCMS.pdf +papers/VirtualDataProvenance.pdf +papers/cpe2000.pdf +papers/SwiftLanguageForDistributedParallelScripting.pdf +papers/index.php +papers/SwiftForSocialSciences-2007.pdf +papers/AutomatingClimateScience.pdf +papers/XDTM_egc05.pdf +papers/p37-special-sw-section-6.pdf +papers/SDSS-SC02.pdf +papers/egc05.pdf +papers/Falkon_SC07_v24.pdf +papers/vonLaszewski-workflow-book.pdf +papers/VDS-CMS.pdf +css/style.css +css/style1col.css +css/style2.css +images/workflow.jpg +images/graphics/h_backgrnd.gif +images/graphics/swift_sketch.gif +images/graphics/banner2.gif +images/graphics/h_ckgrnd.gif +images/graphics/h_backgrnd2.gif +images/graphics/banner.gif +images/workflow.gif +shCoreu.js +apps/style2.css +apps/index.php +README.txt +bric-flow.jpg +sitemap.xml +downloads/release-notes-0.6.txt +downloads/release-notes-0.9.txt +downloads/release-notes-0.5.txt +downloads/release-notes-0.7.txt +downloads/index.php +downloads/release-notes-0.8.txt +main/index.php +push_to.sh +support/index.php +update.sh +" + # Make sure destination directory exists if [ ! -d "$DESTINATION" ]; then mkdir $DESTINATION > /dev/null 2>&1 || exit 1 fi -# Copy directory structure -DIRS_TO_COPY=`find . -mindepth 1 -type d|grep -vi svn|sed s/^.//` -for dir in $DIRS_TO_COPY -do - mkdir $DESTINATION"$dir" > /dev/null 2>&1 - chmod a+r $DESTINATION"$dir" || exit 1 -done - # Copy files to destination -FILES_TO_COPY=`find . -mindepth 1 -type f |grep -vi svn|sed s/^.//` -for file in $FILES_TO_COPY +for FILE in $FILES do - cp -v .$file "$DESTINATION"`dirname $file` || exit 1 - chmod a+r "$DESTINATION"`dirname $file`/`basename $file` + destination_dir=`dirname $FILE` + mkdir -p $DESTINATION/$destination_dir + cp $FILE $DESTINATION/$destination_dir/ + chmod a+r $DESTINATION/$destination_dir/$FILE > /dev/null 2>&1 done popd > /dev/null 2>&1 + From hategan at ci.uchicago.edu Wed May 25 14:55:12 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Wed, 25 May 2011 14:55:12 -0500 (CDT) Subject: [Swift-commit] r4527 - in trunk/src/org/griphyn/vdl/mapping: . file Message-ID: <20110525195512.D5F8E9CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-25 14:55:12 -0500 (Wed, 25 May 2011) New Revision: 4527 Modified: trunk/src/org/griphyn/vdl/mapping/AbstractMapper.java trunk/src/org/griphyn/vdl/mapping/Mapper.java trunk/src/org/griphyn/vdl/mapping/file/ExternalMapper.java Log: generics and logging messages to trace external mapper parameters and output Modified: trunk/src/org/griphyn/vdl/mapping/AbstractMapper.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/AbstractMapper.java 2011-05-25 18:20:22 UTC (rev 4526) +++ trunk/src/org/griphyn/vdl/mapping/AbstractMapper.java 2011-05-25 19:55:12 UTC (rev 4527) @@ -15,11 +15,11 @@ public static final Logger logger = Logger.getLogger(AbstractMapper.class); public static final MappingParam PARAM_INPUT = new MappingParam("input", Boolean.FALSE); - protected Map params; + protected Map params; public synchronized void setParam(String name, Object value) { if (params == null) { - params = new HashMap(); + params = new HashMap(); } params.put(name, value); } @@ -33,7 +33,7 @@ } } - public void setParams(Map params) { + public void setParams(Map params) { this.params = params; } Modified: trunk/src/org/griphyn/vdl/mapping/Mapper.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/Mapper.java 2011-05-25 18:20:22 UTC (rev 4526) +++ trunk/src/org/griphyn/vdl/mapping/Mapper.java 2011-05-25 19:55:12 UTC (rev 4527) @@ -20,7 +20,7 @@ entry is a Path object. The data files mapped to each Path object do not necessarily have to exist. */ - Collection existing(); + Collection existing(); /** * Returns true if data mapped by this mapper cannot @@ -38,7 +38,7 @@ */ boolean isStatic(); - void setParams(Map params); + void setParams(Map params); void setParam(String name, Object value); Modified: trunk/src/org/griphyn/vdl/mapping/file/ExternalMapper.java =================================================================== --- trunk/src/org/griphyn/vdl/mapping/file/ExternalMapper.java 2011-05-25 18:20:22 UTC (rev 4526) +++ trunk/src/org/griphyn/vdl/mapping/file/ExternalMapper.java 2011-05-25 19:55:12 UTC (rev 4527) @@ -9,7 +9,6 @@ import java.util.Collection; import java.util.HashMap; import java.util.HashSet; -import java.util.Iterator; import java.util.List; import java.util.Map; import java.util.Set; @@ -24,15 +23,16 @@ public class ExternalMapper extends AbstractMapper { public static final Logger logger = Logger.getLogger(ExternalMapper.class); - private Map map, rmap = new HashMap(); + private Map map; + private Map rmap; public static final MappingParam PARAM_EXEC = new MappingParam("exec"); public static final MappingParam PARAM_BASEDIR = new MappingParam("#basedir", null); - private static Set ignored; + private static Set ignored; static { - ignored = new HashSet(); + ignored = new HashSet(); ignored.add("exec"); ignored.add("input"); ignored.add("dbgname"); @@ -44,21 +44,18 @@ private static final String[] STRING_ARRAY = new String[0]; - public void setParams(Map params) { + public void setParams(Map params) { super.setParams(params); - map = new HashMap(); - rmap = new HashMap(); + map = new HashMap(); + rmap = new HashMap(); String exec = PARAM_EXEC.getStringValue(this); String bdir = PARAM_BASEDIR.getStringValue(this); if (bdir != null && !exec.startsWith("/")) { exec = bdir + File.separator + exec; } - List cmd = new ArrayList(); + List cmd = new ArrayList(); cmd.add(exec); - Iterator i = params.entrySet().iterator(); - while (i.hasNext()) { - Map.Entry e = (Map.Entry) i.next(); - String name = e.getKey().toString(); + for (String name : params.keySet()) { if (!ignored.contains(name)) { MappingParam tp = new MappingParam(name); cmd.add('-' + name); @@ -66,8 +63,14 @@ } } try { - Process p = Runtime.getRuntime().exec((String[]) cmd.toArray(STRING_ARRAY)); - List lines = fetchOutput(p.getInputStream()); + if (logger.isDebugEnabled()) { + logger.debug("invoking external mapper for " + getParam("dbgname") + ": " + cmd); + } + Process p = Runtime.getRuntime().exec(cmd.toArray(STRING_ARRAY)); + List lines = fetchOutput(p.getInputStream()); + if (logger.isDebugEnabled()) { + logger.debug("external mapper for " + getParam("dbgname") + " output: " + lines); + } int ec = p.waitFor(); if (ec != 0) { throw new RuntimeException("External executable failed. Exit code: " + ec + "\n\t" @@ -83,19 +86,18 @@ } } - private String join(List l) { + private String join(List l) { StringBuffer sb = new StringBuffer(); - Iterator i = l.iterator(); - while (i.hasNext()) { - sb.append(i.next()); + for (Object o : l) { + sb.append(o); sb.append('\n'); sb.append('\t'); } return sb.toString(); } - private List fetchOutput(InputStream is) throws IOException { - ArrayList lines = new ArrayList(); + private List fetchOutput(InputStream is) throws IOException { + ArrayList lines = new ArrayList(); BufferedReader br = new BufferedReader(new InputStreamReader(is)); String line = br.readLine(); while (line != null) { @@ -105,10 +107,8 @@ return lines; } - private void processLines(List lines) { - Iterator i = lines.iterator(); - while (i.hasNext()) { - String line = (String) i.next(); + private void processLines(List lines) { + for (String line : lines) { int s = line.indexOf(' '); int t = line.indexOf('\t'); int m = Math.min(s == -1 ? t : s, t == -1 ? s : t); @@ -123,7 +123,7 @@ } } - public Collection existing() { + public Collection existing() { return map.keySet(); } @@ -131,11 +131,11 @@ if (name == null || name.equals("")) { return null; } - return (Path) rmap.get(name); + return rmap.get(name); } public PhysicalFormat map(Path path) { - return (AbsFile) map.get(path); + return map.get(path); } public boolean isStatic() { From davidk at ci.uchicago.edu Wed May 25 14:57:51 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Wed, 25 May 2011 14:57:51 -0500 (CDT) Subject: [Swift-commit] r4528 - in trunk: . bin etc etc/sites etc/sites/OLD Message-ID: <20110525195751.462C49CC94@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-25 14:57:51 -0500 (Wed, 25 May 2011) New Revision: 4528 Added: trunk/bin/start-coaster-service trunk/bin/stop-coaster-service trunk/etc/coaster-service.conf trunk/etc/sites/OLD/ trunk/etc/sites/OLD/cnari-abe/ trunk/etc/sites/OLD/cnari-queenbee/ trunk/etc/sites/OLD/cnari-ranger/ trunk/etc/sites/OLD/local-pbs-coasters/ trunk/etc/sites/OLD/pads-local-pbs-coasters/ trunk/etc/sites/OLD/pads-remote-pbs-coasters-ssh/ trunk/etc/sites/OLD/teraport-local-pbs-coasters/ trunk/etc/sites/OLD/teraport-remote-pbs-coasters-ssh/ trunk/etc/sites/coaster-service.conf trunk/etc/sites/persistent-coasters Removed: trunk/etc/sites/cnari-abe/ trunk/etc/sites/cnari-queenbee/ trunk/etc/sites/cnari-ranger/ trunk/etc/sites/local-pbs-coasters/ trunk/etc/sites/pads-local-pbs-coasters/ trunk/etc/sites/pads-remote-pbs-coasters-ssh/ trunk/etc/sites/teraport-local-pbs-coasters/ trunk/etc/sites/teraport-remote-pbs-coasters-ssh/ Modified: trunk/bin/gensites trunk/build.xml Log: Initial release of start-coaster-service and stop-coaster-service scripts The start-coaster configuration script is etc/coaster-service.conf Cleaned up the sites directory. The older swiftconfig site templates are moved into the OLD directory (I don't think anyone is actually using these - probably safe to delete in the future) There should now only gensite templates in sites/ Modified: trunk/bin/gensites =================================================================== --- trunk/bin/gensites 2011-05-25 19:55:12 UTC (rev 4527) +++ trunk/bin/gensites 2011-05-25 19:57:51 UTC (rev 4528) @@ -172,6 +172,9 @@ "#site $TEMPLATE slots="*|'#site slots='*) SLOTS=`get_value $line` ;; + "#site $TEMPLATE execution_url="*|'#site slots='*) + EXECUTION_URL=`get_value $line` + ;; esac done < $PROPERTIES_FILE @@ -201,6 +204,7 @@ echo "s/_N_MAX_/${N_MAX}/" echo "s/_SLOTS_/${SLOTS}/" echo "s/_MAXTIME_/${MAXTIME}/" + echo "s/_EXECUTION_URL_/${EXECUTION_URL}/" echo "s at _SERVICE_COASTERS_@${SERVICE_COASTERS:-NO_URL_GIVEN}@" echo "s at _SERVICE_PORT_@${SERVICE_PORT:-NO_PORT_GIVEN}@" } > $SEDFILE Added: trunk/bin/start-coaster-service =================================================================== --- trunk/bin/start-coaster-service (rev 0) +++ trunk/bin/start-coaster-service 2011-05-25 19:57:51 UTC (rev 4528) @@ -0,0 +1,159 @@ +#!/bin/bash + +# crash: Report a problem and exit +crash() +{ + MSG=$1 + echo ${MSG} >&2 + exit 1 +} + +# Start SSH workers +start-workers-ssh() +{ + PORT=$1 + EXECUTION_URL=http://$IPADDR:$PORT + if [ -z "$PORT" ]; then + crash "start-workers-ssh: Port number not specified, giving up" + fi + for MACHINE in $WORKER_HOSTS + do + scp $SWIFT_BIN/$WORKER $MACHINE:$WORKER_WORK > /dev/null 2>&1 + echo Starting worker on $MACHINE + ssh $MACHINE $WORKER_WORK/$WORKER $EXECUTION_URL $MACHINE $LOG_DIR & + echo $! >> $PID_FILE + done + return 0 +} + +# Start local workers +start-workers-local() +{ + echo foo +} + +# Start cobalt workers +start-workers-cobalt() +{ + echo foo +} + +PID_FILE=".coaster-service-pids" +RUN_DIR=`pwd` +pushd $(dirname $(readlink -f $0)) > /dev/null 2>&1 + +# Import settings +CONFIG_FILE="../etc/coaster-service.conf" +if [ -f "$CONFIG_FILE" ]; then + source "$CONFIG_FILE" +else + crash "Cannot find coaster-service.conf!" +fi + +# Determine information needed about this machine +if [ -z "$IPADDR" ]; then + if [ -x "/sbin/ifconfig" ]; then + IPADDR=$( /sbin/ifconfig | grep inet | head -1 | cut -d ':' -f 2 | awk '{print $1}' ) + else + crash "Unable to determine IP address of system. Please add to coaster-service.conf" + fi +fi + +# Find swift +if [ ! -x "$SWIFT" ]; then + SWIFT=`which swift` + if [ ! -x "$SWIFT" ]; then + crash "Unable to find swift! Please either add to your $PATH or specify the path in coaster-service.conf" + fi +fi + +SWIFT_BIN=`dirname $SWIFT` +WORKER=worker.pl + +# Verify worker script is there +if [ ! -x "$SWIFT_BIN/$WORKER" ]; then + crash "Error: Unable to find worker at $SWIFT_BIN/$WORKER!" +fi + +# Try to create $LOG_DIR if needed, relative to $RUN_DIR +if [ ! -d "$RUN_DIR/$LOG_DIR" ]; then + mkdir -p "$RUN_DIR/$LOG_DIR" > /dev/null 2>&1 + if [ ! -d "$RUN_DIR/$LOG_DIR" ]; then + crash "Unable to make directory $RUN_DIR/$LOG_DIR!" + fi +fi + +# Set paths to log files +SWIFT_LOG="$RUN_DIR/$LOG_DIR"/swift.out +COASTER_LOG="$RUN_DIR/$LOG_DIR"/coaster.log + +# Verify we can find coaster service +if [ ! -x "$SWIFT_BIN/coaster-service" ]; then + crash "Unable to find $SWIFT_BIN/coaster-service!" +fi + +# Create files for storing port info, if needed +if [ -z "$LOCAL_PORT" ]; then + LOCAL_PORT_FILE=`mktemp` +fi + +if [ -z "$SERVICE_PORT" ]; then + SERVICE_PORT_FILE=`mktemp` +fi + +# Check values in configuration file to determine how we should start coaster-service +echo Starting coaster-service +if [ -z "$SERVICE_PORT" ] && [ -z "$LOCAL_PORT" ]; then + $SWIFT_BIN/coaster-service -nosec -portfile $SERVICE_PORT_FILE -localportfile $LOCAL_PORT_FILE -passive > $COASTER_LOG 2>&1 & +elif [ -n "$SERVICE_PORT" ] && [ -z "$LOCAL_PORT" ]; then + $SWIFT_BIN/coaster-service -nosec -port $SERVICE_PORT -localportfile $LOCAL_PORT_FILE -passive > $COASTER_LOG 2>&1 & +elif [ -z "$SERVICE_PORT" ] && [ -n "$LOCAL_PORT" ]; then + $SWIFT_BIN/coaster-service -nosec -portfile $SERVICE_PORT_FILE --localport $LOCAL_PORT -passive > $COASTER_LOG 2>&1 & +elif [ -n "$SERVICE_PORT" ] && [ -n "$LOCAL_PORT" ]; then + $SWIFT_BIN/coaster-service -nosec -port $SERVICE_PORT -localport $LOCAL_PORT -passive > $COASTER_LOG 2>&1 & +else + crash "Unknown SERVICE_PORT type specified!" +fi + +echo $! > $PID_FILE +sleep 5 + +# Determine SERVICE_PORT +if [ -z "$SERVICE_PORT" ]; then + if [ ! -f "$SERVICE_PORT_FILE" ]; then + crash "Unable to determine SERVICE_PORT!" + fi + SERVICE_PORT=`cat $SERVICE_PORT_FILE` + rm $SERVICE_PORT_FILE +fi + +# Determine LOCAL_PORT +if [ -z "$LOCAL_PORT" ]; then + if [ ! -f "$LOCAL_PORT_FILE" ]; then + crash "Unable to determine LOCAL_PORT!" + fi + LOCAL_PORT=`cat $LOCAL_PORT_FILE` + rm $LOCAL_PORT_FILE +fi + +echo Service port: $SERVICE_PORT +echo Local port: $LOCAL_PORT + +# Start workers +case $WORKER_MODE in + ssh) + start-workers-ssh $LOCAL_PORT + ;; + local) + start-workers-local $LOCAL_PORT + ;; + cobalt) + start-workers-cobalt $LOCAL_PORT + ;; +esac + +# Generate sites.xml +export EXECUTION_URL="http:\/\/$IPADDR:$SERVICE_PORT" +echo Generating sites.xml.. +gensites persistent-coasters -p $CONFIG_FILE > $RUN_DIR/sites.xml + Property changes on: trunk/bin/start-coaster-service ___________________________________________________________________ Added: svn:executable + * Added: trunk/bin/stop-coaster-service =================================================================== --- trunk/bin/stop-coaster-service (rev 0) +++ trunk/bin/stop-coaster-service 2011-05-25 19:57:51 UTC (rev 4528) @@ -0,0 +1,23 @@ +#!/bin/bash + +pushd $(dirname $(readlink -f $0)) > /dev/null 2>&1 + +PID_FILE=".coaster-service-pids" + +echo Ending coaster processes.. +if [ -f "$PID_FILE" ]; then + for pid in `cat $PID_FILE` + do + #echo "$pid" + for i in `ps -ef| awk '$3 == '$pid' { print $2 }'` + do + #echo "$i" + kill $i > /dev/null 2>&1 + done + kill $pid > /dev/null 2>&1 + done + rm $PID_FILE > /dev/null 2>&1 +fi +echo Done + +popd > /dev/null 2>&1 Property changes on: trunk/bin/stop-coaster-service ___________________________________________________________________ Added: svn:executable + * Modified: trunk/build.xml =================================================================== --- trunk/build.xml 2011-05-25 19:55:12 UTC (rev 4527) +++ trunk/build.xml 2011-05-25 19:57:51 UTC (rev 4528) @@ -88,6 +88,8 @@ + + Added: trunk/etc/coaster-service.conf =================================================================== --- trunk/etc/coaster-service.conf (rev 0) +++ trunk/etc/coaster-service.conf 2011-05-25 19:57:51 UTC (rev 4528) @@ -0,0 +1,33 @@ +# Keep all interesting settings in one place +# User should modify this to fit environment + +# Location of SWIFT. If empty, PATH is referenced +export SWIFT= + +# Where to place/launch worker.pl on the remote machine for sites.xml +export WORKER_WORK=/home/${USER}/work + +# How to launch workers: local, ssh, or cobalt +export WORKER_MODE=ssh + +# Worker logging setting passed to worker.pl for sites.xml +export WORKER_LOGGING=INFO + +# Worker host names for ssh +export WORKERS_HOSTS="host1 host2 host3" + +# Directory to keep log files, relative to working directory when launching start-coaster-service +export LOG_DIR=logs + +# Manually define ports. If not specified, ports will be automatically generated +export LOCAL_PORT= +export SERVICE_PORT= + +# start-coaster-service tries to automatically detect IP address. Specify here if auto detection is not working correctly +export IPADDR= + +# Below are various settings to give information about how to create sites.xml +export work=$HOME/work +export queue=prod-devel +export maxtime=20 +export nodes=64 Added: trunk/etc/sites/coaster-service.conf =================================================================== --- trunk/etc/sites/coaster-service.conf (rev 0) +++ trunk/etc/sites/coaster-service.conf 2011-05-25 19:57:51 UTC (rev 4528) @@ -0,0 +1,31 @@ +# Keep all interesting settings in one place +# User should modify this to fit environment + +# Location of SWIFT. If empty, PATH is referenced +export SWIFT= + +# Where to place/launch worker.pl on the remote machine for sites.xml +export WORKER_WORK=/home/${USER}/work + +# How to launch workers- local or ssh +export WORKER_MODE=ssh + +# Worker logging setting passed to worker.pl for sites.xml +export WORKER_LOGGING=INFO + +# Worker host names for ssh +export WORKERS_HOSTS="crush thwomp stomp crush crank steamroller grind churn trounce thrash vanquish octagon octopus" + +# Directory to keep log files, relative to working directory when launching start-coaster-service +export LOG_DIR=logs + +# Manually define ports. If not specified, ports will be automatically generated +export LOCAL_PORT= +export SERVICE_PORT= + +# Below are various settings to give information about how to create sites.xml +# These must remain as comments in order for gensites to recognize them +#site work=$HOME/work +#site queue=prod-devel +#site maxtime=20 +#site nodes=64 Added: trunk/etc/sites/persistent-coasters =================================================================== --- trunk/etc/sites/persistent-coasters (rev 0) +++ trunk/etc/sites/persistent-coasters 2011-05-25 19:57:51 UTC (rev 4528) @@ -0,0 +1,13 @@ + + + + passive + 4 + .03 + 10000 + + _WORK_ + + From davidk at ci.uchicago.edu Wed May 25 15:42:28 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Wed, 25 May 2011 15:42:28 -0500 (CDT) Subject: [Swift-commit] r4529 - www/docs Message-ID: <20110525204228.C2B7D9CC94@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-25 15:42:28 -0500 (Wed, 25 May 2011) New Revision: 4529 Modified: www/docs/index.php Log: Updated structure for trunk docs Modified: www/docs/index.php =================================================================== --- www/docs/index.php 2011-05-25 19:57:51 UTC (rev 4528) +++ www/docs/index.php 2011-05-25 20:42:28 UTC (rev 4529) @@ -39,6 +39,16 @@

Swift Tutorials

+ + +
  • Swift Tutorial (on your own machine) [html] [pdf]
@@ -67,17 +77,14 @@ information on swift. It is assumed that the reader is already familiar with the material in the Quickstart and Tutorial documents.

-
  • latest (0.91) +
  • historical (0.91) [multi-page html] - [single-page html] - [pdf]
  • +
  • latest (0.92) + [multi-page html] +
  • trunk - [multi-page html] - [single-page html] - [pdf] + [html] [pdf]
  • From hategan at ci.uchicago.edu Wed May 25 15:53:04 2011 From: hategan at ci.uchicago.edu (hategan at ci.uchicago.edu) Date: Wed, 25 May 2011 15:53:04 -0500 (CDT) Subject: [Swift-commit] r4530 - trunk/src/org/griphyn/vdl/karajan/lib/swiftscript Message-ID: <20110525205304.453DF9CC94@svn.ci.uchicago.edu> Author: hategan Date: 2011-05-25 15:53:04 -0500 (Wed, 25 May 2011) New Revision: 4530 Modified: trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java Log: old behavior for trace(); if variable has a value, then print that value Modified: trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java 2011-05-25 20:42:28 UTC (rev 4529) +++ trunk/src/org/griphyn/vdl/karajan/lib/swiftscript/Misc.java 2011-05-25 20:53:04 UTC (rev 4530) @@ -68,7 +68,8 @@ if (i != 0) { buf.append(", "); } - buf.append(args[i]); + Object v = args[i].getValue(); + buf.append(v == null ? args[i] : v); } traceLogger.warn(buf); return null; From davidk at ci.uchicago.edu Fri May 27 09:51:13 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Fri, 27 May 2011 09:51:13 -0500 (CDT) Subject: [Swift-commit] r4531 - in trunk: etc tests tests/providers tests/providers/persistent-coasters tests/providers/persistent-coasters/mcs Message-ID: <20110527145113.7B4589CC9C@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-27 09:51:12 -0500 (Fri, 27 May 2011) New Revision: 4531 Added: trunk/tests/providers/persistent-coasters/ trunk/tests/providers/persistent-coasters/mcs/ trunk/tests/providers/persistent-coasters/mcs/001-catsn.check.sh trunk/tests/providers/persistent-coasters/mcs/001-catsn.clean.sh trunk/tests/providers/persistent-coasters/mcs/001-catsn.setup.sh trunk/tests/providers/persistent-coasters/mcs/001-catsn.swift trunk/tests/providers/persistent-coasters/mcs/001-catsn.timeout trunk/tests/providers/persistent-coasters/mcs/README trunk/tests/providers/persistent-coasters/mcs/catsn.0001.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0002.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0003.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0004.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0005.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0006.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0007.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0008.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0009.out.expected trunk/tests/providers/persistent-coasters/mcs/catsn.0010.out.expected trunk/tests/providers/persistent-coasters/mcs/coaster-service.conf trunk/tests/providers/persistent-coasters/mcs/data.txt trunk/tests/providers/persistent-coasters/mcs/sites.template.xml trunk/tests/providers/persistent-coasters/mcs/tc.template.data trunk/tests/providers/persistent-coasters/mcs/title.txt Modified: trunk/etc/coaster-service.conf trunk/tests/suite.sh Log: Provider tests for persistent coasters on MCS machines over ssh Modified: trunk/etc/coaster-service.conf =================================================================== --- trunk/etc/coaster-service.conf 2011-05-25 20:53:04 UTC (rev 4530) +++ trunk/etc/coaster-service.conf 2011-05-27 14:51:12 UTC (rev 4531) @@ -14,7 +14,7 @@ export WORKER_LOGGING=INFO # Worker host names for ssh -export WORKERS_HOSTS="host1 host2 host3" +export WORKER_HOSTS="host1 host2 host3" # Directory to keep log files, relative to working directory when launching start-coaster-service export LOG_DIR=logs Added: trunk/tests/providers/persistent-coasters/mcs/001-catsn.check.sh =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/001-catsn.check.sh (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/001-catsn.check.sh 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,12 @@ +#!/bin/bash + +set -x + +for count in `seq --format "%04.f" 1 1 10` +do + [ -f catsn.$count.out ] || exit 1 + CONTENTS1=$( cat catsn.$count.out.expected ) + CONTENTS2=$( cat catsn.$count.out ) + [[ $CONTENTS1 == $CONTENTS2 ]] || exit 1 +done +exit 0 Property changes on: trunk/tests/providers/persistent-coasters/mcs/001-catsn.check.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/persistent-coasters/mcs/001-catsn.clean.sh =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/001-catsn.clean.sh (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/001-catsn.clean.sh 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,4 @@ +#!/bin/bash + +stop-coaster-service + Property changes on: trunk/tests/providers/persistent-coasters/mcs/001-catsn.clean.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/persistent-coasters/mcs/001-catsn.setup.sh =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/001-catsn.setup.sh (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/001-catsn.setup.sh 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,5 @@ +#!/bin/bash + +cp -v $GROUP/data.txt . || exit 1 +cp -v $GROUP/*expected . || exit 1 +start-coaster-service || exit 1 Property changes on: trunk/tests/providers/persistent-coasters/mcs/001-catsn.setup.sh ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/persistent-coasters/mcs/001-catsn.swift =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/001-catsn.swift (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/001-catsn.swift 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,12 @@ +type file; + +app (file o) cat (file i) +{ + cat @i stdout=@o; +} + +file out[]; +foreach j in [1:@toint(@arg("n","10"))] { + file data<"data.txt">; + out[j] = cat(data); +} Added: trunk/tests/providers/persistent-coasters/mcs/001-catsn.timeout =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/001-catsn.timeout (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/001-catsn.timeout 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +180 Added: trunk/tests/providers/persistent-coasters/mcs/README =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/README (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/README 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Before running this test, be sure to copy coaster-service.conf to your swift etc directory Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0001.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0001.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0001.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0002.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0002.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0002.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0003.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0003.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0003.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0004.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0004.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0004.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0005.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0005.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0005.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0006.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0006.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0006.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0007.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0007.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0007.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0008.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0008.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0008.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0009.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0009.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0009.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/catsn.0010.out.expected =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/catsn.0010.out.expected (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/catsn.0010.out.expected 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/coaster-service.conf =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/coaster-service.conf (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/coaster-service.conf 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,33 @@ +# Keep all interesting settings in one place +# User should modify this to fit environment + +# Location of SWIFT. If empty, PATH is referenced +export SWIFT= + +# Where to place/launch worker.pl on the remote machine for sites.xml +export WORKER_WORK=/home/${USER}/work + +# How to launch workers: local, ssh, or cobalt +export WORKER_MODE=ssh + +# Worker logging setting passed to worker.pl for sites.xml +export WORKER_LOGGING=INFO + +# Worker host names for ssh +export WORKER_HOSTS="crush.mcs.anl.gov thwomp.mcs.anl.gov stomp.mcs.anl.gov crank.mcs.anl.gov steamroller.mcs.anl.gov grind.mcs.anl.gov churn.mcs.anl.gov trounce.mcs.anl.gov thrash.mcs.anl.gov vanquish.mcs.anl.gov" + +# Directory to keep log files, relative to working directory when launching start-coaster-service +export LOG_DIR=logs + +# Manually define ports. If not specified, ports will be automatically generated +export LOCAL_PORT= +export SERVICE_PORT= + +# start-coaster-service tries to automatically detect IP address. Specify here if auto detection is not working correctly +export IPADDR= + +# Below are various settings to give information about how to create sites.xml +export work=$HOME/work +export queue=prod-devel +export maxtime=20 +export nodes=64 Added: trunk/tests/providers/persistent-coasters/mcs/data.txt =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/data.txt (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/data.txt 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +Hello world Added: trunk/tests/providers/persistent-coasters/mcs/sites.template.xml =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/sites.template.xml (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/sites.template.xml 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,13 @@ + + + + passive + 4 + .03 + 10000 + + _WORK_ + + Property changes on: trunk/tests/providers/persistent-coasters/mcs/sites.template.xml ___________________________________________________________________ Added: svn:executable + * Added: trunk/tests/providers/persistent-coasters/mcs/tc.template.data =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/tc.template.data (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/tc.template.data 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1,7 @@ +persistent-coasters echo /bin/echo INSTALLED INTEL32::LINUX +persistent-coasters cat /bin/cat INSTALLED INTEL32::LINUX +persistent-coasters ls /bin/ls INSTALLED INTEL32::LINUX +persistent-coasters grep /bin/grep INSTALLED INTEL32::LINUX +persistent-coasters sort /bin/sort INSTALLED INTEL32::LINUX +persistent-coasters paste /bin/paste INSTALLED INTEL32::LINUX +persistent-coasters wc /usr/bin/wc INSTALLED INTEL32::LINUX Added: trunk/tests/providers/persistent-coasters/mcs/title.txt =================================================================== --- trunk/tests/providers/persistent-coasters/mcs/title.txt (rev 0) +++ trunk/tests/providers/persistent-coasters/mcs/title.txt 2011-05-27 14:51:12 UTC (rev 4531) @@ -0,0 +1 @@ +MCS Machines with Persistent Coasters and SSH Modified: trunk/tests/suite.sh =================================================================== --- trunk/tests/suite.sh 2011-05-25 20:53:04 UTC (rev 4530) +++ trunk/tests/suite.sh 2011-05-27 14:51:12 UTC (rev 4531) @@ -892,6 +892,7 @@ echo "s at _HOST_@$GLOBUS_HOSTNAME@" echo "s at _PROJECT_@$PROJECT@" echo "s at _QUEUE_@$QUEUE@" + echo "s at _EXECUTION_URL_@$EXECUTION_URL@" } > $RUNDIR/sites.sed return 0 } From wozniak at ci.uchicago.edu Fri May 27 12:21:45 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Fri, 27 May 2011 12:21:45 -0500 (CDT) Subject: [Swift-commit] r4532 - trunk/src/org/griphyn/vdl/karajan/lib Message-ID: <20110527172145.0E7289CCFA@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-27 12:21:44 -0500 (Fri, 27 May 2011) New Revision: 4532 Modified: trunk/src/org/griphyn/vdl/karajan/lib/GetFieldSubscript.java Log: Use generics Modified: trunk/src/org/griphyn/vdl/karajan/lib/GetFieldSubscript.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/GetFieldSubscript.java 2011-05-27 14:51:12 UTC (rev 4531) +++ trunk/src/org/griphyn/vdl/karajan/lib/GetFieldSubscript.java 2011-05-27 17:21:44 UTC (rev 4532) @@ -37,7 +37,7 @@ path = parsePath("["+((Double)index).intValue()+"]", stack); else throw new RuntimeException("Cannot handle array index of Java type "+index.getClass()); - Collection fields = var.getFields(path); + Collection fields = var.getFields(path); if(fields.size() == 1) return fields.iterator().next(); else From wozniak at ci.uchicago.edu Fri May 27 12:26:44 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Fri, 27 May 2011 12:26:44 -0500 (CDT) Subject: [Swift-commit] r4533 - in trunk: etc src/org/griphyn/vdl/karajan src/org/griphyn/vdl/karajan/lib src/org/griphyn/vdl/util Message-ID: <20110527172644.A7D439CCFA@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-27 12:26:44 -0500 (Fri, 27 May 2011) New Revision: 4533 Modified: trunk/etc/log4j.properties trunk/src/org/griphyn/vdl/karajan/Loader.java trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java trunk/src/org/griphyn/vdl/util/VDL2Config.java Log: Enable auto-insertion of input file text in log May be disabled by changing log4j.logger.swift.textfiles Modified: trunk/etc/log4j.properties =================================================================== --- trunk/etc/log4j.properties 2011-05-27 17:21:44 UTC (rev 4532) +++ trunk/etc/log4j.properties 2011-05-27 17:26:44 UTC (rev 4533) @@ -11,12 +11,13 @@ log4j.appender.FILE.layout=org.apache.log4j.PatternLayout log4j.appender.FILE.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss,SSSZZZZZ} %-5p %c{1} %m%n -log4j.logger.swift=DEBUG log4j.logger.org.apache.axis.utils=ERROR # Swift +log4j.logger.swift=DEBUG +log4j.logger.swift.textfiles=DEBUG log4j.logger.org.globus.swift.trace=INFO log4j.logger.org.griphyn.vdl.karajan.Loader=DEBUG log4j.logger.org.griphyn.vdl.karajan.functions.ProcessBulkErrors=WARN Modified: trunk/src/org/griphyn/vdl/karajan/Loader.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/Loader.java 2011-05-27 17:21:44 UTC (rev 4532) +++ trunk/src/org/griphyn/vdl/karajan/Loader.java 2011-05-27 17:26:44 UTC (rev 4533) @@ -37,6 +37,7 @@ import org.globus.cog.karajan.workflow.nodes.grid.AbstractGridNode; import org.globus.cog.util.ArgumentParser; import org.globus.cog.util.ArgumentParserException; +import org.globus.cog.util.TextFileLoader; import org.globus.swift.data.Director; import org.griphyn.vdl.engine.Karajan; import org.griphyn.vdl.karajan.functions.ConfigProperty; @@ -90,10 +91,10 @@ ap.usage(); System.exit(0); } - if (ap.isPresent(ARG_VERSION)){ - ap.version(); - System.exit(0); - } + if (ap.isPresent(ARG_VERSION)){ + ap.version(); + System.exit(0); + } if (ap.isPresent(ARG_MONITOR)) { new Monitor().start(); } @@ -175,7 +176,8 @@ VariableStack stack = new LinkedStack(ec); VDL2Config config = loadConfig(ap, stack); addCommandLineProperties(config, ap); - + debugSitesText(config); + if (ap.isPresent(ARG_DRYRUN)) { stack.setGlobal(CONST_VDL_OPERATION, VDL_OPERATION_DRYRUN); } @@ -226,7 +228,8 @@ String cdmString = null; try { cdmString = ap.getStringValue(ARG_CDMFILE); - File cdmFile = new File(cdmString); + File cdmFile = new File(cdmString); + debugText("CDM FILE", cdmFile); Director.load(cdmFile); } catch (IOException e) { @@ -246,6 +249,7 @@ ParsingException, IncorrectInvocationException, CompilationException, IOException { File swiftscript = new File(project); + debugText("SWIFTSCRIPT", swiftscript); String projectBase = project.substring(0, project.lastIndexOf('.')); File xml = new File(projectBase + ".xml"); File kml = new File(projectBase + ".kml"); @@ -328,7 +332,44 @@ return kml.getAbsolutePath(); } - private static void loadBuildVersion() { + /** + Enter the text content of given files into the log + @throws IOException + */ + public static void debugText(String name, File file) { + Logger textLogger = Logger.getLogger("swift.textfiles"); + try { + if (textLogger.isDebugEnabled()) { + String text = TextFileLoader.loadFromFile(file); + textLogger.debug("BEGIN " + name + ":\n" + text + "\n"); + textLogger.debug("END " + name + ":"); + } + } + catch (IOException e) { + logger.warn("Could not open: " + file); + } + } + + static void debugSitesText(VDL2Config config) { + VDL2Config defaultConfig = null; + try { + defaultConfig = VDL2Config.getDefaultConfig(); + + } catch (IOException e) { + logger.warn("Could not log sites file text"); + } + String poolFile = config.getPoolFile(); + String defaultPoolFile = defaultConfig.getPoolFile(); + if (poolFile.equals(defaultPoolFile)) { + Logger textLogger = Logger.getLogger("swift.textfiles"); + textLogger.debug("using default sites file"); + } + else { + debugText("SITES", new File(poolFile)); + } + } + + private static void loadBuildVersion() { try { File f = new File(System.getProperty("swift.home") + "/libexec/buildid.txt"); @@ -363,7 +404,9 @@ Map.Entry e = (Map.Entry) i.next(); String name = (String) e.getKey(); if (ap.isPresent(name)) { - config.setProperty(name, ap.getStringValue(name)); + String value = ap.getStringValue(name); + logger.debug("setting: " + name + " to: " + value); + config.setProperty(name, value); } } } Modified: trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java =================================================================== --- trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java 2011-05-27 17:21:44 UTC (rev 4532) +++ trunk/src/org/griphyn/vdl/karajan/lib/VDLFunction.java 2011-05-27 17:26:44 UTC (rev 4533) @@ -33,6 +33,7 @@ import org.globus.swift.catalog.transformation.File; import org.globus.swift.catalog.types.TCType; import org.griphyn.vdl.karajan.AssertFailedException; +import org.griphyn.vdl.karajan.Loader; import org.griphyn.vdl.karajan.TCCache; import org.griphyn.vdl.karajan.VDL2FutureException; import org.griphyn.vdl.karajan.WrapperMap; @@ -608,6 +609,7 @@ TCCache tc = (TCCache) stack.firstFrame().getVar(TC); if (tc == null) { String prop = ConfigProperty.getProperty(VDL2ConfigProperties.TC_FILE, stack); + Loader.debugText("TC", new java.io.File(prop)); tc = new TCCache(File.getNonSingletonInstance(prop)); stack.firstFrame().setVar(TC, tc); } Modified: trunk/src/org/griphyn/vdl/util/VDL2Config.java =================================================================== --- trunk/src/org/griphyn/vdl/util/VDL2Config.java 2011-05-27 17:21:44 UTC (rev 4532) +++ trunk/src/org/griphyn/vdl/util/VDL2Config.java 2011-05-27 17:26:44 UTC (rev 4533) @@ -40,7 +40,7 @@ return config.check(); } - private static synchronized VDL2Config getDefaultConfig() throws IOException { + public static synchronized VDL2Config getDefaultConfig() throws IOException { if (config == null) { config = new VDL2Config(); for (int i = 0; i < CONFIG_FILE_SEARCH_PATH.length; i++) { From davidk at ci.uchicago.edu Fri May 27 12:33:03 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Fri, 27 May 2011 12:33:03 -0500 (CDT) Subject: [Swift-commit] r4534 - in trunk: bin etc Message-ID: <20110527173303.3C50A9CCFA@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-27 12:33:03 -0500 (Fri, 27 May 2011) New Revision: 4534 Modified: trunk/bin/gensites trunk/bin/start-coaster-service trunk/etc/coaster-service.conf Log: Updated start-coaster-service to start workers locally and with cobalt Modified: trunk/bin/gensites =================================================================== --- trunk/bin/gensites 2011-05-27 17:26:44 UTC (rev 4533) +++ trunk/bin/gensites 2011-05-27 17:33:03 UTC (rev 4534) @@ -144,7 +144,7 @@ fi # Parse values into variables for later sed processing -WORK=`pwd`"/work" +#WORK=`pwd`"/work" while read line do case "$line" in @@ -204,7 +204,7 @@ echo "s/_N_MAX_/${N_MAX}/" echo "s/_SLOTS_/${SLOTS}/" echo "s/_MAXTIME_/${MAXTIME}/" - echo "s/_EXECUTION_URL_/${EXECUTION_URL}/" + echo "s at _EXECUTION_URL_@${EXECUTION_URL}@" echo "s at _SERVICE_COASTERS_@${SERVICE_COASTERS:-NO_URL_GIVEN}@" echo "s at _SERVICE_PORT_@${SERVICE_PORT:-NO_PORT_GIVEN}@" } > $SEDFILE Modified: trunk/bin/start-coaster-service =================================================================== --- trunk/bin/start-coaster-service 2011-05-27 17:26:44 UTC (rev 4533) +++ trunk/bin/start-coaster-service 2011-05-27 17:33:03 UTC (rev 4534) @@ -29,13 +29,37 @@ # Start local workers start-workers-local() { - echo foo + PORT=$1 + EXECUTION_URL=http://$IPADDR:$PORT + if [ -z "$PORT" ]; then + crash "start-workers-local: Port number not specified, giving up" + fi + echo Starting worker on local machine + $WORKER $EXECUTION_URL LOCAL $LOG_DIR & + echo $! >> $PID_FILE + return 0 } # Start cobalt workers start-workers-cobalt() { - echo foo + PORT=$1 + EXECUTION_URL=http://$IPADDR:$PORT + local TIMESTAMP=$(date "+%Y.%m%d.%H%M%S") + local -Z 5 R=${RANDOM} + ID="${TIMESTAMP}.${R}" + echo cqsub -q ${QUEUE} \ + -k zeptoos \ + -t ${MAXTIME} \ # minutes + -n ${NODES} \ + --cwd ${LOGDIR} \ + -E ${LOGDIR}/cobalt.${$}.stderr \ + -o ${LOGDIR}/cobalt.${$}.stdout \ + -e "WORKER_LOGGING_LEVEL=DEBUG:ZOID_ENABLE_NAT=true" \ + $WORKER $EXECUTION_URL $ID $LOG_DIR + + echo $! >> $PID_FILE + return 0 } PID_FILE=".coaster-service-pids" @@ -153,7 +177,6 @@ esac # Generate sites.xml -export EXECUTION_URL="http:\/\/$IPADDR:$SERVICE_PORT" +export EXECUTION_URL="http://$IPADDR:$SERVICE_PORT" echo Generating sites.xml.. gensites persistent-coasters -p $CONFIG_FILE > $RUN_DIR/sites.xml - Modified: trunk/etc/coaster-service.conf =================================================================== --- trunk/etc/coaster-service.conf 2011-05-27 17:26:44 UTC (rev 4533) +++ trunk/etc/coaster-service.conf 2011-05-27 17:33:03 UTC (rev 4534) @@ -27,7 +27,7 @@ export IPADDR= # Below are various settings to give information about how to create sites.xml -export work=$HOME/work -export queue=prod-devel -export maxtime=20 -export nodes=64 +export WORK=$HOME/work +export QUEUE=prod-devel +export MAXTIME=20 +export NODE=64 From wozniak at ci.uchicago.edu Tue May 31 15:14:17 2011 From: wozniak at ci.uchicago.edu (wozniak at ci.uchicago.edu) Date: Tue, 31 May 2011 15:14:17 -0500 (CDT) Subject: [Swift-commit] r4535 - text/parco10submission Message-ID: <20110531201417.623C09CCA5@svn.ci.uchicago.edu> Author: wozniak Date: 2011-05-31 15:14:17 -0500 (Tue, 31 May 2011) New Revision: 4535 Added: text/parco10submission/highlight.txt Log: Adding Added: text/parco10submission/highlight.txt =================================================================== --- text/parco10submission/highlight.txt (rev 0) +++ text/parco10submission/highlight.txt 2011-05-31 20:14:17 UTC (rev 4535) @@ -0,0 +1,11 @@ +The Swift parallel scripting language is described in detail. + +Swift provides an implicitly parallel functional data flow computation +model that simplifies parallel scripting. + +Swift scripts describe parallel execution patterns for running +independent serial or parallel programs. + +Swift scales from multicore workstations to petascale systems, using +parallel and distributed resources, including clusters, grids, and +clouds. From davidk at ci.uchicago.edu Mon May 16 14:29:37 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Mon, 16 May 2011 19:29:37 -0000 Subject: [Swift-commit] r4479 - in branches/release-0.92/docs: . cookbook tutorial userguide Message-ID: <20110516192935.D7F889CD2E@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-16 14:29:35 -0500 (Mon, 16 May 2011) New Revision: 4479 Added: branches/release-0.92/docs/build_docs.sh branches/release-0.92/docs/cookbook/ branches/release-0.92/docs/cookbook/cookbook-asciidoc.html branches/release-0.92/docs/cookbook/cookbook-asciidoc.pdf branches/release-0.92/docs/cookbook/cookbook-asciidoc.txt branches/release-0.92/docs/tutorial/ branches/release-0.92/docs/tutorial/tutorial.html branches/release-0.92/docs/tutorial/tutorial.pdf branches/release-0.92/docs/tutorial/tutorial.txt branches/release-0.92/docs/userguide/ branches/release-0.92/docs/userguide/swift-site-model.png branches/release-0.92/docs/userguide/type-hierarchy.png branches/release-0.92/docs/userguide/userguide.html branches/release-0.92/docs/userguide/userguide.txt Log: Updated docs Added: branches/release-0.92/docs/build_docs.sh =================================================================== --- branches/release-0.92/docs/build_docs.sh (rev 0) +++ branches/release-0.92/docs/build_docs.sh 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,33 @@ +#!/bin/bash + +if [ -n "$1" ]; then + INSTALLATION_DIRECTORY=$1 +else + echo Error: Must specify a directory for installation + exit 1 +fi + +if [ ! -d "$INSTALLATION_DIRECTORY" ]; then + mkdir $INSTALLATION_DIRECTORY || exit 1 +fi + +echo Installing docs into $INSTALLATION_DIRECTORY + +cd docs || exit 1 +DIRECTORIES=*/ +for directory in $DIRECTORIES +do + cd $directory || exit 1 + FILES=*.txt + for file in $FILES + do + echo Converting $directory"$file" to HTML + asciidoc -a toc $file + echo Converting $directory"$file" to PDF + a2x --format=pdf --no-xmllint $file + done + cp *.html $INSTALLATION_DIRECTORY || exit 1 + cp *.pdf $INSTALLATION_DIRECTORY || exit 1 + cd .. || exit 1 +done +cd .. Property changes on: branches/release-0.92/docs/build_docs.sh ___________________________________________________________________ Added: svn:executable + * Added: branches/release-0.92/docs/cookbook/cookbook-asciidoc.html =================================================================== --- branches/release-0.92/docs/cookbook/cookbook-asciidoc.html (rev 0) +++ branches/release-0.92/docs/cookbook/cookbook-asciidoc.html 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,1497 @@ + + + + + +Swift Cookbook + + + + + +
    +
    +

    Overview

    +
    +

    This cookbook covers various recipes involving setting up and running Swift under diverse +configurations based on the application requirements and the underlying +infrastructures. The Swift system comprises of SwiftScript language and the +Swift runtime system. For +introductory material, consult the Swift tutorial found +here.

    +
    +
    +
    +

    Swift Basics

    +
    +
    +

    Installation

    +

    This section takes you through the installation of the Swift system on your +computer. We will start with the prerequisites as explained in the subsequent +section.

    +
    +

    Prerequisites

    +
    Check your Java

    Swift is a Java application. Make sure you are running Java version 5 or higher. You +can make sure you have Java in your $PATH (or $HOME/.soft file depending upon +your environment)

    +

    Following are the possible ways to detect and run Java:

    +
    +
    +
    $ grep java $HOME/.soft
    +#+java-sun # Gives you Java 5
    ++java-1.6.0_03-sun-r1
    +$ which java
    +/soft/java-1.6.0_11-sun-r1/bin/java
    +$ java -version
    +java version "1.6.0_11"
    +Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
    +Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
    +
    +
    +
    +
    +

    Setting up to run Swift

    +

    This is simple. We will be using a pre-compiled version of Swift that can be +downloaded from here. Download and untar the latest precompiled version as follows:

    +
    +
    +
    $ tar xf swift-0.92.1.tar.gz
    +
    +
    +

    Environment Setup

    +

    The examples were tested with Java version 1.6. Make sure you do not already +have Swift in your PATH. If you do, remove it, or remove any +swift or @swift +lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:

    +
    +
    +
    PATH=$PATH:/path/to/swift/bin
    +
    +

    Note that the environment will be different when using Swift from prebuilt distribution (as above) and trunk. The PATH setup when using swift from trunk would be as follows:

    +
    +
    +
    PATH=$PATH:/path/to/swift/dist/swift-svn/bin
    +
    +
    + + + +
    +
    Warning
    +
    Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you +fully understand how these will affect Swift’s execution.
    +
    +

    To execute your Swift script on a login host (or "localhost") use +the following command:

    +
    +
    +
    swift -tc.file tc somescript.swift
    +
    +
    +
    +

    Setting transformation catalog

    +

    The transformation catalog lists where application executables are located on +remote sites.

    +

    By default, the site catalog is stored in etc/tc.data. This path can be +overridden with the tc.file configuration property, either in the Swift +configuration file or on the command line.

    +

    The format is one line per executable per site, with fields separated by tabs +or spaces.

    +

    Some example entries:

    +
    +
    +
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    +TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX GLOBUS::maxwalltime="00:00:10"
    +
    +

    The fields are: site, transformation-name, executable-path, installation-status, platform, and profile entries.

    +

    The site field should correspond to a site name listed in the sites catalog.

    +

    The transformation-name should correspond to the transformation name used in a +SwiftScript app procedure.

    +

    The executable-path should specify where the particular executable is located +on that site.

    +

    The installation-status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively.

    +

    The profiles field should be set to null if no profile entries are to be +specified, or should contain the profile entries separated by semicolons.

    +
    +
    +

    Setting swift configuration

    +

    Many configuration properties could be set using the Swift configuration file. +We will not cover them all in this section. see +here for details. In this section we will cover a simple configuration file with the most basic properties.

    +
    +
    +
    # A comment
    +wrapperlog.always.transfer=true
    +sitedir.keep=true
    +execution.retries=1
    +lazy.errors=true
    +status.mode=provider
    +use.provider.staging=true
    +provider.staging.pin.swiftfiles=false
    +clustering.enabled=false
    +clustering.queue.delay=10
    +clustering.min.time=86400
    +foreach.max.threads=100
    +provenance.log=true
    +
    +
    +
    +

    Setting sites.xml

    +

    sites.xml specifies details of the sites that Swift can run on. Following is +an example of a simple sites.xml file entry for running Swift on local +environment:

    +
    +
    +
    <pool handle="localhost">
    +<filesystem provider="local" />
    +<execution provider="local" />
    +<workdirectory >/var/tmp</workdirectory>
    +<profile namespace="karajan" key="jobThrottle">.07</profile>
    +<profile namespace="karajan"
    +key="initialScore">100000</profile>
    +</pool>
    +
    +
    +
    +

    First SwiftScript

    +

    Your first SwiftScript +Hello Swift-World!

    +

    A good sanity check that Swift is set up and running OK locally is this:

    +
    +
    +
    $ which swift
    +
    +/home/wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift
    +
    +$ echo 'trace("Hello, Swift world!");' >hello.swift
    +
    +$ swift hello.swift
    +
    +Swift svn swift-r3202 cog-r2682
    +
    +RunID: 20100115-1240-6xhzxuz3
    +
    +Progress:
    +
    +SwiftScript trace: Hello, Swift world!
    +
    +Final status:
    +
    +$
    +
    +

    A good first tutorial in using Swift is at: +http://www.ci.uchicago.edu/swift/guides/tutorial.php. Follow the steps in that +tutorial to learn how to run a few simple scripts on the login host.

    +
    +
    +

    second SwiftScript

    +

    Following is a more involved Swift script.

    +
    +
    +
    type file;
    +
    +app (file o) cat (file i)
    +{
    +    cat @i stdout=@o;
    +}
    +
    +file out[]<simple_mapper; location="outdir", prefix="f.",suffix=".out">;
    +
    +foreach j in [1:@toint(@arg("n","1"))] {
    +
    +    file data<"data.txt">;
    +
    +    out[j] = cat(data);
    +}
    +
    +
    +

    Swift Commandline Options

    +

    A description of Swift Commandline Options

    +

    Also includes a description of Swift inputs and outputs.

    +
    +
    +

    What if Swift hangs

    +

    Owing to its highly multithreaded architecture it is often the case that the +underlying java virtual machine gets into deadlock situations or Swift hangs +because of other complications in its threaded operations. Under such +situations, Swift hang-checker chips in and resolves the situation.

    +
      +
    1. +

      +how to use the information to identify and correct the deadlock. +

      +
    2. +
    3. +

      +How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines? +

      +
    4. +
    5. +

      +The current Hang Checker output is actually very nice and useful already: +

      +
    6. +
    +
    +
    +
    Registered futures:
    +Rupture[] rups  Closed, 1 elements, 0 listeners
    +Variation vars - Closed, no listeners
    +SgtDim sub - Open, 1 listeners
    +string site  Closed, no listeners
    +Variation[] vars  Closed, 72 elements, 0 listeners
    +
    +
    +
    +

    Resuming a stopped or crashed Swift Run

    +

    I had a .rlog file from a Swift run that ran out of time. I kicked it off +using the -resume flag described in section 16.2 of the Swift User Guide and +it picked up where it left off. Then I killed it because I wanted to make +changes to my sites file.

    +
    +
    +
    . . .
    +Progress:  Selecting site:1150  Stage in:55  Active:3  Checking status:1
    +Stage out:37  Finished in previous run:2462  Finished successfully:96
    +Progress:  Selecting site:1150  Stage in:55  Active:2  Checking status:1
    +Stage out:38  Finished in previous run:2462  Finished successfully:96
    +Cleaning up...
    +Shutting down service at https://192.5.86.6:54813
    +Got channel MetaChannel: 1293358091 -> null
    ++ Done
    +Canceling job 9297.svc.pads.ci.uchicago.edu
    +
    +

    No new rlog file was emitted but it did recognize the progress that had been +made, the 96 tasks that finished sucessfully above and resumed from 2558 tasks +finished.

    +
    +
    +
    [nbest at login2 files]$ pwd
    +/home/nbest/bigdata/files
    +[nbest at login2 files]$
    +~wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift \
    +> -tc.file tc -sites.file pbs.xml ~/scripts/mcd12q1.swift -resume
    +> mcd12q1-20100310-1326-ptxe1x1d.0.rlog
    +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    +locally)
    +RunID: 20100311-1027-148caf0a
    +Progress:
    +Progress:  uninitialized:4
    +Progress:  Selecting site:671  Initializing site shared directory:1  Finished
    +in previous run:1864
    +Progress:  uninitialized:1  Selecting site:576  Stage in:96  Finished in
    +previous run:1864
    +Progress:  Selecting site:1150  Stage in:94  Submitting:2  Finished in
    +previous run:2558
    +Progress:  Selecting site:1150  Stage in:94  Submitted:2  Finished in previous
    +run:2558
    +Progress:  Selecting site:1150  Stage in:93  Submitting:1  Submitted:2
    +Finished in previous run:2558
    +Progress:  Selecting site:1150  Stage in:90  Submitting:1  Submitted:5
    +Finished in previous run:2558
    +Progress:  Selecting site:1150  Stage in:90  Submitted:5  Active:1  Finished
    +in previous run:2558
    +
    +

    From Neil: A comment about that section of the user guide: It says "In order +to restart from a restart log file, the -resume logfile argument can be used +after the SwiftScript? program file name." and then puts the -resume logfile +argument before the script file name. I’m sure the order doesn’t matter but +the contradiction is confusing.

    +

    Notes to add (from Mike):

    +
      +
    • +

      +explain what aspects of a Swift script make it restartable, and which + aspects are notrestartable. Eg, if your mappers can return different data at +different times, what happens? What other non-determinsitc behavior would +cause unpredictable, unexpected, or undesired behavior on resumption? +

      +
    • +
    • +

      +explain what changes you can make in the execution environment (eg + increasing or reducing CPUs to run on or throttles, etc); fixing tc.data +entries, env vars, or apps, etc. +

      +
    • +
    • +

      +note that resume will again retry failed app() calls. Explain if the retry + count starts over or not. +

      +
    • +
    • +

      +explain how to resume after multiple failures and resumes - i.e. if a .rlog + is generated on each run, which one should you resume from? Do you have a +choice of resuming from any of them, and what happens if you go backwards to +an older resume file? +

      +
    • +
    • +

      +whap happens when you kill (eg with C) a running swift script? Is the + signal caught, and the resume file written out at that point? Or written out +all along? (Note case in which script ws running for hours, then hit C, but +resume fie was short (54 bbytes) and swift shows no sign of doing a resume? +(It silently ignored resume file instead of acknowleging that it found one +with not useful resume state in it???) Swift should clearly state that its +resuming and what its resume state is. +

      +
    • +
    +

    swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial +run\]

    +
    +
    +

    Passing an array to swift?

    +

    Arrays can be passed to Swift in one of the following ways:

    +
      +
    1. +

      +You can write the array to a file and read in in swift using +readData (or readData2). +

      +
    2. +
    3. +

      +Direct the array into a file (possibly with a "here document" which expands the array) and then read the file in Swift with readData() or process it with a Swift app() function? +

      +
    4. +
    5. +

      +You can use @strsplit on a comma separated command line arg and that works well for me. +

      +
    6. +
    +
    +

    Mappers

    +

    SimpleMapper

    +
    +
    +
    $ cat swiftapply.swift
    +
    +
    +
    +
    type RFile;
    +trace("hi 1");
    +app (RFile result) RunR (RFile rcall)
    +{
    +  RunR @rcall @result;
    +}
    +trace("hi 2");
    +RFile rcalls[] ;
    +RFile results[] ;
    +trace("start");
    +foreach c, i in rcalls {
    +  trace("c",i,@c);
    +  trace("r",i,@filename(results[i]));
    +  results[i] = RunR(c);
    +}
    +
    +
    +
    $ ls calldir resdir
    +calldir:
    +rcall.1.Rdata  rcall.2.Rdata  rcall.3.Rdata  rcall.4.Rdata
    +resdir:
    +result.1.Rdata result.2.Rdata result.3.Rdata result.4.Rdata
    +$
    +
    +

    Notes:

    +

    how the .'s match +prefix and suffix dont span dirs +intervening pattern must be digits +these digits become the array indices +explain how padding= arg works & helps (including padding=0) +figure out and explain differences between simple_mapper and +filesys_mapper +FIXME: Use the "filesys_mapper" and its "location=" parameter to map the +input data from /home/wilde/bigdata/*

    +

    Abbreviations for SingleFileMapper +Notes:

    +

    within <> you can only have a literal string as in <"filename">, not an +expression. Someday we will fix this to make <> accept a general expression. +you can use @filenames( ) (note: plural) to pull off a list of filenames.

    +

    writeData()

    +

    example here

    +
    +
    +
    $ cat writedata.swift
    +
    +
    +
    +
    type file;
    +
    +file f <"filea">;
    +file nf <"filenames">;
    +nf = writeData(@f);
    +
    +
    +
    $ swift writedata.swift
    +Swift svn swift-r3264 (swift modified locally) cog-r2730 (cog modified
    +locally)
    +RunID: 20100319-2002-s9vpo0pe
    +Progress:
    +Final status:
    +$ cat filenames
    +filea$
    +
    +

    StructuredRegexpMapper +IN PROGRESS This mapper can be used to base the mapped filenames of an output +array on the mapped filenames of an existing array. landuse outputfiles[] +<structured_regexp_mapper; source=inputfiles, +location="./output",match="(.)*tif", transform="\\1histogram">;

    +

    Use the undocumented "structured_regexp_mapper" to name the output +filenames based on the input filenames:

    +

    For example:

    +
    +
    +
    login2$ ls /home/wilde/bigdata/data/sample
    +h11v04.histogram  h11v05.histogram  h12v04.histogram  h32v08.histogram
    +h11v04.tif        h11v05.tif        h12v04.tif        h32v08.tif
    +login2$
    +
    +login2$ cat regexp2.swift
    +type tif;
    +type mytype;
    +
    +tif  images[]<filesys_mapper;
    +location="/home/wilde/bigdata/data/sample", prefix="h", suffix=".tif">;
    +
    +mytype of[] <structured_regexp_mapper; source=images, match="(h..v..)",
    +transform="output/myfile.\\1.mytype">;
    +
    +foreach image, i in images {
    +   trace(i, at filename(images));
    +   trace(i, at filename(of[i]));
    +}
    +login2$
    +
    +login1$ swift regexp2.swift
    +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    +locally)
    +
    +RunID: 20100310-1105-4okarq08
    +Progress:
    +SwiftScript trace: 1, output/myfile.h11v04.mytype
    +SwiftScript trace: 2, home/wilde/bigdata/data/sample/h11v05.tif
    +SwiftScript trace: 3, home/wilde/bigdata/data/sample/h12v04.tif
    +SwiftScript trace: 0, output/myfile.h32v08.mytype
    +SwiftScript trace: 0, home/wilde/bigdata/data/sample/h32v08.tif
    +SwiftScript trace: 3, output/myfile.h12v04.mytype
    +SwiftScript trace: 1, home/wilde/bigdata/data/sample/h11v04.tif
    +SwiftScript trace: 2, output/myfile.h11v05.mytype
    +Final status:
    +login1$
    +
    +
    +
    +
    +
    +
    +

    Coasters

    +
    +

    Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters.

    +

    Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were:

    +
    +
    +
    <execution provider="coaster" jobmanager="local:pbs"/>
    +<profile namespace="globus" key="project">CI-CCR000013</profile>
    +
    +<!-- Note that the following is going to be defunct in the new version (0.93+) and replaced by
    +"ProviderAttributes" key and may not work in the future Swift versions-->
    +
    +<!--<profile namespace="globus" key="ppn">24:cray:pack</profile>-->
    +
    +<profile namespace="globus" key="providerAttributes">
    +pbs.aprun
    +pbs.mpp=true
    +</profile>
    +
    +<profile namespace="globus" key="workersPerNode">24</profile>
    +<profile namespace="globus" key="maxTime">100000</profile>
    +
    +<profile namespace="globus" key="lowOverallocation">100</profile>
    +<profile namespace="globus" key="highOverallocation">100</profile>
    +
    +<profile namespace="globus" key="slots">20</profile>
    +<profile namespace="globus" key="nodeGranularity">5</profile>
    +<profile namespace="globus" key="maxNodes">5</profile>
    +<profile namespace="karajan" key="jobThrottle">20.00</profile>
    +<profile namespace="karajan" key="initialScore">10000</profile>
    +

    The following table briefly describes the elements on the coasters setup:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    profile key brief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are infinitely long

    workersPerNode

    How many coaster workers to run per execution node reserve How many seconds to reserve in a block’s walltime for starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block coaster service

    jobThrottle

    the number of concurrent jobs allowed on a site

    +
    +
    +

    For Advanced Users

    +

    One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters.

    +
    +
    +

    Coaster providers: local, ssh, pbs

    +

    Settings and examples for different coaster providers mechanisms.

    +
    +
    +
    +
    +

    Swift on Diverse Infrastructures

    +
    +
    +

    Beagle

    +

    Swift is now installed on Beagle as a module. Swift supports a Coasters based, +computing environment for Beagle. A detailed Swift documentation is maintained +[[here]. To get started +with Swift on Beagle follow the steps outlined below:

    +

    step 1. Load the Swift module on Beagle as follows: module load swift

    +

    step 2. Create and change to a directory where your Swift related work will +stay. (say, mkdir swift-lab, followed by, cd swift-lab)

    +

    step 3. To get started with a simple example running /bin/cat to read an input file data.txt and write to an output file f.nnn.out, copy the folder at /home/ketan/labs/catsn to the above directory. (cp -r /home/ketan/catsn . followed by cd catsn).

    +

    step 4. In the sites file: beagle-coaster.xml, make the following two +changes: 1) change the path of workdirectory to your preferred location +(say to /lustre/beagle/$USER/swift-lab/swift.workdir) and 2) Change the +project name to your project (CI-CCR000013) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs.

    +

    step 5. Run the example using following commandline (also found in run.sh): +swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1 +. You can further change the value of -n to any arbitrary number to run that +many number of concurrent cat

    +

    step 6. Check the output in the generated outdir directory (ls outdir)

    +

    Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes +will get fast prioritized execution. Good for small tests

    +
    +
    +

    PADS

    +

    Swift on PADS +To execute your Swift script on the PADS cluster use this command:

    +
    +
    +
    swift -tc.file tc -sites.file pbs.xml modis.swift
    +
    +

    where the contents of a simple pbs.xml sites file could be:

    +
    +
    +
    <config>
    +  <pool handle="pbs">
    +    <execution provider="pbs" url="none"/>
    +    <profile namespace="globus" key="queue">fast</profile>
    +    <profile namespace="globus" key="maxwalltime">00:05:00</profile>
    +    <profile namespace="karajan" key="initialScore">10000</profile>
    +    <profile namespace="karajan" key="jobThrottle">.10</profile>
    +    <filesystem provider="local"/>
    +    <workdirectory >/home/you/swiftwork</workdirectory>
    +  </pool>
    +</config>
    +
    +
    +

    OSG

    +

    This section describes how to get Swift running on the OSG Grid. We will use a +manual coaster setup to get Swift running on OSG.

    +
    Coaster setup on OSG

    The following figure shows an abstract scheme for the manual coasters setup on +OSG.

    +
    +
    +Coaster setup +
    +
    +

    In the following steps, we will go through the process of manually setting

    +
    +
    +

    Bionimbus

    +

    This section explains a step by step procedure on getting Swift running on the +Bionimbus cloud. We will use the manual coasters configuration on the +Bionimbus cloud.

    +

    step1. Connect to the gateway (ssh gatewayx.lac.uic.edu)

    +

    step2. Start a virtual machine (euca-run-instances -n 1 -t m1.small +emi-17EB1170)

    +

    step3. Start the coaster-service on gateway +coaster-service -port 1984 -localport 35753 -nosec

    +

    step4. Start the Swift-script from the gateway using normal Swift commandline

    +

    swift -config cf -tc.file tc -sites.file sites.xml yourscript.swift -aparam=999

    +
    +
    cf
    +
    +
    wrapperlog.always.transfer=true
    +sitedir.keep=true
    +execution.retries=1
    +lazy.errors=true
    +status.mode=provider
    +use.provider.staging=true
    +provider.staging.pin.swiftfiles=false
    +foreach.max.threads=100
    +provenance.log=true
    +
    +
    +
    tc
    +
    +
    localhost modftdock /home/ketan/swift-labs/bionimbus-coaster-modftdock/app/modftdock.sh null null GLOBUS::maxwalltime="1:00:00"
    +
    +

    (See below for a sample sites.xml for this run)

    +

    step5. Connect back to gateway from virtual machines using reverse ssh tunneling as follows:

    +
    From the gateway prompt

    ssh -R *:5000:localhost:5000 root at 10.101.8.50 sleep 999

    +

    WHERE: +*=network interface, should remain the same on all cases

    +

    localhost=the gateway host, should remain the same

    +

    5000(LEFT OF localhost)=the port number on localhost to listen to **THIS WILL +vary depending upon which port you want to listen to

    +

    5000(RIGHT OF localhost)=the port on target host that you want to forward

    +

    root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will +vary based on what ip you get for your Virtual Machine instance

    +

    #On anywhere as long as provide the correct callback uri: here the +"http://140.221.9.110:42195" is the callback uri of previous ones

    +

    step6. Start the worker from the virtual machine +worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the +coaster service is listening to the workers

    +
    +
    sites.xml for the above run
    +
    +
    <config>
    +  <pool handle="localhost">
    +    <execution provider="coaster-persistent" url="http://localhost:1984" jobmanager="local:local"/>
    +    <profile namespace="globus" key="workerManager">passive</profile>
    +
    +    <profile namespace="globus" key="workersPerNode">4</profile>
    +    <profile namespace="globus" key="maxTime">10000</profile>
    +    <profile namespace="globus" key="lowOverAllocation">100</profile>
    +    <profile namespace="globus" key="highOverAllocation">100</profile>
    +    <profile namespace="globus" key="slots">100</profile>
    +    <profile namespace="globus" key="nodeGranularity">1</profile>
    +    <profile namespace="globus" key="maxNodes">10</profile>
    +    <profile namespace="karajan" key="jobThrottle">25.00</profile>
    +    <profile namespace="karajan" key="initialScore">10000</profile>
    +    <profile namespace="swift" key="stagingMethod">proxy</profile>
    +    <filesystem provider="local"/>
    +    <workdirectory>/home/ketan/swift-labs/bionimbus-coaster-modftdock/swift.workdir</workdirectory>
    +  </pool>
    +</config>
    +
    +
    +
    +
    +

    Debugging Swift

    +
    +

    Swift errors are logged in several places:

    +
      +
    1. +

      +All text from standard output and standard error produced by running the +swift command +

      +
    2. +
    3. +

      +The .log file from this run. It will be named swiftscript.uniqueID.log +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +

      +
    4. +
    5. +

      +$HOME/.globus/coasters directory on remote machines on which you are +running coasters +

      +
    6. +
    7. +

      +$HOME/.globus/scripts directory on the host on which you run the Swift +command, when swift is submitting to a local scheduler (Condor, PBS, SGE, +Cobalt) +

      +
    8. +
    9. +

      +$HOME/.globus/??? on remote systems that you access via Globus +

      +
    10. +
    +
    +
    +
    +

    Log Processing

    +
    +

    To properly generate log plots, you must enable VDL/Karajan logging. Make sure +log4.properties contains:

    +
    +
    +
    log4j.logger.swift=DEBUG
    +log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG
    +
    +
    +

    Make a basic load plot from Coasters Cpu log lines

    +
    Generate the log (may set log4j.logger.swift=INFO for this one)

    (assuming the log is titled swift-run.log)

    +
    +
    Convert the log times to Unix time
    +
    +
    ./iso-to-secs < swift-run.log > swift-run.time
    +
    +
    +
    Make the start time file (this contains the earliest timestamp)
    +
    +
    make LOG=swift-run.log start-time.tmp
    +
    +

    or

    +
    +
    +
    extract-start-time swift-run.log > start-time.tmp
    +
    +
    +
    Normalize the transition times
    +
    +
    ./normalise-event-start-time < swift-run.time > swift-run.norm
    +
    +
    +
    Build up a load data file:
    +
    +
    ./cpu-job-load.pl < swift-run.norm > load.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh load.cfg load.eps load.data
    +
    +
    +

    Make a basic job completion plot from Coasters Cpu log lines

    +
    +
    Same as above, but, build up a completed data file:
    +
    +
    ./cpu-job-completed.pl < swift-run.norm > completed.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh completed.cfg completed.eps completed.data
    +
    +
    +
    +

    Make a basic Block allocation plot from Coasters Block log lines

    +

    Same as above, but:

    +
    +
    Build up a block allocation data file:
    +
    +
    ./block-level.pl < swift-run.norm > blocks.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh blocks.{cfg,eps,data}
    +
    +
    +
    +
    +

    Problem Reporting

    +

    When reporting problems to swift-user at ci.uchicago.edu, please attach the +following files and information:

    +
      +
    1. +

      +tc.data and sites.xml (or whatever you named these files) +

      +
    2. +
    3. +

      +your .swift source file and any .swift files it imports +

      +
    4. +
    5. +

      +any external mapper scripts called by your .swift script +

      +
    6. +
    7. +

      +all text from standard output and standard error produced by running the +swift command +

      +
    8. +
    9. +

      +The .log file from this run. It will be named swiftscript.uniqueID.log +

      +
    10. +
    11. +

      +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +

      +
    12. +
    13. +

      +The swift command line you invoked +

      +
    14. +
    15. +

      +Any swift.properties entries you over-rode ($HOME/.swift/swift.properties, +-config.file argument properties file, any changes to etc/swift.proerties from +your swift distribution) +

      +
    16. +
    17. +

      +Which swift distribution you are running (release; svn revisions; other +local changes you mave have made or included) +

      +
    18. +
    +
    +
    +
    +
    +

    + + + Added: branches/release-0.92/docs/cookbook/cookbook-asciidoc.pdf =================================================================== --- branches/release-0.92/docs/cookbook/cookbook-asciidoc.pdf (rev 0) +++ branches/release-0.92/docs/cookbook/cookbook-asciidoc.pdf 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,4267 @@ +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (section.1) >> +endobj +8 0 obj +(Overview) +endobj +9 0 obj +<< /S /GoTo /D (section.2) >> +endobj +12 0 obj +(Swift Basics) +endobj +13 0 obj +<< /S /GoTo /D (subsection.2.1) >> +endobj +16 0 obj +(Installation) +endobj +17 0 obj +<< /S /GoTo /D (subsubsection.2.1.1) >> +endobj +20 0 obj +(Prerequisites) +endobj +21 0 obj +<< /S /GoTo /D (subsection.2.2) >> +endobj +24 0 obj +(Setting up to run Swift) +endobj +25 0 obj +<< /S /GoTo /D (subsubsection.2.2.1) >> +endobj +28 0 obj +(Environment Setup) +endobj +29 0 obj +<< /S /GoTo /D (subsubsection.2.2.2) >> +endobj +32 0 obj +(Setting transformation catalog) +endobj +33 0 obj +<< /S /GoTo /D (subsubsection.2.2.3) >> +endobj +36 0 obj +(Setting swift configuration) +endobj +37 0 obj +<< /S /GoTo /D (subsubsection.2.2.4) >> +endobj +40 0 obj +(Setting sites.xml) +endobj +41 0 obj +<< /S /GoTo /D (subsection.2.3) >> +endobj +44 0 obj +(First SwiftScript) +endobj +45 0 obj +<< /S /GoTo /D (subsection.2.4) >> +endobj +48 0 obj +(second SwiftScript) +endobj +49 0 obj +<< /S /GoTo /D (subsection.2.5) >> +endobj +52 0 obj +(Swift Commandline Options) +endobj +53 0 obj +<< /S /GoTo /D (subsection.2.6) >> +endobj +56 0 obj +(What if Swift hangs) +endobj +57 0 obj +<< /S /GoTo /D (subsection.2.7) >> +endobj +60 0 obj +(Resuming a stopped or crashed Swift Run) +endobj +61 0 obj +<< /S /GoTo /D (subsection.2.8) >> +endobj +64 0 obj +(Passing an array to swift?) +endobj +65 0 obj +<< /S /GoTo /D (subsubsection.2.8.1) >> +endobj +68 0 obj +(Mappers) +endobj +69 0 obj +<< /S /GoTo /D (section.3) >> +endobj +72 0 obj +(Coasters) +endobj +73 0 obj +<< /S /GoTo /D (subsection.3.1) >> +endobj +76 0 obj +(For Advanced Users) +endobj +77 0 obj +<< /S /GoTo /D (subsection.3.2) >> +endobj +80 0 obj +(Coaster providers: local, ssh, pbs) +endobj +81 0 obj +<< /S /GoTo /D (section.4) >> +endobj +84 0 obj +(Swift on Diverse Infrastructures) +endobj +85 0 obj +<< /S /GoTo /D (subsection.4.1) >> +endobj +88 0 obj +(Beagle) +endobj +89 0 obj +<< /S /GoTo /D (subsection.4.2) >> +endobj +92 0 obj +(PADS) +endobj +93 0 obj +<< /S /GoTo /D (subsection.4.3) >> +endobj +96 0 obj +(OSG) +endobj +97 0 obj +<< /S /GoTo /D (subsection.4.4) >> +endobj +100 0 obj +(Bionimbus) +endobj +101 0 obj +<< /S /GoTo /D (section.5) >> +endobj +104 0 obj +(Debugging Swift) +endobj +105 0 obj +<< /S /GoTo /D (section.6) >> +endobj +108 0 obj +(Log Processing) +endobj +109 0 obj +<< /S /GoTo /D (subsection.6.1) >> +endobj +112 0 obj +(Make a basic load plot from Coasters Cpu log lines) +endobj +113 0 obj +<< /S /GoTo /D (subsubsection.6.1.1) >> +endobj +116 0 obj +(Make a basic job completion plot from Coasters Cpu log lines) +endobj +117 0 obj +<< /S /GoTo /D (subsubsection.6.1.2) >> +endobj +120 0 obj +(Make a basic Block allocation plot from Coasters Block log lines) +endobj +121 0 obj +<< /S /GoTo /D (subsection.6.2) >> +endobj +124 0 obj +(Problem Reporting) +endobj +125 0 obj +<< /S /GoTo /D [126 0 R /FitH ] >> +endobj +128 0 obj << +/Length 277 +/Filter /FlateDecode +>> +stream +x??Q?JCA ??W??^Lv?????????J/ZZ??"?}????X?>??endstream +endobj +126 0 obj << +/Type /Page +/Contents 128 0 R +/Resources 127 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +>> endobj +129 0 obj << +/D [126 0 R /XYZ 56.6929 815.7613 null] +>> endobj +136 0 obj << +/D [126 0 R /XYZ 56.6929 759.0684 null] +>> endobj +127 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +143 0 obj << +/Length 2501 +/Filter /FlateDecode +>> +stream +x??\]s?6}????5????c_v??????dcw????,??6??Rr??? ? +???8?v??I?XG??? ?^?"?H!$???B??$?X?/p?h????8??]????????0?H*???BR$?? +1CUq{???????~vE?|QU???????????B??J?|??????"!h?????^|{?x&??? +??.~????q?I???#? +)??????7????F??R?8?b?Y?d?? BD3???K$??4^T?}???F'c??q??w?Gy;??qPQ?Q +dvE0??????,??????1%b??4SG???PY*6?\?c.#~?? a?{?b????M?"U^?w?EB)???#R????,????? ???l??3?q??_??4-?Q[G?Vv??ov??j5?/?M?fl?)9bt???!\#???3A?+a#2?|? 7?} ?@?O(???s:?H??E4??]k?nd??a??$??H?F??!E???P?R?M +j=??.?????n?/??A)??El#? +??P!Z"???L?~???<?H?`??2???r#5?z????j'J??>?Q????n??~?y?6??m??????i???m?? ?b??"&?&?Gex??9R?yN?~?|M(xQ"??KG?$d????7?A??k??4k???oN?u?Y?c??}??9q4 ??-),??`2?????X#I??3??? /?R??I?W:ZF???c???.?%D(?@^??I??????f?P???h?????zL???J?"6? +??2,?`??E?yN>Y?`r??????cr???r {H1?????rfCr?J?E???????r)?Ha"??z?f????L#???I??j?I?m0&?hmCF?^?G?Kk???????????^%'qC??$g?$?QN???k?g5??3? +[?v0l?h?CF??Q}j1*?D?p?????b????????fQ/?i?)q?$?"?????2???5?6??i???R?&?(!????5?e? =?;cO??h???T??%??????|F(?????? +?&*??(?c?Oj??gJ???b??t?L@F??psV?LxT??w(?K???|s?Zn??????~?vh "????gZL?%?? }r??????):?t???!?g/?\?? ?V|@uB?N????;?/??{?????q???-(?Elw`?w? ?????M????>?C:??LG??4z???%o?????r????=?C?;w%???nKw"?j?????w?}?3o??????5?????{?Gef@?F????$yH???#u?~OGk???? +=??q?3'?????????????v?????????_?m{?O?>)%E?h?8T?nh???NR????-?0l?hM??x&@F?m?s?? +n????p????]???lcgF +fE?)???C'.*P??E ~:ZfQ???????1Bgr??????b??7/o?G? ?F?"}??7???8dI?b???j????H)??T&??h??xi??y???????% +??C??HG?$ +h????J??,?(?%??#?zYm?????OiS?i??bElb??Y??0!? ?x??$???1??E;J0??h????[?Q????+???z?]??????1\?~n?S? eEl+???Q +~?9???h??a???? 1p?G5??s??*??7m?Z-??z_?j?~ zD-Y5*?(?#?D?X?J A??W???zT??P??8?V??k?w?W1t????k?nW?????2??????*?Bz?j?XF9?2?????\a??b"???O?`Hh)????#zk?wj?endstream +endobj +142 0 obj << +/Type /Page +/Contents 143 0 R +/Resources 141 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 145 0 R 149 0 R 150 0 R 151 0 R 152 0 R 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R 163 0 R 164 0 R 165 0 R 166 0 R 167 0 R 168 0 R 169 0 R 170 0 R 171 0 R 172 0 R 173 0 R 174 0 R 175 0 R 176 0 R 177 0 R ] +>> endobj +145 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 706.3558 113.3799 715.332] +/Subtype /Link +/A << /S /GoTo /D (section.1) >> +>> endobj +149 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 678.4604 123.8304 687.4366] +/Subtype /Link +/A << /S /GoTo /D (section.2) >> +>> endobj +150 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 660.5476 140.3783 669.3942] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.1) >> +>> endobj +151 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 640.5575 178.8938 651.4615] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.1.1) >> +>> endobj +152 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 622.6248 186.3259 633.5287] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.2) >> +>> endobj +153 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 604.692 204.239 615.596] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.1) >> +>> endobj +154 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 586.7593 248.0736 597.6632] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.2) >> +>> endobj +155 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 568.8265 233.6979 579.7305] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.3) >> +>> endobj +156 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 550.8938 193.8574 561.7977] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.4) >> +>> endobj +157 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 532.961 161.698 543.865] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.3) >> +>> endobj +158 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 515.0283 171.093 525.9322] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.4) >> +>> endobj +159 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 497.0955 210.1262 507.9995] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.5) >> +>> endobj +160 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 479.1628 175.5165 490.0667] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.6) >> +>> endobj +161 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 461.23 263.2368 472.134] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.7) >> +>> endobj +162 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 443.2973 197.7727 454.2012] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.8) >> +>> endobj +163 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 425.3645 162.2866 436.2685] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.8.1) >> +>> endobj +164 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 399.5065 109.7037 408.4827] +/Subtype /Link +/A << /S /GoTo /D (section.3) >> +>> endobj +165 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 381.4741 177.0411 390.4403] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.1) >> +>> endobj +166 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 361.6036 227.7101 372.5076] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.2) >> +>> endobj +167 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 335.7456 209.7673 344.7218] +/Subtype /Link +/A << /S /GoTo /D (section.4) >> +>> endobj +168 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 315.7755 123.2131 326.6794] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1) >> +>> endobj +169 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 299.9 120.0951 308.7467] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.2) >> +>> endobj +170 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 281.9673 115.4724 290.8139] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.3) >> +>> endobj +171 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 264.0345 139.0835 272.8812] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.4) >> +>> endobj +172 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 234.2163 143.0086 245.0954] +/Subtype /Link +/A << /S /GoTo /D (section.5) >> +>> endobj +173 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 206.3209 136.9314 217.2] +/Subtype /Link +/A << /S /GoTo /D (section.6) >> +>> endobj +174 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 188.2537 299.9385 199.1576] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.1) >> +>> endobj +175 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 170.3209 374.7175 181.2249] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.6.1.1) >> +>> endobj +176 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 152.3882 387.4395 163.2921] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.6.1.2) >> +>> endobj +177 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 134.4554 171.6511 145.3594] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.2) >> +>> endobj +144 0 obj << +/D [142 0 R /XYZ 56.6929 815.7613 null] +>> endobj +141 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +181 0 obj << +/Length 4471 +/Filter /FlateDecode +>> +stream +x??]?o??????]?3H?KR%(?????????H?@??????D??????x?%R?v? 0???xz?{<??& ??E??i??H?RF???? ^\???N??Yk??-?????/??Q?([?].E,??"?)?r?.?6?.O????jM????????????O?"?OY???? ????' ??,??????w'_???YiNP???[??????? +????8???n0?qN7' ???Q?d{rz?]?Q??1?q????Z??$???????$I?ftA(? I??? -&=??2?fY??H-?t?q?on?f?&xy[?+?,?T.??????4C?0??g?U Y???Bg0?a??zn??e?$nW4YMU?????????v?s??????J*j??A???q/??F?m???y?K?m?G?rSqXmI?????1?:6???w????-7???I??u? ??muQ?y?@???JD"p s?~9VMyS?\'8$M?WR<?m???1w??)?Cs?8??E?u?SHX%?????=?7??E}?o?V???/-??????o????X\??NY????D?Eb???????????K??u#?u?;4?l??{???8?MUl??????q????M?G????e +?3??(?PQX?$?uS?~??W????bm??-W3w??lJ??(G??@??A54R!\G?ESQ?%)?Q?6??'?1I????D????n ?Z??E;?5e?<xmI0J?????b?k?D????O??Z(?(???v???nE? +????????V??"??B~s(???*??]??????uS???M)/*Y|??EODe?Ra?_kyh?x?P?WI??![????)xWm?J??h?????7)Y??R??:???? =?Az???Ngs??=??? ????I5Y????@u??tw??????H?J?C +?^_ ?????@??_?????>?./??6????"c)???q?e?R?Pvh/rQG Ay5??_q??!J?l?K?e??\\Z?]???=B?&???????j?*#?????O??C???,UQkW??{.?w?????2????`??`?dc +???B^|????I???c3c;F)^?? +Kt]q +=H[???Ei??b)?????b=???r?4?MJ?c?<??$d???????? e)a?a?Q????3r? ???1/?Ip?5om?B??6??!$?o&???Z>?/?%F4C 2??????KSh?D$??)?=r$c@?H?K?QI? QRJf???rb??Zln??=q???&???,V @]t=D4qh??]t?b;ZE5:?????I?w?HP?P??d*%?H@???? +?R>?N?A?I&?3D?8!M?7???l?!a?C?????0n%?'?k)?]M2M;?`?????3v??H)D?;n?B?R.?????0Bf{????B?????0??^k???m?kC?gz?5x?H???3?F?5??pJ?W{(?}?????? ???????w?;M????2??2????????6,?Q??]J?6k??n???f??H?4~?'?~??1 +?-%?&???k??b;Z?? ???O? /??^?M_r??]??=?:=???>??n?V? +z?S??)???Y0?*!??????m????????????8?????K96(?#????^w=K???m?? H??|??Ah.???bz?????/???fb?m????????vn????m???,W??????%??S???o? ???vm???x?U?C?????@Az[??T?A?gQx???9$%?@:?s-2??;??F8????s#?u???~`"(?)?????;zE????QDf, x??B????(iX???Y??2~s?a???eh? ??3??? ?i? ???????0????g7{^dW?TX??=?9?? ??3??????[?G5?~???a?d?g$}ft +??????|Zy?? +??efz??o???M;-??ur????"%^??qZ?????$????&????kL76????V???7y???/#?=?1?+???g?%{????????<4n??????N??????P??A ?3t}?i??\]? +G?D???cH????T?? +?M.????Y?r???????>%????0??SqM???5?GjQ?m?]?4#????R?u?T???o???,"???.9!???Gr??IV??q?JV?y#C???Hsu?K?y*'%@Q??F???Fp??g????A????????g?q"?\??W???vS??? /?mS?{y?;?C??S?ry~???????H~???F??M?????eS?X??)???????8??C5??:e???;AK?7???????q?=Q?Y??NnX???FJ??????????nzu?T?????u?-???)~l=???~6???c?u?????5;z??????pf?@???H??m???i????l??|~?W?}??\????,| +?J9?m?>j??J<?V]????=z????:E8b?~O?? +_y???F?????Y??(ZD?O?d???(Q?M?E?C??9?.g9t????_D?t??L????KA[??`] ??+???????u???I???(????Q??OH??B????,)???Z??????#3??|???i??????????????????gqp?x!??????8=?vE?_?B?+?Q?B????b6????E??Gxx?m????J\?\??{?F??? {s????wE?@?T???TQ????\Ex)???7???????????????eVd?jQ,?4=??@1N?8K7??`?xa?w??U=???Yw5??? endstream +endobj +180 0 obj << +/Type /Page +/Contents 181 0 R +/Resources 179 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 184 0 R 202 0 R ] +>> endobj +178 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (/autonfs/home/davidk/dblatex-0.3/latex/graphics/warning.pdf) +/PTEX.PageNumber 1 +/PTEX.InfoDict 210 0 R +/Matrix [1.00000000 0.00000000 0.00000000 1.00000000 0.00000000 0.00000000] +/BBox [0.00000000 0.00000000 160.00000000 183.00000000] +/Resources << +/ProcSet [ /PDF ] +/ExtGState << +/R7 211 0 R +>>>> +/Length 212 0 R +/Filter /FlateDecode +>> +stream +x??R;N1 ?} +????? ?f?,?l?Rp}?L2?@??_^??m9o??}??o?xV??C??0??|?? ?rf "??p????W??~???+}??????r??"??M??3?\??!?4K)?~????Vvfm???5~??[G#?6??y GI?7??????????)endstream +endobj +210 0 obj +<< +/Producer (GPL Ghostscript SVN PRE-RELEASE 8.61) +/CreationDate (D:20100125210321Z) +/ModDate (D:20100125210321Z) +>> +endobj +211 0 obj +<< +/Type /ExtGState +/OPM 1 +>> +endobj +212 0 obj +252 +endobj +184 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [321.5267 691.4354 340.6647 702.3393] +/Subtype/Link/A<> +>> endobj +202 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [444.2645 336.0762 463.4026 346.9802] +/Subtype/Link/A<> +>> endobj +182 0 obj << +/D [180 0 R /XYZ 56.6929 815.7613 null] +>> endobj +6 0 obj << +/D [180 0 R /XYZ 56.6929 759.0684 null] +>> endobj +183 0 obj << +/D [180 0 R /XYZ 56.6929 731.2722 null] +>> endobj +10 0 obj << +/D [180 0 R /XYZ 56.6929 677.8333 null] +>> endobj +185 0 obj << +/D [180 0 R /XYZ 56.6929 641.7915 null] +>> endobj +14 0 obj << +/D [180 0 R /XYZ 56.6929 641.7915 null] +>> endobj +186 0 obj << +/D [180 0 R /XYZ 56.6929 615.3924 null] +>> endobj +18 0 obj << +/D [180 0 R /XYZ 56.6929 574.9607 null] +>> endobj +187 0 obj << +/D [180 0 R /XYZ 56.6929 550.1206 null] +>> endobj +188 0 obj << +/D [180 0 R /XYZ 56.6929 500.6172 null] +>> endobj +189 0 obj << +/D [180 0 R /XYZ 56.6929 502.0767 null] +>> endobj +193 0 obj << +/D [180 0 R /XYZ 56.6929 491.1178 null] +>> endobj +194 0 obj << +/D [180 0 R /XYZ 56.6929 480.1588 null] +>> endobj +195 0 obj << +/D [180 0 R /XYZ 56.6929 469.1999 null] +>> endobj +196 0 obj << +/D [180 0 R /XYZ 56.6929 458.241 null] +>> endobj +197 0 obj << +/D [180 0 R /XYZ 56.6929 447.2821 null] +>> endobj +198 0 obj << +/D [180 0 R /XYZ 56.6929 436.3232 null] +>> endobj +199 0 obj << +/D [180 0 R /XYZ 56.6929 425.3643 null] +>> endobj +200 0 obj << +/D [180 0 R /XYZ 56.6929 414.4054 null] +>> endobj +22 0 obj << +/D [180 0 R /XYZ 56.6929 378.6212 null] +>> endobj +201 0 obj << +/D [180 0 R /XYZ 56.6929 352.0227 null] +>> endobj +203 0 obj << +/D [180 0 R /XYZ 56.6929 320.0948 null] +>> endobj +204 0 obj << +/D [180 0 R /XYZ 56.6929 321.5543 null] +>> endobj +26 0 obj << +/D [180 0 R /XYZ 56.6929 285.77 null] +>> endobj +205 0 obj << +/D [180 0 R /XYZ 56.6929 261.7619 null] +>> endobj +206 0 obj << +/D [180 0 R /XYZ 56.6929 229.2362 null] +>> endobj +207 0 obj << +/D [180 0 R /XYZ 56.6929 230.6956 null] +>> endobj +208 0 obj << +/D [180 0 R /XYZ 56.6929 175.3142 null] +>> endobj +209 0 obj << +/D [180 0 R /XYZ 56.6929 176.7737 null] +>> endobj +179 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R /F90 192 0 R >> +/XObject << /Im1 178 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +215 0 obj << +/Length 4909 +/Filter /FlateDecode +>> +stream +x??]mo????_??~??,?W?:4?6 +?^S????|???g?vW????%?Q?H??]??n????h??3r?4ZA?/Z? d.V1?g??6? ?z+???i??!Z?T_?\\???U? g???U?A?C??0????f????????Zc/?4????]?t??x??x5#?U???????1????k9??V???]|uc?2b??a.???????j+t??Zp?z?@?i?V? ??#???dw????G?-??B????R?a??@????????Q?Q]!v????js?U?????UON??6m}???A?,??]?????5'M?#d??l^??M????#???I?uw??????+?.??[?????????????"?? ????6?P?????E[f#?W??U[?n???_??&F`??????l??,???T/?3???x???? +?4H??b????}?I??&???????d6/4 p??]???????@YQX{)??td/?J???7??????????%P?x?1?????M????Ubw?)?p!???Z?????3?@?t?(_???O?+:>???w?'?"??j3 at r?Mj""?$??M??]B9@ ?E6?O???3tci???&2b9 +?"?K?@????????X8l,} +???? ??H? g??T??????}?I ??? G?ypB??E?I?K?H?,?eE.Fs??1??? ???c3 ???2.?p(g??&J?z??`??:????k???? +?????]?F??M??"*?Q????????X?fNUDf" ???%C ?K?Z??;????????????8????????/???u?v????1A????So[?E?YP???/E/???,?w?gWk??? +??z???R?]??????g???6??l=?ZS?D?(zxy,?;?????o4?F*?K?i???m????+V(??G??H???o?[?p???6????2v?+%??? +k?Y$?? ?}?}L??e?????Lt?k??P?v??4???????Y +???c?????@??gz??F??W?????e; ?7?Z???i???Xn????4\?????R???N????D???c?E1?p??P?#1?YY"98?z5?ol???? +?????N??E???_??????"??dO~?????_????????A81j&V!Y?V? ??p?1???,???6??@9???o?????18?sM?? 9"? ?Vn??I?????1 "F0^???I?_????a??fb?%???????H?)??? S1?????L????~???V?'?9?? K????4?????Fo??|1?Q????V??kR?/?L??xT?y ?YbD?y?a???>?k????i??tlLf?kF58:?"???a?Ef???????(?d???3?{?X?????-?X?l???4??t23????x?y???T??V?Y?y?? MJp??N]?O?jS?>z?=???l?zs?+?????uw&[$G?V???????B??2 n??7Pa???N??E,:8$?7P??*??????5?????J}?ne??? ???}e&??8?v??o??j?? ????????1S?}k*?????I??o??T????0??T??o?>>?? +??????N?{[???}???>?!?A/6?Df_p[???>.CO<{?'???5x??O??u +y?S????g????"???J???f?a???*[?$??o??W??eJe??l????3?????[?!?w???a?C2[R?????C??u#????1???u xs?n?Vj?-8???QM????< +.??-?????mi????Y?????Ce?n?z t?*?!?E??B?GpAU?9?(???#??m??^?D?u?!1T?W`?4?"??y:?=??&UAeL_^???$??6???P?? +U ?????y?????(????M?'3?!'?u?!??|?1&??G?G%p?&?? ?? #???v????? ?w???????S^?j?m??j? + ?)???gN'[?ypqqX???Z[?P???%???u?????'??i????*??s?????????*o???S?}iK???????N? +?:Frv??????}L???? +??SW?s??l??L#??8??-???.HW??{? |u?e??`?8??M'?=n?a?:N?\sC????tG??f?????&X??y??????S? ?0zC????1??b??F?]b? ?)_ ??}????m"???W??A??(?s|N8|@?v?8b?????>q?x??u??M?H?ni????k?q?|??c?lQ?EXfFv???3]??#?k????m??????,???d???Q7&&?\? f?+#?^??w$????u\k??(????g?C??????{F??;j?Q+T????&?F?y%%??????o?>? ??II?R?6on???????? r??k??wSB)?,?>Ry??? K??t?q???o?? ???HN???????#??P=???????G??+Y???Dx????b??+J???] ??G?1?F?QIy??????-?L?&vD Qhv5?if?qe?F???[?E?????mo?? +an?p??uW????? +??t???dT"a??3r????#Ny??)?????*/?@?????Y???a+6Dj1,S??q5%??"??|?["o?????_??\m???????Co?X??_ ??Ov?/????8??F?Iendstream +endobj +214 0 obj << +/Type /Page +/Contents 215 0 R +/Resources 213 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 233 0 R ] +>> endobj +233 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [548.7873 407.9685 567.9254 418.8724] +/Subtype/Link/A<> +>> endobj +216 0 obj << +/D [214 0 R /XYZ 56.6929 815.7613 null] +>> endobj +217 0 obj << +/D [214 0 R /XYZ 56.6929 742.9593 null] +>> endobj +218 0 obj << +/D [214 0 R /XYZ 56.6929 744.4188 null] +>> endobj +30 0 obj << +/D [214 0 R /XYZ 56.6929 710.1122 null] +>> endobj +219 0 obj << +/D [214 0 R /XYZ 56.6929 687.1371 null] +>> endobj +220 0 obj << +/D [214 0 R /XYZ 56.6929 608.8432 null] +>> endobj +221 0 obj << +/D [214 0 R /XYZ 56.6929 610.3027 null] +>> endobj +222 0 obj << +/D [214 0 R /XYZ 56.6929 599.3438 null] +>> endobj +34 0 obj << +/D [214 0 R /XYZ 56.6929 449.3441 null] +>> endobj +232 0 obj << +/D [214 0 R /XYZ 56.6929 423.4797 null] +>> endobj +234 0 obj << +/D [214 0 R /XYZ 56.6929 393.02 null] +>> endobj +235 0 obj << +/D [214 0 R /XYZ 56.6929 394.4795 null] +>> endobj +236 0 obj << +/D [214 0 R /XYZ 56.6929 383.5206 null] +>> endobj +237 0 obj << +/D [214 0 R /XYZ 56.6929 372.5617 null] +>> endobj +238 0 obj << +/D [214 0 R /XYZ 56.6929 361.6028 null] +>> endobj +239 0 obj << +/D [214 0 R /XYZ 56.6929 350.6439 null] +>> endobj +240 0 obj << +/D [214 0 R /XYZ 56.6929 339.685 null] +>> endobj +241 0 obj << +/D [214 0 R /XYZ 56.6929 328.7261 null] +>> endobj +242 0 obj << +/D [214 0 R /XYZ 56.6929 317.7672 null] +>> endobj +243 0 obj << +/D [214 0 R /XYZ 56.6929 306.8083 null] +>> endobj +244 0 obj << +/D [214 0 R /XYZ 56.6929 295.8494 null] +>> endobj +245 0 obj << +/D [214 0 R /XYZ 56.6929 284.8904 null] +>> endobj +246 0 obj << +/D [214 0 R /XYZ 56.6929 273.9315 null] +>> endobj +247 0 obj << +/D [214 0 R /XYZ 56.6929 262.9726 null] +>> endobj +38 0 obj << +/D [214 0 R /XYZ 56.6929 228.666 null] +>> endobj +248 0 obj << +/D [214 0 R /XYZ 56.6929 205.6909 null] +>> endobj +249 0 obj << +/D [214 0 R /XYZ 56.6929 177.2885 null] +>> endobj +250 0 obj << +/D [214 0 R /XYZ 56.6929 176.6907 null] +>> endobj +251 0 obj << +/D [214 0 R /XYZ 56.6929 165.7318 null] +>> endobj +252 0 obj << +/D [214 0 R /XYZ 56.6929 154.7729 null] +>> endobj +253 0 obj << +/D [214 0 R /XYZ 56.6929 143.814 null] +>> endobj +254 0 obj << +/D [214 0 R /XYZ 56.6929 132.8551 null] +>> endobj +255 0 obj << +/D [214 0 R /XYZ 56.6929 121.8962 null] +>> endobj +256 0 obj << +/D [214 0 R /XYZ 56.6929 110.9373 null] +>> endobj +257 0 obj << +/D [214 0 R /XYZ 56.6929 99.9784 null] +>> endobj +213 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R /F98 231 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +260 0 obj << +/Length 4318 +/Filter /FlateDecode +>> +stream +x??]m???????=8/pf?*J????k{?pm/????????xm??????%E??D??8?/????y?_??? ?d&2????D ?6[=??????7??YX??/??7??xV?"?????,?(?X?r,+???X???X??? *?????????W/?QE?,WE3??r)D>[? +!hS??b2??3/??r7??xYZ? ? ?kV??y? +????on0?ENf???(/???F??e?~????????[???~Vh?)Bd?g&y?????Li??h?3??i?) +???f4???? ?W?????D?O?y?M?}?:V???-??Um"IT.(E?$?Q??[B?|>???cz?c??????????q???T?,H?8??F?????~?6?N?]U?5?W?r????7K???Nm????|0??]??x????????????~??n?vu????????|v,gw^?k???6??? +? +8?f???l??)0?\??*????a??h9UQ???????Y2??}{??'?}??????~f??mhl? +?G?:j???????I????~?S?.?j??u?? ?dQ??2??P?6???ux=n??????z`&O??(?d??Ju???????P?p??R?R?*Y?_?f2????1??7=???35o?IT??l???:?????+5???v?Uco?e?bH??????V5b08W$?c +??v_k3?V?u`1Q+n????&;)7?6h4?QA?X??<???????}\TgU.??Rl?m?j)?????C?????z??6h?T???????Cm??SB??????<?????}@??(?^h?j+????f\-R??F??x_??~?????0P2j.???R?????R"????Vo????a?H&?????P??? Hp9?o;y??W???Sh6#g????m? ?@???,C?+G|??V????Ww?????h???4G?f??n?A?????7?=?(?0?;)??I?? ??'F?N??j???j?3?rT??`[9h4?D}??6??C?Fl?h?Y?T)?u??????OhS?('E??V*????z?M?$/????*W?}?#NP???$???A?v?M? ?Q?F?????q?*??){?j???(7????S4B????! +F?g?9? ?Q??/?l?R?????_????v_??4|??r<x???O????P???Z??h?N +6r?g???8?=_. ???.??W??????+U???????YvQ? +??e??J/?<]???J?r?.??`?wk?????HIjv??3?/??5??? +? +????"??@??V?7rlD?????I???8?P1 +???`?}?s ?V*?w???+??K????[???f??????)??C????ry???????=?gL??? ?H?>f??V7b=?#????O??R.~e???+}z?}? ??ET???`?\UH?!??j????????f9 +?8???V??kv??!|?$??IR?\;?@????]?o???~?$}}???4j?K?>7A???B-?9^d???.?l?R?Ws?i?????a????? ?@ >u?i??t???"??T???cVH???????t??????9)sGy??F?_O?????Y??S?????E?;BM????eQ"?4?L??G??p??`????T????n?!????F?????????????aq???Qu(?T?3W?u ?? ??>?C??s???6O+l????B?Q????Rcx?W?3???I????? +???y]???=>??/?/?????3?????????/?jn???????????L???B???Z-???\??5?o?????<=?&??????0&D?w???????L????l??N???????oJ??T???W??[27?3??j??E?z?f?o??9Z????3?16L?????m? +?rWzB????-?????f???l?????????F?T0\-?n??x???)Y??I???S??4??@e???\??%cS??nJ?n3pNl2??N???1?g????-UU?}? ?? ???)[v?B"????e??G??,/???s??j6???=$???C??Ww?#`????l???*???bER?N +?m?z???hTF0>??? ??G?L"!????t?Y?e?ZN?L????25B??DS_??mctAG?PIx7B???*a?;G???9??}??"Y? (h_[[#$?\?,?'?+?k?????eB??????????????)X?UA?i?JE?d{??682???????4?6??A?tW??v?>??#?[p???6?P?Q??????n??(PY?u:?R*LK??? +?f??p^??@?T???.[}u??4]?w?? ???[/?e$n?%?-?????>?/??X???A????`3?v(???? +R?y!*m?|?l??k??D?h??E?P????S*6:?C????/?? sY???? +?B??I{P ??????????4M??????>??G8?XH??s???!???jvO"?:?3??=??>V?Vo?????|??)?e???H?/w?^??C?v?O????n?x??V?8U?@_ot?`???v?? +???C??X?p?O >\?????aoN*.J?I???G???5Nfy??% t????K?b??????B?U]R?5??xX???jW??=?@?S?6?????K?!?|]??????? ??w???~??p?*?Q?=????????w????v???????)?4????jP?>j&???JU?3????9???9 +?W??7?3T?Vw^??v??????oM??L +?Z?g?h1?T???[???y[W??X.?:I??hy\m??\?g????l_[??????7??jy*?G???R8???q??Q??R'?x??I,?'o?c}??BRK?`???/-?jgMY+?????k?M.?6?V??f??????U=?[2o????> endobj +283 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [216.7201 469.032 428.9318 479.9359] +/Subtype/Link/A<> +>> endobj +261 0 obj << +/D [259 0 R /XYZ 56.6929 815.7613 null] +>> endobj +42 0 obj << +/D [259 0 R /XYZ 56.6929 759.0684 null] +>> endobj +262 0 obj << +/D [259 0 R /XYZ 56.6929 738.4887 null] +>> endobj +263 0 obj << +/D [259 0 R /XYZ 56.6929 703.155 null] +>> endobj +264 0 obj << +/D [259 0 R /XYZ 56.6929 704.6144 null] +>> endobj +265 0 obj << +/D [259 0 R /XYZ 56.6929 693.6555 null] +>> endobj +266 0 obj << +/D [259 0 R /XYZ 56.6929 682.6966 null] +>> endobj +267 0 obj << +/D [259 0 R /XYZ 56.6929 671.7377 null] +>> endobj +268 0 obj << +/D [259 0 R /XYZ 56.6929 660.7788 null] +>> endobj +269 0 obj << +/D [259 0 R /XYZ 56.6929 649.8199 null] +>> endobj +270 0 obj << +/D [259 0 R /XYZ 56.6929 638.861 null] +>> endobj +271 0 obj << +/D [259 0 R /XYZ 56.6929 627.9021 null] +>> endobj +272 0 obj << +/D [259 0 R /XYZ 56.6929 616.9432 null] +>> endobj +273 0 obj << +/D [259 0 R /XYZ 56.6929 605.9843 null] +>> endobj +274 0 obj << +/D [259 0 R /XYZ 56.6929 595.0254 null] +>> endobj +275 0 obj << +/D [259 0 R /XYZ 56.6929 584.0665 null] +>> endobj +276 0 obj << +/D [259 0 R /XYZ 56.6929 573.1076 null] +>> endobj +277 0 obj << +/D [259 0 R /XYZ 56.6929 562.1487 null] +>> endobj +278 0 obj << +/D [259 0 R /XYZ 56.6929 551.1898 null] +>> endobj +279 0 obj << +/D [259 0 R /XYZ 56.6929 540.2309 null] +>> endobj +280 0 obj << +/D [259 0 R /XYZ 56.6929 529.272 null] +>> endobj +281 0 obj << +/D [259 0 R /XYZ 56.6929 518.3131 null] +>> endobj +282 0 obj << +/D [259 0 R /XYZ 56.6929 507.3542 null] +>> endobj +46 0 obj << +/D [259 0 R /XYZ 56.6929 444.7788 null] +>> endobj +284 0 obj << +/D [259 0 R /XYZ 56.6929 417.8872 null] +>> endobj +285 0 obj << +/D [259 0 R /XYZ 56.6929 398.9923 null] +>> endobj +286 0 obj << +/D [259 0 R /XYZ 56.6929 400.4518 null] +>> endobj +287 0 obj << +/D [259 0 R /XYZ 56.6929 389.4929 null] +>> endobj +288 0 obj << +/D [259 0 R /XYZ 56.6929 378.534 null] +>> endobj +289 0 obj << +/D [259 0 R /XYZ 56.6929 367.5751 null] +>> endobj +290 0 obj << +/D [259 0 R /XYZ 56.6929 356.6162 null] +>> endobj +291 0 obj << +/D [259 0 R /XYZ 56.6929 345.6572 null] +>> endobj +292 0 obj << +/D [259 0 R /XYZ 56.6929 334.6983 null] +>> endobj +293 0 obj << +/D [259 0 R /XYZ 56.6929 323.7394 null] +>> endobj +294 0 obj << +/D [259 0 R /XYZ 56.6929 312.7805 null] +>> endobj +295 0 obj << +/D [259 0 R /XYZ 56.6929 301.8216 null] +>> endobj +296 0 obj << +/D [259 0 R /XYZ 56.6929 290.8627 null] +>> endobj +297 0 obj << +/D [259 0 R /XYZ 56.6929 279.9038 null] +>> endobj +298 0 obj << +/D [259 0 R /XYZ 56.6929 268.9449 null] +>> endobj +299 0 obj << +/D [259 0 R /XYZ 56.6929 257.986 null] +>> endobj +300 0 obj << +/D [259 0 R /XYZ 56.6929 247.0271 null] +>> endobj +50 0 obj << +/D [259 0 R /XYZ 56.6929 212.0137 null] +>> endobj +301 0 obj << +/D [259 0 R /XYZ 56.6929 185.9542 null] +>> endobj +54 0 obj << +/D [259 0 R /XYZ 56.6929 141.8097 null] +>> endobj +302 0 obj << +/D [259 0 R /XYZ 56.6929 114.9182 null] +>> endobj +258 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F98 231 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +305 0 obj << +/Length 7113 +/Filter /FlateDecode +>> +stream +x??]]w#7r}???C4'V????S]???ox3{w7kx??e=???=og???_?quwxs????????[????}#??f??j#?W?????????k~?j%??v???L??]??;?ei?=+D?;?????,gK?7WeQ??}??( ^?l?pU3?Q4??f}???_?G?W^U???W??4?@]7?5k??`e?&???c%}?? +??P[??u???5" ;V?}_????ox}?Q'??????????????mw??j? MW?asX????5?,???v?????0_?????dF????qe=+??Z+&O_Y ?]Y???g{eY?_/?[uMY???????????????q?0v???,?????????7????????????????a?????dJa?5????????z7??????7??W?????&?????v???? ??=??I????!???O??x8??.b'{H-?cwF????Mw??,Z??K[???e"??????Uk??????vL???/??????`"]????? ?w??? ^??q4j???????/???8?ltu?P?.??(?R?Y+ +9?????j???E?}S????????Xh?>d1??)Y? q?M???+;??]?2?nX?xW?^??XD~???m?]t D?u??????Q ~R!??26???,K???8>6[#??g?[??x???`L +i??OV"0???0?S?0?!?(???(\?&~|o +?&????e?E?gcO?G~?????H?T???B????)???????[{ +^????l?A???x???h?\M??????]?-9`?????? +/es???2`??StE?z? ?j??Z?&??_??-???j9?????:???????o?????(??}?x???? V?@?#????#? +???Mz?F?vC4?yC?l??' +??[{????C?Q?u??????lH]}?q?hT?m?5?l???d?N??[m????????JF????0???Hn???>Pvn???%?V-??J?? +XQ??? +??K?h?????????Z? B??d$??&??*G-&=??J???H????U?^?????/Y?W??(?2?|?m?Z????'???Z?9DE?$cO?G~?5??????0?=?&?}v????????1G?1?G5j????????S???/:o5 v????????m[?????????FiH???h??'. at +???+???M??=c-??x?.?q?iG6r?5j?????Ft?S???G ?????7??3???TW?~f????P?cW?a????:=?o??????l????v?.v??{?K??J~????xd/?B??Z? )?Z????_?????R???n???(K??????!?????????R?????W????????a????x#3?Y?????e????k???^_???u?S?l?Bz????_?V???0? ?:I?C5???Z?R??S????,?:????+????I-?x????vCh??8??8????f????O??z???9,?2v?|s??v +?[tZJ?? +???]^#+ ?'? ???Z +??7????O????g?eY?f?8^M???K?????T+;U??K?^???3?,/?H???v?{??/Z?????@??hU?1"pOfC??>7Wz????????7??I?7????>C?????'gp??[F????=i?Si???]???????(CWz? ?Jo,G??F?]??)???y?^??/~??2?.???^?9?7?Jo???8f?[J???|???t??p?Ks5?vZ?Q$?xTu%??????o?^&????$??????v???n?(=??}????Mb??8 ;??pv??|v?a?A????r?p?A?Op~H?A?37??33Z>????cz7F??XcW??o???????@???u?M>h??J?l.[c^~\?2????J???m??[^tB?y????vg???i?:d?V?n?u?&?|zng +????/$??DH??*y?? ??a? Qwe???o??a??,;1"?L0{?V???PV?N1?????6? .??^??~%s%o??????????8?M[T5og?'?MYkx?S?? ????x???;?.??????I?????*??f1???r????????Pvp??????i??fvF&(iS^??H?/P??v?9?o??????? .?S?(????B??????n?(???i?u??'O?#4?50?!??;???y=??U????u? + ?.E%???p?9?????u\?_-????f??vB ??????????8?????B?????w??w?*??????V?E?3} +??-?}y-?9I^???6?K???????????2??????iOio?@??????nXl?7??7z/???hB?_????W?v8m??????????}?o????"??y?q?????&?~1???s?????6???Q?????????x]wf??!P???U!K?R-??????gD?^WAl??F?c9?zF5%????? ?M4????? +?????D???U??+k?D?A???y?-??\???t??gIh7????q`??>0"??r??y???(84f9r???w???}??yM?? +V*?O?w?WVG?#? +??j?L>y +??J ? +????u?cp3#??uq???ir?6-Z??=?????J???yQ?S{)???S??E??L?k????????A#vsp???d???%3f??99)?????p`??B??????N^????+tS???34E??L??;?v????K???W-??????Vv?ZfN?7 +??p ?yX?^??m?(P? +<?;R~e??/???.v????[??fx??????M?`?(??m?#??|??Tr/???????????fp???dCwUK^?^5D?????0??h??"????h?r#??ZY??u?????#????K???l?????kY?_6*?.R?T?d[R?Zi)?????????cG^?a??????????8?VS?e)X?G67?9??ks?8????<~?/l??????a#_?a?>??mS???????????REX??[W????LV~f?O?p???wnV??a5_??6q?????a?F?a???N.=??(??b???????D??X????6??P\??|\??9?w???????????????"??4-??SWs??iY?????c?p|8(`???&?k ?????`i???V=o?9????=???hV???=?=?K_??rff?-?? ??? +?[u?????a> ???G???????~????~0????V{???e?e???(?`G4K????e??k??????-?F??`?#[}????8=??AL?b?77?s??S?[r/???????q?p??NM,??5XuH@?U?$.????oR????H??(?M?B??????("?}?u?!;q?agh?t?O??(????\?#??t9 +jd??\?g???z?5C??;?"G?? ??azI?'?QHP?~:?2-?????8?R?OF?G??8?tx??2<+nO???c?? ???r?K?O?U?(D?\????m??D??j?????g p???>AL?????87?>7Z?????I? ?.?3D8B? p?? p? Q??2T??P?e"=TX?, +??6-?Q\??}\D??9:wB???P?H?O??8E??>E\?ci??8?k?x?\?????(??o?$~^L????????????????">/n?6??#??z??.?FtD?L6?Z????&?????D??+?? ??s?????? +?y???I?J?U>C?? ??w?k??`Q????m?+?>???~m?? ???????8?'??> endobj +306 0 obj << +/D [304 0 R /XYZ 56.6929 815.7613 null] +>> endobj +307 0 obj << +/D [304 0 R /XYZ 56.6929 759.0684 null] +>> endobj +308 0 obj << +/D [304 0 R /XYZ 56.6929 742.9638 null] +>> endobj +309 0 obj << +/D [304 0 R /XYZ 56.6929 711.0834 null] +>> endobj +310 0 obj << +/D [304 0 R /XYZ 56.6929 681.1955 null] +>> endobj +311 0 obj << +/D [304 0 R /XYZ 56.6929 682.6549 null] +>> endobj +312 0 obj << +/D [304 0 R /XYZ 56.6929 671.696 null] +>> endobj +313 0 obj << +/D [304 0 R /XYZ 56.6929 660.7371 null] +>> endobj +314 0 obj << +/D [304 0 R /XYZ 56.6929 649.7782 null] +>> endobj +315 0 obj << +/D [304 0 R /XYZ 56.6929 638.8193 null] +>> endobj +316 0 obj << +/D [304 0 R /XYZ 56.6929 627.8604 null] +>> endobj +58 0 obj << +/D [304 0 R /XYZ 56.6929 590.7101 null] +>> endobj +317 0 obj << +/D [304 0 R /XYZ 56.6929 563.1566 null] +>> endobj +318 0 obj << +/D [304 0 R /XYZ 56.6929 529.3186 null] +>> endobj +319 0 obj << +/D [304 0 R /XYZ 56.6929 530.7781 null] +>> endobj +320 0 obj << +/D [304 0 R /XYZ 56.6929 519.8192 null] +>> endobj +321 0 obj << +/D [304 0 R /XYZ 56.6929 508.8603 null] +>> endobj +322 0 obj << +/D [304 0 R /XYZ 56.6929 497.9014 null] +>> endobj +323 0 obj << +/D [304 0 R /XYZ 56.6929 486.9425 null] +>> endobj +324 0 obj << +/D [304 0 R /XYZ 56.6929 475.9836 null] +>> endobj +325 0 obj << +/D [304 0 R /XYZ 56.6929 465.0247 null] +>> endobj +326 0 obj << +/D [304 0 R /XYZ 56.6929 454.0658 null] +>> endobj +327 0 obj << +/D [304 0 R /XYZ 56.6929 443.1069 null] +>> endobj +328 0 obj << +/D [304 0 R /XYZ 56.6929 432.148 null] +>> endobj +329 0 obj << +/D [304 0 R /XYZ 56.6929 375.9587 null] +>> endobj +330 0 obj << +/D [304 0 R /XYZ 56.6929 375.3609 null] +>> endobj +331 0 obj << +/D [304 0 R /XYZ 56.6929 364.402 null] +>> endobj +332 0 obj << +/D [304 0 R /XYZ 56.6929 353.4431 null] +>> endobj +333 0 obj << +/D [304 0 R /XYZ 56.6929 342.4842 null] +>> endobj +334 0 obj << +/D [304 0 R /XYZ 56.6929 331.5253 null] +>> endobj +335 0 obj << +/D [304 0 R /XYZ 56.6929 320.5664 null] +>> endobj +336 0 obj << +/D [304 0 R /XYZ 56.6929 309.6075 null] +>> endobj +337 0 obj << +/D [304 0 R /XYZ 56.6929 298.6486 null] +>> endobj +338 0 obj << +/D [304 0 R /XYZ 56.6929 287.6897 null] +>> endobj +339 0 obj << +/D [304 0 R /XYZ 56.6929 276.7308 null] +>> endobj +340 0 obj << +/D [304 0 R /XYZ 56.6929 265.7719 null] +>> endobj +341 0 obj << +/D [304 0 R /XYZ 56.6929 254.813 null] +>> endobj +342 0 obj << +/D [304 0 R /XYZ 56.6929 243.8541 null] +>> endobj +343 0 obj << +/D [304 0 R /XYZ 56.6929 232.8952 null] +>> endobj +344 0 obj << +/D [304 0 R /XYZ 56.6929 221.9362 null] +>> endobj +345 0 obj << +/D [304 0 R /XYZ 56.6929 210.9773 null] +>> endobj +346 0 obj << +/D [304 0 R /XYZ 56.6929 200.0184 null] +>> endobj +347 0 obj << +/D [304 0 R /XYZ 56.6929 189.0595 null] +>> endobj +348 0 obj << +/D [304 0 R /XYZ 56.6929 178.1006 null] +>> endobj +349 0 obj << +/D [304 0 R /XYZ 56.6929 167.1417 null] +>> endobj +350 0 obj << +/D [304 0 R /XYZ 56.6929 156.1828 null] +>> endobj +351 0 obj << +/D [304 0 R /XYZ 56.6929 145.2239 null] +>> endobj +352 0 obj << +/D [304 0 R /XYZ 56.6929 134.265 null] +>> endobj +353 0 obj << +/D [304 0 R /XYZ 56.6929 123.3061 null] +>> endobj +354 0 obj << +/D [304 0 R /XYZ 56.6929 112.3472 null] +>> endobj +303 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F90 192 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +357 0 obj << +/Length 4253 +/Filter /FlateDecode +>> +stream +x??]???????q(/pfI?????y!???Eq?Z[???\I?fQ?? _?^?o????"HD??? +9ORZ??(??VQL??g??E$?Y????????b?f??66?_?^?????2??<^???bN??F??&$?x?z?{?????w???gu????~???V) ?& @?? +c$?".?F0,I??????/???XI?H???????t??9|sEI??lu7??0c??U???\?9\?x??????! i???&2??\?$???p~????0?5?????d|?]Q?p? X???|?????+????????]?Zm?????7?^w?qn?F?n???P???c??V?~???????????h??QC?F?|??P???O??C?Z27?l??|, ??BE?*?!o?Y +2???l??Q???o +?????|? ??)??J?????n??l?? +??+!?C??????k?g?/?"A????wu?V????y????kN??n4z[W]??JcJt]??kn?????f,?}Ww?"?? ????O4??\?????5?????K???DX??*z??1????u ??C\?????AI??*'??M?c|??RKhgw????}?we?2?A?Y??JF=??k??;H?E??-????? F?_?-Q?7 pS*&TOE?????7?O???!V?6E#?4???E??)M??)hoSNPcS6(?/? ??r,???<???^???????A6?hZyy? ??F?JS0?Z????????h?Q???>WJ^U????~?? ?3Y?Y????8t???Z?????? jt??:??@???-?o2?`?Pk???????????????z?U????P?WO7?RLqQ"3R???4?r4???-????b'?J?"??*??[S?e%Y!{?;?\?!?????D??"?e??k?H?Ah?"?F>??e{W?[?H?pLeH c]??? +?? ??p?"????MtP?"???r?????7???H?y?S?]m0%?A??Z??:WV???0 +9??yR?M?pM?uh?NP?6(,??z?2?/2???M??2c??`??3? .?;???+??'\??Y???t??)???f*???V&?????5;&?o??????U~?Q?|{???? +?A(????a at nJ???Z??H?????.+-?_?X?uu???b}gr?6oUK?nSS????????u??6YW??)??Z +????Da??6?d???cN?????Y??>?A?O4U????9????$?B???y?M?T9?????R???U1Wq?jE +?- x??b9TJ??T?~????Z?8?? +????9?6??]?? ??I??C%e=H??zIBm,I wB?dIw'?"c?p?2?l@???d??Sx??SMa'???7o?R??o!? +????????????j??g??kq?????d! +m?eK??e??mR?)_ I?L??~Li~?7?nWo?l??????D??bA?7?? +????Q??oU?R??????4g?}?UVeWb??p.??~)??aL?8??PoS???W??$?????p??AS?GnLE???B????W??HR???4"???[?2??????????N?R) ?)?????>??+??Ta?ua?h?3Z??DTEXq|_??L????,w??h?O ??S +BW??J6~?s?0?i?o?????.c??79d??&<]????E??}???FCCq??h???S????q;}???6j'????j?????O ?Dm????y??"B??N??M?rx???=66?0??KR??~?? ?.??$9K M??)L?s????>?]02I?8l"^DI??[/??h~I;O?v? \3AC????O4j?????P E?-????P]&??G??Z?p??j???l??f????S4???E?t6:1???/]???'?1?O?c??:xY ??pc?|?n?? ?SP????8???N{??c??Bu?gQ]PF?A?r???;,[?j*???@??GOn? /??????'?c?????I_z???c??9z?xI~???[xC7??/==b???O?1????i????t??{???X??4y ??-M8??Z???`fk?W??w?fb?-??)?e{wHg??x? +?????/?<,f????????-M8l^S?m?????y?l??m??>?]?I???*??? +??F??t???????-M8?^S?+`[???u??[@/???"?9?+??I_\;?? ?/??o?,&???JqNi? u? +.c0T^?17?$?/o0?????X.?Qjs?Vy??,?>??/?H0?d??$?.o:???"7?"????w?6??-??c??].G? +.x????S.???\?D?????L{??KR??\ ? ????D4?V??a??0?4 ^>n{??3?*???????@[?c?????:??T`?@8?t?5r?O???2?D??)?*?>?:?#?-?v?s??????E?t?oUL?v??=?cn??????%,?xSP??'|????9???:?6?g????9???x?Zq??v??E?s69??9??/?'i?????R?#?h*?U??A??^? 2??,????d??)_?A?????Y? ??? nQLq????.C?2?t???A??pAq?O?z2?s?}????y2??s?3??d??=??M~,??t??|q??p[??R|?y??%?]}?9????n???s????n?)7q?=M!?f???{??|g +??????3eE???B??X6?K????|)??t?T?(4????I??v?]N?>i???????q?e??$J?\N??9???:?&?I?)??????S??>)$J1??????={?\????C??ht??5?OI7Z??????i?9}?cn??WF?????[}?i???+OM???3 +I??????????????e?|o@?T?>???,6=G??_9[]qendstream +endobj +356 0 obj << +/Type /Page +/Contents 357 0 R +/Resources 355 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +358 0 obj << +/D [356 0 R /XYZ 56.6929 815.7613 null] +>> endobj +62 0 obj << +/D [356 0 R /XYZ 56.6929 465.1132 null] +>> endobj +359 0 obj << +/D [356 0 R /XYZ 56.6929 436.1462 null] +>> endobj +360 0 obj << +/D [356 0 R /XYZ 56.6929 410.4223 null] +>> endobj +361 0 obj << +/D [356 0 R /XYZ 56.6929 390.5382 null] +>> endobj +362 0 obj << +/D [356 0 R /XYZ 56.6929 358.6989 null] +>> endobj +66 0 obj << +/D [356 0 R /XYZ 56.6929 328.8596 null] +>> endobj +363 0 obj << +/D [356 0 R /XYZ 56.6929 303.1056 null] +>> endobj +364 0 obj << +/D [356 0 R /XYZ 56.6929 280.7073 null] +>> endobj +365 0 obj << +/D [356 0 R /XYZ 56.6929 282.1668 null] +>> endobj +366 0 obj << +/D [356 0 R /XYZ 56.6929 253.0585 null] +>> endobj +367 0 obj << +/D [356 0 R /XYZ 56.6929 255.3499 null] +>> endobj +368 0 obj << +/D [356 0 R /XYZ 56.6929 244.391 null] +>> endobj +369 0 obj << +/D [356 0 R /XYZ 56.6929 233.4321 null] +>> endobj +370 0 obj << +/D [356 0 R /XYZ 56.6929 222.4732 null] +>> endobj +371 0 obj << +/D [356 0 R /XYZ 56.6929 211.5143 null] +>> endobj +372 0 obj << +/D [356 0 R /XYZ 56.6929 200.5554 null] +>> endobj +373 0 obj << +/D [356 0 R /XYZ 56.6929 189.5965 null] +>> endobj +374 0 obj << +/D [356 0 R /XYZ 56.6929 178.6376 null] +>> endobj +375 0 obj << +/D [356 0 R /XYZ 56.6929 167.6787 null] +>> endobj +376 0 obj << +/D [356 0 R /XYZ 56.6929 156.7198 null] +>> endobj +377 0 obj << +/D [356 0 R /XYZ 56.6929 145.7609 null] +>> endobj +378 0 obj << +/D [356 0 R /XYZ 56.6929 134.802 null] +>> endobj +379 0 obj << +/D [356 0 R /XYZ 56.6929 123.8431 null] +>> endobj +380 0 obj << +/D [356 0 R /XYZ 56.6929 112.8842 null] +>> endobj +381 0 obj << +/D [356 0 R /XYZ 56.6929 101.9253 null] +>> endobj +355 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +385 0 obj << +/Length 5016 +/Filter /FlateDecode +>> +stream +x??]{o?????ba?u???)??????????@?4(?^???}??'????%?C%va?*?????f8?pDg??d?%-'?(?M?7gxr#??????%??Tysv???I?JA???r"(9?????4??Y????[-?3??????/W????7??G???? +???\B?!????? +?X^L/?a?????8??XyI??PR?z???,???a??????0?YI&?3N?%??Y??>?G??~K3?????a?R>? ????????N}|??$+?(a????(????,=?%???@\??L??^1????d&/?\??V??????????x;Mz??o????m^lA?d3???FO??????Sb=25\o?Tj|???r??\vu?WW2?X^?I?D?2.GiB.K??k}? +??G??!+?%e)?4Y??z?^/V??t?D9?i???x?JK1????u?W?>??|?`?'?1G =????q&?H????????;?g `??T?;Q??kY?@[??J?xY?yY?????????%@?7????LhN?+V.t???^??,1?kp??????????????(|?](????fuh???np?Q?q? +^??>??%?2?????X?XWa????????????|?*?????@9??????A???????????7????k?]???i?8????b?=??n?[}%c|?q?=V??O??j{cx???????????>}?:?????W??nSi?:??~???.V??!????ko??v=_m5?V?? )? ??|!?????.??????3OW?????7?x??^??????K???iot?????????|?U???j_m?jW???? ?a??]W???oo???\?k?Mj???:|:4?4????_??k}????)3?+??w:?????BGQ?w???j?}q?y????Mu?8????l? +????? +!/???~z??m???????w?????Z??ZT=w????k????-?????????????x--??^????L????1u?:?W????>?F~??????|???????? ??z,?;s??O?+?4???w8??nS????`+[???g????h? +??92?8H-?l:\N_?6$?j1????3"??4?fH?K??AV?R???/??Wmm?????E?3?M?5?q?#???L~?L^?T?Sj?=?1???d??T??Zs?]?$T?u-???=??;=??s??^??[?????nt????V?2?_??? +??\?G?????E?????1?b ?Z?????????-??}3+`?,YK.9Q???@2??K??X[?z??????H at o +?vk(-?p#?(????? C??d? +~?s?b?7????$??r?n??*?9+F?=z?A^[%}f2T????R#?????e?????y?fs"Z?-e?]?d??aX?????c,???@??c^??wt?????'?J8G???????W?J????i!u5????E?6Q?H??tJ?lJMW?]?^??K????)?4]?j? v?&?6jh[???c?????p|?!RYQ??????7?Y ?[??!s? +FE?El ??8????????n9>?@j{ ??,>x?-?Y?)?E/ l??K??e?RX ?q???R?PnFowT +???q?o\?????X^e???R?;6>?????r?????ww??????X???(??,?c?? ??A??[?????????????O?|?{6???7???????`%??'?>G????a>??n???Y??l??? ???? +??????p?#?e?x^???)?Yl??????M??=??^?Yt?????'?s?d|????!??SC5w?6|?w?6??????x??%?f?X-W?"L??DY?DBw?2!??kI?????OaF???{O?+???????C?|q\?5 +6??8??!?:aew=? *??L??????p??C?v???@?[Py??s?M?m?R??!? ?????P? +y??5f?"C???(X??2??X0tb??Po?r?&??P??+/>F}O%??]+?)X[??~???y??{ f?S????3TF????]???a???X???F_ |?FK???/}2{&0?RL0f??Q??,??????M? +J?N??D:?nw8L?j?5?1/?|??Oh0? +?%?%R]????F?S?U??9??????q? +V 7Z??q?????3=zg?,xVK???r??G?V?,{??P6?4??v8???C?~ $??Q%?Cnp_?????????}????-?k???=w-`?,YK.???H??@P2{??%Y<?????>=FOe??RZ9O??uT. +??X???gyQQ?,??8?H?????? ??R???????x?W?W???s +???rM?I???"??????????7?AXu????????>?.?O?j??????L????>?l92???????O?yw:?????9??no?=??-)qB?P?SA?O????>n\S >E3*?^????4n?x-?9???????????V??3????v??u??>?mX????N????RC?????8WkH-7???Z???;_|?????n????e???&;??}?9??m???????k??'?????iSm???????^??3???;L?;G?? +?= ?n?y?????? J6?????f?b|??0v??V?F??i +?zpQ|?? K??B??H1R?(?i?? ??BJ?HQ?C???S???h?J$??1?,??7???q?m??????K?0?*?p?5??F??4?> ?? ?1??L?2f?b?????-#??)?j?%? + 8sT)dMW$???|????5]>?8.?'???????q??Db7Df??0?C?]N??? +??!?.?z?n?????U???$?3sC?5w??y0???AH7kCfh&?Av??l?L??\t??3SCr5u? ?< +???A?.??$=?? +cw?F??p??????? ?????53` +o^a?? Y???Y???Al7'???0Q?] ?W???8?8?????TN-`*$?8?k?>?@? K?2.??????X??9?^??? 0??}7?`??&QK??L!????l?aE?????Z??????-????J?$?m??4???i?Y??XM??i?????/?7?ut1??'?3x??,ZG??????oA/X4[??-Z-ZI?y)?z)2Z}Em??hv??}?>?Y???*??}???????>?????'\33??U8?wu??EY????A?o???"-?LwT?YIWo????n?4??9_??f~?????? ??L@???B~??y?P\(?fK?%?%?Z?\o???b??`8??!7???? ?????0na?{???C???F{r????????[??????Z?????????o???a????p??_k?9Tm?^???????d6?yS????'??t???7??)x?^???U?&??j[?n??_m?.9Tm?^?????-?H~c??SO ? +Q +???.??,?s?C???)??o????j???3?????m???;?& +T??????7???? +???R?@n??vE??*??%?5]??N?>k??@????P9?????mN?~uv?'8?]?c<.*??_3??S??6?D?E@?\??????6? ??R????? +??X?oZ???'-|HuV?. +???`$k#;??z???!?jHZu!?A?g?xL?????}q] ???????u???M?]C???? f?S?Z?????K??;?G??f +G??_?W??endstream +endobj +384 0 obj << +/Type /Page +/Contents 385 0 R +/Resources 383 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +386 0 obj << +/D [384 0 R /XYZ 56.6929 815.7613 null] +>> endobj +387 0 obj << +/D [384 0 R /XYZ 56.6929 759.0684 null] +>> endobj +388 0 obj << +/D [384 0 R /XYZ 56.6929 752.3934 null] +>> endobj +389 0 obj << +/D [384 0 R /XYZ 56.6929 741.4345 null] +>> endobj +390 0 obj << +/D [384 0 R /XYZ 56.6929 730.4756 null] +>> endobj +391 0 obj << +/D [384 0 R /XYZ 56.6929 719.5167 null] +>> endobj +392 0 obj << +/D [384 0 R /XYZ 56.6929 708.5578 null] +>> endobj +393 0 obj << +/D [384 0 R /XYZ 56.6929 697.5989 null] +>> endobj +394 0 obj << +/D [384 0 R /XYZ 56.6929 513.8231 null] +>> endobj +395 0 obj << +/D [384 0 R /XYZ 56.6929 515.2826 null] +>> endobj +396 0 obj << +/D [384 0 R /XYZ 56.6929 486.092 null] +>> endobj +397 0 obj << +/D [384 0 R /XYZ 56.6929 488.3835 null] +>> endobj +398 0 obj << +/D [384 0 R /XYZ 56.6929 477.4246 null] +>> endobj +399 0 obj << +/D [384 0 R /XYZ 56.6929 466.4657 null] +>> endobj +400 0 obj << +/D [384 0 R /XYZ 56.6929 455.5068 null] +>> endobj +401 0 obj << +/D [384 0 R /XYZ 56.6929 444.5479 null] +>> endobj +402 0 obj << +/D [384 0 R /XYZ 56.6929 415.3573 null] +>> endobj +403 0 obj << +/D [384 0 R /XYZ 56.6929 417.6487 null] +>> endobj +404 0 obj << +/D [384 0 R /XYZ 56.6929 406.6898 null] +>> endobj +405 0 obj << +/D [384 0 R /XYZ 56.6929 395.7309 null] +>> endobj +406 0 obj << +/D [384 0 R /XYZ 56.6929 384.772 null] +>> endobj +407 0 obj << +/D [384 0 R /XYZ 56.6929 373.8131 null] +>> endobj +408 0 obj << +/D [384 0 R /XYZ 56.6929 362.8542 null] +>> endobj +409 0 obj << +/D [384 0 R /XYZ 56.6929 351.8953 null] +>> endobj +410 0 obj << +/D [384 0 R /XYZ 56.6929 340.9364 null] +>> endobj +411 0 obj << +/D [384 0 R /XYZ 56.6929 234.8692 null] +>> endobj +412 0 obj << +/D [384 0 R /XYZ 56.6929 236.3287 null] +>> endobj +413 0 obj << +/D [384 0 R /XYZ 56.6929 225.3698 null] +>> endobj +414 0 obj << +/D [384 0 R /XYZ 56.6929 214.4109 null] +>> endobj +415 0 obj << +/D [384 0 R /XYZ 56.6929 203.452 null] +>> endobj +416 0 obj << +/D [384 0 R /XYZ 56.6929 192.4931 null] +>> endobj +417 0 obj << +/D [384 0 R /XYZ 56.6929 181.5342 null] +>> endobj +418 0 obj << +/D [384 0 R /XYZ 56.6929 170.5752 null] +>> endobj +419 0 obj << +/D [384 0 R /XYZ 56.6929 159.6163 null] +>> endobj +420 0 obj << +/D [384 0 R /XYZ 56.6929 148.6574 null] +>> endobj +421 0 obj << +/D [384 0 R /XYZ 56.6929 137.6985 null] +>> endobj +422 0 obj << +/D [384 0 R /XYZ 56.6929 126.7396 null] +>> endobj +423 0 obj << +/D [384 0 R /XYZ 56.6929 115.7807 null] +>> endobj +424 0 obj << +/D [384 0 R /XYZ 56.6929 104.8218 null] +>> endobj +425 0 obj << +/D [384 0 R /XYZ 56.6929 93.8629 null] +>> endobj +383 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +428 0 obj << +/Length 6847 +/Filter /FlateDecode +>> +stream +x??][s#7v~??`6y?T, ??;?+???e?j????????C?2/#?R???qm4?9b?Iz?v?!O??;?\t????/?%)??jV??d?l?pAgw???.????BW????_??????4%/g?og%'eE?YM+?5??????????v?????????????_?? .e?Z\Zf????D=?b?4E??K+qYU_????L^w??? +/M?j? +^KV?^?? ??~??$oj6{???? +?=\L|?J??Y]???????9?i]????????EQvB?????3???jtv%?U?k?3N???gL???l??n??????(???Q????????. g? +J???/???????w???Oc7~????emn???wo.??N,?!y??n??|q??g?\??l?*?+HV _??kRe %??q???a~??1.??Xr?2R???}?/?L?J6l???F??vv?9'U?? +?,* +???????j?????E??9??M?^?-??_S?B?,x?h)?S??????+y?h.??W????_?3?. "?????8?3??]?k/V?????????????!=??@T??\????c??1V@????G?C??????U??F + +??{\???+?m??(|'7??????]??h?]l?u\0?q\h??????d????S]?v?5?yQN^??x???t?/?d?H?????3R4`$??)=y%1?h??c`T1B?q??????h?????n?Ud???!??VR +7?+?^_???3??? + l?YcA?m?:K??f???MXm? +??[^[<*9?i????x?h??xR???%??#???`?@[b???-1??u??H???r=_???????wX?????m????AR&f??????UT?E???????u?'???Jx????????Dx?b??e???E?6??????d?Pu?o1 +?,?}DFt?j????4??4??FTs??? +1???^]c?d??1?JQ? $WY??0?@???f3????V\???????"M#??o3???0??????S?m???r??o77?E{???\??Y?R????su?|???J?=???C?? _??z? +??m?Hx???{??A\$???+?????b?_n??7?? ?m]Z??R(??l?E Et1W??????V??/???????????????????????a???ln???l???,T+ ?? ??????HS>.o??y??j???OW??????};W4?????????N???^+??Q?W???S??[???????h?{??U??????j&?????????:2????_K?????f??/w???5?ZP)???i???s?vv?b?v?Y???+?D+V4??c??M??? \]???u?{1????????k??vsX+?}????yx???_????????+????]^???~?????????$?%9,??????????{-????$??b???U?Y?O?x?????az*??|-?o?p?D !?]&)?5EEh?u???????o?8???@^???????????c?H?k??????????7??????\?????D????p?(u??}??:1?w?????n??B??"?Z4??Jaq?????N?r?0i!VNGI???!NH???????-????8O9?#?k7T???J?@?? ??u???i?%??D???????x???# ?R?c?w?p=-sB???F'????"????.?????????t??f1?F?x?+P?@W7??u4?5?K>?,wF??41???T???C?f?;?.???=??W?s??nD???!??*????????M?????0=*w???!~??)|??O?1???N?1*#?6`PZ\???W?mG? +??a?7]m?8?????A??????>???:f??Go?@F?IpH???@?????????"???0|?????>?Y???V?m??0?@???!f?J??fc ?6??F??a?"??"Z??F +?u????? ?U???t?td?g?Fqt??#i??????eE??W3W?^?^A?#????%>???`???e??mm?d#????z?>?{??9}?N??E?Xlp??y???r????[??x????v(u%79r?Z?????+?W??????L^3 ?5@?y? +C?M%?Tvf/.?V??dV? +???}\???????IrVK???ON?P?????J?*ZZ?Bx?"? +?.?r?x?T?c??2????f??)????????@J?i???????4?Y5??omk??u?F??h?%?????n)J???3WW??????? +x??V????o???}??????Aj?F????Py?z?n?I?].??sxt{Ajvf????????` ??f[?????=$m?p????9?juV?fu f?W?\???>???yI?Bcm&\?O????2?Yi??$??YHri?5?-{?g}???] ?Y?? ??XM?r?\?oc????F??}{?;???<>/????8????|????!??%n??G????%? +?]??=????a???6\??????LJ?Qbt????e?S??=n?? +iU\?#B/?a?j?????qKt??4A??????$n3?????wON/???/???]>???;??Cm????2Bi?????Gx?z#?+c????Bf/? +@???[???y??jJ\??????jh?$?Z??'\???h???????g?} +G>??P?O,xT?'N?c?X@?? cTF?X?A?D? +>?p?????n???:??)#D???d +???9??}J +?b??????n?@?????7?????????=?-? +????????|??????B0{???$?? 1j?????????=???????S????????Re?pWB?h?????????? ?0?A`=??????+? K? 8?$???iH??DC?0?k?_?yh??F? -+R??}???|???W?S?6??| $??P ? ? +?.(\?G?\a?n8?? 6??D??{?"? +???;??}??AmQ?{?v??'?1?`:C??8xD???@[???cI??j??g??N^_K????nL?? 1??]f???(??a*???T>??????q_{> endobj +454 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 391.8345 314.7523 402.7384] +/Subtype/Link/A<> +>> endobj +429 0 obj << +/D [427 0 R /XYZ 56.6929 815.7613 null] +>> endobj +430 0 obj << +/D [427 0 R /XYZ 56.6929 760.0646 null] +>> endobj +431 0 obj << +/D [427 0 R /XYZ 56.6929 749.1057 null] +>> endobj +432 0 obj << +/D [427 0 R /XYZ 56.6929 738.1468 null] +>> endobj +433 0 obj << +/D [427 0 R /XYZ 56.6929 727.1879 null] +>> endobj +434 0 obj << +/D [427 0 R /XYZ 56.6929 716.229 null] +>> endobj +435 0 obj << +/D [427 0 R /XYZ 56.6929 705.2701 null] +>> endobj +436 0 obj << +/D [427 0 R /XYZ 56.6929 694.3112 null] +>> endobj +437 0 obj << +/D [427 0 R /XYZ 56.6929 683.3523 null] +>> endobj +438 0 obj << +/D [427 0 R /XYZ 56.6929 672.3934 null] +>> endobj +439 0 obj << +/D [427 0 R /XYZ 56.6929 661.4345 null] +>> endobj +440 0 obj << +/D [427 0 R /XYZ 56.6929 650.4756 null] +>> endobj +441 0 obj << +/D [427 0 R /XYZ 56.6929 639.5167 null] +>> endobj +442 0 obj << +/D [427 0 R /XYZ 56.6929 628.5578 null] +>> endobj +443 0 obj << +/D [427 0 R /XYZ 56.6929 617.5989 null] +>> endobj +444 0 obj << +/D [427 0 R /XYZ 56.6929 606.64 null] +>> endobj +445 0 obj << +/D [427 0 R /XYZ 56.6929 595.6811 null] +>> endobj +446 0 obj << +/D [427 0 R /XYZ 56.6929 584.7222 null] +>> endobj +447 0 obj << +/D [427 0 R /XYZ 56.6929 573.7633 null] +>> endobj +448 0 obj << +/D [427 0 R /XYZ 56.6929 562.8044 null] +>> endobj +449 0 obj << +/D [427 0 R /XYZ 56.6929 551.8455 null] +>> endobj +450 0 obj << +/D [427 0 R /XYZ 56.6929 540.8865 null] +>> endobj +451 0 obj << +/D [427 0 R /XYZ 56.6929 529.9276 null] +>> endobj +452 0 obj << +/D [427 0 R /XYZ 56.6929 518.9687 null] +>> endobj +70 0 obj << +/D [427 0 R /XYZ 56.6929 480.7463 null] +>> endobj +453 0 obj << +/D [427 0 R /XYZ 56.6929 444.5815 null] +>> endobj +455 0 obj << +/D [427 0 R /XYZ 56.6929 368.9204 null] +>> endobj +456 0 obj << +/D [427 0 R /XYZ 56.6929 370.3799 null] +>> endobj +457 0 obj << +/D [427 0 R /XYZ 56.6929 359.421 null] +>> endobj +458 0 obj << +/D [427 0 R /XYZ 56.6929 348.4621 null] +>> endobj +459 0 obj << +/D [427 0 R /XYZ 56.6929 337.5031 null] +>> endobj +460 0 obj << +/D [427 0 R /XYZ 56.6929 315.5853 null] +>> endobj +461 0 obj << +/D [427 0 R /XYZ 56.6929 304.6264 null] +>> endobj +462 0 obj << +/D [427 0 R /XYZ 56.6929 293.6675 null] +>> endobj +463 0 obj << +/D [427 0 R /XYZ 56.6929 282.7086 null] +>> endobj +464 0 obj << +/D [427 0 R /XYZ 56.6929 271.7497 null] +>> endobj +465 0 obj << +/D [427 0 R /XYZ 56.6929 260.7908 null] +>> endobj +466 0 obj << +/D [427 0 R /XYZ 56.6929 249.8319 null] +>> endobj +467 0 obj << +/D [427 0 R /XYZ 56.6929 238.873 null] +>> endobj +468 0 obj << +/D [427 0 R /XYZ 56.6929 227.9141 null] +>> endobj +469 0 obj << +/D [427 0 R /XYZ 56.6929 216.9552 null] +>> endobj +470 0 obj << +/D [427 0 R /XYZ 56.6929 205.9963 null] +>> endobj +471 0 obj << +/D [427 0 R /XYZ 56.6929 195.0374 null] +>> endobj +472 0 obj << +/D [427 0 R /XYZ 56.6929 184.0785 null] +>> endobj +473 0 obj << +/D [427 0 R /XYZ 56.6929 173.1196 null] +>> endobj +474 0 obj << +/D [427 0 R /XYZ 56.6929 162.1607 null] +>> endobj +475 0 obj << +/D [427 0 R /XYZ 56.6929 151.2018 null] +>> endobj +476 0 obj << +/D [427 0 R /XYZ 56.6929 140.2429 null] +>> endobj +477 0 obj << +/D [427 0 R /XYZ 56.6929 129.284 null] +>> endobj +478 0 obj << +/D [427 0 R /XYZ 56.6929 118.3251 null] +>> endobj +479 0 obj << +/D [427 0 R /XYZ 56.6929 107.3662 null] +>> endobj +426 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +482 0 obj << +/Length 308 +/Filter /FlateDecode +>> +stream +x??P=O?0??+nL??wv|?A?? +5[???n?Hh?*?=.IZ?Z? ????{??0??????H??a???= +?9?@J?ns1~0^zV ?XI?h????+ ?j?L????`rW??E??y>?R????????AJ$?1?[????d?=??:q???????6??z?9?*?0(3?1@?2O???W?2????s?U????+n??m?/;N?e^????%tf????G?$?r??R???z????Qv?*4?}Y??'EB?a???z? ^??? +?nB??vs?D?qsm/m???q???oz?8t?????endstream +endobj +481 0 obj << +/Type /Page +/Contents 482 0 R +/Resources 480 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +483 0 obj << +/D [481 0 R /XYZ 56.6929 815.7613 null] +>> endobj +480 0 obj << +/Font << /F50 132 0 R /F51 135 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +486 0 obj << +/Length 3502 +/Filter /FlateDecode +>> +stream +x??[K???????!U?T?0???????q?dw|H?>P5b?"e>vv????H?"5k[???v???n4?~???_?P??X???+f4??M?x??/o?????V?Y?=??}??E?b-??a???i?E??,??,?;?z???????r]?=???LE???????T???<'?v?WS???O!X?? ?e!04 #40 b{??gX?=??-??<`,???b???}??2??????)??j j??????????S?]L????T???!???lV?<?? ?b9???!??? Ud?G?e?m?TY3????=^/J??u(???f?????f[??y:?????W?z8z(???f??m?d???v?o?4?N????9?_M?/??dq?9?+& y?q????\????uG??M2???X0??/ +???D??9K3t?2Z6??B?p1?~???g?r?[)??,?z???p9??????4-?.kF?UjY????????v?~?]?????(???#/??y;??|???8 ?3P0?? ?????d???????????????? ??3q3? +,???I??1?????`B??/??aA???`/BG`?r~- PF?&???mb?????? ?????$???????\?N7e?K0 ?l?$s?g??????T????j?????????r?K??????-^????\! +0s*??E??Z$?2??Z????:?o:???;?? +?I????55 fS?x/????????C>u?bC????zc? ?^?^??]??????bA=e??L???38?SqXl??K]lj???<ZP?N`]3?????????? ?0#?X?C6????P?Ue??e?a??Q?>P}??{????x{??[?/?;:???|????w]$?s?OH-t)^8?!?F?u?{?*??%bN?3????w?O???*]8?????>?H??&T1yJ9b?_n????`???????????#? +g&?'Z@>?wt???>?\b????T??Mi?uz?x??1j??.O?n?%??_b?W???e??(Hr???k:?Vn?|????E?z?S?-????rD???{?????Z`?$?cG[[w?????.?? $????'??u?W??lf?h??{}?a?K?KM??!??;?^?Ll +??=?l?????f?8?rw?O???]??????n?1-?K?t;??u??????+???P??a???9 ???O8? ??,(??*!0('??,???I? +???.???G?W??????{zp??@?nT????r??S(??? +0?.??????'_?eTB??p??T??c????g??['~????'??/?r?3??x??}W^????L??????$X@???????z?????x?endstream +endobj +485 0 obj << +/Type /Page +/Contents 486 0 R +/Resources 484 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +/Annots [ 492 0 R ] +>> endobj +492 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [204.0186 316.2483 223.1566 327.1523] +/Subtype/Link/A<> +>> endobj +487 0 obj << +/D [485 0 R /XYZ 56.6929 815.7613 null] +>> endobj +74 0 obj << +/D [485 0 R /XYZ 56.6929 553.0513 null] +>> endobj +488 0 obj << +/D [485 0 R /XYZ 56.6929 522.509 null] +>> endobj +78 0 obj << +/D [485 0 R /XYZ 56.6929 468.7561 null] +>> endobj +489 0 obj << +/D [485 0 R /XYZ 56.6929 440.3707 null] +>> endobj +82 0 obj << +/D [485 0 R /XYZ 56.6929 409.4559 null] +>> endobj +490 0 obj << +/D [485 0 R /XYZ 56.6929 372.4592 null] +>> endobj +86 0 obj << +/D [485 0 R /XYZ 56.6929 372.4592 null] +>> endobj +491 0 obj << +/D [485 0 R /XYZ 56.6929 345.105 null] +>> endobj +484 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F52 139 0 R /F90 192 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +495 0 obj << +/Length 4141 +/Filter /FlateDecode +>> +stream +x??]_s?????????pd?w3M??4/I{??C?Z?m?$??????? ?A?h5??4???$r??],???Y`??,x??????p$r?-V? ???{?/??Y??K??????q?(Q??|q}??)??? ??T,?o?????;\-)???6???{?????(Y?h??G??HZ,????s?=K0<(??7???'/?????DIP??q?????~??[??? ?XY??|????,????,????????z??.e???O??!Z? ?y??+?\??F?A??k6??!??3D??TJ?p?y??&9f%?"_????y\????<`?%4K?s66m?S??xU??G?????[?s}E??g??zu?"?V?I????????? +^?? ????C\?9????????H6Tr????=??%?.?0k?j?C???d?C?bPcC????J??j NB????*??F???>?+??o7?r)V???)??-XR8C7n???}?@8??m'Lb?R??i??$?b????)x?o0"g? ??g?2????!???U?F????f???#??tE?-9D??S6=?3d??kr?$????n?Q??jv?zw?)ys???t???>n4!?$??!?w?????ev????7u0??s???????A?zi"d?)?T??vK%?????????;'(#\???zVs???Z.?T??????4?:r?/`?????????i? +3????;.??[????tC.&???IH?M ??F?Ld^6?>E??'?1iy?UrH?J?'E?A +U +T??C??hf?y^?G???f??}{??-?BK?????\&\???9??????n??s+&:?????????X_'wC??";?K??&zA??Rr????)??g????b??S?8?IM?5?????? +??^???]B +???????"N??y6%??+????????? +?Ev?4???4?t??@f???*????M????38???5/?4q??*???M?d???]?????j"s+0b?C3???~&!??{???83`??7?&!??7??????{z? +w?4? +^\???F??? 1?BM????(-P!??@??????0??"I??????xO?n??N??y6)?C????>????(g at q?8???8?t??E?x??K?)?1??|?.??zDz 1????????H ,S? ?*??s???rL?(??mb??????rl??O?fsXo??c}?D???I?!L??}E??(?8??5?=?,G??b?BQ??'??\%???=!@^ A????&:?43?a?Xn??^-?9M?h??????qvL? +???F??/ k 1L\s??X??/?.Q^.?h????f??(??J????F? o&???N\? ???????8?v?EBC?????j?a??~??Ap.O??>??J??D?dA8??x??T)LE7????i???q??g??j??m????T'???????`>??? +?"??C???)??8??? ?c????(??????b??=?w? !F`???I?g?!'?B??"s|? -?????_??;M???????f??????????C?})??x??./??3???g??tt#Q6????????q?T#??'D??? ?1???X.??G??C????????m??????o?m?:4????????Jy?? +?9?`?"i??L?? ???? +c?+????5?7aG2S??y$???p???cpOMT?~OM??6??]M??u????????n_????m,q??????M?D:?s???g??z??i???_K????f6?????F?W4???????J-????1\???c6?<"+??p8.?"U<@???x@(`?b?\?p?????.p?????|m?????????oj}??????I?;4??}}PL???w???^]???Eu?.H??+???-?Z2Z^?K?%?????f?(U??T???jw?6????t?????G +??KJ.?`??k?\p??????U} bZ +?fN?I*????]??Zp??;????7I2?T???Sw?f?ZV???W?????nx}??? ????V+[????Z?????m???V'?>&?w??6$_0*dW???Z9? ?L I)b?K*JTpS(??[1}?? ?K?????J???F?%???+WL??M?B?? +?Q??L??4r ???????p????(??u{?~s[??????>??%??%t?C?[???K??D?4?M&??LM?yM?m? f??/?$??|;k?wa??wqqX???Z[7S???%???[?7??iD?????}n?op??????GeR?c?????Oc??????"??9???<(+??;xC???i?j??A: #?s??????`?uNy?S?? ?Wc?:??(??-???> endobj +496 0 obj << +/D [494 0 R /XYZ 56.6929 815.7613 null] +>> endobj +90 0 obj << +/D [494 0 R /XYZ 56.6929 759.0684 null] +>> endobj +497 0 obj << +/D [494 0 R /XYZ 56.6929 738.4887 null] +>> endobj +498 0 obj << +/D [494 0 R /XYZ 56.6929 716.6059 null] +>> endobj +499 0 obj << +/D [494 0 R /XYZ 56.6929 718.0654 null] +>> endobj +500 0 obj << +/D [494 0 R /XYZ 56.6929 671.774 null] +>> endobj +501 0 obj << +/D [494 0 R /XYZ 56.6929 673.2335 null] +>> endobj +502 0 obj << +/D [494 0 R /XYZ 56.6929 662.2746 null] +>> endobj +503 0 obj << +/D [494 0 R /XYZ 56.6929 651.3157 null] +>> endobj +504 0 obj << +/D [494 0 R /XYZ 56.6929 640.3568 null] +>> endobj +505 0 obj << +/D [494 0 R /XYZ 56.6929 629.3979 null] +>> endobj +506 0 obj << +/D [494 0 R /XYZ 56.6929 618.439 null] +>> endobj +507 0 obj << +/D [494 0 R /XYZ 56.6929 607.4801 null] +>> endobj +508 0 obj << +/D [494 0 R /XYZ 56.6929 596.5212 null] +>> endobj +509 0 obj << +/D [494 0 R /XYZ 56.6929 585.5623 null] +>> endobj +510 0 obj << +/D [494 0 R /XYZ 56.6929 574.6034 null] +>> endobj +511 0 obj << +/D [494 0 R /XYZ 56.6929 563.6445 null] +>> endobj +94 0 obj << +/D [494 0 R /XYZ 56.6929 526.4941 null] +>> endobj +512 0 obj << +/D [494 0 R /XYZ 56.6929 498.9406 null] +>> endobj +98 0 obj << +/D [494 0 R /XYZ 56.6929 383.4193 null] +>> endobj +513 0 obj << +/D [494 0 R /XYZ 56.6929 355.0339 null] +>> endobj +514 0 obj << +/D [494 0 R /XYZ 56.6929 215.6368 null] +>> endobj +515 0 obj << +/D [494 0 R /XYZ 56.6929 215.0589 null] +>> endobj +516 0 obj << +/D [494 0 R /XYZ 56.6929 204.1 null] +>> endobj +517 0 obj << +/D [494 0 R /XYZ 56.6929 193.1411 null] +>> endobj +518 0 obj << +/D [494 0 R /XYZ 56.6929 182.1822 null] +>> endobj +519 0 obj << +/D [494 0 R /XYZ 56.6929 171.2233 null] +>> endobj +520 0 obj << +/D [494 0 R /XYZ 56.6929 160.2644 null] +>> endobj +521 0 obj << +/D [494 0 R /XYZ 56.6929 149.3055 null] +>> endobj +522 0 obj << +/D [494 0 R /XYZ 56.6929 138.3466 null] +>> endobj +523 0 obj << +/D [494 0 R /XYZ 56.6929 127.3877 null] +>> endobj +493 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R /F98 231 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +526 0 obj << +/Length 5323 +/Filter /FlateDecode +>> +stream +x??]]????}?_???a?Ua??^?^?i?iR???}H???????P????{@|$@??^?U>?8?!?p?? t??t'$??|???? e???*???oo????+??i??????q0?I??????, I??, R??0???~?????X???qp????t?????{8??285a??( +IJ?l6???q6?R +'????????y??V3S?????????? f+???W????????QNg????!KB??????????aD? ???A ?x6O????hs;????AQ )?f!??,?U????# ??T?|????9?%N??w??l?gi*?????[!??y?Ie??8K??N.?+pl?@???~&~r??4?$bQ??O?A?A????6?C`S.???P?]?1??f3??>???4?Q~???BS????????c?*??,?1?J??Kq??0?$"a????@???P????G?s?n??r[X @?h??????p?]?U:OH????J+{????*???O! ??????V?]???a??????zk{?_.??4??O!??e1Roe?[?q????S??h'???Un?A???? ?`???k+ ?*???YF?FW[????r9??????wG???%$???_wm????9????Y?$c???1x?\?,???,iN?;??++ Z?eX???dI??G???? ?qXl?izX???|?nz???? ??? +??*bj ????A?k?[]?c"?L?aJRg2????????Fy??D@????y|?? A??'??*??????? Ix?X>?w??z\/a??jH&Ap=?????!b|hC?DL?????????8???b5?S?K?O?r??4???????y??6n?,? }???N1K??t?u?? +G???????N*??$? ?????`?B?i.%???\??w"W??????!?W*??TI?=B?EE????????H_????>7>????9S?$?B6t?m????y?F?]?(?H??s?????????r?q}?z??"? v??s????v??YN ????^???F(??b???????EC????&?????5yB?.?s????($i?g a"O?????5j??Fz}BI?/@ZF?pq?*? ??????f`???eD?oDM????A??p???]|)??z??M?R????l??U??????[W;D|?P?L??????)EzOQ+?f???"????????e?0;?\~?????sN6?;YRK\T +P??FW?}?$?t???gK??&?$??JL????z#?????_,?, ?!??F,??? ?????+?????r 4????q?)??C +?f??)l??i!?????8??#?zva?~*?^?K?!??t????`,???UW?????^??Qi?zT??E?2?c?N?????t??m ?( ?$?????0?]?}=?????+??Rz ??????????\?k?#B?8Gj??0h??F;o?x????K??????EsU?????T?(>?T???????`???c+?xl??????y??`????gT??=???????????K?.??????BC??IU?????%dc ????R??R?N#x??G??'a?????Nh??O??h? ?[????????a?=????^VZ????>?? ????z??:v?g????^??O??e4I??>+?^VV?>??????)?&?vb4_?? L??~.?[??u#??%???1?????(???N?OA(? ???4????&?a?v?^??w???C?L?O????^N????9DZDYL?????? ??????V?????4???[a?????0u??g#4f??????&?D4e???????.?????;9???~jv??7wv)?|??z?'FE???C???#=??@ ???????)???cJ???K???(LCB?????qhM?????????o%PVO?? ?=?;???\X?#d?]?e??\X??????TJ???9??y3?a#????^?3???XXg??:???.m`ca?!?jmh?^??&????*????;??Vi?w???"c??/?`??r7NS???[ki?????UX?m[g?fA??EvV????F???Ks???????{?\?????UX?;?_s?&&?*?]s?I????M?1x??q~xW?fA?????p???]??&?#??nj???M?qu?[????7?E????\bc????lt??=??????S.j????????!??????? ?V'?????b[?????,????????p????1???$?oJhm????_?? +l?????=6?;B~?`{?l????????p>oKTh???endstream +endobj +525 0 obj << +/Type /Page +/Contents 526 0 R +/Resources 524 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 557 0 R +/Annots [ 530 0 R 531 0 R 532 0 R ] +>> endobj +530 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [342.6799 664.3934 440.3138 675.2726] +/Subtype/Link/A<> +>> endobj +531 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 562.6401 130.2369 573.544] +/Subtype/Link/A<> +>> endobj +532 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [306.5539 502.9987 440.0533 513.8778] +/Subtype/Link/A<> +>> endobj +527 0 obj << +/D [525 0 R /XYZ 56.6929 815.7613 null] +>> endobj +528 0 obj << +/D [525 0 R /XYZ 56.6929 759.0684 null] +>> endobj +529 0 obj << +/D [525 0 R /XYZ 56.6929 752.3934 null] +>> endobj +533 0 obj << +/D [525 0 R /XYZ 56.6929 470.0323 null] +>> endobj +534 0 obj << +/D [525 0 R /XYZ 56.6929 469.4545 null] +>> endobj +535 0 obj << +/D [525 0 R /XYZ 56.6929 458.4955 null] +>> endobj +536 0 obj << +/D [525 0 R /XYZ 56.6929 447.5366 null] +>> endobj +537 0 obj << +/D [525 0 R /XYZ 56.6929 425.6188 null] +>> endobj +538 0 obj << +/D [525 0 R /XYZ 56.6929 414.6599 null] +>> endobj +539 0 obj << +/D [525 0 R /XYZ 56.6929 403.701 null] +>> endobj +540 0 obj << +/D [525 0 R /XYZ 56.6929 392.7421 null] +>> endobj +541 0 obj << +/D [525 0 R /XYZ 56.6929 381.7832 null] +>> endobj +542 0 obj << +/D [525 0 R /XYZ 56.6929 370.8243 null] +>> endobj +543 0 obj << +/D [525 0 R /XYZ 56.6929 359.8654 null] +>> endobj +544 0 obj << +/D [525 0 R /XYZ 56.6929 348.9065 null] +>> endobj +545 0 obj << +/D [525 0 R /XYZ 56.6929 337.9476 null] +>> endobj +546 0 obj << +/D [525 0 R /XYZ 56.6929 326.9887 null] +>> endobj +547 0 obj << +/D [525 0 R /XYZ 56.6929 316.0298 null] +>> endobj +548 0 obj << +/D [525 0 R /XYZ 56.6929 305.0709 null] +>> endobj +549 0 obj << +/D [525 0 R /XYZ 56.6929 294.112 null] +>> endobj +550 0 obj << +/D [525 0 R /XYZ 56.6929 283.1531 null] +>> endobj +551 0 obj << +/D [525 0 R /XYZ 56.6929 261.2353 null] +>> endobj +552 0 obj << +/D [525 0 R /XYZ 56.6929 250.2764 null] +>> endobj +102 0 obj << +/D [525 0 R /XYZ 56.6929 212.0539 null] +>> endobj +553 0 obj << +/D [525 0 R /XYZ 56.6929 175.8891 null] +>> endobj +554 0 obj << +/D [525 0 R /XYZ 56.6929 150.0412 null] +>> endobj +555 0 obj << +/D [525 0 R /XYZ 56.6929 130.1159 null] +>> endobj +556 0 obj << +/D [525 0 R /XYZ 56.6929 98.2355 null] +>> endobj +524 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F92 225 0 R /F96 228 0 R /F57 148 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +560 0 obj << +/Length 4741 +/Filter /FlateDecode +>> +stream +x??]]s??}????>H3L??W'qf?&n??Ik?/i?-m??re7??? xA???3??4??W????X????W????????hV5/XU?|???e????3>?\B?????.???.K???(??V?????"gM}(U.??K?R?T6^??B?D@??MS,!??????)???.Dv~??????????????zs?????g?g}~???O??yq{?O????n??????????????~o}????????????O!????_?6??f3?;?[????n?? ???Q??????vG3"???????p????????_??^??? ??v{R?<:??y!??0?B?D?&???ANC??Ca??/??B?Y? +??O???N?y?????]o?8????}?t??]??~????5/^???3Z????7??Gzb?k8/4?/??W?hU??? +?K?!?9??I???f}?gD?^3?{?Rd,k2?s?b??9???/ju?9uw??]w??l?????????8:h{8?O?????c?t??j;???}?????????$7?q?t???? ?t??q?????????]??v????j??L??"K??a????R?d??K=E???d???J????W?n?f65?f?I9gBp??????4?*?,C?4????F^W???Ak????%??????2 f??~t?O?????$[oV??_????a?*k?ek2???? +Q????O???s5??|5????T/?F???ZP ? FC8??f??k??.8??@P?6???Ys??$?2???'?????|?n?\S(@??( +??????A?!<+?yC< ??UK??}???/?&?Sjg? -??a~???3??=?????j???n???PT/>?-f8???2?a?g3 +?g#f?4????w?j????k?T????? +???,k???I? ?$??W??u??,??Z??? hC??e ??D?&???Q?s????E?V???p?6???? m???L?l?Ix7??o????]?6j]?6?,Y???|f?(x/[?}?????{??S?&N?}????7??Y? +Y?m?g 2WkD??4????}?????? +??K"0G????MGUo]+zqd???????;)^ tR?3?g?K??N????n???????fQ?6?@ust.Ugde??????52??2??????A??+??)?pe*?1?B^???a7z??y^?B??b???e=??Ck????,s?+????v?5???l? +?v???=??:??y?.5?Q{?M??K??J]???????'?y??????"?r?2????x:???????A??|\3O?b???^V?T_??D7? ??3j?'?????v?R?:Jx2?qTk????:O??ne+?u9??&s*wk2?`2/??:<??????????Em?T???&????W?}???L^????0??O???z) +??!g?c???? X/[X?????<8? ??????????.N-p?E]?T??e&????)-????%1??(????Q+)????$??7j????8?LM??~ +?!?B*Y??7? ? +K?????~?]??e?=???h???Bd??~??H{}? +??? ??p *vrR?:B??}u?a???,A?#]1??(?U?XgL"??x??]N? +p>???&*??f???H???X????1??????1???? ??:??@???-??^.????c*?????Q%g56??&??(?t5???2???6 +?ts????n:?????????Z[?o??????????DAg=?Hg???z?:?? +???r??x??j????9?q???????Q=?p????????m???????8??U????Mg??MG?ra??$??td'????u??n:(?i7???*?T9OE-<?,?C??fsq?3?@N`B ????#??]m???X?c[???G9O?????5?S9[???7????e<???~6|??D?SU9????u?E??O*?b????E???OH?&.4m?Q??mMo?????Y??]2q?'??????qM??V??Z???C0?9?~??q?Y?RB?_?wnJ???|?????o???s?0?TDy ???,[?xF!?L??????g??I??6???Y?y??? &? +V????38?~?w??:?'??qpp7k?t?_?A??_??1?\?I??$??-9????g??Y????8?Q?8[x,2??}??@??c???t?;??????e???eTMB????SV?? i????? ?A@??????????L?@j?^?&t??lj?yg{????>??)#???Ztendstream +endobj +559 0 obj << +/Type /Page +/Contents 560 0 R +/Resources 558 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 557 0 R +>> endobj +561 0 obj << +/D [559 0 R /XYZ 56.6929 815.7613 null] +>> endobj +562 0 obj << +/D [559 0 R /XYZ 56.6929 759.0684 null] +>> endobj +563 0 obj << +/D [559 0 R /XYZ 56.6929 732.2374 null] +>> endobj +106 0 obj << +/D [559 0 R /XYZ 56.6929 702.5053 null] +>> endobj +564 0 obj << +/D [559 0 R /XYZ 56.6929 667.2187 null] +>> endobj +565 0 obj << +/D [559 0 R /XYZ 56.6929 648.7762 null] +>> endobj +566 0 obj << +/D [559 0 R /XYZ 56.6929 650.2357 null] +>> endobj +567 0 obj << +/D [559 0 R /XYZ 56.6929 639.2768 null] +>> endobj +110 0 obj << +/D [559 0 R /XYZ 56.6929 604.5727 null] +>> endobj +568 0 obj << +/D [559 0 R /XYZ 56.6929 578.7294 null] +>> endobj +569 0 obj << +/D [559 0 R /XYZ 56.6929 544.1788 null] +>> endobj +570 0 obj << +/D [559 0 R /XYZ 56.6929 545.5039 null] +>> endobj +571 0 obj << +/D [559 0 R /XYZ 56.6929 504.4775 null] +>> endobj +572 0 obj << +/D [559 0 R /XYZ 56.6929 505.8025 null] +>> endobj +573 0 obj << +/D [559 0 R /XYZ 56.6929 466.699 null] +>> endobj +574 0 obj << +/D [559 0 R /XYZ 56.6929 466.1012 null] +>> endobj +575 0 obj << +/D [559 0 R /XYZ 56.6929 426.9777 null] +>> endobj +576 0 obj << +/D [559 0 R /XYZ 56.6929 426.3998 null] +>> endobj +577 0 obj << +/D [559 0 R /XYZ 56.6929 385.3734 null] +>> endobj +578 0 obj << +/D [559 0 R /XYZ 56.6929 386.6985 null] +>> endobj +579 0 obj << +/D [559 0 R /XYZ 56.6929 345.6721 null] +>> endobj +580 0 obj << +/D [559 0 R /XYZ 56.6929 346.9971 null] +>> endobj +114 0 obj << +/D [559 0 R /XYZ 56.6929 312.2931 null] +>> endobj +581 0 obj << +/D [559 0 R /XYZ 56.6929 289.04 null] +>> endobj +582 0 obj << +/D [559 0 R /XYZ 56.6929 270.1143 null] +>> endobj +583 0 obj << +/D [559 0 R /XYZ 56.6929 271.4393 null] +>> endobj +584 0 obj << +/D [559 0 R /XYZ 56.6929 230.4129 null] +>> endobj +585 0 obj << +/D [559 0 R /XYZ 56.6929 231.7379 null] +>> endobj +118 0 obj << +/D [559 0 R /XYZ 56.6929 197.0339 null] +>> endobj +586 0 obj << +/D [559 0 R /XYZ 56.6929 173.7809 null] +>> endobj +587 0 obj << +/D [559 0 R /XYZ 56.6929 138.6325 null] +>> endobj +588 0 obj << +/D [559 0 R /XYZ 56.6929 139.9576 null] +>> endobj +589 0 obj << +/D [559 0 R /XYZ 56.6929 98.9312 null] +>> endobj +590 0 obj << +/D [559 0 R /XYZ 56.6929 100.2562 null] +>> endobj +558 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +593 0 obj << +/Length 1322 +/Filter /FlateDecode +>> +stream +x???Y??6???)??rQqIJ????J??(z?@?6e?l)?/??0?Rh??>?FQ?6m?????]?;q??4L?;??V/?|?????w/ZJ&????-i??H??,c??}??? +]??}?J???1??}9?^H?????B?>7?j?? ???f +~?*?j????????3??P]?T???:?? ??b?Ao~dA???????T-tgQ?:???dPgwx???-??nE??-1?TB|????b?d??z??$?lqJ?l?K??h|(?z ??????> endobj +596 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [170.804 721.5872 284.337 732.4912] +/Subtype/Link/A<> +>> endobj +594 0 obj << +/D [592 0 R /XYZ 56.6929 815.7613 null] +>> endobj +122 0 obj << +/D [592 0 R /XYZ 56.6929 759.0684 null] +>> endobj +595 0 obj << +/D [592 0 R /XYZ 56.6929 738.4887 null] +>> endobj +597 0 obj << +/D [592 0 R /XYZ 56.6929 712.6209 null] +>> endobj +598 0 obj << +/D [592 0 R /XYZ 56.6929 692.6956 null] +>> endobj +599 0 obj << +/D [592 0 R /XYZ 56.6929 672.7703 null] +>> endobj +600 0 obj << +/D [592 0 R /XYZ 56.6929 652.845 null] +>> endobj +601 0 obj << +/D [592 0 R /XYZ 56.6929 632.9197 null] +>> endobj +602 0 obj << +/D [592 0 R /XYZ 56.6929 612.9945 null] +>> endobj +603 0 obj << +/D [592 0 R /XYZ 56.6929 581.114 null] +>> endobj +604 0 obj << +/D [592 0 R /XYZ 56.6929 561.1887 null] +>> endobj +605 0 obj << +/D [592 0 R /XYZ 56.6929 529.3083 null] +>> endobj +591 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +606 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozeng e/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis] +>> endobj +230 0 obj << +/Length1 1647 +/Length2 8562 +/Length3 532 +/Length 9439 +/Filter /FlateDecode +>> +stream +x??weT???.?-8$@?F?????? +4?44nA?C  ????@?????????s?????3s~?u{?????T=U???????TUg?BMA?P[GVvA?2b????(CY?@N??&6?'???V +2qCm?MA?m +2pr8?iRP;7???@???????????&S? O?` [???3?j?:>Q???A ??%`??TTu?????(k??lA??"T?Lm?fE????0??6-fP[ ?wi?O\??? ??r5????v ???? ;,`&??Og??m?l???x?7??I?}????V???e?"??????? +n?v?? +?=mD6?[?@?????3q???6?? ??'?i?{?+.!??e??Xx?f?{?L??? ?zt??C???C at si????ke$aN5^y?????????{tw?? ???2?F?? +9#>? ??O%{?Y????XS?s,??g?????>?0q?riz7?Q????? ???K??`4???J??|???????\??I??f-}n??n?y?S?e????:n???3? {?? K?Sw?PB[1[[V_U?i??sMw????R????.????R?????5nL???7!{?x0R.EVX?Jc{?4???&>/??g?U!?P?????q???e+?(???{T2/?`?????{)GrU???n??vM???????R????:??2w??h?g?????|*^w??A??h?????\s??&??o? +kU???Nq4?j?@?[?`?P? |+l?a&?^??? +??o??&??3?o?k?]7??--?9?o????????uxg??<^???E??!?????k???(?zy*?\?%????_?Re?e?????y|?(e?????c`2???j@????*??b??~N???NHE?r???????=??B&?M????#w,i??b??i??qJ??D?I?p?{?????g?kkf=;gd"D?5?\??????5?N????oc D??w???5.E??j6??,A??O?????iUn??2??z?q*??uZ???>??a?!?S??????^??/???P?$??n???U??%????]r6?p??????:??P?t,5? +@???}u +??????1~?$2??f???NH?H?2??3?????-I?????}????X?R??????6jSn4???i]D?r???????>???j?Bm????m(? ?%_???x@????w?u??m??Fd?|:?2??=????+?V???.??)?.? ???2???c,c?????8]?1U[?^?? ??=?y??0!Uh?/"H??,??Vy\????:??q?cI?-???oYL???-9?[?E}{??&[? ??N(??A??1?????? ]{?Xs? g???G?????l??0?? +?????]????,u/?????_?????QY)?{5??5Q??n#????????H5k?x ??L?Q1 ???qE0???I"???? ~8F9"????UP??V?e=????I??D^4?^,??YZg??S[g??9f3????8T? ??=|v???XW??????????;??? ??????272?????????l-=??w???fJ?-?J?;?7?F????[?????_?l???['Y?-9????wCA???Fb?C??\?M?? ?0???r????????`??gOp.??????`,?????!b-h??x(1W??)??q????5???U?S?je at Q?dXUy????4???jD??(?????{j"s??J?v?f??yl???`8,?,/x?Q#?h^??y???,3????% ?7F ??|???R_?????I?XG??w w??-t5???zb?K?\?]w????J!?+t??D?9&???K?)6??????h ???bL?????4??y' +'??$?3?^??t??I&DHj????????U?Tf?z?? 7?x?C.i$Qd?????q?{?{????s???+?[?nm#??16)??? +???S{???%dj???n2HT?K??%Ovp?{&?B????~?W?F???m~4D.??Qk?5??Y??? +?W ?h??Lc?HO???h???F?? ?R9???\???*v?? 4??yX?V?]O9 ???u;=?h ???6? +???0.???9?)?OC?>?k??AK35????%???j??~???*(?X???])????P;??w91??H???????6.??????C??v?g?Nm????;???????[??d??%?#4q! +??&???v?R>m=,??$Q?+?&i9H0? SU?{???<?)? +c|???L7???#???oE`??XL?y?4???v?`??1sFV?{R9???G? +\/???TV?R??8????????Z??oP?&80??J??????{\??????5??????5`-?1???????[ ??@X?{??g,?A???Q:??B??A?:*??H'???w?1???[?7??? +????&?%?H???kgr?,??? ?V?2??^(?\?????.4? ???C??????n?Y??r?h?(4??k??"??o??X?Ws??}?k"?V????OX\h????MsZ???q?9??'????u]x??X??7]?g&??????}??;?b8B?9???W???} ?n0i????.v ???7???? /B? ???D?h~?},,Fp??,c?:]?Jzb?h?E?F??7\pNNf)????Zy*T??0?????H??y?C????|?[o,E?;LD?qA?????????8'-??z?? +A>H| +??i?5$S???4??Q???DJ???l???/, +k??? +?&?>??a?????e? +???i?\???#???U????t?s'2Z_?? +Q??I|??_???????qA\2?N?#'?On???U?(z?h;\??p?????v??G?6???? +???gS?T8a/?O?n?}????&?????nN?L????#fM????^?\`?39$?$5?+??? 8JB@*????$?;?4??"??Y?7?h{A?B?,?l??I?1??%??$??)?y??B????? ?KN???????wK?????????:??o92? q%o??O1R???s??V???3P????????r?PJ=)??????2???A^?? +y`}?]K,???}??&?k?i???? #??:]???)w?/?]????? ?\??????^9l??I??dp????F) ??f[g???Y???_?P??? D???s'???UB?l??`E?????/U.??p?rB??$???????;He?m?????? + +,? +?+:??s~????Zo!9?`?D~fb??b?xx>f;???2??w/p>~?B?LR_?h?R/?????????rQ???7V"???????Yt(???????I????%??^o??cF??Z?P? +j +?]a?X??=??? ???????E?q?=g??0 ??Ui ??.?????e??*??B?J +?1*?H??h??KM??????t?]?L??G???~?.?rq} ?'????p +???)???6????????????>?A?J????o???? +??zM?*?_?wf????u ?zn?????????|_z?s9???s ?G9?4"??)?dk?????EO%{???6?sH??.l*?'?Q??E{_???x??????aW??gcVc??O?????5 UynM?a??z????*?uU+???5Q?s 7#?? j?? ????N?5a?????P?i????????bh???@@? ?? +f?vcm ])???9???}??@?S????'??H??X7?.Wo??1???[Q?,w?2y4?D?n??"??3X??D???M???&???x?y?5?c????? ?(?E????FM7???????mY=P?? ????#x07?|z?9"?U?}??f4[????/?g???????j??/? ???J5?? +~?u)!?2??E???Ae??????@?j????x??`8O??i?j?f??? ??d=?e$??d??3r????o????f?g?E*? 8 +G?????_?8?`???bwKr?="1?|???Y^w?-??%??????????Vv??e??g+?e?:??c:?G??????? ?-???/v?{????0IZ/?fQ?V?????cL???~u?? ??q??f??5?????????g?G??~kd?? ???&??W?U?_?-j[?Rc/??of????:C????|u??^W?? +t??N(T??\z_????N??}?!??ky?7l??? +?Q?E?D#????????M????}?KU???:Y?J?<[F?L??P??^0]??_`?(Mtz`?J?$??????=2"?r??????[u??}????R.????z?2???????????????????v??LM?p?\???|t?a??eXN?O??*w?W|?:??7??E>'?[???>????AVOl?Cq?w???????l'?????*IQ????B2??w???j?XB??]?fi?.????"|NDZj??|???K?? L?-9??h???f?? q?Fh?R&????`4\c??~???s??lf????E?!??i???N+?? s?`/???? ???O??x??.???e@?~?`e'??????7?GDd?O??cYup/{qCl?3R1??>8(?#.?Y???????.g$u(??Qt$???Z???s?$.??Is?t?xp???? ??Wr??+?G\??'????p?1,??????`???o=?2 "??o???8?{???:?fT??j?]0??????@;?} +??"f??:$w;??? H0??>\ +???????S???N?{Q]???~??+aX????p?#?L2I?.??P??I??Xk??-????,?mf}HWS?8?N7T???5????%?8?2k????Eo????Nk?jrA???a2???r?j? +?kM ????%8w???e??? ?????@??? 8????l????????R/??RWg????}7{?? ?P\?6?\?g?M?I%????w??G??????>???$?K??? ???i?~?,W????_?r?^W/n??2U?IJ?'r5??Wpz "v??xx????u?Y?4?I??PO??LQB??????`p~kxP??%WO\e"???j$A ??J??6??UD???v?W???I?j?|??iQ?BY?^sK??????N??????1? +M???????????K^1Q???75???.6??M???????X?o}Pt??????T????N@%u????.'n????QIU??????O?~f?_=}!??p???;????R??u(l??R??y??? u??o??(k?W?'??(I??%*2,_?-zI?:bz?x??Y?s#?9F??????GP?7U8R??G?0????9?&"?;??_??c^?x2?%???Id&,?L*0?????9????^?v???7???lv6?*??`93???[??!?????pk???Cqcr???F??YBJV??????O???? +??????????C?endstream +endobj +231 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 120 +/Widths 607 0 R +/BaseFont /SEIUYP+NimbusRomNo9L-ReguItal +/FontDescriptor 229 0 R +>> endobj +229 0 obj << +/Ascent 669 +/CapHeight 669 +/Descent -193 +/FontName /SEIUYP+NimbusRomNo9L-ReguItal +/ItalicAngle -15.5 +/StemV 78 +/XHeight 441 +/FontBBox [-169 -270 1010 924] +/Flags 4 +/CharSet (/fi/hyphen/a/b/c/e/f/g/h/i/k/l/m/n/o/p/r/s/t/u/x) +/FontFile 230 0 R +>> endobj +607 0 obj +[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 444 0 444 278 500 500 278 0 444 278 722 500 500 500 0 389 389 278 500 0 0 444 ] +endobj +227 0 obj << +/Length1 761 +/Length2 1025 +/Length3 532 +/Length 1574 +/Filter /FlateDecode +>> +stream +x??RiTW?S +??P%.?!F?H6?P??D#DQ?EA3/0&?????h???*??TQYTZ??(Z??7???????VPk??)?l?t??w???w???c9?G?KPb?8????? X.??y???x +????d??b????4?<?[,? ?,LhSI,1?????7?h ?)?* jh???T*H?j0??#????L?(???SP`L?p?G? W??M?i??R ?L???2????:?P??N'?i???o??K.????M}?S? +?N}? 4ZI 'PH?}????89D1??oUF!jL!????=9qd?F|??x7?_?????5??????h+??v???r?v_?}?w!??z??kW_???Zz??????????pX???????[?E???ax\n???ff??F??OrD????????c???g???5:??????????????GB?R/???7?6!?Ls???*+ -Y?I},?U*?x???=?????G?6r3????c"?$k????????/ +8dl at M]=N?-{? )?????q?6???????ii??k????g????,"?6d?1???gMStv?!Ug???{?97N??D??;?u.~1{???1???3p???^i??c??[7w???BM?# uliB]?N&??q?S'?T??X-?X;_?/2Fq?[?x9Sa??b?}#p? |???n?[?u?N?\???r??????????????????Nd?????.??n*?X;?D??????mw??u&;?Y??A??????3???=?4?7???> endobj +226 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /ILEVCY+CMMI10 +/ItalicAngle -14.04 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/arrowhookright) +/FontFile 227 0 R +>> endobj +609 0 obj +[278 ] +endobj +608 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 45/arrowhookright 46/.notdef] +>> endobj +224 0 obj << +/Length1 753 +/Length2 637 +/Length3 532 +/Length 1177 +/Filter /FlateDecode +>> +stream +x??R{PTU.? ??+ z?!T??]\?G???B?k#1?r??????x? ??kP?2J"|?pJ?B?X?gE?0? ???C]P? ?????????????????*????aM?|T??R?T B<= ?X???`, ??? +dz +@%@$ +?$R?(?d#CjX?N?~?$2dH??c????1-P?8 Y???Z5???` +dR!!@P$??x?!)D8?(?R?@?p??'??R!????8??g??)?P??h?,?9?/L-?k?a?nN~>??pLGj???.Y?B(i2?B?v????^? +a1-??(?>?Q ??<?? ?????????}H ?p??*#??(C???<????1??|?>????v?"???x????N$?b?/?3"??* ???"?@?X(?h?k\4?@M3???????????P??A??w??i?????}9m?R?$?D\?0?b?? ???ZMr)Bh?8??C????/?W???t?9;??L?g???7??e? ?L??,r??=3z?ZS??K?Z? +?????N8??1??z????w??????9?? +x???n???'?*J#/???????_?n?kl?Sp?&?????????Gn-?84q_?>?????????????#\Y?r5?S?PvQa??)???t?Rv.m??y??>???-???_????cXZ?1I??mZ?endstream +endobj +225 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 610 0 R +/FirstChar 32 +/LastChar 32 +/Widths 611 0 R +/BaseFont /MPWXML+CMSY10 +/FontDescriptor 223 0 R +>> endobj +223 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /MPWXML+CMSY10 +/ItalicAngle -14.035 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/arrowleft) +/FontFile 224 0 R +>> endobj +611 0 obj +[1000 ] +endobj +610 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 32/arrowleft 33/.notdef] +>> endobj +191 0 obj << +/Length1 1612 +/Length2 17846 +/Length3 532 +/Length 18762 +/Filter /FlateDecode +>> +stream +x???c????%?v?Qi??m??i??m[??m??J???????_?s??????c<+0cF?Xk?*(? +????l?i???,l?\?d?leh?f.??0????Cg ;[Cg?:??@`L??D???? CJ lg??haf?L@???NIMM?_?B?) I?????Y??m??G2xF?O???D?Q????L?`? ?|??? ??O3?t????I?ld??#?-??S?W?M +?[?|????bWY?[+?)?h?K5?p????????9??<'?6.e?iI????o???B?$O??.???yK??Y3[?a??????HP?????q???G??u??6IB?;?c??6?????2??V?E??????v?vs???Q_?$?p?xbxt????0?????L?[??????P?!t"???"??5=Fe????F?0}'Y???g +??X??T???????u???p??8?h???7?F[V?????E"??ap?w? ??xPOx3???L??1??????.?X?pb? ?FE~?Qs??+?L??FN?/??O?2??}#9^$?|S?p?>lM%T Y???????MR?p?Th??nCvF0??????y )PrP#???????^nY?fk7"????f?Z??0??8??~Y&???|?huK??"9N?tY? +??e??-2#????kLg???a-6g?X??m???^???A0MTC??F???Z?Y??E}M?????i?????N??3??R !?N>???m?bS??g?.P?+ _?#S?&?m??-a?yh?q;!l?%n?????? 9???[C?^???????????????????(?{b????-m?K&Gu?u???? ?? ??? 'C??_e?4??A"<*??L?n7?("??????????9???????v0f?*b_l???HV??c???v?Y]?????;??????4?9[j?b??v?A?f?l?{[P1?A??@L?*G?t?]jpANw??k??e6 +?????`\f??????2j?-?;??C??? +??iC????jd????SG????uh'!???-?????W??? 9?5r?k??LN???+??I???!?X?k?y?b?+..????n??\?O???,?v?#H?7.@ ??C?????????A?/gx{T?}e? +W7 c?Dx??,\{i?N?&??Yw?4+w?U?(?j?? ? ?F??zcL???o?`2]_V7?F??2?/?g<y?@+'PB?%|A?"?W???)!?~DtY?i???y/?????K????7??q??U???h?a?u +f:G +???L???q? +?q???h?<???Jo???Y???n?A? +? e???<&?d?- ?????S?sW>>B@?3K?@ ?#????k??@qn +??HXr|W???"?????4u??7N7>????? +(_??g???? +???|>s>?h?h????T??@??lWr???B?pl???????&???kc?>?)?????? +?U?g??)??72?]{m7 at A????? +^???t???CL0'?o?H[d??:???U??F-??F???? ? +??????45?<???T?m???u??U?h8???C???Cg=?D????x@???6?????l?!?A"uv?H???????G? _Z?8????=?>~?y???|?K????? ?N?2>,S??ot1???M?KU\,Te\??????????m?^[?Wzg???| +???'.???*c????????Ho-??^ ? ??,D??D???D?1 +Qc9&??Pi??n,??u1?Bk?[vh???*??@? ?"?O?:I??xl>w???+?X??????Q?_h?#?,0?%]9?????P?,+~o??ZF?p?????S?"???( +n???Pv`!??*???v?? lO??9?]?}D???v?q???}-??(???O??q{-?894?wATq?K \?4?t?Fw?o0???G?S?wnB???}Q??4;k? +h x?A??i?`??\???fwdr?38?b?{d?we??:? +?N??n??????=?N?A??x?/9l&?D:?B? d???W???-V?#GY????h|???S{??x?fo??|?d???j??g?7?8F??L??w\<4? ES.uM_????vJ?????a?????[4???????=??>???]tv???? ??A)GCm)?;&?????1?:?P?i?'Uh??69zh???t?Je????sdU-???????"ob????V{]@6?.?L??????QQ2???[=_???s?i7??(?#p?i???Mk??U?????(?'???PR???x??.??x6W??i?T??=n?22?0l???R??????????mud??P?+?c???nL??tdq2:??t?~R|??zK?8t????q????*B?1c?"?Z??j?E?????? +?U????? +?>??r???????B7?i?XU4Os +?'?[??t ???X??? Z?(???h?????f&??P2?6??????+??i????Sn0??$?????nd1 i???H????w?f??????i??Na?s?????4???>???? ~&???a?????? +??"@??7(?t???[&o??^*??4J?uG?l???gl?4??? ???T ^H?"?:??????? ??????<(|?& ???! _|?!,m?=???????r???`B?< ??????%?B???pF?Y??'????????+??3&?????? xb?U?[/GL?B???? ??s????P?e??r?r??? +??:?k8Zs?? ??G?;l?)?)`??????$????????!+?H??_m? ?Z????5l?J?K??z.l=i?~_?W,"kjz??6~???a???r????W???%??? ???`~?)[?/?N+?N/?d???l?Z(?????????L????^I`?qi?4??G??l`:(?E????0_?Z?? 6g????Jc}?8??Z???N??}???"???N???*??'J??I?S?Xx6?'?`??%??5??W????W?????*?/?{4?"??-??[??R??}i?$`?/U?`???5P?5? ?\???k???j2FG?\????????xs??Lfwf? ?A ?,n???O. ??@1??M{6Ay?H?3^???j? +?z?`1?P??){??6??bwB ?D ?^?Z/???C?? +?N?f?K,ux?X7r??wBB ????bs?[??3+???? ???B=???+??o??f1]?9??? +J?h?9??(M??v?fM?????i????+?#fDUs?2??R? +t?j??o???[???(]f?'?????J2?????m2???kHB??RO?:)Hd?{?y?s??0?"?#{?_f??3Q' a;?C?A?U?<`? ??iWX'a??? +?"5??!??F??~W?R?N*?I?0p?{?????,???v?x\?J??\????mD{?????81???5 ??5j*i???????w8??]?:8??1? ?=???lf??????????????*?????(ic ????? +?B?S?w?????tv@??[cNU?1?{B?,????T??r????t????_? +???C[)??B8?Z +_J1??z(??p?g"??QCA????k?^R?;?eQ+?_^myxjA|???,?JG[?Dqq??j0%!?N???zBs?t?9???WpOn??sve3??I?n???@'???A\?%????e??U?#?5%????;\'m?0`???f?9? ?@D????qe1????4D|]?t?C2?????/?f?????{???Ty?????f????(??J???????!???)v|?,???/??9??s?C?0ko1r?j~UMu? +?e?(/V?i?Y??[*[?m?)?T?d+?????$~f*a???????2??M?!)?t+W????&??/?{jK')vZ?eLD?j??T?erY|?^w??b?????A??G?V>?4?i??]+?_?? +/??MZU?FE~ ?n????u]???@?R?n?b?Aia?P?????C?E????9???{*??{?(??G?1^??\?^????B? +? ??l +??'<+??JS?l?` +QT?4\r??s????p??y??l4?1???j?}(T ?,E3Zs?&????.?%B?????&PYa??w?????!??T?????o??.:?3???\?O??o^??c?;?$????,???-?-*????1>??^?M?6X_"K???q??????G3?N???S?O?L?*%?Y??C)A8u??2??2??r??#B?k????-).?????53??_T???}H?????J?7?)???}? ?~??????hKu"V?gXA??^A???S???_?P????X??9??!)??J2??r?}??N?????????mO#???????? ???U&?B???cX ??k?&?+????y*n8???em?~??????}|KT???cO?s??Y$?'?? 3&K??2_S?K.h%?Q??L$???D?EP?????}]?j +S? ??eu)???&???w???????MEp?b??}|??CXh0?9??;?"t ?3g????^?2HpZ_??O???6e?=\???? ?B$f????u?????L??8'??-kZQ???q???t???:???&?? +? ??..4[??6???p?!uf??N??rK??V???????#x?.?%$$?8%F?m{GT??Z? ?: +:u?%Xz7X^ +??????5?????q?a??5??????/k#???.?~???$t[?}$B????Bx????{?1?)?wc??/zf? ???np{?;Q??Y??^??-?e}n?p? +OK%R??I??????@G?Q?'??*w??!4???`?t|?c&?????q???J?P?Ia0x???2o?8????+???J*W,S?????@????Z??V???T????]??u???HE????2????o?m?"M?L??D?t?T??l?????K?}L5 )??K???B?$C????PS =?Y5SdQa^lg3???????? +????G??g?0vE???U?%? $ 8?M=FZ-6x???4?"g????)?EK?l%R?4??h?????HM?M?j??uD{=???"*1`?,?????:?T?s/?0 ??Bn???GH?\??Xw o-?????U +L?sI??E?n:?f??3???54a?[???C??n?}!f??k?3??9??A?]??????S?7-?? ?qb??b??7?? ?????I?{7??N?N? p????lV?\IB2qf7AG?/y![M?F=Fr???EkN6??L??k Dq???RU??lZ?,?M??D ????x???M??? +K?? +k ????X???] k??ExB??=SB];-??<+@?JA6,?2??{ +???d????7?'??7????/???k?P?uD??u???~%]???`K????6?VFo????9G???z~^??I{{?)????m?=` ?jC _+v?}??:???????U?/?????[??y?????rn???.I?=G&????????g?+?????&Q???????????n&'??n?O?M????T??%xx???X???B??$W???-????o?????zok?B??8???f?-bD???]X??j??r?????-?N??/???;M??.s?k~8?b{?o.??;?:??I???p?????y?G??`C6h?1 "?.?]??nX?#?BL/??J;??HG?w?7??Q_??? +?) ?le=?h?E}9? +o-k???????Q?l?K^???^ ???????"?\??? +????[??e???#??1??r????????=??Ft/%z? ?~H ???Z??:l?P????h?QV??nI?C?g????? ?]?9N??Eo?-? +?$????V??!??$?v????6?yq?z.?~??F??i???]???o?*?v2??PI?? + ???@F??6d??????8F`:@(??????T?Z? ?MJ1Wq????u???????L??@?K??n?2j:?B?????XAU??"x?N?{????v? 2??b?72M???e?+??o ????7D??????N???7e?r??x??hx????8???y??4u ?Bo[???EL28??l????(?`???#?????xZ?R??? ???????)???-[?t??@l?A9???*?????l?b?i??f??"6N??????E?GX?>@?)?E??'?????????a2?@? n5??G?;??????????B?a??#3?;w@??^?w{^??%?Q\9iQ!=G?(??ab????c2"A???J??lB?????)??R??s?????'?[??;?B??_????N|?z3P +??z?A??{m?L:}???7??7??S?S???????I7??4?sl`??????u??\R????I?u0?S?%?}?_??z?I??Jm~??t???J?L?.3?? >BY?N,?g???0'KG??8??o}o??ca???*??????6?D?????\??{??f???C??1~'"?o? ???*??jM.J +??':E:?????H???_???,E1?jO?Sw?uJiGI???5v?t???\'1???/? ?_^??kG??X,u??~???????????[???f:?? ?? ??Yc?c ?RszMu??????,,???]?b?rG"?p??Cwz??%? ?*?99 ??R?1?uH_??9???? ??????D?oC?????>? ?<?x?4????&???7??.5N?V??vG??????I?d???2^?E??h???`?? ????FZ?+??y?&{p-????????J?'1+Ky??,:??mc:?;L???p?7??FG????????????b??$h???]?k? ??R?0?s??!??G?>DU? ???s?????:GXJ????=??I,?? ?O??*??L??n???~???N?!y?|???8??? +????????F8x??b?TSl?t??;???????(h)!????*5Bd?*?w?Y?rF?@???yV????P??Q?}????A?????? b?<&_??v ?8H?)u?vb????wWT5Pz?}?k??H???? +?=:??e?n=????>??Jd?Cf +?k???zoS???nG.?!jP0a?#.?S?%?D-W?j8?~e???7?=hpfx_??c??O?L?1??_$??sA???g???S?5(???1wj??{C?.???U?}?GE+*YN????8G??OF?d??Di?{??~R?&?B%????R??? ???Q??^???5K1?b???8?????do?@?!??????M????? cD??LO8????6G??,??????eX?@:??c? ??Gn?C??????h??? 1@???7?????6Z?L?????U ?z+F+??"?? ?V?C4 ?o???{??/????]4:???k}SjT????????? h:6???\?o???Eq?\??/E?N?H??????( ?r1t7Z8????.ULt!9 ?B?{F?? (AM!p?Q5??C?On??:??Ka??_i???hA??d?B??hAC2?/??}b -Y?S??q??O?f???,? +&?Y?c????????M?C?|'W W?( q~O??3'??Ho?????G?5A??r???A$????hC?D?O???/?p)g&???W?z|???\?<'?~? ?? Vy?e?-?|?/?yG(rH7YQ#A???A??{?ar?4?_80l?A??? )???%?c??Yh?(r???\W?.?t? O?H?G????U??&M???????~P?????l?#??sp?????9f?=b?rP??cL8hh?`??b +x?3C???Bkf?x%??????#??c? ??e4??*??&??/???6??9???????0g??/AjlA??Q?????+?X?_??@??l??+n?#Q???a?~??????g??v|?a??A?7%??}+?l?@?e!,???)@{ 3VG???h???0?9m? +??????W???I?? +w_}?? ? ?? +???"?n\?N?Sc??????;Tk?&)??b????sS????? ????>Q??-??'m?+? + +?????k??$1??lI???w?EhA'8s?O? ?? +??/I(???'_????N??A??'?L???:7?w?,p*?.]~?????r9?$g??i?5?@???L??(?G?6?eT??????A?eI? n??k??7yF?_?&?rQ???q!?f?7L?7 +?QL??iv??x=?*?&`?????Q??????PLM?zhZ?s??$:?F???????[?p5.??8&??"v????1#?????s?5??wVs???&?%???i_!?X??wK?????????`?o?Bz??????"??e????p??G@?=?TiS?O??Q*?z +f,B`??uu*???2T1???W?zX>??%5???? +K?Q?????W?IBK?vY<L???%?Dz{????L?p??????b??=_????&2%??>?$9P$? d???????Z|??0%?D???????$???]???i3w???hi???????(r???????|?a?$??>???]?%5??< ??U?????T????=???d?I?%7V*}.??N?4?d??k???kf[K??Zu?/ qI???&4??u??d&V??????HV??Q????7?-#Kt"??n????"* :?|????4??-T?????+??`i$?7????^83*G???: ??????6?W?l +??ftd?z"?sexX~=|:`C?;;???$????(v??sP#???k?BI?? ?????????R?w?K????2?4??I?E??W?'"??"???? ?>???c?V???p?;?PI???D?%:?YDiYP+?/H??s:?%@(?L6??'??l???h3? +&K??"? ??|?<2???j?+??{? '?O|?v????v??????K?$^vie??Apg?????????I?>????????????? B.;m?`??:?x?:?? +K????!???????g ??????G sc??????a?/ +???j??%????%;{????^3]?A?????-??R??j?e??'x0?72*,?72??_?P?endstream +endobj +192 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 33 +/LastChar 126 +/Widths 612 0 R +/BaseFont /QTEVNQ+NimbusMonL-Regu +/FontDescriptor 190 0 R +>> endobj +190 0 obj << +/Ascent 625 +/CapHeight 557 +/Descent -147 +/FontName /QTEVNQ+NimbusMonL-Regu +/ItalicAngle 0 +/StemV 41 +/XHeight 426 +/FontBBox [-12 -237 650 811] +/Flags 4 +/CharSet (/exclam/quotedbl/numbersign/dollar/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/R/S/T/U/V/X/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/braceright/asciitilde) +/FontFile 191 0 R +>> endobj +612 0 obj +[600 600 600 600 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 0 600 600 600 600 600 0 600 0 0 600 600 600 0 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 ] +endobj +147 0 obj << +/Length1 1626 +/Length2 14351 +/Length3 532 +/Length 15230 +/Filter /FlateDecode +>> +stream +x??veT]??-????????Cpv????KpH?`?%$???????}??o????y???xg?3?^U?f??Yk?MM???,n?hn)?vcfga????]5T????--@?w;75??????,e?f)???HYv~~~$j????? ??? +@???K????O?_[????y?tY?4????N?`?w???@MKK???%? +do ?TU??W????hd-??.f?5ws{?Z?]-?V?.?,@G????\Y???]fW'K ?=?? h???? ?d??ru}?\?.f`???9@`????_??V?rrq|????{Sstus?????Y??d???????????w7???}??#?????????{??@`W?????_??- W'{3????`N.??i??????d?p??6s???tu}?y???;?????7sr???;???]????jio??????????Fb?kV??V?v??-?????a??w?????wf?`{o???????{J????,?s"?H??"?????=q?U??t?????_?e???U???w ???1????????? 1s?{????u?????J8?[??O????%?`?wY?X??a????,-?@n@????{???k?-,]?A`?w]?n)?????_|Z6 ??/????[?+?w??&?*????)??_\?oT{7-o?wn?V????,????p??2????9?????;!~6??"??@??\+??????u???]?????2?i0??????t3[?O??r?]\?????W????g????????(f??9???o`T????z ???A?kaP?cg`f???sM8K???k?????????P?=mg??Y??%}w!?*M/?n?q)j??n?????:?G6???Qu +??g8??6N??;? J?? ?['?`F}"n;F#Vm??1M???-m???@?%l?1cn""?? *Ml?s.??G? +??H?*4lO +????#?\???t?????C?D????A?oR???=????|+3???h?M?o???$??'?Y?m???6??D??????4??????&J???p???$?>??,??`)??g+?????f??[!T?R???O?*?L???3[??2?O??I?hM at Ih?X5??/5?t%?"??????c!? mb?=?1I8K? +k.\L?5?Tx???6??????C???1%?z???^?(?]iu??+\?_RR????G?J???v|?*q?`?JOm?I?L??{T????0????-e?, ???z?Z$3cS????}"?=8f\V???????6 Mp???DG????a$um@[?????z?????eI? +E*}?Wa?(?!????2R??u?[W?@?$E?K.?1`?~ ?,Eg? 5\???$s???1# ?Xc??H?\Z???????H??M?T?.?)??1gc?m??B`???N?a(?2|??K??&e\TM;PC???? +???????>?.d???_a<6?W[???????T??=?|. +?C???=,???U?z??G?YR9e?\9y???[?0??y?O??V`?d>Y??"?$?8?F??b??,??? I?RG??x????????`???~A?S???ck=????? +?!>Y??Hk????h?st?F+%????2\E>???^?Wb3M???S?%???????c????????6 +?n????C?d?oT?C?j?K????n???0o????a?????Jmkw?!??????Ko?2|???@p?=?n?N???/?"?V7?w?d??v??P?????x???UaG????I?UP??H????u?y?????!?gE??a??q?p up?V???3?? ???R8A??l?Q?h??C??4?Sr??B???V+[?????6??_??4G?d?????^????[??H????c???????Y??8?30g?!?ws??C,e?q?X???p?N??X ?? ?!???5Nj??M????$?=?0 +??????\?/????4dw????????. 'I???????zC?$?????>3.0??0??_???c??0U1-P??y?s???????*?? +?u'd?*:D2??R?C????%g(???>???3L3?H??yi?>`i?,B?U?0Q???mn???O3????i??"'^k? +??I>??? +?T???R+?a?| .?? >uYK??5v????jZ??S??$]???+rEc?)??????Q??h????d?lQ3H_6,? +/??Q???ob?0ZmC?????;9?T ???s??VSoE?d?y&??+?/r?m;?*??sL???&??.?4o-?R7ex?"?0jD?vm??Eg?{j0~?????? ?T?M*:?1>??Z?y ?}[?;??O)C?????V"F?MSm??pl??h?j(b????????z???I at h????Do? +? .?????o6sB???y?\? +??pm?IO??I?????I\??????7=~?????? E?8>?5????:??? +???=$t?l??k}?~?j?X?????S???[D?L?F?u?IE??O(t?????kry.&???5? ?/????%*?Q???'??h??(u???#;f?g#????[?:?45?"]?1zb??)1?3???_?KhH?I}????i??o%?-???y???-??`kG?~?????p~6?6#V??Q?sL?? +?M???J?Oy?p?X?U+d?s???$?@?T?'??y?????O? ????=/???r?:4?????X?OI+'wfL?i?Pu??|i?????V?h??h?G%????????m?{??%??[??qc?4g?Iq +?W?t?k +???????V??0,X?l!W?????(????p?y????)|?d?7? ??K??&;???b;?&?Sq?{?q?H2TmO?f?HLdL~~? $??h?J?Y?)S?Q??FB?P??P??Xx@&@??ms????S??[??rG3??Y??I??Fe*??B+L\?????]????>F??Jv??m??`X???n????}AM?^?+D????^??oS??pQ??b?????6p??g'????5s?u3?V?:?/?????Q?k1?Je?N?X=?}???s=???9?xlg\?????????H?~??P?Q???hr?/?B[????]'?9z?????U*Bs???ifiD?bby?1??+????m??1????Y?3I?w???x?%8FJi2c???L??????I??&.:?{?????o??8?ue{???????j????`$??25?????}#?4*????????`?Z??a?0{???>?????Z@D?Q?L +??X????4??? ???f1?/FOe{???M?~?????eY????~8 Esr*? +?@??'??4?"??]OA?s???]??,?w;?w???%?N|TM?I_??d?oE??n?'rZf4dzL? ???8???Hi??????U?kq7?S[?????U?0????:?/??`?$ ???h?f??+!S???J??*k=???T?"8?????q??b????K?? +?i???q>?? +????? ??^WW????L????]?????)????nX?B.n?G????_t?Z?X?????fX? $u?hu:F?c? P?z8.),????`?=m?~??Y??"M??? ?L?*?Q9?X??o?1? +?\??J?i?fdB???????????tb?>?U??(0D???M??a??h$_?|IM?@g?)5)?Avj??'?- +u??L+W??~b???A?t????+???%?H?J=??=?;yYp?g?U??'???????f ?4??:?=V]??!?%??T<_???????!+s???(?kb?=/A???????O?Z|P?}]????D ?YB?=y3?O??WN Sj?pe??????y?P???????`B|???AWZ?????????????\X?EQ? +?\?????A?P?(??D1?d:AFu1O?????j?R(???% +rQR??F???$l?Gh2???a8k?P??T ?GHS?j?.*.-@=?)??n%?9?S|9L?~?????A8e?]?wx?w?$?h?G??7Pu???$????v???????R?Gcp????j??G???^"S]???j:??kkTfH?t??????j?w??(42z? +?l???????\G?7EM??{< +??I??N??3?'[{ ????!=9?Df< )?/????)L??d$??????_? ??9L +??L?u???7?H?a,?L???????g?QH?3??????=J?^?8%?jL`3???S}????q'???^?g?,G????e@?'rAA$?@?w???D;??7:???)5????%?v.??+>?-X????1J???Y????^????z3R5G???U?&???e;? ??P??L?"?)???l?j#?? ?t????????M??1`a?W?=?????gO5?hVS\??z?/???? ?N?????1#n? +N?W?;??S?2 4???????a ??i?*F????????yI??????kk?P???d???????x??z}??X??C?t)???&??KG?m?0???7???[(*.@?~z??9)c?N?!??L??!?????7o? /6J?7?tM?A? ?JN?m???[[?n????x?>bj??z??W??]3?,?8?I??4>??a??? O????.~T?gG??v? 0l?? +?,c?5qr? ?1??????i?b???J??M?{?w???vG?Lo|S???~v??8?3??-?~?Gd???????M???????N??@?x?Z?l?L]??????S-uZy&?a????Fp?X?pVS_??[S???T?????T?????????lA?d? +A}??s+j? jB}?m???*Ij[L+J?>b?,m?l??GHc????9? +"???????x_? \?h?G????&?{?*?%zC?G?6????A??&??HnF?a??|?Y?:+y???o-????C?M???(i3Zr>?V???tg?*?/??Z#?[?XNx?#Uv?????)?Z?? ???$???/??i?5#t?+?[??'Q????G?[I?E??z??kp?|?oM\^?y<2[?}??|$? ??I??c??+??0-W??P? ?8~m'kt-n?? `?? +O????E?d??????????????u??%l???????5D1????g?&U|a~?P?ure!`_?P?V? +"?;???????f????????'????? ?!,????X?^l\I??????$??????????@A2_3+???D??L@?d??~?H?"?]f@? +u?H??????s??????C????6/? zf?????s?k??44?sVL?b5????? ???? ?a????#?0L?.a?_jF???3?? +^ +m6v!j??@u???????t?Lo??5???K??,?#??? +???z?Y????>??7? ?^?j??? y?Td>Z?5 ?8h?~???O????i?tT?z?3z+???^u??(3 +?????[9"??? +lrV???????<??[?????_?h???((?K7Z-m%?X?_?N~???"jya??Z???8???????? :?? ????`@^??r?-?6)|z??>??NZT??+??;A???F??N?vu??VLg? \p????@$??[??3G!-??f???(!>????e ??#?Oy??|??rh?^QT????Z?E?Ds??j?t?hx???????????gc????NUz?d???{Q?5?e?D?u?<_8s???6????fZB,v???R b??/ ?v?%??? ??0?}?c?C?v??s???1PZ?????R?s~???FY"?S?]???r at SRRT????o?,(?|v???W_???G"U???f?B??? ?X^ ?0????8]????F4GW??V?M?1??uG.???v??qE??6?f|??2S?7?? ?; ???GM?4???I?D?=? ?5 ?~?_??r?~?(??e??]q?}'m?F?jm?B?'?? +??-?????_?Cda?Zl????d?? 6|?LU?m"?E?Y=??W ??0w8F?m?hM^?{I???=???b?08???? ?'?;?z??W9??vP????cY????Sh???zjLz??W????n*A??W.?? +???Ov?,5M?jdGiU??b???F?'7?{>??"???.b*E}2??=?????'y MA??d? ?t?=?z?E??d^?+ ?? ???P?g????????)?xl???7q6x-?H?s???szy?& I$??9????%????????W>??H???N?}???? ????+Q2???????,?Mi?z0?Y?4??;??;d???]??uH}?????G?'???" ????yt*!????x???Iw??q&??WZ{????I????HA?>?V?~8H?s?!^((+7s?????????r]??^??q?3?VJt????l??????? +ho????80???Gm?~(?X?&+??r?Oh???<??.1??????????`0iIi?uSh????F??????J??R???????8??M?,g??r??????????)?B???Tm?>E,}?Ex?&?Hq??`???j9?%?-m!u??E?W?? + c?? +>?Z?d??D????g??pn7L8??e)????????n??? ?c???N~!p?zN?v??S?(?l??W??? n??p?=(??w#??????-4P?j??? DT?D???????H?S?????{?)DfP#K???,z_^???Z??@?T???a?K?/??'???????????@???9F>=Q??????W???4????9?sq(?t?P??~?S? +?? +?Db]?+3?"?hL???"?-c>BJ^^GK?????????5?7?S&?w??N?#M??????6?Q?9????@????? +??$)?nt???w?C???}?fU??u;??q ?l???n?P~?????s?w_4??W??= +?=?p??0p???*:61??=KNR?Y@???`Kq?_??;Wi_i??r?`?4]n?C??/????ju???????I? ?D????#>C?b??v9?z?sX_1??T??i?r?????z? +t?Q????e?dc?+.pKb?????Fm!????l??}???!??? M9?????U{??7?%???{??3`??????&?W??u?Kf$??Y?'N????7?x?????s&?~?*r??T??9 +??????Qs??{61??????????zc>??A?]C?Z??]???p?|>? +???$L?yo?6?(?:L????5?X.40vw?1???v?? +Gj?>T?(?*'b+?T?MJ??$Jv? S?79Kr?????kb? +l??/ +?d??"???A?????????\C?????E?^w?c*8?qp(?H?C?bt????~t??????(???Q???oc?j?p?y???E?@F +v?4?????U??????'?1~??????1p5??J??????mPR??}?S?\?_?????[}LU?%?[[]???fd&9?#?g??*?5?$?+#M?&x???Iz????? R??/??? ???IX??g?~???D?r?e????????X?=G???np???Ki?????w??? ?> !???P?????h?$?2??Dj>w?K??????????5?_?}?tI?((?uNH;`4?????|???????OOP?Z??%?0l??????*?OMSLRJ?e0?h?V?^???X??\??0????`??<{?Y???9F???,?^4?s???p#?????x8?3:f?V?1+? ??????^??????n3R????)9? g? +=?1 [??:???0??xIE??H?l???????????z7? ?M,4?0o??????1d??Rp%?F~??????A????|??k?d????W??XX?*x^?BXa?)??XZ???0??43Z'9=}?Vb????H?????[S??ZV??G?y?zC????X??V?%??02Y??-H??8? 7Ydf?_~?\??aS*?E?L??xk?%??v6 +?j?-j?=????s!?????,?^7ea????????8!e?HP?3??hf????????"?fry???m?? +I"???S??{pakx?? "?R?wv8??^??07???t?%?Et?O???U?(?x?K?~]???? E?m????f3?W????.')?T??E?????Q1??$/<" Fk??\????B??$=Kf?????f?U???? +???bL/?V??>??~?+w???Y?? S?]??lK? +?v ??M??_?`??{~,J????j?? %*J???j????`?c?+v??h??~?8b=P??? +????-??{u?(??????m.s??y??8??????IY?????????@<[ ]{??"?X}??.?:??Kb^9B?????CU*lGs??i}?r?D??\D?%?D???s???? ?a?9?jC?????|?E????1?_??A?????G?qz1???"??9u?{??????`f1???z??F??<.????????yl?????rK.y;?:??U1?"?j?????_?[&??#??7??L?4??Uf? ??p?:?? YV??.??Ss??R?# "??i???????2h?^? ?YZ?x??g3??l 9L/??N?h???????eij?????Ev?v??????9?G???V?o?o+:=??W.?u??" ???6?????? +???????????????????????l?endstream +endobj +148 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 122 +/Widths 613 0 R +/BaseFont /EUPTSE+NimbusRomNo9L-Medi +/FontDescriptor 146 0 R +>> endobj +146 0 obj << +/Ascent 690 +/CapHeight 690 +/Descent -209 +/FontName /EUPTSE+NimbusRomNo9L-Medi +/ItalicAngle 0 +/StemV 140 +/XHeight 461 +/FontBBox [-168 -341 1000 960] +/Flags 4 +/CharSet (/fi/parenleft/parenright/comma/hyphen/period/slash/one/two/three/four/five/six/seven/nine/colon/equal/A/B/C/D/E/F/G/I/J/L/M/N/O/P/S/T/U/X/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/r/s/t/u/v/w/x/y/z) +/FontFile 147 0 R +>> endobj +613 0 obj +[556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 333 0 0 250 333 250 278 0 500 500 500 500 500 500 500 0 500 333 0 0 570 0 0 0 722 667 722 722 667 611 778 0 389 500 0 667 944 722 778 611 0 0 556 667 722 0 0 722 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 556 278 333 556 278 833 556 500 556 0 444 389 333 556 500 722 500 500 444 ] +endobj +138 0 obj << +/Length1 1608 +/Length2 10437 +/Length3 532 +/Length 11293 +/Filter /FlateDecode +>> +stream +x??ueT]??-????9??Kp? 8?A????!?Kpw ?????w?????u??7?c??WU?Y?j?Z??RM?U??( ;?r?qT at v?????`%VI??9????BK+?4uA???N@!?.? +4pq8QhR{wG????A[C????????B?????? +??^?\??{; ?????Q8Y [ @JU?????ANE Mmj??mAf%? 2, ??,f?9????l?XP?)j4?n????r????v (???,M?N?=p?@`3[g????- ?w??F???^?? P'??#?? ??UMZ?_?O?6?=? C????FK?7?xR??l2??/63Z?L'?z???&c??????D????? +?????/F_??wgS7???d????????T?K?cTE=?5Z??S???-???=^NX8i????B???????K??????????~?#????Y?t??h??x5BSA?f?x 3??q???3?P3?U??h@??????F"?=???B???n??0py?????"??d?V??E?? +?0?2???x>f???C?c\a\????g????6??~??T3???q??2U1?r<??P?D? uHzh????$??E?|B????????? H?????#*?b?U.'r?x?%?58???.#~ ??????Dtd!;7???S?;???L?ra?_n?a???????D??.4?[Q7????u7Jg5?K????k!??|l.??K?$4?`???o?COk?Q/? +???????9????A?????W????M?%??u??}s?V{]?=?e????Lb?+~??h??DS?/?)\mJ)@m???Z5??v??q?[Fc?\Y??7?(T????2???h???sQ=???ly]?R,}/??S????z??V +???;]{Ky??`/?$nR?:~N???bu#?????dm???? ??L?E????E?m?%???A??A$?? +??y2??]??vS?k?SC ?????q]???^??#????&!R???Q>1???^?{?jE???J\?cB=D?E??U?m?H}???????So??Im????nu">?g+X???Dy??a?M?????*??;3?_.?????8?)????y???0?s-??nm???{$????j8? ???Y6???~?????????\?????Y????A?D???F?ztA??e ?hM??R?J???:v 7 +1?u?]q???xW??Ej???L??l3?mZ?P??M?V?|???}q{>V????s8?(?{=?????*]2s??????7??+@?$???Gz??r?1???7!??ES?? +????<3 +???yd>E{?;??0?B???Y?4????#?8???` ?O????o?uS?t=r?"?OCi?i??r??I;&U? ??4?b[M?z??'?+?L???V ?X9]/?ID?E???????????????C??l?2?A??z?x?E????uf??n"??b~?S2 ?iylk3?{O????N??6u??ru`??H> ????????t? +69?jA61???{M?*??? ?|???]Z??????yS ??1??`{??4?77?[?)??Zn???F'?K??z3-?p?nL??m???????,E??????N9?n-??c?!?6`aU??~???Ye?Y}???"ge??q?????~( +?7??A?'???[C??\:?????:D??????^Ue?M??\A??rui?~Mir??O?????Y=???M??>??6?JL? ?3?.]?{?b???h??L/?T??P??f???x?,?&????:????@?@???2?3>???bo?!s??\cF?)^??n??@$r??4????????????m??>+?z?*????CoI?*?????U;Y?k? +?+????>?R??I????%?????F? +?h ;B?Dy??/?Q?????????(?]????r%???{?Vnz?????4???n?????????????Z `????tM?????s?:???cx??U|;?v??v#?7+?{??e](??????C?(??vrphW??g????E????QqN?fv?H???7x?6?C%$??$\$?;bAbM?_ z??:????Wt? +??:.b?R???qmG@???,?s????~a???}Zm?!???*?????s??[j|?X.?YN?R? ?O?Z-??dyj??|??D?b??#??k??\????c$??"?Sl?m??Q=?"9?D6sL??????????V9P??K_|?? +}????\?k????F?????s??e?M;?]?3?3H???j??~Q???J??1?t?x??h??~?VPG _?.??????`???????W?@???x?LZu?]?????6? +1??*??Qt???Il?dJl?? ~?6]???1o???7?"?`DM?`?v?:Q???b.0wG???qH?????&?t???7?k?mX].7?????D? ?Q???:2?6??TX??{*VIT/*<^3?j??\{f?csIt0??5O??Q7*P??f??!t?k??=c???VY*????e?&.t+(??Z?M?8?j[??L?????>??#?TNPaIY?#N!??8???A??0??v??}??????8?????5?%?y!??Q[p?i????X|i +u{??z??v?T??!9?E?E,.?E???\??w?Z????ZE??5/?I???i6;?;?S???????D?h? +k?????? ?zM??(?#?G +?????nOL?6? +y?^$?^???>g^??BX????o2???E???x'A|????5l???.?????*????P?$SQ]???E?b].??? uf?2 +?b?????????zs cp??M?L?V?7K??? +e?fcL ?z???u?N?(?7T:J??-\???j?????????~A~;?7?y_?????W??(#]??d3??z~ ???a?ID??%??dQR|cL?J/g?uGtS? ???8?T?4<,? ?n??[:??e?7?+??[?=??k??>.???????_?[??l???o?p???Ik???f???Y??w +?s+.o???ve6{??r?/??z' ??e?Z%y??V?@? ??????d????U???? ? K?=??!?? j??39W?T?b??m??????1?A?????n?&x?2m???&&??|?Q0????/??%??9#r??Pu?a??m&x)??.?Z?Zw???Jwv??]4????????J??W??|?xS>Y?H"??@?8n?#?.7???AH?rW????h`??????p???,?????[x.?'y??????z?d?????k?G?7?R.?O?Y??? +?^?'?????f$??*??F?????RB:-??H?I?w?!?????~??5??????#?P???0.??5J&??;?G???'d?d??;???????:??(??%??d??-t?;???5??d4?yT?)&???gd??O=y????@WM?????????????^p???l??????4S??6tBd???I??,C +U(?VU?? +??@?%U,??S??.E?aV9!gXtm????{9???????Y_@k?0??5UE?X^??a??b?}m#????F?K?5???????L"5r??|???#??H?[C? ????z%9Uf??GW?9?*i???~??%!??hI????I?????D7?t|????Z;F??ol?????;???u +???*???k??Zg"????5?vB??c. +?W^ QH???a>u?K?h?~?VxQi?`C +O (5?2?k???????????????gU?]?????R???s??u?\W6K?}e-?%????? ??L??G??h???5?????=????????1??05?X??w???r??'?DF??ygm??S??|?#??vhB@???? 6??,?Q_???gg?p??h?:M?<_?????F???[??? ??6?S?K=?sH?Me+??]??Fg?????(?@w? ??????)$??x? 5???"???c\??U??(?7????G?!??????}???????!??^*??E????? +????wX?e?????s??P????? +X??&?7?????Z?}?t2 f>??9hV?Y ???r??.*????????????v?B???n??zg\?^??P?(|J>??C"Qv??Z??L????'B??????.4? +O(?#??E???"y????B?^|i????O? +Z????|ppx????-??n?[?;w??.?Q??????7???????Oozd?n????6/??? ?????d|?`?DU?i??5???q?CJO\.b zY???*??1U??,?[GO???M1??????^9???/8????-'yb??x ??a?????MFnQ???G?8?L?w?z +t??????A??????????W???MH? ?Xc????????N??L??Q1??Ads?J????I?Gf/??+??B? ??D???9?M JG?:`???%Q??0????????&?g??]?q?H[XL??????X??Q 16Xxzc??kg?G8?????J???h??[O.?*???.^y??????c7? +_l?|?/V??):?k5????+?????f/`* +p?6?O?%??-i%???????/???@"???????????s?u08??l?e??'??Rb? ?M?Z(?????=???1V +???u???X?Yo?m?????????1?C??-???Q?l2?? +???b?m$F??B +???~#??S??4?????W?Wf ?????}????u*?@?e1??5??\w???.?|HgBUB8??!4%??/??HVa=Y&D?G-???`w???R?t?4We???? ?_EOQ#DQ?g?r?|H}?o?3k?t?'??? ?jSB??'?I?[??E?U?Y?x?KvF??}???????2"?s??@H)?`???^D?A??u?=?~t?.???9Fr????=+??n[??,?R???7??%7???m????*<???4{?.m?}??.?@?/????y +?T|? +???? :? ?????%wR?_??!??0??????Md? +??O?????jv6??G2?vn????E?@e?????m?a?,??xL?K?%EaC???=???;(??????l?j$????k??]? )????d???U??6?@T?Iz0?,~?MRn??1%?????ia??mg?Bd??DEC???-???2???Q??Rq'7??)8?:???^?b???IZ??????F??????T +J??]?rQ???@*B\SZ?L?(?b?FRAS{L???????+?^????0??ITwe?? ?:[??$a+?w??S?8?"?A?G?S?(]???5???? ???F??????z???62??8?l?)????}??hx?m?0?A1?O????$??w']?&??g"m???????? +n???h?L??? ??B?H9???o??G??(??F?{????4?`?4> L ?\??H??&?MG??CNX???|??A ???mXM?fN?Dy???8?I +1E?O?]????i????3???t?fR,d?G?????b?????????a???????7?.>9|?:?y +??S??@;?~=?0?|??S?=?$???x???u3???????????J!.?\ ??=????b?f?D?K??0r???A?]!8??fl???i??&C???x C/z]?????S?>?p=????f?!>-;CQ*????b_P?:?KX?@<2???s! ???2?JT??7??????V??t??&???05Fr??O?????2G??*?q +?hZ"?FO??R??A}???W?8??????Q]D +????C? ?*?SH????? H???M?????Nl?1'?`p??$T????;N?$W,?????a??? f??H??????I??e&km???qZe?#??D??$k???6?\?z?7?BtW?Mp??{~qOw?;?????Q?_FJT?5J?"?????l?4????????`f 4ut???:????^??endstream +endobj +139 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 121 +/Widths 614 0 R +/BaseFont /DCGXEA+NimbusSanL-Bold +/FontDescriptor 137 0 R +>> endobj +137 0 obj << +/Ascent 722 +/CapHeight 722 +/Descent -217 +/FontName /DCGXEA+NimbusSanL-Bold +/ItalicAngle 0 +/StemV 141 +/XHeight 532 +/FontBBox [-173 -307 1003 949] +/Flags 4 +/CharSet (/fi/comma/period/one/two/three/four/five/six/seven/eight/colon/question/A/B/C/D/E/F/G/I/L/M/O/P/R/S/U/W/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 138 0 R +>> endobj +614 0 obj +[611 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 278 0 0 556 556 556 556 556 556 556 556 0 333 0 0 0 0 611 0 722 722 722 722 667 611 778 0 278 0 0 611 833 0 778 667 0 722 667 0 722 0 944 0 0 0 0 0 0 0 0 0 556 611 556 611 556 333 611 611 278 278 556 278 889 611 611 611 611 389 556 333 611 556 778 556 556 ] +endobj +134 0 obj << +/Length1 1166 +/Length2 6834 +/Length3 544 +/Length 7647 +/Filter /FlateDecode +>> +stream +x??ye\Tk?.?1(?1H7Cw7H#? ?C? 0t?? ? ??!?HHH#??R??????????{>?o?w???????u??}=???X?? y??PU? ????\m== ?pm^??'?.(?ge5??\???J?P0 +??+?Qw???'??(( H +?K????B%"?%?z?0W?P??????w?2?? +?? =?H?????t?@=$??w??gU???spD9? +L8??y???$$$???!@e??d?[xA]????(??p??]?v?s???*v0??q??(R??i??????AP@[???1??~????F??|?| ????_+???C?]|?N??B??*?F:j????_Y???;J^??0?WP\??)w?"B?d????GT ??>?????#??s??_#yA?=?? ????????A?`(??o?X +?????????7????5T=]\?P??O9?wzx???q??G:????_^?g? ?O??x4P`D???/?`?0?? q??.?l??w?Cx?~?@^????# ? ?zx???n???*p?w??\ v??W?7 ?tw?????{???=??A(? +??8??H=u?{?vQ?@???=.?+j|v??(??ro??G????V???xj?????l??#?{???*?b????|8$?$??14????u$G????4I??????|??????Xe??H #?????w?t?i? +?tw?8%(.?t?]??%?? u( 8?E?hv6N?d?4'h?vNZ?Nb3;??H(?!R +UwdKkV*&?1?)x?X?jY3?,??B.??/?5?;~~??c?s1???o? ??H??6??????C.:? ? +?????48T????1?jz? ?X?d?g????q +N???O?n$?tn???D!i?w? ??]?R????%???qA?? ?.?Xp?-9t?Z?(??L?@?K?z=.?K?j???H?????E??Q????????????? +[?6???s?EB}?? ????/???v???v?, ?+Z ?ax???6Y?y???e?????{ZP[T?????VT???v&n???x?????}??S?TV?>????^?????GP???uRR?;?d?'????[?6???y|?&%?h??????????????? IO????$????)1W???H?|?:?z????m?????=1?/???x??????}PR<(F'? l#??5???????x?Gy;?D??kaI?R?gF9K????sJ!?? +?F??}YeK???C/F???Ld????:??O???????&??j?'??g? ?=?M??D?W`V?g?{??z$??????[??v?????a???nu +????|3?Sj??}???????rr???3?|???L??L????? o|?|m&?O?? +?!D~??3??-??&Lw pF?E????? +f?3???T4.p5????J2???ff??/?l??Nu??????8K?$??? +????/+m>?????*?'?????2]6 ??u??O??AL? +!*??wT,?????~c??.?`Tv?[?v*6#f9 at Y?U??jK? ?????N????kO]e/f???~????? ?5$?l?_??????????Mz?D??H]??X0?'???P????:r??\%?KQ|???????9?kd??j??????I???b9??3?C????J}?]??????M?????. ?4?w??%?????E?}?"*?~E???51?&??3[vYX?? 0??$:z N?~=E???FoLe? k????????b445??????iX???W?? +g?x?????? +????'?V?? +??[????????e???????9?%?Rw +!k?=j???:?/Z????;??V??ik???s?(? ?eH???$l?u?????m????"cD ?? g?bN?? ??U????????q* ??O?$??7Wh$???w?I?\O?????0J;og??f?NLH74? ???&???????????;???V?V?!?'G?r??-L??&?}???C?==KYVp$?a?? +h?=????1????P???4?}d4??)k??h?z?LE???G???&?.u6? +;&H????? c????z`.cEc?z?H?9i???I+?.?????E^W?? ???|?? +?{?&?3U??,7???> +p??&d??PH?????bkOL:?T{??.???;?????+}?_?Mg????W?U???';???? ?N??x????p-+?C?+1lY??5????XAYo??E?L?sn????91+z"~f;?Fk%F?u?27?r76cNS+~ ,fqaB?N????z?????)???????oJ%??vWOOI??e???2??(????????g6|?cy?"W??j$q?_??????b=r?O????jtB??3{D+S?_??Z?1u??g?e???0???y??"m??????T????-??\  Io?[?a??0???a??R??t?z|3u?V Q?????r????O?n) +????qrz?}]P?T?4?)+?I??( +! +k#?:?eO/c+?(???+??B?Tq??L?I??UbD????LxC?XEV???Ie+TMI????g??P???J? +2#?z????:??D??v???? ?S8???#??Ps????d9??O?g?p???$M???y/??RI???v1????*?? +??????B?G??+????l????5?\??????Y????????2?i???oS??)?a-????&5? ???T)??6{??6f??=MMZ?H?Q[NZ=-?KD??V?'x??uK????????Unh?????? ?1'~?"?hY???#???~?sq???#?0?+?L"????Mu'?/\??=?A?$??Ibk????d??D??~?????{?jY=?"\,??)2b???l ^6?i +1??%?????|pj$;?Aeo??b V? ???t,t8???~~?`?': B?J?& +????_w8?:???1???????_l/%??do\??Y?5?5??H-???Q#?y)??k*V?h???~?[%???*??*r:Y????U?Xz????&???????I?66{?2~r?_9??SHr??????a?b??????-{?7R??|? Xs??'??z??Q??3? n???#???WhV?9?bW?-?g?6?????r??x??4?1E?p???jb???|w???? ??.|???l?%?R?G?????=???_%Yo|??6po??9D[??????????8s??n?\?ba?????H?;`0i? +K?xWTK?mx?tO?>w?kP?Y?P?v^G???O???ex?Sm~??M? ?tA??)???Wh?u???%??K'??C?r? -yH???`????yj?r???FfO?_???????ht?=?8?5???.?b?-?B???au???7?$E?????'?[Q5???~+??/!???z#;???~.??D???9m&Ml??|R????o??iM'?rR?#?S?/?_??`yJ??CF????l????}hhk_???????c??GG??????V??W? +??6?!s???B +?5GJ."%/? +?s?cBc?D"?=??p???NDP?OZ?9j??mj??l?????I0c???????E?{? ??Q+?EDB%$??f_P??P&>????? +S???\?k?M???????H???H?g? v?,:?_?? s?? +??)????x[??k?U?????z??~mV ?1?k?Q?-e????P????$?#?Ga????'????#s???{??G/????x +?6????;r???,O?? T%h?,b7????D|?r?????BTe?z ???E|??d?B?ueZ??1??N%S????g??? ?}"(?C9r???a?:?k?D0n@?{H???????n]O??????i?? +o??e?????> endobj +133 0 obj << +/Ascent 712 +/CapHeight 712 +/Descent -213 +/FontName /REDTNG+NimbusSanL-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 523 +/FontBBox [-174 -285 1001 953] +/Flags 4 +/CharSet (/quoteright/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/A/C/D/E/F/H/I/L/M/N/O/P/S/T/W/underscore/a/c/d/e/f/h/i/l/m/n/o/r/s/t/u/v/w/x/y) +/FontFile 134 0 R +>> endobj +615 0 obj +[222 0 0 0 0 0 0 278 278 556 556 556 556 556 556 556 556 556 556 0 0 0 0 0 0 0 667 0 722 722 667 611 0 722 278 0 0 556 833 722 778 667 0 0 667 611 0 0 944 0 0 0 0 0 0 0 556 0 556 0 500 556 556 278 0 556 222 0 0 222 833 556 556 0 0 333 500 278 556 500 722 500 500 ] +endobj +131 0 obj << +/Length1 1630 +/Length2 19463 +/Length3 532 +/Length 20368 +/Filter /FlateDecode +>> +stream +x???spfo?&?v??I?V???'?m?;f??m[??c???????9S???g??????p-\?^??6?? +????1P???????@?????Y??V??[?Ah? +?+g???q?X????y@S?(???`???????;x:Y?[????5h????S?? ???h?z:[??(???m?l?v.!??U?@??`fi?((jI?K?%??@;??? +@????? ki?s????6?>L??L-?)???/??3???4????0:???8?l-????,??NFv.{?b??3?q5?'??r3?%??d??????/?????????? ?oTEQ???ba??Olg??j???_KS{?J???/?_?????3????O,c ????????o??`N??J???????3?8???Lm???a?b???????To??`??/o?Y??,]??6f?p?,c????mni????H??????[n????tn@?5?????????????'?h?$o??7$????e??>??(?o!?????7r?+G??%????Z???F?????{??.#;??=???hl???>F??6??'??j??w??0)??m?3?K?7?o?Z:?[zM-]L,fF6{?/???)???????????????ZX?X??C??U@;??Z?_??????????,??f???P?? ??z:???????7???`???x30spX?????? q????oB? ????rF.N???uc?W?????I?????????3:*.Fv??? +?Q??:9?%?_ ?o??????=?&p+??&?!Vi?.??9???:??????% +?????=?i????5????P? m??3??)???*S|??,2???HEr?\?0?*???`??????[;??n{?:D?JlH????e?r????e[?y?t?%C LA?o?dI?A???v??y ????????k?b??|b at Q?#3\S??Y????-\???JH???+b??"????I?h?`[_?? #?vS)l?? ?;???x&q????l\???{Q??Dh??C?&?s????????????|?Y??|??!I4????=*???g +?w????_R?K( +???q-???m~?Q??Q?E J?????c?r??sr"-~?s/CK#??j?%??l???MK????sRs??u?U?3?{Z$??????E????/Ky_^YO?"???7 ?X?!?%??#j?!??????e~?!:F?s???@!?Q ~?%?d??,?7Dm?n?????J?(:ZX?y??jOAHQ???T +??C??^?Q??tY??tp??H?z[?|vu?;?WW????k??+A???+#("fGr???#b??"????????V8?$??????7h?8?oj?P8E`??????HYzW0D +l# +????BC?:KR7?B??[??????????8???4=e?q?y4?? N??[5?d?_???g??????????u??M???O~8?=????)?????!7PU?]w??q+??(??%y?I??????LZ/???Y?p +??R?????zZ]` +??p{?K?)??????_?X?NfJ(?K??{7%UO(V?lp?YD>?????}?SS"P? z?DV?JC?i8'?l??????a??g?9*??????IhJ???|?????7??{ no??I +???6???d_????^ )???W???+???????????s9\???Z)E???D??2?UY????h?p?\???V?}^ ?Pm??g?-} +?6N???UEH^e?? ??g ?J??t?#?3=?M???2F6????"?????????O??>?????sp?K=?x????Ow?{??????o?B??????)R-4?|i?z_?-ld??p}?>??L?v?C??T??W[????U??"9?? +?nT??e%?C???5??~?4 +?g?????_??????;1&k??????????]????A?#} +Z5 + +M8??????????EN?S??>???? hV??I???H?????'?<1?Fv?J???D?F?M??4?+d?>?2??Oq?r?@?? ??,$ye???k????w???? +????P9?0,??L0?\???j9d?)? +j???-?????+?,d?qL$???KA???H??p?/ws?3?????~=/^G?OW?~???3?[????w?-/??????*??????T?|???3h??F???4???????:5?????? .????? +w??!?y??u*?q +??H??????3?R&???????vk^(?3+V???1?????Q?RF?f?*?I m?k??5????%??,????e{?A^??8G??1???b?$? ??C?Li?????????l?-??J??T?T?{???=??C?_??7{???Xe???$??M *?[N?L?n.5?S!?1??kB:?.=6?$?!????sq?L)? ??o??a????9???/??E?6{``?\? ?Qw?Npx??]?=?EZk?sS?4Oc ?q???ra?m?n??D?q?U?? +O???*??q??D?t 'U?C?RC?S+F:s??*A?B[2?'K?q6~??Kn????N`'??<?=???)heT?? +[???TGH???????,???%??9???X??`??[????Naf????l?a*f????rQ?D??.$?a\W`9??x?9??,??hk?Y??vN:Or?aW??? +?.??Z? +??t. +/?K???y^9???q?v8p?*?^?Cw???S??n?>?#f???tb????"f??????=$?U?????*??????po???z???????}l@?????ys???4???????t?;?????R??~??e4????v???h?w???V?????????|h?:??5???_?n,D?^@]??T"?G`d?n?z?6??O?]`!N8C?"y?P?s??????*???c??N???*~??#?V +5>??i?3??wI?????,8??D?????}???VF;{?]?5??g?x#??ca[?S????0z?{????$&"z3|B*??J)?I?#P??g?|?Bw??yv.??1?,?? +K?n?>t??q?!?=?\QP$A??s*E????w?|xQ??"?T}? ???.?? ??X?^???~???????a?????{?????*]???????7??>?????5??B#?"?M????|y? +H??6?^Be?o}?u??$??????,?"_????5??&?????????t????F???gY?)??u??L?"]~? ??#?>v^??r?obJ??????f???}??s4??2?q???&t8?D??4n?????'J].ifH_"?S?)????f??????y????W??x??P?&?Ih.?Jpl??#?????Y??%?#?5o??e?~??&Pz4e?????B????$????????.b???n +Y +??g[???Cd?I a????9???ZF????>`n???=D?5?? F???7??? L?b??i?? ?O3???N?`?#f\??_L??Rt??????[D???z????WzD?2???????j?????U??Sq??????D???\%????? ??????b +?jR?{???8????g@?Y???-wd??????4??#r?A,??7~???Ni????h???? ?k?+??3??5^????~?6????At?J?@?.EA?m;????4???&?k???'<?? '?b?X????/g1?bW??O?p8'?R?/??J!!?G?-1E??RY??-??????j?T???9???????}????v'J??a? J?-2K?xl8???_o[ ??k?M??ph}?y#??N??????6??NF?My????B??????? ????H??S????O?L?$?S7 + e?y?????g?~?8???b??_?XC??tmp=?{?#?3jXT?6??e????\"?x?E?0????3ZU]??:^?\dR??9 ? ?s???Y??????\??R?L>? +w?,???r???????a??BvJ??????g???f?? ????q>? ?M??5H?|????Z?????"?O"????????R[??deh,???u??*E????A.??\!v?d??Q.??:??b;?????Y?b?Y+?R????E~??S??6?o4???X?X?-Dr ????4T???JG?=?R?????-??N.+??f?~M?aw??d???6???&iG)???p?.??B@?Wg?e}?9??k?E=S??d????O?? +?????L??H?a?????z???? d??mo????\#?;?5?P?6?/?????r?[f??!"W?N???n???| +$??? +J??0???JT?,lNeF???a?A?????$???X?7?t??8 ?U^??a??8?z[W?5;??IJz??????????Hys??%???B?h?Q4?0?PjH? 9E?v?a?m???????nUT??e?:q??A? ??$?????????b?4?*?????E??y??%;?B3?!?l ~???T?P?1d? ?Iz?k8j???:??????$?E?E)c(_???Ew-??????4???KM'???y??3?n?8??XWa?y;G?Y*G?#??/?lv?????8x???+pY?kM?%?????L???\|?Z??x3??r ??8A[??=(?o????'5A?*?,????*(??0@?f?A??o?5#?TPO??g??U?2??6=??%????}???@???a+#U.??y?c???#/?pG???8??`1???<4?eSh?P-?B+?uz??-??? J????t9?;????0?????8c??auy?%??hA???C;%???>???J??m??3???uHJ5&???????????3wQ6I???E??M??????K?? *UK???i?7`P?????@e??E@'?w??-?"?6k'??[??U?????}P???.??]&??????~g????<"???S???X?AL??`?b79T???????R??U?/e1???????Jb?e????????F1g???????=f? ?X???IV?????h?????D?Pm??@J6????d4 at B;??3????@P???A?g??}O?k??????/s#??5I??`4?????? u>?^*????????mg??)$\?i6mr? +?t??X9?a??]u?=D??8?[??[f??ehZeK???X?pd????????\?????=?2??~rq?!???pQ??>?Hl+??`?l&/z 8E?0?1?BA?????M? ???mES?w? ?????7??U??AF?p???B?>vu#???E?17?p:??w???%_???U +???d?[@??FG?T?Q???s.??Y(J(????T?G??P?mR???M?\>Tc???1Qck???%l;?Np????i?G?u?o???2???;?????ga,??????-k???%e??`?>gO!???.?7????Q??F?D???c_~???tTM???3\???~:??OE?O?e?c?8?ZJY +'??m??4W???{?U?g?C\?~??????h?LC???n"Wt?????;??VQK?I@?4 ?_a +?Y:*B?j?????m??{?S??D?C??C-???[??I? +??4MA?\2?0??)'@8?S, ??>?>?j ?T9?????9o???iud9??$v?fG??L?'?>b?)n-????????g???c?? H? '??N1 ??? +?%e;? +8*?_?v,Z??pv????`??G?"???F1{U?[?%L?^ByT?g$?4%(??U??G?kS?&}?QIs??g?v?k? +?:&4 +M???cu?Y??_:q?_???b??T?Ej????*?z?A?`???5"|??sy??;?????dn?mG???wFW-n?vh?]?aw?_?? +??e +G???d?@??L8??3#?? +(??q"W?7?}??m?j??9B??E\f(D??G????(???UvmD-?S?P????C?{Vc$?"?L?N?????????P??vL??? ?o?????u?7,MM???????S](@??J???????;5~mV??[p?X T2 ?????bl???g????\F??????B???v??eF&_h}?1???h??j6????G? +??yy??),5????k??hIo??8?'?m?????RRF?q|?Jul?=~ +?????0wn>wP{-W?s{????? +??u)??*-wU???s?d?n???`??X{7S?? +p;>(W?,w?? ??x?{?-?Z ?,?)9=?p???+?n?3y???P????I?<?????4???;7???%4??d?cj??^P: JQ"?b?F?&???? +?????/??'????o??_c?WAY???Z??:???ww?*8 <5?XA???3??@N?s??.L?b?@??w?KP?*???????,????l??C?Jw? ??#a?T?|U?.4F????Mp?w???????s?????(?? ?o?;?? .*WU?nO??5 ;! ??m?7A???'??I?H??8x?* ?LH??ok_?@S/??X???$?a?VZS?yzK"!??_H??eX???|!?1?-?S?Q+P?L??RZT?(_^?k~?9??????Ig??????b???Y?'&???????dqk???W?\???5?f?9;y1?b??r F0? V?n?D?\[?? ? +\?a_K3???;*?v?UR?c??o??1{'??X3s??1]e?? w?H????6l?T??G`0\?SMs?`-???o???Y?????k??>}????{??.~8%.??'2??+F??????T? +?A??X??? ??i?!9@??s????0"??S?I????|?O?Eq????????}????????o@]?T???_+yh?G?? ?????7?J?P??A???7X?Us?($<*?N0j?e???u7?~?????C??Fh?J +???'??F(oW?St??,???????????p?:ck?L)??????y:,Do%?mr??`?;???????C??h!??W + +f??G4 +"?|8?,_R?-???9?w?#??a??sX???kCu\,????????[?h? \~?v?VF??qG??&??$e?????R??6?X???|X=??&??? ??N???bibl ??rb?y????????H?>?_?^|?c????`?Gk???)eW?th??kk???s^Zn???????-????]?[?8??]????:???zZ}??!V+??a????%?^8QB????A?j???sW/?K?????T???"4xN???* ????,5G?k? $???AV????????z??+?????????j$J????r?1???????Z8??*hoHV9&(??? +W?q?< ??|??????_?4?v{???NO,}??6??D~w??P? t??o?NZ?#?%Q?d)?? i? ?~?m5?!?>S???R? +??M??L?D$???k+???>??=???"?H?n6?c1??\?????,?/n???A???=?nG?O???o?!HU??2?L?}????M`??u?h??qJ??T????E???k?C[????*\?L?H???????$????+? 'Am?MW?z?L?8y??? ???N?0???????H?b???t?\?:I?T?GV ??????Z?].W?&i? ?O-?I)??? +a+?????=8FjKPosMT}U?n??}f3????,????5?#?}^A????w?-??4??Z???>8;?fj??g????V????c?????0?5? +?-????$u????B???X?%?7?P? +? /????C?~??b(?h+?? Dv?b?M????[???tC*??u????Wg8???.?O??F8?j?? ???vR*??q/z?b??i????g??)?Uh3m???b?V???`?>????q?'?[m???>?????M?BMzc?oRm???w?O????16'v?t??D??????i8[??#??Ua ???L??P?V w??P??^??\3??H?????????]%???????M?[????[ ????NLOB1?3#?????17??rL]??6??????6l.???h?k qi??d#?c??7i?%??????/@dX??M?C~?V?????L???]???'tbw?0??\?0?^w?q??jN??Cr2a???ejrPq??~?'??I?b}????? ?h????N??????V??*??F???3?3????QM??R?A??????-???|???|???3?5?p?????D Q??Nh?X?x2??N?7?tvj??)???????OU? ?%? ?????,???jd?d +dK??????u?X??????[??X??I????ay?](?????????n*?E?%.?g????@??H?EH`:?hg???Z.[X???[A??y?p?Z0?????8k?W??????8??sC?6?i?? Mp?:o?q#?????HI$?]^??G?Ysuq?LOp??j?? ??N??#?(?eL?S3??]-.3?8????e??b ???8?2? +[74??^=|???e??[???T?-7M?? f-?J???#Y2??28/UyN??;? ;?;?'???J?1??Jd????1%?,?M +V ? ???? ?O???! \?. +>/?Fn?r]?j?????d?}???? ??????VE?Qf?,??M?g??E??oy?g??????????V? +"i?k??^?N?????4U??}?Fy???7|????#=-??J?8? ??h$?O at tW|?O? ???4?]?&B?s?i>?:??g:+????>?y +?iR?????q??q??&???+?|"??a?{_.e+???O??u?n?-?2 -?W8?xb???(?????"??1??3?Vzx?:G)?m?jvE??A????m???6????????OT^>? +????/L??????8W?H7??uo?i@???'???Ug?????? ????D?????/???????????Yk????K???-hy?,G?1?2???????*R?o??:?p??Qxi???`? Jb +[????????????!6?G ??n??Y???V????a?????KIp@?? p?&.Q*7dnhts?SR??SG??(?}qS??? +6]R{??J@ K????]??P??=?\?L???L^?a?????? 9DS????~?w}????????Ob??????P(??En??T??Z?r@?z???j&W~???h?? ~?0?4?'xf?6~ud?#R????"???B#??&?&??????NF[??'&J$(??s??x????::?,?$t???????LLdba????????_;???8p?T??[?(?q??g??Br?,???8gd^?}?Jg??R??7QG?23????~?}_??x????HV7?p?2?LZ0?!q??E%????kY8?Th???2???>w????????????T?7???O??8????/3?f? +?}?"?5?>px?a???=.PB?R?ZVA?;?=.?????O??????U_?8??.d???d?4]4XrOC???g?Ls????04?Gn??["(????R?T??JE?g???0?E;&e|??Z??^[>}??*??c?????G?[??M??h??d??U???-?K??/{????8~k?3??? +??????~QS????] +{?k?{4"?S? #@???Zp=?{???p*?+??9?Wl&??H????w?*{z8?7#m` ??#?8a-??????i????8fL^C?|?,????@z?????,?>?Zs>>??$%?3?1T?k?5?$v?n???v?????q???A|?????$4 ?V? ??'3????L??{????1?s?U???Z2?0$?q?Sf??????qW???{8?zPg?|U?m?EZp???????TC]???Lz;???>??,,?9??W_?yHh%?L?${?N.?.5U?^Ss???I$??r1????^b?|???????D?=wA?}Z? ??=????9????????Wlmr??r????tt?Y?WJ?$??&?(???p????X^_i?j?5w??&?E?J???m_v*??ld+o3?GQ?_?????B?\?*??/???5???qt???o?\??d0>?8D?_P????M???H??R0z:?r!QQp?N?.??26xQ???=? d??g?+i2T?? +?A# ??g????V h?w,6??A ?!?GtOe?>??????????p? ????5???)#"X?I!???????gMQ?mH ???h ?yM]?BGN??????l?;?????S6?kI%???e?-V +?c??$F??w?tk +?h?,??-??U?%?^^G?z8 X(Yt???jV/k +?w??A???? +(t????8??b??^G)U?\??gj?#a?u????+??6+?{o??F4??I?A:V????:??????Fj7L???$???|?N????"'7?r?E??????????^S?Wc>??????j?i3??????f[????U#???????A? I?7?fut Ms ?M?}@???&7?C????lL?O?U!?E?????p ?? +????'??LJ???KK??o?I???\??#?Rf???g=????f?????| ?m8??q??T???'?>?m?????1>?p??p??????????q?{?cbi1??i????U?m??xCe5#??ox???Z????8?$^H?[7 -?????u??????7K,%bL?50V??????2??b? ?]?????1oY??????w??O??*b??z*w{???Y??????e?????%o>qM9w.????n,??~????"6g,?????7????b????6+??s????}?dp?z@?&w???u?v??K?S??8V?J? ???O6?S1a???juT???H??1??g?y??%?????x8??????z?????&???q?\??????eE????R b+??5?[?w???????>?????%??[??JY|+ ?%F??=2?????????b???e???"??id???r!???M?j~?????n??xD?:b&??&??9c???4?????_l??#zA?Y?u?b,HZ]??d{??M#C? +???t?q??E}}q??]?t? \????2??U???/?zL??W?? cU???c???_??????4?LX???'Y??}??|S??1?L?? ??F2{z?~?f????&%???s9 ???z<^(R?????-BKX???0?Y-???J:?F?I???????? ++?t!?1??+???ty???8?q?? +V?tv?b???3??z5?B?/4???????B?[~?????A??N?>N?EM??O??v?"OpW?&g??im???????be??e"??l??0r2??? +???????????N??F??????m??P???4?eL_ s????d#????v)Bs?k?A???|?#?N??P???C?$??B20S?????"?e?l>}=yQo???F#?0??=8??? ?wS???+??????9p48??0(?;? + (?wY=???c?????'o?> endobj +130 0 obj << +/Ascent 678 +/CapHeight 651 +/Descent -216 +/FontName /EXVUAL+NimbusRomNo9L-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 450 +/FontBBox [-168 -281 1000 924] +/Flags 4 +/CharSet (/fi/fl/exclam/quotedbl/numbersign/dollar/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/bullet) +/FontFile 131 0 R +>> endobj +616 0 obj +[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 500 500 0 778 333 333 333 500 564 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 564 564 564 444 921 722 667 667 722 611 556 722 722 333 389 722 611 889 722 722 556 0 667 556 611 722 722 944 722 722 0 333 278 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 350 ] +endobj +140 0 obj << +/Type /Pages +/Count 6 +/Parent 617 0 R +/Kids [126 0 R 142 0 R 180 0 R 214 0 R 259 0 R 304 0 R] +>> endobj +382 0 obj << +/Type /Pages +/Count 6 +/Parent 617 0 R +/Kids [356 0 R 384 0 R 427 0 R 481 0 R 485 0 R 494 0 R] +>> endobj +557 0 obj << +/Type /Pages +/Count 3 +/Parent 617 0 R +/Kids [525 0 R 559 0 R 592 0 R] +>> endobj +617 0 obj << +/Type /Pages +/Count 15 +/Kids [140 0 R 382 0 R 557 0 R] +>> endobj +618 0 obj << +/Type /Outlines +/First 7 0 R +/Last 107 0 R +/Count 6 +>> endobj +123 0 obj << +/Title 124 0 R +/A 121 0 R +/Parent 107 0 R +/Prev 111 0 R +>> endobj +119 0 obj << +/Title 120 0 R +/A 117 0 R +/Parent 111 0 R +/Prev 115 0 R +>> endobj +115 0 obj << +/Title 116 0 R +/A 113 0 R +/Parent 111 0 R +/Next 119 0 R +>> endobj +111 0 obj << +/Title 112 0 R +/A 109 0 R +/Parent 107 0 R +/Next 123 0 R +/First 115 0 R +/Last 119 0 R +/Count -2 +>> endobj +107 0 obj << +/Title 108 0 R +/A 105 0 R +/Parent 618 0 R +/Prev 103 0 R +/First 111 0 R +/Last 123 0 R +/Count -2 +>> endobj +103 0 obj << +/Title 104 0 R +/A 101 0 R +/Parent 618 0 R +/Prev 83 0 R +/Next 107 0 R +>> endobj +99 0 obj << +/Title 100 0 R +/A 97 0 R +/Parent 83 0 R +/Prev 95 0 R +>> endobj +95 0 obj << +/Title 96 0 R +/A 93 0 R +/Parent 83 0 R +/Prev 91 0 R +/Next 99 0 R +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 83 0 R +/Prev 87 0 R +/Next 95 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 83 0 R +/Next 91 0 R +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 618 0 R +/Prev 71 0 R +/Next 103 0 R +/First 87 0 R +/Last 99 0 R +/Count -4 +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 71 0 R +/Prev 75 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 618 0 R +/Prev 11 0 R +/Next 83 0 R +/First 75 0 R +/Last 79 0 R +/Count -2 +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 63 0 R +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 11 0 R +/Prev 59 0 R +/First 67 0 R +/Last 67 0 R +/Count -1 +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 11 0 R +/Prev 55 0 R +/Next 63 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 11 0 R +/Prev 51 0 R +/Next 59 0 R +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 11 0 R +/Prev 47 0 R +/Next 55 0 R +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 11 0 R +/Prev 43 0 R +/Next 51 0 R +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 11 0 R +/Prev 23 0 R +/Next 47 0 R +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 23 0 R +/Prev 35 0 R +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 23 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 23 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 11 0 R +/Prev 15 0 R +/Next 43 0 R +/First 27 0 R +/Last 39 0 R +/Count -4 +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 15 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 11 0 R +/Next 23 0 R +/First 19 0 R +/Last 19 0 R +/Count -1 +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 618 0 R +/Prev 7 0 R +/Next 71 0 R +/First 15 0 R +/Last 63 0 R +/Count -8 +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 618 0 R +/Next 11 0 R +>> endobj +619 0 obj << +/Names [(Doc-Start) 136 0 R (Item.1) 307 0 R (Item.10) 562 0 R (Item.11) 563 0 R (Item.12) 597 0 R (Item.13) 598 0 R (Item.14) 599 0 R (Item.15) 600 0 R (Item.16) 601 0 R (Item.17) 602 0 R (Item.18) 603 0 R (Item.19) 604 0 R (Item.2) 308 0 R (Item.20) 605 0 R (Item.3) 309 0 R (Item.4) 360 0 R (Item.5) 361 0 R (Item.6) 362 0 R (Item.7) 554 0 R (Item.8) 555 0 R (Item.9) 556 0 R (_beagle) 491 0 R (_bionimbus) 513 0 R (_coaster_providers_local_ssh_pbs) 489 0 R (_coasters) 453 0 R (_debugging_swift) 553 0 R (_environment_setup) 205 0 R (_first_swiftscript) 262 0 R (_for_advanced_users) 488 0 R (_installation) 186 0 R (_log_processing) 564 0 R (_make_a_basic_block_allocation_plot_from_coasters_block_log_lines) 586 0 R (_make_a_basic_job_completion_plot_from_coasters_cpu_log_lines) 581 0 R (_make_a_basic_load_plot_from_coasters_cpu_log_lines) 568 0 R (_mappers) 363 0 R (_osg) 512 0 R (_overview) 183 0 R (_pads) 497 0 R (_passing_an_array_to_swift) 359 0 R (_prerequisites) 187 0 R ( _problem_reporting) 595 0 R (_resuming_a_stopped_or_crashed_swift_run) 317 0 R (_second_swiftscript) 284 0 R (_setting_sites_xml) 248 0 R (_setting_swift_configuration) 232 0 R (_setting_transformation_catalog) 219 0 R (_setting_up_to_run_swift) 201 0 R (_swift_basics) 185 0 R (_swift_commandline_options) 301 0 R (_swift_on_diverse_infrastructures) 490 0 R (_what_if_swift_hangs) 302 0 R (lstlisting.-1) 188 0 R (lstlisting.-10) 285 0 R (lstlisting.-11) 310 0 R (lstlisting.-12) 318 0 R (lstlisting.-13) 329 0 R (lstlisting.-14) 364 0 R (lstlisting.-15) 366 0 R (lstlisting.-16) 387 0 R (lstlisting.-17) 394 0 R (lstlisting.-18) 396 0 R (lstlisting.-19) 402 0 R (lstlisting.-2) 203 0 R (lstlisting.-20) 411 0 R (lstlisting.-21) 455 0 R (lstlisting.-22) 498 0 R (lstlisting.-23) 500 0 R (lstlisting.-24) 514 0 R (lstlisting.-25) 528 0 R (lstlisting.-26) 533 0 R (lstlisting.-27) 565 0 R (lstlisting.-28) 569 0 R (lstlisting.-29) 571 0 R (lstlisting.-3) 206 0 R (lstlisting.-30) 573 0 R (l stlisting.-31) 575 0 R (lstlisting.-32) 577 0 R (lstlisting.-33) 579 0 R (lstlisting.-34) 582 0 R (lstlisting.-35) 584 0 R (lstlisting.-36) 587 0 R (lstlisting.-37) 589 0 R (lstlisting.-4) 208 0 R (lstlisting.-5) 217 0 R (lstlisting.-6) 220 0 R (lstlisting.-7) 234 0 R (lstlisting.-8) 249 0 R (lstlisting.-9) 263 0 R (lstnumber.-1.1) 189 0 R (lstnumber.-1.2) 193 0 R (lstnumber.-1.3) 194 0 R (lstnumber.-1.4) 195 0 R (lstnumber.-1.5) 196 0 R (lstnumber.-1.6) 197 0 R (lstnumber.-1.7) 198 0 R (lstnumber.-1.8) 199 0 R (lstnumber.-1.9) 200 0 R (lstnumber.-10.1) 286 0 R (lstnumber.-10.10) 295 0 R (lstnumber.-10.11) 296 0 R (lstnumber.-10.12) 297 0 R (lstnumber.-10.13) 298 0 R (lstnumber.-10.14) 299 0 R (lstnumber.-10.15) 300 0 R (lstnumber.-10.2) 287 0 R (lstnumber.-10.3) 288 0 R (lstnumber.-10.4) 289 0 R (lstnumber.-10.5) 290 0 R (lstnumber.-10.6) 291 0 R (lstnumber.-10.7) 292 0 R (lstnumber.-10.8) 293 0 R (lstnumber.-10.9) 294 0 R (lstnumber.-11.1) 311 0 R (lstnumber.-11.2) 312 0 R (lstnumber.-11.3) 313 0 R (lstnumber.-11.4) 314 0 R (lstnumber.-11.5) 315 0 R (lstnumber.-11.6) 316 0 R (lstnumber.-12.1) 319 0 R (lstnumber.-12.10) 328 0 R (lstnumber.-12.2) 320 0 R (lstnumber.-12.3) 321 0 R (lstnumber.-12.4) 322 0 R (lstnumber.-12.5) 323 0 R (lstnumber.-12.6) 324 0 R (lstnumber.-12.7) 325 0 R (lstnumber.-12.8) 326 0 R (lstnumber.-12.9) 327 0 R (lstnumber.-13.1) 330 0 R (lstnumber.-13.10) 339 0 R (lstnumber.-13.11) 340 0 R (lstnumber.-13.12) 341 0 R (lstnumber.-13.13) 342 0 R (lstnumber.-13.14) 343 0 R (lstnumber.-13.15) 344 0 R (lstnumber.-13.16) 345 0 R (lstnumber.-13.17) 346 0 R (lstnumber.-13.18) 347 0 R (lstnumber.-13.19) 348 0 R (lstnumber.-13.2) 331 0 R (lstnumber.-13.20) 349 0 R (lstnumber.-13.21) 350 0 R (lstnumber.-13.22) 351 0 R (lstnumber.-13.23) 352 0 R (lstnumber.-13.24) 353 0 R (lstnumber.-13.25) 354 0 R (lstnumber.-13.3) 332 0 R (lstnumber.-13.4) 333 0 R (lstnumber.-13.5) 334 0 R (lstnumber.-13.6) 335 0 R (lstnumber.-13.7) 336 0 R (lstnumbe r.-13.8) 337 0 R (lstnumber.-13.9) 338 0 R (lstnumber.-14.1) 365 0 R (lstnumber.-15.1) 367 0 R (lstnumber.-15.10) 376 0 R (lstnumber.-15.11) 377 0 R (lstnumber.-15.12) 378 0 R (lstnumber.-15.13) 379 0 R (lstnumber.-15.14) 380 0 R (lstnumber.-15.15) 381 0 R (lstnumber.-15.2) 368 0 R (lstnumber.-15.3) 369 0 R (lstnumber.-15.4) 370 0 R (lstnumber.-15.5) 371 0 R (lstnumber.-15.6) 372 0 R (lstnumber.-15.7) 373 0 R (lstnumber.-15.8) 374 0 R (lstnumber.-15.9) 375 0 R (lstnumber.-16.1) 388 0 R (lstnumber.-16.2) 389 0 R (lstnumber.-16.3) 390 0 R (lstnumber.-16.4) 391 0 R (lstnumber.-16.5) 392 0 R (lstnumber.-16.6) 393 0 R (lstnumber.-17.1) 395 0 R (lstnumber.-18.1) 397 0 R (lstnumber.-18.2) 398 0 R (lstnumber.-18.3) 399 0 R (lstnumber.-18.4) 400 0 R (lstnumber.-18.5) 401 0 R (lstnumber.-19.1) 403 0 R (lstnumber.-19.2) 404 0 R (lstnumber.-19.3) 405 0 R (lstnumber.-19.4) 406 0 R (lstnumber.-19.5) 407 0 R (lstnumber.-19.6) 408 0 R (lstnumber.-19.7) 409 0 R (lstnumber.-19.8) 410 0 R (lst number.-2.1) 204 0 R (lstnumber.-20.1) 412 0 R (lstnumber.-20.10) 421 0 R (lstnumber.-20.11) 422 0 R (lstnumber.-20.12) 423 0 R (lstnumber.-20.13) 424 0 R (lstnumber.-20.14) 425 0 R (lstnumber.-20.15) 430 0 R (lstnumber.-20.16) 431 0 R (lstnumber.-20.17) 432 0 R (lstnumber.-20.18) 433 0 R (lstnumber.-20.19) 434 0 R (lstnumber.-20.2) 413 0 R (lstnumber.-20.20) 435 0 R (lstnumber.-20.21) 436 0 R (lstnumber.-20.22) 437 0 R (lstnumber.-20.23) 438 0 R (lstnumber.-20.24) 439 0 R (lstnumber.-20.25) 440 0 R (lstnumber.-20.26) 441 0 R (lstnumber.-20.27) 442 0 R (lstnumber.-20.28) 443 0 R (lstnumber.-20.29) 444 0 R (lstnumber.-20.3) 414 0 R (lstnumber.-20.30) 445 0 R (lstnumber.-20.31) 446 0 R (lstnumber.-20.32) 447 0 R (lstnumber.-20.33) 448 0 R (lstnumber.-20.34) 449 0 R (lstnumber.-20.35) 450 0 R (lstnumber.-20.36) 451 0 R (lstnumber.-20.37) 452 0 R (lstnumber.-20.4) 415 0 R (lstnumber.-20.5) 416 0 R (lstnumber.-20.6) 417 0 R (lstnumber.-20.7) 418 0 R (lstnumber.-20.8) 419 0 R (lst number.-20.9) 420 0 R (lstnumber.-21.1) 456 0 R (lstnumber.-21.10) 465 0 R (lstnumber.-21.11) 466 0 R (lstnumber.-21.12) 467 0 R (lstnumber.-21.13) 468 0 R (lstnumber.-21.14) 469 0 R (lstnumber.-21.15) 470 0 R (lstnumber.-21.16) 471 0 R (lstnumber.-21.17) 472 0 R (lstnumber.-21.18) 473 0 R (lstnumber.-21.19) 474 0 R (lstnumber.-21.2) 457 0 R (lstnumber.-21.20) 475 0 R (lstnumber.-21.21) 476 0 R (lstnumber.-21.22) 477 0 R (lstnumber.-21.23) 478 0 R (lstnumber.-21.24) 479 0 R (lstnumber.-21.3) 458 0 R (lstnumber.-21.4) 459 0 R (lstnumber.-21.5) 460 0 R (lstnumber.-21.6) 461 0 R (lstnumber.-21.7) 462 0 R (lstnumber.-21.8) 463 0 R (lstnumber.-21.9) 464 0 R (lstnumber.-22.1) 499 0 R (lstnumber.-23.1) 501 0 R (lstnumber.-23.10) 510 0 R (lstnumber.-23.11) 511 0 R (lstnumber.-23.2) 502 0 R (lstnumber.-23.3) 503 0 R (lstnumber.-23.4) 504 0 R (lstnumber.-23.5) 505 0 R (lstnumber.-23.6) 506 0 R (lstnumber.-23.7) 507 0 R (lstnumber.-23.8) 508 0 R (lstnumber.-23.9) 509 0 R (lstnumber.-24 .1) 515 0 R (lstnumber.-24.2) 516 0 R (lstnumber.-24.3) 517 0 R (lstnumber.-24.4) 518 0 R (lstnumber.-24.5) 519 0 R (lstnumber.-24.6) 520 0 R (lstnumber.-24.7) 521 0 R (lstnumber.-24.8) 522 0 R (lstnumber.-24.9) 523 0 R (lstnumber.-25.1) 529 0 R (lstnumber.-26.1) 534 0 R (lstnumber.-26.10) 543 0 R (lstnumber.-26.11) 544 0 R (lstnumber.-26.12) 545 0 R (lstnumber.-26.13) 546 0 R (lstnumber.-26.14) 547 0 R (lstnumber.-26.15) 548 0 R (lstnumber.-26.16) 549 0 R (lstnumber.-26.17) 550 0 R (lstnumber.-26.18) 551 0 R (lstnumber.-26.19) 552 0 R (lstnumber.-26.2) 535 0 R (lstnumber.-26.3) 536 0 R (lstnumber.-26.4) 537 0 R (lstnumber.-26.5) 538 0 R (lstnumber.-26.6) 539 0 R (lstnumber.-26.7) 540 0 R (lstnumber.-26.8) 541 0 R (lstnumber.-26.9) 542 0 R (lstnumber.-27.1) 566 0 R (lstnumber.-27.2) 567 0 R (lstnumber.-28.1) 570 0 R (lstnumber.-29.1) 572 0 R (lstnumber.-3.1) 207 0 R (lstnumber.-30.1) 574 0 R (lstnumber.-31.1) 576 0 R (lstnumber.-32.1) 578 0 R (lstnumber.-33.1) 580 0 R (lstnu mber.-34.1) 583 0 R (lstnumber.-35.1) 585 0 R (lstnumber.-36.1) 588 0 R (lstnumber.-37.1) 590 0 R (lstnumber.-4.1) 209 0 R (lstnumber.-5.1) 218 0 R (lstnumber.-6.1) 221 0 R (lstnumber.-6.2) 222 0 R (lstnumber.-7.1) 235 0 R (lstnumber.-7.10) 244 0 R (lstnumber.-7.11) 245 0 R (lstnumber.-7.12) 246 0 R (lstnumber.-7.13) 247 0 R (lstnumber.-7.2) 236 0 R (lstnumber.-7.3) 237 0 R (lstnumber.-7.4) 238 0 R (lstnumber.-7.5) 239 0 R (lstnumber.-7.6) 240 0 R (lstnumber.-7.7) 241 0 R (lstnumber.-7.8) 242 0 R (lstnumber.-7.9) 243 0 R (lstnumber.-8.1) 250 0 R (lstnumber.-8.2) 251 0 R (lstnumber.-8.3) 252 0 R (lstnumber.-8.4) 253 0 R (lstnumber.-8.5) 254 0 R (lstnumber.-8.6) 255 0 R (lstnumber.-8.7) 256 0 R (lstnumber.-8.8) 257 0 R (lstnumber.-9.1) 264 0 R (lstnumber.-9.10) 273 0 R (lstnumber.-9.11) 274 0 R (lstnumber.-9.12) 275 0 R (lstnumber.-9.13) 276 0 R (lstnumber.-9.14) 277 0 R (lstnumber.-9.15) 278 0 R (lstnumber.-9.16) 279 0 R (lstnumber.-9.17) 280 0 R (lstnumber.-9.18) 281 0 R (ls tnumber.-9.19) 282 0 R (lstnumber.-9.2) 265 0 R (lstnumber.-9.3) 266 0 R (lstnumber.-9.4) 267 0 R (lstnumber.-9.5) 268 0 R (lstnumber.-9.6) 269 0 R (lstnumber.-9.7) 270 0 R (lstnumber.-9.8) 271 0 R (lstnumber.-9.9) 272 0 R (page.1) 182 0 R (page.10) 496 0 R (page.11) 527 0 R (page.12) 561 0 R (page.13) 594 0 R (page.2) 216 0 R (page.3) 261 0 R (page.4) 306 0 R (page.5) 358 0 R (page.6) 386 0 R (page.7) 429 0 R (page.8) 483 0 R (page.9) 487 0 R (page.i) 129 0 R (page.ii) 144 0 R (section.1) 6 0 R (section.2) 10 0 R (section.3) 70 0 R (section.4) 82 0 R (section.5) 102 0 R (section.6) 106 0 R (subsection.2.1) 14 0 R (subsection.2.2) 22 0 R (subsection.2.3) 42 0 R (subsection.2.4) 46 0 R (subsection.2.5) 50 0 R (subsection.2.6) 54 0 R (subsection.2.7) 58 0 R (subsection.2.8) 62 0 R (subsection.3.1) 74 0 R (subsection.3.2) 78 0 R (subsection.4.1) 86 0 R (subsection.4.2) 90 0 R (subsection.4.3) 94 0 R (subsection.4.4) 98 0 R (subsection.6.1) 110 0 R (subsection.6.2) 122 0 R (subs ubsection.2.1.1) 18 0 R (subsubsection.2.2.1) 26 0 R (subsubsection.2.2.2) 30 0 R (subsubsection.2.2.3) 34 0 R (subsubsection.2.2.4) 38 0 R (subsubsection.2.8.1) 66 0 R (subsubsection.6.1.1) 114 0 R (subsubsection.6.1.2) 118 0 R] +/Limits [(Doc-Start) (subsubsection.6.1.2)] +>> endobj +620 0 obj << +/Kids [619 0 R] +>> endobj +621 0 obj << +/Dests 620 0 R +>> endobj +622 0 obj << +/Type /Catalog +/Pages 617 0 R +/Outlines 618 0 R +/Names 621 0 R +/PageMode /UseOutlines +/OpenAction 125 0 R +>> endobj +623 0 obj << +/Author(Swift team)/Title(Swift Cookbook)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() +/CreationDate (D:20110516141543-05'00') +/PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) +>> endobj +xref +0 624 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000017512 00000 n +0000197747 00000 n +0000000054 00000 n +0000000080 00000 n +0000017636 00000 n +0000197624 00000 n +0000000125 00000 n +0000000156 00000 n +0000017761 00000 n +0000197513 00000 n +0000000207 00000 n +0000000238 00000 n +0000017886 00000 n +0000197452 00000 n +0000000294 00000 n +0000000326 00000 n +0000018640 00000 n +0000197328 00000 n +0000000377 00000 n +0000000419 00000 n +0000018891 00000 n +0000197254 00000 n +0000000475 00000 n +0000000511 00000 n +0000024963 00000 n +0000197167 00000 n +0000000567 00000 n +0000000616 00000 n +0000025277 00000 n +0000197080 00000 n +0000000672 00000 n +0000000718 00000 n +0000026281 00000 n +0000197006 00000 n +0000000774 00000 n +0000000810 00000 n +0000031939 00000 n +0000196919 00000 n +0000000861 00000 n +0000000897 00000 n +0000033321 00000 n +0000196832 00000 n +0000000948 00000 n +0000000985 00000 n +0000034452 00000 n +0000196745 00000 n +0000001036 00000 n +0000001080 00000 n +0000034577 00000 n +0000196658 00000 n +0000001131 00000 n +0000001169 00000 n +0000042833 00000 n +0000196571 00000 n +0000001220 00000 n +0000001278 00000 n +0000049927 00000 n +0000196460 00000 n +0000001329 00000 n +0000001374 00000 n +0000050241 00000 n +0000196399 00000 n +0000001430 00000 n +0000001456 00000 n +0000068232 00000 n +0000196274 00000 n +0000001502 00000 n +0000001529 00000 n +0000074711 00000 n +0000196200 00000 n +0000001580 00000 n +0000001617 00000 n +0000074835 00000 n +0000196126 00000 n +0000001668 00000 n +0000001721 00000 n +0000074960 00000 n +0000196000 00000 n +0000001767 00000 n +0000001818 00000 n +0000075085 00000 n +0000195926 00000 n +0000001869 00000 n +0000001894 00000 n +0000079739 00000 n +0000195839 00000 n +0000001945 00000 n +0000001968 00000 n +0000080744 00000 n +0000195752 00000 n +0000002019 00000 n +0000002041 00000 n +0000080869 00000 n +0000195677 00000 n +0000002092 00000 n +0000002121 00000 n +0000089288 00000 n +0000195585 00000 n +0000002168 00000 n +0000002203 00000 n +0000094884 00000 n +0000195467 00000 n +0000002250 00000 n +0000002284 00000 n +0000095199 00000 n +0000195349 00000 n +0000002336 00000 n +0000002406 00000 n +0000096080 00000 n +0000195270 00000 n +0000002463 00000 n +0000002543 00000 n +0000096456 00000 n +0000195191 00000 n +0000002600 00000 n +0000002684 00000 n +0000098747 00000 n +0000195112 00000 n +0000002736 00000 n +0000002773 00000 n +0000003183 00000 n +0000003431 00000 n +0000002826 00000 n +0000003305 00000 n +0000193559 00000 n +0000172896 00000 n +0000193386 00000 n +0000172255 00000 n +0000164316 00000 n +0000172084 00000 n +0000003368 00000 n +0000163588 00000 n +0000152003 00000 n +0000163418 00000 n +0000194632 00000 n +0000011340 00000 n +0000006110 00000 n +0000003529 00000 n +0000011277 00000 n +0000006484 00000 n +0000151224 00000 n +0000135699 00000 n +0000151051 00000 n +0000006638 00000 n +0000006793 00000 n +0000006953 00000 n +0000007118 00000 n +0000007278 00000 n +0000007440 00000 n +0000007605 00000 n +0000007770 00000 n +0000007935 00000 n +0000008092 00000 n +0000008251 00000 n +0000008411 00000 n +0000008571 00000 n +0000008728 00000 n +0000008888 00000 n +0000009053 00000 n +0000009208 00000 n +0000009368 00000 n +0000009528 00000 n +0000009683 00000 n +0000009843 00000 n +0000010000 00000 n +0000010160 00000 n +0000010320 00000 n +0000010475 00000 n +0000010627 00000 n +0000010787 00000 n +0000010952 00000 n +0000011117 00000 n +0000016152 00000 n +0000019266 00000 n +0000016002 00000 n +0000011451 00000 n +0000017449 00000 n +0000017573 00000 n +0000017041 00000 n +0000017698 00000 n +0000017823 00000 n +0000017948 00000 n +0000018011 00000 n +0000018074 00000 n +0000134755 00000 n +0000115700 00000 n +0000134584 00000 n +0000018137 00000 n +0000018200 00000 n +0000018263 00000 n +0000018326 00000 n +0000018388 00000 n +0000018451 00000 n +0000018514 00000 n +0000018577 00000 n +0000018702 00000 n +0000017245 00000 n +0000018765 00000 n +0000018828 00000 n +0000018951 00000 n +0000019014 00000 n +0000019077 00000 n +0000019140 00000 n +0000019203 00000 n +0000016838 00000 n +0000016973 00000 n +0000017020 00000 n +0000026970 00000 n +0000024407 00000 n +0000019418 00000 n +0000024774 00000 n +0000024837 00000 n +0000024900 00000 n +0000025025 00000 n +0000025088 00000 n +0000025151 00000 n +0000025214 00000 n +0000115373 00000 n +0000113916 00000 n +0000115212 00000 n +0000113581 00000 n +0000111726 00000 n +0000113420 00000 n +0000111161 00000 n +0000101424 00000 n +0000110984 00000 n +0000025339 00000 n +0000024549 00000 n +0000025402 00000 n +0000025463 00000 n +0000025526 00000 n +0000025589 00000 n +0000025652 00000 n +0000025715 00000 n +0000025778 00000 n +0000025840 00000 n +0000025903 00000 n +0000025966 00000 n +0000026029 00000 n +0000026092 00000 n +0000026155 00000 n +0000026218 00000 n +0000026342 00000 n +0000026405 00000 n +0000026468 00000 n +0000026531 00000 n +0000026594 00000 n +0000026657 00000 n +0000026719 00000 n +0000026782 00000 n +0000026845 00000 n +0000026908 00000 n +0000034702 00000 n +0000031531 00000 n +0000027133 00000 n +0000031876 00000 n +0000032001 00000 n +0000032064 00000 n +0000032126 00000 n +0000032189 00000 n +0000032252 00000 n +0000032315 00000 n +0000032378 00000 n +0000032441 00000 n +0000032504 00000 n +0000032566 00000 n +0000032629 00000 n +0000032692 00000 n +0000032755 00000 n +0000032818 00000 n +0000032881 00000 n +0000032944 00000 n +0000033007 00000 n +0000033070 00000 n +0000033133 00000 n +0000033195 00000 n +0000033258 00000 n +0000031673 00000 n +0000033383 00000 n +0000033446 00000 n +0000033509 00000 n +0000033572 00000 n +0000033635 00000 n +0000033697 00000 n +0000033760 00000 n +0000033823 00000 n +0000033886 00000 n +0000033949 00000 n +0000034012 00000 n +0000034075 00000 n +0000034138 00000 n +0000034201 00000 n +0000034264 00000 n +0000034327 00000 n +0000034389 00000 n +0000034514 00000 n +0000034639 00000 n +0000045285 00000 n +0000042019 00000 n +0000034826 00000 n +0000042141 00000 n +0000042204 00000 n +0000042267 00000 n +0000042330 00000 n +0000042393 00000 n +0000042456 00000 n +0000042519 00000 n +0000042581 00000 n +0000042644 00000 n +0000042707 00000 n +0000042770 00000 n +0000042895 00000 n +0000042958 00000 n +0000043021 00000 n +0000043084 00000 n +0000043147 00000 n +0000043210 00000 n +0000043273 00000 n +0000043336 00000 n +0000043399 00000 n +0000043462 00000 n +0000043525 00000 n +0000043588 00000 n +0000043650 00000 n +0000043713 00000 n +0000043776 00000 n +0000043838 00000 n +0000043901 00000 n +0000043964 00000 n +0000044027 00000 n +0000044090 00000 n +0000044153 00000 n +0000044216 00000 n +0000044279 00000 n +0000044342 00000 n +0000044405 00000 n +0000044467 00000 n +0000044530 00000 n +0000044593 00000 n +0000044656 00000 n +0000044719 00000 n +0000044782 00000 n +0000044845 00000 n +0000044908 00000 n +0000044971 00000 n +0000045034 00000 n +0000045097 00000 n +0000045159 00000 n +0000045222 00000 n +0000051498 00000 n +0000049742 00000 n +0000045409 00000 n +0000049864 00000 n +0000049989 00000 n +0000050052 00000 n +0000050115 00000 n +0000050178 00000 n +0000050303 00000 n +0000050366 00000 n +0000050429 00000 n +0000050492 00000 n +0000050555 00000 n +0000050618 00000 n +0000050680 00000 n +0000050743 00000 n +0000050806 00000 n +0000050869 00000 n +0000050932 00000 n +0000050995 00000 n +0000051058 00000 n +0000051121 00000 n +0000051184 00000 n +0000051247 00000 n +0000051309 00000 n +0000051372 00000 n +0000051435 00000 n +0000194749 00000 n +0000059343 00000 n +0000056705 00000 n +0000051609 00000 n +0000056827 00000 n +0000056890 00000 n +0000056953 00000 n +0000057016 00000 n +0000057079 00000 n +0000057142 00000 n +0000057205 00000 n +0000057268 00000 n +0000057331 00000 n +0000057394 00000 n +0000057457 00000 n +0000057519 00000 n +0000057582 00000 n +0000057645 00000 n +0000057708 00000 n +0000057771 00000 n +0000057834 00000 n +0000057897 00000 n +0000057960 00000 n +0000058023 00000 n +0000058086 00000 n +0000058148 00000 n +0000058211 00000 n +0000058274 00000 n +0000058337 00000 n +0000058400 00000 n +0000058463 00000 n +0000058526 00000 n +0000058589 00000 n +0000058652 00000 n +0000058714 00000 n +0000058777 00000 n +0000058840 00000 n +0000058903 00000 n +0000058966 00000 n +0000059029 00000 n +0000059092 00000 n +0000059155 00000 n +0000059218 00000 n +0000059281 00000 n +0000069929 00000 n +0000066368 00000 n +0000059441 00000 n +0000066723 00000 n +0000066786 00000 n +0000066849 00000 n +0000066912 00000 n +0000066975 00000 n +0000067038 00000 n +0000067100 00000 n +0000067163 00000 n +0000067226 00000 n +0000067289 00000 n +0000067352 00000 n +0000067415 00000 n +0000067478 00000 n +0000067541 00000 n +0000067604 00000 n +0000067667 00000 n +0000067728 00000 n +0000067791 00000 n +0000067854 00000 n +0000067917 00000 n +0000067980 00000 n +0000068043 00000 n +0000068106 00000 n +0000068169 00000 n +0000068294 00000 n +0000066510 00000 n +0000068357 00000 n +0000068420 00000 n +0000068483 00000 n +0000068545 00000 n +0000068608 00000 n +0000068671 00000 n +0000068734 00000 n +0000068797 00000 n +0000068860 00000 n +0000068923 00000 n +0000068986 00000 n +0000069049 00000 n +0000069112 00000 n +0000069174 00000 n +0000069237 00000 n +0000069300 00000 n +0000069363 00000 n +0000069426 00000 n +0000069489 00000 n +0000069552 00000 n +0000069615 00000 n +0000069678 00000 n +0000069741 00000 n +0000069803 00000 n +0000069866 00000 n +0000070639 00000 n +0000070454 00000 n +0000070066 00000 n +0000070576 00000 n +0000075209 00000 n +0000074306 00000 n +0000070724 00000 n +0000074648 00000 n +0000074773 00000 n +0000074897 00000 n +0000075022 00000 n +0000075147 00000 n +0000074448 00000 n +0000081621 00000 n +0000079554 00000 n +0000075333 00000 n +0000079676 00000 n +0000079801 00000 n +0000079864 00000 n +0000079927 00000 n +0000079990 00000 n +0000080052 00000 n +0000080115 00000 n +0000080178 00000 n +0000080241 00000 n +0000080304 00000 n +0000080367 00000 n +0000080429 00000 n +0000080492 00000 n +0000080555 00000 n +0000080618 00000 n +0000080681 00000 n +0000080806 00000 n +0000080931 00000 n +0000080994 00000 n +0000081057 00000 n +0000081120 00000 n +0000081180 00000 n +0000081243 00000 n +0000081306 00000 n +0000081369 00000 n +0000081432 00000 n +0000081495 00000 n +0000081558 00000 n +0000089602 00000 n +0000087161 00000 n +0000081758 00000 n +0000087841 00000 n +0000087904 00000 n +0000087967 00000 n +0000087319 00000 n +0000087494 00000 n +0000087667 00000 n +0000088030 00000 n +0000088093 00000 n +0000088156 00000 n +0000088219 00000 n +0000088282 00000 n +0000088345 00000 n +0000088408 00000 n +0000088470 00000 n +0000088533 00000 n +0000088596 00000 n +0000088659 00000 n +0000088722 00000 n +0000088785 00000 n +0000088848 00000 n +0000088911 00000 n +0000088974 00000 n +0000089037 00000 n +0000089099 00000 n +0000089162 00000 n +0000089225 00000 n +0000089351 00000 n +0000089414 00000 n +0000089477 00000 n +0000089540 00000 n +0000194866 00000 n +0000096833 00000 n +0000094573 00000 n +0000089752 00000 n +0000094695 00000 n +0000094758 00000 n +0000094821 00000 n +0000094947 00000 n +0000095010 00000 n +0000095073 00000 n +0000095136 00000 n +0000095262 00000 n +0000095325 00000 n +0000095388 00000 n +0000095451 00000 n +0000095514 00000 n +0000095577 00000 n +0000095639 00000 n +0000095702 00000 n +0000095765 00000 n +0000095828 00000 n +0000095891 00000 n +0000095954 00000 n +0000096017 00000 n +0000096143 00000 n +0000096204 00000 n +0000096267 00000 n +0000096330 00000 n +0000096393 00000 n +0000096519 00000 n +0000096582 00000 n +0000096645 00000 n +0000096708 00000 n +0000096770 00000 n +0000099438 00000 n +0000098359 00000 n +0000096957 00000 n +0000098684 00000 n +0000098810 00000 n +0000098501 00000 n +0000098873 00000 n +0000098936 00000 n +0000098999 00000 n +0000099062 00000 n +0000099124 00000 n +0000099187 00000 n +0000099250 00000 n +0000099312 00000 n +0000099375 00000 n +0000099536 00000 n +0000111426 00000 n +0000113821 00000 n +0000113797 00000 n +0000115610 00000 n +0000115585 00000 n +0000135325 00000 n +0000151621 00000 n +0000163948 00000 n +0000172614 00000 n +0000194140 00000 n +0000194959 00000 n +0000195037 00000 n +0000197819 00000 n +0000208006 00000 n +0000208045 00000 n +0000208083 00000 n +0000208213 00000 n +trailer +<< +/Size 624 +/Root 622 0 R +/Info 623 0 R +/ID [<67FDFAA0CD9D108A567B8B97804AD5DB> <67FDFAA0CD9D108A567B8B97804AD5DB>] +>> +startxref +208484 +%%EOF Added: branches/release-0.92/docs/cookbook/cookbook-asciidoc.txt =================================================================== --- branches/release-0.92/docs/cookbook/cookbook-asciidoc.txt (rev 0) +++ branches/release-0.92/docs/cookbook/cookbook-asciidoc.txt 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,891 @@ +// To compile use: asciidoc -a toc -n cookbook-asciidoc.txt + + +Swift Cookbook +============== +Swift team +v0.92, March 2011 + +Overview +-------- +This cookbook covers various recipes involving setting up and running Swift under diverse +configurations based on the application requirements and the underlying +infrastructures. The Swift system comprises of SwiftScript language and the +Swift runtime system. For +introductory material, consult the Swift tutorial found +link:http://www.ci.uchicago.edu/swift/guides/tutorial.php[here]. + +Swift Basics +------------ + +Installation +~~~~~~~~~~~~ + +This section takes you through the installation of the Swift system on your +computer. We will start with the prerequisites as explained in the subsequent +section. + +Prerequisites +^^^^^^^^^^^^^^ +.Check your Java +Swift is a Java application. Make sure you are running Java version 5 or higher. You +can make sure you have Java in your $PATH (or $HOME/.soft file depending upon +your environment) + +Following are the possible ways to detect and run Java: + +---- +$ grep java $HOME/.soft +#+java-sun # Gives you Java 5 ++java-1.6.0_03-sun-r1 +$ which java +/soft/java-1.6.0_11-sun-r1/bin/java +$ java -version +java version "1.6.0_11" +Java(TM) SE Runtime Environment (build 1.6.0_11-b03) +Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode) +---- + +Setting up to run Swift +~~~~~~~~~~~~~~~~~~~~~~~~ +This is simple. We will be using a pre-compiled version of Swift that can be +downloaded from link:http://www.ci.uchicago.edu/swift/downloads/index.php[here]. Download and untar the latest precompiled version as follows: + +---- +$ tar xf swift-0.92.1.tar.gz +---- + +Environment Setup +^^^^^^^^^^^^^^^^^^ + +The examples were tested with Java version 1.6. Make sure you do not already +have Swift in your PATH. If you do, remove it, or remove any +swift or @swift +lines from your $HOME/.soft or $HOME/.bash_profile file. Then do: + +---- +PATH=$PATH:/path/to/swift/bin +---- + +Note that the environment will be different when using Swift from prebuilt distribution (as above) and trunk. The PATH setup when using swift from trunk would be as follows: + +---- +PATH=$PATH:/path/to/swift/dist/swift-svn/bin +---- + +WARNING: Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you +fully understand how these will affect Swift's execution. + +To execute your Swift script on a login host (or "localhost") use +the following command: + +---- +swift -tc.file tc somescript.swift +---- + +Setting transformation catalog +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +The transformation catalog lists where application executables are located on +remote sites. + +By default, the site catalog is stored in etc/tc.data. This path can be +overridden with the tc.file configuration property, either in the Swift +configuration file or on the command line. + +The format is one line per executable per site, with fields separated by tabs +or spaces. + +Some example entries: + +---- +localhost echo /bin/echo INSTALLED INTEL32::LINUX null +TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:00:10" +---- +The fields are: _site_, _transformation-name_, _executable-path_, _installation-status_, _platform_, and _profile_ entries. + +The _site_ field should correspond to a site name listed in the sites catalog. + +The _transformation-name_ should correspond to the transformation name used in a +SwiftScript app procedure. + +The _executable-path_ should specify where the particular executable is located +on that site. + +The _installation-status_ and _platform_ fields are not used. Set them to +**INSTALLED** and **INTEL32::LINUX** respectively. + +The _profiles_ field should be set to null if no profile entries are to be +specified, or should contain the profile entries separated by semicolons. + +Setting swift configuration +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Many configuration properties could be set using the Swift configuration file. +We will not cover them all in this section. see +link:http://www.ci.uchicago.edu/swift/guides/userguide.php#engineconfiguration[here] for details. In this section we will cover a simple configuration file with the most basic properties. + +---- +# A comment +wrapperlog.always.transfer=true +sitedir.keep=true +execution.retries=1 +lazy.errors=true +status.mode=provider +use.provider.staging=true +provider.staging.pin.swiftfiles=false +clustering.enabled=false +clustering.queue.delay=10 +clustering.min.time=86400 +foreach.max.threads=100 +provenance.log=true +---- + +Setting sites.xml +^^^^^^^^^^^^^^^^^^ +sites.xml specifies details of the sites that Swift can run on. Following is +an example of a simple sites.xml file entry for running Swift on local +environment: + +[xml] +source~~~~~~ + + + +/var/tmp +.07 +100000 + +source~~~~~~ + +First SwiftScript +~~~~~~~~~~~~~~~~~ +Your first SwiftScript +Hello Swift-World! + +A good sanity check that Swift is set up and running OK locally is this: + +---- +$ which swift + +/home/wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift + +$ echo 'trace("Hello, Swift world!");' >hello.swift + +$ swift hello.swift + +Swift svn swift-r3202 cog-r2682 + +RunID: 20100115-1240-6xhzxuz3 + +Progress: + +SwiftScript trace: Hello, Swift world! + +Final status: + +$ +---- +A good first tutorial in using Swift is at: +http://www.ci.uchicago.edu/swift/guides/tutorial.php. Follow the steps in that +tutorial to learn how to run a few simple scripts on the login host. + +second SwiftScript +~~~~~~~~~~~~~~~~~~~ +Following is a more involved Swift script. +[java] +source~~~~~~~ +type file; + +app (file o) cat (file i) +{ + cat @i stdout=@o; +} + +file out[]; + +foreach j in [1:@toint(@arg("n","1"))] { + + file data<"data.txt">; + + out[j] = cat(data); +} +source~~~~~~~ + +Swift Commandline Options +~~~~~~~~~~~~~~~~~~~~~~~~~ +A description of Swift Commandline Options + +Also includes a description of Swift inputs and outputs. + +What if Swift hangs +~~~~~~~~~~~~~~~~~~~ +Owing to its highly multithreaded architecture it is often the case that the +underlying java virtual machine gets into deadlock situations or Swift hangs +because of other complications in its threaded operations. Under such +situations, Swift _hang-checker_ chips in and resolves the situation. + +. how to use the information to identify and correct the deadlock. + +. How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines? + +. The current Hang Checker output is actually *very* nice and useful already: + +---- +Registered futures: +Rupture[] rups Closed, 1 elements, 0 listeners +Variation vars - Closed, no listeners +SgtDim sub - Open, 1 listeners +string site Closed, no listeners +Variation[] vars Closed, 72 elements, 0 listeners +---- + +Resuming a stopped or crashed Swift Run +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +I had a .rlog file from a Swift run that ran out of time. I kicked it off +using the -resume flag described in section 16.2 of the Swift User Guide and +it picked up where it left off. Then I killed it because I wanted to make +changes to my sites file. + +---- +. . . +Progress: Selecting site:1150 Stage in:55 Active:3 Checking status:1 +Stage out:37 Finished in previous run:2462 Finished successfully:96 +Progress: Selecting site:1150 Stage in:55 Active:2 Checking status:1 +Stage out:38 Finished in previous run:2462 Finished successfully:96 +Cleaning up... +Shutting down service at https://192.5.86.6:54813 +Got channel MetaChannel: 1293358091 -> null ++ Done +Canceling job 9297.svc.pads.ci.uchicago.edu +---- + +No new rlog file was emitted but it did recognize the progress that had been +made, the 96 tasks that finished sucessfully above and resumed from 2558 tasks +finished. + +---- +[nbest at login2 files]$ pwd +/home/nbest/bigdata/files +[nbest at login2 files]$ +~wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift \ +> -tc.file tc -sites.file pbs.xml ~/scripts/mcd12q1.swift -resume +> mcd12q1-20100310-1326-ptxe1x1d.0.rlog +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified +locally) +RunID: 20100311-1027-148caf0a +Progress: +Progress: uninitialized:4 +Progress: Selecting site:671 Initializing site shared directory:1 Finished +in previous run:1864 +Progress: uninitialized:1 Selecting site:576 Stage in:96 Finished in +previous run:1864 +Progress: Selecting site:1150 Stage in:94 Submitting:2 Finished in +previous run:2558 +Progress: Selecting site:1150 Stage in:94 Submitted:2 Finished in previous +run:2558 +Progress: Selecting site:1150 Stage in:93 Submitting:1 Submitted:2 +Finished in previous run:2558 +Progress: Selecting site:1150 Stage in:90 Submitting:1 Submitted:5 +Finished in previous run:2558 +Progress: Selecting site:1150 Stage in:90 Submitted:5 Active:1 Finished +in previous run:2558 +---- + + +From Neil: A comment about that section of the user guide: It says "In order +to restart from a restart log file, the -resume logfile argument can be used +after the SwiftScript? program file name." and then puts the -resume logfile +argument before the script file name. I'm sure the order doesn't matter but +the contradiction is confusing. + +Notes to add (from Mike): + +- explain what aspects of a Swift script make it restartable, and which + aspects are notrestartable. Eg, if your mappers can return different data at +different times, what happens? What other non-determinsitc behavior would +cause unpredictable, unexpected, or undesired behavior on resumption? + +- explain what changes you can make in the execution environment (eg + increasing or reducing CPUs to run on or throttles, etc); fixing tc.data +entries, env vars, or apps, etc. + +- note that resume will again retry failed app() calls. Explain if the retry + count starts over or not. + +- explain how to resume after multiple failures and resumes - i.e. if a .rlog + is generated on each run, which one should you resume from? Do you have a +choice of resuming from any of them, and what happens if you go backwards to +an older resume file? + +- whap happens when you kill (eg with ^C) a running swift script? Is the + signal caught, and the resume file written out at that point? Or written out +all along? (Note case in which script ws running for hours, then hit ^C, but +resume fie was short (54 bbytes) and swift shows no sign of doing a resume? +(It silently ignored resume file instead of acknowleging that it found one +with not useful resume state in it???) Swift should clearly state that its +resuming and what its resume state is. + ++swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial +run\]+ + + +Passing an array to swift? +~~~~~~~~~~~~~~~~~~~~~~~~~~ +Arrays can be passed to Swift in one of the following ways: + +. You can write the array to a file and read in in swift using +readData (or readData2). +. Direct the array into a file (possibly with a "here document" which expands the array) and then read the file in Swift with readData() or process it with a Swift app() function? +. You can use @strsplit on a comma separated command line arg and that works well for me. + +Mappers +^^^^^^^^ +SimpleMapper + +---- +$ cat swiftapply.swift +---- + +[java] +source~~~~ +type RFile; +trace("hi 1"); +app (RFile result) RunR (RFile rcall) +{ + RunR @rcall @result; +} +trace("hi 2"); +RFile rcalls[] ; +RFile results[] ; +trace("start"); +foreach c, i in rcalls { + trace("c",i, at c); + trace("r",i, at filename(results[i])); + results[i] = RunR(c); +} +source~~~~ + +---- +$ ls calldir resdir +calldir: +rcall.1.Rdata rcall.2.Rdata rcall.3.Rdata rcall.4.Rdata +resdir: +result.1.Rdata result.2.Rdata result.3.Rdata result.4.Rdata +$ +---- + +Notes: + +how the .'s match +prefix and suffix dont span dirs +intervening pattern must be digits +these digits become the array indices +explain how padding= arg works & helps (including padding=0) +figure out and explain differences between simple_mapper and +filesys_mapper +FIXME: Use the "filesys_mapper" and its "location=" parameter to map the +input data from /home/wilde/bigdata/* + +Abbreviations for SingleFileMapper +Notes: + +within <> you can only have a literal string as in <"filename">, not an +expression. Someday we will fix this to make <> accept a general expression. +you can use @filenames( ) (note: plural) to pull off a list of filenames. + +writeData() + +example here + +---- +$ cat writedata.swift +---- + +[java] +source~~~~ +type file; + +file f <"filea">; +file nf <"filenames">; +nf = writeData(@f); +source~~~~ + +---- +$ swift writedata.swift +Swift svn swift-r3264 (swift modified locally) cog-r2730 (cog modified +locally) +RunID: 20100319-2002-s9vpo0pe +Progress: +Final status: +$ cat filenames +filea$ +---- + +StructuredRegexpMapper +IN PROGRESS This mapper can be used to base the mapped filenames of an output +array on the mapped filenames of an existing array. landuse outputfiles[] +; + +Use the undocumented "structured_regexp_mapper" to name the output +filenames based on the input filenames: + +For example: + +---- +login2$ ls /home/wilde/bigdata/data/sample +h11v04.histogram h11v05.histogram h12v04.histogram h32v08.histogram +h11v04.tif h11v05.tif h12v04.tif h32v08.tif +login2$ + +login2$ cat regexp2.swift +type tif; +type mytype; + +tif images[]; + +mytype of[] ; + +foreach image, i in images { + trace(i, at filename(images)); + trace(i, at filename(of[i])); +} +login2$ + +login1$ swift regexp2.swift +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified +locally) + +RunID: 20100310-1105-4okarq08 +Progress: +SwiftScript trace: 1, output/myfile.h11v04.mytype +SwiftScript trace: 2, home/wilde/bigdata/data/sample/h11v05.tif +SwiftScript trace: 3, home/wilde/bigdata/data/sample/h12v04.tif +SwiftScript trace: 0, output/myfile.h32v08.mytype +SwiftScript trace: 0, home/wilde/bigdata/data/sample/h32v08.tif +SwiftScript trace: 3, output/myfile.h12v04.mytype +SwiftScript trace: 1, home/wilde/bigdata/data/sample/h11v04.tif +SwiftScript trace: 2, output/myfile.h11v05.mytype +Final status: +login1$ +---- + +Coasters +-------- +Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters. +//**Include neat diagrams.** + +Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were: + +[xml] +source~~~~ + +CI-CCR000013 + + + + + + +pbs.aprun +pbs.mpp=true + + +24 +100000 + +100 +100 + +20 +5 +5 +20.00 +10000 +source~~~~ + +The following table briefly describes the elements on the coasters setup: +[width="70%", cols="^3,10", options="header"] +|============================================================================================= +|profile key | brief description +|slots | How many maximum LRM jobs/worker blocks are allowed +|workersPerNode | How many coaster workers to run per execution node +|nodeGranularity | Each worker block uses a number of nodes that is a multiple of this number +|lowOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are 1s long +|highOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are infinitely long +|workersPerNode | How many coaster workers to run per execution node reserve How many seconds to reserve in a block's walltime for starting/shutdown operations +|maxnodes | The maximum number of nodes allowed in a block +|maxtime | The maximum number of walltime allowed for a block coaster service +|jobThrottle |the number of concurrent jobs allowed on a site +|============================================================================================== + +// +//For Beginners +//~~~~~~~~~~~~~~ +//Coasters for beginners. Usage of existing, prebuilt templates. +// +//For Intermediate Users +//~~~~~~~~~~~~~~~~~~~~~~~ +//Coasters for intermediate users. +// +//Using gensites +//^^^^^^^^^^^^^^^ +//Usage of gensites to generate your own sites +//configurations. +// +// +// + +For Advanced Users +~~~~~~~~~~~~~~~~~~ + +//Coasters for advanced users. Getting your hands dirty. + +One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters. + +//How to run Swift under different Coasters configurations +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +// +//Manual +//^^^^^^^ +//Todo +// +//Passive +//^^^^^^^^ +//Todo +// +//Persistent +//^^^^^^^^^^^ +//Todo +// +//Summary of Differences Between different Coaster types +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +//A tabular representations of highlights of different coaster setups +// +// +//Data Management +// + +Coaster providers: local, ssh, pbs +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Settings and examples for different coaster providers mechanisms. + + + +Swift on Diverse Infrastructures +--------------------------------- + +Beagle +~~~~~~ +Swift is now installed on Beagle as a module. Swift supports a Coasters based, +computing environment for Beagle. A detailed Swift documentation is maintained +[[http://www.ci.uchicago.edu/swift/docs/index.php][here]]. To get started +with Swift on Beagle follow the steps outlined below: + +*step 1.* Load the Swift module on Beagle as follows: +module load swift+ + +*step 2.* Create and change to a directory where your Swift related work will +stay. (say, +mkdir swift-lab+, followed by, +cd swift-lab+) + +*step 3.* To get started with a simple example running +/bin/cat+ to read an input file +data.txt+ and write to an output file +f.nnn.out+, copy the folder at +/home/ketan/labs/catsn+ to the above directory. (+cp -r /home/ketan/catsn .+ followed by +cd catsn+). + +*step 4.* In the sites file: +beagle-coaster.xml+, make the following two +changes: *1)* change the path of +workdirectory+ to your preferred location +(say to +/lustre/beagle/$USER/swift-lab/swift.workdir+) and *2)* Change the +project name to your project (+CI-CCR000013+) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs. + +*step 5.* Run the example using following commandline (also found in run.sh): ++swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1+ +. You can further change the value of +-n+ to any arbitrary number to run that +many number of concurrent +cat+ + +*step 6.* Check the output in the generated +outdir+ directory (+ls outdir+) + +Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes +will get fast prioritized execution. Good for small tests + +// +//Intrepid-BG/P +//~~~~~~~~~~~~~ +//Swift on Intrepid-BG/P +// + +PADS +~~~~ +Swift on PADS +To execute your Swift script on the PADS cluster use this command: + +---- +swift -tc.file tc -sites.file pbs.xml modis.swift +---- +where the contents of a simple pbs.xml sites file could be: +[xml] +source~~~~ + + + + fast + 00:05:00 + 10000 + .10 + + /home/you/swiftwork + + +source~~~~ + +OSG +~~~ +This section describes how to get Swift running on the OSG Grid. We will use a +manual coaster setup to get Swift running on OSG. + +.Coaster setup on OSG +The following figure shows an abstract scheme for the manual coasters setup on +OSG. + +image::figures/coaster_setup.png[Coaster setup] + +In the following steps, we will go through the process of manually setting +//Swift on OSG +// + +Bionimbus +~~~~~~~~~ +This section explains a step by step procedure on getting Swift running on the +Bionimbus cloud. We will use the _manual_ _coasters_ configuration on the +Bionimbus cloud. + +**step1.** Connect to the gateway (ssh gatewayx.lac.uic.edu) + +**step2.** Start a virtual machine (euca-run-instances -n 1 -t m1.small +emi-17EB1170) + +**step3.** Start the coaster-service on gateway ++coaster-service -port 1984 -localport 35753 -nosec+ + +**step4.** Start the Swift-script from the gateway using normal Swift commandline + ++swift -config cf -tc.file tc -sites.file sites.xml yourscript.swift -aparam=999+ + +.cf +---- +wrapperlog.always.transfer=true +sitedir.keep=true +execution.retries=1 +lazy.errors=true +status.mode=provider +use.provider.staging=true +provider.staging.pin.swiftfiles=false +foreach.max.threads=100 +provenance.log=true +---- + +.tc +---- +localhost modftdock /home/ketan/swift-labs/bionimbus-coaster-modftdock/app/modftdock.sh null null GLOBUS::maxwalltime="1:00:00" +---- + +(See below for a sample sites.xml for this run) + +**step5.** Connect back to gateway from virtual machines using reverse ssh tunneling as follows: + +.From the gateway prompt + ++ssh -R *:5000:localhost:5000 root at 10.101.8.50 sleep 999+ + +WHERE: +*=network interface, should remain the same on all cases + +localhost=the gateway host, should remain the same + +5000(LEFT OF localhost)=the port number on localhost to listen to **THIS WILL +vary depending upon which port you want to listen to + +5000(RIGHT OF localhost)=the port on target host that you want to forward + +root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will +vary based on what ip you get for your Virtual Machine instance + +#On anywhere as long as provide the correct callback uri: here the +"http://140.221.9.110:42195" is the callback uri of previous ones + +**step6.** Start the worker from the virtual machine ++worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the +coaster service is listening to the workers+ + +.sites.xml for the above run + +[xml] +source~~~~ + + + + passive + + 4 + 10000 + 100 + 100 + 100 + 1 + 10 + 25.00 + 10000 + proxy + + /home/ketan/swift-labs/bionimbus-coaster-modftdock/swift.workdir + + +source~~~~ + +//Magellan +//~~~~~~~~ +//Swift on Magellan +// + +Debugging Swift +--------------- +Swift errors are logged in several places: + +. All text from standard output and standard error produced by running the +swift command +. The .log file from this run. It will be named swiftscript.uniqueID.log +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +. $HOME/.globus/coasters directory on remote machines on which you are +running coasters +. $HOME/.globus/scripts directory on the host on which you run the Swift +command, when swift is submitting to a local scheduler (Condor, PBS, SGE, +Cobalt) +. $HOME/.globus/??? on remote systems that you access via Globus + + +Log Processing +--------------- + +To properly generate log plots, you must enable VDL/Karajan logging. Make sure +log4.properties contains: +---- +log4j.logger.swift=DEBUG +log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG +---- + +Make a basic load plot from Coasters Cpu log lines +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.Generate the log (may set log4j.logger.swift=INFO for this one) +(assuming the log is titled swift-run.log) + +.Convert the log times to Unix time + +---- +./iso-to-secs < swift-run.log > swift-run.time +---- + +.Make the start time file (this contains the earliest timestamp) + +---- +make LOG=swift-run.log start-time.tmp +---- + +or + +---- +extract-start-time swift-run.log > start-time.tmp +---- + +.Normalize the transition times + +---- +./normalise-event-start-time < swift-run.time > swift-run.norm +---- + +.Build up a load data file: + +---- +./cpu-job-load.pl < swift-run.norm > load.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh load.cfg load.eps load.data +---- + +Make a basic job completion plot from Coasters Cpu log lines +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.Same as above, but, build up a completed data file: + +---- +./cpu-job-completed.pl < swift-run.norm > completed.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh completed.cfg completed.eps completed.data +---- + +Make a basic Block allocation plot from Coasters Block log lines +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Same as above, but: + +.Build up a block allocation data file: + +---- +./block-level.pl < swift-run.norm > blocks.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh blocks.{cfg,eps,data} +---- + +Problem Reporting +~~~~~~~~~~~~~~~~~ +When reporting problems to swift-user at ci.uchicago.edu, please attach the +following files and information: + +. tc.data and sites.xml (or whatever you named these files) + +. your .swift source file and any .swift files it imports + +. any external mapper scripts called by your .swift script + +. all text from standard output and standard error produced by running the +swift command + +. The .log file from this run. It will be named swiftscript.uniqueID.log + +. where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. + +. The swift command line you invoked + +. Any swift.properties entries you over-rode ($HOME/.swift/swift.properties, +-config.file argument properties file, any changes to etc/swift.proerties from +your swift distribution) + +. Which swift distribution you are running (release; svn revisions; other +local changes you mave have made or included) + + Added: branches/release-0.92/docs/tutorial/tutorial.html =================================================================== --- branches/release-0.92/docs/tutorial/tutorial.html (rev 0) +++ branches/release-0.92/docs/tutorial/tutorial.html 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,1594 @@ + + + + + +A Swift Tutorial + + + + + +
    +
    +

    1. Abstract

    +
    +

    This is an introductory tutorial on the use of Swift and its programming +language SwiftScript.

    +
    +
    +
    +

    2. Introduction

    +
    +

    This tutorial is intended to introduce new users to the basics of Swift. +It is structured as a series of small exercise/examples which you can +try for yourself as you read along. After the first hello world +example, there are two tracks - the language track (which introduces +features of the SwiftScript language) and the runtime track (which +introduces features of the Swift runtime environment, such as running +jobs on different sites).

    +

    For information on getting an installation of Swift running, consult the +Swift Quickstart Guide http://www.ci.uchicago.edu/swift/guides/quickstartguide.php, and +return to this document when you have successfully run the test +SwiftScript program mentioned there.

    +

    There is also a Swift User’s Guide +http://www.ci.uchicago.edu/swift/guides/userguide.php which contains +more detailed reference material on topics covered in this manual. All +of the programs included in this tutorial can be found in your Swift +distribution in the examples/swift directory.

    +
    +
    +
    +

    3. Hello World

    +
    +

    The first example program, first.swift, outputs a hello world message +into a file called hello.txt.

    +
    +
    +
    first.swift
    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting() {
    +    echo "Hello, world!" stdout=@filename(t);
    +}
    +
    +messagefile outfile <"hello.txt">;
    +
    +outfile = greeting();
    +
    +

    We can run this program as follows:

    +
    +
    +
    $ cd examples/swift/
    +$ swift first.swift
    +Swift svn swift-r3334 (swift modified locally) cog-r2752
    +
    +RunID: 20100526-1925-8zjupq1b
    +Progress:
    +Final status:  Finished successfully:1
    +$ cat hello.txt
    +Hello, world!
    +

    The basic structure of this program is a type definition, an +application procedure definition, a variable definition and then a +call to the procedure:

    +
    +
    +
    type messagefile;
    +

    First we define a new type, called messagefile. In this example, we will +use this messagefile type as the type for our output message.

    +

    All data in SwiftScript must be typed, whether it is stored in memory or +on disk. This example defines a very simple type. Later on we will see +more complex type examples.

    +
    +
    +
    app (messagefile t) greeting() {
    +    echo "Hello, world!" stdout=@filename(t);
    +}
    +

    Next we define a procedure called greeting. This procedure will write +out the "hello world" message to a file.

    +

    To achieve this, it executes the unix utility echo with a parameter +"Hello, world!" and directs the standard output into the output file.

    +

    The actual file to use is specified by the return parameter, t.

    +

    messagefile outfile <"hello.txt">;

    +

    Here we define a variable called outfile. The type of this variable is +messagefile, and we specify that the contents of this variable will be +stored on disk in a file called hello.txt

    +

    outfile = greeting();

    +

    Now we call the greeting procedure, with its output going to the outfile +variable and therefore to hello.txt on disk.

    +

    Over the following exercises, we’ll extend this simple hello world +program to demonstrate various features of Swift.

    +
    +
    +
    +

    4. Language features

    +
    +
    +

    4.1. Parameters

    +

    Procedures can have parameters. Input parameters specify inputs to the +procedure and output parameters specify outputs. Our helloworld greeting +procedure already uses an output parameter, t, which indicates where the +greeting output will go. In this section, we will add an input parameter +to the greeting function.

    +

    The code changes from first.swift are highlighted below.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +messagefile outfile <"hello2.txt">;
    +
    +outfile = greeting("hello world");
    +

    We have modified the signature of the greeting procedure to indicate +that it takes a single parameter, s, of type string.

    +

    We have modified the invocation of the echo utility so that it takes +the value of s as a parameter, instead of the string literal "Hello, +world!".

    +

    We have modified the output file definition to point to a different file +on disk.

    +

    We have modified the invocation of greeting so that a greeting string is +supplied.

    +

    The code for this section can be found in parameter.swift. It can be +invoked using the swift command, with output appearing in hello2.txt:

    +
    +
    +
    $ swift parameter.swift
    +

    Now that we can choose our greeting text, we can call the same procedure +with different parameters to generate several output files with +different greetings. The code is in manyparam.swift and can be run as +before using the swift command.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +messagefile english <"english.txt">;
    +messagefile french <"francais.txt">;
    +english = greeting("hello");
    +french = greeting("bonjour");
    +
    +messagefile japanese <"nihongo.txt">;
    +japanese = greeting("konnichiwa");
    +

    Note that we can intermingle definitions of variables with invocations +of procedures.

    +

    When this program has been run, there should be three new files in the +working directory (english.txt, francais.txt and nihongo.txt) each +containing a greeting in a different language.

    +

    In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified - see Named and Optional Parameters.

    +
    +
    +

    4.2. Adding another application

    +

    Now we’ll define a new application procedure. The procedure we define +will capitalise all the words in the input file.

    +

    To do this, we’ll use the unix tr (translate) utility. Here is an +example of using tr on the unix command line, not using Swift:

    +
    +
    +
    $ echo hello | tr '[a-z]' '[A-Z]'
    +HELLO
    +
    There are several steps
      +
    • +

      +transformation catalog +

      +
    • +
    • +

      +application block +

      +
    • +
    +

    First we need to modify the transformation catalog to define a logical +transformation for the tc utility. The transformation catalog can be +found in etc/tc.data. There are already several entries specifying +where programs can be found. Add a new line to the file, specifying +where tr can be found (usually in /usr/bin/tr but it may differ on +your system), like this:

    +
    +
    +
    localhost       tr      /usr/bin/tr     INSTALLED       INTEL32::LINUX  null
    +

    For now, ignore all of the fields except the second and the third. The +second field tr specifies a logical application name and the third +specifies the location of the application executable.

    +

    Now that we have defined where to find tr, we can use it in SwiftScript.

    +

    We can define a new procedure, capitalise, which calls tr.

    +
    +
    +
    (messagefile o) capitalise(messagefile i) {
    +    app {
    +        tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    +    }
    +}
    +

    We can call capitalise like this:

    +
    +
    +
    messagefile final <"capitals.txt">;
    +final = capitalise(hellofile);
    +

    So a full program based on the first exercise might look like this:

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +app (messagefile o) capitalise(messagefile i) {
    +    tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    +}
    +
    +messagefile hellofile <"hello.txt">;
    +messagefile final <"capitals.txt">;
    +
    +hellofile = greeting("hello from Swift");
    +final = capitalise(hellofile);
    +

    We can use the swift command to run it like this.

    +
    +
    +
    $ swift second_procedure.swift
    +...
    +$ cat capitals.txt
    +HELLO FROM SWIFT
    +
    +
    +

    4.3. Anonymous files

    +

    In the previous section, the file greeting.txt is used only to store +an intermediate result. We don’t really care about which name is used +for the file, and we can let Swift choose the name.

    +

    To do that, omit the mapping entirely when declaring outfile:

    +
    +
    +
    messagefile outfile;
    +

    Swift will choose a filename, which in the present version will be in a +subdirectory called _concurrent.

    +
    +
    +

    4.4. Datatypes

    +

    All data in variables and files has a data type. So far, we’ve seen two +types:

    +
      +
    • +

      +string - this is a built-in type for storing strings of text in + memory, much like in other programming languages +

      +
    • +
    • +

      +messagefile - this is a user-defined type used to mark files as + containing messages +

      +
    • +
    +

    SwiftScript has the additional built-in types: boolean, integer and +float that function much like their counterparts in other programming +languages.

    +

    It is also possible to create user defined types with more structure, +for example:

    +
    +
    +
    type details {
    +    string name;
    +    int pies;
    +}
    +

    Each element of the structured type can be accessed using a . like this:

    +
    +
    +
    person.name = "john";
    +

    The following complete program, types.swift, outputs a greeting using a +user-defined structure type to hold parameters for the message:

    +
    +
    +
    type messagefile;
    +
    +type details {
    +    string name;
    +    int pies;
    +}
    +
    +app (messagefile t) greeting (details d) {
    +    echo "Hello. Your name is" d.name "and you have eaten" d.pies "pies." stdout=@filename(t);
    +}
    +
    +details person;
    +
    +person.name = "John";
    +person.pies = 3;
    +
    +messagefile outfile <"q15.txt">;
    +
    +outfile = greeting(person);
    +

    Structured types can be comprised of marker types for files. See the +later section on mappers for more information about this.

    +
    +
    +

    4.5. Arrays

    +

    We can define arrays using the [] suffix in a variable declaration:

    +
    +
    +
    messagefile m[];
    +

    This program, q5.swift, will declare an array of message files.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s[]) {
    +     echo s[0] s[1] s[2] stdout=@filename(t);
    +}
    +
    +messagefile outfile <"q5out.txt">;
    +
    +string words[] = ["how","are","you"];
    +
    +outfile = greeting(words);
    +

    Observe that the type of the parameter to greeting is now an array of +strings, string s[], instead of a single string, string s, that +elements of the array can be referenced numerically, for example s[0], +and that the array is initialised using an array literal, +["how","are","you"].

    +
    +
    +

    4.6. Mappers

    +

    A significant difference between SwiftScript and other languages is that +data can be referred to on disk through variables in a very similar +fashion to data in memory. For example, in the above examples we have +seen a variable definition like this:

    +
    +
    +
    messagefile outfile <"q13greeting.txt">;
    +

    This means that outfile is a dataset variable, which is mapped to a +file on disk called g13greeting.txt. This variable can be assigned to +using = in a similar fashion to an in-memory variable. We can say that +outfile is mapped onto the disk file q13greeting.txt by a mapper.

    +

    There are various ways of mapping in SwiftScript. Two forms have already +been seen in this tutorial. Later exercises will introduce more forms.

    +

    The two forms of mapping seen so far are:

    +

    simple named mapping - the name of the file that a variable is mapped to +is explictly listed. Like this:

    +
    +
    +
    messagefile outfile <"greeting.txt">;
    +

    This is useful when you want to explicitly name input and output files +for your program. For example, outfile in exercise HELLOWORLD.

    +

    anonymous mapping - no name is specified in the source code. A name is +automatically generated for the file. This is useful for intermediate +files that are only referenced through SwiftScript, such as outfile in +exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by +ommitting any mapper definition, like this:

    +
    +
    +
    messagefile outfile;
    +

    Later exercises will introduce other ways of mapping from disk files to +SwiftScript variables.

    +

    TODO: introduce @v syntax.

    +
    +

    4.6.1. The Regexp Mapper

    +

    In this exercise, we introduce the regexp mapper. This mapper +transforms a string expression using a regular expression, and uses the +result of that transformation as the filename to map.

    +

    regexp.swift demonstrates the use of this by placing output into a +file that is based on the name of the input file: our input file is +mapped to the inputfile variable using the simple named mapper, and then +we use the regular expression mapper to map the output file. Then we use +the countwords() procedure to count the works in the input file and +store the result in the output file. In order for the countwords() +procedure to work correctly, add the wc utility (usually found in +/usr/bin/wc) to tc.data.

    +

    The important bit of regexp.swift is:

    +
    +
    +
    messagefile inputfile <"q16.txt">;
    +
    +countfile c <regexp_mapper;
    +             source=@inputfile,
    +             match="(.*)txt",
    +             transform="\\1count"
    +            >;
    +
    +
    +

    4.6.2. fixed_array_mapper

    +

    The fixed array mapper maps a list of files into an array - each +element of the array is mapped into one file in the specified directory. +See fixedarray.swift.

    +
    +
    +
    type messagefile {}
    +type countfile {}
    +
    +(countfile t) countwords (messagefile f) {
    +    app {
    +        wc "-w" @filename(f) stdout=@filename(t);
    +    }
    +}
    +
    +string inputNames = "one.txt two.txt three.txt";
    +string outputNames = "one.count two.count three.count";
    +
    +messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    +countfile outputfiles[] <fixed_array_mapper;files=outputNames>;
    +
    +outputfiles[0] = countwords(inputfiles[0]);
    +outputfiles[1] = countwords(inputfiles[1]);
    +outputfiles[2] = countwords(inputfiles[2]);
    +
    +
    +
    +

    4.7. foreach

    +

    SwiftScript provides a control structure, foreach, to operate on each +element of an array.

    +

    In this example, we will run the previous word counting example over +each file in an array without having to explicitly list the array +elements. The source code for this example is in foreach.swift. The +three input files: one.txt, two.txt and three.txt are supplied. +After you have run the workflow, you should see that there are three +output files: one.count, two.count and three.count, each +containing the word count for the corresponding input file. We combine +the use of the fixed_array_mapper and the regexp_mapper.

    +
    +
    +
    type messagefile {}
    +type countfile {}
    +
    +(countfile t) countwords (messagefile f) {
    +    app {
    +        wc "-w" @filename(f) stdout=@filename(t);
    +    }
    +}
    +
    +string inputNames = "one.txt two.txt three.txt";
    +
    +messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    +
    +
    +foreach f in inputfiles {
    +  countfile c<regexp_mapper;
    +            source=@f,
    +            match="(.*)txt",
    +            transform="\\1count">;
    +  c = countwords(f);
    +}
    +
    +
    +

    4.8. If

    +

    Decisions can be made using if, like this:

    +
    +
    +
    if(morning) {
    +  outfile = greeting("good morning");
    +} else {
    +  outfile = greeting("good afternoon");
    +}
    +

    if.swift contains a simple example of this. Compile and run if.swift +and see that it outputs "good morning". Changing the morning variable +from true to false will cause the program to output "good afternoon".

    +
    +
    +

    4.9. Sequential iteration

    +

    A development version of Swift after 0.2 (revision 1230) introduces a +sequential iteration construct.

    +

    The following example demonstrates a simple application: each step of +the iteration is a string representation of the byte count of the +previous step’s output, with iteration terminating when the byte count +reaches zero.

    +

    Here’s the program:

    +
    +
    +
    type counterfile;
    +
    +app (counterfile t) echo(string m) {
    +    echo m stdout=@filename(t);
    +}
    +
    +app (counterfile t) countstep(counterfile i) {
    +    wcl @filename(i) @filename(t);
    +}
    +
    +counterfile a[]  <simple_mapper;prefix="foldout">;
    +
    +a[0] = echo("793578934574893");
    +
    +iterate v {
    +  a[v+1] = countstep(a[v]);
    + trace("extract int value ",@extractint(a[v+1]));
    +} until (@extractint(a[v+1]) <= 1);
    +

    echo is the standard unix echo.

    +

    wcl is our application code - it counts the number of bytes in the one +file and writes that count out to another, like this:

    +
    +
    +
    $ cat ../wcl
    +#!/bin/bash
    +echo -n $(wc -c < $1) > $2
    +
    +$ echo -n hello > a
    +$ wcl a b
    +$ cat b
    +5
    +

    Install the above wcl script somewhere and add a transformation catalog +entry for it. Then run the example program like this:

    +
    +
    +
    $ swift iterate.swift
    +Swift svn swift-r3334 cog-r2752
    +
    +RunID: 20100526-2259-gtlz8zf4
    +Progress:
    +SwiftScript trace: extract int value , 16.0
    +SwiftScript trace: extract int value , 2.0
    +SwiftScript trace: extract int value , 1.0
    +Final status:  Finished successfully:4
    +
    +$ ls foldout*
    +foldout0000  foldout0001  foldout0002  foldout0003
    +
    +
    +
    +
    +

    5. Runtime features

    +
    +
    +

    5.1. Visualising the workflow as a graph

    +

    When running a workflow, its possible to generate a provenance graph at +the same time:

    +
    +
    +
    $ swift -pgraph graph.dot first.swift
    +$ dot -ograph.png -Tpng graph.dot
    +

    graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org.

    +
    +
    +

    5.2. Running on a remote site

    +

    As configured by default, all jobs are run locally. In the previous +examples, we’ve invoked echo and tr executables from our SwiftScript +program. These have been run on the local system (the same computer on +which you ran swift). We can also make our computations run on a +remote resource.

    +
    + + + +
    +Warning +This example is necessarily more vague than previous examples, +because its requires access to remote resources. You should ensure that +you can submit a job using the globus-job-run (or globusrun-ws?) +command(s).
    +
    +

    We do not need to modify any SwiftScript code to run on another +resource. Instead, we must modify another catalog, the site catalog. +This catalog provides details of the location that applications will be +run, with the default settings referring to the local machine. We will +modify it to refer to a remote resource - the UC Teraport cluster. If +you are not a UC Teraport user, you should use details of a different +resource that you do have access to.

    +

    The site catalog is located in etc/sites.xml and is a relatively +straightforward XML format file. We must modify each of the following +three settings: gridftp (which indicates how and where data can be +transferred to the remote resource), jobmanager (which indicates how +applications can be run on the remote resource) and workdirectory (which +indicates where working storage can be found on the remote resource).

    +
    +
    +

    5.3. Writing a mapper

    +

    This section will introduce writing a custom mapper so that Swift is +able to access data files laid out in application-specific ways.

    +

    An application-specific mapper must take the form of a Java class that +implements the Mapper +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/Mapper.html +interface.

    +

    Usually you don’t need to implement this interface directly, because +Swift provides a number of more concrete classes with some functionality +already implemented.

    +

    The hierarchy of helper classes is:

    + +

    This is the abstract interface for mappers in Swift. You must +implement methods to provide access to mapper properties, to map from a +SwiftScript dataset path (such as foo[1].bar) to a file name, to check +whether a file exists. None of the default Swift mappers implement this +interface directly - instead they use one of the following helper classes.

    + +

    This provides helper methods to manage mapper properties and to handle +existance checking. Examples of mappers which use this class are: +Array Mapper, +CSV Mapper, +Fixed Array Mapper, +Regexp Mapper, +and Single File Mapper.

    +

    AbstractFileMapper +This provides a helper class for mappers which select files based on +selecting files from a directory listing. It is necessary to write some +helper methods that are different from the above mapper methods. +Examples of mappers which use this class are: +simple_mapper, +filesys_mapper, +and the (undocumented) StructuredRegularExpressionMapper.

    +

    In general, to write a mapper, choose either the AbstractMapper or the +AbstractFileMapper and extend those. If your mapper will generally +select the files it returns based on a directory listing and will +convert paths to filenames using some regular conversion (for example, +in the way that simple_mapper maps files in a directory that match a +particular pattern), then you should probably use the +AbstractFileMapper. If your mapper will produce a list of files in some +other way (for example, in the way that csv_mapper maps based on +filenames given in a CSV file rather than looking at which files are in +a directory), then you should probably use the AbstractMapper.

    +
    +
    +

    5.4. Writing a very basic mapper

    +

    In this section, we will write a very basic (almost useless) mapper that +will map a SwiftScript dataset into a hardcoded file called +myfile.txt, like this:

    +
    +
    +
    Swift variable                            Filename
    +
    +
    +
    +
    var   <----------------------------->    myfile.txt
    +
    +

    We should be able to use the mapper we write in a SwiftScript program +like this:

    +
    +
    +
    type file;
    +file f <my_first_mapper;>;
    +

    First we must choose a base class - AbstractMapper or +AbstractFileMapper. We aren’t going to use a directory listing to decide +on our mapping - we are getting the mapping from some other source (in +fact, it will be hard coded). So we will use AbstractMapper.

    +

    So now onto the source code. We must define a subclass of AbstractMapper +and implement several mapper methods: isStatic, existing, and map. These +methods are documented in the javadoc for the Mapper interface.

    +

    Here is the code implementing this mapper. Put this in your source +vdsk directory, make a directory src/tutorial/|and put this file in +src/tutorial/MyFirstMapper.java.

    +
    +
    +
    package tutorial;
    +
    +import java.util.Arrays;
    +import java.util.Collection;
    +import java.util.Collections;
    +
    +import org.griphyn.vdl.mapping.AbsFile;
    +import org.griphyn.vdl.mapping.AbstractMapper;
    +import org.griphyn.vdl.mapping.Path;
    +import org.griphyn.vdl.mapping.PhysicalFormat;
    +
    +public class MyFirstMapper extends AbstractMapper {
    +
    +  AbsFile myfile = new AbsFile("myfile.txt");
    +
    +  public boolean isStatic() {
    +    return false;
    +  }
    +
    +  public Collection existing() {
    +    if (myfile.exists())
    +      return Arrays.asList(new Path[] {Path.EMPTY_PATH});
    +    else
    +      return Collections.EMPTY_LIST;
    +  }
    +
    +  public PhysicalFormat map(Path p) {
    +    if(p.equals(Path.EMPTY_PATH))
    +      return myfile;
    +    else
    +      return null;
    +  }
    +}
    +

    Now we need to inform the Swift engine about the existence of this +mapper. We do that by editing the MapperFactory class definition, in +src/org/griphyn/vdl/mapping/MapperFactory.java and adding a +registerMapper call alongside the existing registerMapper calls, like this:

    +
    +
    +
    registerMapper("my_first_mapper", tutorial.MyFirstMapper.class);
    +

    The first parameter is the name of the mapper that will be used in +SwiftScript program. The second parameter is the new Mapper class that +we just wrote.

    +

    Now rebuild Swift using the "ant redist" target.

    +

    This new Swift build will be aware of your new mapper. We can test it +out with a hello world program:

    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting() {
    +    app {
    +        echo "hello" stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile <my_first_mapper;>;
    +
    +outfile = greeting();
    +

    Run this program, and hopefully you will find the "hello" string has +been output into the hard coded output file myfile.txt:

    +
    +
    +
    $ cat myfile.txt
    +hello
    +

    So that’s a first very simple mapper implemented. Compare the source +code to the single_file_mapper in +SingleFileMapper.java. +There is not much more code to the single_file_mapper - mostly code to +deal with the file parameter.

    +
    +
    +

    5.5. Starting and restarting

    +

    Now we’re going to try out the restart capabilities of Swift. We will +make a workflow that will deliberately fail, and then we will fix the +problem so that Swift can continue with the workflow.

    +

    First we have the program in working form, restart.swift.

    +
    +
    +
    type file;
    +
    +app (file f) touch() {
    +    touch @f;
    +}
    +
    +app (file f) processL(file inp) {
    +    echo "processL" stdout=@f;
    +}
    +
    +app (file f) processR(file inp) {
    +    broken "process" stdout=@f;
    +}
    +
    +app (file f) join(file left, file right) {
    +    echo "join" @left @right stdout=@f;
    +}
    +
    +file f = touch();
    +
    +file g = processL(f);
    +file h = processR(f);
    +
    +file i = join(g,h);
    +

    We must define some transformation catalog entries:

    +
    +
    +
    localhost   touch   /usr/bin/touch  INSTALLED   INTEL32::LINUX  null
    +localhost   broken  /bin/true   INSTALLED   INTEL32::LINUX  null
    +

    Now we can run the program:

    +
    +
    +
    $ swift restart.swift
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1119-3kgzzi15
    +Progress:
    +Final status:  Finished successfully:4
    +

    Four jobs run - touch, echo, broken and a final echo. (note that broken +isn’t actually broken yet).

    +

    Now we will break the broken job and see what happens. Replace the +definition in tc.data for broken with this:

    +
    +
    +
    localhost    broken     /bin/false   INSTALLED       INTEL32::LINUX  null
    +

    Now when we run the workflow, the broken task fails:

    +
    +
    +
    $ swift restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1121-tssdcljg
    +Progress:
    +Progress:  Stage in:1  Finished successfully:2
    +Execution failed:
    +    Exception in broken:
    +Arguments: [process]
    +Host: localhost
    +Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj
    +stderr.txt:
    +stdout.txt:
    +

    From the output we can see that touch and the first echo completed, but +then broken failed and so swift did not attempt to execute the final echo.

    +

    There will be a restart log with the same name as the RunID:

    +
    +
    +
    $ ls *20100526-1121-tssdcljg*rlog
    +restart-20100526-1121-tssdcljg.0.rlog
    +

    This restart log contains enough information for swift to know which +parts of the workflow were executed successfully.

    +

    We can try to rerun it immediately, like this:

    +
    +
    +
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1125-7yx0zi6d
    +Progress:
    +Execution failed:
    +    Exception in broken:
    +Arguments: [process]
    +Host: localhost
    +Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj
    +stderr.txt:
    +stdout.txt:
    +
    +----
    +
    +Caused by:
    +    Exit code 1
    +

    Swift tried to resume the workflow by executing "broken" again. It did +not try to run the touch or first echo jobs, because the restart log +says that they do not need to be executed again.

    +

    Broken failed again, leaving the original restart log in place.

    +

    Now we will fix the problem with "broken" by restoring the original +tc.data line that works.

    +

    Remove the existing "broken" line and replace it with the successful +tc.data entry above:

    +
    +
    +
    localhost       broken          /bin/true   INSTALLED       INTEL32::LINUX  null
    +

    Now run again:

    +
    +
    +
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1128-a2gfuxhg
    +Progress:
    +Final status:  Initializing:2  Finished successfully:2
    +

    Swift tries to run "broken" again. This time it works, and so Swift +continues on to execute the final piece of the workflow as if nothing +had ever gone wrong.

    +
    +
    +
    +
    +

    6. bits

    +
    +
    +

    6.1. Named and optional parameters

    +

    anchor:named_parameters +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified:

    +
    +
    +
    (messagefile t) greeting (string s="hello") {
    +    app {
    +        echo s stdout=@filename(t);
    +    }
    +}
    +

    When we invoke the procedure, we can specify values for the parameters +by name. The following code can be found in q21.swift.

    +
    +
    +
    french = greeting(s="bonjour");
    +

    or we can let the default value apply:

    +
    +
    +
    english = greeting();
    +
    +
    +
    +
    +

    + + + Added: branches/release-0.92/docs/tutorial/tutorial.pdf =================================================================== --- branches/release-0.92/docs/tutorial/tutorial.pdf (rev 0) +++ branches/release-0.92/docs/tutorial/tutorial.pdf 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,4213 @@ +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (section.1) >> +endobj +8 0 obj +(Introduction) +endobj +9 0 obj +<< /S /GoTo /D (section.2) >> +endobj +12 0 obj +(Hello World) +endobj +13 0 obj +<< /S /GoTo /D (section.3) >> +endobj +16 0 obj +(Language features) +endobj +17 0 obj +<< /S /GoTo /D (subsection.3.1) >> +endobj +20 0 obj +(Parameters) +endobj +21 0 obj +<< /S /GoTo /D (subsection.3.2) >> +endobj +24 0 obj +(Adding another application) +endobj +25 0 obj +<< /S /GoTo /D (subsection.3.3) >> +endobj +28 0 obj +(Anonymous files) +endobj +29 0 obj +<< /S /GoTo /D (subsection.3.4) >> +endobj +32 0 obj +(Datatypes) +endobj +33 0 obj +<< /S /GoTo /D (subsection.3.5) >> +endobj +36 0 obj +(Arrays) +endobj +37 0 obj +<< /S /GoTo /D (subsection.3.6) >> +endobj +40 0 obj +(Mappers) +endobj +41 0 obj +<< /S /GoTo /D (subsubsection.3.6.1) >> +endobj +44 0 obj +(The Regexp Mapper) +endobj +45 0 obj +<< /S /GoTo /D (subsubsection.3.6.2) >> +endobj +48 0 obj +(fixed\137array\137mapper) +endobj +49 0 obj +<< /S /GoTo /D (subsection.3.7) >> +endobj +52 0 obj +(foreach) +endobj +53 0 obj +<< /S /GoTo /D (subsection.3.8) >> +endobj +56 0 obj +(If) +endobj +57 0 obj +<< /S /GoTo /D (subsection.3.9) >> +endobj +60 0 obj +(Sequential iteration) +endobj +61 0 obj +<< /S /GoTo /D (section.4) >> +endobj +64 0 obj +(Runtime features) +endobj +65 0 obj +<< /S /GoTo /D (subsection.4.1) >> +endobj +68 0 obj +(Visualising the workflow as a graph) +endobj +69 0 obj +<< /S /GoTo /D (subsection.4.2) >> +endobj +72 0 obj +(Running on a remote site) +endobj +73 0 obj +<< /S /GoTo /D (subsection.4.3) >> +endobj +76 0 obj +(Writing a mapper) +endobj +77 0 obj +<< /S /GoTo /D (subsection.4.4) >> +endobj +80 0 obj +(Writing a very basic mapper) +endobj +81 0 obj +<< /S /GoTo /D (subsection.4.5) >> +endobj +84 0 obj +(Starting and restarting) +endobj +85 0 obj +<< /S /GoTo /D (section.5) >> +endobj +88 0 obj +(bits) +endobj +89 0 obj +<< /S /GoTo /D (subsection.5.1) >> +endobj +92 0 obj +(Named and optional parameters) +endobj +93 0 obj +<< /S /GoTo /D [94 0 R /FitH ] >> +endobj +96 0 obj << +/Length 292 +/Filter /FlateDecode +>> +stream +x??Q?JA ??W??=l?d???QA???{+=????"J??o?v??'2??{//??f???K?/???{??N?v?S?]n4??e??m 3?j,?? t????iY?lq?7?c?5?????G??mV??Y???4??U$?Z"4U???d????FO??r,???*?????NDp?GD#?%/S??g???8vY???j? ?&w'???H????M????%9???i??558????+????]cq??4?(b ???(?r[E??jZq?+??=-???m'???S?2endstream +endobj +94 0 obj << +/Type /Page +/Contents 96 0 R +/Resources 95 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +97 0 obj << +/D [94 0 R /XYZ 56.6929 815.7613 null] +>> endobj +104 0 obj << +/D [94 0 R /XYZ 56.6929 759.0684 null] +>> endobj +95 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +111 0 obj << +/Length 1869 +/Filter /FlateDecode +>> +stream +x??[?r?F??+p$??????$?X????\?H??pQ 0??> +1@C?eP? +-???????8d??X?4????2E?f"??Lhv??4a +f?A???????q????6??hCUf?!?q?]/^O???\?????mY??z&?t_??U????~QXf!?U?4a??l?qJ?C????N~?nYyR?1"??&???lO?bB?t?e?J?t,?L? +??o???????].??V +?BH????3??cLU?????(???1??m???||(?4?I]?S?5??} + ?54$?ZQ`?9??N?o?b??t???????K?qx<*T?S?-*I?)??r??6?((??u??uhQUn?????z????jf?tW?q-1???? +*I??? ??Z(F????Zx?U?M-~??w??nY??v????F??`??Dp?;????$)_???&5????]@?e? =?????y(9?J????i^??e?,?"K??B?x??I???E:w??Ef? +EZ???VG?z??N4XF??????!N??=?L`?Uu^ +;?x??!%?V&? -???n??+? +????I]?g??hP  ?J?rvJb???? ???5???????J?a?a?????D??,???????A????s&?~????\V{??????????o?-?< ???nP ??iB,1O(??R?c? +??6*?V5J?K??=W??*?????A^??{?m?X |?x?W+????W??P???z???? +y??}R?c? +?6*??P8???]?t?p????? +7?R?vW,????RGY? B??tN?]?? Fi~????G_?-?bU-7???2^?8?J$v-???ml??6re??0l???H?(,??4??GMqK\dL?_PE?????^>?(?9M|???j???2W???mY]?9?V????t?U???Y?.??G%X1c?B??????4???? ?^??.@??Rsn?uJ?{'E?.DU?P?NJ???}?;)/?`??9WR?"?;???bxT???[H?]I??U?????? u(H{+??????a??W????B?0ct?+??m?????_??7?Z???]??GkT. ????> endobj +113 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 706.3558 126.6998 715.332] +/Subtype /Link +/A << /S /GoTo /D (section.1) >> +>> endobj +117 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 678.4604 124.7471 687.4366] +/Subtype /Link +/A << /S /GoTo /D (section.2) >> +>> endobj +118 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 648.6621 151.3174 659.5412] +/Subtype /Link +/A << /S /GoTo /D (section.3) >> +>> endobj +119 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 632.6522 139.6612 641.4988] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.1) >> +>> endobj +120 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 612.6622 204.5674 623.5661] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.2) >> +>> endobj +121 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 594.7294 163.2031 605.6333] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.3) >> +>> endobj +122 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 576.7967 135.3873 587.7006] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.4) >> +>> endobj +123 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 558.8639 122.6553 569.7678] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.5) >> +>> endobj +124 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 540.9311 130.4061 551.8351] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.6) >> +>> endobj +125 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 522.9984 209.0213 533.9023] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.3.6.1) >> +>> endobj +126 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 505.0656 207.5069 515.9696] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.3.6.2) >> +>> endobj +127 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 489.1902 125.415 498.0368] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.7) >> +>> endobj +128 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 471.2574 102.1823 480.1041] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.8) >> +>> endobj +129 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 451.2674 173.3045 462.1713] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.9) >> +>> endobj +130 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 425.4093 146.326 434.3856] +/Subtype /Link +/A << /S /GoTo /D (section.4) >> +>> endobj +131 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 405.4392 238.2109 416.3432] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1) >> +>> endobj +132 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 387.5065 195.7206 398.4104] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.2) >> +>> endobj +133 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 369.5737 165.823 380.4777] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.3) >> +>> endobj +134 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 351.641 208.8313 362.5449] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.4) >> +>> endobj +135 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 333.7082 184.094 344.6122] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.5) >> +>> endobj +136 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 307.8502 88.1347 316.8264] +/Subtype /Link +/A << /S /GoTo /D (section.5) >> +>> endobj +137 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 287.8801 222.5397 298.784] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.1) >> +>> endobj +112 0 obj << +/D [110 0 R /XYZ 56.6929 815.7613 null] +>> endobj +109 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +140 0 obj << +/Length 388 +/Filter /FlateDecode +>> +stream +x??R?N?0??7?C???}#H???? +1???Hm?+???6 ?D?P???????3??{?b"1O?[???{??FL1??s?M???X??x??\?7??f?:??\=????a=[|6?4????l????6???!????????Cb?P?0?#M?4??-dM??Z6? ?C==kXe J??H???? ?V1??z3?l?B=??]?????0?c?d??Y??G?F?Fr!g? i?????\a$#~`??^v????O?V??]?$??` ?\_r?Mx???9?4???H?" ?,?QU????QN???6??j????V?4?c?????:??Xt?_??jW#k?y??????????M????~=;?X??{???>O??K?h????|G??q??r?rendstream +endobj +139 0 obj << +/Type /Page +/Contents 140 0 R +/Resources 138 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +141 0 obj << +/D [139 0 R /XYZ 56.6929 815.7613 null] +>> endobj +138 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +144 0 obj << +/Length 4447 +/Filter /FlateDecode +>> +stream +x??][??8r~??? ? +????M?A&??d6y???`v?A?Vw{?m??2='???????(?>?=?K?KT??#Y?*RT5?Q??fRU?zf?$Z11[>???{x??;?i?h??????n#??&??j??n?8Q????????????_?,??????wGw??????q?_7?????-pa3\?@.?? ????ZJn?0??????0?????}???!?A???????l???;J????3?P?????I?B?P?y?????9???"5r?c?B??D?|??J?????j?qwr?f?.?????n??4?C??sw??Ws?6+?h???C++??_?[_?v^??R?????r???+?Y? E??f?su?w??jd???0*k_?????^-P???m?????A?v6?o|[??f{j???????5B????J?????`?Yw???mpl??@?? &?z|??????I?l?+i??^%?????~?7??|q?? +bW???????????????s?p?:%???/???????/??x?u???N?;???????=`?I??I-??? +2*%?q??~>6????{??V*?4?@}8?|???:????????z??m??d{/:??;?A?????yZ???a?????8?+??et??????<[?Xc???:????9?????????7J??rM`X???~G??????o^?5??????c3????????4lSL?` +L?????j?%K??rC48???`l@???????V????i?=????{[E +?????t%??0;w????q +?< +(?g?????i???7??)?kW????n???5L?????,??o%l6??+i\A??t?????F???????8?\k????????[%??????U ?? +3?I???sT????E??? t}??VR??? ????]?U ????|???B% +?H)?? +M?? 0Q? :Xm??:??l???????I ?:Z????f{j6?y?/6???(???rsZM1?;!>_s????????? L?S~8???[N!8z??7?nVI?????/??%??h5h*???&T????K? n#?S?mVd n "f(??|?????(p??1?T??;4?W??u^1>?????lw:>???K7?'Dbp??'Dfo?j?I?py??????%x?v??G????/R?:]-???_-????RUWDY???j P???.g???H????U???U +O?9I?2??:?,:???] C#t?!v?(?+????&$?b\?Vj(? 0?i?~??? ?(?? ??3????????6?h?T???|LE4?Ut??]??PWc?;?? ?h????! F?I?Y??'??M?????`??_????~?.~?! J5p?t a???J???@ec??OIcp: +=????D??.B3-?*A d=h???A$???t???E?*HO?????????U??Z???Z????M +M????p?4O??Bkb?0?.?4??D??:ue?&Lb??Q? ??T???^l?2m???G?Ih???O???Kj0?h??????HK??aa?FM?f??q??% _???o[?95\??????T???N???(*J???'????????R`*8+G)??,?C????$??EWD??? $????y???y?"0?n M"??sNZ?O???????????6???????aW?'9?+O?+??^U?<;@_ql????????}0??|????ug9??u?? ???O?T5x????4?? ??s7?h?m?W??9??????? d?P*?{9??C????6?>??????)???`x???y?????? ZWz\?%????p|H'>?+?e??????,???????Q???Ok+?wo?o???#??? ???? +?????84?.????????@???Lv?????[3,???sdUX????????Ld?-"UA????M? +-???'t????xG'??G???{?U?v??`G? ??RT?R???????3?????;??5=Y\??tq??9?Br?? ?????y??????m??TYh?HU?r??9???K O^|4????]M?? +?p??nFSBfi(? +C7?L???D@???H????to0???Q?X_-??oi:#??5?*?S??W???q??e3?)???V0?,??.???x??hL:???T?)????h3{B3G|?%??O?N??7??JD??k?*?a??a??3 ???G6=6^?????'?{/c????\?? +????96!??+?g????SH???u%?g???~~h1???????? ?:&I%19(????z??????^?a +?n?????/L???6?)???????q???[_??????; ??Bw????L?dr&cZX?????]/???U?c6??w?TS??81?v??????ld??R???? ;?vI6?`?? B??s?vo??+??es??Ew(2?'PMe# ?N{#??dd??g????G???3?c?.?????????=(??????K???i8???|d?X2??h^?K-??> endobj +150 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [427.3941 660.5925 567.9254 671.4964] +/Subtype/Link/A<> +>> endobj +151 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 648.6373 165.3344 659.5412] +/Subtype/Link/A<> +>> endobj +152 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [199.0314 618.7494 421.0166 629.6533] +/Subtype/Link/A<> +>> endobj +145 0 obj << +/D [143 0 R /XYZ 56.6929 815.7613 null] +>> endobj +6 0 obj << +/D [143 0 R /XYZ 56.6929 759.0684 null] +>> endobj +146 0 obj << +/D [143 0 R /XYZ 56.6929 731.2722 null] +>> endobj +10 0 obj << +/D [143 0 R /XYZ 56.6929 580.8258 null] +>> endobj +153 0 obj << +/D [143 0 R /XYZ 56.6929 543.8291 null] +>> endobj +154 0 obj << +/D [143 0 R /XYZ 61.6742 493.2291 null] +>> endobj +155 0 obj << +/D [143 0 R /XYZ 61.6742 492.6512 null] +>> endobj +159 0 obj << +/D [143 0 R /XYZ 61.6742 481.6923 null] +>> endobj +160 0 obj << +/D [143 0 R /XYZ 61.6742 470.7334 null] +>> endobj +161 0 obj << +/D [143 0 R /XYZ 61.6742 459.7745 null] +>> endobj +162 0 obj << +/D [143 0 R /XYZ 61.6742 448.8156 null] +>> endobj +163 0 obj << +/D [143 0 R /XYZ 61.6742 437.8567 null] +>> endobj +164 0 obj << +/D [143 0 R /XYZ 61.6742 426.8978 null] +>> endobj +165 0 obj << +/D [143 0 R /XYZ 61.6742 415.9389 null] +>> endobj +166 0 obj << +/D [143 0 R /XYZ 61.6742 404.98 null] +>> endobj +167 0 obj << +/D [143 0 R /XYZ 56.6929 354.9229 null] +>> endobj +168 0 obj << +/D [143 0 R /XYZ 56.6929 356.3824 null] +>> endobj +169 0 obj << +/D [143 0 R /XYZ 56.6929 345.4235 null] +>> endobj +170 0 obj << +/D [143 0 R /XYZ 56.6929 334.4646 null] +>> endobj +171 0 obj << +/D [143 0 R /XYZ 56.6929 323.5057 null] +>> endobj +172 0 obj << +/D [143 0 R /XYZ 56.6929 312.5468 null] +>> endobj +173 0 obj << +/D [143 0 R /XYZ 56.6929 301.5879 null] +>> endobj +174 0 obj << +/D [143 0 R /XYZ 56.6929 290.629 null] +>> endobj +175 0 obj << +/D [143 0 R /XYZ 56.6929 279.67 null] +>> endobj +176 0 obj << +/D [143 0 R /XYZ 56.6929 268.7111 null] +>> endobj +177 0 obj << +/D [143 0 R /XYZ 56.6929 210.4646 null] +>> endobj +178 0 obj << +/D [143 0 R /XYZ 56.6929 211.9241 null] +>> endobj +179 0 obj << +/D [143 0 R /XYZ 56.6929 123.7896 null] +>> endobj +180 0 obj << +/D [143 0 R /XYZ 56.6929 125.2491 null] +>> endobj +181 0 obj << +/D [143 0 R /XYZ 56.6929 114.2902 null] +>> endobj +182 0 obj << +/D [143 0 R /XYZ 56.6929 103.3313 null] +>> endobj +142 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F91 149 0 R /F57 116 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +185 0 obj << +/Length 3679 +/Filter /FlateDecode +>> +stream +x??]????????(P/pfD?E5???z???*?L????F??Iq????\Mp4f?????+????0i??[?dw?;???m??+?N??i?v1????_+[???q?j5T???E +u5?z??E??X???s?????s??m-?y???;?e?k??^?C??P?k?tzB??P?'q?k?#???f?v??????h? v??wn?'?]3???????P +??l??hQ??O????T?(?z???O???+??|?Uk+?+???????>)??"?u_???F?'Ka;NBB??= +"?)?? _!?/"rW?c1??dQ??????r[?::????<?|gS?!?9?F*?? 7???[? "I????}? +@??5b?&vd?H%??K?f!???:\????#9x?0??&\i"????????????Q?Y !????A?n4?O4n?,??Mw??(?FBk??C{????B?n'??@\g??A?g}P&2????\?gH?x?2??\E? (}??f??0N?(?? >?3?1;eX?T}?]?????}?^ ??;,?TW?_?j??*]m?-j??)F^8? ?90qp???u????F^4?xZ5 +??? S???c???V|W?y?i??/#?3?d5Mv??ST?j(???O?????qF???v??? ?nu?? ??|??-p???[=?T??>l?kN?5????5 ?k[4pU??b?M#@??F?k??+??$!?w??T?????v??aI????\??s?-{???9 v?Q_?Z?j>~wE$?q'H??0?-w?eb??%??9` =?M9?k7e???M9T??7DMga\?p?????p?v?90?G?hc!?v8??.??u??wV?N?3?:|T?????9??r???C:?b??{Xt??G?????4??????;??pD??uX#???nl?s???9??t???????.|fprK?psw?B?xk???{^??S??s?-|???9p??F?? ?uw???e??n???1r????????^9????$ ?u?????~;$I)s?-j?s?L???6????,?E?p,??b?? ?Q????g????[??m>c????9??n?@??p ?A??????2?p?z ???@??? e?o@?_?K?=P??`^b?B?T^?cn??[??kt????????4??sp?748?i2??)??aqs?g???b??????;CK????n??L???AiF??c?G??)m??y???v1?;?!8?L$???%80xp?P`?pD? ?` p??w?????G???;???qx???>x 0b1 ?#??B6s\???2U??)s???wFO?S?ni2e{;?\1?-x????d?}^7?? +k&??^???on?L?F? ???,?,?X???@wAy??x-?v???\P???????????????????%Aendstream +endobj +184 0 obj << +/Type /Page +/Contents 185 0 R +/Resources 183 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +186 0 obj << +/D [184 0 R /XYZ 56.6929 815.7613 null] +>> endobj +14 0 obj << +/D [184 0 R /XYZ 56.6929 584.6307 null] +>> endobj +187 0 obj << +/D [184 0 R /XYZ 56.6929 547.9207 null] +>> endobj +18 0 obj << +/D [184 0 R /XYZ 56.6929 547.9207 null] +>> endobj +188 0 obj << +/D [184 0 R /XYZ 56.6929 520.8533 null] +>> endobj +189 0 obj << +/D [184 0 R /XYZ 56.6929 457.9878 null] +>> endobj +190 0 obj << +/D [184 0 R /XYZ 56.6929 459.4473 null] +>> endobj +191 0 obj << +/D [184 0 R /XYZ 56.6929 448.4883 null] +>> endobj +192 0 obj << +/D [184 0 R /XYZ 56.6929 437.5294 null] +>> endobj +193 0 obj << +/D [184 0 R /XYZ 56.6929 426.5705 null] +>> endobj +194 0 obj << +/D [184 0 R /XYZ 56.6929 415.6116 null] +>> endobj +195 0 obj << +/D [184 0 R /XYZ 56.6929 404.6527 null] +>> endobj +196 0 obj << +/D [184 0 R /XYZ 56.6929 393.6938 null] +>> endobj +197 0 obj << +/D [184 0 R /XYZ 56.6929 382.7349 null] +>> endobj +198 0 obj << +/D [184 0 R /XYZ 56.6929 371.776 null] +>> endobj +199 0 obj << +/D [184 0 R /XYZ 56.6929 233.9081 null] +>> endobj +200 0 obj << +/D [184 0 R /XYZ 56.6929 233.3103 null] +>> endobj +201 0 obj << +/D [184 0 R /XYZ 56.6929 175.9241 null] +>> endobj +202 0 obj << +/D [184 0 R /XYZ 56.6929 177.3835 null] +>> endobj +203 0 obj << +/D [184 0 R /XYZ 56.6929 166.4246 null] +>> endobj +204 0 obj << +/D [184 0 R /XYZ 56.6929 155.4657 null] +>> endobj +205 0 obj << +/D [184 0 R /XYZ 56.6929 144.5068 null] +>> endobj +206 0 obj << +/D [184 0 R /XYZ 56.6929 133.5479 null] +>> endobj +207 0 obj << +/D [184 0 R /XYZ 56.6929 122.589 null] +>> endobj +208 0 obj << +/D [184 0 R /XYZ 56.6929 111.6301 null] +>> endobj +209 0 obj << +/D [184 0 R /XYZ 56.6929 100.6712 null] +>> endobj +210 0 obj << +/D [184 0 R /XYZ 56.6929 89.7123 null] +>> endobj +183 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F91 149 0 R /F52 107 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +213 0 obj << +/Length 5154 +/Filter /FlateDecode +>> +stream +x??]k?????>??a\ 3??V?DJJ? ??????N?s???n???=??~dc??BN????ex??kPP???.hR?e? B???fq???o? +???K???????{+8E?t??[???zh?W IY?{hEe??E????D???7??z??J???ta*???P??E?$C?O???KB)G??2k?????n?4?v{g?????? +\K??-m??)K-\?%,K??'L???8??'???-X|bS?[H??E?RQ?F?tr??????/???"T?? [8??#da8???`???w -???nA~eY?,)??N=)???????? %??p??s +???-RU`?ZH ???p????v?XF?leA???:??????(CBIBa1?Zn@?/?C?m6C?'?JY?????a?J.C???@ ??4??@?6??Q?t?????YJ???Q?{cT, Ae??w???e?I??e??!???Rr??PbQ?Y??h?E??Q?r?f:~??d????,2xo???????\X?"?`O5rR?]???P??x??k????n???}?????? ?"d!??)-?RDB?A ?G??NMZ?E??eP?%S+seVF?L??#S???2?> +????%4:??QC(jB9??QC?%t a at D?}?;62Zx\?*n???,????n?????F??j???t???? /?n???]QvY?????Q?=??5*??;?_?????e?:??C?P'E?s?ul?w?%R1`??'??n_??/?r]????????@y???f???????Y?????C&/mQ?G?E?+???j|%?xE????0???U?o???? ?fi5?? ?x??}?]??A\?r?V?QKF?????? mS/U?.w?c?n;p????I?Z7\???t?P[???z{w??Y?_?? rY?V]??o????W???}?`?????h????????Uo6OW?]? +(??Q} +>???m??U'?e?????Z5?eu??k??)???(/???9)?#?\4.*?V?????,???lJp6%???)?(? +HQn?^[???Y?????aX}????,el?uN?H?ra????E?3Z?x???W?\?|??/@ +?#?Pl at m?l67{ +?3"?a\B??2????????!#P?c??1x)G????w??-2mg1???~??9Nz?v?8?1????71??ID?X?J? +J???Q??1??r?? +?CE? +D?X???]?9T??@???!?|gSaII?????R)????$??^np???=)WE??????o??????ME??auo??C?yY{I???,;???Q?0??[oM????Z1*j[k@?O???*:??ba8??V?????1?{ey/ +?X?f1?W? _D?Q~??A?]? 2??jX#?l +???kGL????{E???J?2o +? ?25?Z?G??V!?????? ???O??????5FW??=A #???}?4???b?D.o???t86?" +? +??D@??#???kV?/??t=/?&-???J????\YAZH 0??f?;?gL?c??Z??n?g????$F? ?> ????(? ???!?!???(?r?l??????????6g??w=???????vG ???C +?Z??XK?????Zh%ku?m??*18I??????S?b?????w7??}????3 +^GZ? ??D9f????F????????, +??dr,??/(???d?????f???>?/9?bTtzh????N:?+?9T?j'Be??N:???T?5P??^?T??I???`m??J?P?????D???D???C???E?Ic2??< +H? DGw91??G?ao?????)????g?#?slgQ??`????VY??E)6J?@-m?L?? ?E>??Z>?@?1???NV?A??$?y??Z*?lis??,'II9?\p???[z??=???G???b??6_w?;?S??wJc ?z???,a??,\l-??E??A?H???????7?8?A)?d??6??,WO?<7?Gi.??[-(n.p?R?q?l??)??YIIx???")h?????????gd?v?????g?N?????2E?????Zc??'???;)?qG??m??7??R??< +??? ?k?C???SD + 2)D?rO????IEY??7?u?>?5???p?^sP?P?y?*?????C?A????X?????+???? +?[?TU???<;|??!?x0?%??A-???x?s??????P??2@???8?!b|70??v????!????'??mm?(??cb???&?@M7??g??$h?????y????I?%$?????A?"?????HA?2??Q?w?A.?? =?????[}?lT??b"#T???????k?o?????????]???2^?]??d5??!??@??.?T?{z??f??f??3Z?????Bn??@1?7????.????y????????W? +?I?2?zE???$?i7XS?? +?"?,`??z?=?`????L??S?T??S??uL&LQ? +8? ?P? ?0????????? +?_" 0?2`?{?A????X??ul#?+??&???V??z??????w???I?K?????Y?e?u????7?>?,(??MLq'?&??????n?D`.PB????8???3m?~?d??~?????M?~^:W:? ????(?,?'gNIA??.??p?b"6zf +b???S?0--T?>?-?l???}??hR??I) ???\?3W??:?F???Ix?????h? fV?(?e i????ss?=????[?????? +E?^C??? +?J? 9?????F?????? +?l?7?O??w??E?1?5Eq?+??Nk??? +???k??w?? *y?g?????????J???9 ??(??u?????$?0C3?S??M?3???c]}\0)????|?h ??G!??[?0u??[}?;? ?Lf?8]o'?yc??P??8?????{?A??^ +?????o???b???????3x????y??gl?K?????z???} J???g?#9???Vd-?k +?? E?#e"?#M??E???wjCk??X?3?f3?KV???B1?N??z??|?*?88?Y?NT?9[?????~?.V ???X??{?? *??_?9???????m?????h???p?endstream +endobj +212 0 obj << +/Type /Page +/Contents 213 0 R +/Resources 211 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +/Annots [ 219 0 R ] +>> endobj +219 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 627.2638 187.3018 638.1678] +/Subtype /Link +/A << /S /GoTo /D (named_parameters) >> +>> endobj +214 0 obj << +/D [212 0 R /XYZ 56.6929 815.7613 null] +>> endobj +215 0 obj << +/D [212 0 R /XYZ 56.6929 760.0646 null] +>> endobj +216 0 obj << +/D [212 0 R /XYZ 56.6929 749.1057 null] +>> endobj +217 0 obj << +/D [212 0 R /XYZ 56.6929 738.1468 null] +>> endobj +218 0 obj << +/D [212 0 R /XYZ 56.6929 727.1879 null] +>> endobj +22 0 obj << +/D [212 0 R /XYZ 56.6929 614.4478 null] +>> endobj +220 0 obj << +/D [212 0 R /XYZ 56.6929 586.3528 null] +>> endobj +221 0 obj << +/D [212 0 R /XYZ 56.6929 547.4086 null] +>> endobj +222 0 obj << +/D [212 0 R /XYZ 56.6929 548.8681 null] +>> endobj +223 0 obj << +/D [212 0 R /XYZ 56.6929 537.9092 null] +>> endobj +224 0 obj << +/D [212 0 R /XYZ 56.6929 398.881 null] +>> endobj +225 0 obj << +/D [212 0 R /XYZ 56.6929 400.3405 null] +>> endobj +226 0 obj << +/D [212 0 R /XYZ 56.6929 307.6807 null] +>> endobj +227 0 obj << +/D [212 0 R /XYZ 56.6929 309.1402 null] +>> endobj +228 0 obj << +/D [212 0 R /XYZ 56.6929 298.1813 null] +>> endobj +229 0 obj << +/D [212 0 R /XYZ 56.6929 287.2224 null] +>> endobj +230 0 obj << +/D [212 0 R /XYZ 56.6929 276.2635 null] +>> endobj +231 0 obj << +/D [212 0 R /XYZ 56.6929 265.3046 null] +>> endobj +232 0 obj << +/D [212 0 R /XYZ 56.6929 219.8846 null] +>> endobj +233 0 obj << +/D [212 0 R /XYZ 56.6929 221.3441 null] +>> endobj +234 0 obj << +/D [212 0 R /XYZ 56.6929 210.3852 null] +>> endobj +235 0 obj << +/D [212 0 R /XYZ 56.6929 164.9652 null] +>> endobj +236 0 obj << +/D [212 0 R /XYZ 56.6929 166.4246 null] +>> endobj +237 0 obj << +/D [212 0 R /XYZ 56.6929 155.4657 null] +>> endobj +238 0 obj << +/D [212 0 R /XYZ 56.6929 144.5068 null] +>> endobj +239 0 obj << +/D [212 0 R /XYZ 56.6929 133.5479 null] +>> endobj +240 0 obj << +/D [212 0 R /XYZ 56.6929 122.589 null] +>> endobj +241 0 obj << +/D [212 0 R /XYZ 56.6929 111.6301 null] +>> endobj +242 0 obj << +/D [212 0 R /XYZ 56.6929 100.6712 null] +>> endobj +243 0 obj << +/D [212 0 R /XYZ 56.6929 89.7123 null] +>> endobj +211 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +247 0 obj << +/Length 3478 +/Filter /FlateDecode +>> +stream +x??]??????????E*m +?h?&H4?@>$A????nl???lE?????I??^\???~?f~? ?E??????f(?IqL?pmWqt?}~??Z?m???\}????????(#(c1?x?P??l?[}r?&4^?z??????uJW???w?????/? ?8p??%e ??h?1?)%?e|????????7?F?r?J????w??????U?????????9?W??$#?????????$Ei?????B?u?)?:"@-?????#?O5?8Z???G??? :?Gu?b?????6#??n?}2??>cy`^????4G8???^N????h??5?0??N?$A,Nq??p??E]/?.?!??x?e?_z??????8??#???9??C????n???es(???/?v?r??0??p?\?)JX?b???? ???r??f!???(?z!? +UH8?(??h??2?!?$1 ?5??^??? A????B???Q?tOa???a ?`~6?Oc? +???p? +G1?-?M??g?P:?t?????IRX?????GCP?fM?$`????D UP??????;???d? ?}d?? ????`)7???]a???? +???Q?l)${4?}???( ??&1H?F +O?x4~? ????@?4d?????8?C??!???Mq??????Q?<{???D?#????8????1?? +?#.J?' ????%8? +???G???@?)" r?%,??;e??M???????U??[???;E???t? +??a? ?nR??tcM??????,[6??z+_@?b??"M%??Oc????#??w?2?RJX?&?j?@?Q?_??Rh:? +???????TW?r{?K?f???v?K7?N?w?sHYy??D?C???t?j1?E?1C??pJ?????0?????{qo????z>2]?I?d?l~/'0s?8??[??hE7?=u??8O?G????5}P|GG??g?k???7j??dl???Wg?? ?4TB???????v.J?????i^??>???Nw?u????.~???{????L7? b {??y??,?B?e?],?????????X????O??h>?? +???M?Cs"?,G6???K???1??L??:^?x??P?y$??8&??Q???????a*Z8???e??h $?j"$|u?*???/;???"??U??]?{B)I???"$?v??N=|n????:?_+Y???i?Z1(???-?C???S??y??k?[?7B?t[???|?j?b?l +???n??xU????n? ?<???? ?avW?i????Q?E????tZ?M?}?N??o?j??X???\??F Y5p??~?h?????9???8???]??DC?SB??????m6?gx?C4t??Rf???????????hg?Lt?????v???\??M{?ux5K\???p?$???Rx,??e?}??6? U?k?jd???@"i?{j?Q???C?d???W8???????g?????k?????p +??p???$c"?b???uswp???R???5?P+?n??;???:????8??G?? ??v???{??n?+u??o?T?h,^??x{?a?)??&??{{ +I?k?&?v???)??e??? ?Q"???}Z?z?????3]??qY2?X???n?? +??????bK??g4=P?.kp??,U?R?\V?@????CSu????8???# +6?iKW??????=7d??@?;?*??? Wg?h?L?????+????????F???J?? +@????s??3?B1?t?:?5??????? { +?m@??????7?#??P?#??Pw?SD????E?+4?????R_?A???A?sWBW?]?m*?"l;???]o6Q?G?B?yp?aunOg?I?"F &?7??;???B???i/[|e2??L?W???P???h?n?hjE?P?2Q?mg???J?,_?%Q?(Q???4 ?4T???????O?4??@?? Qg}??( {????1?$4^??\?M????e???R?Mt'?g?/4?Nlh??h?7?J?r??y e?d?????bO?'%?T?M.???EK&??g?#F????H,??t?????Z?&?4?_?3?????t???? +??ui`????????\??_U???kh?2???????eM?;?/??u??W?????????e?3n??b????????_4n??z?x}e?%?Q?JK9}3?/ ???dt????0?$?x3\gq> endobj +248 0 obj << +/D [246 0 R /XYZ 56.6929 815.7613 null] +>> endobj +249 0 obj << +/D [246 0 R /XYZ 56.6929 760.0646 null] +>> endobj +250 0 obj << +/D [246 0 R /XYZ 56.6929 749.1057 null] +>> endobj +251 0 obj << +/D [246 0 R /XYZ 56.6929 738.1468 null] +>> endobj +252 0 obj << +/D [246 0 R /XYZ 56.6929 727.1879 null] +>> endobj +253 0 obj << +/D [246 0 R /XYZ 56.6929 716.229 null] +>> endobj +254 0 obj << +/D [246 0 R /XYZ 56.6929 705.2701 null] +>> endobj +255 0 obj << +/D [246 0 R /XYZ 56.6929 694.3112 null] +>> endobj +256 0 obj << +/D [246 0 R /XYZ 56.6929 650.5091 null] +>> endobj +257 0 obj << +/D [246 0 R /XYZ 56.6929 649.9113 null] +>> endobj +258 0 obj << +/D [246 0 R /XYZ 56.6929 638.9524 null] +>> endobj +259 0 obj << +/D [246 0 R /XYZ 56.6929 627.9935 null] +>> endobj +260 0 obj << +/D [246 0 R /XYZ 56.6929 617.0346 null] +>> endobj +26 0 obj << +/D [246 0 R /XYZ 56.6929 580.0902 null] +>> endobj +261 0 obj << +/D [246 0 R /XYZ 56.6929 552.6807 null] +>> endobj +262 0 obj << +/D [246 0 R /XYZ 56.6929 501.3419 null] +>> endobj +263 0 obj << +/D [246 0 R /XYZ 56.6929 502.8014 null] +>> endobj +30 0 obj << +/D [246 0 R /XYZ 56.6929 448.9002 null] +>> endobj +264 0 obj << +/D [246 0 R /XYZ 56.6929 420.6588 null] +>> endobj +265 0 obj << +/D [246 0 R /XYZ 56.6929 298.5969 null] +>> endobj +266 0 obj << +/D [246 0 R /XYZ 56.6929 300.0564 null] +>> endobj +267 0 obj << +/D [246 0 R /XYZ 56.6929 289.0975 null] +>> endobj +268 0 obj << +/D [246 0 R /XYZ 56.6929 278.1386 null] +>> endobj +269 0 obj << +/D [246 0 R /XYZ 56.6929 267.1797 null] +>> endobj +270 0 obj << +/D [246 0 R /XYZ 56.6929 221.3203 null] +>> endobj +271 0 obj << +/D [246 0 R /XYZ 56.6929 222.7797 null] +>> endobj +272 0 obj << +/D [246 0 R /XYZ 56.6929 164.9652 null] +>> endobj +273 0 obj << +/D [246 0 R /XYZ 56.6929 166.4246 null] +>> endobj +274 0 obj << +/D [246 0 R /XYZ 56.6929 155.4657 null] +>> endobj +275 0 obj << +/D [246 0 R /XYZ 56.6929 144.5068 null] +>> endobj +276 0 obj << +/D [246 0 R /XYZ 56.6929 133.5479 null] +>> endobj +277 0 obj << +/D [246 0 R /XYZ 56.6929 122.589 null] +>> endobj +278 0 obj << +/D [246 0 R /XYZ 56.6929 111.6301 null] +>> endobj +279 0 obj << +/D [246 0 R /XYZ 56.6929 100.6712 null] +>> endobj +280 0 obj << +/D [246 0 R /XYZ 56.6929 89.7123 null] +>> endobj +245 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +284 0 obj << +/Length 4406 +/Filter /FlateDecode +>> +stream +x??][o???~??(?? +t1?M???A`?? ?"? ?d[?????*??????(Q$?jOb????|o???#?U!??-AY?j?!??xu?=+V??????Y[??/???????? +T%*W?????t? p???????kD???/??Q_^^z?|?wm?????Ah?+.??Xj!? 4?ZC*J??BER??? ??????Q? Y??K?_????????g ??qSD*???Q(.q??????????[D)8?.?Bt?.>????????K2|j??P?????|??V]??w??????t?Mjwo??A?z?IQqgP?U????? 2DD\? +??2?D+???K????????}??TU?a?????Q?YU9j?:r???'T!??3r????1;e??l?^??M???????7?MPX??":6m?N?!??? +A??%L??9?;????r?r?????e%m(?N?-p???????&?_??J??]??B ??6e'7?????i???K??K??`L?p9(x????l#B1.?%?N&??eK?? +????Mc???N&?RfM??z^???(1??\?M??9:?d??%LLn??cF???Irri#,0??G,m??TT?????^?r?v?9x-7jOm???(???&b?????m????@ !K ????2?rtFIaD???M?#??h??B at A??????Q 0??H?%???????V[???qrj???????L?}??????!?$???B???hn?v?9x-7??????f??????t???Tw???9?>?y????w???1????=X????????/`q?t????y?cQ?Msk,$?7F???\l??M~hn???@??m?$??H?v????N??V& +?@?dKp[_????????u??T?s?2T???3N|a1????isd??r!D?,??TT???t?$"?????w?C??? (X?>???f?`? +?!XiX?5???` +g????]?>?????P??m??????? ?G? ??{?I%3n}?4???F??o??R~??x???? 8B????`?????7????R?S???c-????D??G????RG??P?e????6:vJ>??_????:?.???2?E??????4rV???>?`-3?U??k????M}???T??L/?7??K%??*??(R??F??????M?mvGAS??????0?1%:nI>?1???????? T????m????f?zQ?s ?*E&_7????O??pU\!?g ??????lw???7:FN>0SJ|7J??7???z?q*?Wuu}??A?????p +dC????O?P_*???t [ dKb?@? ?X?D??????2???????VG?Vq???Z?f??~v?_?f?o???|??O&??uq?????M?{x?dd??m??i?>??J7H??U?T!?*??(?Y~??[e????Q???r?????6"? 9??vS?8?{?Y]t??2?Dq?c???v??nbb5?$???K??|?s????^ +9?6Le"c^??G???T?d?Uxb?{nZ???{F? ??F?hv??9y?????:???dLa +??????l?|??!??m??????? ????E??0q?\???m???? +?w???n?w???6??q?j?0?csg?\????A*??????????j???Y????Kf4K???o??TL? +?????;??t~?t&???? s??;o.???S7>? ???d?G?????????y??1?v?????;?I:n?????? x?m?4?k??????i?&n&?f2FH????F?a?F???>b|?RAi??w????p?L???r?l?????X? ???%??U?H?????\????????L??F??/??9?endstream +endobj +283 0 obj << +/Type /Page +/Contents 284 0 R +/Resources 282 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +>> endobj +285 0 obj << +/D [283 0 R /XYZ 56.6929 815.7613 null] +>> endobj +286 0 obj << +/D [283 0 R /XYZ 56.6929 760.0646 null] +>> endobj +293 0 obj << +/D [283 0 R /XYZ 56.6929 738.1468 null] +>> endobj +294 0 obj << +/D [283 0 R /XYZ 56.6929 727.1879 null] +>> endobj +295 0 obj << +/D [283 0 R /XYZ 56.6929 716.229 null] +>> endobj +296 0 obj << +/D [283 0 R /XYZ 56.6929 705.2701 null] +>> endobj +297 0 obj << +/D [283 0 R /XYZ 56.6929 694.3112 null] +>> endobj +298 0 obj << +/D [283 0 R /XYZ 56.6929 683.3523 null] +>> endobj +299 0 obj << +/D [283 0 R /XYZ 56.6929 672.3934 null] +>> endobj +300 0 obj << +/D [283 0 R /XYZ 56.6929 661.4345 null] +>> endobj +301 0 obj << +/D [283 0 R /XYZ 56.6929 650.4756 null] +>> endobj +302 0 obj << +/D [283 0 R /XYZ 56.6929 639.5167 null] +>> endobj +34 0 obj << +/D [283 0 R /XYZ 56.6929 585.2655 null] +>> endobj +303 0 obj << +/D [283 0 R /XYZ 56.6929 556.8801 null] +>> endobj +304 0 obj << +/D [283 0 R /XYZ 56.6929 534.9973 null] +>> endobj +305 0 obj << +/D [283 0 R /XYZ 56.6929 536.4568 null] +>> endobj +306 0 obj << +/D [283 0 R /XYZ 56.6929 490.1654 null] +>> endobj +307 0 obj << +/D [283 0 R /XYZ 56.6929 491.6249 null] +>> endobj +308 0 obj << +/D [283 0 R /XYZ 56.6929 480.666 null] +>> endobj +309 0 obj << +/D [283 0 R /XYZ 56.6929 469.7071 null] +>> endobj +310 0 obj << +/D [283 0 R /XYZ 56.6929 458.7482 null] +>> endobj +311 0 obj << +/D [283 0 R /XYZ 56.6929 447.7893 null] +>> endobj +312 0 obj << +/D [283 0 R /XYZ 56.6929 436.8304 null] +>> endobj +313 0 obj << +/D [283 0 R /XYZ 56.6929 425.8715 null] +>> endobj +314 0 obj << +/D [283 0 R /XYZ 56.6929 414.9126 null] +>> endobj +315 0 obj << +/D [283 0 R /XYZ 56.6929 403.9536 null] +>> endobj +316 0 obj << +/D [283 0 R /XYZ 56.6929 392.9947 null] +>> endobj +317 0 obj << +/D [283 0 R /XYZ 56.6929 382.0358 null] +>> endobj +38 0 obj << +/D [283 0 R /XYZ 56.6929 303.8744 null] +>> endobj +318 0 obj << +/D [283 0 R /XYZ 56.6929 275.4889 null] +>> endobj +319 0 obj << +/D [283 0 R /XYZ 56.6929 241.6509 null] +>> endobj +320 0 obj << +/D [283 0 R /XYZ 56.6929 243.1104 null] +>> endobj +321 0 obj << +/D [283 0 R /XYZ 56.6929 107.1553 null] +>> endobj +322 0 obj << +/D [283 0 R /XYZ 56.6929 108.6148 null] +>> endobj +282 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F98 289 0 R /F101 292 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +325 0 obj << +/Length 4310 +/Filter /FlateDecode +>> +stream +x??]m????????'o?H???W$E^???CsWE:[?g??6???E??^R|%JC???KF?X+ +?y?!?3$?????OQ??|??DJ??z?????W???????????'_p??Q??t??f?R? +?(??X??|???zE9^????4???5??SS??bw?????????4QZ?-[?A9??????"[>??$Q??>?(Z?"'(?4S???????|}??3???`DYN?+N?e?R{gw????F??2?p??? +?&?O??4c?????rD0??????x?J?tiO????S?|y??? 91???t??P???}uR? [??????V??,W?????v?w?&?w?w?z?H?????????u_?R?jS??s?Ugo5 ???E?]???????P?E?!??>?n?V3???Si??H3??h???)?}??Ju?u?T???E?ou?oUEO?????.k?O ????????/?????&Ki????imG??3???S???~???????_|???????T????J??_?? +?i+?)??B???:h??H?*?????+?Z????o??o???!Z??????zS? +? +?c}k??I??R??H;?1?N ??E?q?0?z',?+G?~?TnIz?Q?d ??,?u?????y?'Q?(??h???j???K?1????riY<B??? +QrY???y?x?nW?Q??????????/?????vl?H?\(??M9?3%sF?pBj(?????-o?z??????;$]?Z?eyeH(A????z$?_%?eA?a?+'??r?????)d?? ???M????"?????k?F i?#9?#???xIp?b???a???q/{?????=4u?9??3??\f???????n:????M]?????W?|?|k???f?io???qd:?????????q??'??????)????2??+ +*"M?I?&?^t?R??"2D?s??????thY?p??RZ?X??????????N??R?V+')g????)o??u?}E ? OK-?Y@?3u[??QQ????RCD?`?=?:??p??????.????M?gI???I???z~:?????p?1?X1S)?_'7,?:? Y??k?=??^??????b?B?W?CA?4?7#:??+Oe???M??n?4a@?6??wZ??????j?$??nW?????A=?????B?t??p??Nb??W?Q?R???iSK??f??$*???/?3?t?f"??pFLd+??CQ?X(?? ???k +W??U?NW??U_3???L?Y??A??????H?C?'?~?A?j#?u?FZ?Y??]???\?????????????XW?C?????????????N?-SyE??Sc4?t?n=?????S?$??????!?n?Y??d??I.d??$?+\N???A7dm}???.?*'O??d?f3??_??S??m??8>O:???N?????????~?j{xr???Y&?m???0-???U???^m?l???I?d"?2?RnU.??%?%BL0 %0rBs!_?['B0E'?#???Q?i??RHq??b??#?,-??4?a??#?j?^??o??(???B +?4d??Q"m?( +%?I???$?XN,?Pqe#dB E?T??SzS6Je???4o?? M?c?,2?l?L?1?W?LD2?p?'m???\/`)C???????N?3????K ???Wvz?z?F???R????G'6?!$[?:??{???#"F???)N??????? ? +?\*[/!l +?F> +????n?7w????N?J?"?v^??[??@?????_B?w=?SEd????D?l?,+? k6D?V?{??^?? ???0vf???@?+n?c?Zn??d OI?p?<#Ty'A?)??'?SB?D\???`1??w?]j??l????la?.????ep.?|</??????:???????6?CR?HN????xH????bm???f?Hs?]??/i?b???q/???z?s??` +?np?l??s=L???0>??I???d???W?????!?t?q????F??p??F????e?_m$?e?!???%?$?e?V,?2?%#.??x?????,vP???!:u??7}F +t?P +?7?????E]?/??9?_???? ??/?C?,[*???;????F@??m?????U?*}??????A??????P?o??rW???@_c9???>Il?m?P????????S??9`??????n???6?l??w??4?f?d? +d45?93??\6?/K????e??cX?V??J????]??#2?w([???\??d???$FM??>5hS?Q$??P??L&Px?.?????? ??!?t????=K??JE??o???? 5??}j??H E? +\9?6I??j?6????J?????_?~?os???& ?N?.??D*???)???V<?????????I???l?wa?N?G? ?wM?Q??E@m???????K?*# ?\2b?{uvbM +??Y}? ????;????????r@@F9G?e?]?J?????F?N?G?&?????,??????Cm?W??R????GF ?|??o?/???<7?8o??"??????????????z?~`?!9+??s$????I? ?;??%8G??????????>?IY&? ??Qt????J)?M?*?Y?%??????&???l.1q9>vY??w??L?d?<2n?????n ?s?R????????[F??% ?\{d?????v?b?rRpw???>??Bt???{??G????????b?B?Q???!{T?1??E?3???d??=??#????3?t?L??n>??3??h?????????]?????j???-????? 0?_?6g/?ab??? ?l??????v7"???Z?????0?S?`????ect?q???S??G???RbL??O??AA2!??[??Fh:?r??P?J'?9???????3????g???? f.t???o7??n.????rB0??v???t:h???J ?P?x?f_M?q??{??1D???\??x&]?21???M?o???-u?,?!????&?&??r????H?.D????kn??????`?L?6d?.Bz8??m??????n????M????Bmn??????u`?@/????iA?z;?p?m????f^??Y'of???G?>X???????????O1$?|??S}?3+??H1?UX'??\N?i>? +????i ?y?????>:p*????????C?`+tG?a?P??QYw?`f??O?? ??Y?{ +??{.?h3?<6+? ?0??K???g?ic?f;?????Cmm?"q?C??``???j?????????W??D ??u0`?;??L/? (c?r???;??? +?v0?}?????E???>???<?s ? +???Cmq3?????0???`??wF??^q0?[?)?@?@(r?p???M??w?????}?i?h????Eendstream +endobj +324 0 obj << +/Type /Page +/Contents 325 0 R +/Resources 323 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +>> endobj +326 0 obj << +/D [324 0 R /XYZ 56.6929 815.7613 null] +>> endobj +327 0 obj << +/D [324 0 R /XYZ 56.6929 687.1731 null] +>> endobj +328 0 obj << +/D [324 0 R /XYZ 56.6929 688.6325 null] +>> endobj +42 0 obj << +/D [324 0 R /XYZ 56.6929 616.4486 null] +>> endobj +329 0 obj << +/D [324 0 R /XYZ 56.6929 590.6535 null] +>> endobj +330 0 obj << +/D [324 0 R /XYZ 56.6929 484.4867 null] +>> endobj +331 0 obj << +/D [324 0 R /XYZ 56.6929 485.9462 null] +>> endobj +332 0 obj << +/D [324 0 R /XYZ 56.6929 474.9873 null] +>> endobj +333 0 obj << +/D [324 0 R /XYZ 56.6929 464.0284 null] +>> endobj +334 0 obj << +/D [324 0 R /XYZ 56.6929 453.0695 null] +>> endobj +335 0 obj << +/D [324 0 R /XYZ 56.6929 442.1106 null] +>> endobj +336 0 obj << +/D [324 0 R /XYZ 56.6929 431.1517 null] +>> endobj +337 0 obj << +/D [324 0 R /XYZ 56.6929 420.1928 null] +>> endobj +46 0 obj << +/D [324 0 R /XYZ 56.6929 383.0424 null] +>> endobj +338 0 obj << +/D [324 0 R /XYZ 56.6929 358.0792 null] +>> endobj +339 0 obj << +/D [324 0 R /XYZ 56.6929 323.6435 null] +>> endobj +340 0 obj << +/D [324 0 R /XYZ 56.6929 325.103 null] +>> endobj +341 0 obj << +/D [324 0 R /XYZ 56.6929 314.1441 null] +>> endobj +342 0 obj << +/D [324 0 R /XYZ 56.6929 303.1852 null] +>> endobj +343 0 obj << +/D [324 0 R /XYZ 56.6929 292.2263 null] +>> endobj +344 0 obj << +/D [324 0 R /XYZ 56.6929 281.2674 null] +>> endobj +345 0 obj << +/D [324 0 R /XYZ 56.6929 270.3085 null] +>> endobj +346 0 obj << +/D [324 0 R /XYZ 56.6929 259.3496 null] +>> endobj +347 0 obj << +/D [324 0 R /XYZ 56.6929 248.3906 null] +>> endobj +348 0 obj << +/D [324 0 R /XYZ 56.6929 237.4317 null] +>> endobj +349 0 obj << +/D [324 0 R /XYZ 56.6929 226.4728 null] +>> endobj +350 0 obj << +/D [324 0 R /XYZ 56.6929 215.5139 null] +>> endobj +351 0 obj << +/D [324 0 R /XYZ 56.6929 204.555 null] +>> endobj +352 0 obj << +/D [324 0 R /XYZ 56.6929 193.5961 null] +>> endobj +353 0 obj << +/D [324 0 R /XYZ 56.6929 182.6372 null] +>> endobj +354 0 obj << +/D [324 0 R /XYZ 56.6929 171.6783 null] +>> endobj +355 0 obj << +/D [324 0 R /XYZ 56.6929 160.7194 null] +>> endobj +356 0 obj << +/D [324 0 R /XYZ 56.6929 149.7605 null] +>> endobj +357 0 obj << +/D [324 0 R /XYZ 56.6929 138.8016 null] +>> endobj +323 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +360 0 obj << +/Length 4405 +/Filter /FlateDecode +>> +stream +x??][???~?_a?K=E????K?I?6m +?;@6??k?3Fl????n???^E?"???t?T6#KG??/??h??hF?$?p5+M???j?????77H?,????????????J?????,?I^?tV?EB*\?????_?.0M?/?????????rn??rw???[??f%h? ?????BIE)?Z +x?(???????n?r?)*?E?Bq??t??u:[?9???IV?h???g??o(?K?cugw????N?z??$KK:?0Jh?J?p?Y???]??h(h??O????$)????1???L)???b??[????^?nQ:?.2 +nL +^[@? ?"????v{?~>??-??????$?,??Us8??N?8????|i?O?? +G~???????vy??????????????l$?[????mN? 3?g? +?_N?? Eh9??lO??f??.???DJ:?????n'???~M>;??-f?6???%_????Us9???{C?I??W?R?[???OS???w??r?$??Cs9?K???5 K????????|q?=?u??N?F:R??>%? Z???95?vU ?U??w????L]??n???L??LON,??0LO[??Gn,? t??v??9d?:9?=3??j~n`w?1??????lG??e?`?l~?!??50)22?js????]s"2????#?=??HB????G?J?QY??A??8p????Tv~X???V???T??%8_$ DS?0? +^/ ???? +bree$??/??nm??v??j?O?????Ig??L\?s(4?3?x?"? +??(3#-????c??E yg3S]?MHQUQj%Ih?I???lj??tZ?????a?2? +2\(?6?J??^???o?$(II?M???gw????????t??f? 5??Mj????')B8Hp??"???~??-??q???Sv??.???R;???p?MT??"??)!J??PR?D|???_&r(b.g??@m??#?B??? +?@E??U?B4) ??j9?????Q?)?Aj -u?I? 9?/FUf ???g?crrx??L(b???!W(A#2$????q???+?(>??1d????J???`<.?I-g??8?r?%-I?/Z* +???s%?????????0S?_S-?t?,'i????????p??PM?_??avZ????????Q?-}?????,\*??]GE?????^?F?P??G???>"?9?>????3!?lf_??????+ fJ?1\h???,?`hd???b?}??QG??*???z??"??6_, M?k???1p?2???M?9d??c?+????%?n?&$/???+???+Ffv MxQ4b???? ????????j*"?^????J??%N???.-??1:??W?aIqQ^GE?????8?????$?b V?]?1???h_?w> [??)~?"??|??Q?e4?? +?????????k???? ?n??$?eF? +? ??4%A? -Cw?1?W??????Ql |?(v?????hl?o?K???M5??`bh? W?`5????Kct5?FW?D??"?*l??? ???Ng??zy>??Z>?.???0?S$e??9?#?+?????G???G???????)?????%?? +eUo(z?B?9_??V?? +?r?r?09???&?? )MBe?????reJ???+mj??w)???\?A???z?7o?W?-$?A? -CW?o?wa?h9???]O^M????)?f??H2?Y?7\1?b[?i???m????????0???Y?K?B???S1??6??w?? +:b?v^-???????>???? ???? p?G?2??:EO??3+????=J??E?4)1>?'?V??n5f?t????!;????(?????7\?G??\a???N?????gTGC??[?(??+4??_C92|*GJ??.?n|?'?-????#??6O1R?? +?v%9L??=<=?K???Q*?TG??RmRa? +??&bkh?#??~???(????=????? ??68?9*="z +=?!?` ???By??6????p-?e????~ +?d??P)?x?n????i????po?? +"?u +??j?B #=7??k? u?w-_?y?x=?H??!???|??%?G???|?~8???????????8??Z????r?"?????"??? +?P W?P???E?????vk??? ??????6??)?b?g??Kr?!V?l??V????bJ??L7???????k ????0??-? I?!??????>J0????ZK?K?4??,?ow??6FS?~v??d ?K?f?3?? ??V?"??*??[????@Mm??@#?}U|s??????\???ms?;}????o?z??Z^]Nr?=d!d?E???2????!h +???r????G???T???????H?'$??iS?i??F???#?r&:??D??R]??v???????#?0????????????0????6?a?+=????#???????[.?g?M{?|?N???@?VR???????Z*ay??[J*???-? ?t??Q???????>+?IU?t??U[}xea?0?S??q?\?X?u?A?!?G?cE?8?M?????k???#?a?R???=U4&??)TW$?~7F??vR;J?u??DT?;????$???i??? ?$DSJj??[ ?]?H?k{???V?]?N?o????????RT-C?@?q 4f?????~c?"?????8??n ? "wq? ?c,?1qL??;.? ???1al????8??~da???cL???8?8???|X???1&?%;|??4?g?W$i??T???1??o?????9???d04,???#??q? +????!?????n?}_??sh?N??}???rM?s Q?????4??H???V!???3?? ?????.+:?????q?D?1 at L????????9???=???[[?W?#y???+?/?[/8t6??ay?????H Cj????? A?v?|???????!??R??cm??rw???)Ub?r???>???]?{?k???????????????5?qBQ?#Y?? +?vh11?Qyf;??j?#?W?O0????3;??3?=?C????3 "??[????qC????L&??b?$?Qe??xKq????'.X ???^F??b????3???U????i?6????l?g??c?p???f??V?l ??27???+[?9??tIe??aZ+N???)?:N????????R????B??,??;= ???n?c[??he???7???J/??B????G????????AP'?}????a0???~{X?????C}?aI~?E???l?????f?k???$?/???1?A?*4??M?c?>?D???V?p$??b????>??05u??E??? +Zb?-? c;??_!?@M?Ox??&???$??{???bH x U??? ?b??> endobj +361 0 obj << +/D [359 0 R /XYZ 56.6929 815.7613 null] +>> endobj +50 0 obj << +/D [359 0 R /XYZ 56.6929 759.0684 null] +>> endobj +362 0 obj << +/D [359 0 R /XYZ 56.6929 738.4887 null] +>> endobj +363 0 obj << +/D [359 0 R /XYZ 56.6929 651.4927 null] +>> endobj +364 0 obj << +/D [359 0 R /XYZ 56.6929 652.9522 null] +>> endobj +365 0 obj << +/D [359 0 R /XYZ 56.6929 641.9933 null] +>> endobj +366 0 obj << +/D [359 0 R /XYZ 56.6929 631.0344 null] +>> endobj +367 0 obj << +/D [359 0 R /XYZ 56.6929 620.0755 null] +>> endobj +368 0 obj << +/D [359 0 R /XYZ 56.6929 609.1166 null] +>> endobj +369 0 obj << +/D [359 0 R /XYZ 56.6929 598.1577 null] +>> endobj +370 0 obj << +/D [359 0 R /XYZ 56.6929 587.1988 null] +>> endobj +371 0 obj << +/D [359 0 R /XYZ 56.6929 576.2399 null] +>> endobj +372 0 obj << +/D [359 0 R /XYZ 56.6929 565.281 null] +>> endobj +373 0 obj << +/D [359 0 R /XYZ 56.6929 554.3221 null] +>> endobj +374 0 obj << +/D [359 0 R /XYZ 56.6929 543.3632 null] +>> endobj +375 0 obj << +/D [359 0 R /XYZ 56.6929 532.4043 null] +>> endobj +376 0 obj << +/D [359 0 R /XYZ 56.6929 521.4454 null] +>> endobj +377 0 obj << +/D [359 0 R /XYZ 56.6929 510.4865 null] +>> endobj +378 0 obj << +/D [359 0 R /XYZ 56.6929 499.5276 null] +>> endobj +379 0 obj << +/D [359 0 R /XYZ 56.6929 488.5687 null] +>> endobj +380 0 obj << +/D [359 0 R /XYZ 56.6929 477.6098 null] +>> endobj +381 0 obj << +/D [359 0 R /XYZ 56.6929 466.6508 null] +>> endobj +382 0 obj << +/D [359 0 R /XYZ 56.6929 455.6919 null] +>> endobj +383 0 obj << +/D [359 0 R /XYZ 56.6929 444.733 null] +>> endobj +384 0 obj << +/D [359 0 R /XYZ 56.6929 433.7741 null] +>> endobj +54 0 obj << +/D [359 0 R /XYZ 56.6929 396.929 null] +>> endobj +385 0 obj << +/D [359 0 R /XYZ 56.6929 369.589 null] +>> endobj +386 0 obj << +/D [359 0 R /XYZ 56.6929 348.133 null] +>> endobj +387 0 obj << +/D [359 0 R /XYZ 56.6929 349.5925 null] +>> endobj +388 0 obj << +/D [359 0 R /XYZ 56.6929 338.6336 null] +>> endobj +389 0 obj << +/D [359 0 R /XYZ 56.6929 327.6747 null] +>> endobj +390 0 obj << +/D [359 0 R /XYZ 56.6929 316.7158 null] +>> endobj +391 0 obj << +/D [359 0 R /XYZ 56.6929 305.7569 null] +>> endobj +58 0 obj << +/D [359 0 R /XYZ 56.6929 240.0692 null] +>> endobj +392 0 obj << +/D [359 0 R /XYZ 56.6929 211.8972 null] +>> endobj +393 0 obj << +/D [359 0 R /XYZ 56.6929 143.0474 null] +>> endobj +394 0 obj << +/D [359 0 R /XYZ 56.6929 144.5068 null] +>> endobj +395 0 obj << +/D [359 0 R /XYZ 56.6929 133.5479 null] +>> endobj +396 0 obj << +/D [359 0 R /XYZ 56.6929 122.589 null] +>> endobj +397 0 obj << +/D [359 0 R /XYZ 56.6929 111.6301 null] +>> endobj +398 0 obj << +/D [359 0 R /XYZ 56.6929 100.6712 null] +>> endobj +399 0 obj << +/D [359 0 R /XYZ 56.6929 89.7123 null] +>> endobj +358 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F92 158 0 R /F91 149 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +403 0 obj << +/Length 5072 +/Filter /FlateDecode +>> +stream +x??]m??6r?>?BI?*Rba? A????J??N?*w?u???Jq4???v?4?u*?=?B? ?????'o?????< ???? ?d? +TT??q?PY?l????????7D?,????????W?gxV??????????(1?q\???????w??.????????I]?Y?l~>?M?]?}???Bf\h)2?%/K??gKBP???pqk??????}7???R4 ????Q. ?????xv'??? +Fy???Y???+2??0".???o?7?o??k4??????C2D)?- ??X? ?RN~????k??R(?e???E?|F??f?zvo??o? +????hT????????????????X -? +?J?B+??V.??m&FJ???x6??"? XW[??%0K?(quI??1?CP?!V?l-?O?+???_??????l?C$??, Xt??????Br???Z?r?S????d???b?R??6]/$?-rD+??V??O1Pr?H???u?&E#B%???J%?Cm?fI G?W????O2????L*-?K?L?????d??r?M???????#?j?-sY`???7A,?w?fAl??B4????(J?2???v???>{O&"?\p?l??Yh1\?O??Oq^?B??+????????A^K+??$D?o???.?L???d??o????:???T?(g?NU??OZ?J?Fl*????u<?H!???-@??x>bz?/????C?i?vBE????s4???O???O?H??$ |4N5?eS?o??R ?z?'K??D?[?h?m??.~?0?\f#????? .ZI?X?$?&>?[8??*$b???'^?O???????g;U???T?@??? ????R?j?????????1? +????=H!?<:r3?H?S4??)???????)z???%???K:???:U1?_? +?f?&v?2?{?????To???YE???/S??@???N?????b???*??k???6 ?E|????E?~?%??????n3???B \z?????E?j????`Ws ?j?????t???BI???????tN-?MM?zGC?? ?????@??t?/8??1V^sE?l"??Fj4??????2???[ ?6? TP?>?QM????????B;?H ??;b????h??Pob$ +???????Htb???( ?G?`??H4hF?.?6?j??7_????????y?#M????vj`?????C??m?i0?????0??8???????????Bk$??#??_??vnZ?yz\???T????N?u?o~TW?$??EDhVj??=U?s?.??q?Y???a??X?4?R?r2??????yw????????i??6???a?/???n??(??xn6???c????t0???f?c?v?l7?,?xF???2?????%??????v?a?O??b?u????g?B??YE?P?J????Xf????>m?2b/??cs??~N?4?J&B??A?:!??m??{dS+?R?G??2?.-??? K ?q"??J?j??x???j????g???y????E?g}???,?????b????C;????n?kj`???cwv?E??C? $,`??lF*?sg??]u???Y??A?j????01~???k0?P???G?P????L??????WqO +U???A??????x??2?*?|????>??U??????? T??7???(N??O-??O?+???_E???2??Y8?@?s???n?I?z????.???J??i?a??_G?N?^O?$H?I??4\??KKp?E=???W?zM1???`???8+?????????? /;$wy?EV6"?9? +j?tI??? ??p?=???C??BU??\X?tx?_?]???p\.??_!1?"p??>\\?u??Q?7?y?t8+EG??F?e???kd???S^???? 3k?]fut\x9/kVAZ????n?f?%?P??k?? ?a,?EY"??J?}??uqy?>????.g??a????.??hx-s???:???t-'Y)Y?,????.C#?? +??BE?gp?A^09???7??To??????? l?$????Y????J|{???????p=??3ZyS???C?s? +j~x? ?S?N] +1???????????9? +???????????-$H?7?.?????F?%??:?N???P??IK??6? ??V?Acyy?q?%L??K?\?^B??1?0???.?6???%???I??b:5??Fh??t??b? R?-?K2a1z????m ???N??0???.|?b?G??-&H???.A?b^?j? ???%???P?q,& l-? l?L?bX??u???b:5???R?z???? X?f/\??1?[{?O?6?!b??h8?6n*?Z? +l?3k| x?0??M??????????9?fY???A?W?y?Z???y?}?IP?86 ??r??z??-????????+Y?????0??%???3?\]?f??????k?????1?3x?"?M??@??A ???D?l????????C~????=?????9? ???#T?~EyK6????-??\?%?lS?6?%????D8??/v ?,???a?V.?2xiUF?"?dwNp???- ?9n.?}?!B#?E??FE???;??a]??8???b???bY??gd?* ???B)?@??9mvr/@?????1?i?????E??U?7???w?,?? +{;/?XWz?_9?EA?P +4P&A??i??v?n???M??yA??????? +???g?}??O?????????1h@% ?4C??????6? +???,?????H3G9n?q??C?nn??s???z???]????????+??"?$O??4??Q-F4????Jx?]??\??I??\?VN?????K0/#????@????`T?S??.???>???"ap{????nt??j??z'??\o??8;???I?e?????1??S??&?'????p?&??D???7A?D???M?????`???0p?m?R???'VJ???Po?>?8.7&.??i????"U)?tO?sl?@?????q?????k?Z??&?Y?)c?uss?>b?tV;?*??n?L#?e?'%`?P??[0?N,vHb??????E{??v?>kM???.?O-?]?O??E{??X??*T??M_?Jp3?P???h?"?u?????B?&0?N?|????&?f?????(??????f>???pZ??? +?? ??e?h??0?g??,?????v?/(???{;????~?Y?'=??n?? +???~+?4???a/???pn?&??}?>???W?? ?????Z???e??=?v?y-???_uG????aU?t?Bu?aG?????Rq???B?????????g??j????N]????Xf&5?????x>uo???????Q}%L?????pN??I?e??????????A??j}?????oR4:????1vL?????]?B?j????xYV?{"?q5???????????F? ??s??O*???????o?7?o?z?e??????R$lendstream +endobj +402 0 obj << +/Type /Page +/Contents 403 0 R +/Resources 401 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +/Annots [ 444 0 R ] +>> endobj +444 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [168.8613 156.374 268.5368 167.2779] +/Subtype/Link/A<> +>> endobj +404 0 obj << +/D [402 0 R /XYZ 56.6929 815.7613 null] +>> endobj +405 0 obj << +/D [402 0 R /XYZ 56.6929 760.0646 null] +>> endobj +406 0 obj << +/D [402 0 R /XYZ 56.6929 749.1057 null] +>> endobj +407 0 obj << +/D [402 0 R /XYZ 56.6929 738.1468 null] +>> endobj +408 0 obj << +/D [402 0 R /XYZ 56.6929 727.1879 null] +>> endobj +409 0 obj << +/D [402 0 R /XYZ 56.6929 716.229 null] +>> endobj +410 0 obj << +/D [402 0 R /XYZ 56.6929 705.2701 null] +>> endobj +411 0 obj << +/D [402 0 R /XYZ 56.6929 694.3112 null] +>> endobj +412 0 obj << +/D [402 0 R /XYZ 56.6929 683.3523 null] +>> endobj +413 0 obj << +/D [402 0 R /XYZ 56.6929 672.3934 null] +>> endobj +414 0 obj << +/D [402 0 R /XYZ 56.6929 661.4345 null] +>> endobj +415 0 obj << +/D [402 0 R /XYZ 56.6929 650.4756 null] +>> endobj +416 0 obj << +/D [402 0 R /XYZ 56.6929 639.5167 null] +>> endobj +417 0 obj << +/D [402 0 R /XYZ 56.6929 577.5386 null] +>> endobj +418 0 obj << +/D [402 0 R /XYZ 56.6929 578.9981 null] +>> endobj +419 0 obj << +/D [402 0 R /XYZ 56.6929 568.0392 null] +>> endobj +420 0 obj << +/D [402 0 R /XYZ 56.6929 557.0803 null] +>> endobj +421 0 obj << +/D [402 0 R /XYZ 56.6929 546.1214 null] +>> endobj +422 0 obj << +/D [402 0 R /XYZ 56.6929 535.1625 null] +>> endobj +423 0 obj << +/D [402 0 R /XYZ 56.6929 524.2036 null] +>> endobj +424 0 obj << +/D [402 0 R /XYZ 56.6929 513.2447 null] +>> endobj +425 0 obj << +/D [402 0 R /XYZ 56.6929 502.2858 null] +>> endobj +426 0 obj << +/D [402 0 R /XYZ 56.6929 457.679 null] +>> endobj +427 0 obj << +/D [402 0 R /XYZ 56.6929 459.1385 null] +>> endobj +428 0 obj << +/D [402 0 R /XYZ 56.6929 448.1796 null] +>> endobj +429 0 obj << +/D [402 0 R /XYZ 56.6929 437.2207 null] +>> endobj +430 0 obj << +/D [402 0 R /XYZ 56.6929 426.2617 null] +>> endobj +431 0 obj << +/D [402 0 R /XYZ 56.6929 415.3028 null] +>> endobj +432 0 obj << +/D [402 0 R /XYZ 56.6929 404.3439 null] +>> endobj +433 0 obj << +/D [402 0 R /XYZ 56.6929 393.385 null] +>> endobj +434 0 obj << +/D [402 0 R /XYZ 56.6929 382.4261 null] +>> endobj +435 0 obj << +/D [402 0 R /XYZ 56.6929 371.4672 null] +>> endobj +436 0 obj << +/D [402 0 R /XYZ 56.6929 360.5083 null] +>> endobj +437 0 obj << +/D [402 0 R /XYZ 56.6929 349.5494 null] +>> endobj +438 0 obj << +/D [402 0 R /XYZ 56.6929 338.5905 null] +>> endobj +62 0 obj << +/D [402 0 R /XYZ 56.6929 301.1713 null] +>> endobj +439 0 obj << +/D [402 0 R /XYZ 56.6929 265.568 null] +>> endobj +66 0 obj << +/D [402 0 R /XYZ 56.6929 265.568 null] +>> endobj +440 0 obj << +/D [402 0 R /XYZ 56.6929 238.7753 null] +>> endobj +441 0 obj << +/D [402 0 R /XYZ 56.6929 218.0156 null] +>> endobj +442 0 obj << +/D [402 0 R /XYZ 56.6929 219.475 null] +>> endobj +443 0 obj << +/D [402 0 R /XYZ 56.6929 208.5161 null] +>> endobj +70 0 obj << +/D [402 0 R /XYZ 56.6929 143.6746 null] +>> endobj +445 0 obj << +/D [402 0 R /XYZ 56.6929 115.8506 null] +>> endobj +401 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +448 0 obj << +/Length 3528 +/Filter /FlateDecode +>> +stream +x???????}?Bo??V??J%?8vj?8U??s??rQ$5b?"e3??O7?^:f?<h4?F_hP?\?+?p?X??H?N?J?????? gk??c??<=<~?????????@:A???? +?p?????r??????Z?;j>m<?wuS$????o??XE@%PH? CX-Zm?pb???J S?h?H?B?????,???0??e? ????O?*??|??:^??+t\Gz?X|MH)>}?Mx????y?????}???o??95??0/?k?l???X~3tb?????t?@Z???nSG? ??J???4??f???8?u>KB?6???O?????=?Q\?k???????U?g?????_?#G?6?t]Y????? ??{##?v?I-?4???\8?}]?52??- at I?u???DK?M??|??????;?0???C???nQeh?:??x} ?4F???+????? UG"?xdS?h?9O?n0?E??F?M??!]? +1~AdI?A]/?z?????q)G?????Hf????v???K2????X#&?4??????? R???3?O???\FF?????`?"???.?"??????^??VYk??2??T???$????^x;?c? r???'???!?????#??????A???????M????3?#hi?,c)9?Kh?????Q2?m{??'?#EL??E??%???]%? T??!{6hu?G$????#????????rH? ?!&:?FbZX?*0g?B?ig???GBn. 3O~:l %?^>??A?y??6?c9??"G?R??X:2?[???,?v??????m??!?`yC)&?z?Ry????hT?1?o??,??4???T??-v??H???????????4H.???g???kp? V^a821?~?&??k?$4???h2e?????L?"x????N{??p?????>??&?8??e?|????Qu5?@?M +L^ ?????????@Y?MR??K?5A???????5=?u?8y?7G??P(?b?3EI??!??0????J????0> +O|??vk?02 +? ??e6?xL:]?PO ?S?A?w]?T??*????cQ?B?~????Kv??=*D?rAA?M?s%? ) ?l(??y??tm??("??Nj????n??-??P?hdc?i??p{v?????"K?? ?@??6??u???????[??P??????Lz? \?2IS???"?n??$???_??'?obm?|?3?????????no??N? +??y_????{???wsw????_?k??@???_n? +?endstream +endobj +447 0 obj << +/Type /Page +/Contents 448 0 R +/Resources 446 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +/Annots [ 451 0 R 452 0 R 453 0 R 454 0 R 455 0 R 456 0 R 457 0 R 458 0 R 459 0 R 460 0 R 461 0 R 462 0 R ] +>> endobj +400 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (/autonfs/home/davidk/dblatex-0.3/latex/graphics/warning.pdf) +/PTEX.PageNumber 1 +/PTEX.InfoDict 464 0 R +/Matrix [1.00000000 0.00000000 0.00000000 1.00000000 0.00000000 0.00000000] +/BBox [0.00000000 0.00000000 160.00000000 183.00000000] +/Resources << +/ProcSet [ /PDF ] +/ExtGState << +/R7 465 0 R +>>>> +/Length 466 0 R +/Filter /FlateDecode +>> +stream +x??R;N1 ?} +????? ?f?,?l?Rp}?L2?@??_^??m9o??}??o?xV??C??0??|?? ?rf "??p????W??~???+}??????r??"??M??3?\??!?4K)?~????Vvfm???5~??[G#?6??y GI?7??????????)endstream +endobj +464 0 obj +<< +/Producer (GPL Ghostscript SVN PRE-RELEASE 8.61) +/CreationDate (D:20100125210321Z) +/ModDate (D:20100125210321Z) +>> +endobj +465 0 obj +<< +/Type /ExtGState +/OPM 1 +>> +endobj +466 0 obj +252 +endobj +451 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [450.0885 501.0735 567.9254 511.9774] +/Subtype/Link/A<> +>> endobj +452 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 489.1183 289.1986 500.0223] +/Subtype/Link/A<> +>> endobj +453 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 423.3649 88.6727 433.9998] +/Subtype/Link/A<> +>> endobj +454 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 363.5891 124.9163 374.493] +/Subtype/Link/A<> +>> endobj +455 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [112.4627 333.7011 171.1622 344.6051] +/Subtype/Link/A<> +>> endobj +456 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [174.151 333.7011 228.9948 344.6051] +/Subtype/Link/A<> +>> endobj +457 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [231.9836 333.7011 315.7191 344.6051] +/Subtype/Link/A<> +>> endobj +458 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [318.7078 333.7011 384.3116 344.6051] +/Subtype/Link/A<> +>> endobj +459 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [404.177 333.7011 483.1001 344.6051] +/Subtype/Link/A<> +>> endobj +460 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 315.7684 137.9272 326.6723] +/Subtype/Link/A<> +>> endobj +461 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [112.4627 291.858 175.8841 302.762] +/Subtype/Link/A<> +>> endobj +462 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [178.8729 291.858 241.1885 302.762] +/Subtype/Link/A<> +>> endobj +449 0 obj << +/D [447 0 R /XYZ 56.6929 815.7613 null] +>> endobj +74 0 obj << +/D [447 0 R /XYZ 56.6929 564.6668 null] +>> endobj +450 0 obj << +/D [447 0 R /XYZ 56.6929 535.9077 null] +>> endobj +78 0 obj << +/D [447 0 R /XYZ 56.6929 201.2083 null] +>> endobj +463 0 obj << +/D [447 0 R /XYZ 56.6929 172.8229 null] +>> endobj +446 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F92 158 0 R >> +/XObject << /Im1 400 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +469 0 obj << +/Length 4851 +/Filter /FlateDecode +>> +stream +x??]mo?F???_!?????????7 w???`s?=8????h??$:?4?qw?????????g?????d?????U?/d????H3??Q?(XJ???????.???_.??Y)??-???o??tQ?2?????"?H??tQ???e?/?7?-??\E)]^=6?Gqx}???????j{???7??- +???\K?G$gQ?X1F?4?z5???y?|+~X??????&?8?%#q +???.???.6`?7?$e???%QR???"epg?:?????????F Ih?z?&#?Be??%%a4e?_?]??T??i??7?\u??G?V?????=?????v?da??KI??e?Z????5!???n???q????P???%??GN?aq???b?Z???u?????=???J? ~?"QK??*????O???@q?? +?u??9)Ki9?f%D???0??z:xp???@y? +?9#4??????_?j?kJj?_????~ +%???M?k7????cm???N?k8?Ho???Vk???u??D??_ ??r?k?[??6b\??Q??&e?????cm?o?(a,Ig?????? ??)? ??????6???m69??!?l?????|?:????#?A??Z?}?:??mm6?-?>????????$??@?k??X????4?G??.???|??d?YJjB???8|??t??????8z??e,G???TU?.,??,??IM? +??r? ?5?O???GKcZ,WR!??????p ??-W?A?^n`???8l?)?)?V+??H?y????D?????????s???? +B?2`?? + at K?$`y?$/1?r-?r????????j?(c?EE?\I??G??|!?!???^=?Y5?D3%5!??U??h?????&?F3???PT?lX$?9?S?Y^E3>?P?M4??G??l??&??U4???h?Zm?;??f?6? ????0??h?B?h?Zn??4??h???hf? +????< +?? +1r????x_-??h_ at P?j jJjBP????A +%???M +j5;???&???HPs@??? +j6|0??????C????D?MP ???f??A +??5v?-?&Zm???;)?a?[A +?6A +???i?[A +??A??_?G ???????B?Bn??????W?p?~ ????1!3!??J}iCh?fh???K?^? ] \??????e??! ??, t?)?&YkB +??F?b? R?@S @M???' x?sRh?[k&??%?Z??Xk?$ X$???????????UG 1???0l??2????p??16?y?????J1E??e8M)W?4????~3^??$??&~?t'Uw?!????%1??s?? ?(%u??7x?I??G3????t?4 +>?YN?4??n?HR$?%?JLK!s???????h???????Cp?t??$r?F?,? ??w??}+???M?*??W??~???>E??Q?????ht???-??u????o?{{G??!?6????~?l???K?|x?{?7p??{;???y ?b??(YV??0"???O???/?N?????v+?????C?????????"??????\?A?)?m?F???????.VF??????????????jG????|x?\ ?Lr?v?.3?#??q|???apv0N +???????`??P???'??s??????56??=}??_ ??;?z5?? ^f? '6???H?6????P}??Y? ????c +??????!?????|????y?G???UKE????????z??????? Z*@@????,&q???????C?#??? +?%??$Mv+??H[??*??%?WD?z?m?G??( +? ??'?q*?98?????????\?????C?)?c?????D????C??s????3??5$??H????c???z???*?=??"?????TS&?}n?s??G?m?p:?3]{??V`?? ?u? +??O?v#N?? ?" ??$?W?????@b???^???> sYy??l?t?,d? ??i?#O??N???~??SwF??+??F?+???j/?????+:a=??????????8??S|e?{??$i??9????Iy~?H??a?%?'2O??5?`){???"&i?^B*qx???????0"?L??5???|???y +??j??$!Y????h"???O?}O????r?`?????N???x,qf{qu??q?z????????hendstream +endobj +468 0 obj << +/Type /Page +/Contents 469 0 R +/Resources 467 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +>> endobj +470 0 obj << +/D [468 0 R /XYZ 56.6929 815.7613 null] +>> endobj +471 0 obj << +/D [468 0 R /XYZ 56.6929 740.9713 null] +>> endobj +472 0 obj << +/D [468 0 R /XYZ 56.6929 742.4308 null] +>> endobj +473 0 obj << +/D [468 0 R /XYZ 56.6929 731.4719 null] +>> endobj +474 0 obj << +/D [468 0 R /XYZ 56.6929 613.4495 null] +>> endobj +475 0 obj << +/D [468 0 R /XYZ 56.6929 614.909 null] +>> endobj +476 0 obj << +/D [468 0 R /XYZ 56.6929 603.9501 null] +>> endobj +477 0 obj << +/D [468 0 R /XYZ 56.6929 592.9912 null] +>> endobj +478 0 obj << +/D [468 0 R /XYZ 56.6929 582.0323 null] +>> endobj +479 0 obj << +/D [468 0 R /XYZ 56.6929 571.0734 null] +>> endobj +480 0 obj << +/D [468 0 R /XYZ 56.6929 560.1145 null] +>> endobj +481 0 obj << +/D [468 0 R /XYZ 56.6929 549.1556 null] +>> endobj +482 0 obj << +/D [468 0 R /XYZ 56.6929 538.1967 null] +>> endobj +483 0 obj << +/D [468 0 R /XYZ 56.6929 527.2378 null] +>> endobj +484 0 obj << +/D [468 0 R /XYZ 56.6929 516.2789 null] +>> endobj +485 0 obj << +/D [468 0 R /XYZ 56.6929 505.32 null] +>> endobj +486 0 obj << +/D [468 0 R /XYZ 56.6929 494.3611 null] +>> endobj +487 0 obj << +/D [468 0 R /XYZ 56.6929 483.4021 null] +>> endobj +488 0 obj << +/D [468 0 R /XYZ 56.6929 472.4432 null] +>> endobj +489 0 obj << +/D [468 0 R /XYZ 56.6929 461.4843 null] +>> endobj +490 0 obj << +/D [468 0 R /XYZ 56.6929 450.5254 null] +>> endobj +491 0 obj << +/D [468 0 R /XYZ 56.6929 439.5665 null] +>> endobj +492 0 obj << +/D [468 0 R /XYZ 56.6929 428.6076 null] +>> endobj +493 0 obj << +/D [468 0 R /XYZ 56.6929 417.6487 null] +>> endobj +494 0 obj << +/D [468 0 R /XYZ 56.6929 406.6898 null] +>> endobj +495 0 obj << +/D [468 0 R /XYZ 56.6929 395.7309 null] +>> endobj +496 0 obj << +/D [468 0 R /XYZ 56.6929 384.772 null] +>> endobj +497 0 obj << +/D [468 0 R /XYZ 56.6929 373.8131 null] +>> endobj +498 0 obj << +/D [468 0 R /XYZ 56.6929 362.8542 null] +>> endobj +499 0 obj << +/D [468 0 R /XYZ 56.6929 351.8953 null] +>> endobj +500 0 obj << +/D [468 0 R /XYZ 56.6929 340.9364 null] +>> endobj +501 0 obj << +/D [468 0 R /XYZ 56.6929 329.9775 null] +>> endobj +502 0 obj << +/D [468 0 R /XYZ 56.6929 319.0186 null] +>> endobj +503 0 obj << +/D [468 0 R /XYZ 56.6929 308.0597 null] +>> endobj +504 0 obj << +/D [468 0 R /XYZ 56.6929 297.1008 null] +>> endobj +505 0 obj << +/D [468 0 R /XYZ 56.6929 286.1419 null] +>> endobj +506 0 obj << +/D [468 0 R /XYZ 56.6929 275.183 null] +>> endobj +507 0 obj << +/D [468 0 R /XYZ 56.6929 264.2241 null] +>> endobj +508 0 obj << +/D [468 0 R /XYZ 56.6929 194.7397 null] +>> endobj +509 0 obj << +/D [468 0 R /XYZ 56.6929 195.4818 null] +>> endobj +510 0 obj << +/D [468 0 R /XYZ 56.6929 101.3698 null] +>> endobj +511 0 obj << +/D [468 0 R /XYZ 56.6929 102.8293 null] +>> endobj +512 0 obj << +/D [468 0 R /XYZ 56.6929 91.8704 null] +>> endobj +467 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +516 0 obj << +/Length 4609 +/Filter /FlateDecode +>> +stream +x??]m?????>?????M?)JI8w??? ?;? ?F??f??=?????7???)J"E?b??e??D???]??!?,V?M|????P+*Q-J??.x???=?????Nx'??BK_???O>?Ze??U?(?W?B?BgjQf???????N?p?*;}?~}ul???Iuz???????????(AK?-R ??(K?Y??h?p????????'O?:w$-G]q?+x(??????%??????????G??????Dq???~?9ys??^??UH&?R?W +??j?,_???F???'?H??U?-???????-???\p#WV?}??r??o???J4????h???}??A????????U?m6?4g+eZ?_3? + +??LC???e?o??E??{???????>V???zSYp??P\ +h??W,?Uq?\@?s.)?N. y???P?Jm??(?V.? ?#\ _?????~+?C??}]????C?X????2n#???A6e_Yv?????$?DiK??? ?????h?D???(???"?cm??2Q +??,??'??z +??&??n?`L(Hkd???[) +\?????\?'???i?<+?r;) +;???)?$?0??&???N???A+?~????,V?????????@?(??J?K??????_??bE.?C?N?~?mW$?7?C??n????n?k?Zm/?7????~?????aw?~x??l?O?2a??7u??U3)????p????[uxo???????[!]o????????~???/?g ?M'|????>?&?*??????k?M?6??U+???O?p +?bA??N???_?_}]? ? ????e?^?h2 ??UA?? ?J@?BP??X????Z???? +8?f?Y ?M?????)???fv??cjA-tY??(?9f?????`y??'?Tr???HO_??U Je??P/;?Q?????Gi??3??oL !%?????:5??T???k'@??~??3?N????????? (?s??7R?????X_??%D??????[?k T?r????????,???] f`?????6`?)?[??P~??}??j~?????_???X???ukn*???58??nyA?????Du%L%F??$??????I?bm?O???fZ?"?&w~S?? ????]!??_?t?vV?3??4?g?0???j9mD???W$o??`????>v????? p?]?G:?'??g?j???b?L?I?"?#?????Z! +4R?????T&TI???K6???>??[$????4?'?????w;?&????^Co?N?^?O?w-?? _???d?7m??:???????f}\???????fOg???????i?x??????w???/???v?w?r??qQC??f???????c{e?^?7&E?yWk??M&e??4L_??>b??? y?[?j]?w]au?v?^????o???m???NnP%?i;??iA?37?y????? ?%?J?Tb??????q?B??`?m??>'???Px??|x?E!???^??@prN.d?\JG???H????A;?4?$??? ?? i;?W??}???u8????2?X&???}???)?c?????y??O??(;?????*9U?q??? ?H2????zsS?{?F??N??(???G?7?????o?J3^PK"N?o}m?????M????!(???6? +???+???:??? ?%?[?}xK?????D???-? ?k??w???:?#/??J`G?R??k???? +??S "??&Y ?gi??y*??? ??????????q?8) +???#?O:?? shz>u????T???=?Xo???J7g??ss??W???c?(*???S?P@%?m??Fn^?`a?W?= ???7?w?X)j?\A at m??i?P~K'E!G?GO?G +@?xj>?;?'C???\)??N?B???yr????|???%?~#!??BS??v??\s???Seh?y??Ee'E???6$UF1]??c??r:!UF?]?????2R????(?>? +??Se?^?L?????4?x?2? ??????Se??}??cG??Tyb??Tg??S??7I/C????M?1?x?2?R??Q??Pb??? H?=S ???2~??????t?7????3?{??s|?\??G^eW?*??"??#????VNSucc???>OP???j?=M??Y???6???t?=M?Po*Y??-t??qT??}?t??s&M?0;???,{U??V +O??^%?TnN?_~??UgP?r'D???.$S?]???y??8!M??]??a?Ir????1f},?SKg???0G????I???c~????m???d\e^f+D?u%?b?f2???R +???l.w~z?+?a????Y1????B"K?^`??F? ?g?5?I??CP????-D.?{?n +???%?H???l???I_????????uM??U mZ??>???o??????5????????sk??????k???P??m??a?n?&?????????T8????&?:????c????xrn?`g?Bz???N1<?~??9??_b>GJ?F4?o??(?Vn???H???? ??R$?[9=0?U??k????k5??????fJ????o>???tb?????A?W?V?y>?????B????MCN*?????W???85+R?&~??0^??i8??+4@?"9?B?#?>?E????????I??^?????&?J??F?d?}?NTB????wR???=???????]'?(??s?(?s?>"?D?)NE?????Pogx?????v???0?Zz7cL0???/ ?? +x??& +??1,62t????|????[k ??Y)??y????Pj????n?? +??96?96ql????????Onu?+???p?H??&??wl8?H/???b?????mPl?? ?J!g?6??/???P?+'E??'(57t??????? +(?:|Dd? ? (z?t??? Tv?Z?~??iKn>cb??? +?????\???b[)??!?g?????-???C??aQ?????s??'3?TY?/?nu^?????2G?V???p?{??????\?^?{Y7????h?n??????`.?]?;{??????? {??q??????????????I?>/ +???????P?-lw??????p??2?F??J????8C'p?d?n +??9I?^^????N8B?w?A??C?"D^*Vr??? ?He?*q?/?jr??<o???m???h???'8h?m??n3??2??D?Ho?u?}?h?k^9@??~/?????}??????~??#?0~?R?g???J??v??????W?s1d!?1E??'EA?r2??M4z?E?rY?????S??^???????/? +?3????S???????\A???qr??}?N???.jR???K?t?yR??_(?tQ?/uB? O?3?(?>??9&N??IM??7EJ ??GF?tJ?A??#(??C`?e?? ??.??8????? ??????=? z?&??????DH/=?j?DQ>?*g2?I???C??m??;??????X[b??f:?(?v'O?Gz?-?QZ?e?aZ?e??b?T???? +?gt?u#2j Qq??M????epE?5???eyw?~??-?mM??P?????????:?2>??w?&?]????A?k9N +}???????yY??W?B??????[??x?Z'0???K?>`?????>?,??b??x+?'X??C?Rse??s???q?l??sN?y3?X?????x}?????v6@?'????????`@`?????????8p??/??}b?]o??]o????,?toGJ??}=+???]?D?$}Z??vi!n{??T????)?F??$/?(??~? J +?????x???o3?iH?TN???B??}?????????P???f???iAd?}?(L`V-??? ? ??i5??]???k???_X5p????yR??x?????&[????f?K???? ?%_?oN? 37v{????7??7'?????h???e?endstream +endobj +515 0 obj << +/Type /Page +/Contents 516 0 R +/Resources 514 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +/Annots [ 530 0 R ] +>> endobj +530 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [473.4009 576.4484 565.4347 587.3523] +/Subtype/Link/A<> +>> endobj +517 0 obj << +/D [515 0 R /XYZ 56.6929 815.7613 null] +>> endobj +518 0 obj << +/D [515 0 R /XYZ 56.6929 760.0646 null] +>> endobj +519 0 obj << +/D [515 0 R /XYZ 56.6929 749.1057 null] +>> endobj +520 0 obj << +/D [515 0 R /XYZ 56.6929 738.1468 null] +>> endobj +521 0 obj << +/D [515 0 R /XYZ 56.6929 727.1879 null] +>> endobj +522 0 obj << +/D [515 0 R /XYZ 56.6929 716.229 null] +>> endobj +523 0 obj << +/D [515 0 R /XYZ 56.6929 705.2701 null] +>> endobj +524 0 obj << +/D [515 0 R /XYZ 56.6929 694.3112 null] +>> endobj +525 0 obj << +/D [515 0 R /XYZ 56.6929 683.3523 null] +>> endobj +526 0 obj << +/D [515 0 R /XYZ 56.6929 672.3934 null] +>> endobj +527 0 obj << +/D [515 0 R /XYZ 56.6929 626.7955 null] +>> endobj +528 0 obj << +/D [515 0 R /XYZ 56.6929 628.255 null] +>> endobj +529 0 obj << +/D [515 0 R /XYZ 56.6929 617.2961 null] +>> endobj +82 0 obj << +/D [515 0 R /XYZ 56.6929 551.6516 null] +>> endobj +531 0 obj << +/D [515 0 R /XYZ 56.6929 523.4973 null] +>> endobj +532 0 obj << +/D [515 0 R /XYZ 56.6929 472.4201 null] +>> endobj +533 0 obj << +/D [515 0 R /XYZ 56.6929 473.8795 null] +>> endobj +534 0 obj << +/D [515 0 R /XYZ 56.6929 462.9206 null] +>> endobj +535 0 obj << +/D [515 0 R /XYZ 56.6929 451.9617 null] +>> endobj +536 0 obj << +/D [515 0 R /XYZ 56.6929 441.0028 null] +>> endobj +537 0 obj << +/D [515 0 R /XYZ 56.6929 430.0439 null] +>> endobj +538 0 obj << +/D [515 0 R /XYZ 56.6929 419.085 null] +>> endobj +539 0 obj << +/D [515 0 R /XYZ 56.6929 408.1261 null] +>> endobj +540 0 obj << +/D [515 0 R /XYZ 56.6929 397.1672 null] +>> endobj +541 0 obj << +/D [515 0 R /XYZ 56.6929 386.2083 null] +>> endobj +542 0 obj << +/D [515 0 R /XYZ 56.6929 375.2494 null] +>> endobj +543 0 obj << +/D [515 0 R /XYZ 56.6929 364.2905 null] +>> endobj +544 0 obj << +/D [515 0 R /XYZ 56.6929 353.3316 null] +>> endobj +545 0 obj << +/D [515 0 R /XYZ 56.6929 342.3727 null] +>> endobj +546 0 obj << +/D [515 0 R /XYZ 56.6929 331.4138 null] +>> endobj +547 0 obj << +/D [515 0 R /XYZ 56.6929 320.4549 null] +>> endobj +548 0 obj << +/D [515 0 R /XYZ 56.6929 309.496 null] +>> endobj +549 0 obj << +/D [515 0 R /XYZ 56.6929 298.5371 null] +>> endobj +550 0 obj << +/D [515 0 R /XYZ 56.6929 287.5782 null] +>> endobj +551 0 obj << +/D [515 0 R /XYZ 56.6929 276.6193 null] +>> endobj +552 0 obj << +/D [515 0 R /XYZ 56.6929 265.6604 null] +>> endobj +553 0 obj << +/D [515 0 R /XYZ 56.6929 254.7015 null] +>> endobj +554 0 obj << +/D [515 0 R /XYZ 56.6929 243.7426 null] +>> endobj +555 0 obj << +/D [515 0 R /XYZ 56.6929 232.7836 null] +>> endobj +556 0 obj << +/D [515 0 R /XYZ 56.6929 221.8247 null] +>> endobj +557 0 obj << +/D [515 0 R /XYZ 56.6929 176.2269 null] +>> endobj +558 0 obj << +/D [515 0 R /XYZ 56.6929 177.6863 null] +>> endobj +559 0 obj << +/D [515 0 R /XYZ 56.6929 166.7274 null] +>> endobj +560 0 obj << +/D [515 0 R /XYZ 56.6929 121.1296 null] +>> endobj +561 0 obj << +/D [515 0 R /XYZ 56.6929 122.589 null] +>> endobj +562 0 obj << +/D [515 0 R /XYZ 56.6929 111.6301 null] +>> endobj +563 0 obj << +/D [515 0 R /XYZ 56.6929 100.6712 null] +>> endobj +564 0 obj << +/D [515 0 R /XYZ 56.6929 89.7123 null] +>> endobj +514 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +567 0 obj << +/Length 4426 +/Filter /FlateDecode +>> +stream +x??]m???????( +?[? _$R???I?A???h?4??vW9?????]}I??HQ?wW?6Qd??<3??H???????r?xI?UAr$8a???^????xE4fc@????????U?JN???n?)??? ?J*V7?????????<7wmys???K{<5????????*????LP$-VBP???C???(???S?????*it%A,?_?*?????j' +?? +??,??Y?F4+???*'??qj????\?e?h>??p?O????j?%??$?V8????+?]#?6R@!D/?(*??X?+???^?Y?????%?Z4)?~???????? + ^??W??wSmTd%"8????o]?j]??,H????????|7??D??r?J ?3?o?>?o?6???Y V ??biL/??OD?s Jy????\? ?%e?gG?????L?VH~AiJ7?t;?U{ ?9?????v?J??&?:aj? ??7??S?=?Ni??.?????4??"?R??H???09??????????(?L?x?a?XT?_???=Y|,"??M?Ej??V?9???:q(:Eb? ??O`??R ?I?????\z?L?5???9?[?5??????i~k??f?7????Q??/???smY????p?f~W???m=????????????[??Z?????iE?????l???W?"$D??k?N{??v??N ?K???Q%??M +9-H???q[???6??p?!???9?P??9)? +9?q&_?j\???z??9cs?=?9????R?????~P?W:R??????m?)r?+GF7??T???2a?E%HCi?6S5?`??????LE?U?w??\*?q\???r?#LZ?j?4?????~=n?x?????o????/?:2?!?E?(#B.????,???IZ?H??/?a4?Pb??n=???q?O??`*c?Z????]??S??\???W????c2E?,K4?D??????Q?J?%???y?dX?'??3???_J????7r^?????~?v?1^SL0?)??%?????k >?????J????????????%??dKgx=???r?c9?wbAs?????u`^???F?rA??????????D?1?????6??@^??\????? +Z?A%?5????????>7p????Oh?UZ>y82???&?XB?H?,!???\?@??s?S?T?:???w?;?e?????`? U??v??5.? (E??O?h?? ?d????????@?????? ?@j7??k???@??G?uXpti?K +??2'?-???????x??(???6?k??.<$o? +:5A?????U??Y???w??j_??I?N5"??4????C?P?????K?7?S?????a?????G}u?W?y????;#?0.? ?e??7?uG?<1??!???? )X/????c???b??$L??T?*J??Y?u7&?*2D????R?*3DK????Uj|BE???c?.d?tu?? ??0?#m?|&s?4}H~O?r???}xf?,??V?]??f??R?z*??s?? +X????#1<h#c?7?5c???? +?H[?u ????e?Y? ~ ??????FE???D??? +n??C[5??????)?tw<=VC?'[????:B?Mj?]S?u/\WE?7}-???'??q?D???9k?d??d$??;?>6??2(W)????0??????????zt???n???v??????????9?xG?3??n&?w?????9P9c8???e????"?E6?;kH?B)?? =?aw$???.?De?0??=l???c??8????&?6)?AVB5??&Y????v?%x{??*?hU????E?`?????hKr?s?Y????%%?g1??R$6?-*Yu??O??Y?^?? +U?Ig????vg?S?:?=TI???#s??A +Ln???:Y?_WI?gp?zP??%??H???:?p??"2?#??H?\W??:[?TY?????K??2Qu???UG\y???"UG??????z?`A?B?J???????nT?c?:??:- ?)???X??B??x??W?3y???^???dYC}???x"?? h^?????My??q??"???7D? ??,?? ./?R???S?]W?3?,j^?????My?5?)??????O??MyO?fp?j??wH?gQ=?H??#W[?l?@????????c@?R?=???aj?w??'S?}?)? -?sR??`S??&?????????? ??????m?????d?;h?p?? +?M??-.m???F??W/?g9????y?d?PY???*??Bc+ ?"F?O?K??DX??????K??'m" +???Hk?(?u~_]??~??h]????fz??30O?????????56?5:?.$?-GO^~/?uE|?????????b?> endobj +568 0 obj << +/D [566 0 R /XYZ 56.6929 815.7613 null] +>> endobj +569 0 obj << +/D [566 0 R /XYZ 56.6929 760.0646 null] +>> endobj +570 0 obj << +/D [566 0 R /XYZ 56.6929 749.1057 null] +>> endobj +571 0 obj << +/D [566 0 R /XYZ 56.6929 688.5546 null] +>> endobj +572 0 obj << +/D [566 0 R /XYZ 56.6929 690.0141 null] +>> endobj +573 0 obj << +/D [566 0 R /XYZ 56.6929 647.1948 null] +>> endobj +574 0 obj << +/D [566 0 R /XYZ 56.6929 647.937 null] +>> endobj +575 0 obj << +/D [566 0 R /XYZ 56.6929 636.9781 null] +>> endobj +576 0 obj << +/D [566 0 R /XYZ 56.6929 626.0192 null] +>> endobj +577 0 obj << +/D [566 0 R /XYZ 56.6929 615.0603 null] +>> endobj +578 0 obj << +/D [566 0 R /XYZ 56.6929 604.1013 null] +>> endobj +579 0 obj << +/D [566 0 R /XYZ 56.6929 593.1424 null] +>> endobj +580 0 obj << +/D [566 0 R /XYZ 56.6929 582.1835 null] +>> endobj +581 0 obj << +/D [566 0 R /XYZ 56.6929 571.2246 null] +>> endobj +582 0 obj << +/D [566 0 R /XYZ 56.6929 560.2657 null] +>> endobj +583 0 obj << +/D [566 0 R /XYZ 56.6929 549.3068 null] +>> endobj +584 0 obj << +/D [566 0 R /XYZ 56.6929 538.3479 null] +>> endobj +585 0 obj << +/D [566 0 R /XYZ 56.6929 527.389 null] +>> endobj +586 0 obj << +/D [566 0 R /XYZ 56.6929 516.4301 null] +>> endobj +587 0 obj << +/D [566 0 R /XYZ 56.6929 505.4712 null] +>> endobj +588 0 obj << +/D [566 0 R /XYZ 56.6929 432.9649 null] +>> endobj +589 0 obj << +/D [566 0 R /XYZ 56.6929 434.4244 null] +>> endobj +590 0 obj << +/D [566 0 R /XYZ 56.6929 423.4655 null] +>> endobj +591 0 obj << +/D [566 0 R /XYZ 56.6929 362.9144 null] +>> endobj +592 0 obj << +/D [566 0 R /XYZ 56.6929 364.3739 null] +>> endobj +593 0 obj << +/D [566 0 R /XYZ 56.6929 353.415 null] +>> endobj +594 0 obj << +/D [566 0 R /XYZ 56.6929 342.4561 null] +>> endobj +595 0 obj << +/D [566 0 R /XYZ 56.6929 331.4972 null] +>> endobj +596 0 obj << +/D [566 0 R /XYZ 56.6929 320.5383 null] +>> endobj +597 0 obj << +/D [566 0 R /XYZ 56.6929 309.5794 null] +>> endobj +598 0 obj << +/D [566 0 R /XYZ 56.6929 298.6205 null] +>> endobj +599 0 obj << +/D [566 0 R /XYZ 56.6929 287.6616 null] +>> endobj +600 0 obj << +/D [566 0 R /XYZ 56.6929 276.7027 null] +>> endobj +601 0 obj << +/D [566 0 R /XYZ 56.6929 265.7438 null] +>> endobj +602 0 obj << +/D [566 0 R /XYZ 56.6929 254.7849 null] +>> endobj +603 0 obj << +/D [566 0 R /XYZ 56.6929 243.8259 null] +>> endobj +604 0 obj << +/D [566 0 R /XYZ 56.6929 232.867 null] +>> endobj +605 0 obj << +/D [566 0 R /XYZ 56.6929 221.9081 null] +>> endobj +606 0 obj << +/D [566 0 R /XYZ 56.6929 210.9492 null] +>> endobj +607 0 obj << +/D [566 0 R /XYZ 56.6929 199.9903 null] +>> endobj +608 0 obj << +/D [566 0 R /XYZ 56.6929 189.0314 null] +>> endobj +609 0 obj << +/D [566 0 R /XYZ 56.6929 178.0725 null] +>> endobj +565 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +612 0 obj << +/Length 2914 +/Filter /FlateDecode +>> +stream +x??\k???????0?A T?y?\h????K.f?C???????+??`E2k?+???????1C?????{??p??WA??? AL?? ???o??? +??#n4)? +F?R?]?LR??????_-?o)Gk1?hC??b.?_??@?????,???? ??????????~?? ????Hn??`rT??a?8.?p?V???^ +?8m???uo??lOF??o?l??O>^?Ip??)??7c]Iq?8?"t%C]'??40V???z????????,!D]?C?LA?44+?p?~??zXO??????F??@X`??7? 1?i?Y{?/???q??pNz??9?????*r?9???i?*?YwY???a??L??????g??v-?aw,#J!*??;????Cj??*?pN???y?????o??|(?JS)O?+$??)??????????x??P!' +?M??T????{?*"? +????%?s??]???????=? 8???t??H ?#3???HH?Ss?n?????&????eF1??hS?UR|?t????k3????%?AE +"??t0dd?[>?h???T?\&?;n????R??6j??!?? 6?????^??^IW??Dz???M?w????`%??5T&lw7Y]R!.`E???a=]?f?4?f?]?????eX?A??>?|2??3N???!oq?X????.?/? KB?#"!???s0?;,vq"?a??0MG%?r???&0????r +???| Dn?s????4??$7??????XF???????c1?=?? ??=uy'???a??G??????:?H??e??e?]l&??nd??E?%CF[XYt????1j??DIu?????F????G:=??.,??7p???:T?M??j?? ??J?P??Z?>??bO???s???FY?o?U\F??????d+???F?? +??q??1x}?l>Du5&?2???????#Fc??PT}?{??h?I?qJ?,?h?:2???????K:;??#?? /?q?K?g?????mPt9????n?}k??+?j +?????????f???`If????X??C?=z-u+?k*/???b?+??CKu?-???aL???????e ???????y?_????%???G???????N??b?.J{????????????aWoo?? @a?R%i:?]??+???Z?????U*??J"?ISzP?22????R??*?hX?c?`???D35?? I???r????h???\????5?E}?j?????b?4h???h?;B?@???&&s+???????Z??6?M2Xo?????jUY.??v ???/???C???[]H?HD{zJB@x:?(???O????K??h?z??A???)???????2?V???;??9?u??R???#u8?L????{????=??]YFVD ?I?s?????|?9????n?}??-???!?YS?????????<????K$?6??T?sh????H9?c?F??ss???????p?/???I?1?sR?????S})??fSO??~??????!??c? Mr?k????????y?k2%0h*?s?3??0???????Q;?uBG???c?????~??b/?????m??G9???pq8???nI +#?????m$2A? ??o?Y]?? tm??r??????tV??vB???i??vX????bJ_g?0?Y?????>? gB2??]K?G??k???r????r??}???YC?? ??&??d?rh????{???y???+??#N??eC???pA??X?s?>^?:?8Q`??t??D??o?:?0?????arA?cP???v[?*(?????V?K?m???????????]?,W?]iwU( 7?z*\??`?&]????? +?u????u{???\3???um??v??m?X?z5p???F??j^???9???? +??.???)??Ny0?8?b&=L??t?]?]?F?G?????x???H???a????????'?\-?~????,rr l??T?;?6Y??/>?{??)??????B????QY??r???,?>?jf?????} /&WVc~g???VNJ{V?'????Pw?XR#?"(??s?W???d??id-? +a?x?Q??????Y???I?)?~LP??+???????M.??]????????~?ar???8F???9?8-??M????e?i +???M???*:w?M????mu???z?'i=?~??d?H?rO?a?Nx?????C[>?H?T!,?'??O????H N???????L?n?h?????S?endstream +endobj +611 0 obj << +/Type /Page +/Contents 612 0 R +/Resources 610 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +>> endobj +613 0 obj << +/D [611 0 R /XYZ 56.6929 815.7613 null] +>> endobj +614 0 obj << +/D [611 0 R /XYZ 56.6929 759.0684 null] +>> endobj +615 0 obj << +/D [611 0 R /XYZ 56.6929 752.3934 null] +>> endobj +616 0 obj << +/D [611 0 R /XYZ 56.6929 706.1021 null] +>> endobj +617 0 obj << +/D [611 0 R /XYZ 56.6929 707.5615 null] +>> endobj +618 0 obj << +/D [611 0 R /XYZ 56.6929 696.6026 null] +>> endobj +619 0 obj << +/D [611 0 R /XYZ 56.6929 685.6437 null] +>> endobj +620 0 obj << +/D [611 0 R /XYZ 56.6929 674.6848 null] +>> endobj +621 0 obj << +/D [611 0 R /XYZ 56.6929 663.7259 null] +>> endobj +622 0 obj << +/D [611 0 R /XYZ 56.6929 652.767 null] +>> endobj +623 0 obj << +/D [611 0 R /XYZ 56.6929 641.8081 null] +>> endobj +86 0 obj << +/D [611 0 R /XYZ 56.6929 574.5297 null] +>> endobj +624 0 obj << +/D [611 0 R /XYZ 56.6929 537.5329 null] +>> endobj +90 0 obj << +/D [611 0 R /XYZ 56.6929 537.5329 null] +>> endobj +625 0 obj << +/D [611 0 R /XYZ 56.6929 510.1788 null] +>> endobj +626 0 obj << +/D [611 0 R /XYZ 56.6929 476.3408 null] +>> endobj +627 0 obj << +/D [611 0 R /XYZ 56.6929 477.8003 null] +>> endobj +628 0 obj << +/D [611 0 R /XYZ 56.6929 466.8414 null] +>> endobj +629 0 obj << +/D [611 0 R /XYZ 56.6929 455.8825 null] +>> endobj +630 0 obj << +/D [611 0 R /XYZ 56.6929 444.9235 null] +>> endobj +631 0 obj << +/D [611 0 R /XYZ 56.6929 433.9646 null] +>> endobj +632 0 obj << +/D [611 0 R /XYZ 56.6929 387.6733 null] +>> endobj +633 0 obj << +/D [611 0 R /XYZ 56.6929 389.1328 null] +>> endobj +634 0 obj << +/D [611 0 R /XYZ 56.6929 342.8414 null] +>> endobj +635 0 obj << +/D [611 0 R /XYZ 56.6929 344.3009 null] +>> endobj +610 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +244 0 obj +[94 0 R /Fit] +endobj +291 0 obj << +/Length1 761 +/Length2 1025 +/Length3 532 +/Length 1573 +/Filter /FlateDecode +>> +stream +x??RiTW?S +uA???(??l A??DS?" ???????aB?A???j=??? +?????D????w j?n(????S?????y???????????.A?PJ??;???`?\?????1X?`"F?S +?_$????@?x?b??X??`?`B?FbI?p +f????DIL??@?P?PCs(5? ??8@?V????S ? +Q??(?????? n?&?$???4???+?B2?\?d?-%pu@????I?? ??????\?S?g"?^?>??VG4?:?-??hu$??@!???F?7???t??U??1?ORC??????r?-?8?~?$[??8=Z6???????1j?i%LkX?W????i???|??????[??*?????????6O^????u&??Cap?r?9 ??'? ???>??i{n??9I??.% ?~?.0???T at KzM???.,s??}??Y??'???l?,?s??????????=??H}f?`?4x?????Kn?{Ou?Xc?`??J???D4[?F9?;???h?$?5$o0j?olK?K!??W.?*hz?{??q????6?q??W?Qm??EN2??<Z??v??b?????9hd???Uyih?jM?#???2Q?C????uO%??(7??.??????GY??W?????n/v??~!PEn??????? k???~????k???8????????nia? ??%?g=?\?(+f?i?'??1?'?O(?!)B??*????L?endstream +endobj +292 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 636 0 R +/FirstChar 45 +/LastChar 45 +/Widths 637 0 R +/BaseFont /RZVZYK+CMMI10 +/FontDescriptor 290 0 R +>> endobj +290 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /RZVZYK+CMMI10 +/ItalicAngle -14.04 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/arrowhookright) +/FontFile 291 0 R +>> endobj +637 0 obj +[278 ] +endobj +636 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 45/arrowhookright 46/.notdef] +>> endobj +288 0 obj << +/Length1 753 +/Length2 637 +/Length3 532 +/Length 1177 +/Filter /FlateDecode +>> +stream +x??RmPTU.? ??? z?!????,?? +a??R??s???ra?^???]??Dt?L???/????PlG??0"? ~,H?R j u'?Y????s????@?T???~???+]C?,wb?%??y?~??h?^??e?~?8?3?????y7?F??'sb???joG??V??? ????em??)z???yI-????b?q???????{??????_??U^8??nt??ZS?T"??+x?|??;?L?????Q??.????'1???????{GSJF??[???;"O?h?sZ?qN|???E?,2^????j?????|??,nQ^s??Sw??2???Y~??KyI????+o???????K?.??1Y????>?,z?g???5t?]???m? ??!???j}??M?I???[??-??2? +?i?oIV}p?&?????K/???> endobj +287 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /CAGRTG+CMSY10 +/ItalicAngle -14.035 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/arrowleft) +/FontFile 288 0 R +>> endobj +639 0 obj +[1000 ] +endobj +638 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 32/arrowleft 33/.notdef] +>> endobj +640 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozeng e/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis] +>> endobj +157 0 obj << +/Length1 1612 +/Length2 17647 +/Length3 532 +/Length 18565 +/Filter /FlateDecode +>> +stream +x???eT???%?kp????wwwgwwwwwww ???=@???{Nw=????????YU?f??Yk?EA??? djg ??uf`ad???l?]???le???.??Fv + +G??3??V??? +??D?&VV @????dn? ?VS??????/??!c?????? dn ???? +?????:???????-?3?5 ???%%/???WHm??F?Eck? @d?u?????^L?lMA?????K? `p????n????q????6 '??????????o?? [k????????????????`?vN?N&? {g?????????la??On'?_7???o??????%???????d?p?;???09?[y??????/.N [??b@p?9?Z????????;?U'????????_?????8?????f?,?s?8??m?E`?gP?l??,???????O?+??_ +??gfh??02????????????P??????'????-?????O????;????B??X[????_0??7?@??cm??? +7?Y{?6?g???$??p????6C???? ????6???A?@SE???????o??eW?5:Z?l??W3 ,????S??X???z??????I??H??????('?L??w????j???a????(E???-???sx1?=? ?l??? ??????? ????rF?? w?????Y?U????k??0b?&v????????????_??&.??U????[??\?k??@w? ???? O?ezV?s=N?????`? ?H?}Y?jq??]?_z?.W??{]c?4?G??????Ci???~lk??T?u??@!?e'?Q ?~R??F??????6???????~?;???.6G??g2?BL?'{d_???8?n?f0???? ????'????#?}w??t?q??5z???)???#md_? ?m;e???3:x??%??5?o???x??????>7\(??px[???g???f?`?F~A?R:?{????? ?-??(u?5???R03?F?T#???;Qx???X??s?m?R??5???????.dM????p?[????Z8????DL????j?OH??\(yt?^G??'T??=?Di? ???25??u??.?>'???t?tX,????r%} '?'C?6^??????q?? Fm???:??h?]?|n?????????v8e?V??/e???????5? ,I???x??"?^&O??8*???vj?4????Pv?[????? e)??t?f?T??5^??6?3i0?????'??e?X???+?6^{2? ? +??_??6?k?y??????*=u??<8??m'?X]r$?#z?????????%??????}w?E?1B?m???Z.5|???c??????lY;???s~?j_??x??2?U0\:??4O????L??i?w?3HV?8c??&'Oc?Cw~?>???6??a?|-??????????G?`2?? ?dJ???*?D?i ???????p?2XA????{3?Z?W????d???',r????]?'fB????*?p}H?\l?????+j??f??$(?@?????????U?????k?JG??X=? + ?5K^Jm? +?5? ??%??e????????z? ?'?e?T?????????????cI'??8?? +?o+aR??`U?Fo?a,b?^????!?!'=?;???<>?n1????&????>??oKZ??g?????x1??Z?A??? e?u??#??8??a????J1?7?Q?m +?I???gz???? ??nM???n?*?Z%CH???!????Ro?q]???G???j3c?{O?JN:m??u??EB??}e?????U???,????????i#?rW??n?y?? ???pu?p?????i???,j?Ej?????9?S??Ea??$&R0V?3P?F??}l3 _8+St???R?JDC??4,??#P/??????V????q:o?2???? |,??????.???#????s?}?7{J +|?9??Zb?Zb?~??,6W??1?Sp?v?????s~??????wR???W$c?`;??~S??????G??6T{i/?2xs???????.??%?4I|??f?H,GiKVr&F? h??t?????????v?X(???'m?????>? =6? E???-???bv?djlhK?O? +??a??F?]?;????4???_?\O?XU$?MAW29??????????"8????!]j??'^#_j +?Y#??Be?????? X|?j????v?k?A??8?w?x?????z ?????l??B??*w?k?i????? ?J?}??@Fe0ua??T?m???a???\G??r??o???x???Sp?O?8w+Zl?#2Z??????????%,r?>??+??????N?~??Z +??#?jj1???0|<????N"?'qK????y?x?K>~E??gb??U#?M??N????,?"CC???0?????*+?/??????????L???|????gLG?r6?!A)??w?P ?k?7?????y?(?m????????)???S?EB????g?????j?C+a +rcsp"}?4?????r????oL=0Uuu??????wS???8????%?,zg?$?????H??eV??M\n??=??3?? ?c:??????Qg~;D7?Ol??x?~?N???}????]AR????h?s???AQ?-?I^?Jn????YNP?Vw????0x??????C??Xh c?s-l +Y??Z??h?c?|#???ZW??4????????9??? ??*??????^>?Zd?3??m???e +??Y?/?Q@?k??xbV??O??7???2 +?????Z??t+|A???E??4???k??B?`?tH ????f8??)]V??????6??jT3?|?)?w?D9???ac??LQ??g?kK??61w?Xsm??_??F.??U8vzU9eb?f?}&? U?,????????=4Srz???|?.???}8??nYjt? ?1??h?;j35% ???X????,??????&??? #?~??0i$R?{??kpd??c?N?-O???????&F????wm'2??9??V1???xu?a??6?????Ow?+??SG???????%??Q?>h?r?P?'s?5?Xo?F?W?>??]???-?I?~2+?d?H? ?????8=7?ET???=????????5?t?x??U?7'?,?I??0~?X4~?????y??_zO?]??@?P*I??????^????_?}??????1LSzH?-??w?G>?????y?>=?Y???a?aD at +???fQtj)??7}????w?8I?;? @,?d?mu2??m?Dh????_,?????n???,???Z=e????q?\???U=eF????t????????9??'Uu?a???nw??? +??a`?r{l??fP??!>6?r!?G U"2omE?y???0????6@??s?0????C?~1|???z???? +(l??(W?;????u????#??Il?8~??I???1???????7;J????H?,9??????a5??eQs????!???.k?(???"? ??N??03?Y??p?A???y0?qsG|?i?+???>3???E>?P???0?????Y????d?F?.< +El??Vk{?Z3??3r?j?6??????? uy6!???E?k9m?|[???/?F??77?????^:?X?????yC????|k?<&??9` ?e2;? 4>????d2???y????i?5H* I1???hEI-x?A?6??jc_??&????&???:??k??`b????-??w???q?Q.?~fhP??)[??|???-?H????X???eo?x????]*)iL???????lr~ ?T??>>^H???~.???S?AM??5??q~?_??]?????????s?f?k?Y?8???????????f?)L ,??i}?9?? ???(????}?JP?V\??Ew??ID(??7???M??d??e??DadP??$?3??^~2V?.?Q?*??xcZ?sK!UAa???3 "?G?? ?.sR?6??>)2/{?;8??m???q|??$u?Fr?)?0????|??F???????dov#?tF??:????o_\!?j?E&??Ja?" ???2?3??7??L?????? ?????'96?? ??;???G?#????????"??-mT?x? +?(????q??+??F? ??X?A96Na?q?n;??m???vd4?Z???g??-???? C?H?????? ?7????;?L????????)?f???!wl????]&?]?k +? +?????I>{t?a??>??rW??ir:?(?f{????0?Z?#??????r???? +??r?9? kV? +??? +j??C???SW??&??'? ????!?byp??(?~ ?m?e%K^yr??2?s????0Cj??\h?d5?-?N?????EE?RC???q???????\ ???mN??$P7?????? +5???Auf??_*?^?? +???E????i7?H???'?[J?e?B?!???*?2$???L???j ??1????Y???e?y?f/y???????7??j[5??uU?&?e??}?(?????w|??2?????"?R+?c??[Q??< W??"W????}?E?????hE??? }{?IWt?'?mD???v??'c^?rn??"H|?"?\?????????^~???;?v?N?#>U^v +??g? ?=!)?h?/?F???????zo?e?S???????P?b??m,xWn?#???- :F??}?r G?>5.?:hg?@G??>? r???6f?xB?]? +?S?J????f?@?J?????;!H??})??S??|?????/???sr?4vO?Ok???:????kZ??~?????7l$??/??s?}o??????????x??%!??T?V]?Su??0ifr?s?(,???sc???|&????/???_*??Z/???2??P??? +??pN +K?ri????r?G?i?N,n??z???C<7?j?????????*???h??B?B ?Q???7?wT?k??.?t ??dF?\?G?'?eh??#?9???u(2;??????Vt?N?????y????F?e?????y?Pn???U?5Y???~?P?CY?c??u6?W???3}-o%?x?}?M+?????~O?&???u??| ?Sy????l?P??> K??U???)vW ??5WI ?k?V???2BQ?XO>?\,???>?%?.??D??+a|???U??;??????/?I? ????l????z??0???6?[???R]*?,??)??e??V???%AD??b??w?f6??f`?_????9??????g l?????Z??v?p`?G??????>3gu0??f??? 4?X?`?mb?}?a +?2o?tK? O)x?U??/???=??d??? ???T????t??????)????]??6???|?q"??!?0,et2e??W2 +???????F?=GY?`?]??M??>??@??Dl??? +'Z???????f?0???Q??? +???E??J?s?+?u??? +o?????E???l&??????A?"??D?h/rG?????q????0??????yt?r????K??P???????+?(??7l?????Y?F a???? +Ao?X?I2?l??[z ++?\?0?G???2??2?Bz??%2dI???e??NqB?Y=????1?#U??|e?OP??????w?(???d&????o?j???8???0?????8???:`[n&??*?'Q?Si6)?*?tm?2?\9\nW??r?b +7?$????mu??9?r?!??m?S_ +%q<@?S?q??+??????Fj~????z?O?iy?K?F??t??;{,?@?X??????????k????d=Y4??????=?R??? ?.???? d?`Nj8+7?sU?H??E"\? +?$??'??!?? +Uj???NsT0_?j???/?? ?0?v?VI(?S8???7???-U?{US??L??????F?^?+)g?? +c????A???=?A???*??p*?????s^???M-C-x??????o?%(EU??L}????I????a????????????Pb?wB???K?'p??Dz0?X?q?F^???s??]O(w?????%?32~??s>/GL?????Pi???:S?X?g???pvg??????? ?-??V???O?I????? Q???,L?;?d?}? +??K?/5f?C&????z??&??,???+??=}6|yE???'?g?EF?????{??????!??)?)? a"??#p??C??!??a???@?a[?o??3 +G?|?5lv???ze??]??%P?$RS?HF???f?Yz7]aq?":????m?p?s"?????N????E?=0j?W?`O??%c?.(?A???2???????}??n>(??=??Lz?????FB8b?????_$?St????????$?9??(H?????q?=??u=? +??sk?????[)??[? 82??p?? ??C???U???w?????)?E???|D?F?K??^???i~?o?????y??X???I???8D?x?a?? ?_????C?T?&??-?JQ??f?B?????C?5?????B?V???N?lx??a???r??6` ??!?=?? ??6W?ez???9??p?XB?u?FB??? -?? ???T,u? lC???t?X^r?#Es??$?zyW??n?s?????C??l?]???2?.*??D???p??&??"?1t?=??8??L?~#?u?F??????X?8K??U?)?????L?G?U??O???????\????oh0'?:]8y=??@???????Dh?A?????-?6?(????WIX?,=????64???+!a????????L?a????{??V???4H?,?s?pQe?????????B?wZ???3i??'???????j?}iZ?(?LI????H??Es?????[?????O??$l??B?G???9???u???hs?i??%?z???????`;4(??A???d??u +"?{I????_??P???|"?'@?????K??)?Y??????#n???|jm?,=?%???M +?d?????P?a&?W????I[??I/,?6?9?b,?K?V??X???????????eV???1?N?X????\?pAC???e???'???t'???2???????????cs}??!ee?????w??? ? ?????b?|T??t?X^?D?S?+???zeH??IZ????^U!{??*r/G??n?=??-S?&:?mfb]??{?(??-??emx??]???ZBT?iUm?Z?E???T?_???Z ???])???W#??6??x????H??B?F"??ny?>?XX^?q????;???az??i?U|&??r?#m??~??;?(2S??4?wt?Wdmo:???g??aF??n?Yw??*??X???j??Zgr2????W????SC?YU?=?v????k? ?n(?~2??R?-[???9?5??????F???0?Q??}??:?>f???W?t?d??}?[v?Sk?R +O?x??a?y??T8{)d???@?U'??_?L??q???V???C??gtE?jFA?^?B}???2??A?#???a(WC????r9}??S ?k??C|n??V??2????QPq9#?D ?4u'??\??1??'????,? +?x?? a?:?8?z??w?>0?q??????*o?G?[??v??F?jiJ?"K?;????????l? +???k? +uc6??a??3q ?{??$???c:??:?????9~?K61?8nw?{j0]?????[???? +?????-R????zO??????f??5?M????Vu?????t?&???AC?y?/`?hH0??-N&??{?9???yl?A5dy?n?"??3um?_?.??)s???rLv22?xal?71?d???}??2?Y?5????&L??S???W*PL?????+?L? ?:QUVR ?V?y?3P?`??u?u_???????N?"???-0e??!VYoa?????e ?t??Wz?P???EgG?;?Z?????`??f????7P?3^?W??%??&?n6?*~??t.I?)???????S????R??Y??'?F??1?r?????5???`[??0x?T~d/}???????????,?~?Ra?bZ?9Rk?S#)???C?????-????????z-a??,c?2??F??. n??eF???W??;????C?+`???A0?(]?0????????t????? ?5:????p?c????m?I? H??@?U?$?m?????4"? ?Z +G?A???"?????w??????!@#??=}???H??M?????;??#??k??-???|W?@?f?G|?a?\M8?? +?A????WmFF??????>_???[???????Qor?"??,?w?q ???3?bD?~? ???[+?T??qy8?o1q%eF?#??????^?Mh?B???n?.+??s???;W???>??v??;c?d*k{?xi?P?l? S?}W?????^uG??C???)?????&i???q@?????2bP??~??O?\??rt???E??fm??F?r?4#??x? ??N+]?T}?????=n??N???=?_}????/?^5??mc?JYFb????U??>??M???!?JX??S@??6??f??knMI???Xr???s?rl?#?T8E???[??n?W6k\?5??i??K??c?????? ?-AA!????V?s??}??.? 3$??=\r??:????A???B??Y?)??????{???^j?L?,??? +?~??=g7'?*?`?9?d)?0?K?2????!??????????:?t#?A?#v??rf?????E?rza??v5?l?D }+????(?w??? ??0aP???????q?S'?:?? ? ??T?X??+)???M????\?}SsB * 8??v?w??2???0s\o%,?31???J ???????Mz:?E????~??I0?n1?:r)?cd?o9??<??L?O+???`?U????e R( +??????`????\'?J?/??????p???????%]-!?V?Nu?;??t +k??!??+?????`?#?W#?v????xU?T\?????[:????1??SP?}?">R????";d??JhB??'??y/^?Z?N?>????Fx?B???8z??H?]gm??88?t ??S?f???!? ]??i%?P?H???L?G???m??H"?-9?????ZM??g?\????h????S?????+?u??k?C10^X?iM-I[W??e????$?1?P???!??xs]?-?O?$???????+?O%??*?OLt.????'d +? }?E?????endstream +endobj +158 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 33 +/LastChar 125 +/Widths 641 0 R +/BaseFont /TUPMAR+NimbusMonL-Regu +/FontDescriptor 156 0 R +>> endobj +156 0 obj << +/Ascent 625 +/CapHeight 557 +/Descent -147 +/FontName /TUPMAR+NimbusMonL-Regu +/ItalicAngle 0 +/StemV 41 +/XHeight 426 +/FontBBox [-12 -237 650 811] +/Flags 4 +/CharSet (/exclam/quotedbl/numbersign/dollar/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/C/D/E/F/H/I/J/L/M/N/O/P/R/S/T/U/W/X/Y/Z/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright) +/FontFile 157 0 R +>> endobj +641 0 obj +[600 600 600 600 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 0 600 600 600 600 0 600 600 600 0 600 600 600 600 600 0 600 600 600 600 0 600 600 600 600 600 600 600 0 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 ] +endobj +148 0 obj << +/Length1 1647 +/Length2 6901 +/Length3 532 +/Length 7764 +/Filter /FlateDecode +>> +stream +x??teTl?6??? ????t#? 0? LHw?4??tJ +HH+-?????A????Y??????????Z3k?}?}???k???AG?G?b T???<???-??-?q??Hh???pW?=&??????A?? +( 0??vAA????6 @?? +9:???zF\\????v?z?????????/??w7 ~O???p' ?? +(h???j=???2<????&t?? ;???9(??????n +?{?%?`?@;?}???????n ???8Bm???;?C ??+??w?v??????{?{??L???? w8?>????_u??l??s?@?0?p?i?C?n?vOs??m@`????e ??`??6?????????e ` ???*?@??6P{W vOs???v??'??to?????'????5??0??/???}N;?}nG?????? ?????`/?????{f8??????]??@l>-?>%???2??O??????-??????F???o???????Z6n?????/0?~?4???? +?{?????P7????wo#?_U?'????R??????? ?)????: ?????????? +??@?+ ???????? +3p????!?????{??t?g??f?????l???:?S7?v?3??&?????T??/?/????GP???1??G Aa??K??D?:k??? /??/???????,?F??????#}? +??~??i? +?!??{??l????q???@/???4?N*?93; ^?8????Yw?z_?{i?????HG`f??D??]m8o??????S{??6?87:?]?:??G4?L]?DK??b\?!|??xY?Fq??_5V?????\???gYr??v?U?y|????0??????.?>???????ho?5e????g??????k??+7?E???E?S?U??9??fa???3f?C{????N??>?1d?'`_?6o????,?????????q?????k/Ca???K???N?7??e?M??[&?a }Ql?Z??"????)?4?G?8?;?Z$V??-?|? .??????-?7??l:?zp??????Z??B???c?_?#?2o{?lsb?d+?????k?OX ???Y?V=7??????i^????????V?I??pu?=0?UK??O???? ?E%?f#?j?r?~N{??S??3M???.Z^??:oY?){?:B{Bx?????N?J? +?????&-?/?$hX?A<z=~t8V??e\?F???SN?]bd???>-???Q7??F???9_Z??*??i???Y??????;???jG??p?????W??_$O??e[~Z?????6???????f9?@z???? +/?????????[??~n2??=B1?`????E?K???xk"\cT?DNM?~ +?????D?????ed? ????h????w?$pm:??R???Yg.??~"Jq?@*??,????~?x??FxfMS=F??1?o|W???????M?Q?:3{???2????Y?????????-??bZ?K???TL???C'Xs?o*?/?/e??k?=Z???} ????(??E?}I +?? <?FiG>C?>???U???.{?mF??$5%2???j?B?1?g??m[?e?F"I-ED?17??&(?_&@?S3???]-?r?z7m???M?\?):?o??c?HmR???? ?ha]?5??/\?????>T?k`+?;???b????K??Q?C????c>??????+?&???j???v???{f??J???0% Y???d??? +?gKJOv?HJ)?????}n?????^?k4?T??????D1?Q"?!q????W?K???G?zk???o?-m????svM?P?Q?V??m?5????v??O? ,??D??O????????:??U??3#????p>?(?=^O??????6?u?uc.???@?r?e?gH?I!w?R??~j?JY3`?a??h???&j?????????? ?`????d?Tz?????? ??b?gt[W??K?{0?Y?S??O?K`?t?+}?%?????#,??d!?(?a&???????jW? ?}nmj&??y?8[??1D2??? l?`h??:J?`???????f?????;?~?$??j??.?T[M?F??mDi????o?w?PdO?R?>??s~|(????t?H??%[J?????{*h?R??D??>?????%:'?<|!w[?4???%?\??7V?J??_e????7}?m??????%*?????????H???r?wL?V?q?????z;???~z ???J??????]K_?\BY +huT?*O +????Ni???4??;D???0??????i/=??a\?^p????`?e????????rJ?F???/?5??(1o?B{?? ? +??Hp!y??o????!gv9y0_w8C?K???G?? ?P?I^???? ?gF\-?V?|??4???x?????G??;?????W??m???L????V????&? ?o??Vl4?????OI+??D>}g\???????????S???m?A ?T?c]?oIt?u??N?:q?X?fn?LF???N`??hq???4?}??`?????2?TD?:?o:^fb?9w??F???vN?/j?o?K???D^??f??1?f?{a??O??????O??&?:??3???QN?l_?:d?_(????,?f?;?X?3???`?Hzl,z???w?~?????T?z?"????E?C??[-??O? T?i?|??$82? w?a?)??i?*!O???S2?lx??`?b?%?IW+?C?lm?M0d>p0?????HBlw?+?~??wh??,u??G#? g????eL??,???#??l????%?.????g_V????????Q???o??_?l??/?98?$???L??m'????y?B????????^no?[????RU????????(???^w??qX?=????{4?y???v?[???g?????U?~?|"?d???E???Rt?????}?]??u.N????o????=???`^?+Vo????X???3?G??o:p???? py_h?~???!*u???%?????????F?????? ??????]??:9d??Y?>?EJ?G{/???O?7??q?6??s? ??Dm[??? +??;??{N)Kr?D??????M?$F??,e???C]i$????/?z??????s????W????A??_O?f????pK? ?~?? ????w?R??T???`?3?????(??]-???tA*?PZ????PM?ll??$?.??S$??M?`?'???4C?F???!zG?????N???]????2"??????? ??#q?:?x?}???*?q7??&???%G&? n????v!-}?Q??????g???w????E?OX?h??0??x>?2??i?0e?u?????Y???'1X?????/???c??P??; ?;K&??]bN?BI?:`C?E????' +?L???H??i????7???????5??=??L1?4??bj??kH?3???#i?4?kUP?yZ?93??????C$MS??E?G?????'????h?C?l?.????Vendstream +endobj +149 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 99 +/LastChar 119 +/Widths 642 0 R +/BaseFont /WPJZOO+NimbusRomNo9L-ReguItal +/FontDescriptor 147 0 R +>> endobj +147 0 obj << +/Ascent 669 +/CapHeight 669 +/Descent -193 +/FontName /WPJZOO+NimbusRomNo9L-ReguItal +/ItalicAngle -15.5 +/StemV 78 +/XHeight 441 +/FontBBox [-169 -270 1010 924] +/Flags 4 +/CharSet (/c/d/e/f/g/h/i/l/n/o/r/s/t/w) +/FontFile 148 0 R +>> endobj +642 0 obj +[444 500 444 278 500 500 278 0 0 278 0 500 500 0 0 389 389 278 0 0 667 ] +endobj +115 0 obj << +/Length1 1626 +/Length2 10204 +/Length3 532 +/Length 11061 +/Filter /FlateDecode +>> +stream +x??weP??-?Npk???????@c?4??? ?,??w????5?wg?N?7??????uUW?????{?s???R]?U?l ?;CX9?8?? 'KwM??*XP??=?x?????J?- ???(?Zd?V..??? +-@??????t4???Y?i?+`?????Lw??3????'???t??A?_'j??`r??? +U? ??:y?3?????a????????@F? +? +???? +?l +??5w?7,Iw???hzKz[]?r?\?nN w????;?????6r?r????????7!7?[???? +L?q?r?@oU?e???bg???;?? +??EZ??+7???{#$???_???????7?7???o???????O&?#?l??km? ??o?????Vnno?}???????;z?P??V?????>C?? +???????p)??.. ?w}???4???0!???g???eG?iw??#}W:???4????{????y7??? ???^??????!???????i?3?D???=c0?ga?;?;?@???$?v?(?oEG?t???????.??wH?s??i?=?????]sI? +u*? ???1p???????<%g?`???-??x??A?&1}U?????i??B?9 ????SJ??Aok~sK>?#"?N??dW?Oq o?x?B??p??E????y???3Y??3?? +?#???????%J?g ??Al?.v?.?d?i??3:h??-,??4??]1???????c?/?6H?k?????q?I????7X?A??N?'??IE??@??8_?(/?????G????Z!???'?I,?????J??]?????3??.G??i?|??z-????P?R??#?)? ????_???R9?` o?2w1??4??1???????{??+0??)??d???"??<1? + C&{?_i?,JeR??B??:???x?x?Q:;??0M???????Qz?????O? V?????X?????Z?B??Z?MT +????J?? +?w??`???????Z60?9 +?BG?W?????8!?????$k??5-??v???*zb?H8?????/,??'???fO~???????!hl??W??.>??B?1??S?@??`??2?K7?{n??^?Q??&guF????????T? ???????Pf??S?b?Z?O?sd +??s???,?}MBR(3'm?u5??3?&+$k???4?????}?L ???tVC[MDh????W?????/?q????1 +]????l + ????w!?W??b >?2?????l?????n??y????[#zT??L?????S??Y?? ?????n?C???O?s??207+)a?u"dF :?????pP??\c???x +???{??C?_??:d?V?Gk???{?/?0??a???{:]?N???{???=??vqw?~v??>a?[?3)???nf? ?C?????!?8???}??u??l??T?@?? +v????(*.??C??????S?F2s3????MV?????4*??gD??w?=??D?????L???Q??G? ??mcn???i???8????o'?YV!?0t???hw???u?U?v}]i?=?1?\A?1T?}??cWGcK?j?1\?j????*?*?F?e?b????I??V???>???@????k?{???v?)?%???????? +??5?r*?X?SRi??^???o??)?{?*5=? x?X?\??????PG??S??|?K?;?]???cSU?0[;?e???E[?j???????5?t\a6I(??D????_??nqdm??O>eci>l??P?$??p???Ajn?niWm??e???E??????v??????[???3??????,%?m????Z?vp?u????w%^?(???M??7 o??[ ;26[?n????H?? +?????t?L?Y?B ???????}??*!?Z+??????h~BvxLWhm???????~h#O:?d???J??#?_t?i????V?3????:?????? o???!?v???|????????o??????????R@???`?`?????6o???;?g%0???x????????zZ??X??rv??{?h??`P????aG?BB(?T^`nF??L??F??a?????.}????t1+????o??????i??0??z??(?h{??&?|w??i??#?U6Z?E?fj?f??V?:?*??{A??=?qT?G?Om??V????bP.??????y????? ? ??.;??? ????E??Q6gk?%~%%?????? ???q??S?"??x????1Rvj?d??????F?3?k??s?H&/b& ?Y???^U?? +1??????D~]}???5????E?7??$????????MF?'?.v???b???U-R?}???t???G??x? }??Nz?!c?qxa27D??z?^z??&q??7b??????z?m!-???n????6M?6?"Bu??*?Gy~?sA?:?+?s?FY?????}?????]????IK??????y??k?3?P??d?cO????V?*_?f?Gt0???????b??Pn???? x?*|G???????? ???q??/? +?uz?:!?4{K??p?!X??J ]?P?@??SU#????"u???)?u?? +V?i? +?@???.?????U?B?A*??{?2c???"?n???DfRm???]?efO???/??4?W:?{U?[??n?2k??[ja}??%? +???<s{?????R= ?G??v??\??????????n?%?5O?]l?(??% ??i????R??g,NJ]X(!?1h")?B ?=????O??X>?l??????YB?a??y??????C| Le?(?&??`?M?Ug??1(?8mv5?? ??cw,????oJ? ??L????ax???0????????q????V[Z?????X;m???????????"?V"?i?D}@^~k8??%??1????V(?????;??g?}b 70??<?? +2??&]}?Z??g4?M?>_s|?e????nT????GU?????????????l???@n???Q:"Q?{?g????Y/\|?j!?;?L)3??sS???%? +?v??60y#+???NT?n????}?????yr#0`?5' ??1)????$Tm9T?e?,?% ?U???{?] +8????h?{ }??OB\?????gSR..?{????u +'?m? [???T???$B??z??]d?wa:?i?r\1?|???l???H???=Od? c??U????????Fd?W?]????????b?mZe???? UM?,?6????z?????+????_??{??3\???f>??????v????7???j??s?*?j??s?Y?3?pga{YZX?fn?? TyJ73???q?O?@???-~?}??.K????@??c?<-=::+9?v ?????0????;????"??????????*1?9?{??~q?P??!?\tR?uO?*g?]m?X???w&???t?f1?x?z?????8?]F/? ?1???r????H?;?e"B)?AE?A???x?ye????>????C?[?Z?cK?q?)z9u????0D?I? S???????s5??;???IC?5t?l?jX??t0???.0????2*x??_??|#?g??k???*? ?X?t6???>????u?vlj?7?|e]R?4k??*??`U?A ?J?Y,?D[2H?n?}:???V??? G?????8??Q? +????`?"??$?-?.K?;H?,??l{?????i??3?a ??C??!?Q:?"4`k,??P????\d>??????;?T?.{?Wd?e??j?0? ?6? +#WW1???6\??? e???P???8 ???/C?m???????w/?]?w2??(???????C?'??!?!? >?y?|??PY+??i???F??]a?r +?J??n???{?&????????kVV$I?H?t???T=??x? ??s?pS?y?A?I????-?t.3??l?????B?eY??i?TC&R??????+]A?`????o??{?Yj??5??y>???? +.|D?? HA;?+U2?????E<d??? ??s?!?,?} ? r??r-y??O??? ?????"?A??h??I??b????^?j??M}??Qi 2?I????-'_?Yt???@\?S?'(t9E>(??>??*??`d?1??$pL?x?; j?z????f????1e?T(@? p?Y?yr%\?6???P;d?4???? +Gf??7+?? +???V -V3?????l????)?q?u???(?W???U)???p? ?w????PF_????.??67?cS??$[??N????a??1No*?M=???:?2??\???*u?x#?w?????|Y"{???)p? +???????.?????/?(??6??v????wu???Q?m?(DY7[??a?K???&?'?L?.? +?s????A?#.???)3Bd ?g?????\&"?????h?r???8?yefV?!p??)E???????Ja??`s????????.??7Y??^V?[C?>?g?, ?=?6n????>Kb4t=5???=N?7>??:1??_?8???>???ng????????N?S?yq?? .???? +5?4??*@?r?8??fP???;F???????????o????I?.??u???nL.?????C????E?*gg)Rgw?oH?f????2k3????d]i?!ae????#T?m +?zF???/.z?YZ??9? +?????oe?rQ>????5???}L?O???m?(B??T????? +?]?%???91????k?????????????%??????6??? +?W?????']{?nvv ??O??????nx?PN???rN?6? Xu>????? :?,:_ +`%???]!???]0 \?^?? ???x?HQ????uv ??Ke??U?QM? ??0?lz???w>???? +?????})??O;?S?I ?9 6???,?>???im?;??1}??????vC????J?[?QEs??G???w>??w??2?1`?6? +????d?$j???????? +}$?O?c??3Y<8?`?d?z???+D&?+_?V? Vf5@????mg15?)?d@??a?s??{??Y?@ ??W??F??k5k ?LpD??%?(I??I?S????]~?.?eL^?T?[?*zr??hFc??]P???s?H??-5??c??.]??????'k?y?; +??+? q??????9\fW*U4???Y.?A?H?z@?c???????i?W???.l?~_~$d?:s>mk'?PR?g???r?$H].'??0??6_?:?? +? ?]?u??F?? ???#??i? +?L?-??????????i?1??@?X`??Q ???D,?r];?=?V?f?2?S)>???5??])??<^?????-R.~????S????-?n-?wX?l2?$??N?rMr_?p>??.?^|"S[B??()?Rv ????#X???wy??????8??=R;??? +??*?d??????iA?w??}v?????>H????ssaBa??E???????{??'?'??8?}q?l???0?U?,?('?&???[???KK`?????0?c?DL W????'4(? ?j?ofc?#????????}"&0WQ????????????(!?Q????zG1??G????{??? +?$??~}?W,??;?`?N?at????\??? A?"???M??????????????7xw~???y'g?^?q????hxL+Xj???'B???2]?p&??????~??~?X?j}UG?JT?????H??????~?J????J ?????*/B/h???H?WA??Kt?UVo?????U?0????@?Pj&??~????? ?faR???^?????5??F*?????t?d??j???d??Ox?4L?_2?"?30KO?????D?????&8?f?3?F*??t?^|-W ????J??????'??????C??>* +?DA ???????8?In?3?p?!?A???%:d????`D +???v????$lH??Ny?????????M?????3ZU*rh??Q|?wEn? +?d?????????K?]?A}?H??q?aju??2?s"D?kM????q?%c!-a??t $?R??\4??%?BX?0?w??Z?f???:?p???w8L?6G?H?,?FHU$?j??@?q?????+?&U>???}{??-X????=VY??`g?????0?4|??T^?J??? +a???5h??|=???Xl{!?8u?6?? +lL?? ????N*?????v?7?V?BC )?3???[??1? =[m???~?/[??? ?|w`???R?PO?'o????L????2??o=?H??????2??d?????N???_?j?#b???] ??a?gt[??J?!I?t????X??]???_?T-Z????G73?a???:n??? ?>??Sx??^??>????m?pb +xh????;dv?m:6???;T3j?' ?????#?|?>?^????????\q?????/Z?AG?Rc??U"^Sw?????P?:??? IA??2?n?(5?`J??\Y?_C??????W^bw?Y?,?'Tk)?9U??? +?b?F^??P???9????;? ttg?nQ ????Z?6??%????G????6 6??o?tRB???@????!2n???&?`?P????k??"??w??m??????SmXr{!?u(v1?bD??!?M~5Rw?SD??"??? +2?????nxV??-??~???ot?FW~??Ky?b??? c$??m?????o???P4???Z???,Ei??????????|g?P????V?????kR???6?????h?M@?H"Y?e??U1??????`> endobj +114 0 obj << +/Ascent 690 +/CapHeight 690 +/Descent -209 +/FontName /GMEBOS+NimbusRomNo9L-Medi +/ItalicAngle 0 +/StemV 140 +/XHeight 461 +/FontBBox [-168 -341 1000 960] +/Flags 4 +/CharSet (/fi/period/one/two/three/four/five/eight/A/H/I/L/R/W/a/b/c/d/e/f/g/i/l/m/n/o/r/s/t/u/w) +/FontFile 115 0 R +>> endobj +643 0 obj +[556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 250 0 0 500 500 500 500 500 0 0 500 0 0 0 0 0 0 0 0 722 0 0 0 0 0 0 778 389 0 0 667 0 0 0 0 0 722 0 0 0 0 1000 0 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 0 278 0 0 278 833 556 500 0 0 444 389 333 556 0 722 ] +endobj +106 0 obj << +/Length1 1608 +/Length2 9985 +/Length3 532 +/Length 10828 +/Filter /FlateDecode +>> +stream +x??weT???.????%?Kpw ?i?w?????.??]?C????|g??Y??_3??]?????]U???????m?O +??BF6@1kzf&n?????#HY?Z?^????nd?''?b?w0???wr??F?!??g3<9??????????JUI?????_??!?z?w??L??N at K[+???;??x?2p0??,??/? +??r?*q9U?8?h?o Pp4?43???A at j???=?? ????????@ ?XB ?>d 44{?t1??q?l??Vf ??3? 0???vx??? +????????w???_?l?m?#??}?` +6 ??????=?????x:??;?? +2{wl??#?l ?????????of +8]??2??@????????l?????2?6?:?=?D??????c?????????mm-]??m?W?r0s-??????4tx?mbf +??gP$??m?L??9???????ATf?????????+?h ?(g???@??S???'??A????y?w??]??r???????b???r?V??? ?~??2??w???oef???D?=P???????{??M??`b`??? $f?4R0s04?[???/??????????_m?3?????bjfha????\???Fg?.?_??E??T?i?~??????????;???C????0??m\???,z&??????b???o??????????? @??h&??J????V???6?1?3'???F??????nCG{?wE?:??%?s????. at C??C?????j???1??.f??@??:??\?J?N???M?2???@?? ????#??])?_C]X??????OR??\?5?6?_~?:EH)????gs2?_???~m?)*?>CN??????Q??:??`???"{&?Fa??C??;:??;???????????????#?q?D???????Z?aP??W???J???t??????WWj??~\l???s?x????r?H5?J nZ???????d8???H?a^??U!???V??0{cC? ?Q?????? +?????BZ?x??[8???????9y?^???"??Z???? ??????)?????(???Y?kl??%??N???w??7?H?K????I????!=?????? ?????6? *??)9VBZ.???e?0?_??J???8?pI?!H??????????&EQ??w`ay?}??????K??? ????n2??yd?????O?f???w56 +??? ? ????i?/?p?L?2`?2:?[??3t?,?pX????l???M}B?5?K??:???a??a?? +P??H?=#??*m1?? +?????????????Q????2'?I?? +?=?????g?&C`??????C/???$???R????dYW???~q???W??r.6???w??u?8i?g??-????fbr'1?"}?u1? +?~ ?x$?K??r$?B?u?zg?Y?t????4?$?????a ????!q?%>?K?9vU??????l*?Y?N?5x?-???E??U?[Y?|9????"ls +f/???m? ub?:???|????F??7?\u????xZ= J?hV?"5V??j? ??j? ?=ZL???????L?q? ???'d?6??;?????4?????;?u?Hr??????q????b?7\?)??0???E~?1P???i?W? +XN ???+#??}k?B?U?????G???ueu?PEq?&j??I u2??? ?e??z??^??? +?3??-??R???-?`N? +W?j?%A????????EA?=???5??????1?B?????? +??1+????J??D??#S????)??Ff? +???? +??I?'A?B"*c??v ????????j?G????\?I??},P????U>???dvP??xp%?M{ L??B????'Jzn?6I L*n?????,q\????o|????/??&b?&?? +5?$???v????? ??)??fM??u!$???ZyZreyA4?;!PB?-Gk?"????(C??KL??{????L??????sr??????X?c?.??n??????a,?1>s3.??:!?4p@?+?)??;?x??|?"r ?[????,h?O=D?q?5$*_?T[.?N??????7?"?O?k? ???????????K?-? ??88I??G?@??sI??p???g +?H???}S?X ?H[?-?????\Z\?d?@ +CG???r???m6?)???????J???&5?n!X_=??s?Gj??O????T????PD????0x????W4?(?? T?O??? ?/?`??2Ch???? yQ?| sB?[0;?ltE????4+?_?A?!?`?9??i +/N?x??S??=??? ??dG[???q`?3??/???DL?(*x??S??'???3???T??7??_??f????????~?L#l??y????,??J*?B?^`??~????? +iJ?h?qcW??F?#l +??A?:??2??N;??yP?? V???M4ue??????$?v?0??xu?=???????C??????????C3u.?~W +}??????c?L?zOv-E?NB???-???E??C???SA???B?y????od????+)3`k?';??gpn?O'??y?????e?_????N??W%?i?|E?^b?????????M???????RS?{?M???????<]I?,.???????q??M?<|???T+R"[??l?Wz???^???NM??cE???? "<>?????=???j?@m?????W?v??u???h3l&????y6?3??\???}????i??b?X??#??(GI?t????6aia,?b?!?? +??????????????1?^?4????:??C{F???Z????}A??????EfT,?2????d/?j??ue??E?|???J-m?'L???'???A???w?U?????BC??$W|??T? ?4?mi?B!?????"^??{?!|vs?%??%c?K=Q?'?n??:?C??y??[?F??????? +???BJ?!????4?m?????(MO??/??&wMGs? +?\???l?$w{?p??y?q?)?w??I?uL? ????:???????pR???????~?v?4?P??{????q??? +]?????Usi??+?[h?d?KZ{?? N?????V??P???s?(??AM?^='?_???3?n??$?e??yqlf??t?2G??,B?b???d?  ??m??+H?y}VcQ??<\?9 B4??u?f!????p???W??Q????2$???t3x?d?/:n???ds +????1qj??/X??;S?wX????U.???F?{p???S-CIk???W??????{????^evP6??6???e5?*?`????e?mV?4????!???$l????????3???R?Y+?h???i??L?k??n???F?Z3???T????????2?r?e?+&????$???O?_M??{?? +?D+?? #??????T?j?????[\[??M{?-z?????#??9I?]??? +h?>??E?4J??'???5[=??OkY?? +?@?ffC??z??s[?v?e?T?quD?H\0???b?1~???-?????{n??)??K +h?3????E~e??J?????'??BbGV??|.&??/6????? ?????v?pT?W9dv(???y???3=^?/?^?[2Y??K=P??EVfxI??~+?T]?mFp????kL?j?1?N5?J2Hn2?? rn{u????r??eq??z??l!????_?c?T'[??IV???????e?bj???2?G< +h&X +mA.????)?3??^?<^?G?~??bq????'?)?Q:???? +???09???^??????U??c??s&"(???r=9?@^?< +?O???(i??1u?N?\-?q{As0?:?\Kh?m'???~????F???{$??0?:????2??-y$Y??????????h%]'???=???T??_???D???????? +?Kf???9?"?dA?'?_,??p??"?????\6`?Z(+??V?PTx??%?????d?#???h^?~%?z?:????2??? ?? $~???^???>C??)?-?_?/?aQ+qZ???`????b???L??Y]?I??????AV?t??X?O??]?Qo? ??j? `???????9?????n7?@ +??}`-]?mbo ?O??r??\k?i?*?[!??oG??Xj??g???????V/ +???( ????@???0RG????I`?W}?????^-?0?r6??) +]?{8?S??8a?K@(-g?E????u?9?????Cj??i2N??^*Lf? +N7df?4!????D~l???_???qZ +??_?4??X???{?Q?????b??x?+?v??J?8??4? ???}????"????-\?h"??)??+]?? ???? +?7??K97?N?e3 +?8?Y????'?1?iKSWM ??b???\?????R???L???????{J?c???o??????0??#?????V?????7p???> 8? +8????)?@(m?|??E??r?RaE????RYJ?{?l??7;v 55?0 ?X??0on?Fl +w???Pa?{??&j???? ?j?I?*???N +??2bn@??|8R?0???p?Ws!???B`?????WX????Z|??&?=9?{)??????K ??8?b9F??]?{??4?$_%?`?< ;???Fu?p0*!!zbl?UT\??=r,?#??? +?|??~???|?T ?x1?,H???k?????A?0?? I??^1H?;??h ???k?????E????b??EU ?5>???&jP??t??SI;`?:s?*?BPQTs?? ??,>; ??y???????|?G?????X;"d +????(???n#:uZ?[?????m +?3?K~Ln????????f?V*???g +ok?=?OPH??Y(?c?B;cJ5(d?[????QlA???F??+? ;???x ??P???5?!???\/{??cc????~'|? ?zD?6h?"??x?????7??6?"?# !??0Z~Y?? ?w?~??W???S(c?)?Vj?e???????4???qk????4??F!?''a??_|Sr???-??e.?? +?????S???????c??(KkO|]s~;??G:??U=??????Gf?a9?b????0G]?p??.??E?g?Q?`?[???,????]Pf????T??>?5?:g]?T??7~???I??Elx??}???hn??&I]o\???C??}J??i???n7? cX?b??%f????= +d???t?&?(@?46(e?%/?u6?c?Ig???0?????N??WF.\1??????/??B?QQE"A?[E??&0???t;??H??"?aC???91??@yI?,?:dIK???????L?? S,?d??@??MX*?Fm?? ???2?yb??????t?%??d8?^??? +T?e???? ?????????w??w???? +?u?????+????U`???h??\v?ut"x??????;v?/8??-?W?? ? +)?y???{*?P?]??[q??D? +?????X????U7?k~@)?????J???,????"?P?????Y;!?T??Z??n???????Y??T 4?p?/a~?`?~????^?m?d0'S???s??? ??Ww??t?Cb?????_?????7??VA???y?eY??Z?'?u9-(? K?K?B^C&?J?a? ???????{\???T????}3????#?JZ?BJ?l.??mp;1P?;??N???p????^??C?|???F?L?????????n?'i?@x?7??F?j1_3U9d?????%??w?????,??9????s????D?????m}:'???Z?0e???????!?uWe????m w?(?K???????,w?p?^??G??????e?????????s??WY?xu>3??@?????q??O??=x????[????n?Q?s?0H??+???:?????1R??-?~?@JZ???r???o?? +????M??/sxd??l??????]???c?S??F??*?? +?8J????????QH??B???'??H?? ?F?=a?)? ?????8?4????????????B??j??t+????o?4 +????????v;/???s ???h?????*?a???sn??????$Lc? fh???3?~??E{?%&???\?\^????d??-5???)????W2??0??;,UP-?`?S??<????e5s? ?$????V?Z+"?D???$D???)? ?JH? ??\?7s??q?Y?h?{6R?XG?????<Gg`??=?\????? ????XD???????-??5/R?a6&#yIc +?cwd???i??W??q??]? +?qT??(?_??8???K7M(?oi?&???k????k?I7????????Y??s?,?????(?dk????U?3??{M? +?G???#1????TB??o ?T8? ??????x??J?[E.? ???z?B[??Zo8a???[?5?`??!w?}????Y?? ?68?? ?)?V#nK?????@S???|???b???f?a?X?6??&????s?Q?? "1??aTY?&cQ8????^????????N??}?????Uz?`?A7L??.??Y???? +???A+?C??u?c???I??;???#)?J???| ?\5>???vU?+?UW=????|?!=?o???b$?????'?*:?????????^?C??t?el?'u??)~??????M???nJ???3?+????k?#?????????>+??v>f?????j?????m?>???^$?)$|h?N?????O?f????8????J5?f?2?j`?E?3 +?O?t??s?F6XF?g????UM,?J???&y +?(>??-? I?s@???U?D?_??Q5uQa??X?F???????,f?I?^r?I?u?m?1??i? 3:?tE?p????1?+2?*?????"3k?1al??D??????l?Q?^???OP]??Q?????N???R?M?C??????xKY?G?7??b???21?v +?)??Dt\???L??.#XxH?=_N?B*Ga??@b? qk??9???&ORD ????4?U`_r: ?7N0???=?q+?????w +5E?g~a4??0??th??8M????q?{????i@]?b3?%\????FO/???3?7???????? ?0nhzj???????f?im???]?]L?:G?L8]?????? +??qS&H?%??xRc???nB??Z?????c]?n%??O?p0?E??]]?22?q?S?????&)o???P]?~?=c????,3?????x?+?I????:?D]V??l9??s?|?0?A?dYk???rhp?A?W??8?"?%Mz?pD?6??#;'3?w???a?w????g???O?p?2?S??5??x?????RuN????y??c???c[?B????f`?mb?e?>????'ZU?TL~??gP +y?7?q???????^?)???o:???:????{?9jd??A?5?5V?I?J?????sc??2??o?y?W 2a1??n>?c.?G??,?wiT=d?_~???????@}{+}{ ????endstream +endobj +107 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 2 +/LastChar 121 +/Widths 644 0 R +/BaseFont /BDKNUS+NimbusSanL-Bold +/FontDescriptor 105 0 R +>> endobj +105 0 obj << +/Ascent 722 +/CapHeight 722 +/Descent -217 +/FontName /BDKNUS+NimbusSanL-Bold +/ItalicAngle 0 +/StemV 141 +/XHeight 532 +/FontBBox [-173 -307 1003 949] +/Flags 4 +/CharSet (/fi/fl/period/one/two/three/four/five/six/seven/eight/nine/A/C/D/H/I/L/M/N/P/R/S/T/V/W/underscore/a/b/c/d/e/f/g/h/i/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 106 0 R +>> endobj +644 0 obj +[611 611 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 0 556 556 556 556 556 556 556 556 556 0 0 0 0 0 0 0 722 0 722 722 0 0 0 722 278 0 0 611 833 722 0 667 0 722 667 611 0 667 944 0 0 0 0 0 0 0 556 0 556 611 556 611 556 333 611 611 278 0 556 278 889 611 611 611 611 389 556 333 611 556 778 556 556 ] +endobj +102 0 obj << +/Length1 1166 +/Length2 6485 +/Length3 544 +/Length 7294 +/Filter /FlateDecode +>> +stream +x??yU\??%?48 + +???;??C?h???=A?CpM????{pBpB +?!???=s???4o???????v????V=+??S9[?5DC?????ZPk??`????p????C?????????a?`?=????#? H$*.?w? ??G?tP?/@?? ???{Hn???!?z??:C!?zw???.????????>???a?g???1??>111???_@??????g???J?*q????\;??-?{\??*???!?1^w;^ ??oT f?w?M???[3E(bs?????9??^0???Aa??d?? +4?A?< j???|??;fA?@? 1???x?8???q?????a?~?pW????????????? ????????l?6H?5????f?C???k???7? ? ?@??????-???w??+?)?*>?????????S???x?E???r?(&$?O?i??Du?????7???s?{???p??&??s??_ ???@[?$?w?????Z????j??P?pv?C????????V????t? ???????D#???????!??P9????d??+C?!?:P????v?Ke???C????K?? ???w??8? ???g???????n ???"?] F??+???@ ????????ko?o????-??m$B???]???z?l}?68??`??uF??E???r*??;M?Q?u??2C?DG +O?U??r?o??&% #ES??9????'8??????I??J{???3???????UZa??i8?"???tg?M?????W{w?S???????s??8??p?"??yD?zg????)~??Ye;???|?m"?}????X?}???u??i???e&A???alP??qZYD;?c~Pz??l????X??BJ?@?/?@??^???_????E?j????+s_??????e?U?o#?~?&g?s?ev V???b!?Z???z.K|??F???r_|ZSXF??G?????>]??Atqcj?`-/?)??a??2??????#??4?p???????d????o?????f??H'?i?/?at???C7???A/?????i,?\???~??3js????????E???j'???? ??????[?Y_^?KkasJ? ?h5@??'?????#~?????@?Z"E^??wY?)??????????J?~?l)???????Oo????6?8?U??*F#?h#??c?I8P? |W?]7??1,aq_f? +?7Aw8iT?o?H?V?#ng??T-N?!W?,B*???x?[C/v?$?g ????????[???Rl_?u??N_.e??H??C?????ik?S??8S??????T??ntP??t)_<+?*???sK 5?PZ?{??~\??^?r 8{???y?Eh????_??????q???Q6??o??;???|?W?1?z?o\???Vb? 6i?????`7'?}??[*5?????{?f^ +A6??I&an??Q? ??W??? +'?????v?j?\s?{,????j?'2i?^o??r?V#gh?X6:|I?gx at h?-????????u??!?C?? mV +?\M?/??M9?^?0???Y|*EC-a3?9?a??K???hV?p??K???JNO?GLz?z;?v?]?FQ????????????Y]?/gQ??e?H?$0o?'U5?6?b ????bQ?0??(_bEP ??X??|j 5P"????\~;zay#?e}?[? +??)fI?$???";?)ALB??O??m$?? ?Sw????*?E?0??'?4?p??5???:???l??5?[????a??" ????JZ?6??o?????X??85??+??????n???S"?????kQ?x?????S?aQ???u??!t???5???,O`??ro1Vs?,??y??/???{???Wz>-?K?,??Z?~hh?&?,!? ??P?????D^???'6%}?????c>!v?m^?:?Ij??????) vx?y?#?("O?:]U?|????:??%?d`i??8????0????Y> ?b???V?F???D?? ????H?a??'?? o?5dv>BD???4s?:?????10???M?L:????!?zlK'aX?g"3?c????NI:b????LdQ?0M????m????t?z????w?%"?7?!n??!\?????Aeb1????J-?????)G{?'?\?b??Uq??Ya?r?P_??#?Z???3?gt??9?[??? ????-??CF??yO??h????Y3D??????}?@?D??? +&p???E?G,??H.??;u??????s??jf?????d|W??7?\?Ge?8?1??{.?|d?Ug? +????&???&??????? +???????{3vS????i??o?g???i?@?c!2Z??a? ?W0?a?d3?v???? +??%?????4G!???&?F??j?o4?t???O???&? ?????%???5Ci?rE?YDy??5\B!??lH?T?"?+)?v??P.?2???:|+S?%~?BzD????????O?i/?/?????? uz?N?_l??x?b??5??;?? +q`???s???1??:cm?^,A???c?q7??W?'N?Za?????Ab???N?qE?OZ%?????_?;??????G?P"L??#v?>??b`???hje??_??X8??????H?X?cF????_?g?%???\28%s??a???????v??G*?a??~P?y?*_>??M?%?????IAq??+4tTd|?K?]????n??;?WU????????k??1???9?^???hDe???FelcK???o^N?\(??v+2?56 ?jz??????? + ??zm? +?p?%'?w=Q4???????d????d||A???Q?u???S`??????\?&F??'`:?????Z$\|>??? +????????:%???[?r< +?3V*P?%r$It??????|N???|????t?Tk;???Ky???????UeW"t?????:R??I?w??z???5zd?t????vDwBE??-'?i:*j??Oy.+??* +??#9?!F?+??#G???+?????^?????F$????e????f?p,??pF =?M2??????c,??0?LL??3$A??dD?????"y_??2S?/??Q?&GE?QV???W????B!??;?????xv??d??????d?Tj?$?2,?^sF?3???G?IX"???i5?????R??y??hzI#,`hw]8?3w??????Ffd???9"?.F? U!???+?VTI??g????i??O??o??Q`????HI_|???sraf?, ????y?\?'1\??k{???tuu7?? ???DW??QZ??`??a????:?????>?G"???}*?#?G ?? +Y??D?`mU&???c?A??&?fW?Kms?d?7Sr?z|???A??C?????w?'V??>-????7!???7O?0???.+?? ~???????=?Px +?????=,M?????hEQM^???L'?`-???4$?b?;?kp??????l??<_????U???8%#?X +???????z=????=????)A6??e7 ??^?????6d?Nr??:?P)"?V??_[D?8%`&<>T?}??j???fn???}?T?;W?25?3??w??zg?T3?F???s?p"?????D n????????rF?G ?Pm?7??$??`;}h????(? %??p??r?~=vX??r?A +?F?)??????+#/??K?t?z????;{?* S????&?H??z=??a??U\@,J????J??b?\?mX????F G??\????LNF?????[dh?7A??i?+c???Za?(O?????;?/???G??]?[???dWy?????E}S??6D?8Pc????t[??????????w? +Z??????-??Gw??>6???\y?:?????????H???=????.J)?"hi??F?[??}??euU???H????Is]?tX?r?~??O@}}?i~W^???)??(?5??%?????j?i?MGNP?%i??? ?? +E???K;?l???$?q??;?1??M? } ?#\%k"r4u-??? ?? ????m??Oki??/???C????JGY8D(G??\????Z??lk?????????lM??????)K??l.d}?|??)tj????]$XPQ??A\???4T?v?h,N?`,?y?D??~?????0??O?:294K'B????dD{/?????6?r????}?????8???3kq9?:X9Pq ???a??FX?0?E:q R???????????}????P????:YnA????Ja??+1Yx_w?? #?M&'?O? ???A???cI?q?v??%????????3n ? + ;?M?????"1p-??E????0&'?<(g????j?k??:?`???N??5F???[![?IE?????????!???G=??#9%? ^c?y7??n?????,3g:?d????|??}C?????????c?c?n?>??u??O?u?w>?.?Y??????,???b??+p??cA?}!5??.>?7uIElivJs?(i;??6? +)?u??J??Ei??JGL?2y???b?O??^^????/?W??j??g?u#?2?;a??^???q?[?w?A?oJv??????? ??????????? +mv)????j?|??!????Yqt`?X??Y?IuI?fzF???f??????|;z?????????(z*lZ?l?)??jN?IHGN??r ???X?fF?o?z?i????n?2m?? ?O??4????Q??D?m?????? +Z3?#?N?Y?y?t???c0?[_?N+}?;"?????23/?fYd?%??c_n ???_g?N?N%?W???&T?C@??GObL??C\q?zd??H??0Y??H???N??4? ?? +@?/?&?|?4?~?P??/?=??T?/?M??_A?f????? ?~? ?'??1?dz???V??G?????S9Ad?> endobj +101 0 obj << +/Ascent 712 +/CapHeight 712 +/Descent -213 +/FontName /XDADQD+NimbusSanL-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 523 +/FontBBox [-174 -285 1001 953] +/Flags 4 +/CharSet (/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/question/T/Y/a/b/c/d/e/g/h/i/j/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 102 0 R +>> endobj +645 0 obj +[333 333 0 0 278 333 278 278 556 556 556 556 556 556 556 556 556 556 0 0 0 0 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 611 0 0 0 0 667 0 0 0 0 0 0 0 556 556 500 556 556 0 556 556 222 222 0 222 833 556 556 556 556 333 500 278 556 500 722 500 500 ] +endobj +99 0 obj << +/Length1 1630 +/Length2 18284 +/Length3 532 +/Length 19207 +/Filter /FlateDecode +>> +stream +x???ctem?&?v??v?b?6vl?6+???b;??b?????????8_????c????k????{,rbezA;#????3=3@?????I??F??[?^ h??+g?#'v:[???:y?@????`????#??{8Z??;?T???ii??S?? ???h?z:Y??(??????m???!????@??9`ja +?+hJ?????T?@[???5@????? ca ?uRL???>??lM,?)???/????d4???t7?????m,????,?f????{?l??5?v1?'??rS?%d?h??????/??????????3?oT???ln??Ol'??j???_K;c?J???/?_?????????O,# ????????o??`???J???????3?8? M??NNa?b???????Tohoo??/o?Y??,????? p?,c;??mfa ????H??????-7q??:W???D???P?M??????`4?c??s?@??2??? +????B????????????? +-?bm-gh?w??c???-?????Y4?????C k?????V?;?????????????????B '1 w??????9????o??%W?5:Z[??r?????????N????????????? +??????D?EUUh?7 ?_? +?Y???on?Q???????}??i?O8?z=?2?Ei\???<??=w'#???8?4?0T,?Q&_?8?????P?M?<'?6S?\7)UQ?0???A?9j??;Z??{?FY???????6??!??f-???h??c????5?V?*b?!:F?u???@!?????K??9Y?o??k?e.??w?2???ha9?%.??'?Oe?,?P??P?????AiU?*L?={gY??????7a`W'5??!gue????&????P?2?"l?~$Kq??>"$? ????-?o`?# c???M?/???,????>?.(??D?VCj???Y|???U82v?R!??WL????:`?&?? ?nPkz5??Gnn???*?2?m4C?d(??? +?? ?M 8'??z??.???)?T????/?????? ??Y????j7 V???`??eqS`???`A???}?? ?H)?GVq[???zX#k??r??H? u??`2A;?z\?n;MOPla?m??2 h?????G???&7Mr???Zfq?9?(?e???)8? +D?p{??4pFUr????&???V???Q??^lSC_??( 3?"6??6"i?UI????((???u??fJ??????m??q?????y89`%arJo?????F??x?c?d??e:?n????"B?NsB??6e?I??p?+j6^? ySb?? +Cv???????V? +?P2?K?,??4???=??^???>??=??????????v2????Z[?/6?{??G? ?T???X??(?nB??X???ho??|????{^? ???H?z?LZ?JM?i0'?b?h????n?6??? ?f`Pq??,0?????iv?b?=??{ ??2??**7??m?S*?}??C ?{X?H$?^1??? ?ng ?;??Kt?S!o\???Zy???<9?nP?e?9? ?*ZnV? ?????c?#?`:? ??8????4???u??U??:??!??W?gR3??~vY/GZ?9??^{?????2?HdWx?J??@ +RR?o?2?????ce?F??=y}??k??VE???s?'???h???J????I4OIEI??9???{??p???o?????If?????`?q??hP8?(6lS?r???*???2??5h?p???v=6,!?? +=@?;????2??'Z1???? } ???????D????6?;? #?+v7?}0??y)?????n ?qK?n????'???L??? ??=????h??6??????cn-????#?? fC????????P??M? +?+J??D?^??V??Ov{f??????F??i-D?~8?????>???d}??&???E???5^[5Imx5'y5?????c@?E??~?????1TH44??7W???,?.[??u?8???l??4???I???H?????%?$??B?(r??>??'?k??????-?&?????l? +??r??d?d?{???;??}?o?9????x??7^mp2K????-?q??7?*?)??]?5!-B?.?^2?v?H??$d???GeF$}5??a??n? Fq???z L?? +???n????????Xs-un?7????}????l?^???M??:?2??? mu?Pa?qaT?trb`?8tt?B?7-??"?-??^b Q??-7a??????????kY?]???FEK?I???9%OW???????W?E??o?/?5?s???'?q?Eq@????????n5?>(?3?j??&5?He????^Z????1???{??@?fES?1x?????<f?9Q?WF?????~?;?i h}}s?,3?Yj??/t?>b2?<4???V????S?????&?q??Y/?o????\?#?;? ?e?P?"?^m??.???#?+?,??Y+7?'???+?l??]???Z(?5?6??<"???s,Q?????d??F??????????:????owK +A?{cx????????|??{p?1?=;H?d?Y??j?????Oa^D?At&????????+?? +???????j??s*SR?n?|?w ?aKz?SQ?2??G?"i^]????V?/????r!?,j??Vd?C?M??`?>5~K??????0????B?0????:?\???9?UH?Oq?by??N??U?Hi^??T???&????0*c???????????}?s"??*?[?????????7?U??M??Em-?eNW????n????w????-???????O???=??7??: ?N?s! y?? !?j,??e???h???C?{??????T????y?7?x??b?T=?L???. ?L??|)????????3??????,??t??G?a?j?zb?p-AA??md>?4??,?Q??\??CI???@?(z9????Rp[?????>??????s?3&M?W??Y=??F? 1?????NB?C;%@?B-?? S'^?x TU??8?=????JZ?`M??????? Rm????1@??q?< ?X? d???.???F???a?m?"WC8N1 ? ?#3?? ???ys$? kg??{?i??t?0??QU????i?k??@k?n?z?????gv?p|???????w?|?9?@?R*??????PI??KOu]?=Y????1!?????'?pArM/?Yf?)}s?d????.$?Ijd?Y?v +?mA +n?- O?e??O?r,??{?k??u???(???E???????~????G??>??x?zb????}?*?sT?x)@?S??\???\?Qs|??????5??A?%??v?Fp??F?!9Q?r?O3E???Z?)c?t!c??i??`k ??O:=???z????????E?M???g??ZVUZ?f??????|????????????1,?{?-&?j*8?pn??S>????????% +?k?j=????Z0?/"`5???y????H]???1????0?i???/V?? 5y?+? c??????v"*=]??F??? ????????3??????4??1?v|N??K????U???@??H?????Bv???>?f$1?k??~B?Y)?IZ5?#)M?e??:1??g?2 ?)+Pt?????|W???HE?-???Xo?D? o???c}???????$???h?g?h;,;a?h?`-b?Ac8??L2W?V????????????????H???t?*i???????9 06=??EA-_s????/Wd???9?"?^\{yQ?m????I????sv? ????z????????@??l=?d???M?????Z???S6'h?6??Ec?]??j????zFvn?fb???>?&#?o_S?wcCM3Gm?x???z???t????V??'n?????t#+?sPn?6zn?7?H?@cD??????u_*r????14T??d?5E0????"?q?v????/??U????? ????? +?-f`?(#E??ua,h ???sMZ?u?(f??r???PA?#??!?5/?IY? ??9?NDP?t#??Y?Z???h?,?Z?W! ???q? ]????g?.?s??Fz??H#9?%?%NyMZ????;???0??S1?y??v?C2?X?j????I??Ra8??UV?y +? 1u'???????? +?-L??a?J?'?oOHE\ 7??5w:u????????????G???*T???}???4?Z?m???Y"}?|?H +%???/????? 3??>?%??VrU??Gxa?????R ?/0?gz?K[???2aO=???K(RB? +3d???o{???Z??VO;2=h?s?????4?y?MjAR???3]t7?(???x0??????9???%?P?lQa??"{?b]?{????P??y??\??6??? bD?????P?mV???h??1?#?n4 ]8????1c|???C??5?H?m?N?tm????????r?6???6b?D??[?8w?P?W? +gK1???>???!??qB???T?:?A?q??U??????h??F?K/3ic=??VJ&???{?]x?I Z~O;|?G!}??V??&?? r?F??F|?QfS +.?????????fXY?Nd7Rg +u???\?F?yR???Gz??????2?\.??O?>L?????z??x?J??)?Z?D?qbG????cv???N???jZcc?X?r^?^0v??|?|%W???????????*??q?l????????K?T?z|bY???kZ4??6Q$??n?????? ???++??N?,??*$e?C?k? ? X/?Gf??????d??O*/\?2?????2?`?*R???? ??A)? =???????D,?>?>H??qPU??c????????$*K|?(:??????;U?\??#7?kyj?` ?}???w?q?????i????@?)???? ??????d??ECBzb???{7???c ???=Ga???b?0x)?D at WG] ???"??2C??v~????@*??????#bTkhC???(?^U??X???^???S?Kl???5?????E1?S-? +?U??W?@??P??=?>?!????? ?675?????2?????9?W??U??~??md?????SO?`#u?AL??'R?`X?????????????s?#?L??)??< +??? +?7?Cs'??YJ"1?? +2?6?V?2??T1????K]???????7%?? ?_?L??????-???u?b#?5???T1?q?B??A????MC4e#3?????????(?l? +J?:nCp?,3~U???@?F{ye?f?#?2????*????&3??#??????FP?P?=?ZH ??;??`???? +?"(????????&CD??3???????|!-?d8???!????Vt????Up??b~????,-?R? +????????????z X ??=2+vu??????????gBk\:^??{????no?SC(?@dz????R???'???-}?/?Ug??8?ht$z?^[?S??~?,?yNI??:}?%?hE??{+?????^???kz:???????x?G ??_i??'???X=????Hl?_?\b??????4????? a?m_?w??S?;=$;?w????u4d7?%Ct??? +z?W?J +??uX?:? +bw?-# +???Y?.?rc +?7??]???????tW@C???m3?b}???1??C???5l??!?2???,0Y?????.z?????2-c?K{-$?#4Q? Z??Q???= +q??Jm+o?;r?,??'0?*???g??u? +?E?.???rv????$N?=??'[`&?}r????z??#t??Y??o?2????l?zQ?9???^bfrj?u>*/MM +?X???+?X??]]?A??????e???b?Orey?^?a?&:?}???? +??o??HM?bZ*????N>??Rm??????wu?=?'?????%?3?NH?h??u?O??<-???G?v?h???)?B?% ?? VX>???1" ??F?7???5??? ??\???C??6?M???0?^ ?(??X??tUt?R?t$??K?B???B????????(|?~?v????q$?/??Zm?:??K?{????Zc=???E?l??????5?M'?yt?Y%\??9eP?~rwg??0?B????,?>???Sh5I?S??? g???J~?~V???6??/???H????5???&1???7??I(??r??????m|Vuc?^v?E?*D&?????l??|[?D???D?/7??KC? +\? o?[?tKR1? ?]??y7?0l7<??6\m?]?b???E6???M2??]HW??z?N??? ?D@?~c?l'?84?:H???LC???? ?H???:?\?g??9??2???DP^??5??d???9Se?0&v?u??[0M^&??Y$B73!?;Jh_????? ???S?W? ?????d? ??OX???JxV?n?????p=?4r[?V?f?3??,????W?/???f? )??3"n?G?_?N??d??3???k?' ??3*?^?]??h???&!?Y?????/?bk0e%?J?F?i"?~?????(z?g?????$?^????????????B??G??L??,L?ER[?e{???C$??????PH3???? +\??????????f??!???cM??(????hvx?w?m??2??Gwc?'D2V?##\??z???p9?R`^?f#??????v ?mu?0n?X??p5???7?n.\=??/{?/?]?b:+?c?v??$f?[? +?????m??nE????{?0??@?bO??????L1????#??5h at K?R?~?_?$??}?! +r +\???Rn???B5k?^???$|??p????s_???A? ?E?.??$7R&?? J?????c????????D???qK???(?+kC???Y???B|!s3m?)?v$?A?(V`??????G??D&?F?G? +??????L"????2/ ?z??m?E:'?u???>?l????s7~? )_???dw??:??oN~H???7o0????70????=8?X?_????u/??y]?&?I??$?of?Y?` I??9?w6???????R.9??b??'?0P????a?\???s?T???7V??(?????)Fp>??^????J?)?E? O?'???FJ?>?"|?{? +(?V?rl????y??Zm?vg??V9y?{pi???/???pi??[z6????f?????"o???4<???H?j}%???^??v?F?'?x"???$:??Gj??*??;/???gD"iF?D??????v?7????e? +?\1??&????MrJ?\??,?0l?a??}??a= +??6Ws[?y>??{???+?? 7h??U&r???tpt???T???????2?C?????-?1?7???(M???y*???????0ye????J?@?%/?j??k??6n8??Q +??}?kh?H???~?llIf??z?)Y7???????? +? ????&?N3?xS?????[!????>????????Z6??~?}???Ne?7gD??/>????~?Z#?okL??G'?-??]?3???j?G??$glRW??]?TpNNd? +?????? +a'????8PsF?????Z??C2????Z?%?Ghn??'A?? ??<J??j?? +?(S???? +;tQ??????O??T?? ?j5???HNo??7?u?z:????V???&i???????!H?}~?d?? ?????????l???~?????Ek?~??????7e???q????3??\??W?????????e??Zl`?,?3?m?uP???3???????Y???(7-??+?????? *G\O?y?&?e???ID_4b??w??7l?????}VX?|h?5t?O}??R3???O???f?1???#;L'?~?{??????'.??P?"?}'???O????1`y!?????D\??g?Qx???Uws??U?? ?e????3?x?2?v?? +???K?E? ?|?H&??a~??^?????#p?p?? ?J????????$?wB9?N?]?B?lv?7V D??d?6???;????7Ds?/m<?q???f6R???I??)???M????? M?a-?L[F9??|?x?~?aQ"k??0?9E$E_}T#?????m$??Bp#?MV?s?|g?? ~? ?r?e4?[?????D\?????w^Z???;???d?O{?5Q(s??KSub +??}?K?:?7??b +5??????j?o???;I??*?I?c???T.???k?$???z^??yi?? ??R?Z?v?0B??Z?[?Zd!t????7 ??R?rzB7?m7'L3mSa`?S 8?a%???NC????;qM!A?\hU?pW???[??6e =??????ZP?W?/ +??????? V??v`V$?;H?N{d??4<??????Fl?????#???Di)??????-?M??c?G?;?V?9{??8p +K?"???F?!\??$?????f?~?????%???Y\???e!????m????mz?????t?Bbi/??]??b???Sh??9??^???J?1???o),8?}?}???9;?$d??!J????:"i??I?>?2E7?????????f)^?q :???DCR=?]T??ig??mE???????(d??L??????!??~u?-???/g??A?c?z94c2????r??i??? +?????? +w?.?? + `pb?'EeaUs??w??g,??K?:?I??.M%??#?????J??g?!U?YX?[?zMz????K at d>??a?Ej??6 ??;??OJT8????^???@??X??e?8Oi???????Fd?V?L??v???!(???)??r?;\=\??>8 Y?"q#??^???h?????%???8z +?????7t????"?J7?Q?@{n(}?f??.??o8?x??8+UL9??S?????w +?fyO???g??xrR5????2???+??$<?????e?L? ?(?a??S?-????ao ?z??5$=?]?v?2PL-???G?@??{s?)??7?.1??]????#?SJ???F?(2???>?$#! xW?y?f???&qmt??H????}???A|???_?s??r???^m>^??XU??Vh?????m +??a??^kE?34Y?p?OL +??vs\?]w???????Q/?>a?#DZhB7r???!D9$0KW?4Q?xc?mG?????????C??6?N??? +?uIVp??O5??????y?t???j|G??S?[??i?????x[????c??e"?=A?wX??tQd?2B.??l{W??3?o???\6?9>'?#?2???X??y"?+??t3??$;k?Tx????????=??.???T???b?j^??s ?Q????9?c??$?[k?z?r??OpkT[!??????On??j.????`??????E?m?5??!???d.?%??0?????)ic(?j]????T??%F??.{O!????P?!?v???>?[O\??????-.0?? +?Yb?????R??T/?%??c?1 +?S??l???y[????????. *[??'Qz????? ???z@7.??&(??W??.s?#???&G??V?D??\?6??V?m?????a!G??????2'U????s??????c?9_m??'?l??{???????'???????? +c?T?sF??R?>????&?q??+?????? ??$?v? #?b????DR>??]?i?4??q~./-?}k +cj??]?u??2????b??T????z??/????Xb?Z?3~???J?? +?"L???????e_???qi?fH#?}3z? + H??:?$t ??K????Tb?@BAb0J???|???????_^K#????8[ ?????-??6?4??*??s?r?? +?????q??????.?S?^???KZE????@?????C??D??MUpC?v?*7????m?4?h???a?Q&???R????c?O???B? +0????n??l???U????w??FE??n?2???Uh???'$?Ab??igZf??g?b??x? ??? Q??6=?-???R*?a?d??TQ,eH?L0|"'???(]U????O3q?????S??E|?j?7R.$?LUP??????t?????o?Z??8?m? /??:11S?8Dk?U?.??n?;6???v?u???F?S +??? w4?\??? \H??????3??X9JM???!?rr??x??>#"Y??`^Dd?? ?M??c]?z?}??.n>??%!E ???????.????<$v?m???? +=?|?%? ?}?m?P??[???^??n\??? ?oLZ??[u(z??Dt@???????d??c[?F0???P?i:??????hV?+?*?2g=N???#???\Qa??$c??)??s;???J +B?'???QJSh?i'????!?/?'?Z}Z???????mO?? ?ZE?uM??o?u???o?8K?xd7N??;???(???,??+? ??6?????I???67???,[$?CPmG???;_??/????????9~J??^z.6l???C%j??g????%{?3O?r?=??x??[?b????????''??????'?ev??$?C'.?n??n???^?Ym[???Af?BAv!?Fo?]I?????c?c???'j????;??Y X?|?23lN???????y'?~x???m?P????1? f??)?|D?>?c^?y?0/?@??Q/z?f?"7?,?i??~Q??q???f:.?b??$??V?`?'???]????? ?6??C????Q??hC|???mZT?^???j?????J???_???v +W?E? +??~?0?}?t??w??Hog??x6Bl?"q??????-.??=?y#+9[P?M???????? y??:??O+?[??z?O-?6?=?\A?`?K?o\?????~??d?B*??9???? ??:?S?_?\?`+h?P?C??????5?(Z?KA?5?a?,?V?2c:?od???|?-??5~????O??|????????]p|^??R?P>+??bn???????? +??? ,84??K??(?endstream +endobj +100 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 2 +/LastChar 149 +/Widths 646 0 R +/BaseFont /JDSEUT+NimbusRomNo9L-Regu +/FontDescriptor 98 0 R +>> endobj +98 0 obj << +/Ascent 678 +/CapHeight 651 +/Descent -216 +/FontName /JDSEUT+NimbusRomNo9L-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 450 +/FontBBox [-168 -281 1000 924] +/Flags 4 +/CharSet (/fi/fl/exclam/quotedbl/quoteright/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/bar/bullet) +/FontFile 99 0 R +>> endobj +646 0 obj +[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 0 0 0 0 333 333 333 0 0 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 564 564 564 0 921 722 667 667 722 611 556 722 722 333 389 0 611 889 722 722 556 722 667 556 611 722 722 944 722 722 0 333 0 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 200 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 350 ] +endobj +108 0 obj << +/Type /Pages +/Count 6 +/Parent 647 0 R +/Kids [94 0 R 110 0 R 139 0 R 143 0 R 184 0 R 212 0 R] +>> endobj +281 0 obj << +/Type /Pages +/Count 6 +/Parent 647 0 R +/Kids [246 0 R 283 0 R 324 0 R 359 0 R 402 0 R 447 0 R] +>> endobj +513 0 obj << +/Type /Pages +/Count 4 +/Parent 647 0 R +/Kids [468 0 R 515 0 R 566 0 R 611 0 R] +>> endobj +647 0 obj << +/Type /Pages +/Count 16 +/Kids [108 0 R 281 0 R 513 0 R] +>> endobj +648 0 obj << +/Type /Outlines +/First 7 0 R +/Last 87 0 R +/Count 5 +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 87 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 648 0 R +/Prev 63 0 R +/First 91 0 R +/Last 91 0 R +/Count -1 +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 63 0 R +/Prev 79 0 R +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 63 0 R +/Prev 75 0 R +/Next 83 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 63 0 R +/Prev 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 63 0 R +/Prev 67 0 R +/Next 75 0 R +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 63 0 R +/Next 71 0 R +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 648 0 R +/Prev 15 0 R +/Next 87 0 R +/First 67 0 R +/Last 83 0 R +/Count -5 +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 15 0 R +/Prev 55 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 15 0 R +/Prev 51 0 R +/Next 59 0 R +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 15 0 R +/Prev 39 0 R +/Next 55 0 R +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 39 0 R +/Prev 43 0 R +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 39 0 R +/Next 47 0 R +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 15 0 R +/Prev 35 0 R +/Next 51 0 R +/First 43 0 R +/Last 47 0 R +/Count -2 +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 15 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 15 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 15 0 R +/Prev 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 15 0 R +/Prev 19 0 R +/Next 27 0 R +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 15 0 R +/Next 23 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 648 0 R +/Prev 11 0 R +/Next 63 0 R +/First 19 0 R +/Last 59 0 R +/Count -9 +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 648 0 R +/Prev 7 0 R +/Next 15 0 R +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 648 0 R +/Next 11 0 R +>> endobj +649 0 obj << +/Names [(Doc-Start) 104 0 R (_adding_another_application) 220 0 R (_anonymous_files) 261 0 R (_arrays) 303 0 R (_bits) 624 0 R (_datatypes) 264 0 R (_fixed_array_mapper) 338 0 R (_foreach) 362 0 R (_hello_world) 153 0 R (_if) 385 0 R (_introduction) 146 0 R (_language_features) 187 0 R (_mappers) 318 0 R (_named_and_optional_parameters) 625 0 R (_parameters) 188 0 R (_running_on_a_remote_site) 445 0 R (_runtime_features) 439 0 R (_sequential_iteration) 392 0 R (_starting_and_restarting) 531 0 R (_the_regexp_mapper) 329 0 R (_visualising_the_workflow_as_a_graph) 440 0 R (_writing_a_mapper) 450 0 R (_writing_a_very_basic_mapper) 463 0 R (lstlisting.-1) 154 0 R (lstlisting.-10) 226 0 R (lstlisting.-11) 232 0 R (lstlisting.-12) 235 0 R (lstlisting.-13) 256 0 R (lstlisting.-14) 262 0 R (lstlisting.-15) 265 0 R (lstlisting.-16) 270 0 R (lstlisting.-17) 272 0 R (lstlisting.-18) 304 0 R (lstlisting.-19) 306 0 R (lstlisting.-2) 167 0 R (lstlisting.-20) 319 0 R (lstlisting.-21) 321 0 R (lstlisting.-22) 327 0 R (lstlisting.-23) 330 0 R (lstlisting.-24) 339 0 R (lstlisting.-25) 363 0 R (lstlisting.-26) 386 0 R (lstlisting.-27) 393 0 R (lstlisting.-28) 417 0 R (lstlisting.-29) 426 0 R (lstlisting.-3) 177 0 R (lstlisting.-30) 441 0 R (lstlisting.-31) 471 0 R (lstlisting.-32) 474 0 R (lstlisting.-33) 508 0 R (lstlisting.-34) 510 0 R (lstlisting.-35) 527 0 R (lstlisting.-36) 532 0 R (lstlisting.-37) 557 0 R (lstlisting.-38) 560 0 R (lstlisting.-39) 571 0 R (lstlisting.-4) 179 0 R (lstlisting.-40) 573 0 R (lstlisting.-41) 588 0 R (lstlisting.-42) 591 0 R (lstlisting.-43) 614 0 R (lstlisting.-44) 616 0 R (lstlisting.-45) 626 0 R (lstlisting.-46) 632 0 R (lstlisting.-47) 634 0 R (lstlisting.-5) 189 0 R (lstlisting.-6) 199 0 R (lstlisting.-7) 201 0 R (lstlisting.-8) 221 0 R (lstlisting.-9) 224 0 R (lstnumber.-1.1) 155 0 R (lstnumber.-1.2) 159 0 R (lstnumber.-1.3) 160 0 R (lstnumber.-1.4) 161 0 R (lstnumber.-1.5) 162 0 R (lstnumber.-1.6) 163 0 R (lstnumber.-1.7) 16 4 0 R (lstnumber.-1.8) 165 0 R (lstnumber.-1.9) 166 0 R (lstnumber.-10.1) 227 0 R (lstnumber.-10.2) 228 0 R (lstnumber.-10.3) 229 0 R (lstnumber.-10.4) 230 0 R (lstnumber.-10.5) 231 0 R (lstnumber.-11.1) 233 0 R (lstnumber.-11.2) 234 0 R (lstnumber.-12.1) 236 0 R (lstnumber.-12.10) 250 0 R (lstnumber.-12.11) 251 0 R (lstnumber.-12.12) 252 0 R (lstnumber.-12.13) 253 0 R (lstnumber.-12.14) 254 0 R (lstnumber.-12.15) 255 0 R (lstnumber.-12.2) 237 0 R (lstnumber.-12.3) 238 0 R (lstnumber.-12.4) 239 0 R (lstnumber.-12.5) 240 0 R (lstnumber.-12.6) 241 0 R (lstnumber.-12.7) 242 0 R (lstnumber.-12.8) 243 0 R (lstnumber.-12.9) 249 0 R (lstnumber.-13.1) 257 0 R (lstnumber.-13.2) 258 0 R (lstnumber.-13.3) 259 0 R (lstnumber.-13.4) 260 0 R (lstnumber.-14.1) 263 0 R (lstnumber.-15.1) 266 0 R (lstnumber.-15.2) 267 0 R (lstnumber.-15.3) 268 0 R (lstnumber.-15.4) 269 0 R (lstnumber.-16.1) 271 0 R (lstnumber.-17.1) 273 0 R (lstnumber.-17.10) 293 0 R (lstnumber.-17.11) 294 0 R (lstnumber.-17. 12) 295 0 R (lstnumber.-17.13) 296 0 R (lstnumber.-17.14) 297 0 R (lstnumber.-17.15) 298 0 R (lstnumber.-17.16) 299 0 R (lstnumber.-17.17) 300 0 R (lstnumber.-17.18) 301 0 R (lstnumber.-17.19) 302 0 R (lstnumber.-17.2) 274 0 R (lstnumber.-17.3) 275 0 R (lstnumber.-17.4) 276 0 R (lstnumber.-17.5) 277 0 R (lstnumber.-17.6) 278 0 R (lstnumber.-17.7) 279 0 R (lstnumber.-17.8) 280 0 R (lstnumber.-17.9) 286 0 R (lstnumber.-18.1) 305 0 R (lstnumber.-19.1) 307 0 R (lstnumber.-19.10) 316 0 R (lstnumber.-19.11) 317 0 R (lstnumber.-19.2) 308 0 R (lstnumber.-19.3) 309 0 R (lstnumber.-19.4) 310 0 R (lstnumber.-19.5) 311 0 R (lstnumber.-19.6) 312 0 R (lstnumber.-19.7) 313 0 R (lstnumber.-19.8) 314 0 R (lstnumber.-19.9) 315 0 R (lstnumber.-2.1) 168 0 R (lstnumber.-2.2) 169 0 R (lstnumber.-2.3) 170 0 R (lstnumber.-2.4) 171 0 R (lstnumber.-2.5) 172 0 R (lstnumber.-2.6) 173 0 R (lstnumber.-2.7) 174 0 R (lstnumber.-2.8) 175 0 R (lstnumber.-2.9) 176 0 R (lstnumber.-20.1) 320 0 R (lstnumber.-21. 1) 322 0 R (lstnumber.-22.1) 328 0 R (lstnumber.-23.1) 331 0 R (lstnumber.-23.2) 332 0 R (lstnumber.-23.3) 333 0 R (lstnumber.-23.4) 334 0 R (lstnumber.-23.5) 335 0 R (lstnumber.-23.6) 336 0 R (lstnumber.-23.7) 337 0 R (lstnumber.-24.1) 340 0 R (lstnumber.-24.10) 349 0 R (lstnumber.-24.11) 350 0 R (lstnumber.-24.12) 351 0 R (lstnumber.-24.13) 352 0 R (lstnumber.-24.14) 353 0 R (lstnumber.-24.15) 354 0 R (lstnumber.-24.16) 355 0 R (lstnumber.-24.17) 356 0 R (lstnumber.-24.18) 357 0 R (lstnumber.-24.2) 341 0 R (lstnumber.-24.3) 342 0 R (lstnumber.-24.4) 343 0 R (lstnumber.-24.5) 344 0 R (lstnumber.-24.6) 345 0 R (lstnumber.-24.7) 346 0 R (lstnumber.-24.8) 347 0 R (lstnumber.-24.9) 348 0 R (lstnumber.-25.1) 364 0 R (lstnumber.-25.10) 373 0 R (lstnumber.-25.11) 374 0 R (lstnumber.-25.12) 375 0 R (lstnumber.-25.13) 376 0 R (lstnumber.-25.14) 377 0 R (lstnumber.-25.15) 378 0 R (lstnumber.-25.16) 379 0 R (lstnumber.-25.17) 380 0 R (lstnumber.-25.18) 381 0 R (lstnumber.-25.19) 382 0 R (lstnumber.-25.2) 365 0 R (lstnumber.-25.20) 383 0 R (lstnumber.-25.21) 384 0 R (lstnumber.-25.3) 366 0 R (lstnumber.-25.4) 367 0 R (lstnumber.-25.5) 368 0 R (lstnumber.-25.6) 369 0 R (lstnumber.-25.7) 370 0 R (lstnumber.-25.8) 371 0 R (lstnumber.-25.9) 372 0 R (lstnumber.-26.1) 387 0 R (lstnumber.-26.2) 388 0 R (lstnumber.-26.3) 389 0 R (lstnumber.-26.4) 390 0 R (lstnumber.-26.5) 391 0 R (lstnumber.-27.1) 394 0 R (lstnumber.-27.10) 408 0 R (lstnumber.-27.11) 409 0 R (lstnumber.-27.12) 410 0 R (lstnumber.-27.13) 411 0 R (lstnumber.-27.14) 412 0 R (lstnumber.-27.15) 413 0 R (lstnumber.-27.16) 414 0 R (lstnumber.-27.17) 415 0 R (lstnumber.-27.18) 416 0 R (lstnumber.-27.2) 395 0 R (lstnumber.-27.3) 396 0 R (lstnumber.-27.4) 397 0 R (lstnumber.-27.5) 398 0 R (lstnumber.-27.6) 399 0 R (lstnumber.-27.7) 405 0 R (lstnumber.-27.8) 406 0 R (lstnumber.-27.9) 407 0 R (lstnumber.-28.1) 418 0 R (lstnumber.-28.2) 419 0 R (lstnumber.-28.3) 420 0 R (lstnumber.-28.4) 421 0 R (lstnumber.-2 8.5) 422 0 R (lstnumber.-28.6) 423 0 R (lstnumber.-28.7) 424 0 R (lstnumber.-28.8) 425 0 R (lstnumber.-29.1) 427 0 R (lstnumber.-29.10) 436 0 R (lstnumber.-29.11) 437 0 R (lstnumber.-29.12) 438 0 R (lstnumber.-29.2) 428 0 R (lstnumber.-29.3) 429 0 R (lstnumber.-29.4) 430 0 R (lstnumber.-29.5) 431 0 R (lstnumber.-29.6) 432 0 R (lstnumber.-29.7) 433 0 R (lstnumber.-29.8) 434 0 R (lstnumber.-29.9) 435 0 R (lstnumber.-3.1) 178 0 R (lstnumber.-30.1) 442 0 R (lstnumber.-30.2) 443 0 R (lstnumber.-31.1) 472 0 R (lstnumber.-31.2) 473 0 R (lstnumber.-32.1) 475 0 R (lstnumber.-32.10) 484 0 R (lstnumber.-32.11) 485 0 R (lstnumber.-32.12) 486 0 R (lstnumber.-32.13) 487 0 R (lstnumber.-32.14) 488 0 R (lstnumber.-32.15) 489 0 R (lstnumber.-32.16) 490 0 R (lstnumber.-32.17) 491 0 R (lstnumber.-32.18) 492 0 R (lstnumber.-32.19) 493 0 R (lstnumber.-32.2) 476 0 R (lstnumber.-32.20) 494 0 R (lstnumber.-32.21) 495 0 R (lstnumber.-32.22) 496 0 R (lstnumber.-32.23) 497 0 R (lstnumber.-32.24) 498 0 R (lstnumber.-32.25) 499 0 R (lstnumber.-32.26) 500 0 R (lstnumber.-32.27) 501 0 R (lstnumber.-32.28) 502 0 R (lstnumber.-32.29) 503 0 R (lstnumber.-32.3) 477 0 R (lstnumber.-32.30) 504 0 R (lstnumber.-32.31) 505 0 R (lstnumber.-32.32) 506 0 R (lstnumber.-32.33) 507 0 R (lstnumber.-32.4) 478 0 R (lstnumber.-32.5) 479 0 R (lstnumber.-32.6) 480 0 R (lstnumber.-32.7) 481 0 R (lstnumber.-32.8) 482 0 R (lstnumber.-32.9) 483 0 R (lstnumber.-33.1) 509 0 R (lstnumber.-34.1) 511 0 R (lstnumber.-34.10) 525 0 R (lstnumber.-34.11) 526 0 R (lstnumber.-34.2) 512 0 R (lstnumber.-34.3) 518 0 R (lstnumber.-34.4) 519 0 R (lstnumber.-34.5) 520 0 R (lstnumber.-34.6) 521 0 R (lstnumber.-34.7) 522 0 R (lstnumber.-34.8) 523 0 R (lstnumber.-34.9) 524 0 R (lstnumber.-35.1) 528 0 R (lstnumber.-35.2) 529 0 R (lstnumber.-36.1) 533 0 R (lstnumber.-36.10) 542 0 R (lstnumber.-36.11) 543 0 R (lstnumber.-36.12) 544 0 R (lstnumber.-36.13) 545 0 R (lstnumber.-36.14) 546 0 R (lstnumber.-36.15) 547 0 R (lstnum ber.-36.16) 548 0 R (lstnumber.-36.17) 549 0 R (lstnumber.-36.18) 550 0 R (lstnumber.-36.19) 551 0 R (lstnumber.-36.2) 534 0 R (lstnumber.-36.20) 552 0 R (lstnumber.-36.21) 553 0 R (lstnumber.-36.22) 554 0 R (lstnumber.-36.23) 555 0 R (lstnumber.-36.24) 556 0 R (lstnumber.-36.3) 535 0 R (lstnumber.-36.4) 536 0 R (lstnumber.-36.5) 537 0 R (lstnumber.-36.6) 538 0 R (lstnumber.-36.7) 539 0 R (lstnumber.-36.8) 540 0 R (lstnumber.-36.9) 541 0 R (lstnumber.-37.1) 558 0 R (lstnumber.-37.2) 559 0 R (lstnumber.-38.1) 561 0 R (lstnumber.-38.2) 562 0 R (lstnumber.-38.3) 563 0 R (lstnumber.-38.4) 564 0 R (lstnumber.-38.5) 569 0 R (lstnumber.-38.6) 570 0 R (lstnumber.-39.1) 572 0 R (lstnumber.-4.1) 180 0 R (lstnumber.-4.2) 181 0 R (lstnumber.-4.3) 182 0 R (lstnumber.-40.1) 574 0 R (lstnumber.-40.10) 583 0 R (lstnumber.-40.11) 584 0 R (lstnumber.-40.12) 585 0 R (lstnumber.-40.13) 586 0 R (lstnumber.-40.14) 587 0 R (lstnumber.-40.2) 575 0 R (lstnumber.-40.3) 576 0 R (lstnumber.-40.4) 577 0 R (lstnumber.-40.5) 578 0 R (lstnumber.-40.6) 579 0 R (lstnumber.-40.7) 580 0 R (lstnumber.-40.8) 581 0 R (lstnumber.-40.9) 582 0 R (lstnumber.-41.1) 589 0 R (lstnumber.-41.2) 590 0 R (lstnumber.-42.1) 592 0 R (lstnumber.-42.10) 601 0 R (lstnumber.-42.11) 602 0 R (lstnumber.-42.12) 603 0 R (lstnumber.-42.13) 604 0 R (lstnumber.-42.14) 605 0 R (lstnumber.-42.15) 606 0 R (lstnumber.-42.16) 607 0 R (lstnumber.-42.17) 608 0 R (lstnumber.-42.18) 609 0 R (lstnumber.-42.2) 593 0 R (lstnumber.-42.3) 594 0 R (lstnumber.-42.4) 595 0 R (lstnumber.-42.5) 596 0 R (lstnumber.-42.6) 597 0 R (lstnumber.-42.7) 598 0 R (lstnumber.-42.8) 599 0 R (lstnumber.-42.9) 600 0 R (lstnumber.-43.1) 615 0 R (lstnumber.-44.1) 617 0 R (lstnumber.-44.2) 618 0 R (lstnumber.-44.3) 619 0 R (lstnumber.-44.4) 620 0 R (lstnumber.-44.5) 621 0 R (lstnumber.-44.6) 622 0 R (lstnumber.-44.7) 623 0 R (lstnumber.-45.1) 627 0 R (lstnumber.-45.2) 628 0 R (lstnumber.-45.3) 629 0 R (lstnumber.-45.4) 630 0 R (lstnumber.-45. 5) 631 0 R (lstnumber.-46.1) 633 0 R (lstnumber.-47.1) 635 0 R (lstnumber.-5.1) 190 0 R (lstnumber.-5.2) 191 0 R (lstnumber.-5.3) 192 0 R (lstnumber.-5.4) 193 0 R (lstnumber.-5.5) 194 0 R (lstnumber.-5.6) 195 0 R (lstnumber.-5.7) 196 0 R (lstnumber.-5.8) 197 0 R (lstnumber.-5.9) 198 0 R (lstnumber.-6.1) 200 0 R (lstnumber.-7.1) 202 0 R (lstnumber.-7.10) 215 0 R (lstnumber.-7.11) 216 0 R (lstnumber.-7.12) 217 0 R (lstnumber.-7.13) 218 0 R (lstnumber.-7.2) 203 0 R (lstnumber.-7.3) 204 0 R (lstnumber.-7.4) 205 0 R (lstnumber.-7.5) 206 0 R (lstnumber.-7.6) 207 0 R (lstnumber.-7.7) 208 0 R (lstnumber.-7.8) 209 0 R (lstnumber.-7.9) 210 0 R (lstnumber.-8.1) 222 0 R (lstnumber.-8.2) 223 0 R (lstnumber.-9.1) 225 0 R (named_parameters) 244 0 R (page.1) 145 0 R (page.10) 470 0 R (page.11) 517 0 R (page.12) 568 0 R (page.13) 613 0 R (page.2) 186 0 R (page.3) 214 0 R (page.4) 248 0 R (page.5) 285 0 R (page.6) 326 0 R (page.7) 361 0 R (page.8) 404 0 R (page.9) 449 0 R (page.i) 97 0 R (pag e.ii) 112 0 R (page.iii) 141 0 R (section.1) 6 0 R (section.2) 10 0 R (section.3) 14 0 R (section.4) 62 0 R (section.5) 86 0 R (subsection.3.1) 18 0 R (subsection.3.2) 22 0 R (subsection.3.3) 26 0 R (subsection.3.4) 30 0 R (subsection.3.5) 34 0 R (subsection.3.6) 38 0 R (subsection.3.7) 50 0 R (subsection.3.8) 54 0 R (subsection.3.9) 58 0 R (subsection.4.1) 66 0 R (subsection.4.2) 70 0 R (subsection.4.3) 74 0 R (subsection.4.4) 78 0 R (subsection.4.5) 82 0 R (subsection.5.1) 90 0 R (subsubsection.3.6.1) 42 0 R (subsubsection.3.6.2) 46 0 R] +/Limits [(Doc-Start) (subsubsection.3.6.2)] +>> endobj +650 0 obj << +/Kids [649 0 R] +>> endobj +651 0 obj << +/Dests 650 0 R +>> endobj +652 0 obj << +/Type /Catalog +/Pages 647 0 R +/Outlines 648 0 R +/Names 651 0 R +/PageMode /UseOutlines +/OpenAction 93 0 R +>> endobj +653 0 obj << +/Author()/Title(A Swift Tutorial)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() +/CreationDate (D:20110516142225-05'00') +/PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) +>> endobj +xref +0 654 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000014704 00000 n +0000190452 00000 n +0000000054 00000 n +0000000084 00000 n +0000014828 00000 n +0000190366 00000 n +0000000129 00000 n +0000000159 00000 n +0000020667 00000 n +0000190241 00000 n +0000000205 00000 n +0000000241 00000 n +0000020792 00000 n +0000190167 00000 n +0000000292 00000 n +0000000321 00000 n +0000028277 00000 n +0000190080 00000 n +0000000372 00000 n +0000000417 00000 n +0000034470 00000 n +0000189993 00000 n +0000000468 00000 n +0000000502 00000 n +0000034721 00000 n +0000189906 00000 n +0000000553 00000 n +0000000581 00000 n +0000041326 00000 n +0000189819 00000 n +0000000632 00000 n +0000000657 00000 n +0000042332 00000 n +0000189695 00000 n +0000000708 00000 n +0000000734 00000 n +0000047548 00000 n +0000189621 00000 n +0000000790 00000 n +0000000826 00000 n +0000048177 00000 n +0000189547 00000 n +0000000882 00000 n +0000000925 00000 n +0000054278 00000 n +0000189460 00000 n +0000000976 00000 n +0000001002 00000 n +0000055787 00000 n +0000189373 00000 n +0000001053 00000 n +0000001074 00000 n +0000056287 00000 n +0000189299 00000 n +0000001125 00000 n +0000001164 00000 n +0000064645 00000 n +0000189174 00000 n +0000001210 00000 n +0000001245 00000 n +0000064769 00000 n +0000189100 00000 n +0000001296 00000 n +0000001350 00000 n +0000065081 00000 n +0000189013 00000 n +0000001401 00000 n +0000001444 00000 n +0000072874 00000 n +0000188926 00000 n +0000001495 00000 n +0000001530 00000 n +0000072999 00000 n +0000188839 00000 n +0000001581 00000 n +0000001627 00000 n +0000087023 00000 n +0000188765 00000 n +0000001678 00000 n +0000001720 00000 n +0000100510 00000 n +0000188653 00000 n +0000001766 00000 n +0000001789 00000 n +0000100635 00000 n +0000188592 00000 n +0000001840 00000 n +0000001888 00000 n +0000002310 00000 n +0000002552 00000 n +0000001939 00000 n +0000002429 00000 n +0000187104 00000 n +0000167604 00000 n +0000186932 00000 n +0000166974 00000 n +0000159388 00000 n +0000166803 00000 n +0000002490 00000 n +0000158674 00000 n +0000147555 00000 n +0000158504 00000 n +0000188106 00000 n +0000008468 00000 n +0000004598 00000 n +0000002649 00000 n +0000008405 00000 n +0000004908 00000 n +0000146940 00000 n +0000135584 00000 n +0000146767 00000 n +0000005062 00000 n +0000005217 00000 n +0000005372 00000 n +0000005532 00000 n +0000005692 00000 n +0000005852 00000 n +0000006012 00000 n +0000006172 00000 n +0000006332 00000 n +0000006497 00000 n +0000006662 00000 n +0000006821 00000 n +0000006981 00000 n +0000007141 00000 n +0000007295 00000 n +0000007455 00000 n +0000007615 00000 n +0000007774 00000 n +0000007933 00000 n +0000008092 00000 n +0000008246 00000 n +0000009232 00000 n +0000009047 00000 n +0000008579 00000 n +0000009169 00000 n +0000016586 00000 n +0000013857 00000 n +0000009330 00000 n +0000014641 00000 n +0000014765 00000 n +0000135249 00000 n +0000127186 00000 n +0000135071 00000 n +0000014015 00000 n +0000014226 00000 n +0000014436 00000 n +0000014890 00000 n +0000014953 00000 n +0000015016 00000 n +0000126251 00000 n +0000107393 00000 n +0000126080 00000 n +0000015079 00000 n +0000015142 00000 n +0000015205 00000 n +0000015268 00000 n +0000015331 00000 n +0000015394 00000 n +0000015457 00000 n +0000015520 00000 n +0000015581 00000 n +0000015644 00000 n +0000015707 00000 n +0000015770 00000 n +0000015833 00000 n +0000015896 00000 n +0000015959 00000 n +0000016022 00000 n +0000016084 00000 n +0000016145 00000 n +0000016208 00000 n +0000016271 00000 n +0000016334 00000 n +0000016397 00000 n +0000016460 00000 n +0000016523 00000 n +0000022300 00000 n +0000020482 00000 n +0000016723 00000 n +0000020604 00000 n +0000020729 00000 n +0000020854 00000 n +0000020917 00000 n +0000020980 00000 n +0000021043 00000 n +0000021106 00000 n +0000021169 00000 n +0000021232 00000 n +0000021295 00000 n +0000021358 00000 n +0000021421 00000 n +0000021484 00000 n +0000021546 00000 n +0000021609 00000 n +0000021672 00000 n +0000021735 00000 n +0000021798 00000 n +0000021861 00000 n +0000021924 00000 n +0000021987 00000 n +0000022050 00000 n +0000022112 00000 n +0000022175 00000 n +0000022238 00000 n +0000029848 00000 n +0000027658 00000 n +0000022424 00000 n +0000027962 00000 n +0000028025 00000 n +0000028088 00000 n +0000028151 00000 n +0000028214 00000 n +0000027800 00000 n +0000028339 00000 n +0000028402 00000 n +0000028465 00000 n +0000028528 00000 n +0000028591 00000 n +0000028653 00000 n +0000028716 00000 n +0000028779 00000 n +0000028842 00000 n +0000028905 00000 n +0000028968 00000 n +0000029031 00000 n +0000029094 00000 n +0000029157 00000 n +0000029220 00000 n +0000029283 00000 n +0000029346 00000 n +0000029409 00000 n +0000029472 00000 n +0000029535 00000 n +0000029598 00000 n +0000029660 00000 n +0000029723 00000 n +0000029786 00000 n +0000101501 00000 n +0000035852 00000 n +0000033530 00000 n +0000029972 00000 n +0000033652 00000 n +0000033715 00000 n +0000033778 00000 n +0000033841 00000 n +0000033904 00000 n +0000033967 00000 n +0000034029 00000 n +0000034092 00000 n +0000034155 00000 n +0000034218 00000 n +0000034281 00000 n +0000034344 00000 n +0000034407 00000 n +0000034532 00000 n +0000034595 00000 n +0000034658 00000 n +0000034783 00000 n +0000034846 00000 n +0000034909 00000 n +0000034972 00000 n +0000035035 00000 n +0000035098 00000 n +0000035161 00000 n +0000035224 00000 n +0000035287 00000 n +0000035350 00000 n +0000035413 00000 n +0000035476 00000 n +0000035539 00000 n +0000035602 00000 n +0000035664 00000 n +0000035727 00000 n +0000035790 00000 n +0000188222 00000 n +0000042709 00000 n +0000040449 00000 n +0000035963 00000 n +0000040571 00000 n +0000040634 00000 n +0000105178 00000 n +0000103721 00000 n +0000105017 00000 n +0000103386 00000 n +0000101532 00000 n +0000103225 00000 n +0000040697 00000 n +0000040760 00000 n +0000040823 00000 n +0000040885 00000 n +0000040948 00000 n +0000041011 00000 n +0000041074 00000 n +0000041137 00000 n +0000041200 00000 n +0000041263 00000 n +0000041388 00000 n +0000041451 00000 n +0000041514 00000 n +0000041577 00000 n +0000041640 00000 n +0000041703 00000 n +0000041765 00000 n +0000041828 00000 n +0000041891 00000 n +0000041954 00000 n +0000042017 00000 n +0000042080 00000 n +0000042143 00000 n +0000042206 00000 n +0000042269 00000 n +0000042394 00000 n +0000042457 00000 n +0000042520 00000 n +0000042583 00000 n +0000042646 00000 n +0000049497 00000 n +0000047237 00000 n +0000042847 00000 n +0000047359 00000 n +0000047422 00000 n +0000047485 00000 n +0000047610 00000 n +0000047673 00000 n +0000047736 00000 n +0000047799 00000 n +0000047862 00000 n +0000047925 00000 n +0000047988 00000 n +0000048051 00000 n +0000048114 00000 n +0000048239 00000 n +0000048302 00000 n +0000048365 00000 n +0000048427 00000 n +0000048490 00000 n +0000048553 00000 n +0000048616 00000 n +0000048679 00000 n +0000048742 00000 n +0000048805 00000 n +0000048868 00000 n +0000048931 00000 n +0000048994 00000 n +0000049057 00000 n +0000049119 00000 n +0000049182 00000 n +0000049245 00000 n +0000049308 00000 n +0000049371 00000 n +0000049434 00000 n +0000056851 00000 n +0000054093 00000 n +0000049608 00000 n +0000054215 00000 n +0000054340 00000 n +0000054403 00000 n +0000054466 00000 n +0000054529 00000 n +0000054592 00000 n +0000054655 00000 n +0000054718 00000 n +0000054781 00000 n +0000054844 00000 n +0000054907 00000 n +0000054970 00000 n +0000055032 00000 n +0000055095 00000 n +0000055158 00000 n +0000055221 00000 n +0000055284 00000 n +0000055347 00000 n +0000055410 00000 n +0000055473 00000 n +0000055536 00000 n +0000055599 00000 n +0000055662 00000 n +0000055724 00000 n +0000055848 00000 n +0000055910 00000 n +0000055972 00000 n +0000056035 00000 n +0000056098 00000 n +0000056161 00000 n +0000056224 00000 n +0000056349 00000 n +0000056412 00000 n +0000056475 00000 n +0000056538 00000 n +0000056601 00000 n +0000056663 00000 n +0000056726 00000 n +0000056789 00000 n +0000069155 00000 n +0000065206 00000 n +0000062127 00000 n +0000056975 00000 n +0000062443 00000 n +0000062506 00000 n +0000062569 00000 n +0000062632 00000 n +0000062695 00000 n +0000062758 00000 n +0000062820 00000 n +0000062883 00000 n +0000062946 00000 n +0000063009 00000 n +0000063072 00000 n +0000063135 00000 n +0000063198 00000 n +0000063261 00000 n +0000063324 00000 n +0000063387 00000 n +0000063450 00000 n +0000063513 00000 n +0000063576 00000 n +0000063639 00000 n +0000063702 00000 n +0000063765 00000 n +0000063828 00000 n +0000063890 00000 n +0000063953 00000 n +0000064016 00000 n +0000064079 00000 n +0000064142 00000 n +0000064205 00000 n +0000064268 00000 n +0000064330 00000 n +0000064393 00000 n +0000064456 00000 n +0000064519 00000 n +0000064582 00000 n +0000064707 00000 n +0000064830 00000 n +0000064893 00000 n +0000064956 00000 n +0000065018 00000 n +0000062269 00000 n +0000065143 00000 n +0000073124 00000 n +0000068925 00000 n +0000065317 00000 n +0000072811 00000 n +0000072936 00000 n +0000070044 00000 n +0000070277 00000 n +0000070509 00000 n +0000070740 00000 n +0000070979 00000 n +0000071204 00000 n +0000071426 00000 n +0000071657 00000 n +0000071883 00000 n +0000072113 00000 n +0000072362 00000 n +0000072586 00000 n +0000073061 00000 n +0000069841 00000 n +0000069976 00000 n +0000070023 00000 n +0000081019 00000 n +0000078194 00000 n +0000073263 00000 n +0000078316 00000 n +0000078379 00000 n +0000078442 00000 n +0000078505 00000 n +0000078568 00000 n +0000078631 00000 n +0000078693 00000 n +0000078756 00000 n +0000078819 00000 n +0000078882 00000 n +0000078945 00000 n +0000079008 00000 n +0000079071 00000 n +0000079134 00000 n +0000079197 00000 n +0000079260 00000 n +0000079321 00000 n +0000079384 00000 n +0000079447 00000 n +0000079510 00000 n +0000079573 00000 n +0000079636 00000 n +0000079699 00000 n +0000079762 00000 n +0000079825 00000 n +0000079888 00000 n +0000079951 00000 n +0000080013 00000 n +0000080076 00000 n +0000080139 00000 n +0000080202 00000 n +0000080265 00000 n +0000080328 00000 n +0000080391 00000 n +0000080454 00000 n +0000080517 00000 n +0000080580 00000 n +0000080642 00000 n +0000080705 00000 n +0000080768 00000 n +0000080831 00000 n +0000080894 00000 n +0000080957 00000 n +0000188339 00000 n +0000089223 00000 n +0000085806 00000 n +0000081117 00000 n +0000086206 00000 n +0000086269 00000 n +0000086332 00000 n +0000086395 00000 n +0000086458 00000 n +0000086521 00000 n +0000086583 00000 n +0000086646 00000 n +0000086709 00000 n +0000086772 00000 n +0000086835 00000 n +0000086898 00000 n +0000086960 00000 n +0000085948 00000 n +0000087085 00000 n +0000087148 00000 n +0000087211 00000 n +0000087274 00000 n +0000087337 00000 n +0000087400 00000 n +0000087463 00000 n +0000087526 00000 n +0000087588 00000 n +0000087651 00000 n +0000087714 00000 n +0000087777 00000 n +0000087840 00000 n +0000087903 00000 n +0000087966 00000 n +0000088029 00000 n +0000088092 00000 n +0000088155 00000 n +0000088217 00000 n +0000088280 00000 n +0000088343 00000 n +0000088406 00000 n +0000088469 00000 n +0000088532 00000 n +0000088595 00000 n +0000088658 00000 n +0000088721 00000 n +0000088784 00000 n +0000088847 00000 n +0000088910 00000 n +0000088973 00000 n +0000089035 00000 n +0000089098 00000 n +0000089161 00000 n +0000096604 00000 n +0000093840 00000 n +0000089334 00000 n +0000093962 00000 n +0000094025 00000 n +0000094088 00000 n +0000094151 00000 n +0000094214 00000 n +0000094277 00000 n +0000094340 00000 n +0000094402 00000 n +0000094465 00000 n +0000094528 00000 n +0000094591 00000 n +0000094654 00000 n +0000094717 00000 n +0000094780 00000 n +0000094843 00000 n +0000094906 00000 n +0000094969 00000 n +0000095032 00000 n +0000095094 00000 n +0000095157 00000 n +0000095220 00000 n +0000095283 00000 n +0000095346 00000 n +0000095409 00000 n +0000095472 00000 n +0000095535 00000 n +0000095597 00000 n +0000095660 00000 n +0000095723 00000 n +0000095786 00000 n +0000095849 00000 n +0000095912 00000 n +0000095975 00000 n +0000096038 00000 n +0000096101 00000 n +0000096164 00000 n +0000096227 00000 n +0000096289 00000 n +0000096352 00000 n +0000096415 00000 n +0000096478 00000 n +0000096541 00000 n +0000101390 00000 n +0000099696 00000 n +0000096702 00000 n +0000099818 00000 n +0000099881 00000 n +0000099944 00000 n +0000100007 00000 n +0000100070 00000 n +0000100133 00000 n +0000100196 00000 n +0000100259 00000 n +0000100322 00000 n +0000100385 00000 n +0000100447 00000 n +0000100572 00000 n +0000100697 00000 n +0000100760 00000 n +0000100823 00000 n +0000100886 00000 n +0000100949 00000 n +0000101012 00000 n +0000101075 00000 n +0000101138 00000 n +0000101201 00000 n +0000101264 00000 n +0000101327 00000 n +0000103626 00000 n +0000103602 00000 n +0000105415 00000 n +0000105390 00000 n +0000105505 00000 n +0000126814 00000 n +0000135494 00000 n +0000147236 00000 n +0000159026 00000 n +0000167336 00000 n +0000187626 00000 n +0000188440 00000 n +0000188518 00000 n +0000190524 00000 n +0000202016 00000 n +0000202055 00000 n +0000202093 00000 n +0000202222 00000 n +trailer +<< +/Size 654 +/Root 652 0 R +/Info 653 0 R +/ID [<624EFF68B3B6150ADBBC3276EFE85189> <624EFF68B3B6150ADBBC3276EFE85189>] +>> +startxref +202485 +%%EOF Added: branches/release-0.92/docs/tutorial/tutorial.txt =================================================================== --- branches/release-0.92/docs/tutorial/tutorial.txt (rev 0) +++ branches/release-0.92/docs/tutorial/tutorial.txt 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,900 @@ +A Swift Tutorial +================ + +:toc: +:icons: +:website: http://www.ci.uchicago.edu/swift/guides/tutorial.php +:numbered: + +[abstract] +Abstract +-------- +This is an introductory tutorial on the use of Swift and its programming +language SwiftScript. + +Introduction +------------ +This tutorial is intended to introduce new users to the basics of Swift. +It is structured as a series of small exercise/examples which you can +try for yourself as you read along. After the first 'hello world' +example, there are two tracks - the language track (which introduces +features of the SwiftScript language) and the runtime track (which +introduces features of the Swift runtime environment, such as running +jobs on different sites). + +For information on getting an installation of Swift running, consult the +Swift Quickstart Guide , and +return to this document when you have successfully run the test +SwiftScript program mentioned there. + +There is also a Swift User's Guide + which contains +more detailed reference material on topics covered in this manual. All +of the programs included in this tutorial can be found in your Swift +distribution in the examples/swift directory. + +Hello World +----------- +The first example program, first.swift, outputs a hello world message +into a file called hello.txt. + +.first.swift +************ +[java] +source~~~~ +include::../../examples/first.swift[] +source~~~~ +************ + +We can run this program as follows: +[java] +source~~~~ +$ cd examples/swift/ +$ swift first.swift +Swift svn swift-r3334 (swift modified locally) cog-r2752 + +RunID: 20100526-1925-8zjupq1b +Progress: +Final status: Finished successfully:1 +$ cat hello.txt +Hello, world! +source~~~~ + +The basic structure of this program is a type definition, an +application procedure definition, a variable definition and then a +call to the procedure: + +[java] +source~~~~ +type messagefile; +source~~~~ + +First we define a new type, called messagefile. In this example, we will +use this messagefile type as the type for our output message. + + +All data in SwiftScript must be typed, whether it is stored in memory or +on disk. This example defines a very simple type. Later on we will see +more complex type examples. + +[java] +source~~~~ +app (messagefile t) greeting() { + echo "Hello, world!" stdout=@filename(t); +} +source~~~~ + +Next we define a procedure called greeting. This procedure will write +out the "hello world" message to a file. + +To achieve this, it executes the unix utility 'echo' with a parameter +"Hello, world!" and directs the standard output into the output file. + +The actual file to use is specified by the return parameter, t. + +messagefile outfile <"hello.txt">; + +Here we define a variable called outfile. The type of this variable is +messagefile, and we specify that the contents of this variable will be +stored on disk in a file called hello.txt + +outfile = greeting(); + +Now we call the greeting procedure, with its output going to the outfile +variable and therefore to hello.txt on disk. + +Over the following exercises, we'll extend this simple hello world +program to demonstrate various features of Swift. + + +Language features +----------------- + +Parameters +~~~~~~~~~~ + +Procedures can have parameters. Input parameters specify inputs to the +procedure and output parameters specify outputs. Our helloworld greeting +procedure already uses an output parameter, t, which indicates where the +greeting output will go. In this section, we will add an input parameter +to the greeting function. + +The code changes from first.swift are highlighted below. + +[java] +source~~~~ +include::../../examples/parameter.swift[] +source~~~~ + +We have modified the signature of the greeting procedure to indicate +that it takes a single parameter, s, of type 'string'. + +We have modified the invocation of the 'echo' utility so that it takes +the value of s as a parameter, instead of the string literal "Hello, +world!". + +We have modified the output file definition to point to a different file +on disk. + +We have modified the invocation of greeting so that a greeting string is +supplied. + +The code for this section can be found in parameter.swift. It can be +invoked using the swift command, with output appearing in hello2.txt: + +[java] +source~~~~ +$ swift parameter.swift +source~~~~ + +Now that we can choose our greeting text, we can call the same procedure +with different parameters to generate several output files with +different greetings. The code is in manyparam.swift and can be run as +before using the swift command. + +[java] +source~~~~ +include::../../examples/manyparam.swift[] +source~~~~ + +Note that we can intermingle definitions of variables with invocations +of procedures. + +When this program has been run, there should be three new files in the +working directory (english.txt, francais.txt and nihongo.txt) each +containing a greeting in a different language. + +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified - see <>. + +Adding another application +~~~~~~~~~~~~~~~~~~~~~~~~~~ +Now we'll define a new application procedure. The procedure we define +will capitalise all the words in the input file. + +To do this, we'll use the unix tr (translate) utility. Here is an +example of using tr on the unix command line, not using Swift: + +[java] +source~~~~ +$ echo hello | tr '[a-z]' '[A-Z]' +HELLO +source~~~~ + +.There are several steps +- transformation catalog +- application block + +First we need to modify the transformation catalog to define a logical +transformation for the tc utility. The transformation catalog can be +found in etc/tc.data. There are already several entries specifying +where programs can be found. Add a new line to the file, specifying +where *tr* can be found (usually in /usr/bin/tr but it may differ on +your system), like this: + +[java] +source~~~~ +localhost tr /usr/bin/tr INSTALLED INTEL32::LINUX null +source~~~~ + +For now, ignore all of the fields except the second and the third. The +second field tr specifies a logical application name and the third +specifies the location of the application executable. + +Now that we have defined where to find tr, we can use it in SwiftScript. + +We can define a new procedure, capitalise, which calls tr. + +[java] +source~~~~ +(messagefile o) capitalise(messagefile i) { + app { + tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); + } +} +source~~~~ +We can call capitalise like this: + +[java] +source~~~~ +messagefile final <"capitals.txt">; +final = capitalise(hellofile); +source~~~~ + +So a full program based on the first exercise might look like this: + +[java] +source~~~~ +include::../../examples/second_procedure.swift[] +source~~~~ + +We can use the swift command to run it like this. + +[java] +source~~~~ +$ swift second_procedure.swift +... +$ cat capitals.txt +HELLO FROM SWIFT +source~~~~ + +Anonymous files +~~~~~~~~~~~~~~~ +In the previous section, the file greeting.txt is used only to store +an intermediate result. We don't really care about which name is used +for the file, and we can let Swift choose the name. + +To do that, omit the mapping entirely when declaring outfile: + +[java] +source~~~~ +messagefile outfile; +source~~~~ + +Swift will choose a filename, which in the present version will be in a +subdirectory called _concurrent. + + +Datatypes +~~~~~~~~~ +All data in variables and files has a data type. So far, we've seen two +types: + + - string - this is a built-in type for storing strings of text in + memory, much like in other programming languages + - messagefile - this is a user-defined type used to mark files as + containing messages + +SwiftScript has the additional built-in types: boolean, integer and +float that function much like their counterparts in other programming +languages. + +It is also possible to create user defined types with more structure, +for example: + +[java] +source~~~~ +type details { + string name; + int pies; +} +source~~~~ + +Each element of the structured type can be accessed using a . like this: + +[java] +source~~~~ +person.name = "john"; +source~~~~ + +The following complete program, types.swift, outputs a greeting using a +user-defined structure type to hold parameters for the message: + +[java] +source~~~~ +include::../../examples/types.swift[] +source~~~~ + +Structured types can be comprised of marker types for files. See the +later section on mappers for more information about this. + + +Arrays +~~~~~~ + +We can define arrays using the [] suffix in a variable declaration: + +[java] +source~~~~ +messagefile m[]; +source~~~~ + +This program, q5.swift, will declare an array of message files. + +[java] +source~~~~ +include::../../examples/q5.swift[] +source~~~~ + +Observe that the type of the parameter to greeting is now an array of +strings, string s[], instead of a single string, string s, that +elements of the array can be referenced numerically, for example s[0], +and that the array is initialised using an array literal, +["how","are","you"]. + + +Mappers +~~~~~~~ + +A significant difference between SwiftScript and other languages is that +data can be referred to on disk through variables in a very similar +fashion to data in memory. For example, in the above examples we have +seen a variable definition like this: + +[java] +source~~~~ +messagefile outfile <"q13greeting.txt">; +source~~~~ + +This means that outfile is a dataset variable, which is mapped to a +file on disk called g13greeting.txt. This variable can be assigned to +using = in a similar fashion to an in-memory variable. We can say that +outfile is mapped onto the disk file q13greeting.txt by a mapper. + +There are various ways of mapping in SwiftScript. Two forms have already +been seen in this tutorial. Later exercises will introduce more forms. + +The two forms of mapping seen so far are: + +simple named mapping - the name of the file that a variable is mapped to +is explictly listed. Like this: + +[java] +source~~~~ +messagefile outfile <"greeting.txt">; +source~~~~ + +This is useful when you want to explicitly name input and output files +for your program. For example, outfile in exercise HELLOWORLD. + +anonymous mapping - no name is specified in the source code. A name is +automatically generated for the file. This is useful for intermediate +files that are only referenced through SwiftScript, such as outfile in +exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by +ommitting any mapper definition, like this: + +[java] +source~~~~ +messagefile outfile; +source~~~~ + +Later exercises will introduce other ways of mapping from disk files to +SwiftScript variables. + +TODO: introduce @v syntax. + + +The Regexp Mapper +^^^^^^^^^^^^^^^^^ +In this exercise, we introduce the regexp mapper. This mapper +transforms a string expression using a regular expression, and uses the +result of that transformation as the filename to map. + +regexp.swift demonstrates the use of this by placing output into a +file that is based on the name of the input file: our input file is +mapped to the inputfile variable using the simple named mapper, and then +we use the regular expression mapper to map the output file. Then we use +the countwords() procedure to count the works in the input file and +store the result in the output file. In order for the countwords() +procedure to work correctly, add the wc utility (usually found in +/usr/bin/wc) to tc.data. + +The important bit of regexp.swift is: + +[java] +source~~~~ +messagefile inputfile <"q16.txt">; + +countfile c ; +source~~~~ + +fixed_array_mapper +^^^^^^^^^^^^^^^^^^ +The fixed array mapper maps a list of files into an array - each +element of the array is mapped into one file in the specified directory. +See fixedarray.swift. + +[java] +source~~~~ +include::../../examples/fixedarray.swift[] +source~~~~ + +foreach +~~~~~~~ +SwiftScript provides a control structure, foreach, to operate on each +element of an array. + +In this example, we will run the previous word counting example over +each file in an array without having to explicitly list the array +elements. The source code for this example is in foreach.swift. The +three input files: one.txt, two.txt and three.txt are supplied. +After you have run the workflow, you should see that there are three +output files: one.count, two.count and three.count, each +containing the word count for the corresponding input file. We combine +the use of the fixed_array_mapper and the regexp_mapper. + +[java] +source~~~~ +include::../../examples/foreach.swift[] +source~~~~ + +If +~~ +Decisions can be made using 'if', like this: + +[java] +source~~~~ +if(morning) { + outfile = greeting("good morning"); +} else { + outfile = greeting("good afternoon"); +} +source~~~~ + +if.swift contains a simple example of this. Compile and run if.swift +and see that it outputs "good morning". Changing the morning variable +from true to false will cause the program to output "good afternoon". + +Sequential iteration +~~~~~~~~~~~~~~~~~~~~ + +A development version of Swift after 0.2 (revision 1230) introduces a +sequential iteration construct. + +The following example demonstrates a simple application: each step of +the iteration is a string representation of the byte count of the +previous step's output, with iteration terminating when the byte count +reaches zero. + +Here's the program: + +[java] +source~~~~ +include::../../examples/iterate.swift[] +source~~~~ + +echo is the standard unix echo. + +wcl is our application code - it counts the number of bytes in the one +file and writes that count out to another, like this: + +[java] +source~~~~ +$ cat ../wcl +#!/bin/bash +echo -n $(wc -c < $1) > $2 + +$ echo -n hello > a +$ wcl a b +$ cat b +5 +source~~~~ + +Install the above wcl script somewhere and add a transformation catalog +entry for it. Then run the example program like this: + +[java] +source~~~~ +$ swift iterate.swift +Swift svn swift-r3334 cog-r2752 + +RunID: 20100526-2259-gtlz8zf4 +Progress: +SwiftScript trace: extract int value , 16.0 +SwiftScript trace: extract int value , 2.0 +SwiftScript trace: extract int value , 1.0 +Final status: Finished successfully:4 + +$ ls foldout* +foldout0000 foldout0001 foldout0002 foldout0003 +source~~~~ + +Runtime features +---------------- + +Visualising the workflow as a graph +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +When running a workflow, its possible to generate a provenance graph at +the same time: + +[java] +source~~~~~ +$ swift -pgraph graph.dot first.swift +$ dot -ograph.png -Tpng graph.dot +source~~~~ + +graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org. + +Running on a remote site +~~~~~~~~~~~~~~~~~~~~~~~~ + +As configured by default, all jobs are run locally. In the previous +examples, we've invoked echo and tr executables from our SwiftScript +program. These have been run on the local system (the same computer on +which you ran swift). We can also make our computations run on a +remote resource. + +WARNING: This example is necessarily more vague than previous examples, +because its requires access to remote resources. You should ensure that +you can submit a job using the globus-job-run (or globusrun-ws?) +command(s). + +We do not need to modify any SwiftScript code to run on another +resource. Instead, we must modify another catalog, the site catalog. +This catalog provides details of the location that applications will be +run, with the default settings referring to the local machine. We will +modify it to refer to a remote resource - the UC Teraport cluster. If +you are not a UC Teraport user, you should use details of a different +resource that you do have access to. + +The site catalog is located in etc/sites.xml and is a relatively +straightforward XML format file. We must modify each of the following +three settings: gridftp (which indicates how and where data can be +transferred to the remote resource), jobmanager (which indicates how +applications can be run on the remote resource) and workdirectory (which +indicates where working storage can be found on the remote resource). + + +Writing a mapper +~~~~~~~~~~~~~~~~ + +This section will introduce writing a custom mapper so that Swift is +able to access data files laid out in application-specific ways. + +An application-specific mapper must take the form of a Java class that +implements the Mapper + +interface. + +Usually you don't need to implement this interface directly, because +Swift provides a number of more concrete classes with some functionality +already implemented. + +The hierarchy of helper classes is: + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/Mapper.html[Mapper] + +This is the abstract interface for mappers in Swift. You must +implement methods to provide access to mapper properties, to map from a +SwiftScript dataset path (such as foo[1].bar) to a file name, to check +whether a file exists. None of the default Swift mappers implement this +interface directly - instead they use one of the following helper classes. + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/AbstractMapper.html[Abstract Mapper] + +This provides helper methods to manage mapper properties and to handle +existance checking. Examples of mappers which use this class are: +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.array_mapper[Array Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.csv_mapper[CSV Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.fixed_array_mapper[Fixed Array Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.regexp_mapper[Regexp Mapper], +and http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.single_file_mapper[Single File Mapper]. + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/file/AbstractFileMapper.html[AbstractFileMapper] +This provides a helper class for mappers which select files based on +selecting files from a directory listing. It is necessary to write some +helper methods that are different from the above mapper methods. +Examples of mappers which use this class are: +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.simple_mapper[simple_mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.filesys_mapper[filesys_mapper], +and the (undocumented) StructuredRegularExpressionMapper. + +In general, to write a mapper, choose either the AbstractMapper or the +AbstractFileMapper and extend those. If your mapper will generally +select the files it returns based on a directory listing and will +convert paths to filenames using some regular conversion (for example, +in the way that simple_mapper maps files in a directory that match a +particular pattern), then you should probably use the +AbstractFileMapper. If your mapper will produce a list of files in some +other way (for example, in the way that csv_mapper maps based on +filenames given in a CSV file rather than looking at which files are in +a directory), then you should probably use the AbstractMapper. + + +Writing a very basic mapper +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In this section, we will write a very basic (almost useless) mapper that +will map a SwiftScript dataset into a hardcoded file called +myfile.txt, like this: + + + Swift variable Filename + + var <-----------------------------> myfile.txt + +We should be able to use the mapper we write in a SwiftScript program +like this: + +[java] +source~~~~ +type file; +file f ; +source~~~~ + +First we must choose a base class - AbstractMapper or +AbstractFileMapper. We aren't going to use a directory listing to decide +on our mapping - we are getting the mapping from some other source (in +fact, it will be hard coded). So we will use AbstractMapper. + +So now onto the source code. We must define a subclass of AbstractMapper +and implement several mapper methods: isStatic, existing, and map. These +methods are documented in the javadoc for the Mapper interface. + +Here is the code implementing this mapper. Put this in your source +vdsk directory, make a directory src/tutorial/|and put this file in +src/tutorial/MyFirstMapper.java. + +[java] +source~~~~ +package tutorial; + +import java.util.Arrays; +import java.util.Collection; +import java.util.Collections; + +import org.griphyn.vdl.mapping.AbsFile; +import org.griphyn.vdl.mapping.AbstractMapper; +import org.griphyn.vdl.mapping.Path; +import org.griphyn.vdl.mapping.PhysicalFormat; + +public class MyFirstMapper extends AbstractMapper { + + AbsFile myfile = new AbsFile("myfile.txt"); + + public boolean isStatic() { + return false; + } + + public Collection existing() { + if (myfile.exists()) + return Arrays.asList(new Path[] {Path.EMPTY_PATH}); + else + return Collections.EMPTY_LIST; + } + + public PhysicalFormat map(Path p) { + if(p.equals(Path.EMPTY_PATH)) + return myfile; + else + return null; + } +} +source~~~~ + +Now we need to inform the Swift engine about the existence of this +mapper. We do that by editing the MapperFactory class definition, in +src/org/griphyn/vdl/mapping/MapperFactory.java and adding a +registerMapper call alongside the existing registerMapper calls, like this: + +[java] +source~~~~ +registerMapper("my_first_mapper", tutorial.MyFirstMapper.class); +source~~~~ + +The first parameter is the name of the mapper that will be used in +SwiftScript program. The second parameter is the new Mapper class that +we just wrote. + +Now rebuild Swift using the "ant redist" target. + +This new Swift build will be aware of your new mapper. We can test it +out with a hello world program: + +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting() { + app { + echo "hello" stdout=@filename(t); + } +} + +messagefile outfile ; + +outfile = greeting(); +source~~~~ + +Run this program, and hopefully you will find the "hello" string has +been output into the hard coded output file myfile.txt: + +[java] +source~~~~ +$ cat myfile.txt +hello +source~~~~ + +So that's a first very simple mapper implemented. Compare the source +code to the single_file_mapper in +http://www.ci.uchicago.edu/trac/swift/browser/trunk/src/org/griphyn/vdl/mapping/file/SingleFileMapper.java[SingleFileMapper.java]. +There is not much more code to the single_file_mapper - mostly code to +deal with the file parameter. + + +Starting and restarting +~~~~~~~~~~~~~~~~~~~~~~~ + +Now we're going to try out the restart capabilities of Swift. We will +make a workflow that will deliberately fail, and then we will fix the +problem so that Swift can continue with the workflow. + +First we have the program in working form, restart.swift. + +[java] +source~~~~ +include::../../examples/restart.swift[] +source~~~~ + +We must define some transformation catalog entries: + +[java] +source~~~~ +localhost touch /usr/bin/touch INSTALLED INTEL32::LINUX null +localhost broken /bin/true INSTALLED INTEL32::LINUX null +source~~~~ + +Now we can run the program: + +[java] +source~~~~ +$ swift restart.swift +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1119-3kgzzi15 +Progress: +Final status: Finished successfully:4 +source~~~~ + +Four jobs run - touch, echo, broken and a final echo. (note that broken +isn't actually broken yet). + +Now we will break the broken job and see what happens. Replace the +definition in tc.data for broken with this: + +[java] +source~~~~ +localhost broken /bin/false INSTALLED INTEL32::LINUX null +source~~~~ + +Now when we run the workflow, the broken task fails: + +[java] +source~~~~ +$ swift restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1121-tssdcljg +Progress: +Progress: Stage in:1 Finished successfully:2 +Execution failed: + Exception in broken: +Arguments: [process] +Host: localhost +Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj +stderr.txt: +stdout.txt: +source~~~~ + +From the output we can see that touch and the first echo completed, but +then broken failed and so swift did not attempt to execute the final echo. + +There will be a restart log with the same name as the RunID: + +[java] +source~~~~ +$ ls *20100526-1121-tssdcljg*rlog +restart-20100526-1121-tssdcljg.0.rlog +source~~~~ + +This restart log contains enough information for swift to know which +parts of the workflow were executed successfully. + +We can try to rerun it immediately, like this: + +[java] +source~~~~ +$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1125-7yx0zi6d +Progress: +Execution failed: + Exception in broken: +Arguments: [process] +Host: localhost +Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj +stderr.txt: +stdout.txt: + +---- + +Caused by: + Exit code 1 +source~~~~ + +Swift tried to resume the workflow by executing "broken" again. It did +not try to run the touch or first echo jobs, because the restart log +says that they do not need to be executed again. + +Broken failed again, leaving the original restart log in place. + +Now we will fix the problem with "broken" by restoring the original +tc.data line that works. + +Remove the existing "broken" line and replace it with the successful +tc.data entry above: + +[java] +source~~~~ +localhost broken /bin/true INSTALLED INTEL32::LINUX null +source~~~~ + +Now run again: + +[java] +source~~~~ +$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1128-a2gfuxhg +Progress: +Final status: Initializing:2 Finished successfully:2 +source~~~~ + +Swift tries to run "broken" again. This time it works, and so Swift +continues on to execute the final piece of the workflow as if nothing +had ever gone wrong. + + +bits +---- + +Named and optional parameters +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +anchor:named_parameters +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified: + +[java] +source~~~~ +(messagefile t) greeting (string s="hello") { + app { + echo s stdout=@filename(t); + } +} +source~~~~ + +When we invoke the procedure, we can specify values for the parameters +by name. The following code can be found in q21.swift. + +[java] +source~~~~ +french = greeting(s="bonjour"); +source~~~~ + +or we can let the default value apply: + +[java] +source~~~~ +english = greeting(); +source~~~~ Added: branches/release-0.92/docs/userguide/swift-site-model.png =================================================================== (Binary files differ) Property changes on: branches/release-0.92/docs/userguide/swift-site-model.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: branches/release-0.92/docs/userguide/type-hierarchy.png =================================================================== (Binary files differ) Property changes on: branches/release-0.92/docs/userguide/type-hierarchy.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: branches/release-0.92/docs/userguide/userguide.html =================================================================== --- branches/release-0.92/docs/userguide/userguide.html (rev 0) +++ branches/release-0.92/docs/userguide/userguide.html 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,4351 @@ + + + + + +Swift User Guide + + + + + +
    +
    +

    1. Overview

    +
    +

    This manual provides reference material for Swift: the SwiftScript +language and the Swift runtime system. For introductory material, +consult the Swift tutorial +http://www.ci.uchicago.edu/swift/guides/tutorial.php.

    +

    Swift is a data-oriented coarse grained scripting language that supports +dataset typing and mapping, dataset iteration, conditional branching, +and procedural composition.

    +

    Swift programs (or workflows) are written in a language called +SwiftScript.

    +

    SwiftScript programs are dataflow oriented - they are primarily +concerned with processing (possibly large) collections of data files, by +invoking programs to do that processing. Swift handles execution of such +programs on remote sites by choosing sites, handling the staging of +input and output files to and from the chosen sites and remote execution +of program code.

    +
    +
    +
    +

    2. The SwiftScript Language

    +
    +
    +

    2.1. Language basics

    +

    A Swift script describes data, application components, invocations of +applications components, and the inter-relations (data flow) between +those invocations.

    +

    Data is represented in a script by strongly-typed single-assignment +variables. The syntax superficially resembles C and Java. For example, +{ and } characters are used to enclose blocks of statements.

    +

    Types in Swift can be atomic or composite. An atomic type can be +either a primitive type or a mapped type. Swift provides a fixed set +of primitive types, such as integer and string. A mapped type +indicates that the actual data does not reside in CPU addressable memory +(as it would in conventional programming languages), but in POSIX-like +files. Composite types are further subdivided into structures and +arrays. Structures are similar in most respects to structure types in +other languages. Arrays use numeric indices, but are sparse. They can +contain elements of any type, including other array types, but all +elements in an array must be of the same type. We often refer to +instances of composites of mapped types as datasets.

    +

    +type-hierarchy.png +

    +

    Mapped type and composite type variable declarations can be annotated +with a mapping descriptor indicating the file(s) that make up that +dataset. For example, the following line declares a variable named +photo with type image. It additionally declares that the data for +this variable is stored in a single file named shane.jpeg.

    +
    +
    +
    image photo <"shane.jpeg">;
    +

    Component programs of scripts are declared in an app declaration, with +the description of the command line syntax for that program and a list +of input and output data. An app block describes a functional/dataflow +style interface to imperative components.

    +

    For example, the following example lists a procedure which makes use of +the ImageMagick http://www.imagemagick.org/ convert command to +rotate a supplied image by a specified angle:

    +
    +
    +
    app (image output) rotate(image input) {
    +  convert "-rotate" angle @input @output;
    +}
    +

    A procedure is invoked using the familiar syntax:

    +
    +
    +
    rotated = rotate(photo, 180);
    +

    While this looks like an assignment, the actual unix level execution +consists of invoking the command line specified in the app +declaration, with variables on the left of the assignment bound to the +output parameters, and variables to the right of the procedure +invocation passed as inputs.

    +

    The examples above have used the type image without any definition of +that type. We can declare it as a marker type which has no structure +exposed to SwiftScript:

    +
    +
    +
    type image;
    +

    This does not indicate that the data is unstructured; but it indicates +that the structure of the data is not exposed to SwiftScript. Instead, +SwiftScript will treat variables of this type as individual opaque files.

    +

    With mechanisms to declare types, map variables to data files, and +declare and invoke procedures, we can build a complete (albeit simple) +script:

    +
    +
    +
    type image;
    +image photo <"shane.jpeg">;
    +image rotated <"rotated.jpeg">;
    +
    +app (image output) rotate(image input, int angle) {
    +   convert "-rotate" angle @input @output;
    +}
    +
    +rotated = rotate(photo, 180);
    +

    This script can be invoked from the command line:

    +
    +
    +
      $ ls *.jpeg
    +  shane.jpeg
    +  $ swift example.swift
    +  ...
    +  $ ls *.jpeg
    +  shane.jpeg rotated.jpeg
    +

    This executes a single convert command, hiding from the user features +such as remote multisite execution and fault tolerance that will be +discussed in a later section.

    +
    Figure 1. shane.jpeg

    +userguide-shane.jpeg +

    +
    Figure 2. rotated.jpeg

    +userguide-rotated.jpeg +

    +
    +
    +

    2.2. Arrays and Parallel Execution

    +

    Arrays of values can be declared using the [] suffix. An array be +mapped to a collection of files, one element per file, by using a +different form of mapping expression. For example, the filesys_mapper +maps all files matching a particular unix glob pattern into an array:

    +
    +
    +
    file frames[] <filesys_mapper; pattern="*.jpeg">;
    +

    The foreach construct can be used to apply the same block of code to +each element of an array:

    +
    +
    +
    foreach f,ix in frames {
    +  output[ix] = rotate(frames, 180);
    +}
    +

    Sequential iteration can be expressed using the iterate construct:

    +
    +
    +
    step[0] = initialCondition();
    +iterate ix {
    +  step[ix] = simulate(step[ix-1]);
    +}
    +

    This fragment will initialise the 0-th element of the step array to +some initial condition, and then repeatedly run the simulate +procedure, using each execution’s outputs as input to the next step.

    +
    +
    +

    2.3. Ordering of execution

    +

    Non-array variables are single-assignment, which means that they must +be assigned to exactly one value during execution. A procedure or +expression will be executed when all of its input parameters have been +assigned values. As a result of such execution, more variables may +become assigned, possibly allowing further parts of the script to execute.

    +

    In this way, scripts are implicitly parallel. Aside from serialisation +implied by these dataflow dependencies, execution of component programs +can proceed in parallel.

    +

    In this fragment, execution of procedures p and q can happen in +parallel:

    +
    +
    +
    y=p(x);
    +z=q(x);
    +

    while in this fragment, execution is serialised by the variable y, +with procedure p executing before q.

    +
    +
    +
    y=p(x);
    +z=q(y);
    +

    Arrays in SwiftScript are more monotonic - a generalisation of being +assignment. Knowledge about the content of an array increases during +execution, but cannot otherwise change. Each element of the array is +itself single assignment or monotonic (depending on its type). During a +run all values for an array are eventually known, and that array is +regarded as closed.

    +

    Statements which deal with the array as a whole will often wait for the +array to be closed before executing (thus, a closed array is the +equivalent of a non-array type being assigned). However, a foreach +statement will apply its body to elements of an array as they become +known. It will not wait until the array is closed.

    +

    Consider this script:

    +
    +
    +
    file a[];
    +file b[];
    +foreach v,i in a {
    +  b[i] = p(v);
    +}
    +a[0] = r();
    +a[1] = s();
    +

    Initially, the foreach statement will have nothing to execute, as the +array a has not been assigned any values. The procedures r and s +will execute. As soon as either of them is finished, the corresponding +invocation of procedure p will occur. After both r and s have +completed, the array a will be closed since no other statements in the +script make an assignment to a.

    +
    +
    +

    2.4. Compound procedures

    +

    As with many other programming languages, procedures consisting of +SwiftScript code can be defined. These differ from the previously +mentioned procedures declared with the app keyword, as they invoke +other SwiftScript procedures rather than a component program.

    +
    +
    +
    (file output) process (file input) {
    +  file intermediate;
    +  intermediate = first(input);
    +  output = second(intermediate);
    +}
    +
    +file x <"x.txt">;
    +file y <"y.txt">;
    +y = process(x);
    +

    This will invoke two procedures, with an intermediate data file named +anonymously connecting the first and second procedures.

    +

    Ordering of execution is generally determined by execution of app +procedures, not by any containing compound procedures. In this code block:

    +
    +
    +
    (file a, file b) A() {
    +  a = A1();
    +  b = A2();
    +}
    +file x, y, s, t;
    +(x,y) = A();
    +s = S(x);
    +t = S(y);
    +

    then a valid execution order is: A1 S(x) A2 S(y). The compound +procedure A does not have to have fully completed for its return +values to be used by subsequent statements.

    +
    +
    +

    2.5. More about types

    +

    Each variable and procedure parameter in SwiftScript is strongly typed. +Types are used to structure data, to aid in debugging and checking +program correctness and to influence how Swift interacts with data.

    +

    The image type declared in previous examples is a marker type. +Marker types indicate that data for a variable is stored in a single +file with no further structure exposed at the SwiftScript level.

    +

    Arrays have been mentioned above, in the arrays section. A code block +may be applied to each element of an array using foreach; or +individual elements may be references using [] notation.

    +

    There are a number of primitive types:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    type contains

    int

    integers

    string

    strings of text

    float

    floating point numbers, that behave the same as Java doubles

    boolean

    true/false

    +
    +

    Complex types may be defined using the type keyword:

    +
    +
    +
    type headerfile;
    +type voxelfile;
    +type volume {
    +  headerfile h;
    +  voxelfile v;
    +}
    +

    Members of a complex type can be accessed using the . operator:

    +
    +
    +
    volume brain;
    +o = p(brain.h);
    +

    Sometimes data may be stored in a form that does not fit with Swift’s +file-and-site model; for example, data might be stored in an RDBMS on +some database server. In that case, a variable can be declared to have +external type. This indicates that Swift should use the variable to +determine execution dependency, but should not attempt other data +management; for example, it will not perform any form of data stage-in +or stage-out it will not manage local data caches on sites; and it will +not enforce component program atomicity on data output. This can add +substantial responsibility to component programs, in exchange for +allowing arbitrary data storage and access methods to be plugged in to +scripts.

    +
    +
    +
    type file;
    +
    +app (external o) populateDatabase() {
    +  populationProgram;
    +}
    +
    +app (file o) analyseDatabase(external i) {
    +  analysisProgram @o;
    +}
    +
    +external database;
    +file result <"results.txt">;
    +
    +database = populateDatabase();
    +result = analyseDatabase(database);
    +

    Some external database is represented by the database variable. The +populateDatabase procedure populates the database with some data, and +the analyseDatabase procedure performs some subsequent analysis on +that database. The declaration of database contains no mapping; and +the procedures which use database do not reference them in any way; +the description of database is entirely outside of the script. The +single assignment and execution ordering rules will still apply though; +populateDatabase will always be run before analyseDatabase.

    +
    +
    +

    2.6. Data model

    +

    Data processed by Swift is strongly typed. It may be take the form of +values in memory or as out-of-core files on disk. Language constructs +called mappers specify how each piece of data is stored.

    +
    +
    +

    2.7. Mappers

    +

    When a DSHandle represents a data file (or container of datafiles), it +is associated with a mapper. The mapper is used to identify which files +belong to that DSHandle.

    +

    A dataset’s physical representation is declared by a mapping descriptor, +which defines how each element in the dataset’s logical schema is stored +in, and fetched from, physical structures such as directories, files, +and remote servers.

    +

    Mappers are parameterized to take into account properties such as +varying dataset location. In order to access a dataset, we need to know +three things: its type, its mapping, and the value(s) of any +parameter(s) associated with the mapping descriptor. For example, if we +want to describe a dataset, of type imagefile, and whose physical +representation is a file called "file1.bin" located at +"/home/yongzh/data/", then the dataset might be declared as follows:

    +
    +
    +
    imagefile f1<single_file_mapper;file="/home/yongzh/data/file1.bin">
    +

    The above example declares a dataset called f1, which uses a single file +mapper to map a file from a specific location.

    +

    SwiftScript has a simplified syntax for this case, since +single_file_mapper is frequently used:

    +
    +
    +
    binaryfile f1<"/home/yongzh/data/file1.bin">
    +

    Swift comes with a number of mappers that handle common mapping +patterns. These are documented in the mappers section of this +guide.

    +
    +
    +

    2.8. More technical details about SwiftScript

    +

    The syntax of SwiftScript has a superficial resemblance to C and Java. +For example, { and } characters are used to enclose blocks of statements.

    +

    A SwiftScript program consists of a number of statements. Statements may +declare types, procedures and variables, assign values to variables, and +express operations over arrays.

    +
    +

    2.8.1. Variables

    +

    Variables in SwiftScript are declared to be of a specific type. +Assignments to those variables must be data of that type. SwiftScript +variables are single-assignment - a value may be assigned to a variable +at most once. This assignment can happen at declaration time or later on +in execution. When an attempt to read from a variable that has not yet +been assigned is made, the code performing the read is suspended until +that variable has been written to. This forms the basis for Swift’s +ability to parallelise execution - all code will execute in parallel +unless there are variables shared between the code that cause sequencing.

    +
    +
    +

    2.8.2. Variable Declarations

    +

    Variable declaration statements declare new variables. They can +optionally assign a value to them or map those variables to on-disk files.

    +

    Declaration statements have the general form:

    +
    +
    +
    typename variablename (<mapping> | = initialValue ) ;
    +

    The format of the mapping expression is defined in the Mappers section. +initialValue may be either an expression or a procedure call that +returns a single value.

    +

    Variables can also be declared in a multivalued-procedure statement, +described in another section.

    +
    +
    +

    2.8.3. Assignment Statements

    +

    Assignment statements assign values to previously declared variables. +Assignments may only be made to variables that have not already been +assigned. Assignment statements have the general form:

    +
    +
    +
    variable = value;
    +

    where value can be either an expression or a procedure call that returns +a single value.

    +

    Variables can also be assigned in a multivalued-procedure statement, +described in another section.

    +
    +
    +
    +

    2.9. Procedures

    +

    There are two kinds of procedure: An atomic procedure, which describes +how an external program can be executed; and compound procedures which +consist of a sequence of SwiftScript statements.

    +

    A procedure declaration defines the name of a procedure and its input +and output parameters. SwiftScript procedures can take multiple inputs +and produce multiple outputs. Inputs are specified to the right of the +function name, and outputs are specified to the left. For example:

    +
    +
    +
    (type3 out1, type4 out2) myproc (type1 in1, type2 in2)
    +

    The above example declares a procedure called myproc, which has two +inputs in1 (of type type1) and in2 (of type type2) and two +outputs out1 (of type type3) and out2 (of type type4).

    +

    A procedure input parameter can be an optional parameter in which case +it must be declared with a default value. When calling a procedure, both +positional parameter and named parameter passings can be passed, +provided that all optional parameters are declared after the required +parameters and any optional parameter is bound using keyword parameter +passing. For example, if myproc1 is defined as:

    +
    +
    +
    (binaryfile bf) myproc1 (int i, string s="foo")
    +

    Then that procedure can be called like this, omitting the optional

    +
    +
    +
    parameter s:
    +binaryfile mybf = myproc1(1);
    +

    or like this supplying a value for the optional parameter s:

    +
    +
    +
    binaryfile mybf = myproc1 (1, s="bar");
    +
    +

    2.9.1. Atomic procedures

    +

    An atomic procedure specifies how to invoke an external executable +program, and how logical data types are mapped to command line arguments.

    +

    Atomic procedures are defined with the app keyword:

    +
    +
    +
    app (binaryfile bf) myproc (int i, string s="foo") {
    +    myapp i s @filename(bf);
    +}
    +

    which specifies that myproc invokes an executable called myapp, +passing the values of i, s and the filename of bf as command line +arguments.

    +
    +
    +

    2.9.2. Compound procedures

    +

    A compound procedure contains a set of SwiftScript statements:

    +
    +
    +
    (type2 b) foo_bar (type1 a) {
    +    type3 c;
    +    c = foo(a);    // c holds the result of foo
    +    b = bar(c);    // c is an input to bar
    +}
    +
    +
    +
    +

    2.10. Control Constructs

    +

    SwiftScript provides if, switch, foreach, and iterate +constructs, with syntax and semantics similar to comparable constructs +in other high-level languages.

    +
    +

    2.10.1. foreach

    +

    The foreach construct is used to apply a block of statements to each +element in an array. For example:

    +
    +
    +
    check_order (file a[]) {
    +    foreach f in a {
    +        compute(f);
    +    }
    +}
    +

    foreach statements have the general form:

    +
    +
    +
    foreach controlvariable (,index) in expression {
    +    statements
    +}
    +

    The block of statements is evaluated once for each element in +expression which must be an array, with controlvariable set to the +corresponding element and index (if specified) set to the integer +position in the array that is being iterated over.

    +
    +
    +

    2.10.2. if

    +

    The if statement allows one of two blocks of statements to be +executed, based on a boolean predicate. if statements generally have +the form:

    +
    +
    +
    if(predicate) {
    +    statements
    +} else {
    +    statements
    +}
    +

    where predicate is a boolean expression.

    +
    +
    +

    2.10.3. switch

    +

    switch expressions allow one of a selection of blocks to be chosen +based on the value of a numerical control expression. switch +statements take the general form:

    +
    +
    +
    switch(controlExpression) {
    +    case n1:
    +        statements2
    +    case n2:
    +        statements2
    +    [...]
    +    default:
    +        statements
    +}
    +

    The control expression is evaluated, the resulting numerical value used +to select a corresponding case, and the statements belonging to that +case block are evaluated. If no case corresponds, then the statements +belonging to the default block are evaluated.

    +

    Unlike C or Java switch statements, execution does not fall through to +subsequent case blocks, and no break statement is necessary at the +end of each block.

    +
    +
    +

    2.10.4. iterate

    +

    iterate expressions allow a block of code to be evaluated repeatedly, +with an integer parameter sweeping upwards from 0 until a termination +condition holds.

    +

    The general form is:

    +
    +
    +
    iterate var {
    +    statements;
    +} until (terminationExpression);
    +

    with the variable var starting at 0 and increasing by one in each +iteration. That variable is in scope in the statements block and when +evaluating the termination expression.

    +
    +
    +
    +

    2.11. Operators

    +

    The following infix operators are available for use in SwiftScript +expressions.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    operatorpurpose

    +

    numeric addition; string concatenation

    -

    numeric subtraction

    *

    numeric multiplication

    /

    floating point division

    %/

    integer division

    %%

    integer remainder of division

    == !=

    comparison and not-equal-to

    < > ⇐ >=

    numerical ordering

    && ||

    boolean and, or

    !

    boolean not

    +
    +
    +
    +

    2.12. Global constants

    +

    At the top level of a SwiftScript program, the global modified may be +added to a declaration so that it is visible throughout the program, +rather than only at the top level of the program. This allows global +constants (of any type) to be defined. (since Swift 0.10)

    +
    +
    +

    2.13. Imports

    +

    The import directive can be used to import definitions from another +SwiftScript file. (since Swift 0.10)

    +

    For example, a SwiftScript program might contain this:

    +
    +
    +
    import defs;
    +file f;
    +

    which would import the content of defs.swift in the current directory:

    +
    +
    +
    type file;
    +

    Imported files are read from the current working directory.

    +

    There is no requirement that a module is imported only once. If a module +is imported multiple times, for example in different files, then Swift +will only process the imports once.

    +

    Imports may contain anything that is valid in a SwiftScript program, +including code that causes remote execution.

    +
    +
    +
    +
    +

    3. Mappers

    +
    +

    Mappers provide a mechanism to specify the layout of mapped datasets on +disk. This is needed when Swift must access files to transfer them to +remote sites for execution or to pass to applications.

    +

    Swift provides a number of mappers that are useful in common cases. This +section details those standard mappers. For more complex cases, it is +possible to write application-specific mappers in Java and use them +within a SwiftScript program.

    +
    +

    3.1. The single file mapper

    +

    The single_file_mapper maps a single physical file to a dataset.

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    f

    myfile

    f[0]

    INVALID

    f.bar

    INVALID

    +
    +
    + +++ + + + + + + + + + + + +
    parametermeaning

    file

    The location of the physical file including path and file name.

    +
    +

    Example:

    +
    +
    +
    file f <single_file_mapper;file="plot_outfile_param">;
    +

    There is a simplified syntax for this mapper:

    +
    +
    +
    file f <"plot_outfile_param">;
    +
    +
    +

    3.2. The simple mapper

    +

    The simple_mapper maps a file or a list of files into an array by +prefix, suffix, and pattern. If more than one file is matched, each of +the file names will be mapped as a subelement of the dataset.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored.

    +
    +
    +
    +
    type file;
    +file f <simple_mapper;prefix="foo", suffix=".txt">;
    +

    The above maps all filenames that start with foo and have an extension +.txt into file f.

    +
    + +++ + + + + + + + + + + + +
    Swift variableFilename

    f

    foo.txt

    +
    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting(string m) {.
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile <simple_mapper;prefix="foo",suffix=".txt">;
    +
    +outfile = greeting("hi");
    +

    This will output the string hi to the file foo.txt.

    +

    The simple_mapper can be used to map arrays. It will map the array +index into the filename between the prefix and suffix.

    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting(string m) {
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile[] <simple_mapper;prefix="baz",suffix=".txt">;
    +
    +outfile[0] = greeting("hello");
    +outfile[1] = greeting("middle");
    +outfile[2] = greeting("goodbye");
    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    outfile[0]

    baz0000.txt

    outfile[1]

    baz0001.txt

    outfile[2]

    baz0002.txt

    +
    +

    simple_mapper can be used to map structures. It will map the name of +the structure member into the filename, between the prefix and the suffix.

    +
    +
    +
    type messagefile;
    +
    +type mystruct {
    +  messagefile left;
    +  messagefile right;
    +};
    +
    +(messagefile t) greeting(string m) {
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +mystruct out <simple_mapper;prefix="qux",suffix=".txt">;
    +
    +out.left = greeting("hello");
    +out.right = greeting("goodbye");
    +

    This will output the string "hello" into the file qux.left.txt and the +string "goodbye" into the file qux.right.txt.

    +
    + +++ + + + + + + + + + + + + + + + +
    Swift variableFilename

    out.left

    quxleft.txt

    out.right

    quxright.txt

    +
    +
    +
    +

    3.3. concurrent mapper

    +

    concurrent_mapper is almost the same as the simple mapper, except that +it is used to map an output file, and the filename generated will +contain an extract sequence that is unique. This mapper is the default +mapper for variables when no mapper is specified.

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt" +pattern A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored.

    +
    +

    Example:

    +
    +
    +
    file f1;
    +file f2 <concurrent_mapper;prefix="foo", suffix=".txt">;
    +

    The above example would use concurrent mapper for f1 and f2, and +generate f2 filename with prefix "foo" and extension ".txt"

    +
    +
    +

    3.4. File system mapper

    +

    filesys_mapper is similar to the simple mapper, but maps a file or a +list of files to an array. Each of the filename is mapped as an element +in the array. The order of files in the resulting array is not defined.

    +

    TODO: note on difference between location as a relative vs absolute path +wrt staging to remote location - as mihael said: It’s because you +specify that location in the mapper. Try location="." instead of +location="/sandbox/…"

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    parametermeaning

    location

    The directory where the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo.

    +
    +

    Example:

    +
    +
    +
    file texts[] <filesys_mapper;prefix="foo", suffix=".txt">;
    +

    The above example would map all filenames that start with "foo" and +have an extension ".txt" into the array texts. For example, if the +specified directory contains files: foo1.txt, footest.txt, +foo__1.txt, then the mapping might be:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    texts[0]

    footest.txt

    texts[1]

    foo1.txt

    texts[2]

    foo__1.txt

    +
    +
    +
    +

    3.5. fixed array mapper

    +

    The fixed_array_mapper maps from a string that contains a list of +filenames into a file array.

    +
    + +++ + + + + + + + + + + + +
    parameterMeaning

    files

    A string that contains a list of filenames, separated by space, +comma or colon

    +
    +

    Example:

    +
    +
    +
    file texts[] <fixed_array_mapper;files="file1.txt, fileB.txt, file3.txt">;
    +

    would cause a mapping like this:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    texts[0]

    file1.txt

    texts[1]

    fileB.txt

    texts[2]

    file3.txt

    +
    +
    +
    +

    3.6. array mapper

    +

    The array_mapper maps from an array of strings into a file

    +
    + +++ + + + + + + + + + + + +
    parametermeaning

    files

    An array of strings containing one filename per element

    +
    +

    Example:

    +
    +
    +
    string s[] = [ "a.txt", "b.txt", "c.txt" ];
    +
    +file f[] <array_mapper;files=s>;
    +

    This will establish the mapping:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    f[0]

    a.txt

    f[1]

    b.txt

    f[2]

    c.txt

    +
    +
    +
    +

    3.7. regular expression mapper

    +

    The regexp_mapper transforms one file name to another using regular +expression matching.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    parametermeaning

    source

    The source file name

    match

    Regular expression pattern to match, use

    ()

    to match whatever +regular expression is inside the parentheses, and indicate the start and +end of a group; the contents of a group can be retrieved with the

    \\number

    special sequence (two backslashes are needed because the +backslash is an escape sequence introducer)

    transform

    The pattern of the file name to transform to, use \number to +reference the group matched.

    +
    +

    Example:

    +
    +
    +
    string s = "picture.gif";
    +file f <regexp_mapper;
    +  source=s,
    +  match="(.*)gif",
    +  transform="\\1jpg">;
    +

    This example transforms a string ending gif into one ending jpg and +maps that to a file.

    +
    + +++ + + + + + + + + + + + +
    Swift variableFilename

    f

    picture.jpg

    +
    +
    +
    +

    3.8. csv mapper

    +

    The csv_mapper maps the content of a CSV (comma-separated value) file +into an array of structures. The dataset type needs to be correctly +defined to conform to the column names in the file. For instance, if the +file contains columns: name age GPA then the type needs to have member +elements like this:

    +
    +
    +
    type student {
    +  file name;
    +  file age;
    +  file GPA;
    +}
    +

    If the file does not contain a header with column info, then the column +names are assumed as column1, column2, etc.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    file

    The name of the CSV file to read mappings from.

    header

    Whether the file has a line describing header info; default is

    true

    skip

    The number of lines to skip at the beginning (after header line); +default is 0.

    hdelim

    Header field delimiter; default is the value of the

    delim

    parameter

    delim

    Content field delimiters; defaults are space, tab and comma

    +
    +

    Example:

    +
    +
    +
    student stus[] <csv_mapper;file="stu_list.txt">;
    +

    The above example would read a list of student info from file +"stu_list.txt" and map them into a student array. By default, the file +should contain a header line specifying the names of the columns. If +stu_list.txt contains the following:

    +
    +
    +
    name,age,gpa
    +101-name.txt, 101-age.txt, 101-gpa.txt
    +name55.txt, age55.txt, age55.txt
    +q, r, s
    +

    then some of the mappings produced by this example would be:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    stus[0].name101-name.txt

    stus[0].age

    101-age.txt

    stus[0].gpa

    101-gpa.txt

    stus[1].name

    name55.txt

    stus[1].age

    age55.txt

    stus[1].gpa

    gpa55.txt

    stus[2].name

    q

    stus[2].age

    r

    stus[2].gpa

    s

    +
    +
    +
    +

    3.9. external mapper

    +

    The external mapper, ext maps based on the output of a supplied Unix +executable.

    +
    + +++ + + + + + + + + + + + + + +

    parameter

    meaning

    exec

    The name of the executable (relative to the current directory, if +an absolute path is not specified)

    *

    Other parameters are passed to the executable prefixed with a - symbol

    +
    +

    The output of the executable should consist of two columns of data, +separated by a space. The first column should be the path of the mapped +variable, in SwiftScript syntax (for example [2] means the 2nd element +of an array) or the symbol $ to represent the root of the mapped +variable.

    +

    Example: With the following in mapper.sh,

    +
    +
    +
    #!/bin/bash
    +echo "[2] qux"
    +echo "[0] foo"
    +echo "[1] bar"
    +

    then a mapping statement:

    +
    +
    +
    student stus[] <ext;exec="mapper.sh">;
    +

    would map

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    stus[0]

    foo

    stus[1]

    bar

    stus[2]

    qux

    +
    +
    +
    +
    +
    +

    4. Commands

    +
    +

    The commands detailed in this section are available in the bin/ +directory of a Swift installation and can by run from the commandline if +that directory is placed on the PATH.

    +
    +

    4.1. swift

    +

    The swift command is the main command line tool for executing +SwiftScript programs.

    +
    +

    4.1.1. Command-line Syntax

    +

    The swift command is invoked as follows: swift [options] +SwiftScript-program [SwiftScript-arguments]* with options taken from the +following list, and SwiftScript-arguments made available to the +SwiftScript program through the @arg function.

    +

    Swift command-line options

    +

    -help or -h

    +
    +
    +
    Display usage information
    +
    +

    -typecheck

    +
    +
    +
    Does a typecheck of a SwiftScript program, instead of executing it.
    +
    +

    -dryrun

    +
    +
    +
    Runs the SwiftScript program without submitting any jobs (can be
    +used to get a graph)
    +
    +

    -monitor

    +
    +
    +
    Shows a graphical resource monitor
    +
    +

    -resume file

    +
    +
    +
    Resumes the execution using a log file
    +
    +

    -config file

    +
    +
    +
    Indicates the Swift configuration file to be used for this run.
    +Properties in this configuration file will override the default
    +properties. If individual command line arguments are used for
    +properties, they will override the contents of this file.
    +
    +

    -verbose | -v

    +
    +
    +
    Increases the level of output that Swift produces on the console to
    +include more detail about the execution
    +
    +

    -debug | -d

    +
    +
    +
    Increases the level of output that Swift produces on the console to
    +include lots of detail about the execution
    +
    +

    -logfile file

    +
    +
    +
    Specifies a file where log messages should go to. By default Swift
    +uses the name of the program being run and a numeric index (e.g.
    +myworkflow.1.log)
    +
    +

    -runid identifier

    +
    +
    +
    Specifies the run identifier. This must be unique for every
    +invocation and is used in several places to keep files from
    +different executions cleanly separated. By default, a datestamp and
    +random number are used to generate a run identifier. When using this
    +parameter, care should be taken to ensure that the run ID remains
    +unique with respect to all other run IDs that might be used,
    +irrespective of (at least) expected execution sites, program or user.
    +
    +

    -tui

    +
    +
    +
    Displays an interactive text mode monitor during a run. (since Swift
    +0.9)
    +
    +

    In addition, the following Swift properties can be set on the command line:

    +
      +
    • +

      +caching.algorithm +

      +
    • +
    • +

      +clustering.enabled +

      +
    • +
    • +

      +clustering.min.time +

      +
    • +
    • +

      +clustering.queue.delay +

      +
    • +
    • +

      +ip.address +

      +
    • +
    • +

      +kickstart.always.transfer +

      +
    • +
    • +

      +kickstart.enabled +

      +
    • +
    • +

      +lazy.errors +

      +
    • +
    • +

      +pgraph +

      +
    • +
    • +

      +pgraph.graph.options +

      +
    • +
    • +

      +pgraph.node.options +

      +
    • +
    • +

      +sitedir.keep +

      +
    • +
    • +

      +sites.file +

      +
    • +
    • +

      +tc.file +

      +
    • +
    • +

      +tcp.port.range +

      +
    • +
    +
    +
    +

    4.1.2. Return codes

    +

    The swift command may exit with the following return codes:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    valuemeaning

    0

    success

    1

    command line syntax error or missing project name

    2

    error during execution

    3

    error during compilation

    4

    input file does not exist

    +
    +
    +
    +

    4.1.3. Environment variables

    +

    The swift is influenced by the following environment variables:

    +

    GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment +before running Swift. These can be set to inform Swift of the +configuration of your local firewall. More information can be found in +the Globus firewall How-to http://dev.globus.org/wiki/FirewallHowTo.

    +

    COG_OPTS - set in the environment before running Swift. Options set in +this variable will be passed as parameters to the Java Virtual Machine +which will run Swift. The parameters vary between virtual machine +imlementations, but can usually be used to alter settings such as +maximum heap size. Typing java -help will sometimes give a list of +commands. The Sun Java 1.4.2 command line options are documented here +http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/java.html.

    +
    +
    +
    +

    4.2. swift-osg-ress-site-catalog

    +

    The swift-osg-ress-site-catalog command generates a site catalog based +on OSG http://www.opensciencegrid.org/'s ReSS information system +(since Swift 0.9)

    +

    Usage: swift-osg-ress-site-catalog [options]

    +

    --help

    +
    +
    +
    Show help message
    +
    +

    --vo=[name]

    +
    +
    +
    Set what VO to query ReSS for
    +
    +

    --engage-verified

    +
    +
    +
    Only retrieve sites verified by the Engagement VO site verification
    +tests This can not be used together with |--vo|, as the query will
    +only work for sites advertising support for the Engagement VO.
    +
    +
    +
    +
    This option means information will be retrieved from the Engagement
    +collector instead of the top-level ReSS collector.
    +
    +

    --out=[filename]

    +
    +
    +
    Write to [filename] instead of stdout
    +
    +

    --condor-g

    +
    +
    +
    Generates sites files which will submit jobs using a local Condor-G
    +installation rather than through direct GRAM2 submission. (since
    +Swift 0.10)
    +
    +
    +
    +

    4.3. swift-plot-log

    +

    swift-plot-log generates summaries of Swift run log files.

    +

    Usage: swift-plot-log [logfile] [targets]

    +

    When no targets are specified, swift-plog-log will generate an HTML +report for the run. When targets are specified, only those named targets +will be generated.

    +
    +
    +
    +
    +

    5. Executing app procedures

    +
    +

    This section describes how Swift executes app procedures, and +requirements on the behaviour of application programs used in app +procedures. These requirements are primarily to ensure that the Swift +can run your application in different places and with the various fault +tolerance mechanisms in place.

    +
    +

    5.1. Mapping of app semantics into unix process execution semantics

    +

    This section describes how an app procedure invocation is translated +into a (remote) unix process execution. It does not describe the +mechanisms by which Swift performs that translation; that is described +in the next section.

    +

    In this section, this example SwiftScript program is used for reference:

    +
    +
    +
    type file;
    +
    +app (file o) count(file i) {
    +  wc @i stdout=@o;
    +}
    +
    +file q <"input.txt">;
    +file r <"output.txt">;
    +

    The executable for wc will be looked up in tc.data.

    +

    This unix executable will then be executed in some application +procedure workspace. This means:

    +

    Each application procedure workspace will have an application workspace +directory. (TODO: can collapse terms application procedure workspace +and application workspace directory ?

    +

    This application workspace directory will not be shared with any other +application procedure execution attempt; all application procedure +execution attempts will run with distinct application procedure +workspaces. (for the avoidance of doubt: If a SwiftScript procedure +invocation is subject to multiple application procedure execution +attempts (due to Swift-level restarts, retries or replication) then each +of those application procedure execution attempts will be made in a +different application procedure workspace. )

    +

    The application workspace directory will be a directory on a POSIX +filesystem accessible throughout the application execution by the +application executable.

    +

    Before the application executable is executed:

    +
      +
    • +

      +The application workspace directory will exist. +

      +
    • +
    • +

      +The input files will exist inside the application workspace + directory (but not necessarily as direct children; there may be + subdirectories within the application workspace directory). +

      +
    • +
    • +

      +The input files will be those files mapped to input parameters + of the application procedure invocation. (In the example, this + means that the file input.txt will exist in the application + workspace directory) +

      +
    • +
    • +

      +For each input file dataset, it will be the case that @filename + or @filenames invoked with that dataset as a parameter will + return the path relative to the application workspace directory + for the file(s) that are associated with that dataset. (In the + example, that means that @i will evaluate to the path input.txt) +

      +
    • +
    • +

      +For each file-bound parameter of the Swift procedure invocation, + the associated files (determined by data type?) will always exist. +

      +
    • +
    • +

      +The input files must be treated as read only files. This may or + may not be enforced by unix file system permissions. They may or + may not be copies of the source file (conversely, they may be + links to the actual source file). +

      +
    • +
    +

    During/after the application executable execution, the following must +be true:

    +
      +
    • +

      +If the application executable execution was successful (in the + opinion of the application executable), then the application + executable should exit with unix return code 0; if the + application executable execution was unsuccessful (in the opinion + of the application executable), then the application executable + should exit with unix return code not equal to 0. +

      +
    • +
    • +

      +Each file mapped from an output parameter of the SwiftScript + procedure call must exist. Files will be mapped in the same way as + for input files. +

      +
      +
      +
      (? Is it defined that output subdirectories will be precreated
      +before execution or should app executables expect to make them?
      +That's probably determined by the present behaviour of wrapper.sh)
      +
      +
    • +
    • +

      +Output produced by running the application executable on some + inputs should be the same no matter how many times, when or where + that application executable is run. The same can vary depending + on application (for example, in an application it might be + acceptable for a PNG→JPEG conversion to produce different, + similar looking, output jpegs depending on the environment) +

      +
    • +
    +

    Things to not assume:

    +
      +
    • +

      +anything about the path of the application workspace directory +

      +
    • +
    • +

      +that either the application workspace directory will be deleted or + will continue to exist or will remain unmodified after execution + has finished +

      +
    • +
    • +

      +that files can be passed(?def) between application procedure + invocations through any mechanism except through files known to + Swift through the mapping mechanism (there is some exception here + for external datasets - there are a separate set of assertions + that hold for external datasets) +

      +
    • +
    • +

      +that application executables will run on any particular site of + those available, or than any combination of applications will run + on the same or different sites. +

      +
    • +
    +
    +
    +

    5.2. How Swift implements the site execution model

    +

    This section describes the implementation of the semantics described in +the previous section.

    +

    Swift executes application procedures on one or more sites.

    +

    Each site consists of:

    +
      +
    • +

      +worker nodes. There is some execution mechanism through which + the Swift client side executable can execute its wrapper script + on those worker nodes. This is commonly GRAM or Falkon or coasters. +

      +
    • +
    • +

      +a site-shared file system. This site shared filesystem is + accessible through some file transfer mechanism from the Swift + client side executable. This is commonly GridFTP or coasters. This + site shared filesystem is also accessible through the posix file + system on all worker nodes, mounted at the same location as seen + through the file transfer mechanism. Swift is configured with the + location of some site working directory on that site-shared file + system. +

      +
    • +
    +

    There is no assumption that the site shared file system for one site is +accessible from another site.

    +

    For each workflow run, on each site that is used by that run, a run +directory is created in the site working directory, by the Swift client +side.

    +

    In that run directory are placed several subdirectories:

    +
      +
    • +

      +shared/ - site shared files cache +

      +
    • +
    • +

      +kickstart/ - when kickstart is used, kickstart record files for + each job that has generated a kickstart record. +

      +
    • +
    • +

      +info/ - wrapper script log files +

      +
    • +
    • +

      +status/ - job status files +

      +
    • +
    • +

      +jobs/ - application workspace directories (optionally placed + here - see below) +

      +
    • +
    +

    Application execution looks like this:

    +

    For each application procedure call:

    +

    The Swift client side selects a site; copies the input files for that +procedure call to the site shared file cache if they are not already in +the cache, using the file transfer mechanism; and then invokes the +wrapper script on that site using the execution mechanism.

    +

    The wrapper script creates the application workspace directory; places +the input files for that job into the application workspace directory +using either cp or ln -s (depending on a configuration option); +executes the application unix executable; copies output files from the +application workspace directory to the site shared directory using cp; +creates a status file under the status/ directory; and exits, +returning control to the Swift client side. Logs created during the +execution of the wrapper script are stored under the info/ directory.

    +

    The Swift client side then checks for the presence of and deletes a +status file indicating success; and copies files from the site shared +directory to the appropriate client side location.

    +

    The job directory is created (in the default mode) under the jobs/ +directory. However, it can be created under an arbitrary other path, +which allows it to be created on a different file system (such as a +worker node local file system in the case that the worker node has a +local file system).

    +

    +swift-site-model.png +

    +
    +
    +
    +
    +

    6. Technical overview of the Swift architecture

    +
    +

    This section attempts to provide a technical overview of the Swift +architecture.

    +
    +

    6.1. Execution layer

    +

    The execution layer causes an application program (in the form of a unix +executable) to be executed either locally or remotely.

    +

    The two main choices are local unix execution and execution through +GRAM. Other options are available, and user provided code can also be +plugged in.

    +

    The kickstart utility can be used to capture environmental +information at execution time to aid in debugging and provenance capture.

    +
    +
    +

    6.2. SwiftScript language compilation layer

    +

    Step i: text to XML intermediate form parser/processor. parser written +in ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the +intermediate language is in resources/XDTM.xsd.

    +

    Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads +the XML intermediate form. compiles to karajan workflow language - for +example, expressions are converted from SwiftScript syntax into Karajan +syntax, and function invocations become karajan function invocations +with various modifications to parameters to accomodate return parameters +and dataset handling.

    +
    +
    +

    6.3. Swift/karajan library layer

    +

    Some Swift functionality is provided in the form of Karajan libraries +that are used at runtime by the Karajan workflows that the Swift +compiler generates.

    +
    +
    +
    +
    +

    7. Ways in which Swift can be extended

    +
    +

    Swift is extensible in a number of ways. It is possible to add mappers +to accomodate different filesystem arrangements, site selectors to +change how Swift decides where to run each job, and job submission +interfaces to submit jobs through different mechanisms.

    +

    A number of mappers are provided as part of the Swift release and +documented in the mappers section. New mappers can be +implemented in Java by implementing the org.griphyn.vdl.mapping.Mapper +interface. The Swift tutorial +http://www.ci.uchicago.edu/swift/guides/tutorial.php contains a simple +example of this.

    +

    Swift provides a default site selector, the Adaptive Scheduler. New site +selectors can be plugged in by implementing the +org.globus.cog.karajan.scheduler.Scheduler interface and modifying +libexec/scheduler.xml and etc/karajan.properties to refer to the new +scheduler.

    +

    Execution providers and filesystem providers, which allow to Swift to +execute jobs and to stage files in and out through mechanisms such as +GRAM and GridFTP can be implemented as Java CoG kit providers.

    +
    +
    +
    +

    8. Function reference

    +
    +

    This section details functions that are available for use in the +SwiftScript language.

    +
    +

    8.1. @arg

    +

    Takes a command line parameter name as a string parameter and an +optional default value and returns the value of that string parameter +from the command line. If no default value is specified and the command +line parameter is missing, an error is generated. If a default value is +specified and the command line parameter is missing, @arg will return +the default value.

    +

    Command line parameters recognized by @arg begin with exactly one +hyphen and need to be positioned after the script name.

    +

    For example:

    +
    +
    +
    trace(@arg("myparam"));
    +trace(@arg("optionalparam", "defaultvalue"));
    +
    +
    +
    $ swift arg.swift -myparam=hello
    +Swift v0.3-dev r1674 (modified locally)
    +
    +RunID: 20080220-1548-ylc4pmda
    +SwiftScript trace: defaultvalue
    +SwiftScript trace: hello
    +
    +
    +

    8.2. @extractint

    +

    @extractint(file) will read the specified file, parse an integer from +the file contents and return that integer.

    +
    +
    +

    8.3. @filename

    +

    @filename(v) will return a string containing the filename(s) for the +file(s) mapped to the variable v. When more than one filename is +returned, the filenames will be space separated inside a single string +return value.

    +
    +
    +

    8.4. @filenames

    +

    @filenames(v) will return multiple values (!) containing the +filename(s) for the file(s) mapped to the variable v. (compare to + at filename)

    +
    +
    +

    8.5. @regexp

    +

    @regexp(input,pattern,replacement) will apply regular expression +substitution using the Java java.util.regexp API +http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html. +For example:

    +
    +
    +
    string v =  @regexp("abcdefghi", "c(def)g","monkey");
    +

    will assign the value "abmonkeyhi" to the variable v.

    +
    +
    +

    8.6. @strcat

    +

    @strcat(a,b,c,d,…) will return a string containing all of the +strings passed as parameters joined into a single string. There may be +any number of parameters.

    +

    The + operator concatenates two strings: @strcat(a,b) is the same as +a + b

    +
    +
    +

    8.7. @strcut

    +

    @strcut(input,pattern) will match the regular expression in the +pattern parameter against the supplied input string and return the +section that matches the first matching parenthesised group.

    +

    For example:

    +
    +
    +
    string t = "my name is John and i like puppies.";
    +string name = @strcut(t, "my name is ([^ ]*) ");
    +string out = @strcat("Your name is ",name);
    +trace(out);
    +

    will output the message: Your name is John.

    +
    +
    +

    8.8. @strsplit

    +

    @strsplit(input,pattern) will split the input string based on +separators that match the given pattern and return a string array. +(since Swift 0.9)

    +

    Example:

    +
    +
    +
    string t = "my name is John and i like puppies.";
    +string words[] = @strsplit(t, "\\s");
    +foreach word in words {
    +    trace(word);
    +}
    +

    will output one word of the sentence on each line (though not +necessarily in order, due to the fact that foreach iterations execute in +parallel).

    +
    +
    +

    8.9. @toint

    +

    @toint(input) will parse its input string into an integer. This can be +used with @arg to pass input parameters to a SwiftScript program as +integers.

    +
    +
    +
    +
    +

    9. Built-in procedure reference

    +
    +

    This section details built-in procedures that are available for use in +the SwiftScript language.

    +
    +

    9.1. readData

    +

    readData will read data from a specified file.

    +

    The format of the input file is controlled by the type of the return value.

    +

    For scalar return types, such as int, the specified file should contain +a single value of that type.

    +

    For arrays of scalars, the specified file should contain one value per +line.

    +

    For structs of scalars, the file should contain two rows. The first row +should be structure member names separated by whitespace. The second row +should be the corresponding values for each structure member, separated +by whitespace, in the same order as the header row.

    +

    For arrays of structs, the file should contain a heading row listing +structure member names separated by whitespace. There should be one row +for each element of the array, with structure member elements listed in +the same order as the header row and separated by whitespace. (since +Swift 0.4)

    +
    +
    +

    9.2. readdata2

    +

    readdata2 will read data from a specified file, like readdata, but +using a different file format more closely related to that used by the +ext mapper.

    +

    Input files should list, one per line, a path into a Swift structure, +and the value for that position in the structure:

    +
    +
    +
    rows[0].columns[0] = 0
    +rows[0].columns[1] = 2
    +rows[0].columns[2] = 4
    +rows[1].columns[0] = 1
    +rows[1].columns[1] = 3
    +rows[1].columns[2] = 5
    +

    which can be read into a structure defined like this:

    +
    +
    +
    type vector {
    +        int columns[];
    +}
    +
    +type matrix {
    +        vector rows[];
    +}
    +
    +matrix m;
    +
    +m = readData2("readData2.in");
    +

    (since Swift 0.7)

    +
    +
    +

    9.3. trace

    +

    trace will log its parameters. By default these will appear on both +stdout and in the run log file. Some formatting occurs to produce the +log message. The particular output format should not be relied upon. +(since Swift 0.4)

    +
    +
    +

    9.4. writeData

    +

    writeData will write out data structures in the format described for +readData

    +
    +
    +
    +
    +

    10. Swift configuration properties

    +
    +

    Various aspects of the behavior of the Swift Engine can be configured +through properties. The Swift Engine recognizes a global, per +installation properties file which can found in etc/swift.properties +in the Swift installation directory and a user properties file which can +be created by each user in ~/.swift/swift.properties. The Swift Engine +will first load the global properties file. It will then try to load the +user properties file. If a user properties file is found, individual +properties explicitly set in that file will override the respective +properties in the global properties file. Furthermore, some of the +properties can be overridden directly using command line arguments to +the swift command.

    +

    Swift properties are specified in the following format:

    +

    <name>=<value>

    +

    The value can contain variables which will be expanded when the +properties file is read. Expansion is performed when the name of the +variable is used inside the standard shell dereference construct: +configuration file:

    +

    Swift Configuration Variables

    +

    swift.home

    +
    +
    +
    Points to the Swift installation directory ($SWIFT_HOME). In
    +general, this should not be set as Swift can find its own
    +installation directory, and incorrectly setting it may impair the
    +correct functionality of Swift.
    +
    +

    user.name

    +
    +
    +
    The name of the current logged in user.
    +
    +

    user.home

    +
    +
    +
    The user's home directory.
    +
    +

    The following is a list of valid Swift properties:

    +

    Swift Properties

    +

    caching.algorithm

    +
    +
    +
    Valid values: LRU
    +
    +
    +
    +
    Default value: LRU
    +
    +
    +
    +
    Swift caches files that are staged in on remote resources, and files
    +that are produced remotely by applications, such that they can be
    +re-used if needed without being transfered again. However, the
    +amount of remote file system space to be used for caching can be
    +limited using the swift:storagesize profile entry in the sites.xml file. Example:
    +
    +
    +
    +
    <pool handle="example" sysinfo="INTEL32::LINUX">
    +<gridftp url="gsiftp://example.org" storage="/scratch/swift" major="2" minor="4" patch="3"/>
    +<jobmanager universe="vanilla" url="example.org/jobmanager-pbs" major="2" minor="4" patch="3"/>
    +<workdirectory>/scratch/swift</workdirectory>
    +<profile namespace="SWIFT" key="storagesize">20000000</profile>
    +</pool>
    +
    +
    +
    The decision of which files to keep in the cache and which files to
    +remove is made considering the value of the caching.algorithm
    +property. Currently, the only available value for this property is
    +LRU, which would cause the least recently used files to be deleted
    +first.
    +
    +

    clustering.enabled

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Enables clustering.
    +
    +

    clustering.min.time

    +
    +
    +
    Valid values: <int>
    +
    +
    +
    +
    Default value: 60
    +
    +
    +
    +
    Indicates the threshold wall time for clustering, in seconds. Jobs
    +that have a wall time smaller than the value of this property will
    +be considered for clustering.
    +
    +

    clustering.queue.delay

    +
    +
    +
    Valid values: <int>
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    This property indicates the interval, in seconds, at which the
    +clustering queue is processed.
    +
    +

    execution.retries

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 2
    +
    +
    +
    +
    The number of time a job will be retried if it fails (giving a
    +maximum of 1 + execution.retries attempts at execution)
    +
    +

    foreach.max.threads

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 1024
    +
    +
    +
    +
    Limits the number of concurrent iterations that each foreach
    +statement can have at one time. This conserves memory for swift
    +programs that have large numbers of iterations (which would
    +otherwise all be executed in parallel). (since Swift 0.9)
    +
    +

    ip.address

    +
    +
    +
    Valid values: <ipaddress>
    +
    +
    +
    +
    Default value: N/A
    +
    +
    +
    +
    The Globus GRAM service uses a callback mechanism to send
    +notifications about the status of submitted jobs. The callback
    +mechanism requires that the Swift client be reachable from the hosts
    +the GRAM services are running on. Normally, Swift can detect the
    +correct IP address of the client machine. However, in certain cases
    +(such as the client machine having more than one network interface)
    +the automatic detection mechanism is not reliable. In such cases,
    +the IP address of the Swift client machine can be specified using
    +this property. The value of this property must be a numeric address
    +without quotes.
    +
    +
    +
    +
    This option is deprecated and the hostname property should be used
    +instead.
    +
    +

    kickstart.always.transfer

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls when output from Kickstart is transfered back
    +to the submit site, if Kickstart is enabled. When set to false,
    +Kickstart output is only transfered for jobs that fail. If set to
    +true, Kickstart output is transfered after every job is completed
    +or failed.
    +
    +

    kickstart.enabled

    +
    +
    +
    Valid values: true, false, maybe
    +
    +
    +
    +
    Default value: maybe
    +
    +
    +
    +
    This option allows controlling of when Swift uses Kickstart.
    +A value of false disables the use of Kickstart,
    +while a value of true enables the use of Kickstart, in which case
    +sites specified in the sites.xml file must have valid
    +gridlaunch attributes. The maybe value will enable the use of
    +Kickstart only on sites that have the gridlaunch attribute
    +specified.
    +
    +

    lazy.errors

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Swift can report application errors in two modes, depending on the
    +value of this property. If set to false, Swift will report the
    +first error encountered and immediately stop execution. If set to
    +true, Swift will attempt to run as much as possible from a
    +SwiftScript program before stopping execution and reporting all
    +errors encountered.
    +
    +
    +
    +
    When developing SwiftScript programs, using the default value of
    +false can make the program easier to debug. However in production
    +runs, using true will allow more of a SwiftScript program to be
    +run before Swift aborts execution.
    +
    +

    pgraph

    +
    +
    +
    Valid values: true, false, <file>
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Swift can generate a Graphviz <http://www.graphviz.org/> file
    +representing the structure of the SwiftScript program it has run. If
    +this property is set to true, Swift will save the provenance graph
    +in a file named by concatenating the program name and the instance
    +ID (e.g. helloworld-ht0adgi315l61.dot).
    +
    +
    +
    +
    If set to false, no provenance graph will be generated. If a file
    +name is used, then the provenance graph will be saved in the
    +specified file.
    +
    +
    +
    +
    The generated dot file can be rendered into a graphical form using
    +Graphviz <http://www.graphviz.org/>, for example with a command-line
    +such as:
    +
    +
    +
    +
    $ swift -pgraph graph1.dot q1.swift
    +$ dot -ograph.png -Tpng graph1.dot
    +

    pgraph.graph.options

    +
    +
    +
    Valid values: <string>
    +
    +
    +
    +
    Default value: splines="compound", rankdir="TB"
    +
    +
    +
    +
    This property specifies a Graphviz <http://www.graphviz.org>
    +specific set of parameters for the graph.
    +
    +

    pgraph.node.options

    +
    +
    +
    Valid values: <string>
    +
    +
    +
    +
    Default value: color="seagreen", style="filled"
    +
    +
    +
    +
    Used to specify a set of Graphviz <http://www.graphviz.org> specific
    +properties for the nodes in the graph.
    +
    +

    provenance.log

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls whether the log file will contain provenance
    +information enabling this will increase the size of log files,
    +sometimes significantly.
    +
    +

    replication.enabled

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Enables/disables replication. Replication is used to deal with jobs
    +sitting in batch queues for abnormally large amounts of time. If
    +replication is enabled and certain conditions are met, Swift creates
    +and submits replicas of jobs, and allows multiple instances of a job
    +to compete.
    +
    +

    replication.limit

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 3
    +
    +
    +
    +
    The maximum number of replicas that Swift should attempt.
    +
    +

    sitedir.keep

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Indicates whether the working directory on the remote site should be
    +left intact even when a run completes successfully. This can be used
    +to inspect the site working directory for debugging purposes.
    +
    +

    sites.file

    +
    +
    +
    Valid values: <file>
    +
    +
    +
    +
    Default value: ${swift.home}/etc/sites.xml
    +
    +
    +
    +
    Points to the location of the site catalog, which contains a list of
    +all sites that Swift should use.
    +
    +

    status.mode

    +
    +
    +
    Valid values: files, provider
    +
    +
    +
    +
    Default value: files
    +
    +
    +
    +
    Controls how Swift will communicate the result code of running user
    +programs from workers to the submit side. In files mode, a file
    +indicating success or failure will be created on the site shared
    +filesystem. In provider mode, the execution provider job status
    +will be used.
    +
    +
    +
    +
    provider mode requires the underlying job execution system to
    +correctly return exit codes. In at least the cases of GRAM2, and
    +clusters used with any provider, exit codes are not returned, and so
    +files mode must be used in those cases. Otherwise, provider mode
    +can be used to reduce the amount of filesystem access. (since Swift
    +0.8)
    +
    +

    tc.file

    +
    +
    +
    Valid values: <file>
    +
    +
    +
    +
    Default value: ${swift.home}/etc/tc.data
    +
    +
    +
    +
    Points to the location of the transformation catalog file which
    +contains information about installed applications. Details about the
    +format of the transformation catalog can be found here
    +<http://vds.uchicago.edu/vds/doc/userguide/html/H_TransformationCatalog.html>.
    +
    +

    tcp.port.range

    +
    +
    +
    Valid values: <start>,<end> where start and end are integers
    +
    +
    +
    +
    Default value: none
    +
    +
    +
    +
    A TCP port range can be specified to restrict the ports on which
    +GRAM callback services are started. This is likely needed if your
    +submit host is behind a firewall, in which case the firewall should
    +be configured to allow incoming connections on ports in the range.
    +
    +

    throttle.file.operations

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 8
    +
    +
    +
    +
    Limits the total number of concurrent file operations that can
    +happen at any given time. File operations (like transfers) require
    +an exclusive connection to a site. These connections can be
    +expensive to establish. A large number of concurrent file operations
    +may cause Swift to attempt to establish many such expensive
    +connections to various sites. Limiting the number of concurrent file
    +operations causes Swift to use a small number of cached connections
    +and achieve better overall performance.
    +
    +

    throttle.host.submit

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 2
    +
    +
    +
    +
    Limits the number of concurrent submissions for any of the sites
    +Swift will try to send jobs to. In other words it guarantees that no
    +more than the value of this throttle jobs sent to any site will be
    +concurrently in a state of being submitted.
    +
    +

    throttle.score.job.factor

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    The Swift scheduler has the ability to limit the number of
    +concurrent jobs allowed on a site based on the performance history
    +of that site. Each site is assigned a score (initially 1), which can
    +increase or decrease based on whether the site yields successful or
    +faulty job runs. The score for a site can take values in the (0.1,
    +100) interval. The number of allowed jobs is calculated using the
    +following formula:
    +
    +
    +
    +
    2 + score*throttle.score.job.factor
    +
    +
    +
    +
    This means a site will always be allowed at least two concurrent
    +jobs and at most 2 + 100*throttle.score.job.factor. With a default
    +of 4 this means at least 2 jobs and at most 402.
    +
    +
    +
    +
    This parameter can also be set per site using the jobThrottle
    +profile key in a site catalog entry.
    +
    +

    throttle.submit

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    Limits the number of concurrent submissions for a run. This throttle
    +only limits the number of concurrent tasks (jobs) that are being
    +sent to sites, not the total number of concurrent jobs that can be
    +run. The submission stage in GRAM is one of the most CPU expensive
    +stages (due mostly to the mutual authentication and delegation).
    +Having too many concurrent submissions can overload either or both
    +the submit host CPU and the remote host/head node causing degraded
    +performance.
    +
    +

    throttle.transfers

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    Limits the total number of concurrent file transfers that can happen
    +at any given time. File transfers consume bandwidth. Too many
    +concurrent transfers can cause the network to be overloaded
    +preventing various other signaling traffic from flowing properly.
    +
    +

    ticker.disable

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    When set to true, suppresses the output progress ticker that Swift
    +sends to the console every few seconds during a run (since Swift 0.9)
    +
    +

    wrapper.invocation.mode

    +
    +
    +
    Valid values: absolute, relative
    +
    +
    +
    +
    Default value: absolute
    +
    +
    +
    +
    Determines if Swift remote wrappers will be executed by specifying
    +an absolute path, or a path relative to the job initial working
    +directory. In most cases, execution will be successful with either
    +option. However, some execution sites ignore the specified initial
    +working directory, and so absolute must be used. Conversely on
    +some sites, job directories appear in a different place on the
    +worker node file system than on the filesystem access node, with the
    +execution system handling translation of the job initial working
    +directory. In such cases, relative mode must be used. (since Swift
    +0.9)
    +
    +

    wrapper.parameter.mode

    +
    +
    +
    Controls how Swift will supply parameters to the remote wrapper
    +script. args mode will pass parameters on the command line. Some
    +execution systems do not pass commandline parameters sufficiently
    +cleanly for Swift to operate correctly. files mode will pass
    +parameters through an additional input file (since Swift 0.95). This
    +provides a cleaner communication channel for parameters, at the
    +expense of transferring an additional file for each job invocation.
    +
    +

    wrapperlog.always.transfer

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls when output from the Swift remote wrapper is
    +transfered back to the submit site. When set to false, wrapper
    +logs are only transfered for jobs that fail. If set to true,
    +wrapper logs are transfered after every job is completed or failed.
    +
    +

    Example:

    +
    +
    +
    sites.file=${vds.home}/etc/sites.xml
    +tc.file=${vds.home}/etc/tc.data
    +ip.address=192.168.0.1
    +
    +
    +
    +

    11. Profiles

    +
    +

    Profiles are configuration parameters than can be specified either for +sites or for transformation catalog entries. They influence the +behaviour of Swift towards that site (for example, by changing the load +Swift will place on that sites) or when running a particular procedure.

    +

    Profile entries for a site are specified in the site catalog. Profile +entries for specific procedures are specified in the transformation +catalog.

    +
    +

    11.1. Karajan namespace

    +

    maxSubmitRate limits the maximum rate of job submission, in jobs per +second. For example:

    +
    +
    +
    <profile namespace="karajan" key="maxSubmitRate">0.2</profile>
    +

    will limit job submission to 0.2 jobs per second (or equivalently, one +job every five seconds).

    +

    jobThrottle allows the job throttle factor (see Swift property +throttle.score.job.factor to be +set per site.

    +

    initialScore allows the initial score for rate limiting and site +selection to be set to a value other than 0.

    +

    delayBase controls how much a site will be delayed when it performs +poorly. With each reduction in a sites score by 1, the delay between +execution attempts will increase by a factor of delayBase.

    +

    status.mode allows the status.mode property to be set per-site instead +of for an entire run. See the Swift configuration properties section for +more information. (since Swift 0.8)

    +
    +
    +

    11.2. swift namespace

    +

    storagesize limits the amount of space that will be used on the remote +site for temporary files. When more than that amount of space is used, +the remote temporary file cache will be cleared using the algorithm +specified in the caching.algorithm property.

    +

    wrapperInterpreter - The wrapper interpreter indicates the command +(executable) to be used to run the Swift wrapper script. The default is +"/bin/bash" on Unix sites and "cscript.exe" on Windows sites.

    +

    wrapperInterpreterOptions - Allows specifying additional options to the +executable used to run the Swift wrapper. The defaults are no options on +Unix sites and "Nologo" on Windows sites.

    +

    wrapperScript - Specifies the name of the wrapper script to be used on a +site. The defaults are "_swiftwrap" on Unix sites and "_swiftwrap.vbs" +on Windows sites. If you specify a custom wrapper script, it must be +present in the "libexec" directory of the Swift installation.

    +

    cleanupCommand Indicates the command to be run at the end of a Swift +run to clean up the run directories on a remote site. Defaults are +"/bin/rm" on Unix sites and "cmd.exe" on Windows sites

    +

    cleanupCommandOptions Specifies the options to be passed to the +cleanup command above. The options are passed in the argument list to +the cleanup command. After the options, the last argument is the +directory to be deleted. The default on Unix sites is "-rf". The default +on Windows sites is ["/C", "del", "/Q"].

    +
    +
    +

    11.3. Globus namespace

    +

    maxwalltime specifies a walltime limit for each job, in minutes.

    +

    The following formats are recognized:

    +
      +
    • +

      +Minutes +

      +
    • +
    • +

      +Hours:Minutes +

      +
    • +
    • +

      +Hours:Minutes:Seconds +

      +
    • +
    +

    Example:

    +
    +
    +
    localhost       echo    /bin/echo       INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="00:20:00"
    +

    When replication is enabled (see replication), then +walltime will also be enforced at the Swift client side: when a job has +been active for more than twice the maxwalltime, Swift will kill the job +and regard it as failed.

    +

    When clustering is used, maxwalltime will be used to select which jobs +will be clustered together. More information on this is available in the +clustering section.

    +

    When coasters as used, maxwalltime influences the default coaster +worker maxwalltime, and which jobs will be sent to which workers. More +information on this is available in the coasters section.

    +

    queue is used by the PBS, GRAM2 and GRAM4 providers. This profile +entry specifies which queue jobs will be submitted to. The valid queue +names are site-specific.

    +

    host_types specifies the types of host that are permissible for a job +to run on. The valid values are site-specific. This profile entry is +used by the GRAM2 and GRAM4 providers.

    +

    condor_requirements allows a requirements string to be specified when +Condor is used as an LRM behind GRAM2. Example:

    +
    +
    +
    <profile
    +namespace="globus" key="condor_requirements">Arch == "X86_64" || Arch="INTEL"</profile>
    +

    slots When using coasters, this parameter specifies the +maximum number of jobs/blocks that the coaster scheduler will have +running at any given time. The default is 20.

    +

    workersPerNode - This parameter determines how many coaster workers are +started one each compute node. The default value is 1.

    +

    nodeGranularity - When allocating a coaster worker block, this parameter +restricts the number of nodes in a block to a multiple of this value. +The total number of workers will then be a multiple of workersPerNode * +nodeGranularity. The default value is 1.

    +

    allocationStepSize - Each time the coaster block scheduler computes a +schedule, it will attempt to allocate a number of slots from the number +of available slots (limited using the above slots profile). This +parameter specifies the maximum fraction of slots that are allocated in +one schedule. Default is 0.1.

    +

    lowOverallocation - Overallocation is a function of the walltime of a +job which determines how long (time-wise) a worker job will be. For +example, if a number of 10s jobs are submitted to the coaster service, +and the overallocation for 10s jobs is 10, the coaster scheduler will +attempt to start worker jobs that have a walltime of 100s. The +overallocation is controlled by manipulating the end-points of an +overallocation function. The low endpoint, specified by this parameter, +is the overallocation for a 1s job. The high endpoint is the +overallocation for a (theoretical) job of infinite length. The +overallocation for job sizes in the [1s, +inf) interval is determined +using an exponential decay function: overallocation(walltime) = walltime +* (lowOverallocation - highOverallocation) * exp(-walltime * +overallocationDecayFactor) + highOverallocation The default value of +lowOverallocation is 10.

    +

    highOverallocation - The high overallocation endpoint (as described +above). Default: 1

    +

    overallocationDecayFactor - The decay factor for the overallocation +curve. Default 0.001 (1e-3).

    +

    spread - When a large number of jobs is submitted to the a coaster +service, the work is divided into blocks. This parameter allows a rough +control of the relative sizes of those blocks. A value of 0 indicates +that all work should be divided equally between the blocks (and blocks +will therefore have equal sizes). A value of 1 indicates the largest +possible spread. The existence of the spread parameter is based on the +assumption that smaller overall jobs will generally spend less time in +the queue than larger jobs. By submitting blocks of different sizes, +submitted jobs may be finished quicker by smaller blocks. Default: 0.9.

    +

    reserve - Reserve time is a time in the allocation of a worker that sits +at the end of the worker time and is useable only for critical +operations. For example, a job will not be submitted to a worker if it +overlaps its reserve time, but a job that (due to inaccurate walltime +specification) runs into the reserve time will not be killed (note that +once the worker exceeds its walltime, the queuing system will kill the +job anyway). Default 10 (s).

    +

    maxnodes - Determines the maximum number of nodes that can be allocated +in one coaster block. Default: unlimited.

    +

    maxtime - Indicates the maximum walltime that a coaster block can have. +Default: unlimited.

    +

    remoteMonitorEnabled - If set to "true", the client side will get a +Swing window showing, graphically, the state of the coaster scheduler +(blocks, jobs, etc.). Default: false

    +
    +
    +

    11.4. env namespace

    +

    Profile keys set in the env namespace will be set in the unix +environment of the executed job. Some environment variables influence +the worker-side behaviour of Swift:

    +

    PATHPREFIX - set in env namespace profiles. This path is prefixed onto +the start of the PATH when jobs are executed. It can be more useful +than setting the PATH environment variable directly, because setting +PATH will cause the execution site’s default path to be lost.

    +

    SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift +will use the path specified here as a worker-node local temporary +directory to copy input files to before running a job. If unset, Swift +will keep input files on the site-shared filesystem. In some cases, +copying to a worker-node local directory can be much faster than having +applications access the site-shared filesystem directly.

    +

    SWIFT_EXTRA_INFO - set in env namespace profiles. If set, then Swift +will execute the command specified in SWIFT_EXTRA_INFO on execution +sites immediately before each application execution, and will record the +stdout of that command in the wrapper info log file for that job. This +is intended to allow software version and other arbitrary information +about the remote site to be gathered and returned to the submit side. +(since Swift 0.9)

    +
    +
    +
    +
    +

    12. The Site Catalog - sites.xml

    +
    +

    The site catalog lists details of each site that Swift can use. The +default file contains one entry for local execution, and a large number +of commented-out example entries for other sites.

    +

    By default, the site catalog is stored in etc/sites.xml. This path can +be overridden with the sites.file configuration property, either in +the Swift configuration file or on the command line.

    +

    The sites file is formatted as XML. It consists of <pool> elements, +one for each site that Swift will use.

    +
    +

    12.1. Pool element

    +

    Each pool element must have a handle attribute, giving a symbolic +name for the site. This can be any name, but must correspond to entries +for that site in the transformation catalog.

    +

    Optionally, the gridlaunch attribute can be used to specify the path +to kickstart on the site.

    +

    Each pool must specify a file transfer method, an execution method and +a remote working directory. Optionally, profile settings can +be specified.

    +
    +
    +

    12.2. File transfer method

    +

    Transfer methods are specified with either the <gridftp> element or +the <filesystem> element.

    +

    To use gridftp or local filesystem copy, use the <gridftp> element:

    +
    +
    +
    <gridftp  url="gsiftp://evitable.ci.uchicago.edu" />
    +

    The url attribute may specify a GridFTP server, using the gsiftp URI +scheme; or it may specify that filesystem copying will be used (which +assumes that the site has access to the same filesystem as the +submitting machine) using the URI local://localhost.

    +

    Filesystem access using scp (the SSH copy protocol) can be specified +using the <filesystem> element:

    +
    +
    +
    <filesystem url="www11.i2u2.org" provider="ssh"/>
    +

    For additional ssh configuration information, see the ssh execution +provider documentation below.

    +

    Filesystem access using CoG coasters can be also be +specified using the <filesystem> element. More detail about +configuring that can be found in the CoG coasters section.

    +
    +
    +

    12.3. Execution method

    +

    Execution methods may be specified either with the <jobmanager> or +<execution> element.

    +

    The <jobmanager> element can be used to specify execution through +GRAM2. For example,

    +
    +
    +
    <jobmanager universe="vanilla" url="evitable.ci.uchicago.edu/jobmanager-fork" major="2" />
    +

    The universe attribute should always be set to vanilla. The url +attribute should specify the name of the GRAM2 gatekeeper host, and the +name of the jobmanager to use. The major attribute should always be set +to 2.

    +

    The <execution> element can be used to specify execution through other +execution providers:

    +

    To use GRAM4, specify the gt4 provider. For example:

    +
    +
    +
    <execution provider="gt4" jobmanager="PBS" url="tg-grid.uc.teragrid.org" />
    +

    The url attribute should specify the GRAM4 submission site. The +jobmanager attribute should specify which GRAM4 jobmanager will be used.

    +

    For local execution, the local provider should be used, like this:

    +
    +
    +
    <execution provider="local" url="none" />
    +

    For PBS execution, the pbs provider should be used:

    +
    +
    +
    <execution provider="pbs" url="none" />
    +

    The GLOBUS::queue profile key can be used to +specify which PBS queue jobs will be submitted to.

    +

    For execution through a local Condor installation, the condor provider +should be used. This provider can run jobs either in the default vanilla +universe, or can use Condor-G to run jobs on remote sites.

    +

    When running locally, only the <execution> element needs to be specified:

    +
    +
    +
    <execution provider="condor" url="none" />
    +

    When running with Condor-G, it is necessary to specify the Condor grid +universe and the contact string for the remote site. For example:

    +
    +
    +
    <execution provider="condor" />
    +<profile namespace="globus" key="jobType">grid</profile>
    +<profile namespace="globus" key="gridResource">gt2 belhaven-1.renci.org/jobmanager-fork</profile>
    +

    For execution through SSH, the ssh provider should be used:

    +
    +
    +
    <execution url="www11.i2u2.org" provider="ssh"/>
    +

    with configuration made in ~/.ssh/auth.defaults with the string +www11.i2u2.org changed to the appropriate host name:

    +
    +
    +
    www11.i2u2.org.type=key
    +www11.i2u2.org.username=hategan
    +www11.i2u2.org.key=/home/mike/.ssh/i2u2portal
    +www11.i2u2.org.passphrase=XXXX
    +

    For execution using the CoG Coaster mechanism, the coaster +provider should be used:

    +
    +
    +
    <execution provider="coaster" url="tg-grid.uc.teragrid.org"
    +    jobmanager="gt2:gt2:pbs" />
    +

    More details about configuration of coasters can be found in the section +on coasters.

    +
    +
    +

    12.4. Work directory

    +

    The workdirectory element specifies where on the site files can be +stored.

    +
    +
    +
    <workdirectory>/home/benc</workdirectory>
    +

    This file must be accessible through the transfer mechanism specified in +the <gridftp> element and also mounted on all worker nodes that will +be used for execution. A shared cluster scratch filesystem is +appropriate for this.

    +
    +
    +

    12.5. Profiles

    +

    Profile keys can be specified using the <profile> element. +For example:

    +
    +
    +
    <profile namespace="globus" key="queue">fast</profile>
    +

    The site catalog format is an evolution of the VDS site catalog format +which is documented here +http://vds.uchicago.edu/vds/doc/userguide/html/H_SiteCatalog.html.

    +
    +
    +
    +
    +

    13. The Transformation Catalog - tc.data

    +
    +

    The transformation catalog lists where application executables are +located on remote sites.

    +

    By default, the site catalog is stored in etc/tc.data. This path can +be overridden with the tc.file configuration property, either in the +Swift configuration file or on the command line.

    +

    The format is one line per executable per site, with fields separated by +tabs. Spaces cannot be used to separate fields.

    +

    Some example entries:

    +
    +
    +
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    +TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="0:1"
    +

    The fields are: site, transformation name, executable path, installation +status, platform, and profile entrys.

    +

    The site field should correspond to a site name listed in the sites catalog.

    +

    The transformation name should correspond to the transformation name +used in a SwiftScript app procedure.

    +

    The executable path should specify where the particular executable is +located on that site.

    +

    The installation status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively.

    +

    The profiles field should be set to null if no profile entries are to +be specified, or should contain the profile entries separated by +semicolons.

    +
    +
    +
    +

    14. Build options

    +
    +

    See the Swift download page +http://www.ci.uchicago.edu/swift/downloads/ for instructions on +downloading and building Swift from source. When building, various build +options can be supplied on the ant commandline. These are summarised here:

    +

    with-provider-condor - build with CoG condor provider

    +

    with-provider-coaster - build with CoG coaster provider (see the +section on coasters). Since 0.8, coasters are always built, +and this option has no effect.

    +

    with-provider-deef - build with Falkon provider deef. In order for +this option to work, it is necessary to check out the provider-deef code +in the cog/modules directory alongside swift:

    +
    +
    +
    $ cd cog/modules
    +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef
    +$ cd ../swift
    +$ ant -Dwith-provider-deef=true redist
    +

    with-provider-wonky - build with provider-wonky, an execution provider +that provides delays and unreliability for the purposes of testing +Swift’s fault tolerance mechanisms. In order for this option to work, it +is necessary to check out the provider-wonky code in the |cog/modules| +directory alongside swift:

    +
    +
    +
    $ cd cog/modules
    +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky
    +$ cd ../swift|*
    +$ ant -Dwith-provider-wonky=true redist
    +

    no-supporting - produces a distribution without supporting commands +such as grid-proxy-init. This is intended for when the Swift +distribution will be used in an environment where those commands are +already provided by other packages, where the Swift package should be +providing only Swift commands, and where the presence of commands such +as grid-proxy-init from the Swift distribution in the path will mask the +presence of those commands from their true distribution package such as +a Globus Toolkit package.

    +
    +
    +
    $ ant -Dno-supporting=true redist
    +
    +
    +
    +

    15. Kickstart

    +
    +

    Kickstart is a tool that can be used to gather various information about +the remote execution environment for each job that Swift tries to run.

    +

    For each job, Kickstart generates an XML invocation record. By default +this record is staged back to the submit host if the job fails.

    +

    Before it can be used it must be installed on the remote site and the +sites file must be configured to point to kickstart.

    +

    Kickstart can be downloaded as part of the Pegasus worker package +available from the worker packages section of the Pegasus download page +http://pegasus.isi.edu/code.php.

    +

    Untar the relevant worker package somewhere where it is visible to all +of the worker nodes on the remote execution machine (such as in a shared +application filesystem).

    +

    Now configure the gridlaunch attribute of the sites catalog to point to +that path, by adding a gridlaunch attribute to the pool element in +the site catalog:

    +
    +
    +
    <pool handle="example" gridlaunch="/usr/local/bin/kickstart" sysinfo="INTEL32::LINUX">
    +...
    +</pool>
    +

    There are various kickstat.* properties, which have sensible default +values. These are documented in the properties section.

    +
    +
    +
    +

    16. Reliability mechanisms

    +
    +

    This section details reliabilty mechanisms in Swift: retries, restarts +and replication.

    +
    +

    16.1. Retries

    +

    If an application procedure execution fails, Swift will attempt that +execution again repeatedly until it succeeds, up until the limit defined +in the execution.retries configuration property.

    +

    Site selection will occur for retried jobs in the same way that it +happens for new jobs. Retried jobs may run on the same site or may run +on a different site.

    +

    If the retry limit execution.retries is reached for an application +procedure, then that application procedure will fail. This will cause +the entire run to fail - either immediately (if the lazy.errors +property is false) or after all other possible work has been attempted +(if the lazy.errors property is true).

    +
    +
    +

    16.2. Restarts

    +

    If a run fails, Swift can resume the program from the point of failure. +When a run fails, a restart log file will be left behind in a file named +using the unique job ID and a .rlog extension. This restart log can +then be passed to a subsequent Swift invocation using the -resume +parameter. Swift will resume execution, avoiding execution of +invocations that have previously completed successfully. The SwiftScript +source file and input data files should not be modified between runs.

    +

    Every run creates a restart log file with a named composed of the file +name of the workflow being executed, an invocation ID, a numeric ID, and +the .rlog extension. For example, example.swift, when executed, +could produce the following restart log file: +example-ht0adgi315l61.0.rlog. Normally, if the run completes +successfully, the restart log file is deleted. If however the workflow +fails, swift can use the restart log file to continue execution from a +point before the failure occurred. In order to restart from a restart +log file, the -resume logfile argument can be used after the +SwiftScript program file name. Example:

    +
    +
    +
    $ swift -resume example-ht0adgi315l61.0.rlog example.swift.
    +
    +
    +

    16.3. Replication

    +

    When an execution job has been waiting in a site queue for a certain +period of time, Swift can resubmit replicas of that job (up to the limit +defined in the replication.limit configuration property). When any of +those jobs moves from queued to active state, all of the other replicas +will be cancelled.

    +

    This is intended to deal with situations where some sites have a +substantially longer (sometimes effectively infinite) queue time than +other sites. Selecting those slower sites can cause a very large delay +in overall run time.

    +

    Replication can be enabled by setting the replication.enabled +configuration property to true. The maximum number of replicas that +will be submitted for a job is controlled by the replication.limit +configuration property.

    +

    When replication is enabled, Swift will also enforce the maxwalltime +profile setting for jobs as documented in the profiles section.

    +
    +
    +
    +
    +

    17. Clustering

    +
    +

    Swift can group a number of short job submissions into a single larger +job submission to minimize overhead involved in launching jobs (for +example, caused by security negotiation and queuing delay). In general, +CoG coasters should be used in preference to the clustering +mechanism documented in this section.

    +

    By default, clustering is disabled. It can be activated by setting the +clustering.enabled property to true.

    +

    A job is eligible for clustering if the GLOBUS::maxwalltime profile +is specified in the tc.data entry for that job, and its value is +less than the value of the clustering.min.time property.

    +

    Two or more jobs are considered compatible if they share the same site +and do not have conflicting profiles (e.g. different values for the same +environment variable).

    +

    When a submitted job is eligible for clustering, it will be put in a +clustering queue rather than being submitted to a remote site. The +clustering queue is processed at intervals specified by the +clustering.queue.delay property. The +processing of the clustering queue consists of selecting compatible jobs +and grouping them into clusters whose maximum wall time does not exceed +twice the value of the clustering.min.time property.

    +
    +
    +
    +

    18. Coasters

    +
    +

    Coasters were introduced in Swift v0.6 as an experimental feature.

    +

    In many applications, Swift performance can be greatly enhanced by the +use of CoG coasters. CoG coasters provide a low-overhead job submission +and file transfer mechanism suited for the execution of short jobs (on +the order of a few seconds) and the transfer of small files (on the +order of a few kilobytes) for which other grid protocols such as GRAM +and GridFTP are poorly suited.

    +

    The coaster mechanism submits a head job using some other execution +mechanism such as GRAM, and for each worker node that will be used in a +remote cluster, it submits a worker job, again using some other +execution mechanism such as GRAM. Details on the design of the coaster +mechanism can be found here. http://wiki.cogkit.org/wiki/Coasters

    +

    The head job manages file transfers and the dispatch of execution jobs +to workers. Much of the overhead associated with other grid protocols +(such as authentication and authorization, and allocation of worker +nodes by the site’s local resource manager) is reduced, because that +overhead is associated with the allocation of a coaster head or coaster +worker, rather than with every Swift-level procedure invocation; +potentially hundreds or thousands of Swift-level procedure invocations +can be run through a single worker.

    +

    Coasters can be configured for use in two situations: job execution and +file transfer.

    +

    To use for job execution, specify a sites.xml execution element like this:

    +
    +
    +
    <execution provider="coaster" jobmanager="gt2:gt2:pbs" url="grid.myhost.org">
    +

    The jobmanager string contains more detail than with other providers. It +contains either two or three colon separated fields: 1:the provider to +be use to execute the coaster head job - this provider will submit from +the Swift client side environment. Commonly this will be one of the GRAM +providers; 2: the provider to be used to execute coaster worker jobs. +This provider will be used to submit from the coaster head job +environment, so a local scheduler provider can sometimes be used instead +of GRAM. 3: optionally, the jobmanager to be used when submitting worker +job using the provider specified in field 2.

    +

    To use for file transfer, specify a sites.xml filesystem element like this:

    +
    +
    +
    <filesystem provider="coaster" url="gt2://grid.myhost.org" />
    +

    The url parameter should be a pseudo-URI formed with the URI scheme +being the name of the provider to use to submit the coaster head job, +and the hostname portion being the hostname to be used to execute the +coaster head job. Note that this provider and hostname will be used for +execution of a coaster head job, not for file transfer; so for example, +a GRAM endpoint should be specified here rather than a GridFTP endpoint.

    +

    Coasters are affected by the following profile settings, which are +documented in the Globus namespace profile section:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Profile keyBrief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a +multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a +block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a +block’s walltime be if all jobs are infinitely long

    overallocationDecayFactor

    How quickly should the overallocation curve +tend towards the highOverallocation as job walltimes get larger

    spread

    By how much should worker blocks vary in worker size

    workersPerNode

    How many coaster workers to run per execution node

    reserve

    How many seconds to reserve in a block’s walltime for +starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block

    remoteMonitorEnabled

    If true, show a graphical display of the status of +the coaster service

    +
    +
    +
    +
    +

    19. How-To Tips for Specific User Communities

    +
    +
    +

    19.1. Saving Logs - for UChicago CI Users

    +

    If you have a UChicago Computation Institute account, run this command +in your submit directory after each run. It will copy all your logs and +kickstart records into a directory at the CI for reporting, usage +tracking, support and debugging.

    +
    +
    +
    rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose
    +
    +
    +

    19.2. Specifying TeraGrid allocations

    +

    TeraGrid users with no default project or with several project +allocations can specify a project allocation using a profile key in the +site catalog entry for a TeraGrid site:

    +
    +
    +
    <profile namespace="globus" key="project">TG-CCR080002N</profile>
    +

    More information on the TeraGrid allocations process can be found here +http://www.teragrid.org/userinfo/access/allocations.php.

    +
    +
    +

    19.3. Launching MPI jobs from Swift

    +

    Here is an example of running a simple MPI program.

    +

    In SwiftScript, we make an invocation that does not look any different +from any other invocation. In the below code, we do not have any input +files, and have two output files on stdout and stderr:

    +
    +
    +
    type file;
    +
    +(file o, file e) p() {
    +    app {
    +        mpi stdout=@filename(o) stderr=@filename(e);
    +    }
    +}
    +
    +file mpiout <"mpi.out">;
    +file mpierr <"mpi.err">;
    +
    +(mpiout, mpierr) = p();
    +

    Now we define how mpi will run in tc.data:

    +
    +
    +
    tguc    mpi             /home/benc/mpi/mpi.sh   INSTALLED       INTEL32::LINUX GLOBUS::host_xcount=3
    +

    mpi.sh is a wrapper script that launches the MPI program. It must be +installed on the remote site:

    +
    +
    +
    #!/bin/bash
    +mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out
    +

    Because of the way that Swift runs its server side code, +provider-specific MPI modes (such as GRAM jobType=mpi) should not be +used. Instead, the mpirun command should be explicitly invoked.

    +
    +
    +

    19.4. Running on Windows

    +

    Since 10/11/09, the development version of Swift has the ability to run +on a Windows machine, as well as the ability to submit jobs to a Windows +site (provided that an appropriate provider is used).

    +

    In order to launch Swift on Windows, use the provided batch file +(swift.bat). In certain cases, when a large number of jar libraries are +present in the Swift lib directory and depending on the exact location +of the Swift installation, the classpath environment variable that the +Swift batch launcher tries to create may be larger than what Windows can +handle. In such a case, either install Swift in a directory closer to +the root of the disk (say, c:\swift) or remove non-essential jar files +from the Swift lib directory.

    +

    Due to the large differences between Windows and Unix environments, +Swift must use environment specific tools to achieve some of its goals. +In particular, each Swift executable is launched using a wrapper script. +This script is a Bourne Shell script. On Windows machines, which have no +Bourne Shell interpreter installed by default, the Windows Scripting +Host is used instead, and the wrapper script is written in VBScript. +Similarly, when cleaning up after a run, the "/bin/rm" command available +in typical Unix environments must be replaced by the "del" shell command.

    +

    It is important to note that in order to select the proper set of tools +to use, Swift must know when a site runs under Windows. To inform Swift +of this, specify the "sysinfo" attribute for the "pool" element in the +site catalog. For example:

    +
    +
    +
    <pool handle="localhost" sysinfo="INTEL32::WINDOWS">
    +...
    +</pool>
    +
    +
    +
    +
    +

    + + + Added: branches/release-0.92/docs/userguide/userguide.txt =================================================================== --- branches/release-0.92/docs/userguide/userguide.txt (rev 0) +++ branches/release-0.92/docs/userguide/userguide.txt 2011-05-16 19:29:35 UTC (rev 4479) @@ -0,0 +1,3000 @@ +Swift User Guide +================ + +:toc: +:icons: +:website: http://www.ci.uchicago.edu/swift/guides/userguide.php +:numbered: + +Overview +-------- +This manual provides reference material for Swift: the SwiftScript +language and the Swift runtime system. For introductory material, +consult the Swift tutorial +. + +Swift is a data-oriented coarse grained scripting language that supports +dataset typing and mapping, dataset iteration, conditional branching, +and procedural composition. + +Swift programs (or workflows) are written in a language called +SwiftScript. + +SwiftScript programs are dataflow oriented - they are primarily +concerned with processing (possibly large) collections of data files, by +invoking programs to do that processing. Swift handles execution of such +programs on remote sites by choosing sites, handling the staging of +input and output files to and from the chosen sites and remote execution +of program code. + + +The SwiftScript Language +------------------------ + +Language basics +~~~~~~~~~~~~~~~ +A Swift script describes data, application components, invocations of +applications components, and the inter-relations (data flow) between +those invocations. + +Data is represented in a script by strongly-typed single-assignment +variables. The syntax superficially resembles C and Java. For example, +{ and } characters are used to enclose blocks of statements. + +Types in Swift can be atomic or composite. An atomic type can be +either a primitive type or a mapped type. Swift provides a fixed set +of primitive types, such as integer and string. A mapped type +indicates that the actual data does not reside in CPU addressable memory +(as it would in conventional programming languages), but in POSIX-like +files. Composite types are further subdivided into structures and +arrays. Structures are similar in most respects to structure types in +other languages. Arrays use numeric indices, but are sparse. They can +contain elements of any type, including other array types, but all +elements in an array must be of the same type. We often refer to +instances of composites of mapped types as datasets. + +image:type-hierarchy.png[] + +Mapped type and composite type variable declarations can be annotated +with a mapping descriptor indicating the file(s) that make up that +dataset. For example, the following line declares a variable named +photo with type image. It additionally declares that the data for +this variable is stored in a single file named shane.jpeg. + +[java] +source~~~~ +image photo <"shane.jpeg">; +source~~~~ + +Component programs of scripts are declared in an app declaration, with +the description of the command line syntax for that program and a list +of input and output data. An app block describes a functional/dataflow +style interface to imperative components. + +For example, the following example lists a procedure which makes use of +the ImageMagick convert command to +rotate a supplied image by a specified angle: + +[java] +source~~~~ +app (image output) rotate(image input) { + convert "-rotate" angle @input @output; +} +source~~~~ + +A procedure is invoked using the familiar syntax: + +[java] +source~~~~ +rotated = rotate(photo, 180); +source~~~~ + +While this looks like an assignment, the actual unix level execution +consists of invoking the command line specified in the app +declaration, with variables on the left of the assignment bound to the +output parameters, and variables to the right of the procedure +invocation passed as inputs. + +The examples above have used the type image without any definition of +that type. We can declare it as a marker type which has no structure +exposed to SwiftScript: + +[java] +source~~~~ +type image; +source~~~~ + +This does not indicate that the data is unstructured; but it indicates +that the structure of the data is not exposed to SwiftScript. Instead, +SwiftScript will treat variables of this type as individual opaque files. + +With mechanisms to declare types, map variables to data files, and +declare and invoke procedures, we can build a complete (albeit simple) +script: + +[java] +source~~~~ +type image; +image photo <"shane.jpeg">; +image rotated <"rotated.jpeg">; + +app (image output) rotate(image input, int angle) { + convert "-rotate" angle @input @output; +} + +rotated = rotate(photo, 180); +source~~~~ + +This script can be invoked from the command line: +[txt] +source~~~~ + $ ls *.jpeg + shane.jpeg + $ swift example.swift + ... + $ ls *.jpeg + shane.jpeg rotated.jpeg +source~~~~ + +This executes a single convert command, hiding from the user features +such as remote multisite execution and fault tolerance that will be +discussed in a later section. + +.Figure 1. shane.jpeg +image:userguide-shane.jpeg[] + +.Figure 2. rotated.jpeg +image:userguide-rotated.jpeg[] + + +Arrays and Parallel Execution +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Arrays of values can be declared using the [] suffix. An array be +mapped to a collection of files, one element per file, by using a +different form of mapping expression. For example, the filesys_mapper +maps all files matching a particular unix glob pattern into an array: + +[java] +source~~~~ +file frames[] ; +source~~~~ + +The foreach construct can be used to apply the same block of code to +each element of an array: + +[java] +source~~~~ +foreach f,ix in frames { + output[ix] = rotate(frames, 180); +} +source~~~~ + +Sequential iteration can be expressed using the iterate construct: + +[java] +source~~~~ +step[0] = initialCondition(); +iterate ix { + step[ix] = simulate(step[ix-1]); +} +source~~~~ + +This fragment will initialise the 0-th element of the step array to +some initial condition, and then repeatedly run the simulate +procedure, using each execution's outputs as input to the next step. + +Ordering of execution +~~~~~~~~~~~~~~~~~~~~~ +Non-array variables are single-assignment, which means that they must +be assigned to exactly one value during execution. A procedure or +expression will be executed when all of its input parameters have been +assigned values. As a result of such execution, more variables may +become assigned, possibly allowing further parts of the script to execute. + +In this way, scripts are implicitly parallel. Aside from serialisation +implied by these dataflow dependencies, execution of component programs +can proceed in parallel. + +In this fragment, execution of procedures p and q can happen in +parallel: + +[java] +source~~~~ +y=p(x); +z=q(x); +source~~~~ + +while in this fragment, execution is serialised by the variable y, +with procedure p executing before q. + +[java] +source~~~~ +y=p(x); +z=q(y); +source~~~~ + +Arrays in SwiftScript are more monotonic - a generalisation of being +assignment. Knowledge about the content of an array increases during +execution, but cannot otherwise change. Each element of the array is +itself single assignment or monotonic (depending on its type). During a +run all values for an array are eventually known, and that array is +regarded as closed. + +Statements which deal with the array as a whole will often wait for the +array to be closed before executing (thus, a closed array is the +equivalent of a non-array type being assigned). However, a foreach +statement will apply its body to elements of an array as they become +known. It will not wait until the array is closed. + +Consider this script: +[java] +source~~~~ +file a[]; +file b[]; +foreach v,i in a { + b[i] = p(v); +} +a[0] = r(); +a[1] = s(); +source~~~~ + +Initially, the foreach statement will have nothing to execute, as the +array a has not been assigned any values. The procedures r and s +will execute. As soon as either of them is finished, the corresponding +invocation of procedure p will occur. After both r and s have +completed, the array a will be closed since no other statements in the +script make an assignment to a. + + +Compound procedures +~~~~~~~~~~~~~~~~~~~ + +As with many other programming languages, procedures consisting of +SwiftScript code can be defined. These differ from the previously +mentioned procedures declared with the app keyword, as they invoke +other SwiftScript procedures rather than a component program. + +[java] +source~~~~ +(file output) process (file input) { + file intermediate; + intermediate = first(input); + output = second(intermediate); +} + +file x <"x.txt">; +file y <"y.txt">; +y = process(x); +source~~~~ + +This will invoke two procedures, with an intermediate data file named +anonymously connecting the first and second procedures. + +Ordering of execution is generally determined by execution of app +procedures, not by any containing compound procedures. In this code block: + +[java] +source~~~~ +(file a, file b) A() { + a = A1(); + b = A2(); +} +file x, y, s, t; +(x,y) = A(); +s = S(x); +t = S(y); +source~~~~ + +then a valid execution order is: A1 S(x) A2 S(y). The compound +procedure A does not have to have fully completed for its return +values to be used by subsequent statements. + + +More about types +~~~~~~~~~~~~~~~~ + +Each variable and procedure parameter in SwiftScript is strongly typed. +Types are used to structure data, to aid in debugging and checking +program correctness and to influence how Swift interacts with data. + +The image type declared in previous examples is a marker type. +Marker types indicate that data for a variable is stored in a single +file with no further structure exposed at the SwiftScript level. + +Arrays have been mentioned above, in the arrays section. A code block +may be applied to each element of an array using foreach; or +individual elements may be references using [] notation. + +There are a number of primitive types: + +[options="header"] +|================ +|type |contains +|int |integers +|string |strings of text +|float |floating point numbers, that behave the same as Java doubles +|boolean |true/false +|================ + + +Complex types may be defined using the type keyword: + +[java] +source~~~~ +type headerfile; +type voxelfile; +type volume { + headerfile h; + voxelfile v; +} +source~~~~ + +Members of a complex type can be accessed using the . operator: + +[java] +source~~~~ +volume brain; +o = p(brain.h); +source~~~~ + +Sometimes data may be stored in a form that does not fit with Swift's +file-and-site model; for example, data might be stored in an RDBMS on +some database server. In that case, a variable can be declared to have +external type. This indicates that Swift should use the variable to +determine execution dependency, but should not attempt other data +management; for example, it will not perform any form of data stage-in +or stage-out it will not manage local data caches on sites; and it will +not enforce component program atomicity on data output. This can add +substantial responsibility to component programs, in exchange for +allowing arbitrary data storage and access methods to be plugged in to +scripts. + +[java] +source~~~~ +type file; + +app (external o) populateDatabase() { + populationProgram; +} + +app (file o) analyseDatabase(external i) { + analysisProgram @o; +} + +external database; +file result <"results.txt">; + +database = populateDatabase(); +result = analyseDatabase(database); +source~~~~ + +Some external database is represented by the database variable. The +populateDatabase procedure populates the database with some data, and +the analyseDatabase procedure performs some subsequent analysis on +that database. The declaration of database contains no mapping; and +the procedures which use database do not reference them in any way; +the description of database is entirely outside of the script. The +single assignment and execution ordering rules will still apply though; +populateDatabase will always be run before analyseDatabase. + +Data model +~~~~~~~~~~ +Data processed by Swift is strongly typed. It may be take the form of +values in memory or as out-of-core files on disk. Language constructs +called mappers specify how each piece of data is stored. + + +Mappers +~~~~~~~ +When a DSHandle represents a data file (or container of datafiles), it +is associated with a mapper. The mapper is used to identify which files +belong to that DSHandle. + +A dataset's physical representation is declared by a mapping descriptor, +which defines how each element in the dataset's logical schema is stored +in, and fetched from, physical structures such as directories, files, +and remote servers. + +Mappers are parameterized to take into account properties such as +varying dataset location. In order to access a dataset, we need to know +three things: its type, its mapping, and the value(s) of any +parameter(s) associated with the mapping descriptor. For example, if we +want to describe a dataset, of type imagefile, and whose physical +representation is a file called "file1.bin" located at +"/home/yongzh/data/", then the dataset might be declared as follows: + +[java] +source~~~~ +imagefile f1 +source~~~~ + +The above example declares a dataset called f1, which uses a single file +mapper to map a file from a specific location. + +SwiftScript has a simplified syntax for this case, since +single_file_mapper is frequently used: + +[java] +source~~~~ +binaryfile f1<"/home/yongzh/data/file1.bin"> +source~~~~ + +Swift comes with a number of mappers that handle common mapping +patterns. These are documented in the mappers section of this +guide. + +More technical details about SwiftScript +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The syntax of SwiftScript has a superficial resemblance to C and Java. +For example, { and } characters are used to enclose blocks of statements. + +A SwiftScript program consists of a number of statements. Statements may +declare types, procedures and variables, assign values to variables, and +express operations over arrays. + + +Variables +^^^^^^^^^ +Variables in SwiftScript are declared to be of a specific type. +Assignments to those variables must be data of that type. SwiftScript +variables are single-assignment - a value may be assigned to a variable +at most once. This assignment can happen at declaration time or later on +in execution. When an attempt to read from a variable that has not yet +been assigned is made, the code performing the read is suspended until +that variable has been written to. This forms the basis for Swift's +ability to parallelise execution - all code will execute in parallel +unless there are variables shared between the code that cause sequencing. + + +Variable Declarations +^^^^^^^^^^^^^^^^^^^^^ +Variable declaration statements declare new variables. They can +optionally assign a value to them or map those variables to on-disk files. + +Declaration statements have the general form: + +[java] +source~~~~ +typename variablename ( | = initialValue ) ; +source~~~~ + +The format of the mapping expression is defined in the Mappers section. +initialValue may be either an expression or a procedure call that +returns a single value. + +Variables can also be declared in a multivalued-procedure statement, +described in another section. + + +Assignment Statements +^^^^^^^^^^^^^^^^^^^^^ +Assignment statements assign values to previously declared variables. +Assignments may only be made to variables that have not already been +assigned. Assignment statements have the general form: + +[java] +source~~~~ +variable = value; +source~~~~ + +where value can be either an expression or a procedure call that returns +a single value. + +Variables can also be assigned in a multivalued-procedure statement, +described in another section. + + +Procedures +~~~~~~~~~~ +There are two kinds of procedure: An atomic procedure, which describes +how an external program can be executed; and compound procedures which +consist of a sequence of SwiftScript statements. + +A procedure declaration defines the name of a procedure and its input +and output parameters. SwiftScript procedures can take multiple inputs +and produce multiple outputs. Inputs are specified to the right of the +function name, and outputs are specified to the left. For example: + +[java] +source~~~~ +(type3 out1, type4 out2) myproc (type1 in1, type2 in2) +source~~~~ + +The above example declares a procedure called myproc, which has two +inputs in1 (of type type1) and in2 (of type type2) and two +outputs out1 (of type type3) and out2 (of type type4). + +A procedure input parameter can be an optional parameter in which case +it must be declared with a default value. When calling a procedure, both +positional parameter and named parameter passings can be passed, +provided that all optional parameters are declared after the required +parameters and any optional parameter is bound using keyword parameter +passing. For example, if myproc1 is defined as: + +[java] +source~~~~ +(binaryfile bf) myproc1 (int i, string s="foo") +source~~~~ + +Then that procedure can be called like this, omitting the optional +[java] +source~~~~ +parameter s: +binaryfile mybf = myproc1(1); +source~~~~ + +or like this supplying a value for the optional parameter s: +[java] +source~~~~ +binaryfile mybf = myproc1 (1, s="bar"); +source~~~~ + +Atomic procedures +^^^^^^^^^^^^^^^^^ +An atomic procedure specifies how to invoke an external executable +program, and how logical data types are mapped to command line arguments. + +Atomic procedures are defined with the app keyword: + +[java] +source~~~~ +app (binaryfile bf) myproc (int i, string s="foo") { + myapp i s @filename(bf); +} +source~~~~ + +which specifies that myproc invokes an executable called myapp, +passing the values of i, s and the filename of bf as command line +arguments. + + +Compound procedures +^^^^^^^^^^^^^^^^^^^ +A compound procedure contains a set of SwiftScript statements: + +[java] +source~~~~ +(type2 b) foo_bar (type1 a) { + type3 c; + c = foo(a); // c holds the result of foo + b = bar(c); // c is an input to bar +} +source~~~~ + +Control Constructs +~~~~~~~~~~~~~~~~~~ +SwiftScript provides if, switch, foreach, and iterate +constructs, with syntax and semantics similar to comparable constructs +in other high-level languages. + + +foreach +^^^^^^^ +The foreach construct is used to apply a block of statements to each +element in an array. For example: + +[java] +source~~~~ +check_order (file a[]) { + foreach f in a { + compute(f); + } +} +source~~~~ + +foreach statements have the general form: + +[java] +source~~~~ +foreach controlvariable (,index) in expression { + statements +} +source~~~~ + +The block of statements is evaluated once for each element in +expression which must be an array, with controlvariable set to the +corresponding element and index (if specified) set to the integer +position in the array that is being iterated over. + + +if +^^ +The if statement allows one of two blocks of statements to be +executed, based on a boolean predicate. if statements generally have +the form: + +[java] +source~~~~ +if(predicate) { + statements +} else { + statements +} +source~~~~ + +where predicate is a boolean expression. + + +switch +^^^^^^ + +switch expressions allow one of a selection of blocks to be chosen +based on the value of a numerical control expression. switch +statements take the general form: + +[java] +source~~~~ +switch(controlExpression) { + case n1: + statements2 + case n2: + statements2 + [...] + default: + statements +} +source~~~~ + +The control expression is evaluated, the resulting numerical value used +to select a corresponding case, and the statements belonging to that +case block are evaluated. If no case corresponds, then the statements +belonging to the default block are evaluated. + +Unlike C or Java switch statements, execution does not fall through to +subsequent case blocks, and no break statement is necessary at the +end of each block. + + +iterate +^^^^^^^ +iterate expressions allow a block of code to be evaluated repeatedly, +with an integer parameter sweeping upwards from 0 until a termination +condition holds. + +The general form is: + +[java] +source~~~~ +iterate var { + statements; +} until (terminationExpression); +source~~~~ + +with the variable var starting at 0 and increasing by one in each +iteration. That variable is in scope in the statements block and when +evaluating the termination expression. + +Operators +~~~~~~~~~ +The following infix operators are available for use in SwiftScript +expressions. + +[options="header"] +|================= +|operator|purpose +|+|numeric addition; string concatenation +|-|numeric subtraction +|*|numeric multiplication +|/|floating point division +|%/|integer division +|%%|integer remainder of division +|== !=|comparison and not-equal-to +|< > <= >=|numerical ordering +|&& \|\||boolean and, or +|!|boolean not +|================= + +Global constants +~~~~~~~~~~~~~~~~ + +At the top level of a SwiftScript program, the global modified may be +added to a declaration so that it is visible throughout the program, +rather than only at the top level of the program. This allows global +constants (of any type) to be defined. (since Swift 0.10) + + +Imports +~~~~~~~ +The import directive can be used to import definitions from another +SwiftScript file. (since Swift 0.10) + +For example, a SwiftScript program might contain this: + +[java] +source~~~~ +import defs; +file f; +source~~~~ + +which would import the content of defs.swift in the current directory: + +[java] +source~~~~ +type file; +source~~~~ + +Imported files are read from the current working directory. + +There is no requirement that a module is imported only once. If a module +is imported multiple times, for example in different files, then Swift +will only process the imports once. + +Imports may contain anything that is valid in a SwiftScript program, +including code that causes remote execution. + +Mappers +------- +Mappers provide a mechanism to specify the layout of mapped datasets on +disk. This is needed when Swift must access files to transfer them to +remote sites for execution or to pass to applications. + +Swift provides a number of mappers that are useful in common cases. This +section details those standard mappers. For more complex cases, it is +possible to write application-specific mappers in Java and use them +within a SwiftScript program. + + +The single file mapper +~~~~~~~~~~~~~~~~~~~~~~ +The single_file_mapper maps a single physical file to a dataset. + +[options="header"] +|======================= +|Swift variable|Filename +|f|myfile +|f[0]|INVALID +|f.bar|INVALID +|======================= + +[options="header"] +|================= +|parameter|meaning +|file|The location of the physical file including path and file name. +|================= + +Example: +[java] +source~~~~ +file f ; +source~~~~ + +There is a simplified syntax for this mapper: +[java] +source~~~~ +file f <"plot_outfile_param">; +source~~~~ + +The simple mapper +~~~~~~~~~~~~~~~~~ +The simple_mapper maps a file or a list of files into an array by +prefix, suffix, and pattern. If more than one file is matched, each of +the file names will be mapped as a subelement of the dataset. + +[options="header"] +|==================== +|Parameter|Meaning +|location|A directory that the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +|pattern|A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored. +|==================== + +[java] +source~~~~ +type file; +file f ; +source~~~~ + +The above maps all filenames that start with foo and have an extension +.txt into file f. + +[options="header"] +|================ +|Swift variable|Filename +|f|foo.txt +|================= +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting(string m) {. + app { + echo m stdout=@filename(t); + } +} + +messagefile outfile ; + +outfile = greeting("hi"); +source~~~~ + +This will output the string 'hi' to the file foo.txt. + +The simple_mapper can be used to map arrays. It will map the array +index into the filename between the prefix and suffix. + +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting(string m) { + app { + echo m stdout=@filename(t); + } +} + +messagefile outfile[] ; + +outfile[0] = greeting("hello"); +outfile[1] = greeting("middle"); +outfile[2] = greeting("goodbye"); +source~~~~ + +[options="header"] +|======================= +|Swift variable|Filename +|outfile[0]|baz0000.txt +|outfile[1]|baz0001.txt +|outfile[2]|baz0002.txt +|======================= + +simple_mapper can be used to map structures. It will map the name of +the structure member into the filename, between the prefix and the suffix. + +[java] +source~~~~ +type messagefile; + +type mystruct { + messagefile left; + messagefile right; +}; + +(messagefile t) greeting(string m) { + app { + echo m stdout=@filename(t); + } +} + +mystruct out ; + +out.left = greeting("hello"); +out.right = greeting("goodbye"); +source~~~~ + +This will output the string "hello" into the file qux.left.txt and the +string "goodbye" into the file qux.right.txt. + +[options="header"] +|======================= +|Swift variable|Filename +|out.left|quxleft.txt +|out.right|quxright.txt +|======================= + +concurrent mapper +~~~~~~~~~~~~~~~~~ +concurrent_mapper is almost the same as the simple mapper, except that +it is used to map an output file, and the filename generated will +contain an extract sequence that is unique. This mapper is the default +mapper for variables when no mapper is specified. + + +[options="header"] +|================= +|Parameter|Meaning +|location|A directory that the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +pattern A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored. +|================= + +Example: +[java] +source~~~~ +file f1; +file f2 ; +source~~~~ + +The above example would use concurrent mapper for f1 and f2, and +generate f2 filename with prefix "foo" and extension ".txt" + + +File system mapper +~~~~~~~~~~~~~~~~~~ +filesys_mapper is similar to the simple mapper, but maps a file or a +list of files to an array. Each of the filename is mapped as an element +in the array. The order of files in the resulting array is not defined. + +TODO: note on difference between location as a relative vs absolute path +wrt staging to remote location - as mihael said: It's because you +specify that location in the mapper. Try location="." instead of +location="/sandbox/..." + +[options="header"] +|====================== +|parameter|meaning +|location|The directory where the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +|pattern|A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. +|====================== + +Example: +[java] +source~~~~ +file texts[] ; +source~~~~ + +The above example would map all filenames that start with "foo" and +have an extension ".txt" into the array texts. For example, if the +specified directory contains files: foo1.txt, footest.txt, +foo__1.txt, then the mapping might be: + +[options="header"] +|================= +|Swift variable|Filename +|texts[0]|footest.txt +|texts[1]|foo1.txt +|texts[2]|foo__1.txt +|================= + + + +fixed array mapper +~~~~~~~~~~~~~~~~~~ +The fixed_array_mapper maps from a string that contains a list of +filenames into a file array. + +[options="header"] +|================= +|parameter|Meaning +|files|A string that contains a list of filenames, separated by space, +comma or colon +|================= + +Example: + +[java] +source~~~~ +file texts[] ; +source~~~~ + +would cause a mapping like this: + +[options="header"] +|======== +|Swift variable|Filename +|texts[0]|file1.txt +|texts[1]|fileB.txt +|texts[2]|file3.txt +|======== + +array mapper +~~~~~~~~~~~~ +The array_mapper maps from an array of strings into a file + +[options="header"] +|============ +|parameter|meaning +|files|An array of strings containing one filename per element +|============== + +Example: +[java] +source~~~~ +string s[] = [ "a.txt", "b.txt", "c.txt" ]; + +file f[] ; +source~~~~ + +This will establish the mapping: + +[options="header"] +|========== +|Swift variable|Filename +|f[0]|a.txt +|f[1]|b.txt +|f[2]|c.txt +|========== + +regular expression mapper +~~~~~~~~~~~~~~~~~~~~~~~~~ +The regexp_mapper transforms one file name to another using regular +expression matching. + +[options="header"] +|========== +|parameter|meaning +|source|The source file name +|match|Regular expression pattern to match, use |()| to match whatever +regular expression is inside the parentheses, and indicate the start and +end of a group; the contents of a group can be retrieved with the +|\\number|special sequence (two backslashes are needed because the +backslash is an escape sequence introducer) +|transform|The pattern of the file name to transform to, use \number to +reference the group matched. +|========== + +Example: +[java] +source~~~~ +string s = "picture.gif"; +file f ; +source~~~~ + +This example transforms a string ending gif into one ending jpg and +maps that to a file. + +[options="header"] +|=========== +|Swift variable|Filename +|f|picture.jpg +|============= + + +csv mapper +~~~~~~~~~~ +The csv_mapper maps the content of a CSV (comma-separated value) file +into an array of structures. The dataset type needs to be correctly +defined to conform to the column names in the file. For instance, if the +file contains columns: name age GPA then the type needs to have member +elements like this: + +[java] +source~~~~ +type student { + file name; + file age; + file GPA; +} +source~~~~ + +If the file does not contain a header with column info, then the column +names are assumed as column1, column2, etc. + +[options="header"] +|============ +|Parameter|Meaning +|file|The name of the CSV file to read mappings from. +|header|Whether the file has a line describing header info; default is |true| +|skip|The number of lines to skip at the beginning (after header line); +default is 0. +|hdelim|Header field delimiter; default is the value of the |delim| parameter +|delim|Content field delimiters; defaults are space, tab and comma +|============= + +Example: +[java] +source~~~~ +student stus[] ; +source~~~~ + +The above example would read a list of student info from file +"stu_list.txt" and map them into a student array. By default, the file +should contain a header line specifying the names of the columns. If +stu_list.txt contains the following: + +[java] +source~~~~ +name,age,gpa +101-name.txt, 101-age.txt, 101-gpa.txt +name55.txt, age55.txt, age55.txt +q, r, s +source~~~~ + +then some of the mappings produced by this example would be: + +[options="header"] +|========= +|stus[0].name|101-name.txt +|stus[0].age|101-age.txt +|stus[0].gpa|101-gpa.txt +|stus[1].name|name55.txt +|stus[1].age|age55.txt +|stus[1].gpa|gpa55.txt +|stus[2].name|q +|stus[2].age|r +|stus[2].gpa|s +|========= + + + +external mapper +~~~~~~~~~~~~~~~ +The external mapper, ext maps based on the output of a supplied Unix +executable. + +[option="header"] +|============= +|parameter|meaning +|exec|The name of the executable (relative to the current directory, if +an absolute path is not specified) +|*|Other parameters are passed to the executable prefixed with a - symbol +|============== + +The output of the executable should consist of two columns of data, +separated by a space. The first column should be the path of the mapped +variable, in SwiftScript syntax (for example [2] means the 2nd element +of an array) or the symbol $ to represent the root of the mapped +variable. + +Example: With the following in mapper.sh, + +[shell] +source~~~~ +#!/bin/bash +echo "[2] qux" +echo "[0] foo" +echo "[1] bar" +source~~~~ + +then a mapping statement: + +[java] +source~~~~~ +student stus[] ; +source~~~~ + +would map + +[options="header"] +|============ +|Swift variable|Filename +|stus[0]|foo +|stus[1]|bar +|stus[2]|qux +|=========== + +Commands +-------- +The commands detailed in this section are available in the bin/ +directory of a Swift installation and can by run from the commandline if +that directory is placed on the PATH. + + +swift +~~~~~ +The swift command is the main command line tool for executing +SwiftScript programs. + + +Command-line Syntax +^^^^^^^^^^^^^^^^^^^ +The swift command is invoked as follows: swift [options] +SwiftScript-program [SwiftScript-arguments]* with options taken from the +following list, and SwiftScript-arguments made available to the +SwiftScript program through the @arg function. + +Swift command-line options + +-help or -h + + Display usage information + +-typecheck + + Does a typecheck of a SwiftScript program, instead of executing it. + +-dryrun + + Runs the SwiftScript program without submitting any jobs (can be + used to get a graph) + +-monitor + + Shows a graphical resource monitor + +-resume file + + Resumes the execution using a log file + +-config file + + Indicates the Swift configuration file to be used for this run. + Properties in this configuration file will override the default + properties. If individual command line arguments are used for + properties, they will override the contents of this file. + +-verbose | -v + + Increases the level of output that Swift produces on the console to + include more detail about the execution + +-debug | -d + + Increases the level of output that Swift produces on the console to + include lots of detail about the execution + +-logfile file + + Specifies a file where log messages should go to. By default Swift + uses the name of the program being run and a numeric index (e.g. + myworkflow.1.log) + +-runid identifier + + Specifies the run identifier. This must be unique for every + invocation and is used in several places to keep files from + different executions cleanly separated. By default, a datestamp and + random number are used to generate a run identifier. When using this + parameter, care should be taken to ensure that the run ID remains + unique with respect to all other run IDs that might be used, + irrespective of (at least) expected execution sites, program or user. + +-tui + + Displays an interactive text mode monitor during a run. (since Swift + 0.9) + +In addition, the following Swift properties can be set on the command line: + + * caching.algorithm + * clustering.enabled + * clustering.min.time + * clustering.queue.delay + * ip.address + * kickstart.always.transfer + * kickstart.enabled + * lazy.errors + * pgraph + * pgraph.graph.options + * pgraph.node.options + * sitedir.keep + * sites.file + * tc.file + * tcp.port.range + + +Return codes +^^^^^^^^^^^^ + +The swift command may exit with the following return codes: + +[options="header"] +|========= +|value|meaning +|0|success +|1|command line syntax error or missing project name +|2|error during execution +|3|error during compilation +|4|input file does not exist +|=========== + +Environment variables +^^^^^^^^^^^^^^^^^^^^^ + +The swift is influenced by the following environment variables: + +GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment +before running Swift. These can be set to inform Swift of the +configuration of your local firewall. More information can be found in +the Globus firewall How-to . + +COG_OPTS - set in the environment before running Swift. Options set in +this variable will be passed as parameters to the Java Virtual Machine +which will run Swift. The parameters vary between virtual machine +imlementations, but can usually be used to alter settings such as +maximum heap size. Typing 'java -help' will sometimes give a list of +commands. The Sun Java 1.4.2 command line options are documented here +. + + +swift-osg-ress-site-catalog +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The swift-osg-ress-site-catalog command generates a site catalog based +on OSG 's ReSS information system +(since Swift 0.9) + +Usage: *swift-osg-ress-site-catalog [options]* + +--help + + Show help message + +--vo=[name] + + Set what VO to query ReSS for + +--engage-verified + + Only retrieve sites verified by the Engagement VO site verification + tests This can not be used together with |--vo|, as the query will + only work for sites advertising support for the Engagement VO. + + This option means information will be retrieved from the Engagement + collector instead of the top-level ReSS collector. + +--out=[filename] + + Write to [filename] instead of stdout + +--condor-g + + Generates sites files which will submit jobs using a local Condor-G + installation rather than through direct GRAM2 submission. (since + Swift 0.10) + + +swift-plot-log +~~~~~~~~~~~~~~ +swift-plot-log generates summaries of Swift run log files. + +Usage: swift-plot-log [logfile] [targets] + +When no targets are specified, swift-plog-log will generate an HTML +report for the run. When targets are specified, only those named targets +will be generated. + + +Executing app procedures +------------------------ +This section describes how Swift executes app procedures, and +requirements on the behaviour of application programs used in app +procedures. These requirements are primarily to ensure that the Swift +can run your application in different places and with the various fault +tolerance mechanisms in place. + + +Mapping of app semantics into unix process execution semantics +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This section describes how an app procedure invocation is translated +into a (remote) unix process execution. It does not describe the +mechanisms by which Swift performs that translation; that is described +in the next section. + +In this section, this example SwiftScript program is used for reference: + +[java] +source~~~~~ +type file; + +app (file o) count(file i) { + wc @i stdout=@o; +} + +file q <"input.txt">; +file r <"output.txt">; +source~~~~ + +The executable for wc will be looked up in tc.data. + +This unix executable will then be executed in some application +procedure workspace. This means: + +Each application procedure workspace will have an application workspace +directory. (TODO: can collapse terms application procedure workspace +and application workspace directory ? + +This application workspace directory will not be shared with any other +application procedure execution attempt; all application procedure +execution attempts will run with distinct application procedure +workspaces. (for the avoidance of doubt: If a SwiftScript procedure +invocation is subject to multiple application procedure execution +attempts (due to Swift-level restarts, retries or replication) then each +of those application procedure execution attempts will be made in a +different application procedure workspace. ) + +The application workspace directory will be a directory on a POSIX +filesystem accessible throughout the application execution by the +application executable. + +Before the application executable is executed: + + * The application workspace directory will exist. + + * The input files will exist inside the application workspace + directory (but not necessarily as direct children; there may be + subdirectories within the application workspace directory). + + * The input files will be those files mapped to input parameters + of the application procedure invocation. (In the example, this + means that the file input.txt will exist in the application + workspace directory) + + * For each input file dataset, it will be the case that @filename + or @filenames invoked with that dataset as a parameter will + return the path relative to the application workspace directory + for the file(s) that are associated with that dataset. (In the + example, that means that @i will evaluate to the path input.txt) + + * For each file-bound parameter of the Swift procedure invocation, + the associated files (determined by data type?) will always exist. + + * The input files must be treated as read only files. This may or + may not be enforced by unix file system permissions. They may or + may not be copies of the source file (conversely, they may be + links to the actual source file). + +During/after the application executable execution, the following must +be true: + + * If the application executable execution was successful (in the + opinion of the application executable), then the application + executable should exit with unix return code 0; if the + application executable execution was unsuccessful (in the opinion + of the application executable), then the application executable + should exit with unix return code not equal to 0. + + * Each file mapped from an output parameter of the SwiftScript + procedure call must exist. Files will be mapped in the same way as + for input files. + + (? Is it defined that output subdirectories will be precreated + before execution or should app executables expect to make them? + That's probably determined by the present behaviour of wrapper.sh) + + * Output produced by running the application executable on some + inputs should be the same no matter how many times, when or where + that application executable is run. 'The same' can vary depending + on application (for example, in an application it might be + acceptable for a PNG->JPEG conversion to produce different, + similar looking, output jpegs depending on the environment) + +Things to not assume: + + * anything about the path of the application workspace directory + + * that either the application workspace directory will be deleted or + will continue to exist or will remain unmodified after execution + has finished + + * that files can be passed(?def) between application procedure + invocations through any mechanism except through files known to + Swift through the mapping mechanism (there is some exception here + for external datasets - there are a separate set of assertions + that hold for external datasets) + + * that application executables will run on any particular site of + those available, or than any combination of applications will run + on the same or different sites. + + +How Swift implements the site execution model +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +This section describes the implementation of the semantics described in +the previous section. + +Swift executes application procedures on one or more sites. + +Each site consists of: + + * worker nodes. There is some execution mechanism through which + the Swift client side executable can execute its wrapper script + on those worker nodes. This is commonly GRAM or Falkon or coasters. + + * a site-shared file system. This site shared filesystem is + accessible through some file transfer mechanism from the Swift + client side executable. This is commonly GridFTP or coasters. This + site shared filesystem is also accessible through the posix file + system on all worker nodes, mounted at the same location as seen + through the file transfer mechanism. Swift is configured with the + location of some site working directory on that site-shared file + system. + +There is no assumption that the site shared file system for one site is +accessible from another site. + +For each workflow run, on each site that is used by that run, a run +directory is created in the site working directory, by the Swift client +side. + +In that run directory are placed several subdirectories: + + * shared/ - site shared files cache + + * kickstart/ - when kickstart is used, kickstart record files for + each job that has generated a kickstart record. + + * info/ - wrapper script log files + + * status/ - job status files + + * jobs/ - application workspace directories (optionally placed + here - see below) + +Application execution looks like this: + +For each application procedure call: + +The Swift client side selects a site; copies the input files for that +procedure call to the site shared file cache if they are not already in +the cache, using the file transfer mechanism; and then invokes the +wrapper script on that site using the execution mechanism. + +The wrapper script creates the application workspace directory; places +the input files for that job into the application workspace directory +using either cp or ln -s (depending on a configuration option); +executes the application unix executable; copies output files from the +application workspace directory to the site shared directory using cp; +creates a status file under the status/ directory; and exits, +returning control to the Swift client side. Logs created during the +execution of the wrapper script are stored under the info/ directory. + +The Swift client side then checks for the presence of and deletes a +status file indicating success; and copies files from the site shared +directory to the appropriate client side location. + +The job directory is created (in the default mode) under the jobs/ +directory. However, it can be created under an arbitrary other path, +which allows it to be created on a different file system (such as a +worker node local file system in the case that the worker node has a +local file system). + +image:swift-site-model.png[] + +Technical overview of the Swift architecture +-------------------------------------------- +This section attempts to provide a technical overview of the Swift +architecture. + +Execution layer +~~~~~~~~~~~~~~~ +The execution layer causes an application program (in the form of a unix +executable) to be executed either locally or remotely. + +The two main choices are local unix execution and execution through +GRAM. Other options are available, and user provided code can also be +plugged in. + +The kickstart utility can be used to capture environmental +information at execution time to aid in debugging and provenance capture. + + +SwiftScript language compilation layer +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Step i: text to XML intermediate form parser/processor. parser written +in ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the +intermediate language is in resources/XDTM.xsd. + +Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads +the XML intermediate form. compiles to karajan workflow language - for +example, expressions are converted from SwiftScript syntax into Karajan +syntax, and function invocations become karajan function invocations +with various modifications to parameters to accomodate return parameters +and dataset handling. + + +Swift/karajan library layer +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Some Swift functionality is provided in the form of Karajan libraries +that are used at runtime by the Karajan workflows that the Swift +compiler generates. + + +Ways in which Swift can be extended +----------------------------------- +Swift is extensible in a number of ways. It is possible to add mappers +to accomodate different filesystem arrangements, site selectors to +change how Swift decides where to run each job, and job submission +interfaces to submit jobs through different mechanisms. + +A number of mappers are provided as part of the Swift release and +documented in the mappers section. New mappers can be +implemented in Java by implementing the org.griphyn.vdl.mapping.Mapper +interface. The Swift tutorial + contains a simple +example of this. + +Swift provides a default site selector, the Adaptive Scheduler. New site +selectors can be plugged in by implementing the +org.globus.cog.karajan.scheduler.Scheduler interface and modifying +libexec/scheduler.xml and etc/karajan.properties to refer to the new +scheduler. + +Execution providers and filesystem providers, which allow to Swift to +execute jobs and to stage files in and out through mechanisms such as +GRAM and GridFTP can be implemented as Java CoG kit providers. + + +Function reference +------------------ +This section details functions that are available for use in the +SwiftScript language. + + at arg +~~~~ +Takes a command line parameter name as a string parameter and an +optional default value and returns the value of that string parameter +from the command line. If no default value is specified and the command +line parameter is missing, an error is generated. If a default value is +specified and the command line parameter is missing, @arg will return +the default value. + +Command line parameters recognized by @arg begin with exactly one +hyphen and need to be positioned after the script name. + +For example: + +[java] +source~~~~ +trace(@arg("myparam")); +trace(@arg("optionalparam", "defaultvalue")); +source~~~~ + +[java] +source~~~~ +$ swift arg.swift -myparam=hello +Swift v0.3-dev r1674 (modified locally) + +RunID: 20080220-1548-ylc4pmda +SwiftScript trace: defaultvalue +SwiftScript trace: hello +source~~~~ + + at extractint +~~~~~~~~~~~ + at extractint(file) will read the specified file, parse an integer from +the file contents and return that integer. + + + at filename +~~~~~~~~~ + at filename(v) will return a string containing the filename(s) for the +file(s) mapped to the variable v. When more than one filename is +returned, the filenames will be space separated inside a single string +return value. + + + at filenames +~~~~~~~~~~ + at filenames(v) will return multiple values (!) containing the +filename(s) for the file(s) mapped to the variable v. (compare to + at filename) + + at regexp +~~~~~~~ + at regexp(input,pattern,replacement) will apply regular expression +substitution using the Java java.util.regexp API +. +For example: + +[java] +source~~~~ +string v = @regexp("abcdefghi", "c(def)g","monkey"); +source~~~~ + +will assign the value "abmonkeyhi" to the variable v. + + at strcat +~~~~~~~ + at strcat(a,b,c,d,...) will return a string containing all of the +strings passed as parameters joined into a single string. There may be +any number of parameters. + +The + operator concatenates two strings: @strcat(a,b) is the same as +a + b + + at strcut +~~~~~~~ + at strcut(input,pattern) will match the regular expression in the +pattern parameter against the supplied input string and return the +section that matches the first matching parenthesised group. + +For example: +[java] +source~~~~ +string t = "my name is John and i like puppies."; +string name = @strcut(t, "my name is ([^ ]*) "); +string out = @strcat("Your name is ",name); +trace(out); +source~~~~ + +will output the message: Your name is John. + + at strsplit +~~~~~~~~~ + at strsplit(input,pattern) will split the input string based on +separators that match the given pattern and return a string array. +(since Swift 0.9) + +Example: +[java] +source~~~~ +string t = "my name is John and i like puppies."; +string words[] = @strsplit(t, "\\s"); +foreach word in words { + trace(word); +} +source~~~~ + +will output one word of the sentence on each line (though not +necessarily in order, due to the fact that foreach iterations execute in +parallel). + + + at toint +~~~~~~ + at toint(input) will parse its input string into an integer. This can be +used with @arg to pass input parameters to a SwiftScript program as +integers. + + +Built-in procedure reference +---------------------------- +This section details built-in procedures that are available for use in +the SwiftScript language. + +readData +~~~~~~~~ +readData will read data from a specified file. + +The format of the input file is controlled by the type of the return value. + +For scalar return types, such as int, the specified file should contain +a single value of that type. + +For arrays of scalars, the specified file should contain one value per +line. + +For structs of scalars, the file should contain two rows. The first row +should be structure member names separated by whitespace. The second row +should be the corresponding values for each structure member, separated +by whitespace, in the same order as the header row. + +For arrays of structs, the file should contain a heading row listing +structure member names separated by whitespace. There should be one row +for each element of the array, with structure member elements listed in +the same order as the header row and separated by whitespace. (since +Swift 0.4) + +readdata2 +~~~~~~~~~ +readdata2 will read data from a specified file, like readdata, but +using a different file format more closely related to that used by the +ext mapper. + +Input files should list, one per line, a path into a Swift structure, +and the value for that position in the structure: + +[java] +source~~~~ +rows[0].columns[0] = 0 +rows[0].columns[1] = 2 +rows[0].columns[2] = 4 +rows[1].columns[0] = 1 +rows[1].columns[1] = 3 +rows[1].columns[2] = 5 +source~~~~ + +which can be read into a structure defined like this: + +[java] +source~~~~ +type vector { + int columns[]; +} + +type matrix { + vector rows[]; +} + +matrix m; + +m = readData2("readData2.in"); +source~~~~ + +(since Swift 0.7) + +trace +~~~~~ +trace will log its parameters. By default these will appear on both +stdout and in the run log file. Some formatting occurs to produce the +log message. The particular output format should not be relied upon. +(since Swift 0.4) + +writeData +~~~~~~~~~ +writeData will write out data structures in the format described for +readData + +Swift configuration properties +------------------------------ +Various aspects of the behavior of the Swift Engine can be configured +through properties. The Swift Engine recognizes a global, per +installation properties file which can found in etc/swift.properties +in the Swift installation directory and a user properties file which can +be created by each user in ~/.swift/swift.properties. The Swift Engine +will first load the global properties file. It will then try to load the +user properties file. If a user properties file is found, individual +properties explicitly set in that file will override the respective +properties in the global properties file. Furthermore, some of the +properties can be overridden directly using command line arguments to +the *swift* command. + +Swift properties are specified in the following format: + += + +The value can contain variables which will be expanded when the +properties file is read. Expansion is performed when the name of the +variable is used inside the standard shell dereference construct: +${name}. The following variables can be used in the Swift +configuration file: + +Swift Configuration Variables + +swift.home + + Points to the Swift installation directory ($SWIFT_HOME). In + general, this should not be set as Swift can find its own + installation directory, and incorrectly setting it may impair the + correct functionality of Swift. + +user.name + + The name of the current logged in user. + +user.home + + The user's home directory. + +The following is a list of valid Swift properties: + +Swift Properties + +caching.algorithm + + Valid values: LRU + + Default value: LRU + + Swift caches files that are staged in on remote resources, and files + that are produced remotely by applications, such that they can be + re-used if needed without being transfered again. However, the + amount of remote file system space to be used for caching can be + limited using the swift:storagesize profile entry in the sites.xml file. Example: + +[xml] +source~~~~ + + + +/scratch/swift +20000000 + +source~~~~ + + The decision of which files to keep in the cache and which files to + remove is made considering the value of the caching.algorithm + property. Currently, the only available value for this property is + LRU, which would cause the least recently used files to be deleted + first. + +clustering.enabled + + Valid values: true, false + + Default value: false + + Enables clustering. + +clustering.min.time + + Valid values: + + Default value: 60 + + Indicates the threshold wall time for clustering, in seconds. Jobs + that have a wall time smaller than the value of this property will + be considered for clustering. + +clustering.queue.delay + + Valid values: + + Default value: 4 + + This property indicates the interval, in seconds, at which the + clustering queue is processed. + +execution.retries + + Valid values: positive integers + + Default value: 2 + + The number of time a job will be retried if it fails (giving a + maximum of 1 + execution.retries attempts at execution) + +foreach.max.threads + + Valid values: positive integers + + Default value: 1024 + + Limits the number of concurrent iterations that each foreach + statement can have at one time. This conserves memory for swift + programs that have large numbers of iterations (which would + otherwise all be executed in parallel). (since Swift 0.9) + +ip.address + + Valid values: + + Default value: N/A + + The Globus GRAM service uses a callback mechanism to send + notifications about the status of submitted jobs. The callback + mechanism requires that the Swift client be reachable from the hosts + the GRAM services are running on. Normally, Swift can detect the + correct IP address of the client machine. However, in certain cases + (such as the client machine having more than one network interface) + the automatic detection mechanism is not reliable. In such cases, + the IP address of the Swift client machine can be specified using + this property. The value of this property must be a numeric address + without quotes. + + This option is deprecated and the hostname property should be used + instead. + +kickstart.always.transfer + + Valid values: true, false + + Default value: false + + This property controls when output from Kickstart is transfered back + to the submit site, if Kickstart is enabled. When set to false, + Kickstart output is only transfered for jobs that fail. If set to + true, Kickstart output is transfered after every job is completed + or failed. + +kickstart.enabled + + Valid values: true, false, maybe + + Default value: maybe + + This option allows controlling of when Swift uses Kickstart. + A value of false disables the use of Kickstart, + while a value of true enables the use of Kickstart, in which case + sites specified in the sites.xml file must have valid + gridlaunch attributes. The maybe value will enable the use of + Kickstart only on sites that have the gridlaunch attribute + specified. + +lazy.errors + + Valid values: true, false + + Default value: false + + Swift can report application errors in two modes, depending on the + value of this property. If set to false, Swift will report the + first error encountered and immediately stop execution. If set to + true, Swift will attempt to run as much as possible from a + SwiftScript program before stopping execution and reporting all + errors encountered. + + When developing SwiftScript programs, using the default value of + false can make the program easier to debug. However in production + runs, using true will allow more of a SwiftScript program to be + run before Swift aborts execution. + +pgraph + + Valid values: true, false, + + Default value: false + + Swift can generate a Graphviz file + representing the structure of the SwiftScript program it has run. If + this property is set to true, Swift will save the provenance graph + in a file named by concatenating the program name and the instance + ID (e.g. helloworld-ht0adgi315l61.dot). + + If set to false, no provenance graph will be generated. If a file + name is used, then the provenance graph will be saved in the + specified file. + + The generated dot file can be rendered into a graphical form using + Graphviz , for example with a command-line + such as: + +[shell] +source~~~~ +$ swift -pgraph graph1.dot q1.swift +$ dot -ograph.png -Tpng graph1.dot +source~~~~ + +pgraph.graph.options + + Valid values: + + Default value: splines="compound", rankdir="TB" + + This property specifies a Graphviz + specific set of parameters for the graph. + +pgraph.node.options + + Valid values: + + Default value: color="seagreen", style="filled" + + Used to specify a set of Graphviz specific + properties for the nodes in the graph. + +provenance.log + + Valid values: true, false + + Default value: false + + This property controls whether the log file will contain provenance + information enabling this will increase the size of log files, + sometimes significantly. + +replication.enabled + + Valid values: true, false + + Default value: false + + Enables/disables replication. Replication is used to deal with jobs + sitting in batch queues for abnormally large amounts of time. If + replication is enabled and certain conditions are met, Swift creates + and submits replicas of jobs, and allows multiple instances of a job + to compete. + +replication.limit + + Valid values: positive integers + + Default value: 3 + + The maximum number of replicas that Swift should attempt. + +sitedir.keep + + Valid values: true, false + + Default value: false + + Indicates whether the working directory on the remote site should be + left intact even when a run completes successfully. This can be used + to inspect the site working directory for debugging purposes. + +sites.file + + Valid values: + + Default value: ${swift.home}/etc/sites.xml + + Points to the location of the site catalog, which contains a list of + all sites that Swift should use. + +status.mode + + Valid values: files, provider + + Default value: files + + Controls how Swift will communicate the result code of running user + programs from workers to the submit side. In files mode, a file + indicating success or failure will be created on the site shared + filesystem. In provider mode, the execution provider job status + will be used. + + provider mode requires the underlying job execution system to + correctly return exit codes. In at least the cases of GRAM2, and + clusters used with any provider, exit codes are not returned, and so + files mode must be used in those cases. Otherwise, provider mode + can be used to reduce the amount of filesystem access. (since Swift + 0.8) + +tc.file + + Valid values: + + Default value: ${swift.home}/etc/tc.data + + Points to the location of the transformation catalog file which + contains information about installed applications. Details about the + format of the transformation catalog can be found here + . + + +tcp.port.range + + Valid values: , where start and end are integers + + Default value: none + + A TCP port range can be specified to restrict the ports on which + GRAM callback services are started. This is likely needed if your + submit host is behind a firewall, in which case the firewall should + be configured to allow incoming connections on ports in the range. + +throttle.file.operations + + Valid values: , off + + Default value: 8 + + Limits the total number of concurrent file operations that can + happen at any given time. File operations (like transfers) require + an exclusive connection to a site. These connections can be + expensive to establish. A large number of concurrent file operations + may cause Swift to attempt to establish many such expensive + connections to various sites. Limiting the number of concurrent file + operations causes Swift to use a small number of cached connections + and achieve better overall performance. + +throttle.host.submit + + Valid values: , off + + Default value: 2 + + Limits the number of concurrent submissions for any of the sites + Swift will try to send jobs to. In other words it guarantees that no + more than the value of this throttle jobs sent to any site will be + concurrently in a state of being submitted. + +throttle.score.job.factor + + Valid values: , off + + Default value: 4 + + The Swift scheduler has the ability to limit the number of + concurrent jobs allowed on a site based on the performance history + of that site. Each site is assigned a score (initially 1), which can + increase or decrease based on whether the site yields successful or + faulty job runs. The score for a site can take values in the (0.1, + 100) interval. The number of allowed jobs is calculated using the + following formula: + + 2 + score*throttle.score.job.factor + + This means a site will always be allowed at least two concurrent + jobs and at most 2 + 100*throttle.score.job.factor. With a default + of 4 this means at least 2 jobs and at most 402. + + This parameter can also be set per site using the jobThrottle + profile key in a site catalog entry. + +throttle.submit + + Valid values: , off + + Default value: 4 + + Limits the number of concurrent submissions for a run. This throttle + only limits the number of concurrent tasks (jobs) that are being + sent to sites, not the total number of concurrent jobs that can be + run. The submission stage in GRAM is one of the most CPU expensive + stages (due mostly to the mutual authentication and delegation). + Having too many concurrent submissions can overload either or both + the submit host CPU and the remote host/head node causing degraded + performance. + +throttle.transfers + + Valid values: , off + + Default value: 4 + + Limits the total number of concurrent file transfers that can happen + at any given time. File transfers consume bandwidth. Too many + concurrent transfers can cause the network to be overloaded + preventing various other signaling traffic from flowing properly. + +ticker.disable + + Valid values: true, false + + Default value: false + + When set to true, suppresses the output progress ticker that Swift + sends to the console every few seconds during a run (since Swift 0.9) + +wrapper.invocation.mode + + Valid values: absolute, relative + + Default value: absolute + + Determines if Swift remote wrappers will be executed by specifying + an absolute path, or a path relative to the job initial working + directory. In most cases, execution will be successful with either + option. However, some execution sites ignore the specified initial + working directory, and so absolute must be used. Conversely on + some sites, job directories appear in a different place on the + worker node file system than on the filesystem access node, with the + execution system handling translation of the job initial working + directory. In such cases, relative mode must be used. (since Swift + 0.9) + +wrapper.parameter.mode + + Controls how Swift will supply parameters to the remote wrapper + script. args mode will pass parameters on the command line. Some + execution systems do not pass commandline parameters sufficiently + cleanly for Swift to operate correctly. files mode will pass + parameters through an additional input file (since Swift 0.95). This + provides a cleaner communication channel for parameters, at the + expense of transferring an additional file for each job invocation. + +wrapperlog.always.transfer + + Valid values: true, false + + Default value: false + + This property controls when output from the Swift remote wrapper is + transfered back to the submit site. When set to false, wrapper + logs are only transfered for jobs that fail. If set to true, + wrapper logs are transfered after every job is completed or failed. + +Example: + +[source,xml] +sites.file=${vds.home}/etc/sites.xml +tc.file=${vds.home}/etc/tc.data +ip.address=192.168.0.1 + +Profiles +-------- +Profiles are configuration parameters than can be specified either for +sites or for transformation catalog entries. They influence the +behaviour of Swift towards that site (for example, by changing the load +Swift will place on that sites) or when running a particular procedure. + +Profile entries for a site are specified in the site catalog. Profile +entries for specific procedures are specified in the transformation +catalog. + + +Karajan namespace +~~~~~~~~~~~~~~~~~ +maxSubmitRate limits the maximum rate of job submission, in jobs per +second. For example: + +[source,xml] +0.2 + +will limit job submission to 0.2 jobs per second (or equivalently, one +job every five seconds). + +jobThrottle allows the job throttle factor (see Swift property +throttle.score.job.factor to be +set per site. + +initialScore allows the initial score for rate limiting and site +selection to be set to a value other than 0. + +delayBase controls how much a site will be delayed when it performs +poorly. With each reduction in a sites score by 1, the delay between +execution attempts will increase by a factor of delayBase. + +status.mode allows the status.mode property to be set per-site instead +of for an entire run. See the Swift configuration properties section for +more information. (since Swift 0.8) + +swift namespace +~~~~~~~~~~~~~~~ +storagesize limits the amount of space that will be used on the remote +site for temporary files. When more than that amount of space is used, +the remote temporary file cache will be cleared using the algorithm +specified in the caching.algorithm property. + +wrapperInterpreter - The wrapper interpreter indicates the command +(executable) to be used to run the Swift wrapper script. The default is +"/bin/bash" on Unix sites and "cscript.exe" on Windows sites. + +wrapperInterpreterOptions - Allows specifying additional options to the +executable used to run the Swift wrapper. The defaults are no options on +Unix sites and "Nologo" on Windows sites. + +wrapperScript - Specifies the name of the wrapper script to be used on a +site. The defaults are "_swiftwrap" on Unix sites and "_swiftwrap.vbs" +on Windows sites. If you specify a custom wrapper script, it must be +present in the "libexec" directory of the Swift installation. + +cleanupCommand Indicates the command to be run at the end of a Swift +run to clean up the run directories on a remote site. Defaults are +"/bin/rm" on Unix sites and "cmd.exe" on Windows sites + +cleanupCommandOptions Specifies the options to be passed to the +cleanup command above. The options are passed in the argument list to +the cleanup command. After the options, the last argument is the +directory to be deleted. The default on Unix sites is "-rf". The default +on Windows sites is ["/C", "del", "/Q"]. + + +Globus namespace +~~~~~~~~~~~~~~~~ +maxwalltime specifies a walltime limit for each job, in minutes. + +The following formats are recognized: + + * Minutes + * Hours:Minutes + * Hours:Minutes:Seconds + +Example: +[source,java] +localhost echo /bin/echo INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:20:00" + +When replication is enabled (see replication), then +walltime will also be enforced at the Swift client side: when a job has +been active for more than twice the maxwalltime, Swift will kill the job +and regard it as failed. + +When clustering is used, maxwalltime will be used to select which jobs +will be clustered together. More information on this is available in the +clustering section. + +When coasters as used, maxwalltime influences the default coaster +worker maxwalltime, and which jobs will be sent to which workers. More +information on this is available in the coasters section. + +queue is used by the PBS, GRAM2 and GRAM4 providers. This profile +entry specifies which queue jobs will be submitted to. The valid queue +names are site-specific. + +host_types specifies the types of host that are permissible for a job +to run on. The valid values are site-specific. This profile entry is +used by the GRAM2 and GRAM4 providers. + +condor_requirements allows a requirements string to be specified when +Condor is used as an LRM behind GRAM2. Example: + +[source,xml] +Arch == "X86_64" || Arch="INTEL" + +slots When using coasters, this parameter specifies the +maximum number of jobs/blocks that the coaster scheduler will have +running at any given time. The default is 20. + +workersPerNode - This parameter determines how many coaster workers are +started one each compute node. The default value is 1. + +nodeGranularity - When allocating a coaster worker block, this parameter +restricts the number of nodes in a block to a multiple of this value. +The total number of workers will then be a multiple of workersPerNode * +nodeGranularity. The default value is 1. + +allocationStepSize - Each time the coaster block scheduler computes a +schedule, it will attempt to allocate a number of slots from the number +of available slots (limited using the above slots profile). This +parameter specifies the maximum fraction of slots that are allocated in +one schedule. Default is 0.1. + +lowOverallocation - Overallocation is a function of the walltime of a +job which determines how long (time-wise) a worker job will be. For +example, if a number of 10s jobs are submitted to the coaster service, +and the overallocation for 10s jobs is 10, the coaster scheduler will +attempt to start worker jobs that have a walltime of 100s. The +overallocation is controlled by manipulating the end-points of an +overallocation function. The low endpoint, specified by this parameter, +is the overallocation for a 1s job. The high endpoint is the +overallocation for a (theoretical) job of infinite length. The +overallocation for job sizes in the [1s, +inf) interval is determined +using an exponential decay function: overallocation(walltime) = walltime +* (lowOverallocation - highOverallocation) * exp(-walltime * +overallocationDecayFactor) + highOverallocation The default value of +lowOverallocation is 10. + +highOverallocation - The high overallocation endpoint (as described +above). Default: 1 + +overallocationDecayFactor - The decay factor for the overallocation +curve. Default 0.001 (1e-3). + +spread - When a large number of jobs is submitted to the a coaster +service, the work is divided into blocks. This parameter allows a rough +control of the relative sizes of those blocks. A value of 0 indicates +that all work should be divided equally between the blocks (and blocks +will therefore have equal sizes). A value of 1 indicates the largest +possible spread. The existence of the spread parameter is based on the +assumption that smaller overall jobs will generally spend less time in +the queue than larger jobs. By submitting blocks of different sizes, +submitted jobs may be finished quicker by smaller blocks. Default: 0.9. + +reserve - Reserve time is a time in the allocation of a worker that sits +at the end of the worker time and is useable only for critical +operations. For example, a job will not be submitted to a worker if it +overlaps its reserve time, but a job that (due to inaccurate walltime +specification) runs into the reserve time will not be killed (note that +once the worker exceeds its walltime, the queuing system will kill the +job anyway). Default 10 (s). + +maxnodes - Determines the maximum number of nodes that can be allocated +in one coaster block. Default: unlimited. + +maxtime - Indicates the maximum walltime that a coaster block can have. +Default: unlimited. + +remoteMonitorEnabled - If set to "true", the client side will get a +Swing window showing, graphically, the state of the coaster scheduler +(blocks, jobs, etc.). Default: false + +env namespace +~~~~~~~~~~~~~ +Profile keys set in the env namespace will be set in the unix +environment of the executed job. Some environment variables influence +the worker-side behaviour of Swift: + +PATHPREFIX - set in env namespace profiles. This path is prefixed onto +the start of the PATH when jobs are executed. It can be more useful +than setting the PATH environment variable directly, because setting +PATH will cause the execution site's default path to be lost. + +SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift +will use the path specified here as a worker-node local temporary +directory to copy input files to before running a job. If unset, Swift +will keep input files on the site-shared filesystem. In some cases, +copying to a worker-node local directory can be much faster than having +applications access the site-shared filesystem directly. + +SWIFT_EXTRA_INFO - set in env namespace profiles. If set, then Swift +will execute the command specified in SWIFT_EXTRA_INFO on execution +sites immediately before each application execution, and will record the +stdout of that command in the wrapper info log file for that job. This +is intended to allow software version and other arbitrary information +about the remote site to be gathered and returned to the submit side. +(since Swift 0.9) + +The Site Catalog - sites.xml +---------------------------- +The site catalog lists details of each site that Swift can use. The +default file contains one entry for local execution, and a large number +of commented-out example entries for other sites. + +By default, the site catalog is stored in etc/sites.xml. This path can +be overridden with the sites.file configuration property, either in +the Swift configuration file or on the command line. + +The sites file is formatted as XML. It consists of elements, +one for each site that Swift will use. + + +Pool element +~~~~~~~~~~~~ +Each pool element must have a handle attribute, giving a symbolic +name for the site. This can be any name, but must correspond to entries +for that site in the transformation catalog. + +Optionally, the gridlaunch attribute can be used to specify the path +to kickstart on the site. + +Each pool must specify a file transfer method, an execution method and +a remote working directory. Optionally, profile settings can +be specified. + + +File transfer method +~~~~~~~~~~~~~~~~~~~~ +Transfer methods are specified with either the element or +the element. + +To use gridftp or local filesystem copy, use the element: + +[source,xml] + + +The url attribute may specify a GridFTP server, using the gsiftp URI +scheme; or it may specify that filesystem copying will be used (which +assumes that the site has access to the same filesystem as the +submitting machine) using the URI local://localhost. + +Filesystem access using scp (the SSH copy protocol) can be specified +using the element: + +[source,xml] + + +For additional ssh configuration information, see the ssh execution +provider documentation below. + +Filesystem access using CoG coasters can be also be +specified using the element. More detail about +configuring that can be found in the CoG coasters section. + +Execution method +~~~~~~~~~~~~~~~~ +Execution methods may be specified either with the or + element. + +The element can be used to specify execution through +GRAM2. For example, + +[source,xml] + + +The universe attribute should always be set to vanilla. The url +attribute should specify the name of the GRAM2 gatekeeper host, and the +name of the jobmanager to use. The major attribute should always be set +to 2. + +The element can be used to specify execution through other +execution providers: + +To use GRAM4, specify the gt4 provider. For example: + +[source,xml] + + +The url attribute should specify the GRAM4 submission site. The +jobmanager attribute should specify which GRAM4 jobmanager will be used. + +For local execution, the local provider should be used, like this: + +[source,xml] + + +For PBS execution, the pbs provider should be used: + +[source,xml] + + +The GLOBUS::queue profile key can be used to +specify which PBS queue jobs will be submitted to. + +For execution through a local Condor installation, the condor provider +should be used. This provider can run jobs either in the default vanilla +universe, or can use Condor-G to run jobs on remote sites. + +When running locally, only the element needs to be specified: + +[source,xml] + + +When running with Condor-G, it is necessary to specify the Condor grid +universe and the contact string for the remote site. For example: + +[source,xml] + + grid + gt2 belhaven-1.renci.org/jobmanager-fork + +For execution through SSH, the ssh provider should be used: + +[source,xml] + + +with configuration made in ~/.ssh/auth.defaults with the string +'www11.i2u2.org' changed to the appropriate host name: + +[source,shell] +www11.i2u2.org.type=key +www11.i2u2.org.username=hategan +www11.i2u2.org.key=/home/mike/.ssh/i2u2portal +www11.i2u2.org.passphrase=XXXX + +For execution using the CoG Coaster mechanism, the coaster +provider should be used: + +[source,xml] + + +More details about configuration of coasters can be found in the section +on coasters. + +Work directory +~~~~~~~~~~~~~~ +The workdirectory element specifies where on the site files can be +stored. + +[source,xml] +/home/benc + +This file must be accessible through the transfer mechanism specified in +the element and also mounted on all worker nodes that will +be used for execution. A shared cluster scratch filesystem is +appropriate for this. + +Profiles +~~~~~~~~ +Profile keys can be specified using the element. +For example: + +[source,xml] +fast + +The site catalog format is an evolution of the VDS site catalog format +which is documented here +. + + +The Transformation Catalog - tc.data +------------------------------------ +The transformation catalog lists where application executables are +located on remote sites. + +By default, the site catalog is stored in etc/tc.data. This path can +be overridden with the tc.file configuration property, either in the +Swift configuration file or on the command line. + +The format is one line per executable per site, with fields separated by +tabs. Spaces cannot be used to separate fields. + +Some example entries: +[source,shell] +localhost echo /bin/echo INSTALLED INTEL32::LINUX null +TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1" + +The fields are: site, transformation name, executable path, installation +status, platform, and profile entrys. + +The site field should correspond to a site name listed in the sites catalog. + +The transformation name should correspond to the transformation name +used in a SwiftScript app procedure. + +The executable path should specify where the particular executable is +located on that site. + +The installation status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively. + +The profiles field should be set to null if no profile entries are to +be specified, or should contain the profile entries separated by +semicolons. + +Build options +------------- +See the Swift download page + for instructions on +downloading and building Swift from source. When building, various build +options can be supplied on the ant commandline. These are summarised here: + +with-provider-condor - build with CoG condor provider + +with-provider-coaster - build with CoG coaster provider (see the +section on coasters). Since 0.8, coasters are always built, +and this option has no effect. + +with-provider-deef - build with Falkon provider deef. In order for +this option to work, it is necessary to check out the provider-deef code +in the cog/modules directory alongside swift: + +[source,shell] +$ cd cog/modules +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef +$ cd ../swift +$ ant -Dwith-provider-deef=true redist + +with-provider-wonky - build with provider-wonky, an execution provider +that provides delays and unreliability for the purposes of testing +Swift's fault tolerance mechanisms. In order for this option to work, it +is necessary to check out the provider-wonky code in the |cog/modules| +directory alongside swift: + +[source,shell] +$ cd cog/modules +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky +$ cd ../swift|* +$ ant -Dwith-provider-wonky=true redist + +no-supporting - produces a distribution without supporting commands +such as grid-proxy-init. This is intended for when the Swift +distribution will be used in an environment where those commands are +already provided by other packages, where the Swift package should be +providing only Swift commands, and where the presence of commands such +as grid-proxy-init from the Swift distribution in the path will mask the +presence of those commands from their true distribution package such as +a Globus Toolkit package. + +[source,shell] +$ ant -Dno-supporting=true redist + +Kickstart +--------- +Kickstart is a tool that can be used to gather various information about +the remote execution environment for each job that Swift tries to run. + +For each job, Kickstart generates an XML invocation record. By default +this record is staged back to the submit host if the job fails. + +Before it can be used it must be installed on the remote site and the +sites file must be configured to point to kickstart. + +Kickstart can be downloaded as part of the Pegasus 'worker package' +available from the worker packages section of the Pegasus download page +. + +Untar the relevant worker package somewhere where it is visible to all +of the worker nodes on the remote execution machine (such as in a shared +application filesystem). + +Now configure the gridlaunch attribute of the sites catalog to point to +that path, by adding a gridlaunch attribute to the pool element in +the site catalog: + +[source,xml] + +... + + +There are various kickstat.* properties, which have sensible default +values. These are documented in the properties section. + +Reliability mechanisms +---------------------- +This section details reliabilty mechanisms in Swift: retries, restarts +and replication. + +Retries +~~~~~~~ +If an application procedure execution fails, Swift will attempt that +execution again repeatedly until it succeeds, up until the limit defined +in the execution.retries configuration property. + +Site selection will occur for retried jobs in the same way that it +happens for new jobs. Retried jobs may run on the same site or may run +on a different site. + +If the retry limit execution.retries is reached for an application +procedure, then that application procedure will fail. This will cause +the entire run to fail - either immediately (if the lazy.errors +property is false) or after all other possible work has been attempted +(if the lazy.errors property is true). + +Restarts +~~~~~~~~ +If a run fails, Swift can resume the program from the point of failure. +When a run fails, a restart log file will be left behind in a file named +using the unique job ID and a .rlog extension. This restart log can +then be passed to a subsequent Swift invocation using the -resume +parameter. Swift will resume execution, avoiding execution of +invocations that have previously completed successfully. The SwiftScript +source file and input data files should not be modified between runs. + +Every run creates a restart log file with a named composed of the file +name of the workflow being executed, an invocation ID, a numeric ID, and +the .rlog extension. For example, example.swift, when executed, +could produce the following restart log file: +example-ht0adgi315l61.0.rlog. Normally, if the run completes +successfully, the restart log file is deleted. If however the workflow +fails, swift can use the restart log file to continue execution from a +point before the failure occurred. In order to restart from a restart +log file, the -resume logfile argument can be used after the +SwiftScript program file name. Example: + +[source,shell] +$ swift -resume example-ht0adgi315l61.0.rlog example.swift. + +Replication +~~~~~~~~~~~ +When an execution job has been waiting in a site queue for a certain +period of time, Swift can resubmit replicas of that job (up to the limit +defined in the replication.limit configuration property). When any of +those jobs moves from queued to active state, all of the other replicas +will be cancelled. + +This is intended to deal with situations where some sites have a +substantially longer (sometimes effectively infinite) queue time than +other sites. Selecting those slower sites can cause a very large delay +in overall run time. + +Replication can be enabled by setting the replication.enabled +configuration property to true. The maximum number of replicas that +will be submitted for a job is controlled by the replication.limit +configuration property. + +When replication is enabled, Swift will also enforce the maxwalltime +profile setting for jobs as documented in the profiles section. + +Clustering +---------- +Swift can group a number of short job submissions into a single larger +job submission to minimize overhead involved in launching jobs (for +example, caused by security negotiation and queuing delay). In general, +CoG coasters should be used in preference to the clustering +mechanism documented in this section. + +By default, clustering is disabled. It can be activated by setting the +clustering.enabled property to true. + +A job is eligible for clustering if the GLOBUS::maxwalltime profile +is specified in the tc.data entry for that job, and its value is +less than the value of the clustering.min.time property. + +Two or more jobs are considered compatible if they share the same site +and do not have conflicting profiles (e.g. different values for the same +environment variable). + +When a submitted job is eligible for clustering, it will be put in a +clustering queue rather than being submitted to a remote site. The +clustering queue is processed at intervals specified by the +clustering.queue.delay property. The +processing of the clustering queue consists of selecting compatible jobs +and grouping them into clusters whose maximum wall time does not exceed +twice the value of the clustering.min.time property. + +Coasters +-------- +Coasters were introduced in Swift v0.6 as an experimental feature. + +In many applications, Swift performance can be greatly enhanced by the +use of CoG coasters. CoG coasters provide a low-overhead job submission +and file transfer mechanism suited for the execution of short jobs (on +the order of a few seconds) and the transfer of small files (on the +order of a few kilobytes) for which other grid protocols such as GRAM +and GridFTP are poorly suited. + +The coaster mechanism submits a head job using some other execution +mechanism such as GRAM, and for each worker node that will be used in a +remote cluster, it submits a worker job, again using some other +execution mechanism such as GRAM. Details on the design of the coaster +mechanism can be found here. + +The head job manages file transfers and the dispatch of execution jobs +to workers. Much of the overhead associated with other grid protocols +(such as authentication and authorization, and allocation of worker +nodes by the site's local resource manager) is reduced, because that +overhead is associated with the allocation of a coaster head or coaster +worker, rather than with every Swift-level procedure invocation; +potentially hundreds or thousands of Swift-level procedure invocations +can be run through a single worker. + +Coasters can be configured for use in two situations: job execution and +file transfer. + +To use for job execution, specify a sites.xml execution element like this: + +[source,xml] + + +The jobmanager string contains more detail than with other providers. It +contains either two or three colon separated fields: 1:the provider to +be use to execute the coaster head job - this provider will submit from +the Swift client side environment. Commonly this will be one of the GRAM +providers; 2: the provider to be used to execute coaster worker jobs. +This provider will be used to submit from the coaster head job +environment, so a local scheduler provider can sometimes be used instead +of GRAM. 3: optionally, the jobmanager to be used when submitting worker +job using the provider specified in field 2. + +To use for file transfer, specify a sites.xml filesystem element like this: + +[source,xml] + + +The url parameter should be a pseudo-URI formed with the URI scheme +being the name of the provider to use to submit the coaster head job, +and the hostname portion being the hostname to be used to execute the +coaster head job. Note that this provider and hostname will be used for +execution of a coaster head job, not for file transfer; so for example, +a GRAM endpoint should be specified here rather than a GridFTP endpoint. + +Coasters are affected by the following profile settings, which are +documented in the Globus namespace profile section: + +[options="header"] +|================= +|Profile key|Brief description +|slots|How many maximum LRM jobs/worker blocks are allowed +|workersPerNode|How many coaster workers to run per execution node +|nodeGranularity|Each worker block uses a number of nodes that is a +multiple of this number +|lowOverallocation|How many times larger than the job walltime should a +block's walltime be if all jobs are 1s long +|highOverallocation|How many times larger than the job walltime should a +block's walltime be if all jobs are infinitely long +|overallocationDecayFactor|How quickly should the overallocation curve +tend towards the highOverallocation as job walltimes get larger +|spread|By how much should worker blocks vary in worker size +|workersPerNode|How many coaster workers to run per execution node +|reserve|How many seconds to reserve in a block's walltime for +starting/shutdown operations +|maxnodes|The maximum number of nodes allowed in a block +|maxtime|The maximum number of walltime allowed for a block +|remoteMonitorEnabled|If true, show a graphical display of the status of +the coaster service +|================== + +How-To Tips for Specific User Communities +----------------------------------------- + +Saving Logs - for UChicago CI Users +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +If you have a UChicago Computation Institute account, run this command +in your submit directory after each run. It will copy all your logs and +kickstart records into a directory at the CI for reporting, usage +tracking, support and debugging. + +[source,shell] +rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose + +Specifying TeraGrid allocations +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +TeraGrid users with no default project or with several project +allocations can specify a project allocation using a profile key in the +site catalog entry for a TeraGrid site: + +[source,xml] +TG-CCR080002N + +More information on the TeraGrid allocations process can be found here +. + +Launching MPI jobs from Swift +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Here is an example of running a simple MPI program. + +In SwiftScript, we make an invocation that does not look any different +from any other invocation. In the below code, we do not have any input +files, and have two output files on stdout and stderr: + +[java] +source~~~~ +type file; + +(file o, file e) p() { + app { + mpi stdout=@filename(o) stderr=@filename(e); + } +} + +file mpiout <"mpi.out">; +file mpierr <"mpi.err">; + +(mpiout, mpierr) = p(); +source~~~~ + +Now we define how 'mpi' will run in tc.data: +[source,shell] +tguc mpi /home/benc/mpi/mpi.sh INSTALLED INTEL32::LINUX GLOBUS::host_xcount=3 + +mpi.sh is a wrapper script that launches the MPI program. It must be +installed on the remote site: + +[source,shell] +#!/bin/bash +mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out + +Because of the way that Swift runs its server side code, +provider-specific MPI modes (such as GRAM jobType=mpi) should not be +used. Instead, the mpirun command should be explicitly invoked. + +Running on Windows +~~~~~~~~~~~~~~~~~~ +Since 10/11/09, the development version of Swift has the ability to run +on a Windows machine, as well as the ability to submit jobs to a Windows +site (provided that an appropriate provider is used). + +In order to launch Swift on Windows, use the provided batch file +(swift.bat). In certain cases, when a large number of jar libraries are +present in the Swift lib directory and depending on the exact location +of the Swift installation, the classpath environment variable that the +Swift batch launcher tries to create may be larger than what Windows can +handle. In such a case, either install Swift in a directory closer to +the root of the disk (say, c:\swift) or remove non-essential jar files +from the Swift lib directory. + +Due to the large differences between Windows and Unix environments, +Swift must use environment specific tools to achieve some of its goals. +In particular, each Swift executable is launched using a wrapper script. +This script is a Bourne Shell script. On Windows machines, which have no +Bourne Shell interpreter installed by default, the Windows Scripting +Host is used instead, and the wrapper script is written in VBScript. +Similarly, when cleaning up after a run, the "/bin/rm" command available +in typical Unix environments must be replaced by the "del" shell command. + +It is important to note that in order to select the proper set of tools +to use, Swift must know when a site runs under Windows. To inform Swift +of this, specify the "sysinfo" attribute for the "pool" element in the +site catalog. For example: + +[source,xml] + +... + From davidk at ci.uchicago.edu Mon May 16 14:29:37 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Mon, 16 May 2011 19:29:37 -0000 Subject: [Swift-commit] r4478 - in branches/release-0.92: . docs Message-ID: <20110516192901.A1EC99CD2E@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-16 14:29:01 -0500 (Mon, 16 May 2011) New Revision: 4478 Removed: branches/release-0.92/docs/Makefile branches/release-0.92/docs/README.txt branches/release-0.92/docs/build-chunked-userguide.sh branches/release-0.92/docs/buildguides.sh branches/release-0.92/docs/formatting/ branches/release-0.92/docs/historical/ branches/release-0.92/docs/log-processing.xml branches/release-0.92/docs/plot-tour.xml branches/release-0.92/docs/plot-tour/ branches/release-0.92/docs/provenance.xml branches/release-0.92/docs/quickstartguide.xml branches/release-0.92/docs/reallyquickstartguide.xml branches/release-0.92/docs/swift-site-model.fig branches/release-0.92/docs/swift-site-model.png branches/release-0.92/docs/tutorial-live.xml branches/release-0.92/docs/tutorial.xml branches/release-0.92/docs/type-hierarchy.fig branches/release-0.92/docs/type-hierarchy.png branches/release-0.92/docs/userguide-rotated.jpeg branches/release-0.92/docs/userguide-shane.jpeg branches/release-0.92/docs/userguide.xml Modified: branches/release-0.92/build.xml Log: First draft of updated document formats and scripts Modified: branches/release-0.92/build.xml =================================================================== --- branches/release-0.92/build.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/build.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -55,6 +55,8 @@ fixeol: change newlines to the unix standard. + docs: + Build Swift documentation from asciidoc txt files @@ -260,6 +262,15 @@ + + + + + + + + + Deleted: branches/release-0.92/docs/Makefile =================================================================== --- branches/release-0.92/docs/Makefile 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/Makefile 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,35 +0,0 @@ - -# FOP = fop -FOP = fop/fop.sh - -all: phps pdfs - -phps: userguide.php tutorial.php tutorial-live.php quickstartguide.php reallyquickstartguide.php provenance.php historical/languagespec.php historical/languagespec-0.6.php log-processing.php plot-tour.php - -htmls: userguide.html tutorial.html tutorial-live.html quickstartguide.html reallyquickstartguide.html provenance.html historical/languagespec.html historical/languagespec-0.6.html log-processing.html plot-tour.html - -pdfs: userguide.pdf tutorial.pdf tutorial-live.pdf quickstartguide.pdf reallyquickstartguide.pdf provenance.pdf historical/languagespec.pdf historical/languagespec-0.6.pdf log-processing.pdf - -GUIDE_PHP=$(shell find userguide -name "*.php" ) -GUIDE_HTML=$(patsubst %.php,%.html,$(GUIDE_PHP)) - -guide_html: $(GUIDE_HTML) - -chunked-userguide: userguide.xml - ./build-chunked-userguide.sh - -%.php: %.xml formatting/swiftsh_html.xsl - xsltproc --nonet formatting/swiftsh_html.xsl $< - sed -e "s/index.html#/#/g" index.html >$@ - chmod a+rx $@ - -%.pdf: %.xml formatting/vdl2_fo.xsl - $(FOP) -xsl formatting/vdl2_fo.xsl -xml $< -pdf $@ - chmod a+rx $@ - -%.html: %.php - cp $< $@ - chmod a+rx $@ - -clean: - rm -fv *.php userguide/*.php Deleted: branches/release-0.92/docs/README.txt =================================================================== --- branches/release-0.92/docs/README.txt 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/README.txt 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,69 +0,0 @@ -Swift Documentation -=================== - -General principles: - - - sections and subsections are ordered from , , or using - arbitrary depth
    tags - - code samples are given inside tags, which will cause - syntax highlighting to happen automatically - - user interactions / screen output are given inside tags. - - be careful to escape in-text "<" to "<" - - there are some conventions for using id attributes at various - places in the documents - for example, some tutorial sections use - 'tutorial.'; profile entries in the user guide use - 'profile..'. Try to keep id attributes unique across - the entire document set. - -The first time guides are built in a particular checkout, it is necessary -to place the docbook formatting stylesheets under the formatting/docbook/ -directory. This can be done with a symlink if docbook is installed elsewhere. - -For example: - -A) On the CI network, /home/hategan/docbook contains a docbook installation that -can be linked like this: - -$ cd formatting -$ ln -s /home/hategan/docbook/ docbook - - -B) on benc's os x machine: - -# install docbook from DarwinPorts -$ sudo port install docbook-xsl - -# setup links -$ cd formatting -$ ln -s /opt/local/share/xsl/docbook-xsl/ docbook - -C) in general: - - 1) Install Apache - - 2) Install PHP (cf. http://dan.drydog.com/apache2php.html) - - 3) Add these lines to Apache's httpd.conf: - - AddHandler php5-script php - AddType text/html php - - 4) Update httpd.conf, adding index.php: - - DirectoryIndex index.html index.php - - 5) Make sure perms are correct - - 6) Create formatting/docbook link (see above) - - 7) Create fop link - -Once the links are set up, the buildguides.sh script will build all guides -as php. Run it with no parameters, like this: - -$ ./buildguides.sh - -or use make to get HTML documents like this: - -$ make userguide.html - Deleted: branches/release-0.92/docs/build-chunked-userguide.sh =================================================================== --- branches/release-0.92/docs/build-chunked-userguide.sh 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/build-chunked-userguide.sh 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,11 +0,0 @@ -#!/bin/sh - -mkdir -p userguide/ || exit 1 -cd userguide/ || exit 2 -rm -f *.html *.php -cp ../*.png . -cp ../*.jpeg . - -xsltproc --nonet ../formatting/swiftsh_html_chunked.xsl ../userguide.xml -chmod a+r *.php - Deleted: branches/release-0.92/docs/buildguides.sh =================================================================== --- branches/release-0.92/docs/buildguides.sh 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/buildguides.sh 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,5 +0,0 @@ -#!/bin/sh - -make all chunked-userguide -./build-chunked-userguide.sh - Deleted: branches/release-0.92/docs/log-processing.xml =================================================================== --- branches/release-0.92/docs/log-processing.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/log-processing.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,162 +0,0 @@ - - - - -
    - - Swift log processing tools - Source control $LastChangedRevision$ - - -
    - Overview - -There is a package of Swift log processing utilties. - - -
    -
    Prerequisites - -gnuplot 4.0, gnu m4, gnu textutils, perl - - -
    -
    Web page about a run - - -swift-plot-log /path/to/readData-20080304-0903-xgqf5nhe.log - -This will create a web page, report-readData-20080304-0903-xgqf5nhe -If the above command is used before a run is completed, the web page will -report information about the workflow progress so far. - - -
    -
    CEDPS logs - -The log processing tools can output transition streams in -CEDPS logging format: - -swift-plot-log /path/to/readData-20080304-0903-xgqf5nhe.log execute.cedps - - -
    -
    Event/transition channels - -Various event channels are extracted from the log files and made available -as .event and .transition files. -These roughly correspond to processes within the Swift runtime environment. - - These streams are then used to provide the data for the various -output formats, such as graphs, web pages and CEDPS log format. -The available streams are: - - - - Stream nameDescription - - executeSwift procedure invocations - execute2individual execution attempts - kickstartkickstart records (not available as transitions) - karatasks karajan level tasks, available as transitions (there are also four substreams karatasks.FILE_OPERATION, karatasks.FILE_TRANSFER and karatasks.JOB_SUBMISSION available as events but not transitions) - workflowa single event representing the entire workflow - dostageinstage-in operations for execute2s - dostageoutstage-out operations for execute2s - - -
    - -
    - -Streams are generated from their source log files either as .transitions -or .event files, for example by swift-plot-log whatever.log foo.event. - - -Various plots are available based on different streams: - - - - Makefile targetDescription - - foo.pngPlots the foo event stream - foo-total.pngPlots how many foo events are in progress at any time - foo.sorted-start.pngPlot like foo.png but ordered by start time - - -
    - -
    - -Text-based statistics are also available with make foo.stats. - - -Event streams are nested something like this: - - -workflow - execute - execute2 - dostagein - karatasks (fileops and filetrans) - clustering (optional) - karatasks (execution) - cluster-log (optional) - wrapper log (optional) - kickstart log - dostageout - karatasks (fileops and filetrans) - - - -
    -
    Internal file formats -The log processing code generates a number of internal files that -follow a standard format. These are used for communication between the -modules that parse various log files to extract relevant information; and -the modules that generate plots and other summary information. - -need an event file format of one event per line, with that line -containing start time and duration and other useful data. - -col1 = start, col2 = duration, col3 onwards = event specific data - for -some utilities for now should be column based, but later will maybe -move to attribute based. - -between col 1 and col 2 exactly one space -between col 2 and col 3 exactly one space - -start time is in seconds since unix epoch. start time should *not* be -normalised to start of workflow - -event files should not (for now) be assumed to be in order - -different event streams can be stored in different files. each event -stream should use the extension .event - - - -.coloured-event files -===================== -third column is a colour index -first two columns as per .event (thus a coloured-event is a specific -form of .event) - - -
    - -
    hacky scripts -There are a couple of hacky scripts that aren't made into proper -commandline tools. These are in the libexec/log-processing/ directory: - - - ./execute2-status-from-log [logfile] - lists every (execute2) job and its final status - - ./execute2-summary-from-log [logfile] - lists the counts of each final job status in log - - -
    -
    - - Deleted: branches/release-0.92/docs/plot-tour.xml =================================================================== --- branches/release-0.92/docs/plot-tour.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/plot-tour.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,311 +0,0 @@ - - - - -
    - - Swift log plotting and the some internal mechanics of Swift - - -
    - Overview - -This document attempts to explain some of the meaning of the Swift -log-processing plots, giving an explanation of how some of Swift's -execution mechanism works and of some of the terminology used. - -
    - -
    'execute' - SwiftScript app {} block invocations - - -When a SwiftScript program invokes a application procedure (one with an -app {} block), an 'execute' appears in the log file in START state. When -all attempts at execution have finished (either successfully or unsuccessfully) -then the execute will go into END_SUCCESS or END_FAILURE state. A workflow -is successful if and only if all invocations end in END_SUCCESS. - - - -The execute states represent progress -through the karajan procedure defined in -libexec/execute-default.k. - -State changes for execute logs are defined by karajan log calls throughout -this file. - - - -An execute consists of multiple attempts to perform -execute2s, with retries and replication -as appropriate. Retries and replication are not exposed through the states -of 'execute's. - - -Executes are uniquely identified within a run by their karajan thread ID, -which is present in the log files as the thread= parameter on execute -log messsages. - - - -Here is a simple SwiftScript program which runs a foreach loop (few.swift): - -p() { - app { - sleep "10s"; - } -} - -foreach i in [1:8] { - p(); -} - - - - - -Using the swift-plot-log from the log processing module, -this graph gets generated to summarise execute state transitions: - - - - - -In this graph, the forloop calls p() eight times. Because there are no -dependencies between those eight invocations, they are all invoked at the same -time, around 1s into the run. This is show on the graph by the JOB_START line -going from zero up to eight at around x=1s. As time passes, the sleep jobs -complete, and as they do so the number of jobs in END_SUCCESS state increases. -When all eight jobs are in END_SUCCESS state, the run is over. - -Here is a program with some data dependencies between invocations (dep.swift): - - -$ cat dep.swift -type file; - -p(file f) { - app { - sleep "10s"; - } -} - -(file o) q() { - app { - touch @o; - } -} - -file intermediate = q(); -p(intermediate); - - - - - -Here is a plot of the execute states for this program: - - - - -In this run, one invocation starts (q()) fairly quickly, -but the other invocation (of p()) does not - instead, it does not start until -approximately the time that the q() invocation has reached END_SUCCESS. - - - -Finally in this section on 'execute', here is a demonstration of how the above -two patterns fit together in one program (few2.swift: - -type file; - -(file o) p(file i) { - app { - sleepcopy @i @o; - } -} - -file input <"input">; -file output[]; - -foreach i in [1:8] { - file intermediate; - intermediate = p(input); - output[i] = p(intermediate); -} - - - - - -In total the program has 16 invocations of p(), dependent on each other in -pairs. The dependencies can be plotted like this: - - -$ swift -pgraph few2.dot few2.swift -$ dot -Tpng -o few2.png few2.dot - - -yielding this graph: - - - - - -When this program is run, the first row of 8 invocations can all start at the -beginning of the program, because they have no dependencies (aside from on -the input file). This can be seen around t=4 when the start line jumps up to 8. -The other 8 invocations can only begin when the invocations they are dependent -on have finished. This can be seen in the graph - every time one of the first -invocations reaches END_SUCCESS, a new invocation enters START. - - - - -
    -
    execute2 - one attempt at running an execute - -An execute2 is one attempt to execute an app procedure. execute2s are invoked -by execute, once for each retry or replication -attempt. - -The states of an execute2 represent progress through the execute2 karajan -procedure defined in libexec/vdl-int.k - - - -Before an execute2 makes its first state log entry, it chooses a site to run on. -Then at the start of file stage-in, the execute2 goes into THREAD_ASSOCIATION -state. Once stagein is completed, the JOB_START state is entered, indicating -that execution of the job executable will now be attempted. Following that, -STAGING_OUT indicates that the output files are being staged out. If everything -is completed successfully, the job will enter JOB_END state. - -There are two exceptions to the above sequence: JOB_CANCELLED indicates that -the replication mechanism has cancelled this job because a different execute2 -began actual execution on a site for the same execute. APPLICATION_EXCEPTION -indicates that there was an error somewhere in the attempt to stage in, -actually execute or stage out. If a job goes into APPLICATION_EXCEPTION state -then it will generally be retried (up to a certain number of times defined -by the "execution.retries" parameter) by the containing execute. - - - -In this example, we use a large input file to slow down file staging so that -it is visible on an execute2 graph (big-files.swift): - -type file; - -(file o) p(file i) { - app { - sleepcopy @i @o; - } -} - -file input <"biginput">; -file output[]; - -foreach i in [1:8] { - output[i] = p(input); -} - - - - - - - -There is an initial large input file that must be staged in. This causes the first -jobs to be in stagein state for a period of time (the space between the -ASSOCIATED and JOB_START lines at the lower left corner of the graph). All -invocations share a single input file, so it is only staged in once and -shared between all subsequent invocations - once the file has staged in at the -start, there is no space later on between the ASSOCIATED and JOB_START lines -because of this. - - -Conversely, each invocation generates a large output file without there being -any sharing. Each of those output files must be staged back to the submit -side, which in this application takes some time. This can be seen by the large -amount of space between the STAGING_OUT and JOB_END lines. - - -The remaining large space on the graph is between the JOB_START and STAGING_OUT -lines. This represents the time taken to queue and execute the application -executable (and surrounding Swift worker-side wrapper, which can sometimes -have non-negligable execution times - this can be seen in the -info section). - - -
    - -
    wrapper info logs - -When a job runs, it is wrapped by a Swift shell script on the remote site that -prepares the job environment, creating a temporary directory and moving -input and output files around. Each wrapper invocation corresponds to a single -application execution. For each invocation of the wrapper, a log file is created. -Sometimes that log file is moved back to the submission side (when there is -an error during execution, or when the setting -wrapper.always.transfer=true -is set) and placed in a *.d/ directory corresponding in -name to the main log file. - - - -The states of the info logs represent progress through the wrapper -script, libexec/wrapper.sh. - - - -For the same run of big-files.swift as shown in the -execute2 section, here is a plot of states -in wrapper info log files: - - - - - - -The trace lines on this graph fit entirely within the space between JOB_START -and STAGING_OUT on the corresponding execute2 graph, because the Swift worker node -wrapper script does not run until the submit side of Swift has submitted a -job for execution and that job has begun running. - - - -Many of the lines on this plot are very close together, because many of the -operations take minimal time. The main space between lines is between -EXECUTE and EXECUTE_DONE, where the actual application executable is executing; -and between COPYING_OUTPUTS and RM_JOBDIR, where the large output files are -copied from a job specific working directory to the site-specific shared -directory. It is quite hard to distinguish on the graph where overlapping -lines are plotted together. - - - -Note also that minimal time is spent copying input files into the job-specific -directory in the wrapper script; that is because in this run, the wrapper -script is using the default behaviour of making symbolic links in the job-specific -directory; symbolic links are usually cheap to create compared to copying file -content. However, if the SWIFT_JOBDIR_PATH parameter is set, then Swift will -copy the input file to the specified job directory instead of linking. This -will generally result in much more time being spent preparing the job directory -in the Swift wrapper, but in certain circumstances this time is overwhelmingly -offset by increased performance of the actual application executable (so on -this chart, this would be seen as an increased job directory preparation time, -but a reduced-by-more application executable time). - - - -
    - -
    Relation of logged entities to each other -Here is a simple diagram of how some of the above log channels along -with other pieces fit together: - - -
    - -
    - Deleted: branches/release-0.92/docs/provenance.xml =================================================================== --- branches/release-0.92/docs/provenance.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/provenance.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,2592 +0,0 @@ - - - - -
    -provenance working notes, benc -$Id$ -
    Goal of this present work - -The goal of the work described in this document is to investigate -retrospective provenance and -metadata handling in Swift, with an emphasis -on effective querying of the data, rather than on collection of the data. - - - -The motivating examples are queries of the kinds discussed in section 4 of -'Applying the Virtual Data Provenance Model'; -the queries and metadata in the First Provenance Challenge; and the metadata database used by -i2u2 cosmic. - - - -I am attempting to scope this so that it can be implemented in a few -months; more expensive features, though desirable, are relegated the the -'What this work does not address' section. Features which appear fairly -orthogonal to the main aims are also omitted. - - - -This document is a combination of working notes and on-going status report -regarding my provenance work; as such its got quite a lot of opinion in it, -some of it not justified in the text. - - -
    -
    Running your own provenance database -This section details running your own SQL-based provenance database on -servers of your own control. - -
    Check out the latest SVN code - - -Use the following command to check out the provenancedb -module: - - -svn co https://svn.ci.uchicago.edu/svn/vdl2/provenancedb - - - -
    - - -
    Configuring your SQL database - -Follow the instructions in one of the following sections, to configure your -database either for sqlite3 or for postgres. - -
    Configuring your sqlite3 SQL database - -This section describes configuring the SQL scripts to use -sqlite, which is -appropriate for a single-user installation. - -Install or find sqlite3. On -communicado.ci.uchicago.edu, it is installed and can be -accessed by adding the line +sqlite3 to your ~/.soft file -and typing resoft. Alternatively, on OS X with MacPorts, this command works: - -$ sudo port install sqlite3 - -Similar commands using apt or yum will -probably work under Linux. - - -In the next section, you will create a provenance.config -file. In that, you should configure the use of sqlite3 by specifying: - -export SQLCMD="sqlite3 provdb " - -(note the trailing space before the closing quote) - -
    - -
    Configuring your own postgres 8.3 SQL database - -This section describes configuring a postgres 8.3 database, which is -appropriate for a large installation (where large means lots of log -files or multiple users) - - -First install and start postgres as appropriate for your platform -(using apt-get or port for example). - - -As user postgres, create a database: - -$ /opt/local/lib/postgresql83/bin/createdb provtest1 - - - -Check that you can connect and see the empty database: - -$ psql83 -d provtest1 -U postgres -Welcome to psql83 8.3.6, the PostgreSQL interactive terminal. - -Type: \copyright for distribution terms - \h for help with SQL commands - \? for help with psql commands - \g or terminate with semicolon to execute query - \q to quit - -provtest1=# \dt -No relations found. -provtest1=# \q - - - -In the next section, when configuring provenance.config, -specify the use of postgres like this: - -export SQLCMD="psql83 -d provtest1 -U postgres " - -Note the trailing space before the final quote. Also, note that if you -fiddled the above test command line to make it work, you will have to make -similar fiddles in the SQLCMD configuration line. - -
    -
    - -
    Import your logs - -Now create a etc/provenance.config file to define local -configuration. An example that I use on my laptop is present in -provenance.config.soju. -The SQLCMD indicates which command to run for SQL -access. This is used by other scripts to access the database. The -LOGREPO and IDIR variables should -point to the directory under which you collect your Swift logs. - - -Now import your logs for the first time like this: - -$ ./swift-prov-import-all-logs rebuild - - - -
    - -
    Querying the newly generated database - -You can use swift-about-* commands, described in -the commands section. - - -If you're using the SQLite database, you can get an interactive SQL -session to query your new provenance database like this: - -$ sqlite3 provdb -SQLite version 3.6.11 -Enter ".help" for instructions -Enter SQL statements terminated with a ";" -sqlite> - - - -
    - -
    - -
    swift-about-* commands -There are several swift-about- commands: - -swift-about-filename - returns the global dataset IDs for the specified -filename. Several runs may have output the same filename; the provenance -database cannot tell which run (if any) any file with that name that -exists now came from. - -Example: this looks for information about -001-echo.out which is the output of the first -test in the language-behaviour test suite: - -$ ./swift-about-filename 001-echo.out -Dataset IDs for files that have name file://localhost/001-echo.out - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-1440-67vursv4:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-2146-ja2r2z5f:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-1608-itdd69l6:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080303-1011-krz4g2y0:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080303-1100-4in9a325:720000000001 - -Six different datasets in the provenance database have had that filename -(because six language behaviour test runs have been uploaded to the -database). - - -swift-about-dataset - returns information about a dataset, given -that dataset's uri. Returned information includes the IDs of a containing -dataset, datasets contained within this dataset, and IDs for executions -that used this dataset as input or output. - -Example: - -$ ./swift-about-dataset tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 -About dataset tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 -That dataset has these filename(s): - file://localhost/001-echo.out - -That dataset is part of these datasets: - -That dataset contains these datasets: - -That dataset was input to the following executions (as the specified named parameter): - -That dataset was output from the following executions (as the specified return parameter): - tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 | t - -This shows that this dataset is not part of a more complicated dataset -structure, and was produced as an output parameter t from an execution. - -swift-about-execution - gives information about an execution, given -an execution ID - -$ ./swift-about-execution tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 -About execution tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 - id | starttime | duration | finalstate | app | scratch -----------------------------------------------------------------------------------------------------------------------------------+----------------+-------------------+----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------- - tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 | 1200318839.393 | 0.743000030517578 | 0 | END_SUCCESS | echo -(1 row) - -This shows some basic information about the execution - the start time, -the duration, the name of the application, the final status. - - -
    - - -
    What this work does not address - -This work explicitly excludes a number of uses which traditionally -have been associated with the VDS1 Virtual Data Catalog - either as real -or as imagined functionality. - - -Much of this is open to debate; especially regarding which features are the -most important to implement after the first round of implementation has -occurred. - - - - - -Namespaces and versioning - -the need for these is somewhat orthogonal to the work here. - -Namespaces and versions provide a richer identifier but don't -fundamentally change the nature of the identifier. -so for now I mostly ignore as they are -(I think) fairly straightforward drudgework to implement, rather than -being fundamentally part of how queries are formed. Global namespaces -are used a little bit for identifying datasets between runs (see tag URI -section) - - - - -Prospective provenance - -SwiftScript source programs don't have as -close a similarity to their retrospective structure as in VDL1, so a bunch -of thought required here. Is this required? Is it different from the -SwiftScript program-library point? - - - A database of all logged information - -though it would be interesting -to see what could be done there. straightforward to import eg. -.event and/or .transition files from log parsers into the DB. - - - - - Replica management - - -No specific replica location or management support. However see sections -on general metadata handling (in as much as general metadata can support -replica location as a specific metadata usecase); and also the section on -global naming in the to-be-discussed section. This ties in with the -Logical File Names concept somehow. - - - - - - A library for SwiftScript code - -need better uses for this and -some indication that a more conventional version control system is -not more appropriate. - - -Also included in this exclusion is storage of type definitions. -Its straightforward to store type names; but the definitions are -per-execution. More usecases would be useful here to figure out what sort -of query people want to make. - - - - - Live status updates of in-progress workflows - - -this may happen if data goes -into the DB during run rather than at end (which may or may not happen). -also need to deal with slightly different data - for example, execute2s -that ran but failed (which is not direct lineage provenance?) - - -so - one successful invocation has: one execute, one execute2 (the most recent), -and maybe one kickstart record. it doesn't track execute2s and kickstarts for -failed execution attempts (nor, perhaps, for failed workflows at all...) - - - - - -Deleting or otherwise modifying provenance data - - -Deleting or otherwise modifying provenance data. Though deleting/modifying -other metadata should be taken into account. - - - - - Security - -There are several approaches -here. The most native approach is to use the security model of the -underlying database (which will vary depending on which database is used). - -This is a non-trivial area, especially to do with any richness. -Trust relationships between the various parties accessing the database -should be taken into account. - - - - -A new metadata or provenance query language - -Designing a (useful - i.e. usable and performing) database -and query language is a non-trivial exercise (on the order of years). - - -For now, use existing query languages and their implementations. Boilerplate -queries can be developed around those languages. - - -One property of this is that there will not be a uniform query language for -all prototypes. This is contrast to the VDS1 VDC which had a language which -was then mapped to at least SQL and perhaps some XML query language too. - - -An intermediate / alternative to something language-like is a much more -tightly constrained set of library / template queries with a very constrained -set of parameters. - - -Related to this is the avoidance as much as possible of mixing models; so that -one query language is needed for part of a query, and another query language -is needed for another part of a query. An example of this in practice is the -storage of XML kickstart records as blobs inside a relational database in the -VDS1 VDC. SQL could be used to query the containing records, whilst an -XML query language had to be used to query inner records. No benefit could -be derived there from query language level joining and query optimisation; -instead the join had to be implemented poorly by hand. - - - - -An elegant collection mechanism for provenance or -metadata - -The prototypes here collect their information through log stripping. This -may or may not be the best way to collect the data. For example, hooks -inside the code might be a better way. - - - - -
    - -
    Data model -
    Introduction to the data model - -All of the prototypes use a basic data model that is strongly -related to the structure of data in the log files; much of the naming here -comes from names in the log files, which in turn often comes from source -code procedure names. - - -The data model consists of the following data objects: - -execute - an execute represents a procedure call in a -SwiftScript program. - -execute2 - an execute2 is an attempt to actually execute an -'execute' object. -dataset - a dataset is data used by a Swift program. this might be -a file, an array, a structure, or a simple value. -workflow - a workflow is an execution of an entire SwiftScript -program -
    - -
    execute - - -execute - an 'execute' is an execution of a -procedure call in a SwiftScript program. Every procedure call in a -SwiftScript program corresponds to either -one execute (if the execution was attempted) or zero (if the workflow was -abandoned before an execution was attempted). An 'execute' may encompass -a number of attempts to run the appropriate procedure, possibly on differnt -sites. Those attempts are contained within an execute as execute2 entities. -Each execute is related to zero or more datasets - those passed as inputs -and those that are produced as outputs. - -
    -
    execute2 - -execute2 - an 'execute2' is an attempt to run a -program on some grid site. It consists of staging in input files, running the -program, and staging out the output files. Each execute2 belongs to exactly -one execute. If the database is storing only successful workflows and -successful executions, then each execute will be associated with -exactly one execute2. If storing data about unsuccessful workflows or -executions, then each execute may have zero or more execute2s. - -
    -
    dataset - -A dataset represents data within a -SwiftScript program. A dataset can be an array, a structure, a file or -a simple value. Depending on the nature of the dataset it may have some -of the following attributes: a value (for example, if the dataset -represents an integer); a filename (if the dataset represents a file); -child datasets (if the dataset represents a structure or an array); and -parent dataset (if the dataset is contained with a structure or an -array). - - - -At present, each dataset corresponds to exactly one in-memory DSHandle -object in the Swift runtime environment; however this might not continue -to be the case - see the discussion section on cross-dataset run -identification. - - -Datasets may be related to executes, either as datasets -taken as inputs by an execute, or as datasets produced by an execute. -A dataset may be produced as an output by at most one execute. If it is not -produced by any execute, it is an input to the workflow -and has been produced through some other mechanism. Multiple datasets may -have the same filename - for example, at present, each time the same file -is used as an input in different workflows, a different dataset appears in -the database. this might change. multiple workflows might (and commonly do) -output files with the same name. at present, these are different datasets, -but are likely to remain that way to some extent - if the contents of files -is different then the datasets should be regarded as distinct. - -
    -
    workflow - -workflow - a 'workflow' is an execution of an -entire SwiftScript program. Each execute belongs to exactly one workflow. At -present, each dataset also belongs to exactly one workflow (though the -discussion section talks about how that should not necessarily be the case). - -
    - -TODO: diagram of the dataset model (similar to the one in the -provenance paper but probably different). design so that in the XML -model, the element containment hierarchies can be easily marked in a -different colour -
    - -
    Prototype Implementations - -I have made a few prototype implementations to explore ways of storing -and querying provenance data. - - -The basic approach is: build on the log-processing code, which knows how -to pull out lots of information from the log files and store it in a -structured text format; extend Swift to log additional information as -needed; -write import code which knows -how to take the log-processing structured files and put them into whatever -database/format is needed by the particular prototype. - - -If it is desirable to support more than one of these storage/query mechanisms -(perhaps because -they have unordered values of usability vs query expessibility) then -perhaps should be core provenance output code which is somewhat -agnostic to storage system (equivalent to the post-log-processing -text files at the moment) and then some relatively straightforward set -of importers which are doing little more than syntax change -(cf. it was easy to adapt the SQL import code to make -prolog code instead) - - - -The script import-all will import into the -basic SQL and eXist XML databases. - - -
    Relational, using SQL -There are a couple of approaches based around relational databases -using SQL. The plain SQL approach allows many queries to be answered, but -does provide particularly easy querying for the transitive relations -(such as the 'preceeds' relation mentioned elsewhere); ameliorating this -problem is point of the second model. - -
    -Plain SQL -In this model, the provenance model is mapped to a relational -schema, stored in sqlite3 and queried with SQL. - - - -This prototype uses sqlite3 on my laptop. The import-all -will initialise and import into this database (and also into the XML DB). - - - -example query - counts how many of each procedure have been called. - -sqlite> select procedure_name, count(procedure_name) from executes, invocation_procedure_names where executes.id = invocation_procedure_names.execute_id group by procedure_name; -align|4 -average|1 -convert|3 -slicer|3 - - - -needs an SQL database. sqlite is easy to get (from standard OS software -repos, and from globus toolkit) so this is not as horrible as it seems. -setup requirements for sqlite are minimal. - - -metadata: one way is to handle them as SQL relations. this allows them -to be queried using SQL quite nicely, and to be indexed and joined on -quite easily. - - -prov query 1:Find the process that led to Atlas X Graphic / everything that caused Atlas X Graphic to be as it is. This should tell us the new brain images from which the averaged atlas was generated, the warping performed etc. - - -
    Description of tables - -Executions are stored in a table called 'executes'. Each execution has the fields: id - a globally unique ID for that execution; starttime - the start time -of the execution attempt, in seconds since the unix epoch (this is roughly -the time that swift decides to submit the task, *not* the time that a worker -node started executing the task); duration - in seconds (time from start time -to swift finally finishing the execution, not the actual on-worker execution -time); final state (is likely to always be END_SUCCESS as the present import -code ignores failed tasks, but in future may include details of failures; -app - the symbolic name of the application - - -Details of datasets are stored in three tables: dataset_filenames, -dataset_usage and dataset_containment. - - -dataset_filenames maps filenames (or more generally URIs) to unique dataset -identifiers. - - -dataset_usage maps from unique dataset identifiers to the execution -unique identifiers for executions that take those datasets as inputs -and outputs. execute_id and dataset_id identify the execution and the -procedure which are related. direction indicates whether this dataset -was used as an input or an output. param_name is the name of the parameter -in the SwiftScript source file. - - -dataset_containment indicates which datasets are contained within others, -for example within a structure or array. An array or structure is a dataset -with its own unique identifier; and each member of the array or structure -is again a dataset with its own unique identifier. The outer_dataset_id and -inner_dataset_id fields in each row indicate respectively the -containing and contained dataset. - - -
    - -
    - -
    -SQL with Pre-generated Transitive Closures - -SQL does not allow expression of transitive relations. This causes a -problem for some of the queries. -Work has previously been done (cite) to work on pre-generating -transitive closures over relations. This is similar in concept to the -pregenerated indices that SQL databases traditionally provide. - -In the pre-generated transitive closure model, a transitive closure -table is pregenerated (and can be incrementally maintained as data is added -to the database). Queries are then made against this table instead of -against the ground table. - - -All of the data available in the earlier SQL model is available, in -addition to the additional closures generated here. - - -Prototype code: There is a script called prov-sql-generate-transitive-closures.sh to generate the close of the preceeds -relation and places it in a table called trans: - -$ prov-sql-generate-transitive-closures.sh -Previous: 0 Now: 869 -Previous: 869 Now: 1077 -Previous: 1077 Now: 1251 -Previous: 1251 Now: 1430 -Previous: 1430 Now: 1614 -Previous: 1614 Now: 1848 -Previous: 1848 Now: 2063 -Previous: 2063 Now: 2235 -Previous: 2235 Now: 2340 -Previous: 2340 Now: 2385 -Previous: 2385 Now: 2396 -Previous: 2396 Now: 2398 -Previous: 2398 Now: 2398 - - -A note on timing - constructing the closure of 869 base relations, -leading to 2398 relations in the closure takes 48s with no indices; adding -an index on a column in the transitive relations table takes this time down -to 1.6s. This is interesting as an example of how some decent understanding -of the data structure to produce properly optimised queries and the like -is very helpful in scaling up, and an argument against implementing a poor -'inner system'. - -Now we can reformulate some of the queries from the SQL section -making use of this table. - - -There's some papers around about transitive closures in SQL: - -'Maintaining transitive closure of graphs in SQL' -and -http://willets.org/sqlgraphs.html - - - -how expensive is doing this? how cheaper queries? how more expensive is -adding data? and how scales (in both time and size (eg row count)) as we -put in more rows (eg. i2u2 scale?) exponential, perhaps? though -the theoretical limit is going to be influenced by our usage pattern -which I think for the most part will be lots of disjoint graphs -(I think). we get to index the transitive closure table, which we don't -get to do when making the closure at run time. - - -We don't have the path(s) between nodes but we could store that in the -closure table too if we wanted (though multiple paths would then be more -expensive as there are now more unique rows to go in the closure table) - - -This is a violation of normalisation which the traditional relational people -would say is bad, but OLAP people would say is ok. - - - -how much easier does it make queries? -for queries to root, should be much easier (query over -transitive table almost as if over base table). but queries such as -'go back n-far then stop' and the like harder to query. - - - -keyword: 'incremental evaluation system' (to maintain transitive closure) - - - -The difference between plain SQL and SQL-with-transitive-closures -is that in SQL mode, construction occurs at query time and the query -needs to specify that construction. In the transitive-close mode, -construction occurs at data insertion time, with increased expense there -and in size of db, but cheaper queries (I think). - - -sample numbers: fmri example has 50 rows in base causal relation -table. 757 in table with transitive close. - - - -If running entirely separate workflows, both those numbers will scale linearly -with the number of workflows; however, if there is some crossover between -subsequent workflows in terms of shared data files then the transitive -graph will grow super-linearly. - - -
    -
    -
    XML - -In this XML approach, provenance data and metadata is represented as -a set of XML documents. - -Each document is stored in some kind of document store. -Two different document stores are used: -the posix filesystem and eXist. XPath and XQuery are investigated as -query languages. - -semi-structuredness allows structured metadata without having to -necessarily declare its schema (which I think is one of the desired properties -that turns people off using plain SQL tables to reflect the metadata -schema). but won't get indexing without some configuration of structure so -whilst that will be nice for small DBs it may be necessary to scale up -(though that in itself isn't a problem - it allows gentle start without -schema declaration and to scale up, add schema declarations later on - fits -in with the scripting style). semi-structured form of XML lines up very -will with the desire to have semi-structured metadata. compare ease of -converting other things (eg fmri showheader output) to loose XML - field -relabelling without having to know what the fields actually are - to how -this needs to be done in SQL. - - - -The hierarchical structure of XML perhaps better for dataset containment -because we can use // operator which is transitive down the tree for -dataset containment. - - -XML provides a more convenient export format than SQL or the other formats -in terms of an easily parseable file format. There are lots of -tools around for processing XML files in various different ways (for example, -treating as text-like documents; deserialising into Java in-memory objects -based on an XML Schema definition), and XML is one of the most familiar -structured data file formats. - - -Not sure what DAG representation would look like here? many (one per arc) -small documents? is that a problem for the DBs? many small elements, more -likely, rather than many small documents - roughly one document per workflow. - - -
    xml metadata -in the XML model, two different ways of putting in metadata: as descendents of the -appropriate objects (eg. dataset metadata under the relevant datasets). this -is most xml-like in the sense that its strongly hierarchical. as separate -elements at a higher level (eg. separate documents in xml db). the two ways -are compatible to the extent that some metadata can be stored one way, some -the other way, although the way of querying each will be different. - - -way i: at time of converting provenance data into XML, insert metadata at -appropriate slots (though if XML storage medium allows, it could be inserted -later on). - - -modified prov-to-xml.sh to put that info in for -the appropriate datasets (identified using the below descripted false-filename -method - -can now make queries such as 'tell me the datasets which have header metadata': - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '//dataset[headermeta]' - - - -way ii: need to figure out what the dataset IDs for the volumes are. At the -moment, the filename field for (some) mapped dataset parents still -has a filename -even though that file never exists, like below. This depends on the mapper -being able to invent a filename for such. Mappers aren't guaranteed to be -able to do that - eg where filenames are not formed as a function of the -parameters and path, but rely on eg. whats in the directory at initialisation -(like the filesystem mapper). - -<dataset identifier="10682109"> -<filename>file://localhost/0001.in</filename> -<dataset identifier="12735302"> -<filename>file://localhost/0001.h.in</filename> -</dataset> -<dataset identifier="7080341"> -<filename>file://localhost/0001.v.in</filename> -</dataset> - -so we can perhaps use that. The mapped filename here is providing a -dataset identification (by chance, not by design) so we can take advantage -of it: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.in"]/@identifier' -10682109 - - -I think metadata in XML is more flexible than metadata in relational, -in terms of not having to define schema and not having to stick to schema. -However, how will it stand up to the challenge of scalability? Need to get -a big DB. Its ok to say that indices need to be made - I don't dispute that. -What's nice is that you can operate at the low end without such. So need to -get this stuff being imported into eg eXist (maybe the prototype XML processing -should look like -> XML doc(s) on disk -> whatever xmldb in order to -facilitate prototyping and pluggability.) - - -
    - -
    XPath query language - - -XPath queries can be run either against the posix file system store -or against the eXist database. When using eXist, the opportunity exists -for more optimised query processing (and indeed, the eXist query processing -model appears to evaluate queries in an initially surprising and unintuitive -way to get speed); compared to on the filesystem, -where XML is stored in serialised form and must be parsed for each query. - - - -xml generation: - -./prov-to-xml.sh > /tmp/prov.xml - -and basic querying with xpathtool (http://www.semicomplete.com/projects/xpathtool/) - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/execute[thread="0-4-1"]' - - - -q1: - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance//dataset[filename="file://localhost/0001.jpeg"]' -<toplevel> - <dataset identifier="14976260"> - <filename>file://localhost/0001.jpeg</filename> - </dataset> -</toplevel> - -or can get the identifier like this: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier' -14976260 - -can also request eg IDs for multiple, like this: - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier|/provenance//dataset[filename="file://localhost/0002.jpeg"]/@identifier' - - - -can find the threads that use this dataset like this: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/tie[dataset=/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier]' -<toplevel> - <tie> - <thread>0-4-3</thread> - <direction>output</direction> - <dataset>14976260</dataset> - <param>j</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 14976260 with no value at dataset=final path=[1]</value> - </tie> - - - -now we can iterate as in the SQL example: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-4-3"][direction="input"]/dataset' -4845856 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="4845856"][direction="output"]/thread' -0-3-3 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-3-3"][direction="input"]/dataset' -3354850 -6033476 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="3354850"][direction="output"]/thread' -0-2 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-2"][direction="input"]/dataset' -4436324 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="4436324"][direction="output"]/thread' - - -so now we've exhausted the tie relation - dataset 4436324 comes from -elsewhere... - -so we say this: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/dataset[@identifier="4436324"]//dataset/@identifier' -11153746 -7202698 -12705705 -7202698 -12705705 -655223 -2088036 -13671126 -2088036 -13671126 -5169861 -14285084 -12896050 -14285084 -12896050 -6487148 -5772360 -4910675 -5772360 -4910675 - -which gives us (non-unique) datasets contained within dataset 4436324. We can -uniquify outside of the language: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/dataset[@identifier="4436324"]//dataset/@identifier' | sort |uniq -11153746 -12705705 -12896050 -13671126 -14285084 -2088036 -4910675 -5169861 -5772360 -6487148 -655223 -7202698 - -and now need to find what produced all of those... iterate everything again. -probably we can do it integrated with the previous query so that we -don't have to iterate externally: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/tie[dataset=/provenance/dataset[@identifier="4436324"]//dataset/@identifier]' -<?xml version="1.0"?> -<toplevel> - <tie> - <thread>0-1-3</thread> - <direction>output</direction> - <dataset>5169861</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 5169861 with no value at dataset=aligned path=[4]</value> - </tie> - <tie> - <thread>0-1-4</thread> - <direction>output</direction> - <dataset>6487148</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 6487148 with no value at dataset=aligned path=[1]</value> - </tie> - <tie> - <thread>0-1-2</thread> - <direction>output</direction> - <dataset>655223</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 655223 with no value at dataset=aligned path=[2]</value> - </tie> - <tie> - <thread>0-1-1</thread> - <direction>output</direction> - <dataset>11153746</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 11153746 with no value at dataset=aligned path=[3]</value> - </tie> -</toplevel> - -which reveals only 4 ties to procedures from those datasets - the elements -of the aligned array. We can get just the thread IDs for that by adding -/thread onto the end: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset=/provenance/dataset[@identifier="4436324"]//dataset/@identifier]/thread' -0-1-3 -0-1-4 -0-1-2 -0-1-1 - -so now we need to iterate over those four threads as before using same -process. - -so we will ask 'which datasets does this contain?' because at -present, a composite dataset will ultimately be produced by its component -datasets (though I think perhaps we'll end up with apps producing datasets -that are composites, eg when a file is output that then maps into some -structure - eg file contains (1,2) and this maps to struct { int x; int y;}. -TODO move this para into section on issues-for-future-discussion. - -so xpath here doesn't really seem too different in expressive ability -from the SQL approach - it still needs external implementation of -transitivity for some of the transitive relations (though not for -dataset containment). and that's a big complicating factor for ad-hoc queries... - -
    notes on using eXist -command line -client doc - -run in command line shell with local embedded DB (not running inside a -server, so analogous to using sqlite rather than postgres): - -~/work/eXist/bin/client.sh -s -ouri=xmldb:exist:// - - - -import a file: - -~/work/eXist/bin/client.sh -m /db/prov -p `pwd`/tmp.xml -ouri=xmldb:exist:// - -note that the -p document path is relative to exist root directory, not to -the pwd, hence the explicit pwd. - - -xpath query from commandline: - - echo '//tie' | ~/work/eXist/bin/client.sh -ouri=xmldb:exist:// -x - - -
    -
    - -
    XSLT - -very much like when we revieved xpath, xslt and xquery for MDS data - these -are the three I'll consider for the XML data model? does XSLT add anything? -not sure. for now I think not so ignore, or at least comment that it does -not add anything. - - - -./prov-to-xml.sh > /tmp/prov.xml -xsltproc ./prov-xml-stylesheet.xslt /tmp/prov.xml - -with no rules will generate plain text output that is not much use. - - -Two potential uses: i) as a formatting language for stuff coming out of -some other (perhaps also XSLT, or perhaps other language) query process. -and ii) as that other language doing semantic rather than presentation -level querying (better names for those levels?) - -
    - -
    XQuery query language - -Build query results for this using probably the same database as the -above XPath section, but indicating where things could be better expressed -using XPath. - - -Using XQuery with eXists: - -$ cat xq.xq -//tie -$ ~/work/eXist/bin/client.sh -ouri=xmldb:exist:// -F `pwd`/xq.xq - - - -A more advanced query: - -for $t in //tie - let $dataset := //dataset[@identifier=$t/dataset] - let $exec := //execute[thread=$t/thread] - where $t/direction="input" - return <r>An invocation of {$exec/trname} took input {$dataset/filename}</r> - - -
    - -
    - -
    RDF and SPARQL - -This can probably also be extended to SPARQL-with-transitive-closures -using the same methods as 1; or see OWL note below. - - -Pegasus/WINGS queries could be interesting to look at here - they -are from the same tradition as Swift. However, the don't deal very -well with transitivity. - -OWL mentions transitivity as something that can be expressed in -an OWL ontology but are there any query languages around that can -make use of that kind of information? - -See prolog section on RDF querying with prolog. - - -There's an RDF-in-XML format for exposing information in serialised form. -Same discussion applies to this as to the discussion in XML above. - -
    - -
    GraphGrep - - - download link see email -graphgrep -graphgrep install notes: port install db3 -some hack patches to get it to build with db3 - - -Got a version of graph grep with interesting graph language apparently in it. -Haven't tried it yet though. - -
    - -
    prolog -Perhaps interesting querying ability here. Probably slow? but not -really sure - SWI Prolog talks about indexing its database (and allowing -the indexing to be customised) and about supporting very large databases. -So this sounds hopeful. - - -convert database into SWI prolog. make queries based on that. - -Can make library to handle things like transitive relations - should be -easy to express the transitivity in various different ways (dataset -containment, procedure-ordering, whatever) - far more clear there than -in any other query language. - -SWI Prolog has some RDF interfacing, so this is clearly a realm that is -being investigated by some other people. For example: -
    It is assumed that Prolog is a suitable vehicle to reason with the data expressed in RDF models -- http://www.swi-prolog.org/packages/rdf2pl.html
    -
    - -http://www.xml.com/pub/a/2001/04/25/prologrdf/index.html - - - -prolog can be used over RDF or over any other tuples. stuff in SQL -tables should map neatly too. Stuff in XML hieararchy perhaps not so -easily but should still be doable. -indeed, SPARQL queries have a very prolog-like feel to them -superficially. - -prolog db is a program at the moment - want something that looks more -like a persistent modifiable database. not sure what the prolog approach -to doing that is. - -so maybe prolog makes an interesting place to do future research on -query language? not used by this immediate work but a direction to -do query expressibility research (building on top of whatever DB is used -for this round?) - - -q1 incremental: - - -?- dataset_filenames(Dataset,'file://localhost/0001.in'). - -Dataset = '10682109' ; - - -Now with lib.pl: - - -dataset_trans_preceeds(Product, Source) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Source, _, _). - - -dataset_trans_preceeds(Product, Source) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Inter, _, _), - dataset_trans_preceeds(Inter, Source). - - -then we can ask: - - -?- dataset_trans_preceeds('14976260',S). - -S = '4845856' ; - -S = '3354850' ; - -S = '6033476' ; - -S = '4436324' ; - -No - - -which is all the dataset IDs up until the point that we get into -array construction. This is the same iterative problem we have -in the SQL section too - however, it should be solvable in the prolog case -within prolog in the same way that the recursion is. so now: - - -base_dataset_trans_preceeds(Product, Source, Derivation) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Source, _, _), - Derivation = f(one). - -base_dataset_trans_preceeds(Product, Source, Derivation) :- - dataset_containment(Product, Source), - Derivation = f(two). - -dataset_trans_preceeds(Product, Source, Derivation) :- - base_dataset_trans_preceeds(Product, Source, DBase), - Derivation = [DBase]. - -dataset_trans_preceeds(Product, Source, Derivation) :- - base_dataset_trans_preceeds(Product, Inter, DA), - dataset_trans_preceeds(Inter, Source, DB), - Derivation = [DA|DB]. - - - - - -q4: - - -invocation_procedure_names(Thread, 'align_warp'), dataset_usage(Thread, Direction, Dataset, 'model', '12'), execute(Thread, Time, Duration, Disposition, Executable), format_time(atom(DayOfWeek), '%u', Time), DayOfWeek = '5'. -TODO format this multiline, perhaps remove unused bindings - - - - -
    - -
    amazon simpledb -restricted beta access... dunno if i will get any access - i have -none so far, though I have applied. - -From reading a bit about it, my impressions are that this will prove to be -a key->value lookup mechanism with poor support for going the other way -(eg. value or value pattern or predicate-on-value -> key) or for doing -joins (so rather like a hash table - which then makes me say 'why not also -investigate last year's buzzword of DHTs?'. I think that these additional -lookup mechanisms are probably necessary for a lot of the -query patterns. - - - -For some set of queries, though, key -> value lookup is sufficient; and -likely the set of queries that is appropriate to this model varies depending -on how the key -> value model is laid out (i.e. what gets to be a key -and what is its value? do we form a hierarchy from workflow downwards?) - - -
    - - -
    graphviz - -This is a very different approach that is on the boundaries of relevance. - - -goal: produce an annotated graph showing the procedures and the -datasets, with appropriate annotation of identifiers and -descriptive text (eg filenames, procedure names, executable names) that -for small (eg. fmri sized workflows) its easy to get a visual view of -whats going on. - - -don't target anything much bigger than the fmri example for this. -(though there is maybe some desire to produce larger visualisations for -this - perhaps as a separate piece of work. eg could combine foreach -into single node, datasets into single node) - - -perhaps make subgraphs by the various containment relationships: -datasets in same subgraph as their top level parent; -app procedure invocations in the same subgraph as their compound -procedure invocation. - -
    -
    - -
    Comparison with related work that our group has done -before -
    -vs VDS1 VDC -gendax - VDS1 has a tool gendax which provides -various ways of accessing data from the command line. Eg. prov challenge -question 1 very easily answered by this. - - -two points I don't like that should discuss here: i) the metadata schema -(I claim there doesn't need to be a generic metadata schema at all - -when applications decide they want to store certain metadata, they declare -it in the database); and ii) the mixed-model - this is discussed a bit in -the 'no general query language' section. consolidate/crosslink. - -
    - - -
    vs VDL provenance paper figure 1 schema - -The significant differences are: -(TODO perhaps produce a diagram for comparison. could use same diagram -differently annotated to indicate trees in the XML section and also -in the transitivity discussion section) - - -the 'annotation' model - screw that, go -native -the dataset containment model, which doesn't exist in the -virtual dataset model. - - -workflow object has a fromDV and toDV field. what are -those meant to mean? In present model, there isn't any base data for a workflow -at the moment - everything can be found in the descriptions of its -components (such as files used, start time, etc). (see notes on -compound procedure containment with model of a workflow as a compound -procedure) - -invocation to call to procedure chain. this chain looks different. -there are executes (which look like invocations/calls) and procedure names -(which do not exist as primary objects because I am not storing -program code). kickstart records and execute2 records would be more like -the annotations you'd get from the annotation part, with the call being -more directly associated with the execute object. - -
    -
    -
    Questions/Discussion points - -
    metadata - -discourse analysis: Perhaps the word 'metadata' should be banned in -this document - it implies that there is -some special property that distinguishes it sufficiently from normal -data such that it must be treated differently from different data. -I don't believe this to be the case. - - -script prov-mfd-meta-to-xml that generates (fake) -metadata record in XML like this: -$ ./prov-mfd-meta-to-xml 123 -<headermeta> - <dataset>123</dataset> - <bitspixel>16</bitspixel> - <xdim>256</xdim> - <ydim>256</ydim> - <zdim>128</zdim> - <xsize>1.000000e+00</xsize> - <ysize>1.000000e+00</ysize> - <zsize>1.250000e+00</zsize> - <globalmaximum>4095</globalmaximum> - <globalminimum>0</globalminimum> -</headermeta> - - - -
    metadata random notes - -metadata: there's a model of arbitrary metadata pairs being -associated with arbitrary objects. -there's another model (that I tend to -favour) in that the metadata schema is more defined than this - eg in i2u2 -for any particular elab, the schema for metadata is fairly well defined. - - -eg in cosmic, there are strongly typed fields such as "blessed" or -"detector number" that -are hard-coded throughout the elab. whilst the VDS1 VDC can deal with -arbitrary typing, that's not the model that i2u2/cosmic is using. need to be -careful to avoid the inner-platform effect here especially - "we need a -system that can do arbitrarily typed metadata pairs" is not actually a -requirement in this case as the schema is known at application build time. -(note that this matters for SQL a lot, not so much for plain XML data model, -though if we want to specify things like 'is-transitive' properties then -in any model things like that need to be better defined) - - -fMRI provenance challenge metadata (extracted using scanheader) looks like -this: - -$ /Users/benc/work/fmri-tutorial/AIR5.2.5/bin/scanheader ./anatomy0001.hdr -bits/pixel=16 -x_dim=256 -y_dim=256 -z_dim=128 -x_size=1.000000e+00 -y_size=1.000000e+00 -z_size=1.250000e+00 - -global maximum=4095 -global minimum=0 - - -
    - -
    - - -
    The 'preceeds' relation - -
    Provenance of hierarchical datasets - - - - -One of the main provenance queries is whether some entity (a -data file or a procedure) was influenced by some other entity. - - - -In VDS1 a workflow is represented by a bipartite DAG where one -vertex partition is files and the other is procedures. - - - -The more complex data structures in Swift make the provenance graph -not so straightforward. Procedures input and output datasets that may -be composed of smaller datasets and may in turn be composed into larger -datasets. - - - -For example, a dataset D coming out of a procedure P may form a part -of a larger dataset E. Dataset E may then be an input to procedure Q. -The ordering is then: - - P --output--> D --contained-by-> E --input--> Q - - - - -Conversely, a dataset D coming out of a procedure P may contain a -smaller dataset E. Dataset E may then be used as an input to procedure -Q. - - P --output--> D --contains--> E --input--> Q - - - - -So the contains relation and its reverse, the contained-by relation, do not -in the general case seem to give an appropriate preceeds relation. - - -so: i) should Q1<->Q be a bidirection dependency (in which case we - no longer have a DAG, which causes trouble) - -or - - ii) the dependency direction between Q1 and Q depends on how Q and Q1 -were constructed. I think this is the better approach, because I think -there really is some natural dependency order. - -If A writes to Q1 and Q1 is part of Q then A->Q1->Q -If A writes to Q and Q1 is part of Q then A->Q->Q1 - -So when we write to a dataset, we need to propagate out the dependency -from there (both upwards and downwards, I think). - -eg. if Q1X is part of Q1 is part of Q -and A writes to Q1, then Q1X depends on Q1 and Q depends on Q1. - - - - - - - - - -Various ways of doing closure - we have various relations in the graph -such as dataset containment and procedure input/output. Need to figure out -how this relates to predecessor/successors in the provenance sense. - - -A( -Also there are multiple levels of tracking (see the section on that): - -If an app procedure produces eg -volume v, consisting of two files v.img and v.hdr (the fmri example) -then what is the dependency here? I guess v.img and v.hdr is the -output... (so in the present model there will never be -downward propagation as every produced dataset will be produced out of -base files. however its worth noting that this perhaps not always the -case...) - -Alternatively we can model at the level of the app procedure, which in -the above case returns a volume v. - -I guess this is similar to the case of the compound procedures vs -contained app procedures... - -If we model at the level of files, then we don't really need to know -about higher datasets much? - -Perhaps for now should model at level of procedure calls -)A - -List A()A above as an issue and pick one choice - for now, lowest=file -production, so that all intermediate and output datasets will end up -with a strictly upward dependency - -This rule does not deal with input-only datasets (that is, datasets -which we do not know where they came from). It would be fairly natural -with the above choice to again make dependencies from files upward. - -So for now, dataset dependency rule is: - - * parent datasets depend on their children. - -Perhaps? - - - - -
    - -
    Transitivity of relations in query language - -One of my biggest concerns in query languages such as SQL and XPath -is lack of decent transitive query ability. - - -I think we need a main relation, the preceeds -relation. None of the relations defined in the source provenance data -provides this relation. - -The relation needs to be such that if any dataset or program Y that -contributed to the production of any other dataset or program Y, then -X preceeds Y. - - -We can construct pieces of this relation from the existing relations: - -There are fairly simple rules for procedure inputs and -outputs: -A dataset passed as an input to a procedure preceeds that procedure. -Similarly, a procedure that outputs a dataset preceeds that dataset. - - - -Hierarchical datasets are straightforward to describe in the present -implementation. Composite data structures are always described in terms -of their members, so the members of a data structure always preceed -the structures that contain them. [not true, i think - we can pass a -struct into a procedure and have that procedure populate multiple -contained files... bleugh] - - - -The relation is transitive, so the presence of some relations by the -above rules will imply the presence of other relations to ensure -transitivity. - - - -
    -
    - - -
    Unique identification of provenance objects - - -A few issues - what are the objects that should be identified? (semantics); -and how should the objects be identified? (syntax). - -
    provenence object identifier syntax - -For syntax, I favour a URI-based approach and this is what I have -implemented in the prototypes. URIs rovide a ready made system for -identifying different kinds of objects in different ways within the -same syntax. -which should be useful for the querys that want to do that. -file, gsiftp URIs for filenames. probably should be normalising file -URIs to refer to a specific hostname? otherwise they're fairly -meaningless outside of one host... -also, these name files but files are mutable. - - -its also fairly straightforward to subsume other identifier schemes into -URIs (for example, that is already done for UUIDs, in RFC4122). - - -for other IDs, such as workflow IDs, a tag or uuid URI would be nice. - - -cite: RFC4151 -
    -The tag algorithm lets people mint -- create -- identifiers that no one else using the same algorithm could ever mint. It is simple enough to do in your head, and the resulting identifiers can be easy to read, write, and remember. The identifiers conform to the URI (URL) Syntax. -
    -
    - -cite: RFC4122 -
    -This specification defines a Uniform Resource Name namespace for -UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally -Unique IDentifier). A UUID is 128 bits long, and requires no central -registration process. -
    -
    - -
    tag URIs - - -tag URIs for identifiers of provenance objects: - - - -all URIs allocated according to this section are labelled beginning with one -of: - -tag:benc at ci.uchicago.edu,2007:swift: -tag:benc at ci.uchicago.edu,2008: - - - - -for datasets identified only within a run (that is, for example, anything -that doesn't have a filename): -tag:benc at ci.uchicago.edu,2007:swift:dataset:TIMESTAMP:SEQ -with TIMESTAMP being a timestamp of sometime near the start of the run, -intending to be a unique workflow id (probably better to use the -run-id) -and SEQ being a sequence number. However, shouldn't really be pulling any -information out of these time and seq fields. - - -for executes - this is based on the karajan thread ID and the log base -filename (which is assumed to be a globally unique identifying string): -tag:benc at ci.uchicago.edu,2007:swiftlogs:execute:WFID:THREAD with, -as for datasets, WFID is a workflow-id-like entity. - - -
    - - -
    - -
    Dataset identifier semantics - -At present, dataset identifiers are formed uniquely for every -dataset object created in the swift runtime (unique across JVMs as well -as within a JVM). - -This provides an overly sensitive(?) identity - datasets -which are the same will be given different dataset identifiers at -different times/places; although two different datasets will never be -given the same identifier. - - -A different approach would be to say 'datasets are made of files, -so we want to identify files, and files already have identiers called -filenames'. - -I think this approach is also insufficient. - -The assertion 'datasets are made of files' is not correct. Datasets -come in several forms: typed files, typed simple values, and typed -collections of other datasets. Each of these needs a way to identify it. - - - -Simple values are probably the easiest to identify. They can be identified -by their own value and embedded within a suitable URI scheme. For example, -a dataset representing the integer 7 could be identified as: - -tag:benc at ci.uchicago.edu,2008:swift:types:int:7 - -This would have the property that all datasets representing the integer -7 would be identical (that is, have the same identifier). - - - -Collections of datasets are more complicated. One interesting example of -something that feels to me quite similar is the treatment of directories -in hash-based file systems, such as git. In this model, a collection of -datasets would be represented by a hash of a canonical representation of -its contenst, for example, a dataset consisting of a three element array -of three files in this order: "x-foo:red", "x-foo:green" and "x-foo:blue" -might be represented as: - -tag:benc at ci.uchicago.edu,2008:collection:QHASH - -where: - -QHASH := sha1sum(QLONG) - -QLONG := "[0] x-foo:red [1] x-foo:green [2] x-foo:blue" - -This allows a repeatable computation of dataset identifiers given -only knowledge of the contents of the dataset. Specifically it does -not rely on a shared database to map content to identifier. However, -it can only be computed when the content of the dataset is fully known -(roughly equivalent to when the dataset is closed in the Swift -runtime) - - - -For identifying a dataset that is a file, there are various properties. -Filename is one property. File content is another property. It seems -desirable to distinguish between datasets that have the same name yet -have different content, whilst identifying datasets that have the same -content. To this end, an identifier might be constructed from both the -filename and a hash of the content. - - - - -for prototype could deal only with files staged to local system, -so that we can easily compute a hash over the content. - - -related to taking md5sums, kickstart provides the first few bytes -of certain files (the executable and specified input and output files); -whilst useful for basic sanity checks, there are very strong correlations -with magic numbers and common headers that make this a poor content -identifying function. perhaps it should be absorbed as dataset metadata if -its available? - - - -TODO the following para needs to rephrase as justification for -having identities for dataset collections ::: at run-time when can we -pick up the -identities from other runs? pretty much we want identity to be expressed -in some way so that we can get cross-run linkup. -how do we label a dataset such that we can annotate it - eg in fmri -example, how do we identify the input datasets (as file pairs) rather than -the individual files? - -Its desirable to give the same dataset the same identifier in multiple -runs; and be able to figure out that dataset identifier outside of a run, -for example for the purposes of dealing with metadata that is annotating -a dataset. - -
    - -
    File content tracking - -identify file contents with md5sum (or other hash) - this is somewhat -expensive, but without it we have (significantly) lessened belief in what the -contents of a file are - we would otherwise, I think, be using only names -and relying on the fact that those names are primary keys to file content -(which is not true in general). -so this should be perhaps optional. plus where to do it? various places... -in wrapper.sh? - - -References here for using content-hashes: -git, many of the DHTs (freenet, for example - amusing to cite the classic -freenet gpl.txt example) - -
    - -
    - -
    Type representation - -how to represent types in this? for now use names, but that doesn't -go cross-program because we can define a different type with the same -name in every different program. hashtree of type definitions? - -
    -
    representation of workflows - -perhaps need a workflow object that acts something like a namespace -but implicitly definted rather than being user labelled (hence capturing -the actual runtime space rather than what the user claims). that's the -runID, I guess. - - -Also tracking of workflow source file. Above-mentioned reference to -tracking file contents applies to this file too. - -
    -
    metadata extraction - -provenance challenge I question 5 reports about pulling fields out of the -headers of one of the input files. There's a program, scanheader, that -extracts this info. Related but not actually useful, I think, for this -question is that header fields could be mapped into SwiftScript if we -allowed value+file simultaneous data structures. - -
    - -
    source code recreation - -should the output of the queries be sufficient to regenerate the -data? the most difficult thing here seems to be handling data -sets - we have the mapping tree for a dataset, but what is the right -way to specify that in swift syntax? maybe need mapper that takes a -literal datastructure and maps the filenames from it. though that -doesn't account for file contents (so this bit of this point is -the file contents issue, which should perhaps be its own chapter -in this file) - -
    -
    Input parameters - -Should also work on workflows which take an input parameter, so that we -end up with the same output file generated several times with different -output values - eg pass a string as a parameter and write that to -'output.txt' - every time we run it, the file will be different, and we'll -have multiple provenance reports indicating how it was made, with different -parameters. that's a simple demonstration of the content-tracking which -could be useful. - - -If we're tracking datasets for simple values, I think we get this -automatically. The input parameters are input datasets in the same way -that input files are input datasets; and so fit into the model in the -same way. - - -
    - - -
    - -
    Open Provenance Model (OPM) -
    OPM-defined terms and their relation to Swift - -OPM defines a number of terms. This section describes how those terms -relate to Swift. - - -artifact: This OPM term maps well onto the internal Swift representation -of DSHandles. Each DSHandle in a Swift run is an -OPM artifact, and each OPM artifact in a graph is a DSHandle. - -collection: OPM collections are a specific kind of artifact, containing -other artifacts. This corresponds with DSHandles for composite data types -(structs and arrays). OPM has collection accessors and collection -constructors which correspond to the [] and -. operators (for accessors) and various assignment -forms for constructors. - - -process: An OPM process corresponds to a number of Swift concepts (although -they are slowly converging in Swift to a single concept). Those concepts -are: procedure invocations, function calls, and operators. - - -agent: There are several entities which can act as an agent. At the -highest level where only Swift is involved, a run of the -swift commandline client is an agent which drives -everything. Some other components of Swift may be regarded as agents, -such as the client side wrapper script. For present OPM work, the -only agent will be the Swift command line client invocation. - - -account: For present OPM work, there will be one account per workflow run. -In future, different levels of granularity that could be expressed through -different accounts might include representing compound procedure calls as -processes vs representing atomic procedures calls explicitly. - - -OPM graph: there are two kinds of OPM graph that appear interesting and -straightforward to export: i) of entire provenance database (thus containing -multiple workflow runs); ii) of a single run - -
    -
    OPM links -Open Provenance Model at ipaw.info -
    - -
    Swift specific OPM considerations - - -non-strictness: Swift sometimes lazily constructs collections (leading to -the notion in Swift of an array being closed, which means that we know no -more contents will be created, somewhat like knowing we've reached the end -of a list). It may be that an array is never closed during a run, but that -we still have sufficient provenance information to answer useful queries -(for example, if we specify a list [1:100000] and only refer to the 5th -element in that array, we probably never generate most of the DSHandles... -so an explicit representation of that array in terms of datasets cannot be -expressed - though a higher level representation of it in terms of its -constructor parameters can be made) (?) - - - -aliasing: (this is related to some similar ambiguity in other parts of -Swift, to do with dataset roots - not provenance related). It is possible to -construct arrays by explicitly listing their members: - -int i = 8; -int j = 100; -int a[] = [i,j]; -int k = a[1]; -// here, k = 8 - -The dataset contained in i is an artifact (a literal, so -some input artifact that has no creating process). The array -a is an artifact created by the explicit array construction -syntax [memberlist] (which is an OPM process). If we -then model the array accessor syntax a[1] as an OPM -process, what artifact does it return? The same one or a different one? -In OPM, we want it to return a different artifact; but in Swift we want this -to be the same dataset... (perhaps explaining this with int -type variables is not the best way - using file-mapped data might be better) -TODO: what are the reasons we want files to have a single dataset -representation in Swift? dependency ordering - definitely. cache management? -Does this lead to a stronger notion of aliasing in Swift? - - - -Provenance of array indices: It seems fairly natural to represent arrays as OPM -collections, with array element extraction being a process. However, in OPM, -the index of an array is indicated with a role (with suggestions that it might -be a simple number or an XPath expression). In Swift arrays, the index is -a number, but it has its own provenance, so by recording only an integer there, -we lose provenance information about where that integer came from - that -integer is a Swift dataset in its own right, which has its own provenance. -It would be nice to be able to represent that (even if its not standardised -in OPM). I think that needs re-ification of roles so that they can be -described; or it needs treatment of [] as being like any other binary -operator (which is what happens inside swift) - where the LHS and RHS are -artifacts, and the role is not used for identifying the member (which would -also be an argument for making array element extraction be treated more -like a plain binary operator inside the Swift compiler and runtime) - - - -provenance of references vs provenance of the data in them: the array and -structure access operators can be used to acquire DSHandles -which have no value yet, and which are then subsequently assigned. In this -usage, the provenance of the containing structure should perhaps be that it -is constructed from the assignments made to its members, rather than the -other way round. There is some subtlety here that I have not fully figured -out. - - - -Piecewise construction of collections: arrays and structs can be -constructed piecewise using . = and [] =. -how is this to be represented in OPM? perhaps the closing operation maps -to the OPM process that creates the array, so that it ends up looking -like an explicit array construction, happening at the time of the close? - - - -Provenance of mapper parameters: mapper parameters are artifacts. We can -represent references to those in a Swift-specific part of an artifacts -value, perhaps. Probably not something OPM-generalisable. - - -
    - -
    - - - -
    Processing i2u2 cosmic metadata -i2u2 cosmic metadata is extracted from a VDS1 VDC. - -TODO some notes here about how I dislike the inner-plaform effect in the -metadata part of the VDS1 VDC. - - -to launch postgres on soju.hawaga.org.uk: - -sudo -u postgres /opt/local/lib/postgresql82/bin/postgres -D /opt/local/var/db/postgresql82/defaultdb - - -and then to import i2u2 vdc data as VDC1 vdc: - - -$ /opt/local/lib/postgresql82/bin/createdb -U postgres i2u2vdc1 -CREATE DATABASE -$ psql82 -U postgres -d i2u2vdc1 < work/i2u2.vdc -gives lots of errors like this: -ERROR: role "portal2006_1022" does not exist -because indeed that role doesn't exist -but I think that doesn't matter for these purposes - everything will end -up being owned by the postgres user which suffices for what I want to do. - - - - - -annotation tables are: - - public | anno_bool | table | postgres 29214 rows - this is boolean values - - public | anno_call | table | postgres 0 rows -- this is a subject table. also has did - - public | anno_date | table | postgres 52644 rows - this is date values - - public | anno_definition | table | postgres 1849 rows - this is XML-embedded derivations (values / objects) - - public | anno_dv | table | postgres 0 rows -- this is a subject table. also has did - - public | anno_float | table | postgres 27966 rows - this is float values - - public | anno_int | table | postgres 58879 rows - this is int values - - public | anno_lfn | table | postgres 411490 rows - this is the subject record for LFN subjects - subjects have an - mkey (predicate) column - - public | anno_lfn_b | table | postgres -this appears to be keyed by did field - ties dids to what looks like -LFNs - - public | anno_lfn_i | table | postgres - public | anno_lfn_o | table | postgres -likewise these two - - public | anno_targ | table | postgres -is this a subject table? it has an mkey value that always appears to be -'description' and then has a name column which lists invocation parameter -names and ties them to dids. - - public | anno_text | table | postgres 242824 rows -text values (objects) - - public | anno_tr | table | postgres - - - - -most of the interesting data starts in anno_lfn because data is mostly -annotating LFNs: - - - -i2u2vdc1=# select * from anno_lfn limit 1; - id | name | mkey -----+---------------------+---------- - 2 | 180.2004.0819.0.raw | origname - - - -There are 63 different mkeys (predicates in RDF-speak): - - - -i2u2vdc1=# select distinct mkey from anno_lfn; - mkey ------------------------------- - alpha - alpha_error - author - avgaltitude - avglatitude - avglongitude - background_constant - background_constant_error - bins - blessed - caption - chan1 - chan2 - chan3 - chan4 - channel - city - coincidence - comments - cpldfrequency - creationdate - date - description - detectorcoincidence - detectorid - dvname - enddate - energycheck - eventcoincidence - eventnum - expire - filename - gate - gatewidth - group - height - julianstartdate - lifetime(microseconds) - lifetime_error(microseconds) - name - nondatalines - numBins - origname - plotURL - project - provenance - radius - rawanalyze - rawdate - school - source - stacked - startdate - state - study - teacher - thumbnail - time - title - totalevents - transformation - type - year -(63 rows) - - - -so work on a metadata importer for i2u2 cosmic that will initially deal -with only the lfn records. - - - -There are 19040 annotated LFNs, with 411490 annotations in total, so about -21 annotations per LFN. - - -The typing of the i2u2 data doesn't support metadata objects -that aren't swift workflow entities - for example high schools as -objects in their own right - the same text string is stored as a value -over and over in many anno_text rows. A more generalised -Subject-Predicate-Object model in RDF would have perhaps a URI for -the high school, with metadata on files tying files to a high school and -metadata on the high school object. In SQL, that same could be modelled -in a relational schema. - - - -Conversion of i2u2 VDS1 VDC LFN/text annotations into an XML document -using quick hack script took 32mins on soju, my laptop. resulting XML -is 8mb. needed some manual massage to remove malformed embedded xml and -things like that. - -./i2u2-to-xml.sh >lfn-text-anno.xml - - -so we end up with a lot of records that look like this: - - -<lfn name="43.2007.0619.0.raw"> -<origname>rgnew.txt</origname> -<group>riogrande</group> -<teacher>Luis Torres Rosa</teacher> -<school>Escuelo Superior Pedro Falu</school> -<city>Rio Grande</city> -<state>PR</state> -<year>AY2007</year> -<project>cosmic</project> -<comments></comments> -<detectorid>43</detectorid> -<type>raw</type> -<avglatitude>18.22.8264</avglatitude> -<avglongitude>-65.50.1975</avglongitude> -<avgaltitude>-30</avgaltitude> -</lfn> - - -The translation here is not cosmic-aware - the XML tag is the mkey name from -vdc and the content is the value. So we get all the different metadata -(informal) schemas that appear to have been used, translated. - - - - -Output the entire provenance database: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic' | wc -c - 10178037 - -real 0m2.624s -user 0m2.612s -sys 0m0.348s - - - - -Select all LFN objects (which on this dataset means everything one layer -down): - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn' | wc -c - 9618818 - -real 0m2.692s -user 0m2.703s -sys 0m0.337s - - - - -Try to select an LFN that doesn't exist, by specifying a filename that is not -there: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn[@name="NOSUCHNAME"]' -<?xml version="1.0"?> -<toplevel/> - -real 0m0.867s -user 0m0.740s -sys 0m0.143s - - - - -Similar query for a filename that does exist: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn[@name="1.2005.0801.0"]' -<?xml version="1.0"?> -<toplevel> - <lfn name="1.2005.0801.0"> - <origname>C:\Documents and Settings\zsaleh\My Documents\Tera stuff\Qnet\Qnet Data\All_data_Aug_01_2005_TERA_9_Vth_1000.TXT</origname> - <group>TERA</group> - <teacher>Marcus Hohlmann</teacher> - <school>Florida Institute of Technology</school> - <city>Melbourne</city> - <state>FL</state> - <year>AY2004</year> - <project>cosmic</project> - <comments/> - <source>1.2005.0801.0</source> - <detectorid>1</detectorid> - <type>split</type> - </lfn> -</toplevel> - -real 0m0.875s -user 0m0.745s -sys 0m0.154s - - - -
    - -
    processing fMRI metadata - -for fmri, we can extract embedded image metadata using the scanheader -utility. - - -associate that with the 'volume' dataset, not with the actual image data -files. for now that means we need the datasets to have been labelled with -their ID already, which is at the moment after execution has completed. -that's fine for now with the retrospective provenance restriction of this -immediate work. see the -'cross-run dataset ID' section, for which this -also applies - we are generating dataset IDs outside of a particular run. - -
    - -
    random unsorted notes - -to put provdb in postgres instead of sqlite3: - -start as per i2u2 instructions, then /opt/local/lib/postgresql82/bin/createdb -U postgres provdb - -then: - - psql82 -U postgres -d provdb < prov-init.sql - to initialise the db. - - -on terminable, made new database that is not the default system db install, -by using existing postgres but running under my user id: - - 131 mkdir pgplay - 133 chmod 0700 pgplay/ - 135 initdb -D ~/pgplay/ - 138 postmaster -D ~/pgplay/ -p 5435 -$ createdb -p 5435 provdb -CREATE DATABASE - -now can access like this: - -$ psql -p 5435 -d provdb -provdb=# \dt -No relations found. - - -osg/gratia - how does this data tie in? - -cedps logging - potential for info there but there doesn't seem -anything particularly substantial at the moment - -
    - -
    Provenance Challenge 1 examples -
    Basic SQL -
    provch q1 - - -get the dataset id for the relevant final dataset: -sqlite> select * from dataset_filenames where filename like '%0001.jpeg'; -14976260|file://localhost/0001.jpeg - -get containment info for that file: -sqlite> select * from dataset_containment where inner_dataset_id = 14976260; -7316236|14976260 -sqlite> select * from dataset_containment where inner_dataset_id = 7316236; -[no answer] - -now need to find what contributed to those... - -> select * from dataset_usage where dataset_id=14976260; -0-4-3|O|14976260 - -> select * from dataset_usage where execute_id='0-4-3' and direction='I'; -0-4-3|I|4845856 -qlite> select * from dataset_usage where dataset_id=4845856 and direction='O'; -0-3-3|O|4845856 - -sqlite> select * from dataset_usage where execute_id='0-3-3' and direction='I'; -0-3-3|I|3354850 -0-3-3|I|6033476 - -qlite> select * from dataset_usage where (dataset_id=3354850 or dataset_id=6033476) and direction='O'; -0-2|O|3354850 - -sqlite> select * from dataset_usage where execute_id='0-2' and direction='I';0-2|I|4436324 - -sqlite> select * from dataset_usage where dataset_id=4436324 and direction='O'; -[no answer] - -so here we have run out of places to keep going. however, I think this 4436324 -is not an input - its related to another dataset. so we need another rule for -inference here... - - - - -
    - -
    prov ch q4 -prov ch q4 incremental solutions: - -first cut: -this will select align_warp procedures and their start times. does not -select based on parameters, and does not select based on day of week. -(the former we don't have the information for; the latter maybe don't have -the information in sqlite3 to do - or maybe need SQL date ops and SQL dates -rather than unix timestamps) - -sqlite> select id, starttime from invocation_procedure_names, executes where executes.id = invocation_procedure_names.execute_id and procedure_name='align_warp'; - -Next, this will display the day of week for an invocation: - -select id, strftime('%w',starttime, 'unixepoch') from executes,invocation_procedure_names where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id; -0-0-3|5 -0-0-4|5 -0-0-1|5 -0-0-2|5 - - -And this will match day of week (sample data is on day 5, which is a -Friday, not the day requested in the question): - -sqlite> select id from executes,invocation_procedure_names where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5'; -0-0-3 -0-0-4 -0-0-1 -0-0-2 - - - -Now we bring in input data binding: we query which datasets were passed in -as the model parameter for each of the above found invocations: - -sqlite> select executes.id, dataset_usage.dataset_id from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model'; -0-0-3|11032210 -0-0-4|13014156 -0-0-1|14537849 -0-0-2|16166946 - -though at the moment this doesn't give us the value of the parameter. - - -so now pull in the parameter value: - - -sqlite> select executes.id, dataset_usage.dataset_id, dataset_usage.value from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model'; -0-0-3|11032210|12 -0-0-4|13014156|12 -0-0-1|14537849|12 -0-0-2|16166946|12 - - - - -Now we can select on the parameter value and get our final answer: - -sqlite> select executes.id from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model' and dataset_usage.value=12; -0-0-3 -0-0-4 -0-0-1 -0-0-2 - -Note that in SQL in general, -we *don't* get typing of the parameter value here so can't do anything -more than string comparison. For example, we couldn't check for the -parameter being greater than 12 or similar. In sqlite, it happens that -its typing is dynamic enough to allow the use of relational operators like -> on fields no matter what their declared type, because declared type is -ignored. This would stop working if stuff was run on eg postgres or mysql, -I think. - -
    -
    prov ch metadata -metadata: in the prov challenge, we annotate (some) files with -their header info. in the provenance paper, we want annotations on more -than just files. - -for prov ch metadata, define a scanheader table with the result of -scanheader on each input dataset, but do it *after* we've done the -run (because we're then aware of dataset IDs) -There's a representation question here - the metadata is about a volume -dataset which is a pair of files, not about a header or image file separately. -how to represent this? we need to know the dataset ID for the volume. at -the moment, we can know that after a run. but this ties into the -identification of datasets outside of an individual run point - move this -paragraph into that questions/discussions section. - - -should probably for each storage method show the inner-platform style of -doing metadata too; associated queries to allow comparison with the -different styles; speeds of metadata query for large metadata collections -(eg. dump i2u2 cosmic metadata for real cosmic VDC) - -
    -
    - -
    SQL with transitive closures -
    -prov ch question 1: - -$ sqlite3 provdb -SQLite version 3.3.17 -Enter ".help" for instructions -sqlite> select * from dataset_filenames where filename like '%0001.jpeg'; -14976260|file://localhost/0001.jpeg --- can query keeping relations -sqlite> select * from trans where after=14976260; -0-4-3|14976260 -4845856|14976260 -0-3-3|14976260 -3354850|14976260 -6033476|14976260 -4825541|14976260 -7061626|14976260 -0-2|14976260 -4436324|14976260 -11153746|14976260 -655223|14976260 -5169861|14976260 -6487148|14976260 -5772360|14976260 -4910675|14976260 -7202698|14976260 -12705705|14976260 -2088036|14976260 -13671126|14976260 -14285084|14976260 -12896050|14976260 -0-1-3|14976260 -0-1-4|14976260 -0-1-2|14976260 -0-1-1|14976260 -2673619|14976260 -9339756|14976260 -10682109|14976260 -8426950|14976260 -16032673|14976260 -2274050|14976260 -1461238|14976260 -13975694|14976260 -9282438|14976260 -12766963|14976260 -8344105|14976260 -9190543|14976260 -14055055|14976260 -2942918|14976260 -12735302|14976260 -7080341|14976260 -0-0-3|14976260 -0-0-4|14976260 -0-0-2|14976260 -0-0-1|14976260 -2307300|14976260 -11032210|14976260 -16166946|14976260 -14537849|14976260 -13014156|14976260 -6435309|14976260 -6646123|14976260 --- or can query without relations: -sqlite> select before from trans where after=14976260; -0-4-3 -4845856 -0-3-3 -3354850 -6033476 -4825541 -7061626 -0-2 -4436324 -11153746 -655223 -5169861 -6487148 -5772360 -4910675 -7202698 -12705705 -2088036 -13671126 -14285084 -12896050 -0-1-3 -0-1-4 -0-1-2 -0-1-1 -2673619 -9339756 -10682109 -8426950 -16032673 -2274050 -1461238 -13975694 -9282438 -12766963 -8344105 -9190543 -14055055 -2942918 -12735302 -7080341 -0-0-3 -0-0-4 -0-0-2 -0-0-1 -2307300 -11032210 -16166946 -14537849 -13014156 -6435309 -6646123 - - - -
    - - -
    - -
    - -
    Representation of dataset containment and procedure execution in r2681 and how it could change. - - -Representation of processes that transform one dataset into another dataset -at present only occurs for app procedures, in logging of -vdl:execute invocations, in lines like this: - -2009-03-12 12:20:29,772+0100 INFO vdl:parameterlog PARAM thread=0-10-1 direction=input variable=s provenanceid=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000033 - -and dataset containment is represented at closing of the containing DSHandle by this: - -2009-03-12 12:20:30,205+0100 INFO AbstractDataNode CONTAINMENT parent=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000020 child=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000086 -2009-03-12 12:20:30,205+0100 INFO AbstractDataNode ROOTPATH dataset=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000086 path=[2] - - - - -This representation does not represent the relationship between datasets when -they are related by @functions or operators. Nor does it represent causal -relationships between collections and their members - instead it represents -containment. - - - -Adding representation of operators (including array construction) and of - at function invocations would give substantially more information about -the provenance of many more datasets. - - -
    - -
    - Deleted: branches/release-0.92/docs/quickstartguide.xml =================================================================== --- branches/release-0.92/docs/quickstartguide.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/quickstartguide.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,272 +0,0 @@ - - - - -
    - - Swift Quick Start Guide - Source Control $LastChangedRevision$ - - - - - - - The impatient may find the Swift Really Quick Start - Guide to be more convenient. - - This guide describes the steps needed to download, install, - configure, and run the basic examples for Swift. If you are - using a pre-installed version of Swift, you can skip - directly to the configuration - section. - - - - - - - - Downloading a Swift Distribution - - - - There are three main ways of getting the Swift implementation: stable releases, nightly builds, and the source code repository. - - - - - Stable Releases - - - - Stable releases can be obtained from the Swift download page: - Swift - Downloads Page. Once you downloaded the package, please - move to the install section. - - - - - - Nightly Builds - - - - Swift builds and tests are being run every day. The Swift - downloads page contains links to the latest build and - test page. The nightly builds reflect a development version of - the Swift code and should not be used in production mode. After - downloading a nightly build package, please continue to the - install section. - - - - - - Source Repository - - - - Details about accessing the Swift source repository together with - build instructions are available on the Swift - downloads page. Once built, the dist/swift-svn directory - will contain a self-contained build which can be used in place or moved to a different location. - You should then proceed to the configuration section. - - - - - - - Installing a Swift Binary Package - - - - Simply unpack the downloaded package (swift-<version>.tar.gz) into a - directory of your choice: - - -> tar swift-<version>.tar.gz - - - This will create a swift-<version> directory - containing the build. - - - - - - Configuring Swift - - - - This section describes configuration steps that need to be taken in - order to get Swift running. Since all command line tools provided - with Swift can be found in the bin/ directory of the Swift distribution, it may - be a good idea to add this directory to your PATH - environment variable: - - -> export PATH=/path/to/swift/bin:$PATH - - - - Grid Security - For local execution of jobs, no grid security configuration - is necessary. - - However, when submitting jobs to a remote machine using Globus - Toolkit services, Swift makes use of the - - Grid Security Infrastructure (GSI) for authentication - and authorization. The requirements for this are detailed in - the following sections. Note that GSI is not required to be - configured for local execution (which will usually be the - case when first starting with Swift). - - - - - User Certificate - - - GSI requires a certificate/private key - pair for authentication to - Globus Toolkit - services. The certificate and private key should - be placed into the ~/.globus/usercert.pem and ~/.globus/userkey.pem files, - respectively. - - - - - - - - Certificate Authorities Root Certificates - - - - The Swift client libraries are generally required to authenticate - the services to which they connect. This process requires the - presence on the Swift submit site of the root certificates used - to sign the host certificates of services used. These root - certificates need to be installed in either (or both) the - ~/.globus/certificates - and /etc/grid-security/certificates - directories. A package with the root certificates of the - certificate authorities used in the TeraGrid can be found - here. - - - - - - - - - Swift Properties - - - - A Swift properties file (named swift.properties) can be used to - customize certain configuration aspects of Swift. A shared - version of this file, etc/swift.properties - in the installation directory - can be used to provide installation-wide defaults. A per-user - properties file, ~/.swift/swift.properties can be used for - user specific settings. Swift first loads the shared - configuration file and, if present, the user configuration file. - Any properties not explicitly set in the user configuration file - will be inherited from the shared configuration file. Properties - are specified in the following format: - - -name=value - - - For details about the various properties Swift accepts, please - take a look at the Swift - Properties Section in the Swift - User Guide. - - - - - - - - - Running Swift Examples - - - - The Swift examples can be found in the examples directory in the Swift distribution. - The examples are written in the SwiftScript - language, and have .swift as - a file extension. - - - - - - The Grid Security Infrastructure, which Swift uses, works with - limited time certificates called proxies. These proxies can be - generated from your user certificate and private key using one of - grid-proxy-init or - cog-proxy-init (the latter being a Java Swing - interface to the former). - - - - - - Execution of a Swift workflow is done using the - swift command, which takes the Swift - workflow file name as an argument: - - -> cd examples/swift -> swift - - - The Swift - Command Options Section in the Swift - User Guide contains details about the various options of the - swift. - - - - -
    Deleted: branches/release-0.92/docs/reallyquickstartguide.xml =================================================================== --- branches/release-0.92/docs/reallyquickstartguide.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/reallyquickstartguide.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,109 +0,0 @@ - - - - -
    - - Swift Really Quick Start Guide - Source control $LastChangedRevision$ - - - - - - - This guide is a compressed version of the Swift Quick Start - Guide. - - - - - - - - Swift Really Quick Start Guide - - - - - - - Download - Swift. - - - - - - - - Unpack it and add the swift-xyz/bin directory to your - PATH. - - - - - - - - Make sure you have your user certificate, a valid GSI proxy - certificate, and the proper CA root certificates in either - ~/.globus/certificates or - /etc/grid-security/certificates. - - - - - - - - Edit swift-xyz/etc/swift.properties. You - should add your numeric IP address there - (ip.address=x.y.z.w). - - - - - - - - Use the example site catalog and transformation catalog (they - are configured for local submission): - - -cd swift-xyz/etc -cp sites.xml.example sites.xml -cp tc.data.example tc.data - - - - - - - - - Use swift file.dtm to compile and execute - file.dtm. - - - - - - - - Use swift -resume file-<runid>.?.rlog - file.dtm to resume a failed run. - - - - - - - -
    Deleted: branches/release-0.92/docs/swift-site-model.fig =================================================================== --- branches/release-0.92/docs/swift-site-model.fig 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/swift-site-model.fig 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,53 +0,0 @@ -#FIG 3.2 Produced by xfig version 3.2.5 -Landscape -Center -Inches -Letter -100.00 -Single --2 -1200 2 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 2100 3450 4425 2025 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 2100 3675 4425 3825 -2 4 0 1 0 11 999 -1 20 0.000 0 0 7 0 0 5 - 8850 4800 4200 4800 4200 675 8850 675 8850 4800 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 2025 8400 2025 8400 2775 7425 2775 7425 2025 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 2850 8400 2850 8400 3600 7425 3600 7425 2850 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 3675 8400 3675 8400 4425 7425 4425 7425 3675 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 1200 8400 1200 8400 1950 7425 1950 7425 1200 -2 2 0 1 0 6 500 -1 20 0.000 0 0 -1 0 0 5 - 525 3000 2025 3000 2025 4050 525 4050 525 3000 -2 2 0 1 0 6 100 -1 20 0.000 0 0 -1 0 0 5 - 4500 1350 6300 1350 6300 2700 4500 2700 4500 1350 -2 2 0 1 0 6 100 -1 20 0.000 0 0 -1 0 0 5 - 4500 3225 6375 3225 6375 4425 4500 4425 4500 3225 -2 4 0 1 0 11 55 -1 20 0.000 0 0 7 0 0 5 - 8850 5850 4200 5850 4200 5100 8850 5100 8850 5850 -2 4 0 1 0 11 55 -1 20 0.000 0 0 7 0 0 5 - 8850 6675 4200 6675 4200 6075 8850 6075 8850 6675 -3 0 0 1 0 7 50 -1 -1 0.000 0 0 0 2 - 7350 1575 6375 1950 - 0.000 0.000 -3 0 0 1 0 7 50 -1 -1 0.000 0 0 0 2 - 7350 1725 6450 3975 - 0.000 0.000 -4 0 0 50 -1 0 12 0.0000 4 150 450 750 3300 Swift\001 -4 0 0 50 -1 0 12 0.0000 4 150 1155 750 3555 commandline\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 750 3810 client\001 -4 0 0 50 -1 0 12 0.0000 4 195 1500 4725 2100 shared filesystem\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 4800 3900 LRM\001 -4 0 0 50 -1 0 12 0.0000 4 150 1215 7350 900 Worker nodes\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 6525 1425 Posix\001 -4 0 0 50 -1 0 12 0.0000 4 150 1065 5325 5475 Another site\001 -4 0 0 50 -1 0 12 0.0000 4 150 1065 5250 6450 Another site\001 -4 0 0 50 -1 0 12 0.0000 4 150 810 2475 2475 remote fs\001 -4 0 0 50 -1 0 12 0.0000 4 105 600 2475 2730 access\001 -4 0 0 50 -1 0 12 0.0000 4 195 1260 2400 4125 job submission\001 -4 0 0 50 -1 0 12 0.0000 4 195 915 2400 4380 eg GRAM\001 -4 0 0 50 -1 0 12 0.0000 4 195 1080 3075 3000 eg. GridFTP\001 Deleted: branches/release-0.92/docs/swift-site-model.png =================================================================== (Binary files differ) Deleted: branches/release-0.92/docs/tutorial-live.xml =================================================================== --- branches/release-0.92/docs/tutorial-live.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/tutorial-live.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,982 +0,0 @@ - - - -
    - - A Swift Tutorial for ISSGC07 - - - Introduction - -This tutorial is intended to introduce new users to the basics of Swift. -It is structured as a series of small exercise/examples which you can -try for yourself as you read along. - - This is version: $LastChangedRevision$ - - -Environment setup - -First set up the swift environment: - - - -$ cp ~benc/workflow/vdsk-0.1-r877/etc/tc.data ~ -$ cp ~benc/workflow/vdsk-0.1-r877/etc/sites.xml ~ -$ export PATH=$PATH:~benc/workflow/vdsk-0.1-r877/bin - - - - - A first workflow - -The first example program uses an image processing utility to perform -a visual special effect on a supplied file. - - -Here is the program we will use: - - - -type imagefile; - -(imagefile output) flip(imagefile input) { - app { - convert "-rotate" "180" @input @output; - } -} - -imagefile puppy <"input-1.jpeg">; -imagefile flipped <"output.jpeg">; - -flipped = flip(puppy); - - - - - -This simple workflow has the effect of running this command: -convert -rotate 180 input-1.jpeg output.jpeg - - -ACTION: First prepare your working environment: - - - -$ cp ~benc/workflow/input-1.jpeg . - -$ ls *.jpeg -input-1.jpeg - - - -ACTION: Open input-1.jpeg - - -You should see a picture. This is the -picture that we will modify in our first workflow. - - -ACTION: use your favourite text editor to put the above SwiftScript -program into a file called -flipper.swift - - -Once you have put the program into flipper.swift, you can execute -the workflow like this: - - - - -$ swift flipper.swift - -Swift v0.1-dev - -RunID: e1bupgygrzn12 -convert started -convert completed - -$ ls *.jpeg -input-1.jpeg -output.jpeg - - -A new jpeg has appeared - output.jpeg. - -ACTION: Open it. -You should see that the image is different from the input image - it -has been rotated 180 degress. - -The basic structure of this program is a type definition, -a procedure definition, a variable definition and -then a call to the procedure: - - -All data in SwiftScript must have a type. This line defines a new type -called imagefile, which will be the type that all of our images will be. - - - -type imagefile; - - - -Next we define a procedure called flip. This procedure will use the -ImageMagick convert application to rotate a picture around by 180 degrees. - - - -(imagefile output) flip(imagefile input) { - app { - convert "-rotate" "180" @input @output; - } -} - - - -To achieve this, it executes the ImageMagick utility 'convert', passing -in the appropriate commandline option and the name of the input and output -files. - - - -In swift, the output of a program looks like a return value. -It has a type, and also has a variable name -(unlike in most other programming languages). - - - -imagefile puppy <"input-1.jpeg">; -imagefile flipped <"output.jpeg">; - - - -We define two variables, called puppy and flipped. These variables will -contain our input and output images, respectively. - - -We tell swift that the contents of the variables will be stored on -disk (rather than in memory) in the files "input-1.jpeg" (which already -exists), and in "output.jpeg". This is called mapping -and will be discussed in more depth later. - - -flipped = flip(puppy); - - - -Now we call the flip procedure, with 'puppy' as its input and its -output going into 'flipped'. - - -Over the following exercises, we will use this relatively -simple SwiftScript program as a base for future exercises. - - - -A second program - - -Our next example program uses some more swift syntax to produce images that are -rotated by different angles, instead of flipped over all the way. - - -Here is the program in full. We'll go over it section by section. - -type imagefile; - -(imagefile output) rotate(imagefile input, int angle) { - app { - convert "-rotate" angle @input @output; - } -} - -imagefile puppy <"input-1.jpeg">; - -int angles[] = [45, 90, 120]; - -foreach a in angles { - imagefile output <single_file_mapper;file=@strcat("rotated-",a,".jpeg")>; - output = rotate(puppy, a); -} - - - -type imagefile; - - - -We keep the type definition the same as in the previous program. - - - -(imagefile output) rotate(imagefile input, int angle) { - app { - convert "-rotate" angle @input @output; - } -} - - - -This rotate procedure looks very much like the flip procedure -from the previous program, -but we have added another parameter, called angle. Angle is of type 'int', -which is a built-in SwiftScript type for integers. We use that on the -commandline instead of a hard coded 180 degrees. - - - -imagefile puppy <"input-1.jpeg">; - - - -Our input image is the same as before. - - - -int angles[] = [45, 90, 120]; - - - -Now we define an array of integers, and initialise it with three angles. - - - -foreach a in angles { - - - -Now we have a foreach loop. This loop will iterate over each of the elements -in angles. In each iteration, the element will be put in the variable 'a'. - - - - imagefile output <single_file_mapper;file=@strcat("rotated-",a,".jpeg")>; - - - -Inside the loop body, we have an output variable that is mapped differently -for each iteration. We use the single_file_mapper and the @strcat function -to construct a filename and then map that filename to our output variable. - - - - output = rotate(puppy, a); -} - - -Now we invoke rotate, passing in our input image and the angle to -use, and putting the output in the mapped output file. This will happen -three times, with a different output filename and a different angle -each time. - - - -ACTION: Put the program source into a file called in rotate.swift and -execute it with the swift command, like we did for flipper.swift above. - - - -$ ls rotated* -rotated-120.jpeg rotated-45.jpeg rotated-90.jpeg - - - - - -Third example - - -Our third example will introduce some more concepts: complex data -types, the comma-separated values mapper, and the transformation -catalog. - - - -Here's the complete listing: - - - - -type imagefile; -type pgmfile; - -type voxelfile; -type headerfile; - -type volume { - voxelfile img; - headerfile hdr; -}; - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile output) convert(pgmfile inpgm) -{ - app { - convert @inpgm @output; - } -} - -pgmfile slice; - -imagefile slicejpeg <"slice.jpeg">; - -slice = slicer(reference, "-x", ".5"); - -slicejpeg = convert(slice); - - - -IMPORTANT! We need to make some changes to other files in addition -to putting the above source into a file. Read the following notes -carefully to find out what to change. - - -type imagefile; -type pgmfile; -type voxelfile; -type headerfile; - - - -We define some simple types - imagefile as before, as well as three new ones. - - - -type volume { - voxelfile img; - headerfile hdr; -}; - - - -Now we define a complex type to represent a brain scan. -Our programs store brain data in two files - a .img file and a .hdr file. -This complex type defines a volume type, consisting of a voxelfile and a -headerfile. - - - -volume references[] <csv_mapper;file="reference.csv">; - - - -Now that we have defined a more complex type that consists of several -elements (and hence several files on disk), we can no longer use the -same ways of mapping. Instead, we will use a new mapper, the CSV mapper. -This maps rows of a comma-separated value file into an array of complex -types. - -ACTION: Make a file called reference.csv using your -favourite text editor. This is what it should look contain (2 lines): - - -img,hdr -Raw/reference.img,Raw/reference.hdr - -Our mapped structure will be a 1 element array (because there was one -data line in the CSV file), and that element will be mapped to two -files: the img component will map to the file Raw/reference.img and the -hdr component will map to Raw/reference.hdr - - -We also need to put the Raw/reference files into the current directory -so that swift can find them. - -ACTION REQUIRED: Type the following: - - -$ mkdir Raw -$ cp ~benc/workflow/data/reference.* Raw/ - - -Now you will have the reference files in your home directory. - - - -volume reference=references[0]; - - - -We only want the single first element of the references array, so this line -makes a new volume variable and extracts the first element of references. - - - -(imagefile output) convert(pgmfile inpgm) -{ - app { - convert @inpgm @output; - } -} - - - -This procedure is like the previous flip and rotate procedures. It uses -convert to change a file from one file format (.pgm format) to another -format (.jpeg format) - - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - - - -Now we define another procedure that uses a new application called 'slicer'. -Slicer will take a slice through a supplied brain scan volume and produce -a 2d image in PGM format. - - - -We must tell Swift how to run 'slicer' by modifying the -transformation catalog. The transformation catalog -maps logical transformation names into unix executable names. - - -The transformation catalog is in your home directory, in a file called -tc.data. -There is already one entry there, for convert. - - -localhost convert /usr/bin/convert INSTALLED INTEL32::LINUX null - - -ACTION REQUIRED: Open tc.data in your favourite unix text -editor, and add a new line to configure the location of slicer. Note that -you must use TABS and not spaces to separate the fields: - - -localhost slicer /afs/pdc.kth.se/home/b/benc/workflow/slicer-swift INSTALLED INTEL32::LINUX null - - -For now, ignore all of the fields except the second and the third. -The second field 'slicer' specifies a logical transformation name and the -third specifies the location of an executable to perform that -transformation. - - -pgmfile slice; - - - -Now we define a variable which will store the sliced image. It will be -a file on disk, but note that there is no filename mapping defined. This -means that swift will choose a filename automatically. This is useful for -intermediate files in a workflow. - - - -imagefile slicejpeg <"slice.jpeg">; - - -Now we declare a variable for our output and map it to a filename. - - - -slice = slicer(reference, "-x", ".5"); - -slicejpeg = convert(slice); - - - -Finally we invoke the two procedures to slice the brain volume and -then convert that slice into a jpeg. - - -ACTION: Place the source above into a file (for example, third.swift) and -make the other modifications discussed above. Then run the workflow -with the swift command, as before. - - - -Running on another site - - -So far everything has been run on the local site. -Swift can run jobs over the grid to remote resources. It will handle the -transfer of files to and from the remote resource, and execution of jobs -on the remote resource. - - - -We will run the first flip program, but this time on a grid resource -located in chicago. - - - -First clear away the output from the first program: - - - -$ rm output.jpeg -$ ls output.jpeg -ls: output.jpeg: No such file or directory - - - -Now initialise your grid proxy, to log-in to the grid. - - - -$ grid-proxy-init - - -Now we must tell Swift about the other site. This is done through -another catalog file, the site catalog. - -The site catalog is found in sites.xml - -Open sites.xml. There is one entry in there in XML defining the -local site. Because this is the only site defined, all execution will -happen locally. - -Another sites.xml is available for use, in -~benc/workflow/sites-iceage.xml - - -ACTION: Copy ~benc/workflow/sites-iceage.xml to your home directory - and look inside. See how it differs from sites.xml. - -Now we will run the first flipper exercise again, but this time via -Globus GRAM. - -We will use this other sites file to run the first workflow. In -addition to telling swift about the other site in the sites file, -we need to tell swift where to find transformations on the new site. - -ACTION: Edit the transformation catalog and add a line to tell swift where -it can find convert. Conveniently, it is in the same path when running -locally and through GRAM. -Here is the line to add: - - - -iceage convert /usr/bin/convert INSTALLED INTEL32::LINUX null - - -Note the different between this line and the existing convert -definition in the file. All fields are the same except for the first -column, which is the site column. We say 'iceage' here instead of -localhost. This matches up with the site name 'iceage' defined in -the new site catalog, and identifies the name of the remote site. - - -Now use the same swift command as before, but with an -extra parameter to tell swift to use a different sites file: - - - -$ swift -sites.file ~benc/workflow/sites-iceage.xml flipper.swift - - - -If this runs successfully, you should now have an output.jpeg file with -a flipped picture in it. It should look exactly the same as when run locally. -You have used the same program to produce the same output, but used a remote -resource to do it. - - - - - - - -A bigger workflow example - -Now we'll make a bigger workflow that will execute a total of -15 jobs. - - - -As before, here is the entire program listing. Afterwards, we will go through -the listing step by step. - - - -type voxelfile; -type headerfile; - -type pgmfile; -type imagefile; - -type warpfile; - -type volume { - voxelfile img; - headerfile hdr; -}; - -(warpfile warp) align_warp(volume reference, volume subject, string model, string quick) { - app { - align_warp @reference.img @subject.img @warp "-m " model quick; - } -} - -(volume sliced) reslice(warpfile warp, volume subject) -{ - app { - reslice @warp @sliced.img; - } -} - -(volume sliced) align_and_reslice(volume reference, volume subject, string model, string quick) { - warpfile warp; - warp = align_warp(reference, subject, model, quick); - sliced = reslice(warp, subject); -} - - -(volume atlas) softmean(volume sliced[]) -{ - app { - softmean @atlas.img "y" "null" @filenames(sliced[*].img); - } -} - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile outimg) convert(pgmfile inpgm) -{ - app { - convert @inpgm @outimg; - } -} - -(imagefile outimg) slice_to_jpeg(volume inp, string axis, string position) -{ - pgmfile outslice; - outslice = slicer(inp, axis, position); - outimg = convert(outslice); -} - -(volume s[]) all_align_reslices(volume reference, volume subjects[]) { - - foreach subject, i in subjects { - s[i] = align_and_reslice(reference, subjects[i], "12", "-q"); - } - -} - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - -volume subjects[] <csv_mapper;file="subjects.csv">; - -volume slices[] <csv_mapper;file="slices.csv">; -slices = all_align_reslices(reference, subjects); - -volume atlas <simple_mapper;prefix="atlas">; -atlas = softmean(slices); - -string directions[] = [ "x", "y", "z"]; - -foreach direction in directions { - imagefile o <single_file_mapper;file=@strcat("atlas-",direction,".jpeg")>; - string option = @strcat("-",direction); - o = slice_to_jpeg(atlas, option, ".5"); -} - - - - -As before, there are some other changes to make to the environment -in addition to running the program. These are discussed inline below. - - - -type voxelfile; -type headerfile; - -type pgmfile; -type imagefile; - -type warpfile; - - - -We define some simple types, like in the previous programs. We add another -one for a new kind of intermediate file - a warpfile, which will be used by -some new applications that we will use. - - - - -type volume { - voxelfile img; - headerfile hdr; -}; - - - -The same complex type as before, a volume consisting of a pair of files - -the voxel data and the header data. - - - - -(warpfile warp) align_warp(volume reference, volume subject, string model, string quick) { - app { - align_warp @reference.img @subject.img @warp "-m " model quick; - } -} - - - - -Now we define a new transformation called align_warp. We haven't used -align_warp before, so we need to add in a transformation catalog entry -for it. We will be adding some other transformations too, so add those -entries now too. - - - -ACTION: Edit the transformation catalog (like in the third -exercise). Add entries for the following transformations. The table -below lists the path. You must write the appropriate syntax for -transformation catalog entries yourself, using the existing two -entries as examples. - - -Here is the list of transformations to add: - -align_warp (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/AIR/bin/align_warp) -reslice (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/AIR/bin/reslice) -softmean (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/softmean-swift) - - - -These programs come from several software packages: -the AIR (Automated Image Registration) suite -http://bishopw.loni.ucla.edu/AIR5/index.html and -FSL http://www.fmrib.ox.ac.uk/fsl/fsl/intro.html - - -Make sure you have added three entries to the transformation -catalog, listing the above three transformations and the appropriate -path - - - -(volume sliced) reslice(warpfile warp, volume subject) -{ - app { - reslice @warp @sliced.img; - } -} - - - - -This adds another transformation, called reslice. We already added the -transformation catalog entry for this, in the previous step. - - - - - -(volume sliced) align_and_reslice(volume reference, volume subject, string model, string quick) { - warpfile warp; - warp = align_warp(reference, subject, model, quick); - sliced = reslice(warp, subject); -} - - - - -This is a new kind of procedure, called a compound -procedure. A compound procedure does not call applications -directly. Instead it calls other procedures, connecting them together -with variables. This procedure above calls align_warp and then reslice. - - - - -(volume atlas) softmean(volume sliced[]) -{ - app { - softmean @atlas.img "y" "null" @filenames(sliced[*].img); - } -} - - - - -Yet another application procedure. Again, we added the transformation catalog -entry for this above. Note the special @filenames ... [*] syntax. - - - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile outimg) convert(pgmfile inpgm) -{ - app { - convert @inpgm @outimg; - } -} - - - -These are two more straightforward application transforms - - - -(imagefile outimg) slice_to_jpeg(volume inp, string axis, string position) -{ - pgmfile outslice; - outslice = slicer(inp, axis, position); - outimg = convert(outslice); -} - -(volume s[]) all_align_reslices(volume reference, volume subjects[]) { - - foreach subject, i in subjects { - s[i] = align_and_reslice(reference, subjects[i], "12", "-q"); - } - -} - - - - -slice_to_jpeg and all_align_reslices are compound procedures. They call -other procedures, like align_and_reslice did above. Note how -all_align_reslices uses foreach to run the same procedure on each element -in an array. - - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - - -The same mapping we used in the previous exercise to map a pair -of reference files into the reference variable using a complex type. - - - -volume subjects[] <csv_mapper;file="subjects.csv">; - - - -Now we map a number of subject images into the subjects array. - - -ACTION REQUIRED: Copy the subjects data files into your -working directory, like this: - - - -$ cp ~benc/workflow/data/anatomy* Raw/ -$ ls Raw/ -anatomy1.hdr anatomy2.hdr anatomy3.hdr anatomy4.hdr reference.hdr -anatomy1.img anatomy2.img anatomy3.img anatomy4.img reference.img - - -ACTION REQUIRED: Create a text file called subjects.csv using your -favourite text editor. List all four image pairs. Here is an example -of how to start: - - - -img,hdr -Raw/anatomy1.img,Raw/anatomy1.hdr -Raw/anatomy2.img,Raw/anatomy2.hdr - - - -Put the above text in students.csv and also add two new lines to list -anatomy data sets 3 and 4. - - - -volume slices[] <csv_mapper;file="slices.csv">; - - - -Slices will hold intermediate volumes that have been processed by some -of our tools. We need to map to tell swift where to put these intermediate -files. Because we need the filenames to correspond, we cannot use -anonymous mapping for these intermediate values like in the second -exercise. We need to populate slices.csv, but we do not need to find -the corresponding files. Swift will create these files as part of -executing the workflow. - - -ACTION REQUIRED: Create a text file called slices.csv with your -text editor, and put the following content into it: - - - -img,hdr -slice1.img,slice1.hdr -slice2.img,slice2.hdr -slice3.img,slice3.hdr -slice4.img,slice4.hdr - - - -slices = all_align_reslices(reference, subjects); - -volume atlas <simple_mapper;prefix="atlas">; -atlas = softmean(slices); - -string directions[] = [ "x", "y", "z"]; - -foreach direction in directions { - imagefile o <single_file_mapper;file=@strcat("atlas-",direction,".jpeg")>; - string option = @strcat("-",direction); - o = slice_to_jpeg(atlas, option, ".5"); -} - - - -Finally we make a number of actual procedure invocations (and declare a few -more variables). The ultimate output of our workflow comes from the o -variable inside the foreach look. This is mapped to a different filename -in each iteration, similar to exercise two. - - - -ACTION: -Put the workflow into a file called final.swift, and -then run the workflow with the swift command. Then open -the resulting files - atlas-x.jpeg, atlas-y.jpeg and atlas-z.jpeg. - - -You should see three brain images, along three different axes. - - - - -The End -
    - Deleted: branches/release-0.92/docs/tutorial.xml =================================================================== --- branches/release-0.92/docs/tutorial.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/tutorial.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,1317 +0,0 @@ - - - -
    - - A Swift Tutorial - - - -This is an introductory tutorial on the use of Swift and its -programming language SwiftScript. - - -$LastChangedRevision$ - - - - - -
    Introduction - -This tutorial is intended to introduce new users to the basics of Swift. -It is structured as a series of small exercise/examples which you can -try for yourself as you read along. After the first 'hello world' -example, there are two tracks - the language track (which introduces -features of the SwiftScript language) and the runtime track (which -introduces features of the Swift runtime environment, such as -running jobs on different sites) - - -For information on getting an installation of Swift running, consult the -Swift Quickstart Guide, -and return to this document when you have -successfully run the test SwiftScript program mentioned there. - - -There is also a -Swift User's Guide -which contains more detailed reference -material on topics covered in this manual. - -All of the programs included in this tutorial can be found in your Swift distribution in the examples/swift directory. - -
    - -
    Hello World - -The first example program, -first.swift, -outputs a hello world message into -a file called hello.txt. - - - -type messagefile; - -app (messagefile t) greeting () { - echo "Hello, world!" stdout=@filename(t); -} - -messagefile outfile <"hello.txt">; - -outfile = greeting(); - - -We can run this program as follows: - - -$ cd examples/swift/ -$ swift first.swift -Swift svn swift-r3334 (swift modified locally) cog-r2752 - -RunID: 20100526-1925-8zjupq1b -Progress: -Final status: Finished successfully:1 -$ cat hello.txt -Hello, world! - - -The basic structure of this program is a -type definition, -an application procedure definition, -a variable definition and -then a call to the procedure: - - - -type messagefile; - - - -First we define a new type, called messagefile. -In this example, we will use this messagefile -type as the type for our output message. - - -All data in SwiftScript must be typed, -whether it is stored in memory or on disk. This example defines a -very simple type. Later on we will see more complex type examples. - - - - - -app (messagefile t) greeting() { - echo "Hello, world!" stdout=@filename(t); -} - - - -Next we define a procedure called greeting. This procedure will write out -the "hello world" message to a file. - - - -To achieve this, it executes the unix utility 'echo' with a parameter -"Hello, world!" and directs the standard output into the output file. - - - -The actual file to use is specified by the -return parameter, t. - - - -messagefile outfile <"hello.txt">; - - - -Here we define a variable called outfile. The type of this variable is -messagefile, and we specify that the contents of this variable will -be stored on disk in a file called hello.txt - - - -outfile = greeting(); - - - -Now we call the greeting procedure, with its output going to the -outfile variable and therefore to hello.txt on disk. - - -Over the following exercises, we'll extend this simple -hello world program to demonstrate various features of Swift. - -
    - -
    Language features - -
    Parameters - - -Procedures can have parameters. Input parameters specify inputs to the -procedure and output parameters specify outputs. Our helloworld greeting -procedure already uses an output parameter, t, which indicates where the -greeting output will go. In this section, we will add an input parameter -to the greeting function. -The code changes from first.swift -are highlighted below. - - -type messagefile; - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -messagefile outfile <"hello2.txt">; - -outfile = greeting("hello world"); - - -We have modified the signature of the greeting procedure to indicate -that it takes a single parameter, s, of type 'string'. -We have modified the invocation of the 'echo' utility so that it -takes the value of s as a parameter, instead of the string literal -"Hello, world!". -We have modified the output file definition to point to a different -file on disk. -We have modified the invocation of greeting so that a greeting -string is supplied. - -The code for this section can be found in -parameter.swift. It can be -invoked using the swift command, with output appearing in -hello2.txt: - - -$ swift parameter.swift - - -Now that we can choose our greeting text, we can call the same -procedure with different parameters to generate several output files with -different greetings. The code is in manyparam.swift and can be run as before -using the swift command. - - - -type messagefile; - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -messagefile english <"english.txt">; -messagefile french <"francais.txt">; -english = greeting("hello"); -french = greeting("bonjour"); - -messagefile japanese <"nihongo.txt">; -japanese = greeting("konnichiwa"); - - -Note that we can intermingle definitions of variables with invocations -of procedures. -When this program has been run, there should be three new files in the -working directory (english.txt, francais.txt and nihongo.txt) each containing -a greeting in a different language. - -In addition to specifying parameters positionally, parameters can -be named, and if desired a default value can be specified - see -Named and optional -parameters. -
    -
    Adding another application - -Now we'll define a new application procedure. The procedure we define -will capitalise all the words in the input file. - - -To do this, we'll use the unix 'tr' (translate) utility. - -Here is an example of using tr on the unix -command line, not using Swift: - - -$ echo hello | tr '[a-z]' '[A-Z]' -HELLO - - - -There are several steps: - -transformation catalog -application block - - - -First we need to modify the -transformation catalog to define -a logical transformation for the tc utility. The transformation -catalog can be found in etc/tc.data. -There are already several entries specifying where programs can -be found. Add a new line to the file, specifying where -tr can be found -(usually in /usr/bin/tr -but it may differ on your system), like this: - - - -localhost tr /usr/bin/tr INSTALLED INTEL32::LINUX null - - -For now, ignore all of the fields except the second and the third. -The second field 'tr' specifies a logical application name and the -third specifies the location of the application executable. - - -Now that we have defined where to find tr, we can -use it in SwiftScript. - - - -We can define a new procedure, capitalise which calls -tr. - -(messagefile o) capitalise(messagefile i) { - app { - tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); - } -} - - - - - -We can call capitalise like this: - -messagefile final <"capitals.txt">; -final = capitalise(hellofile); - - - - -So a full program based on the first exercise might look like this: - - -type messagefile {} - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -(messagefile o) capitalise(messagefile i) { - app { - tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); - } -} - -messagefile hellofile <"hello.txt">; -messagefile final <"capitals.txt">; - -hellofile = greeting("hello from Swift"); -final = capitalise(hellofile); - - - -We can use the swift command to run this: - - -$ swift second_procedure.swift -[...] -$ cat capitals.txt -HELLO FROM SWIFT - - - -
    - -
    Anonymous files - -In the previous section, the file -greeting.txt is used only to -store an intermediate result. We don't really care about which name is used -for the file, and we can let Swift choose the name. - -To do that, omit the mapping entirely when declaring outfile: - -messagefile outfile; - - - - -Swift will choose a filename, which in the present version will be -in a subdirectory called _concurrent. - - -
    - -
    Datatypes - - -All data in variables and files has a data type. So -far, we've seen two types: - - -string - this is a built-in type for storing strings of text in -memory, much like in other programming languages -messagefile - this is a user-defined type used to mark -files as containing messages - - - - -SwiftScript has the additional built-in types: -boolean, integer and -float that function much like their counterparts -in other programming languages. - - -It is also possible to create user defined types with more -structure, for example: - -type details { - string name; - int pies; -} - -Each element of the structured type can be accessed using a . like this: - -person.name = "john"; - - - - -The following complete program, types.swift, outputs a greeting using a user-defined -structure type to hold parameters for the message: - - -type messagefile {} - -type details { - string name; - int pies; -} - -(messagefile t) greeting (details d) { - app { - echo "Hello. Your name is" d.name "and you have eaten" d.pies "pies." stdout=@filename(t); - } -} - -details person; - -person.name = "John"; -person.pies = 3; - -messagefile outfile <"q15.txt>"; - -outfile = greeting(person); - - - - -Structured types can be comprised of marker types for files. See the later -section on mappers for more information about this. - - -
    - -
    Arrays -We can define arrays using the [] suffix in a variable declaration: - -messagefile m[]; - -This program, q5.swift, will declare an array of message files. - - - -type messagefile; - -(messagefile t) greeting (string s[]) { - app { - echo s[0] s[1] s[2] stdout=@filename(t); - } -} - -messagefile outfile <"q5out.txt">; - -string words[] = ["how","are","you"]; - -outfile = greeting(words); - - - -Observe that the type of the parameter to greeting is now an -array of strings, 'string s[]', instead of a single string, 'string s', -that elements of the array can be referenced numerically, for example -s[0], and that the array is initialised using an array literal, -["how","are","you"]. - -
    - -
    Mappers - -A significant difference between SwiftScript and other languages is -that data can be referred to on disk through variables in a very -similar fashion to data in memory. For example, in the above -examples we have seen a variable definition like this: - - -messagefile outfile <"q13greeting.txt">; - - -This means that 'outfile' is a dataset variable, which is -mapped to a file on disk called 'g13greeting.txt'. This variable -can be assigned to using = in a similar fashion to an in-memory -variable. We can say that 'outfile' is mapped onto the disk file -'q13greeting.txt' by a mapper. - - -There are various ways of mapping in SwiftScript. Two forms have already -been seen in this tutorial. Later exercises will introduce more forms. - - -The two forms of mapping seen so far are: - - - -simple named mapping - the name of the file that a variable is -mapped to is explictly listed. Like this: - -messagefile outfile <"greeting.txt">; - - -This is useful when you want to explicitly name input and output -files for your program. For example, 'outfile' in exercise HELLOWORLD. - - - - -anonymous mapping - no name is specified in the source code. -A name is automatically generated for the file. This is useful -for intermediate files that are only referenced through SwiftScript, -such as 'outfile' in exercise ANONYMOUSFILE. A variable declaration -is mapped anonymously by ommitting any mapper definition, like this: - - -messagefile outfile; - - - - - - -Later exercises will introduce other ways of mapping from -disk files to SwiftScript variables. - -TODO: introduce @v syntax. - -
    The regexp mapper -In this exercise, we introduce the regexp mapper. -This mapper transforms a string expression using a regular expression, -and uses the result of that transformation as the filename to map. - -regexp.swift demonstrates the use of this by placing output into a file that -is based on the name of the input file: our input file is mapped -to the inputfile variable using the simple named mapper, and then -we use the regular expression mapper to map the output file. Then we -use the countwords() procedure to count the works in the input file and -store the result in the output file. In order for the countwords() procedure -to work correctly, add the wc utility (usually found in /usr/bin/wc) to tc.data. - - - -The important bit of regexp.swift is: - -messagefile inputfile <"q16.txt">; - -countfile c <regexp_mapper; - source=@inputfile, - match="(.*)txt", - transform="\\1count" - >; - - -
    - -
    fixed_array_mapper - -The fixed array mapper maps a list of files into -an array - each element of the array is mapped into one file in the -specified directory. See fixedarray.swift. - - -string inputNames = "one.txt two.txt three.txt"; -string outputNames = "one.count two.count three.count"; - -messagefile inputfiles[] <fixed_array_mapper; files=inputNames>; -countfile outputfiles[] <fixed_array_mapper; files=outputNames>; - -outputfiles[0] = countwords(inputfiles[0]); -outputfiles[1] = countwords(inputfiles[1]); -outputfiles[2] = countwords(inputfiles[2]); - -
    - -
    - -
    foreach -SwiftScript provides a control structure, foreach, to operate -on each element of an array. -In this example, we will run the previous word counting example -over each file in an array without having to explicitly list the -array elements. The source code for this example is in -foreach.swift. The three input files -(one.txt, two.txt and -three.txt) are supplied. After -you have run the workflow, you should see that there are three output -files (one.count, two.count -and three.count) each containing the word -count for the corresponding input file. We combine the use of the -fixed_array_mapper and the regexp_mapper. - -string inputNames = "one.txt two.txt three.txt"; - -messagefile inputfiles[] <fixed_array_mapper; files=inputNames>; - - -foreach f in inputfiles { - countfile c <regexp_mapper; - source=@f, - match="(.*)txt", - transform="\\1count">; - c = countwords(f); -} - - -
    - -
    If - -Decisions can be made using 'if', like this: - - - -if(morning) { - outfile = greeting("good morning"); -} else { - outfile = greeting("good afternoon"); -} - - - - if.swift contains a simple example of -this. Compile and run if.swift and see that it -outputs 'good morning'. Changing the 'morning' -variable from true to false will cause the program to output 'good -afternoon'. - -
    - -
    Sequential iteration -A development version of Swift after 0.2 (revision 1230) introduces -a sequential iteration construct. - -The following example demonstrates a simple application: each step of the -iteration is a string representation of the byte count of the previous -step's output, with iteration terminating when the byte count reaches zero. - - - -Here's the program: - - - -type counterfile; - -(counterfile t) echo(string m) { - app { - echo m stdout=@filename(t); - } -} - -(counterfile t) countstep(counterfile i) { - app { - wcl @filename(i) @filename(t); - } -} - -counterfile a[] <simple_mapper;prefix="foldout">; - -a[0] = echo("793578934574893"); - -iterate v { - a[v+1] = countstep(a[v]); - trace("extract int value ", at extractint(a[v+1])); -} until (@extractint(a[v+1]) <= 1); - - - - -echo is the standard unix echo. - - wcl -is our application code - it counts the number of bytes in the one file -and writes that count out to another, like this: - - -$ cat ../wcl -#!/bin/bash -echo -n $(wc -c < $1) > $2 - -$ echo -n hello > a -$ wcl a b -$ cat b -5 - - -Install the above wcl script somewhere and add a transformation catalog -entry for it. Then run the example program like this: - - - -$ swift iterate.swift -Swift svn swift-r3334 cog-r2752 - -RunID: 20100526-2259-gtlz8zf4 -Progress: -SwiftScript trace: extract int value , 16.0 -SwiftScript trace: extract int value , 2.0 -SwiftScript trace: extract int value , 1.0 -Final status: Finished successfully:4 - -$ ls foldout* -foldout0000 foldout0001 foldout0002 foldout0003 - - -
    - -
    -
    Runtime features - -
    Visualising the workflow as a graph - - -When running a workflow, its possible to generate a provenance graph at the -same time: - -$ swift -pgraph graph.dot first.swift -$ dot -ograph.png -Tpng graph.dot - -graph.png can then be viewed using your favourite image viewer. -Dot is a utility for drawing directed graphs. It is a part of the graphViz package and must be installed separately. More information about graphViz can be found at http://www.graphviz.org. - -
    - -
    Running on a remote site - -As configured by default, all jobs are run locally. In the previous -examples, we've invoked 'echo' and 'tr' executables from our -SwiftScript program. These have been run on the local system -(the same computer on which you ran 'swift'). We can also make our -computations run on a remote resource. - -WARNING: This example is necessarily more vague than previous examples, -because its requires access to remote resources. You should ensure that you -can submit a job using the globus-job-run (or globusrun-ws?) command(s). - - -We do not need to modify any SwiftScript code to run on another resource. -Instead, we must modify another catalog, the 'site catalog'. This catalog -provides details of the location that applications will be run, with the -default settings referring to the local machine. We will modify it to -refer to a remote resource - the UC Teraport cluster. If you are not a -UC Teraport user, you should use details of a different resource that -you do have access to. - - -The site catalog is located in etc/sites.xml and is a relatively -straightforward XML format file. We must modify each of the following -three settings: gridftp (which indicates how and where data can be -transferred to the remote resource), jobmanager (which indicates how -applications can be run on the remote resource) and workdirectory -(which indicates where working storage can be found on the -remote resource). -
    - -
    Writing a mapper - - -This section will introduce writing a custom mapper so that Swift is able -to access data files laid out in application-specific ways. - - -An application-specific mapper must take the form of a Java class -that implements the -Mapper interface. - - -Usually you don't need to implement this interface directly, because -Swift provides a number of more concrete classes with some functionality -already implemented. - -The hierarchy of helper classes is: - - -Mapper -- This is the abstract interface for mappers in Swift. You -must implement methods to provide access to mapper properties, to map -from a SwiftScript dataset path (such as foo[1].bar) to a file name, -to check whether a file exists. None of the default Swift mappers -implement this interface directly - instead they use one of the -following helper classes. - - -AbstractMapper -- This provides helper methods to manage mapper -properties and to handle existance checking. Examples of mappers which -use this class are: -array_mapper, -csv_mapper, -fixed_array_mapper, -regexp_mapper and -single file mapper -. - - -AbstractFileMapper - - This provides a helper class for mappers -which select files based on selecting files from a directory listing. -It is necessary to write some helper methods that are different from -the above mapper methods. Examples of mappers which use this class -are: -simple_mapper, -filesys_mapper and the (undocumented) -StructuredRegularExpressionMapper. - - - -In general, to write a mapper, choose either the AbstractMapper or the -AbstractFileMapper and extend those. If your mapper will generally -select the files it returns based on a directory listing and will -convert paths to filenames using some regular conversion (for example, in -the way that simple_mapper maps files in a directory that match a -particular pattern), then you should probably use the AbstractFileMapper. -If your mapper will produce a list of files in some other way (for example, -in the way that csv_mapper maps based on filenames given in a CSV -file rather than looking at which files are in a directory), then you -should probably use the AbstractMapper. - - -
    Writing a very basic mapper -In this section, we will write a very basic (almost useless) -mapper that will map a SwiftScript dataset into a hardcoded file -called myfile.txt, like this: - - - - - Swift variable Filename - - var <-----------------------------> myfile.txt - - - - -We should be able to use the mapper we write in a SwiftScript program -like this: - - - -type file; - -file f <my_first_mapper>; - - - -First we must choose a base class - AbstractMapper or AbstractFileMapper. -We aren't going to use a directory listing to decide on our mapping -- we are getting the mapping from some other source (in fact, it -will be hard coded). So we will use AbstractMapper. - - - -So now onto the source code. We must define a subclass of -AbstractMapper and implement several -mapper methods: isStatic, existing, and map. These methods are documented -in the javadoc for the -Mapper -interface. - - - -Here is the code implementing this mapper. Put this in your source -vdsk directory, make a directory -src/tutorial/ and put this -file in src/tutorial/MyFirstMapper.java - - -package tutorial; - -import java.util.Arrays; -import java.util.Collection; -import java.util.Collections; - -import org.griphyn.vdl.mapping.AbsFile; -import org.griphyn.vdl.mapping.AbstractMapper; -import org.griphyn.vdl.mapping.Path; -import org.griphyn.vdl.mapping.PhysicalFormat; - -public class MyFirstMapper extends AbstractMapper { - - AbsFile myfile = new AbsFile("myfile.txt"); - - public boolean isStatic() { - return false; - } - - public Collection existing() { - if (myfile.exists()) - return Arrays.asList(new Path[] {Path.EMPTY_PATH}); - else - return Collections.EMPTY_LIST; - } - - public PhysicalFormat map(Path p) { - if(p.equals(Path.EMPTY_PATH)) - return myfile; - else - return null; - } -} - - - -Now we need to inform the Swift engine about the existence of this -mapper. We do that by editing the MapperFactory class definition, in -src/org/griphyn/vdl/mapping/MapperFactory.java and -adding a registerMapper call alongside the existing registerMapper calls, -like this: - - -registerMapper("my_first_mapper", tutorial.MyFirstMapper.class); - - -The first parameter is the name of the mapper that will be used -in SwiftScript program. The second parameter is the new Mapper class -that we just wrote. - - - -Now rebuild Swift using the 'ant redist' target. - - - -This new Swift build will be aware of your new mapper. We can test it out -with a hello world program: - - -type messagefile; - -(messagefile t) greeting() { - app { - echo "hello" stdout=@filename(t); - } -} - -messagefile outfile <my_first_mapper>; - -outfile = greeting(); - -Run this program, and hopefully you will find the "hello" string has -been output into the hard coded output file myfile.txt: - - -$ cat myfile.txt -hello - - -So that's a first very simple mapper implemented. Compare the -source code to the single_file_mapper in -SingleFileMapper.java. There is -not much more code to the single_file_mapper - mostly code to deal -with the file parameter. - - -
    - - -
    - -
    Starting and restarting - - -Now we're going to try out the restart capabilities of Swift. We will make -a workflow that will deliberately fail, and then we will fix the problem -so that Swift can continue with the workflow. - - - -First we have the program in working form, restart.swift. - - - -type file; - -(file f) touch() { - app { - touch @f; - } -} - -(file f) processL(file inp) { - app { - echo "processL" stdout=@f; - } -} - -(file f) processR(file inp) { - app { - broken "process" stdout=@f; - } -} - -(file f) join(file left, file right) { - app { - echo "join" @left @right stdout=@f; - } -} - -file f = touch(); - -file g = processL(f); -file h = processR(f); - -file i = join(g,h); - - - -We must define some transformation catalog entries: - - - -localhost touch /usr/bin/touch INSTALLED INTEL32::LINUX null -localhost broken /bin/true INSTALLED INTEL32::LINUX null - - - -Now we can run the program: - - - -$ swift restart.swift -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1119-3kgzzi15 -Progress: -Final status: Finished successfully:4 - - - -Four jobs run - touch, echo, broken and a final echo. (note that broken -isn't actually broken yet). - - - -Now we will break the 'broken' job and see what happens. Replace the -definition in tc.data for 'broken' with this: - - -localhost broken /bin/false INSTALLED INTEL32::LINUX null - - -Now when we run the workflow, the broken task fails: - - -$ swift restart.swift - -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1121-tssdcljg -Progress: -Progress: Stage in:1 Finished successfully:2 -Execution failed: - Exception in broken: -Arguments: [process] -Host: localhost -Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj -stderr.txt: -stdout.txt: - - - -From the output we can see that touch and the first echo completed, -but then broken failed and so swift did not attempt to execute the -final echo. - -There will be a restart log with the same name as the RunID: - - - -$ ls *20100526-1121-tssdcljg*rlog -restart-20100526-1121-tssdcljg.0.rlog - - -This restart log contains enough information for swift to know -which parts of the workflow were executed successfully. - -We can try to rerun it immediately, like this: - - -$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift - -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1125-7yx0zi6d -Progress: -Execution failed: - Exception in broken: -Arguments: [process] -Host: localhost -Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj -stderr.txt: -stdout.txt: - ----- - -Caused by: - Exit code 1 - - - - -Swift tried to resume the workflow by executing 'broken' again. It did not -try to run the touch or first echo jobs, because the restart log says that -they do not need to be executed again. - - -Broken failed again, leaving the original restart log in place. - -Now we will fix the problem with 'broken' by restoring the original -tc.data line that works. - -Remove the existing 'broken' line and replace it with the successful -tc.data entry above: - - - -localhost broken /bin/true INSTALLED INTEL32::LINUX null - - - -Now run again: - - - -$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift - -wift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1128-a2gfuxhg -Progress: -Final status: Initializing:2 Finished successfully:2 - - -Swift tries to run 'broken' again. This time it works, and so -Swift continues on to execute the final piece of the workflow as if -nothing had ever gone wrong. - - -
    -
    - -
    bits -
    Named and optional parameters -In addition to specifying parameters positionally, parameters can -be named, and if desired a default value can be specified: - - -(messagefile t) greeting (string s="hello") { - app { - echo s stdout=@filename(t); - } -} - - -When we invoke the procedure, we can specify values for the parameters -by name. The following code can be found in q21.swift. - - -french = greeting(s="bonjour"); - - -or we can let the default value apply: - - -english = greeting(); - - - -
    -
    -
    - Deleted: branches/release-0.92/docs/type-hierarchy.fig =================================================================== --- branches/release-0.92/docs/type-hierarchy.fig 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/type-hierarchy.fig 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,29 +0,0 @@ -#FIG 3.2 Produced by xfig version 3.2.5 -Landscape -Center -Inches -Letter -100.00 -Single --2 -1200 2 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 4950 1350 4050 1800 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 5325 1350 6225 1800 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 3525 2100 3150 2850 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 3975 2100 4275 2775 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 6525 2175 6225 2775 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 6900 2175 7125 2775 -4 0 0 50 -1 0 12 0.0000 4 195 960 4575 1200 Swift types\001 -4 0 0 50 -1 0 12 0.0000 4 195 1275 2475 3075 Primitive types\001 -4 0 0 50 -1 0 12 0.0000 4 195 615 2475 3330 (eg int)\001 -4 0 0 50 -1 0 12 0.0000 4 195 1170 3975 3075 Marker types\001 -4 0 0 50 -1 0 12 0.0000 4 195 615 5925 3000 Arrays\001 -4 0 0 50 -1 0 12 0.0000 4 150 900 6900 3000 Structures\001 -4 0 0 50 -1 0 12 0.0000 4 195 1440 6225 2100 Composite types\001 -4 0 0 50 -1 0 12 0.0000 4 195 1155 3300 2025 Atomic types\001 Deleted: branches/release-0.92/docs/type-hierarchy.png =================================================================== (Binary files differ) Deleted: branches/release-0.92/docs/userguide-rotated.jpeg =================================================================== (Binary files differ) Deleted: branches/release-0.92/docs/userguide-shane.jpeg =================================================================== (Binary files differ) Deleted: branches/release-0.92/docs/userguide.xml =================================================================== --- branches/release-0.92/docs/userguide.xml 2011-05-16 15:43:22 UTC (rev 4477) +++ branches/release-0.92/docs/userguide.xml 2011-05-16 19:29:01 UTC (rev 4478) @@ -1,4337 +0,0 @@ - - - - -
    - - Swift User Guide - Source control $LastChangedRevision$ - - -
    - Overview - -This manual provides reference material for Swift: the SwiftScript language -and the Swift runtime system. For introductory material, consult -the Swift -tutorial. - - -Swift is a data-oriented coarse grained scripting language that -supports dataset typing and mapping, dataset iteration, -conditional branching, and procedural composition. - - -Swift programs (or workflows) are written in -a language called SwiftScript. - - -SwiftScript programs are dataflow oriented - they are primarily -concerned with processing (possibly large) collections of data files, -by invoking programs to do that processing. Swift handles execution of -such programs on remote sites by choosing sites, handling the staging -of input and output files to and from the chosen sites and remote execution -of program code. - -
    -
    - The SwiftScript Language -
    Language basics - -A Swift script describes data, application components, invocations -of applications components, and the inter-relations (data flow) -between those invocations. - - -Data is represented in a script by strongly-typed single-assignment -variables. The syntax superficially resembles C and Java. For example, -{ and } characters are used to -enclose blocks of statements. - - -Types in Swift can be atomic or -composite. An atomic type can be either a -primitive type or a mapped type. -Swift provides a fixed set of primitive types, such as -integer and string. A mapped -type indicates that the actual data does not reside in CPU addressable -memory (as it would in conventional programming languages), but in -POSIX-like files. Composite types are further subdivided into -structures and arrays. -Structures are similar in most respects to structure types in other languages. -Arrays use numeric indices, but are sparse. They can contain elements of -any type, including other array types, but all elements in an array must be -of the same type. We often refer to instances of composites of mapped types -as datasets. - - - -Mapped type and composite type variable declarations can be annotated with a -mapping descriptor indicating the file(s) that make up -that dataset. For example, the following line declares a variable named -photo with type image. It additionally -declares that the data for this variable is stored in a single file named -shane.jpeg. - - - - image photo <"shane.jpeg">; - - - -Component programs of scripts are declared in an app -declaration, with the description of the command line syntax -for that program and a list of input and output data. An app -block describes a functional/dataflow style interface to imperative -components. - - - -For example, the following example lists a procedure which makes use of -the ImageMagick -convert command to rotate a supplied -image by a specified angle: - - - - app (image output) rotate(image input) { - convert "-rotate" angle @input @output; - } - - - -A procedure is invoked using the familiar syntax: - - - - rotated = rotate(photo, 180); - - - -While this looks like an assignment, the actual unix level execution -consists of invoking the command line specified in the app -declaration, with variables on the left of the assignment bound to the -output parameters, and variables to the right of the procedure -invocation passed as inputs. - - - -The examples above have used the type image without any -definition of that type. We can declare it as a marker type -which has no structure exposed to SwiftScript: - - - - type image; - - - -This does not indicate that the data is unstructured; but it indicates -that the structure of the data is not exposed to SwiftScript. Instead, -SwiftScript will treat variables of this type as individual opaque -files. - - - -With mechanisms to declare types, map variables to data files, and -declare and invoke procedures, we can build a complete (albeit simple) -script: - - - - type image; - image photo <"shane.jpeg">; - image rotated <"rotated.jpeg">; - - app (image output) rotate(image input, int angle) { - convert "-rotate" angle @input @output; - } - - rotated = rotate(photo, 180); - - - -This script can be invoked from the command line: - - - - $ ls *.jpeg - shane.jpeg - $ swift example.swift - ... - $ ls *.jpeg - shane.jpeg rotated.jpeg - - - -This executes a single convert command, hiding from the -user features such as remote multisite execution and fault tolerance that -will be discussed in a later section. - -
    shane.jpeg - -
    -
    rotated.jpeg - -
    -
    - -
    Arrays and Parallel Execution - -Arrays of values can be declared using the [] suffix. An -array be mapped to a collection of files, one element per file, by using -a different form of mapping expression. For example, the -filesys_mapper -maps all files matching a particular unix glob pattern into an array: - - - - file frames[] <filesys_mapper; pattern="*.jpeg">; - - - -The foreach construct can be used -to apply the same block of code to each element of an array: - - - - foreach f,ix in frames { - output[ix] = rotate(frames, 180); - } - - - -Sequential iteration can be expressed using the iterate -construct: - - - - step[0] = initialCondition(); - iterate ix { - step[ix] = simulate(step[ix-1]); - } - - - -This fragment will initialise the 0-th element of the step -array to some initial condition, and then repeatedly run the -simulate procedure, using each execution's outputs as -input to the next step. - - -
    - -
    Ordering of execution - - -Non-array variables are single-assignment, which -means that they must be assigned to exactly one value during execution. -A procedure or expression will be executed when all of its input parameters -have been assigned values. As a result of such execution, more variables may -become assigned, possibly allowing further parts of the script to -execute. - - - -In this way, scripts are implicitly parallel. Aside from serialisation -implied by these dataflow dependencies, execution of component programs -can proceed in parallel. - - - -In this fragment, execution of procedures p and -q can happen in parallel: - - - - y=p(x); - z=q(x); - - -while in this fragment, execution is serialised by the variable -y, with procedure p executing -before q. - - - y=p(x); - z=q(y); - - - -Arrays in SwiftScript are more -monotonic - a generalisation of being -assignment. Knowledge about the -content of an array increases during execution, but cannot otherwise -change. Each element of the array is itself single assignment or monotonic -(depending on its type). -During a run all values for an array are eventually known, and that array -is regarded as closed. - - - -Statements which deal with the array as a whole will often wait for the array -to be closed before executing (thus, a closed array is the equivalent -of a non-array type being assigned). However, a foreach -statement will apply its body to elements of an array as they become -known. It will not wait until the array is closed. - - - -Consider this script: - - - - file a[]; - file b[]; - foreach v,i in a { - b[i] = p(v); - } - a[0] = r(); - a[1] = s(); - - - -Initially, the foreach statement will have nothing to -execute, as the array a has not been assigned any values. -The procedures r and s will execute. -As soon as either of them is finished, the corresponding invocation of -procedure p will occur. After both r -and s have completed, the array a will -be closed since no other statements in the script make an assignment to -a. - - -
    - -
    Compound procedures - -As with many other programming languages, procedures consisting of SwiftScript -code can be defined. These differ from the previously mentioned procedures -declared with the app keyword, as they invoke other -SwiftScript procedures rather than a component program. - - - - (file output) process (file input) { - file intermediate; - intermediate = first(input); - output = second(intermediate); - } - - file x <"x.txt">; - file y <"y.txt">; - y = process(x); - - - -This will invoke two procedures, with an intermediate data file named -anonymously connecting the first and -second procedures. - - - -Ordering of execution is generally determined by execution of -app procedures, not by any containing compound procedures. -In this code block: - - - - (file a, file b) A() { - a = A1(); - b = A2(); - } - file x, y, s, t; - (x,y) = A(); - s = S(x); - t = S(y); - - - -then a valid execution order is: A1 S(x) A2 S(y). The -compound procedure A does not have to have fully completed -for its return values to be used by subsequent statements. - - -
    - -
    More about types - -Each variable and procedure parameter in SwiftScript is strongly typed. -Types are used to structure data, to aid in debugging and checking program -correctness and to influence how Swift interacts with data. - - - -The image type declared in previous examples is a -marker type. Marker types indicate that data for a -variable is stored in a single file with no further structure exposed at -the SwiftScript level. - - - -Arrays have been mentioned above, in the arrays section. A code block -may be applied to each element of an array using foreach; -or individual elements may be references using [] notation. - - -There are a number of primitive types: - - - - typecontains - - intintegers - stringstrings of text - floatfloating point numbers, that behave the same as Java doubles - booleantrue/false - - -
    - - -Complex types may be defined using the type keyword: - - - type headerfile; - type voxelfile; - type volume { - headerfile h; - voxelfile v; - } - - - -Members of a complex type can be accessed using the . -operator: - - - - volume brain; - o = p(brain.h); - - - -Sometimes data may be stored in a form that does not fit with Swift's -file-and-site model; for example, data might be stored in an RDBMS on some -database server. In that case, a variable can be declared to have -external type. This indicates that -Swift should use the variable to determine execution dependency, but should -not attempt other data management; for example, it will not perform any form -of data stage-in or stage-out it will not manage local data caches on sites; -and it will not enforce component program atomicity on data output. This can -add substantial responsibility to component programs, in exchange for allowing -arbitrary data storage and access methods to be plugged in to scripts. - - - - type file; - - app (external o) populateDatabase() { - populationProgram; - } - - app (file o) analyseDatabase(external i) { - analysisProgram @o; - } - - external database; - file result <"results.txt">; - - database = populateDatabase(); - result = analyseDatabase(database); - - - -Some external database is represented by the database -variable. The populateDatabase procedure populates the -database with some data, and the analyseDatabase procedure -performs some subsequent analysis on that database. The declaration of -database contains no mapping; and the procedures which -use database do not reference them in any way; the -description of database is entirely outside of the script. -The single assignment and execution ordering rules will still apply though; -populateDatabase will always be run before -analyseDatabase. - - -
    - -
    Data model -Data processed by Swift is strongly typed. It may be take the form -of values in memory or as out-of-core files on disk. Language constructs -called mappers specify how each piece of data is stored. - -
    Mappers - -When a DSHandle represents a data file (or container of datafiles), it is -associated with a mapper. The mapper is used to -identify which files belong to that DSHandle. - - -A dataset's physical representation is declared by a mapping descriptor, -which defines how each element in the dataset's logical schema is -stored in, and fetched from, physical structures such as directories, -files, and remote servers. - - - -Mappers are parameterized to take into account properties such as -varying dataset location. -In order -to access a dataset, we need to know three things: its type, -its mapping, and the value(s) of any parameter(s) associated -with the mapping descriptor. For example, if we want to describe a dataset, -of type imagefile, and whose physical -representation is a file called "file1.bin" located at "/home/yongzh/data/", -then the dataset might be declared as follows: - - - -imagefile f1<single_file_mapper;file="/home/yongzh/data/file1.bin"> - - - -The above example declares a dataset called f1, which uses a single -file mapper to map a file from a specific location. - - -SwiftScript has a simplified syntax for this case, since single_file_mapper -is frequently used: - - -binaryfile f1<"/home/yongzh/data/file1.bin"> - - - - -Swift comes with a number of mappers that handle common mapping patterns. -These are documented in the mappers section -of this guide. - - -
    - -
    -
    - More technical details about SwiftScript -The syntax of SwiftScript has a superficial resemblance to C and -Java. For example, { and } characters are used to enclose blocks of -statements. - - -A SwiftScript program consists of a number of statements. -Statements may declare types, procedures and variables, assign values to -variables, and express operations over arrays. - - - -
    Variables -Variables in SwiftScript are declared to be of a specific type. -Assignments to those variables must be data of that type. -SwiftScript variables are single-assignment - a value may be assigned -to a variable at most once. This assignment can happen at declaration time -or later on in execution. When an attempt to read from a variable -that has not yet been assigned is made, the code performing the read -is suspended until that variable has been written to. This forms the -basis for Swift's ability to parallelise execution - all code will -execute in parallel unless there are variables shared between the code -that cause sequencing. - -
    - Variable Declarations - -Variable declaration statements declare new variables. They can -optionally assign a value to them or map those variables to on-disk files. - - -Declaration statements have the general form: - - typename variablename (<mapping> | = initialValue ) ; - -The format of the mapping expression is defined in the Mappers section. -initialValue may be either an expression or a procedure call that -returns a single value. - -Variables can also be declared in a multivalued-procedure statement, -described in another section. -
    - -
    - Assignment Statements - -Assignment statements assign values to previously declared variables. -Assignments may only be made to variables that have not already been -assigned. Assignment statements have the general form: - - - variable = value; - -where value can be either an expression or a procedure call that returns -a single value. - - - -Variables can also be assigned in a multivalued-procedure statement, -described in another section. - -
    -
    - -
    Procedures - -There are two kinds of procedure: An atomic procedure, which -describes how an external program can be executed; and compound -procedures which consist of a sequence of SwiftScript statements. - - - -A procedure declaration defines the name of a procedure and its -input and output parameters. SwiftScript procedures can take multiple -inputs and produce multiple outputs. Inputs are specified to the right -of the function name, and outputs are specified to the left. For example: - - -(type3 out1, type4 out2) myproc (type1 in1, type2 in2) - - -The above example declares a procedure called myproc, which -has two inputs in1 (of type type1) -and in2 (of type type2) -and two outputs out1 (of type type3) -and out2 (of type type4). - - - -A procedure input parameter can be an optional -parameter in which case it must be declared with a default -value. When calling a procedure, both positional parameter and named -parameter passings can be passed, provided that all optional -parameters are declared after the required parameters and any -optional parameter is bound using keyword parameter passing. -For example, if myproc1 is defined as: - - -(binaryfile bf) myproc1 (int i, string s="foo") - - -Then that procedure can be called like this, omitting the optional -parameter s: - - -binaryfile mybf = myproc1(1); - - -or like this supplying a value for the optional parameter -s: - - -binaryfile mybf = myproc1 (1, s="bar"); - - - - -
    Atomic procedures - -An atomic procedure specifies how to invoke an -external executable program, and how logical data -types are mapped to command line arguments. - - - -Atomic procedures are defined with the app keyword: - -app (binaryfile bf) myproc (int i, string s="foo") { - myapp i s @filename(bf); -} - - -which specifies that myproc invokes an executable -called myapp, -passing the values of i, s -and the filename of bf as command line arguments. - -
    - -
    Compound procedures - -A compound procedure contains a set of SwiftScript statements: - - -(type2 b) foo_bar (type1 a) { - type3 c; - c = foo(a); // c holds the result of foo - b = bar(c); // c is an input to bar -} - - - -
    -
    -
    - Control Constructs - -SwiftScript provides if, switch, -foreach, and iterate constructs, -with syntax and semantics similar to comparable constructs in -other high-level languages. - -
    foreach - -The foreach construct is used to apply a block of statements to -each element in an array. For example: - - -check_order (file a[]) { - foreach f in a { - compute(f); - } -} - - - -foreach statements have the general form: - - -foreach controlvariable (,index) in expression { - statements -} - - -The block of statements is evaluated once for each element in -expression which must be an array, -with controlvariable set to the corresponding element -and index (if specified) set to the -integer position in the array that is being iterated over. - - -
    - -
    if - -The if statement allows one of two blocks of statements to be -executed, based on a boolean predicate. if statements generally -have the form: - -if(predicate) { - statements -} else { - statements -} - - -where predicate is a boolean expression. - -
    - -
    switch - -switch expressions allow one of a selection of blocks to be chosen based on -the value of a numerical control expression. switch statements take the -general form: - -switch(controlExpression) { - case n1: - statements2 - case n2: - statements2 - [...] - default: - statements -} - -The control expression is evaluated, the resulting numerical value used to -select a corresponding case, and the statements belonging to that -case block -are evaluated. If no case corresponds, then the statements belonging to -the default block are evaluated. - -Unlike C or Java switch statements, execution does not fall through to -subsequent case blocks, and no break -statement is necessary at the end of each block. - -
    - -
    iterate - -iterate expressions allow a block of code to be evaluated repeatedly, with an -integer parameter sweeping upwards from 0 until a termination condition -holds. - - -The general form is: - -iterate var { - statements; -} until (terminationExpression); - -with the variable var starting at 0 and increasing -by one in each iteration. That -variable is in scope in the statements block and when evaluating the -termination expression. - -
    -
    -
    - -
    Operators - -The following infix operators are available for use in -SwiftScript expressions. - - - - operatorpurpose - - +numeric addition; string concatenation - -numeric subtraction - *numeric multiplication - /floating point division - %/integer division - %%integer remainder of division - == !=comparison and not-equal-to - < > <= >=numerical ordering - && ||boolean and, or - !boolean not - - -
    -
    - -
    Global constants - -At the top level of a SwiftScript program, the global -modified may be added to a declaration so that it is visible throughout -the program, rather than only at the top level of the program. This allows -global constants (of any type) to be defined. (since Swift 0.10) - -
    - -
    Imports - -The import directive can be used to import definitions from -another SwiftScript file. (since Swift 0.10) - - -For example, a SwiftScript program might contain this: - -import defs; -file f; - -which would import the content of defs.swift in the -current directory: - -type file; - - - -Imported files are read from the current working directory. - - -There is no requirement that a module is imported only once. If a module -is imported multiple times, for example in different files, then Swift will -only process the imports once. - - -Imports may contain anything that is valid in a SwiftScript program, -including code that causes remote execution. - -
    - -
    -
    - Mappers - -Mappers provide a mechanism to specify the layout of mapped datasets on -disk. This is needed when Swift must access files to transfer them to -remote sites for execution or to pass to applications. - -Swift provides a number of mappers that are useful in common cases. This -section details those standard mappers. For more complex cases, it is -possible to write application-specific mappers in Java and -use them within a SwiftScript program. - - -
    The single file mapper - - -The single_file_mapper maps a single physical file to a dataset. - - - - - Swift variable -------------------> Filename - - f myfile - - f[0] INVALID - - f.bar INVALID - - - - - - - - - parameter - meaning - - - - fileThe location of the physical file including path and file name. - - -
    - -Example: - - file f <single_file_mapper;file="plot_outfile_param">; - -There is a simplified syntax for this mapper: - - - - file f <"plot_outfile_param">; - -
    - -
    The simple mapper -The simple_mapper maps a file or a list of files -into an array by prefix, suffix, and pattern. If more than one file is -matched, each of the file names will be mapped as a subelement of the dataset. - - - - - - - parameter - meaning - - - - locationA directory that the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. When this mapper is used to specify output -filenames, pattern is ignored. - - -
    - - - -Examples: - - - - type file; - file f <simple_mapper;prefix="foo", suffix=".txt">; - -The above maps all filenames that start with foo and -have an extension .txt into file f. - - - - Swift variable -------------------> Filename - - f foo.txt - - - - - - -type messagefile; - -(messagefile t) greeting(string m) {. - app { - echo m stdout=@filename(t); - } -} - -messagefile outfile <simple_mapper;prefix="foo",suffix=".txt">; - -outfile = greeting("hi"); - - -This will output the string 'hi' to the file foo.txt. - - - -The simple_mapper can be used to map arrays. It will map the array index -into the filename between the prefix and suffix. - - -type messagefile; - -(messagefile t) greeting(string m) { - app { - echo m stdout=@filename(t); - } -} - -messagefile outfile[] <simple_mapper;prefix="baz",suffix=".txt">; - -outfile[0] = greeting("hello"); -outfile[1] = greeting("middle"); -outfile[2] = greeting("goodbye"); - - - - - Swift variable -------------------> Filename - - outfile[0] baz0000.txt - outfile[1] baz0001.txt - outfile[2] baz0002.txt - - - - - - -simple_mapper can be used to map structures. It will map the name of the -structure member into the filename, between the prefix and the -suffix. - - -type messagefile; - -type mystruct { - messagefile left; - messagefile right; -}; - -(messagefile t) greeting(string m) { - app { - echo m stdout=@filename(t); - } -} - -mystruct out <simple_mapper;prefix="qux",suffix=".txt">; - -out.left = greeting("hello"); -out.right = greeting("goodbye"); - - -This will output the string "hello" into the file -qux.left.txt and the string "goodbye" -into the file qux.right.txt. - - - - Swift variable -------------------> Filename - - out.left quxleft.txt - out.right quxright.txt - - - - -
    - -
    concurrent mapper - -concurrent_mapper is almost the same as the simple mapper, -except that it is used to map an output file, and the filename -generated will contain an extract sequence that is unique. -This mapper is the default mapper for variables when no mapper is -specified. - - - - - - - parameter - meaning - - - - locationA directory that the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. When this mapper is used to specify output -filenames, pattern is ignored. - - -
    - - - Example: - - file f1; - file f2 <concurrent_mapper;prefix="foo", suffix=".txt">; - -The above example would use concurrent mapper for f1 and -f2, and -generate f2 filename with prefix "foo" and extension ".txt" - -
    - -
    file system mapper - -filesys_mapper is similar to the simple mapper, -but maps a file or -a list of files to an array. Each of the filename is -mapped as an element in the array. The order of files in the resulting -array is not defined. - - -TODO: note on difference between location as a relative vs absolute -path wrt staging to remote location - as mihael said: -It's because you specify that location in the mapper. Try location="." -instead of location="/sandbox/..." - - - - - - parameter - meaning - - - - locationThe directory where the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. - - - -
    - - Example: - - file texts[] <filesys_mapper;prefix="foo", suffix=".txt">; - -The above example would map all filenames that start with "foo" -and have an extension ".txt" into the array texts. -For example, if the specified directory contains files: foo1.txt, footest.txt, -foo__1.txt, then the mapping might be: - - - Swift variable -------------------> Filename - - texts[0] footest.txt - texts[1] foo1.txt - texts[2] foo__1.txt - - - -
    - -
    fixed array mapper -The fixed_array_mapper maps from a string that -contains a list of filenames into a file array. - - - - - - parameter - meaning - - - - filesA string that contains a list of filenames, separated by space, comma or colon - - -
    - - Example: - - file texts[] <fixed_array_mapper;files="file1.txt, fileB.txt, file3.txt">; - -would cause a mapping like this: - - - Swift variable -------------------> Filename - - texts[0] file1.txt - texts[1] fileB.txt - texts[2] file3.txt - - - -
    - -
    array mapper - The array_mapper maps from an array of strings -into a file - - - - - - parameter - meaning - - - - filesAn array of strings containing one filename per element - - -
    - - Example: - -string s[] = [ "a.txt", "b.txt", "c.txt" ]; - -file f[] <array_mapper;files=s>; - -This will establish the mapping: - - - Swift variable -------------------> Filename - - f[0] a.txt - f[1] b.txt - f[2] c.txt - - - - -
    - -
    regular expression mapper -The regexp_mapper transforms one file name to -another using regular expression matching. - - - - - - - parameter - meaning - - - - sourceThe source file name - matchRegular expression pattern to match, use -() to match whatever regular expression is inside the -parentheses, and indicate the start and end of a group; the contents of a -group can be retrieved with the \\number special sequence -(two backslashes are needed because the backslash is an escape sequence introducer) - - transformThe pattern of the file name to -transform to, use \number to reference the -group matched. - - -
    - -Example: - - string s = "picture.gif"; - file f <regexp_mapper; - source=s, - match="(.*)gif", - transform="\\1jpg">; - -This example transforms a string ending gif into one -ending jpg and maps that to a file. - - - Swift variable -------------------> Filename - - f picture.jpg - - - - -
    - -
    csv mapper - - -The csv_mapper maps the content of a CSV (comma-separated -value) file into an array of structures. The dataset type needs to be -correctly defined to conform to the column names in the -file. For instance, if the file contains columns: -name age GPA then the type needs to have member elements -like this: - - type student { - file name; - file age; - file GPA; - } - - -If the file does not contain a header with column info, then the column -names are assumed as column1, column2, -etc. - - - - - - - parameter - meaning - - - - fileThe name of the CSV file to read mappings from. - headerWhether the file has a line describing header info; default is true - skipThe number of lines to skip at the beginning (after header line); default is 0. - hdelimHeader field delimiter; default is the value of the delim parameter - delimContent field delimiters; defaults are space, tab and comma - - -
    - - Example: - - student stus[] <csv_mapper;file="stu_list.txt">; - -The above example would read a list of student info from file -"stu_list.txt" and map them into a student array. By default, the file should contain a header line specifying the names of the columns. -If stu_list.txt contains the following: - -name,age,gpa -101-name.txt, 101-age.txt, 101-gpa.txt -name55.txt, age55.txt, age55.txt -q, r, s - -then some of the mappings produced by this example would be: - - - Swift variable -------------------> Filename - - stus[0].name 101-name.txt - stus[0].age 101-age.txt - stus[0].gpa 101-gpa.txt - stus[1].name name55.txt - stus[1].age age55.txt - stus[1].gpa gpa55.txt - stus[2].name q - stus[2].age r - stus[2].gpa s - - - -
    - -
    external mapper - -The external mapper, ext maps based on the output of a -supplied Unix executable. - - - - - - - parameter - meaning - - - - execThe name of the executable -(relative to the current directory, if an absolute path is not -specified) - *Other parameters are passed to the -executable prefixed with a - symbol - - -
    - - -The output of the executable should consist of two columns of data, separated -by a space. The first column should be the path of the mapped variable, -in SwiftScript syntax (for example [2] means the 2nd element of an -array) or the symbol $ to represent the root of the mapped variable. - - - Example: -With the following in mapper.sh, - -#!/bin/bash -echo "[2] qux" -echo "[0] foo" -echo "[1] bar" - - -then a mapping statement: - - - student stus[] <ext;exec="mapper.sh">; - - -would map - - - - Swift variable -------------------> Filename - - stus[0] foo - stus[1] bar - stus[2] qux - - - - - -
    - -
    mapping URIs - -The above mappers may be used to map files based on a URI which can be specified in the filename. This is useful for mapping files on remote machines. - - - - Example: - - - student st <single_file_mapper;file="gsiftp://communicado.ci.uchicago.edu//tmp/student.txt">; - - - - - -
    - -
    -
    Commands - -The commands detailed in this section are available in the -bin/ directory of a Swift installation and can -by run from the commandline if that directory is placed on the -PATH. - -
    - swift - -The swift command is the main command line tool -for executing SwiftScript programs. - -
    Command-line Syntax -The swift command is invoked as follows: -swift [options] SwiftScript-program [SwiftScript-arguments] -with options taken from the following list, and SwiftScript-arguments -made available to the SwiftScript program through the -@arg function. - - Swift command-line options - -help or -h - - Display usage information - - -typecheck - - Does a typecheck of a SwiftScript program, instead of executing it. - - - -dryrun - - Runs the SwiftScript program without submitting any jobs (can be used to get - a graph) - - - - -monitor - - Shows a graphical resource monitor - - - - -resume file - - Resumes the execution using a log file - - - - -config file - - Indicates the Swift configuration file to be used for this run. - Properties in this configuration file will override the default - properties. If individual command line arguments are used for - properties, they will override the contents of this file. - - - - -verbose | -v - - Increases the level of output that Swift produces on the console - to include more detail about the execution - - - - -debug | -d - - Increases the level of output that Swift produces on the console - to include lots of detail about the execution - - - - -logfile file - - Specifies a file where log messages should go to. By default - Swift uses the name of the program being run and a numeric index - (e.g. myworkflow.1.log) - - - - -runid identifier - - Specifies the run identifier. This must be unique for every invocation - and is used in several places to keep files from different executions - cleanly separated. By default, a datestamp and random number are used - to generate a run identifier. When using this parameter, care should be - taken to ensure that the run ID remains unique with respect to all - other run IDs that might be used, irrespective of (at least) expected - execution sites, program or user. - - - - -tui - - Displays an interactive text mode monitor during a run. (since Swift 0.9) - - - - - -In addition, the following Swift properties can be set on the -command line: - - -caching.algorithm -clustering.enabled -clustering.min.time -clustering.queue.delay -ip.address -kickstart.always.transfer -kickstart.enabled -lazy.errors -pgraph -pgraph.graph.options -pgraph.node.options -sitedir.keep -sites.file -tc.file -tcp.port.range - - - -
    -
    Return codes - -The swift command may exit with the following return codes: - - - - - value - meaning - - - - 0success - 1command line syntax error or missing project name - 2error during execution - 3error during compilation - 4input file does not exist - - -
    -
    -
    -
    Environment variables - The swift is influenced by the -following environment variables: - - -GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment before running -Swift. These can be set to inform Swift of the -configuration of your local firewall. More information can be found in -the Globus firewall -How-to. - - -COG_OPTS - set in the environment before running Swift. Options set in this -variable will be passed as parameters to the Java Virtual Machine which -will run Swift. The parameters vary between virtual machine imlementations, -but can usually be used to alter settings such as maximum heap size. -Typing 'java -help' will sometimes give a list of commands. The Sun Java -1.4.2 command line options are documented here. - - - -
    - -
    - -
    swift-osg-ress-site-catalog - -The swift-osg-ress-site-catalog command generates a site -catalog based on OSG's -ReSS information system (since Swift 0.9) - - -Usage: swift-osg-ress-site-catalog [options] - - - --help - -Show help message - - - - --vo=[name] - -Set what VO to query ReSS for - - - - --engage-verified - -Only retrieve sites verified by the Engagement VO site -verification tests This can not be used together with --vo, -as the query will only work for sites advertising support for the -Engagement VO. - -This option means information will be retrieved from the -Engagement collector instead of the top-level ReSS collector. - - - - - --out=[filename] - -Write to [filename] instead of stdout - - - - --condor-g - -Generates sites files which will submit jobs using a local Condor-G -installation rather than through direct GRAM2 submission. (since Swift 0.10) - - - - - - - - -
    - - -
    swift-plot-log - -swift-plot-log generates summaries of Swift run log -files. - - -Usage: swift-plot-log [logfile] [targets] - - -When no targets are specified, swift-plog-log will -generate an HTML report for the run. When targets are specified, only -those named targets will be generated. - -
    - -
    -
    Executing <literal>app</literal> procedures - -This section describes how Swift executes app procedures, -and requirements on the behaviour of application programs used in -app procedures. -These requirements are primarily to ensure -that the Swift can run your application in different places and with the -various fault tolerance mechanisms in place. - - -
    Mapping of <literal>app</literal> semantics into unix -process execution semantics - -This section describes how an app procedure -invocation is translated into a (remote) unix process execution. It does not -describe the mechanisms by which Swift performs that translation; that -is described in the next section. - -In this section, this example SwiftScript program is used -for reference: - - - type file; - - app (file o) count(file i) { - wc @i stdout=@o; - } - - file q <"input.txt">; - file r <"output.txt">; - - - -The executable for wc will be looked up in tc.data. - - - -This unix executable will then be executed in some application -procedure workspace. This means: - - - -Each application procedure workspace will have an application workspace -directory. (TODO: can collapse terms //application procedure workspace// -and //application workspace directory// ? - - - -This application workspace directory will not be shared with any other -application procedure execution attempt; all -application procedure -execution attempts will run with distinct application procedure -workspaces. (for the avoidance of doubt: - If a SwiftScript procedure invocation is subject -to multiple application procedure execution attempts (due to Swift-level -restarts, retries or replication) then each of those application procedure -execution attempts will be made in a different application procedure workspace. -) - - -The application workspace directory will be a directory on a POSIX -filesystem accessible throughout the application execution by the -application executable. - - - -Before the application executable is executed: - - - - - -The application workspace directory will exist. - - - -The input files will exist inside the application workspace -directory (but not necessarily as direct children; there may be -subdirectories within the application workspace directory). - - - -The input files will be those files mapped -to input parameters of the application procedure -invocation. (In the example, this means that the file -input.txt will exist in the application workspace -directory) - - - -For each input file dataset, it will be the case that -@filename or -@filenames invoked with that dataset as a parameter -will return the path -relative to the application workspace directory for the file(s) that are -associated with that dataset. (In the example, that means that @i will -evaluate to the path input.txt) - - - -For each file-bound parameter of the Swift procedure invocation, the -associated files (determined by data type?) will always exist. - - - -The input files must be treated as read only files. This may or may not -be enforced by unix file system permissions. They may or may not be copies -of the source file (conversely, they may be links to the actual source file). - - - - - -During/after the application executable execution, -the following must be true: - - - - -If the application executable execution was successful (in the opinion -of the application executable), then the application executable should -exit with unix return code 0; -if the application executable execution -was unsuccessful (in the opinion of the application executable), then the -application executable should exit with unix return code not equal to -0. - - - -Each file mapped from an output parameter of the SwiftScript procedure -call must exist. Files will be mapped in the same way as for input files. - - -(? Is it defined that output subdirectories will be precreated before -execution or should app executables expect to make them? That's probably -determined by the present behaviour of wrapper.sh) - - - -Output produced by running the application executable on some inputs should -be the same no matter how many times, when or where that application -executable is run. 'The same' can vary depending on application (for example, -in an application it might be acceptable for a PNG->JPEG conversion to -produce different, similar looking, output jpegs depending on the -environment) - - - - - -Things to not assume: - - - - - -anything about the path of the application workspace directory - - - -that either the application workspace directory will be deleted or will -continue to exist or will remain unmodified after execution has finished - - - -that files can be passed(?def) between application procedure invocations -through any mechanism except through files known to Swift through the -mapping mechanism (there is some exception here for external -datasets - there are a separate set of assertions that hold for -external datasets) - - - -that application executables will run on any particular site of those -available, or than any combination of applications will run on the same or -different sites. - - - - -
    - -
    -How Swift implements the site execution model - - - -This section describes the implementation of the semantics described -in the previous section. - - - -Swift executes application procedures on one or more sites. - - - -Each site consists of: - - - - -worker nodes. There is some execution mechanism -through which the Swift client side executable can execute its -wrapper script on those -worker nodes. This is commonly GRAM or Falkon or coasters. - - - -a site-shared file system. This site shared filesystem is accessible -through some file transfer mechanism from the -Swift client side -executable. This is commonly GridFTP or coasters. This site shared -filesystem is also accessible through the posix file system on all worker -nodes, mounted at the same location as seen through the file transfer -mechanism. Swift is configured with the location of some site working -directory on that site-shared file system. - - - - -There is no assumption that the site shared file system for one site is -accessible from another site. - - - -For each workflow run, on each site that is used by that run, a run -directory is created in the site working directory, by the Swift client -side. - - - -In that run directory are placed several subdirectories: - - - - -shared/ - site shared files cache - - - -kickstart/ - when kickstart is used, kickstart record files -for each job that has generated a kickstart record. - - - - -info/ - wrapper script log files - - - -status/ - job status files - - - -jobs/ - application workspace directories (optionally placed here - -see below) - - - - -Application execution looks like this: - - - -For each application procedure call: - - - -The Swift client side selects a site; copies the input files for that -procedure call to the site shared file cache if they are not already in -the cache, using the file transfer mechanism; and then invokes the wrapper -script on that site using the execution mechanism. - - - -The wrapper script creates the application workspace directory; places the -input files for that job into the application workspace directory using -either cp or ln -s (depending on a configuration option); executes the -application unix executable; copies output files from the application -workspace directory to the site shared directory using cp; creates a -status file under the status/ directory; and exits, returning control to -the Swift client side. Logs created during the execution of the wrapper -script are stored under the info/ directory. - - - -The Swift client side then checks for the presence of and deletes a status -file indicating success; and copies files from the site shared directory to -the appropriate client side location. - - - -The job directory is created (in the default mode) under the jobs/ -directory. However, it can be created under an arbitrary other path, which -allows it to be created on a different file system (such as a worker node -local file system in the case that the worker node has a local file -system). - - -
    - -
    - -
    - Technical overview of the Swift architecture - -This section attempts to provide a technical overview of the Swift -architecture. - - -
    karajan - the core execution engine -
    - -
    Execution layer - -The execution layer causes an application program (in the form of a unix -executable) to be executed either locally or remotely. - - -The two main choices are local unix execution and execution through GRAM. -Other options are available, and user provided code can also be plugged in. - - -The kickstart utility can -be used to capture environmental information at execution time -to aid in debugging and provenance capture. - -
    - -
    SwiftScript language compilation layer - -Step i: text to XML intermediate form parser/processor. parser written in -ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the -intermediate language is in resources/XDTM.xsd. - - -Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads -the XML intermediate form. compiles to karajan workflow language - for -example, expressions are converted from SwiftScript syntax into Karajan -syntax, and function invocations become karajan function invocations -with various modifications to parameters to accomodate return parameters -and dataset handling. - -
    - -
    Swift/karajan library layer - -Some Swift functionality is provided in the form of Karajan libraries -that are used at runtime by the Karajan workflows that the Swift -compiler generates. - -
    - -
    - -
    Ways in which Swift can be extended -Swift is extensible in a number of ways. It is possible to add -mappers to accomodate different filesystem arrangements, site selectors -to change how Swift decides where to run each job, and job submission -interfaces to submit jobs through different mechanisms. - -A number of mappers are provided as part of the Swift release and -documented in the mappers section. -New mappers can be implemented -in Java by implementing the org.griphyn.vdl.mapping.Mapper interface. The -Swift -tutorial contains a simple example of this. - -Swift provides a default site selector, the Adaptive Scheduler. -New site selectors can be plugged in by implementing the -org.globus.cog.karajan.scheduler.Scheduler interface and modifying -libexec/scheduler.xml and etc/karajan.properties to refer to the new -scheduler. - -Execution providers and filesystem providers, which allow to Swift -to execute jobs and to stage files in and out through mechanisms such -as GRAM and GridFTP can be implemented as Java CoG kit providers. - -
    - -
    Function reference - -This section details functions that are available for use in the SwiftScript -language. - -
    @arg - -Takes a command line parameter name as a string parameter and an optional -default value and returns the value of that string parameter from the -command line. If no default value is specified and the command line parameter -is missing, an error is generated. If a default value is specified and the -command line parameter is missing, @arg will return the default value. - - -Command line parameters recognized by @arg begin with exactly one hyphen -and need to be positioned after the script name. - - - For example: - -trace(@arg("myparam")); -trace(@arg("optionalparam", "defaultvalue")); - - -$ swift arg.swift -myparam=hello -Swift v0.3-dev r1674 (modified locally) - -RunID: 20080220-1548-ylc4pmda -SwiftScript trace: defaultvalue -SwiftScript trace: hello - - -
    - -
    @extractint - -@extractint(file) will read the specified file, parse an integer from the -file contents and return that integer. - -
    - -
    @filename - -@filename(v) will return a string containing the filename(s) for the file(s) -mapped to the variable v. When more than one filename is returned, the -filenames will be space separated inside a single string return value. - -
    -
    @filenames - -@filenames(v) will return multiple values (!) containing the filename(s) for -the file(s) mapped to the variable v. (compare to -@filename) - -
    -
    @regexp - -@regexp(input,pattern,replacement) will apply regular expression -substitution using the Java java.util.regexp API. For example: - -string v = @regexp("abcdefghi", "c(def)g","monkey"); - -will assign the value "abmonkeyhi" to the variable v. - -
    -
    @strcat - -@strcat(a,b,c,d,...) will return a string containing all of the strings -passed as parameters joined into a single string. There may be any number -of parameters. - - -The + operator concatenates two strings: @strcat(a,b) is the same as a + b - -
    -
    @strcut - -@strcut(input,pattern) will match the regular expression in the pattern -parameter against the supplied input string and return the section that -matches the first matching parenthesised group. - - -For example: - - - -string t = "my name is John and i like puppies."; -string name = @strcut(t, "my name is ([^ ]*) "); -string out = @strcat("Your name is ",name); -trace(out); - - - -will output the message: Your name is John. - -
    - -
    @strsplit - -@strsplit(input,pattern) will split the input string based on separators -that match the given pattern and return a string array. (since Swift 0.9) - - -Example: - - - -string t = "my name is John and i like puppies."; -string words[] = @strsplit(t, "\\s"); -foreach word in words { - trace(word); -} - - - -will output one word of the sentence on each line (though -not necessarily in order, due to the fact that foreach -iterations execute in parallel). - -
    - - -
    @toint - -@toint(input) will parse its input string into an integer. This can be -used with @arg to pass input parameters to a SwiftScript program as -integers. - -
    -
    - -
    Built-in procedure reference - -This section details built-in procedures that are available for use in -the SwiftScript language. - - -
    readData - -readData will read data from a specified file. - - -The format of the input file is controlled by the type of the return -value. - - - -For scalar return types, such as int, the specified file should contain -a single value of that type. - - -For arrays of scalars, the specified file should contain one value -per line. - - -For structs of scalars, the file should contain two rows. -The first row should be structure member names separated by whitespace. -The second row should be the corresponding values for each structure -member, separated by whitespace, in the same order as the header row. - - -For arrays of structs, the file should contain a heading row listing -structure member names separated by whitespace. There should be one row -for each element of the array, with structure member elements listed in -the same order as the header row and separated by whitespace. (since Swift 0.4) - - -
    -
    readdata2 - -readdata2 will read data from a specified file, like readdata, but using -a different file format more closely related to that used by the -ext mapper. - - -Input files should list, one per line, a path into a Swift structure, and -the value for that position in the structure: - -rows[0].columns[0] = 0 -rows[0].columns[1] = 2 -rows[0].columns[2] = 4 -rows[1].columns[0] = 1 -rows[1].columns[1] = 3 -rows[1].columns[2] = 5 - -which can be read into a structure defined like this: - -type vector { - int columns[]; -} - -type matrix { - vector rows[]; -} - -matrix m; - -m = readData2("readData2.in"); - - - - -(since Swift 0.7) - -
    -
    trace - -trace will log its parameters. By default these will appear on both stdout -and in the run log file. Some formatting occurs to produce the log message. -The particular output format should not be relied upon. (since Swift 0.4) - -
    - -
    writeData - -writeData will write out data structures in the format -described for readData - -
    -
    - -
    - - Swift configuration properties - - - - Various aspects of the behavior of the Swift Engine can be - configured through properties. The Swift Engine recognizes a global, - per installation properties file which can found in etc/swift.properties in the Swift installation directory and a user - properties file which can be created by each user in ~/.swift/swift.properties. The Swift Engine - will first load the global properties file. It will then try to load - the user properties file. If a user properties file is found, - individual properties explicitly set in that file will override the - respective properties in the global properties file. Furthermore, - some of the properties can be overridden directly using command line - arguments to the swift command. - - - - - - Swift properties are specified in the following format: - - -<name>=<value> - - - The value can contain variables which will be expanded when the - properties file is read. Expansion is performed when the name of - the variable is used inside the standard shell dereference - construct: ${name}. The following variables - can be used in the Swift configuration file: - - - Swift Configuration Variables - - - - swift.home - - - - - Points to the Swift installation directory - ($SWIFT_HOME). In general, this should not be set -as Swift can find its own installation directory, and incorrectly setting it -may impair the correct functionality of Swift. - - - - - - - - user.name - - - - - The name of the current logged in user. - - - - - - - - user.home - - - - - The user's home directory. - - - - - - - The following is a list of valid Swift properties: - - - Swift Properties - - - - caching.algorithm - - - - - Valid values: LRU - - - - Default value: LRU - - - - - Swift caches files that are staged in on remote - resources, and files that are produced remotely - by applications, such that they can be re-used - if needed without being transfered again. - However, the amount of remote file system space - to be used for caching can be limited using the - swift:storagesize profile - entry in the sites.xml file. Example: - - - -<pool handle="example" sysinfo="INTEL32::LINUX"> - <gridftp url="gsiftp://example.org" storage="/scratch/swift" major="2" minor="4" patch="3"/> - <jobmanager universe="vanilla" url="example.org/jobmanager-pbs" major="2" minor="4" patch="3"/> - <workdirectory>/scratch/swift</workdirectory> - <profile namespace="SWIFT" key="storagesize">20000000</profile> -</pool> - - - - - The decision of which files to keep in the cache - and which files to remove is made considering - the value of the - caching.algorithm property. - Currently, the only available value for this - property is LRU, which would - cause the least recently used files to be - deleted first. - - - - - - - - clustering.enabled - - - - - Valid values: true, false - - - - Default value: false - - - - Enables clustering. - - - - - - - - clustering.min.time - - - - - Valid values: <int> - - - - Default value: 60 - - - - - Indicates the threshold wall time for - clustering, in seconds. Jobs that have a - wall time smaller than the value of this - property will be considered for clustering. - - - - - - - - clustering.queue.delay - - - - - Valid values: <int> - - - - Default value: 4 - - - - - This property indicates the interval, in - seconds, at which the clustering queue is - processed. - - - - - - - execution.retries - - - Valid values: positive integers - - - Default value: 2 - - - The number of time a job will be retried if it - fails (giving a maximum of 1 + - execution.retries attempts at execution) - - - - - - - foreach.max.threads - - - Valid values: positive integers - - - Default value: 1024 - - -Limits the number of concurrent iterations that each foreach statement -can have at one time. This conserves memory for swift programs that -have large numbers of iterations (which would otherwise all be executed -in parallel). (since Swift 0.9) - - - - - - - - ip.address - - - - - Valid values: <ipaddress> - - - - Default value: N/A - - - - The Globus GRAM service uses a callback - mechanism to send notifications about the status - of submitted jobs. The callback mechanism - requires that the Swift client be reachable from - the hosts the GRAM services are running on. - Normally, Swift can detect the correct IP address - of the client machine. However, in certain cases - (such as the client machine having more than one - network interface) the automatic detection - mechanism is not reliable. In such cases, the IP - address of the Swift client machine can be - specified using this property. The value of this - property must be a numeric address without quotes. - - - This option is deprecated and the hostname - property should be used instead. - - - - - - - kickstart.always.transfer - - - - - Valid values: true, false - - - - Default value: false - - - - - This property controls when output from - Kickstart is transfered back to the submit site, - if Kickstart is enabled. When set to - false, Kickstart output is - only transfered for jobs that fail. If set to - true, Kickstart output is - transfered after every job is completed or - failed. - - - - - - - - kickstart.enabled - - - - - Valid values: true, false, maybe - - - - Default value: maybe - - - - - This option allows controlling of - when Swift uses Kickstart. A value of - false disables the use of - Kickstart, while a value of - true enables the use of - Kickstart, in which case sites specified in the - sites.xml file - must have valid - gridlaunch attributes. - The maybe value will - enable the use of Kickstart only - on sites that have the - gridlaunch attribute - specified. - - - - - - - - lazy.errors - - - - - Valid values: true, false - - - - Default value: false - - - - - Swift can report application errors in two - modes, depending on the value of this property. - If set to false, Swift will - report the first error encountered and - immediately stop execution. If set to - true, Swift will attempt to - run as much as possible from a SwiftScript program before - stopping execution and reporting all errors - encountered. - - When developing SwiftScript programs, using the - default value of false can - make the program easier to debug. However - in production runs, using true - will allow more of a SwiftScript program to be run before - Swift aborts execution. - - - - - - - pgraph - - - - - Valid values: true, false, <file> - - - - Default value: false - - - - - Swift can generate a -Graphviz file representing - the structure of the SwiftScript program it has run. If this - property is set to true, - Swift will save the provenance graph in a file - named by concatenating the program name and the - instance ID (e.g. helloworld-ht0adgi315l61.dot). - - - If set to false, no - provenance graph will be generated. If a file - name is used, then the provenance graph will be - saved in the specified file. - - - The generated dot file can be rendered - into a graphical form using - Graphviz, - for example with a command-line such as: - - -$ swift -pgraph graph1.dot q1.swift -$ dot -ograph.png -Tpng graph1.dot - - - - - - - pgraph.graph.options - - - - - Valid values: <string> - - - - Default value: splines="compound", rankdir="TB" - - - - - This property specifies a Graphviz - specific set of parameters for the graph. - - - - - - - - pgraph.node.options - - - - - Valid values: <string> - - - - Default value: color="seagreen", style="filled" - - - - - Used to specify a set of Graphviz - specific properties for the nodes in the graph. - - - - - - - - provenance.log - - - - Valid values: true, false - - - Default value: false - - - This property controls whether the log file will contain provenance information enabling this will increase the size of log files, sometimes significantly. - - - - - - - replication.enabled - - - - - Valid values: true, false - - - - Default value: false - - - -Enables/disables replication. Replication is used to deal with jobs sitting -in batch queues for abnormally large amounts of time. If replication is enabled -and certain conditions are met, Swift creates and submits replicas of jobs, and -allows multiple instances of a job to compete. - - - - - - - replication.limit - - - - - Valid values: positive integers - - - - Default value: 3 - - - -The maximum number of replicas that Swift should attempt. - - - - - - - sitedir.keep - - - - Valid values: true, false - - - - Default value: false - - - -Indicates whether the working directory on the remote site should be -left intact even when a run completes successfully. This can be -used to inspect the site working directory for debugging purposes. - - - - - - - sites.file - - - - - Valid values: <file> - - - - Default value: ${swift.home}/etc/sites.xml - - - - - Points to the location of the site - catalog, which contains a list of all sites that - Swift should use. - - - - - - - - - status.mode - - - - Valid values: files, provider - - - - Default value: files - - - -Controls how Swift will communicate the result code of running user programs -from workers to the submit side. In files mode, a file -indicating success or failure will be created on the site shared filesystem. -In provider mode, the execution provider job status will -be used. - - -provider mode requires the underlying job execution system -to correctly return exit codes. In at least the cases of GRAM2, and clusters -used with any provider, exit codes are not returned, and so -files mode must be used in those cases. Otherwise, -provider mode can be used to reduce the amount of -filesystem access. (since Swift 0.8) - - - - - - - tc.file - - - - Valid values: <file> - - - - Default value: ${swift.home}/etc/tc.data - - - - - Points to the location of the transformation - catalog file which contains information about - installed applications. Details about the format - of the transformation catalog can be found - here. - - - - - - - - tcp.port.range - - - Valid values: <start>,<end> where start and end are integers - Default value: none - -A TCP port range can be specified to restrict the ports on which -GRAM callback services are started. This is likely needed if your - submit host is behind a firewall, in which case the firewall -should be configured to allow incoming connections on ports in -the range. - - - - - - - - throttle.file.operations - - - - - Valid values: <int>, off - - - - Default value: 8 - - - - - Limits the total number of concurrent file - operations that can happen at any given time. - File operations (like transfers) require an - exclusive connection to a site. These - connections can be expensive to establish. A - large number of concurrent file operations may - cause Swift to attempt to establish many such - expensive connections to various sites. Limiting - the number of concurrent file operations causes - Swift to use a small number of cached - connections and achieve better overall - performance. - - - - - - - - throttle.host.submit - - - - - Valid values: <int>, off - - - - Default value: 2 - - - - - Limits the number of concurrent submissions for - any of the sites Swift will try to send jobs to. - In other words it guarantees that no more than - the value of this throttle jobs sent to any - site will be concurrently in a state of being - submitted. - - - - - - - - throttle.score.job.factor - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - The Swift scheduler has the ability to limit - the number of concurrent jobs allowed on a - site based on the performance history of that - site. Each site is assigned a score (initially - 1), which can increase or decrease based on - whether the site yields successful or faulty - job runs. The score for a site can take values - in the (0.1, 100) interval. The number of - allowed jobs is calculated using the - following formula: - - - 2 + score*throttle.score.job.factor - - - This means a site will always be allowed - at least two concurrent jobs and at most - 2 + 100*throttle.score.job.factor. With a - default of 4 this means at least 2 jobs and - at most 402. - - - This parameter can also be set per site - using the jobThrottle profile key in a site - catalog entry. - - - - - - - throttle.submit - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - - Limits the number of concurrent submissions for - a run. This throttle only limits - the number of concurrent tasks (jobs) that are - being sent to sites, not the total number of - concurrent jobs that can be run. The submission - stage in GRAM is one of the most CPU expensive - stages (due mostly to the mutual authentication - and delegation). Having too many concurrent - submissions can overload either or both the - submit host CPU and the remote host/head node - causing degraded performance. - - - - - - - - - throttle.transfers - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - - Limits the total number of concurrent file - transfers that can happen at any given time. - File transfers consume bandwidth. Too many - concurrent transfers can cause the network to be - overloaded preventing various other signaling - traffic from flowing properly. - - - - - - - - ticker.disable - - - - Valid values: true, false - - - - Default value: false - - - -When set to true, suppresses the output progress ticker that Swift sends -to the console every few seconds during a run (since Swift 0.9) - - - - - - - wrapper.invocation.mode - - - -Valid values: absolute, relative - - -Default value: absolute - - -Determines if Swift remote wrappers will be executed by specifying an -absolute path, or a path relative to the job initial working directory. -In most cases, execution will be successful with either option. However, -some execution sites ignore the specified initial working directory, and -so absolute must be used. Conversely on some sites, -job directories appear in a different place on the worker node file system -than on the filesystem access node, with the execution system handling -translation of the job initial working directory. In such cases, -relative mode must be used. (since Swift 0.9) - - - - - - - - wrapper.parameter.mode - - - -Controls how Swift will supply parameters to the remote wrapper script. -args mode will pass parameters on the command line. Some -execution systems do not pass commandline parameters sufficiently cleanly -for Swift to operate correctly. -files mode will pass parameters through an additional -input file (since Swift 0.95). This provides a cleaner communication channel -for parameters, at the expense of transferring an additional file for each -job invocation. - - - - - - - - wrapperlog.always.transfer - - - - - Valid values: true, false - - - - Default value: false - - - - - This property controls when output from - the Swift remote wrapper is transfered - back to the submit site. When set to - false, wrapper logs are - only transfered for jobs that fail. If set to - true, wrapper logs are - transfered after every job is completed or - failed. - - - - - - - - Example: - - -sites.file=${vds.home}/etc/sites.xml -tc.file=${vds.home}/etc/tc.data -ip.address=192.168.0.1 - - - - -
    - - -
    Profiles - -Profiles are configuration parameters than can be specified either for -sites or for transformation catalog entries. They influence the behaviour -of Swift towards that site (for example, by changing the load Swift will -place on that sites) or when running a particular procedure. - - -Profile entries for a site are specified in the site catalog. Profile -entries for specific procedures are specified in the transformation -catalog. - -
    Karajan namespace - maxSubmitRate limits the maximum rate of job submission, in jobs per second. -For example: - -<profile namespace="karajan" key="maxSubmitRate">0.2</profile> - -will limit job submission to 0.2 jobs per second (or equivalently, -one job every five seconds). - - jobThrottle -allows the job throttle factor (see Swift property throttle.score.job.factor) to be set per site. - - initialScore -allows the initial score for rate limiting and site selection to be set to -a value other than 0. - - delayBase controls how much a site will be delayed when it performs poorly. With each reduction -in a sites score by 1, the delay between execution attempts will increase by -a factor of delayBase. - status.mode allows the status.mode property to be set per-site instead of for an entire run. -See the Swift configuration properties section for more information. -(since Swift 0.8) -
    -
    swift namespace - storagesize limits the -amount of space that will be used on the remote site for temporary files. -When more than that amount of space is used, the remote temporary file -cache will be cleared using the algorithm specified in the -caching.algorithm property. - - wrapperInterpreter -The wrapper interpreter indicates the command (executable) to be used to run the Swift wrapper -script. The default is "/bin/bash" on Unix sites and "cscript.exe" on Windows sites. - - wrapperInterpreterOptions -Allows specifying additional options to the executable used to run the Swift wrapper. The defaults -are no options on Unix sites and "//Nologo" on Windows sites. - - wrapperScript -Specifies the name of the wrapper script to be used on a site. The defaults are "_swiftwrap" on -Unix sites and "_swiftwrap.vbs" on Windows sites. If you specify a custom wrapper script, it -must be present in the "libexec" directory of the Swift installation. - - cleanupCommand -Indicates the command to be run at the end of a Swift run to clean up the run directories on a -remote site. Defaults are "/bin/rm" on Unix sites and "cmd.exe" on Windows sites - - cleanupCommandOptions -Specifies the options to be passed to the cleanup command above. The options are passed in the -argument list to the cleanup command. After the options, the last argument is the directory -to be deleted. The default on Unix sites is "-rf". The default on Windows sites is ["/C", "del", "/Q"]. - - -
    -
    Globus namespace - maxwalltime specifies a walltime limit for each job, in minutes. - - -The following formats are recognized: - - Minutes - Hours:Minutes - Hours:Minutes:Seconds - - - Example: - -localhost echo /bin/echo INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:20:00" - - When replication is enabled (see replication), then walltime will also be enforced at the Swift client side: when -a job has been active for more than twice the maxwalltime, Swift will kill the -job and regard it as failed. - - -When clustering is used, maxwalltime will be used to -select which jobs will be clustered together. More information on this is -available in the clustering section. - - -When coasters as used, maxwalltime influences the default -coaster worker maxwalltime, and which jobs will be sent to which workers. -More information on this is available in the coasters -section. - - queue -is used by the PBS, GRAM2 and GRAM4 providers. This profile -entry specifies which queue jobs will be submitted to. The valid queue names -are site-specific. - - host_types -specifies the types of host that are permissible for a job to run on. -The valid values are site-specific. This profile entry is used by the -GRAM2 and GRAM4 providers. - - condor_requirements allows a requirements string to be specified -when Condor is used as an LRM behind GRAM2. Example: <profile namespace="globus" key="condor_requirements">Arch == "X86_64" || Arch="INTEL"</profile> - - slots -When using coasters, this parameter -specifies the maximum number of jobs/blocks that the coaster scheduler will have running at any given time. -The default is 20. - - workersPerNode -This parameter determines how many coaster workers are -started one each compute node. The default value is 1. - - nodeGranularity -When allocating a coaster worker block, this parameter -restricts the number of nodes in a block to a multiple of this value. The total number of workers will -then be a multiple of workersPerNode * nodeGranularity. The default value is 1. - - allocationStepSize -Each time the coaster block scheduler computes a schedule, it will attempt to allocate a -number of slots from the number of available slots (limited using the above slots profile). This -parameter specifies the maximum fraction of slots that are allocated in one schedule. Default is -0.1. - - lowOverallocation -Overallocation is a function of the walltime of a job which determines how long (time-wise) a -worker job will be. For example, if a number of 10s jobs are submitted to the coaster service, -and the overallocation for 10s jobs is 10, the coaster scheduler will attempt to start worker -jobs that have a walltime of 100s. The overallocation is controlled by manipulating the end-points -of an overallocation function. The low endpoint, specified by this parameter, is the overallocation -for a 1s job. The high endpoint is the overallocation for a (theoretical) job of infinite length. -The overallocation for job sizes in the [1s, +inf) interval is determined using an exponential decay function: - -overallocation(walltime) = walltime * (lowOverallocation - highOverallocation) * exp(-walltime * overallocationDecayFactor) + highOverallocation - -The default value of lowOverallocation is 10. - - highOverallocation -The high overallocation endpoint (as described above). Default: 1 - - overallocationDecayFactor -The decay factor for the overallocation curve. Default 0.001 (1e-3). - - spread -When a large number of jobs is submitted to the a coaster service, the work is divided into blocks. This -parameter allows a rough control of the relative sizes of those blocks. A value of 0 indicates that all work -should be divided equally between the blocks (and blocks will therefore have equal sizes). A value of 1 -indicates the largest possible spread. The existence of the spread parameter is based on the assumption -that smaller overall jobs will generally spend less time in the queue than larger jobs. By submitting -blocks of different sizes, submitted jobs may be finished quicker by smaller blocks. Default: 0.9. - - reserve -Reserve time is a time in the allocation of a worker that sits at the end of the worker time and -is useable only for critical operations. For example, a job will not be submitted to a worker if -it overlaps its reserve time, but a job that (due to inaccurate walltime specification) runs into -the reserve time will not be killed (note that once the worker exceeds its walltime, the queuing -system will kill the job anyway). Default 10 (s). - - maxnodes -Determines the maximum number of nodes that can be allocated in one coaster block. Default: unlimited. - - maxtime -Indicates the maximum walltime that a coaster block can have. Default: unlimited. - - remoteMonitorEnabled -If set to "true", the client side will get a Swing window showing, graphically, the state of the -coaster scheduler (blocks, jobs, etc.). Default: false - - -
    - -
    env namespace - -Profile keys set in the env namespace will be set in the unix environment of the -executed job. Some environment variables influence the worker-side -behaviour of Swift: - - -PATHPREFIX - set in env namespace profiles. This path is prefixed onto the start -of the PATH when jobs are -executed. It can be more useful than setting the PATH environment variable directly, -because setting PATH will cause the execution site's default path to be lost. - - -SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift will -use the path specified here as a worker-node local temporary directory to -copy input files to before running a job. If unset, Swift will keep input -files on the site-shared filesystem. In some cases, copying to a worker-node -local directory can be much faster than having applications access the -site-shared filesystem directly. - - -SWIFT_EXTRA_INFO - set in env namespace profiles. If set, -then Swift will execute the command specified in -SWIFT_EXTRA_INFO on execution sites immediately before -each application execution, and will record the stdout of that command in the -wrapper info log file for that job. This is intended to allow software -version and other arbitrary information about the remote site to be gathered -and returned to the submit side. (since Swift 0.9) - -
    -
    - -
    The Site Catalog - sites.xml - -The site catalog lists details of each site that Swift can use. The default -file contains one entry for local execution, and a large number of -commented-out example entries for other sites. - - - -By default, the site catalog is stored in etc/sites.xml. -This path can be overridden with the sites.file configuration property, -either in the Swift configuration file or on the command line. - - - -The sites file is formatted as XML. It consists of <pool> elements, -one for each site that Swift will use. - - -
    Pool element - -Each pool element must have a handle attribute, giving a symbolic name -for the site. This can be any name, but must correspond to entries for -that site in the transformation catalog. - - - -Optionally, the gridlaunch attribute can be used to specify the path to -kickstart on the site. - - - -Each pool must specify a file transfer method, an execution method -and a remote working directory. Optionally, profile settings can be specified. - - -
    -
    File transfer method - - -Transfer methods are specified with either -the <gridftp> element or the -<filesystem> element. - - -To use gridftp or local filesystem copy, use the <gridftp> -element: - -<gridftp url="gsiftp://evitable.ci.uchicago.edu" /> - -The url attribute may specify a GridFTP server, using the gsiftp URI scheme; -or it may specify that filesystem copying will be used (which assumes that -the site has access to the same filesystem as the submitting machine) using -the URI local://localhost. - - -Filesystem access using scp (the SSH copy protocol) can be specified using the -<filesystem> element: - -<filesystem url="www11.i2u2.org" provider="ssh"/> - -For additional ssh configuration information, see the ssh execution -provider documentation below. - - -Filesystem access using CoG coasters can be -also be specified using the <filesystem> element. More detail about -configuring that can be found in the CoG -coasters section. - -
    - -
    Execution method - - -Execution methods may be specified either with the <jobmanager> -or <execution> element. - - - -The <jobmanager> element can be used to specify -execution through GRAM2. For example, - - <jobmanager universe="vanilla" url="evitable.ci.uchicago.edu/jobmanager-fork" major="2" /> - -The universe attribute should always be set to vanilla. The -url attribute -should specify the name of the GRAM2 gatekeeper host, and the name of the -jobmanager to use. The major attribute should always be set to 2. - - - -The <execution> element can be used to specify -execution through other execution providers: - - -To use GRAM4, specify the gt4 provider. For example: - -<execution provider="gt4" jobmanager="PBS" url="tg-grid.uc.teragrid.org" /> - -The url attribute should specify the GRAM4 submission site. -The jobmanager -attribute should specify which GRAM4 jobmanager will be used. - - - -For local execution, the local provider should be used, -like this: - -<execution provider="local" url="none" /> - - - - -For PBS execution, the pbs provider should be used: - -<execution provider="pbs" url="none" /> - -The GLOBUS::queue profile key -can be used to specify which PBS queue jobs will be submitted to. - - - -For execution through a local Condor installation, the condor -provider should be used. This provider can run jobs either in the default -vanilla universe, or can use Condor-G to run jobs on remote sites. - - -When running locally, only the <execution> element -needs to be specified: - -<execution provider="condor" url="none" /> - - - -When running with Condor-G, it is necessary to specify the Condor grid -universe and the contact string for the remote site. For example: - - <execution provider="condor" /> - <profile namespace="globus" key="jobType">grid</profile> - <profile namespace="globus" key="gridResource">gt2 belhaven-1.renci.org/jobmanager-fork</profile> - - - - -For execution through SSH, the ssh provider should be used: - -<execution url="www11.i2u2.org" provider="ssh"/> - -with configuration made in ~/.ssh/auth.defaults with -the string 'www11.i2u2.org' changed to the appropriate host name: - -www11.i2u2.org.type=key -www11.i2u2.org.username=hategan -www11.i2u2.org.key=/home/mike/.ssh/i2u2portal -www11.i2u2.org.passphrase=XXXX - - - -For execution using the -CoG Coaster mechanism, the coaster provider -should be used: - -<execution provider="coaster" url="tg-grid.uc.teragrid.org" - jobmanager="gt2:gt2:pbs" /> - -More details about configuration of coasters can be found in the -section on coasters. - -
    -
    Work directory - - -The workdirectory element specifies where on the site files can be -stored. - -<workdirectory>/home/benc</workdirectory> - -This file must be accessible through the transfer mechanism specified -in the <gridftp> element and also mounted on all worker nodes that -will be used for execution. A shared cluster scratch filesystem is -appropriate for this. - - -
    -
    Profiles - - -Profile keys can be specified using -the <profile> element. For example: - -<profile namespace="globus" key="queue">fast</profile> - - -
    - - -The site catalog format is an evolution of the VDS site catalog format which -is documented -here. - -
    - -
    The Transformation Catalog - tc.data - -The transformation catalog lists where application executables are located -on remote sites. - - -By default, the site catalog is stored in etc/tc.data. -This path can be overridden with the tc.file configuration property, -either in the Swift configuration file or on the command line. - - -The format is one line per executable per site, with fields separated by -tabs. Spaces cannot be used to separate fields. - - Some example entries: - -localhost echo /bin/echo INSTALLED INTEL32::LINUX null -localhost touch /bin/touch INSTALLED INTEL32::LINUX null - -TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1" -TGUC R /usr/bin/R INSTALLED INTEL32::LINUX env::R_LIBS=/home/skenny/R_libs - - - -The fields are: site, transformation name, executable path, installation -status, platform, and profile entries. - - -The site field should correspond to a site name listed in the sites -catalog. - -The transformation name should correspond to the transformation name -used in a SwiftScript app procedure. - - -The executable path should specify where the particular executable is -located on that site. - - -The installation status and platform fields are not used. Set them to -INSTALLED and INTEL32::LINUX respectively. - - -The profiles field should be set to null if no profile entries are to be -specified, or should contain the profile entries separated by semicolons. - - -
    shell invocation - -Because the above implementation requires an entry for each executable on a given site, it is often preferable to simply have a single element for each site in the transformation catalog representing a wrapper that sets the environment and then invokes the shell to call a given application. This wrapper is installed on the site and can be used to set the PATH and other environment variables prior to invoking the shell so that each executable need not be entered in the tc.data file. - - for example, the entries for TGUC and localhost can now each be collapsed into a single line: - -localhost shell /usr/local/bin/swiftshell INSTALLED INTEL32::LINUX null -TGUC shell /usr/local/bin/swiftshell INSTALLED INTEL32::LINUX null - -where swiftshell sets up the users's environment so that all the installed applications are added to the PATH before the application is invoked. - - -touch would now be called in the SwiftScript like this: - -app (file tout) shelltest(){ - shell "touch" @filename(tout); -} - - -
    -
    - -
    Build options - -See the -Swift download page for instructions on downloading and -building Swift from source. When building, various build options can -be supplied on the ant commandline. These are summarised here: - - -with-provider-condor - build with CoG condor provider - - -with-provider-coaster - build with CoG coaster provider (see -the section on coasters). Since 0.8, -coasters are always built, and this option has no effect. - - -with-provider-deef - build with Falkon provider deef. In order for this -option to work, it is necessary to check out the provider-deef code in -the cog/modules directory alongside swift: - - -$ cd cog/modules -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef -$ cd ../swift -$ ant -Dwith-provider-deef=true redist - - - - -with-provider-wonky - build with provider-wonky, an execution provider -that provides delays and unreliability for the purposes of testing Swift's -fault tolerance mechanisms. In order for this option to work, it is -necessary to check out the provider-wonky code in the cog/modules -directory alongside swift: - - -$ cd cog/modules -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky -$ cd ../swift -$ ant -Dwith-provider-wonky=true redist - - - -no-supporting - produces a distribution without supporting commands such -as grid-proxy-init. This is intended for when the Swift distribution will be -used in an environment where those commands are already provided by other -packages, where the Swift package should be providing only Swift -commands, and where the presence of commands such as grid-proxy-init from -the Swift distribution in the path will mask the presence of those -commands from their true distribution package such as a Globus Toolkit -package. - -$ ant -Dno-supporting=true redist - - -
    - -
    Kickstart - - -Kickstart is a tool that can be used to gather various information -about the remote execution environment for each job that Swift tries -to run. - - - -For each job, Kickstart generates an XML invocation -record. By default this record is staged back to the submit -host if the job fails. - - - -Before it can be used it must be installed on the remote site and -the sites file must be configured to point to kickstart. - - - -Kickstart can be downloaded as part of the Pegasus 'worker package' available -from the worker packages section of the Pegasus download page. - - -Untar the relevant worker package somewhere where it is visible to all of the -worker nodes on the remote execution machine (such as in a shared application -filesystem). - - -Now configure the gridlaunch attribute of the sites catalog -to point to that path, by adding a gridlaunch -attribute to the pool element in the site -catalog: - - - -<pool handle="example" gridlaunch="/usr/local/bin/kickstart" sysinfo="INTEL32::LINUX"> -[...] -</pool> - - - - - - -There are various kickstat.* properties, which have sensible default -values. These are documented in the -properties section. - - - - -
    - -
    Reliability mechanisms - -This section details reliabilty mechanisms in Swift: retries, restarts -and replication. - - -
    Retries - -If an application procedure execution fails, Swift will attempt that -execution again repeatedly until it succeeds, up until the limit -defined in the execution.retries configuration -property. - - -Site selection will occur for retried jobs in the same way that it happens -for new jobs. Retried jobs may run on the same site or may run on a -different site. - - -If the retry limit execution.retries is reached for an -application procedure, then that application procedure will fail. This will -cause the entire run to fail - either immediately (if the -lazy.errors property is false) or -after all other possible work has been attempted (if the -lazy.errors property is true). - -
    - -
    Restarts - -If a run fails, Swift can resume the program from the point of -failure. When a run fails, a restart log file will be left behind in -a file named using the unique job ID and a .rlog extension. This restart log -can then be passed to a subsequent Swift invocation using the -resume -parameter. Swift will resume execution, avoiding execution of invocations -that have previously completed successfully. The SwiftScript source file -and input data files should not be modified between runs. - - -Every run creates a restart -log file with a named composed of the file name of the workflow -being executed, an invocation ID, a numeric ID, and the .rlog extension. For example, example.swift, when executed, could produce -the following restart log file: example-ht0adgi315l61.0.rlog. Normally, if -the run completes successfully, the restart log file is -deleted. If however the workflow fails, swift -can use the restart log file to continue -execution from a point before the -failure occurred. In order to restart from a restart log -file, the argument can be -used after the SwiftScript program file name. Example: - - -$ swift . - - - -
    - -
    Replication - -When an execution job has been waiting in a site queue for a certain -period of time, Swift can resubmit replicas of that job (up to the limit -defined in the replication.limit configuration property). -When any of those jobs moves from queued to active state, all of the -other replicas will be cancelled. - - -This is intended to deal with situations where some sites have a substantially -longer (sometimes effectively infinite) queue time than other sites. -Selecting those slower sites can cause a very large delay in overall run time. - - -Replication can be enabled by setting the -replication.enabled configuration property to -true. The maximum number of replicas that will be -submitted for a job is controlled by the replication.limit -configuration property. - - -When replication is enabled, Swift will also enforce the -maxwalltime profile setting for jobs as documented in -the profiles section. - -
    - -
    - -
    Clustering - -Swift can group a number of short job submissions into a single larger -job submission to minimize overhead involved in launching jobs (for example, -caused by security negotiation and queuing delay). In general, -CoG coasters should be used in preference -to the clustering mechanism documented in this section. - - - -By default, clustering is disabled. It can be activated by setting the -clustering.enabled -property to true. - - - -A job is eligible for clustering if -the GLOBUS::maxwalltime profile is specified in the tc.data entry for that job, and its value is -less than the value of the -clustering.min.time -property. - - - -Two or more jobs are considered compatible if they share the same site -and do not have conflicting profiles (e.g. different values for the same -environment variable). - - - -When a submitted job is eligible for clustering, -it will be put in a clustering queue rather than being submitted to -a remote site. The clustering queue is processed at intervals -specified by the -clustering.queue.delay -property. The processing of the clustering queue consists of selecting -compatible jobs and grouping them into clusters whose maximum wall time does -not exceed twice the value of the clustering.min.time -property. - - - -
    - - - -
    Coasters -Coasters were introduced in Swift v0.6 as an experimental feature. - - -In many applications, Swift performance can be greatly enhanced by the -use of CoG coasters. CoG coasters provide a low-overhead job submission -and file transfer mechanism suited for the execution of short jobs -(on the order of a few seconds) and the transfer of small files (on the -order of a few kilobytes) for which other grid protocols such as GRAM -and GridFTP are poorly suited. - - -The coaster mechanism submits a head job using some other execution -mechanism such as GRAM, and for each worker node that will be used in -a remote cluster, it submits a worker job, again using some other -execution mechanism such as GRAM. Details on the design of the coaster -mechanism can be found - -here. - - -The head job manages file transfers and the dispatch of execution jobs -to workers. Much of the overhead associated with other grid protocols -(such as authentication and authorization, and allocation of worker nodes -by the site's local resource manager) is reduced, because that overhead -is associated with the allocation of a coaster head or coaster worker, -rather than with every Swift-level procedure invocation; potentially hundreds -or thousands of Swift-level procedure invocations can be run through a single -worker. - - -Coasters can be configured for use in two situations: job execution and -file transfer. - - -To use for job execution, specify a sites.xml execution element like this: - -<execution provider="coaster" jobmanager="gt2:gt2:pbs" url="grid.myhost.org"> - -The jobmanager string contains more detail than with other providers. It -contains either two or three colon separated fields: -1:the provider to be use to execute the coaster head job - this provider -will submit from the Swift client side environment. Commonly this will be -one of the GRAM providers; 2: the provider -to be used to execute coaster worker jobs. This provider will be used -to submit from the coaster head job environment, so a local scheduler -provider can sometimes be used instead of GRAM. 3: optionally, the -jobmanager to be used when submitting worker job using the provider -specified in field 2. - - -To use for file transfer, specify a sites.xml filesystem element like this: - -<filesystem provider="coaster" url="gt2://grid.myhost.org" /> - -The url parameter should be a pseudo-URI formed with the URI scheme being -the name of the provider to use to submit the coaster head job, and the -hostname portion being the hostname to be used to execute the coaster -head job. Note that this provider and hostname will be used for execution -of a coaster head job, not for file transfer; so for example, a GRAM -endpoint should be specified here rather than a GridFTP endpoint. - - -Coasters are affected by the following profile settings, which are -documented in the Globus namespace profile -section: - - - - - profile keybrief description - - slotsHow many maximum LRM jobs/worker blocks are allowed - workersPerNodeHow many coaster workers to run per execution node - nodeGranularityEach worker block uses a number of nodes that is a multiple of this number - lowOverallocationHow many times larger than the job walltime should a block's walltime be if all jobs are 1s long - highOverallocationHow many times larger than the job walltime should a block's walltime be if all jobs are infinitely long - overallocationDecayFactorHow quickly should the overallocation curve tend towards the highOverallocation as job walltimes get larger - spreadBy how much should worker blocks vary in worker size - workersPerNodeHow many coaster workers to run per execution node - reserveHow many seconds to reserve in a block's walltime for starting/shutdown operations - maxnodesThe maximum number of nodes allowed in a block - maxtimeThe maximum number of walltime allowed for a block - remoteMonitorEnabledIf true, show a graphical display of the status of the coaster service - - -
    -
    -
    How-To Tips for Specific User Communities -
    Saving Logs - for UChicago CI Users - -If you have a UChicago Computation Institute account, run this command in your -submit directory after each run. It will copy all your logs and kickstart -records into a directory at the CI for reporting, usage tracking, support and debugging. - - - -rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose - - -
    -
    Specifying TeraGrid allocations -TeraGrid users with no default project or with several project -allocations can specify a project allocation using a profile key in -the site catalog entry for a TeraGrid site: - -<profile namespace="globus" key="project">TG-CCR080002N</profile> - - - - -More information on the TeraGrid allocations process can -be found here. - - -
    -
    Launching MPI jobs from Swift - -Here is an example of running a simple MPI program. - - -In SwiftScript, we make an invocation that does not look any different -from any other invocation. In the below code, we do not have any input -files, and have two output files on stdout and stderr: - -type file; - -(file o, file e) p() { - app { - mpi stdout=@filename(o) stderr=@filename(e); - } -} - -file mpiout <"mpi.out">; -file mpierr <"mpi.err">; - -(mpiout, mpierr) = p(); - - - -Now we define how 'mpi' will run in tc.data: - -tguc mpi /home/benc/mpi/mpi.sh INSTALLED INTEL32::LINUX GLOBUS::host_xcount=3 - - - -mpi.sh is a wrapper script that launches the MPI program. It must be installed -on the remote site: - -#!/bin/bash -mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out - - - -Because of the way that Swift runs its server side code, provider-specific -MPI modes (such as GRAM jobType=mpi) should not be used. Instead, the -mpirun command should be explicitly invoked. - -
    -
    Running on Windows - - - Since 10/11/09, the development version of Swift has the -ability to run on a Windows machine, as well as the ability to submit -jobs to a Windows site (provided that an appropriate provider is used). - - - - -In order to launch Swift on Windows, use the provided batch file -(swift.bat). In certain cases, when a large number of jar libraries are -present in the Swift lib directory and depending on the exact location -of the Swift installation, the classpath environment variable that the -Swift batch launcher tries to create may be larger than what Windows can -handle. In such a case, either install Swift in a directory closer to -the root of the disk (say, c:\swift) or remove non-essential jar files -from the Swift lib directory. - - - - - -Due to the large differences between Windows and Unix environments, -Swift must use environment specific tools to achieve some of its goals. -In particular, each Swift executable is launched using a wrapper script. -This script is a Bourne Shell script. On Windows machines, which have no -Bourne Shell interpreter installed by default, the Windows Scripting -Host is used instead, and the wrapper script is written in VBScript. -Similarly, when cleaning up after a run, the "/bin/rm" command available -in typical Unix environments must be replaced by the "del" shell command. - - - - - -It is important to note that in order to select the proper set of tools -to use, Swift must know when a site runs under Windows. To inform Swift -of this, specify the "sysinfo" attribute for the "pool" element in the -site catalog. For example: - - - <pool handle="localhost" sysinfo="INTEL32::WINDOWS"> - ... - </pool> - - - -
    -
    - -
    - Collective Data Management - - - -CDM Features - -Overview: - - 1. The user specifies a CDM policy in a file, customarily fs.data. - 2. fs.data is given to Swift on the command line. - 3. The Swift data module (org.globus.swift.data) is informed of the CDM policy. - 4. At job launch time, the VDL Karajan code queries the CDM policy, - 1. altering the file staging phase, and - 2. sending fs.data to the compute site. - 5. At job run time, the Swift wrapper script - 1. consults a Perl script to obtain policy, and - 2. uses wrapper extensions to modify data movement. - 6. Similarly, stage out can be changed. - - -Command line: - - * swift -sites.file sites.xml -tc.file tc.data -cdm.file fs.data stream.swift - - -CDM policy file format: - -Example: - -# Describe CDM for my job -property GATHER_LIMIT 1 -rule .*input.txt DIRECT /gpfs/homes/wozniak/data -rule .*xfile*.data BROADCAST /dev/shm -rule .* DEFAULT - -The lines contain: - - 1. A directive, either rule or property - 2. A rule has: - 1. A regular expression - 2. A policy token - 3. Additional policy-specific arguments - 3. A property has - 1. A policy property token - 2. The token value - 4. Comments with # . - 5. Blank lines are ignored. - - -Notes: - - 1. The policy file is used as a lookup database by Swift and Perl methods. - 2. For example, a lookup with the database above given the argument input.txt would result in the Direct policy. - 3. If the lookup does not succeed, the result is DEFAULT. - 4. Policies are listed as subclasses of org.globus.swift.data.policy.Policy . - - -Policy Descriptions: - -Default: - - * Just use file staging as provided by Swift/CoG. Identical to behavior if no CDM file is given. - - -Broadcast: - - rule .*xfile*.data BROADCAST /dev/shm - - * The input files matching the pattern will be stored in the given directory, an LFS location, with links in the job directory. - * On the BG/P, this will make use of the f2cn tool. - * On machines not implementing an efficient broadcast, we will just ensure correctness. For example, on a workstation, the location could be in a /tmp RAM FS. - - -Direct: - - rule .*input.txt DIRECT /gpfs/scratch/wozniak/ - - * Allows for direct I/O to the parallel FS without staging. - * The input files matching the pattern must already exist in the given directory, a GFS location. Links will be placed in the job directory. - * The output files matching the pattern will be stored in the given directory, with links in the job directory. - * Example: In the rule above, the Swift-generated file name ./data/input.txt would be accessed by the user job in /gpfs/homes/wozniak/data/input.txt . - - -Local: - - rule .*input.txt LOCAL dd /gpfs/homes/wozniak/data obs=64K - - * Allows for client-directed input copy to the compute node. - * The user may specify cp or dd as the input transfer program. - - * The input files matching the pattern must already exist in the given directory, a GFS location. Copies will be placed in the job directory. - * Argument list: [tool] [GFS directory] [tool arguments]* - - -Gather: - - property GATHER_LIMIT 500000000 # 500 MB - property GATHER_DIR /dev/shm/gather - property GATHER_TARGET /gpfs/wozniak/data/gather_target - rule .*.output.txt GATHER - - * The output files matching the pattern will be present to tasks in the job directory as usual but noted in a _swiftwrap shell array GATHER_OUTPUT. - * The GATHER_OUTPUT files will be cached in the GATHER_DIR, an LFS location. - * The cache will be flushed when a job ends if a du on GATHER_DIR exceeds GATHER_LIMIT. - * As the cache fills or on stage out, the files will be bundled into randomly named tarballs in GATHER_TARGET, a GFS location. - * If the compute node is an SMP, GATHER_DIR is a shared resource. It is protected by the link file GATHER_DIR/.cdm.lock . - * Unpacking the tarballs in GATHER_TARGET will produce the user-specified filenames. - - Summary: - - 1. Files created by application - 2. Acquire lock - 3. Move files to cache - 4. Check cache size - 5. If limit exceeded, move all cache files to outbox - 6. Release lock - 7. If limit was exceeded, stream outbox as tarball to target - - - Notes: - - * Gather required quite a bit of shell functionality to manage the lock, etc. This is placed in cdm_lib.sh . - * vdl_int.k needed an additional task submission (cdm_cleanup.sh) to perform the final flush at workflow completion time . This task also uses cdm_lib.sh . - - -VDL/Karajan processing: - - 1. CDM functions are available in Karajan via the cdm namespace. - 2. These functions are defined in org.globus.swift.data.Query . - 3. If CDM is enabled, VDL skips file staging for files unless the policy is DEFAULT. - - -Swift wrapper CDM routines: - - 1. The cdm.pl script is shipped to the compute node if CDM is enabled. - 2. When linking in inputs, CDM is consulted by _swiftwrap:cdm_lookup(). - 3. The cdm_action() shell function handles CDM methods, typically just producing a link. - - -Test case: - -(See About.txt for more information.) - - 1. Simple test cases are in: - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts/cdm-direct and - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts/all-pairs - 2. Do a: - mkdir cdm - cd cdm - svn co https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts - 3. In cdm-direct, run: - source ./setup.sh local local local - 4. Run workflow: - swift -sites.file sites.xml -tc.file tc.data -cdm.file fs.data stream.swift - 5. Note that staging is skipped for input.txt - policy: file://localhost/input.txt : DIRECT - FILE_STAGE_IN_START file=input.txt ... - FILE_STAGE_IN_SKIP file=input.txt policy=DIRECT - FILE_STAGE_IN_END file=input.txt ... - 6. In the wrapper output, the input file is handled by CDM functionality: - Progress 2010-01-21 13:50:32.466572727-0600 LINK_INPUTS - CDM_POLICY: DIRECT /homes/wozniak/cdm/scripts/cdm-direct - CDM: jobs/t/cp_sh-tkul4nmj input.txt DIRECT /homes/wozniak/cdm/scripts/cdm-direct - CDM[DIRECT]: Linking jobs/t/cp_sh-tkul4nmj/input.txt to /homes/wozniak/cdm/scripts/cdm-direct/input.txt - Progress 2010-01-21 13:50:32.486016708-0600 EXECUTE - 7. all-pairs is quite similar but uses more policies. - - -PTMap case: - - 1. Start with vanilla PTMap: - cd cdm - mkdir apps - cd apps - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/apps/ptmap - 2. Source setup.sh - 3. Use start.sh, which - 1. applies CDM policy from fs.local.data - - -CDM site-aware policy file format: - -Example: - -# Describe CDM for my job -# Use DIRECT and BROADCAST if on cluster1, else use DEFAULT behavior -property GATHER_LIMIT 1 -rule cluster1 .*input.txt DIRECT /gpfs/homes/wozniak/data -rule cluster1 .*xfile*.data BROADCAST /dev/shm -rule ANYWHERE .* DEFAULT - -The lines contain: - - 1. A directive, either rule or property - 2. A rule has: - 1. A regular expression for site matchin - 2. A regular expression for filename matching - 3. A policy token - 4. Additional policy-specific arguments - 3. A property has - 1. A policy property token - 2. The token value - 4. Comments with # . - 5. Blank lines are ignored. - - - -
    -
    - From davidk at ci.uchicago.edu Mon May 16 14:38:03 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Mon, 16 May 2011 19:38:03 -0000 Subject: [Swift-commit] r4480 - in trunk/docs: . cookbook tutorial userguide Message-ID: <20110516193802.8F5A79CC94@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-16 14:38:01 -0500 (Mon, 16 May 2011) New Revision: 4480 Added: trunk/docs/build_docs.sh trunk/docs/cookbook/ trunk/docs/cookbook/cookbook-asciidoc.html trunk/docs/cookbook/cookbook-asciidoc.pdf trunk/docs/cookbook/cookbook-asciidoc.txt trunk/docs/tutorial/ trunk/docs/tutorial/tutorial.html trunk/docs/tutorial/tutorial.pdf trunk/docs/tutorial/tutorial.txt trunk/docs/userguide/ trunk/docs/userguide/swift-site-model.png trunk/docs/userguide/type-hierarchy.png trunk/docs/userguide/userguide.html trunk/docs/userguide/userguide.txt Removed: trunk/docs/Makefile trunk/docs/README.txt trunk/docs/build-chunked-userguide.sh trunk/docs/buildguides.sh trunk/docs/formatting/ trunk/docs/historical/ trunk/docs/log-processing.xml trunk/docs/plot-tour.xml trunk/docs/plot-tour/ trunk/docs/provenance.xml trunk/docs/quickstartguide.xml trunk/docs/reallyquickstartguide.xml trunk/docs/swift-site-model.fig trunk/docs/swift-site-model.png trunk/docs/tutorial-live.xml trunk/docs/tutorial.xml trunk/docs/type-hierarchy.fig trunk/docs/type-hierarchy.png trunk/docs/userguide-rotated.jpeg trunk/docs/userguide-shane.jpeg trunk/docs/userguide.xml Log: Updated asciidoc guides Deleted: trunk/docs/Makefile =================================================================== --- trunk/docs/Makefile 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/Makefile 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,35 +0,0 @@ - -# FOP = fop -FOP = fop/fop.sh - -all: phps pdfs - -phps: userguide.php tutorial.php tutorial-live.php quickstartguide.php reallyquickstartguide.php provenance.php historical/languagespec.php historical/languagespec-0.6.php log-processing.php plot-tour.php - -htmls: userguide.html tutorial.html tutorial-live.html quickstartguide.html reallyquickstartguide.html provenance.html historical/languagespec.html historical/languagespec-0.6.html log-processing.html plot-tour.html - -pdfs: userguide.pdf tutorial.pdf tutorial-live.pdf quickstartguide.pdf reallyquickstartguide.pdf provenance.pdf historical/languagespec.pdf historical/languagespec-0.6.pdf log-processing.pdf - -GUIDE_PHP=$(shell find userguide -name "*.php" ) -GUIDE_HTML=$(patsubst %.php,%.html,$(GUIDE_PHP)) - -guide_html: $(GUIDE_HTML) - -chunked-userguide: userguide.xml - ./build-chunked-userguide.sh - -%.php: %.xml formatting/swiftsh_html.xsl - xsltproc --nonet formatting/swiftsh_html.xsl $< - sed -e "s/index.html#/#/g" index.html >$@ - chmod a+rx $@ - -%.pdf: %.xml formatting/vdl2_fo.xsl - $(FOP) -xsl formatting/vdl2_fo.xsl -xml $< -pdf $@ - chmod a+rx $@ - -%.html: %.php - cp $< $@ - chmod a+rx $@ - -clean: - rm -fv *.php userguide/*.php Deleted: trunk/docs/README.txt =================================================================== --- trunk/docs/README.txt 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/README.txt 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,69 +0,0 @@ -Swift Documentation -=================== - -General principles: - - - sections and subsections are ordered from , , or using - arbitrary depth
    tags - - code samples are given inside tags, which will cause - syntax highlighting to happen automatically - - user interactions / screen output are given inside tags. - - be careful to escape in-text "<" to "<" - - there are some conventions for using id attributes at various - places in the documents - for example, some tutorial sections use - 'tutorial.'; profile entries in the user guide use - 'profile..'. Try to keep id attributes unique across - the entire document set. - -The first time guides are built in a particular checkout, it is necessary -to place the docbook formatting stylesheets under the formatting/docbook/ -directory. This can be done with a symlink if docbook is installed elsewhere. - -For example: - -A) On the CI network, /home/hategan/docbook contains a docbook installation that -can be linked like this: - -$ cd formatting -$ ln -s /home/hategan/docbook/ docbook - - -B) on benc's os x machine: - -# install docbook from DarwinPorts -$ sudo port install docbook-xsl - -# setup links -$ cd formatting -$ ln -s /opt/local/share/xsl/docbook-xsl/ docbook - -C) in general: - - 1) Install Apache - - 2) Install PHP (cf. http://dan.drydog.com/apache2php.html) - - 3) Add these lines to Apache's httpd.conf: - - AddHandler php5-script php - AddType text/html php - - 4) Update httpd.conf, adding index.php: - - DirectoryIndex index.html index.php - - 5) Make sure perms are correct - - 6) Create formatting/docbook link (see above) - - 7) Create fop link - -Once the links are set up, the buildguides.sh script will build all guides -as php. Run it with no parameters, like this: - -$ ./buildguides.sh - -or use make to get HTML documents like this: - -$ make userguide.html - Deleted: trunk/docs/build-chunked-userguide.sh =================================================================== --- trunk/docs/build-chunked-userguide.sh 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/build-chunked-userguide.sh 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,11 +0,0 @@ -#!/bin/sh - -mkdir -p userguide/ || exit 1 -cd userguide/ || exit 2 -rm -f *.html *.php -cp ../*.png . -cp ../*.jpeg . - -xsltproc --nonet ../formatting/swiftsh_html_chunked.xsl ../userguide.xml -chmod a+r *.php - Added: trunk/docs/build_docs.sh =================================================================== --- trunk/docs/build_docs.sh (rev 0) +++ trunk/docs/build_docs.sh 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,33 @@ +#!/bin/bash + +if [ -n "$1" ]; then + INSTALLATION_DIRECTORY=$1 +else + echo Error: Must specify a directory for installation + exit 1 +fi + +if [ ! -d "$INSTALLATION_DIRECTORY" ]; then + mkdir $INSTALLATION_DIRECTORY || exit 1 +fi + +echo Installing docs into $INSTALLATION_DIRECTORY + +cd docs || exit 1 +DIRECTORIES=*/ +for directory in $DIRECTORIES +do + cd $directory || exit 1 + FILES=*.txt + for file in $FILES + do + echo Converting $directory"$file" to HTML + asciidoc -a toc $file + echo Converting $directory"$file" to PDF + a2x --format=pdf --no-xmllint $file + done + cp *.html $INSTALLATION_DIRECTORY || exit 1 + cp *.pdf $INSTALLATION_DIRECTORY || exit 1 + cd .. || exit 1 +done +cd .. Property changes on: trunk/docs/build_docs.sh ___________________________________________________________________ Added: svn:executable + * Deleted: trunk/docs/buildguides.sh =================================================================== --- trunk/docs/buildguides.sh 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/buildguides.sh 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,5 +0,0 @@ -#!/bin/sh - -make all chunked-userguide -./build-chunked-userguide.sh - Added: trunk/docs/cookbook/cookbook-asciidoc.html =================================================================== --- trunk/docs/cookbook/cookbook-asciidoc.html (rev 0) +++ trunk/docs/cookbook/cookbook-asciidoc.html 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,1497 @@ + + + + + +Swift Cookbook + + + + + +
    +
    +

    Overview

    +
    +

    This cookbook covers various recipes involving setting up and running Swift under diverse +configurations based on the application requirements and the underlying +infrastructures. The Swift system comprises of SwiftScript language and the +Swift runtime system. For +introductory material, consult the Swift tutorial found +here.

    +
    +
    +
    +

    Swift Basics

    +
    +
    +

    Installation

    +

    This section takes you through the installation of the Swift system on your +computer. We will start with the prerequisites as explained in the subsequent +section.

    +
    +

    Prerequisites

    +
    Check your Java

    Swift is a Java application. Make sure you are running Java version 5 or higher. You +can make sure you have Java in your $PATH (or $HOME/.soft file depending upon +your environment)

    +

    Following are the possible ways to detect and run Java:

    +
    +
    +
    $ grep java $HOME/.soft
    +#+java-sun # Gives you Java 5
    ++java-1.6.0_03-sun-r1
    +$ which java
    +/soft/java-1.6.0_11-sun-r1/bin/java
    +$ java -version
    +java version "1.6.0_11"
    +Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
    +Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
    +
    +
    +
    +
    +

    Setting up to run Swift

    +

    This is simple. We will be using a pre-compiled version of Swift that can be +downloaded from here. Download and untar the latest precompiled version as follows:

    +
    +
    +
    $ tar xf swift-0.92.1.tar.gz
    +
    +
    +

    Environment Setup

    +

    The examples were tested with Java version 1.6. Make sure you do not already +have Swift in your PATH. If you do, remove it, or remove any +swift or @swift +lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:

    +
    +
    +
    PATH=$PATH:/path/to/swift/bin
    +
    +

    Note that the environment will be different when using Swift from prebuilt distribution (as above) and trunk. The PATH setup when using swift from trunk would be as follows:

    +
    +
    +
    PATH=$PATH:/path/to/swift/dist/swift-svn/bin
    +
    +
    + + + +
    +
    Warning
    +
    Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you +fully understand how these will affect Swift’s execution.
    +
    +

    To execute your Swift script on a login host (or "localhost") use +the following command:

    +
    +
    +
    swift -tc.file tc somescript.swift
    +
    +
    +
    +

    Setting transformation catalog

    +

    The transformation catalog lists where application executables are located on +remote sites.

    +

    By default, the site catalog is stored in etc/tc.data. This path can be +overridden with the tc.file configuration property, either in the Swift +configuration file or on the command line.

    +

    The format is one line per executable per site, with fields separated by tabs +or spaces.

    +

    Some example entries:

    +
    +
    +
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    +TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX GLOBUS::maxwalltime="00:00:10"
    +
    +

    The fields are: site, transformation-name, executable-path, installation-status, platform, and profile entries.

    +

    The site field should correspond to a site name listed in the sites catalog.

    +

    The transformation-name should correspond to the transformation name used in a +SwiftScript app procedure.

    +

    The executable-path should specify where the particular executable is located +on that site.

    +

    The installation-status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively.

    +

    The profiles field should be set to null if no profile entries are to be +specified, or should contain the profile entries separated by semicolons.

    +
    +
    +

    Setting swift configuration

    +

    Many configuration properties could be set using the Swift configuration file. +We will not cover them all in this section. see +here for details. In this section we will cover a simple configuration file with the most basic properties.

    +
    +
    +
    # A comment
    +wrapperlog.always.transfer=true
    +sitedir.keep=true
    +execution.retries=1
    +lazy.errors=true
    +status.mode=provider
    +use.provider.staging=true
    +provider.staging.pin.swiftfiles=false
    +clustering.enabled=false
    +clustering.queue.delay=10
    +clustering.min.time=86400
    +foreach.max.threads=100
    +provenance.log=true
    +
    +
    +
    +

    Setting sites.xml

    +

    sites.xml specifies details of the sites that Swift can run on. Following is +an example of a simple sites.xml file entry for running Swift on local +environment:

    +
    +
    +
    <pool handle="localhost">
    +<filesystem provider="local" />
    +<execution provider="local" />
    +<workdirectory >/var/tmp</workdirectory>
    +<profile namespace="karajan" key="jobThrottle">.07</profile>
    +<profile namespace="karajan"
    +key="initialScore">100000</profile>
    +</pool>
    +
    +
    +
    +

    First SwiftScript

    +

    Your first SwiftScript +Hello Swift-World!

    +

    A good sanity check that Swift is set up and running OK locally is this:

    +
    +
    +
    $ which swift
    +
    +/home/wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift
    +
    +$ echo 'trace("Hello, Swift world!");' >hello.swift
    +
    +$ swift hello.swift
    +
    +Swift svn swift-r3202 cog-r2682
    +
    +RunID: 20100115-1240-6xhzxuz3
    +
    +Progress:
    +
    +SwiftScript trace: Hello, Swift world!
    +
    +Final status:
    +
    +$
    +
    +

    A good first tutorial in using Swift is at: +http://www.ci.uchicago.edu/swift/guides/tutorial.php. Follow the steps in that +tutorial to learn how to run a few simple scripts on the login host.

    +
    +
    +

    second SwiftScript

    +

    Following is a more involved Swift script.

    +
    +
    +
    type file;
    +
    +app (file o) cat (file i)
    +{
    +    cat @i stdout=@o;
    +}
    +
    +file out[]<simple_mapper; location="outdir", prefix="f.",suffix=".out">;
    +
    +foreach j in [1:@toint(@arg("n","1"))] {
    +
    +    file data<"data.txt">;
    +
    +    out[j] = cat(data);
    +}
    +
    +
    +

    Swift Commandline Options

    +

    A description of Swift Commandline Options

    +

    Also includes a description of Swift inputs and outputs.

    +
    +
    +

    What if Swift hangs

    +

    Owing to its highly multithreaded architecture it is often the case that the +underlying java virtual machine gets into deadlock situations or Swift hangs +because of other complications in its threaded operations. Under such +situations, Swift hang-checker chips in and resolves the situation.

    +
      +
    1. +

      +how to use the information to identify and correct the deadlock. +

      +
    2. +
    3. +

      +How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines? +

      +
    4. +
    5. +

      +The current Hang Checker output is actually very nice and useful already: +

      +
    6. +
    +
    +
    +
    Registered futures:
    +Rupture[] rups  Closed, 1 elements, 0 listeners
    +Variation vars - Closed, no listeners
    +SgtDim sub - Open, 1 listeners
    +string site  Closed, no listeners
    +Variation[] vars  Closed, 72 elements, 0 listeners
    +
    +
    +
    +

    Resuming a stopped or crashed Swift Run

    +

    I had a .rlog file from a Swift run that ran out of time. I kicked it off +using the -resume flag described in section 16.2 of the Swift User Guide and +it picked up where it left off. Then I killed it because I wanted to make +changes to my sites file.

    +
    +
    +
    . . .
    +Progress:  Selecting site:1150  Stage in:55  Active:3  Checking status:1
    +Stage out:37  Finished in previous run:2462  Finished successfully:96
    +Progress:  Selecting site:1150  Stage in:55  Active:2  Checking status:1
    +Stage out:38  Finished in previous run:2462  Finished successfully:96
    +Cleaning up...
    +Shutting down service at https://192.5.86.6:54813
    +Got channel MetaChannel: 1293358091 -> null
    ++ Done
    +Canceling job 9297.svc.pads.ci.uchicago.edu
    +
    +

    No new rlog file was emitted but it did recognize the progress that had been +made, the 96 tasks that finished sucessfully above and resumed from 2558 tasks +finished.

    +
    +
    +
    [nbest at login2 files]$ pwd
    +/home/nbest/bigdata/files
    +[nbest at login2 files]$
    +~wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift \
    +> -tc.file tc -sites.file pbs.xml ~/scripts/mcd12q1.swift -resume
    +> mcd12q1-20100310-1326-ptxe1x1d.0.rlog
    +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    +locally)
    +RunID: 20100311-1027-148caf0a
    +Progress:
    +Progress:  uninitialized:4
    +Progress:  Selecting site:671  Initializing site shared directory:1  Finished
    +in previous run:1864
    +Progress:  uninitialized:1  Selecting site:576  Stage in:96  Finished in
    +previous run:1864
    +Progress:  Selecting site:1150  Stage in:94  Submitting:2  Finished in
    +previous run:2558
    +Progress:  Selecting site:1150  Stage in:94  Submitted:2  Finished in previous
    +run:2558
    +Progress:  Selecting site:1150  Stage in:93  Submitting:1  Submitted:2
    +Finished in previous run:2558
    +Progress:  Selecting site:1150  Stage in:90  Submitting:1  Submitted:5
    +Finished in previous run:2558
    +Progress:  Selecting site:1150  Stage in:90  Submitted:5  Active:1  Finished
    +in previous run:2558
    +
    +

    From Neil: A comment about that section of the user guide: It says "In order +to restart from a restart log file, the -resume logfile argument can be used +after the SwiftScript? program file name." and then puts the -resume logfile +argument before the script file name. I’m sure the order doesn’t matter but +the contradiction is confusing.

    +

    Notes to add (from Mike):

    +
      +
    • +

      +explain what aspects of a Swift script make it restartable, and which + aspects are notrestartable. Eg, if your mappers can return different data at +different times, what happens? What other non-determinsitc behavior would +cause unpredictable, unexpected, or undesired behavior on resumption? +

      +
    • +
    • +

      +explain what changes you can make in the execution environment (eg + increasing or reducing CPUs to run on or throttles, etc); fixing tc.data +entries, env vars, or apps, etc. +

      +
    • +
    • +

      +note that resume will again retry failed app() calls. Explain if the retry + count starts over or not. +

      +
    • +
    • +

      +explain how to resume after multiple failures and resumes - i.e. if a .rlog + is generated on each run, which one should you resume from? Do you have a +choice of resuming from any of them, and what happens if you go backwards to +an older resume file? +

      +
    • +
    • +

      +whap happens when you kill (eg with C) a running swift script? Is the + signal caught, and the resume file written out at that point? Or written out +all along? (Note case in which script ws running for hours, then hit C, but +resume fie was short (54 bbytes) and swift shows no sign of doing a resume? +(It silently ignored resume file instead of acknowleging that it found one +with not useful resume state in it???) Swift should clearly state that its +resuming and what its resume state is. +

      +
    • +
    +

    swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial +run\]

    +
    +
    +

    Passing an array to swift?

    +

    Arrays can be passed to Swift in one of the following ways:

    +
      +
    1. +

      +You can write the array to a file and read in in swift using +readData (or readData2). +

      +
    2. +
    3. +

      +Direct the array into a file (possibly with a "here document" which expands the array) and then read the file in Swift with readData() or process it with a Swift app() function? +

      +
    4. +
    5. +

      +You can use @strsplit on a comma separated command line arg and that works well for me. +

      +
    6. +
    +
    +

    Mappers

    +

    SimpleMapper

    +
    +
    +
    $ cat swiftapply.swift
    +
    +
    +
    +
    type RFile;
    +trace("hi 1");
    +app (RFile result) RunR (RFile rcall)
    +{
    +  RunR @rcall @result;
    +}
    +trace("hi 2");
    +RFile rcalls[] ;
    +RFile results[] ;
    +trace("start");
    +foreach c, i in rcalls {
    +  trace("c",i,@c);
    +  trace("r",i,@filename(results[i]));
    +  results[i] = RunR(c);
    +}
    +
    +
    +
    $ ls calldir resdir
    +calldir:
    +rcall.1.Rdata  rcall.2.Rdata  rcall.3.Rdata  rcall.4.Rdata
    +resdir:
    +result.1.Rdata result.2.Rdata result.3.Rdata result.4.Rdata
    +$
    +
    +

    Notes:

    +

    how the .'s match +prefix and suffix dont span dirs +intervening pattern must be digits +these digits become the array indices +explain how padding= arg works & helps (including padding=0) +figure out and explain differences between simple_mapper and +filesys_mapper +FIXME: Use the "filesys_mapper" and its "location=" parameter to map the +input data from /home/wilde/bigdata/*

    +

    Abbreviations for SingleFileMapper +Notes:

    +

    within <> you can only have a literal string as in <"filename">, not an +expression. Someday we will fix this to make <> accept a general expression. +you can use @filenames( ) (note: plural) to pull off a list of filenames.

    +

    writeData()

    +

    example here

    +
    +
    +
    $ cat writedata.swift
    +
    +
    +
    +
    type file;
    +
    +file f <"filea">;
    +file nf <"filenames">;
    +nf = writeData(@f);
    +
    +
    +
    $ swift writedata.swift
    +Swift svn swift-r3264 (swift modified locally) cog-r2730 (cog modified
    +locally)
    +RunID: 20100319-2002-s9vpo0pe
    +Progress:
    +Final status:
    +$ cat filenames
    +filea$
    +
    +

    StructuredRegexpMapper +IN PROGRESS This mapper can be used to base the mapped filenames of an output +array on the mapped filenames of an existing array. landuse outputfiles[] +<structured_regexp_mapper; source=inputfiles, +location="./output",match="(.)*tif", transform="\\1histogram">;

    +

    Use the undocumented "structured_regexp_mapper" to name the output +filenames based on the input filenames:

    +

    For example:

    +
    +
    +
    login2$ ls /home/wilde/bigdata/data/sample
    +h11v04.histogram  h11v05.histogram  h12v04.histogram  h32v08.histogram
    +h11v04.tif        h11v05.tif        h12v04.tif        h32v08.tif
    +login2$
    +
    +login2$ cat regexp2.swift
    +type tif;
    +type mytype;
    +
    +tif  images[]<filesys_mapper;
    +location="/home/wilde/bigdata/data/sample", prefix="h", suffix=".tif">;
    +
    +mytype of[] <structured_regexp_mapper; source=images, match="(h..v..)",
    +transform="output/myfile.\\1.mytype">;
    +
    +foreach image, i in images {
    +   trace(i, at filename(images));
    +   trace(i, at filename(of[i]));
    +}
    +login2$
    +
    +login1$ swift regexp2.swift
    +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    +locally)
    +
    +RunID: 20100310-1105-4okarq08
    +Progress:
    +SwiftScript trace: 1, output/myfile.h11v04.mytype
    +SwiftScript trace: 2, home/wilde/bigdata/data/sample/h11v05.tif
    +SwiftScript trace: 3, home/wilde/bigdata/data/sample/h12v04.tif
    +SwiftScript trace: 0, output/myfile.h32v08.mytype
    +SwiftScript trace: 0, home/wilde/bigdata/data/sample/h32v08.tif
    +SwiftScript trace: 3, output/myfile.h12v04.mytype
    +SwiftScript trace: 1, home/wilde/bigdata/data/sample/h11v04.tif
    +SwiftScript trace: 2, output/myfile.h11v05.mytype
    +Final status:
    +login1$
    +
    +
    +
    +
    +
    +
    +

    Coasters

    +
    +

    Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters.

    +

    Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were:

    +
    +
    +
    <execution provider="coaster" jobmanager="local:pbs"/>
    +<profile namespace="globus" key="project">CI-CCR000013</profile>
    +
    +<!-- Note that the following is going to be defunct in the new version (0.93+) and replaced by
    +"ProviderAttributes" key and may not work in the future Swift versions-->
    +
    +<!--<profile namespace="globus" key="ppn">24:cray:pack</profile>-->
    +
    +<profile namespace="globus" key="providerAttributes">
    +pbs.aprun
    +pbs.mpp=true
    +</profile>
    +
    +<profile namespace="globus" key="workersPerNode">24</profile>
    +<profile namespace="globus" key="maxTime">100000</profile>
    +
    +<profile namespace="globus" key="lowOverallocation">100</profile>
    +<profile namespace="globus" key="highOverallocation">100</profile>
    +
    +<profile namespace="globus" key="slots">20</profile>
    +<profile namespace="globus" key="nodeGranularity">5</profile>
    +<profile namespace="globus" key="maxNodes">5</profile>
    +<profile namespace="karajan" key="jobThrottle">20.00</profile>
    +<profile namespace="karajan" key="initialScore">10000</profile>
    +

    The following table briefly describes the elements on the coasters setup:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    profile key brief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are infinitely long

    workersPerNode

    How many coaster workers to run per execution node reserve How many seconds to reserve in a block’s walltime for starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block coaster service

    jobThrottle

    the number of concurrent jobs allowed on a site

    +
    +
    +

    For Advanced Users

    +

    One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters.

    +
    +
    +

    Coaster providers: local, ssh, pbs

    +

    Settings and examples for different coaster providers mechanisms.

    +
    +
    +
    +
    +

    Swift on Diverse Infrastructures

    +
    +
    +

    Beagle

    +

    Swift is now installed on Beagle as a module. Swift supports a Coasters based, +computing environment for Beagle. A detailed Swift documentation is maintained +[[here]. To get started +with Swift on Beagle follow the steps outlined below:

    +

    step 1. Load the Swift module on Beagle as follows: module load swift

    +

    step 2. Create and change to a directory where your Swift related work will +stay. (say, mkdir swift-lab, followed by, cd swift-lab)

    +

    step 3. To get started with a simple example running /bin/cat to read an input file data.txt and write to an output file f.nnn.out, copy the folder at /home/ketan/labs/catsn to the above directory. (cp -r /home/ketan/catsn . followed by cd catsn).

    +

    step 4. In the sites file: beagle-coaster.xml, make the following two +changes: 1) change the path of workdirectory to your preferred location +(say to /lustre/beagle/$USER/swift-lab/swift.workdir) and 2) Change the +project name to your project (CI-CCR000013) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs.

    +

    step 5. Run the example using following commandline (also found in run.sh): +swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1 +. You can further change the value of -n to any arbitrary number to run that +many number of concurrent cat

    +

    step 6. Check the output in the generated outdir directory (ls outdir)

    +

    Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes +will get fast prioritized execution. Good for small tests

    +
    +
    +

    PADS

    +

    Swift on PADS +To execute your Swift script on the PADS cluster use this command:

    +
    +
    +
    swift -tc.file tc -sites.file pbs.xml modis.swift
    +
    +

    where the contents of a simple pbs.xml sites file could be:

    +
    +
    +
    <config>
    +  <pool handle="pbs">
    +    <execution provider="pbs" url="none"/>
    +    <profile namespace="globus" key="queue">fast</profile>
    +    <profile namespace="globus" key="maxwalltime">00:05:00</profile>
    +    <profile namespace="karajan" key="initialScore">10000</profile>
    +    <profile namespace="karajan" key="jobThrottle">.10</profile>
    +    <filesystem provider="local"/>
    +    <workdirectory >/home/you/swiftwork</workdirectory>
    +  </pool>
    +</config>
    +
    +
    +

    OSG

    +

    This section describes how to get Swift running on the OSG Grid. We will use a +manual coaster setup to get Swift running on OSG.

    +
    Coaster setup on OSG

    The following figure shows an abstract scheme for the manual coasters setup on +OSG.

    +
    +
    +Coaster setup +
    +
    +

    In the following steps, we will go through the process of manually setting

    +
    +
    +

    Bionimbus

    +

    This section explains a step by step procedure on getting Swift running on the +Bionimbus cloud. We will use the manual coasters configuration on the +Bionimbus cloud.

    +

    step1. Connect to the gateway (ssh gatewayx.lac.uic.edu)

    +

    step2. Start a virtual machine (euca-run-instances -n 1 -t m1.small +emi-17EB1170)

    +

    step3. Start the coaster-service on gateway +coaster-service -port 1984 -localport 35753 -nosec

    +

    step4. Start the Swift-script from the gateway using normal Swift commandline

    +

    swift -config cf -tc.file tc -sites.file sites.xml yourscript.swift -aparam=999

    +
    +
    cf
    +
    +
    wrapperlog.always.transfer=true
    +sitedir.keep=true
    +execution.retries=1
    +lazy.errors=true
    +status.mode=provider
    +use.provider.staging=true
    +provider.staging.pin.swiftfiles=false
    +foreach.max.threads=100
    +provenance.log=true
    +
    +
    +
    tc
    +
    +
    localhost modftdock /home/ketan/swift-labs/bionimbus-coaster-modftdock/app/modftdock.sh null null GLOBUS::maxwalltime="1:00:00"
    +
    +

    (See below for a sample sites.xml for this run)

    +

    step5. Connect back to gateway from virtual machines using reverse ssh tunneling as follows:

    +
    From the gateway prompt

    ssh -R *:5000:localhost:5000 root at 10.101.8.50 sleep 999

    +

    WHERE: +*=network interface, should remain the same on all cases

    +

    localhost=the gateway host, should remain the same

    +

    5000(LEFT OF localhost)=the port number on localhost to listen to **THIS WILL +vary depending upon which port you want to listen to

    +

    5000(RIGHT OF localhost)=the port on target host that you want to forward

    +

    root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will +vary based on what ip you get for your Virtual Machine instance

    +

    #On anywhere as long as provide the correct callback uri: here the +"http://140.221.9.110:42195" is the callback uri of previous ones

    +

    step6. Start the worker from the virtual machine +worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the +coaster service is listening to the workers

    +
    +
    sites.xml for the above run
    +
    +
    <config>
    +  <pool handle="localhost">
    +    <execution provider="coaster-persistent" url="http://localhost:1984" jobmanager="local:local"/>
    +    <profile namespace="globus" key="workerManager">passive</profile>
    +
    +    <profile namespace="globus" key="workersPerNode">4</profile>
    +    <profile namespace="globus" key="maxTime">10000</profile>
    +    <profile namespace="globus" key="lowOverAllocation">100</profile>
    +    <profile namespace="globus" key="highOverAllocation">100</profile>
    +    <profile namespace="globus" key="slots">100</profile>
    +    <profile namespace="globus" key="nodeGranularity">1</profile>
    +    <profile namespace="globus" key="maxNodes">10</profile>
    +    <profile namespace="karajan" key="jobThrottle">25.00</profile>
    +    <profile namespace="karajan" key="initialScore">10000</profile>
    +    <profile namespace="swift" key="stagingMethod">proxy</profile>
    +    <filesystem provider="local"/>
    +    <workdirectory>/home/ketan/swift-labs/bionimbus-coaster-modftdock/swift.workdir</workdirectory>
    +  </pool>
    +</config>
    +
    +
    +
    +
    +

    Debugging Swift

    +
    +

    Swift errors are logged in several places:

    +
      +
    1. +

      +All text from standard output and standard error produced by running the +swift command +

      +
    2. +
    3. +

      +The .log file from this run. It will be named swiftscript.uniqueID.log +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +

      +
    4. +
    5. +

      +$HOME/.globus/coasters directory on remote machines on which you are +running coasters +

      +
    6. +
    7. +

      +$HOME/.globus/scripts directory on the host on which you run the Swift +command, when swift is submitting to a local scheduler (Condor, PBS, SGE, +Cobalt) +

      +
    8. +
    9. +

      +$HOME/.globus/??? on remote systems that you access via Globus +

      +
    10. +
    +
    +
    +
    +

    Log Processing

    +
    +

    To properly generate log plots, you must enable VDL/Karajan logging. Make sure +log4.properties contains:

    +
    +
    +
    log4j.logger.swift=DEBUG
    +log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG
    +
    +
    +

    Make a basic load plot from Coasters Cpu log lines

    +
    Generate the log (may set log4j.logger.swift=INFO for this one)

    (assuming the log is titled swift-run.log)

    +
    +
    Convert the log times to Unix time
    +
    +
    ./iso-to-secs < swift-run.log > swift-run.time
    +
    +
    +
    Make the start time file (this contains the earliest timestamp)
    +
    +
    make LOG=swift-run.log start-time.tmp
    +
    +

    or

    +
    +
    +
    extract-start-time swift-run.log > start-time.tmp
    +
    +
    +
    Normalize the transition times
    +
    +
    ./normalise-event-start-time < swift-run.time > swift-run.norm
    +
    +
    +
    Build up a load data file:
    +
    +
    ./cpu-job-load.pl < swift-run.norm > load.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh load.cfg load.eps load.data
    +
    +
    +

    Make a basic job completion plot from Coasters Cpu log lines

    +
    +
    Same as above, but, build up a completed data file:
    +
    +
    ./cpu-job-completed.pl < swift-run.norm > completed.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh completed.cfg completed.eps completed.data
    +
    +
    +
    +

    Make a basic Block allocation plot from Coasters Block log lines

    +

    Same as above, but:

    +
    +
    Build up a block allocation data file:
    +
    +
    ./block-level.pl < swift-run.norm > blocks.data
    +
    +
    +
    Plot with the JFreeChart-based plotter in usertools/plotter:
    +
    +
    lines.zsh blocks.{cfg,eps,data}
    +
    +
    +
    +
    +

    Problem Reporting

    +

    When reporting problems to swift-user at ci.uchicago.edu, please attach the +following files and information:

    +
      +
    1. +

      +tc.data and sites.xml (or whatever you named these files) +

      +
    2. +
    3. +

      +your .swift source file and any .swift files it imports +

      +
    4. +
    5. +

      +any external mapper scripts called by your .swift script +

      +
    6. +
    7. +

      +all text from standard output and standard error produced by running the +swift command +

      +
    8. +
    9. +

      +The .log file from this run. It will be named swiftscript.uniqueID.log +

      +
    10. +
    11. +

      +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +

      +
    12. +
    13. +

      +The swift command line you invoked +

      +
    14. +
    15. +

      +Any swift.properties entries you over-rode ($HOME/.swift/swift.properties, +-config.file argument properties file, any changes to etc/swift.proerties from +your swift distribution) +

      +
    16. +
    17. +

      +Which swift distribution you are running (release; svn revisions; other +local changes you mave have made or included) +

      +
    18. +
    +
    +
    +
    +
    +

    + + + Added: trunk/docs/cookbook/cookbook-asciidoc.pdf =================================================================== --- trunk/docs/cookbook/cookbook-asciidoc.pdf (rev 0) +++ trunk/docs/cookbook/cookbook-asciidoc.pdf 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,4267 @@ +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (section.1) >> +endobj +8 0 obj +(Overview) +endobj +9 0 obj +<< /S /GoTo /D (section.2) >> +endobj +12 0 obj +(Swift Basics) +endobj +13 0 obj +<< /S /GoTo /D (subsection.2.1) >> +endobj +16 0 obj +(Installation) +endobj +17 0 obj +<< /S /GoTo /D (subsubsection.2.1.1) >> +endobj +20 0 obj +(Prerequisites) +endobj +21 0 obj +<< /S /GoTo /D (subsection.2.2) >> +endobj +24 0 obj +(Setting up to run Swift) +endobj +25 0 obj +<< /S /GoTo /D (subsubsection.2.2.1) >> +endobj +28 0 obj +(Environment Setup) +endobj +29 0 obj +<< /S /GoTo /D (subsubsection.2.2.2) >> +endobj +32 0 obj +(Setting transformation catalog) +endobj +33 0 obj +<< /S /GoTo /D (subsubsection.2.2.3) >> +endobj +36 0 obj +(Setting swift configuration) +endobj +37 0 obj +<< /S /GoTo /D (subsubsection.2.2.4) >> +endobj +40 0 obj +(Setting sites.xml) +endobj +41 0 obj +<< /S /GoTo /D (subsection.2.3) >> +endobj +44 0 obj +(First SwiftScript) +endobj +45 0 obj +<< /S /GoTo /D (subsection.2.4) >> +endobj +48 0 obj +(second SwiftScript) +endobj +49 0 obj +<< /S /GoTo /D (subsection.2.5) >> +endobj +52 0 obj +(Swift Commandline Options) +endobj +53 0 obj +<< /S /GoTo /D (subsection.2.6) >> +endobj +56 0 obj +(What if Swift hangs) +endobj +57 0 obj +<< /S /GoTo /D (subsection.2.7) >> +endobj +60 0 obj +(Resuming a stopped or crashed Swift Run) +endobj +61 0 obj +<< /S /GoTo /D (subsection.2.8) >> +endobj +64 0 obj +(Passing an array to swift?) +endobj +65 0 obj +<< /S /GoTo /D (subsubsection.2.8.1) >> +endobj +68 0 obj +(Mappers) +endobj +69 0 obj +<< /S /GoTo /D (section.3) >> +endobj +72 0 obj +(Coasters) +endobj +73 0 obj +<< /S /GoTo /D (subsection.3.1) >> +endobj +76 0 obj +(For Advanced Users) +endobj +77 0 obj +<< /S /GoTo /D (subsection.3.2) >> +endobj +80 0 obj +(Coaster providers: local, ssh, pbs) +endobj +81 0 obj +<< /S /GoTo /D (section.4) >> +endobj +84 0 obj +(Swift on Diverse Infrastructures) +endobj +85 0 obj +<< /S /GoTo /D (subsection.4.1) >> +endobj +88 0 obj +(Beagle) +endobj +89 0 obj +<< /S /GoTo /D (subsection.4.2) >> +endobj +92 0 obj +(PADS) +endobj +93 0 obj +<< /S /GoTo /D (subsection.4.3) >> +endobj +96 0 obj +(OSG) +endobj +97 0 obj +<< /S /GoTo /D (subsection.4.4) >> +endobj +100 0 obj +(Bionimbus) +endobj +101 0 obj +<< /S /GoTo /D (section.5) >> +endobj +104 0 obj +(Debugging Swift) +endobj +105 0 obj +<< /S /GoTo /D (section.6) >> +endobj +108 0 obj +(Log Processing) +endobj +109 0 obj +<< /S /GoTo /D (subsection.6.1) >> +endobj +112 0 obj +(Make a basic load plot from Coasters Cpu log lines) +endobj +113 0 obj +<< /S /GoTo /D (subsubsection.6.1.1) >> +endobj +116 0 obj +(Make a basic job completion plot from Coasters Cpu log lines) +endobj +117 0 obj +<< /S /GoTo /D (subsubsection.6.1.2) >> +endobj +120 0 obj +(Make a basic Block allocation plot from Coasters Block log lines) +endobj +121 0 obj +<< /S /GoTo /D (subsection.6.2) >> +endobj +124 0 obj +(Problem Reporting) +endobj +125 0 obj +<< /S /GoTo /D [126 0 R /FitH ] >> +endobj +128 0 obj << +/Length 277 +/Filter /FlateDecode +>> +stream +x??Q?JCA ??W??^Lv?????????J/ZZ??"?}????X?>??endstream +endobj +126 0 obj << +/Type /Page +/Contents 128 0 R +/Resources 127 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +>> endobj +129 0 obj << +/D [126 0 R /XYZ 56.6929 815.7613 null] +>> endobj +136 0 obj << +/D [126 0 R /XYZ 56.6929 759.0684 null] +>> endobj +127 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +143 0 obj << +/Length 2501 +/Filter /FlateDecode +>> +stream +x??\]s?6}????5????c_v??????dcw????,??6??Rr??? ? +???8?v??I?XG??? ?^?"?H!$???B??$?X?/p?h????8??]????????0?H*???BR$?? +1CUq{???????~vE?|QU???????????B??J?|??????"!h?????^|{?x&??? +??.~????q?I???#? +)??????7????F??R?8?b?Y?d?? BD3???K$??4^T?}???F'c??q??w?Gy;??qPQ?Q +dvE0??????,??????1%b??4SG???PY*6?\?c.#~?? a?{?b????M?"U^?w?EB)???#R????,????? ???l??3?q??_??4-?Q[G?Vv??ov??j5?/?M?fl?)9bt???!\#???3A?+a#2?|? 7?} ?@?O(???s:?H??E4??]k?nd??a??$??H?F??!E???P?R?M +j=??.?????n?/??A)??El#? +??P!Z"???L?~???<?H?`??2???r#5?z????j'J??>?Q????n??~?y?6??m??????i???m?? ?b??"&?&?Gex??9R?yN?~?|M(xQ"??KG?$d????7?A??k??4k???oN?u?Y?c??}??9q4 ??-),??`2?????X#I??3??? /?R??I?W:ZF???c???.?%D(?@^??I??????f?P???h?????zL???J?"6? +??2,?`??E?yN>Y?`r??????cr???r {H1?????rfCr?J?E???????r)?Ha"??z?f????L#???I??j?I?m0&?hmCF?^?G?Kk???????????^%'qC??$g?$?QN???k?g5??3? +[?v0l?h?CF??Q}j1*?D?p?????b????????fQ/?i?)q?$?"?????2???5?6??i???R?&?(!????5?e? =?;cO??h???T??%??????|F(?????? +?&*??(?c?Oj??gJ???b??t?L@F??psV?LxT??w(?K???|s?Zn??????~?vh "????gZL?%?? }r??????):?t???!?g/?\?? ?V|@uB?N????;?/??{?????q???-(?Elw`?w? ?????M????>?C:??LG??4z???%o?????r????=?C?;w%???nKw"?j?????w?}?3o??????5?????{?Gef@?F????$yH???#u?~OGk???? +=??q?3'?????????????v?????????_?m{?O?>)%E?h?8T?nh???NR????-?0l?hM??x&@F?m?s?? +n????p????]???lcgF +fE?)???C'.*P??E ~:ZfQ???????1Bgr??????b??7/o?G? ?F?"}??7???8dI?b???j????H)??T&??h??xi??y???????% +??C??HG?$ +h????J??,?(?%??#?zYm?????OiS?i??bElb??Y??0!? ?x??$???1??E;J0??h????[?Q????+???z?]??????1\?~n?S? eEl+???Q +~?9???h??a???? 1p?G5??s??*??7m?Z-??z_?j?~ zD-Y5*?(?#?D?X?J A??W???zT??P??8?V??k?w?W1t????k?nW?????2??????*?Bz?j?XF9?2?????\a??b"???O?`Hh)????#zk?wj?endstream +endobj +142 0 obj << +/Type /Page +/Contents 143 0 R +/Resources 141 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 145 0 R 149 0 R 150 0 R 151 0 R 152 0 R 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R 163 0 R 164 0 R 165 0 R 166 0 R 167 0 R 168 0 R 169 0 R 170 0 R 171 0 R 172 0 R 173 0 R 174 0 R 175 0 R 176 0 R 177 0 R ] +>> endobj +145 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 706.3558 113.3799 715.332] +/Subtype /Link +/A << /S /GoTo /D (section.1) >> +>> endobj +149 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 678.4604 123.8304 687.4366] +/Subtype /Link +/A << /S /GoTo /D (section.2) >> +>> endobj +150 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 660.5476 140.3783 669.3942] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.1) >> +>> endobj +151 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 640.5575 178.8938 651.4615] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.1.1) >> +>> endobj +152 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 622.6248 186.3259 633.5287] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.2) >> +>> endobj +153 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 604.692 204.239 615.596] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.1) >> +>> endobj +154 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 586.7593 248.0736 597.6632] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.2) >> +>> endobj +155 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 568.8265 233.6979 579.7305] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.3) >> +>> endobj +156 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 550.8938 193.8574 561.7977] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.4) >> +>> endobj +157 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 532.961 161.698 543.865] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.3) >> +>> endobj +158 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 515.0283 171.093 525.9322] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.4) >> +>> endobj +159 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 497.0955 210.1262 507.9995] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.5) >> +>> endobj +160 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 479.1628 175.5165 490.0667] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.6) >> +>> endobj +161 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 461.23 263.2368 472.134] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.7) >> +>> endobj +162 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 443.2973 197.7727 454.2012] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.8) >> +>> endobj +163 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 425.3645 162.2866 436.2685] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.8.1) >> +>> endobj +164 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 399.5065 109.7037 408.4827] +/Subtype /Link +/A << /S /GoTo /D (section.3) >> +>> endobj +165 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 381.4741 177.0411 390.4403] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.1) >> +>> endobj +166 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 361.6036 227.7101 372.5076] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.2) >> +>> endobj +167 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 335.7456 209.7673 344.7218] +/Subtype /Link +/A << /S /GoTo /D (section.4) >> +>> endobj +168 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 315.7755 123.2131 326.6794] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1) >> +>> endobj +169 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 299.9 120.0951 308.7467] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.2) >> +>> endobj +170 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 281.9673 115.4724 290.8139] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.3) >> +>> endobj +171 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 264.0345 139.0835 272.8812] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.4) >> +>> endobj +172 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 234.2163 143.0086 245.0954] +/Subtype /Link +/A << /S /GoTo /D (section.5) >> +>> endobj +173 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 206.3209 136.9314 217.2] +/Subtype /Link +/A << /S /GoTo /D (section.6) >> +>> endobj +174 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 188.2537 299.9385 199.1576] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.1) >> +>> endobj +175 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 170.3209 374.7175 181.2249] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.6.1.1) >> +>> endobj +176 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 152.3882 387.4395 163.2921] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.6.1.2) >> +>> endobj +177 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 134.4554 171.6511 145.3594] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.2) >> +>> endobj +144 0 obj << +/D [142 0 R /XYZ 56.6929 815.7613 null] +>> endobj +141 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +181 0 obj << +/Length 4471 +/Filter /FlateDecode +>> +stream +x??]?o??????]?3H?KR%(?????????H?@??????D??????x?%R?v? 0???xz?{<??& ??E??i??H?RF???? ^\???N??Yk??-?????/??Q?([?].E,??"?)?r?.?6?.O????jM????????????O?"?OY???? ????' ??,??????w'_???YiNP???[??????? +????8???n0?qN7' ???Q?d{rz?]?Q??1?q????Z??$???????$I?ftA(? I??? -&=??2?fY??H-?t?q?on?f?&xy[?+?,?T.??????4C?0??g?U Y???Bg0?a??zn??e?$nW4YMU?????????v?s??????J*j??A???q/??F?m???y?K?m?G?rSqXmI?????1?:6???w????-7???I??u? ??muQ?y?@???JD"p s?~9VMyS?\'8$M?WR<?m???1w??)?Cs?8??E?u?SHX%?????=?7??E}?o?V???/-??????o????X\??NY????D?Eb???????????K??u#?u?;4?l??{???8?MUl??????q????M?G????e +?3??(?PQX?$?uS?~??W????bm??-W3w??lJ??(G??@??A54R!\G?ESQ?%)?Q?6??'?1I????D????n ?Z??E;?5e?<xmI0J?????b?k?D????O??Z(?(???v???nE? +????????V??"??B~s(???*??]??????uS???M)/*Y|??EODe?Ra?_kyh?x?P?WI??![????)xWm?J??h?????7)Y??R??:???? =?Az???Ngs??=??? ????I5Y????@u??tw??????H?J?C +?^_ ?????@??_?????>?./??6????"c)???q?e?R?Pvh/rQG Ay5??_q??!J?l?K?e??\\Z?]???=B?&???????j?*#?????O??C???,UQkW??{.?w?????2????`??`?dc +???B^|????I???c3c;F)^?? +Kt]q +=H[???Ei??b)?????b=???r?4?MJ?c?<??$d???????? e)a?a?Q????3r? ???1/?Ip?5om?B??6??!$?o&???Z>?/?%F4C 2??????KSh?D$??)?=r$c@?H?K?QI? QRJf???rb??Zln??=q???&???,V @]t=D4qh??]t?b;ZE5:?????I?w?HP?P??d*%?H@???? +?R>?N?A?I&?3D?8!M?7???l?!a?C?????0n%?'?k)?]M2M;?`?????3v??H)D?;n?B?R.?????0Bf{????B?????0??^k???m?kC?gz?5x?H???3?F?5??pJ?W{(?}?????? ???????w?;M????2??2????????6,?Q??]J?6k??n???f??H?4~?'?~??1 +?-%?&???k??b;Z?? ???O? /??^?M_r??]??=?:=???>??n?V? +z?S??)???Y0?*!??????m????????????8?????K96(?#????^w=K???m?? H??|??Ah.???bz?????/???fb?m????????vn????m???,W??????%??S???o? ???vm???x?U?C?????@Az[??T?A?gQx???9$%?@:?s-2??;??F8????s#?u???~`"(?)?????;zE????QDf, x??B????(iX???Y??2~s?a???eh? ??3??? ?i? ???????0????g7{^dW?TX??=?9?? ??3??????[?G5?~???a?d?g$}ft +??????|Zy?? +??efz??o???M;-??ur????"%^??qZ?????$????&????kL76????V???7y???/#?=?1?+???g?%{????????<4n??????N??????P??A ?3t}?i??\]? +G?D???cH????T?? +?M.????Y?r???????>%????0??SqM???5?GjQ?m?]?4#????R?u?T???o???,"???.9!???Gr??IV??q?JV?y#C???Hsu?K?y*'%@Q??F???Fp??g????A????????g?q"?\??W???vS??? /?mS?{y?;?C??S?ry~???????H~???F??M?????eS?X??)???????8??C5??:e???;AK?7???????q?=Q?Y??NnX???FJ??????????nzu?T?????u?-???)~l=???~6???c?u?????5;z??????pf?@???H??m???i????l??|~?W?}??\????,| +?J9?m?>j??J<?V]????=z????:E8b?~O?? +_y???F?????Y??(ZD?O?d???(Q?M?E?C??9?.g9t????_D?t??L????KA[??`] ??+???????u???I???(????Q??OH??B????,)???Z??????#3??|???i??????????????????gqp?x!??????8=?vE?_?B?+?Q?B????b6????E??Gxx?m????J\?\??{?F??? {s????wE?@?T???TQ????\Ex)???7???????????????eVd?jQ,?4=??@1N?8K7??`?xa?w??U=???Yw5??? endstream +endobj +180 0 obj << +/Type /Page +/Contents 181 0 R +/Resources 179 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 184 0 R 202 0 R ] +>> endobj +178 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (/autonfs/home/davidk/dblatex-0.3/latex/graphics/warning.pdf) +/PTEX.PageNumber 1 +/PTEX.InfoDict 210 0 R +/Matrix [1.00000000 0.00000000 0.00000000 1.00000000 0.00000000 0.00000000] +/BBox [0.00000000 0.00000000 160.00000000 183.00000000] +/Resources << +/ProcSet [ /PDF ] +/ExtGState << +/R7 211 0 R +>>>> +/Length 212 0 R +/Filter /FlateDecode +>> +stream +x??R;N1 ?} +????? ?f?,?l?Rp}?L2?@??_^??m9o??}??o?xV??C??0??|?? ?rf "??p????W??~???+}??????r??"??M??3?\??!?4K)?~????Vvfm???5~??[G#?6??y GI?7??????????)endstream +endobj +210 0 obj +<< +/Producer (GPL Ghostscript SVN PRE-RELEASE 8.61) +/CreationDate (D:20100125210321Z) +/ModDate (D:20100125210321Z) +>> +endobj +211 0 obj +<< +/Type /ExtGState +/OPM 1 +>> +endobj +212 0 obj +252 +endobj +184 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [321.5267 691.4354 340.6647 702.3393] +/Subtype/Link/A<> +>> endobj +202 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [444.2645 336.0762 463.4026 346.9802] +/Subtype/Link/A<> +>> endobj +182 0 obj << +/D [180 0 R /XYZ 56.6929 815.7613 null] +>> endobj +6 0 obj << +/D [180 0 R /XYZ 56.6929 759.0684 null] +>> endobj +183 0 obj << +/D [180 0 R /XYZ 56.6929 731.2722 null] +>> endobj +10 0 obj << +/D [180 0 R /XYZ 56.6929 677.8333 null] +>> endobj +185 0 obj << +/D [180 0 R /XYZ 56.6929 641.7915 null] +>> endobj +14 0 obj << +/D [180 0 R /XYZ 56.6929 641.7915 null] +>> endobj +186 0 obj << +/D [180 0 R /XYZ 56.6929 615.3924 null] +>> endobj +18 0 obj << +/D [180 0 R /XYZ 56.6929 574.9607 null] +>> endobj +187 0 obj << +/D [180 0 R /XYZ 56.6929 550.1206 null] +>> endobj +188 0 obj << +/D [180 0 R /XYZ 56.6929 500.6172 null] +>> endobj +189 0 obj << +/D [180 0 R /XYZ 56.6929 502.0767 null] +>> endobj +193 0 obj << +/D [180 0 R /XYZ 56.6929 491.1178 null] +>> endobj +194 0 obj << +/D [180 0 R /XYZ 56.6929 480.1588 null] +>> endobj +195 0 obj << +/D [180 0 R /XYZ 56.6929 469.1999 null] +>> endobj +196 0 obj << +/D [180 0 R /XYZ 56.6929 458.241 null] +>> endobj +197 0 obj << +/D [180 0 R /XYZ 56.6929 447.2821 null] +>> endobj +198 0 obj << +/D [180 0 R /XYZ 56.6929 436.3232 null] +>> endobj +199 0 obj << +/D [180 0 R /XYZ 56.6929 425.3643 null] +>> endobj +200 0 obj << +/D [180 0 R /XYZ 56.6929 414.4054 null] +>> endobj +22 0 obj << +/D [180 0 R /XYZ 56.6929 378.6212 null] +>> endobj +201 0 obj << +/D [180 0 R /XYZ 56.6929 352.0227 null] +>> endobj +203 0 obj << +/D [180 0 R /XYZ 56.6929 320.0948 null] +>> endobj +204 0 obj << +/D [180 0 R /XYZ 56.6929 321.5543 null] +>> endobj +26 0 obj << +/D [180 0 R /XYZ 56.6929 285.77 null] +>> endobj +205 0 obj << +/D [180 0 R /XYZ 56.6929 261.7619 null] +>> endobj +206 0 obj << +/D [180 0 R /XYZ 56.6929 229.2362 null] +>> endobj +207 0 obj << +/D [180 0 R /XYZ 56.6929 230.6956 null] +>> endobj +208 0 obj << +/D [180 0 R /XYZ 56.6929 175.3142 null] +>> endobj +209 0 obj << +/D [180 0 R /XYZ 56.6929 176.7737 null] +>> endobj +179 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R /F90 192 0 R >> +/XObject << /Im1 178 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +215 0 obj << +/Length 4909 +/Filter /FlateDecode +>> +stream +x??]mo????_??~??,?W?:4?6 +?^S????|???g?vW????%?Q?H??]??n????h??3r?4ZA?/Z? d.V1?g??6? ?z+???i??!Z?T_?\\???U? g???U?A?C??0????f????????Zc/?4????]?t??x??x5#?U???????1????k9??V???]|uc?2b??a.???????j+t??Zp?z?@?i?V? ??#???dw????G?-??B????R?a??@????????Q?Q]!v????js?U?????UON??6m}???A?,??]?????5'M?#d??l^??M????#???I?uw??????+?.??[?????????????"?? ????6?P?????E[f#?W??U[?n???_??&F`??????l??,???T/?3???x???? +?4H??b????}?I??&???????d6/4 p??]???????@YQX{)??td/?J???7??????????%P?x?1?????M????Ubw?)?p!???Z?????3?@?t?(_???O?+:>???w?'?"??j3 at r?Mj""?$??M??]B9@ ?E6?O???3tci???&2b9 +?"?K?@????????X8l,} +???? ??H? g??T??????}?I ??? G?ypB??E?I?K?H?,?eE.Fs??1??? ???c3 ???2.?p(g??&J?z??`??:????k???? +?????]?F??M??"*?Q????????X?fNUDf" ???%C ?K?Z??;????????????8????????/???u?v????1A????So[?E?YP???/E/???,?w?gWk??? +??z???R?]??????g???6??l=?ZS?D?(zxy,?;?????o4?F*?K?i???m????+V(??G??H???o?[?p???6????2v?+%??? +k?Y$?? ?}?}L??e?????Lt?k??P?v??4???????Y +???c?????@??gz??F??W?????e; ?7?Z???i???Xn????4\?????R???N????D???c?E1?p??P?#1?YY"98?z5?ol???? +?????N??E???_??????"??dO~?????_????????A81j&V!Y?V? ??p?1???,???6??@9???o?????18?sM?? 9"? ?Vn??I?????1 "F0^???I?_????a??fb?%???????H?)??? S1?????L????~???V?'?9?? K????4?????Fo??|1?Q????V??kR?/?L??xT?y ?YbD?y?a???>?k????i??tlLf?kF58:?"???a?Ef???????(?d???3?{?X?????-?X?l???4??t23????x?y???T??V?Y?y?? MJp??N]?O?jS?>z?=???l?zs?+?????uw&[$G?V???????B??2 n??7Pa???N??E,:8$?7P??*??????5?????J}?ne??? ???}e&??8?v??o??j?? ????????1S?}k*?????I??o??T????0??T??o?>>?? +??????N?{[???}???>?!?A/6?Df_p[???>.CO<{?'???5x??O??u +y?S????g????"???J???f?a???*[?$??o??W??eJe??l????3?????[?!?w???a?C2[R?????C??u#????1???u xs?n?Vj?-8???QM????< +.??-?????mi????Y?????Ce?n?z t?*?!?E??B?GpAU?9?(???#??m??^?D?u?!1T?W`?4?"??y:?=??&UAeL_^???$??6???P?? +U ?????y?????(????M?'3?!'?u?!??|?1&??G?G%p?&?? ?? #???v????? ?w???????S^?j?m??j? + ?)???gN'[?ypqqX???Z[?P???%???u?????'??i????*??s?????????*o???S?}iK???????N? +?:Frv??????}L???? +??SW?s??l??L#??8??-???.HW??{? |u?e??`?8??M'?=n?a?:N?\sC????tG??f?????&X??y??????S? ?0zC????1??b??F?]b? ?)_ ??}????m"???W??A??(?s|N8|@?v?8b?????>q?x??u??M?H?ni????k?q?|??c?lQ?EXfFv???3]??#?k????m??????,???d???Q7&&?\? f?+#?^??w$????u\k??(????g?C??????{F??;j?Q+T????&?F?y%%??????o?>? ??II?R?6on???????? r??k??wSB)?,?>Ry??? K??t?q???o?? ???HN???????#??P=???????G??+Y???Dx????b??+J???] ??G?1?F?QIy??????-?L?&vD Qhv5?if?qe?F???[?E?????mo?? +an?p??uW????? +??t???dT"a??3r????#Ny??)?????*/?@?????Y???a+6Dj1,S??q5%??"??|?["o?????_??\m???????Co?X??_ ??Ov?/????8??F?Iendstream +endobj +214 0 obj << +/Type /Page +/Contents 215 0 R +/Resources 213 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 140 0 R +/Annots [ 233 0 R ] +>> endobj +233 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [548.7873 407.9685 567.9254 418.8724] +/Subtype/Link/A<> +>> endobj +216 0 obj << +/D [214 0 R /XYZ 56.6929 815.7613 null] +>> endobj +217 0 obj << +/D [214 0 R /XYZ 56.6929 742.9593 null] +>> endobj +218 0 obj << +/D [214 0 R /XYZ 56.6929 744.4188 null] +>> endobj +30 0 obj << +/D [214 0 R /XYZ 56.6929 710.1122 null] +>> endobj +219 0 obj << +/D [214 0 R /XYZ 56.6929 687.1371 null] +>> endobj +220 0 obj << +/D [214 0 R /XYZ 56.6929 608.8432 null] +>> endobj +221 0 obj << +/D [214 0 R /XYZ 56.6929 610.3027 null] +>> endobj +222 0 obj << +/D [214 0 R /XYZ 56.6929 599.3438 null] +>> endobj +34 0 obj << +/D [214 0 R /XYZ 56.6929 449.3441 null] +>> endobj +232 0 obj << +/D [214 0 R /XYZ 56.6929 423.4797 null] +>> endobj +234 0 obj << +/D [214 0 R /XYZ 56.6929 393.02 null] +>> endobj +235 0 obj << +/D [214 0 R /XYZ 56.6929 394.4795 null] +>> endobj +236 0 obj << +/D [214 0 R /XYZ 56.6929 383.5206 null] +>> endobj +237 0 obj << +/D [214 0 R /XYZ 56.6929 372.5617 null] +>> endobj +238 0 obj << +/D [214 0 R /XYZ 56.6929 361.6028 null] +>> endobj +239 0 obj << +/D [214 0 R /XYZ 56.6929 350.6439 null] +>> endobj +240 0 obj << +/D [214 0 R /XYZ 56.6929 339.685 null] +>> endobj +241 0 obj << +/D [214 0 R /XYZ 56.6929 328.7261 null] +>> endobj +242 0 obj << +/D [214 0 R /XYZ 56.6929 317.7672 null] +>> endobj +243 0 obj << +/D [214 0 R /XYZ 56.6929 306.8083 null] +>> endobj +244 0 obj << +/D [214 0 R /XYZ 56.6929 295.8494 null] +>> endobj +245 0 obj << +/D [214 0 R /XYZ 56.6929 284.8904 null] +>> endobj +246 0 obj << +/D [214 0 R /XYZ 56.6929 273.9315 null] +>> endobj +247 0 obj << +/D [214 0 R /XYZ 56.6929 262.9726 null] +>> endobj +38 0 obj << +/D [214 0 R /XYZ 56.6929 228.666 null] +>> endobj +248 0 obj << +/D [214 0 R /XYZ 56.6929 205.6909 null] +>> endobj +249 0 obj << +/D [214 0 R /XYZ 56.6929 177.2885 null] +>> endobj +250 0 obj << +/D [214 0 R /XYZ 56.6929 176.6907 null] +>> endobj +251 0 obj << +/D [214 0 R /XYZ 56.6929 165.7318 null] +>> endobj +252 0 obj << +/D [214 0 R /XYZ 56.6929 154.7729 null] +>> endobj +253 0 obj << +/D [214 0 R /XYZ 56.6929 143.814 null] +>> endobj +254 0 obj << +/D [214 0 R /XYZ 56.6929 132.8551 null] +>> endobj +255 0 obj << +/D [214 0 R /XYZ 56.6929 121.8962 null] +>> endobj +256 0 obj << +/D [214 0 R /XYZ 56.6929 110.9373 null] +>> endobj +257 0 obj << +/D [214 0 R /XYZ 56.6929 99.9784 null] +>> endobj +213 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R /F98 231 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +260 0 obj << +/Length 4318 +/Filter /FlateDecode +>> +stream +x??]m???????=8/pf?*J????k{?pm/????????xm??????%E??D??8?/????y?_??? ?d&2????D ?6[=??????7??YX??/??7??xV?"?????,?(?X?r,+???X???X??? *?????????W/?QE?,WE3??r)D>[? +!hS??b2??3/??r7??xYZ? ? ?kV??y? +????on0?ENf???(/???F??e?~????????[???~Vh?)Bd?g&y?????Li??h?3??i?) +???f4???? ?W?????D?O?y?M?}?:V???-??Um"IT.(E?$?Q??[B?|>???cz?c??????????q???T?,H?8??F?????~?6?N?]U?5?W?r????7K???Nm????|0??]??x????????????~??n?vu????????|v,gw^?k???6??? +? +8?f???l??)0?\??*????a??h9UQ???????Y2??}{??'?}??????~f??mhl? +?G?:j???????I????~?S?.?j??u?? ?dQ??2??P?6???ux=n??????z`&O??(?d??Ju???????P?p??R?R?*Y?_?f2????1??7=???35o?IT??l???:?????+5???v?Uco?e?bH??????V5b08W$?c +??v_k3?V?u`1Q+n????&;)7?6h4?QA?X??<???????}\TgU.??Rl?m?j)?????C?????z??6h?T???????Cm??SB??????<?????}@??(?^h?j+????f\-R??F??x_??~?????0P2j.???R?????R"????Vo????a?H&?????P??? Hp9?o;y??W???Sh6#g????m? ?@???,C?+G|??V????Ww?????h???4G?f??n?A?????7?=?(?0?;)??I?? ??'F?N??j???j?3?rT??`[9h4?D}??6??C?Fl?h?Y?T)?u??????OhS?('E??V*????z?M?$/????*W?}?#NP???$???A?v?M? ?Q?F?????q?*??){?j???(7????S4B????! +F?g?9? ?Q??/?l?R?????_????v_??4|??r<x???O????P???Z??h?N +6r?g???8?=_. ???.??W??????+U???????YvQ? +??e??J/?<]???J?r?.??`?wk?????HIjv??3?/??5??? +? +????"??@??V?7rlD?????I???8?P1 +???`?}?s ?V*?w???+??K????[???f??????)??C????ry???????=?gL??? ?H?>f??V7b=?#????O??R.~e???+}z?}? ??ET???`?\UH?!??j????????f9 +?8???V??kv??!|?$??IR?\;?@????]?o???~?$}}???4j?K?>7A???B-?9^d???.?l?R?Ws?i?????a????? ?@ >u?i??t???"??T???cVH???????t??????9)sGy??F?_O?????Y??S?????E?;BM????eQ"?4?L??G??p??`????T????n?!????F?????????????aq???Qu(?T?3W?u ?? ??>?C??s???6O+l????B?Q????Rcx?W?3???I????? +???y]???=>??/?/?????3?????????/?jn???????????L???B???Z-???\??5?o?????<=?&??????0&D?w???????L????l??N???????oJ??T???W??[27?3??j??E?z?f?o??9Z????3?16L?????m? +?rWzB????-?????f???l?????????F?T0\-?n??x???)Y??I???S??4??@e???\??%cS??nJ?n3pNl2??N???1?g????-UU?}? ?? ???)[v?B"????e??G??,/???s??j6???=$???C??Ww?#`????l???*???bER?N +?m?z???hTF0>??? ??G?L"!????t?Y?e?ZN?L????25B??DS_??mctAG?PIx7B???*a?;G???9??}??"Y? (h_[[#$?\?,?'?+?k?????eB??????????????)X?UA?i?JE?d{??682???????4?6??A?tW??v?>??#?[p???6?P?Q??????n??(PY?u:?R*LK??? +?f??p^??@?T???.[}u??4]?w?? ???[/?e$n?%?-?????>?/??X???A????`3?v(???? +R?y!*m?|?l??k??D?h??E?P????S*6:?C????/?? sY???? +?B??I{P ??????????4M??????>??G8?XH??s???!???jvO"?:?3??=??>V?Vo?????|??)?e???H?/w?^??C?v?O????n?x??V?8U?@_ot?`???v?? +???C??X?p?O >\?????aoN*.J?I???G???5Nfy??% t????K?b??????B?U]R?5??xX???jW??=?@?S?6?????K?!?|]??????? ??w???~??p?*?Q?=????????w????v???????)?4????jP?>j&???JU?3????9???9 +?W??7?3T?Vw^??v??????oM??L +?Z?g?h1?T???[???y[W??X.?:I??hy\m??\?g????l_[??????7??jy*?G???R8???q??Q??R'?x??I,?'o?c}??BRK?`???/-?jgMY+?????k?M.?6?V??f??????U=?[2o????> endobj +283 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [216.7201 469.032 428.9318 479.9359] +/Subtype/Link/A<> +>> endobj +261 0 obj << +/D [259 0 R /XYZ 56.6929 815.7613 null] +>> endobj +42 0 obj << +/D [259 0 R /XYZ 56.6929 759.0684 null] +>> endobj +262 0 obj << +/D [259 0 R /XYZ 56.6929 738.4887 null] +>> endobj +263 0 obj << +/D [259 0 R /XYZ 56.6929 703.155 null] +>> endobj +264 0 obj << +/D [259 0 R /XYZ 56.6929 704.6144 null] +>> endobj +265 0 obj << +/D [259 0 R /XYZ 56.6929 693.6555 null] +>> endobj +266 0 obj << +/D [259 0 R /XYZ 56.6929 682.6966 null] +>> endobj +267 0 obj << +/D [259 0 R /XYZ 56.6929 671.7377 null] +>> endobj +268 0 obj << +/D [259 0 R /XYZ 56.6929 660.7788 null] +>> endobj +269 0 obj << +/D [259 0 R /XYZ 56.6929 649.8199 null] +>> endobj +270 0 obj << +/D [259 0 R /XYZ 56.6929 638.861 null] +>> endobj +271 0 obj << +/D [259 0 R /XYZ 56.6929 627.9021 null] +>> endobj +272 0 obj << +/D [259 0 R /XYZ 56.6929 616.9432 null] +>> endobj +273 0 obj << +/D [259 0 R /XYZ 56.6929 605.9843 null] +>> endobj +274 0 obj << +/D [259 0 R /XYZ 56.6929 595.0254 null] +>> endobj +275 0 obj << +/D [259 0 R /XYZ 56.6929 584.0665 null] +>> endobj +276 0 obj << +/D [259 0 R /XYZ 56.6929 573.1076 null] +>> endobj +277 0 obj << +/D [259 0 R /XYZ 56.6929 562.1487 null] +>> endobj +278 0 obj << +/D [259 0 R /XYZ 56.6929 551.1898 null] +>> endobj +279 0 obj << +/D [259 0 R /XYZ 56.6929 540.2309 null] +>> endobj +280 0 obj << +/D [259 0 R /XYZ 56.6929 529.272 null] +>> endobj +281 0 obj << +/D [259 0 R /XYZ 56.6929 518.3131 null] +>> endobj +282 0 obj << +/D [259 0 R /XYZ 56.6929 507.3542 null] +>> endobj +46 0 obj << +/D [259 0 R /XYZ 56.6929 444.7788 null] +>> endobj +284 0 obj << +/D [259 0 R /XYZ 56.6929 417.8872 null] +>> endobj +285 0 obj << +/D [259 0 R /XYZ 56.6929 398.9923 null] +>> endobj +286 0 obj << +/D [259 0 R /XYZ 56.6929 400.4518 null] +>> endobj +287 0 obj << +/D [259 0 R /XYZ 56.6929 389.4929 null] +>> endobj +288 0 obj << +/D [259 0 R /XYZ 56.6929 378.534 null] +>> endobj +289 0 obj << +/D [259 0 R /XYZ 56.6929 367.5751 null] +>> endobj +290 0 obj << +/D [259 0 R /XYZ 56.6929 356.6162 null] +>> endobj +291 0 obj << +/D [259 0 R /XYZ 56.6929 345.6572 null] +>> endobj +292 0 obj << +/D [259 0 R /XYZ 56.6929 334.6983 null] +>> endobj +293 0 obj << +/D [259 0 R /XYZ 56.6929 323.7394 null] +>> endobj +294 0 obj << +/D [259 0 R /XYZ 56.6929 312.7805 null] +>> endobj +295 0 obj << +/D [259 0 R /XYZ 56.6929 301.8216 null] +>> endobj +296 0 obj << +/D [259 0 R /XYZ 56.6929 290.8627 null] +>> endobj +297 0 obj << +/D [259 0 R /XYZ 56.6929 279.9038 null] +>> endobj +298 0 obj << +/D [259 0 R /XYZ 56.6929 268.9449 null] +>> endobj +299 0 obj << +/D [259 0 R /XYZ 56.6929 257.986 null] +>> endobj +300 0 obj << +/D [259 0 R /XYZ 56.6929 247.0271 null] +>> endobj +50 0 obj << +/D [259 0 R /XYZ 56.6929 212.0137 null] +>> endobj +301 0 obj << +/D [259 0 R /XYZ 56.6929 185.9542 null] +>> endobj +54 0 obj << +/D [259 0 R /XYZ 56.6929 141.8097 null] +>> endobj +302 0 obj << +/D [259 0 R /XYZ 56.6929 114.9182 null] +>> endobj +258 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F98 231 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +305 0 obj << +/Length 7113 +/Filter /FlateDecode +>> +stream +x??]]w#7r}???C4'V????S]???ox3{w7kx??e=???=og???_?quwxs????????[????}#??f??j#?W?????????k~?j%??v???L??]??;?ei?=+D?;?????,gK?7WeQ??}??( ^?l?pU3?Q4??f}???_?G?W^U???W??4?@]7?5k??`e?&???c%}?? +??P[??u???5" ;V?}_????ox}?Q'??????????????mw??j? MW?asX????5?,???v?????0_?????dF????qe=+??Z+&O_Y ?]Y???g{eY?_/?[uMY???????????????q?0v???,?????????7????????????????a?????dJa?5????????z7??????7??W?????&?????v???? ??=??I????!???O??x8??.b'{H-?cwF????Mw??,Z??K[???e"??????Uk??????vL???/??????`"]????? ?w??? ^??q4j???????/???8?ltu?P?.??(?R?Y+ +9?????j???E?}S????????Xh?>d1??)Y? q?M???+;??]?2?nX?xW?^??XD~???m?]t D?u??????Q ~R!??26???,K???8>6[#??g?[??x???`L +i??OV"0???0?S?0?!?(???(\?&~|o +?&????e?E?gcO?G~?????H?T???B????)???????[{ +^????l?A???x???h?\M??????]?-9`?????? +/es???2`??StE?z? ?j??Z?&??_??-???j9?????:???????o?????(??}?x???? V?@?#????#? +???Mz?F?vC4?yC?l??' +??[{????C?Q?u??????lH]}?q?hT?m?5?l???d?N??[m????????JF????0???Hn???>Pvn???%?V-??J?? +XQ??? +??K?h?????????Z? B??d$??&??*G-&=??J???H????U?^?????/Y?W??(?2?|?m?Z????'???Z?9DE?$cO?G~?5??????0?=?&?}v????????1G?1?G5j????????S???/:o5 v????????m[?????????FiH???h??'. at +???+???M??=c-??x?.?q?iG6r?5j?????Ft?S???G ?????7??3???TW?~f????P?cW?a????:=?o??????l????v?.v??{?K??J~????xd/?B??Z? )?Z????_?????R???n???(K??????!?????????R?????W????????a????x#3?Y?????e????k???^_???u?S?l?Bz????_?V???0? ?:I?C5???Z?R??S????,?:????+????I-?x????vCh??8??8????f????O??z???9,?2v?|s??v +?[tZJ?? +???]^#+ ?'? ???Z +??7????O????g?eY?f?8^M???K?????T+;U??K?^???3?,/?H???v?{??/Z?????@??hU?1"pOfC??>7Wz????????7??I?7????>C?????'gp??[F????=i?Si???]???????(CWz? ?Jo,G??F?]??)???y?^??/~??2?.???^?9?7?Jo???8f?[J???|???t??p?Ks5?vZ?Q$?xTu%??????o?^&????$??????v???n?(=??}????Mb??8 ;??pv??|v?a?A????r?p?A?Op~H?A?37??33Z>????cz7F??XcW??o???????@???u?M>h??J?l.[c^~\?2????J???m??[^tB?y????vg???i?:d?V?n?u?&?|zng +????/$??DH??*y?? ??a? Qwe???o??a??,;1"?L0{?V???PV?N1?????6? .??^??~%s%o??????????8?M[T5og?'?MYkx?S?? ????x???;?.??????I?????*??f1???r????????Pvp??????i??fvF&(iS^??H?/P??v?9?o??????? .?S?(????B??????n?(???i?u??'O?#4?50?!??;???y=??U????u? + ?.E%???p?9?????u\?_-????f??vB ??????????8?????B?????w??w?*??????V?E?3} +??-?}y-?9I^???6?K???????????2??????iOio?@??????nXl?7??7z/???hB?_????W?v8m??????????}?o????"??y?q?????&?~1???s?????6???Q?????????x]wf??!P???U!K?R-??????gD?^WAl??F?c9?zF5%????? ?M4????? +?????D???U??+k?D?A???y?-??\???t??gIh7????q`??>0"??r??y???(84f9r???w???}??yM?? +V*?O?w?WVG?#? +??j?L>y +??J ? +????u?cp3#??uq???ir?6-Z??=?????J???yQ?S{)???S??E??L?k????????A#vsp???d???%3f??99)?????p`??B??????N^????+tS???34E??L??;?v????K???W-??????Vv?ZfN?7 +??p ?yX?^??m?(P? +<?;R~e??/???.v????[??fx??????M?`?(??m?#??|??Tr/???????????fp???dCwUK^?^5D?????0??h??"????h?r#??ZY??u?????#????K???l?????kY?_6*?.R?T?d[R?Zi)?????????cG^?a??????????8?VS?e)X?G67?9??ks?8????<~?/l??????a#_?a?>??mS???????????REX??[W????LV~f?O?p???wnV??a5_??6q?????a?F?a???N.=??(??b???????D??X????6??P\??|\??9?w???????????????"??4-??SWs??iY?????c?p|8(`???&?k ?????`i???V=o?9????=???hV???=?=?K_??rff?-?? ??? +?[u?????a> ???G???????~????~0????V{???e?e???(?`G4K????e??k??????-?F??`?#[}????8=??AL?b?77?s??S?[r/???????q?p??NM,??5XuH@?U?$.????oR????H??(?M?B??????("?}?u?!;q?agh?t?O??(????\?#??t9 +jd??\?g???z?5C??;?"G?? ??azI?'?QHP?~:?2-?????8?R?OF?G??8?tx??2<+nO???c?? ???r?K?O?U?(D?\????m??D??j?????g p???>AL?????87?>7Z?????I? ?.?3D8B? p?? p? Q??2T??P?e"=TX?, +??6-?Q\??}\D??9:wB???P?H?O??8E??>E\?ci??8?k?x?\?????(??o?$~^L????????????????">/n?6??#??z??.?FtD?L6?Z????&?????D??+?? ??s?????? +?y???I?J?U>C?? ??w?k??`Q????m?+?>???~m?? ???????8?'??> endobj +306 0 obj << +/D [304 0 R /XYZ 56.6929 815.7613 null] +>> endobj +307 0 obj << +/D [304 0 R /XYZ 56.6929 759.0684 null] +>> endobj +308 0 obj << +/D [304 0 R /XYZ 56.6929 742.9638 null] +>> endobj +309 0 obj << +/D [304 0 R /XYZ 56.6929 711.0834 null] +>> endobj +310 0 obj << +/D [304 0 R /XYZ 56.6929 681.1955 null] +>> endobj +311 0 obj << +/D [304 0 R /XYZ 56.6929 682.6549 null] +>> endobj +312 0 obj << +/D [304 0 R /XYZ 56.6929 671.696 null] +>> endobj +313 0 obj << +/D [304 0 R /XYZ 56.6929 660.7371 null] +>> endobj +314 0 obj << +/D [304 0 R /XYZ 56.6929 649.7782 null] +>> endobj +315 0 obj << +/D [304 0 R /XYZ 56.6929 638.8193 null] +>> endobj +316 0 obj << +/D [304 0 R /XYZ 56.6929 627.8604 null] +>> endobj +58 0 obj << +/D [304 0 R /XYZ 56.6929 590.7101 null] +>> endobj +317 0 obj << +/D [304 0 R /XYZ 56.6929 563.1566 null] +>> endobj +318 0 obj << +/D [304 0 R /XYZ 56.6929 529.3186 null] +>> endobj +319 0 obj << +/D [304 0 R /XYZ 56.6929 530.7781 null] +>> endobj +320 0 obj << +/D [304 0 R /XYZ 56.6929 519.8192 null] +>> endobj +321 0 obj << +/D [304 0 R /XYZ 56.6929 508.8603 null] +>> endobj +322 0 obj << +/D [304 0 R /XYZ 56.6929 497.9014 null] +>> endobj +323 0 obj << +/D [304 0 R /XYZ 56.6929 486.9425 null] +>> endobj +324 0 obj << +/D [304 0 R /XYZ 56.6929 475.9836 null] +>> endobj +325 0 obj << +/D [304 0 R /XYZ 56.6929 465.0247 null] +>> endobj +326 0 obj << +/D [304 0 R /XYZ 56.6929 454.0658 null] +>> endobj +327 0 obj << +/D [304 0 R /XYZ 56.6929 443.1069 null] +>> endobj +328 0 obj << +/D [304 0 R /XYZ 56.6929 432.148 null] +>> endobj +329 0 obj << +/D [304 0 R /XYZ 56.6929 375.9587 null] +>> endobj +330 0 obj << +/D [304 0 R /XYZ 56.6929 375.3609 null] +>> endobj +331 0 obj << +/D [304 0 R /XYZ 56.6929 364.402 null] +>> endobj +332 0 obj << +/D [304 0 R /XYZ 56.6929 353.4431 null] +>> endobj +333 0 obj << +/D [304 0 R /XYZ 56.6929 342.4842 null] +>> endobj +334 0 obj << +/D [304 0 R /XYZ 56.6929 331.5253 null] +>> endobj +335 0 obj << +/D [304 0 R /XYZ 56.6929 320.5664 null] +>> endobj +336 0 obj << +/D [304 0 R /XYZ 56.6929 309.6075 null] +>> endobj +337 0 obj << +/D [304 0 R /XYZ 56.6929 298.6486 null] +>> endobj +338 0 obj << +/D [304 0 R /XYZ 56.6929 287.6897 null] +>> endobj +339 0 obj << +/D [304 0 R /XYZ 56.6929 276.7308 null] +>> endobj +340 0 obj << +/D [304 0 R /XYZ 56.6929 265.7719 null] +>> endobj +341 0 obj << +/D [304 0 R /XYZ 56.6929 254.813 null] +>> endobj +342 0 obj << +/D [304 0 R /XYZ 56.6929 243.8541 null] +>> endobj +343 0 obj << +/D [304 0 R /XYZ 56.6929 232.8952 null] +>> endobj +344 0 obj << +/D [304 0 R /XYZ 56.6929 221.9362 null] +>> endobj +345 0 obj << +/D [304 0 R /XYZ 56.6929 210.9773 null] +>> endobj +346 0 obj << +/D [304 0 R /XYZ 56.6929 200.0184 null] +>> endobj +347 0 obj << +/D [304 0 R /XYZ 56.6929 189.0595 null] +>> endobj +348 0 obj << +/D [304 0 R /XYZ 56.6929 178.1006 null] +>> endobj +349 0 obj << +/D [304 0 R /XYZ 56.6929 167.1417 null] +>> endobj +350 0 obj << +/D [304 0 R /XYZ 56.6929 156.1828 null] +>> endobj +351 0 obj << +/D [304 0 R /XYZ 56.6929 145.2239 null] +>> endobj +352 0 obj << +/D [304 0 R /XYZ 56.6929 134.265 null] +>> endobj +353 0 obj << +/D [304 0 R /XYZ 56.6929 123.3061 null] +>> endobj +354 0 obj << +/D [304 0 R /XYZ 56.6929 112.3472 null] +>> endobj +303 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F90 192 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +357 0 obj << +/Length 4253 +/Filter /FlateDecode +>> +stream +x??]???????q(/pfI?????y!???Eq?Z[???\I?fQ?? _?^?o????"HD??? +9ORZ??(??VQL??g??E$?Y????????b?f??66?_?^?????2??<^???bN??F??&$?x?z?{?????w???gu????~???V) ?& @?? +c$?".?F0,I??????/???XI?H???????t??9|sEI??lu7??0c??U???\?9\?x??????! i???&2??\?$???p~????0?5?????d|?]Q?p? X???|?????+????????]?Zm?????7?^w?qn?F?n???P???c??V?~???????????h??QC?F?|??P???O??C?Z27?l??|, ??BE?*?!o?Y +2???l??Q???o +?????|? ??)??J?????n??l?? +??+!?C??????k?g?/?"A????wu?V????y????kN??n4z[W]??JcJt]??kn?????f,?}Ww?"?? ????O4??\?????5?????K???DX??*z??1????u ??C\?????AI??*'??M?c|??RKhgw????}?we?2?A?Y??JF=??k??;H?E??-????? F?_?-Q?7 pS*&TOE?????7?O???!V?6E#?4???E??)M??)hoSNPcS6(?/? ??r,???<???^???????A6?hZyy? ??F?JS0?Z????????h?Q???>WJ^U????~?? ?3Y?Y????8t???Z?????? jt??:??@???-?o2?`?Pk???????????????z?U????P?WO7?RLqQ"3R???4?r4???-????b'?J?"??*??[S?e%Y!{?;?\?!?????D??"?e??k?H?Ah?"?F>??e{W?[?H?pLeH c]??? +?? ??p?"????MtP?"???r?????7???H?y?S?]m0%?A??Z??:WV???0 +9??yR?M?pM?uh?NP?6(,??z?2?/2???M??2c??`??3? .?;???+??'\??Y???t??)???f*???V&?????5;&?o??????U~?Q?|{???? +?A(????a at nJ???Z??H?????.+-?_?X?uu???b}gr?6oUK?nSS????????u??6YW??)??Z +????Da??6?d???cN?????Y??>?A?O4U????9????$?B???y?M?T9?????R???U1Wq?jE +?- x??b9TJ??T?~????Z?8?? +????9?6??]?? ??I??C%e=H??zIBm,I wB?dIw'?"c?p?2?l@???d??Sx??SMa'???7o?R??o!? +????????????j??g??kq?????d! +m?eK??e??mR?)_ I?L??~Li~?7?nWo?l??????D??bA?7?? +????Q??oU?R??????4g?}?UVeWb??p.??~)??aL?8??PoS???W??$?????p??AS?GnLE???B????W??HR???4"???[?2??????????N?R) ?)?????>??+??Ta?ua?h?3Z??DTEXq|_??L????,w??h?O ??S +BW??J6~?s?0?i?o?????.c??79d??&<]????E??}???FCCq??h???S????q;}???6j'????j?????O ?Dm????y??"B??N??M?rx???=66?0??KR??~?? ?.??$9K M??)L?s????>?]02I?8l"^DI??[/??h~I;O?v? \3AC????O4j?????P E?-????P]&??G??Z?p??j???l??f????S4???E?t6:1???/]???'?1?O?c??:xY ??pc?|?n?? ?SP????8???N{??c??Bu?gQ]PF?A?r???;,[?j*???@??GOn? /??????'?c?????I_z???c??9z?xI~???[xC7??/==b???O?1????i????t??{???X??4y ??-M8??Z???`fk?W??w?fb?-??)?e{wHg??x? +?????/?<,f????????-M8l^S?m?????y?l??m??>?]?I???*??? +??F??t???????-M8?^S?+`[???u??[@/???"?9?+??I_\;?? ?/??o?,&???JqNi? u? +.c0T^?17?$?/o0?????X.?Qjs?Vy??,?>??/?H0?d??$?.o:???"7?"????w?6??-??c??].G? +.x????S.???\?D?????L{??KR??\ ? ????D4?V??a??0?4 ^>n{??3?*???????@[?c?????:??T`?@8?t?5r?O???2?D??)?*?>?:?#?-?v?s??????E?t?oUL?v??=?cn??????%,?xSP??'|????9???:?6?g????9???x?Zq??v??E?s69??9??/?'i?????R?#?h*?U??A??^? 2??,????d??)_?A?????Y? ??? nQLq????.C?2?t???A??pAq?O?z2?s?}????y2??s?3??d??=??M~,??t??|q??p[??R|?y??%?]}?9????n???s????n?)7q?=M!?f???{??|g +??????3eE???B??X6?K????|)??t?T?(4????I??v?]N?>i???????q?e??$J?\N??9???:?&?I?)??????S??>)$J1??????={?\????C??ht??5?OI7Z??????i?9}?cn??WF?????[}?i???+OM???3 +I??????????????e?|o@?T?>???,6=G??_9[]qendstream +endobj +356 0 obj << +/Type /Page +/Contents 357 0 R +/Resources 355 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +358 0 obj << +/D [356 0 R /XYZ 56.6929 815.7613 null] +>> endobj +62 0 obj << +/D [356 0 R /XYZ 56.6929 465.1132 null] +>> endobj +359 0 obj << +/D [356 0 R /XYZ 56.6929 436.1462 null] +>> endobj +360 0 obj << +/D [356 0 R /XYZ 56.6929 410.4223 null] +>> endobj +361 0 obj << +/D [356 0 R /XYZ 56.6929 390.5382 null] +>> endobj +362 0 obj << +/D [356 0 R /XYZ 56.6929 358.6989 null] +>> endobj +66 0 obj << +/D [356 0 R /XYZ 56.6929 328.8596 null] +>> endobj +363 0 obj << +/D [356 0 R /XYZ 56.6929 303.1056 null] +>> endobj +364 0 obj << +/D [356 0 R /XYZ 56.6929 280.7073 null] +>> endobj +365 0 obj << +/D [356 0 R /XYZ 56.6929 282.1668 null] +>> endobj +366 0 obj << +/D [356 0 R /XYZ 56.6929 253.0585 null] +>> endobj +367 0 obj << +/D [356 0 R /XYZ 56.6929 255.3499 null] +>> endobj +368 0 obj << +/D [356 0 R /XYZ 56.6929 244.391 null] +>> endobj +369 0 obj << +/D [356 0 R /XYZ 56.6929 233.4321 null] +>> endobj +370 0 obj << +/D [356 0 R /XYZ 56.6929 222.4732 null] +>> endobj +371 0 obj << +/D [356 0 R /XYZ 56.6929 211.5143 null] +>> endobj +372 0 obj << +/D [356 0 R /XYZ 56.6929 200.5554 null] +>> endobj +373 0 obj << +/D [356 0 R /XYZ 56.6929 189.5965 null] +>> endobj +374 0 obj << +/D [356 0 R /XYZ 56.6929 178.6376 null] +>> endobj +375 0 obj << +/D [356 0 R /XYZ 56.6929 167.6787 null] +>> endobj +376 0 obj << +/D [356 0 R /XYZ 56.6929 156.7198 null] +>> endobj +377 0 obj << +/D [356 0 R /XYZ 56.6929 145.7609 null] +>> endobj +378 0 obj << +/D [356 0 R /XYZ 56.6929 134.802 null] +>> endobj +379 0 obj << +/D [356 0 R /XYZ 56.6929 123.8431 null] +>> endobj +380 0 obj << +/D [356 0 R /XYZ 56.6929 112.8842 null] +>> endobj +381 0 obj << +/D [356 0 R /XYZ 56.6929 101.9253 null] +>> endobj +355 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +385 0 obj << +/Length 5016 +/Filter /FlateDecode +>> +stream +x??]{o?????ba?u???)??????????@?4(?^???}??'????%?C%va?*?????f8?pDg??d?%-'?(?M?7gxr#??????%??Tysv???I?JA???r"(9?????4??Y????[-?3??????/W????7??G???? +???\B?!????? +?X^L/?a?????8??XyI??PR?z???,???a??????0?YI&?3N?%??Y??>?G??~K3?????a?R>? ????????N}|??$+?(a????(????,=?%???@\??L??^1????d&/?\??V??????????x;Mz??o????m^lA?d3???FO??????Sb=25\o?Tj|???r??\vu?WW2?X^?I?D?2.GiB.K??k}? +??G??!+?%e)?4Y??z?^/V??t?D9?i???x?JK1????u?W?>??|?`?'?1G =????q&?H????????;?g `??T?;Q??kY?@[??J?xY?yY?????????%@?7????LhN?+V.t???^??,1?kp??????????????(|?](????fuh???np?Q?q? +^??>??%?2?????X?XWa????????????|?*?????@9??????A???????????7????k?]???i?8????b?=??n?[}%c|?q?=V??O??j{cx???????????>}?:?????W??nSi?:??~???.V??!????ko??v=_m5?V?? )? ??|!?????.??????3OW?????7?x??^??????K???iot?????????|?U???j_m?jW???? ?a??]W???oo???\?k?Mj???:|:4?4????_??k}????)3?+??w:?????BGQ?w???j?}q?y????Mu?8????l? +????? +!/???~z??m???????w?????Z??ZT=w????k????-?????????????x--??^????L????1u?:?W????>?F~??????|???????? ??z,?;s??O?+?4???w8??nS????`+[???g????h? +??92?8H-?l:\N_?6$?j1????3"??4?fH?K??AV?R???/??Wmm?????E?3?M?5?q?#???L~?L^?T?Sj?=?1???d??T??Zs?]?$T?u-???=??;=??s??^??[?????nt????V?2?_??? +??\?G?????E?????1?b ?Z?????????-??}3+`?,YK.9Q???@2??K??X[?z??????H at o +?vk(-?p#?(????? C??d? +~?s?b?7????$??r?n??*?9+F?=z?A^[%}f2T????R#?????e?????y?fs"Z?-e?]?d??aX?????c,???@??c^??wt?????'?J8G???????W?J????i!u5????E?6Q?H??tJ?lJMW?]?^??K????)?4]?j? v?&?6jh[???c?????p|?!RYQ??????7?Y ?[??!s? +FE?El ??8????????n9>?@j{ ??,>x?-?Y?)?E/ l??K??e?RX ?q???R?PnFowT +???q?o\?????X^e???R?;6>?????r?????ww??????X???(??,?c?? ??A??[?????????????O?|?{6???7???????`%??'?>G????a>??n???Y??l??? ???? +??????p?#?e?x^???)?Yl??????M??=??^?Yt?????'?s?d|????!??SC5w?6|?w?6??????x??%?f?X-W?"L??DY?DBw?2!??kI?????OaF???{O?+???????C?|q\?5 +6??8??!?:aew=? *??L??????p??C?v???@?[Py??s?M?m?R??!? ?????P? +y??5f?"C???(X??2??X0tb??Po?r?&??P??+/>F}O%??]+?)X[??~???y??{ f?S????3TF????]???a???X???F_ |?FK???/}2{&0?RL0f??Q??,??????M? +J?N??D:?nw8L?j?5?1/?|??Oh0? +?%?%R]????F?S?U??9??????q? +V 7Z??q?????3=zg?,xVK???r??G?V?,{??P6?4??v8???C?~ $??Q%?Cnp_?????????}????-?k???=w-`?,YK.???H??@P2{??%Y<?????>=FOe??RZ9O??uT. +??X???gyQQ?,??8?H?????? ??R???????x?W?W???s +???rM?I???"??????????7?AXu????????>?.?O?j??????L????>?l92???????O?yw:?????9??no?=??-)qB?P?SA?O????>n\S >E3*?^????4n?x-?9???????????V??3????v??u??>?mX????N????RC?????8WkH-7???Z???;_|?????n????e???&;??}?9??m???????k??'?????iSm???????^??3???;L?;G?? +?= ?n?y?????? J6?????f?b|??0v??V?F??i +?zpQ|?? K??B??H1R?(?i?? ??BJ?HQ?C???S???h?J$??1?,??7???q?m??????K?0?*?p?5??F??4?> ?? ?1??L?2f?b?????-#??)?j?%? + 8sT)dMW$???|????5]>?8.?'???????q??Db7Df??0?C?]N??? +??!?.?z?n?????U???$?3sC?5w??y0???AH7kCfh&?Av??l?L??\t??3SCr5u? ?< +???A?.??$=?? +cw?F??p??????? ?????53` +o^a?? Y???Y???Al7'???0Q?] ?W???8?8?????TN-`*$?8?k?>?@? K?2.??????X??9?^??? 0??}7?`??&QK??L!????l?aE?????Z??????-????J?$?m??4???i?Y??XM??i?????/?7?ut1??'?3x??,ZG??????oA/X4[??-Z-ZI?y)?z)2Z}Em??hv??}?>?Y???*??}???????>?????'\33??U8?wu??EY????A?o???"-?LwT?YIWo????n?4??9_??f~?????? ??L@???B~??y?P\(?fK?%?%?Z?\o???b??`8??!7???? ?????0na?{???C???F{r????????[??????Z?????????o???a????p??_k?9Tm?^???????d6?yS????'??t???7??)x?^???U?&??j[?n??_m?.9Tm?^?????-?H~c??SO ? +Q +???.??,?s?C???)??o????j???3?????m???;?& +T??????7???? +???R?@n??vE??*??%?5]??N?>k??@????P9?????mN?~uv?'8?]?c<.*??_3??S??6?D?E@?\??????6? ??R????? +??X?oZ???'-|HuV?. +???`$k#;??z???!?jHZu!?A?g?xL?????}q] ???????u???M?]C???? f?S?Z?????K??;?G??f +G??_?W??endstream +endobj +384 0 obj << +/Type /Page +/Contents 385 0 R +/Resources 383 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +386 0 obj << +/D [384 0 R /XYZ 56.6929 815.7613 null] +>> endobj +387 0 obj << +/D [384 0 R /XYZ 56.6929 759.0684 null] +>> endobj +388 0 obj << +/D [384 0 R /XYZ 56.6929 752.3934 null] +>> endobj +389 0 obj << +/D [384 0 R /XYZ 56.6929 741.4345 null] +>> endobj +390 0 obj << +/D [384 0 R /XYZ 56.6929 730.4756 null] +>> endobj +391 0 obj << +/D [384 0 R /XYZ 56.6929 719.5167 null] +>> endobj +392 0 obj << +/D [384 0 R /XYZ 56.6929 708.5578 null] +>> endobj +393 0 obj << +/D [384 0 R /XYZ 56.6929 697.5989 null] +>> endobj +394 0 obj << +/D [384 0 R /XYZ 56.6929 513.8231 null] +>> endobj +395 0 obj << +/D [384 0 R /XYZ 56.6929 515.2826 null] +>> endobj +396 0 obj << +/D [384 0 R /XYZ 56.6929 486.092 null] +>> endobj +397 0 obj << +/D [384 0 R /XYZ 56.6929 488.3835 null] +>> endobj +398 0 obj << +/D [384 0 R /XYZ 56.6929 477.4246 null] +>> endobj +399 0 obj << +/D [384 0 R /XYZ 56.6929 466.4657 null] +>> endobj +400 0 obj << +/D [384 0 R /XYZ 56.6929 455.5068 null] +>> endobj +401 0 obj << +/D [384 0 R /XYZ 56.6929 444.5479 null] +>> endobj +402 0 obj << +/D [384 0 R /XYZ 56.6929 415.3573 null] +>> endobj +403 0 obj << +/D [384 0 R /XYZ 56.6929 417.6487 null] +>> endobj +404 0 obj << +/D [384 0 R /XYZ 56.6929 406.6898 null] +>> endobj +405 0 obj << +/D [384 0 R /XYZ 56.6929 395.7309 null] +>> endobj +406 0 obj << +/D [384 0 R /XYZ 56.6929 384.772 null] +>> endobj +407 0 obj << +/D [384 0 R /XYZ 56.6929 373.8131 null] +>> endobj +408 0 obj << +/D [384 0 R /XYZ 56.6929 362.8542 null] +>> endobj +409 0 obj << +/D [384 0 R /XYZ 56.6929 351.8953 null] +>> endobj +410 0 obj << +/D [384 0 R /XYZ 56.6929 340.9364 null] +>> endobj +411 0 obj << +/D [384 0 R /XYZ 56.6929 234.8692 null] +>> endobj +412 0 obj << +/D [384 0 R /XYZ 56.6929 236.3287 null] +>> endobj +413 0 obj << +/D [384 0 R /XYZ 56.6929 225.3698 null] +>> endobj +414 0 obj << +/D [384 0 R /XYZ 56.6929 214.4109 null] +>> endobj +415 0 obj << +/D [384 0 R /XYZ 56.6929 203.452 null] +>> endobj +416 0 obj << +/D [384 0 R /XYZ 56.6929 192.4931 null] +>> endobj +417 0 obj << +/D [384 0 R /XYZ 56.6929 181.5342 null] +>> endobj +418 0 obj << +/D [384 0 R /XYZ 56.6929 170.5752 null] +>> endobj +419 0 obj << +/D [384 0 R /XYZ 56.6929 159.6163 null] +>> endobj +420 0 obj << +/D [384 0 R /XYZ 56.6929 148.6574 null] +>> endobj +421 0 obj << +/D [384 0 R /XYZ 56.6929 137.6985 null] +>> endobj +422 0 obj << +/D [384 0 R /XYZ 56.6929 126.7396 null] +>> endobj +423 0 obj << +/D [384 0 R /XYZ 56.6929 115.7807 null] +>> endobj +424 0 obj << +/D [384 0 R /XYZ 56.6929 104.8218 null] +>> endobj +425 0 obj << +/D [384 0 R /XYZ 56.6929 93.8629 null] +>> endobj +383 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +428 0 obj << +/Length 6847 +/Filter /FlateDecode +>> +stream +x??][s#7v~??`6y?T, ??;?+???e?j????????C?2/#?R???qm4?9b?Iz?v?!O??;?\t????/?%)??jV??d?l?pAgw???.????BW????_??????4%/g?og%'eE?YM+?5??????????v?????????????_?? .e?Z\Zf????D=?b?4E??K+qYU_????L^w??? +/M?j? +^KV?^?? ??~??$oj6{???? +?=\L|?J??Y]???????9?i]????????EQvB?????3???jtv%?U?k?3N???gL???l??n??????(???Q????????. g? +J???/???????w???Oc7~????emn???wo.??N,?!y??n??|q??g?\??l?*?+HV _??kRe %??q???a~??1.??Xr?2R???}?/?L?J6l???F??vv?9'U?? +?,* +???????j?????E??9??M?^?-??_S?B?,x?h)?S??????+y?h.??W????_?3?. "?????8?3??]?k/V?????????????!=??@T??\????c??1V@????G?C??????U??F + +??{\???+?m??(|'7??????]??h?]l?u\0?q\h??????d????S]?v?5?yQN^??x???t?/?d?H?????3R4`$??)=y%1?h??c`T1B?q??????h?????n?Ud???!??VR +7?+?^_???3??? + l?YcA?m?:K??f???MXm? +??[^[<*9?i????x?h??xR???%??#???`?@[b???-1??u??H???r=_???????wX?????m????AR&f??????UT?E???????u?'???Jx????????Dx?b??e???E?6??????d?Pu?o1 +?,?}DFt?j????4??4??FTs??? +1???^]c?d??1?JQ? $WY??0?@???f3????V\???????"M#??o3???0??????S?m???r??o77?E{???\??Y?R????su?|???J?=???C?? _??z? +??m?Hx???{??A\$???+?????b?_n??7?? ?m]Z??R(??l?E Et1W??????V??/???????????????????????a???ln???l???,T+ ?? ??????HS>.o??y??j???OW??????};W4?????????N???^+??Q?W???S??[???????h?{??U??????j&?????????:2????_K?????f??/w???5?ZP)???i???s?vv?b?v?Y???+?D+V4??c??M??? \]???u?{1????????k??vsX+?}????yx???_????????+????]^???~?????????$?%9,??????????{-????$??b???U?Y?O?x?????az*??|-?o?p?D !?]&)?5EEh?u???????o?8???@^???????????c?H?k??????????7??????\?????D????p?(u??}??:1?w?????n??B??"?Z4??Jaq?????N?r?0i!VNGI???!NH???????-????8O9?#?k7T???J?@?? ??u???i?%??D???????x???# ?R?c?w?p=-sB???F'????"????.?????????t??f1?F?x?+P?@W7??u4?5?K>?,wF??41???T???C?f?;?.???=??W?s??nD???!??*????????M?????0=*w???!~??)|??O?1???N?1*#?6`PZ\???W?mG? +??a?7]m?8?????A??????>???:f??Go?@F?IpH???@?????????"???0|?????>?Y???V?m??0?@???!f?J??fc ?6??F??a?"??"Z??F +?u????? ?U???t?td?g?Fqt??#i??????eE??W3W?^?^A?#????%>???`???e??mm?d#????z?>?{??9}?N??E?Xlp??y???r????[??x????v(u%79r?Z?????+?W??????L^3 ?5@?y? +C?M%?Tvf/.?V??dV? +???}\???????IrVK???ON?P?????J?*ZZ?Bx?"? +?.?r?x?T?c??2????f??)????????@J?i???????4?Y5??omk??u?F??h?%?????n)J???3WW??????? +x??V????o???}??????Aj?F????Py?z?n?I?].??sxt{Ajvf????????` ??f[?????=$m?p????9?juV?fu f?W?\???>???yI?Bcm&\?O????2?Yi??$??YHri?5?-{?g}???] ?Y?? ??XM?r?\?oc????F??}{?;???<>/????8????|????!??%n??G????%? +?]??=????a???6\??????LJ?Qbt????e?S??=n?? +iU\?#B/?a?j?????qKt??4A??????$n3?????wON/???/???]>???;??Cm????2Bi?????Gx?z#?+c????Bf/? +@???[???y??jJ\??????jh?$?Z??'\???h???????g?} +G>??P?O,xT?'N?c?X@?? cTF?X?A?D? +>?p?????n???:??)#D???d +???9??}J +?b??????n?@?????7?????????=?-? +????????|??????B0{???$?? 1j?????????=???????S????????Re?pWB?h?????????? ?0?A`=??????+? K? 8?$???iH??DC?0?k?_?yh??F? -+R??}???|???W?S?6??| $??P ? ? +?.(\?G?\a?n8?? 6??D??{?"? +???;??}??AmQ?{?v??'?1?`:C??8xD???@[???cI??j??g??N^_K????nL?? 1??]f???(??a*???T>??????q_{> endobj +454 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 391.8345 314.7523 402.7384] +/Subtype/Link/A<> +>> endobj +429 0 obj << +/D [427 0 R /XYZ 56.6929 815.7613 null] +>> endobj +430 0 obj << +/D [427 0 R /XYZ 56.6929 760.0646 null] +>> endobj +431 0 obj << +/D [427 0 R /XYZ 56.6929 749.1057 null] +>> endobj +432 0 obj << +/D [427 0 R /XYZ 56.6929 738.1468 null] +>> endobj +433 0 obj << +/D [427 0 R /XYZ 56.6929 727.1879 null] +>> endobj +434 0 obj << +/D [427 0 R /XYZ 56.6929 716.229 null] +>> endobj +435 0 obj << +/D [427 0 R /XYZ 56.6929 705.2701 null] +>> endobj +436 0 obj << +/D [427 0 R /XYZ 56.6929 694.3112 null] +>> endobj +437 0 obj << +/D [427 0 R /XYZ 56.6929 683.3523 null] +>> endobj +438 0 obj << +/D [427 0 R /XYZ 56.6929 672.3934 null] +>> endobj +439 0 obj << +/D [427 0 R /XYZ 56.6929 661.4345 null] +>> endobj +440 0 obj << +/D [427 0 R /XYZ 56.6929 650.4756 null] +>> endobj +441 0 obj << +/D [427 0 R /XYZ 56.6929 639.5167 null] +>> endobj +442 0 obj << +/D [427 0 R /XYZ 56.6929 628.5578 null] +>> endobj +443 0 obj << +/D [427 0 R /XYZ 56.6929 617.5989 null] +>> endobj +444 0 obj << +/D [427 0 R /XYZ 56.6929 606.64 null] +>> endobj +445 0 obj << +/D [427 0 R /XYZ 56.6929 595.6811 null] +>> endobj +446 0 obj << +/D [427 0 R /XYZ 56.6929 584.7222 null] +>> endobj +447 0 obj << +/D [427 0 R /XYZ 56.6929 573.7633 null] +>> endobj +448 0 obj << +/D [427 0 R /XYZ 56.6929 562.8044 null] +>> endobj +449 0 obj << +/D [427 0 R /XYZ 56.6929 551.8455 null] +>> endobj +450 0 obj << +/D [427 0 R /XYZ 56.6929 540.8865 null] +>> endobj +451 0 obj << +/D [427 0 R /XYZ 56.6929 529.9276 null] +>> endobj +452 0 obj << +/D [427 0 R /XYZ 56.6929 518.9687 null] +>> endobj +70 0 obj << +/D [427 0 R /XYZ 56.6929 480.7463 null] +>> endobj +453 0 obj << +/D [427 0 R /XYZ 56.6929 444.5815 null] +>> endobj +455 0 obj << +/D [427 0 R /XYZ 56.6929 368.9204 null] +>> endobj +456 0 obj << +/D [427 0 R /XYZ 56.6929 370.3799 null] +>> endobj +457 0 obj << +/D [427 0 R /XYZ 56.6929 359.421 null] +>> endobj +458 0 obj << +/D [427 0 R /XYZ 56.6929 348.4621 null] +>> endobj +459 0 obj << +/D [427 0 R /XYZ 56.6929 337.5031 null] +>> endobj +460 0 obj << +/D [427 0 R /XYZ 56.6929 315.5853 null] +>> endobj +461 0 obj << +/D [427 0 R /XYZ 56.6929 304.6264 null] +>> endobj +462 0 obj << +/D [427 0 R /XYZ 56.6929 293.6675 null] +>> endobj +463 0 obj << +/D [427 0 R /XYZ 56.6929 282.7086 null] +>> endobj +464 0 obj << +/D [427 0 R /XYZ 56.6929 271.7497 null] +>> endobj +465 0 obj << +/D [427 0 R /XYZ 56.6929 260.7908 null] +>> endobj +466 0 obj << +/D [427 0 R /XYZ 56.6929 249.8319 null] +>> endobj +467 0 obj << +/D [427 0 R /XYZ 56.6929 238.873 null] +>> endobj +468 0 obj << +/D [427 0 R /XYZ 56.6929 227.9141 null] +>> endobj +469 0 obj << +/D [427 0 R /XYZ 56.6929 216.9552 null] +>> endobj +470 0 obj << +/D [427 0 R /XYZ 56.6929 205.9963 null] +>> endobj +471 0 obj << +/D [427 0 R /XYZ 56.6929 195.0374 null] +>> endobj +472 0 obj << +/D [427 0 R /XYZ 56.6929 184.0785 null] +>> endobj +473 0 obj << +/D [427 0 R /XYZ 56.6929 173.1196 null] +>> endobj +474 0 obj << +/D [427 0 R /XYZ 56.6929 162.1607 null] +>> endobj +475 0 obj << +/D [427 0 R /XYZ 56.6929 151.2018 null] +>> endobj +476 0 obj << +/D [427 0 R /XYZ 56.6929 140.2429 null] +>> endobj +477 0 obj << +/D [427 0 R /XYZ 56.6929 129.284 null] +>> endobj +478 0 obj << +/D [427 0 R /XYZ 56.6929 118.3251 null] +>> endobj +479 0 obj << +/D [427 0 R /XYZ 56.6929 107.3662 null] +>> endobj +426 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +482 0 obj << +/Length 308 +/Filter /FlateDecode +>> +stream +x??P=O?0??+nL??wv|?A?? +5[???n?Hh?*?=.IZ?Z? ????{??0??????H??a???= +?9?@J?ns1~0^zV ?XI?h????+ ?j?L????`rW??E??y>?R????????AJ$?1?[????d?=??:q???????6??z?9?*?0(3?1@?2O???W?2????s?U????+n??m?/;N?e^????%tf????G?$?r??R???z????Qv?*4?}Y??'EB?a???z? ^??? +?nB??vs?D?qsm/m???q???oz?8t?????endstream +endobj +481 0 obj << +/Type /Page +/Contents 482 0 R +/Resources 480 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +>> endobj +483 0 obj << +/D [481 0 R /XYZ 56.6929 815.7613 null] +>> endobj +480 0 obj << +/Font << /F50 132 0 R /F51 135 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +486 0 obj << +/Length 3502 +/Filter /FlateDecode +>> +stream +x??[K???????!U?T?0???????q?dw|H?>P5b?"e>vv????H?"5k[???v???n4?~???_?P??X???+f4??M?x??/o?????V?Y?=??}??E?b-??a???i?E??,??,?;?z???????r]?=???LE???????T???<'?v?WS???O!X?? ?e!04 #40 b{??gX?=??-??<`,???b???}??2??????)??j j??????????S?]L????T???!???lV?<?? ?b9???!??? Ud?G?e?m?TY3????=^/J??u(???f?????f[??y:?????W?z8z(???f??m?d???v?o?4?N????9?_M?/??dq?9?+& y?q????\????uG??M2???X0??/ +???D??9K3t?2Z6??B?p1?~???g?r?[)??,?z???p9??????4-?.kF?UjY????????v?~?]?????(???#/??y;??|???8 ?3P0?? ?????d???????????????? ??3q3? +,???I??1?????`B??/??aA???`/BG`?r~- PF?&???mb?????? ?????$???????\?N7e?K0 ?l?$s?g??????T????j?????????r?K??????-^????\! +0s*??E??Z$?2??Z????:?o:???;?? +?I????55 fS?x/????????C>u?bC????zc? ?^?^??]??????bA=e??L???38?SqXl??K]lj???<ZP?N`]3?????????? ?0#?X?C6????P?Ue??e?a??Q?>P}??{????x{??[?/?;:???|????w]$?s?OH-t)^8?!?F?u?{?*??%bN?3????w?O???*]8?????>?H??&T1yJ9b?_n????`???????????#? +g&?'Z@>?wt???>?\b????T??Mi?uz?x??1j??.O?n?%??_b?W???e??(Hr???k:?Vn?|????E?z?S?-????rD???{?????Z`?$?cG[[w?????.?? $????'??u?W??lf?h??{}?a?K?KM??!??;?^?Ll +??=?l?????f?8?rw?O???]??????n?1-?K?t;??u??????+???P??a???9 ???O8? ??,(??*!0('??,???I? +???.???G?W??????{zp??@?nT????r??S(??? +0?.??????'_?eTB??p??T??c????g??['~????'??/?r?3??x??}W^????L??????$X@???????z?????x?endstream +endobj +485 0 obj << +/Type /Page +/Contents 486 0 R +/Resources 484 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 382 0 R +/Annots [ 492 0 R ] +>> endobj +492 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [204.0186 316.2483 223.1566 327.1523] +/Subtype/Link/A<> +>> endobj +487 0 obj << +/D [485 0 R /XYZ 56.6929 815.7613 null] +>> endobj +74 0 obj << +/D [485 0 R /XYZ 56.6929 553.0513 null] +>> endobj +488 0 obj << +/D [485 0 R /XYZ 56.6929 522.509 null] +>> endobj +78 0 obj << +/D [485 0 R /XYZ 56.6929 468.7561 null] +>> endobj +489 0 obj << +/D [485 0 R /XYZ 56.6929 440.3707 null] +>> endobj +82 0 obj << +/D [485 0 R /XYZ 56.6929 409.4559 null] +>> endobj +490 0 obj << +/D [485 0 R /XYZ 56.6929 372.4592 null] +>> endobj +86 0 obj << +/D [485 0 R /XYZ 56.6929 372.4592 null] +>> endobj +491 0 obj << +/D [485 0 R /XYZ 56.6929 345.105 null] +>> endobj +484 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F52 139 0 R /F90 192 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +495 0 obj << +/Length 4141 +/Filter /FlateDecode +>> +stream +x??]_s?????????pd?w3M??4/I{??C?Z?m?$??????? ?A?h5??4???$r??],???Y`??,x??????p$r?-V? ???{?/??Y??K??????q?(Q??|q}??)??? ??T,?o?????;\-)???6???{?????(Y?h??G??HZ,????s?=K0<(??7???'/?????DIP??q?????~??[??? ?XY??|????,????,????????z??.e???O??!Z? ?y??+?\??F?A??k6??!??3D??TJ?p?y??&9f%?"_????y\????<`?%4K?s66m?S??xU??G?????[?s}E??g??zu?"?V?I????????? +^?? ????C\?9????????H6Tr????=??%?.?0k?j?C???d?C?bPcC????J??j NB????*??F???>?+??o7?r)V???)??-XR8C7n???}?@8??m'Lb?R??i??$?b????)x?o0"g? ??g?2????!???U?F????f???#??tE?-9D??S6=?3d??kr?$????n?Q??jv?zw?)ys???t???>n4!?$??!?w?????ev????7u0??s???????A?zi"d?)?T??vK%?????????;'(#\???zVs???Z.?T??????4?:r?/`?????????i? +3????;.??[????tC.&???IH?M ??F?Ld^6?>E??'?1iy?UrH?J?'E?A +U +T??C??hf?y^?G???f??}{??-?BK?????\&\???9??????n??s+&:?????????X_'wC??";?K??&zA??Rr????)??g????b??S?8?IM?5?????? +??^???]B +???????"N??y6%??+????????? +?Ev?4???4?t??@f???*????M????38???5/?4q??*???M?d???]?????j"s+0b?C3???~&!??{???83`??7?&!??7??????{z? +w?4? +^\???F??? 1?BM????(-P!??@??????0??"I??????xO?n??N??y6)?C????>????(g at q?8???8?t??E?x??K?)?1??|?.??zDz 1????????H ,S? ?*??s???rL?(??mb??????rl??O?fsXo??c}?D???I?!L??}E??(?8??5?=?,G??b?BQ??'??\%???=!@^ A????&:?43?a?Xn??^-?9M?h??????qvL? +???F??/ k 1L\s??X??/?.Q^.?h????f??(??J????F? o&???N\? ???????8?v?EBC?????j?a??~??Ap.O??>??J??D?dA8??x??T)LE7????i???q??g??j??m????T'???????`>??? +?"??C???)??8??? ?c????(??????b??=?w? !F`???I?g?!'?B??"s|? -?????_??;M???????f??????????C?})??x??./??3???g??tt#Q6????????q?T#??'D??? ?1???X.??G??C????????m??????o?m?:4????????Jy?? +?9?`?"i??L?? ???? +c?+????5?7aG2S??y$???p???cpOMT?~OM??6??]M??u????????n_????m,q??????M?D:?s???g??z??i???_K????f6?????F?W4???????J-????1\???c6?<"+??p8.?"U<@???x@(`?b?\?p?????.p?????|m?????????oj}??????I?;4??}}PL???w???^]???Eu?.H??+???-?Z2Z^?K?%?????f?(U??T???jw?6????t?????G +??KJ.?`??k?\p??????U} bZ +?fN?I*????]??Zp??;????7I2?T???Sw?f?ZV???W?????nx}??? ????V+[????Z?????m???V'?>&?w??6$_0*dW???Z9? ?L I)b?K*JTpS(??[1}?? ?K?????J???F?%???+WL??M?B?? +?Q??L??4r ???????p????(??u{?~s[??????>??%??%t?C?[???K??D?4?M&??LM?yM?m? f??/?$??|;k?wa??wqqX???Z[7S???%???[?7??iD?????}n?op??????GeR?c?????Oc??????"??9???<(+??;xC???i?j??A: #?s??????`?uNy?S?? ?Wc?:??(??-???> endobj +496 0 obj << +/D [494 0 R /XYZ 56.6929 815.7613 null] +>> endobj +90 0 obj << +/D [494 0 R /XYZ 56.6929 759.0684 null] +>> endobj +497 0 obj << +/D [494 0 R /XYZ 56.6929 738.4887 null] +>> endobj +498 0 obj << +/D [494 0 R /XYZ 56.6929 716.6059 null] +>> endobj +499 0 obj << +/D [494 0 R /XYZ 56.6929 718.0654 null] +>> endobj +500 0 obj << +/D [494 0 R /XYZ 56.6929 671.774 null] +>> endobj +501 0 obj << +/D [494 0 R /XYZ 56.6929 673.2335 null] +>> endobj +502 0 obj << +/D [494 0 R /XYZ 56.6929 662.2746 null] +>> endobj +503 0 obj << +/D [494 0 R /XYZ 56.6929 651.3157 null] +>> endobj +504 0 obj << +/D [494 0 R /XYZ 56.6929 640.3568 null] +>> endobj +505 0 obj << +/D [494 0 R /XYZ 56.6929 629.3979 null] +>> endobj +506 0 obj << +/D [494 0 R /XYZ 56.6929 618.439 null] +>> endobj +507 0 obj << +/D [494 0 R /XYZ 56.6929 607.4801 null] +>> endobj +508 0 obj << +/D [494 0 R /XYZ 56.6929 596.5212 null] +>> endobj +509 0 obj << +/D [494 0 R /XYZ 56.6929 585.5623 null] +>> endobj +510 0 obj << +/D [494 0 R /XYZ 56.6929 574.6034 null] +>> endobj +511 0 obj << +/D [494 0 R /XYZ 56.6929 563.6445 null] +>> endobj +94 0 obj << +/D [494 0 R /XYZ 56.6929 526.4941 null] +>> endobj +512 0 obj << +/D [494 0 R /XYZ 56.6929 498.9406 null] +>> endobj +98 0 obj << +/D [494 0 R /XYZ 56.6929 383.4193 null] +>> endobj +513 0 obj << +/D [494 0 R /XYZ 56.6929 355.0339 null] +>> endobj +514 0 obj << +/D [494 0 R /XYZ 56.6929 215.6368 null] +>> endobj +515 0 obj << +/D [494 0 R /XYZ 56.6929 215.0589 null] +>> endobj +516 0 obj << +/D [494 0 R /XYZ 56.6929 204.1 null] +>> endobj +517 0 obj << +/D [494 0 R /XYZ 56.6929 193.1411 null] +>> endobj +518 0 obj << +/D [494 0 R /XYZ 56.6929 182.1822 null] +>> endobj +519 0 obj << +/D [494 0 R /XYZ 56.6929 171.2233 null] +>> endobj +520 0 obj << +/D [494 0 R /XYZ 56.6929 160.2644 null] +>> endobj +521 0 obj << +/D [494 0 R /XYZ 56.6929 149.3055 null] +>> endobj +522 0 obj << +/D [494 0 R /XYZ 56.6929 138.3466 null] +>> endobj +523 0 obj << +/D [494 0 R /XYZ 56.6929 127.3877 null] +>> endobj +493 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R /F98 231 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +526 0 obj << +/Length 5323 +/Filter /FlateDecode +>> +stream +x??]]????}?_???a?Ua??^?^?i?iR???}H???????P????{@|$@??^?U>?8?!?p?? t??t'$??|???? e???*???oo????+??i??????q0?I??????, I??, R??0???~?????X???qp????t?????{8??285a??( +IJ?l6???q6?R +'????????y??V3S?????????? f+???W????????QNg????!KB??????????aD? ???A ?x6O????hs;????AQ )?f!??,?U????# ??T?|????9?%N??w??l?gi*?????[!??y?Ie??8K??N.?+pl?@???~&~r??4?$bQ??O?A?A????6?C`S.???P?]?1??f3??>???4?Q~???BS????????c?*??,?1?J??Kq??0?$"a????@???P????G?s?n??r[X @?h??????p?]?U:OH????J+{????*???O! ??????V?]???a??????zk{?_.??4??O!??e1Roe?[?q????S??h'???Un?A???? ?`???k+ ?*???YF?FW[????r9??????wG???%$???_wm????9????Y?$c???1x?\?,???,iN?;??++ Z?eX???dI??G???? ?qXl?izX???|?nz???? ??? +??*bj ????A?k?[]?c"?L?aJRg2????????Fy??D@????y|?? A??'??*??????? Ix?X>?w??z\/a??jH&Ap=?????!b|hC?DL?????????8???b5?S?K?O?r??4???????y??6n?,? }???N1K??t?u?? +G???????N*??$? ?????`?B?i.%???\??w"W??????!?W*??TI?=B?EE????????H_????>7>????9S?$?B6t?m????y?F?]?(?H??s?????????r?q}?z??"? v??s????v??YN ????^???F(??b???????EC????&?????5yB?.?s????($i?g a"O?????5j??Fz}BI?/@ZF?pq?*? ??????f`???eD?oDM????A??p???]|)??z??M?R????l??U??????[W;D|?P?L??????)EzOQ+?f???"????????e?0;?\~?????sN6?;YRK\T +P??FW?}?$?t???gK??&?$??JL????z#?????_,?, ?!??F,??? ?????+?????r 4????q?)??C +?f??)l??i!?????8??#?zva?~*?^?K?!??t????`,???UW?????^??Qi?zT??E?2?c?N?????t??m ?( ?$?????0?]?}=?????+??Rz ??????????\?k?#B?8Gj??0h??F;o?x????K??????EsU?????T?(>?T???????`???c+?xl??????y??`????gT??=???????????K?.??????BC??IU?????%dc ????R??R?N#x??G??'a?????Nh??O??h? ?[????????a?=????^VZ????>?? ????z??:v?g????^??O??e4I??>+?^VV?>??????)?&?vb4_?? L??~.?[??u#??%???1?????(???N?OA(? ???4????&?a?v?^??w???C?L?O????^N????9DZDYL?????? ??????V?????4???[a?????0u??g#4f??????&?D4e???????.?????;9???~jv??7wv)?|??z?'FE???C???#=??@ ???????)???cJ???K???(LCB?????qhM?????????o%PVO?? ?=?;???\X?#d?]?e??\X??????TJ???9??y3?a#????^?3???XXg??:???.m`ca?!?jmh?^??&????*????;??Vi?w???"c??/?`??r7NS???[ki?????UX?m[g?fA??EvV????F???Ks???????{?\?????UX?;?_s?&&?*?]s?I????M?1x??q~xW?fA?????p???]??&?#??nj???M?qu?[????7?E????\bc????lt??=??????S.j????????!??????? ?V'?????b[?????,????????p????1???$?oJhm????_?? +l?????=6?;B~?`{?l????????p>oKTh???endstream +endobj +525 0 obj << +/Type /Page +/Contents 526 0 R +/Resources 524 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 557 0 R +/Annots [ 530 0 R 531 0 R 532 0 R ] +>> endobj +530 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [342.6799 664.3934 440.3138 675.2726] +/Subtype/Link/A<> +>> endobj +531 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 562.6401 130.2369 573.544] +/Subtype/Link/A<> +>> endobj +532 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [306.5539 502.9987 440.0533 513.8778] +/Subtype/Link/A<> +>> endobj +527 0 obj << +/D [525 0 R /XYZ 56.6929 815.7613 null] +>> endobj +528 0 obj << +/D [525 0 R /XYZ 56.6929 759.0684 null] +>> endobj +529 0 obj << +/D [525 0 R /XYZ 56.6929 752.3934 null] +>> endobj +533 0 obj << +/D [525 0 R /XYZ 56.6929 470.0323 null] +>> endobj +534 0 obj << +/D [525 0 R /XYZ 56.6929 469.4545 null] +>> endobj +535 0 obj << +/D [525 0 R /XYZ 56.6929 458.4955 null] +>> endobj +536 0 obj << +/D [525 0 R /XYZ 56.6929 447.5366 null] +>> endobj +537 0 obj << +/D [525 0 R /XYZ 56.6929 425.6188 null] +>> endobj +538 0 obj << +/D [525 0 R /XYZ 56.6929 414.6599 null] +>> endobj +539 0 obj << +/D [525 0 R /XYZ 56.6929 403.701 null] +>> endobj +540 0 obj << +/D [525 0 R /XYZ 56.6929 392.7421 null] +>> endobj +541 0 obj << +/D [525 0 R /XYZ 56.6929 381.7832 null] +>> endobj +542 0 obj << +/D [525 0 R /XYZ 56.6929 370.8243 null] +>> endobj +543 0 obj << +/D [525 0 R /XYZ 56.6929 359.8654 null] +>> endobj +544 0 obj << +/D [525 0 R /XYZ 56.6929 348.9065 null] +>> endobj +545 0 obj << +/D [525 0 R /XYZ 56.6929 337.9476 null] +>> endobj +546 0 obj << +/D [525 0 R /XYZ 56.6929 326.9887 null] +>> endobj +547 0 obj << +/D [525 0 R /XYZ 56.6929 316.0298 null] +>> endobj +548 0 obj << +/D [525 0 R /XYZ 56.6929 305.0709 null] +>> endobj +549 0 obj << +/D [525 0 R /XYZ 56.6929 294.112 null] +>> endobj +550 0 obj << +/D [525 0 R /XYZ 56.6929 283.1531 null] +>> endobj +551 0 obj << +/D [525 0 R /XYZ 56.6929 261.2353 null] +>> endobj +552 0 obj << +/D [525 0 R /XYZ 56.6929 250.2764 null] +>> endobj +102 0 obj << +/D [525 0 R /XYZ 56.6929 212.0539 null] +>> endobj +553 0 obj << +/D [525 0 R /XYZ 56.6929 175.8891 null] +>> endobj +554 0 obj << +/D [525 0 R /XYZ 56.6929 150.0412 null] +>> endobj +555 0 obj << +/D [525 0 R /XYZ 56.6929 130.1159 null] +>> endobj +556 0 obj << +/D [525 0 R /XYZ 56.6929 98.2355 null] +>> endobj +524 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F92 225 0 R /F96 228 0 R /F57 148 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +560 0 obj << +/Length 4741 +/Filter /FlateDecode +>> +stream +x??]]s??}????>H3L??W'qf?&n??Ik?/i?-m??re7??? xA???3??4??W????X????W????????hV5/XU?|???e????3>?\B?????.???.K???(??V?????"gM}(U.??K?R?T6^??B?D@??MS,!??????)???.Dv~??????????????zs?????g?g}~???O??yq{?O????n??????????????~o}????????????O!????_?6??f3?;?[????n?? ???Q??????vG3"???????p????????_??^??? ??v{R?<:??y!??0?B?D?&???ANC??Ca??/??B?Y? +??O???N?y?????]o?8????}?t??]??~????5/^???3Z????7??Gzb?k8/4?/??W?hU??? +?K?!?9??I???f}?gD?^3?{?Rd,k2?s?b??9???/ju?9uw??]w??l?????????8:h{8?O?????c?t??j;???}?????????$7?q?t???? ?t??q?????????]??v????j??L??"K??a????R?d??K=E???d???J????W?n?f65?f?I9gBp??????4?*?,C?4????F^W???Ak????%??????2 f??~t?O?????$[oV??_????a?*k?ek2???? +Q????O???s5??|5????T/?F???ZP ? FC8??f??k??.8??@P?6???Ys??$?2???'?????|?n?\S(@??( +??????A?!<+?yC< ??UK??}???/?&?Sjg? -??a~???3??=?????j???n???PT/>?-f8???2?a?g3 +?g#f?4????w?j????k?T????? +???,k???I? ?$??W??u??,??Z??? hC??e ??D?&???Q?s????E?V???p?6???? m???L?l?Ix7??o????]?6j]?6?,Y???|f?(x/[?}?????{??S?&N?}????7??Y? +Y?m?g 2WkD??4????}?????? +??K"0G????MGUo]+zqd???????;)^ tR?3?g?K??N????n???????fQ?6?@ust.Ugde??????52??2??????A??+??)?pe*?1?B^???a7z??y^?B??b???e=??Ck????,s?+????v?5???l? +?v???=??:??y?.5?Q{?M??K??J]???????'?y??????"?r?2????x:???????A??|\3O?b???^V?T_??D7? ??3j?'?????v?R?:Jx2?qTk????:O??ne+?u9??&s*wk2?`2/??:<??????????Em?T???&????W?}???L^????0??O???z) +??!g?c???? X/[X?????<8? ??????????.N-p?E]?T??e&????)-????%1??(????Q+)????$??7j????8?LM??~ +?!?B*Y??7? ? +K?????~?]??e?=???h???Bd??~??H{}? +??? ??p *vrR?:B??}u?a???,A?#]1??(?U?XgL"??x??]N? +p>???&*??f???H???X????1??????1???? ??:??@???-??^.????c*?????Q%g56??&??(?t5???2???6 +?ts????n:?????????Z[?o??????????DAg=?Hg???z?:?? +???r??x??j????9?q???????Q=?p????????m???????8??U????Mg??MG?ra??$??td'????u??n:(?i7???*?T9OE-<?,?C??fsq?3?@N`B ????#??]m???X?c[???G9O?????5?S9[???7????e<???~6|??D?SU9????u?E??O*?b????E???OH?&.4m?Q??mMo?????Y??]2q?'??????qM??V??Z???C0?9?~??q?Y?RB?_?wnJ???|?????o???s?0?TDy ???,[?xF!?L??????g??I??6???Y?y??? &? +V????38?~?w??:?'??qpp7k?t?_?A??_??1?\?I??$??-9????g??Y????8?Q?8[x,2??}??@??c???t?;??????e???eTMB????SV?? i????? ?A@??????????L?@j?^?&t??lj?yg{????>??)#???Ztendstream +endobj +559 0 obj << +/Type /Page +/Contents 560 0 R +/Resources 558 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 557 0 R +>> endobj +561 0 obj << +/D [559 0 R /XYZ 56.6929 815.7613 null] +>> endobj +562 0 obj << +/D [559 0 R /XYZ 56.6929 759.0684 null] +>> endobj +563 0 obj << +/D [559 0 R /XYZ 56.6929 732.2374 null] +>> endobj +106 0 obj << +/D [559 0 R /XYZ 56.6929 702.5053 null] +>> endobj +564 0 obj << +/D [559 0 R /XYZ 56.6929 667.2187 null] +>> endobj +565 0 obj << +/D [559 0 R /XYZ 56.6929 648.7762 null] +>> endobj +566 0 obj << +/D [559 0 R /XYZ 56.6929 650.2357 null] +>> endobj +567 0 obj << +/D [559 0 R /XYZ 56.6929 639.2768 null] +>> endobj +110 0 obj << +/D [559 0 R /XYZ 56.6929 604.5727 null] +>> endobj +568 0 obj << +/D [559 0 R /XYZ 56.6929 578.7294 null] +>> endobj +569 0 obj << +/D [559 0 R /XYZ 56.6929 544.1788 null] +>> endobj +570 0 obj << +/D [559 0 R /XYZ 56.6929 545.5039 null] +>> endobj +571 0 obj << +/D [559 0 R /XYZ 56.6929 504.4775 null] +>> endobj +572 0 obj << +/D [559 0 R /XYZ 56.6929 505.8025 null] +>> endobj +573 0 obj << +/D [559 0 R /XYZ 56.6929 466.699 null] +>> endobj +574 0 obj << +/D [559 0 R /XYZ 56.6929 466.1012 null] +>> endobj +575 0 obj << +/D [559 0 R /XYZ 56.6929 426.9777 null] +>> endobj +576 0 obj << +/D [559 0 R /XYZ 56.6929 426.3998 null] +>> endobj +577 0 obj << +/D [559 0 R /XYZ 56.6929 385.3734 null] +>> endobj +578 0 obj << +/D [559 0 R /XYZ 56.6929 386.6985 null] +>> endobj +579 0 obj << +/D [559 0 R /XYZ 56.6929 345.6721 null] +>> endobj +580 0 obj << +/D [559 0 R /XYZ 56.6929 346.9971 null] +>> endobj +114 0 obj << +/D [559 0 R /XYZ 56.6929 312.2931 null] +>> endobj +581 0 obj << +/D [559 0 R /XYZ 56.6929 289.04 null] +>> endobj +582 0 obj << +/D [559 0 R /XYZ 56.6929 270.1143 null] +>> endobj +583 0 obj << +/D [559 0 R /XYZ 56.6929 271.4393 null] +>> endobj +584 0 obj << +/D [559 0 R /XYZ 56.6929 230.4129 null] +>> endobj +585 0 obj << +/D [559 0 R /XYZ 56.6929 231.7379 null] +>> endobj +118 0 obj << +/D [559 0 R /XYZ 56.6929 197.0339 null] +>> endobj +586 0 obj << +/D [559 0 R /XYZ 56.6929 173.7809 null] +>> endobj +587 0 obj << +/D [559 0 R /XYZ 56.6929 138.6325 null] +>> endobj +588 0 obj << +/D [559 0 R /XYZ 56.6929 139.9576 null] +>> endobj +589 0 obj << +/D [559 0 R /XYZ 56.6929 98.9312 null] +>> endobj +590 0 obj << +/D [559 0 R /XYZ 56.6929 100.2562 null] +>> endobj +558 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +593 0 obj << +/Length 1322 +/Filter /FlateDecode +>> +stream +x???Y??6???)??rQqIJ????J??(z?@?6e?l)?/??0?Rh??>?FQ?6m?????]?;q??4L?;??V/?|?????w/ZJ&????-i??H??,c??}??? +]??}?J???1??}9?^H?????B?>7?j?? ???f +~?*?j????????3??P]?T???:?? ??b?Ao~dA???????T-tgQ?:???dPgwx???-??nE??-1?TB|????b?d??z??$?lqJ?l?K??h|(?z ??????> endobj +596 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [170.804 721.5872 284.337 732.4912] +/Subtype/Link/A<> +>> endobj +594 0 obj << +/D [592 0 R /XYZ 56.6929 815.7613 null] +>> endobj +122 0 obj << +/D [592 0 R /XYZ 56.6929 759.0684 null] +>> endobj +595 0 obj << +/D [592 0 R /XYZ 56.6929 738.4887 null] +>> endobj +597 0 obj << +/D [592 0 R /XYZ 56.6929 712.6209 null] +>> endobj +598 0 obj << +/D [592 0 R /XYZ 56.6929 692.6956 null] +>> endobj +599 0 obj << +/D [592 0 R /XYZ 56.6929 672.7703 null] +>> endobj +600 0 obj << +/D [592 0 R /XYZ 56.6929 652.845 null] +>> endobj +601 0 obj << +/D [592 0 R /XYZ 56.6929 632.9197 null] +>> endobj +602 0 obj << +/D [592 0 R /XYZ 56.6929 612.9945 null] +>> endobj +603 0 obj << +/D [592 0 R /XYZ 56.6929 581.114 null] +>> endobj +604 0 obj << +/D [592 0 R /XYZ 56.6929 561.1887 null] +>> endobj +605 0 obj << +/D [592 0 R /XYZ 56.6929 529.3083 null] +>> endobj +591 0 obj << +/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +606 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozeng e/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis] +>> endobj +230 0 obj << +/Length1 1647 +/Length2 8562 +/Length3 532 +/Length 9439 +/Filter /FlateDecode +>> +stream +x??weT???.?-8$@?F?????? +4?44nA?C  ????@?????????s?????3s~?u{?????T=U???????TUg?BMA?P[GVvA?2b????(CY?@N??&6?'???V +2qCm?MA?m +2pr8?iRP;7???@???????????&S? O?` [???3?j?:>Q???A ??%`??TTu?????(k??lA??"T?Lm?fE????0??6-fP[ ?wi?O\??? ??r5????v ???? ;,`&??Og??m?l???x?7??I?}????V???e?"??????? +n?v?? +?=mD6?[?@?????3q???6?? ??'?i?{?+.!??e??Xx?f?{?L??? ?zt??C???C at si????ke$aN5^y?????????{tw?? ???2?F?? +9#>? ??O%{?Y????XS?s,??g?????>?0q?riz7?Q????? ???K??`4???J??|???????\??I??f-}n??n?y?S?e????:n???3? {?? K?Sw?PB[1[[V_U?i??sMw????R????.????R?????5nL???7!{?x0R.EVX?Jc{?4???&>/??g?U!?P?????q???e+?(???{T2/?`?????{)GrU???n??vM???????R????:??2w??h?g?????|*^w??A??h?????\s??&??o? +kU???Nq4?j?@?[?`?P? |+l?a&?^??? +??o??&??3?o?k?]7??--?9?o????????uxg??<^???E??!?????k???(?zy*?\?%????_?Re?e?????y|?(e?????c`2???j@????*??b??~N???NHE?r???????=??B&?M????#w,i??b??i??qJ??D?I?p?{?????g?kkf=;gd"D?5?\??????5?N????oc D??w???5.E??j6??,A??O?????iUn??2??z?q*??uZ???>??a?!?S??????^??/???P?$??n???U??%????]r6?p??????:??P?t,5? +@???}u +??????1~?$2??f???NH?H?2??3?????-I?????}????X?R??????6jSn4???i]D?r???????>???j?Bm????m(? ?%_???x@????w?u??m??Fd?|:?2??=????+?V???.??)?.? ???2???c,c?????8]?1U[?^?? ??=?y??0!Uh?/"H??,??Vy\????:??q?cI?-???oYL???-9?[?E}{??&[? ??N(??A??1?????? ]{?Xs? g???G?????l??0?? +?????]????,u/?????_?????QY)?{5??5Q??n#????????H5k?x ??L?Q1 ???qE0???I"???? ~8F9"????UP??V?e=????I??D^4?^,??YZg??S[g??9f3????8T? ??=|v???XW??????????;??? ??????272?????????l-=??w???fJ?-?J?;?7?F????[?????_?l???['Y?-9????wCA???Fb?C??\?M?? ?0???r????????`??gOp.??????`,?????!b-h??x(1W??)??q????5???U?S?je at Q?dXUy????4???jD??(?????{j"s??J?v?f??yl???`8,?,/x?Q#?h^??y???,3????% ?7F ??|???R_?????I?XG??w w??-t5???zb?K?\?]w????J!?+t??D?9&???K?)6??????h ???bL?????4??y' +'??$?3?^??t??I&DHj????????U?Tf?z?? 7?x?C.i$Qd?????q?{?{????s???+?[?nm#??16)??? +???S{???%dj???n2HT?K??%Ovp?{&?B????~?W?F???m~4D.??Qk?5??Y??? +?W ?h??Lc?HO???h???F?? ?R9???\???*v?? 4??yX?V?]O9 ???u;=?h ???6? +???0.???9?)?OC?>?k??AK35????%???j??~???*(?X???])????P;??w91??H???????6.??????C??v?g?Nm????;???????[??d??%?#4q! +??&???v?R>m=,??$Q?+?&i9H0? SU?{???<?)? +c|???L7???#???oE`??XL?y?4???v?`??1sFV?{R9???G? +\/???TV?R??8????????Z??oP?&80??J??????{\??????5??????5`-?1???????[ ??@X?{??g,?A???Q:??B??A?:*??H'???w?1???[?7??? +????&?%?H???kgr?,??? ?V?2??^(?\?????.4? ???C??????n?Y??r?h?(4??k??"??o??X?Ws??}?k"?V????OX\h????MsZ???q?9??'????u]x??X??7]?g&??????}??;?b8B?9???W???} ?n0i????.v ???7???? /B? ???D?h~?},,Fp??,c?:]?Jzb?h?E?F??7\pNNf)????Zy*T??0?????H??y?C????|?[o,E?;LD?qA?????????8'-??z?? +A>H| +??i?5$S???4??Q???DJ???l???/, +k??? +?&?>??a?????e? +???i?\???#???U????t?s'2Z_?? +Q??I|??_???????qA\2?N?#'?On???U?(z?h;\??p?????v??G?6???? +???gS?T8a/?O?n?}????&?????nN?L????#fM????^?\`?39$?$5?+??? 8JB@*????$?;?4??"??Y?7?h{A?B?,?l??I?1??%??$??)?y??B????? ?KN???????wK?????????:??o92? q%o??O1R???s??V???3P????????r?PJ=)??????2???A^?? +y`}?]K,???}??&?k?i???? #??:]???)w?/?]????? ?\??????^9l??I??dp????F) ??f[g???Y???_?P??? D???s'???UB?l??`E?????/U.??p?rB??$???????;He?m?????? + +,? +?+:??s~????Zo!9?`?D~fb??b?xx>f;???2??w/p>~?B?LR_?h?R/?????????rQ???7V"???????Yt(???????I????%??^o??cF??Z?P? +j +?]a?X??=??? ???????E?q?=g??0 ??Ui ??.?????e??*??B?J +?1*?H??h??KM??????t?]?L??G???~?.?rq} ?'????p +???)???6????????????>?A?J????o???? +??zM?*?_?wf????u ?zn?????????|_z?s9???s ?G9?4"??)?dk?????EO%{???6?sH??.l*?'?Q??E{_???x??????aW??gcVc??O?????5 UynM?a??z????*?uU+???5Q?s 7#?? j?? ????N?5a?????P?i????????bh???@@? ?? +f?vcm ])???9???}??@?S????'??H??X7?.Wo??1???[Q?,w?2y4?D?n??"??3X??D???M???&???x?y?5?c????? ?(?E????FM7???????mY=P?? ????#x07?|z?9"?U?}??f4[????/?g???????j??/? ???J5?? +~?u)!?2??E???Ae??????@?j????x??`8O??i?j?f??? ??d=?e$??d??3r????o????f?g?E*? 8 +G?????_?8?`???bwKr?="1?|???Y^w?-??%??????????Vv??e??g+?e?:??c:?G??????? ?-???/v?{????0IZ/?fQ?V?????cL???~u?? ??q??f??5?????????g?G??~kd?? ???&??W?U?_?-j[?Rc/??of????:C????|u??^W?? +t??N(T??\z_????N??}?!??ky?7l??? +?Q?E?D#????????M????}?KU???:Y?J?<[F?L??P??^0]??_`?(Mtz`?J?$??????=2"?r??????[u??}????R.????z?2???????????????????v??LM?p?\???|t?a??eXN?O??*w?W|?:??7??E>'?[???>????AVOl?Cq?w???????l'?????*IQ????B2??w???j?XB??]?fi?.????"|NDZj??|???K?? L?-9??h???f?? q?Fh?R&????`4\c??~???s??lf????E?!??i???N+?? s?`/???? ???O??x??.???e@?~?`e'??????7?GDd?O??cYup/{qCl?3R1??>8(?#.?Y???????.g$u(??Qt$???Z???s?$.??Is?t?xp???? ??Wr??+?G\??'????p?1,??????`???o=?2 "??o???8?{???:?fT??j?]0??????@;?} +??"f??:$w;??? H0??>\ +???????S???N?{Q]???~??+aX????p?#?L2I?.??P??I??Xk??-????,?mf}HWS?8?N7T???5????%?8?2k????Eo????Nk?jrA???a2???r?j? +?kM ????%8w???e??? ?????@??? 8????l????????R/??RWg????}7{?? ?P\?6?\?g?M?I%????w??G??????>???$?K??? ???i?~?,W????_?r?^W/n??2U?IJ?'r5??Wpz "v??xx????u?Y?4?I??PO??LQB??????`p~kxP??%WO\e"???j$A ??J??6??UD???v?W???I?j?|??iQ?BY?^sK??????N??????1? +M???????????K^1Q???75???.6??M???????X?o}Pt??????T????N@%u????.'n????QIU??????O?~f?_=}!??p???;????R??u(l??R??y??? u??o??(k?W?'??(I??%*2,_?-zI?:bz?x??Y?s#?9F??????GP?7U8R??G?0????9?&"?;??_??c^?x2?%???Id&,?L*0?????9????^?v???7???lv6?*??`93???[??!?????pk???Cqcr???F??YBJV??????O???? +??????????C?endstream +endobj +231 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 120 +/Widths 607 0 R +/BaseFont /SEIUYP+NimbusRomNo9L-ReguItal +/FontDescriptor 229 0 R +>> endobj +229 0 obj << +/Ascent 669 +/CapHeight 669 +/Descent -193 +/FontName /SEIUYP+NimbusRomNo9L-ReguItal +/ItalicAngle -15.5 +/StemV 78 +/XHeight 441 +/FontBBox [-169 -270 1010 924] +/Flags 4 +/CharSet (/fi/hyphen/a/b/c/e/f/g/h/i/k/l/m/n/o/p/r/s/t/u/x) +/FontFile 230 0 R +>> endobj +607 0 obj +[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 444 0 444 278 500 500 278 0 444 278 722 500 500 500 0 389 389 278 500 0 0 444 ] +endobj +227 0 obj << +/Length1 761 +/Length2 1025 +/Length3 532 +/Length 1574 +/Filter /FlateDecode +>> +stream +x??RiTW?S +??P%.?!F?H6?P??D#DQ?EA3/0&?????h???*??TQYTZ??(Z??7???????VPk??)?l?t??w???w???c9?G?KPb?8????? X.??y???x +????d??b????4?<?[,? ?,LhSI,1?????7?h ?)?* jh???T*H?j0??#????L?(???SP`L?p?G? W??M?i??R ?L???2????:?P??N'?i???o??K.????M}?S? +?N}? 4ZI 'PH?}????89D1??oUF!jL!????=9qd?F|??x7?_?????5??????h+??v???r?v_?}?w!??z??kW_???Zz??????????pX???????[?E???ax\n???ff??F??OrD????????c???g???5:??????????????GB?R/???7?6!?Ls???*+ -Y?I},?U*?x???=?????G?6r3????c"?$k????????/ +8dl at M]=N?-{? )?????q?6???????ii??k????g????,"?6d?1???gMStv?!Ug???{?97N??D??;?u.~1{???1???3p???^i??c??[7w???BM?# uliB]?N&??q?S'?T??X-?X;_?/2Fq?[?x9Sa??b?}#p? |???n?[?u?N?\???r??????????????????Nd?????.??n*?X;?D??????mw??u&;?Y??A??????3???=?4?7???> endobj +226 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /ILEVCY+CMMI10 +/ItalicAngle -14.04 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/arrowhookright) +/FontFile 227 0 R +>> endobj +609 0 obj +[278 ] +endobj +608 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 45/arrowhookright 46/.notdef] +>> endobj +224 0 obj << +/Length1 753 +/Length2 637 +/Length3 532 +/Length 1177 +/Filter /FlateDecode +>> +stream +x??R{PTU.? ??+ z?!T??]\?G???B?k#1?r??????x? ??kP?2J"|?pJ?B?X?gE?0? ???C]P? ?????????????????*????aM?|T??R?T B<= ?X???`, ??? +dz +@%@$ +?$R?(?d#CjX?N?~?$2dH??c????1-P?8 Y???Z5???` +dR!!@P$??x?!)D8?(?R?@?p??'??R!????8??g??)?P??h?,?9?/L-?k?a?nN~>??pLGj???.Y?B(i2?B?v????^? +a1-??(?>?Q ??<?? ?????????}H ?p??*#??(C???<????1??|?>????v?"???x????N$?b?/?3"??* ???"?@?X(?h?k\4?@M3???????????P??A??w??i?????}9m?R?$?D\?0?b?? ???ZMr)Bh?8??C????/?W???t?9;??L?g???7??e? ?L??,r??=3z?ZS??K?Z? +?????N8??1??z????w??????9?? +x???n???'?*J#/???????_?n?kl?Sp?&?????????Gn-?84q_?>?????????????#\Y?r5?S?PvQa??)???t?Rv.m??y??>???-???_????cXZ?1I??mZ?endstream +endobj +225 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 610 0 R +/FirstChar 32 +/LastChar 32 +/Widths 611 0 R +/BaseFont /MPWXML+CMSY10 +/FontDescriptor 223 0 R +>> endobj +223 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /MPWXML+CMSY10 +/ItalicAngle -14.035 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/arrowleft) +/FontFile 224 0 R +>> endobj +611 0 obj +[1000 ] +endobj +610 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 32/arrowleft 33/.notdef] +>> endobj +191 0 obj << +/Length1 1612 +/Length2 17846 +/Length3 532 +/Length 18762 +/Filter /FlateDecode +>> +stream +x???c????%?v?Qi??m??i??m[??m??J???????_?s??????c<+0cF?Xk?*(? +????l?i???,l?\?d?leh?f.??0????Cg ;[Cg?:??@`L??D???? CJ lg??haf?L@???NIMM?_?B?) I?????Y??m??G2xF?O???D?Q????L?`? ?|??? ??O3?t????I?ld??#?-??S?W?M +?[?|????bWY?[+?)?h?K5?p????????9??<'?6.e?iI????o???B?$O??.???yK??Y3[?a??????HP?????q???G??u??6IB?;?c??6?????2??V?E??????v?vs???Q_?$?p?xbxt????0?????L?[??????P?!t"???"??5=Fe????F?0}'Y???g +??X??T???????u???p??8?h???7?F[V?????E"??ap?w? ??xPOx3???L??1??????.?X?pb? ?FE~?Qs??+?L??FN?/??O?2??}#9^$?|S?p?>lM%T Y???????MR?p?Th??nCvF0??????y )PrP#???????^nY?fk7"????f?Z??0??8??~Y&???|?huK??"9N?tY? +??e??-2#????kLg???a-6g?X??m???^???A0MTC??F???Z?Y??E}M?????i?????N??3??R !?N>???m?bS??g?.P?+ _?#S?&?m??-a?yh?q;!l?%n?????? 9???[C?^???????????????????(?{b????-m?K&Gu?u???? ?? ??? 'C??_e?4??A"<*??L?n7?("??????????9???????v0f?*b_l???HV??c???v?Y]?????;??????4?9[j?b??v?A?f?l?{[P1?A??@L?*G?t?]jpANw??k??e6 +?????`\f??????2j?-?;??C??? +??iC????jd????SG????uh'!???-?????W??? 9?5r?k??LN???+??I???!?X?k?y?b?+..????n??\?O???,?v?#H?7.@ ??C?????????A?/gx{T?}e? +W7 c?Dx??,\{i?N?&??Yw?4+w?U?(?j?? ? ?F??zcL???o?`2]_V7?F??2?/?g<y?@+'PB?%|A?"?W???)!?~DtY?i???y/?????K????7??q??U???h?a?u +f:G +???L???q? +?q???h?<???Jo???Y???n?A? +? e???<&?d?- ?????S?sW>>B@?3K?@ ?#????k??@qn +??HXr|W???"?????4u??7N7>????? +(_??g???? +???|>s>?h?h????T??@??lWr???B?pl???????&???kc?>?)?????? +?U?g??)??72?]{m7 at A????? +^???t???CL0'?o?H[d??:???U??F-??F???? ? +??????45?<???T?m???u??U?h8???C???Cg=?D????x@???6?????l?!?A"uv?H???????G? _Z?8????=?>~?y???|?K????? ?N?2>,S??ot1???M?KU\,Te\??????????m?^[?Wzg???| +???'.???*c????????Ho-??^ ? ??,D??D???D?1 +Qc9&??Pi??n,??u1?Bk?[vh???*??@? ?"?O?:I??xl>w???+?X??????Q?_h?#?,0?%]9?????P?,+~o??ZF?p?????S?"???( +n???Pv`!??*???v?? lO??9?]?}D???v?q???}-??(???O??q{-?894?wATq?K \?4?t?Fw?o0???G?S?wnB???}Q??4;k? +h x?A??i?`??\???fwdr?38?b?{d?we??:? +?N??n??????=?N?A??x?/9l&?D:?B? d???W???-V?#GY????h|???S{??x?fo??|?d???j??g?7?8F??L??w\<4? ES.uM_????vJ?????a?????[4???????=??>???]tv???? ??A)GCm)?;&?????1?:?P?i?'Uh??69zh???t?Je????sdU-???????"ob????V{]@6?.?L??????QQ2???[=_???s?i7??(?#p?i???Mk??U?????(?'???PR???x??.??x6W??i?T??=n?22?0l???R??????????mud??P?+?c???nL??tdq2:??t?~R|??zK?8t????q????*B?1c?"?Z??j?E?????? +?U????? +?>??r???????B7?i?XU4Os +?'?[??t ???X??? Z?(???h?????f&??P2?6??????+??i????Sn0??$?????nd1 i???H????w?f??????i??Na?s?????4???>???? ~&???a?????? +??"@??7(?t???[&o??^*??4J?uG?l???gl?4??? ???T ^H?"?:??????? ??????<(|?& ???! _|?!,m?=???????r???`B?< ??????%?B???pF?Y??'????????+??3&?????? xb?U?[/GL?B???? ??s????P?e??r?r??? +??:?k8Zs?? ??G?;l?)?)`??????$????????!+?H??_m? ?Z????5l?J?K??z.l=i?~_?W,"kjz??6~???a???r????W???%??? ???`~?)[?/?N+?N/?d???l?Z(?????????L????^I`?qi?4??G??l`:(?E????0_?Z?? 6g????Jc}?8??Z???N??}???"???N???*??'J??I?S?Xx6?'?`??%??5??W????W?????*?/?{4?"??-??[??R??}i?$`?/U?`???5P?5? ?\???k???j2FG?\????????xs??Lfwf? ?A ?,n???O. ??@1??M{6Ay?H?3^???j? +?z?`1?P??){??6??bwB ?D ?^?Z/???C?? +?N?f?K,ux?X7r??wBB ????bs?[??3+???? ???B=???+??o??f1]?9??? +J?h?9??(M??v?fM?????i????+?#fDUs?2??R? +t?j??o???[???(]f?'?????J2?????m2???kHB??RO?:)Hd?{?y?s??0?"?#{?_f??3Q' a;?C?A?U?<`? ??iWX'a??? +?"5??!??F??~W?R?N*?I?0p?{?????,???v?x\?J??\????mD{?????81???5 ??5j*i???????w8??]?:8??1? ?=???lf??????????????*?????(ic ????? +?B?S?w?????tv@??[cNU?1?{B?,????T??r????t????_? +???C[)??B8?Z +_J1??z(??p?g"??QCA????k?^R?;?eQ+?_^myxjA|???,?JG[?Dqq??j0%!?N???zBs?t?9???WpOn??sve3??I?n???@'???A\?%????e??U?#?5%????;\'m?0`???f?9? ?@D????qe1????4D|]?t?C2?????/?f?????{???Ty?????f????(??J???????!???)v|?,???/??9??s?C?0ko1r?j~UMu? +?e?(/V?i?Y??[*[?m?)?T?d+?????$~f*a???????2??M?!)?t+W????&??/?{jK')vZ?eLD?j??T?erY|?^w??b?????A??G?V>?4?i??]+?_?? +/??MZU?FE~ ?n????u]???@?R?n?b?Aia?P?????C?E????9???{*??{?(??G?1^??\?^????B? +? ??l +??'<+??JS?l?` +QT?4\r??s????p??y??l4?1???j?}(T ?,E3Zs?&????.?%B?????&PYa??w?????!??T?????o??.:?3???\?O??o^??c?;?$????,???-?-*????1>??^?M?6X_"K???q??????G3?N???S?O?L?*%?Y??C)A8u??2??2??r??#B?k????-).?????53??_T???}H?????J?7?)???}? ?~??????hKu"V?gXA??^A???S???_?P????X??9??!)??J2??r?}??N?????????mO#???????? ???U&?B???cX ??k?&?+????y*n8???em?~??????}|KT???cO?s??Y$?'?? 3&K??2_S?K.h%?Q??L$???D?EP?????}]?j +S? ??eu)???&???w???????MEp?b??}|??CXh0?9??;?"t ?3g????^?2HpZ_??O???6e?=\???? ?B$f????u?????L??8'??-kZQ???q???t???:???&?? +? ??..4[??6???p?!uf??N??rK??V???????#x?.?%$$?8%F?m{GT??Z? ?: +:u?%Xz7X^ +??????5?????q?a??5??????/k#???.?~???$t[?}$B????Bx????{?1?)?wc??/zf? ???np{?;Q??Y??^??-?e}n?p? +OK%R??I??????@G?Q?'??*w??!4???`?t|?c&?????q???J?P?Ia0x???2o?8????+???J*W,S?????@????Z??V???T????]??u???HE????2????o?m?"M?L??D?t?T??l?????K?}L5 )??K???B?$C????PS =?Y5SdQa^lg3???????? +????G??g?0vE???U?%? $ 8?M=FZ-6x???4?"g????)?EK?l%R?4??h?????HM?M?j??uD{=???"*1`?,?????:?T?s/?0 ??Bn???GH?\??Xw o-?????U +L?sI??E?n:?f??3???54a?[???C??n?}!f??k?3??9??A?]??????S?7-?? ?qb??b??7?? ?????I?{7??N?N? p????lV?\IB2qf7AG?/y![M?F=Fr???EkN6??L??k Dq???RU??lZ?,?M??D ????x???M??? +K?? +k ????X???] k??ExB??=SB];-??<+@?JA6,?2??{ +???d????7?'??7????/???k?P?uD??u???~%]???`K????6?VFo????9G???z~^??I{{?)????m?=` ?jC _+v?}??:???????U?/?????[??y?????rn???.I?=G&????????g?+?????&Q???????????n&'??n?O?M????T??%xx???X???B??$W???-????o?????zok?B??8???f?-bD???]X??j??r?????-?N??/???;M??.s?k~8?b{?o.??;?:??I???p?????y?G??`C6h?1 "?.?]??nX?#?BL/??J;??HG?w?7??Q_??? +?) ?le=?h?E}9? +o-k???????Q?l?K^???^ ???????"?\??? +????[??e???#??1??r????????=??Ft/%z? ?~H ???Z??:l?P????h?QV??nI?C?g????? ?]?9N??Eo?-? +?$????V??!??$?v????6?yq?z.?~??F??i???]???o?*?v2??PI?? + ???@F??6d??????8F`:@(??????T?Z? ?MJ1Wq????u???????L??@?K??n?2j:?B?????XAU??"x?N?{????v? 2??b?72M???e?+??o ????7D??????N???7e?r??x??hx????8???y??4u ?Bo[???EL28??l????(?`???#?????xZ?R??? ???????)???-[?t??@l?A9???*?????l?b?i??f??"6N??????E?GX?>@?)?E??'?????????a2?@? n5??G?;??????????B?a??#3?;w@??^?w{^??%?Q\9iQ!=G?(??ab????c2"A???J??lB?????)??R??s?????'?[??;?B??_????N|?z3P +??z?A??{m?L:}???7??7??S?S???????I7??4?sl`??????u??\R????I?u0?S?%?}?_??z?I??Jm~??t???J?L?.3?? >BY?N,?g???0'KG??8??o}o??ca???*??????6?D?????\??{??f???C??1~'"?o? ???*??jM.J +??':E:?????H???_???,E1?jO?Sw?uJiGI???5v?t???\'1???/? ?_^??kG??X,u??~???????????[???f:?? ?? ??Yc?c ?RszMu??????,,???]?b?rG"?p??Cwz??%? ?*?99 ??R?1?uH_??9???? ??????D?oC?????>? ?<?x?4????&???7??.5N?V??vG??????I?d???2^?E??h???`?? ????FZ?+??y?&{p-????????J?'1+Ky??,:??mc:?;L???p?7??FG????????????b??$h???]?k? ??R?0?s??!??G?>DU? ???s?????:GXJ????=??I,?? ?O??*??L??n???~???N?!y?|???8??? +????????F8x??b?TSl?t??;???????(h)!????*5Bd?*?w?Y?rF?@???yV????P??Q?}????A?????? b?<&_??v ?8H?)u?vb????wWT5Pz?}?k??H???? +?=:??e?n=????>??Jd?Cf +?k???zoS???nG.?!jP0a?#.?S?%?D-W?j8?~e???7?=hpfx_??c??O?L?1??_$??sA???g???S?5(???1wj??{C?.???U?}?GE+*YN????8G??OF?d??Di?{??~R?&?B%????R??? ???Q??^???5K1?b???8?????do?@?!??????M????? cD??LO8????6G??,??????eX?@:??c? ??Gn?C??????h??? 1@???7?????6Z?L?????U ?z+F+??"?? ?V?C4 ?o???{??/????]4:???k}SjT????????? h:6???\?o???Eq?\??/E?N?H??????( ?r1t7Z8????.ULt!9 ?B?{F?? (AM!p?Q5??C?On??:??Ka??_i???hA??d?B??hAC2?/??}b -Y?S??q??O?f???,? +&?Y?c????????M?C?|'W W?( q~O??3'??Ho?????G?5A??r???A$????hC?D?O???/?p)g&???W?z|???\?<'?~? ?? Vy?e?-?|?/?yG(rH7YQ#A???A??{?ar?4?_80l?A??? )???%?c??Yh?(r???\W?.?t? O?H?G????U??&M???????~P?????l?#??sp?????9f?=b?rP??cL8hh?`??b +x?3C???Bkf?x%??????#??c? ??e4??*??&??/???6??9???????0g??/AjlA??Q?????+?X?_??@??l??+n?#Q???a?~??????g??v|?a??A?7%??}+?l?@?e!,???)@{ 3VG???h???0?9m? +??????W???I?? +w_}?? ? ?? +???"?n\?N?Sc??????;Tk?&)??b????sS????? ????>Q??-??'m?+? + +?????k??$1??lI???w?EhA'8s?O? ?? +??/I(???'_????N??A??'?L???:7?w?,p*?.]~?????r9?$g??i?5?@???L??(?G?6?eT??????A?eI? n??k??7yF?_?&?rQ???q!?f?7L?7 +?QL??iv??x=?*?&`?????Q??????PLM?zhZ?s??$:?F???????[?p5.??8&??"v????1#?????s?5??wVs???&?%???i_!?X??wK?????????`?o?Bz??????"??e????p??G@?=?TiS?O??Q*?z +f,B`??uu*???2T1???W?zX>??%5???? +K?Q?????W?IBK?vY<L???%?Dz{????L?p??????b??=_????&2%??>?$9P$? d???????Z|??0%?D???????$???]???i3w???hi???????(r???????|?a?$??>???]?%5??< ??U?????T????=???d?I?%7V*}.??N?4?d??k???kf[K??Zu?/ qI???&4??u??d&V??????HV??Q????7?-#Kt"??n????"* :?|????4??-T?????+??`i$?7????^83*G???: ??????6?W?l +??ftd?z"?sexX~=|:`C?;;???$????(v??sP#???k?BI?? ?????????R?w?K????2?4??I?E??W?'"??"???? ?>???c?V???p?;?PI???D?%:?YDiYP+?/H??s:?%@(?L6??'??l???h3? +&K??"? ??|?<2???j?+??{? '?O|?v????v??????K?$^vie??Apg?????????I?>????????????? B.;m?`??:?x?:?? +K????!???????g ??????G sc??????a?/ +???j??%????%;{????^3]?A?????-??R??j?e??'x0?72*,?72??_?P?endstream +endobj +192 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 33 +/LastChar 126 +/Widths 612 0 R +/BaseFont /QTEVNQ+NimbusMonL-Regu +/FontDescriptor 190 0 R +>> endobj +190 0 obj << +/Ascent 625 +/CapHeight 557 +/Descent -147 +/FontName /QTEVNQ+NimbusMonL-Regu +/ItalicAngle 0 +/StemV 41 +/XHeight 426 +/FontBBox [-12 -237 650 811] +/Flags 4 +/CharSet (/exclam/quotedbl/numbersign/dollar/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/R/S/T/U/V/X/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/braceright/asciitilde) +/FontFile 191 0 R +>> endobj +612 0 obj +[600 600 600 600 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 0 600 600 600 600 600 0 600 0 0 600 600 600 0 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 ] +endobj +147 0 obj << +/Length1 1626 +/Length2 14351 +/Length3 532 +/Length 15230 +/Filter /FlateDecode +>> +stream +x??veT]??-????????Cpv????KpH?`?%$???????}??o????y???xg?3?^U?f??Yk?MM???,n?hn)?vcfga????]5T????--@?w;75??????,e?f)???HYv~~~$j????? ??? +@???K????O?_[????y?tY?4????N?`?w???@MKK???%? +do ?TU??W????hd-??.f?5ws{?Z?]-?V?.?,@G????\Y???]fW'K ?=?? h???? ?d??ru}?\?.f`???9@`????_??V?rrq|????{Sstus?????Y??d???????????w7???}??#?????????{??@`W?????_??- W'{3????`N.??i??????d?p??6s???tu}?y???;?????7sr???;???]????jio??????????Fb?kV??V?v??-?????a??w?????wf?`{o???????{J????,?s"?H??"?????=q?U??t?????_?e???U???w ???1????????? 1s?{????u?????J8?[??O????%?`?wY?X??a????,-?@n@????{???k?-,]?A`?w]?n)?????_|Z6 ??/????[?+?w??&?*????)??_\?oT{7-o?wn?V????,????p??2????9?????;!~6??"??@??\+??????u???]?????2?i0??????t3[?O??r?]\?????W????g????????(f??9???o`T????z ???A?kaP?cg`f???sM8K???k?????????P?=mg??Y??%}w!?*M/?n?q)j??n?????:?G6???Qu +??g8??6N??;? J?? ?['?`F}"n;F#Vm??1M???-m???@?%l?1cn""?? *Ml?s.??G? +??H?*4lO +????#?\???t?????C?D????A?oR???=????|+3???h?M?o???$??'?Y?m???6??D??????4??????&J???p???$?>??,??`)??g+?????f??[!T?R???O?*?L???3[??2?O??I?hM at Ih?X5??/5?t%?"??????c!? mb?=?1I8K? +k.\L?5?Tx???6??????C???1%?z???^?(?]iu??+\?_RR????G?J???v|?*q?`?JOm?I?L??{T????0????-e?, ???z?Z$3cS????}"?=8f\V???????6 Mp???DG????a$um@[?????z?????eI? +E*}?Wa?(?!????2R??u?[W?@?$E?K.?1`?~ ?,Eg? 5\???$s???1# ?Xc??H?\Z???????H??M?T?.?)??1gc?m??B`???N?a(?2|??K??&e\TM;PC???? +???????>?.d???_a<6?W[???????T??=?|. +?C???=,???U?z??G?YR9e?\9y???[?0??y?O??V`?d>Y??"?$?8?F??b??,??? I?RG??x????????`???~A?S???ck=????? +?!>Y??Hk????h?st?F+%????2\E>???^?Wb3M???S?%???????c????????6 +?n????C?d?oT?C?j?K????n???0o????a?????Jmkw?!??????Ko?2|???@p?=?n?N???/?"?V7?w?d??v??P?????x???UaG????I?UP??H????u?y?????!?gE??a??q?p up?V???3?? ???R8A??l?Q?h??C??4?Sr??B???V+[?????6??_??4G?d?????^????[??H????c???????Y??8?30g?!?ws??C,e?q?X???p?N??X ?? ?!???5Nj??M????$?=?0 +??????\?/????4dw????????. 'I???????zC?$?????>3.0??0??_???c??0U1-P??y?s???????*?? +?u'd?*:D2??R?C????%g(???>???3L3?H??yi?>`i?,B?U?0Q???mn???O3????i??"'^k? +??I>??? +?T???R+?a?| .?? >uYK??5v????jZ??S??$]???+rEc?)??????Q??h????d?lQ3H_6,? +/??Q???ob?0ZmC?????;9?T ???s??VSoE?d?y&??+?/r?m;?*??sL???&??.?4o-?R7ex?"?0jD?vm??Eg?{j0~?????? ?T?M*:?1>??Z?y ?}[?;??O)C?????V"F?MSm??pl??h?j(b????????z???I at h????Do? +? .?????o6sB???y?\? +??pm?IO??I?????I\??????7=~?????? E?8>?5????:??? +???=$t?l??k}?~?j?X?????S???[D?L?F?u?IE??O(t?????kry.&???5? ?/????%*?Q???'??h??(u???#;f?g#????[?:?45?"]?1zb??)1?3???_?KhH?I}????i??o%?-???y???-??`kG?~?????p~6?6#V??Q?sL?? +?M???J?Oy?p?X?U+d?s???$?@?T?'??y?????O? ????=/???r?:4?????X?OI+'wfL?i?Pu??|i?????V?h??h?G%????????m?{??%??[??qc?4g?Iq +?W?t?k +???????V??0,X?l!W?????(????p?y????)|?d?7? ??K??&;???b;?&?Sq?{?q?H2TmO?f?HLdL~~? $??h?J?Y?)S?Q??FB?P??P??Xx@&@??ms????S??[??rG3??Y??I??Fe*??B+L\?????]????>F??Jv??m??`X???n????}AM?^?+D????^??oS??pQ??b?????6p??g'????5s?u3?V?:?/?????Q?k1?Je?N?X=?}???s=???9?xlg\?????????H?~??P?Q???hr?/?B[????]'?9z?????U*Bs???ifiD?bby?1??+????m??1????Y?3I?w???x?%8FJi2c???L??????I??&.:?{?????o??8?ue{???????j????`$??25?????}#?4*????????`?Z??a?0{???>?????Z@D?Q?L +??X????4??? ???f1?/FOe{???M?~?????eY????~8 Esr*? +?@??'??4?"??]OA?s???]??,?w;?w???%?N|TM?I_??d?oE??n?'rZf4dzL? ???8???Hi??????U?kq7?S[?????U?0????:?/??`?$ ???h?f??+!S???J??*k=???T?"8?????q??b????K?? +?i???q>?? +????? ??^WW????L????]?????)????nX?B.n?G????_t?Z?X?????fX? $u?hu:F?c? P?z8.),????`?=m?~??Y??"M??? ?L?*?Q9?X??o?1? +?\??J?i?fdB???????????tb?>?U??(0D???M??a??h$_?|IM?@g?)5)?Avj??'?- +u??L+W??~b???A?t????+???%?H?J=??=?;yYp?g?U??'???????f ?4??:?=V]??!?%??T<_???????!+s???(?kb?=/A???????O?Z|P?}]????D ?YB?=y3?O??WN Sj?pe??????y?P???????`B|???AWZ?????????????\X?EQ? +?\?????A?P?(??D1?d:AFu1O?????j?R(???% +rQR??F???$l?Gh2???a8k?P??T ?GHS?j?.*.-@=?)??n%?9?S|9L?~?????A8e?]?wx?w?$?h?G??7Pu???$????v???????R?Gcp????j??G???^"S]???j:??kkTfH?t??????j?w??(42z? +?l???????\G?7EM??{< +??I??N??3?'[{ ????!=9?Df< )?/????)L??d$??????_? ??9L +??L?u???7?H?a,?L???????g?QH?3??????=J?^?8%?jL`3???S}????q'???^?g?,G????e@?'rAA$?@?w???D;??7:???)5????%?v.??+>?-X????1J???Y????^????z3R5G???U?&???e;? ??P??L?"?)???l?j#?? ?t????????M??1`a?W?=?????gO5?hVS\??z?/???? ?N?????1#n? +N?W?;??S?2 4???????a ??i?*F????????yI??????kk?P???d???????x??z}??X??C?t)???&??KG?m?0???7???[(*.@?~z??9)c?N?!??L??!?????7o? /6J?7?tM?A? ?JN?m???[[?n????x?>bj??z??W??]3?,?8?I??4>??a??? O????.~T?gG??v? 0l?? +?,c?5qr? ?1??????i?b???J??M?{?w???vG?Lo|S???~v??8?3??-?~?Gd???????M???????N??@?x?Z?l?L]??????S-uZy&?a????Fp?X?pVS_??[S???T?????T?????????lA?d? +A}??s+j? jB}?m???*Ij[L+J?>b?,m?l??GHc????9? +"???????x_? \?h?G????&?{?*?%zC?G?6????A??&??HnF?a??|?Y?:+y???o-????C?M???(i3Zr>?V???tg?*?/??Z#?[?XNx?#Uv?????)?Z?? ???$???/??i?5#t?+?[??'Q????G?[I?E??z??kp?|?oM\^?y<2[?}??|$? ??I??c??+??0-W??P? ?8~m'kt-n?? `?? +O????E?d??????????????u??%l???????5D1????g?&U|a~?P?ure!`_?P?V? +"?;???????f????????'????? ?!,????X?^l\I??????$??????????@A2_3+???D??L@?d??~?H?"?]f@? +u?H??????s??????C????6/? zf?????s?k??44?sVL?b5????? ???? ?a????#?0L?.a?_jF???3?? +^ +m6v!j??@u???????t?Lo??5???K??,?#??? +???z?Y????>??7? ?^?j??? y?Td>Z?5 ?8h?~???O????i?tT?z?3z+???^u??(3 +?????[9"??? +lrV???????<??[?????_?h???((?K7Z-m%?X?_?N~???"jya??Z???8???????? :?? ????`@^??r?-?6)|z??>??NZT??+??;A???F??N?vu??VLg? \p????@$??[??3G!-??f???(!>????e ??#?Oy??|??rh?^QT????Z?E?Ds??j?t?hx???????????gc????NUz?d???{Q?5?e?D?u?<_8s???6????fZB,v???R b??/ ?v?%??? ??0?}?c?C?v??s???1PZ?????R?s~???FY"?S?]???r at SRRT????o?,(?|v???W_???G"U???f?B??? ?X^ ?0????8]????F4GW??V?M?1??uG.???v??qE??6?f|??2S?7?? ?; ???GM?4???I?D?=? ?5 ?~?_??r?~?(??e??]q?}'m?F?jm?B?'?? +??-?????_?Cda?Zl????d?? 6|?LU?m"?E?Y=??W ??0w8F?m?hM^?{I???=???b?08???? ?'?;?z??W9??vP????cY????Sh???zjLz??W????n*A??W.?? +???Ov?,5M?jdGiU??b???F?'7?{>??"???.b*E}2??=?????'y MA??d? ?t?=?z?E??d^?+ ?? ???P?g????????)?xl???7q6x-?H?s???szy?& I$??9????%????????W>??H???N?}???? ????+Q2???????,?Mi?z0?Y?4??;??;d???]??uH}?????G?'???" ????yt*!????x???Iw??q&??WZ{????I????HA?>?V?~8H?s?!^((+7s?????????r]??^??q?3?VJt????l??????? +ho????80???Gm?~(?X?&+??r?Oh???<??.1??????????`0iIi?uSh????F??????J??R???????8??M?,g??r??????????)?B???Tm?>E,}?Ex?&?Hq??`???j9?%?-m!u??E?W?? + c?? +>?Z?d??D????g??pn7L8??e)????????n??? ?c???N~!p?zN?v??S?(?l??W??? n??p?=(??w#??????-4P?j??? DT?D???????H?S?????{?)DfP#K???,z_^???Z??@?T???a?K?/??'???????????@???9F>=Q??????W???4????9?sq(?t?P??~?S? +?? +?Db]?+3?"?hL???"?-c>BJ^^GK?????????5?7?S&?w??N?#M??????6?Q?9????@????? +??$)?nt???w?C???}?fU??u;??q ?l???n?P~?????s?w_4??W??= +?=?p??0p???*:61??=KNR?Y@???`Kq?_??;Wi_i??r?`?4]n?C??/????ju???????I? ?D????#>C?b??v9?z?sX_1??T??i?r?????z? +t?Q????e?dc?+.pKb?????Fm!????l??}???!??? M9?????U{??7?%???{??3`??????&?W??u?Kf$??Y?'N????7?x?????s&?~?*r??T??9 +??????Qs??{61??????????zc>??A?]C?Z??]???p?|>? +???$L?yo?6?(?:L????5?X.40vw?1???v?? +Gj?>T?(?*'b+?T?MJ??$Jv? S?79Kr?????kb? +l??/ +?d??"???A?????????\C?????E?^w?c*8?qp(?H?C?bt????~t??????(???Q???oc?j?p?y???E?@F +v?4?????U??????'?1~??????1p5??J??????mPR??}?S?\?_?????[}LU?%?[[]???fd&9?#?g??*?5?$?+#M?&x???Iz????? R??/??? ???IX??g?~???D?r?e????????X?=G???np???Ki?????w??? ?> !???P?????h?$?2??Dj>w?K??????????5?_?}?tI?((?uNH;`4?????|???????OOP?Z??%?0l??????*?OMSLRJ?e0?h?V?^???X??\??0????`??<{?Y???9F???,?^4?s???p#?????x8?3:f?V?1+? ??????^??????n3R????)9? g? +=?1 [??:???0??xIE??H?l???????????z7? ?M,4?0o??????1d??Rp%?F~??????A????|??k?d????W??XX?*x^?BXa?)??XZ???0??43Z'9=}?Vb????H?????[S??ZV??G?y?zC????X??V?%??02Y??-H??8? 7Ydf?_~?\??aS*?E?L??xk?%??v6 +?j?-j?=????s!?????,?^7ea????????8!e?HP?3??hf????????"?fry???m?? +I"???S??{pakx?? "?R?wv8??^??07???t?%?Et?O???U?(?x?K?~]???? E?m????f3?W????.')?T??E?????Q1??$/<" Fk??\????B??$=Kf?????f?U???? +???bL/?V??>??~?+w???Y?? S?]??lK? +?v ??M??_?`??{~,J????j?? %*J???j????`?c?+v??h??~?8b=P??? +????-??{u?(??????m.s??y??8??????IY?????????@<[ ]{??"?X}??.?:??Kb^9B?????CU*lGs??i}?r?D??\D?%?D???s???? ?a?9?jC?????|?E????1?_??A?????G?qz1???"??9u?{??????`f1???z??F??<.????????yl?????rK.y;?:??U1?"?j?????_?[&??#??7??L?4??Uf? ??p?:?? YV??.??Ss??R?# "??i???????2h?^? ?YZ?x??g3??l 9L/??N?h???????eij?????Ev?v??????9?G???V?o?o+:=??W.?u??" ???6?????? +???????????????????????l?endstream +endobj +148 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 122 +/Widths 613 0 R +/BaseFont /EUPTSE+NimbusRomNo9L-Medi +/FontDescriptor 146 0 R +>> endobj +146 0 obj << +/Ascent 690 +/CapHeight 690 +/Descent -209 +/FontName /EUPTSE+NimbusRomNo9L-Medi +/ItalicAngle 0 +/StemV 140 +/XHeight 461 +/FontBBox [-168 -341 1000 960] +/Flags 4 +/CharSet (/fi/parenleft/parenright/comma/hyphen/period/slash/one/two/three/four/five/six/seven/nine/colon/equal/A/B/C/D/E/F/G/I/J/L/M/N/O/P/S/T/U/X/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/r/s/t/u/v/w/x/y/z) +/FontFile 147 0 R +>> endobj +613 0 obj +[556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 333 0 0 250 333 250 278 0 500 500 500 500 500 500 500 0 500 333 0 0 570 0 0 0 722 667 722 722 667 611 778 0 389 500 0 667 944 722 778 611 0 0 556 667 722 0 0 722 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 556 278 333 556 278 833 556 500 556 0 444 389 333 556 500 722 500 500 444 ] +endobj +138 0 obj << +/Length1 1608 +/Length2 10437 +/Length3 532 +/Length 11293 +/Filter /FlateDecode +>> +stream +x??ueT]??-????9??Kp? 8?A????!?Kpw ?????w?????u??7?c??WU?Y?j?Z??RM?U??( ;?r?qT at v?????`%VI??9????BK+?4uA???N@!?.? +4pq8QhR{wG????A[C????????B?????? +??^?\??{; ?????Q8Y [ @JU?????ANE Mmj??mAf%? 2, ??,f?9????l?XP?)j4?n????r????v (???,M?N?=p?@`3[g????- ?w??F???^?? P'??#?? ??UMZ?_?O?6?=? C????FK?7?xR??l2??/63Z?L'?z???&c??????D????? +?????/F_??wgS7???d????????T?K?cTE=?5Z??S???-???=^NX8i????B???????K??????????~?#????Y?t??h??x5BSA?f?x 3??q???3?P3?U??h@??????F"?=???B???n??0py?????"??d?V??E?? +?0?2???x>f???C?c\a\????g????6??~??T3???q??2U1?r<??P?D? uHzh????$??E?|B????????? H?????#*?b?U.'r?x?%?58???.#~ ??????Dtd!;7???S?;???L?ra?_n?a???????D??.4?[Q7????u7Jg5?K????k!??|l.??K?$4?`???o?COk?Q/? +???????9????A?????W????M?%??u??}s?V{]?=?e????Lb?+~??h??DS?/?)\mJ)@m???Z5??v??q?[Fc?\Y??7?(T????2???h???sQ=???ly]?R,}/??S????z??V +???;]{Ky??`/?$nR?:~N???bu#?????dm???? ??L?E????E?m?%???A??A$?? +??y2??]??vS?k?SC ?????q]???^??#????&!R???Q>1???^?{?jE???J\?cB=D?E??U?m?H}???????So??Im????nu">?g+X???Dy??a?M?????*??;3?_.?????8?)????y???0?s-??nm???{$????j8? ???Y6???~?????????\?????Y????A?D???F?ztA??e ?hM??R?J???:v 7 +1?u?]q???xW??Ej???L??l3?mZ?P??M?V?|???}q{>V????s8?(?{=?????*]2s??????7??+@?$???Gz??r?1???7!??ES?? +????<3 +???yd>E{?;??0?B???Y?4????#?8???` ?O????o?uS?t=r?"?OCi?i??r??I;&U? ??4?b[M?z??'?+?L???V ?X9]/?ID?E???????????????C??l?2?A??z?x?E????uf??n"??b~?S2 ?iylk3?{O????N??6u??ru`??H> ????????t? +69?jA61???{M?*??? ?|???]Z??????yS ??1??`{??4?77?[?)??Zn???F'?K??z3-?p?nL??m???????,E??????N9?n-??c?!?6`aU??~???Ye?Y}???"ge??q?????~( +?7??A?'???[C??\:?????:D??????^Ue?M??\A??rui?~Mir??O?????Y=???M??>??6?JL? ?3?.]?{?b???h??L/?T??P??f???x?,?&????:????@?@???2?3>???bo?!s??\cF?)^??n??@$r??4????????????m??>+?z?*????CoI?*?????U;Y?k? +?+????>?R??I????%?????F? +?h ;B?Dy??/?Q?????????(?]????r%???{?Vnz?????4???n?????????????Z `????tM?????s?:???cx??U|;?v??v#?7+?{??e](??????C?(??vrphW??g????E????QqN?fv?H???7x?6?C%$??$\$?;bAbM?_ z??:????Wt? +??:.b?R???qmG@???,?s????~a???}Zm?!???*?????s??[j|?X.?YN?R? ?O?Z-??dyj??|??D?b??#??k??\????c$??"?Sl?m??Q=?"9?D6sL??????????V9P??K_|?? +}????\?k????F?????s??e?M;?]?3?3H???j??~Q???J??1?t?x??h??~?VPG _?.??????`???????W?@???x?LZu?]?????6? +1??*??Qt???Il?dJl?? ~?6]???1o???7?"?`DM?`?v?:Q???b.0wG???qH?????&?t???7?k?mX].7?????D? ?Q???:2?6??TX??{*VIT/*<^3?j??\{f?csIt0??5O??Q7*P??f??!t?k??=c???VY*????e?&.t+(??Z?M?8?j[??L?????>??#?TNPaIY?#N!??8???A??0??v??}??????8?????5?%?y!??Q[p?i????X|i +u{??z??v?T??!9?E?E,.?E???\??w?Z????ZE??5/?I???i6;?;?S???????D?h? +k?????? ?zM??(?#?G +?????nOL?6? +y?^$?^???>g^??BX????o2???E???x'A|????5l???.?????*????P?$SQ]???E?b].??? uf?2 +?b?????????zs cp??M?L?V?7K??? +e?fcL ?z???u?N?(?7T:J??-\???j?????????~A~;?7?y_?????W??(#]??d3??z~ ???a?ID??%??dQR|cL?J/g?uGtS? ???8?T?4<,? ?n??[:??e?7?+??[?=??k??>.???????_?[??l???o?p???Ik???f???Y??w +?s+.o???ve6{??r?/??z' ??e?Z%y??V?@? ??????d????U???? ? K?=??!?? j??39W?T?b??m??????1?A?????n?&x?2m???&&??|?Q0????/??%??9#r??Pu?a??m&x)??.?Z?Zw???Jwv??]4????????J??W??|?xS>Y?H"??@?8n?#?.7???AH?rW????h`??????p???,?????[x.?'y??????z?d?????k?G?7?R.?O?Y??? +?^?'?????f$??*??F?????RB:-??H?I?w?!?????~??5??????#?P???0.??5J&??;?G???'d?d??;???????:??(??%??d??-t?;???5??d4?yT?)&???gd??O=y????@WM?????????????^p???l??????4S??6tBd???I??,C +U(?VU?? +??@?%U,??S??.E?aV9!gXtm????{9???????Y_@k?0??5UE?X^??a??b?}m#????F?K?5???????L"5r??|???#??H?[C? ????z%9Uf??GW?9?*i???~??%!??hI????I?????D7?t|????Z;F??ol?????;???u +???*???k??Zg"????5?vB??c. +?W^ QH???a>u?K?h?~?VxQi?`C +O (5?2?k???????????????gU?]?????R???s??u?\W6K?}e-?%????? ??L??G??h???5?????=????????1??05?X??w???r??'?DF??ygm??S??|?#??vhB@???? 6??,?Q_???gg?p??h?:M?<_?????F???[??? ??6?S?K=?sH?Me+??]??Fg?????(?@w? ??????)$??x? 5???"???c\??U??(?7????G?!??????}???????!??^*??E????? +????wX?e?????s??P????? +X??&?7?????Z?}?t2 f>??9hV?Y ???r??.*????????????v?B???n??zg\?^??P?(|J>??C"Qv??Z??L????'B??????.4? +O(?#??E???"y????B?^|i????O? +Z????|ppx????-??n?[?;w??.?Q??????7???????Oozd?n????6/??? ?????d|?`?DU?i??5???q?CJO\.b zY???*??1U??,?[GO???M1??????^9???/8????-'yb??x ??a?????MFnQ???G?8?L?w?z +t??????A??????????W???MH? ?Xc????????N??L??Q1??Ads?J????I?Gf/??+??B? ??D???9?M JG?:`???%Q??0????????&?g??]?q?H[XL??????X??Q 16Xxzc??kg?G8?????J???h??[O.?*???.^y??????c7? +_l?|?/V??):?k5????+?????f/`* +p?6?O?%??-i%???????/???@"???????????s?u08??l?e??'??Rb? ?M?Z(?????=???1V +???u???X?Yo?m?????????1?C??-???Q?l2?? +???b?m$F??B +???~#??S??4?????W?Wf ?????}????u*?@?e1??5??\w???.?|HgBUB8??!4%??/??HVa=Y&D?G-???`w???R?t?4We???? ?_EOQ#DQ?g?r?|H}?o?3k?t?'??? ?jSB??'?I?[??E?U?Y?x?KvF??}???????2"?s??@H)?`???^D?A??u?=?~t?.???9Fr????=+??n[??,?R???7??%7???m????*<???4{?.m?}??.?@?/????y +?T|? +???? :? ?????%wR?_??!??0??????Md? +??O?????jv6??G2?vn????E?@e?????m?a?,??xL?K?%EaC???=???;(??????l?j$????k??]? )????d???U??6?@T?Iz0?,~?MRn??1%?????ia??mg?Bd??DEC???-???2???Q??Rq'7??)8?:???^?b???IZ??????F??????T +J??]?rQ???@*B\SZ?L?(?b?FRAS{L???????+?^????0??ITwe?? ?:[??$a+?w??S?8?"?A?G?S?(]???5???? ???F??????z???62??8?l?)????}??hx?m?0?A1?O????$??w']?&??g"m???????? +n???h?L??? ??B?H9???o??G??(??F?{????4?`?4> L ?\??H??&?MG??CNX???|??A ???mXM?fN?Dy???8?I +1E?O?]????i????3???t?fR,d?G?????b?????????a???????7?.>9|?:?y +??S??@;?~=?0?|??S?=?$???x???u3???????????J!.?\ ??=????b?f?D?K??0r???A?]!8??fl???i??&C???x C/z]?????S?>?p=????f?!>-;CQ*????b_P?:?KX?@<2???s! ???2?JT??7??????V??t??&???05Fr??O?????2G??*?q +?hZ"?FO??R??A}???W?8??????Q]D +????C? ?*?SH????? H???M?????Nl?1'?`p??$T????;N?$W,?????a??? f??H??????I??e&km???qZe?#??D??$k???6?\?z?7?BtW?Mp??{~qOw?;?????Q?_FJT?5J?"?????l?4????????`f 4ut???:????^??endstream +endobj +139 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 606 0 R +/FirstChar 2 +/LastChar 121 +/Widths 614 0 R +/BaseFont /DCGXEA+NimbusSanL-Bold +/FontDescriptor 137 0 R +>> endobj +137 0 obj << +/Ascent 722 +/CapHeight 722 +/Descent -217 +/FontName /DCGXEA+NimbusSanL-Bold +/ItalicAngle 0 +/StemV 141 +/XHeight 532 +/FontBBox [-173 -307 1003 949] +/Flags 4 +/CharSet (/fi/comma/period/one/two/three/four/five/six/seven/eight/colon/question/A/B/C/D/E/F/G/I/L/M/O/P/R/S/U/W/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 138 0 R +>> endobj +614 0 obj +[611 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 278 0 0 556 556 556 556 556 556 556 556 0 333 0 0 0 0 611 0 722 722 722 722 667 611 778 0 278 0 0 611 833 0 778 667 0 722 667 0 722 0 944 0 0 0 0 0 0 0 0 0 556 611 556 611 556 333 611 611 278 278 556 278 889 611 611 611 611 389 556 333 611 556 778 556 556 ] +endobj +134 0 obj << +/Length1 1166 +/Length2 6834 +/Length3 544 +/Length 7647 +/Filter /FlateDecode +>> +stream +x??ye\Tk?.?1(?1H7Cw7H#? ?C? 0t?? ? ??!?HHH#??R??????????{>?o?w???????u??}=???X?? y??PU? ????\m== ?pm^??'?.(?ge5??\???J?P0 +??+?Qw???'??(( H +?K????B%"?%?z?0W?P??????w?2?? +?? =?H?????t?@=$??w??gU???spD9? +L8??y???$$$???!@e??d?[xA]????(??p??]?v?s???*v0??q??(R??i??????AP@[???1??~????F??|?| ????_+???C?]|?N??B??*?F:j????_Y???;J^??0?WP\??)w?"B?d????GT ??>?????#??s??_#yA?=?? ????????A?`(??o?X +?????????7????5T=]\?P??O9?wzx???q??G:????_^?g? ?O??x4P`D???/?`?0?? q??.?l??w?Cx?~?@^????# ? ?zx???n???*p?w??\ v??W?7 ?tw?????{???=??A(? +??8??H=u?{?vQ?@???=.?+j|v??(??ro??G????V???xj?????l??#?{???*?b????|8$?$??14????u$G????4I??????|??????Xe??H #?????w?t?i? +?tw?8%(.?t?]??%?? u( 8?E?hv6N?d?4'h?vNZ?Nb3;??H(?!R +UwdKkV*&?1?)x?X?jY3?,??B.??/?5?;~~??c?s1???o? ??H??6??????C.:? ? +?????48T????1?jz? ?X?d?g????q +N???O?n$?tn???D!i?w? ??]?R????%???qA?? ?.?Xp?-9t?Z?(??L?@?K?z=.?K?j???H?????E??Q????????????? +[?6???s?EB}?? ????/???v???v?, ?+Z ?ax???6Y?y???e?????{ZP[T?????VT???v&n???x?????}??S?TV?>????^?????GP???uRR?;?d?'????[?6???y|?&%?h??????????????? IO????$????)1W???H?|?:?z????m?????=1?/???x??????}PR<(F'? l#??5???????x?Gy;?D??kaI?R?gF9K????sJ!?? +?F??}YeK???C/F???Ld????:??O???????&??j?'??g? ?=?M??D?W`V?g?{??z$??????[??v?????a???nu +????|3?Sj??}???????rr???3?|???L??L????? o|?|m&?O?? +?!D~??3??-??&Lw pF?E????? +f?3???T4.p5????J2???ff??/?l??Nu??????8K?$??? +????/+m>?????*?'?????2]6 ??u??O??AL? +!*??wT,?????~c??.?`Tv?[?v*6#f9 at Y?U??jK? ?????N????kO]e/f???~????? ?5$?l?_??????????Mz?D??H]??X0?'???P????:r??\%?KQ|???????9?kd??j??????I???b9??3?C????J}?]??????M?????. ?4?w??%?????E?}?"*?~E???51?&??3[vYX?? 0??$:z N?~=E???FoLe? k????????b445??????iX???W?? +g?x?????? +????'?V?? +??[????????e???????9?%?Rw +!k?=j???:?/Z????;??V??ik???s?(? ?eH???$l?u?????m????"cD ?? g?bN?? ??U????????q* ??O?$??7Wh$???w?I?\O?????0J;og??f?NLH74? ???&???????????;???V?V?!?'G?r??-L??&?}???C?==KYVp$?a?? +h?=????1????P???4?}d4??)k??h?z?LE???G???&?.u6? +;&H????? c????z`.cEc?z?H?9i???I+?.?????E^W?? ???|?? +?{?&?3U??,7???> +p??&d??PH?????bkOL:?T{??.???;?????+}?_?Mg????W?U???';???? ?N??x????p-+?C?+1lY??5????XAYo??E?L?sn????91+z"~f;?Fk%F?u?27?r76cNS+~ ,fqaB?N????z?????)???????oJ%??vWOOI??e???2??(????????g6|?cy?"W??j$q?_??????b=r?O????jtB??3{D+S?_??Z?1u??g?e???0???y??"m??????T????-??\  Io?[?a??0???a??R??t?z|3u?V Q?????r????O?n) +????qrz?}]P?T?4?)+?I??( +! +k#?:?eO/c+?(???+??B?Tq??L?I??UbD????LxC?XEV???Ie+TMI????g??P???J? +2#?z????:??D??v???? ?S8???#??Ps????d9??O?g?p???$M???y/??RI???v1????*?? +??????B?G??+????l????5?\??????Y????????2?i???oS??)?a-????&5? ???T)??6{??6f??=MMZ?H?Q[NZ=-?KD??V?'x??uK????????Unh?????? ?1'~?"?hY???#???~?sq???#?0?+?L"????Mu'?/\??=?A?$??Ibk????d??D??~?????{?jY=?"\,??)2b???l ^6?i +1??%?????|pj$;?Aeo??b V? ???t,t8???~~?`?': B?J?& +????_w8?:???1???????_l/%??do\??Y?5?5??H-???Q#?y)??k*V?h???~?[%???*??*r:Y????U?Xz????&???????I?66{?2~r?_9??SHr??????a?b??????-{?7R??|? Xs??'??z??Q??3? n???#???WhV?9?bW?-?g?6?????r??x??4?1E?p???jb???|w???? ??.|???l?%?R?G?????=???_%Yo|??6po??9D[??????????8s??n?\?ba?????H?;`0i? +K?xWTK?mx?tO?>w?kP?Y?P?v^G???O???ex?Sm~??M? ?tA??)???Wh?u???%??K'??C?r? -yH???`????yj?r???FfO?_???????ht?=?8?5???.?b?-?B???au???7?$E?????'?[Q5???~+??/!???z#;???~.??D???9m&Ml??|R????o??iM'?rR?#?S?/?_??`yJ??CF????l????}hhk_???????c??GG??????V??W? +??6?!s???B +?5GJ."%/? +?s?cBc?D"?=??p???NDP?OZ?9j??mj??l?????I0c???????E?{? ??Q+?EDB%$??f_P??P&>????? +S???\?k?M???????H???H?g? v?,:?_?? s?? +??)????x[??k?U?????z??~mV ?1?k?Q?-e????P????$?#?Ga????'????#s???{??G/????x +?6????;r???,O?? T%h?,b7????D|?r?????BTe?z ???E|??d?B?ueZ??1??N%S????g??? ?}"(?C9r???a?:?k?D0n@?{H???????n]O??????i?? +o??e?????> endobj +133 0 obj << +/Ascent 712 +/CapHeight 712 +/Descent -213 +/FontName /REDTNG+NimbusSanL-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 523 +/FontBBox [-174 -285 1001 953] +/Flags 4 +/CharSet (/quoteright/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/A/C/D/E/F/H/I/L/M/N/O/P/S/T/W/underscore/a/c/d/e/f/h/i/l/m/n/o/r/s/t/u/v/w/x/y) +/FontFile 134 0 R +>> endobj +615 0 obj +[222 0 0 0 0 0 0 278 278 556 556 556 556 556 556 556 556 556 556 0 0 0 0 0 0 0 667 0 722 722 667 611 0 722 278 0 0 556 833 722 778 667 0 0 667 611 0 0 944 0 0 0 0 0 0 0 556 0 556 0 500 556 556 278 0 556 222 0 0 222 833 556 556 0 0 333 500 278 556 500 722 500 500 ] +endobj +131 0 obj << +/Length1 1630 +/Length2 19463 +/Length3 532 +/Length 20368 +/Filter /FlateDecode +>> +stream +x???spfo?&?v??I?V???'?m?;f??m[??c???????9S???g??????p-\?^??6?? +????1P???????@?????Y??V??[?Ah? +?+g???q?X????y@S?(???`???????;x:Y?[????5h????S?? ???h?z:[??(???m?l?v.!??U?@??`fi?((jI?K?%??@;??? +@????? ki?s????6?>L??L-?)???/??3???4????0:???8?l-????,??NFv.{?b??3?q5?'??r3?%??d??????/?????????? ?oTEQ???ba??Olg??j???_KS{?J???/?_?????3????O,c ????????o??`N??J???????3?8???Lm???a?b???????To??`??/o?Y??,]??6f?p?,c????mni????H??????[n????tn@?5?????????????'?h?$o??7$????e??>??(?o!?????7r?+G??%????Z???F?????{??.#;??=???hl???>F??6??'??j??w??0)??m?3?K?7?o?Z:?[zM-]L,fF6{?/???)???????????????ZX?X??C??U@;??Z?_??????????,??f???P?? ??z:???????7???`???x30spX?????? q????oB? ????rF.N???uc?W?????I?????????3:*.Fv??? +?Q??:9?%?_ ?o??????=?&p+??&?!Vi?.??9???:??????% +?????=?i????5????P? m??3??)???*S|??,2???HEr?\?0?*???`??????[;??n{?:D?JlH????e?r????e[?y?t?%C LA?o?dI?A???v??y ????????k?b??|b at Q?#3\S??Y????-\???JH???+b??"????I?h?`[_?? #?vS)l?? ?;???x&q????l\???{Q??Dh??C?&?s????????????|?Y??|??!I4????=*???g +?w????_R?K( +???q-???m~?Q??Q?E J?????c?r??sr"-~?s/CK#??j?%??l???MK????sRs??u?U?3?{Z$??????E????/Ky_^YO?"???7 ?X?!?%??#j?!??????e~?!:F?s???@!?Q ~?%?d??,?7Dm?n?????J?(:ZX?y??jOAHQ???T +??C??^?Q??tY??tp??H?z[?|vu?;?WW????k??+A???+#("fGr???#b??"????????V8?$??????7h?8?oj?P8E`??????HYzW0D +l# +????BC?:KR7?B??[??????????8???4=e?q?y4?? N??[5?d?_???g??????????u??M???O~8?=????)?????!7PU?]w??q+??(??%y?I??????LZ/???Y?p +??R?????zZ]` +??p{?K?)??????_?X?NfJ(?K??{7%UO(V?lp?YD>?????}?SS"P? z?DV?JC?i8'?l??????a??g?9*??????IhJ???|?????7??{ no??I +???6???d_????^ )???W???+???????????s9\???Z)E???D??2?UY????h?p?\???V?}^ ?Pm??g?-} +?6N???UEH^e?? ??g ?J??t?#?3=?M???2F6????"?????????O??>?????sp?K=?x????Ow?{??????o?B??????)R-4?|i?z_?-ld??p}?>??L?v?C??T??W[????U??"9?? +?nT??e%?C???5??~?4 +?g?????_??????;1&k??????????]????A?#} +Z5 + +M8??????????EN?S??>???? hV??I???H?????'?<1?Fv?J???D?F?M??4?+d?>?2??Oq?r?@?? ??,$ye???k????w???? +????P9?0,??L0?\???j9d?)? +j???-?????+?,d?qL$???KA???H??p?/ws?3?????~=/^G?OW?~???3?[????w?-/??????*??????T?|???3h??F???4???????:5?????? .????? +w??!?y??u*?q +??H??????3?R&???????vk^(?3+V???1?????Q?RF?f?*?I m?k??5????%??,????e{?A^??8G??1???b?$? ??C?Li?????????l?-??J??T?T?{???=??C?_??7{???Xe???$??M *?[N?L?n.5?S!?1??kB:?.=6?$?!????sq?L)? ??o??a????9???/??E?6{``?\? ?Qw?Npx??]?=?EZk?sS?4Oc ?q???ra?m?n??D?q?U?? +O???*??q??D?t 'U?C?RC?S+F:s??*A?B[2?'K?q6~??Kn????N`'??<?=???)heT?? +[???TGH???????,???%??9???X??`??[????Naf????l?a*f????rQ?D??.$?a\W`9??x?9??,??hk?Y??vN:Or?aW??? +?.??Z? +??t. +/?K???y^9???q?v8p?*?^?Cw???S??n?>?#f???tb????"f??????=$?U?????*??????po???z???????}l@?????ys???4???????t?;?????R??~??e4????v???h?w???V?????????|h?:??5???_?n,D?^@]??T"?G`d?n?z?6??O?]`!N8C?"y?P?s??????*???c??N???*~??#?V +5>??i?3??wI?????,8??D?????}???VF;{?]?5??g?x#??ca[?S????0z?{????$&"z3|B*??J)?I?#P??g?|?Bw??yv.??1?,?? +K?n?>t??q?!?=?\QP$A??s*E????w?|xQ??"?T}? ???.?? ??X?^???~???????a?????{?????*]???????7??>?????5??B#?"?M????|y? +H??6?^Be?o}?u??$??????,?"_????5??&?????????t????F???gY?)??u??L?"]~? ??#?>v^??r?obJ??????f???}??s4??2?q???&t8?D??4n?????'J].ifH_"?S?)????f??????y????W??x??P?&?Ih.?Jpl??#?????Y??%?#?5o??e?~??&Pz4e?????B????$????????.b???n +Y +??g[???Cd?I a????9???ZF????>`n???=D?5?? F???7??? L?b??i?? ?O3???N?`?#f\??_L??Rt??????[D???z????WzD?2???????j?????U??Sq??????D???\%????? ??????b +?jR?{???8????g@?Y???-wd??????4??#r?A,??7~???Ni????h???? ?k?+??3??5^????~?6????At?J?@?.EA?m;????4???&?k???'<?? '?b?X????/g1?bW??O?p8'?R?/??J!!?G?-1E??RY??-??????j?T???9???????}????v'J??a? J?-2K?xl8???_o[ ??k?M??ph}?y#??N??????6??NF?My????B??????? ????H??S????O?L?$?S7 + e?y?????g?~?8???b??_?XC??tmp=?{?#?3jXT?6??e????\"?x?E?0????3ZU]??:^?\dR??9 ? ?s???Y??????\??R?L>? +w?,???r???????a??BvJ??????g???f?? ????q>? ?M??5H?|????Z?????"?O"????????R[??deh,???u??*E????A.??\!v?d??Q.??:??b;?????Y?b?Y+?R????E~??S??6?o4???X?X?-Dr ????4T???JG?=?R?????-??N.+??f?~M?aw??d???6???&iG)???p?.??B@?Wg?e}?9??k?E=S??d????O?? +?????L??H?a?????z???? d??mo????\#?;?5?P?6?/?????r?[f??!"W?N???n???| +$??? +J??0???JT?,lNeF???a?A?????$???X?7?t??8 ?U^??a??8?z[W?5;??IJz??????????Hys??%???B?h?Q4?0?PjH? 9E?v?a?m???????nUT??e?:q??A? ??$?????????b?4?*?????E??y??%;?B3?!?l ~???T?P?1d? ?Iz?k8j???:??????$?E?E)c(_???Ew-??????4???KM'???y??3?n?8??XWa?y;G?Y*G?#??/?lv?????8x???+pY?kM?%?????L???\|?Z??x3??r ??8A[??=(?o????'5A?*?,????*(??0@?f?A??o?5#?TPO??g??U?2??6=??%????}???@???a+#U.??y?c???#/?pG???8??`1???<4?eSh?P-?B+?uz??-??? J????t9?;????0?????8c??auy?%??hA???C;%???>???J??m??3???uHJ5&???????????3wQ6I???E??M??????K?? *UK???i?7`P?????@e??E@'?w??-?"?6k'??[??U?????}P???.??]&??????~g????<"???S???X?AL??`?b79T???????R??U?/e1???????Jb?e????????F1g???????=f? ?X???IV?????h?????D?Pm??@J6????d4 at B;??3????@P???A?g??}O?k??????/s#??5I??`4?????? u>?^*????????mg??)$\?i6mr? +?t??X9?a??]u?=D??8?[??[f??ehZeK???X?pd????????\?????=?2??~rq?!???pQ??>?Hl+??`?l&/z 8E?0?1?BA?????M? ???mES?w? ?????7??U??AF?p???B?>vu#???E?17?p:??w???%_???U +???d?[@??FG?T?Q???s.??Y(J(????T?G??P?mR???M?\>Tc???1Qck???%l;?Np????i?G?u?o???2???;?????ga,??????-k???%e??`?>gO!???.?7????Q??F?D???c_~???tTM???3\???~:??OE?O?e?c?8?ZJY +'??m??4W???{?U?g?C\?~??????h?LC???n"Wt?????;??VQK?I@?4 ?_a +?Y:*B?j?????m??{?S??D?C??C-???[??I? +??4MA?\2?0??)'@8?S, ??>?>?j ?T9?????9o???iud9??$v?fG??L?'?>b?)n-????????g???c?? H? '??N1 ??? +?%e;? +8*?_?v,Z??pv????`??G?"???F1{U?[?%L?^ByT?g$?4%(??U??G?kS?&}?QIs??g?v?k? +?:&4 +M???cu?Y??_:q?_???b??T?Ej????*?z?A?`???5"|??sy??;?????dn?mG???wFW-n?vh?]?aw?_?? +??e +G???d?@??L8??3#?? +(??q"W?7?}??m?j??9B??E\f(D??G????(???UvmD-?S?P????C?{Vc$?"?L?N?????????P??vL??? ?o?????u?7,MM???????S](@??J???????;5~mV??[p?X T2 ?????bl???g????\F??????B???v??eF&_h}?1???h??j6????G? +??yy??),5????k??hIo??8?'?m?????RRF?q|?Jul?=~ +?????0wn>wP{-W?s{????? +??u)??*-wU???s?d?n???`??X{7S?? +p;>(W?,w?? ??x?{?-?Z ?,?)9=?p???+?n?3y???P????I?<?????4???;7???%4??d?cj??^P: JQ"?b?F?&???? +?????/??'????o??_c?WAY???Z??:???ww?*8 <5?XA???3??@N?s??.L?b?@??w?KP?*???????,????l??C?Jw? ??#a?T?|U?.4F????Mp?w???????s?????(?? ?o?;?? .*WU?nO??5 ;! ??m?7A???'??I?H??8x?* ?LH??ok_?@S/??X???$?a?VZS?yzK"!??_H??eX???|!?1?-?S?Q+P?L??RZT?(_^?k~?9??????Ig??????b???Y?'&???????dqk???W?\???5?f?9;y1?b??r F0? V?n?D?\[?? ? +\?a_K3???;*?v?UR?c??o??1{'??X3s??1]e?? w?H????6l?T??G`0\?SMs?`-???o???Y?????k??>}????{??.~8%.??'2??+F??????T? +?A??X??? ??i?!9@??s????0"??S?I????|?O?Eq????????}????????o@]?T???_+yh?G?? ?????7?J?P??A???7X?Us?($<*?N0j?e???u7?~?????C??Fh?J +???'??F(oW?St??,???????????p?:ck?L)??????y:,Do%?mr??`?;???????C??h!??W + +f??G4 +"?|8?,_R?-???9?w?#??a??sX???kCu\,????????[?h? \~?v?VF??qG??&??$e?????R??6?X???|X=??&??? ??N???bibl ??rb?y????????H?>?_?^|?c????`?Gk???)eW?th??kk???s^Zn???????-????]?[?8??]????:???zZ}??!V+??a????%?^8QB????A?j???sW/?K?????T???"4xN???* ????,5G?k? $???AV????????z??+?????????j$J????r?1???????Z8??*hoHV9&(??? +W?q?< ??|??????_?4?v{???NO,}??6??D~w??P? t??o?NZ?#?%Q?d)?? i? ?~?m5?!?>S???R? +??M??L?D$???k+???>??=???"?H?n6?c1??\?????,?/n???A???=?nG?O???o?!HU??2?L?}????M`??u?h??qJ??T????E???k?C[????*\?L?H???????$????+? 'Am?MW?z?L?8y??? ???N?0???????H?b???t?\?:I?T?GV ??????Z?].W?&i? ?O-?I)??? +a+?????=8FjKPosMT}U?n??}f3????,????5?#?}^A????w?-??4??Z???>8;?fj??g????V????c?????0?5? +?-????$u????B???X?%?7?P? +? /????C?~??b(?h+?? Dv?b?M????[???tC*??u????Wg8???.?O??F8?j?? ???vR*??q/z?b??i????g??)?Uh3m???b?V???`?>????q?'?[m???>?????M?BMzc?oRm???w?O????16'v?t??D??????i8[??#??Ua ???L??P?V w??P??^??\3??H?????????]%???????M?[????[ ????NLOB1?3#?????17??rL]??6??????6l.???h?k qi??d#?c??7i?%??????/@dX??M?C~?V?????L???]???'tbw?0??\?0?^w?q??jN??Cr2a???ejrPq??~?'??I?b}????? ?h????N??????V??*??F???3?3????QM??R?A??????-???|???|???3?5?p?????D Q??Nh?X?x2??N?7?tvj??)???????OU? ?%? ?????,???jd?d +dK??????u?X??????[??X??I????ay?](?????????n*?E?%.?g????@??H?EH`:?hg???Z.[X???[A??y?p?Z0?????8k?W??????8??sC?6?i?? Mp?:o?q#?????HI$?]^??G?Ysuq?LOp??j?? ??N??#?(?eL?S3??]-.3?8????e??b ???8?2? +[74??^=|???e??[???T?-7M?? f-?J???#Y2??28/UyN??;? ;?;?'???J?1??Jd????1%?,?M +V ? ???? ?O???! \?. +>/?Fn?r]?j?????d?}???? ??????VE?Qf?,??M?g??E??oy?g??????????V? +"i?k??^?N?????4U??}?Fy???7|????#=-??J?8? ??h$?O at tW|?O? ???4?]?&B?s?i>?:??g:+????>?y +?iR?????q??q??&???+?|"??a?{_.e+???O??u?n?-?2 -?W8?xb???(?????"??1??3?Vzx?:G)?m?jvE??A????m???6????????OT^>? +????/L??????8W?H7??uo?i@???'???Ug?????? ????D?????/???????????Yk????K???-hy?,G?1?2???????*R?o??:?p??Qxi???`? Jb +[????????????!6?G ??n??Y???V????a?????KIp@?? p?&.Q*7dnhts?SR??SG??(?}qS??? +6]R{??J@ K????]??P??=?\?L???L^?a?????? 9DS????~?w}????????Ob??????P(??En??T??Z?r@?z???j&W~???h?? ~?0?4?'xf?6~ud?#R????"???B#??&?&??????NF[??'&J$(??s??x????::?,?$t???????LLdba????????_;???8p?T??[?(?q??g??Br?,???8gd^?}?Jg??R??7QG?23????~?}_??x????HV7?p?2?LZ0?!q??E%????kY8?Th???2???>w????????????T?7???O??8????/3?f? +?}?"?5?>px?a???=.PB?R?ZVA?;?=.?????O??????U_?8??.d???d?4]4XrOC???g?Ls????04?Gn??["(????R?T??JE?g???0?E;&e|??Z??^[>}??*??c?????G?[??M??h??d??U???-?K??/{????8~k?3??? +??????~QS????] +{?k?{4"?S? #@???Zp=?{???p*?+??9?Wl&??H????w?*{z8?7#m` ??#?8a-??????i????8fL^C?|?,????@z?????,?>?Zs>>??$%?3?1T?k?5?$v?n???v?????q???A|?????$4 ?V? ??'3????L??{????1?s?U???Z2?0$?q?Sf??????qW???{8?zPg?|U?m?EZp???????TC]???Lz;???>??,,?9??W_?yHh%?L?${?N.?.5U?^Ss???I$??r1????^b?|???????D?=wA?}Z? ??=????9????????Wlmr??r????tt?Y?WJ?$??&?(???p????X^_i?j?5w??&?E?J???m_v*??ld+o3?GQ?_?????B?\?*??/???5???qt???o?\??d0>?8D?_P????M???H??R0z:?r!QQp?N?.??26xQ???=? d??g?+i2T?? +?A# ??g????V h?w,6??A ?!?GtOe?>??????????p? ????5???)#"X?I!???????gMQ?mH ???h ?yM]?BGN??????l?;?????S6?kI%???e?-V +?c??$F??w?tk +?h?,??-??U?%?^^G?z8 X(Yt???jV/k +?w??A???? +(t????8??b??^G)U?\??gj?#a?u????+??6+?{o??F4??I?A:V????:??????Fj7L???$???|?N????"'7?r?E??????????^S?Wc>??????j?i3??????f[????U#???????A? I?7?fut Ms ?M?}@???&7?C????lL?O?U!?E?????p ?? +????'??LJ???KK??o?I???\??#?Rf???g=????f?????| ?m8??q??T???'?>?m?????1>?p??p??????????q?{?cbi1??i????U?m??xCe5#??ox???Z????8?$^H?[7 -?????u??????7K,%bL?50V??????2??b? ?]?????1oY??????w??O??*b??z*w{???Y??????e?????%o>qM9w.????n,??~????"6g,?????7????b????6+??s????}?dp?z@?&w???u?v??K?S??8V?J? ???O6?S1a???juT???H??1??g?y??%?????x8??????z?????&???q?\??????eE????R b+??5?[?w???????>?????%??[??JY|+ ?%F??=2?????????b???e???"??id???r!???M?j~?????n??xD?:b&??&??9c???4?????_l??#zA?Y?u?b,HZ]??d{??M#C? +???t?q??E}}q??]?t? \????2??U???/?zL??W?? cU???c???_??????4?LX???'Y??}??|S??1?L?? ??F2{z?~?f????&%???s9 ???z<^(R?????-BKX???0?Y-???J:?F?I???????? ++?t!?1??+???ty???8?q?? +V?tv?b???3??z5?B?/4???????B?[~?????A??N?>N?EM??O??v?"OpW?&g??im???????be??e"??l??0r2??? +???????????N??F??????m??P???4?eL_ s????d#????v)Bs?k?A???|?#?N??P???C?$??B20S?????"?e?l>}=yQo???F#?0??=8??? ?wS???+??????9p48??0(?;? + (?wY=???c?????'o?> endobj +130 0 obj << +/Ascent 678 +/CapHeight 651 +/Descent -216 +/FontName /EXVUAL+NimbusRomNo9L-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 450 +/FontBBox [-168 -281 1000 924] +/Flags 4 +/CharSet (/fi/fl/exclam/quotedbl/numbersign/dollar/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/bullet) +/FontFile 131 0 R +>> endobj +616 0 obj +[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 500 500 0 778 333 333 333 500 564 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 564 564 564 444 921 722 667 667 722 611 556 722 722 333 389 722 611 889 722 722 556 0 667 556 611 722 722 944 722 722 0 333 278 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 350 ] +endobj +140 0 obj << +/Type /Pages +/Count 6 +/Parent 617 0 R +/Kids [126 0 R 142 0 R 180 0 R 214 0 R 259 0 R 304 0 R] +>> endobj +382 0 obj << +/Type /Pages +/Count 6 +/Parent 617 0 R +/Kids [356 0 R 384 0 R 427 0 R 481 0 R 485 0 R 494 0 R] +>> endobj +557 0 obj << +/Type /Pages +/Count 3 +/Parent 617 0 R +/Kids [525 0 R 559 0 R 592 0 R] +>> endobj +617 0 obj << +/Type /Pages +/Count 15 +/Kids [140 0 R 382 0 R 557 0 R] +>> endobj +618 0 obj << +/Type /Outlines +/First 7 0 R +/Last 107 0 R +/Count 6 +>> endobj +123 0 obj << +/Title 124 0 R +/A 121 0 R +/Parent 107 0 R +/Prev 111 0 R +>> endobj +119 0 obj << +/Title 120 0 R +/A 117 0 R +/Parent 111 0 R +/Prev 115 0 R +>> endobj +115 0 obj << +/Title 116 0 R +/A 113 0 R +/Parent 111 0 R +/Next 119 0 R +>> endobj +111 0 obj << +/Title 112 0 R +/A 109 0 R +/Parent 107 0 R +/Next 123 0 R +/First 115 0 R +/Last 119 0 R +/Count -2 +>> endobj +107 0 obj << +/Title 108 0 R +/A 105 0 R +/Parent 618 0 R +/Prev 103 0 R +/First 111 0 R +/Last 123 0 R +/Count -2 +>> endobj +103 0 obj << +/Title 104 0 R +/A 101 0 R +/Parent 618 0 R +/Prev 83 0 R +/Next 107 0 R +>> endobj +99 0 obj << +/Title 100 0 R +/A 97 0 R +/Parent 83 0 R +/Prev 95 0 R +>> endobj +95 0 obj << +/Title 96 0 R +/A 93 0 R +/Parent 83 0 R +/Prev 91 0 R +/Next 99 0 R +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 83 0 R +/Prev 87 0 R +/Next 95 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 83 0 R +/Next 91 0 R +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 618 0 R +/Prev 71 0 R +/Next 103 0 R +/First 87 0 R +/Last 99 0 R +/Count -4 +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 71 0 R +/Prev 75 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 618 0 R +/Prev 11 0 R +/Next 83 0 R +/First 75 0 R +/Last 79 0 R +/Count -2 +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 63 0 R +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 11 0 R +/Prev 59 0 R +/First 67 0 R +/Last 67 0 R +/Count -1 +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 11 0 R +/Prev 55 0 R +/Next 63 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 11 0 R +/Prev 51 0 R +/Next 59 0 R +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 11 0 R +/Prev 47 0 R +/Next 55 0 R +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 11 0 R +/Prev 43 0 R +/Next 51 0 R +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 11 0 R +/Prev 23 0 R +/Next 47 0 R +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 23 0 R +/Prev 35 0 R +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 23 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 23 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 11 0 R +/Prev 15 0 R +/Next 43 0 R +/First 27 0 R +/Last 39 0 R +/Count -4 +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 15 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 11 0 R +/Next 23 0 R +/First 19 0 R +/Last 19 0 R +/Count -1 +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 618 0 R +/Prev 7 0 R +/Next 71 0 R +/First 15 0 R +/Last 63 0 R +/Count -8 +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 618 0 R +/Next 11 0 R +>> endobj +619 0 obj << +/Names [(Doc-Start) 136 0 R (Item.1) 307 0 R (Item.10) 562 0 R (Item.11) 563 0 R (Item.12) 597 0 R (Item.13) 598 0 R (Item.14) 599 0 R (Item.15) 600 0 R (Item.16) 601 0 R (Item.17) 602 0 R (Item.18) 603 0 R (Item.19) 604 0 R (Item.2) 308 0 R (Item.20) 605 0 R (Item.3) 309 0 R (Item.4) 360 0 R (Item.5) 361 0 R (Item.6) 362 0 R (Item.7) 554 0 R (Item.8) 555 0 R (Item.9) 556 0 R (_beagle) 491 0 R (_bionimbus) 513 0 R (_coaster_providers_local_ssh_pbs) 489 0 R (_coasters) 453 0 R (_debugging_swift) 553 0 R (_environment_setup) 205 0 R (_first_swiftscript) 262 0 R (_for_advanced_users) 488 0 R (_installation) 186 0 R (_log_processing) 564 0 R (_make_a_basic_block_allocation_plot_from_coasters_block_log_lines) 586 0 R (_make_a_basic_job_completion_plot_from_coasters_cpu_log_lines) 581 0 R (_make_a_basic_load_plot_from_coasters_cpu_log_lines) 568 0 R (_mappers) 363 0 R (_osg) 512 0 R (_overview) 183 0 R (_pads) 497 0 R (_passing_an_array_to_swift) 359 0 R (_prerequisites) 187 0 R ( _problem_reporting) 595 0 R (_resuming_a_stopped_or_crashed_swift_run) 317 0 R (_second_swiftscript) 284 0 R (_setting_sites_xml) 248 0 R (_setting_swift_configuration) 232 0 R (_setting_transformation_catalog) 219 0 R (_setting_up_to_run_swift) 201 0 R (_swift_basics) 185 0 R (_swift_commandline_options) 301 0 R (_swift_on_diverse_infrastructures) 490 0 R (_what_if_swift_hangs) 302 0 R (lstlisting.-1) 188 0 R (lstlisting.-10) 285 0 R (lstlisting.-11) 310 0 R (lstlisting.-12) 318 0 R (lstlisting.-13) 329 0 R (lstlisting.-14) 364 0 R (lstlisting.-15) 366 0 R (lstlisting.-16) 387 0 R (lstlisting.-17) 394 0 R (lstlisting.-18) 396 0 R (lstlisting.-19) 402 0 R (lstlisting.-2) 203 0 R (lstlisting.-20) 411 0 R (lstlisting.-21) 455 0 R (lstlisting.-22) 498 0 R (lstlisting.-23) 500 0 R (lstlisting.-24) 514 0 R (lstlisting.-25) 528 0 R (lstlisting.-26) 533 0 R (lstlisting.-27) 565 0 R (lstlisting.-28) 569 0 R (lstlisting.-29) 571 0 R (lstlisting.-3) 206 0 R (lstlisting.-30) 573 0 R (l stlisting.-31) 575 0 R (lstlisting.-32) 577 0 R (lstlisting.-33) 579 0 R (lstlisting.-34) 582 0 R (lstlisting.-35) 584 0 R (lstlisting.-36) 587 0 R (lstlisting.-37) 589 0 R (lstlisting.-4) 208 0 R (lstlisting.-5) 217 0 R (lstlisting.-6) 220 0 R (lstlisting.-7) 234 0 R (lstlisting.-8) 249 0 R (lstlisting.-9) 263 0 R (lstnumber.-1.1) 189 0 R (lstnumber.-1.2) 193 0 R (lstnumber.-1.3) 194 0 R (lstnumber.-1.4) 195 0 R (lstnumber.-1.5) 196 0 R (lstnumber.-1.6) 197 0 R (lstnumber.-1.7) 198 0 R (lstnumber.-1.8) 199 0 R (lstnumber.-1.9) 200 0 R (lstnumber.-10.1) 286 0 R (lstnumber.-10.10) 295 0 R (lstnumber.-10.11) 296 0 R (lstnumber.-10.12) 297 0 R (lstnumber.-10.13) 298 0 R (lstnumber.-10.14) 299 0 R (lstnumber.-10.15) 300 0 R (lstnumber.-10.2) 287 0 R (lstnumber.-10.3) 288 0 R (lstnumber.-10.4) 289 0 R (lstnumber.-10.5) 290 0 R (lstnumber.-10.6) 291 0 R (lstnumber.-10.7) 292 0 R (lstnumber.-10.8) 293 0 R (lstnumber.-10.9) 294 0 R (lstnumber.-11.1) 311 0 R (lstnumber.-11.2) 312 0 R (lstnumber.-11.3) 313 0 R (lstnumber.-11.4) 314 0 R (lstnumber.-11.5) 315 0 R (lstnumber.-11.6) 316 0 R (lstnumber.-12.1) 319 0 R (lstnumber.-12.10) 328 0 R (lstnumber.-12.2) 320 0 R (lstnumber.-12.3) 321 0 R (lstnumber.-12.4) 322 0 R (lstnumber.-12.5) 323 0 R (lstnumber.-12.6) 324 0 R (lstnumber.-12.7) 325 0 R (lstnumber.-12.8) 326 0 R (lstnumber.-12.9) 327 0 R (lstnumber.-13.1) 330 0 R (lstnumber.-13.10) 339 0 R (lstnumber.-13.11) 340 0 R (lstnumber.-13.12) 341 0 R (lstnumber.-13.13) 342 0 R (lstnumber.-13.14) 343 0 R (lstnumber.-13.15) 344 0 R (lstnumber.-13.16) 345 0 R (lstnumber.-13.17) 346 0 R (lstnumber.-13.18) 347 0 R (lstnumber.-13.19) 348 0 R (lstnumber.-13.2) 331 0 R (lstnumber.-13.20) 349 0 R (lstnumber.-13.21) 350 0 R (lstnumber.-13.22) 351 0 R (lstnumber.-13.23) 352 0 R (lstnumber.-13.24) 353 0 R (lstnumber.-13.25) 354 0 R (lstnumber.-13.3) 332 0 R (lstnumber.-13.4) 333 0 R (lstnumber.-13.5) 334 0 R (lstnumber.-13.6) 335 0 R (lstnumber.-13.7) 336 0 R (lstnumbe r.-13.8) 337 0 R (lstnumber.-13.9) 338 0 R (lstnumber.-14.1) 365 0 R (lstnumber.-15.1) 367 0 R (lstnumber.-15.10) 376 0 R (lstnumber.-15.11) 377 0 R (lstnumber.-15.12) 378 0 R (lstnumber.-15.13) 379 0 R (lstnumber.-15.14) 380 0 R (lstnumber.-15.15) 381 0 R (lstnumber.-15.2) 368 0 R (lstnumber.-15.3) 369 0 R (lstnumber.-15.4) 370 0 R (lstnumber.-15.5) 371 0 R (lstnumber.-15.6) 372 0 R (lstnumber.-15.7) 373 0 R (lstnumber.-15.8) 374 0 R (lstnumber.-15.9) 375 0 R (lstnumber.-16.1) 388 0 R (lstnumber.-16.2) 389 0 R (lstnumber.-16.3) 390 0 R (lstnumber.-16.4) 391 0 R (lstnumber.-16.5) 392 0 R (lstnumber.-16.6) 393 0 R (lstnumber.-17.1) 395 0 R (lstnumber.-18.1) 397 0 R (lstnumber.-18.2) 398 0 R (lstnumber.-18.3) 399 0 R (lstnumber.-18.4) 400 0 R (lstnumber.-18.5) 401 0 R (lstnumber.-19.1) 403 0 R (lstnumber.-19.2) 404 0 R (lstnumber.-19.3) 405 0 R (lstnumber.-19.4) 406 0 R (lstnumber.-19.5) 407 0 R (lstnumber.-19.6) 408 0 R (lstnumber.-19.7) 409 0 R (lstnumber.-19.8) 410 0 R (lst number.-2.1) 204 0 R (lstnumber.-20.1) 412 0 R (lstnumber.-20.10) 421 0 R (lstnumber.-20.11) 422 0 R (lstnumber.-20.12) 423 0 R (lstnumber.-20.13) 424 0 R (lstnumber.-20.14) 425 0 R (lstnumber.-20.15) 430 0 R (lstnumber.-20.16) 431 0 R (lstnumber.-20.17) 432 0 R (lstnumber.-20.18) 433 0 R (lstnumber.-20.19) 434 0 R (lstnumber.-20.2) 413 0 R (lstnumber.-20.20) 435 0 R (lstnumber.-20.21) 436 0 R (lstnumber.-20.22) 437 0 R (lstnumber.-20.23) 438 0 R (lstnumber.-20.24) 439 0 R (lstnumber.-20.25) 440 0 R (lstnumber.-20.26) 441 0 R (lstnumber.-20.27) 442 0 R (lstnumber.-20.28) 443 0 R (lstnumber.-20.29) 444 0 R (lstnumber.-20.3) 414 0 R (lstnumber.-20.30) 445 0 R (lstnumber.-20.31) 446 0 R (lstnumber.-20.32) 447 0 R (lstnumber.-20.33) 448 0 R (lstnumber.-20.34) 449 0 R (lstnumber.-20.35) 450 0 R (lstnumber.-20.36) 451 0 R (lstnumber.-20.37) 452 0 R (lstnumber.-20.4) 415 0 R (lstnumber.-20.5) 416 0 R (lstnumber.-20.6) 417 0 R (lstnumber.-20.7) 418 0 R (lstnumber.-20.8) 419 0 R (lst number.-20.9) 420 0 R (lstnumber.-21.1) 456 0 R (lstnumber.-21.10) 465 0 R (lstnumber.-21.11) 466 0 R (lstnumber.-21.12) 467 0 R (lstnumber.-21.13) 468 0 R (lstnumber.-21.14) 469 0 R (lstnumber.-21.15) 470 0 R (lstnumber.-21.16) 471 0 R (lstnumber.-21.17) 472 0 R (lstnumber.-21.18) 473 0 R (lstnumber.-21.19) 474 0 R (lstnumber.-21.2) 457 0 R (lstnumber.-21.20) 475 0 R (lstnumber.-21.21) 476 0 R (lstnumber.-21.22) 477 0 R (lstnumber.-21.23) 478 0 R (lstnumber.-21.24) 479 0 R (lstnumber.-21.3) 458 0 R (lstnumber.-21.4) 459 0 R (lstnumber.-21.5) 460 0 R (lstnumber.-21.6) 461 0 R (lstnumber.-21.7) 462 0 R (lstnumber.-21.8) 463 0 R (lstnumber.-21.9) 464 0 R (lstnumber.-22.1) 499 0 R (lstnumber.-23.1) 501 0 R (lstnumber.-23.10) 510 0 R (lstnumber.-23.11) 511 0 R (lstnumber.-23.2) 502 0 R (lstnumber.-23.3) 503 0 R (lstnumber.-23.4) 504 0 R (lstnumber.-23.5) 505 0 R (lstnumber.-23.6) 506 0 R (lstnumber.-23.7) 507 0 R (lstnumber.-23.8) 508 0 R (lstnumber.-23.9) 509 0 R (lstnumber.-24 .1) 515 0 R (lstnumber.-24.2) 516 0 R (lstnumber.-24.3) 517 0 R (lstnumber.-24.4) 518 0 R (lstnumber.-24.5) 519 0 R (lstnumber.-24.6) 520 0 R (lstnumber.-24.7) 521 0 R (lstnumber.-24.8) 522 0 R (lstnumber.-24.9) 523 0 R (lstnumber.-25.1) 529 0 R (lstnumber.-26.1) 534 0 R (lstnumber.-26.10) 543 0 R (lstnumber.-26.11) 544 0 R (lstnumber.-26.12) 545 0 R (lstnumber.-26.13) 546 0 R (lstnumber.-26.14) 547 0 R (lstnumber.-26.15) 548 0 R (lstnumber.-26.16) 549 0 R (lstnumber.-26.17) 550 0 R (lstnumber.-26.18) 551 0 R (lstnumber.-26.19) 552 0 R (lstnumber.-26.2) 535 0 R (lstnumber.-26.3) 536 0 R (lstnumber.-26.4) 537 0 R (lstnumber.-26.5) 538 0 R (lstnumber.-26.6) 539 0 R (lstnumber.-26.7) 540 0 R (lstnumber.-26.8) 541 0 R (lstnumber.-26.9) 542 0 R (lstnumber.-27.1) 566 0 R (lstnumber.-27.2) 567 0 R (lstnumber.-28.1) 570 0 R (lstnumber.-29.1) 572 0 R (lstnumber.-3.1) 207 0 R (lstnumber.-30.1) 574 0 R (lstnumber.-31.1) 576 0 R (lstnumber.-32.1) 578 0 R (lstnumber.-33.1) 580 0 R (lstnu mber.-34.1) 583 0 R (lstnumber.-35.1) 585 0 R (lstnumber.-36.1) 588 0 R (lstnumber.-37.1) 590 0 R (lstnumber.-4.1) 209 0 R (lstnumber.-5.1) 218 0 R (lstnumber.-6.1) 221 0 R (lstnumber.-6.2) 222 0 R (lstnumber.-7.1) 235 0 R (lstnumber.-7.10) 244 0 R (lstnumber.-7.11) 245 0 R (lstnumber.-7.12) 246 0 R (lstnumber.-7.13) 247 0 R (lstnumber.-7.2) 236 0 R (lstnumber.-7.3) 237 0 R (lstnumber.-7.4) 238 0 R (lstnumber.-7.5) 239 0 R (lstnumber.-7.6) 240 0 R (lstnumber.-7.7) 241 0 R (lstnumber.-7.8) 242 0 R (lstnumber.-7.9) 243 0 R (lstnumber.-8.1) 250 0 R (lstnumber.-8.2) 251 0 R (lstnumber.-8.3) 252 0 R (lstnumber.-8.4) 253 0 R (lstnumber.-8.5) 254 0 R (lstnumber.-8.6) 255 0 R (lstnumber.-8.7) 256 0 R (lstnumber.-8.8) 257 0 R (lstnumber.-9.1) 264 0 R (lstnumber.-9.10) 273 0 R (lstnumber.-9.11) 274 0 R (lstnumber.-9.12) 275 0 R (lstnumber.-9.13) 276 0 R (lstnumber.-9.14) 277 0 R (lstnumber.-9.15) 278 0 R (lstnumber.-9.16) 279 0 R (lstnumber.-9.17) 280 0 R (lstnumber.-9.18) 281 0 R (ls tnumber.-9.19) 282 0 R (lstnumber.-9.2) 265 0 R (lstnumber.-9.3) 266 0 R (lstnumber.-9.4) 267 0 R (lstnumber.-9.5) 268 0 R (lstnumber.-9.6) 269 0 R (lstnumber.-9.7) 270 0 R (lstnumber.-9.8) 271 0 R (lstnumber.-9.9) 272 0 R (page.1) 182 0 R (page.10) 496 0 R (page.11) 527 0 R (page.12) 561 0 R (page.13) 594 0 R (page.2) 216 0 R (page.3) 261 0 R (page.4) 306 0 R (page.5) 358 0 R (page.6) 386 0 R (page.7) 429 0 R (page.8) 483 0 R (page.9) 487 0 R (page.i) 129 0 R (page.ii) 144 0 R (section.1) 6 0 R (section.2) 10 0 R (section.3) 70 0 R (section.4) 82 0 R (section.5) 102 0 R (section.6) 106 0 R (subsection.2.1) 14 0 R (subsection.2.2) 22 0 R (subsection.2.3) 42 0 R (subsection.2.4) 46 0 R (subsection.2.5) 50 0 R (subsection.2.6) 54 0 R (subsection.2.7) 58 0 R (subsection.2.8) 62 0 R (subsection.3.1) 74 0 R (subsection.3.2) 78 0 R (subsection.4.1) 86 0 R (subsection.4.2) 90 0 R (subsection.4.3) 94 0 R (subsection.4.4) 98 0 R (subsection.6.1) 110 0 R (subsection.6.2) 122 0 R (subs ubsection.2.1.1) 18 0 R (subsubsection.2.2.1) 26 0 R (subsubsection.2.2.2) 30 0 R (subsubsection.2.2.3) 34 0 R (subsubsection.2.2.4) 38 0 R (subsubsection.2.8.1) 66 0 R (subsubsection.6.1.1) 114 0 R (subsubsection.6.1.2) 118 0 R] +/Limits [(Doc-Start) (subsubsection.6.1.2)] +>> endobj +620 0 obj << +/Kids [619 0 R] +>> endobj +621 0 obj << +/Dests 620 0 R +>> endobj +622 0 obj << +/Type /Catalog +/Pages 617 0 R +/Outlines 618 0 R +/Names 621 0 R +/PageMode /UseOutlines +/OpenAction 125 0 R +>> endobj +623 0 obj << +/Author(Swift team)/Title(Swift Cookbook)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() +/CreationDate (D:20110516141543-05'00') +/PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) +>> endobj +xref +0 624 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000017512 00000 n +0000197747 00000 n +0000000054 00000 n +0000000080 00000 n +0000017636 00000 n +0000197624 00000 n +0000000125 00000 n +0000000156 00000 n +0000017761 00000 n +0000197513 00000 n +0000000207 00000 n +0000000238 00000 n +0000017886 00000 n +0000197452 00000 n +0000000294 00000 n +0000000326 00000 n +0000018640 00000 n +0000197328 00000 n +0000000377 00000 n +0000000419 00000 n +0000018891 00000 n +0000197254 00000 n +0000000475 00000 n +0000000511 00000 n +0000024963 00000 n +0000197167 00000 n +0000000567 00000 n +0000000616 00000 n +0000025277 00000 n +0000197080 00000 n +0000000672 00000 n +0000000718 00000 n +0000026281 00000 n +0000197006 00000 n +0000000774 00000 n +0000000810 00000 n +0000031939 00000 n +0000196919 00000 n +0000000861 00000 n +0000000897 00000 n +0000033321 00000 n +0000196832 00000 n +0000000948 00000 n +0000000985 00000 n +0000034452 00000 n +0000196745 00000 n +0000001036 00000 n +0000001080 00000 n +0000034577 00000 n +0000196658 00000 n +0000001131 00000 n +0000001169 00000 n +0000042833 00000 n +0000196571 00000 n +0000001220 00000 n +0000001278 00000 n +0000049927 00000 n +0000196460 00000 n +0000001329 00000 n +0000001374 00000 n +0000050241 00000 n +0000196399 00000 n +0000001430 00000 n +0000001456 00000 n +0000068232 00000 n +0000196274 00000 n +0000001502 00000 n +0000001529 00000 n +0000074711 00000 n +0000196200 00000 n +0000001580 00000 n +0000001617 00000 n +0000074835 00000 n +0000196126 00000 n +0000001668 00000 n +0000001721 00000 n +0000074960 00000 n +0000196000 00000 n +0000001767 00000 n +0000001818 00000 n +0000075085 00000 n +0000195926 00000 n +0000001869 00000 n +0000001894 00000 n +0000079739 00000 n +0000195839 00000 n +0000001945 00000 n +0000001968 00000 n +0000080744 00000 n +0000195752 00000 n +0000002019 00000 n +0000002041 00000 n +0000080869 00000 n +0000195677 00000 n +0000002092 00000 n +0000002121 00000 n +0000089288 00000 n +0000195585 00000 n +0000002168 00000 n +0000002203 00000 n +0000094884 00000 n +0000195467 00000 n +0000002250 00000 n +0000002284 00000 n +0000095199 00000 n +0000195349 00000 n +0000002336 00000 n +0000002406 00000 n +0000096080 00000 n +0000195270 00000 n +0000002463 00000 n +0000002543 00000 n +0000096456 00000 n +0000195191 00000 n +0000002600 00000 n +0000002684 00000 n +0000098747 00000 n +0000195112 00000 n +0000002736 00000 n +0000002773 00000 n +0000003183 00000 n +0000003431 00000 n +0000002826 00000 n +0000003305 00000 n +0000193559 00000 n +0000172896 00000 n +0000193386 00000 n +0000172255 00000 n +0000164316 00000 n +0000172084 00000 n +0000003368 00000 n +0000163588 00000 n +0000152003 00000 n +0000163418 00000 n +0000194632 00000 n +0000011340 00000 n +0000006110 00000 n +0000003529 00000 n +0000011277 00000 n +0000006484 00000 n +0000151224 00000 n +0000135699 00000 n +0000151051 00000 n +0000006638 00000 n +0000006793 00000 n +0000006953 00000 n +0000007118 00000 n +0000007278 00000 n +0000007440 00000 n +0000007605 00000 n +0000007770 00000 n +0000007935 00000 n +0000008092 00000 n +0000008251 00000 n +0000008411 00000 n +0000008571 00000 n +0000008728 00000 n +0000008888 00000 n +0000009053 00000 n +0000009208 00000 n +0000009368 00000 n +0000009528 00000 n +0000009683 00000 n +0000009843 00000 n +0000010000 00000 n +0000010160 00000 n +0000010320 00000 n +0000010475 00000 n +0000010627 00000 n +0000010787 00000 n +0000010952 00000 n +0000011117 00000 n +0000016152 00000 n +0000019266 00000 n +0000016002 00000 n +0000011451 00000 n +0000017449 00000 n +0000017573 00000 n +0000017041 00000 n +0000017698 00000 n +0000017823 00000 n +0000017948 00000 n +0000018011 00000 n +0000018074 00000 n +0000134755 00000 n +0000115700 00000 n +0000134584 00000 n +0000018137 00000 n +0000018200 00000 n +0000018263 00000 n +0000018326 00000 n +0000018388 00000 n +0000018451 00000 n +0000018514 00000 n +0000018577 00000 n +0000018702 00000 n +0000017245 00000 n +0000018765 00000 n +0000018828 00000 n +0000018951 00000 n +0000019014 00000 n +0000019077 00000 n +0000019140 00000 n +0000019203 00000 n +0000016838 00000 n +0000016973 00000 n +0000017020 00000 n +0000026970 00000 n +0000024407 00000 n +0000019418 00000 n +0000024774 00000 n +0000024837 00000 n +0000024900 00000 n +0000025025 00000 n +0000025088 00000 n +0000025151 00000 n +0000025214 00000 n +0000115373 00000 n +0000113916 00000 n +0000115212 00000 n +0000113581 00000 n +0000111726 00000 n +0000113420 00000 n +0000111161 00000 n +0000101424 00000 n +0000110984 00000 n +0000025339 00000 n +0000024549 00000 n +0000025402 00000 n +0000025463 00000 n +0000025526 00000 n +0000025589 00000 n +0000025652 00000 n +0000025715 00000 n +0000025778 00000 n +0000025840 00000 n +0000025903 00000 n +0000025966 00000 n +0000026029 00000 n +0000026092 00000 n +0000026155 00000 n +0000026218 00000 n +0000026342 00000 n +0000026405 00000 n +0000026468 00000 n +0000026531 00000 n +0000026594 00000 n +0000026657 00000 n +0000026719 00000 n +0000026782 00000 n +0000026845 00000 n +0000026908 00000 n +0000034702 00000 n +0000031531 00000 n +0000027133 00000 n +0000031876 00000 n +0000032001 00000 n +0000032064 00000 n +0000032126 00000 n +0000032189 00000 n +0000032252 00000 n +0000032315 00000 n +0000032378 00000 n +0000032441 00000 n +0000032504 00000 n +0000032566 00000 n +0000032629 00000 n +0000032692 00000 n +0000032755 00000 n +0000032818 00000 n +0000032881 00000 n +0000032944 00000 n +0000033007 00000 n +0000033070 00000 n +0000033133 00000 n +0000033195 00000 n +0000033258 00000 n +0000031673 00000 n +0000033383 00000 n +0000033446 00000 n +0000033509 00000 n +0000033572 00000 n +0000033635 00000 n +0000033697 00000 n +0000033760 00000 n +0000033823 00000 n +0000033886 00000 n +0000033949 00000 n +0000034012 00000 n +0000034075 00000 n +0000034138 00000 n +0000034201 00000 n +0000034264 00000 n +0000034327 00000 n +0000034389 00000 n +0000034514 00000 n +0000034639 00000 n +0000045285 00000 n +0000042019 00000 n +0000034826 00000 n +0000042141 00000 n +0000042204 00000 n +0000042267 00000 n +0000042330 00000 n +0000042393 00000 n +0000042456 00000 n +0000042519 00000 n +0000042581 00000 n +0000042644 00000 n +0000042707 00000 n +0000042770 00000 n +0000042895 00000 n +0000042958 00000 n +0000043021 00000 n +0000043084 00000 n +0000043147 00000 n +0000043210 00000 n +0000043273 00000 n +0000043336 00000 n +0000043399 00000 n +0000043462 00000 n +0000043525 00000 n +0000043588 00000 n +0000043650 00000 n +0000043713 00000 n +0000043776 00000 n +0000043838 00000 n +0000043901 00000 n +0000043964 00000 n +0000044027 00000 n +0000044090 00000 n +0000044153 00000 n +0000044216 00000 n +0000044279 00000 n +0000044342 00000 n +0000044405 00000 n +0000044467 00000 n +0000044530 00000 n +0000044593 00000 n +0000044656 00000 n +0000044719 00000 n +0000044782 00000 n +0000044845 00000 n +0000044908 00000 n +0000044971 00000 n +0000045034 00000 n +0000045097 00000 n +0000045159 00000 n +0000045222 00000 n +0000051498 00000 n +0000049742 00000 n +0000045409 00000 n +0000049864 00000 n +0000049989 00000 n +0000050052 00000 n +0000050115 00000 n +0000050178 00000 n +0000050303 00000 n +0000050366 00000 n +0000050429 00000 n +0000050492 00000 n +0000050555 00000 n +0000050618 00000 n +0000050680 00000 n +0000050743 00000 n +0000050806 00000 n +0000050869 00000 n +0000050932 00000 n +0000050995 00000 n +0000051058 00000 n +0000051121 00000 n +0000051184 00000 n +0000051247 00000 n +0000051309 00000 n +0000051372 00000 n +0000051435 00000 n +0000194749 00000 n +0000059343 00000 n +0000056705 00000 n +0000051609 00000 n +0000056827 00000 n +0000056890 00000 n +0000056953 00000 n +0000057016 00000 n +0000057079 00000 n +0000057142 00000 n +0000057205 00000 n +0000057268 00000 n +0000057331 00000 n +0000057394 00000 n +0000057457 00000 n +0000057519 00000 n +0000057582 00000 n +0000057645 00000 n +0000057708 00000 n +0000057771 00000 n +0000057834 00000 n +0000057897 00000 n +0000057960 00000 n +0000058023 00000 n +0000058086 00000 n +0000058148 00000 n +0000058211 00000 n +0000058274 00000 n +0000058337 00000 n +0000058400 00000 n +0000058463 00000 n +0000058526 00000 n +0000058589 00000 n +0000058652 00000 n +0000058714 00000 n +0000058777 00000 n +0000058840 00000 n +0000058903 00000 n +0000058966 00000 n +0000059029 00000 n +0000059092 00000 n +0000059155 00000 n +0000059218 00000 n +0000059281 00000 n +0000069929 00000 n +0000066368 00000 n +0000059441 00000 n +0000066723 00000 n +0000066786 00000 n +0000066849 00000 n +0000066912 00000 n +0000066975 00000 n +0000067038 00000 n +0000067100 00000 n +0000067163 00000 n +0000067226 00000 n +0000067289 00000 n +0000067352 00000 n +0000067415 00000 n +0000067478 00000 n +0000067541 00000 n +0000067604 00000 n +0000067667 00000 n +0000067728 00000 n +0000067791 00000 n +0000067854 00000 n +0000067917 00000 n +0000067980 00000 n +0000068043 00000 n +0000068106 00000 n +0000068169 00000 n +0000068294 00000 n +0000066510 00000 n +0000068357 00000 n +0000068420 00000 n +0000068483 00000 n +0000068545 00000 n +0000068608 00000 n +0000068671 00000 n +0000068734 00000 n +0000068797 00000 n +0000068860 00000 n +0000068923 00000 n +0000068986 00000 n +0000069049 00000 n +0000069112 00000 n +0000069174 00000 n +0000069237 00000 n +0000069300 00000 n +0000069363 00000 n +0000069426 00000 n +0000069489 00000 n +0000069552 00000 n +0000069615 00000 n +0000069678 00000 n +0000069741 00000 n +0000069803 00000 n +0000069866 00000 n +0000070639 00000 n +0000070454 00000 n +0000070066 00000 n +0000070576 00000 n +0000075209 00000 n +0000074306 00000 n +0000070724 00000 n +0000074648 00000 n +0000074773 00000 n +0000074897 00000 n +0000075022 00000 n +0000075147 00000 n +0000074448 00000 n +0000081621 00000 n +0000079554 00000 n +0000075333 00000 n +0000079676 00000 n +0000079801 00000 n +0000079864 00000 n +0000079927 00000 n +0000079990 00000 n +0000080052 00000 n +0000080115 00000 n +0000080178 00000 n +0000080241 00000 n +0000080304 00000 n +0000080367 00000 n +0000080429 00000 n +0000080492 00000 n +0000080555 00000 n +0000080618 00000 n +0000080681 00000 n +0000080806 00000 n +0000080931 00000 n +0000080994 00000 n +0000081057 00000 n +0000081120 00000 n +0000081180 00000 n +0000081243 00000 n +0000081306 00000 n +0000081369 00000 n +0000081432 00000 n +0000081495 00000 n +0000081558 00000 n +0000089602 00000 n +0000087161 00000 n +0000081758 00000 n +0000087841 00000 n +0000087904 00000 n +0000087967 00000 n +0000087319 00000 n +0000087494 00000 n +0000087667 00000 n +0000088030 00000 n +0000088093 00000 n +0000088156 00000 n +0000088219 00000 n +0000088282 00000 n +0000088345 00000 n +0000088408 00000 n +0000088470 00000 n +0000088533 00000 n +0000088596 00000 n +0000088659 00000 n +0000088722 00000 n +0000088785 00000 n +0000088848 00000 n +0000088911 00000 n +0000088974 00000 n +0000089037 00000 n +0000089099 00000 n +0000089162 00000 n +0000089225 00000 n +0000089351 00000 n +0000089414 00000 n +0000089477 00000 n +0000089540 00000 n +0000194866 00000 n +0000096833 00000 n +0000094573 00000 n +0000089752 00000 n +0000094695 00000 n +0000094758 00000 n +0000094821 00000 n +0000094947 00000 n +0000095010 00000 n +0000095073 00000 n +0000095136 00000 n +0000095262 00000 n +0000095325 00000 n +0000095388 00000 n +0000095451 00000 n +0000095514 00000 n +0000095577 00000 n +0000095639 00000 n +0000095702 00000 n +0000095765 00000 n +0000095828 00000 n +0000095891 00000 n +0000095954 00000 n +0000096017 00000 n +0000096143 00000 n +0000096204 00000 n +0000096267 00000 n +0000096330 00000 n +0000096393 00000 n +0000096519 00000 n +0000096582 00000 n +0000096645 00000 n +0000096708 00000 n +0000096770 00000 n +0000099438 00000 n +0000098359 00000 n +0000096957 00000 n +0000098684 00000 n +0000098810 00000 n +0000098501 00000 n +0000098873 00000 n +0000098936 00000 n +0000098999 00000 n +0000099062 00000 n +0000099124 00000 n +0000099187 00000 n +0000099250 00000 n +0000099312 00000 n +0000099375 00000 n +0000099536 00000 n +0000111426 00000 n +0000113821 00000 n +0000113797 00000 n +0000115610 00000 n +0000115585 00000 n +0000135325 00000 n +0000151621 00000 n +0000163948 00000 n +0000172614 00000 n +0000194140 00000 n +0000194959 00000 n +0000195037 00000 n +0000197819 00000 n +0000208006 00000 n +0000208045 00000 n +0000208083 00000 n +0000208213 00000 n +trailer +<< +/Size 624 +/Root 622 0 R +/Info 623 0 R +/ID [<67FDFAA0CD9D108A567B8B97804AD5DB> <67FDFAA0CD9D108A567B8B97804AD5DB>] +>> +startxref +208484 +%%EOF Added: trunk/docs/cookbook/cookbook-asciidoc.txt =================================================================== --- trunk/docs/cookbook/cookbook-asciidoc.txt (rev 0) +++ trunk/docs/cookbook/cookbook-asciidoc.txt 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,891 @@ +// To compile use: asciidoc -a toc -n cookbook-asciidoc.txt + + +Swift Cookbook +============== +Swift team +v0.92, March 2011 + +Overview +-------- +This cookbook covers various recipes involving setting up and running Swift under diverse +configurations based on the application requirements and the underlying +infrastructures. The Swift system comprises of SwiftScript language and the +Swift runtime system. For +introductory material, consult the Swift tutorial found +link:http://www.ci.uchicago.edu/swift/guides/tutorial.php[here]. + +Swift Basics +------------ + +Installation +~~~~~~~~~~~~ + +This section takes you through the installation of the Swift system on your +computer. We will start with the prerequisites as explained in the subsequent +section. + +Prerequisites +^^^^^^^^^^^^^^ +.Check your Java +Swift is a Java application. Make sure you are running Java version 5 or higher. You +can make sure you have Java in your $PATH (or $HOME/.soft file depending upon +your environment) + +Following are the possible ways to detect and run Java: + +---- +$ grep java $HOME/.soft +#+java-sun # Gives you Java 5 ++java-1.6.0_03-sun-r1 +$ which java +/soft/java-1.6.0_11-sun-r1/bin/java +$ java -version +java version "1.6.0_11" +Java(TM) SE Runtime Environment (build 1.6.0_11-b03) +Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode) +---- + +Setting up to run Swift +~~~~~~~~~~~~~~~~~~~~~~~~ +This is simple. We will be using a pre-compiled version of Swift that can be +downloaded from link:http://www.ci.uchicago.edu/swift/downloads/index.php[here]. Download and untar the latest precompiled version as follows: + +---- +$ tar xf swift-0.92.1.tar.gz +---- + +Environment Setup +^^^^^^^^^^^^^^^^^^ + +The examples were tested with Java version 1.6. Make sure you do not already +have Swift in your PATH. If you do, remove it, or remove any +swift or @swift +lines from your $HOME/.soft or $HOME/.bash_profile file. Then do: + +---- +PATH=$PATH:/path/to/swift/bin +---- + +Note that the environment will be different when using Swift from prebuilt distribution (as above) and trunk. The PATH setup when using swift from trunk would be as follows: + +---- +PATH=$PATH:/path/to/swift/dist/swift-svn/bin +---- + +WARNING: Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you +fully understand how these will affect Swift's execution. + +To execute your Swift script on a login host (or "localhost") use +the following command: + +---- +swift -tc.file tc somescript.swift +---- + +Setting transformation catalog +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +The transformation catalog lists where application executables are located on +remote sites. + +By default, the site catalog is stored in etc/tc.data. This path can be +overridden with the tc.file configuration property, either in the Swift +configuration file or on the command line. + +The format is one line per executable per site, with fields separated by tabs +or spaces. + +Some example entries: + +---- +localhost echo /bin/echo INSTALLED INTEL32::LINUX null +TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:00:10" +---- +The fields are: _site_, _transformation-name_, _executable-path_, _installation-status_, _platform_, and _profile_ entries. + +The _site_ field should correspond to a site name listed in the sites catalog. + +The _transformation-name_ should correspond to the transformation name used in a +SwiftScript app procedure. + +The _executable-path_ should specify where the particular executable is located +on that site. + +The _installation-status_ and _platform_ fields are not used. Set them to +**INSTALLED** and **INTEL32::LINUX** respectively. + +The _profiles_ field should be set to null if no profile entries are to be +specified, or should contain the profile entries separated by semicolons. + +Setting swift configuration +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Many configuration properties could be set using the Swift configuration file. +We will not cover them all in this section. see +link:http://www.ci.uchicago.edu/swift/guides/userguide.php#engineconfiguration[here] for details. In this section we will cover a simple configuration file with the most basic properties. + +---- +# A comment +wrapperlog.always.transfer=true +sitedir.keep=true +execution.retries=1 +lazy.errors=true +status.mode=provider +use.provider.staging=true +provider.staging.pin.swiftfiles=false +clustering.enabled=false +clustering.queue.delay=10 +clustering.min.time=86400 +foreach.max.threads=100 +provenance.log=true +---- + +Setting sites.xml +^^^^^^^^^^^^^^^^^^ +sites.xml specifies details of the sites that Swift can run on. Following is +an example of a simple sites.xml file entry for running Swift on local +environment: + +[xml] +source~~~~~~ + + + +/var/tmp +.07 +100000 + +source~~~~~~ + +First SwiftScript +~~~~~~~~~~~~~~~~~ +Your first SwiftScript +Hello Swift-World! + +A good sanity check that Swift is set up and running OK locally is this: + +---- +$ which swift + +/home/wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift + +$ echo 'trace("Hello, Swift world!");' >hello.swift + +$ swift hello.swift + +Swift svn swift-r3202 cog-r2682 + +RunID: 20100115-1240-6xhzxuz3 + +Progress: + +SwiftScript trace: Hello, Swift world! + +Final status: + +$ +---- +A good first tutorial in using Swift is at: +http://www.ci.uchicago.edu/swift/guides/tutorial.php. Follow the steps in that +tutorial to learn how to run a few simple scripts on the login host. + +second SwiftScript +~~~~~~~~~~~~~~~~~~~ +Following is a more involved Swift script. +[java] +source~~~~~~~ +type file; + +app (file o) cat (file i) +{ + cat @i stdout=@o; +} + +file out[]; + +foreach j in [1:@toint(@arg("n","1"))] { + + file data<"data.txt">; + + out[j] = cat(data); +} +source~~~~~~~ + +Swift Commandline Options +~~~~~~~~~~~~~~~~~~~~~~~~~ +A description of Swift Commandline Options + +Also includes a description of Swift inputs and outputs. + +What if Swift hangs +~~~~~~~~~~~~~~~~~~~ +Owing to its highly multithreaded architecture it is often the case that the +underlying java virtual machine gets into deadlock situations or Swift hangs +because of other complications in its threaded operations. Under such +situations, Swift _hang-checker_ chips in and resolves the situation. + +. how to use the information to identify and correct the deadlock. + +. How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines? + +. The current Hang Checker output is actually *very* nice and useful already: + +---- +Registered futures: +Rupture[] rups Closed, 1 elements, 0 listeners +Variation vars - Closed, no listeners +SgtDim sub - Open, 1 listeners +string site Closed, no listeners +Variation[] vars Closed, 72 elements, 0 listeners +---- + +Resuming a stopped or crashed Swift Run +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +I had a .rlog file from a Swift run that ran out of time. I kicked it off +using the -resume flag described in section 16.2 of the Swift User Guide and +it picked up where it left off. Then I killed it because I wanted to make +changes to my sites file. + +---- +. . . +Progress: Selecting site:1150 Stage in:55 Active:3 Checking status:1 +Stage out:37 Finished in previous run:2462 Finished successfully:96 +Progress: Selecting site:1150 Stage in:55 Active:2 Checking status:1 +Stage out:38 Finished in previous run:2462 Finished successfully:96 +Cleaning up... +Shutting down service at https://192.5.86.6:54813 +Got channel MetaChannel: 1293358091 -> null ++ Done +Canceling job 9297.svc.pads.ci.uchicago.edu +---- + +No new rlog file was emitted but it did recognize the progress that had been +made, the 96 tasks that finished sucessfully above and resumed from 2558 tasks +finished. + +---- +[nbest at login2 files]$ pwd +/home/nbest/bigdata/files +[nbest at login2 files]$ +~wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift \ +> -tc.file tc -sites.file pbs.xml ~/scripts/mcd12q1.swift -resume +> mcd12q1-20100310-1326-ptxe1x1d.0.rlog +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified +locally) +RunID: 20100311-1027-148caf0a +Progress: +Progress: uninitialized:4 +Progress: Selecting site:671 Initializing site shared directory:1 Finished +in previous run:1864 +Progress: uninitialized:1 Selecting site:576 Stage in:96 Finished in +previous run:1864 +Progress: Selecting site:1150 Stage in:94 Submitting:2 Finished in +previous run:2558 +Progress: Selecting site:1150 Stage in:94 Submitted:2 Finished in previous +run:2558 +Progress: Selecting site:1150 Stage in:93 Submitting:1 Submitted:2 +Finished in previous run:2558 +Progress: Selecting site:1150 Stage in:90 Submitting:1 Submitted:5 +Finished in previous run:2558 +Progress: Selecting site:1150 Stage in:90 Submitted:5 Active:1 Finished +in previous run:2558 +---- + + +From Neil: A comment about that section of the user guide: It says "In order +to restart from a restart log file, the -resume logfile argument can be used +after the SwiftScript? program file name." and then puts the -resume logfile +argument before the script file name. I'm sure the order doesn't matter but +the contradiction is confusing. + +Notes to add (from Mike): + +- explain what aspects of a Swift script make it restartable, and which + aspects are notrestartable. Eg, if your mappers can return different data at +different times, what happens? What other non-determinsitc behavior would +cause unpredictable, unexpected, or undesired behavior on resumption? + +- explain what changes you can make in the execution environment (eg + increasing or reducing CPUs to run on or throttles, etc); fixing tc.data +entries, env vars, or apps, etc. + +- note that resume will again retry failed app() calls. Explain if the retry + count starts over or not. + +- explain how to resume after multiple failures and resumes - i.e. if a .rlog + is generated on each run, which one should you resume from? Do you have a +choice of resuming from any of them, and what happens if you go backwards to +an older resume file? + +- whap happens when you kill (eg with ^C) a running swift script? Is the + signal caught, and the resume file written out at that point? Or written out +all along? (Note case in which script ws running for hours, then hit ^C, but +resume fie was short (54 bbytes) and swift shows no sign of doing a resume? +(It silently ignored resume file instead of acknowleging that it found one +with not useful resume state in it???) Swift should clearly state that its +resuming and what its resume state is. + ++swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial +run\]+ + + +Passing an array to swift? +~~~~~~~~~~~~~~~~~~~~~~~~~~ +Arrays can be passed to Swift in one of the following ways: + +. You can write the array to a file and read in in swift using +readData (or readData2). +. Direct the array into a file (possibly with a "here document" which expands the array) and then read the file in Swift with readData() or process it with a Swift app() function? +. You can use @strsplit on a comma separated command line arg and that works well for me. + +Mappers +^^^^^^^^ +SimpleMapper + +---- +$ cat swiftapply.swift +---- + +[java] +source~~~~ +type RFile; +trace("hi 1"); +app (RFile result) RunR (RFile rcall) +{ + RunR @rcall @result; +} +trace("hi 2"); +RFile rcalls[] ; +RFile results[] ; +trace("start"); +foreach c, i in rcalls { + trace("c",i, at c); + trace("r",i, at filename(results[i])); + results[i] = RunR(c); +} +source~~~~ + +---- +$ ls calldir resdir +calldir: +rcall.1.Rdata rcall.2.Rdata rcall.3.Rdata rcall.4.Rdata +resdir: +result.1.Rdata result.2.Rdata result.3.Rdata result.4.Rdata +$ +---- + +Notes: + +how the .'s match +prefix and suffix dont span dirs +intervening pattern must be digits +these digits become the array indices +explain how padding= arg works & helps (including padding=0) +figure out and explain differences between simple_mapper and +filesys_mapper +FIXME: Use the "filesys_mapper" and its "location=" parameter to map the +input data from /home/wilde/bigdata/* + +Abbreviations for SingleFileMapper +Notes: + +within <> you can only have a literal string as in <"filename">, not an +expression. Someday we will fix this to make <> accept a general expression. +you can use @filenames( ) (note: plural) to pull off a list of filenames. + +writeData() + +example here + +---- +$ cat writedata.swift +---- + +[java] +source~~~~ +type file; + +file f <"filea">; +file nf <"filenames">; +nf = writeData(@f); +source~~~~ + +---- +$ swift writedata.swift +Swift svn swift-r3264 (swift modified locally) cog-r2730 (cog modified +locally) +RunID: 20100319-2002-s9vpo0pe +Progress: +Final status: +$ cat filenames +filea$ +---- + +StructuredRegexpMapper +IN PROGRESS This mapper can be used to base the mapped filenames of an output +array on the mapped filenames of an existing array. landuse outputfiles[] +; + +Use the undocumented "structured_regexp_mapper" to name the output +filenames based on the input filenames: + +For example: + +---- +login2$ ls /home/wilde/bigdata/data/sample +h11v04.histogram h11v05.histogram h12v04.histogram h32v08.histogram +h11v04.tif h11v05.tif h12v04.tif h32v08.tif +login2$ + +login2$ cat regexp2.swift +type tif; +type mytype; + +tif images[]; + +mytype of[] ; + +foreach image, i in images { + trace(i, at filename(images)); + trace(i, at filename(of[i])); +} +login2$ + +login1$ swift regexp2.swift +Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified +locally) + +RunID: 20100310-1105-4okarq08 +Progress: +SwiftScript trace: 1, output/myfile.h11v04.mytype +SwiftScript trace: 2, home/wilde/bigdata/data/sample/h11v05.tif +SwiftScript trace: 3, home/wilde/bigdata/data/sample/h12v04.tif +SwiftScript trace: 0, output/myfile.h32v08.mytype +SwiftScript trace: 0, home/wilde/bigdata/data/sample/h32v08.tif +SwiftScript trace: 3, output/myfile.h12v04.mytype +SwiftScript trace: 1, home/wilde/bigdata/data/sample/h11v04.tif +SwiftScript trace: 2, output/myfile.h11v05.mytype +Final status: +login1$ +---- + +Coasters +-------- +Coasters were introduced in Swift v0.6 as an experimental feature. In many +applications, Swift performance can be greatly enhanced by the use of CoG +coasters. CoG coasters provide a low-overhead job submission and file transfer +mechanism suited for the execution of short jobs (on the order of a few +seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters. +//**Include neat diagrams.** + +Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were: + +[xml] +source~~~~ + +CI-CCR000013 + + + + + + +pbs.aprun +pbs.mpp=true + + +24 +100000 + +100 +100 + +20 +5 +5 +20.00 +10000 +source~~~~ + +The following table briefly describes the elements on the coasters setup: +[width="70%", cols="^3,10", options="header"] +|============================================================================================= +|profile key | brief description +|slots | How many maximum LRM jobs/worker blocks are allowed +|workersPerNode | How many coaster workers to run per execution node +|nodeGranularity | Each worker block uses a number of nodes that is a multiple of this number +|lowOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are 1s long +|highOverallocation | How many times larger than the job walltime should a block's walltime be if all jobs are infinitely long +|workersPerNode | How many coaster workers to run per execution node reserve How many seconds to reserve in a block's walltime for starting/shutdown operations +|maxnodes | The maximum number of nodes allowed in a block +|maxtime | The maximum number of walltime allowed for a block coaster service +|jobThrottle |the number of concurrent jobs allowed on a site +|============================================================================================== + +// +//For Beginners +//~~~~~~~~~~~~~~ +//Coasters for beginners. Usage of existing, prebuilt templates. +// +//For Intermediate Users +//~~~~~~~~~~~~~~~~~~~~~~~ +//Coasters for intermediate users. +// +//Using gensites +//^^^^^^^^^^^^^^^ +//Usage of gensites to generate your own sites +//configurations. +// +// +// + +For Advanced Users +~~~~~~~~~~~~~~~~~~ + +//Coasters for advanced users. Getting your hands dirty. + +One of the main reason that one would initially deviate from coaster +defaults into more complex pool entries is to force jobs to fit into some +site-imposed constraint. For instance a typical submission to the experimental +queue requires a user to request upto 3 nodes for under 1 hour. This setup +could be achieved with a careful tuning of coaters parameters. + +//How to run Swift under different Coasters configurations +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +// +//Manual +//^^^^^^^ +//Todo +// +//Passive +//^^^^^^^^ +//Todo +// +//Persistent +//^^^^^^^^^^^ +//Todo +// +//Summary of Differences Between different Coaster types +//~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +//A tabular representations of highlights of different coaster setups +// +// +//Data Management +// + +Coaster providers: local, ssh, pbs +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Settings and examples for different coaster providers mechanisms. + + + +Swift on Diverse Infrastructures +--------------------------------- + +Beagle +~~~~~~ +Swift is now installed on Beagle as a module. Swift supports a Coasters based, +computing environment for Beagle. A detailed Swift documentation is maintained +[[http://www.ci.uchicago.edu/swift/docs/index.php][here]]. To get started +with Swift on Beagle follow the steps outlined below: + +*step 1.* Load the Swift module on Beagle as follows: +module load swift+ + +*step 2.* Create and change to a directory where your Swift related work will +stay. (say, +mkdir swift-lab+, followed by, +cd swift-lab+) + +*step 3.* To get started with a simple example running +/bin/cat+ to read an input file +data.txt+ and write to an output file +f.nnn.out+, copy the folder at +/home/ketan/labs/catsn+ to the above directory. (+cp -r /home/ketan/catsn .+ followed by +cd catsn+). + +*step 4.* In the sites file: +beagle-coaster.xml+, make the following two +changes: *1)* change the path of +workdirectory+ to your preferred location +(say to +/lustre/beagle/$USER/swift-lab/swift.workdir+) and *2)* Change the +project name to your project (+CI-CCR000013+) . The workdirectory will contain +execution data related to each run, e.g. wrapper scripts, system information, +inputs and outputs. + +*step 5.* Run the example using following commandline (also found in run.sh): ++swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1+ +. You can further change the value of +-n+ to any arbitrary number to run that +many number of concurrent +cat+ + +*step 6.* Check the output in the generated +outdir+ directory (+ls outdir+) + +Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes +will get fast prioritized execution. Good for small tests + +// +//Intrepid-BG/P +//~~~~~~~~~~~~~ +//Swift on Intrepid-BG/P +// + +PADS +~~~~ +Swift on PADS +To execute your Swift script on the PADS cluster use this command: + +---- +swift -tc.file tc -sites.file pbs.xml modis.swift +---- +where the contents of a simple pbs.xml sites file could be: +[xml] +source~~~~ + + + + fast + 00:05:00 + 10000 + .10 + + /home/you/swiftwork + + +source~~~~ + +OSG +~~~ +This section describes how to get Swift running on the OSG Grid. We will use a +manual coaster setup to get Swift running on OSG. + +.Coaster setup on OSG +The following figure shows an abstract scheme for the manual coasters setup on +OSG. + +image::figures/coaster_setup.png[Coaster setup] + +In the following steps, we will go through the process of manually setting +//Swift on OSG +// + +Bionimbus +~~~~~~~~~ +This section explains a step by step procedure on getting Swift running on the +Bionimbus cloud. We will use the _manual_ _coasters_ configuration on the +Bionimbus cloud. + +**step1.** Connect to the gateway (ssh gatewayx.lac.uic.edu) + +**step2.** Start a virtual machine (euca-run-instances -n 1 -t m1.small +emi-17EB1170) + +**step3.** Start the coaster-service on gateway ++coaster-service -port 1984 -localport 35753 -nosec+ + +**step4.** Start the Swift-script from the gateway using normal Swift commandline + ++swift -config cf -tc.file tc -sites.file sites.xml yourscript.swift -aparam=999+ + +.cf +---- +wrapperlog.always.transfer=true +sitedir.keep=true +execution.retries=1 +lazy.errors=true +status.mode=provider +use.provider.staging=true +provider.staging.pin.swiftfiles=false +foreach.max.threads=100 +provenance.log=true +---- + +.tc +---- +localhost modftdock /home/ketan/swift-labs/bionimbus-coaster-modftdock/app/modftdock.sh null null GLOBUS::maxwalltime="1:00:00" +---- + +(See below for a sample sites.xml for this run) + +**step5.** Connect back to gateway from virtual machines using reverse ssh tunneling as follows: + +.From the gateway prompt + ++ssh -R *:5000:localhost:5000 root at 10.101.8.50 sleep 999+ + +WHERE: +*=network interface, should remain the same on all cases + +localhost=the gateway host, should remain the same + +5000(LEFT OF localhost)=the port number on localhost to listen to **THIS WILL +vary depending upon which port you want to listen to + +5000(RIGHT OF localhost)=the port on target host that you want to forward + +root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will +vary based on what ip you get for your Virtual Machine instance + +#On anywhere as long as provide the correct callback uri: here the +"http://140.221.9.110:42195" is the callback uri of previous ones + +**step6.** Start the worker from the virtual machine ++worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the +coaster service is listening to the workers+ + +.sites.xml for the above run + +[xml] +source~~~~ + + + + passive + + 4 + 10000 + 100 + 100 + 100 + 1 + 10 + 25.00 + 10000 + proxy + + /home/ketan/swift-labs/bionimbus-coaster-modftdock/swift.workdir + + +source~~~~ + +//Magellan +//~~~~~~~~ +//Swift on Magellan +// + +Debugging Swift +--------------- +Swift errors are logged in several places: + +. All text from standard output and standard error produced by running the +swift command +. The .log file from this run. It will be named swiftscript.uniqueID.log +where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. +. $HOME/.globus/coasters directory on remote machines on which you are +running coasters +. $HOME/.globus/scripts directory on the host on which you run the Swift +command, when swift is submitting to a local scheduler (Condor, PBS, SGE, +Cobalt) +. $HOME/.globus/??? on remote systems that you access via Globus + + +Log Processing +--------------- + +To properly generate log plots, you must enable VDL/Karajan logging. Make sure +log4.properties contains: +---- +log4j.logger.swift=DEBUG +log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG +---- + +Make a basic load plot from Coasters Cpu log lines +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +.Generate the log (may set log4j.logger.swift=INFO for this one) +(assuming the log is titled swift-run.log) + +.Convert the log times to Unix time + +---- +./iso-to-secs < swift-run.log > swift-run.time +---- + +.Make the start time file (this contains the earliest timestamp) + +---- +make LOG=swift-run.log start-time.tmp +---- + +or + +---- +extract-start-time swift-run.log > start-time.tmp +---- + +.Normalize the transition times + +---- +./normalise-event-start-time < swift-run.time > swift-run.norm +---- + +.Build up a load data file: + +---- +./cpu-job-load.pl < swift-run.norm > load.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh load.cfg load.eps load.data +---- + +Make a basic job completion plot from Coasters Cpu log lines +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +.Same as above, but, build up a completed data file: + +---- +./cpu-job-completed.pl < swift-run.norm > completed.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh completed.cfg completed.eps completed.data +---- + +Make a basic Block allocation plot from Coasters Block log lines +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Same as above, but: + +.Build up a block allocation data file: + +---- +./block-level.pl < swift-run.norm > blocks.data +---- + +.Plot with the JFreeChart-based plotter in usertools/plotter: + +---- +lines.zsh blocks.{cfg,eps,data} +---- + +Problem Reporting +~~~~~~~~~~~~~~~~~ +When reporting problems to swift-user at ci.uchicago.edu, please attach the +following files and information: + +. tc.data and sites.xml (or whatever you named these files) + +. your .swift source file and any .swift files it imports + +. any external mapper scripts called by your .swift script + +. all text from standard output and standard error produced by running the +swift command + +. The .log file from this run. It will be named swiftscript.uniqueID.log + +. where "swiftscript" is the name of your *.swift script source file, and +uniqueID is a long unique id which starts with the date and time you ran the +swift command. + +. The swift command line you invoked + +. Any swift.properties entries you over-rode ($HOME/.swift/swift.properties, +-config.file argument properties file, any changes to etc/swift.proerties from +your swift distribution) + +. Which swift distribution you are running (release; svn revisions; other +local changes you mave have made or included) + + Deleted: trunk/docs/log-processing.xml =================================================================== --- trunk/docs/log-processing.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/log-processing.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,162 +0,0 @@ - - - - -
    - - Swift log processing tools - Source control $LastChangedRevision$ - - -
    - Overview - -There is a package of Swift log processing utilties. - - -
    -
    Prerequisites - -gnuplot 4.0, gnu m4, gnu textutils, perl - - -
    -
    Web page about a run - - -swift-plot-log /path/to/readData-20080304-0903-xgqf5nhe.log - -This will create a web page, report-readData-20080304-0903-xgqf5nhe -If the above command is used before a run is completed, the web page will -report information about the workflow progress so far. - - -
    -
    CEDPS logs - -The log processing tools can output transition streams in -CEDPS logging format: - -swift-plot-log /path/to/readData-20080304-0903-xgqf5nhe.log execute.cedps - - -
    -
    Event/transition channels - -Various event channels are extracted from the log files and made available -as .event and .transition files. -These roughly correspond to processes within the Swift runtime environment. - - These streams are then used to provide the data for the various -output formats, such as graphs, web pages and CEDPS log format. -The available streams are: - - - - Stream nameDescription - - executeSwift procedure invocations - execute2individual execution attempts - kickstartkickstart records (not available as transitions) - karatasks karajan level tasks, available as transitions (there are also four substreams karatasks.FILE_OPERATION, karatasks.FILE_TRANSFER and karatasks.JOB_SUBMISSION available as events but not transitions) - workflowa single event representing the entire workflow - dostageinstage-in operations for execute2s - dostageoutstage-out operations for execute2s - - -
    - -
    - -Streams are generated from their source log files either as .transitions -or .event files, for example by swift-plot-log whatever.log foo.event. - - -Various plots are available based on different streams: - - - - Makefile targetDescription - - foo.pngPlots the foo event stream - foo-total.pngPlots how many foo events are in progress at any time - foo.sorted-start.pngPlot like foo.png but ordered by start time - - -
    - -
    - -Text-based statistics are also available with make foo.stats. - - -Event streams are nested something like this: - - -workflow - execute - execute2 - dostagein - karatasks (fileops and filetrans) - clustering (optional) - karatasks (execution) - cluster-log (optional) - wrapper log (optional) - kickstart log - dostageout - karatasks (fileops and filetrans) - - - -
    -
    Internal file formats -The log processing code generates a number of internal files that -follow a standard format. These are used for communication between the -modules that parse various log files to extract relevant information; and -the modules that generate plots and other summary information. - -need an event file format of one event per line, with that line -containing start time and duration and other useful data. - -col1 = start, col2 = duration, col3 onwards = event specific data - for -some utilities for now should be column based, but later will maybe -move to attribute based. - -between col 1 and col 2 exactly one space -between col 2 and col 3 exactly one space - -start time is in seconds since unix epoch. start time should *not* be -normalised to start of workflow - -event files should not (for now) be assumed to be in order - -different event streams can be stored in different files. each event -stream should use the extension .event - - - -.coloured-event files -===================== -third column is a colour index -first two columns as per .event (thus a coloured-event is a specific -form of .event) - - -
    - -
    hacky scripts -There are a couple of hacky scripts that aren't made into proper -commandline tools. These are in the libexec/log-processing/ directory: - - - ./execute2-status-from-log [logfile] - lists every (execute2) job and its final status - - ./execute2-summary-from-log [logfile] - lists the counts of each final job status in log - - -
    -
    - - Deleted: trunk/docs/plot-tour.xml =================================================================== --- trunk/docs/plot-tour.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/plot-tour.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,311 +0,0 @@ - - - - -
    - - Swift log plotting and the some internal mechanics of Swift - - -
    - Overview - -This document attempts to explain some of the meaning of the Swift -log-processing plots, giving an explanation of how some of Swift's -execution mechanism works and of some of the terminology used. - -
    - -
    'execute' - SwiftScript app {} block invocations - - -When a SwiftScript program invokes a application procedure (one with an -app {} block), an 'execute' appears in the log file in START state. When -all attempts at execution have finished (either successfully or unsuccessfully) -then the execute will go into END_SUCCESS or END_FAILURE state. A workflow -is successful if and only if all invocations end in END_SUCCESS. - - - -The execute states represent progress -through the karajan procedure defined in -libexec/execute-default.k. - -State changes for execute logs are defined by karajan log calls throughout -this file. - - - -An execute consists of multiple attempts to perform -execute2s, with retries and replication -as appropriate. Retries and replication are not exposed through the states -of 'execute's. - - -Executes are uniquely identified within a run by their karajan thread ID, -which is present in the log files as the thread= parameter on execute -log messsages. - - - -Here is a simple SwiftScript program which runs a foreach loop (few.swift): - -p() { - app { - sleep "10s"; - } -} - -foreach i in [1:8] { - p(); -} - - - - - -Using the swift-plot-log from the log processing module, -this graph gets generated to summarise execute state transitions: - - - - - -In this graph, the forloop calls p() eight times. Because there are no -dependencies between those eight invocations, they are all invoked at the same -time, around 1s into the run. This is show on the graph by the JOB_START line -going from zero up to eight at around x=1s. As time passes, the sleep jobs -complete, and as they do so the number of jobs in END_SUCCESS state increases. -When all eight jobs are in END_SUCCESS state, the run is over. - -Here is a program with some data dependencies between invocations (dep.swift): - - -$ cat dep.swift -type file; - -p(file f) { - app { - sleep "10s"; - } -} - -(file o) q() { - app { - touch @o; - } -} - -file intermediate = q(); -p(intermediate); - - - - - -Here is a plot of the execute states for this program: - - - - -In this run, one invocation starts (q()) fairly quickly, -but the other invocation (of p()) does not - instead, it does not start until -approximately the time that the q() invocation has reached END_SUCCESS. - - - -Finally in this section on 'execute', here is a demonstration of how the above -two patterns fit together in one program (few2.swift: - -type file; - -(file o) p(file i) { - app { - sleepcopy @i @o; - } -} - -file input <"input">; -file output[]; - -foreach i in [1:8] { - file intermediate; - intermediate = p(input); - output[i] = p(intermediate); -} - - - - - -In total the program has 16 invocations of p(), dependent on each other in -pairs. The dependencies can be plotted like this: - - -$ swift -pgraph few2.dot few2.swift -$ dot -Tpng -o few2.png few2.dot - - -yielding this graph: - - - - - -When this program is run, the first row of 8 invocations can all start at the -beginning of the program, because they have no dependencies (aside from on -the input file). This can be seen around t=4 when the start line jumps up to 8. -The other 8 invocations can only begin when the invocations they are dependent -on have finished. This can be seen in the graph - every time one of the first -invocations reaches END_SUCCESS, a new invocation enters START. - - - - -
    -
    execute2 - one attempt at running an execute - -An execute2 is one attempt to execute an app procedure. execute2s are invoked -by execute, once for each retry or replication -attempt. - -The states of an execute2 represent progress through the execute2 karajan -procedure defined in libexec/vdl-int.k - - - -Before an execute2 makes its first state log entry, it chooses a site to run on. -Then at the start of file stage-in, the execute2 goes into THREAD_ASSOCIATION -state. Once stagein is completed, the JOB_START state is entered, indicating -that execution of the job executable will now be attempted. Following that, -STAGING_OUT indicates that the output files are being staged out. If everything -is completed successfully, the job will enter JOB_END state. - -There are two exceptions to the above sequence: JOB_CANCELLED indicates that -the replication mechanism has cancelled this job because a different execute2 -began actual execution on a site for the same execute. APPLICATION_EXCEPTION -indicates that there was an error somewhere in the attempt to stage in, -actually execute or stage out. If a job goes into APPLICATION_EXCEPTION state -then it will generally be retried (up to a certain number of times defined -by the "execution.retries" parameter) by the containing execute. - - - -In this example, we use a large input file to slow down file staging so that -it is visible on an execute2 graph (big-files.swift): - -type file; - -(file o) p(file i) { - app { - sleepcopy @i @o; - } -} - -file input <"biginput">; -file output[]; - -foreach i in [1:8] { - output[i] = p(input); -} - - - - - - - -There is an initial large input file that must be staged in. This causes the first -jobs to be in stagein state for a period of time (the space between the -ASSOCIATED and JOB_START lines at the lower left corner of the graph). All -invocations share a single input file, so it is only staged in once and -shared between all subsequent invocations - once the file has staged in at the -start, there is no space later on between the ASSOCIATED and JOB_START lines -because of this. - - -Conversely, each invocation generates a large output file without there being -any sharing. Each of those output files must be staged back to the submit -side, which in this application takes some time. This can be seen by the large -amount of space between the STAGING_OUT and JOB_END lines. - - -The remaining large space on the graph is between the JOB_START and STAGING_OUT -lines. This represents the time taken to queue and execute the application -executable (and surrounding Swift worker-side wrapper, which can sometimes -have non-negligable execution times - this can be seen in the -info section). - - -
    - -
    wrapper info logs - -When a job runs, it is wrapped by a Swift shell script on the remote site that -prepares the job environment, creating a temporary directory and moving -input and output files around. Each wrapper invocation corresponds to a single -application execution. For each invocation of the wrapper, a log file is created. -Sometimes that log file is moved back to the submission side (when there is -an error during execution, or when the setting -wrapper.always.transfer=true -is set) and placed in a *.d/ directory corresponding in -name to the main log file. - - - -The states of the info logs represent progress through the wrapper -script, libexec/wrapper.sh. - - - -For the same run of big-files.swift as shown in the -execute2 section, here is a plot of states -in wrapper info log files: - - - - - - -The trace lines on this graph fit entirely within the space between JOB_START -and STAGING_OUT on the corresponding execute2 graph, because the Swift worker node -wrapper script does not run until the submit side of Swift has submitted a -job for execution and that job has begun running. - - - -Many of the lines on this plot are very close together, because many of the -operations take minimal time. The main space between lines is between -EXECUTE and EXECUTE_DONE, where the actual application executable is executing; -and between COPYING_OUTPUTS and RM_JOBDIR, where the large output files are -copied from a job specific working directory to the site-specific shared -directory. It is quite hard to distinguish on the graph where overlapping -lines are plotted together. - - - -Note also that minimal time is spent copying input files into the job-specific -directory in the wrapper script; that is because in this run, the wrapper -script is using the default behaviour of making symbolic links in the job-specific -directory; symbolic links are usually cheap to create compared to copying file -content. However, if the SWIFT_JOBDIR_PATH parameter is set, then Swift will -copy the input file to the specified job directory instead of linking. This -will generally result in much more time being spent preparing the job directory -in the Swift wrapper, but in certain circumstances this time is overwhelmingly -offset by increased performance of the actual application executable (so on -this chart, this would be seen as an increased job directory preparation time, -but a reduced-by-more application executable time). - - - -
    - -
    Relation of logged entities to each other -Here is a simple diagram of how some of the above log channels along -with other pieces fit together: - - -
    - -
    - Deleted: trunk/docs/provenance.xml =================================================================== --- trunk/docs/provenance.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/provenance.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,2592 +0,0 @@ - - - - -
    -provenance working notes, benc -$Id$ -
    Goal of this present work - -The goal of the work described in this document is to investigate -retrospective provenance and -metadata handling in Swift, with an emphasis -on effective querying of the data, rather than on collection of the data. - - - -The motivating examples are queries of the kinds discussed in section 4 of -'Applying the Virtual Data Provenance Model'; -the queries and metadata in the First Provenance Challenge; and the metadata database used by -i2u2 cosmic. - - - -I am attempting to scope this so that it can be implemented in a few -months; more expensive features, though desirable, are relegated the the -'What this work does not address' section. Features which appear fairly -orthogonal to the main aims are also omitted. - - - -This document is a combination of working notes and on-going status report -regarding my provenance work; as such its got quite a lot of opinion in it, -some of it not justified in the text. - - -
    -
    Running your own provenance database -This section details running your own SQL-based provenance database on -servers of your own control. - -
    Check out the latest SVN code - - -Use the following command to check out the provenancedb -module: - - -svn co https://svn.ci.uchicago.edu/svn/vdl2/provenancedb - - - -
    - - -
    Configuring your SQL database - -Follow the instructions in one of the following sections, to configure your -database either for sqlite3 or for postgres. - -
    Configuring your sqlite3 SQL database - -This section describes configuring the SQL scripts to use -sqlite, which is -appropriate for a single-user installation. - -Install or find sqlite3. On -communicado.ci.uchicago.edu, it is installed and can be -accessed by adding the line +sqlite3 to your ~/.soft file -and typing resoft. Alternatively, on OS X with MacPorts, this command works: - -$ sudo port install sqlite3 - -Similar commands using apt or yum will -probably work under Linux. - - -In the next section, you will create a provenance.config -file. In that, you should configure the use of sqlite3 by specifying: - -export SQLCMD="sqlite3 provdb " - -(note the trailing space before the closing quote) - -
    - -
    Configuring your own postgres 8.3 SQL database - -This section describes configuring a postgres 8.3 database, which is -appropriate for a large installation (where large means lots of log -files or multiple users) - - -First install and start postgres as appropriate for your platform -(using apt-get or port for example). - - -As user postgres, create a database: - -$ /opt/local/lib/postgresql83/bin/createdb provtest1 - - - -Check that you can connect and see the empty database: - -$ psql83 -d provtest1 -U postgres -Welcome to psql83 8.3.6, the PostgreSQL interactive terminal. - -Type: \copyright for distribution terms - \h for help with SQL commands - \? for help with psql commands - \g or terminate with semicolon to execute query - \q to quit - -provtest1=# \dt -No relations found. -provtest1=# \q - - - -In the next section, when configuring provenance.config, -specify the use of postgres like this: - -export SQLCMD="psql83 -d provtest1 -U postgres " - -Note the trailing space before the final quote. Also, note that if you -fiddled the above test command line to make it work, you will have to make -similar fiddles in the SQLCMD configuration line. - -
    -
    - -
    Import your logs - -Now create a etc/provenance.config file to define local -configuration. An example that I use on my laptop is present in -provenance.config.soju. -The SQLCMD indicates which command to run for SQL -access. This is used by other scripts to access the database. The -LOGREPO and IDIR variables should -point to the directory under which you collect your Swift logs. - - -Now import your logs for the first time like this: - -$ ./swift-prov-import-all-logs rebuild - - - -
    - -
    Querying the newly generated database - -You can use swift-about-* commands, described in -the commands section. - - -If you're using the SQLite database, you can get an interactive SQL -session to query your new provenance database like this: - -$ sqlite3 provdb -SQLite version 3.6.11 -Enter ".help" for instructions -Enter SQL statements terminated with a ";" -sqlite> - - - -
    - -
    - -
    swift-about-* commands -There are several swift-about- commands: - -swift-about-filename - returns the global dataset IDs for the specified -filename. Several runs may have output the same filename; the provenance -database cannot tell which run (if any) any file with that name that -exists now came from. - -Example: this looks for information about -001-echo.out which is the output of the first -test in the language-behaviour test suite: - -$ ./swift-about-filename 001-echo.out -Dataset IDs for files that have name file://localhost/001-echo.out - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-1440-67vursv4:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-2146-ja2r2z5f:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080107-1608-itdd69l6:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080303-1011-krz4g2y0:720000000001 - tag:benc at ci.uchicago.edu,2008:swift:dataset:20080303-1100-4in9a325:720000000001 - -Six different datasets in the provenance database have had that filename -(because six language behaviour test runs have been uploaded to the -database). - - -swift-about-dataset - returns information about a dataset, given -that dataset's uri. Returned information includes the IDs of a containing -dataset, datasets contained within this dataset, and IDs for executions -that used this dataset as input or output. - -Example: - -$ ./swift-about-dataset tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 -About dataset tag:benc at ci.uchicago.edu,2008:swift:dataset:20080114-1353-g1y3moc0:720000000001 -That dataset has these filename(s): - file://localhost/001-echo.out - -That dataset is part of these datasets: - -That dataset contains these datasets: - -That dataset was input to the following executions (as the specified named parameter): - -That dataset was output from the following executions (as the specified return parameter): - tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 | t - -This shows that this dataset is not part of a more complicated dataset -structure, and was produced as an output parameter t from an execution. - -swift-about-execution - gives information about an execution, given -an execution ID - -$ ./swift-about-execution tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 -About execution tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 - id | starttime | duration | finalstate | app | scratch -----------------------------------------------------------------------------------------------------------------------------------+----------------+-------------------+----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------- - tag:benc at ci.uchicago.edu,2008:swiftlogs:execute:001-echo-20080114-1353-n7puv429:0 | 1200318839.393 | 0.743000030517578 | 0 | END_SUCCESS | echo -(1 row) - -This shows some basic information about the execution - the start time, -the duration, the name of the application, the final status. - - -
    - - -
    What this work does not address - -This work explicitly excludes a number of uses which traditionally -have been associated with the VDS1 Virtual Data Catalog - either as real -or as imagined functionality. - - -Much of this is open to debate; especially regarding which features are the -most important to implement after the first round of implementation has -occurred. - - - - - -Namespaces and versioning - -the need for these is somewhat orthogonal to the work here. - -Namespaces and versions provide a richer identifier but don't -fundamentally change the nature of the identifier. -so for now I mostly ignore as they are -(I think) fairly straightforward drudgework to implement, rather than -being fundamentally part of how queries are formed. Global namespaces -are used a little bit for identifying datasets between runs (see tag URI -section) - - - - -Prospective provenance - -SwiftScript source programs don't have as -close a similarity to their retrospective structure as in VDL1, so a bunch -of thought required here. Is this required? Is it different from the -SwiftScript program-library point? - - - A database of all logged information - -though it would be interesting -to see what could be done there. straightforward to import eg. -.event and/or .transition files from log parsers into the DB. - - - - - Replica management - - -No specific replica location or management support. However see sections -on general metadata handling (in as much as general metadata can support -replica location as a specific metadata usecase); and also the section on -global naming in the to-be-discussed section. This ties in with the -Logical File Names concept somehow. - - - - - - A library for SwiftScript code - -need better uses for this and -some indication that a more conventional version control system is -not more appropriate. - - -Also included in this exclusion is storage of type definitions. -Its straightforward to store type names; but the definitions are -per-execution. More usecases would be useful here to figure out what sort -of query people want to make. - - - - - Live status updates of in-progress workflows - - -this may happen if data goes -into the DB during run rather than at end (which may or may not happen). -also need to deal with slightly different data - for example, execute2s -that ran but failed (which is not direct lineage provenance?) - - -so - one successful invocation has: one execute, one execute2 (the most recent), -and maybe one kickstart record. it doesn't track execute2s and kickstarts for -failed execution attempts (nor, perhaps, for failed workflows at all...) - - - - - -Deleting or otherwise modifying provenance data - - -Deleting or otherwise modifying provenance data. Though deleting/modifying -other metadata should be taken into account. - - - - - Security - -There are several approaches -here. The most native approach is to use the security model of the -underlying database (which will vary depending on which database is used). - -This is a non-trivial area, especially to do with any richness. -Trust relationships between the various parties accessing the database -should be taken into account. - - - - -A new metadata or provenance query language - -Designing a (useful - i.e. usable and performing) database -and query language is a non-trivial exercise (on the order of years). - - -For now, use existing query languages and their implementations. Boilerplate -queries can be developed around those languages. - - -One property of this is that there will not be a uniform query language for -all prototypes. This is contrast to the VDS1 VDC which had a language which -was then mapped to at least SQL and perhaps some XML query language too. - - -An intermediate / alternative to something language-like is a much more -tightly constrained set of library / template queries with a very constrained -set of parameters. - - -Related to this is the avoidance as much as possible of mixing models; so that -one query language is needed for part of a query, and another query language -is needed for another part of a query. An example of this in practice is the -storage of XML kickstart records as blobs inside a relational database in the -VDS1 VDC. SQL could be used to query the containing records, whilst an -XML query language had to be used to query inner records. No benefit could -be derived there from query language level joining and query optimisation; -instead the join had to be implemented poorly by hand. - - - - -An elegant collection mechanism for provenance or -metadata - -The prototypes here collect their information through log stripping. This -may or may not be the best way to collect the data. For example, hooks -inside the code might be a better way. - - - - -
    - -
    Data model -
    Introduction to the data model - -All of the prototypes use a basic data model that is strongly -related to the structure of data in the log files; much of the naming here -comes from names in the log files, which in turn often comes from source -code procedure names. - - -The data model consists of the following data objects: - -execute - an execute represents a procedure call in a -SwiftScript program. - -execute2 - an execute2 is an attempt to actually execute an -'execute' object. -dataset - a dataset is data used by a Swift program. this might be -a file, an array, a structure, or a simple value. -workflow - a workflow is an execution of an entire SwiftScript -program -
    - -
    execute - - -execute - an 'execute' is an execution of a -procedure call in a SwiftScript program. Every procedure call in a -SwiftScript program corresponds to either -one execute (if the execution was attempted) or zero (if the workflow was -abandoned before an execution was attempted). An 'execute' may encompass -a number of attempts to run the appropriate procedure, possibly on differnt -sites. Those attempts are contained within an execute as execute2 entities. -Each execute is related to zero or more datasets - those passed as inputs -and those that are produced as outputs. - -
    -
    execute2 - -execute2 - an 'execute2' is an attempt to run a -program on some grid site. It consists of staging in input files, running the -program, and staging out the output files. Each execute2 belongs to exactly -one execute. If the database is storing only successful workflows and -successful executions, then each execute will be associated with -exactly one execute2. If storing data about unsuccessful workflows or -executions, then each execute may have zero or more execute2s. - -
    -
    dataset - -A dataset represents data within a -SwiftScript program. A dataset can be an array, a structure, a file or -a simple value. Depending on the nature of the dataset it may have some -of the following attributes: a value (for example, if the dataset -represents an integer); a filename (if the dataset represents a file); -child datasets (if the dataset represents a structure or an array); and -parent dataset (if the dataset is contained with a structure or an -array). - - - -At present, each dataset corresponds to exactly one in-memory DSHandle -object in the Swift runtime environment; however this might not continue -to be the case - see the discussion section on cross-dataset run -identification. - - -Datasets may be related to executes, either as datasets -taken as inputs by an execute, or as datasets produced by an execute. -A dataset may be produced as an output by at most one execute. If it is not -produced by any execute, it is an input to the workflow -and has been produced through some other mechanism. Multiple datasets may -have the same filename - for example, at present, each time the same file -is used as an input in different workflows, a different dataset appears in -the database. this might change. multiple workflows might (and commonly do) -output files with the same name. at present, these are different datasets, -but are likely to remain that way to some extent - if the contents of files -is different then the datasets should be regarded as distinct. - -
    -
    workflow - -workflow - a 'workflow' is an execution of an -entire SwiftScript program. Each execute belongs to exactly one workflow. At -present, each dataset also belongs to exactly one workflow (though the -discussion section talks about how that should not necessarily be the case). - -
    - -TODO: diagram of the dataset model (similar to the one in the -provenance paper but probably different). design so that in the XML -model, the element containment hierarchies can be easily marked in a -different colour -
    - -
    Prototype Implementations - -I have made a few prototype implementations to explore ways of storing -and querying provenance data. - - -The basic approach is: build on the log-processing code, which knows how -to pull out lots of information from the log files and store it in a -structured text format; extend Swift to log additional information as -needed; -write import code which knows -how to take the log-processing structured files and put them into whatever -database/format is needed by the particular prototype. - - -If it is desirable to support more than one of these storage/query mechanisms -(perhaps because -they have unordered values of usability vs query expessibility) then -perhaps should be core provenance output code which is somewhat -agnostic to storage system (equivalent to the post-log-processing -text files at the moment) and then some relatively straightforward set -of importers which are doing little more than syntax change -(cf. it was easy to adapt the SQL import code to make -prolog code instead) - - - -The script import-all will import into the -basic SQL and eXist XML databases. - - -
    Relational, using SQL -There are a couple of approaches based around relational databases -using SQL. The plain SQL approach allows many queries to be answered, but -does provide particularly easy querying for the transitive relations -(such as the 'preceeds' relation mentioned elsewhere); ameliorating this -problem is point of the second model. - -
    -Plain SQL -In this model, the provenance model is mapped to a relational -schema, stored in sqlite3 and queried with SQL. - - - -This prototype uses sqlite3 on my laptop. The import-all -will initialise and import into this database (and also into the XML DB). - - - -example query - counts how many of each procedure have been called. - -sqlite> select procedure_name, count(procedure_name) from executes, invocation_procedure_names where executes.id = invocation_procedure_names.execute_id group by procedure_name; -align|4 -average|1 -convert|3 -slicer|3 - - - -needs an SQL database. sqlite is easy to get (from standard OS software -repos, and from globus toolkit) so this is not as horrible as it seems. -setup requirements for sqlite are minimal. - - -metadata: one way is to handle them as SQL relations. this allows them -to be queried using SQL quite nicely, and to be indexed and joined on -quite easily. - - -prov query 1:Find the process that led to Atlas X Graphic / everything that caused Atlas X Graphic to be as it is. This should tell us the new brain images from which the averaged atlas was generated, the warping performed etc. - - -
    Description of tables - -Executions are stored in a table called 'executes'. Each execution has the fields: id - a globally unique ID for that execution; starttime - the start time -of the execution attempt, in seconds since the unix epoch (this is roughly -the time that swift decides to submit the task, *not* the time that a worker -node started executing the task); duration - in seconds (time from start time -to swift finally finishing the execution, not the actual on-worker execution -time); final state (is likely to always be END_SUCCESS as the present import -code ignores failed tasks, but in future may include details of failures; -app - the symbolic name of the application - - -Details of datasets are stored in three tables: dataset_filenames, -dataset_usage and dataset_containment. - - -dataset_filenames maps filenames (or more generally URIs) to unique dataset -identifiers. - - -dataset_usage maps from unique dataset identifiers to the execution -unique identifiers for executions that take those datasets as inputs -and outputs. execute_id and dataset_id identify the execution and the -procedure which are related. direction indicates whether this dataset -was used as an input or an output. param_name is the name of the parameter -in the SwiftScript source file. - - -dataset_containment indicates which datasets are contained within others, -for example within a structure or array. An array or structure is a dataset -with its own unique identifier; and each member of the array or structure -is again a dataset with its own unique identifier. The outer_dataset_id and -inner_dataset_id fields in each row indicate respectively the -containing and contained dataset. - - -
    - -
    - -
    -SQL with Pre-generated Transitive Closures - -SQL does not allow expression of transitive relations. This causes a -problem for some of the queries. -Work has previously been done (cite) to work on pre-generating -transitive closures over relations. This is similar in concept to the -pregenerated indices that SQL databases traditionally provide. - -In the pre-generated transitive closure model, a transitive closure -table is pregenerated (and can be incrementally maintained as data is added -to the database). Queries are then made against this table instead of -against the ground table. - - -All of the data available in the earlier SQL model is available, in -addition to the additional closures generated here. - - -Prototype code: There is a script called prov-sql-generate-transitive-closures.sh to generate the close of the preceeds -relation and places it in a table called trans: - -$ prov-sql-generate-transitive-closures.sh -Previous: 0 Now: 869 -Previous: 869 Now: 1077 -Previous: 1077 Now: 1251 -Previous: 1251 Now: 1430 -Previous: 1430 Now: 1614 -Previous: 1614 Now: 1848 -Previous: 1848 Now: 2063 -Previous: 2063 Now: 2235 -Previous: 2235 Now: 2340 -Previous: 2340 Now: 2385 -Previous: 2385 Now: 2396 -Previous: 2396 Now: 2398 -Previous: 2398 Now: 2398 - - -A note on timing - constructing the closure of 869 base relations, -leading to 2398 relations in the closure takes 48s with no indices; adding -an index on a column in the transitive relations table takes this time down -to 1.6s. This is interesting as an example of how some decent understanding -of the data structure to produce properly optimised queries and the like -is very helpful in scaling up, and an argument against implementing a poor -'inner system'. - -Now we can reformulate some of the queries from the SQL section -making use of this table. - - -There's some papers around about transitive closures in SQL: - -'Maintaining transitive closure of graphs in SQL' -and -http://willets.org/sqlgraphs.html - - - -how expensive is doing this? how cheaper queries? how more expensive is -adding data? and how scales (in both time and size (eg row count)) as we -put in more rows (eg. i2u2 scale?) exponential, perhaps? though -the theoretical limit is going to be influenced by our usage pattern -which I think for the most part will be lots of disjoint graphs -(I think). we get to index the transitive closure table, which we don't -get to do when making the closure at run time. - - -We don't have the path(s) between nodes but we could store that in the -closure table too if we wanted (though multiple paths would then be more -expensive as there are now more unique rows to go in the closure table) - - -This is a violation of normalisation which the traditional relational people -would say is bad, but OLAP people would say is ok. - - - -how much easier does it make queries? -for queries to root, should be much easier (query over -transitive table almost as if over base table). but queries such as -'go back n-far then stop' and the like harder to query. - - - -keyword: 'incremental evaluation system' (to maintain transitive closure) - - - -The difference between plain SQL and SQL-with-transitive-closures -is that in SQL mode, construction occurs at query time and the query -needs to specify that construction. In the transitive-close mode, -construction occurs at data insertion time, with increased expense there -and in size of db, but cheaper queries (I think). - - -sample numbers: fmri example has 50 rows in base causal relation -table. 757 in table with transitive close. - - - -If running entirely separate workflows, both those numbers will scale linearly -with the number of workflows; however, if there is some crossover between -subsequent workflows in terms of shared data files then the transitive -graph will grow super-linearly. - - -
    -
    -
    XML - -In this XML approach, provenance data and metadata is represented as -a set of XML documents. - -Each document is stored in some kind of document store. -Two different document stores are used: -the posix filesystem and eXist. XPath and XQuery are investigated as -query languages. - -semi-structuredness allows structured metadata without having to -necessarily declare its schema (which I think is one of the desired properties -that turns people off using plain SQL tables to reflect the metadata -schema). but won't get indexing without some configuration of structure so -whilst that will be nice for small DBs it may be necessary to scale up -(though that in itself isn't a problem - it allows gentle start without -schema declaration and to scale up, add schema declarations later on - fits -in with the scripting style). semi-structured form of XML lines up very -will with the desire to have semi-structured metadata. compare ease of -converting other things (eg fmri showheader output) to loose XML - field -relabelling without having to know what the fields actually are - to how -this needs to be done in SQL. - - - -The hierarchical structure of XML perhaps better for dataset containment -because we can use // operator which is transitive down the tree for -dataset containment. - - -XML provides a more convenient export format than SQL or the other formats -in terms of an easily parseable file format. There are lots of -tools around for processing XML files in various different ways (for example, -treating as text-like documents; deserialising into Java in-memory objects -based on an XML Schema definition), and XML is one of the most familiar -structured data file formats. - - -Not sure what DAG representation would look like here? many (one per arc) -small documents? is that a problem for the DBs? many small elements, more -likely, rather than many small documents - roughly one document per workflow. - - -
    xml metadata -in the XML model, two different ways of putting in metadata: as descendents of the -appropriate objects (eg. dataset metadata under the relevant datasets). this -is most xml-like in the sense that its strongly hierarchical. as separate -elements at a higher level (eg. separate documents in xml db). the two ways -are compatible to the extent that some metadata can be stored one way, some -the other way, although the way of querying each will be different. - - -way i: at time of converting provenance data into XML, insert metadata at -appropriate slots (though if XML storage medium allows, it could be inserted -later on). - - -modified prov-to-xml.sh to put that info in for -the appropriate datasets (identified using the below descripted false-filename -method - -can now make queries such as 'tell me the datasets which have header metadata': - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '//dataset[headermeta]' - - - -way ii: need to figure out what the dataset IDs for the volumes are. At the -moment, the filename field for (some) mapped dataset parents still -has a filename -even though that file never exists, like below. This depends on the mapper -being able to invent a filename for such. Mappers aren't guaranteed to be -able to do that - eg where filenames are not formed as a function of the -parameters and path, but rely on eg. whats in the directory at initialisation -(like the filesystem mapper). - -<dataset identifier="10682109"> -<filename>file://localhost/0001.in</filename> -<dataset identifier="12735302"> -<filename>file://localhost/0001.h.in</filename> -</dataset> -<dataset identifier="7080341"> -<filename>file://localhost/0001.v.in</filename> -</dataset> - -so we can perhaps use that. The mapped filename here is providing a -dataset identification (by chance, not by design) so we can take advantage -of it: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.in"]/@identifier' -10682109 - - -I think metadata in XML is more flexible than metadata in relational, -in terms of not having to define schema and not having to stick to schema. -However, how will it stand up to the challenge of scalability? Need to get -a big DB. Its ok to say that indices need to be made - I don't dispute that. -What's nice is that you can operate at the low end without such. So need to -get this stuff being imported into eg eXist (maybe the prototype XML processing -should look like -> XML doc(s) on disk -> whatever xmldb in order to -facilitate prototyping and pluggability.) - - -
    - -
    XPath query language - - -XPath queries can be run either against the posix file system store -or against the eXist database. When using eXist, the opportunity exists -for more optimised query processing (and indeed, the eXist query processing -model appears to evaluate queries in an initially surprising and unintuitive -way to get speed); compared to on the filesystem, -where XML is stored in serialised form and must be parsed for each query. - - - -xml generation: - -./prov-to-xml.sh > /tmp/prov.xml - -and basic querying with xpathtool (http://www.semicomplete.com/projects/xpathtool/) - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/execute[thread="0-4-1"]' - - - -q1: - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance//dataset[filename="file://localhost/0001.jpeg"]' -<toplevel> - <dataset identifier="14976260"> - <filename>file://localhost/0001.jpeg</filename> - </dataset> -</toplevel> - -or can get the identifier like this: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier' -14976260 - -can also request eg IDs for multiple, like this: - -cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier|/provenance//dataset[filename="file://localhost/0002.jpeg"]/@identifier' - - - -can find the threads that use this dataset like this: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/tie[dataset=/provenance//dataset[filename="file://localhost/0001.jpeg"]/@identifier]' -<toplevel> - <tie> - <thread>0-4-3</thread> - <direction>output</direction> - <dataset>14976260</dataset> - <param>j</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 14976260 with no value at dataset=final path=[1]</value> - </tie> - - - -now we can iterate as in the SQL example: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-4-3"][direction="input"]/dataset' -4845856 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="4845856"][direction="output"]/thread' -0-3-3 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-3-3"][direction="input"]/dataset' -3354850 -6033476 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="3354850"][direction="output"]/thread' -0-2 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[thread="0-2"][direction="input"]/dataset' -4436324 -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset="4436324"][direction="output"]/thread' - - -so now we've exhausted the tie relation - dataset 4436324 comes from -elsewhere... - -so we say this: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/dataset[@identifier="4436324"]//dataset/@identifier' -11153746 -7202698 -12705705 -7202698 -12705705 -655223 -2088036 -13671126 -2088036 -13671126 -5169861 -14285084 -12896050 -14285084 -12896050 -6487148 -5772360 -4910675 -5772360 -4910675 - -which gives us (non-unique) datasets contained within dataset 4436324. We can -uniquify outside of the language: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/dataset[@identifier="4436324"]//dataset/@identifier' | sort |uniq -11153746 -12705705 -12896050 -13671126 -14285084 -2088036 -4910675 -5169861 -5772360 -6487148 -655223 -7202698 - -and now need to find what produced all of those... iterate everything again. -probably we can do it integrated with the previous query so that we -don't have to iterate externally: - -$ cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/provenance/tie[dataset=/provenance/dataset[@identifier="4436324"]//dataset/@identifier]' -<?xml version="1.0"?> -<toplevel> - <tie> - <thread>0-1-3</thread> - <direction>output</direction> - <dataset>5169861</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 5169861 with no value at dataset=aligned path=[4]</value> - </tie> - <tie> - <thread>0-1-4</thread> - <direction>output</direction> - <dataset>6487148</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 6487148 with no value at dataset=aligned path=[1]</value> - </tie> - <tie> - <thread>0-1-2</thread> - <direction>output</direction> - <dataset>655223</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 655223 with no value at dataset=aligned path=[2]</value> - </tie> - <tie> - <thread>0-1-1</thread> - <direction>output</direction> - <dataset>11153746</dataset> - <param>o</param> - <value>org.griphyn.vdl.mapping.DataNode hashCode 11153746 with no value at dataset=aligned path=[3]</value> - </tie> -</toplevel> - -which reveals only 4 ties to procedures from those datasets - the elements -of the aligned array. We can get just the thread IDs for that by adding -/thread onto the end: - - cat /tmp/prov.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh '/provenance/tie[dataset=/provenance/dataset[@identifier="4436324"]//dataset/@identifier]/thread' -0-1-3 -0-1-4 -0-1-2 -0-1-1 - -so now we need to iterate over those four threads as before using same -process. - -so we will ask 'which datasets does this contain?' because at -present, a composite dataset will ultimately be produced by its component -datasets (though I think perhaps we'll end up with apps producing datasets -that are composites, eg when a file is output that then maps into some -structure - eg file contains (1,2) and this maps to struct { int x; int y;}. -TODO move this para into section on issues-for-future-discussion. - -so xpath here doesn't really seem too different in expressive ability -from the SQL approach - it still needs external implementation of -transitivity for some of the transitive relations (though not for -dataset containment). and that's a big complicating factor for ad-hoc queries... - -
    notes on using eXist -command line -client doc - -run in command line shell with local embedded DB (not running inside a -server, so analogous to using sqlite rather than postgres): - -~/work/eXist/bin/client.sh -s -ouri=xmldb:exist:// - - - -import a file: - -~/work/eXist/bin/client.sh -m /db/prov -p `pwd`/tmp.xml -ouri=xmldb:exist:// - -note that the -p document path is relative to exist root directory, not to -the pwd, hence the explicit pwd. - - -xpath query from commandline: - - echo '//tie' | ~/work/eXist/bin/client.sh -ouri=xmldb:exist:// -x - - -
    -
    - -
    XSLT - -very much like when we revieved xpath, xslt and xquery for MDS data - these -are the three I'll consider for the XML data model? does XSLT add anything? -not sure. for now I think not so ignore, or at least comment that it does -not add anything. - - - -./prov-to-xml.sh > /tmp/prov.xml -xsltproc ./prov-xml-stylesheet.xslt /tmp/prov.xml - -with no rules will generate plain text output that is not much use. - - -Two potential uses: i) as a formatting language for stuff coming out of -some other (perhaps also XSLT, or perhaps other language) query process. -and ii) as that other language doing semantic rather than presentation -level querying (better names for those levels?) - -
    - -
    XQuery query language - -Build query results for this using probably the same database as the -above XPath section, but indicating where things could be better expressed -using XPath. - - -Using XQuery with eXists: - -$ cat xq.xq -//tie -$ ~/work/eXist/bin/client.sh -ouri=xmldb:exist:// -F `pwd`/xq.xq - - - -A more advanced query: - -for $t in //tie - let $dataset := //dataset[@identifier=$t/dataset] - let $exec := //execute[thread=$t/thread] - where $t/direction="input" - return <r>An invocation of {$exec/trname} took input {$dataset/filename}</r> - - -
    - -
    - -
    RDF and SPARQL - -This can probably also be extended to SPARQL-with-transitive-closures -using the same methods as 1; or see OWL note below. - - -Pegasus/WINGS queries could be interesting to look at here - they -are from the same tradition as Swift. However, the don't deal very -well with transitivity. - -OWL mentions transitivity as something that can be expressed in -an OWL ontology but are there any query languages around that can -make use of that kind of information? - -See prolog section on RDF querying with prolog. - - -There's an RDF-in-XML format for exposing information in serialised form. -Same discussion applies to this as to the discussion in XML above. - -
    - -
    GraphGrep - - - download link see email -graphgrep -graphgrep install notes: port install db3 -some hack patches to get it to build with db3 - - -Got a version of graph grep with interesting graph language apparently in it. -Haven't tried it yet though. - -
    - -
    prolog -Perhaps interesting querying ability here. Probably slow? but not -really sure - SWI Prolog talks about indexing its database (and allowing -the indexing to be customised) and about supporting very large databases. -So this sounds hopeful. - - -convert database into SWI prolog. make queries based on that. - -Can make library to handle things like transitive relations - should be -easy to express the transitivity in various different ways (dataset -containment, procedure-ordering, whatever) - far more clear there than -in any other query language. - -SWI Prolog has some RDF interfacing, so this is clearly a realm that is -being investigated by some other people. For example: -
    It is assumed that Prolog is a suitable vehicle to reason with the data expressed in RDF models -- http://www.swi-prolog.org/packages/rdf2pl.html
    -
    - -http://www.xml.com/pub/a/2001/04/25/prologrdf/index.html - - - -prolog can be used over RDF or over any other tuples. stuff in SQL -tables should map neatly too. Stuff in XML hieararchy perhaps not so -easily but should still be doable. -indeed, SPARQL queries have a very prolog-like feel to them -superficially. - -prolog db is a program at the moment - want something that looks more -like a persistent modifiable database. not sure what the prolog approach -to doing that is. - -so maybe prolog makes an interesting place to do future research on -query language? not used by this immediate work but a direction to -do query expressibility research (building on top of whatever DB is used -for this round?) - - -q1 incremental: - - -?- dataset_filenames(Dataset,'file://localhost/0001.in'). - -Dataset = '10682109' ; - - -Now with lib.pl: - - -dataset_trans_preceeds(Product, Source) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Source, _, _). - - -dataset_trans_preceeds(Product, Source) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Inter, _, _), - dataset_trans_preceeds(Inter, Source). - - -then we can ask: - - -?- dataset_trans_preceeds('14976260',S). - -S = '4845856' ; - -S = '3354850' ; - -S = '6033476' ; - -S = '4436324' ; - -No - - -which is all the dataset IDs up until the point that we get into -array construction. This is the same iterative problem we have -in the SQL section too - however, it should be solvable in the prolog case -within prolog in the same way that the recursion is. so now: - - -base_dataset_trans_preceeds(Product, Source, Derivation) :- - dataset_usage(Thread, 'O', Product, _, _), - dataset_usage(Thread, 'I', Source, _, _), - Derivation = f(one). - -base_dataset_trans_preceeds(Product, Source, Derivation) :- - dataset_containment(Product, Source), - Derivation = f(two). - -dataset_trans_preceeds(Product, Source, Derivation) :- - base_dataset_trans_preceeds(Product, Source, DBase), - Derivation = [DBase]. - -dataset_trans_preceeds(Product, Source, Derivation) :- - base_dataset_trans_preceeds(Product, Inter, DA), - dataset_trans_preceeds(Inter, Source, DB), - Derivation = [DA|DB]. - - - - - -q4: - - -invocation_procedure_names(Thread, 'align_warp'), dataset_usage(Thread, Direction, Dataset, 'model', '12'), execute(Thread, Time, Duration, Disposition, Executable), format_time(atom(DayOfWeek), '%u', Time), DayOfWeek = '5'. -TODO format this multiline, perhaps remove unused bindings - - - - -
    - -
    amazon simpledb -restricted beta access... dunno if i will get any access - i have -none so far, though I have applied. - -From reading a bit about it, my impressions are that this will prove to be -a key->value lookup mechanism with poor support for going the other way -(eg. value or value pattern or predicate-on-value -> key) or for doing -joins (so rather like a hash table - which then makes me say 'why not also -investigate last year's buzzword of DHTs?'. I think that these additional -lookup mechanisms are probably necessary for a lot of the -query patterns. - - - -For some set of queries, though, key -> value lookup is sufficient; and -likely the set of queries that is appropriate to this model varies depending -on how the key -> value model is laid out (i.e. what gets to be a key -and what is its value? do we form a hierarchy from workflow downwards?) - - -
    - - -
    graphviz - -This is a very different approach that is on the boundaries of relevance. - - -goal: produce an annotated graph showing the procedures and the -datasets, with appropriate annotation of identifiers and -descriptive text (eg filenames, procedure names, executable names) that -for small (eg. fmri sized workflows) its easy to get a visual view of -whats going on. - - -don't target anything much bigger than the fmri example for this. -(though there is maybe some desire to produce larger visualisations for -this - perhaps as a separate piece of work. eg could combine foreach -into single node, datasets into single node) - - -perhaps make subgraphs by the various containment relationships: -datasets in same subgraph as their top level parent; -app procedure invocations in the same subgraph as their compound -procedure invocation. - -
    -
    - -
    Comparison with related work that our group has done -before -
    -vs VDS1 VDC -gendax - VDS1 has a tool gendax which provides -various ways of accessing data from the command line. Eg. prov challenge -question 1 very easily answered by this. - - -two points I don't like that should discuss here: i) the metadata schema -(I claim there doesn't need to be a generic metadata schema at all - -when applications decide they want to store certain metadata, they declare -it in the database); and ii) the mixed-model - this is discussed a bit in -the 'no general query language' section. consolidate/crosslink. - -
    - - -
    vs VDL provenance paper figure 1 schema - -The significant differences are: -(TODO perhaps produce a diagram for comparison. could use same diagram -differently annotated to indicate trees in the XML section and also -in the transitivity discussion section) - - -the 'annotation' model - screw that, go -native -the dataset containment model, which doesn't exist in the -virtual dataset model. - - -workflow object has a fromDV and toDV field. what are -those meant to mean? In present model, there isn't any base data for a workflow -at the moment - everything can be found in the descriptions of its -components (such as files used, start time, etc). (see notes on -compound procedure containment with model of a workflow as a compound -procedure) - -invocation to call to procedure chain. this chain looks different. -there are executes (which look like invocations/calls) and procedure names -(which do not exist as primary objects because I am not storing -program code). kickstart records and execute2 records would be more like -the annotations you'd get from the annotation part, with the call being -more directly associated with the execute object. - -
    -
    -
    Questions/Discussion points - -
    metadata - -discourse analysis: Perhaps the word 'metadata' should be banned in -this document - it implies that there is -some special property that distinguishes it sufficiently from normal -data such that it must be treated differently from different data. -I don't believe this to be the case. - - -script prov-mfd-meta-to-xml that generates (fake) -metadata record in XML like this: -$ ./prov-mfd-meta-to-xml 123 -<headermeta> - <dataset>123</dataset> - <bitspixel>16</bitspixel> - <xdim>256</xdim> - <ydim>256</ydim> - <zdim>128</zdim> - <xsize>1.000000e+00</xsize> - <ysize>1.000000e+00</ysize> - <zsize>1.250000e+00</zsize> - <globalmaximum>4095</globalmaximum> - <globalminimum>0</globalminimum> -</headermeta> - - - -
    metadata random notes - -metadata: there's a model of arbitrary metadata pairs being -associated with arbitrary objects. -there's another model (that I tend to -favour) in that the metadata schema is more defined than this - eg in i2u2 -for any particular elab, the schema for metadata is fairly well defined. - - -eg in cosmic, there are strongly typed fields such as "blessed" or -"detector number" that -are hard-coded throughout the elab. whilst the VDS1 VDC can deal with -arbitrary typing, that's not the model that i2u2/cosmic is using. need to be -careful to avoid the inner-platform effect here especially - "we need a -system that can do arbitrarily typed metadata pairs" is not actually a -requirement in this case as the schema is known at application build time. -(note that this matters for SQL a lot, not so much for plain XML data model, -though if we want to specify things like 'is-transitive' properties then -in any model things like that need to be better defined) - - -fMRI provenance challenge metadata (extracted using scanheader) looks like -this: - -$ /Users/benc/work/fmri-tutorial/AIR5.2.5/bin/scanheader ./anatomy0001.hdr -bits/pixel=16 -x_dim=256 -y_dim=256 -z_dim=128 -x_size=1.000000e+00 -y_size=1.000000e+00 -z_size=1.250000e+00 - -global maximum=4095 -global minimum=0 - - -
    - -
    - - -
    The 'preceeds' relation - -
    Provenance of hierarchical datasets - - - - -One of the main provenance queries is whether some entity (a -data file or a procedure) was influenced by some other entity. - - - -In VDS1 a workflow is represented by a bipartite DAG where one -vertex partition is files and the other is procedures. - - - -The more complex data structures in Swift make the provenance graph -not so straightforward. Procedures input and output datasets that may -be composed of smaller datasets and may in turn be composed into larger -datasets. - - - -For example, a dataset D coming out of a procedure P may form a part -of a larger dataset E. Dataset E may then be an input to procedure Q. -The ordering is then: - - P --output--> D --contained-by-> E --input--> Q - - - - -Conversely, a dataset D coming out of a procedure P may contain a -smaller dataset E. Dataset E may then be used as an input to procedure -Q. - - P --output--> D --contains--> E --input--> Q - - - - -So the contains relation and its reverse, the contained-by relation, do not -in the general case seem to give an appropriate preceeds relation. - - -so: i) should Q1<->Q be a bidirection dependency (in which case we - no longer have a DAG, which causes trouble) - -or - - ii) the dependency direction between Q1 and Q depends on how Q and Q1 -were constructed. I think this is the better approach, because I think -there really is some natural dependency order. - -If A writes to Q1 and Q1 is part of Q then A->Q1->Q -If A writes to Q and Q1 is part of Q then A->Q->Q1 - -So when we write to a dataset, we need to propagate out the dependency -from there (both upwards and downwards, I think). - -eg. if Q1X is part of Q1 is part of Q -and A writes to Q1, then Q1X depends on Q1 and Q depends on Q1. - - - - - - - - - -Various ways of doing closure - we have various relations in the graph -such as dataset containment and procedure input/output. Need to figure out -how this relates to predecessor/successors in the provenance sense. - - -A( -Also there are multiple levels of tracking (see the section on that): - -If an app procedure produces eg -volume v, consisting of two files v.img and v.hdr (the fmri example) -then what is the dependency here? I guess v.img and v.hdr is the -output... (so in the present model there will never be -downward propagation as every produced dataset will be produced out of -base files. however its worth noting that this perhaps not always the -case...) - -Alternatively we can model at the level of the app procedure, which in -the above case returns a volume v. - -I guess this is similar to the case of the compound procedures vs -contained app procedures... - -If we model at the level of files, then we don't really need to know -about higher datasets much? - -Perhaps for now should model at level of procedure calls -)A - -List A()A above as an issue and pick one choice - for now, lowest=file -production, so that all intermediate and output datasets will end up -with a strictly upward dependency - -This rule does not deal with input-only datasets (that is, datasets -which we do not know where they came from). It would be fairly natural -with the above choice to again make dependencies from files upward. - -So for now, dataset dependency rule is: - - * parent datasets depend on their children. - -Perhaps? - - - - -
    - -
    Transitivity of relations in query language - -One of my biggest concerns in query languages such as SQL and XPath -is lack of decent transitive query ability. - - -I think we need a main relation, the preceeds -relation. None of the relations defined in the source provenance data -provides this relation. - -The relation needs to be such that if any dataset or program Y that -contributed to the production of any other dataset or program Y, then -X preceeds Y. - - -We can construct pieces of this relation from the existing relations: - -There are fairly simple rules for procedure inputs and -outputs: -A dataset passed as an input to a procedure preceeds that procedure. -Similarly, a procedure that outputs a dataset preceeds that dataset. - - - -Hierarchical datasets are straightforward to describe in the present -implementation. Composite data structures are always described in terms -of their members, so the members of a data structure always preceed -the structures that contain them. [not true, i think - we can pass a -struct into a procedure and have that procedure populate multiple -contained files... bleugh] - - - -The relation is transitive, so the presence of some relations by the -above rules will imply the presence of other relations to ensure -transitivity. - - - -
    -
    - - -
    Unique identification of provenance objects - - -A few issues - what are the objects that should be identified? (semantics); -and how should the objects be identified? (syntax). - -
    provenence object identifier syntax - -For syntax, I favour a URI-based approach and this is what I have -implemented in the prototypes. URIs rovide a ready made system for -identifying different kinds of objects in different ways within the -same syntax. -which should be useful for the querys that want to do that. -file, gsiftp URIs for filenames. probably should be normalising file -URIs to refer to a specific hostname? otherwise they're fairly -meaningless outside of one host... -also, these name files but files are mutable. - - -its also fairly straightforward to subsume other identifier schemes into -URIs (for example, that is already done for UUIDs, in RFC4122). - - -for other IDs, such as workflow IDs, a tag or uuid URI would be nice. - - -cite: RFC4151 -
    -The tag algorithm lets people mint -- create -- identifiers that no one else using the same algorithm could ever mint. It is simple enough to do in your head, and the resulting identifiers can be easy to read, write, and remember. The identifiers conform to the URI (URL) Syntax. -
    -
    - -cite: RFC4122 -
    -This specification defines a Uniform Resource Name namespace for -UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally -Unique IDentifier). A UUID is 128 bits long, and requires no central -registration process. -
    -
    - -
    tag URIs - - -tag URIs for identifiers of provenance objects: - - - -all URIs allocated according to this section are labelled beginning with one -of: - -tag:benc at ci.uchicago.edu,2007:swift: -tag:benc at ci.uchicago.edu,2008: - - - - -for datasets identified only within a run (that is, for example, anything -that doesn't have a filename): -tag:benc at ci.uchicago.edu,2007:swift:dataset:TIMESTAMP:SEQ -with TIMESTAMP being a timestamp of sometime near the start of the run, -intending to be a unique workflow id (probably better to use the -run-id) -and SEQ being a sequence number. However, shouldn't really be pulling any -information out of these time and seq fields. - - -for executes - this is based on the karajan thread ID and the log base -filename (which is assumed to be a globally unique identifying string): -tag:benc at ci.uchicago.edu,2007:swiftlogs:execute:WFID:THREAD with, -as for datasets, WFID is a workflow-id-like entity. - - -
    - - -
    - -
    Dataset identifier semantics - -At present, dataset identifiers are formed uniquely for every -dataset object created in the swift runtime (unique across JVMs as well -as within a JVM). - -This provides an overly sensitive(?) identity - datasets -which are the same will be given different dataset identifiers at -different times/places; although two different datasets will never be -given the same identifier. - - -A different approach would be to say 'datasets are made of files, -so we want to identify files, and files already have identiers called -filenames'. - -I think this approach is also insufficient. - -The assertion 'datasets are made of files' is not correct. Datasets -come in several forms: typed files, typed simple values, and typed -collections of other datasets. Each of these needs a way to identify it. - - - -Simple values are probably the easiest to identify. They can be identified -by their own value and embedded within a suitable URI scheme. For example, -a dataset representing the integer 7 could be identified as: - -tag:benc at ci.uchicago.edu,2008:swift:types:int:7 - -This would have the property that all datasets representing the integer -7 would be identical (that is, have the same identifier). - - - -Collections of datasets are more complicated. One interesting example of -something that feels to me quite similar is the treatment of directories -in hash-based file systems, such as git. In this model, a collection of -datasets would be represented by a hash of a canonical representation of -its contenst, for example, a dataset consisting of a three element array -of three files in this order: "x-foo:red", "x-foo:green" and "x-foo:blue" -might be represented as: - -tag:benc at ci.uchicago.edu,2008:collection:QHASH - -where: - -QHASH := sha1sum(QLONG) - -QLONG := "[0] x-foo:red [1] x-foo:green [2] x-foo:blue" - -This allows a repeatable computation of dataset identifiers given -only knowledge of the contents of the dataset. Specifically it does -not rely on a shared database to map content to identifier. However, -it can only be computed when the content of the dataset is fully known -(roughly equivalent to when the dataset is closed in the Swift -runtime) - - - -For identifying a dataset that is a file, there are various properties. -Filename is one property. File content is another property. It seems -desirable to distinguish between datasets that have the same name yet -have different content, whilst identifying datasets that have the same -content. To this end, an identifier might be constructed from both the -filename and a hash of the content. - - - - -for prototype could deal only with files staged to local system, -so that we can easily compute a hash over the content. - - -related to taking md5sums, kickstart provides the first few bytes -of certain files (the executable and specified input and output files); -whilst useful for basic sanity checks, there are very strong correlations -with magic numbers and common headers that make this a poor content -identifying function. perhaps it should be absorbed as dataset metadata if -its available? - - - -TODO the following para needs to rephrase as justification for -having identities for dataset collections ::: at run-time when can we -pick up the -identities from other runs? pretty much we want identity to be expressed -in some way so that we can get cross-run linkup. -how do we label a dataset such that we can annotate it - eg in fmri -example, how do we identify the input datasets (as file pairs) rather than -the individual files? - -Its desirable to give the same dataset the same identifier in multiple -runs; and be able to figure out that dataset identifier outside of a run, -for example for the purposes of dealing with metadata that is annotating -a dataset. - -
    - -
    File content tracking - -identify file contents with md5sum (or other hash) - this is somewhat -expensive, but without it we have (significantly) lessened belief in what the -contents of a file are - we would otherwise, I think, be using only names -and relying on the fact that those names are primary keys to file content -(which is not true in general). -so this should be perhaps optional. plus where to do it? various places... -in wrapper.sh? - - -References here for using content-hashes: -git, many of the DHTs (freenet, for example - amusing to cite the classic -freenet gpl.txt example) - -
    - -
    - -
    Type representation - -how to represent types in this? for now use names, but that doesn't -go cross-program because we can define a different type with the same -name in every different program. hashtree of type definitions? - -
    -
    representation of workflows - -perhaps need a workflow object that acts something like a namespace -but implicitly definted rather than being user labelled (hence capturing -the actual runtime space rather than what the user claims). that's the -runID, I guess. - - -Also tracking of workflow source file. Above-mentioned reference to -tracking file contents applies to this file too. - -
    -
    metadata extraction - -provenance challenge I question 5 reports about pulling fields out of the -headers of one of the input files. There's a program, scanheader, that -extracts this info. Related but not actually useful, I think, for this -question is that header fields could be mapped into SwiftScript if we -allowed value+file simultaneous data structures. - -
    - -
    source code recreation - -should the output of the queries be sufficient to regenerate the -data? the most difficult thing here seems to be handling data -sets - we have the mapping tree for a dataset, but what is the right -way to specify that in swift syntax? maybe need mapper that takes a -literal datastructure and maps the filenames from it. though that -doesn't account for file contents (so this bit of this point is -the file contents issue, which should perhaps be its own chapter -in this file) - -
    -
    Input parameters - -Should also work on workflows which take an input parameter, so that we -end up with the same output file generated several times with different -output values - eg pass a string as a parameter and write that to -'output.txt' - every time we run it, the file will be different, and we'll -have multiple provenance reports indicating how it was made, with different -parameters. that's a simple demonstration of the content-tracking which -could be useful. - - -If we're tracking datasets for simple values, I think we get this -automatically. The input parameters are input datasets in the same way -that input files are input datasets; and so fit into the model in the -same way. - - -
    - - -
    - -
    Open Provenance Model (OPM) -
    OPM-defined terms and their relation to Swift - -OPM defines a number of terms. This section describes how those terms -relate to Swift. - - -artifact: This OPM term maps well onto the internal Swift representation -of DSHandles. Each DSHandle in a Swift run is an -OPM artifact, and each OPM artifact in a graph is a DSHandle. - -collection: OPM collections are a specific kind of artifact, containing -other artifacts. This corresponds with DSHandles for composite data types -(structs and arrays). OPM has collection accessors and collection -constructors which correspond to the [] and -. operators (for accessors) and various assignment -forms for constructors. - - -process: An OPM process corresponds to a number of Swift concepts (although -they are slowly converging in Swift to a single concept). Those concepts -are: procedure invocations, function calls, and operators. - - -agent: There are several entities which can act as an agent. At the -highest level where only Swift is involved, a run of the -swift commandline client is an agent which drives -everything. Some other components of Swift may be regarded as agents, -such as the client side wrapper script. For present OPM work, the -only agent will be the Swift command line client invocation. - - -account: For present OPM work, there will be one account per workflow run. -In future, different levels of granularity that could be expressed through -different accounts might include representing compound procedure calls as -processes vs representing atomic procedures calls explicitly. - - -OPM graph: there are two kinds of OPM graph that appear interesting and -straightforward to export: i) of entire provenance database (thus containing -multiple workflow runs); ii) of a single run - -
    -
    OPM links -Open Provenance Model at ipaw.info -
    - -
    Swift specific OPM considerations - - -non-strictness: Swift sometimes lazily constructs collections (leading to -the notion in Swift of an array being closed, which means that we know no -more contents will be created, somewhat like knowing we've reached the end -of a list). It may be that an array is never closed during a run, but that -we still have sufficient provenance information to answer useful queries -(for example, if we specify a list [1:100000] and only refer to the 5th -element in that array, we probably never generate most of the DSHandles... -so an explicit representation of that array in terms of datasets cannot be -expressed - though a higher level representation of it in terms of its -constructor parameters can be made) (?) - - - -aliasing: (this is related to some similar ambiguity in other parts of -Swift, to do with dataset roots - not provenance related). It is possible to -construct arrays by explicitly listing their members: - -int i = 8; -int j = 100; -int a[] = [i,j]; -int k = a[1]; -// here, k = 8 - -The dataset contained in i is an artifact (a literal, so -some input artifact that has no creating process). The array -a is an artifact created by the explicit array construction -syntax [memberlist] (which is an OPM process). If we -then model the array accessor syntax a[1] as an OPM -process, what artifact does it return? The same one or a different one? -In OPM, we want it to return a different artifact; but in Swift we want this -to be the same dataset... (perhaps explaining this with int -type variables is not the best way - using file-mapped data might be better) -TODO: what are the reasons we want files to have a single dataset -representation in Swift? dependency ordering - definitely. cache management? -Does this lead to a stronger notion of aliasing in Swift? - - - -Provenance of array indices: It seems fairly natural to represent arrays as OPM -collections, with array element extraction being a process. However, in OPM, -the index of an array is indicated with a role (with suggestions that it might -be a simple number or an XPath expression). In Swift arrays, the index is -a number, but it has its own provenance, so by recording only an integer there, -we lose provenance information about where that integer came from - that -integer is a Swift dataset in its own right, which has its own provenance. -It would be nice to be able to represent that (even if its not standardised -in OPM). I think that needs re-ification of roles so that they can be -described; or it needs treatment of [] as being like any other binary -operator (which is what happens inside swift) - where the LHS and RHS are -artifacts, and the role is not used for identifying the member (which would -also be an argument for making array element extraction be treated more -like a plain binary operator inside the Swift compiler and runtime) - - - -provenance of references vs provenance of the data in them: the array and -structure access operators can be used to acquire DSHandles -which have no value yet, and which are then subsequently assigned. In this -usage, the provenance of the containing structure should perhaps be that it -is constructed from the assignments made to its members, rather than the -other way round. There is some subtlety here that I have not fully figured -out. - - - -Piecewise construction of collections: arrays and structs can be -constructed piecewise using . = and [] =. -how is this to be represented in OPM? perhaps the closing operation maps -to the OPM process that creates the array, so that it ends up looking -like an explicit array construction, happening at the time of the close? - - - -Provenance of mapper parameters: mapper parameters are artifacts. We can -represent references to those in a Swift-specific part of an artifacts -value, perhaps. Probably not something OPM-generalisable. - - -
    - -
    - - - -
    Processing i2u2 cosmic metadata -i2u2 cosmic metadata is extracted from a VDS1 VDC. - -TODO some notes here about how I dislike the inner-plaform effect in the -metadata part of the VDS1 VDC. - - -to launch postgres on soju.hawaga.org.uk: - -sudo -u postgres /opt/local/lib/postgresql82/bin/postgres -D /opt/local/var/db/postgresql82/defaultdb - - -and then to import i2u2 vdc data as VDC1 vdc: - - -$ /opt/local/lib/postgresql82/bin/createdb -U postgres i2u2vdc1 -CREATE DATABASE -$ psql82 -U postgres -d i2u2vdc1 < work/i2u2.vdc -gives lots of errors like this: -ERROR: role "portal2006_1022" does not exist -because indeed that role doesn't exist -but I think that doesn't matter for these purposes - everything will end -up being owned by the postgres user which suffices for what I want to do. - - - - - -annotation tables are: - - public | anno_bool | table | postgres 29214 rows - this is boolean values - - public | anno_call | table | postgres 0 rows -- this is a subject table. also has did - - public | anno_date | table | postgres 52644 rows - this is date values - - public | anno_definition | table | postgres 1849 rows - this is XML-embedded derivations (values / objects) - - public | anno_dv | table | postgres 0 rows -- this is a subject table. also has did - - public | anno_float | table | postgres 27966 rows - this is float values - - public | anno_int | table | postgres 58879 rows - this is int values - - public | anno_lfn | table | postgres 411490 rows - this is the subject record for LFN subjects - subjects have an - mkey (predicate) column - - public | anno_lfn_b | table | postgres -this appears to be keyed by did field - ties dids to what looks like -LFNs - - public | anno_lfn_i | table | postgres - public | anno_lfn_o | table | postgres -likewise these two - - public | anno_targ | table | postgres -is this a subject table? it has an mkey value that always appears to be -'description' and then has a name column which lists invocation parameter -names and ties them to dids. - - public | anno_text | table | postgres 242824 rows -text values (objects) - - public | anno_tr | table | postgres - - - - -most of the interesting data starts in anno_lfn because data is mostly -annotating LFNs: - - - -i2u2vdc1=# select * from anno_lfn limit 1; - id | name | mkey -----+---------------------+---------- - 2 | 180.2004.0819.0.raw | origname - - - -There are 63 different mkeys (predicates in RDF-speak): - - - -i2u2vdc1=# select distinct mkey from anno_lfn; - mkey ------------------------------- - alpha - alpha_error - author - avgaltitude - avglatitude - avglongitude - background_constant - background_constant_error - bins - blessed - caption - chan1 - chan2 - chan3 - chan4 - channel - city - coincidence - comments - cpldfrequency - creationdate - date - description - detectorcoincidence - detectorid - dvname - enddate - energycheck - eventcoincidence - eventnum - expire - filename - gate - gatewidth - group - height - julianstartdate - lifetime(microseconds) - lifetime_error(microseconds) - name - nondatalines - numBins - origname - plotURL - project - provenance - radius - rawanalyze - rawdate - school - source - stacked - startdate - state - study - teacher - thumbnail - time - title - totalevents - transformation - type - year -(63 rows) - - - -so work on a metadata importer for i2u2 cosmic that will initially deal -with only the lfn records. - - - -There are 19040 annotated LFNs, with 411490 annotations in total, so about -21 annotations per LFN. - - -The typing of the i2u2 data doesn't support metadata objects -that aren't swift workflow entities - for example high schools as -objects in their own right - the same text string is stored as a value -over and over in many anno_text rows. A more generalised -Subject-Predicate-Object model in RDF would have perhaps a URI for -the high school, with metadata on files tying files to a high school and -metadata on the high school object. In SQL, that same could be modelled -in a relational schema. - - - -Conversion of i2u2 VDS1 VDC LFN/text annotations into an XML document -using quick hack script took 32mins on soju, my laptop. resulting XML -is 8mb. needed some manual massage to remove malformed embedded xml and -things like that. - -./i2u2-to-xml.sh >lfn-text-anno.xml - - -so we end up with a lot of records that look like this: - - -<lfn name="43.2007.0619.0.raw"> -<origname>rgnew.txt</origname> -<group>riogrande</group> -<teacher>Luis Torres Rosa</teacher> -<school>Escuelo Superior Pedro Falu</school> -<city>Rio Grande</city> -<state>PR</state> -<year>AY2007</year> -<project>cosmic</project> -<comments></comments> -<detectorid>43</detectorid> -<type>raw</type> -<avglatitude>18.22.8264</avglatitude> -<avglongitude>-65.50.1975</avglongitude> -<avgaltitude>-30</avgaltitude> -</lfn> - - -The translation here is not cosmic-aware - the XML tag is the mkey name from -vdc and the content is the value. So we get all the different metadata -(informal) schemas that appear to have been used, translated. - - - - -Output the entire provenance database: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic' | wc -c - 10178037 - -real 0m2.624s -user 0m2.612s -sys 0m0.348s - - - - -Select all LFN objects (which on this dataset means everything one layer -down): - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn' | wc -c - 9618818 - -real 0m2.692s -user 0m2.703s -sys 0m0.337s - - - - -Try to select an LFN that doesn't exist, by specifying a filename that is not -there: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn[@name="NOSUCHNAME"]' -<?xml version="1.0"?> -<toplevel/> - -real 0m0.867s -user 0m0.740s -sys 0m0.143s - - - - -Similar query for a filename that does exist: - -$ time cat lfn-text-anno.xml | ~/work/xpathtool-20071102/xpathtool/xpathtool.sh --oxml '/cosmic/lfn[@name="1.2005.0801.0"]' -<?xml version="1.0"?> -<toplevel> - <lfn name="1.2005.0801.0"> - <origname>C:\Documents and Settings\zsaleh\My Documents\Tera stuff\Qnet\Qnet Data\All_data_Aug_01_2005_TERA_9_Vth_1000.TXT</origname> - <group>TERA</group> - <teacher>Marcus Hohlmann</teacher> - <school>Florida Institute of Technology</school> - <city>Melbourne</city> - <state>FL</state> - <year>AY2004</year> - <project>cosmic</project> - <comments/> - <source>1.2005.0801.0</source> - <detectorid>1</detectorid> - <type>split</type> - </lfn> -</toplevel> - -real 0m0.875s -user 0m0.745s -sys 0m0.154s - - - -
    - -
    processing fMRI metadata - -for fmri, we can extract embedded image metadata using the scanheader -utility. - - -associate that with the 'volume' dataset, not with the actual image data -files. for now that means we need the datasets to have been labelled with -their ID already, which is at the moment after execution has completed. -that's fine for now with the retrospective provenance restriction of this -immediate work. see the -'cross-run dataset ID' section, for which this -also applies - we are generating dataset IDs outside of a particular run. - -
    - -
    random unsorted notes - -to put provdb in postgres instead of sqlite3: - -start as per i2u2 instructions, then /opt/local/lib/postgresql82/bin/createdb -U postgres provdb - -then: - - psql82 -U postgres -d provdb < prov-init.sql - to initialise the db. - - -on terminable, made new database that is not the default system db install, -by using existing postgres but running under my user id: - - 131 mkdir pgplay - 133 chmod 0700 pgplay/ - 135 initdb -D ~/pgplay/ - 138 postmaster -D ~/pgplay/ -p 5435 -$ createdb -p 5435 provdb -CREATE DATABASE - -now can access like this: - -$ psql -p 5435 -d provdb -provdb=# \dt -No relations found. - - -osg/gratia - how does this data tie in? - -cedps logging - potential for info there but there doesn't seem -anything particularly substantial at the moment - -
    - -
    Provenance Challenge 1 examples -
    Basic SQL -
    provch q1 - - -get the dataset id for the relevant final dataset: -sqlite> select * from dataset_filenames where filename like '%0001.jpeg'; -14976260|file://localhost/0001.jpeg - -get containment info for that file: -sqlite> select * from dataset_containment where inner_dataset_id = 14976260; -7316236|14976260 -sqlite> select * from dataset_containment where inner_dataset_id = 7316236; -[no answer] - -now need to find what contributed to those... - -> select * from dataset_usage where dataset_id=14976260; -0-4-3|O|14976260 - -> select * from dataset_usage where execute_id='0-4-3' and direction='I'; -0-4-3|I|4845856 -qlite> select * from dataset_usage where dataset_id=4845856 and direction='O'; -0-3-3|O|4845856 - -sqlite> select * from dataset_usage where execute_id='0-3-3' and direction='I'; -0-3-3|I|3354850 -0-3-3|I|6033476 - -qlite> select * from dataset_usage where (dataset_id=3354850 or dataset_id=6033476) and direction='O'; -0-2|O|3354850 - -sqlite> select * from dataset_usage where execute_id='0-2' and direction='I';0-2|I|4436324 - -sqlite> select * from dataset_usage where dataset_id=4436324 and direction='O'; -[no answer] - -so here we have run out of places to keep going. however, I think this 4436324 -is not an input - its related to another dataset. so we need another rule for -inference here... - - - - -
    - -
    prov ch q4 -prov ch q4 incremental solutions: - -first cut: -this will select align_warp procedures and their start times. does not -select based on parameters, and does not select based on day of week. -(the former we don't have the information for; the latter maybe don't have -the information in sqlite3 to do - or maybe need SQL date ops and SQL dates -rather than unix timestamps) - -sqlite> select id, starttime from invocation_procedure_names, executes where executes.id = invocation_procedure_names.execute_id and procedure_name='align_warp'; - -Next, this will display the day of week for an invocation: - -select id, strftime('%w',starttime, 'unixepoch') from executes,invocation_procedure_names where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id; -0-0-3|5 -0-0-4|5 -0-0-1|5 -0-0-2|5 - - -And this will match day of week (sample data is on day 5, which is a -Friday, not the day requested in the question): - -sqlite> select id from executes,invocation_procedure_names where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5'; -0-0-3 -0-0-4 -0-0-1 -0-0-2 - - - -Now we bring in input data binding: we query which datasets were passed in -as the model parameter for each of the above found invocations: - -sqlite> select executes.id, dataset_usage.dataset_id from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model'; -0-0-3|11032210 -0-0-4|13014156 -0-0-1|14537849 -0-0-2|16166946 - -though at the moment this doesn't give us the value of the parameter. - - -so now pull in the parameter value: - - -sqlite> select executes.id, dataset_usage.dataset_id, dataset_usage.value from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model'; -0-0-3|11032210|12 -0-0-4|13014156|12 -0-0-1|14537849|12 -0-0-2|16166946|12 - - - - -Now we can select on the parameter value and get our final answer: - -sqlite> select executes.id from executes,invocation_procedure_names, dataset_usage where procedure_name='align_warp' and executes.id=invocation_Procedure_names.execute_id and strftime('%w',starttime, 'unixepoch') = '5' and dataset_usage.execute_id = executes.id and direction='I' and param_name='model' and dataset_usage.value=12; -0-0-3 -0-0-4 -0-0-1 -0-0-2 - -Note that in SQL in general, -we *don't* get typing of the parameter value here so can't do anything -more than string comparison. For example, we couldn't check for the -parameter being greater than 12 or similar. In sqlite, it happens that -its typing is dynamic enough to allow the use of relational operators like -> on fields no matter what their declared type, because declared type is -ignored. This would stop working if stuff was run on eg postgres or mysql, -I think. - -
    -
    prov ch metadata -metadata: in the prov challenge, we annotate (some) files with -their header info. in the provenance paper, we want annotations on more -than just files. - -for prov ch metadata, define a scanheader table with the result of -scanheader on each input dataset, but do it *after* we've done the -run (because we're then aware of dataset IDs) -There's a representation question here - the metadata is about a volume -dataset which is a pair of files, not about a header or image file separately. -how to represent this? we need to know the dataset ID for the volume. at -the moment, we can know that after a run. but this ties into the -identification of datasets outside of an individual run point - move this -paragraph into that questions/discussions section. - - -should probably for each storage method show the inner-platform style of -doing metadata too; associated queries to allow comparison with the -different styles; speeds of metadata query for large metadata collections -(eg. dump i2u2 cosmic metadata for real cosmic VDC) - -
    -
    - -
    SQL with transitive closures -
    -prov ch question 1: - -$ sqlite3 provdb -SQLite version 3.3.17 -Enter ".help" for instructions -sqlite> select * from dataset_filenames where filename like '%0001.jpeg'; -14976260|file://localhost/0001.jpeg --- can query keeping relations -sqlite> select * from trans where after=14976260; -0-4-3|14976260 -4845856|14976260 -0-3-3|14976260 -3354850|14976260 -6033476|14976260 -4825541|14976260 -7061626|14976260 -0-2|14976260 -4436324|14976260 -11153746|14976260 -655223|14976260 -5169861|14976260 -6487148|14976260 -5772360|14976260 -4910675|14976260 -7202698|14976260 -12705705|14976260 -2088036|14976260 -13671126|14976260 -14285084|14976260 -12896050|14976260 -0-1-3|14976260 -0-1-4|14976260 -0-1-2|14976260 -0-1-1|14976260 -2673619|14976260 -9339756|14976260 -10682109|14976260 -8426950|14976260 -16032673|14976260 -2274050|14976260 -1461238|14976260 -13975694|14976260 -9282438|14976260 -12766963|14976260 -8344105|14976260 -9190543|14976260 -14055055|14976260 -2942918|14976260 -12735302|14976260 -7080341|14976260 -0-0-3|14976260 -0-0-4|14976260 -0-0-2|14976260 -0-0-1|14976260 -2307300|14976260 -11032210|14976260 -16166946|14976260 -14537849|14976260 -13014156|14976260 -6435309|14976260 -6646123|14976260 --- or can query without relations: -sqlite> select before from trans where after=14976260; -0-4-3 -4845856 -0-3-3 -3354850 -6033476 -4825541 -7061626 -0-2 -4436324 -11153746 -655223 -5169861 -6487148 -5772360 -4910675 -7202698 -12705705 -2088036 -13671126 -14285084 -12896050 -0-1-3 -0-1-4 -0-1-2 -0-1-1 -2673619 -9339756 -10682109 -8426950 -16032673 -2274050 -1461238 -13975694 -9282438 -12766963 -8344105 -9190543 -14055055 -2942918 -12735302 -7080341 -0-0-3 -0-0-4 -0-0-2 -0-0-1 -2307300 -11032210 -16166946 -14537849 -13014156 -6435309 -6646123 - - - -
    - - -
    - -
    - -
    Representation of dataset containment and procedure execution in r2681 and how it could change. - - -Representation of processes that transform one dataset into another dataset -at present only occurs for app procedures, in logging of -vdl:execute invocations, in lines like this: - -2009-03-12 12:20:29,772+0100 INFO vdl:parameterlog PARAM thread=0-10-1 direction=input variable=s provenanceid=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000033 - -and dataset containment is represented at closing of the containing DSHandle by this: - -2009-03-12 12:20:30,205+0100 INFO AbstractDataNode CONTAINMENT parent=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000020 child=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000086 -2009-03-12 12:20:30,205+0100 INFO AbstractDataNode ROOTPATH dataset=tag:benc at ci.uchicago.edu,2008:swift:dataset:20090312-1220-md2mfc24:720000000086 path=[2] - - - - -This representation does not represent the relationship between datasets when -they are related by @functions or operators. Nor does it represent causal -relationships between collections and their members - instead it represents -containment. - - - -Adding representation of operators (including array construction) and of - at function invocations would give substantially more information about -the provenance of many more datasets. - - -
    - -
    - Deleted: trunk/docs/quickstartguide.xml =================================================================== --- trunk/docs/quickstartguide.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/quickstartguide.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,272 +0,0 @@ - - - - -
    - - Swift Quick Start Guide - Source Control $LastChangedRevision$ - - - - - - - The impatient may find the Swift Really Quick Start - Guide to be more convenient. - - This guide describes the steps needed to download, install, - configure, and run the basic examples for Swift. If you are - using a pre-installed version of Swift, you can skip - directly to the configuration - section. - - - - - - - - Downloading a Swift Distribution - - - - There are three main ways of getting the Swift implementation: stable releases, nightly builds, and the source code repository. - - - - - Stable Releases - - - - Stable releases can be obtained from the Swift download page: - Swift - Downloads Page. Once you downloaded the package, please - move to the install section. - - - - - - Nightly Builds - - - - Swift builds and tests are being run every day. The Swift - downloads page contains links to the latest build and - test page. The nightly builds reflect a development version of - the Swift code and should not be used in production mode. After - downloading a nightly build package, please continue to the - install section. - - - - - - Source Repository - - - - Details about accessing the Swift source repository together with - build instructions are available on the Swift - downloads page. Once built, the dist/swift-svn directory - will contain a self-contained build which can be used in place or moved to a different location. - You should then proceed to the configuration section. - - - - - - - Installing a Swift Binary Package - - - - Simply unpack the downloaded package (swift-<version>.tar.gz) into a - directory of your choice: - - -> tar swift-<version>.tar.gz - - - This will create a swift-<version> directory - containing the build. - - - - - - Configuring Swift - - - - This section describes configuration steps that need to be taken in - order to get Swift running. Since all command line tools provided - with Swift can be found in the bin/ directory of the Swift distribution, it may - be a good idea to add this directory to your PATH - environment variable: - - -> export PATH=/path/to/swift/bin:$PATH - - - - Grid Security - For local execution of jobs, no grid security configuration - is necessary. - - However, when submitting jobs to a remote machine using Globus - Toolkit services, Swift makes use of the - - Grid Security Infrastructure (GSI) for authentication - and authorization. The requirements for this are detailed in - the following sections. Note that GSI is not required to be - configured for local execution (which will usually be the - case when first starting with Swift). - - - - - User Certificate - - - GSI requires a certificate/private key - pair for authentication to - Globus Toolkit - services. The certificate and private key should - be placed into the ~/.globus/usercert.pem and ~/.globus/userkey.pem files, - respectively. - - - - - - - - Certificate Authorities Root Certificates - - - - The Swift client libraries are generally required to authenticate - the services to which they connect. This process requires the - presence on the Swift submit site of the root certificates used - to sign the host certificates of services used. These root - certificates need to be installed in either (or both) the - ~/.globus/certificates - and /etc/grid-security/certificates - directories. A package with the root certificates of the - certificate authorities used in the TeraGrid can be found - here. - - - - - - - - - Swift Properties - - - - A Swift properties file (named swift.properties) can be used to - customize certain configuration aspects of Swift. A shared - version of this file, etc/swift.properties - in the installation directory - can be used to provide installation-wide defaults. A per-user - properties file, ~/.swift/swift.properties can be used for - user specific settings. Swift first loads the shared - configuration file and, if present, the user configuration file. - Any properties not explicitly set in the user configuration file - will be inherited from the shared configuration file. Properties - are specified in the following format: - - -name=value - - - For details about the various properties Swift accepts, please - take a look at the Swift - Properties Section in the Swift - User Guide. - - - - - - - - - Running Swift Examples - - - - The Swift examples can be found in the examples directory in the Swift distribution. - The examples are written in the SwiftScript - language, and have .swift as - a file extension. - - - - - - The Grid Security Infrastructure, which Swift uses, works with - limited time certificates called proxies. These proxies can be - generated from your user certificate and private key using one of - grid-proxy-init or - cog-proxy-init (the latter being a Java Swing - interface to the former). - - - - - - Execution of a Swift workflow is done using the - swift command, which takes the Swift - workflow file name as an argument: - - -> cd examples/swift -> swift - - - The Swift - Command Options Section in the Swift - User Guide contains details about the various options of the - swift. - - - - -
    Deleted: trunk/docs/reallyquickstartguide.xml =================================================================== --- trunk/docs/reallyquickstartguide.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/reallyquickstartguide.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,109 +0,0 @@ - - - - -
    - - Swift Really Quick Start Guide - Source control $LastChangedRevision$ - - - - - - - This guide is a compressed version of the Swift Quick Start - Guide. - - - - - - - - Swift Really Quick Start Guide - - - - - - - Download - Swift. - - - - - - - - Unpack it and add the swift-xyz/bin directory to your - PATH. - - - - - - - - Make sure you have your user certificate, a valid GSI proxy - certificate, and the proper CA root certificates in either - ~/.globus/certificates or - /etc/grid-security/certificates. - - - - - - - - Edit swift-xyz/etc/swift.properties. You - should add your numeric IP address there - (ip.address=x.y.z.w). - - - - - - - - Use the example site catalog and transformation catalog (they - are configured for local submission): - - -cd swift-xyz/etc -cp sites.xml.example sites.xml -cp tc.data.example tc.data - - - - - - - - - Use swift file.dtm to compile and execute - file.dtm. - - - - - - - - Use swift -resume file-<runid>.?.rlog - file.dtm to resume a failed run. - - - - - - - -
    Deleted: trunk/docs/swift-site-model.fig =================================================================== --- trunk/docs/swift-site-model.fig 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/swift-site-model.fig 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,53 +0,0 @@ -#FIG 3.2 Produced by xfig version 3.2.5 -Landscape -Center -Inches -Letter -100.00 -Single --2 -1200 2 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 2100 3450 4425 2025 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 2100 3675 4425 3825 -2 4 0 1 0 11 999 -1 20 0.000 0 0 7 0 0 5 - 8850 4800 4200 4800 4200 675 8850 675 8850 4800 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 2025 8400 2025 8400 2775 7425 2775 7425 2025 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 2850 8400 2850 8400 3600 7425 3600 7425 2850 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 3675 8400 3675 8400 4425 7425 4425 7425 3675 -2 2 0 1 0 5 50 -1 20 0.000 0 0 -1 0 0 5 - 7425 1200 8400 1200 8400 1950 7425 1950 7425 1200 -2 2 0 1 0 6 500 -1 20 0.000 0 0 -1 0 0 5 - 525 3000 2025 3000 2025 4050 525 4050 525 3000 -2 2 0 1 0 6 100 -1 20 0.000 0 0 -1 0 0 5 - 4500 1350 6300 1350 6300 2700 4500 2700 4500 1350 -2 2 0 1 0 6 100 -1 20 0.000 0 0 -1 0 0 5 - 4500 3225 6375 3225 6375 4425 4500 4425 4500 3225 -2 4 0 1 0 11 55 -1 20 0.000 0 0 7 0 0 5 - 8850 5850 4200 5850 4200 5100 8850 5100 8850 5850 -2 4 0 1 0 11 55 -1 20 0.000 0 0 7 0 0 5 - 8850 6675 4200 6675 4200 6075 8850 6075 8850 6675 -3 0 0 1 0 7 50 -1 -1 0.000 0 0 0 2 - 7350 1575 6375 1950 - 0.000 0.000 -3 0 0 1 0 7 50 -1 -1 0.000 0 0 0 2 - 7350 1725 6450 3975 - 0.000 0.000 -4 0 0 50 -1 0 12 0.0000 4 150 450 750 3300 Swift\001 -4 0 0 50 -1 0 12 0.0000 4 150 1155 750 3555 commandline\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 750 3810 client\001 -4 0 0 50 -1 0 12 0.0000 4 195 1500 4725 2100 shared filesystem\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 4800 3900 LRM\001 -4 0 0 50 -1 0 12 0.0000 4 150 1215 7350 900 Worker nodes\001 -4 0 0 50 -1 0 12 0.0000 4 150 465 6525 1425 Posix\001 -4 0 0 50 -1 0 12 0.0000 4 150 1065 5325 5475 Another site\001 -4 0 0 50 -1 0 12 0.0000 4 150 1065 5250 6450 Another site\001 -4 0 0 50 -1 0 12 0.0000 4 150 810 2475 2475 remote fs\001 -4 0 0 50 -1 0 12 0.0000 4 105 600 2475 2730 access\001 -4 0 0 50 -1 0 12 0.0000 4 195 1260 2400 4125 job submission\001 -4 0 0 50 -1 0 12 0.0000 4 195 915 2400 4380 eg GRAM\001 -4 0 0 50 -1 0 12 0.0000 4 195 1080 3075 3000 eg. GridFTP\001 Deleted: trunk/docs/swift-site-model.png =================================================================== (Binary files differ) Added: trunk/docs/tutorial/tutorial.html =================================================================== --- trunk/docs/tutorial/tutorial.html (rev 0) +++ trunk/docs/tutorial/tutorial.html 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,1594 @@ + + + + + +A Swift Tutorial + + + + + +
    +
    +

    1. Abstract

    +
    +

    This is an introductory tutorial on the use of Swift and its programming +language SwiftScript.

    +
    +
    +
    +

    2. Introduction

    +
    +

    This tutorial is intended to introduce new users to the basics of Swift. +It is structured as a series of small exercise/examples which you can +try for yourself as you read along. After the first hello world +example, there are two tracks - the language track (which introduces +features of the SwiftScript language) and the runtime track (which +introduces features of the Swift runtime environment, such as running +jobs on different sites).

    +

    For information on getting an installation of Swift running, consult the +Swift Quickstart Guide http://www.ci.uchicago.edu/swift/guides/quickstartguide.php, and +return to this document when you have successfully run the test +SwiftScript program mentioned there.

    +

    There is also a Swift User’s Guide +http://www.ci.uchicago.edu/swift/guides/userguide.php which contains +more detailed reference material on topics covered in this manual. All +of the programs included in this tutorial can be found in your Swift +distribution in the examples/swift directory.

    +
    +
    +
    +

    3. Hello World

    +
    +

    The first example program, first.swift, outputs a hello world message +into a file called hello.txt.

    +
    +
    +
    first.swift
    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting() {
    +    echo "Hello, world!" stdout=@filename(t);
    +}
    +
    +messagefile outfile <"hello.txt">;
    +
    +outfile = greeting();
    +
    +

    We can run this program as follows:

    +
    +
    +
    $ cd examples/swift/
    +$ swift first.swift
    +Swift svn swift-r3334 (swift modified locally) cog-r2752
    +
    +RunID: 20100526-1925-8zjupq1b
    +Progress:
    +Final status:  Finished successfully:1
    +$ cat hello.txt
    +Hello, world!
    +

    The basic structure of this program is a type definition, an +application procedure definition, a variable definition and then a +call to the procedure:

    +
    +
    +
    type messagefile;
    +

    First we define a new type, called messagefile. In this example, we will +use this messagefile type as the type for our output message.

    +

    All data in SwiftScript must be typed, whether it is stored in memory or +on disk. This example defines a very simple type. Later on we will see +more complex type examples.

    +
    +
    +
    app (messagefile t) greeting() {
    +    echo "Hello, world!" stdout=@filename(t);
    +}
    +

    Next we define a procedure called greeting. This procedure will write +out the "hello world" message to a file.

    +

    To achieve this, it executes the unix utility echo with a parameter +"Hello, world!" and directs the standard output into the output file.

    +

    The actual file to use is specified by the return parameter, t.

    +

    messagefile outfile <"hello.txt">;

    +

    Here we define a variable called outfile. The type of this variable is +messagefile, and we specify that the contents of this variable will be +stored on disk in a file called hello.txt

    +

    outfile = greeting();

    +

    Now we call the greeting procedure, with its output going to the outfile +variable and therefore to hello.txt on disk.

    +

    Over the following exercises, we’ll extend this simple hello world +program to demonstrate various features of Swift.

    +
    +
    +
    +

    4. Language features

    +
    +
    +

    4.1. Parameters

    +

    Procedures can have parameters. Input parameters specify inputs to the +procedure and output parameters specify outputs. Our helloworld greeting +procedure already uses an output parameter, t, which indicates where the +greeting output will go. In this section, we will add an input parameter +to the greeting function.

    +

    The code changes from first.swift are highlighted below.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +messagefile outfile <"hello2.txt">;
    +
    +outfile = greeting("hello world");
    +

    We have modified the signature of the greeting procedure to indicate +that it takes a single parameter, s, of type string.

    +

    We have modified the invocation of the echo utility so that it takes +the value of s as a parameter, instead of the string literal "Hello, +world!".

    +

    We have modified the output file definition to point to a different file +on disk.

    +

    We have modified the invocation of greeting so that a greeting string is +supplied.

    +

    The code for this section can be found in parameter.swift. It can be +invoked using the swift command, with output appearing in hello2.txt:

    +
    +
    +
    $ swift parameter.swift
    +

    Now that we can choose our greeting text, we can call the same procedure +with different parameters to generate several output files with +different greetings. The code is in manyparam.swift and can be run as +before using the swift command.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +messagefile english <"english.txt">;
    +messagefile french <"francais.txt">;
    +english = greeting("hello");
    +french = greeting("bonjour");
    +
    +messagefile japanese <"nihongo.txt">;
    +japanese = greeting("konnichiwa");
    +

    Note that we can intermingle definitions of variables with invocations +of procedures.

    +

    When this program has been run, there should be three new files in the +working directory (english.txt, francais.txt and nihongo.txt) each +containing a greeting in a different language.

    +

    In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified - see Named and Optional Parameters.

    +
    +
    +

    4.2. Adding another application

    +

    Now we’ll define a new application procedure. The procedure we define +will capitalise all the words in the input file.

    +

    To do this, we’ll use the unix tr (translate) utility. Here is an +example of using tr on the unix command line, not using Swift:

    +
    +
    +
    $ echo hello | tr '[a-z]' '[A-Z]'
    +HELLO
    +
    There are several steps
      +
    • +

      +transformation catalog +

      +
    • +
    • +

      +application block +

      +
    • +
    +

    First we need to modify the transformation catalog to define a logical +transformation for the tc utility. The transformation catalog can be +found in etc/tc.data. There are already several entries specifying +where programs can be found. Add a new line to the file, specifying +where tr can be found (usually in /usr/bin/tr but it may differ on +your system), like this:

    +
    +
    +
    localhost       tr      /usr/bin/tr     INSTALLED       INTEL32::LINUX  null
    +

    For now, ignore all of the fields except the second and the third. The +second field tr specifies a logical application name and the third +specifies the location of the application executable.

    +

    Now that we have defined where to find tr, we can use it in SwiftScript.

    +

    We can define a new procedure, capitalise, which calls tr.

    +
    +
    +
    (messagefile o) capitalise(messagefile i) {
    +    app {
    +        tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    +    }
    +}
    +

    We can call capitalise like this:

    +
    +
    +
    messagefile final <"capitals.txt">;
    +final = capitalise(hellofile);
    +

    So a full program based on the first exercise might look like this:

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s) {
    +    echo s stdout=@filename(t);
    +}
    +
    +app (messagefile o) capitalise(messagefile i) {
    +    tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    +}
    +
    +messagefile hellofile <"hello.txt">;
    +messagefile final <"capitals.txt">;
    +
    +hellofile = greeting("hello from Swift");
    +final = capitalise(hellofile);
    +

    We can use the swift command to run it like this.

    +
    +
    +
    $ swift second_procedure.swift
    +...
    +$ cat capitals.txt
    +HELLO FROM SWIFT
    +
    +
    +

    4.3. Anonymous files

    +

    In the previous section, the file greeting.txt is used only to store +an intermediate result. We don’t really care about which name is used +for the file, and we can let Swift choose the name.

    +

    To do that, omit the mapping entirely when declaring outfile:

    +
    +
    +
    messagefile outfile;
    +

    Swift will choose a filename, which in the present version will be in a +subdirectory called _concurrent.

    +
    +
    +

    4.4. Datatypes

    +

    All data in variables and files has a data type. So far, we’ve seen two +types:

    +
      +
    • +

      +string - this is a built-in type for storing strings of text in + memory, much like in other programming languages +

      +
    • +
    • +

      +messagefile - this is a user-defined type used to mark files as + containing messages +

      +
    • +
    +

    SwiftScript has the additional built-in types: boolean, integer and +float that function much like their counterparts in other programming +languages.

    +

    It is also possible to create user defined types with more structure, +for example:

    +
    +
    +
    type details {
    +    string name;
    +    int pies;
    +}
    +

    Each element of the structured type can be accessed using a . like this:

    +
    +
    +
    person.name = "john";
    +

    The following complete program, types.swift, outputs a greeting using a +user-defined structure type to hold parameters for the message:

    +
    +
    +
    type messagefile;
    +
    +type details {
    +    string name;
    +    int pies;
    +}
    +
    +app (messagefile t) greeting (details d) {
    +    echo "Hello. Your name is" d.name "and you have eaten" d.pies "pies." stdout=@filename(t);
    +}
    +
    +details person;
    +
    +person.name = "John";
    +person.pies = 3;
    +
    +messagefile outfile <"q15.txt">;
    +
    +outfile = greeting(person);
    +

    Structured types can be comprised of marker types for files. See the +later section on mappers for more information about this.

    +
    +
    +

    4.5. Arrays

    +

    We can define arrays using the [] suffix in a variable declaration:

    +
    +
    +
    messagefile m[];
    +

    This program, q5.swift, will declare an array of message files.

    +
    +
    +
    type messagefile;
    +
    +app (messagefile t) greeting (string s[]) {
    +     echo s[0] s[1] s[2] stdout=@filename(t);
    +}
    +
    +messagefile outfile <"q5out.txt">;
    +
    +string words[] = ["how","are","you"];
    +
    +outfile = greeting(words);
    +

    Observe that the type of the parameter to greeting is now an array of +strings, string s[], instead of a single string, string s, that +elements of the array can be referenced numerically, for example s[0], +and that the array is initialised using an array literal, +["how","are","you"].

    +
    +
    +

    4.6. Mappers

    +

    A significant difference between SwiftScript and other languages is that +data can be referred to on disk through variables in a very similar +fashion to data in memory. For example, in the above examples we have +seen a variable definition like this:

    +
    +
    +
    messagefile outfile <"q13greeting.txt">;
    +

    This means that outfile is a dataset variable, which is mapped to a +file on disk called g13greeting.txt. This variable can be assigned to +using = in a similar fashion to an in-memory variable. We can say that +outfile is mapped onto the disk file q13greeting.txt by a mapper.

    +

    There are various ways of mapping in SwiftScript. Two forms have already +been seen in this tutorial. Later exercises will introduce more forms.

    +

    The two forms of mapping seen so far are:

    +

    simple named mapping - the name of the file that a variable is mapped to +is explictly listed. Like this:

    +
    +
    +
    messagefile outfile <"greeting.txt">;
    +

    This is useful when you want to explicitly name input and output files +for your program. For example, outfile in exercise HELLOWORLD.

    +

    anonymous mapping - no name is specified in the source code. A name is +automatically generated for the file. This is useful for intermediate +files that are only referenced through SwiftScript, such as outfile in +exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by +ommitting any mapper definition, like this:

    +
    +
    +
    messagefile outfile;
    +

    Later exercises will introduce other ways of mapping from disk files to +SwiftScript variables.

    +

    TODO: introduce @v syntax.

    +
    +

    4.6.1. The Regexp Mapper

    +

    In this exercise, we introduce the regexp mapper. This mapper +transforms a string expression using a regular expression, and uses the +result of that transformation as the filename to map.

    +

    regexp.swift demonstrates the use of this by placing output into a +file that is based on the name of the input file: our input file is +mapped to the inputfile variable using the simple named mapper, and then +we use the regular expression mapper to map the output file. Then we use +the countwords() procedure to count the works in the input file and +store the result in the output file. In order for the countwords() +procedure to work correctly, add the wc utility (usually found in +/usr/bin/wc) to tc.data.

    +

    The important bit of regexp.swift is:

    +
    +
    +
    messagefile inputfile <"q16.txt">;
    +
    +countfile c <regexp_mapper;
    +             source=@inputfile,
    +             match="(.*)txt",
    +             transform="\\1count"
    +            >;
    +
    +
    +

    4.6.2. fixed_array_mapper

    +

    The fixed array mapper maps a list of files into an array - each +element of the array is mapped into one file in the specified directory. +See fixedarray.swift.

    +
    +
    +
    type messagefile {}
    +type countfile {}
    +
    +(countfile t) countwords (messagefile f) {
    +    app {
    +        wc "-w" @filename(f) stdout=@filename(t);
    +    }
    +}
    +
    +string inputNames = "one.txt two.txt three.txt";
    +string outputNames = "one.count two.count three.count";
    +
    +messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    +countfile outputfiles[] <fixed_array_mapper;files=outputNames>;
    +
    +outputfiles[0] = countwords(inputfiles[0]);
    +outputfiles[1] = countwords(inputfiles[1]);
    +outputfiles[2] = countwords(inputfiles[2]);
    +
    +
    +
    +

    4.7. foreach

    +

    SwiftScript provides a control structure, foreach, to operate on each +element of an array.

    +

    In this example, we will run the previous word counting example over +each file in an array without having to explicitly list the array +elements. The source code for this example is in foreach.swift. The +three input files: one.txt, two.txt and three.txt are supplied. +After you have run the workflow, you should see that there are three +output files: one.count, two.count and three.count, each +containing the word count for the corresponding input file. We combine +the use of the fixed_array_mapper and the regexp_mapper.

    +
    +
    +
    type messagefile {}
    +type countfile {}
    +
    +(countfile t) countwords (messagefile f) {
    +    app {
    +        wc "-w" @filename(f) stdout=@filename(t);
    +    }
    +}
    +
    +string inputNames = "one.txt two.txt three.txt";
    +
    +messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    +
    +
    +foreach f in inputfiles {
    +  countfile c<regexp_mapper;
    +            source=@f,
    +            match="(.*)txt",
    +            transform="\\1count">;
    +  c = countwords(f);
    +}
    +
    +
    +

    4.8. If

    +

    Decisions can be made using if, like this:

    +
    +
    +
    if(morning) {
    +  outfile = greeting("good morning");
    +} else {
    +  outfile = greeting("good afternoon");
    +}
    +

    if.swift contains a simple example of this. Compile and run if.swift +and see that it outputs "good morning". Changing the morning variable +from true to false will cause the program to output "good afternoon".

    +
    +
    +

    4.9. Sequential iteration

    +

    A development version of Swift after 0.2 (revision 1230) introduces a +sequential iteration construct.

    +

    The following example demonstrates a simple application: each step of +the iteration is a string representation of the byte count of the +previous step’s output, with iteration terminating when the byte count +reaches zero.

    +

    Here’s the program:

    +
    +
    +
    type counterfile;
    +
    +app (counterfile t) echo(string m) {
    +    echo m stdout=@filename(t);
    +}
    +
    +app (counterfile t) countstep(counterfile i) {
    +    wcl @filename(i) @filename(t);
    +}
    +
    +counterfile a[]  <simple_mapper;prefix="foldout">;
    +
    +a[0] = echo("793578934574893");
    +
    +iterate v {
    +  a[v+1] = countstep(a[v]);
    + trace("extract int value ",@extractint(a[v+1]));
    +} until (@extractint(a[v+1]) <= 1);
    +

    echo is the standard unix echo.

    +

    wcl is our application code - it counts the number of bytes in the one +file and writes that count out to another, like this:

    +
    +
    +
    $ cat ../wcl
    +#!/bin/bash
    +echo -n $(wc -c < $1) > $2
    +
    +$ echo -n hello > a
    +$ wcl a b
    +$ cat b
    +5
    +

    Install the above wcl script somewhere and add a transformation catalog +entry for it. Then run the example program like this:

    +
    +
    +
    $ swift iterate.swift
    +Swift svn swift-r3334 cog-r2752
    +
    +RunID: 20100526-2259-gtlz8zf4
    +Progress:
    +SwiftScript trace: extract int value , 16.0
    +SwiftScript trace: extract int value , 2.0
    +SwiftScript trace: extract int value , 1.0
    +Final status:  Finished successfully:4
    +
    +$ ls foldout*
    +foldout0000  foldout0001  foldout0002  foldout0003
    +
    +
    +
    +
    +

    5. Runtime features

    +
    +
    +

    5.1. Visualising the workflow as a graph

    +

    When running a workflow, its possible to generate a provenance graph at +the same time:

    +
    +
    +
    $ swift -pgraph graph.dot first.swift
    +$ dot -ograph.png -Tpng graph.dot
    +

    graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org.

    +
    +
    +

    5.2. Running on a remote site

    +

    As configured by default, all jobs are run locally. In the previous +examples, we’ve invoked echo and tr executables from our SwiftScript +program. These have been run on the local system (the same computer on +which you ran swift). We can also make our computations run on a +remote resource.

    +
    + + + +
    +Warning +This example is necessarily more vague than previous examples, +because its requires access to remote resources. You should ensure that +you can submit a job using the globus-job-run (or globusrun-ws?) +command(s).
    +
    +

    We do not need to modify any SwiftScript code to run on another +resource. Instead, we must modify another catalog, the site catalog. +This catalog provides details of the location that applications will be +run, with the default settings referring to the local machine. We will +modify it to refer to a remote resource - the UC Teraport cluster. If +you are not a UC Teraport user, you should use details of a different +resource that you do have access to.

    +

    The site catalog is located in etc/sites.xml and is a relatively +straightforward XML format file. We must modify each of the following +three settings: gridftp (which indicates how and where data can be +transferred to the remote resource), jobmanager (which indicates how +applications can be run on the remote resource) and workdirectory (which +indicates where working storage can be found on the remote resource).

    +
    +
    +

    5.3. Writing a mapper

    +

    This section will introduce writing a custom mapper so that Swift is +able to access data files laid out in application-specific ways.

    +

    An application-specific mapper must take the form of a Java class that +implements the Mapper +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/Mapper.html +interface.

    +

    Usually you don’t need to implement this interface directly, because +Swift provides a number of more concrete classes with some functionality +already implemented.

    +

    The hierarchy of helper classes is:

    + +

    This is the abstract interface for mappers in Swift. You must +implement methods to provide access to mapper properties, to map from a +SwiftScript dataset path (such as foo[1].bar) to a file name, to check +whether a file exists. None of the default Swift mappers implement this +interface directly - instead they use one of the following helper classes.

    + +

    This provides helper methods to manage mapper properties and to handle +existance checking. Examples of mappers which use this class are: +Array Mapper, +CSV Mapper, +Fixed Array Mapper, +Regexp Mapper, +and Single File Mapper.

    +

    AbstractFileMapper +This provides a helper class for mappers which select files based on +selecting files from a directory listing. It is necessary to write some +helper methods that are different from the above mapper methods. +Examples of mappers which use this class are: +simple_mapper, +filesys_mapper, +and the (undocumented) StructuredRegularExpressionMapper.

    +

    In general, to write a mapper, choose either the AbstractMapper or the +AbstractFileMapper and extend those. If your mapper will generally +select the files it returns based on a directory listing and will +convert paths to filenames using some regular conversion (for example, +in the way that simple_mapper maps files in a directory that match a +particular pattern), then you should probably use the +AbstractFileMapper. If your mapper will produce a list of files in some +other way (for example, in the way that csv_mapper maps based on +filenames given in a CSV file rather than looking at which files are in +a directory), then you should probably use the AbstractMapper.

    +
    +
    +

    5.4. Writing a very basic mapper

    +

    In this section, we will write a very basic (almost useless) mapper that +will map a SwiftScript dataset into a hardcoded file called +myfile.txt, like this:

    +
    +
    +
    Swift variable                            Filename
    +
    +
    +
    +
    var   <----------------------------->    myfile.txt
    +
    +

    We should be able to use the mapper we write in a SwiftScript program +like this:

    +
    +
    +
    type file;
    +file f <my_first_mapper;>;
    +

    First we must choose a base class - AbstractMapper or +AbstractFileMapper. We aren’t going to use a directory listing to decide +on our mapping - we are getting the mapping from some other source (in +fact, it will be hard coded). So we will use AbstractMapper.

    +

    So now onto the source code. We must define a subclass of AbstractMapper +and implement several mapper methods: isStatic, existing, and map. These +methods are documented in the javadoc for the Mapper interface.

    +

    Here is the code implementing this mapper. Put this in your source +vdsk directory, make a directory src/tutorial/|and put this file in +src/tutorial/MyFirstMapper.java.

    +
    +
    +
    package tutorial;
    +
    +import java.util.Arrays;
    +import java.util.Collection;
    +import java.util.Collections;
    +
    +import org.griphyn.vdl.mapping.AbsFile;
    +import org.griphyn.vdl.mapping.AbstractMapper;
    +import org.griphyn.vdl.mapping.Path;
    +import org.griphyn.vdl.mapping.PhysicalFormat;
    +
    +public class MyFirstMapper extends AbstractMapper {
    +
    +  AbsFile myfile = new AbsFile("myfile.txt");
    +
    +  public boolean isStatic() {
    +    return false;
    +  }
    +
    +  public Collection existing() {
    +    if (myfile.exists())
    +      return Arrays.asList(new Path[] {Path.EMPTY_PATH});
    +    else
    +      return Collections.EMPTY_LIST;
    +  }
    +
    +  public PhysicalFormat map(Path p) {
    +    if(p.equals(Path.EMPTY_PATH))
    +      return myfile;
    +    else
    +      return null;
    +  }
    +}
    +

    Now we need to inform the Swift engine about the existence of this +mapper. We do that by editing the MapperFactory class definition, in +src/org/griphyn/vdl/mapping/MapperFactory.java and adding a +registerMapper call alongside the existing registerMapper calls, like this:

    +
    +
    +
    registerMapper("my_first_mapper", tutorial.MyFirstMapper.class);
    +

    The first parameter is the name of the mapper that will be used in +SwiftScript program. The second parameter is the new Mapper class that +we just wrote.

    +

    Now rebuild Swift using the "ant redist" target.

    +

    This new Swift build will be aware of your new mapper. We can test it +out with a hello world program:

    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting() {
    +    app {
    +        echo "hello" stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile <my_first_mapper;>;
    +
    +outfile = greeting();
    +

    Run this program, and hopefully you will find the "hello" string has +been output into the hard coded output file myfile.txt:

    +
    +
    +
    $ cat myfile.txt
    +hello
    +

    So that’s a first very simple mapper implemented. Compare the source +code to the single_file_mapper in +SingleFileMapper.java. +There is not much more code to the single_file_mapper - mostly code to +deal with the file parameter.

    +
    +
    +

    5.5. Starting and restarting

    +

    Now we’re going to try out the restart capabilities of Swift. We will +make a workflow that will deliberately fail, and then we will fix the +problem so that Swift can continue with the workflow.

    +

    First we have the program in working form, restart.swift.

    +
    +
    +
    type file;
    +
    +app (file f) touch() {
    +    touch @f;
    +}
    +
    +app (file f) processL(file inp) {
    +    echo "processL" stdout=@f;
    +}
    +
    +app (file f) processR(file inp) {
    +    broken "process" stdout=@f;
    +}
    +
    +app (file f) join(file left, file right) {
    +    echo "join" @left @right stdout=@f;
    +}
    +
    +file f = touch();
    +
    +file g = processL(f);
    +file h = processR(f);
    +
    +file i = join(g,h);
    +

    We must define some transformation catalog entries:

    +
    +
    +
    localhost   touch   /usr/bin/touch  INSTALLED   INTEL32::LINUX  null
    +localhost   broken  /bin/true   INSTALLED   INTEL32::LINUX  null
    +

    Now we can run the program:

    +
    +
    +
    $ swift restart.swift
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1119-3kgzzi15
    +Progress:
    +Final status:  Finished successfully:4
    +

    Four jobs run - touch, echo, broken and a final echo. (note that broken +isn’t actually broken yet).

    +

    Now we will break the broken job and see what happens. Replace the +definition in tc.data for broken with this:

    +
    +
    +
    localhost    broken     /bin/false   INSTALLED       INTEL32::LINUX  null
    +

    Now when we run the workflow, the broken task fails:

    +
    +
    +
    $ swift restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1121-tssdcljg
    +Progress:
    +Progress:  Stage in:1  Finished successfully:2
    +Execution failed:
    +    Exception in broken:
    +Arguments: [process]
    +Host: localhost
    +Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj
    +stderr.txt:
    +stdout.txt:
    +

    From the output we can see that touch and the first echo completed, but +then broken failed and so swift did not attempt to execute the final echo.

    +

    There will be a restart log with the same name as the RunID:

    +
    +
    +
    $ ls *20100526-1121-tssdcljg*rlog
    +restart-20100526-1121-tssdcljg.0.rlog
    +

    This restart log contains enough information for swift to know which +parts of the workflow were executed successfully.

    +

    We can try to rerun it immediately, like this:

    +
    +
    +
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1125-7yx0zi6d
    +Progress:
    +Execution failed:
    +    Exception in broken:
    +Arguments: [process]
    +Host: localhost
    +Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj
    +stderr.txt:
    +stdout.txt:
    +
    +----
    +
    +Caused by:
    +    Exit code 1
    +

    Swift tried to resume the workflow by executing "broken" again. It did +not try to run the touch or first echo jobs, because the restart log +says that they do not need to be executed again.

    +

    Broken failed again, leaving the original restart log in place.

    +

    Now we will fix the problem with "broken" by restoring the original +tc.data line that works.

    +

    Remove the existing "broken" line and replace it with the successful +tc.data entry above:

    +
    +
    +
    localhost       broken          /bin/true   INSTALLED       INTEL32::LINUX  null
    +

    Now run again:

    +
    +
    +
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    +
    +Swift 0.9 swift-r2860 cog-r2388
    +
    +RunID: 20100526-1128-a2gfuxhg
    +Progress:
    +Final status:  Initializing:2  Finished successfully:2
    +

    Swift tries to run "broken" again. This time it works, and so Swift +continues on to execute the final piece of the workflow as if nothing +had ever gone wrong.

    +
    +
    +
    +
    +

    6. bits

    +
    +
    +

    6.1. Named and optional parameters

    +

    anchor:named_parameters +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified:

    +
    +
    +
    (messagefile t) greeting (string s="hello") {
    +    app {
    +        echo s stdout=@filename(t);
    +    }
    +}
    +

    When we invoke the procedure, we can specify values for the parameters +by name. The following code can be found in q21.swift.

    +
    +
    +
    french = greeting(s="bonjour");
    +

    or we can let the default value apply:

    +
    +
    +
    english = greeting();
    +
    +
    +
    +
    +

    + + + Added: trunk/docs/tutorial/tutorial.pdf =================================================================== --- trunk/docs/tutorial/tutorial.pdf (rev 0) +++ trunk/docs/tutorial/tutorial.pdf 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,4213 @@ +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (section.1) >> +endobj +8 0 obj +(Introduction) +endobj +9 0 obj +<< /S /GoTo /D (section.2) >> +endobj +12 0 obj +(Hello World) +endobj +13 0 obj +<< /S /GoTo /D (section.3) >> +endobj +16 0 obj +(Language features) +endobj +17 0 obj +<< /S /GoTo /D (subsection.3.1) >> +endobj +20 0 obj +(Parameters) +endobj +21 0 obj +<< /S /GoTo /D (subsection.3.2) >> +endobj +24 0 obj +(Adding another application) +endobj +25 0 obj +<< /S /GoTo /D (subsection.3.3) >> +endobj +28 0 obj +(Anonymous files) +endobj +29 0 obj +<< /S /GoTo /D (subsection.3.4) >> +endobj +32 0 obj +(Datatypes) +endobj +33 0 obj +<< /S /GoTo /D (subsection.3.5) >> +endobj +36 0 obj +(Arrays) +endobj +37 0 obj +<< /S /GoTo /D (subsection.3.6) >> +endobj +40 0 obj +(Mappers) +endobj +41 0 obj +<< /S /GoTo /D (subsubsection.3.6.1) >> +endobj +44 0 obj +(The Regexp Mapper) +endobj +45 0 obj +<< /S /GoTo /D (subsubsection.3.6.2) >> +endobj +48 0 obj +(fixed\137array\137mapper) +endobj +49 0 obj +<< /S /GoTo /D (subsection.3.7) >> +endobj +52 0 obj +(foreach) +endobj +53 0 obj +<< /S /GoTo /D (subsection.3.8) >> +endobj +56 0 obj +(If) +endobj +57 0 obj +<< /S /GoTo /D (subsection.3.9) >> +endobj +60 0 obj +(Sequential iteration) +endobj +61 0 obj +<< /S /GoTo /D (section.4) >> +endobj +64 0 obj +(Runtime features) +endobj +65 0 obj +<< /S /GoTo /D (subsection.4.1) >> +endobj +68 0 obj +(Visualising the workflow as a graph) +endobj +69 0 obj +<< /S /GoTo /D (subsection.4.2) >> +endobj +72 0 obj +(Running on a remote site) +endobj +73 0 obj +<< /S /GoTo /D (subsection.4.3) >> +endobj +76 0 obj +(Writing a mapper) +endobj +77 0 obj +<< /S /GoTo /D (subsection.4.4) >> +endobj +80 0 obj +(Writing a very basic mapper) +endobj +81 0 obj +<< /S /GoTo /D (subsection.4.5) >> +endobj +84 0 obj +(Starting and restarting) +endobj +85 0 obj +<< /S /GoTo /D (section.5) >> +endobj +88 0 obj +(bits) +endobj +89 0 obj +<< /S /GoTo /D (subsection.5.1) >> +endobj +92 0 obj +(Named and optional parameters) +endobj +93 0 obj +<< /S /GoTo /D [94 0 R /FitH ] >> +endobj +96 0 obj << +/Length 292 +/Filter /FlateDecode +>> +stream +x??Q?JA ??W??=l?d???QA???{+=????"J??o?v??'2??{//??f???K?/???{??N?v?S?]n4??e??m 3?j,?? t????iY?lq?7?c?5?????G??mV??Y???4??U$?Z"4U???d????FO??r,???*?????NDp?GD#?%/S??g???8vY???j? ?&w'???H????M????%9???i??558????+????]cq??4?(b ???(?r[E??jZq?+??=-???m'???S?2endstream +endobj +94 0 obj << +/Type /Page +/Contents 96 0 R +/Resources 95 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +97 0 obj << +/D [94 0 R /XYZ 56.6929 815.7613 null] +>> endobj +104 0 obj << +/D [94 0 R /XYZ 56.6929 759.0684 null] +>> endobj +95 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +111 0 obj << +/Length 1869 +/Filter /FlateDecode +>> +stream +x??[?r?F??+p$??????$?X????\?H??pQ 0??> +1@C?eP? +-???????8d??X?4????2E?f"??Lhv??4a +f?A???????q????6??hCUf?!?q?]/^O???\?????mY??z&?t_??U????~QXf!?U?4a??l?qJ?C????N~?nYyR?1"??&???lO?bB?t?e?J?t,?L? +??o???????].??V +?BH????3??cLU?????(???1??m???||(?4?I]?S?5??} + ?54$?ZQ`?9??N?o?b??t???????K?qx<*T?S?-*I?)??r??6?((??u??uhQUn?????z????jf?tW?q-1???? +*I??? ??Z(F????Zx?U?M-~??w??nY??v????F??`??Dp?;????$)_???&5????]@?e? =?????y(9?J????i^??e?,?"K??B?x??I???E:w??Ef? +EZ???VG?z??N4XF??????!N??=?L`?Uu^ +;?x??!%?V&? -???n??+? +????I]?g??hP  ?J?rvJb???? ???5???????J?a?a?????D??,???????A????s&?~????\V{??????????o?-?< ???nP ??iB,1O(??R?c? +??6*?V5J?K??=W??*?????A^??{?m?X |?x?W+????W??P???z???? +y??}R?c? +?6*??P8???]?t?p????? +7?R?vW,????RGY? B??tN?]?? Fi~????G_?-?bU-7???2^?8?J$v-???ml??6re??0l???H?(,??4??GMqK\dL?_PE?????^>?(?9M|???j???2W???mY]?9?V????t?U???Y?.??G%X1c?B??????4???? ?^??.@??Rsn?uJ?{'E?.DU?P?NJ???}?;)/?`??9WR?"?;???bxT???[H?]I??U?????? u(H{+??????a??W????B?0ct?+??m?????_??7?Z???]??GkT. ????> endobj +113 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 706.3558 126.6998 715.332] +/Subtype /Link +/A << /S /GoTo /D (section.1) >> +>> endobj +117 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 678.4604 124.7471 687.4366] +/Subtype /Link +/A << /S /GoTo /D (section.2) >> +>> endobj +118 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 648.6621 151.3174 659.5412] +/Subtype /Link +/A << /S /GoTo /D (section.3) >> +>> endobj +119 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 632.6522 139.6612 641.4988] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.1) >> +>> endobj +120 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 612.6622 204.5674 623.5661] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.2) >> +>> endobj +121 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 594.7294 163.2031 605.6333] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.3) >> +>> endobj +122 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 576.7967 135.3873 587.7006] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.4) >> +>> endobj +123 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 558.8639 122.6553 569.7678] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.5) >> +>> endobj +124 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 540.9311 130.4061 551.8351] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.6) >> +>> endobj +125 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 522.9984 209.0213 533.9023] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.3.6.1) >> +>> endobj +126 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [93.5547 505.0656 207.5069 515.9696] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.3.6.2) >> +>> endobj +127 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 489.1902 125.415 498.0368] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.7) >> +>> endobj +128 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 471.2574 102.1823 480.1041] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.8) >> +>> endobj +129 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 451.2674 173.3045 462.1713] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.9) >> +>> endobj +130 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 425.4093 146.326 434.3856] +/Subtype /Link +/A << /S /GoTo /D (section.4) >> +>> endobj +131 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 405.4392 238.2109 416.3432] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1) >> +>> endobj +132 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 387.5065 195.7206 398.4104] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.2) >> +>> endobj +133 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 369.5737 165.823 380.4777] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.3) >> +>> endobj +134 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 351.641 208.8313 362.5449] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.4) >> +>> endobj +135 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 333.7082 184.094 344.6122] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.5) >> +>> endobj +136 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 307.8502 88.1347 316.8264] +/Subtype /Link +/A << /S /GoTo /D (section.5) >> +>> endobj +137 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [70.6406 287.8801 222.5397 298.784] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.1) >> +>> endobj +112 0 obj << +/D [110 0 R /XYZ 56.6929 815.7613 null] +>> endobj +109 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +140 0 obj << +/Length 388 +/Filter /FlateDecode +>> +stream +x??R?N?0??7?C???}#H???? +1???Hm?+???6 ?D?P???????3??{?b"1O?[???{??FL1??s?M???X??x??\?7??f?:??\=????a=[|6?4????l????6???!????????Cb?P?0?#M?4??-dM??Z6? ?C==kXe J??H???? ?V1??z3?l?B=??]?????0?c?d??Y??G?F?Fr!g? i?????\a$#~`??^v????O?V??]?$??` ?\_r?Mx???9?4???H?" ?,?QU????QN???6??j????V?4?c?????:??Xt?_??jW#k?y??????????M????~=;?X??{???>O??K?h????|G??q??r?rendstream +endobj +139 0 obj << +/Type /Page +/Contents 140 0 R +/Resources 138 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +141 0 obj << +/D [139 0 R /XYZ 56.6929 815.7613 null] +>> endobj +138 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +144 0 obj << +/Length 4447 +/Filter /FlateDecode +>> +stream +x??][??8r~??? ? +????M?A&??d6y???`v?A?Vw{?m??2='???????(?>?=?K?KT??#Y?*RT5?Q??fRU?zf?$Z11[>???{x??;?i?h??????n#??&??j??n?8Q????????????_?,??????wGw??????q?_7?????-pa3\?@.?? ????ZJn?0??????0?????}???!?A???????l???;J????3?P?????I?B?P?y?????9???"5r?c?B??D?|??J?????j?qwr?f?.?????n??4?C??sw??Ws?6+?h???C++??_?[_?v^??R?????r???+?Y? E??f?su?w??jd???0*k_?????^-P???m?????A?v6?o|[??f{j???????5B????J?????`?Yw???mpl??@?? &?z|??????I?l?+i??^%?????~?7??|q?? +bW???????????????s?p?:%???/???????/??x?u???N?;???????=`?I??I-??? +2*%?q??~>6????{??V*?4?@}8?|???:????????z??m??d{/:??;?A?????yZ???a?????8?+??et??????<[?Xc???:????9?????????7J??rM`X???~G??????o^?5??????c3????????4lSL?` +L?????j?%K??rC48???`l@???????V????i?=????{[E +?????t%??0;w????q +?< +(?g?????i???7??)?kW????n???5L?????,??o%l6??+i\A??t?????F???????8?\k????????[%??????U ?? +3?I???sT????E??? t}??VR??? ????]?U ????|???B% +?H)?? +M?? 0Q? :Xm??:??l???????I ?:Z????f{j6?y?/6???(???rsZM1?;!>_s????????? L?S~8???[N!8z??7?nVI?????/??%??h5h*???&T????K? n#?S?mVd n "f(??|?????(p??1?T??;4?W??u^1>?????lw:>???K7?'Dbp??'Dfo?j?I?py??????%x?v??G????/R?:]-???_-????RUWDY???j P???.g???H????U???U +O?9I?2??:?,:???] C#t?!v?(?+????&$?b\?Vj(? 0?i?~??? ?(?? ??3????????6?h?T???|LE4?Ut??]??PWc?;?? ?h????! F?I?Y??'??M?????`??_????~?.~?! J5p?t a???J???@ec??OIcp: +=????D??.B3-?*A d=h???A$???t???E?*HO?????????U??Z???Z????M +M????p?4O??Bkb?0?.?4??D??:ue?&Lb??Q? ??T???^l?2m???G?Ih???O???Kj0?h??????HK??aa?FM?f??q??% _???o[?95\??????T???N???(*J???'????????R`*8+G)??,?C????$??EWD??? $????y???y?"0?n M"??sNZ?O???????????6???????aW?'9?+O?+??^U?<;@_ql????????}0??|????ug9??u?? ???O?T5x????4?? ??s7?h?m?W??9??????? d?P*?{9??C????6?>??????)???`x???y?????? ZWz\?%????p|H'>?+?e??????,???????Q???Ok+?wo?o???#??? ???? +?????84?.????????@???Lv?????[3,???sdUX????????Ld?-"UA????M? +-???'t????xG'??G???{?U?v??`G? ??RT?R???????3?????;??5=Y\??tq??9?Br?? ?????y??????m??TYh?HU?r??9???K O^|4????]M?? +?p??nFSBfi(? +C7?L???D@???H????to0???Q?X_-??oi:#??5?*?S??W???q??e3?)???V0?,??.???x??hL:???T?)????h3{B3G|?%??O?N??7??JD??k?*?a??a??3 ???G6=6^?????'?{/c????\?? +????96!??+?g????SH???u%?g???~~h1???????? ?:&I%19(????z??????^?a +?n?????/L???6?)???????q???[_??????; ??Bw????L?dr&cZX?????]/???U?c6??w?TS??81?v??????ld??R???? ;?vI6?`?? B??s?vo??+??es??Ew(2?'PMe# ?N{#??dd??g????G???3?c?.?????????=(??????K???i8???|d?X2??h^?K-??> endobj +150 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [427.3941 660.5925 567.9254 671.4964] +/Subtype/Link/A<> +>> endobj +151 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 648.6373 165.3344 659.5412] +/Subtype/Link/A<> +>> endobj +152 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [199.0314 618.7494 421.0166 629.6533] +/Subtype/Link/A<> +>> endobj +145 0 obj << +/D [143 0 R /XYZ 56.6929 815.7613 null] +>> endobj +6 0 obj << +/D [143 0 R /XYZ 56.6929 759.0684 null] +>> endobj +146 0 obj << +/D [143 0 R /XYZ 56.6929 731.2722 null] +>> endobj +10 0 obj << +/D [143 0 R /XYZ 56.6929 580.8258 null] +>> endobj +153 0 obj << +/D [143 0 R /XYZ 56.6929 543.8291 null] +>> endobj +154 0 obj << +/D [143 0 R /XYZ 61.6742 493.2291 null] +>> endobj +155 0 obj << +/D [143 0 R /XYZ 61.6742 492.6512 null] +>> endobj +159 0 obj << +/D [143 0 R /XYZ 61.6742 481.6923 null] +>> endobj +160 0 obj << +/D [143 0 R /XYZ 61.6742 470.7334 null] +>> endobj +161 0 obj << +/D [143 0 R /XYZ 61.6742 459.7745 null] +>> endobj +162 0 obj << +/D [143 0 R /XYZ 61.6742 448.8156 null] +>> endobj +163 0 obj << +/D [143 0 R /XYZ 61.6742 437.8567 null] +>> endobj +164 0 obj << +/D [143 0 R /XYZ 61.6742 426.8978 null] +>> endobj +165 0 obj << +/D [143 0 R /XYZ 61.6742 415.9389 null] +>> endobj +166 0 obj << +/D [143 0 R /XYZ 61.6742 404.98 null] +>> endobj +167 0 obj << +/D [143 0 R /XYZ 56.6929 354.9229 null] +>> endobj +168 0 obj << +/D [143 0 R /XYZ 56.6929 356.3824 null] +>> endobj +169 0 obj << +/D [143 0 R /XYZ 56.6929 345.4235 null] +>> endobj +170 0 obj << +/D [143 0 R /XYZ 56.6929 334.4646 null] +>> endobj +171 0 obj << +/D [143 0 R /XYZ 56.6929 323.5057 null] +>> endobj +172 0 obj << +/D [143 0 R /XYZ 56.6929 312.5468 null] +>> endobj +173 0 obj << +/D [143 0 R /XYZ 56.6929 301.5879 null] +>> endobj +174 0 obj << +/D [143 0 R /XYZ 56.6929 290.629 null] +>> endobj +175 0 obj << +/D [143 0 R /XYZ 56.6929 279.67 null] +>> endobj +176 0 obj << +/D [143 0 R /XYZ 56.6929 268.7111 null] +>> endobj +177 0 obj << +/D [143 0 R /XYZ 56.6929 210.4646 null] +>> endobj +178 0 obj << +/D [143 0 R /XYZ 56.6929 211.9241 null] +>> endobj +179 0 obj << +/D [143 0 R /XYZ 56.6929 123.7896 null] +>> endobj +180 0 obj << +/D [143 0 R /XYZ 56.6929 125.2491 null] +>> endobj +181 0 obj << +/D [143 0 R /XYZ 56.6929 114.2902 null] +>> endobj +182 0 obj << +/D [143 0 R /XYZ 56.6929 103.3313 null] +>> endobj +142 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F91 149 0 R /F57 116 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +185 0 obj << +/Length 3679 +/Filter /FlateDecode +>> +stream +x??]????????(P/pfD?E5???z???*?L????F??Iq????\Mp4f?????+????0i??[?dw?;???m??+?N??i?v1????_+[???q?j5T???E +u5?z??E??X???s?????s??m-?y???;?e?k??^?C??P?k?tzB??P?'q?k?#???f?v??????h? v??wn?'?]3???????P +??l??hQ??O????T?(?z???O???+??|?Uk+?+???????>)??"?u_???F?'Ka;NBB??= +"?)?? _!?/"rW?c1??dQ??????r[?::????<?|gS?!?9?F*?? 7???[? "I????}? +@??5b?&vd?H%??K?f!???:\????#9x?0??&\i"????????????Q?Y !????A?n4?O4n?,??Mw??(?FBk??C{????B?n'??@\g??A?g}P&2????\?gH?x?2??\E? (}??f??0N?(?? >?3?1;eX?T}?]?????}?^ ??;,?TW?_?j??*]m?-j??)F^8? ?90qp???u????F^4?xZ5 +??? S???c???V|W?y?i??/#?3?d5Mv??ST?j(???O?????qF???v??? ?nu?? ??|??-p???[=?T??>l?kN?5????5 ?k[4pU??b?M#@??F?k??+??$!?w??T?????v??aI????\??s?-{???9 v?Q_?Z?j>~wE$?q'H??0?-w?eb??%??9` =?M9?k7e???M9T??7DMga\?p?????p?v?90?G?hc!?v8??.??u??wV?N?3?:|T?????9??r???C:?b??{Xt??G?????4??????;??pD??uX#???nl?s???9??t???????.|fprK?psw?B?xk???{^??S??s?-|???9p??F?? ?uw???e??n???1r????????^9????$ ?u?????~;$I)s?-j?s?L???6????,?E?p,??b?? ?Q????g????[??m>c????9??n?@??p ?A??????2?p?z ???@??? e?o@?_?K?=P??`^b?B?T^?cn??[??kt????????4??sp?748?i2??)??aqs?g???b??????;CK????n??L???AiF??c?G??)m??y???v1?;?!8?L$???%80xp?P`?pD? ?` p??w?????G???;???qx???>x 0b1 ?#??B6s\???2U??)s???wFO?S?ni2e{;?\1?-x????d?}^7?? +k&??^???on?L?F? ???,?,?X???@wAy??x-?v???\P???????????????????%Aendstream +endobj +184 0 obj << +/Type /Page +/Contents 185 0 R +/Resources 183 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +>> endobj +186 0 obj << +/D [184 0 R /XYZ 56.6929 815.7613 null] +>> endobj +14 0 obj << +/D [184 0 R /XYZ 56.6929 584.6307 null] +>> endobj +187 0 obj << +/D [184 0 R /XYZ 56.6929 547.9207 null] +>> endobj +18 0 obj << +/D [184 0 R /XYZ 56.6929 547.9207 null] +>> endobj +188 0 obj << +/D [184 0 R /XYZ 56.6929 520.8533 null] +>> endobj +189 0 obj << +/D [184 0 R /XYZ 56.6929 457.9878 null] +>> endobj +190 0 obj << +/D [184 0 R /XYZ 56.6929 459.4473 null] +>> endobj +191 0 obj << +/D [184 0 R /XYZ 56.6929 448.4883 null] +>> endobj +192 0 obj << +/D [184 0 R /XYZ 56.6929 437.5294 null] +>> endobj +193 0 obj << +/D [184 0 R /XYZ 56.6929 426.5705 null] +>> endobj +194 0 obj << +/D [184 0 R /XYZ 56.6929 415.6116 null] +>> endobj +195 0 obj << +/D [184 0 R /XYZ 56.6929 404.6527 null] +>> endobj +196 0 obj << +/D [184 0 R /XYZ 56.6929 393.6938 null] +>> endobj +197 0 obj << +/D [184 0 R /XYZ 56.6929 382.7349 null] +>> endobj +198 0 obj << +/D [184 0 R /XYZ 56.6929 371.776 null] +>> endobj +199 0 obj << +/D [184 0 R /XYZ 56.6929 233.9081 null] +>> endobj +200 0 obj << +/D [184 0 R /XYZ 56.6929 233.3103 null] +>> endobj +201 0 obj << +/D [184 0 R /XYZ 56.6929 175.9241 null] +>> endobj +202 0 obj << +/D [184 0 R /XYZ 56.6929 177.3835 null] +>> endobj +203 0 obj << +/D [184 0 R /XYZ 56.6929 166.4246 null] +>> endobj +204 0 obj << +/D [184 0 R /XYZ 56.6929 155.4657 null] +>> endobj +205 0 obj << +/D [184 0 R /XYZ 56.6929 144.5068 null] +>> endobj +206 0 obj << +/D [184 0 R /XYZ 56.6929 133.5479 null] +>> endobj +207 0 obj << +/D [184 0 R /XYZ 56.6929 122.589 null] +>> endobj +208 0 obj << +/D [184 0 R /XYZ 56.6929 111.6301 null] +>> endobj +209 0 obj << +/D [184 0 R /XYZ 56.6929 100.6712 null] +>> endobj +210 0 obj << +/D [184 0 R /XYZ 56.6929 89.7123 null] +>> endobj +183 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F91 149 0 R /F52 107 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +213 0 obj << +/Length 5154 +/Filter /FlateDecode +>> +stream +x??]k?????>??a\ 3??V?DJJ? ??????N?s???n???=??~dc??BN????ex??kPP???.hR?e? B???fq???o? +???K???????{+8E?t??[???zh?W IY?{hEe??E????D???7??z??J???ta*???P??E?$C?O???KB)G??2k?????n?4?v{g?????? +\K??-m??)K-\?%,K??'L???8??'???-X|bS?[H??E?RQ?F?tr??????/???"T?? [8??#da8???`???w -???nA~eY?,)??N=)???????? %??p??s +???-RU`?ZH ???p????v?XF?leA???:??????(CBIBa1?Zn@?/?C?m6C?'?JY?????a?J.C???@ ??4??@?6??Q?t?????YJ???Q?{cT, Ae??w???e?I??e??!???Rr??PbQ?Y??h?E??Q?r?f:~??d????,2xo???????\X?"?`O5rR?]???P??x??k????n???}?????? ?"d!??)-?RDB?A ?G??NMZ?E??eP?%S+seVF?L??#S???2?> +????%4:??QC(jB9??QC?%t a at D?}?;62Zx\?*n???,????n?????F??j???t???? /?n???]QvY?????Q?=??5*??;?_?????e?:??C?P'E?s?ul?w?%R1`??'??n_??/?r]????????@y???f???????Y?????C&/mQ?G?E?+???j|%?xE????0???U?o???? ?fi5?? ?x??}?]??A\?r?V?QKF?????? mS/U?.w?c?n;p????I?Z7\???t?P[???z{w??Y?_?? rY?V]??o????W???}?`?????h????????Uo6OW?]? +(??Q} +>???m??U'?e?????Z5?eu??k??)???(/???9)?#?\4.*?V?????,???lJp6%???)?(? +HQn?^[???Y?????aX}????,el?uN?H?ra????E?3Z?x???W?\?|??/@ +?#?Pl at m?l67{ +?3"?a\B??2????????!#P?c??1x)G????w??-2mg1???~??9Nz?v?8?1????71??ID?X?J? +J???Q??1??r?? +?CE? +D?X???]?9T??@???!?|gSaII?????R)????$??^np???=)WE??????o??????ME??auo??C?yY{I???,;???Q?0??[oM????Z1*j[k@?O???*:??ba8??V?????1?{ey/ +?X?f1?W? _D?Q~??A?]? 2??jX#?l +???kGL????{E???J?2o +? ?25?Z?G??V!?????? ???O??????5FW??=A #???}?4???b?D.o???t86?" +? +??D@??#???kV?/??t=/?&-???J????\YAZH 0??f?;?gL?c??Z??n?g????$F? ?> ????(? ???!?!???(?r?l??????????6g??w=???????vG ???C +?Z??XK?????Zh%ku?m??*18I??????S?b?????w7??}????3 +^GZ? ??D9f????F????????, +??dr,??/(???d?????f???>?/9?bTtzh????N:?+?9T?j'Be??N:???T?5P??^?T??I???`m??J?P?????D???D???C???E?Ic2??< +H? DGw91??G?ao?????)????g?#?slgQ??`????VY??E)6J?@-m?L?? ?E>??Z>?@?1???NV?A??$?y??Z*?lis??,'II9?\p???[z??=???G???b??6_w?;?S??wJc ?z???,a??,\l-??E??A?H???????7?8?A)?d??6??,WO?<7?Gi.??[-(n.p?R?q?l??)??YIIx???")h?????????gd?v?????g?N?????2E?????Zc??'???;)?qG??m??7??R??< +??? ?k?C???SD + 2)D?rO????IEY??7?u?>?5???p?^sP?P?y?*?????C?A????X?????+???? +?[?TU???<;|??!?x0?%??A-???x?s??????P??2@???8?!b|70??v????!????'??mm?(??cb???&?@M7??g??$h?????y????I?%$?????A?"?????HA?2??Q?w?A.?? =?????[}?lT??b"#T???????k?o?????????]???2^?]??d5??!??@??.?T?{z??f??f??3Z?????Bn??@1?7????.????y????????W? +?I?2?zE???$?i7XS?? +?"?,`??z?=?`????L??S?T??S??uL&LQ? +8? ?P? ?0????????? +?_" 0?2`?{?A????X??ul#?+??&???V??z??????w???I?K?????Y?e?u????7?>?,(??MLq'?&??????n?D`.PB????8???3m?~?d??~?????M?~^:W:? ????(?,?'gNIA??.??p?b"6zf +b???S?0--T?>?-?l???}??hR??I) ???\?3W??:?F???Ix?????h? fV?(?e i????ss?=????[?????? +E?^C??? +?J? 9?????F?????? +?l?7?O??w??E?1?5Eq?+??Nk??? +???k??w?? *y?g?????????J???9 ??(??u?????$?0C3?S??M?3???c]}\0)????|?h ??G!??[?0u??[}?;? ?Lf?8]o'?yc??P??8?????{?A??^ +?????o???b???????3x????y??gl?K?????z???} J???g?#9???Vd-?k +?? E?#e"?#M??E???wjCk??X?3?f3?KV???B1?N??z??|?*?88?Y?NT?9[?????~?.V ???X??{?? *??_?9???????m?????h???p?endstream +endobj +212 0 obj << +/Type /Page +/Contents 213 0 R +/Resources 211 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 108 0 R +/Annots [ 219 0 R ] +>> endobj +219 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [55.6967 627.2638 187.3018 638.1678] +/Subtype /Link +/A << /S /GoTo /D (named_parameters) >> +>> endobj +214 0 obj << +/D [212 0 R /XYZ 56.6929 815.7613 null] +>> endobj +215 0 obj << +/D [212 0 R /XYZ 56.6929 760.0646 null] +>> endobj +216 0 obj << +/D [212 0 R /XYZ 56.6929 749.1057 null] +>> endobj +217 0 obj << +/D [212 0 R /XYZ 56.6929 738.1468 null] +>> endobj +218 0 obj << +/D [212 0 R /XYZ 56.6929 727.1879 null] +>> endobj +22 0 obj << +/D [212 0 R /XYZ 56.6929 614.4478 null] +>> endobj +220 0 obj << +/D [212 0 R /XYZ 56.6929 586.3528 null] +>> endobj +221 0 obj << +/D [212 0 R /XYZ 56.6929 547.4086 null] +>> endobj +222 0 obj << +/D [212 0 R /XYZ 56.6929 548.8681 null] +>> endobj +223 0 obj << +/D [212 0 R /XYZ 56.6929 537.9092 null] +>> endobj +224 0 obj << +/D [212 0 R /XYZ 56.6929 398.881 null] +>> endobj +225 0 obj << +/D [212 0 R /XYZ 56.6929 400.3405 null] +>> endobj +226 0 obj << +/D [212 0 R /XYZ 56.6929 307.6807 null] +>> endobj +227 0 obj << +/D [212 0 R /XYZ 56.6929 309.1402 null] +>> endobj +228 0 obj << +/D [212 0 R /XYZ 56.6929 298.1813 null] +>> endobj +229 0 obj << +/D [212 0 R /XYZ 56.6929 287.2224 null] +>> endobj +230 0 obj << +/D [212 0 R /XYZ 56.6929 276.2635 null] +>> endobj +231 0 obj << +/D [212 0 R /XYZ 56.6929 265.3046 null] +>> endobj +232 0 obj << +/D [212 0 R /XYZ 56.6929 219.8846 null] +>> endobj +233 0 obj << +/D [212 0 R /XYZ 56.6929 221.3441 null] +>> endobj +234 0 obj << +/D [212 0 R /XYZ 56.6929 210.3852 null] +>> endobj +235 0 obj << +/D [212 0 R /XYZ 56.6929 164.9652 null] +>> endobj +236 0 obj << +/D [212 0 R /XYZ 56.6929 166.4246 null] +>> endobj +237 0 obj << +/D [212 0 R /XYZ 56.6929 155.4657 null] +>> endobj +238 0 obj << +/D [212 0 R /XYZ 56.6929 144.5068 null] +>> endobj +239 0 obj << +/D [212 0 R /XYZ 56.6929 133.5479 null] +>> endobj +240 0 obj << +/D [212 0 R /XYZ 56.6929 122.589 null] +>> endobj +241 0 obj << +/D [212 0 R /XYZ 56.6929 111.6301 null] +>> endobj +242 0 obj << +/D [212 0 R /XYZ 56.6929 100.6712 null] +>> endobj +243 0 obj << +/D [212 0 R /XYZ 56.6929 89.7123 null] +>> endobj +211 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R /F57 116 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +247 0 obj << +/Length 3478 +/Filter /FlateDecode +>> +stream +x??]??????????E*m +?h?&H4?@>$A????nl???lE?????I??^\???~?f~? ?E??????f(?IqL?pmWqt?}~??Z?m???\}????????(#(c1?x?P??l?[}r?&4^?z??????uJW???w?????/? ?8p??%e ??h?1?)%?e|????????7?F?r?J????w??????U?????????9?W??$#?????????$Ei?????B?u?)?:"@-?????#?O5?8Z???G??? :?Gu?b?????6#??n?}2??>cy`^????4G8???^N????h??5?0??N?$A,Nq??p??E]/?.?!??x?e?_z??????8??#???9??C????n???es(???/?v?r??0??p?\?)JX?b???? ???r??f!???(?z!? +UH8?(??h??2?!?$1 ?5??^??? A????B???Q?tOa???a ?`~6?Oc? +???p? +G1?-?M??g?P:?t?????IRX?????GCP?fM?$`????D UP??????;???d? ?}d?? ????`)7???]a???? +???Q?l)${4?}???( ??&1H?F +O?x4~? ????@?4d?????8?C??!???Mq??????Q?<{???D?#????8????1?? +?#.J?' ????%8? +???G???@?)" r?%,??;e??M???????U??[???;E???t? +??a? ?nR??tcM??????,[6??z+_@?b??"M%??Oc????#??w?2?RJX?&?j?@?Q?_??Rh:? +???????TW?r{?K?f???v?K7?N?w?sHYy??D?C???t?j1?E?1C??pJ?????0?????{qo????z>2]?I?d?l~/'0s?8??[??hE7?=u??8O?G????5}P|GG??g?k???7j??dl???Wg?? ?4TB???????v.J?????i^??>???Nw?u????.~???{????L7? b {??y??,?B?e?],?????????X????O??h>?? +???M?Cs"?,G6???K???1??L??:^?x??P?y$??8&??Q???????a*Z8???e??h $?j"$|u?*???/;???"??U??]?{B)I???"$?v??N=|n????:?_+Y???i?Z1(???-?C???S??y??k?[?7B?t[???|?j?b?l +???n??xU????n? ?<???? ?avW?i????Q?E????tZ?M?}?N??o?j??X???\??F Y5p??~?h?????9???8???]??DC?SB??????m6?gx?C4t??Rf???????????hg?Lt?????v???\??M{?ux5K\???p?$???Rx,??e?}??6? U?k?jd???@"i?{j?Q???C?d???W8???????g?????k?????p +??p???$c"?b???uswp???R???5?P+?n??;???:????8??G?? ??v???{??n?+u??o?T?h,^??x{?a?)??&??{{ +I?k?&?v???)??e??? ?Q"???}Z?z?????3]??qY2?X???n?? +??????bK??g4=P?.kp??,U?R?\V?@????CSu????8???# +6?iKW??????=7d??@?;?*??? Wg?h?L?????+????????F???J?? +@????s??3?B1?t?:?5??????? { +?m@??????7?#??P?#??Pw?SD????E?+4?????R_?A???A?sWBW?]?m*?"l;???]o6Q?G?B?yp?aunOg?I?"F &?7??;???B???i/[|e2??L?W???P???h?n?hjE?P?2Q?mg???J?,_?%Q?(Q???4 ?4T???????O?4??@?? Qg}??( {????1?$4^??\?M????e???R?Mt'?g?/4?Nlh??h?7?J?r??y e?d?????bO?'%?T?M.???EK&??g?#F????H,??t?????Z?&?4?_?3?????t???? +??ui`????????\??_U???kh?2???????eM?;?/??u??W?????????e?3n??b????????_4n??z?x}e?%?Q?JK9}3?/ ???dt????0?$?x3\gq> endobj +248 0 obj << +/D [246 0 R /XYZ 56.6929 815.7613 null] +>> endobj +249 0 obj << +/D [246 0 R /XYZ 56.6929 760.0646 null] +>> endobj +250 0 obj << +/D [246 0 R /XYZ 56.6929 749.1057 null] +>> endobj +251 0 obj << +/D [246 0 R /XYZ 56.6929 738.1468 null] +>> endobj +252 0 obj << +/D [246 0 R /XYZ 56.6929 727.1879 null] +>> endobj +253 0 obj << +/D [246 0 R /XYZ 56.6929 716.229 null] +>> endobj +254 0 obj << +/D [246 0 R /XYZ 56.6929 705.2701 null] +>> endobj +255 0 obj << +/D [246 0 R /XYZ 56.6929 694.3112 null] +>> endobj +256 0 obj << +/D [246 0 R /XYZ 56.6929 650.5091 null] +>> endobj +257 0 obj << +/D [246 0 R /XYZ 56.6929 649.9113 null] +>> endobj +258 0 obj << +/D [246 0 R /XYZ 56.6929 638.9524 null] +>> endobj +259 0 obj << +/D [246 0 R /XYZ 56.6929 627.9935 null] +>> endobj +260 0 obj << +/D [246 0 R /XYZ 56.6929 617.0346 null] +>> endobj +26 0 obj << +/D [246 0 R /XYZ 56.6929 580.0902 null] +>> endobj +261 0 obj << +/D [246 0 R /XYZ 56.6929 552.6807 null] +>> endobj +262 0 obj << +/D [246 0 R /XYZ 56.6929 501.3419 null] +>> endobj +263 0 obj << +/D [246 0 R /XYZ 56.6929 502.8014 null] +>> endobj +30 0 obj << +/D [246 0 R /XYZ 56.6929 448.9002 null] +>> endobj +264 0 obj << +/D [246 0 R /XYZ 56.6929 420.6588 null] +>> endobj +265 0 obj << +/D [246 0 R /XYZ 56.6929 298.5969 null] +>> endobj +266 0 obj << +/D [246 0 R /XYZ 56.6929 300.0564 null] +>> endobj +267 0 obj << +/D [246 0 R /XYZ 56.6929 289.0975 null] +>> endobj +268 0 obj << +/D [246 0 R /XYZ 56.6929 278.1386 null] +>> endobj +269 0 obj << +/D [246 0 R /XYZ 56.6929 267.1797 null] +>> endobj +270 0 obj << +/D [246 0 R /XYZ 56.6929 221.3203 null] +>> endobj +271 0 obj << +/D [246 0 R /XYZ 56.6929 222.7797 null] +>> endobj +272 0 obj << +/D [246 0 R /XYZ 56.6929 164.9652 null] +>> endobj +273 0 obj << +/D [246 0 R /XYZ 56.6929 166.4246 null] +>> endobj +274 0 obj << +/D [246 0 R /XYZ 56.6929 155.4657 null] +>> endobj +275 0 obj << +/D [246 0 R /XYZ 56.6929 144.5068 null] +>> endobj +276 0 obj << +/D [246 0 R /XYZ 56.6929 133.5479 null] +>> endobj +277 0 obj << +/D [246 0 R /XYZ 56.6929 122.589 null] +>> endobj +278 0 obj << +/D [246 0 R /XYZ 56.6929 111.6301 null] +>> endobj +279 0 obj << +/D [246 0 R /XYZ 56.6929 100.6712 null] +>> endobj +280 0 obj << +/D [246 0 R /XYZ 56.6929 89.7123 null] +>> endobj +245 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +284 0 obj << +/Length 4406 +/Filter /FlateDecode +>> +stream +x??][o???~??(?? +t1?M???A`?? ?"? ?d[?????*??????(Q$?jOb????|o???#?U!??-AY?j?!??xu?=+V??????Y[??/???????? +T%*W?????t? p???????kD???/??Q_^^z?|?wm?????Ah?+.??Xj!? 4?ZC*J??BER??? ??????Q? Y??K?_????????g ??qSD*???Q(.q??????????[D)8?.?Bt?.>????????K2|j??P?????|??V]??w??????t?Mjwo??A?z?IQqgP?U????? 2DD\? +??2?D+???K????????}??TU?a?????Q?YU9j?:r???'T!??3r????1;e??l?^??M???????7?MPX??":6m?N?!??? +A??%L??9?;????r?r?????e%m(?N?-p???????&?_??J??]??B ??6e'7?????i???K??K??`L?p9(x????l#B1.?%?N&??eK?? +????Mc???N&?RfM??z^???(1??\?M??9:?d??%LLn??cF???Irri#,0??G,m??TT?????^?r?v?9x-7jOm???(???&b?????m????@ !K ????2?rtFIaD???M?#??h??B at A??????Q 0??H?%???????V[???qrj???????L?}??????!?$???B???hn?v?9x-7??????f??????t???Tw???9?>?y????w???1????=X????????/`q?t????y?cQ?Msk,$?7F???\l??M~hn???@??m?$??H?v????N??V& +?@?dKp[_????????u??T?s?2T???3N|a1????isd??r!D?,??TT???t?$"?????w?C??? (X?>???f?`? +?!XiX?5???` +g????]?>?????P??m??????? ?G? ??{?I%3n}?4???F??o??R~??x???? 8B????`?????7????R?S???c-????D??G????RG??P?e????6:vJ>??_????:?.???2?E??????4rV???>?`-3?U??k????M}???T??L/?7??K%??*??(R??F??????M?mvGAS??????0?1%:nI>?1???????? T????m????f?zQ?s ?*E&_7????O??pU\!?g ??????lw???7:FN>0SJ|7J??7???z?q*?Wuu}??A?????p +dC????O?P_*???t [ dKb?@? ?X?D??????2???????VG?Vq???Z?f??~v?_?f?o???|??O&??uq?????M?{x?dd??m??i?>??J7H??U?T!?*??(?Y~??[e????Q???r?????6"? 9??vS?8?{?Y]t??2?Dq?c???v??nbb5?$???K??|?s????^ +9?6Le"c^??G???T?d?Uxb?{nZ???{F? ??F?hv??9y?????:???dLa +??????l?|??!??m??????? ????E??0q?\???m???? +?w???n?w???6??q?j?0?csg?\????A*??????????j???Y????Kf4K???o??TL? +?????;??t~?t&???? s??;o.???S7>? ???d?G?????????y??1?v?????;?I:n?????? x?m?4?k??????i?&n&?f2FH????F?a?F???>b|?RAi??w????p?L???r?l?????X? ???%??U?H?????\????????L??F??/??9?endstream +endobj +283 0 obj << +/Type /Page +/Contents 284 0 R +/Resources 282 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +>> endobj +285 0 obj << +/D [283 0 R /XYZ 56.6929 815.7613 null] +>> endobj +286 0 obj << +/D [283 0 R /XYZ 56.6929 760.0646 null] +>> endobj +293 0 obj << +/D [283 0 R /XYZ 56.6929 738.1468 null] +>> endobj +294 0 obj << +/D [283 0 R /XYZ 56.6929 727.1879 null] +>> endobj +295 0 obj << +/D [283 0 R /XYZ 56.6929 716.229 null] +>> endobj +296 0 obj << +/D [283 0 R /XYZ 56.6929 705.2701 null] +>> endobj +297 0 obj << +/D [283 0 R /XYZ 56.6929 694.3112 null] +>> endobj +298 0 obj << +/D [283 0 R /XYZ 56.6929 683.3523 null] +>> endobj +299 0 obj << +/D [283 0 R /XYZ 56.6929 672.3934 null] +>> endobj +300 0 obj << +/D [283 0 R /XYZ 56.6929 661.4345 null] +>> endobj +301 0 obj << +/D [283 0 R /XYZ 56.6929 650.4756 null] +>> endobj +302 0 obj << +/D [283 0 R /XYZ 56.6929 639.5167 null] +>> endobj +34 0 obj << +/D [283 0 R /XYZ 56.6929 585.2655 null] +>> endobj +303 0 obj << +/D [283 0 R /XYZ 56.6929 556.8801 null] +>> endobj +304 0 obj << +/D [283 0 R /XYZ 56.6929 534.9973 null] +>> endobj +305 0 obj << +/D [283 0 R /XYZ 56.6929 536.4568 null] +>> endobj +306 0 obj << +/D [283 0 R /XYZ 56.6929 490.1654 null] +>> endobj +307 0 obj << +/D [283 0 R /XYZ 56.6929 491.6249 null] +>> endobj +308 0 obj << +/D [283 0 R /XYZ 56.6929 480.666 null] +>> endobj +309 0 obj << +/D [283 0 R /XYZ 56.6929 469.7071 null] +>> endobj +310 0 obj << +/D [283 0 R /XYZ 56.6929 458.7482 null] +>> endobj +311 0 obj << +/D [283 0 R /XYZ 56.6929 447.7893 null] +>> endobj +312 0 obj << +/D [283 0 R /XYZ 56.6929 436.8304 null] +>> endobj +313 0 obj << +/D [283 0 R /XYZ 56.6929 425.8715 null] +>> endobj +314 0 obj << +/D [283 0 R /XYZ 56.6929 414.9126 null] +>> endobj +315 0 obj << +/D [283 0 R /XYZ 56.6929 403.9536 null] +>> endobj +316 0 obj << +/D [283 0 R /XYZ 56.6929 392.9947 null] +>> endobj +317 0 obj << +/D [283 0 R /XYZ 56.6929 382.0358 null] +>> endobj +38 0 obj << +/D [283 0 R /XYZ 56.6929 303.8744 null] +>> endobj +318 0 obj << +/D [283 0 R /XYZ 56.6929 275.4889 null] +>> endobj +319 0 obj << +/D [283 0 R /XYZ 56.6929 241.6509 null] +>> endobj +320 0 obj << +/D [283 0 R /XYZ 56.6929 243.1104 null] +>> endobj +321 0 obj << +/D [283 0 R /XYZ 56.6929 107.1553 null] +>> endobj +322 0 obj << +/D [283 0 R /XYZ 56.6929 108.6148 null] +>> endobj +282 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F98 289 0 R /F101 292 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +325 0 obj << +/Length 4310 +/Filter /FlateDecode +>> +stream +x??]m????????'o?H???W$E^???CsWE:[?g??6???E??^R|%JC???KF?X+ +?y?!?3$?????OQ??|??DJ??z?????W???????????'_p??Q??t??f?R? +?(??X??|???zE9^????4???5??SS??bw?????????4QZ?-[?A9??????"[>??$Q??>?(Z?"'(?4S???????|}??3???`DYN?+N?e?R{gw????F??2?p??? +?&?O??4c?????rD0??????x?J?tiO????S?|y??? 91???t??P???}uR? [??????V??,W?????v?w?&?w?w?z?H?????????u_?R?jS??s?Ugo5 ???E?]???????P?E?!??>?n?V3???Si??H3??h???)?}??Ju?u?T???E?ou?oUEO?????.k?O ????????/?????&Ki????imG??3???S???~???????_|???????T????J??_?? +?i+?)??B???:h??H?*?????+?Z????o??o???!Z??????zS? +? +?c}k??I??R??H;?1?N ??E?q?0?z',?+G?~?TnIz?Q?d ??,?u?????y?'Q?(??h???j???K?1????riY<B??? +QrY???y?x?nW?Q??????????/?????vl?H?\(??M9?3%sF?pBj(?????-o?z??????;$]?Z?eyeH(A????z$?_%?eA?a?+'??r?????)d?? ???M????"?????k?F i?#9?#???xIp?b???a???q/{?????=4u?9??3??\f???????n:????M]?????W?|?|k???f?io???qd:?????????q??'??????)????2??+ +*"M?I?&?^t?R??"2D?s??????thY?p??RZ?X??????????N??R?V+')g????)o??u?}E ? OK-?Y@?3u[??QQ????RCD?`?=?:??p??????.????M?gI???I???z~:?????p?1?X1S)?_'7,?:? Y??k?=??^??????b?B?W?CA?4?7#:??+Oe???M??n?4a@?6??wZ??????j?$??nW?????A=?????B?t??p??Nb??W?Q?R???iSK??f??$*???/?3?t?f"??pFLd+??CQ?X(?? ???k +W??U?NW??U_3???L?Y??A??????H?C?'?~?A?j#?u?FZ?Y??]???\?????????????XW?C?????????????N?-SyE??Sc4?t?n=?????S?$??????!?n?Y??d??I.d??$?+\N???A7dm}???.?*'O??d?f3??_??S??m??8>O:???N?????????~?j{xr???Y&?m???0-???U???^m?l???I?d"?2?RnU.??%?%BL0 %0rBs!_?['B0E'?#???Q?i??RHq??b??#?,-??4?a??#?j?^??o??(???B +?4d??Q"m?( +%?I???$?XN,?Pqe#dB E?T??SzS6Je???4o?? M?c?,2?l?L?1?W?LD2?p?'m???\/`)C???????N?3????K ???Wvz?z?F???R????G'6?!$[?:??{???#"F???)N??????? ? +?\*[/!l +?F> +????n?7w????N?J?"?v^??[??@?????_B?w=?SEd????D?l?,+? k6D?V?{??^?? ???0vf???@?+n?c?Zn??d OI?p?<#Ty'A?)??'?SB?D\???`1??w?]j??l????la?.????ep.?|</??????:???????6?CR?HN????xH????bm???f?Hs?]??/i?b???q/???z?s??` +?np?l??s=L???0>??I???d???W?????!?t?q????F??p??F????e?_m$?e?!???%?$?e?V,?2?%#.??x?????,vP???!:u??7}F +t?P +?7?????E]?/??9?_???? ??/?C?,[*???;????F@??m?????U?*}??????A??????P?o??rW???@_c9???>Il?m?P????????S??9`??????n???6?l??w??4?f?d? +d45?93??\6?/K????e??cX?V??J????]??#2?w([???\??d???$FM??>5hS?Q$??P??L&Px?.?????? ??!?t????=K??JE??o???? 5??}j??H E? +\9?6I??j?6????J?????_?~?os???& ?N?.??D*???)???V<?????????I???l?wa?N?G? ?wM?Q??E@m???????K?*# ?\2b?{uvbM +??Y}? ????;????????r@@F9G?e?]?J?????F?N?G?&?????,??????Cm?W??R????GF ?|??o?/???<7?8o??"??????????????z?~`?!9+??s$????I? ?;??%8G??????????>?IY&? ??Qt????J)?M?*?Y?%??????&???l.1q9>vY??w??L?d?<2n?????n ?s?R????????[F??% ?\{d?????v?b?rRpw???>??Bt???{??G????????b?B?Q???!{T?1??E?3???d??=??#????3?t?L??n>??3??h?????????]?????j???-????? 0?_?6g/?ab??? ?l??????v7"???Z?????0?S?`????ect?q???S??G???RbL??O??AA2!??[??Fh:?r??P?J'?9???????3????g???? f.t???o7??n.????rB0??v???t:h???J ?P?x?f_M?q??{??1D???\??x&]?21???M?o???-u?,?!????&?&??r????H?.D????kn??????`?L?6d?.Bz8??m??????n????M????Bmn??????u`?@/????iA?z;?p?m????f^??Y'of???G?>X???????????O1$?|??S}?3+??H1?UX'??\N?i>? +????i ?y?????>:p*????????C?`+tG?a?P??QYw?`f??O?? ??Y?{ +??{.?h3?<6+? ?0??K???g?ic?f;?????Cmm?"q?C??``???j?????????W??D ??u0`?;??L/? (c?r???;??? +?v0?}?????E???>???<?s ? +???Cmq3?????0???`??wF??^q0?[?)?@?@(r?p???M??w?????}?i?h????Eendstream +endobj +324 0 obj << +/Type /Page +/Contents 325 0 R +/Resources 323 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +>> endobj +326 0 obj << +/D [324 0 R /XYZ 56.6929 815.7613 null] +>> endobj +327 0 obj << +/D [324 0 R /XYZ 56.6929 687.1731 null] +>> endobj +328 0 obj << +/D [324 0 R /XYZ 56.6929 688.6325 null] +>> endobj +42 0 obj << +/D [324 0 R /XYZ 56.6929 616.4486 null] +>> endobj +329 0 obj << +/D [324 0 R /XYZ 56.6929 590.6535 null] +>> endobj +330 0 obj << +/D [324 0 R /XYZ 56.6929 484.4867 null] +>> endobj +331 0 obj << +/D [324 0 R /XYZ 56.6929 485.9462 null] +>> endobj +332 0 obj << +/D [324 0 R /XYZ 56.6929 474.9873 null] +>> endobj +333 0 obj << +/D [324 0 R /XYZ 56.6929 464.0284 null] +>> endobj +334 0 obj << +/D [324 0 R /XYZ 56.6929 453.0695 null] +>> endobj +335 0 obj << +/D [324 0 R /XYZ 56.6929 442.1106 null] +>> endobj +336 0 obj << +/D [324 0 R /XYZ 56.6929 431.1517 null] +>> endobj +337 0 obj << +/D [324 0 R /XYZ 56.6929 420.1928 null] +>> endobj +46 0 obj << +/D [324 0 R /XYZ 56.6929 383.0424 null] +>> endobj +338 0 obj << +/D [324 0 R /XYZ 56.6929 358.0792 null] +>> endobj +339 0 obj << +/D [324 0 R /XYZ 56.6929 323.6435 null] +>> endobj +340 0 obj << +/D [324 0 R /XYZ 56.6929 325.103 null] +>> endobj +341 0 obj << +/D [324 0 R /XYZ 56.6929 314.1441 null] +>> endobj +342 0 obj << +/D [324 0 R /XYZ 56.6929 303.1852 null] +>> endobj +343 0 obj << +/D [324 0 R /XYZ 56.6929 292.2263 null] +>> endobj +344 0 obj << +/D [324 0 R /XYZ 56.6929 281.2674 null] +>> endobj +345 0 obj << +/D [324 0 R /XYZ 56.6929 270.3085 null] +>> endobj +346 0 obj << +/D [324 0 R /XYZ 56.6929 259.3496 null] +>> endobj +347 0 obj << +/D [324 0 R /XYZ 56.6929 248.3906 null] +>> endobj +348 0 obj << +/D [324 0 R /XYZ 56.6929 237.4317 null] +>> endobj +349 0 obj << +/D [324 0 R /XYZ 56.6929 226.4728 null] +>> endobj +350 0 obj << +/D [324 0 R /XYZ 56.6929 215.5139 null] +>> endobj +351 0 obj << +/D [324 0 R /XYZ 56.6929 204.555 null] +>> endobj +352 0 obj << +/D [324 0 R /XYZ 56.6929 193.5961 null] +>> endobj +353 0 obj << +/D [324 0 R /XYZ 56.6929 182.6372 null] +>> endobj +354 0 obj << +/D [324 0 R /XYZ 56.6929 171.6783 null] +>> endobj +355 0 obj << +/D [324 0 R /XYZ 56.6929 160.7194 null] +>> endobj +356 0 obj << +/D [324 0 R /XYZ 56.6929 149.7605 null] +>> endobj +357 0 obj << +/D [324 0 R /XYZ 56.6929 138.8016 null] +>> endobj +323 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +360 0 obj << +/Length 4405 +/Filter /FlateDecode +>> +stream +x??][???~?_a?K=E????K?I?6m +?;@6??k?3Fl????n???^E?"???t?T6#KG??/??h??hF?$?p5+M???j?????77H?,????????????J?????,?I^?tV?EB*\?????_?.0M?/?????????rn??rw???[??f%h? ?????BIE)?Z +x?(???????n?r?)*?E?Bq??t??u:[?9???IV?h???g??o(?K?cugw????N?z??$KK:?0Jh?J?p?Y???]??h(h??O????$)????1???L)???b??[????^?nQ:?.2 +nL +^[@? ?"????v{?~>??-??????$?,??Us8??N?8????|i?O?? +G~???????vy??????????????l$?[????mN? 3?g? +?_N?? Eh9??lO??f??.???DJ:?????n'???~M>;??-f?6???%_????Us9???{C?I??W?R?[???OS???w??r?$??Cs9?K???5 K????????|q?=?u??N?F:R??>%? Z???95?vU ?U??w????L]??n???L??LON,??0LO[??Gn,? t??v??9d?:9?=3??j~n`w?1??????lG??e?`?l~?!??50)22?js????]s"2????#?=??HB????G?J?QY??A??8p????Tv~X???V???T??%8_$ DS?0? +^/ ???? +bree$??/??nm??v??j?O?????Ig??L\?s(4?3?x?"? +??(3#-????c??E yg3S]?MHQUQj%Ih?I???lj??tZ?????a?2? +2\(?6?J??^???o?$(II?M???gw????????t??f? 5??Mj????')B8Hp??"???~??-??q???Sv??.???R;???p?MT??"??)!J??PR?D|???_&r(b.g??@m??#?B??? +?@E??U?B4) ??j9?????Q?)?Aj -u?I? 9?/FUf ???g?crrx??L(b???!W(A#2$????q???+?(>??1d????J???`<.?I-g??8?r?%-I?/Z* +???s%?????????0S?_S-?t?,'i????????p??PM?_??avZ????????Q?-}?????,\*??]GE?????^?F?P??G???>"?9?>????3!?lf_??????+ fJ?1\h???,?`hd???b?}??QG??*???z??"??6_, M?k???1p?2???M?9d??c?+????%?n?&$/???+???+Ffv MxQ4b???? ????????j*"?^????J??%N???.-??1:??W?aIqQ^GE?????8?????$?b V?]?1???h_?w> [??)~?"??|??Q?e4?? +?????????k???? ?n??$?eF? +? ??4%A? -Cw?1?W??????Ql |?(v?????hl?o?K???M5??`bh? W?`5????Kct5?FW?D??"?*l??? ???Ng??zy>??Z>?.???0?S$e??9?#?+?????G???G???????)?????%?? +eUo(z?B?9_??V?? +?r?r?09???&?? )MBe?????reJ???+mj??w)???\?A???z?7o?W?-$?A? -CW?o?wa?h9???]O^M????)?f??H2?Y?7\1?b[?i???m????????0???Y?K?B???S1??6??w?? +:b?v^-???????>???? ???? p?G?2??:EO??3+????=J??E?4)1>?'?V??n5f?t????!;????(?????7\?G??\a???N?????gTGC??[?(??+4??_C92|*GJ??.?n|?'?-????#??6O1R?? +?v%9L??=<=?K???Q*?TG??RmRa? +??&bkh?#??~???(????=????? ??68?9*="z +=?!?` ???By??6????p-?e????~ +?d??P)?x?n????i????po?? +"?u +??j?B #=7??k? u?w-_?y?x=?H??!???|??%?G???|?~8???????????8??Z????r?"?????"??? +?P W?P???E?????vk??? ??????6??)?b?g??Kr?!V?l??V????bJ??L7???????k ????0??-? I?!??????>J0????ZK?K?4??,?ow??6FS?~v??d ?K?f?3?? ??V?"??*??[????@Mm??@#?}U|s??????\???ms?;}????o?z??Z^]Nr?=d!d?E???2????!h +???r????G???T???????H?'$??iS?i??F???#?r&:??D??R]??v???????#?0????????????0????6?a?+=????#???????[.?g?M{?|?N???@?VR???????Z*ay??[J*???-? ?t??Q???????>+?IU?t??U[}xea?0?S??q?\?X?u?A?!?G?cE?8?M?????k???#?a?R???=U4&??)TW$?~7F??vR;J?u??DT?;????$???i??? ?$DSJj??[ ?]?H?k{???V?]?N?o????????RT-C?@?q 4f?????~c?"?????8??n ? "wq? ?c,?1qL??;.? ???1al????8??~da???cL???8?8???|X???1&?%;|??4?g?W$i??T???1??o?????9???d04,???#??q? +????!?????n?}_??sh?N??}???rM?s Q?????4??H???V!???3?? ?????.+:?????q?D?1 at L????????9???=???[[?W?#y???+?/?[/8t6??ay?????H Cj????? A?v?|???????!??R??cm??rw???)Ub?r???>???]?{?k???????????????5?qBQ?#Y?? +?vh11?Qyf;??j?#?W?O0????3;??3?=?C????3 "??[????qC????L&??b?$?Qe??xKq????'.X ???^F??b????3???U????i?6????l?g??c?p???f??V?l ??27???+[?9??tIe??aZ+N???)?:N????????R????B??,??;= ???n?c[??he???7???J/??B????G????????AP'?}????a0???~{X?????C}?aI~?E???l?????f?k???$?/???1?A?*4??M?c?>?D???V?p$??b????>??05u??E??? +Zb?-? c;??_!?@M?Ox??&???$??{???bH x U??? ?b??> endobj +361 0 obj << +/D [359 0 R /XYZ 56.6929 815.7613 null] +>> endobj +50 0 obj << +/D [359 0 R /XYZ 56.6929 759.0684 null] +>> endobj +362 0 obj << +/D [359 0 R /XYZ 56.6929 738.4887 null] +>> endobj +363 0 obj << +/D [359 0 R /XYZ 56.6929 651.4927 null] +>> endobj +364 0 obj << +/D [359 0 R /XYZ 56.6929 652.9522 null] +>> endobj +365 0 obj << +/D [359 0 R /XYZ 56.6929 641.9933 null] +>> endobj +366 0 obj << +/D [359 0 R /XYZ 56.6929 631.0344 null] +>> endobj +367 0 obj << +/D [359 0 R /XYZ 56.6929 620.0755 null] +>> endobj +368 0 obj << +/D [359 0 R /XYZ 56.6929 609.1166 null] +>> endobj +369 0 obj << +/D [359 0 R /XYZ 56.6929 598.1577 null] +>> endobj +370 0 obj << +/D [359 0 R /XYZ 56.6929 587.1988 null] +>> endobj +371 0 obj << +/D [359 0 R /XYZ 56.6929 576.2399 null] +>> endobj +372 0 obj << +/D [359 0 R /XYZ 56.6929 565.281 null] +>> endobj +373 0 obj << +/D [359 0 R /XYZ 56.6929 554.3221 null] +>> endobj +374 0 obj << +/D [359 0 R /XYZ 56.6929 543.3632 null] +>> endobj +375 0 obj << +/D [359 0 R /XYZ 56.6929 532.4043 null] +>> endobj +376 0 obj << +/D [359 0 R /XYZ 56.6929 521.4454 null] +>> endobj +377 0 obj << +/D [359 0 R /XYZ 56.6929 510.4865 null] +>> endobj +378 0 obj << +/D [359 0 R /XYZ 56.6929 499.5276 null] +>> endobj +379 0 obj << +/D [359 0 R /XYZ 56.6929 488.5687 null] +>> endobj +380 0 obj << +/D [359 0 R /XYZ 56.6929 477.6098 null] +>> endobj +381 0 obj << +/D [359 0 R /XYZ 56.6929 466.6508 null] +>> endobj +382 0 obj << +/D [359 0 R /XYZ 56.6929 455.6919 null] +>> endobj +383 0 obj << +/D [359 0 R /XYZ 56.6929 444.733 null] +>> endobj +384 0 obj << +/D [359 0 R /XYZ 56.6929 433.7741 null] +>> endobj +54 0 obj << +/D [359 0 R /XYZ 56.6929 396.929 null] +>> endobj +385 0 obj << +/D [359 0 R /XYZ 56.6929 369.589 null] +>> endobj +386 0 obj << +/D [359 0 R /XYZ 56.6929 348.133 null] +>> endobj +387 0 obj << +/D [359 0 R /XYZ 56.6929 349.5925 null] +>> endobj +388 0 obj << +/D [359 0 R /XYZ 56.6929 338.6336 null] +>> endobj +389 0 obj << +/D [359 0 R /XYZ 56.6929 327.6747 null] +>> endobj +390 0 obj << +/D [359 0 R /XYZ 56.6929 316.7158 null] +>> endobj +391 0 obj << +/D [359 0 R /XYZ 56.6929 305.7569 null] +>> endobj +58 0 obj << +/D [359 0 R /XYZ 56.6929 240.0692 null] +>> endobj +392 0 obj << +/D [359 0 R /XYZ 56.6929 211.8972 null] +>> endobj +393 0 obj << +/D [359 0 R /XYZ 56.6929 143.0474 null] +>> endobj +394 0 obj << +/D [359 0 R /XYZ 56.6929 144.5068 null] +>> endobj +395 0 obj << +/D [359 0 R /XYZ 56.6929 133.5479 null] +>> endobj +396 0 obj << +/D [359 0 R /XYZ 56.6929 122.589 null] +>> endobj +397 0 obj << +/D [359 0 R /XYZ 56.6929 111.6301 null] +>> endobj +398 0 obj << +/D [359 0 R /XYZ 56.6929 100.6712 null] +>> endobj +399 0 obj << +/D [359 0 R /XYZ 56.6929 89.7123 null] +>> endobj +358 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F92 158 0 R /F91 149 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +403 0 obj << +/Length 5072 +/Filter /FlateDecode +>> +stream +x??]m??6r?>?BI?*Rba? A????J??N?*w?u???Jq4???v?4?u*?=?B? ?????'o?????< ???? ?d? +TT??q?PY?l????????7D?,????????W?gxV??????????(1?q\???????w??.????????I]?Y?l~>?M?]?}???Bf\h)2?%/K??gKBP???pqk??????}7???R4 ????Q. ?????xv'??? +Fy???Y???+2??0".???o?7?o??k4??????C2D)?- ??X? ?RN~????k??R(?e???E?|F??f?zvo??o? +????hT????????????????X -? +?J?B+??V.??m&FJ???x6??"? XW[??%0K?(quI??1?CP?!V?l-?O?+???_??????l?C$??, Xt??????Br???Z?r?S????d???b?R??6]/$?-rD+??V??O1Pr?H???u?&E#B%???J%?Cm?fI G?W????O2????L*-?K?L?????d??r?M???????#?j?-sY`???7A,?w?fAl??B4????(J?2???v???>{O&"?\p?l??Yh1\?O??Oq^?B??+????????A^K+??$D?o???.?L???d??o????:???T?(g?NU??OZ?J?Fl*????u<?H!???-@??x>bz?/????C?i?vBE????s4???O???O?H??$ |4N5?eS?o??R ?z?'K??D?[?h?m??.~?0?\f#????? .ZI?X?$?&>?[8??*$b???'^?O???????g;U???T?@??? ????R?j?????????1? +????=H!?<:r3?H?S4??)???????)z???%???K:???:U1?_? +?f?&v?2?{?????To???YE???/S??@???N?????b???*??k???6 ?E|????E?~?%??????n3???B \z?????E?j????`Ws ?j?????t???BI???????tN-?MM?zGC?? ?????@??t?/8??1V^sE?l"??Fj4??????2???[ ?6? TP?>?QM????????B;?H ??;b????h??Pob$ +???????Htb???( ?G?`??H4hF?.?6?j??7_????????y?#M????vj`?????C??m?i0?????0??8???????????Bk$??#??_??vnZ?yz\???T????N?u?o~TW?$??EDhVj??=U?s?.??q?Y???a??X?4?R?r2??????yw????????i??6???a?/???n??(??xn6???c????t0???f?c?v?l7?,?xF???2?????%??????v?a?O??b?u????g?B??YE?P?J????Xf????>m?2b/??cs??~N?4?J&B??A?:!??m??{dS+?R?G??2?.-??? K ?q"??J?j??x???j????g???y????E?g}???,?????b????C;????n?kj`???cwv?E??C? $,`??lF*?sg??]u???Y??A?j????01~???k0?P???G?P????L??????WqO +U???A??????x??2?*?|????>??U??????? T??7???(N??O-??O?+???_E???2??Y8?@?s???n?I?z????.???J??i?a??_G?N?^O?$H?I??4\??KKp?E=???W?zM1???`???8+?????????? /;$wy?EV6"?9? +j?tI??? ??p?=???C??BU??\X?tx?_?]???p\.??_!1?"p??>\\?u??Q?7?y?t8+EG??F?e???kd???S^???? 3k?]fut\x9/kVAZ????n?f?%?P??k?? ?a,?EY"??J?}??uqy?>????.g??a????.??hx-s???:???t-'Y)Y?,????.C#?? +??BE?gp?A^09???7??To??????? l?$????Y????J|{???????p=??3ZyS???C?s? +j~x? ?S?N] +1???????????9? +???????????-$H?7?.?????F?%??:?N???P??IK??6? ??V?Acyy?q?%L??K?\?^B??1?0???.?6???%???I??b:5??Fh??t??b? R?-?K2a1z????m ???N??0???.|?b?G??-&H???.A?b^?j? ???%???P?q,& l-? l?L?bX??u???b:5???R?z???? X?f/\??1?[{?O?6?!b??h8?6n*?Z? +l?3k| x?0??M??????????9?fY???A?W?y?Z???y?}?IP?86 ??r??z??-????????+Y?????0??%???3?\]?f??????k?????1?3x?"?M??@??A ???D?l????????C~????=?????9? ???#T?~EyK6????-??\?%?lS?6?%????D8??/v ?,???a?V.?2xiUF?"?dwNp???- ?9n.?}?!B#?E??FE???;??a]??8???b???bY??gd?* ???B)?@??9mvr/@?????1?i?????E??U?7???w?,?? +{;/?XWz?_9?EA?P +4P&A??i??v?n???M??yA??????? +???g?}??O?????????1h@% ?4C??????6? +???,?????H3G9n?q??C?nn??s???z???]????????+??"?$O??4??Q-F4????Jx?]??\??I??\?VN?????K0/#????@????`T?S??.???>???"ap{????nt??j??z'??\o??8;???I?e?????1??S??&?'????p?&??D???7A?D???M?????`???0p?m?R???'VJ???Po?>?8.7&.??i????"U)?tO?sl?@?????q?????k?Z??&?Y?)c?uss?>b?tV;?*??n?L#?e?'%`?P??[0?N,vHb??????E{??v?>kM???.?O-?]?O??E{??X??*T??M_?Jp3?P???h?"?u?????B?&0?N?|????&?f?????(??????f>???pZ??? +?? ??e?h??0?g??,?????v?/(???{;????~?Y?'=??n?? +???~+?4???a/???pn?&??}?>???W?? ?????Z???e??=?v?y-???_uG????aU?t?Bu?aG?????Rq???B?????????g??j????N]????Xf&5?????x>uo???????Q}%L?????pN??I?e??????????A??j}?????oR4:????1vL?????]?B?j????xYV?{"?q5???????????F? ??s??O*???????o?7?o?z?e??????R$lendstream +endobj +402 0 obj << +/Type /Page +/Contents 403 0 R +/Resources 401 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +/Annots [ 444 0 R ] +>> endobj +444 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [168.8613 156.374 268.5368 167.2779] +/Subtype/Link/A<> +>> endobj +404 0 obj << +/D [402 0 R /XYZ 56.6929 815.7613 null] +>> endobj +405 0 obj << +/D [402 0 R /XYZ 56.6929 760.0646 null] +>> endobj +406 0 obj << +/D [402 0 R /XYZ 56.6929 749.1057 null] +>> endobj +407 0 obj << +/D [402 0 R /XYZ 56.6929 738.1468 null] +>> endobj +408 0 obj << +/D [402 0 R /XYZ 56.6929 727.1879 null] +>> endobj +409 0 obj << +/D [402 0 R /XYZ 56.6929 716.229 null] +>> endobj +410 0 obj << +/D [402 0 R /XYZ 56.6929 705.2701 null] +>> endobj +411 0 obj << +/D [402 0 R /XYZ 56.6929 694.3112 null] +>> endobj +412 0 obj << +/D [402 0 R /XYZ 56.6929 683.3523 null] +>> endobj +413 0 obj << +/D [402 0 R /XYZ 56.6929 672.3934 null] +>> endobj +414 0 obj << +/D [402 0 R /XYZ 56.6929 661.4345 null] +>> endobj +415 0 obj << +/D [402 0 R /XYZ 56.6929 650.4756 null] +>> endobj +416 0 obj << +/D [402 0 R /XYZ 56.6929 639.5167 null] +>> endobj +417 0 obj << +/D [402 0 R /XYZ 56.6929 577.5386 null] +>> endobj +418 0 obj << +/D [402 0 R /XYZ 56.6929 578.9981 null] +>> endobj +419 0 obj << +/D [402 0 R /XYZ 56.6929 568.0392 null] +>> endobj +420 0 obj << +/D [402 0 R /XYZ 56.6929 557.0803 null] +>> endobj +421 0 obj << +/D [402 0 R /XYZ 56.6929 546.1214 null] +>> endobj +422 0 obj << +/D [402 0 R /XYZ 56.6929 535.1625 null] +>> endobj +423 0 obj << +/D [402 0 R /XYZ 56.6929 524.2036 null] +>> endobj +424 0 obj << +/D [402 0 R /XYZ 56.6929 513.2447 null] +>> endobj +425 0 obj << +/D [402 0 R /XYZ 56.6929 502.2858 null] +>> endobj +426 0 obj << +/D [402 0 R /XYZ 56.6929 457.679 null] +>> endobj +427 0 obj << +/D [402 0 R /XYZ 56.6929 459.1385 null] +>> endobj +428 0 obj << +/D [402 0 R /XYZ 56.6929 448.1796 null] +>> endobj +429 0 obj << +/D [402 0 R /XYZ 56.6929 437.2207 null] +>> endobj +430 0 obj << +/D [402 0 R /XYZ 56.6929 426.2617 null] +>> endobj +431 0 obj << +/D [402 0 R /XYZ 56.6929 415.3028 null] +>> endobj +432 0 obj << +/D [402 0 R /XYZ 56.6929 404.3439 null] +>> endobj +433 0 obj << +/D [402 0 R /XYZ 56.6929 393.385 null] +>> endobj +434 0 obj << +/D [402 0 R /XYZ 56.6929 382.4261 null] +>> endobj +435 0 obj << +/D [402 0 R /XYZ 56.6929 371.4672 null] +>> endobj +436 0 obj << +/D [402 0 R /XYZ 56.6929 360.5083 null] +>> endobj +437 0 obj << +/D [402 0 R /XYZ 56.6929 349.5494 null] +>> endobj +438 0 obj << +/D [402 0 R /XYZ 56.6929 338.5905 null] +>> endobj +62 0 obj << +/D [402 0 R /XYZ 56.6929 301.1713 null] +>> endobj +439 0 obj << +/D [402 0 R /XYZ 56.6929 265.568 null] +>> endobj +66 0 obj << +/D [402 0 R /XYZ 56.6929 265.568 null] +>> endobj +440 0 obj << +/D [402 0 R /XYZ 56.6929 238.7753 null] +>> endobj +441 0 obj << +/D [402 0 R /XYZ 56.6929 218.0156 null] +>> endobj +442 0 obj << +/D [402 0 R /XYZ 56.6929 219.475 null] +>> endobj +443 0 obj << +/D [402 0 R /XYZ 56.6929 208.5161 null] +>> endobj +70 0 obj << +/D [402 0 R /XYZ 56.6929 143.6746 null] +>> endobj +445 0 obj << +/D [402 0 R /XYZ 56.6929 115.8506 null] +>> endobj +401 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +448 0 obj << +/Length 3528 +/Filter /FlateDecode +>> +stream +x???????}?Bo??V??J%?8vj?8U??s??rQ$5b?"e3??O7?^:f?<h4?F_hP?\?+?p?X??H?N?J?????? gk??c??<=<~?????????@:A???? +?p?????r??????Z?;j>m<?wuS$????o??XE@%PH? CX-Zm?pb???J S?h?H?B?????,???0??e? ????O?*??|??:^??+t\Gz?X|MH)>}?Mx????y?????}???o??95??0/?k?l???X~3tb?????t?@Z???nSG? ??J???4??f???8?u>KB?6???O?????=?Q\?k???????U?g?????_?#G?6?t]Y????? ??{##?v?I-?4???\8?}]?52??- at I?u???DK?M??|??????;?0???C???nQeh?:??x} ?4F???+????? UG"?xdS?h?9O?n0?E??F?M??!]? +1~AdI?A]/?z?????q)G?????Hf????v???K2????X#&?4??????? R???3?O???\FF?????`?"???.?"??????^??VYk??2??T???$????^x;?c? r???'???!?????#??????A???????M????3?#hi?,c)9?Kh?????Q2?m{??'?#EL??E??%???]%? T??!{6hu?G$????#????????rH? ?!&:?FbZX?*0g?B?ig???GBn. 3O~:l %?^>??A?y??6?c9??"G?R??X:2?[???,?v??????m??!?`yC)&?z?Ry????hT?1?o??,??4???T??-v??H???????????4H.???g???kp? V^a821?~?&??k?$4???h2e?????L?"x????N{??p?????>??&?8??e?|????Qu5?@?M +L^ ?????????@Y?MR??K?5A???????5=?u?8y?7G??P(?b?3EI??!??0????J????0> +O|??vk?02 +? ??e6?xL:]?PO ?S?A?w]?T??*????cQ?B?~????Kv??=*D?rAA?M?s%? ) ?l(??y??tm??("??Nj????n??-??P?hdc?i??p{v?????"K?? ?@??6??u???????[??P??????Lz? \?2IS???"?n??$???_??'?obm?|?3?????????no??N? +??y_????{???wsw????_?k??@???_n? +?endstream +endobj +447 0 obj << +/Type /Page +/Contents 448 0 R +/Resources 446 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 281 0 R +/Annots [ 451 0 R 452 0 R 453 0 R 454 0 R 455 0 R 456 0 R 457 0 R 458 0 R 459 0 R 460 0 R 461 0 R 462 0 R ] +>> endobj +400 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (/autonfs/home/davidk/dblatex-0.3/latex/graphics/warning.pdf) +/PTEX.PageNumber 1 +/PTEX.InfoDict 464 0 R +/Matrix [1.00000000 0.00000000 0.00000000 1.00000000 0.00000000 0.00000000] +/BBox [0.00000000 0.00000000 160.00000000 183.00000000] +/Resources << +/ProcSet [ /PDF ] +/ExtGState << +/R7 465 0 R +>>>> +/Length 466 0 R +/Filter /FlateDecode +>> +stream +x??R;N1 ?} +????? ?f?,?l?Rp}?L2?@??_^??m9o??}??o?xV??C??0??|?? ?rf "??p????W??~???+}??????r??"??M??3?\??!?4K)?~????Vvfm???5~??[G#?6??y GI?7??????????)endstream +endobj +464 0 obj +<< +/Producer (GPL Ghostscript SVN PRE-RELEASE 8.61) +/CreationDate (D:20100125210321Z) +/ModDate (D:20100125210321Z) +>> +endobj +465 0 obj +<< +/Type /ExtGState +/OPM 1 +>> +endobj +466 0 obj +252 +endobj +451 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [450.0885 501.0735 567.9254 511.9774] +/Subtype/Link/A<> +>> endobj +452 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 489.1183 289.1986 500.0223] +/Subtype/Link/A<> +>> endobj +453 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 423.3649 88.6727 433.9998] +/Subtype/Link/A<> +>> endobj +454 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 363.5891 124.9163 374.493] +/Subtype/Link/A<> +>> endobj +455 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [112.4627 333.7011 171.1622 344.6051] +/Subtype/Link/A<> +>> endobj +456 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [174.151 333.7011 228.9948 344.6051] +/Subtype/Link/A<> +>> endobj +457 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [231.9836 333.7011 315.7191 344.6051] +/Subtype/Link/A<> +>> endobj +458 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [318.7078 333.7011 384.3116 344.6051] +/Subtype/Link/A<> +>> endobj +459 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [404.177 333.7011 483.1001 344.6051] +/Subtype/Link/A<> +>> endobj +460 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [55.6967 315.7684 137.9272 326.6723] +/Subtype/Link/A<> +>> endobj +461 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [112.4627 291.858 175.8841 302.762] +/Subtype/Link/A<> +>> endobj +462 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [178.8729 291.858 241.1885 302.762] +/Subtype/Link/A<> +>> endobj +449 0 obj << +/D [447 0 R /XYZ 56.6929 815.7613 null] +>> endobj +74 0 obj << +/D [447 0 R /XYZ 56.6929 564.6668 null] +>> endobj +450 0 obj << +/D [447 0 R /XYZ 56.6929 535.9077 null] +>> endobj +78 0 obj << +/D [447 0 R /XYZ 56.6929 201.2083 null] +>> endobj +463 0 obj << +/D [447 0 R /XYZ 56.6929 172.8229 null] +>> endobj +446 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F52 107 0 R /F92 158 0 R >> +/XObject << /Im1 400 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +469 0 obj << +/Length 4851 +/Filter /FlateDecode +>> +stream +x??]mo?F???_!?????????7 w???`s?=8????h??$:?4?qw?????????g?????d?????U?/d????H3??Q?(XJ???????.???_.??Y)??-???o??tQ?2?????"?H??tQ???e?/?7?-??\E)]^=6?Gqx}???????j{???7??- +???\K?G$gQ?X1F?4?z5???y?|+~X??????&?8?%#q +???.???.6`?7?$e???%QR???"epg?:?????????F Ih?z?&#?Be??%%a4e?_?]??T??i??7?\u??G?V?????=?????v?da??KI??e?Z????5!???n???q????P???%??GN?aq???b?Z???u?????=???J? ~?"QK??*????O???@q?? +?u??9)Ki9?f%D???0??z:xp???@y? +?9#4??????_?j?kJj?_????~ +%???M?k7????cm???N?k8?Ho???Vk???u??D??_ ??r?k?[??6b\??Q??&e?????cm?o?(a,Ig?????? ??)? ??????6???m69??!?l?????|?:????#?A??Z?}?:??mm6?-?>????????$??@?k??X????4?G??.???|??d?YJjB???8|??t??????8z??e,G???TU?.,??,??IM? +??r? ?5?O???GKcZ,WR!??????p ??-W?A?^n`???8l?)?)?V+??H?y????D?????????s???? +B?2`?? + at K?$`y?$/1?r-?r????????j?(c?EE?\I??G??|!?!???^=?Y5?D3%5!??U??h?????&?F3???PT?lX$?9?S?Y^E3>?P?M4??G??l??&??U4???h?Zm?;??f?6? ????0??h?B?h?Zn??4??h???hf? +????< +?? +1r????x_-??h_ at P?j jJjBP????A +%???M +j5;???&???HPs@??? +j6|0??????C????D?MP ???f??A +??5v?-?&Zm???;)?a?[A +?6A +???i?[A +??A??_?G ???????B?Bn??????W?p?~ ????1!3!??J}iCh?fh???K?^? ] \??????e??! ??, t?)?&YkB +??F?b? R?@S @M???' x?sRh?[k&??%?Z??Xk?$ X$???????????UG 1???0l??2????p??16?y?????J1E??e8M)W?4????~3^??$??&~?t'Uw?!????%1??s?? ?(%u??7x?I??G3????t?4 +>?YN?4??n?HR$?%?JLK!s???????h???????Cp?t??$r?F?,? ??w??}+???M?*??W??~???>E??Q?????ht???-??u????o?{{G??!?6????~?l???K?|x?{?7p??{;???y ?b??(YV??0"???O???/?N?????v+?????C?????????"??????\?A?)?m?F???????.VF??????????????jG????|x?\ ?Lr?v?.3?#??q|???apv0N +???????`??P???'??s??????56??=}??_ ??;?z5?? ^f? '6???H?6????P}??Y? ????c +??????!?????|????y?G???UKE????????z??????? Z*@@????,&q???????C?#??? +?%??$Mv+??H[??*??%?WD?z?m?G??( +? ??'?q*?98?????????\?????C?)?c?????D????C??s????3??5$??H????c???z???*?=??"?????TS&?}n?s??G?m?p:?3]{??V`?? ?u? +??O?v#N?? ?" ??$?W?????@b???^???> sYy??l?t?,d? ??i?#O??N???~??SwF??+??F?+???j/?????+:a=??????????8??S|e?{??$i??9????Iy~?H??a?%?'2O??5?`){???"&i?^B*qx???????0"?L??5???|???y +??j??$!Y????h"???O?}O????r?`?????N???x,qf{qu??q?z????????hendstream +endobj +468 0 obj << +/Type /Page +/Contents 469 0 R +/Resources 467 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +>> endobj +470 0 obj << +/D [468 0 R /XYZ 56.6929 815.7613 null] +>> endobj +471 0 obj << +/D [468 0 R /XYZ 56.6929 740.9713 null] +>> endobj +472 0 obj << +/D [468 0 R /XYZ 56.6929 742.4308 null] +>> endobj +473 0 obj << +/D [468 0 R /XYZ 56.6929 731.4719 null] +>> endobj +474 0 obj << +/D [468 0 R /XYZ 56.6929 613.4495 null] +>> endobj +475 0 obj << +/D [468 0 R /XYZ 56.6929 614.909 null] +>> endobj +476 0 obj << +/D [468 0 R /XYZ 56.6929 603.9501 null] +>> endobj +477 0 obj << +/D [468 0 R /XYZ 56.6929 592.9912 null] +>> endobj +478 0 obj << +/D [468 0 R /XYZ 56.6929 582.0323 null] +>> endobj +479 0 obj << +/D [468 0 R /XYZ 56.6929 571.0734 null] +>> endobj +480 0 obj << +/D [468 0 R /XYZ 56.6929 560.1145 null] +>> endobj +481 0 obj << +/D [468 0 R /XYZ 56.6929 549.1556 null] +>> endobj +482 0 obj << +/D [468 0 R /XYZ 56.6929 538.1967 null] +>> endobj +483 0 obj << +/D [468 0 R /XYZ 56.6929 527.2378 null] +>> endobj +484 0 obj << +/D [468 0 R /XYZ 56.6929 516.2789 null] +>> endobj +485 0 obj << +/D [468 0 R /XYZ 56.6929 505.32 null] +>> endobj +486 0 obj << +/D [468 0 R /XYZ 56.6929 494.3611 null] +>> endobj +487 0 obj << +/D [468 0 R /XYZ 56.6929 483.4021 null] +>> endobj +488 0 obj << +/D [468 0 R /XYZ 56.6929 472.4432 null] +>> endobj +489 0 obj << +/D [468 0 R /XYZ 56.6929 461.4843 null] +>> endobj +490 0 obj << +/D [468 0 R /XYZ 56.6929 450.5254 null] +>> endobj +491 0 obj << +/D [468 0 R /XYZ 56.6929 439.5665 null] +>> endobj +492 0 obj << +/D [468 0 R /XYZ 56.6929 428.6076 null] +>> endobj +493 0 obj << +/D [468 0 R /XYZ 56.6929 417.6487 null] +>> endobj +494 0 obj << +/D [468 0 R /XYZ 56.6929 406.6898 null] +>> endobj +495 0 obj << +/D [468 0 R /XYZ 56.6929 395.7309 null] +>> endobj +496 0 obj << +/D [468 0 R /XYZ 56.6929 384.772 null] +>> endobj +497 0 obj << +/D [468 0 R /XYZ 56.6929 373.8131 null] +>> endobj +498 0 obj << +/D [468 0 R /XYZ 56.6929 362.8542 null] +>> endobj +499 0 obj << +/D [468 0 R /XYZ 56.6929 351.8953 null] +>> endobj +500 0 obj << +/D [468 0 R /XYZ 56.6929 340.9364 null] +>> endobj +501 0 obj << +/D [468 0 R /XYZ 56.6929 329.9775 null] +>> endobj +502 0 obj << +/D [468 0 R /XYZ 56.6929 319.0186 null] +>> endobj +503 0 obj << +/D [468 0 R /XYZ 56.6929 308.0597 null] +>> endobj +504 0 obj << +/D [468 0 R /XYZ 56.6929 297.1008 null] +>> endobj +505 0 obj << +/D [468 0 R /XYZ 56.6929 286.1419 null] +>> endobj +506 0 obj << +/D [468 0 R /XYZ 56.6929 275.183 null] +>> endobj +507 0 obj << +/D [468 0 R /XYZ 56.6929 264.2241 null] +>> endobj +508 0 obj << +/D [468 0 R /XYZ 56.6929 194.7397 null] +>> endobj +509 0 obj << +/D [468 0 R /XYZ 56.6929 195.4818 null] +>> endobj +510 0 obj << +/D [468 0 R /XYZ 56.6929 101.3698 null] +>> endobj +511 0 obj << +/D [468 0 R /XYZ 56.6929 102.8293 null] +>> endobj +512 0 obj << +/D [468 0 R /XYZ 56.6929 91.8704 null] +>> endobj +467 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +516 0 obj << +/Length 4609 +/Filter /FlateDecode +>> +stream +x??]m?????>?????M?)JI8w??? ?;? ?F??f??=?????7???)J"E?b??e??D???]??!?,V?M|????P+*Q-J??.x???=?????Nx'??BK_???O>?Ze??U?(?W?B?BgjQf???????N?p?*;}?~}ul???Iuz???????????(AK?-R ??(K?Y??h?p????????'O?:w$-G]q?+x(??????%??????????G??????Dq???~?9ys??^??UH&?R?W +??j?,_???F???'?H??U?-???????-???\p#WV?}??r??o???J4????h???}??A????????U?m6?4g+eZ?_3? + +??LC???e?o??E??{???????>V???zSYp??P\ +h??W,?Uq?\@?s.)?N. y???P?Jm??(?V.? ?#\ _?????~+?C??}]????C?X????2n#???A6e_Yv?????$?DiK??? ?????h?D???(???"?cm??2Q +??,??'??z +??&??n?`L(Hkd???[) +\?????\?'???i?<+?r;) +;???)?$?0??&???N???A+?~????,V?????????@?(??J?K??????_??bE.?C?N?~?mW$?7?C??n????n?k?Zm/?7????~?????aw?~x??l?O?2a??7u??U3)????p????[uxo???????[!]o????????~???/?g ?M'|????>?&?*??????k?M?6??U+???O?p +?bA??N???_?_}]? ? ????e?^?h2 ??UA?? ?J@?BP??X????Z???? +8?f?Y ?M?????)???fv??cjA-tY??(?9f?????`y??'?Tr???HO_??U Je??P/;?Q?????Gi??3??oL !%?????:5??T???k'@??~??3?N????????? (?s??7R?????X_??%D??????[?k T?r????????,???] f`?????6`?)?[??P~??}??j~?????_???X???ukn*???58??nyA?????Du%L%F??$??????I?bm?O???fZ?"?&w~S?? ????]!??_?t?vV?3??4?g?0???j9mD???W$o??`????>v????? p?]?G:?'??g?j???b?L?I?"?#?????Z! +4R?????T&TI???K6???>??[$????4?'?????w;?&????^Co?N?^?O?w-?? _???d?7m??:???????f}\???????fOg???????i?x??????w???/???v?w?r??qQC??f???????c{e?^?7&E?yWk??M&e??4L_??>b??? y?[?j]?w]au?v?^????o???m???NnP%?i;??iA?37?y????? ?%?J?Tb??????q?B??`?m??>'???Px??|x?E!???^??@prN.d?\JG???H????A;?4?$??? ?? i;?W??}???u8????2?X&???}???)?c?????y??O??(;?????*9U?q??? ?H2????zsS?{?F??N??(???G?7?????o?J3^PK"N?o}m?????M????!(???6? +???+???:??? ?%?[?}xK?????D???-? ?k??w???:?#/??J`G?R??k???? +??S "??&Y ?gi??y*??? ??????????q?8) +???#?O:?? shz>u????T???=?Xo???J7g??ss??W???c?(*???S?P@%?m??Fn^?`a?W?= ???7?w?X)j?\A at m??i?P~K'E!G?GO?G +@?xj>?;?'C???\)??N?B???yr????|???%?~#!??BS??v??\s???Seh?y??Ee'E???6$UF1]??c??r:!UF?]?????2R????(?>? +??Se?^?L?????4?x?2? ??????Se??}??cG??Tyb??Tg??S??7I/C????M?1?x?2?R??Q??Pb??? H?=S ???2~??????t?7????3?{??s|?\??G^eW?*??"??#????VNSucc???>OP???j?=M??Y???6???t?=M?Po*Y??-t??qT??}?t??s&M?0;???,{U??V +O??^%?TnN?_~??UgP?r'D???.$S?]???y??8!M??]??a?Ir????1f},?SKg???0G????I???c~????m???d\e^f+D?u%?b?f2???R +???l.w~z?+?a????Y1????B"K?^`??F? ?g?5?I??CP????-D.?{?n +???%?H???l???I_????????uM??U mZ??>???o??????5????????sk??????k???P??m??a?n?&?????????T8????&?:????c????xrn?`g?Bz???N1<?~??9??_b>GJ?F4?o??(?Vn???H???? ??R$?[9=0?U??k????k5??????fJ????o>???tb?????A?W?V?y>?????B????MCN*?????W???85+R?&~??0^??i8??+4@?"9?B?#?>?E????????I??^?????&?J??F?d?}?NTB????wR???=???????]'?(??s?(?s?>"?D?)NE?????Pogx?????v???0?Zz7cL0???/ ?? +x??& +??1,62t????|????[k ??Y)??y????Pj????n?? +??96?96ql????????Onu?+???p?H??&??wl8?H/???b?????mPl?? ?J!g?6??/???P?+'E??'(57t??????? +(?:|Dd? ? (z?t??? Tv?Z?~??iKn>cb??? +?????\???b[)??!?g?????-???C??aQ?????s??'3?TY?/?nu^?????2G?V???p?{??????\?^?{Y7????h?n??????`.?]?;{??????? {??q??????????????I?>/ +???????P?-lw??????p??2?F??J????8C'p?d?n +??9I?^^????N8B?w?A??C?"D^*Vr??? ?He?*q?/?jr??<o???m???h???'8h?m??n3??2??D?Ho?u?}?h?k^9@??~/?????}??????~??#?0~?R?g???J??v??????W?s1d!?1E??'EA?r2??M4z?E?rY?????S??^???????/? +?3????S???????\A???qr??}?N???.jR???K?t?yR??_(?tQ?/uB? O?3?(?>??9&N??IM??7EJ ??GF?tJ?A??#(??C`?e?? ??.??8????? ??????=? z?&??????DH/=?j?DQ>?*g2?I???C??m??;??????X[b??f:?(?v'O?Gz?-?QZ?e?aZ?e??b?T???? +?gt?u#2j Qq??M????epE?5???eyw?~??-?mM??P?????????:?2>??w?&?]????A?k9N +}???????yY??W?B??????[??x?Z'0???K?>`?????>?,??b??x+?'X??C?Rse??s???q?l??sN?y3?X?????x}?????v6@?'????????`@`?????????8p??/??}b?]o??]o????,?toGJ??}=+???]?D?$}Z??vi!n{??T????)?F??$/?(??~? J +?????x???o3?iH?TN???B??}?????????P???f???iAd?}?(L`V-??? ? ??i5??]???k???_X5p????yR??x?????&[????f?K???? ?%_?oN? 37v{????7??7'?????h???e?endstream +endobj +515 0 obj << +/Type /Page +/Contents 516 0 R +/Resources 514 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +/Annots [ 530 0 R ] +>> endobj +530 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [473.4009 576.4484 565.4347 587.3523] +/Subtype/Link/A<> +>> endobj +517 0 obj << +/D [515 0 R /XYZ 56.6929 815.7613 null] +>> endobj +518 0 obj << +/D [515 0 R /XYZ 56.6929 760.0646 null] +>> endobj +519 0 obj << +/D [515 0 R /XYZ 56.6929 749.1057 null] +>> endobj +520 0 obj << +/D [515 0 R /XYZ 56.6929 738.1468 null] +>> endobj +521 0 obj << +/D [515 0 R /XYZ 56.6929 727.1879 null] +>> endobj +522 0 obj << +/D [515 0 R /XYZ 56.6929 716.229 null] +>> endobj +523 0 obj << +/D [515 0 R /XYZ 56.6929 705.2701 null] +>> endobj +524 0 obj << +/D [515 0 R /XYZ 56.6929 694.3112 null] +>> endobj +525 0 obj << +/D [515 0 R /XYZ 56.6929 683.3523 null] +>> endobj +526 0 obj << +/D [515 0 R /XYZ 56.6929 672.3934 null] +>> endobj +527 0 obj << +/D [515 0 R /XYZ 56.6929 626.7955 null] +>> endobj +528 0 obj << +/D [515 0 R /XYZ 56.6929 628.255 null] +>> endobj +529 0 obj << +/D [515 0 R /XYZ 56.6929 617.2961 null] +>> endobj +82 0 obj << +/D [515 0 R /XYZ 56.6929 551.6516 null] +>> endobj +531 0 obj << +/D [515 0 R /XYZ 56.6929 523.4973 null] +>> endobj +532 0 obj << +/D [515 0 R /XYZ 56.6929 472.4201 null] +>> endobj +533 0 obj << +/D [515 0 R /XYZ 56.6929 473.8795 null] +>> endobj +534 0 obj << +/D [515 0 R /XYZ 56.6929 462.9206 null] +>> endobj +535 0 obj << +/D [515 0 R /XYZ 56.6929 451.9617 null] +>> endobj +536 0 obj << +/D [515 0 R /XYZ 56.6929 441.0028 null] +>> endobj +537 0 obj << +/D [515 0 R /XYZ 56.6929 430.0439 null] +>> endobj +538 0 obj << +/D [515 0 R /XYZ 56.6929 419.085 null] +>> endobj +539 0 obj << +/D [515 0 R /XYZ 56.6929 408.1261 null] +>> endobj +540 0 obj << +/D [515 0 R /XYZ 56.6929 397.1672 null] +>> endobj +541 0 obj << +/D [515 0 R /XYZ 56.6929 386.2083 null] +>> endobj +542 0 obj << +/D [515 0 R /XYZ 56.6929 375.2494 null] +>> endobj +543 0 obj << +/D [515 0 R /XYZ 56.6929 364.2905 null] +>> endobj +544 0 obj << +/D [515 0 R /XYZ 56.6929 353.3316 null] +>> endobj +545 0 obj << +/D [515 0 R /XYZ 56.6929 342.3727 null] +>> endobj +546 0 obj << +/D [515 0 R /XYZ 56.6929 331.4138 null] +>> endobj +547 0 obj << +/D [515 0 R /XYZ 56.6929 320.4549 null] +>> endobj +548 0 obj << +/D [515 0 R /XYZ 56.6929 309.496 null] +>> endobj +549 0 obj << +/D [515 0 R /XYZ 56.6929 298.5371 null] +>> endobj +550 0 obj << +/D [515 0 R /XYZ 56.6929 287.5782 null] +>> endobj +551 0 obj << +/D [515 0 R /XYZ 56.6929 276.6193 null] +>> endobj +552 0 obj << +/D [515 0 R /XYZ 56.6929 265.6604 null] +>> endobj +553 0 obj << +/D [515 0 R /XYZ 56.6929 254.7015 null] +>> endobj +554 0 obj << +/D [515 0 R /XYZ 56.6929 243.7426 null] +>> endobj +555 0 obj << +/D [515 0 R /XYZ 56.6929 232.7836 null] +>> endobj +556 0 obj << +/D [515 0 R /XYZ 56.6929 221.8247 null] +>> endobj +557 0 obj << +/D [515 0 R /XYZ 56.6929 176.2269 null] +>> endobj +558 0 obj << +/D [515 0 R /XYZ 56.6929 177.6863 null] +>> endobj +559 0 obj << +/D [515 0 R /XYZ 56.6929 166.7274 null] +>> endobj +560 0 obj << +/D [515 0 R /XYZ 56.6929 121.1296 null] +>> endobj +561 0 obj << +/D [515 0 R /XYZ 56.6929 122.589 null] +>> endobj +562 0 obj << +/D [515 0 R /XYZ 56.6929 111.6301 null] +>> endobj +563 0 obj << +/D [515 0 R /XYZ 56.6929 100.6712 null] +>> endobj +564 0 obj << +/D [515 0 R /XYZ 56.6929 89.7123 null] +>> endobj +514 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +567 0 obj << +/Length 4426 +/Filter /FlateDecode +>> +stream +x??]m???????( +?[? _$R???I?A???h?4??vW9?????]}I??HQ?wW?6Qd??<3??H???????r?xI?UAr$8a???^????xE4fc@????????U?JN???n?)??? ?J*V7?????????<7wmys???K{<5????????*????LP$-VBP???C???(???S?????*it%A,?_?*?????j' +?? +??,??Y?F4+???*'??qj????\?e?h>??p?O????j?%??$?V8????+?]#?6R@!D/?(*??X?+???^?Y?????%?Z4)?~???????? + ^??W??wSmTd%"8????o]?j]??,H????????|7??D??r?J ?3?o?>?o?6???Y V ??biL/??OD?s Jy????\? ?%e?gG?????L?VH~AiJ7?t;?U{ ?9?????v?J??&?:aj? ??7??S?=?Ni??.?????4??"?R??H???09??????????(?L?x?a?XT?_???=Y|,"??M?Ej??V?9???:q(:Eb? ??O`??R ?I?????\z?L?5???9?[?5??????i~k??f?7????Q??/???smY????p?f~W???m=????????????[??Z?????iE?????l???W?"$D??k?N{??v??N ?K???Q%??M +9-H???q[???6??p?!???9?P??9)? +9?q&_?j\???z??9cs?=?9????R?????~P?W:R??????m?)r?+GF7??T???2a?E%HCi?6S5?`??????LE?U?w??\*?q\???r?#LZ?j?4?????~=n?x?????o????/?:2?!?E?(#B.????,???IZ?H??/?a4?Pb??n=???q?O??`*c?Z????]??S??\???W????c2E?,K4?D??????Q?J?%???y?dX?'??3???_J????7r^?????~?v?1^SL0?)??%?????k >?????J????????????%??dKgx=???r?c9?wbAs?????u`^???F?rA??????????D?1?????6??@^??\????? +Z?A%?5????????>7p????Oh?UZ>y82???&?XB?H?,!???\?@??s?S?T?:???w?;?e?????`? U??v??5.? (E??O?h?? ?d????????@?????? ?@j7??k???@??G?uXpti?K +??2'?-???????x??(???6?k??.<$o? +:5A?????U??Y???w??j_??I?N5"??4????C?P?????K?7?S?????a?????G}u?W?y????;#?0.? ?e??7?uG?<1??!???? )X/????c???b??$L??T?*J??Y?u7&?*2D????R?*3DK????Uj|BE???c?.d?tu?? ??0?#m?|&s?4}H~O?r???}xf?,??V?]??f??R?z*??s?? +X????#1<h#c?7?5c???? +?H[?u ????e?Y? ~ ??????FE???D??? +n??C[5??????)?tw<=VC?'[????:B?Mj?]S?u/\WE?7}-???'??q?D???9k?d??d$??;?>6??2(W)????0??????????zt???n???v??????????9?xG?3??n&?w?????9P9c8???e????"?E6?;kH?B)?? =?aw$???.?De?0??=l???c??8????&?6)?AVB5??&Y????v?%x{??*?hU????E?`?????hKr?s?Y????%%?g1??R$6?-*Yu??O??Y?^?? +U?Ig????vg?S?:?=TI???#s??A +Ln???:Y?_WI?gp?zP??%??H???:?p??"2?#??H?\W??:[?TY?????K??2Qu???UG\y???"UG??????z?`A?B?J???????nT?c?:??:- ?)???X??B??x??W?3y???^???dYC}???x"?? h^?????My??q??"???7D? ??,?? ./?R???S?]W?3?,j^?????My?5?)??????O??MyO?fp?j??wH?gQ=?H??#W[?l?@????????c@?R?=???aj?w??'S?}?)? -?sR??`S??&?????????? ??????m?????d?;h?p?? +?M??-.m???F??W/?g9????y?d?PY???*??Bc+ ?"F?O?K??DX??????K??'m" +???Hk?(?u~_]??~??h]????fz??30O?????????56?5:?.$?-GO^~/?uE|?????????b?> endobj +568 0 obj << +/D [566 0 R /XYZ 56.6929 815.7613 null] +>> endobj +569 0 obj << +/D [566 0 R /XYZ 56.6929 760.0646 null] +>> endobj +570 0 obj << +/D [566 0 R /XYZ 56.6929 749.1057 null] +>> endobj +571 0 obj << +/D [566 0 R /XYZ 56.6929 688.5546 null] +>> endobj +572 0 obj << +/D [566 0 R /XYZ 56.6929 690.0141 null] +>> endobj +573 0 obj << +/D [566 0 R /XYZ 56.6929 647.1948 null] +>> endobj +574 0 obj << +/D [566 0 R /XYZ 56.6929 647.937 null] +>> endobj +575 0 obj << +/D [566 0 R /XYZ 56.6929 636.9781 null] +>> endobj +576 0 obj << +/D [566 0 R /XYZ 56.6929 626.0192 null] +>> endobj +577 0 obj << +/D [566 0 R /XYZ 56.6929 615.0603 null] +>> endobj +578 0 obj << +/D [566 0 R /XYZ 56.6929 604.1013 null] +>> endobj +579 0 obj << +/D [566 0 R /XYZ 56.6929 593.1424 null] +>> endobj +580 0 obj << +/D [566 0 R /XYZ 56.6929 582.1835 null] +>> endobj +581 0 obj << +/D [566 0 R /XYZ 56.6929 571.2246 null] +>> endobj +582 0 obj << +/D [566 0 R /XYZ 56.6929 560.2657 null] +>> endobj +583 0 obj << +/D [566 0 R /XYZ 56.6929 549.3068 null] +>> endobj +584 0 obj << +/D [566 0 R /XYZ 56.6929 538.3479 null] +>> endobj +585 0 obj << +/D [566 0 R /XYZ 56.6929 527.389 null] +>> endobj +586 0 obj << +/D [566 0 R /XYZ 56.6929 516.4301 null] +>> endobj +587 0 obj << +/D [566 0 R /XYZ 56.6929 505.4712 null] +>> endobj +588 0 obj << +/D [566 0 R /XYZ 56.6929 432.9649 null] +>> endobj +589 0 obj << +/D [566 0 R /XYZ 56.6929 434.4244 null] +>> endobj +590 0 obj << +/D [566 0 R /XYZ 56.6929 423.4655 null] +>> endobj +591 0 obj << +/D [566 0 R /XYZ 56.6929 362.9144 null] +>> endobj +592 0 obj << +/D [566 0 R /XYZ 56.6929 364.3739 null] +>> endobj +593 0 obj << +/D [566 0 R /XYZ 56.6929 353.415 null] +>> endobj +594 0 obj << +/D [566 0 R /XYZ 56.6929 342.4561 null] +>> endobj +595 0 obj << +/D [566 0 R /XYZ 56.6929 331.4972 null] +>> endobj +596 0 obj << +/D [566 0 R /XYZ 56.6929 320.5383 null] +>> endobj +597 0 obj << +/D [566 0 R /XYZ 56.6929 309.5794 null] +>> endobj +598 0 obj << +/D [566 0 R /XYZ 56.6929 298.6205 null] +>> endobj +599 0 obj << +/D [566 0 R /XYZ 56.6929 287.6616 null] +>> endobj +600 0 obj << +/D [566 0 R /XYZ 56.6929 276.7027 null] +>> endobj +601 0 obj << +/D [566 0 R /XYZ 56.6929 265.7438 null] +>> endobj +602 0 obj << +/D [566 0 R /XYZ 56.6929 254.7849 null] +>> endobj +603 0 obj << +/D [566 0 R /XYZ 56.6929 243.8259 null] +>> endobj +604 0 obj << +/D [566 0 R /XYZ 56.6929 232.867 null] +>> endobj +605 0 obj << +/D [566 0 R /XYZ 56.6929 221.9081 null] +>> endobj +606 0 obj << +/D [566 0 R /XYZ 56.6929 210.9492 null] +>> endobj +607 0 obj << +/D [566 0 R /XYZ 56.6929 199.9903 null] +>> endobj +608 0 obj << +/D [566 0 R /XYZ 56.6929 189.0314 null] +>> endobj +609 0 obj << +/D [566 0 R /XYZ 56.6929 178.0725 null] +>> endobj +565 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +612 0 obj << +/Length 2914 +/Filter /FlateDecode +>> +stream +x??\k???????0?A T?y?\h????K.f?C???????+??`E2k?+???????1C?????{??p??WA??? AL?? ???o??? +??#n4)? +F?R?]?LR??????_-?o)Gk1?hC??b.?_??@?????,???? ??????????~?? ????Hn??`rT??a?8.?p?V???^ +?8m???uo??lOF??o?l??O>^?Ip??)??7c]Iq?8?"t%C]'??40V???z????????,!D]?C?LA?44+?p?~??zXO??????F??@X`??7? 1?i?Y{?/???q??pNz??9?????*r?9???i?*?YwY???a??L??????g??v-?aw,#J!*??;????Cj??*?pN???y?????o??|(?JS)O?+$??)??????????x??P!' +?M??T????{?*"? +????%?s??]???????=? 8???t??H ?#3???HH?Ss?n?????&????eF1??hS?UR|?t????k3????%?AE +"??t0dd?[>?h???T?\&?;n????R??6j??!?? 6?????^??^IW??Dz???M?w????`%??5T&lw7Y]R!.`E???a=]?f?4?f?]?????eX?A??>?|2??3N???!oq?X????.?/? KB?#"!???s0?;,vq"?a??0MG%?r???&0????r +???| Dn?s????4??$7??????XF???????c1?=?? ??=uy'???a??G??????:?H??e??e?]l&??nd??E?%CF[XYt????1j??DIu?????F????G:=??.,??7p???:T?M??j?? ??J?P??Z?>??bO???s???FY?o?U\F??????d+???F?? +??q??1x}?l>Du5&?2???????#Fc??PT}?{??h?I?qJ?,?h?:2???????K:;??#?? /?q?K?g?????mPt9????n?}k??+?j +?????????f???`If????X??C?=z-u+?k*/???b?+??CKu?-???aL???????e ???????y?_????%???G???????N??b?.J{????????????aWoo?? @a?R%i:?]??+???Z?????U*??J"?ISzP?22????R??*?hX?c?`???D35?? I???r????h???\????5?E}?j?????b?4h???h?;B?@???&&s+???????Z??6?M2Xo?????jUY.??v ???/???C???[]H?HD{zJB@x:?(???O????K??h?z??A???)???????2?V???;??9?u??R???#u8?L????{????=??]YFVD ?I?s?????|?9????n?}??-???!?YS?????????<????K$?6??T?sh????H9?c?F??ss???????p?/???I?1?sR?????S})??fSO??~??????!??c? Mr?k????????y?k2%0h*?s?3??0???????Q;?uBG???c?????~??b/?????m??G9???pq8???nI +#?????m$2A? ??o?Y]?? tm??r??????tV??vB???i??vX????bJ_g?0?Y?????>? gB2??]K?G??k???r????r??}???YC?? ??&??d?rh????{???y???+??#N??eC???pA??X?s?>^?:?8Q`??t??D??o?:?0?????arA?cP???v[?*(?????V?K?m???????????]?,W?]iwU( 7?z*\??`?&]????? +?u????u{???\3???um??v??m?X?z5p???F??j^???9???? +??.???)??Ny0?8?b&=L??t?]?]?F?G?????x???H???a????????'?\-?~????,rr l??T?;?6Y??/>?{??)??????B????QY??r???,?>?jf?????} /&WVc~g???VNJ{V?'????Pw?XR#?"(??s?W???d??id-? +a?x?Q??????Y???I?)?~LP??+???????M.??]????????~?ar???8F???9?8-??M????e?i +???M???*:w?M????mu???z?'i=?~??d?H?rO?a?Nx?????C[>?H?T!,?'??O????H N???????L?n?h?????S?endstream +endobj +611 0 obj << +/Type /Page +/Contents 612 0 R +/Resources 610 0 R +/MediaBox [0 0 595.2756 841.8897] +/Parent 513 0 R +>> endobj +613 0 obj << +/D [611 0 R /XYZ 56.6929 815.7613 null] +>> endobj +614 0 obj << +/D [611 0 R /XYZ 56.6929 759.0684 null] +>> endobj +615 0 obj << +/D [611 0 R /XYZ 56.6929 752.3934 null] +>> endobj +616 0 obj << +/D [611 0 R /XYZ 56.6929 706.1021 null] +>> endobj +617 0 obj << +/D [611 0 R /XYZ 56.6929 707.5615 null] +>> endobj +618 0 obj << +/D [611 0 R /XYZ 56.6929 696.6026 null] +>> endobj +619 0 obj << +/D [611 0 R /XYZ 56.6929 685.6437 null] +>> endobj +620 0 obj << +/D [611 0 R /XYZ 56.6929 674.6848 null] +>> endobj +621 0 obj << +/D [611 0 R /XYZ 56.6929 663.7259 null] +>> endobj +622 0 obj << +/D [611 0 R /XYZ 56.6929 652.767 null] +>> endobj +623 0 obj << +/D [611 0 R /XYZ 56.6929 641.8081 null] +>> endobj +86 0 obj << +/D [611 0 R /XYZ 56.6929 574.5297 null] +>> endobj +624 0 obj << +/D [611 0 R /XYZ 56.6929 537.5329 null] +>> endobj +90 0 obj << +/D [611 0 R /XYZ 56.6929 537.5329 null] +>> endobj +625 0 obj << +/D [611 0 R /XYZ 56.6929 510.1788 null] +>> endobj +626 0 obj << +/D [611 0 R /XYZ 56.6929 476.3408 null] +>> endobj +627 0 obj << +/D [611 0 R /XYZ 56.6929 477.8003 null] +>> endobj +628 0 obj << +/D [611 0 R /XYZ 56.6929 466.8414 null] +>> endobj +629 0 obj << +/D [611 0 R /XYZ 56.6929 455.8825 null] +>> endobj +630 0 obj << +/D [611 0 R /XYZ 56.6929 444.9235 null] +>> endobj +631 0 obj << +/D [611 0 R /XYZ 56.6929 433.9646 null] +>> endobj +632 0 obj << +/D [611 0 R /XYZ 56.6929 387.6733 null] +>> endobj +633 0 obj << +/D [611 0 R /XYZ 56.6929 389.1328 null] +>> endobj +634 0 obj << +/D [611 0 R /XYZ 56.6929 342.8414 null] +>> endobj +635 0 obj << +/D [611 0 R /XYZ 56.6929 344.3009 null] +>> endobj +610 0 obj << +/Font << /F50 100 0 R /F51 103 0 R /F92 158 0 R /F52 107 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +244 0 obj +[94 0 R /Fit] +endobj +291 0 obj << +/Length1 761 +/Length2 1025 +/Length3 532 +/Length 1573 +/Filter /FlateDecode +>> +stream +x??RiTW?S +uA???(??l A??DS?" ???????aB?A???j=??? +?????D????w j?n(????S?????y???????????.A?PJ??;???`?\?????1X?`"F?S +?_$????@?x?b??X??`?`B?FbI?p +f????DIL??@?P?PCs(5? ??8@?V????S ? +Q??(?????? n?&?$???4???+?B2?\?d?-%pu@????I?? ??????\?S?g"?^?>??VG4?:?-??hu$??@!???F?7???t??U??1?ORC??????r?-?8?~?$[??8=Z6???????1j?i%LkX?W????i???|??????[??*?????????6O^????u&??Cap?r?9 ??'? ???>??i{n??9I??.% ?~?.0???T at KzM???.,s??}??Y??'???l?,?s??????????=??H}f?`?4x?????Kn?{Ou?Xc?`??J???D4[?F9?;???h?$?5$o0j?olK?K!??W.?*hz?{??q????6?q??W?Qm??EN2??<Z??v??b?????9hd???Uyih?jM?#???2Q?C????uO%??(7??.??????GY??W?????n/v??~!PEn??????? k???~????k???8????????nia? ??%?g=?\?(+f?i?'??1?'?O(?!)B??*????L?endstream +endobj +292 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 636 0 R +/FirstChar 45 +/LastChar 45 +/Widths 637 0 R +/BaseFont /RZVZYK+CMMI10 +/FontDescriptor 290 0 R +>> endobj +290 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /RZVZYK+CMMI10 +/ItalicAngle -14.04 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/arrowhookright) +/FontFile 291 0 R +>> endobj +637 0 obj +[278 ] +endobj +636 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 45/arrowhookright 46/.notdef] +>> endobj +288 0 obj << +/Length1 753 +/Length2 637 +/Length3 532 +/Length 1177 +/Filter /FlateDecode +>> +stream +x??RmPTU.? ??? z?!????,?? +a??R??s???ra?^???]??Dt?L???/????PlG??0"? ~,H?R j u'?Y????s????@?T???~???+]C?,wb?%??y?~??h?^??e?~?8?3?????y7?F??'sb???joG??V??? ????em??)z???yI-????b?q???????{??????_??U^8??nt??ZS?T"??+x?|??;?L?????Q??.????'1???????{GSJF??[???;"O?h?sZ?qN|???E?,2^????j?????|??,nQ^s??Sw??2???Y~??KyI????+o???????K?.??1Y????>?,z?g???5t?]???m? ??!???j}??M?I???[??-??2? +?i?oIV}p?&?????K/???> endobj +287 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /CAGRTG+CMSY10 +/ItalicAngle -14.035 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/arrowleft) +/FontFile 288 0 R +>> endobj +639 0 obj +[1000 ] +endobj +638 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 32/arrowleft 33/.notdef] +>> endobj +640 0 obj << +/Type /Encoding +/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozeng e/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis] +>> endobj +157 0 obj << +/Length1 1612 +/Length2 17647 +/Length3 532 +/Length 18565 +/Filter /FlateDecode +>> +stream +x???eT???%?kp????wwwgwwwwwww ???=@???{Nw=????????YU?f??Yk?EA??? djg ??uf`ad???l?]???le???.??Fv + +G??3??V??? +??D?&VV @????dn? ?VS??????/??!c?????? dn ???? +?????:???????-?3?5 ???%%/???WHm??F?Eck? @d?u?????^L?lMA?????K? `p????n????q????6 '??????????o?? [k????????????????`?vN?N&? {g?????????la??On'?_7???o??????%???????d?p?;???09?[y??????/.N [??b@p?9?Z????????;?U'????????_?????8?????f?,?s?8??m?E`?gP?l??,???????O?+??_ +??gfh??02????????????P??????'????-?????O????;????B??X[????_0??7?@??cm??? +7?Y{?6?g???$??p????6C???? ????6???A?@SE???????o??eW?5:Z?l??W3 ,????S??X???z??????I??H??????('?L??w????j???a????(E???-???sx1?=? ?l??? ??????? ????rF?? w?????Y?U????k??0b?&v????????????_??&.??U????[??\?k??@w? ???? O?ezV?s=N?????`? ?H?}Y?jq??]?_z?.W??{]c?4?G??????Ci???~lk??T?u??@!?e'?Q ?~R??F??????6???????~?;???.6G??g2?BL?'{d_???8?n?f0???? ????'????#?}w??t?q??5z???)???#md_? ?m;e???3:x??%??5?o???x??????>7\(??px[???g???f?`?F~A?R:?{????? ?-??(u?5???R03?F?T#???;Qx???X??s?m?R??5???????.dM????p?[????Z8????DL????j?OH??\(yt?^G??'T??=?Di? ???25??u??.?>'???t?tX,????r%} '?'C?6^??????q?? Fm???:??h?]?|n?????????v8e?V??/e???????5? ,I???x??"?^&O??8*???vj?4????Pv?[????? e)??t?f?T??5^??6?3i0?????'??e?X???+?6^{2? ? +??_??6?k?y??????*=u??<8??m'?X]r$?#z?????????%??????}w?E?1B?m???Z.5|???c??????lY;???s~?j_??x??2?U0\:??4O????L??i?w?3HV?8c??&'Oc?Cw~?>???6??a?|-??????????G?`2?? ?dJ???*?D?i ???????p?2XA????{3?Z?W????d???',r????]?'fB????*?p}H?\l?????+j??f??$(?@?????????U?????k?JG??X=? + ?5K^Jm? +?5? ??%??e????????z? ?'?e?T?????????????cI'??8?? +?o+aR??`U?Fo?a,b?^????!?!'=?;???<>?n1????&????>??oKZ??g?????x1??Z?A??? e?u??#??8??a????J1?7?Q?m +?I???gz???? ??nM???n?*?Z%CH???!????Ro?q]???G???j3c?{O?JN:m??u??EB??}e?????U???,????????i#?rW??n?y?? ???pu?p?????i???,j?Ej?????9?S??Ea??$&R0V?3P?F??}l3 _8+St???R?JDC??4,??#P/??????V????q:o?2???? |,??????.???#????s?}?7{J +|?9??Zb?Zb?~??,6W??1?Sp?v?????s~??????wR???W$c?`;??~S??????G??6T{i/?2xs???????.??%?4I|??f?H,GiKVr&F? h??t?????????v?X(???'m?????>? =6? E???-???bv?djlhK?O? +??a??F?]?;????4???_?\O?XU$?MAW29??????????"8????!]j??'^#_j +?Y#??Be?????? X|?j????v?k?A??8?w?x?????z ?????l??B??*w?k?i????? ?J?}??@Fe0ua??T?m???a???\G??r??o???x???Sp?O?8w+Zl?#2Z??????????%,r?>??+??????N?~??Z +??#?jj1???0|<????N"?'qK????y?x?K>~E??gb??U#?M??N????,?"CC???0?????*+?/??????????L???|????gLG?r6?!A)??w?P ?k?7?????y?(?m????????)???S?EB????g?????j?C+a +rcsp"}?4?????r????oL=0Uuu??????wS???8????%?,zg?$?????H??eV??M\n??=??3?? ?c:??????Qg~;D7?Ol??x?~?N???}????]AR????h?s???AQ?-?I^?Jn????YNP?Vw????0x??????C??Xh c?s-l +Y??Z??h?c?|#???ZW??4????????9??? ??*??????^>?Zd?3??m???e +??Y?/?Q@?k??xbV??O??7???2 +?????Z??t+|A???E??4???k??B?`?tH ????f8??)]V??????6??jT3?|?)?w?D9???ac??LQ??g?kK??61w?Xsm??_??F.??U8vzU9eb?f?}&? U?,????????=4Srz???|?.???}8??nYjt? ?1??h?;j35% ???X????,??????&??? #?~??0i$R?{??kpd??c?N?-O???????&F????wm'2??9??V1???xu?a??6?????Ow?+??SG???????%??Q?>h?r?P?'s?5?Xo?F?W?>??]???-?I?~2+?d?H? ?????8=7?ET???=????????5?t?x??U?7'?,?I??0~?X4~?????y??_zO?]??@?P*I??????^????_?}??????1LSzH?-??w?G>?????y?>=?Y???a?aD at +???fQtj)??7}????w?8I?;? @,?d?mu2??m?Dh????_,?????n???,???Z=e????q?\???U=eF????t????????9??'Uu?a???nw??? +??a`?r{l??fP??!>6?r!?G U"2omE?y???0????6@??s?0????C?~1|???z???? +(l??(W?;????u????#??Il?8~??I???1???????7;J????H?,9??????a5??eQs????!???.k?(???"? ??N??03?Y??p?A???y0?qsG|?i?+???>3???E>?P???0?????Y????d?F?.< +El??Vk{?Z3??3r?j?6??????? uy6!???E?k9m?|[???/?F??77?????^:?X?????yC????|k?<&??9` ?e2;? 4>????d2???y????i?5H* I1???hEI-x?A?6??jc_??&????&???:??k??`b????-??w???q?Q.?~fhP??)[??|???-?H????X???eo?x????]*)iL???????lr~ ?T??>>^H???~.???S?AM??5??q~?_??]?????????s?f?k?Y?8???????????f?)L ,??i}?9?? ???(????}?JP?V\??Ew??ID(??7???M??d??e??DadP??$?3??^~2V?.?Q?*??xcZ?sK!UAa???3 "?G?? ?.sR?6??>)2/{?;8??m???q|??$u?Fr?)?0????|??F???????dov#?tF??:????o_\!?j?E&??Ja?" ???2?3??7??L?????? ?????'96?? ??;???G?#????????"??-mT?x? +?(????q??+??F? ??X?A96Na?q?n;??m???vd4?Z???g??-???? C?H?????? ?7????;?L????????)?f???!wl????]&?]?k +? +?????I>{t?a??>??rW??ir:?(?f{????0?Z?#??????r???? +??r?9? kV? +??? +j??C???SW??&??'? ????!?byp??(?~ ?m?e%K^yr??2?s????0Cj??\h?d5?-?N?????EE?RC???q???????\ ???mN??$P7?????? +5???Auf??_*?^?? +???E????i7?H???'?[J?e?B?!???*?2$???L???j ??1????Y???e?y?f/y???????7??j[5??uU?&?e??}?(?????w|??2?????"?R+?c??[Q??< W??"W????}?E?????hE??? }{?IWt?'?mD???v??'c^?rn??"H|?"?\?????????^~???;?v?N?#>U^v +??g? ?=!)?h?/?F???????zo?e?S???????P?b??m,xWn?#???- :F??}?r G?>5.?:hg?@G??>? r???6f?xB?]? +?S?J????f?@?J?????;!H??})??S??|?????/???sr?4vO?Ok???:????kZ??~?????7l$??/??s?}o??????????x??%!??T?V]?Su??0ifr?s?(,???sc???|&????/???_*??Z/???2??P??? +??pN +K?ri????r?G?i?N,n??z???C<7?j?????????*???h??B?B ?Q???7?wT?k??.?t ??dF?\?G?'?eh??#?9???u(2;??????Vt?N?????y????F?e?????y?Pn???U?5Y???~?P?CY?c??u6?W???3}-o%?x?}?M+?????~O?&???u??| ?Sy????l?P??> K??U???)vW ??5WI ?k?V???2BQ?XO>?\,???>?%?.??D??+a|???U??;??????/?I? ????l????z??0???6?[???R]*?,??)??e??V???%AD??b??w?f6??f`?_????9??????g l?????Z??v?p`?G??????>3gu0??f??? 4?X?`?mb?}?a +?2o?tK? O)x?U??/???=??d??? ???T????t??????)????]??6???|?q"??!?0,et2e??W2 +???????F?=GY?`?]??M??>??@??Dl??? +'Z???????f?0???Q??? +???E??J?s?+?u??? +o?????E???l&??????A?"??D?h/rG?????q????0??????yt?r????K??P???????+?(??7l?????Y?F a???? +Ao?X?I2?l??[z ++?\?0?G???2??2?Bz??%2dI???e??NqB?Y=????1?#U??|e?OP??????w?(???d&????o?j???8???0?????8???:`[n&??*?'Q?Si6)?*?tm?2?\9\nW??r?b +7?$????mu??9?r?!??m?S_ +%q<@?S?q??+??????Fj~????z?O?iy?K?F??t??;{,?@?X??????????k????d=Y4??????=?R??? ?.???? d?`Nj8+7?sU?H??E"\? +?$??'??!?? +Uj???NsT0_?j???/?? ?0?v?VI(?S8???7???-U?{US??L??????F?^?+)g?? +c????A???=?A???*??p*?????s^???M-C-x??????o?%(EU??L}????I????a????????????Pb?wB???K?'p??Dz0?X?q?F^???s??]O(w?????%?32~??s>/GL?????Pi???:S?X?g???pvg??????? ?-??V???O?I????? Q???,L?;?d?}? +??K?/5f?C&????z??&??,???+??=}6|yE???'?g?EF?????{??????!??)?)? a"??#p??C??!??a???@?a[?o??3 +G?|?5lv???ze??]??%P?$RS?HF???f?Yz7]aq?":????m?p?s"?????N????E?=0j?W?`O??%c?.(?A???2???????}??n>(??=??Lz?????FB8b?????_$?St????????$?9??(H?????q?=??u=? +??sk?????[)??[? 82??p?? ??C???U???w?????)?E???|D?F?K??^???i~?o?????y??X???I???8D?x?a?? ?_????C?T?&??-?JQ??f?B?????C?5?????B?V???N?lx??a???r??6` ??!?=?? ??6W?ez???9??p?XB?u?FB??? -?? ???T,u? lC???t?X^r?#Es??$?zyW??n?s?????C??l?]???2?.*??D???p??&??"?1t?=??8??L?~#?u?F??????X?8K??U?)?????L?G?U??O???????\????oh0'?:]8y=??@???????Dh?A?????-?6?(????WIX?,=????64???+!a????????L?a????{??V???4H?,?s?pQe?????????B?wZ???3i??'???????j?}iZ?(?LI????H??Es?????[?????O??$l??B?G???9???u???hs?i??%?z???????`;4(??A???d??u +"?{I????_??P???|"?'@?????K??)?Y??????#n???|jm?,=?%???M +?d?????P?a&?W????I[??I/,?6?9?b,?K?V??X???????????eV???1?N?X????\?pAC???e???'???t'???2???????????cs}??!ee?????w??? ? ?????b?|T??t?X^?D?S?+???zeH??IZ????^U!{??*r/G??n?=??-S?&:?mfb]??{?(??-??emx??]???ZBT?iUm?Z?E???T?_???Z ???])???W#??6??x????H??B?F"??ny?>?XX^?q????;???az??i?U|&??r?#m??~??;?(2S??4?wt?Wdmo:???g??aF??n?Yw??*??X???j??Zgr2????W????SC?YU?=?v????k? ?n(?~2??R?-[???9?5??????F???0?Q??}??:?>f???W?t?d??}?[v?Sk?R +O?x??a?y??T8{)d???@?U'??_?L??q???V???C??gtE?jFA?^?B}???2??A?#???a(WC????r9}??S ?k??C|n??V??2????QPq9#?D ?4u'??\??1??'????,? +?x?? a?:?8?z??w?>0?q??????*o?G?[??v??F?jiJ?"K?;????????l? +???k? +uc6??a??3q ?{??$???c:??:?????9~?K61?8nw?{j0]?????[???? +?????-R????zO??????f??5?M????Vu?????t?&???AC?y?/`?hH0??-N&??{?9???yl?A5dy?n?"??3um?_?.??)s???rLv22?xal?71?d???}??2?Y?5????&L??S???W*PL?????+?L? ?:QUVR ?V?y?3P?`??u?u_???????N?"???-0e??!VYoa?????e ?t??Wz?P???EgG?;?Z?????`??f????7P?3^?W??%??&?n6?*~??t.I?)???????S????R??Y??'?F??1?r?????5???`[??0x?T~d/}???????????,?~?Ra?bZ?9Rk?S#)???C?????-????????z-a??,c?2??F??. n??eF???W??;????C?+`???A0?(]?0????????t????? ?5:????p?c????m?I? H??@?U?$?m?????4"? ?Z +G?A???"?????w??????!@#??=}???H??M?????;??#??k??-???|W?@?f?G|?a?\M8?? +?A????WmFF??????>_???[???????Qor?"??,?w?q ???3?bD?~? ???[+?T??qy8?o1q%eF?#??????^?Mh?B???n?.+??s???;W???>??v??;c?d*k{?xi?P?l? S?}W?????^uG??C???)?????&i???q@?????2bP??~??O?\??rt???E??fm??F?r?4#??x? ??N+]?T}?????=n??N???=?_}????/?^5??mc?JYFb????U??>??M???!?JX??S@??6??f??knMI???Xr???s?rl?#?T8E???[??n?W6k\?5??i??K??c?????? ?-AA!????V?s??}??.? 3$??=\r??:????A???B??Y?)??????{???^j?L?,??? +?~??=g7'?*?`?9?d)?0?K?2????!??????????:?t#?A?#v??rf?????E?rza??v5?l?D }+????(?w??? ??0aP???????q?S'?:?? ? ??T?X??+)???M????\?}SsB * 8??v?w??2???0s\o%,?31???J ???????Mz:?E????~??I0?n1?:r)?cd?o9??<??L?O+???`?U????e R( +??????`????\'?J?/??????p???????%]-!?V?Nu?;??t +k??!??+?????`?#?W#?v????xU?T\?????[:????1??SP?}?">R????";d??JhB??'??y/^?Z?N?>????Fx?B???8z??H?]gm??88?t ??S?f???!? ]??i%?P?H???L?G???m??H"?-9?????ZM??g?\????h????S?????+?u??k?C10^X?iM-I[W??e????$?1?P???!??xs]?-?O?$???????+?O%??*?OLt.????'d +? }?E?????endstream +endobj +158 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 33 +/LastChar 125 +/Widths 641 0 R +/BaseFont /TUPMAR+NimbusMonL-Regu +/FontDescriptor 156 0 R +>> endobj +156 0 obj << +/Ascent 625 +/CapHeight 557 +/Descent -147 +/FontName /TUPMAR+NimbusMonL-Regu +/ItalicAngle 0 +/StemV 41 +/XHeight 426 +/FontBBox [-12 -237 650 811] +/Flags 4 +/CharSet (/exclam/quotedbl/numbersign/dollar/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/C/D/E/F/H/I/J/L/M/N/O/P/R/S/T/U/W/X/Y/Z/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright) +/FontFile 157 0 R +>> endobj +641 0 obj +[600 600 600 600 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 0 600 600 600 600 0 600 600 600 0 600 600 600 600 600 0 600 600 600 600 0 600 600 600 600 600 600 600 0 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 ] +endobj +148 0 obj << +/Length1 1647 +/Length2 6901 +/Length3 532 +/Length 7764 +/Filter /FlateDecode +>> +stream +x??teTl?6??? ????t#? 0? LHw?4??tJ +HH+-?????A????Y??????????Z3k?}?}???k???AG?G?b T???<???-??-?q??Hh???pW?=&??????A?? +( 0??vAA????6 @?? +9:???zF\\????v?z?????????/??w7 ~O???p' ?? +(h???j=???2<????&t?? ;???9(??????n +?{?%?`?@;?}???????n ???8Bm???;?C ??+??w?v??????{?{??L???? w8?>????_u??l??s?@?0?p?i?C?n?vOs??m@`????e ??`??6?????????e ` ???*?@??6P{W vOs???v??'??to?????'????5??0??/???}N;?}nG?????? ?????`/?????{f8??????]??@l>-?>%???2??O??????-??????F???o???????Z6n?????/0?~?4???? +?{?????P7????wo#?_U?'????R??????? ?)????: ?????????? +??@?+ ???????? +3p????!?????{??t?g??f?????l???:?S7?v?3??&?????T??/?/????GP???1??G Aa??K??D?:k??? /??/???????,?F??????#}? +??~??i? +?!??{??l????q???@/???4?N*?93; ^?8????Yw?z_?{i?????HG`f??D??]m8o??????S{??6?87:?]?:??G4?L]?DK??b\?!|??xY?Fq??_5V?????\???gYr??v?U?y|????0??????.?>???????ho?5e????g??????k??+7?E???E?S?U??9??fa???3f?C{????N??>?1d?'`_?6o????,?????????q?????k/Ca???K???N?7??e?M??[&?a }Ql?Z??"????)?4?G?8?;?Z$V??-?|? .??????-?7??l:?zp??????Z??B???c?_?#?2o{?lsb?d+?????k?OX ???Y?V=7??????i^????????V?I??pu?=0?UK??O???? ?E%?f#?j?r?~N{??S??3M???.Z^??:oY?){?:B{Bx?????N?J? +?????&-?/?$hX?A<z=~t8V??e\?F???SN?]bd???>-???Q7??F???9_Z??*??i???Y??????;???jG??p?????W??_$O??e[~Z?????6???????f9?@z???? +/?????????[??~n2??=B1?`????E?K???xk"\cT?DNM?~ +?????D?????ed? ????h????w?$pm:??R???Yg.??~"Jq?@*??,????~?x??FxfMS=F??1?o|W???????M?Q?:3{???2????Y?????????-??bZ?K???TL???C'Xs?o*?/?/e??k?=Z???} ????(??E?}I +?? <?FiG>C?>???U???.{?mF??$5%2???j?B?1?g??m[?e?F"I-ED?17??&(?_&@?S3???]-?r?z7m???M?\?):?o??c?HmR???? ?ha]?5??/\?????>T?k`+?;???b????K??Q?C????c>??????+?&???j???v???{f??J???0% Y???d??? +?gKJOv?HJ)?????}n?????^?k4?T??????D1?Q"?!q????W?K???G?zk???o?-m????svM?P?Q?V??m?5????v??O? ,??D??O????????:??U??3#????p>?(?=^O??????6?u?uc.???@?r?e?gH?I!w?R??~j?JY3`?a??h???&j?????????? ?`????d?Tz?????? ??b?gt[W??K?{0?Y?S??O?K`?t?+}?%?????#,??d!?(?a&???????jW? ?}nmj&??y?8[??1D2??? l?`h??:J?`???????f?????;?~?$??j??.?T[M?F??mDi????o?w?PdO?R?>??s~|(????t?H??%[J?????{*h?R??D??>?????%:'?<|!w[?4???%?\??7V?J??_e????7}?m??????%*?????????H???r?wL?V?q?????z;???~z ???J??????]K_?\BY +huT?*O +????Ni???4??;D???0??????i/=??a\?^p????`?e????????rJ?F???/?5??(1o?B{?? ? +??Hp!y??o????!gv9y0_w8C?K???G?? ?P?I^???? ?gF\-?V?|??4???x?????G??;?????W??m???L????V????&? ?o??Vl4?????OI+??D>}g\???????????S???m?A ?T?c]?oIt?u??N?:q?X?fn?LF???N`??hq???4?}??`?????2?TD?:?o:^fb?9w??F???vN?/j?o?K???D^??f??1?f?{a??O??????O??&?:??3???QN?l_?:d?_(????,?f?;?X?3???`?Hzl,z???w?~?????T?z?"????E?C??[-??O? T?i?|??$82? w?a?)??i?*!O???S2?lx??`?b?%?IW+?C?lm?M0d>p0?????HBlw?+?~??wh??,u??G#? g????eL??,???#??l????%?.????g_V????????Q???o??_?l??/?98?$???L??m'????y?B????????^no?[????RU????????(???^w??qX?=????{4?y???v?[???g?????U?~?|"?d???E???Rt?????}?]??u.N????o????=???`^?+Vo????X???3?G??o:p???? py_h?~???!*u???%?????????F?????? ??????]??:9d??Y?>?EJ?G{/???O?7??q?6??s? ??Dm[??? +??;??{N)Kr?D??????M?$F??,e???C]i$????/?z??????s????W????A??_O?f????pK? ?~?? ????w?R??T???`?3?????(??]-???tA*?PZ????PM?ll??$?.??S$??M?`?'???4C?F???!zG?????N???]????2"??????? ??#q?:?x?}???*?q7??&???%G&? n????v!-}?Q??????g???w????E?OX?h??0??x>?2??i?0e?u?????Y???'1X?????/???c??P??; ?;K&??]bN?BI?:`C?E????' +?L???H??i????7???????5??=??L1?4??bj??kH?3???#i?4?kUP?yZ?93??????C$MS??E?G?????'????h?C?l?.????Vendstream +endobj +149 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 99 +/LastChar 119 +/Widths 642 0 R +/BaseFont /WPJZOO+NimbusRomNo9L-ReguItal +/FontDescriptor 147 0 R +>> endobj +147 0 obj << +/Ascent 669 +/CapHeight 669 +/Descent -193 +/FontName /WPJZOO+NimbusRomNo9L-ReguItal +/ItalicAngle -15.5 +/StemV 78 +/XHeight 441 +/FontBBox [-169 -270 1010 924] +/Flags 4 +/CharSet (/c/d/e/f/g/h/i/l/n/o/r/s/t/w) +/FontFile 148 0 R +>> endobj +642 0 obj +[444 500 444 278 500 500 278 0 0 278 0 500 500 0 0 389 389 278 0 0 667 ] +endobj +115 0 obj << +/Length1 1626 +/Length2 10204 +/Length3 532 +/Length 11061 +/Filter /FlateDecode +>> +stream +x??weP??-?Npk???????@c?4??? ?,??w????5?wg?N?7??????uUW?????{?s???R]?U?l ?;CX9?8?? 'KwM??*XP??=?x?????J?- ???(?Zd?V..??? +-@??????t4???Y?i?+`?????Lw??3????'???t??A?_'j??`r??? +U? ??:y?3?????a????????@F? +? +???? +?l +??5w?7,Iw???hzKz[]?r?\?nN w????;?????6r?r????????7!7?[???? +L?q?r?@oU?e???bg???;?? +??EZ??+7???{#$???_???????7?7???o???????O&?#?l??km? ??o?????Vnno?}???????;z?P??V?????>C?? +???????p)??.. ?w}???4???0!???g???eG?iw??#}W:???4????{????y7??? ???^??????!???????i?3?D???=c0?ga?;?;?@???$?v?(?oEG?t???????.??wH?s??i?=?????]sI? +u*? ???1p???????<%g?`???-??x??A?&1}U?????i??B?9 ????SJ??Aok~sK>?#"?N??dW?Oq o?x?B??p??E????y???3Y??3?? +?#???????%J?g ??Al?.v?.?d?i??3:h??-,??4??]1???????c?/?6H?k?????q?I????7X?A??N?'??IE??@??8_?(/?????G????Z!???'?I,?????J??]?????3??.G??i?|??z-????P?R??#?)? ????_???R9?` o?2w1??4??1???????{??+0??)??d???"??<1? + C&{?_i?,JeR??B??:???x?x?Q:;??0M???????Qz?????O? V?????X?????Z?B??Z?MT +????J?? +?w??`???????Z60?9 +?BG?W?????8!?????$k??5-??v???*zb?H8?????/,??'???fO~???????!hl??W??.>??B?1??S?@??`??2?K7?{n??^?Q??&guF????????T? ???????Pf??S?b?Z?O?sd +??s???,?}MBR(3'm?u5??3?&+$k???4?????}?L ???tVC[MDh????W?????/?q????1 +]????l + ????w!?W??b >?2?????l?????n??y????[#zT??L?????S??Y?? ?????n?C???O?s??207+)a?u"dF :?????pP??\c???x +???{??C?_??:d?V?Gk???{?/?0??a???{:]?N???{???=??vqw?~v??>a?[?3)???nf? ?C?????!?8???}??u??l??T?@?? +v????(*.??C??????S?F2s3????MV?????4*??gD??w?=??D?????L???Q??G? ??mcn???i???8????o'?YV!?0t???hw???u?U?v}]i?=?1?\A?1T?}??cWGcK?j?1\?j????*?*?F?e?b????I??V???>???@????k?{???v?)?%???????? +??5?r*?X?SRi??^???o??)?{?*5=? x?X?\??????PG??S??|?K?;?]???cSU?0[;?e???E[?j???????5?t\a6I(??D????_??nqdm??O>eci>l??P?$??p???Ajn?niWm??e???E??????v??????[???3??????,%?m????Z?vp?u????w%^?(???M??7 o??[ ;26[?n????H?? +?????t?L?Y?B ???????}??*!?Z+??????h~BvxLWhm???????~h#O:?d???J??#?_t?i????V?3????:?????? o???!?v???|????????o??????????R@???`?`?????6o???;?g%0???x????????zZ??X??rv??{?h??`P????aG?BB(?T^`nF??L??F??a?????.}????t1+????o??????i??0??z??(?h{??&?|w??i??#?U6Z?E?fj?f??V?:?*??{A??=?qT?G?Om??V????bP.??????y????? ? ??.;??? ????E??Q6gk?%~%%?????? ???q??S?"??x????1Rvj?d??????F?3?k??s?H&/b& ?Y???^U?? +1??????D~]}???5????E?7??$????????MF?'?.v???b???U-R?}???t???G??x? }??Nz?!c?qxa27D??z?^z??&q??7b??????z?m!-???n????6M?6?"Bu??*?Gy~?sA?:?+?s?FY?????}?????]????IK??????y??k?3?P??d?cO????V?*_?f?Gt0???????b??Pn???? x?*|G???????? ???q??/? +?uz?:!?4{K??p?!X??J ]?P?@??SU#????"u???)?u?? +V?i? +?@???.?????U?B?A*??{?2c???"?n???DfRm???]?efO???/??4?W:?{U?[??n?2k??[ja}??%? +???<s{?????R= ?G??v??\??????????n?%?5O?]l?(??% ??i????R??g,NJ]X(!?1h")?B ?=????O??X>?l??????YB?a??y??????C| Le?(?&??`?M?Ug??1(?8mv5?? ??cw,????oJ? ??L????ax???0????????q????V[Z?????X;m???????????"?V"?i?D}@^~k8??%??1????V(?????;??g?}b 70??<?? +2??&]}?Z??g4?M?>_s|?e????nT????GU?????????????l???@n???Q:"Q?{?g????Y/\|?j!?;?L)3??sS???%? +?v??60y#+???NT?n????}?????yr#0`?5' ??1)????$Tm9T?e?,?% ?U???{?] +8????h?{ }??OB\?????gSR..?{????u +'?m? [???T???$B??z??]d?wa:?i?r\1?|???l???H???=Od? c??U????????Fd?W?]????????b?mZe???? UM?,?6????z?????+????_??{??3\???f>??????v????7???j??s?*?j??s?Y?3?pga{YZX?fn?? TyJ73???q?O?@???-~?}??.K????@??c?<-=::+9?v ?????0????;????"??????????*1?9?{??~q?P??!?\tR?uO?*g?]m?X???w&???t?f1?x?z?????8?]F/? ?1???r????H?;?e"B)?AE?A???x?ye????>????C?[?Z?cK?q?)z9u????0D?I? S???????s5??;???IC?5t?l?jX??t0???.0????2*x??_??|#?g??k???*? ?X?t6???>????u?vlj?7?|e]R?4k??*??`U?A ?J?Y,?D[2H?n?}:???V??? G?????8??Q? +????`?"??$?-?.K?;H?,??l{?????i??3?a ??C??!?Q:?"4`k,??P????\d>??????;?T?.{?Wd?e??j?0? ?6? +#WW1???6\??? e???P???8 ???/C?m???????w/?]?w2??(???????C?'??!?!? >?y?|??PY+??i???F??]a?r +?J??n???{?&????????kVV$I?H?t???T=??x? ??s?pS?y?A?I????-?t.3??l?????B?eY??i?TC&R??????+]A?`????o??{?Yj??5??y>???? +.|D?? HA;?+U2?????E<d??? ??s?!?,?} ? r??r-y??O??? ?????"?A??h??I??b????^?j??M}??Qi 2?I????-'_?Yt???@\?S?'(t9E>(??>??*??`d?1??$pL?x?; j?z????f????1e?T(@? p?Y?yr%\?6???P;d?4???? +Gf??7+?? +???V -V3?????l????)?q?u???(?W???U)???p? ?w????PF_????.??67?cS??$[??N????a??1No*?M=???:?2??\???*u?x#?w?????|Y"{???)p? +???????.?????/?(??6??v????wu???Q?m?(DY7[??a?K???&?'?L?.? +?s????A?#.???)3Bd ?g?????\&"?????h?r???8?yefV?!p??)E???????Ja??`s????????.??7Y??^V?[C?>?g?, ?=?6n????>Kb4t=5???=N?7>??:1??_?8???>???ng????????N?S?yq?? .???? +5?4??*@?r?8??fP???;F???????????o????I?.??u???nL.?????C????E?*gg)Rgw?oH?f????2k3????d]i?!ae????#T?m +?zF???/.z?YZ??9? +?????oe?rQ>????5???}L?O???m?(B??T????? +?]?%???91????k?????????????%??????6??? +?W?????']{?nvv ??O??????nx?PN???rN?6? Xu>????? :?,:_ +`%???]!???]0 \?^?? ???x?HQ????uv ??Ke??U?QM? ??0?lz???w>???? +?????})??O;?S?I ?9 6???,?>???im?;??1}??????vC????J?[?QEs??G???w>??w??2?1`?6? +????d?$j???????? +}$?O?c??3Y<8?`?d?z???+D&?+_?V? Vf5@????mg15?)?d@??a?s??{??Y?@ ??W??F??k5k ?LpD??%?(I??I?S????]~?.?eL^?T?[?*zr??hFc??]P???s?H??-5??c??.]??????'k?y?; +??+? q??????9\fW*U4???Y.?A?H?z@?c???????i?W???.l?~_~$d?:s>mk'?PR?g???r?$H].'??0??6_?:?? +? ?]?u??F?? ???#??i? +?L?-??????????i?1??@?X`??Q ???D,?r];?=?V?f?2?S)>???5??])??<^?????-R.~????S????-?n-?wX?l2?$??N?rMr_?p>??.?^|"S[B??()?Rv ????#X???wy??????8??=R;??? +??*?d??????iA?w??}v?????>H????ssaBa??E???????{??'?'??8?}q?l???0?U?,?('?&???[???KK`?????0?c?DL W????'4(? ?j?ofc?#????????}"&0WQ????????????(!?Q????zG1??G????{??? +?$??~}?W,??;?`?N?at????\??? A?"???M??????????????7xw~???y'g?^?q????hxL+Xj???'B???2]?p&??????~??~?X?j}UG?JT?????H??????~?J????J ?????*/B/h???H?WA??Kt?UVo?????U?0????@?Pj&??~????? ?faR???^?????5??F*?????t?d??j???d??Ox?4L?_2?"?30KO?????D?????&8?f?3?F*??t?^|-W ????J??????'??????C??>* +?DA ???????8?In?3?p?!?A???%:d????`D +???v????$lH??Ny?????????M?????3ZU*rh??Q|?wEn? +?d?????????K?]?A}?H??q?aju??2?s"D?kM????q?%c!-a??t $?R??\4??%?BX?0?w??Z?f???:?p???w8L?6G?H?,?FHU$?j??@?q?????+?&U>???}{??-X????=VY??`g?????0?4|??T^?J??? +a???5h??|=???Xl{!?8u?6?? +lL?? ????N*?????v?7?V?BC )?3???[??1? =[m???~?/[??? ?|w`???R?PO?'o????L????2??o=?H??????2??d?????N???_?j?#b???] ??a?gt[??J?!I?t????X??]???_?T-Z????G73?a???:n??? ?>??Sx??^??>????m?pb +xh????;dv?m:6???;T3j?' ?????#?|?>?^????????\q?????/Z?AG?Rc??U"^Sw?????P?:??? IA??2?n?(5?`J??\Y?_C??????W^bw?Y?,?'Tk)?9U??? +?b?F^??P???9????;? ttg?nQ ????Z?6??%????G????6 6??o?tRB???@????!2n???&?`?P????k??"??w??m??????SmXr{!?u(v1?bD??!?M~5Rw?SD??"??? +2?????nxV??-??~???ot?FW~??Ky?b??? c$??m?????o???P4???Z???,Ei??????????|g?P????V?????kR???6?????h?M@?H"Y?e??U1??????`> endobj +114 0 obj << +/Ascent 690 +/CapHeight 690 +/Descent -209 +/FontName /GMEBOS+NimbusRomNo9L-Medi +/ItalicAngle 0 +/StemV 140 +/XHeight 461 +/FontBBox [-168 -341 1000 960] +/Flags 4 +/CharSet (/fi/period/one/two/three/four/five/eight/A/H/I/L/R/W/a/b/c/d/e/f/g/i/l/m/n/o/r/s/t/u/w) +/FontFile 115 0 R +>> endobj +643 0 obj +[556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 250 0 0 500 500 500 500 500 0 0 500 0 0 0 0 0 0 0 0 722 0 0 0 0 0 0 778 389 0 0 667 0 0 0 0 0 722 0 0 0 0 1000 0 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 0 278 0 0 278 833 556 500 0 0 444 389 333 556 0 722 ] +endobj +106 0 obj << +/Length1 1608 +/Length2 9985 +/Length3 532 +/Length 10828 +/Filter /FlateDecode +>> +stream +x??weT???.????%?Kpw ?i?w?????.??]?C????|g??Y??_3??]?????]U???????m?O +??BF6@1kzf&n?????#HY?Z?^????nd?''?b?w0???wr??F?!??g3<9??????????JUI?????_??!?z?w??L??N at K[+???;??x?2p0??,??/? +??r?*q9U?8?h?o Pp4?43???A at j???=?? ????????@ ?XB ?>d 44{?t1??q?l??Vf ??3? 0???vx??? +????????w???_?l?m?#??}?` +6 ??????=?????x:??;?? +2{wl??#?l ?????????of +8]??2??@????????l?????2?6?:?=?D??????c?????????mm-]??m?W?r0s-??????4tx?mbf +??gP$??m?L??9???????ATf?????????+?h ?(g???@??S???'??A????y?w??]??r???????b???r?V??? ?~??2??w???oef???D?=P???????{??M??`b`??? $f?4R0s04?[???/??????????_m?3?????bjfha????\???Fg?.?_??E??T?i?~??????????;???C????0??m\???,z&??????b???o??????????? @??h&??J????V???6?1?3'???F??????nCG{?wE?:??%?s????. at C??C?????j???1??.f??@??:??\?J?N???M?2???@?? ????#??])?_C]X??????OR??\?5?6?_~?:EH)????gs2?_???~m?)*?>CN??????Q??:??`???"{&?Fa??C??;:??;???????????????#?q?D???????Z?aP??W???J???t??????WWj??~\l???s?x????r?H5?J nZ???????d8???H?a^??U!???V??0{cC? ?Q?????? +?????BZ?x??[8???????9y?^???"??Z???? ??????)?????(???Y?kl??%??N???w??7?H?K????I????!=?????? ?????6? *??)9VBZ.???e?0?_??J???8?pI?!H??????????&EQ??w`ay?}??????K??? ????n2??yd?????O?f???w56 +??? ? ????i?/?p?L?2`?2:?[??3t?,?pX????l???M}B?5?K??:???a??a?? +P??H?=#??*m1?? +?????????????Q????2'?I?? +?=?????g?&C`??????C/???$???R????dYW???~q???W??r.6???w??u?8i?g??-????fbr'1?"}?u1? +?~ ?x$?K??r$?B?u?zg?Y?t????4?$?????a ????!q?%>?K?9vU??????l*?Y?N?5x?-???E??U?[Y?|9????"ls +f/???m? ub?:???|????F??7?\u????xZ= J?hV?"5V??j? ??j? ?=ZL???????L?q? ???'d?6??;?????4?????;?u?Hr??????q????b?7\?)??0???E~?1P???i?W? +XN ???+#??}k?B?U?????G???ueu?PEq?&j??I u2??? ?e??z??^??? +?3??-??R???-?`N? +W?j?%A????????EA?=???5??????1?B?????? +??1+????J??D??#S????)??Ff? +???? +??I?'A?B"*c??v ????????j?G????\?I??},P????U>???dvP??xp%?M{ L??B????'Jzn?6I L*n?????,q\????o|????/??&b?&?? +5?$???v????? ??)??fM??u!$???ZyZreyA4?;!PB?-Gk?"????(C??KL??{????L??????sr??????X?c?.??n??????a,?1>s3.??:!?4p@?+?)??;?x??|?"r ?[????,h?O=D?q?5$*_?T[.?N??????7?"?O?k? ???????????K?-? ??88I??G?@??sI??p???g +?H???}S?X ?H[?-?????\Z\?d?@ +CG???r???m6?)???????J???&5?n!X_=??s?Gj??O????T????PD????0x????W4?(?? T?O??? ?/?`??2Ch???? yQ?| sB?[0;?ltE????4+?_?A?!?`?9??i +/N?x??S??=??? ??dG[???q`?3??/???DL?(*x??S??'???3???T??7??_??f????????~?L#l??y????,??J*?B?^`??~????? +iJ?h?qcW??F?#l +??A?:??2??N;??yP?? V???M4ue??????$?v?0??xu?=???????C??????????C3u.?~W +}??????c?L?zOv-E?NB???-???E??C???SA???B?y????od????+)3`k?';??gpn?O'??y?????e?_????N??W%?i?|E?^b?????????M???????RS?{?M???????<]I?,.???????q??M?<|???T+R"[??l?Wz???^???NM??cE???? "<>?????=???j?@m?????W?v??u???h3l&????y6?3??\???}????i??b?X??#??(GI?t????6aia,?b?!?? +??????????????1?^?4????:??C{F???Z????}A??????EfT,?2????d/?j??ue??E?|???J-m?'L???'???A???w?U?????BC??$W|??T? ?4?mi?B!?????"^??{?!|vs?%??%c?K=Q?'?n??:?C??y??[?F??????? +???BJ?!????4?m?????(MO??/??&wMGs? +?\???l?$w{?p??y?q?)?w??I?uL? ????:???????pR???????~?v?4?P??{????q??? +]?????Usi??+?[h?d?KZ{?? N?????V??P???s?(??AM?^='?_???3?n??$?e??yqlf??t?2G??,B?b???d?  ??m??+H?y}VcQ??<\?9 B4??u?f!????p???W??Q????2$???t3x?d?/:n???ds +????1qj??/X??;S?wX????U.???F?{p???S-CIk???W??????{????^evP6??6???e5?*?`????e?mV?4????!???$l????????3???R?Y+?h???i??L?k??n???F?Z3???T????????2?r?e?+&????$???O?_M??{?? +?D+?? #??????T?j?????[\[??M{?-z?????#??9I?]??? +h?>??E?4J??'???5[=??OkY?? +?@?ffC??z??s[?v?e?T?quD?H\0???b?1~???-?????{n??)??K +h?3????E~e??J?????'??BbGV??|.&??/6????? ?????v?pT?W9dv(???y???3=^?/?^?[2Y??K=P??EVfxI??~+?T]?mFp????kL?j?1?N5?J2Hn2?? rn{u????r??eq??z??l!????_?c?T'[??IV???????e?bj???2?G< +h&X +mA.????)?3??^?<^?G?~??bq????'?)?Q:???? +???09???^??????U??c??s&"(???r=9?@^?< +?O???(i??1u?N?\-?q{As0?:?\Kh?m'???~????F???{$??0?:????2??-y$Y??????????h%]'???=???T??_???D???????? +?Kf???9?"?dA?'?_,??p??"?????\6`?Z(+??V?PTx??%?????d?#???h^?~%?z?:????2??? ?? $~???^???>C??)?-?_?/?aQ+qZ???`????b???L??Y]?I??????AV?t??X?O??]?Qo? ??j? `???????9?????n7?@ +??}`-]?mbo ?O??r??\k?i?*?[!??oG??Xj??g???????V/ +???( ????@???0RG????I`?W}?????^-?0?r6??) +]?{8?S??8a?K@(-g?E????u?9?????Cj??i2N??^*Lf? +N7df?4!????D~l???_???qZ +??_?4??X???{?Q?????b??x?+?v??J?8??4? ???}????"????-\?h"??)??+]?? ???? +?7??K97?N?e3 +?8?Y????'?1?iKSWM ??b???\?????R???L???????{J?c???o??????0??#?????V?????7p???> 8? +8????)?@(m?|??E??r?RaE????RYJ?{?l??7;v 55?0 ?X??0on?Fl +w???Pa?{??&j???? ?j?I?*???N +??2bn@??|8R?0???p?Ws!???B`?????WX????Z|??&?=9?{)??????K ??8?b9F??]?{??4?$_%?`?< ;???Fu?p0*!!zbl?UT\??=r,?#??? +?|??~???|?T ?x1?,H???k?????A?0?? I??^1H?;??h ???k?????E????b??EU ?5>???&jP??t??SI;`?:s?*?BPQTs?? ??,>; ??y???????|?G?????X;"d +????(???n#:uZ?[?????m +?3?K~Ln????????f?V*???g +ok?=?OPH??Y(?c?B;cJ5(d?[????QlA???F??+? ;???x ??P???5?!???\/{??cc????~'|? ?zD?6h?"??x?????7??6?"?# !??0Z~Y?? ?w?~??W???S(c?)?Vj?e???????4???qk????4??F!?''a??_|Sr???-??e.?? +?????S???????c??(KkO|]s~;??G:??U=??????Gf?a9?b????0G]?p??.??E?g?Q?`?[???,????]Pf????T??>?5?:g]?T??7~???I??Elx??}???hn??&I]o\???C??}J??i???n7? cX?b??%f????= +d???t?&?(@?46(e?%/?u6?c?Ig???0?????N??WF.\1??????/??B?QQE"A?[E??&0???t;??H??"?aC???91??@yI?,?:dIK???????L?? S,?d??@??MX*?Fm?? ???2?yb??????t?%??d8?^??? +T?e???? ?????????w??w???? +?u?????+????U`???h??\v?ut"x??????;v?/8??-?W?? ? +)?y???{*?P?]??[q??D? +?????X????U7?k~@)?????J???,????"?P?????Y;!?T??Z??n???????Y??T 4?p?/a~?`?~????^?m?d0'S???s??? ??Ww??t?Cb?????_?????7??VA???y?eY??Z?'?u9-(? K?K?B^C&?J?a? ???????{\???T????}3????#?JZ?BJ?l.??mp;1P?;??N???p????^??C?|???F?L?????????n?'i?@x?7??F?j1_3U9d?????%??w?????,??9????s????D?????m}:'???Z?0e???????!?uWe????m w?(?K???????,w?p?^??G??????e?????????s??WY?xu>3??@?????q??O??=x????[????n?Q?s?0H??+???:?????1R??-?~?@JZ???r???o?? +????M??/sxd??l??????]???c?S??F??*?? +?8J????????QH??B???'??H?? ?F?=a?)? ?????8?4????????????B??j??t+????o?4 +????????v;/???s ???h?????*?a???sn??????$Lc? fh???3?~??E{?%&???\?\^????d??-5???)????W2??0??;,UP-?`?S??<????e5s? ?$????V?Z+"?D???$D???)? ?JH? ??\?7s??q?Y?h?{6R?XG?????<Gg`??=?\????? ????XD???????-??5/R?a6&#yIc +?cwd???i??W??q??]? +?qT??(?_??8???K7M(?oi?&???k????k?I7????????Y??s?,?????(?dk????U?3??{M? +?G???#1????TB??o ?T8? ??????x??J?[E.? ???z?B[??Zo8a???[?5?`??!w?}????Y?? ?68?? ?)?V#nK?????@S???|???b???f?a?X?6??&????s?Q?? "1??aTY?&cQ8????^????????N??}?????Uz?`?A7L??.??Y???? +???A+?C??u?c???I??;???#)?J???| ?\5>???vU?+?UW=????|?!=?o???b$?????'?*:?????????^?C??t?el?'u??)~??????M???nJ???3?+????k?#?????????>+??v>f?????j?????m?>???^$?)$|h?N?????O?f????8????J5?f?2?j`?E?3 +?O?t??s?F6XF?g????UM,?J???&y +?(>??-? I?s@???U?D?_??Q5uQa??X?F???????,f?I?^r?I?u?m?1??i? 3:?tE?p????1?+2?*?????"3k?1al??D??????l?Q?^???OP]??Q?????N???R?M?C??????xKY?G?7??b???21?v +?)??Dt\???L??.#XxH?=_N?B*Ga??@b? qk??9???&ORD ????4?U`_r: ?7N0???=?q+?????w +5E?g~a4??0??th??8M????q?{????i@]?b3?%\????FO/???3?7???????? ?0nhzj???????f?im???]?]L?:G?L8]?????? +??qS&H?%??xRc???nB??Z?????c]?n%??O?p0?E??]]?22?q?S?????&)o???P]?~?=c????,3?????x?+?I????:?D]V??l9??s?|?0?A?dYk???rhp?A?W??8?"?%Mz?pD?6??#;'3?w???a?w????g???O?p?2?S??5??x?????RuN????y??c???c[?B????f`?mb?e?>????'ZU?TL~??gP +y?7?q???????^?)???o:???:????{?9jd??A?5?5V?I?J?????sc??2??o?y?W 2a1??n>?c.?G??,?wiT=d?_~???????@}{+}{ ????endstream +endobj +107 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 2 +/LastChar 121 +/Widths 644 0 R +/BaseFont /BDKNUS+NimbusSanL-Bold +/FontDescriptor 105 0 R +>> endobj +105 0 obj << +/Ascent 722 +/CapHeight 722 +/Descent -217 +/FontName /BDKNUS+NimbusSanL-Bold +/ItalicAngle 0 +/StemV 141 +/XHeight 532 +/FontBBox [-173 -307 1003 949] +/Flags 4 +/CharSet (/fi/fl/period/one/two/three/four/five/six/seven/eight/nine/A/C/D/H/I/L/M/N/P/R/S/T/V/W/underscore/a/b/c/d/e/f/g/h/i/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 106 0 R +>> endobj +644 0 obj +[611 611 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 0 556 556 556 556 556 556 556 556 556 0 0 0 0 0 0 0 722 0 722 722 0 0 0 722 278 0 0 611 833 722 0 667 0 722 667 611 0 667 944 0 0 0 0 0 0 0 556 0 556 611 556 611 556 333 611 611 278 0 556 278 889 611 611 611 611 389 556 333 611 556 778 556 556 ] +endobj +102 0 obj << +/Length1 1166 +/Length2 6485 +/Length3 544 +/Length 7294 +/Filter /FlateDecode +>> +stream +x??yU\??%?48 + +???;??C?h???=A?CpM????{pBpB +?!???=s???4o???????v????V=+??S9[?5DC?????ZPk??`????p????C?????????a?`?=????#? H$*.?w? ??G?tP?/@?? ???{Hn???!?z??:C!?zw???.????????>???a?g???1??>111???_@??????g???J?*q????\;??-?{\??*???!?1^w;^ ??oT f?w?M???[3E(bs?????9??^0???Aa??d?? +4?A?< j???|??;fA?@? 1???x?8???q?????a?~?pW????????????? ????????l?6H?5????f?C???k???7? ? ?@??????-???w??+?)?*>?????????S???x?E???r?(&$?O?i??Du?????7???s?{???p??&??s??_ ???@[?$?w?????Z????j??P?pv?C????????V????t? ???????D#???????!??P9????d??+C?!?:P????v?Ke???C????K?? ???w??8? ???g???????n ???"?] F??+???@ ????????ko?o????-??m$B???]???z?l}?68??`??uF??E???r*??;M?Q?u??2C?DG +O?U??r?o??&% #ES??9????'8??????I??J{???3???????UZa??i8?"???tg?M?????W{w?S???????s??8??p?"??yD?zg????)~??Ye;???|?m"?}????X?}???u??i???e&A???alP??qZYD;?c~Pz??l????X??BJ?@?/?@??^???_????E?j????+s_??????e?U?o#?~?&g?s?ev V???b!?Z???z.K|??F???r_|ZSXF??G?????>]??Atqcj?`-/?)??a??2??????#??4?p???????d????o?????f??H'?i?/?at???C7???A/?????i,?\???~??3js????????E???j'???? ??????[?Y_^?KkasJ? ?h5@??'?????#~?????@?Z"E^??wY?)??????????J?~?l)???????Oo????6?8?U??*F#?h#??c?I8P? |W?]7??1,aq_f? +?7Aw8iT?o?H?V?#ng??T-N?!W?,B*???x?[C/v?$?g ????????[???Rl_?u??N_.e??H??C?????ik?S??8S??????T??ntP??t)_<+?*???sK 5?PZ?{??~\??^?r 8{???y?Eh????_??????q???Q6??o??;???|?W?1?z?o\???Vb? 6i?????`7'?}??[*5?????{?f^ +A6??I&an??Q? ??W??? +'?????v?j?\s?{,????j?'2i?^o??r?V#gh?X6:|I?gx at h?-????????u??!?C?? mV +?\M?/??M9?^?0???Y|*EC-a3?9?a??K???hV?p??K???JNO?GLz?z;?v?]?FQ????????????Y]?/gQ??e?H?$0o?'U5?6?b ????bQ?0??(_bEP ??X??|j 5P"????\~;zay#?e}?[? +??)fI?$???";?)ALB??O??m$?? ?Sw????*?E?0??'?4?p??5???:???l??5?[????a??" ????JZ?6??o?????X??85??+??????n???S"?????kQ?x?????S?aQ???u??!t???5???,O`??ro1Vs?,??y??/???{???Wz>-?K?,??Z?~hh?&?,!? ??P?????D^???'6%}?????c>!v?m^?:?Ij??????) vx?y?#?("O?:]U?|????:??%?d`i??8????0????Y> ?b???V?F???D?? ????H?a??'?? o?5dv>BD???4s?:?????10???M?L:????!?zlK'aX?g"3?c????NI:b????LdQ?0M????m????t?z????w?%"?7?!n??!\?????Aeb1????J-?????)G{?'?\?b??Uq??Ya?r?P_??#?Z???3?gt??9?[??? ????-??CF??yO??h????Y3D??????}?@?D??? +&p???E?G,??H.??;u??????s??jf?????d|W??7?\?Ge?8?1??{.?|d?Ug? +????&???&??????? +???????{3vS????i??o?g???i?@?c!2Z??a? ?W0?a?d3?v???? +??%?????4G!???&?F??j?o4?t???O???&? ?????%???5Ci?rE?YDy??5\B!??lH?T?"?+)?v??P.?2???:|+S?%~?BzD????????O?i/?/?????? uz?N?_l??x?b??5??;?? +q`???s???1??:cm?^,A???c?q7??W?'N?Za?????Ab???N?qE?OZ%?????_?;??????G?P"L??#v?>??b`???hje??_??X8??????H?X?cF????_?g?%???\28%s??a???????v??G*?a??~P?y?*_>??M?%?????IAq??+4tTd|?K?]????n??;?WU????????k??1???9?^???hDe???FelcK???o^N?\(??v+2?56 ?jz??????? + ??zm? +?p?%'?w=Q4???????d????d||A???Q?u???S`??????\?&F??'`:?????Z$\|>??? +????????:%???[?r< +?3V*P?%r$It??????|N???|????t?Tk;???Ky???????UeW"t?????:R??I?w??z???5zd?t????vDwBE??-'?i:*j??Oy.+??* +??#9?!F?+??#G???+?????^?????F$????e????f?p,??pF =?M2??????c,??0?LL??3$A??dD?????"y_??2S?/??Q?&GE?QV???W????B!??;?????xv??d??????d?Tj?$?2,?^sF?3???G?IX"???i5?????R??y??hzI#,`hw]8?3w??????Ffd???9"?.F? U!???+?VTI??g????i??O??o??Q`????HI_|???sraf?, ????y?\?'1\??k{???tuu7?? ???DW??QZ??`??a????:?????>?G"???}*?#?G ?? +Y??D?`mU&???c?A??&?fW?Kms?d?7Sr?z|???A??C?????w?'V??>-????7!???7O?0???.+?? ~???????=?Px +?????=,M?????hEQM^???L'?`-???4$?b?;?kp??????l??<_????U???8%#?X +???????z=????=????)A6??e7 ??^?????6d?Nr??:?P)"?V??_[D?8%`&<>T?}??j???fn???}?T?;W?25?3??w??zg?T3?F???s?p"?????D n????????rF?G ?Pm?7??$??`;}h????(? %??p??r?~=vX??r?A +?F?)??????+#/??K?t?z????;{?* S????&?H??z=??a??U\@,J????J??b?\?mX????F G??\????LNF?????[dh?7A??i?+c???Za?(O?????;?/???G??]?[???dWy?????E}S??6D?8Pc????t[??????????w? +Z??????-??Gw??>6???\y?:?????????H???=????.J)?"hi??F?[??}??euU???H????Is]?tX?r?~??O@}}?i~W^???)??(?5??%?????j?i?MGNP?%i??? ?? +E???K;?l???$?q??;?1??M? } ?#\%k"r4u-??? ?? ????m??Oki??/???C????JGY8D(G??\????Z??lk?????????lM??????)K??l.d}?|??)tj????]$XPQ??A\???4T?v?h,N?`,?y?D??~?????0??O?:294K'B????dD{/?????6?r????}?????8???3kq9?:X9Pq ???a??FX?0?E:q R???????????}????P????:YnA????Ja??+1Yx_w?? #?M&'?O? ???A???cI?q?v??%????????3n ? + ;?M?????"1p-??E????0&'?<(g????j?k??:?`???N??5F???[![?IE?????????!???G=??#9%? ^c?y7??n?????,3g:?d????|??}C?????????c?c?n?>??u??O?u?w>?.?Y??????,???b??+p??cA?}!5??.>?7uIElivJs?(i;??6? +)?u??J??Ei??JGL?2y???b?O??^^????/?W??j??g?u#?2?;a??^???q?[?w?A?oJv??????? ??????????? +mv)????j?|??!????Yqt`?X??Y?IuI?fzF???f??????|;z?????????(z*lZ?l?)??jN?IHGN??r ???X?fF?o?z?i????n?2m?? ?O??4????Q??D?m?????? +Z3?#?N?Y?y?t???c0?[_?N+}?;"?????23/?fYd?%??c_n ???_g?N?N%?W???&T?C@??GObL??C\q?zd??H??0Y??H???N??4? ?? +@?/?&?|?4?~?P??/?=??T?/?M??_A?f????? ?~? ?'??1?dz???V??G?????S9Ad?> endobj +101 0 obj << +/Ascent 712 +/CapHeight 712 +/Descent -213 +/FontName /XDADQD+NimbusSanL-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 523 +/FontBBox [-174 -285 1001 953] +/Flags 4 +/CharSet (/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/question/T/Y/a/b/c/d/e/g/h/i/j/l/m/n/o/p/q/r/s/t/u/v/w/x/y) +/FontFile 102 0 R +>> endobj +645 0 obj +[333 333 0 0 278 333 278 278 556 556 556 556 556 556 556 556 556 556 0 0 0 0 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 611 0 0 0 0 667 0 0 0 0 0 0 0 556 556 500 556 556 0 556 556 222 222 0 222 833 556 556 556 556 333 500 278 556 500 722 500 500 ] +endobj +99 0 obj << +/Length1 1630 +/Length2 18284 +/Length3 532 +/Length 19207 +/Filter /FlateDecode +>> +stream +x???ctem?&?v??v?b?6vl?6+???b;??b?????????8_????c????k????{,rbezA;#????3=3@?????I??F??[?^ h??+g?#'v:[???:y?@????`????#??{8Z??;?T???ii??S?? ???h?z:Y??(??????m???!????@??9`ja +?+hJ?????T?@[???5@????? ca ?uRL???>??lM,?)???/????d4???t7?????m,????,?f????{?l??5?v1?'??rS?%d?h??????/??????????3?oT???ln??Ol'??j???_K;c?J???/?_?????????O,# ????????o??`???J???????3?8? M??NNa?b???????Tohoo??/o?Y??,????? p?,c;??mfa ????H??????-7q??:W???D???P?M??????`4?c??s?@??2??? +????B????????????? +-?bm-gh?w??c???-?????Y4?????C k?????V?;?????????????????B '1 w??????9????o??%W?5:Z[??r?????????N????????????? +??????D?EUUh?7 ?_? +?Y???on?Q???????}??i?O8?z=?2?Ei\???<??=w'#???8?4?0T,?Q&_?8?????P?M?<'?6S?\7)UQ?0???A?9j??;Z??{?FY???????6??!??f-???h??c????5?V?*b?!:F?u???@!?????K??9Y?o??k?e.??w?2???ha9?%.??'?Oe?,?P??P?????AiU?*L?={gY??????7a`W'5??!gue????&????P?2?"l?~$Kq??>"$? ????-?o`?# c???M?/???,????>?.(??D?VCj???Y|???U82v?R!??WL????:`?&?? ?nPkz5??Gnn???*?2?m4C?d(??? +?? ?M 8'??z??.???)?T????/?????? ??Y????j7 V???`??eqS`???`A???}?? ?H)?GVq[???zX#k??r??H? u??`2A;?z\?n;MOPla?m??2 h?????G???&7Mr???Zfq?9?(?e???)8? +D?p{??4pFUr????&???V???Q??^lSC_??( 3?"6??6"i?UI????((???u??fJ??????m??q?????y89`%arJo?????F??x?c?d??e:?n????"B?NsB??6e?I??p?+j6^? ySb?? +Cv???????V? +?P2?K?,??4???=??^???>??=??????????v2????Z[?/6?{??G? ?T???X??(?nB??X???ho??|????{^? ???H?z?LZ?JM?i0'?b?h????n?6??? ?f`Pq??,0?????iv?b?=??{ ??2??**7??m?S*?}??C ?{X?H$?^1??? ?ng ?;??Kt?S!o\???Zy???<9?nP?e?9? ?*ZnV? ?????c?#?`:? ??8????4???u??U??:??!??W?gR3??~vY/GZ?9??^{?????2?HdWx?J??@ +RR?o?2?????ce?F??=y}??k??VE???s?'???h???J????I4OIEI??9???{??p???o?????If?????`?q??hP8?(6lS?r???*???2??5h?p???v=6,!?? +=@?;????2??'Z1???? } ???????D????6?;? #?+v7?}0??y)?????n ?qK?n????'???L??? ??=????h??6??????cn-????#?? fC????????P??M? +?+J??D?^??V??Ov{f??????F??i-D?~8?????>???d}??&???E???5^[5Imx5'y5?????c@?E??~?????1TH44??7W???,?.[??u?8???l??4???I???H?????%?$??B?(r??>??'?k??????-?&?????l? +??r??d?d?{???;??}?o?9????x??7^mp2K????-?q??7?*?)??]?5!-B?.?^2?v?H??$d???GeF$}5??a??n? Fq???z L?? +???n????????Xs-un?7????}????l?^???M??:?2??? mu?Pa?qaT?trb`?8tt?B?7-??"?-??^b Q??-7a??????????kY?]???FEK?I???9%OW???????W?E??o?/?5?s???'?q?Eq@????????n5?>(?3?j??&5?He????^Z????1???{??@?fES?1x?????<f?9Q?WF?????~?;?i h}}s?,3?Yj??/t?>b2?<4???V????S?????&?q??Y/?o????\?#?;? ?e?P?"?^m??.???#?+?,??Y+7?'???+?l??]???Z(?5?6??<"???s,Q?????d??F??????????:????owK +A?{cx????????|??{p?1?=;H?d?Y??j?????Oa^D?At&????????+?? +???????j??s*SR?n?|?w ?aKz?SQ?2??G?"i^]????V?/????r!?,j??Vd?C?M??`?>5~K??????0????B?0????:?\???9?UH?Oq?by??N??U?Hi^??T???&????0*c???????????}?s"??*?[?????????7?U??M??Em-?eNW????n????w????-???????O???=??7??: ?N?s! y?? !?j,??e???h???C?{??????T????y?7?x??b?T=?L???. ?L??|)????????3??????,??t??G?a?j?zb?p-AA??md>?4??,?Q??\??CI???@?(z9????Rp[?????>??????s?3&M?W??Y=??F? 1?????NB?C;%@?B-?? S'^?x TU??8?=????JZ?`M??????? Rm????1@??q?< ?X? d???.???F???a?m?"WC8N1 ? ?#3?? ???ys$? kg??{?i??t?0??QU????i?k??@k?n?z?????gv?p|???????w?|?9?@?R*??????PI??KOu]?=Y????1!?????'?pArM/?Yf?)}s?d????.$?Ijd?Y?v +?mA +n?- O?e??O?r,??{?k??u???(???E???????~????G??>??x?zb????}?*?sT?x)@?S??\???\?Qs|??????5??A?%??v?Fp??F?!9Q?r?O3E???Z?)c?t!c??i??`k ??O:=???z????????E?M???g??ZVUZ?f??????|????????????1,?{?-&?j*8?pn??S>????????% +?k?j=????Z0?/"`5???y????H]???1????0?i???/V?? 5y?+? c??????v"*=]??F??? ????????3??????4??1?v|N??K????U???@??H?????Bv???>?f$1?k??~B?Y)?IZ5?#)M?e??:1??g?2 ?)+Pt?????|W???HE?-???Xo?D? o???c}???????$???h?g?h;,;a?h?`-b?Ac8??L2W?V????????????????H???t?*i???????9 06=??EA-_s????/Wd???9?"?^\{yQ?m????I????sv? ????z????????@??l=?d???M?????Z???S6'h?6??Ec?]??j????zFvn?fb???>?&#?o_S?wcCM3Gm?x???z???t????V??'n?????t#+?sPn?6zn?7?H?@cD??????u_*r????14T??d?5E0????"?q?v????/??U????? ????? +?-f`?(#E??ua,h ???sMZ?u?(f??r???PA?#??!?5/?IY? ??9?NDP?t#??Y?Z???h?,?Z?W! ???q? ]????g?.?s??Fz??H#9?%?%NyMZ????;???0??S1?y??v?C2?X?j????I??Ra8??UV?y +? 1u'???????? +?-L??a?J?'?oOHE\ 7??5w:u????????????G???*T???}???4?Z?m???Y"}?|?H +%???/????? 3??>?%??VrU??Gxa?????R ?/0?gz?K[???2aO=???K(RB? +3d???o{???Z??VO;2=h?s?????4?y?MjAR???3]t7?(???x0??????9???%?P?lQa??"{?b]?{????P??y??\??6??? bD?????P?mV???h??1?#?n4 ]8????1c|???C??5?H?m?N?tm????????r?6???6b?D??[?8w?P?W? +gK1???>???!??qB???T?:?A?q??U??????h??F?K/3ic=??VJ&???{?]x?I Z~O;|?G!}??V??&?? r?F??F|?QfS +.?????????fXY?Nd7Rg +u???\?F?yR???Gz??????2?\.??O?>L?????z??x?J??)?Z?D?qbG????cv???N???jZcc?X?r^?^0v??|?|%W???????????*??q?l????????K?T?z|bY???kZ4??6Q$??n?????? ???++??N?,??*$e?C?k? ? X/?Gf??????d??O*/\?2?????2?`?*R???? ??A)? =???????D,?>?>H??qPU??c????????$*K|?(:??????;U?\??#7?kyj?` ?}???w?q?????i????@?)???? ??????d??ECBzb???{7???c ???=Ga???b?0x)?D at WG] ???"??2C??v~????@*??????#bTkhC???(?^U??X???^???S?Kl???5?????E1?S-? +?U??W?@??P??=?>?!????? ?675?????2?????9?W??U??~??md?????SO?`#u?AL??'R?`X?????????????s?#?L??)??< +??? +?7?Cs'??YJ"1?? +2?6?V?2??T1????K]???????7%?? ?_?L??????-???u?b#?5???T1?q?B??A????MC4e#3?????????(?l? +J?:nCp?,3~U???@?F{ye?f?#?2????*????&3??#??????FP?P?=?ZH ??;??`???? +?"(????????&CD??3???????|!-?d8???!????Vt????Up??b~????,-?R? +????????????z X ??=2+vu??????????gBk\:^??{????no?SC(?@dz????R???'???-}?/?Ug??8?ht$z?^[?S??~?,?yNI??:}?%?hE??{+?????^???kz:???????x?G ??_i??'???X=????Hl?_?\b??????4????? a?m_?w??S?;=$;?w????u4d7?%Ct??? +z?W?J +??uX?:? +bw?-# +???Y?.?rc +?7??]???????tW@C???m3?b}???1??C???5l??!?2???,0Y?????.z?????2-c?K{-$?#4Q? Z??Q???= +q??Jm+o?;r?,??'0?*???g??u? +?E?.???rv????$N?=??'[`&?}r????z??#t??Y??o?2????l?zQ?9???^bfrj?u>*/MM +?X???+?X??]]?A??????e???b?Orey?^?a?&:?}???? +??o??HM?bZ*????N>??Rm??????wu?=?'?????%?3?NH?h??u?O??<-???G?v?h???)?B?% ?? VX>???1" ??F?7???5??? ??\???C??6?M???0?^ ?(??X??tUt?R?t$??K?B???B????????(|?~?v????q$?/??Zm?:??K?{????Zc=???E?l??????5?M'?yt?Y%\??9eP?~rwg??0?B????,?>???Sh5I?S??? g???J~?~V???6??/???H????5???&1???7??I(??r??????m|Vuc?^v?E?*D&?????l??|[?D???D?/7??KC? +\? o?[?tKR1? ?]??y7?0l7<??6\m?]?b???E6???M2??]HW??z?N??? ?D@?~c?l'?84?:H???LC???? ?H???:?\?g??9??2???DP^??5??d???9Se?0&v?u??[0M^&??Y$B73!?;Jh_????? ???S?W? ?????d? ??OX???JxV?n?????p=?4r[?V?f?3??,????W?/???f? )??3"n?G?_?N??d??3???k?' ??3*?^?]??h???&!?Y?????/?bk0e%?J?F?i"?~?????(z?g?????$?^????????????B??G??L??,L?ER[?e{???C$??????PH3???? +\??????????f??!???cM??(????hvx?w?m??2??Gwc?'D2V?##\??z???p9?R`^?f#??????v ?mu?0n?X??p5???7?n.\=??/{?/?]?b:+?c?v??$f?[? +?????m??nE????{?0??@?bO??????L1????#??5h at K?R?~?_?$??}?! +r +\???Rn???B5k?^???$|??p????s_???A? ?E?.??$7R&?? J?????c????????D???qK???(?+kC???Y???B|!s3m?)?v$?A?(V`??????G??D&?F?G? +??????L"????2/ ?z??m?E:'?u???>?l????s7~? )_???dw??:??oN~H???7o0????70????=8?X?_????u/??y]?&?I??$?of?Y?` I??9?w6???????R.9??b??'?0P????a?\???s?T???7V??(?????)Fp>??^????J?)?E? O?'???FJ?>?"|?{? +(?V?rl????y??Zm?vg??V9y?{pi???/???pi??[z6????f?????"o???4<???H?j}%???^??v?F?'?x"???$:??Gj??*??;/???gD"iF?D??????v?7????e? +?\1??&????MrJ?\??,?0l?a??}??a= +??6Ws[?y>??{???+?? 7h??U&r???tpt???T???????2?C?????-?1?7???(M???y*???????0ye????J?@?%/?j??k??6n8??Q +??}?kh?H???~?llIf??z?)Y7???????? +? ????&?N3?xS?????[!????>????????Z6??~?}???Ne?7gD??/>????~?Z#?okL??G'?-??]?3???j?G??$glRW??]?TpNNd? +?????? +a'????8PsF?????Z??C2????Z?%?Ghn??'A?? ??<J??j?? +?(S???? +;tQ??????O??T?? ?j5???HNo??7?u?z:????V???&i???????!H?}~?d?? ?????????l???~?????Ek?~??????7e???q????3??\??W?????????e??Zl`?,?3?m?uP???3???????Y???(7-??+?????? *G\O?y?&?e???ID_4b??w??7l?????}VX?|h?5t?O}??R3???O???f?1???#;L'?~?{??????'.??P?"?}'???O????1`y!?????D\??g?Qx???Uws??U?? ?e????3?x?2?v?? +???K?E? ?|?H&??a~??^?????#p?p?? ?J????????$?wB9?N?]?B?lv?7V D??d?6???;????7Ds?/m<?q???f6R???I??)???M????? M?a-?L[F9??|?x?~?aQ"k??0?9E$E_}T#?????m$??Bp#?MV?s?|g?? ~? ?r?e4?[?????D\?????w^Z???;???d?O{?5Q(s??KSub +??}?K?:?7??b +5??????j?o???;I??*?I?c???T.???k?$???z^??yi?? ??R?Z?v?0B??Z?[?Zd!t????7 ??R?rzB7?m7'L3mSa`?S 8?a%???NC????;qM!A?\hU?pW???[??6e =??????ZP?W?/ +??????? V??v`V$?;H?N{d??4<??????Fl?????#???Di)??????-?M??c?G?;?V?9{??8p +K?"???F?!\??$?????f?~?????%???Y\???e!????m????mz?????t?Bbi/??]??b???Sh??9??^???J?1???o),8?}?}???9;?$d??!J????:"i??I?>?2E7?????????f)^?q :???DCR=?]T??ig??mE???????(d??L??????!??~u?-???/g??A?c?z94c2????r??i??? +?????? +w?.?? + `pb?'EeaUs??w??g,??K?:?I??.M%??#?????J??g?!U?YX?[?zMz????K at d>??a?Ej??6 ??;??OJT8????^???@??X??e?8Oi???????Fd?V?L??v???!(???)??r?;\=\??>8 Y?"q#??^???h?????%???8z +?????7t????"?J7?Q?@{n(}?f??.??o8?x??8+UL9??S?????w +?fyO???g??xrR5????2???+??$<?????e?L? ?(?a??S?-????ao ?z??5$=?]?v?2PL-???G?@??{s?)??7?.1??]????#?SJ???F?(2???>?$#! xW?y?f???&qmt??H????}???A|???_?s??r???^m>^??XU??Vh?????m +??a??^kE?34Y?p?OL +??vs\?]w???????Q/?>a?#DZhB7r???!D9$0KW?4Q?xc?mG?????????C??6?N??? +?uIVp??O5??????y?t???j|G??S?[??i?????x[????c??e"?=A?wX??tQd?2B.??l{W??3?o???\6?9>'?#?2???X??y"?+??t3??$;k?Tx????????=??.???T???b?j^??s ?Q????9?c??$?[k?z?r??OpkT[!??????On??j.????`??????E?m?5??!???d.?%??0?????)ic(?j]????T??%F??.{O!????P?!?v???>?[O\??????-.0?? +?Yb?????R??T/?%??c?1 +?S??l???y[????????. *[??'Qz????? ???z@7.??&(??W??.s?#???&G??V?D??\?6??V?m?????a!G??????2'U????s??????c?9_m??'?l??{???????'???????? +c?T?sF??R?>????&?q??+?????? ??$?v? #?b????DR>??]?i?4??q~./-?}k +cj??]?u??2????b??T????z??/????Xb?Z?3~???J?? +?"L???????e_???qi?fH#?}3z? + H??:?$t ??K????Tb?@BAb0J???|???????_^K#????8[ ?????-??6?4??*??s?r?? +?????q??????.?S?^???KZE????@?????C??D??MUpC?v?*7????m?4?h???a?Q&???R????c?O???B? +0????n??l???U????w??FE??n?2???Uh???'$?Ab??igZf??g?b??x? ??? Q??6=?-???R*?a?d??TQ,eH?L0|"'???(]U????O3q?????S??E|?j?7R.$?LUP??????t?????o?Z??8?m? /??:11S?8Dk?U?.??n?;6???v?u???F?S +??? w4?\??? \H??????3??X9JM???!?rr??x??>#"Y??`^Dd?? ?M??c]?z?}??.n>??%!E ???????.????<$v?m???? +=?|?%? ?}?m?P??[???^??n\??? ?oLZ??[u(z??Dt@???????d??c[?F0???P?i:??????hV?+?*?2g=N???#???\Qa??$c??)??s;???J +B?'???QJSh?i'????!?/?'?Z}Z???????mO?? ?ZE?uM??o?u???o?8K?xd7N??;???(???,??+? ??6?????I???67???,[$?CPmG???;_??/????????9~J??^z.6l???C%j??g????%{?3O?r?=??x??[?b????????''??????'?ev??$?C'.?n??n???^?Ym[???Af?BAv!?Fo?]I?????c?c???'j????;??Y X?|?23lN???????y'?~x???m?P????1? f??)?|D?>?c^?y?0/?@??Q/z?f?"7?,?i??~Q??q???f:.?b??$??V?`?'???]????? ?6??C????Q??hC|???mZT?^???j?????J???_???v +W?E? +??~?0?}?t??w??Hog??x6Bl?"q??????-.??=?y#+9[P?M???????? y??:??O+?[??z?O-?6?=?\A?`?K?o\?????~??d?B*??9???? ??:?S?_?\?`+h?P?C??????5?(Z?KA?5?a?,?V?2c:?od???|?-??5~????O??|????????]p|^??R?P>+??bn???????? +??? ,84??K??(?endstream +endobj +100 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 640 0 R +/FirstChar 2 +/LastChar 149 +/Widths 646 0 R +/BaseFont /JDSEUT+NimbusRomNo9L-Regu +/FontDescriptor 98 0 R +>> endobj +98 0 obj << +/Ascent 678 +/CapHeight 651 +/Descent -216 +/FontName /JDSEUT+NimbusRomNo9L-Regu +/ItalicAngle 0 +/StemV 85 +/XHeight 450 +/FontBBox [-168 -281 1000 924] +/Flags 4 +/CharSet (/fi/fl/exclam/quotedbl/quoteright/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/bar/bullet) +/FontFile 99 0 R +>> endobj +646 0 obj +[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 0 0 0 0 333 333 333 0 0 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 564 564 564 0 921 722 667 667 722 611 556 722 722 333 389 0 611 889 722 722 556 722 667 556 611 722 722 944 722 722 0 333 0 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 200 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 350 ] +endobj +108 0 obj << +/Type /Pages +/Count 6 +/Parent 647 0 R +/Kids [94 0 R 110 0 R 139 0 R 143 0 R 184 0 R 212 0 R] +>> endobj +281 0 obj << +/Type /Pages +/Count 6 +/Parent 647 0 R +/Kids [246 0 R 283 0 R 324 0 R 359 0 R 402 0 R 447 0 R] +>> endobj +513 0 obj << +/Type /Pages +/Count 4 +/Parent 647 0 R +/Kids [468 0 R 515 0 R 566 0 R 611 0 R] +>> endobj +647 0 obj << +/Type /Pages +/Count 16 +/Kids [108 0 R 281 0 R 513 0 R] +>> endobj +648 0 obj << +/Type /Outlines +/First 7 0 R +/Last 87 0 R +/Count 5 +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 87 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 648 0 R +/Prev 63 0 R +/First 91 0 R +/Last 91 0 R +/Count -1 +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 63 0 R +/Prev 79 0 R +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 63 0 R +/Prev 75 0 R +/Next 83 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 63 0 R +/Prev 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 63 0 R +/Prev 67 0 R +/Next 75 0 R +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 63 0 R +/Next 71 0 R +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 648 0 R +/Prev 15 0 R +/Next 87 0 R +/First 67 0 R +/Last 83 0 R +/Count -5 +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 15 0 R +/Prev 55 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 15 0 R +/Prev 51 0 R +/Next 59 0 R +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 15 0 R +/Prev 39 0 R +/Next 55 0 R +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 39 0 R +/Prev 43 0 R +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 39 0 R +/Next 47 0 R +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 15 0 R +/Prev 35 0 R +/Next 51 0 R +/First 43 0 R +/Last 47 0 R +/Count -2 +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 15 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 15 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 15 0 R +/Prev 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 15 0 R +/Prev 19 0 R +/Next 27 0 R +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 15 0 R +/Next 23 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 648 0 R +/Prev 11 0 R +/Next 63 0 R +/First 19 0 R +/Last 59 0 R +/Count -9 +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 648 0 R +/Prev 7 0 R +/Next 15 0 R +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 648 0 R +/Next 11 0 R +>> endobj +649 0 obj << +/Names [(Doc-Start) 104 0 R (_adding_another_application) 220 0 R (_anonymous_files) 261 0 R (_arrays) 303 0 R (_bits) 624 0 R (_datatypes) 264 0 R (_fixed_array_mapper) 338 0 R (_foreach) 362 0 R (_hello_world) 153 0 R (_if) 385 0 R (_introduction) 146 0 R (_language_features) 187 0 R (_mappers) 318 0 R (_named_and_optional_parameters) 625 0 R (_parameters) 188 0 R (_running_on_a_remote_site) 445 0 R (_runtime_features) 439 0 R (_sequential_iteration) 392 0 R (_starting_and_restarting) 531 0 R (_the_regexp_mapper) 329 0 R (_visualising_the_workflow_as_a_graph) 440 0 R (_writing_a_mapper) 450 0 R (_writing_a_very_basic_mapper) 463 0 R (lstlisting.-1) 154 0 R (lstlisting.-10) 226 0 R (lstlisting.-11) 232 0 R (lstlisting.-12) 235 0 R (lstlisting.-13) 256 0 R (lstlisting.-14) 262 0 R (lstlisting.-15) 265 0 R (lstlisting.-16) 270 0 R (lstlisting.-17) 272 0 R (lstlisting.-18) 304 0 R (lstlisting.-19) 306 0 R (lstlisting.-2) 167 0 R (lstlisting.-20) 319 0 R (lstlisting.-21) 321 0 R (lstlisting.-22) 327 0 R (lstlisting.-23) 330 0 R (lstlisting.-24) 339 0 R (lstlisting.-25) 363 0 R (lstlisting.-26) 386 0 R (lstlisting.-27) 393 0 R (lstlisting.-28) 417 0 R (lstlisting.-29) 426 0 R (lstlisting.-3) 177 0 R (lstlisting.-30) 441 0 R (lstlisting.-31) 471 0 R (lstlisting.-32) 474 0 R (lstlisting.-33) 508 0 R (lstlisting.-34) 510 0 R (lstlisting.-35) 527 0 R (lstlisting.-36) 532 0 R (lstlisting.-37) 557 0 R (lstlisting.-38) 560 0 R (lstlisting.-39) 571 0 R (lstlisting.-4) 179 0 R (lstlisting.-40) 573 0 R (lstlisting.-41) 588 0 R (lstlisting.-42) 591 0 R (lstlisting.-43) 614 0 R (lstlisting.-44) 616 0 R (lstlisting.-45) 626 0 R (lstlisting.-46) 632 0 R (lstlisting.-47) 634 0 R (lstlisting.-5) 189 0 R (lstlisting.-6) 199 0 R (lstlisting.-7) 201 0 R (lstlisting.-8) 221 0 R (lstlisting.-9) 224 0 R (lstnumber.-1.1) 155 0 R (lstnumber.-1.2) 159 0 R (lstnumber.-1.3) 160 0 R (lstnumber.-1.4) 161 0 R (lstnumber.-1.5) 162 0 R (lstnumber.-1.6) 163 0 R (lstnumber.-1.7) 16 4 0 R (lstnumber.-1.8) 165 0 R (lstnumber.-1.9) 166 0 R (lstnumber.-10.1) 227 0 R (lstnumber.-10.2) 228 0 R (lstnumber.-10.3) 229 0 R (lstnumber.-10.4) 230 0 R (lstnumber.-10.5) 231 0 R (lstnumber.-11.1) 233 0 R (lstnumber.-11.2) 234 0 R (lstnumber.-12.1) 236 0 R (lstnumber.-12.10) 250 0 R (lstnumber.-12.11) 251 0 R (lstnumber.-12.12) 252 0 R (lstnumber.-12.13) 253 0 R (lstnumber.-12.14) 254 0 R (lstnumber.-12.15) 255 0 R (lstnumber.-12.2) 237 0 R (lstnumber.-12.3) 238 0 R (lstnumber.-12.4) 239 0 R (lstnumber.-12.5) 240 0 R (lstnumber.-12.6) 241 0 R (lstnumber.-12.7) 242 0 R (lstnumber.-12.8) 243 0 R (lstnumber.-12.9) 249 0 R (lstnumber.-13.1) 257 0 R (lstnumber.-13.2) 258 0 R (lstnumber.-13.3) 259 0 R (lstnumber.-13.4) 260 0 R (lstnumber.-14.1) 263 0 R (lstnumber.-15.1) 266 0 R (lstnumber.-15.2) 267 0 R (lstnumber.-15.3) 268 0 R (lstnumber.-15.4) 269 0 R (lstnumber.-16.1) 271 0 R (lstnumber.-17.1) 273 0 R (lstnumber.-17.10) 293 0 R (lstnumber.-17.11) 294 0 R (lstnumber.-17. 12) 295 0 R (lstnumber.-17.13) 296 0 R (lstnumber.-17.14) 297 0 R (lstnumber.-17.15) 298 0 R (lstnumber.-17.16) 299 0 R (lstnumber.-17.17) 300 0 R (lstnumber.-17.18) 301 0 R (lstnumber.-17.19) 302 0 R (lstnumber.-17.2) 274 0 R (lstnumber.-17.3) 275 0 R (lstnumber.-17.4) 276 0 R (lstnumber.-17.5) 277 0 R (lstnumber.-17.6) 278 0 R (lstnumber.-17.7) 279 0 R (lstnumber.-17.8) 280 0 R (lstnumber.-17.9) 286 0 R (lstnumber.-18.1) 305 0 R (lstnumber.-19.1) 307 0 R (lstnumber.-19.10) 316 0 R (lstnumber.-19.11) 317 0 R (lstnumber.-19.2) 308 0 R (lstnumber.-19.3) 309 0 R (lstnumber.-19.4) 310 0 R (lstnumber.-19.5) 311 0 R (lstnumber.-19.6) 312 0 R (lstnumber.-19.7) 313 0 R (lstnumber.-19.8) 314 0 R (lstnumber.-19.9) 315 0 R (lstnumber.-2.1) 168 0 R (lstnumber.-2.2) 169 0 R (lstnumber.-2.3) 170 0 R (lstnumber.-2.4) 171 0 R (lstnumber.-2.5) 172 0 R (lstnumber.-2.6) 173 0 R (lstnumber.-2.7) 174 0 R (lstnumber.-2.8) 175 0 R (lstnumber.-2.9) 176 0 R (lstnumber.-20.1) 320 0 R (lstnumber.-21. 1) 322 0 R (lstnumber.-22.1) 328 0 R (lstnumber.-23.1) 331 0 R (lstnumber.-23.2) 332 0 R (lstnumber.-23.3) 333 0 R (lstnumber.-23.4) 334 0 R (lstnumber.-23.5) 335 0 R (lstnumber.-23.6) 336 0 R (lstnumber.-23.7) 337 0 R (lstnumber.-24.1) 340 0 R (lstnumber.-24.10) 349 0 R (lstnumber.-24.11) 350 0 R (lstnumber.-24.12) 351 0 R (lstnumber.-24.13) 352 0 R (lstnumber.-24.14) 353 0 R (lstnumber.-24.15) 354 0 R (lstnumber.-24.16) 355 0 R (lstnumber.-24.17) 356 0 R (lstnumber.-24.18) 357 0 R (lstnumber.-24.2) 341 0 R (lstnumber.-24.3) 342 0 R (lstnumber.-24.4) 343 0 R (lstnumber.-24.5) 344 0 R (lstnumber.-24.6) 345 0 R (lstnumber.-24.7) 346 0 R (lstnumber.-24.8) 347 0 R (lstnumber.-24.9) 348 0 R (lstnumber.-25.1) 364 0 R (lstnumber.-25.10) 373 0 R (lstnumber.-25.11) 374 0 R (lstnumber.-25.12) 375 0 R (lstnumber.-25.13) 376 0 R (lstnumber.-25.14) 377 0 R (lstnumber.-25.15) 378 0 R (lstnumber.-25.16) 379 0 R (lstnumber.-25.17) 380 0 R (lstnumber.-25.18) 381 0 R (lstnumber.-25.19) 382 0 R (lstnumber.-25.2) 365 0 R (lstnumber.-25.20) 383 0 R (lstnumber.-25.21) 384 0 R (lstnumber.-25.3) 366 0 R (lstnumber.-25.4) 367 0 R (lstnumber.-25.5) 368 0 R (lstnumber.-25.6) 369 0 R (lstnumber.-25.7) 370 0 R (lstnumber.-25.8) 371 0 R (lstnumber.-25.9) 372 0 R (lstnumber.-26.1) 387 0 R (lstnumber.-26.2) 388 0 R (lstnumber.-26.3) 389 0 R (lstnumber.-26.4) 390 0 R (lstnumber.-26.5) 391 0 R (lstnumber.-27.1) 394 0 R (lstnumber.-27.10) 408 0 R (lstnumber.-27.11) 409 0 R (lstnumber.-27.12) 410 0 R (lstnumber.-27.13) 411 0 R (lstnumber.-27.14) 412 0 R (lstnumber.-27.15) 413 0 R (lstnumber.-27.16) 414 0 R (lstnumber.-27.17) 415 0 R (lstnumber.-27.18) 416 0 R (lstnumber.-27.2) 395 0 R (lstnumber.-27.3) 396 0 R (lstnumber.-27.4) 397 0 R (lstnumber.-27.5) 398 0 R (lstnumber.-27.6) 399 0 R (lstnumber.-27.7) 405 0 R (lstnumber.-27.8) 406 0 R (lstnumber.-27.9) 407 0 R (lstnumber.-28.1) 418 0 R (lstnumber.-28.2) 419 0 R (lstnumber.-28.3) 420 0 R (lstnumber.-28.4) 421 0 R (lstnumber.-2 8.5) 422 0 R (lstnumber.-28.6) 423 0 R (lstnumber.-28.7) 424 0 R (lstnumber.-28.8) 425 0 R (lstnumber.-29.1) 427 0 R (lstnumber.-29.10) 436 0 R (lstnumber.-29.11) 437 0 R (lstnumber.-29.12) 438 0 R (lstnumber.-29.2) 428 0 R (lstnumber.-29.3) 429 0 R (lstnumber.-29.4) 430 0 R (lstnumber.-29.5) 431 0 R (lstnumber.-29.6) 432 0 R (lstnumber.-29.7) 433 0 R (lstnumber.-29.8) 434 0 R (lstnumber.-29.9) 435 0 R (lstnumber.-3.1) 178 0 R (lstnumber.-30.1) 442 0 R (lstnumber.-30.2) 443 0 R (lstnumber.-31.1) 472 0 R (lstnumber.-31.2) 473 0 R (lstnumber.-32.1) 475 0 R (lstnumber.-32.10) 484 0 R (lstnumber.-32.11) 485 0 R (lstnumber.-32.12) 486 0 R (lstnumber.-32.13) 487 0 R (lstnumber.-32.14) 488 0 R (lstnumber.-32.15) 489 0 R (lstnumber.-32.16) 490 0 R (lstnumber.-32.17) 491 0 R (lstnumber.-32.18) 492 0 R (lstnumber.-32.19) 493 0 R (lstnumber.-32.2) 476 0 R (lstnumber.-32.20) 494 0 R (lstnumber.-32.21) 495 0 R (lstnumber.-32.22) 496 0 R (lstnumber.-32.23) 497 0 R (lstnumber.-32.24) 498 0 R (lstnumber.-32.25) 499 0 R (lstnumber.-32.26) 500 0 R (lstnumber.-32.27) 501 0 R (lstnumber.-32.28) 502 0 R (lstnumber.-32.29) 503 0 R (lstnumber.-32.3) 477 0 R (lstnumber.-32.30) 504 0 R (lstnumber.-32.31) 505 0 R (lstnumber.-32.32) 506 0 R (lstnumber.-32.33) 507 0 R (lstnumber.-32.4) 478 0 R (lstnumber.-32.5) 479 0 R (lstnumber.-32.6) 480 0 R (lstnumber.-32.7) 481 0 R (lstnumber.-32.8) 482 0 R (lstnumber.-32.9) 483 0 R (lstnumber.-33.1) 509 0 R (lstnumber.-34.1) 511 0 R (lstnumber.-34.10) 525 0 R (lstnumber.-34.11) 526 0 R (lstnumber.-34.2) 512 0 R (lstnumber.-34.3) 518 0 R (lstnumber.-34.4) 519 0 R (lstnumber.-34.5) 520 0 R (lstnumber.-34.6) 521 0 R (lstnumber.-34.7) 522 0 R (lstnumber.-34.8) 523 0 R (lstnumber.-34.9) 524 0 R (lstnumber.-35.1) 528 0 R (lstnumber.-35.2) 529 0 R (lstnumber.-36.1) 533 0 R (lstnumber.-36.10) 542 0 R (lstnumber.-36.11) 543 0 R (lstnumber.-36.12) 544 0 R (lstnumber.-36.13) 545 0 R (lstnumber.-36.14) 546 0 R (lstnumber.-36.15) 547 0 R (lstnum ber.-36.16) 548 0 R (lstnumber.-36.17) 549 0 R (lstnumber.-36.18) 550 0 R (lstnumber.-36.19) 551 0 R (lstnumber.-36.2) 534 0 R (lstnumber.-36.20) 552 0 R (lstnumber.-36.21) 553 0 R (lstnumber.-36.22) 554 0 R (lstnumber.-36.23) 555 0 R (lstnumber.-36.24) 556 0 R (lstnumber.-36.3) 535 0 R (lstnumber.-36.4) 536 0 R (lstnumber.-36.5) 537 0 R (lstnumber.-36.6) 538 0 R (lstnumber.-36.7) 539 0 R (lstnumber.-36.8) 540 0 R (lstnumber.-36.9) 541 0 R (lstnumber.-37.1) 558 0 R (lstnumber.-37.2) 559 0 R (lstnumber.-38.1) 561 0 R (lstnumber.-38.2) 562 0 R (lstnumber.-38.3) 563 0 R (lstnumber.-38.4) 564 0 R (lstnumber.-38.5) 569 0 R (lstnumber.-38.6) 570 0 R (lstnumber.-39.1) 572 0 R (lstnumber.-4.1) 180 0 R (lstnumber.-4.2) 181 0 R (lstnumber.-4.3) 182 0 R (lstnumber.-40.1) 574 0 R (lstnumber.-40.10) 583 0 R (lstnumber.-40.11) 584 0 R (lstnumber.-40.12) 585 0 R (lstnumber.-40.13) 586 0 R (lstnumber.-40.14) 587 0 R (lstnumber.-40.2) 575 0 R (lstnumber.-40.3) 576 0 R (lstnumber.-40.4) 577 0 R (lstnumber.-40.5) 578 0 R (lstnumber.-40.6) 579 0 R (lstnumber.-40.7) 580 0 R (lstnumber.-40.8) 581 0 R (lstnumber.-40.9) 582 0 R (lstnumber.-41.1) 589 0 R (lstnumber.-41.2) 590 0 R (lstnumber.-42.1) 592 0 R (lstnumber.-42.10) 601 0 R (lstnumber.-42.11) 602 0 R (lstnumber.-42.12) 603 0 R (lstnumber.-42.13) 604 0 R (lstnumber.-42.14) 605 0 R (lstnumber.-42.15) 606 0 R (lstnumber.-42.16) 607 0 R (lstnumber.-42.17) 608 0 R (lstnumber.-42.18) 609 0 R (lstnumber.-42.2) 593 0 R (lstnumber.-42.3) 594 0 R (lstnumber.-42.4) 595 0 R (lstnumber.-42.5) 596 0 R (lstnumber.-42.6) 597 0 R (lstnumber.-42.7) 598 0 R (lstnumber.-42.8) 599 0 R (lstnumber.-42.9) 600 0 R (lstnumber.-43.1) 615 0 R (lstnumber.-44.1) 617 0 R (lstnumber.-44.2) 618 0 R (lstnumber.-44.3) 619 0 R (lstnumber.-44.4) 620 0 R (lstnumber.-44.5) 621 0 R (lstnumber.-44.6) 622 0 R (lstnumber.-44.7) 623 0 R (lstnumber.-45.1) 627 0 R (lstnumber.-45.2) 628 0 R (lstnumber.-45.3) 629 0 R (lstnumber.-45.4) 630 0 R (lstnumber.-45. 5) 631 0 R (lstnumber.-46.1) 633 0 R (lstnumber.-47.1) 635 0 R (lstnumber.-5.1) 190 0 R (lstnumber.-5.2) 191 0 R (lstnumber.-5.3) 192 0 R (lstnumber.-5.4) 193 0 R (lstnumber.-5.5) 194 0 R (lstnumber.-5.6) 195 0 R (lstnumber.-5.7) 196 0 R (lstnumber.-5.8) 197 0 R (lstnumber.-5.9) 198 0 R (lstnumber.-6.1) 200 0 R (lstnumber.-7.1) 202 0 R (lstnumber.-7.10) 215 0 R (lstnumber.-7.11) 216 0 R (lstnumber.-7.12) 217 0 R (lstnumber.-7.13) 218 0 R (lstnumber.-7.2) 203 0 R (lstnumber.-7.3) 204 0 R (lstnumber.-7.4) 205 0 R (lstnumber.-7.5) 206 0 R (lstnumber.-7.6) 207 0 R (lstnumber.-7.7) 208 0 R (lstnumber.-7.8) 209 0 R (lstnumber.-7.9) 210 0 R (lstnumber.-8.1) 222 0 R (lstnumber.-8.2) 223 0 R (lstnumber.-9.1) 225 0 R (named_parameters) 244 0 R (page.1) 145 0 R (page.10) 470 0 R (page.11) 517 0 R (page.12) 568 0 R (page.13) 613 0 R (page.2) 186 0 R (page.3) 214 0 R (page.4) 248 0 R (page.5) 285 0 R (page.6) 326 0 R (page.7) 361 0 R (page.8) 404 0 R (page.9) 449 0 R (page.i) 97 0 R (pag e.ii) 112 0 R (page.iii) 141 0 R (section.1) 6 0 R (section.2) 10 0 R (section.3) 14 0 R (section.4) 62 0 R (section.5) 86 0 R (subsection.3.1) 18 0 R (subsection.3.2) 22 0 R (subsection.3.3) 26 0 R (subsection.3.4) 30 0 R (subsection.3.5) 34 0 R (subsection.3.6) 38 0 R (subsection.3.7) 50 0 R (subsection.3.8) 54 0 R (subsection.3.9) 58 0 R (subsection.4.1) 66 0 R (subsection.4.2) 70 0 R (subsection.4.3) 74 0 R (subsection.4.4) 78 0 R (subsection.4.5) 82 0 R (subsection.5.1) 90 0 R (subsubsection.3.6.1) 42 0 R (subsubsection.3.6.2) 46 0 R] +/Limits [(Doc-Start) (subsubsection.3.6.2)] +>> endobj +650 0 obj << +/Kids [649 0 R] +>> endobj +651 0 obj << +/Dests 650 0 R +>> endobj +652 0 obj << +/Type /Catalog +/Pages 647 0 R +/Outlines 648 0 R +/Names 651 0 R +/PageMode /UseOutlines +/OpenAction 93 0 R +>> endobj +653 0 obj << +/Author()/Title(A Swift Tutorial)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() +/CreationDate (D:20110516142225-05'00') +/PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) +>> endobj +xref +0 654 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000014704 00000 n +0000190452 00000 n +0000000054 00000 n +0000000084 00000 n +0000014828 00000 n +0000190366 00000 n +0000000129 00000 n +0000000159 00000 n +0000020667 00000 n +0000190241 00000 n +0000000205 00000 n +0000000241 00000 n +0000020792 00000 n +0000190167 00000 n +0000000292 00000 n +0000000321 00000 n +0000028277 00000 n +0000190080 00000 n +0000000372 00000 n +0000000417 00000 n +0000034470 00000 n +0000189993 00000 n +0000000468 00000 n +0000000502 00000 n +0000034721 00000 n +0000189906 00000 n +0000000553 00000 n +0000000581 00000 n +0000041326 00000 n +0000189819 00000 n +0000000632 00000 n +0000000657 00000 n +0000042332 00000 n +0000189695 00000 n +0000000708 00000 n +0000000734 00000 n +0000047548 00000 n +0000189621 00000 n +0000000790 00000 n +0000000826 00000 n +0000048177 00000 n +0000189547 00000 n +0000000882 00000 n +0000000925 00000 n +0000054278 00000 n +0000189460 00000 n +0000000976 00000 n +0000001002 00000 n +0000055787 00000 n +0000189373 00000 n +0000001053 00000 n +0000001074 00000 n +0000056287 00000 n +0000189299 00000 n +0000001125 00000 n +0000001164 00000 n +0000064645 00000 n +0000189174 00000 n +0000001210 00000 n +0000001245 00000 n +0000064769 00000 n +0000189100 00000 n +0000001296 00000 n +0000001350 00000 n +0000065081 00000 n +0000189013 00000 n +0000001401 00000 n +0000001444 00000 n +0000072874 00000 n +0000188926 00000 n +0000001495 00000 n +0000001530 00000 n +0000072999 00000 n +0000188839 00000 n +0000001581 00000 n +0000001627 00000 n +0000087023 00000 n +0000188765 00000 n +0000001678 00000 n +0000001720 00000 n +0000100510 00000 n +0000188653 00000 n +0000001766 00000 n +0000001789 00000 n +0000100635 00000 n +0000188592 00000 n +0000001840 00000 n +0000001888 00000 n +0000002310 00000 n +0000002552 00000 n +0000001939 00000 n +0000002429 00000 n +0000187104 00000 n +0000167604 00000 n +0000186932 00000 n +0000166974 00000 n +0000159388 00000 n +0000166803 00000 n +0000002490 00000 n +0000158674 00000 n +0000147555 00000 n +0000158504 00000 n +0000188106 00000 n +0000008468 00000 n +0000004598 00000 n +0000002649 00000 n +0000008405 00000 n +0000004908 00000 n +0000146940 00000 n +0000135584 00000 n +0000146767 00000 n +0000005062 00000 n +0000005217 00000 n +0000005372 00000 n +0000005532 00000 n +0000005692 00000 n +0000005852 00000 n +0000006012 00000 n +0000006172 00000 n +0000006332 00000 n +0000006497 00000 n +0000006662 00000 n +0000006821 00000 n +0000006981 00000 n +0000007141 00000 n +0000007295 00000 n +0000007455 00000 n +0000007615 00000 n +0000007774 00000 n +0000007933 00000 n +0000008092 00000 n +0000008246 00000 n +0000009232 00000 n +0000009047 00000 n +0000008579 00000 n +0000009169 00000 n +0000016586 00000 n +0000013857 00000 n +0000009330 00000 n +0000014641 00000 n +0000014765 00000 n +0000135249 00000 n +0000127186 00000 n +0000135071 00000 n +0000014015 00000 n +0000014226 00000 n +0000014436 00000 n +0000014890 00000 n +0000014953 00000 n +0000015016 00000 n +0000126251 00000 n +0000107393 00000 n +0000126080 00000 n +0000015079 00000 n +0000015142 00000 n +0000015205 00000 n +0000015268 00000 n +0000015331 00000 n +0000015394 00000 n +0000015457 00000 n +0000015520 00000 n +0000015581 00000 n +0000015644 00000 n +0000015707 00000 n +0000015770 00000 n +0000015833 00000 n +0000015896 00000 n +0000015959 00000 n +0000016022 00000 n +0000016084 00000 n +0000016145 00000 n +0000016208 00000 n +0000016271 00000 n +0000016334 00000 n +0000016397 00000 n +0000016460 00000 n +0000016523 00000 n +0000022300 00000 n +0000020482 00000 n +0000016723 00000 n +0000020604 00000 n +0000020729 00000 n +0000020854 00000 n +0000020917 00000 n +0000020980 00000 n +0000021043 00000 n +0000021106 00000 n +0000021169 00000 n +0000021232 00000 n +0000021295 00000 n +0000021358 00000 n +0000021421 00000 n +0000021484 00000 n +0000021546 00000 n +0000021609 00000 n +0000021672 00000 n +0000021735 00000 n +0000021798 00000 n +0000021861 00000 n +0000021924 00000 n +0000021987 00000 n +0000022050 00000 n +0000022112 00000 n +0000022175 00000 n +0000022238 00000 n +0000029848 00000 n +0000027658 00000 n +0000022424 00000 n +0000027962 00000 n +0000028025 00000 n +0000028088 00000 n +0000028151 00000 n +0000028214 00000 n +0000027800 00000 n +0000028339 00000 n +0000028402 00000 n +0000028465 00000 n +0000028528 00000 n +0000028591 00000 n +0000028653 00000 n +0000028716 00000 n +0000028779 00000 n +0000028842 00000 n +0000028905 00000 n +0000028968 00000 n +0000029031 00000 n +0000029094 00000 n +0000029157 00000 n +0000029220 00000 n +0000029283 00000 n +0000029346 00000 n +0000029409 00000 n +0000029472 00000 n +0000029535 00000 n +0000029598 00000 n +0000029660 00000 n +0000029723 00000 n +0000029786 00000 n +0000101501 00000 n +0000035852 00000 n +0000033530 00000 n +0000029972 00000 n +0000033652 00000 n +0000033715 00000 n +0000033778 00000 n +0000033841 00000 n +0000033904 00000 n +0000033967 00000 n +0000034029 00000 n +0000034092 00000 n +0000034155 00000 n +0000034218 00000 n +0000034281 00000 n +0000034344 00000 n +0000034407 00000 n +0000034532 00000 n +0000034595 00000 n +0000034658 00000 n +0000034783 00000 n +0000034846 00000 n +0000034909 00000 n +0000034972 00000 n +0000035035 00000 n +0000035098 00000 n +0000035161 00000 n +0000035224 00000 n +0000035287 00000 n +0000035350 00000 n +0000035413 00000 n +0000035476 00000 n +0000035539 00000 n +0000035602 00000 n +0000035664 00000 n +0000035727 00000 n +0000035790 00000 n +0000188222 00000 n +0000042709 00000 n +0000040449 00000 n +0000035963 00000 n +0000040571 00000 n +0000040634 00000 n +0000105178 00000 n +0000103721 00000 n +0000105017 00000 n +0000103386 00000 n +0000101532 00000 n +0000103225 00000 n +0000040697 00000 n +0000040760 00000 n +0000040823 00000 n +0000040885 00000 n +0000040948 00000 n +0000041011 00000 n +0000041074 00000 n +0000041137 00000 n +0000041200 00000 n +0000041263 00000 n +0000041388 00000 n +0000041451 00000 n +0000041514 00000 n +0000041577 00000 n +0000041640 00000 n +0000041703 00000 n +0000041765 00000 n +0000041828 00000 n +0000041891 00000 n +0000041954 00000 n +0000042017 00000 n +0000042080 00000 n +0000042143 00000 n +0000042206 00000 n +0000042269 00000 n +0000042394 00000 n +0000042457 00000 n +0000042520 00000 n +0000042583 00000 n +0000042646 00000 n +0000049497 00000 n +0000047237 00000 n +0000042847 00000 n +0000047359 00000 n +0000047422 00000 n +0000047485 00000 n +0000047610 00000 n +0000047673 00000 n +0000047736 00000 n +0000047799 00000 n +0000047862 00000 n +0000047925 00000 n +0000047988 00000 n +0000048051 00000 n +0000048114 00000 n +0000048239 00000 n +0000048302 00000 n +0000048365 00000 n +0000048427 00000 n +0000048490 00000 n +0000048553 00000 n +0000048616 00000 n +0000048679 00000 n +0000048742 00000 n +0000048805 00000 n +0000048868 00000 n +0000048931 00000 n +0000048994 00000 n +0000049057 00000 n +0000049119 00000 n +0000049182 00000 n +0000049245 00000 n +0000049308 00000 n +0000049371 00000 n +0000049434 00000 n +0000056851 00000 n +0000054093 00000 n +0000049608 00000 n +0000054215 00000 n +0000054340 00000 n +0000054403 00000 n +0000054466 00000 n +0000054529 00000 n +0000054592 00000 n +0000054655 00000 n +0000054718 00000 n +0000054781 00000 n +0000054844 00000 n +0000054907 00000 n +0000054970 00000 n +0000055032 00000 n +0000055095 00000 n +0000055158 00000 n +0000055221 00000 n +0000055284 00000 n +0000055347 00000 n +0000055410 00000 n +0000055473 00000 n +0000055536 00000 n +0000055599 00000 n +0000055662 00000 n +0000055724 00000 n +0000055848 00000 n +0000055910 00000 n +0000055972 00000 n +0000056035 00000 n +0000056098 00000 n +0000056161 00000 n +0000056224 00000 n +0000056349 00000 n +0000056412 00000 n +0000056475 00000 n +0000056538 00000 n +0000056601 00000 n +0000056663 00000 n +0000056726 00000 n +0000056789 00000 n +0000069155 00000 n +0000065206 00000 n +0000062127 00000 n +0000056975 00000 n +0000062443 00000 n +0000062506 00000 n +0000062569 00000 n +0000062632 00000 n +0000062695 00000 n +0000062758 00000 n +0000062820 00000 n +0000062883 00000 n +0000062946 00000 n +0000063009 00000 n +0000063072 00000 n +0000063135 00000 n +0000063198 00000 n +0000063261 00000 n +0000063324 00000 n +0000063387 00000 n +0000063450 00000 n +0000063513 00000 n +0000063576 00000 n +0000063639 00000 n +0000063702 00000 n +0000063765 00000 n +0000063828 00000 n +0000063890 00000 n +0000063953 00000 n +0000064016 00000 n +0000064079 00000 n +0000064142 00000 n +0000064205 00000 n +0000064268 00000 n +0000064330 00000 n +0000064393 00000 n +0000064456 00000 n +0000064519 00000 n +0000064582 00000 n +0000064707 00000 n +0000064830 00000 n +0000064893 00000 n +0000064956 00000 n +0000065018 00000 n +0000062269 00000 n +0000065143 00000 n +0000073124 00000 n +0000068925 00000 n +0000065317 00000 n +0000072811 00000 n +0000072936 00000 n +0000070044 00000 n +0000070277 00000 n +0000070509 00000 n +0000070740 00000 n +0000070979 00000 n +0000071204 00000 n +0000071426 00000 n +0000071657 00000 n +0000071883 00000 n +0000072113 00000 n +0000072362 00000 n +0000072586 00000 n +0000073061 00000 n +0000069841 00000 n +0000069976 00000 n +0000070023 00000 n +0000081019 00000 n +0000078194 00000 n +0000073263 00000 n +0000078316 00000 n +0000078379 00000 n +0000078442 00000 n +0000078505 00000 n +0000078568 00000 n +0000078631 00000 n +0000078693 00000 n +0000078756 00000 n +0000078819 00000 n +0000078882 00000 n +0000078945 00000 n +0000079008 00000 n +0000079071 00000 n +0000079134 00000 n +0000079197 00000 n +0000079260 00000 n +0000079321 00000 n +0000079384 00000 n +0000079447 00000 n +0000079510 00000 n +0000079573 00000 n +0000079636 00000 n +0000079699 00000 n +0000079762 00000 n +0000079825 00000 n +0000079888 00000 n +0000079951 00000 n +0000080013 00000 n +0000080076 00000 n +0000080139 00000 n +0000080202 00000 n +0000080265 00000 n +0000080328 00000 n +0000080391 00000 n +0000080454 00000 n +0000080517 00000 n +0000080580 00000 n +0000080642 00000 n +0000080705 00000 n +0000080768 00000 n +0000080831 00000 n +0000080894 00000 n +0000080957 00000 n +0000188339 00000 n +0000089223 00000 n +0000085806 00000 n +0000081117 00000 n +0000086206 00000 n +0000086269 00000 n +0000086332 00000 n +0000086395 00000 n +0000086458 00000 n +0000086521 00000 n +0000086583 00000 n +0000086646 00000 n +0000086709 00000 n +0000086772 00000 n +0000086835 00000 n +0000086898 00000 n +0000086960 00000 n +0000085948 00000 n +0000087085 00000 n +0000087148 00000 n +0000087211 00000 n +0000087274 00000 n +0000087337 00000 n +0000087400 00000 n +0000087463 00000 n +0000087526 00000 n +0000087588 00000 n +0000087651 00000 n +0000087714 00000 n +0000087777 00000 n +0000087840 00000 n +0000087903 00000 n +0000087966 00000 n +0000088029 00000 n +0000088092 00000 n +0000088155 00000 n +0000088217 00000 n +0000088280 00000 n +0000088343 00000 n +0000088406 00000 n +0000088469 00000 n +0000088532 00000 n +0000088595 00000 n +0000088658 00000 n +0000088721 00000 n +0000088784 00000 n +0000088847 00000 n +0000088910 00000 n +0000088973 00000 n +0000089035 00000 n +0000089098 00000 n +0000089161 00000 n +0000096604 00000 n +0000093840 00000 n +0000089334 00000 n +0000093962 00000 n +0000094025 00000 n +0000094088 00000 n +0000094151 00000 n +0000094214 00000 n +0000094277 00000 n +0000094340 00000 n +0000094402 00000 n +0000094465 00000 n +0000094528 00000 n +0000094591 00000 n +0000094654 00000 n +0000094717 00000 n +0000094780 00000 n +0000094843 00000 n +0000094906 00000 n +0000094969 00000 n +0000095032 00000 n +0000095094 00000 n +0000095157 00000 n +0000095220 00000 n +0000095283 00000 n +0000095346 00000 n +0000095409 00000 n +0000095472 00000 n +0000095535 00000 n +0000095597 00000 n +0000095660 00000 n +0000095723 00000 n +0000095786 00000 n +0000095849 00000 n +0000095912 00000 n +0000095975 00000 n +0000096038 00000 n +0000096101 00000 n +0000096164 00000 n +0000096227 00000 n +0000096289 00000 n +0000096352 00000 n +0000096415 00000 n +0000096478 00000 n +0000096541 00000 n +0000101390 00000 n +0000099696 00000 n +0000096702 00000 n +0000099818 00000 n +0000099881 00000 n +0000099944 00000 n +0000100007 00000 n +0000100070 00000 n +0000100133 00000 n +0000100196 00000 n +0000100259 00000 n +0000100322 00000 n +0000100385 00000 n +0000100447 00000 n +0000100572 00000 n +0000100697 00000 n +0000100760 00000 n +0000100823 00000 n +0000100886 00000 n +0000100949 00000 n +0000101012 00000 n +0000101075 00000 n +0000101138 00000 n +0000101201 00000 n +0000101264 00000 n +0000101327 00000 n +0000103626 00000 n +0000103602 00000 n +0000105415 00000 n +0000105390 00000 n +0000105505 00000 n +0000126814 00000 n +0000135494 00000 n +0000147236 00000 n +0000159026 00000 n +0000167336 00000 n +0000187626 00000 n +0000188440 00000 n +0000188518 00000 n +0000190524 00000 n +0000202016 00000 n +0000202055 00000 n +0000202093 00000 n +0000202222 00000 n +trailer +<< +/Size 654 +/Root 652 0 R +/Info 653 0 R +/ID [<624EFF68B3B6150ADBBC3276EFE85189> <624EFF68B3B6150ADBBC3276EFE85189>] +>> +startxref +202485 +%%EOF Added: trunk/docs/tutorial/tutorial.txt =================================================================== --- trunk/docs/tutorial/tutorial.txt (rev 0) +++ trunk/docs/tutorial/tutorial.txt 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,900 @@ +A Swift Tutorial +================ + +:toc: +:icons: +:website: http://www.ci.uchicago.edu/swift/guides/tutorial.php +:numbered: + +[abstract] +Abstract +-------- +This is an introductory tutorial on the use of Swift and its programming +language SwiftScript. + +Introduction +------------ +This tutorial is intended to introduce new users to the basics of Swift. +It is structured as a series of small exercise/examples which you can +try for yourself as you read along. After the first 'hello world' +example, there are two tracks - the language track (which introduces +features of the SwiftScript language) and the runtime track (which +introduces features of the Swift runtime environment, such as running +jobs on different sites). + +For information on getting an installation of Swift running, consult the +Swift Quickstart Guide , and +return to this document when you have successfully run the test +SwiftScript program mentioned there. + +There is also a Swift User's Guide + which contains +more detailed reference material on topics covered in this manual. All +of the programs included in this tutorial can be found in your Swift +distribution in the examples/swift directory. + +Hello World +----------- +The first example program, first.swift, outputs a hello world message +into a file called hello.txt. + +.first.swift +************ +[java] +source~~~~ +include::../../examples/first.swift[] +source~~~~ +************ + +We can run this program as follows: +[java] +source~~~~ +$ cd examples/swift/ +$ swift first.swift +Swift svn swift-r3334 (swift modified locally) cog-r2752 + +RunID: 20100526-1925-8zjupq1b +Progress: +Final status: Finished successfully:1 +$ cat hello.txt +Hello, world! +source~~~~ + +The basic structure of this program is a type definition, an +application procedure definition, a variable definition and then a +call to the procedure: + +[java] +source~~~~ +type messagefile; +source~~~~ + +First we define a new type, called messagefile. In this example, we will +use this messagefile type as the type for our output message. + + +All data in SwiftScript must be typed, whether it is stored in memory or +on disk. This example defines a very simple type. Later on we will see +more complex type examples. + +[java] +source~~~~ +app (messagefile t) greeting() { + echo "Hello, world!" stdout=@filename(t); +} +source~~~~ + +Next we define a procedure called greeting. This procedure will write +out the "hello world" message to a file. + +To achieve this, it executes the unix utility 'echo' with a parameter +"Hello, world!" and directs the standard output into the output file. + +The actual file to use is specified by the return parameter, t. + +messagefile outfile <"hello.txt">; + +Here we define a variable called outfile. The type of this variable is +messagefile, and we specify that the contents of this variable will be +stored on disk in a file called hello.txt + +outfile = greeting(); + +Now we call the greeting procedure, with its output going to the outfile +variable and therefore to hello.txt on disk. + +Over the following exercises, we'll extend this simple hello world +program to demonstrate various features of Swift. + + +Language features +----------------- + +Parameters +~~~~~~~~~~ + +Procedures can have parameters. Input parameters specify inputs to the +procedure and output parameters specify outputs. Our helloworld greeting +procedure already uses an output parameter, t, which indicates where the +greeting output will go. In this section, we will add an input parameter +to the greeting function. + +The code changes from first.swift are highlighted below. + +[java] +source~~~~ +include::../../examples/parameter.swift[] +source~~~~ + +We have modified the signature of the greeting procedure to indicate +that it takes a single parameter, s, of type 'string'. + +We have modified the invocation of the 'echo' utility so that it takes +the value of s as a parameter, instead of the string literal "Hello, +world!". + +We have modified the output file definition to point to a different file +on disk. + +We have modified the invocation of greeting so that a greeting string is +supplied. + +The code for this section can be found in parameter.swift. It can be +invoked using the swift command, with output appearing in hello2.txt: + +[java] +source~~~~ +$ swift parameter.swift +source~~~~ + +Now that we can choose our greeting text, we can call the same procedure +with different parameters to generate several output files with +different greetings. The code is in manyparam.swift and can be run as +before using the swift command. + +[java] +source~~~~ +include::../../examples/manyparam.swift[] +source~~~~ + +Note that we can intermingle definitions of variables with invocations +of procedures. + +When this program has been run, there should be three new files in the +working directory (english.txt, francais.txt and nihongo.txt) each +containing a greeting in a different language. + +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified - see <>. + +Adding another application +~~~~~~~~~~~~~~~~~~~~~~~~~~ +Now we'll define a new application procedure. The procedure we define +will capitalise all the words in the input file. + +To do this, we'll use the unix tr (translate) utility. Here is an +example of using tr on the unix command line, not using Swift: + +[java] +source~~~~ +$ echo hello | tr '[a-z]' '[A-Z]' +HELLO +source~~~~ + +.There are several steps +- transformation catalog +- application block + +First we need to modify the transformation catalog to define a logical +transformation for the tc utility. The transformation catalog can be +found in etc/tc.data. There are already several entries specifying +where programs can be found. Add a new line to the file, specifying +where *tr* can be found (usually in /usr/bin/tr but it may differ on +your system), like this: + +[java] +source~~~~ +localhost tr /usr/bin/tr INSTALLED INTEL32::LINUX null +source~~~~ + +For now, ignore all of the fields except the second and the third. The +second field tr specifies a logical application name and the third +specifies the location of the application executable. + +Now that we have defined where to find tr, we can use it in SwiftScript. + +We can define a new procedure, capitalise, which calls tr. + +[java] +source~~~~ +(messagefile o) capitalise(messagefile i) { + app { + tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); + } +} +source~~~~ +We can call capitalise like this: + +[java] +source~~~~ +messagefile final <"capitals.txt">; +final = capitalise(hellofile); +source~~~~ + +So a full program based on the first exercise might look like this: + +[java] +source~~~~ +include::../../examples/second_procedure.swift[] +source~~~~ + +We can use the swift command to run it like this. + +[java] +source~~~~ +$ swift second_procedure.swift +... +$ cat capitals.txt +HELLO FROM SWIFT +source~~~~ + +Anonymous files +~~~~~~~~~~~~~~~ +In the previous section, the file greeting.txt is used only to store +an intermediate result. We don't really care about which name is used +for the file, and we can let Swift choose the name. + +To do that, omit the mapping entirely when declaring outfile: + +[java] +source~~~~ +messagefile outfile; +source~~~~ + +Swift will choose a filename, which in the present version will be in a +subdirectory called _concurrent. + + +Datatypes +~~~~~~~~~ +All data in variables and files has a data type. So far, we've seen two +types: + + - string - this is a built-in type for storing strings of text in + memory, much like in other programming languages + - messagefile - this is a user-defined type used to mark files as + containing messages + +SwiftScript has the additional built-in types: boolean, integer and +float that function much like their counterparts in other programming +languages. + +It is also possible to create user defined types with more structure, +for example: + +[java] +source~~~~ +type details { + string name; + int pies; +} +source~~~~ + +Each element of the structured type can be accessed using a . like this: + +[java] +source~~~~ +person.name = "john"; +source~~~~ + +The following complete program, types.swift, outputs a greeting using a +user-defined structure type to hold parameters for the message: + +[java] +source~~~~ +include::../../examples/types.swift[] +source~~~~ + +Structured types can be comprised of marker types for files. See the +later section on mappers for more information about this. + + +Arrays +~~~~~~ + +We can define arrays using the [] suffix in a variable declaration: + +[java] +source~~~~ +messagefile m[]; +source~~~~ + +This program, q5.swift, will declare an array of message files. + +[java] +source~~~~ +include::../../examples/q5.swift[] +source~~~~ + +Observe that the type of the parameter to greeting is now an array of +strings, string s[], instead of a single string, string s, that +elements of the array can be referenced numerically, for example s[0], +and that the array is initialised using an array literal, +["how","are","you"]. + + +Mappers +~~~~~~~ + +A significant difference between SwiftScript and other languages is that +data can be referred to on disk through variables in a very similar +fashion to data in memory. For example, in the above examples we have +seen a variable definition like this: + +[java] +source~~~~ +messagefile outfile <"q13greeting.txt">; +source~~~~ + +This means that outfile is a dataset variable, which is mapped to a +file on disk called g13greeting.txt. This variable can be assigned to +using = in a similar fashion to an in-memory variable. We can say that +outfile is mapped onto the disk file q13greeting.txt by a mapper. + +There are various ways of mapping in SwiftScript. Two forms have already +been seen in this tutorial. Later exercises will introduce more forms. + +The two forms of mapping seen so far are: + +simple named mapping - the name of the file that a variable is mapped to +is explictly listed. Like this: + +[java] +source~~~~ +messagefile outfile <"greeting.txt">; +source~~~~ + +This is useful when you want to explicitly name input and output files +for your program. For example, outfile in exercise HELLOWORLD. + +anonymous mapping - no name is specified in the source code. A name is +automatically generated for the file. This is useful for intermediate +files that are only referenced through SwiftScript, such as outfile in +exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by +ommitting any mapper definition, like this: + +[java] +source~~~~ +messagefile outfile; +source~~~~ + +Later exercises will introduce other ways of mapping from disk files to +SwiftScript variables. + +TODO: introduce @v syntax. + + +The Regexp Mapper +^^^^^^^^^^^^^^^^^ +In this exercise, we introduce the regexp mapper. This mapper +transforms a string expression using a regular expression, and uses the +result of that transformation as the filename to map. + +regexp.swift demonstrates the use of this by placing output into a +file that is based on the name of the input file: our input file is +mapped to the inputfile variable using the simple named mapper, and then +we use the regular expression mapper to map the output file. Then we use +the countwords() procedure to count the works in the input file and +store the result in the output file. In order for the countwords() +procedure to work correctly, add the wc utility (usually found in +/usr/bin/wc) to tc.data. + +The important bit of regexp.swift is: + +[java] +source~~~~ +messagefile inputfile <"q16.txt">; + +countfile c ; +source~~~~ + +fixed_array_mapper +^^^^^^^^^^^^^^^^^^ +The fixed array mapper maps a list of files into an array - each +element of the array is mapped into one file in the specified directory. +See fixedarray.swift. + +[java] +source~~~~ +include::../../examples/fixedarray.swift[] +source~~~~ + +foreach +~~~~~~~ +SwiftScript provides a control structure, foreach, to operate on each +element of an array. + +In this example, we will run the previous word counting example over +each file in an array without having to explicitly list the array +elements. The source code for this example is in foreach.swift. The +three input files: one.txt, two.txt and three.txt are supplied. +After you have run the workflow, you should see that there are three +output files: one.count, two.count and three.count, each +containing the word count for the corresponding input file. We combine +the use of the fixed_array_mapper and the regexp_mapper. + +[java] +source~~~~ +include::../../examples/foreach.swift[] +source~~~~ + +If +~~ +Decisions can be made using 'if', like this: + +[java] +source~~~~ +if(morning) { + outfile = greeting("good morning"); +} else { + outfile = greeting("good afternoon"); +} +source~~~~ + +if.swift contains a simple example of this. Compile and run if.swift +and see that it outputs "good morning". Changing the morning variable +from true to false will cause the program to output "good afternoon". + +Sequential iteration +~~~~~~~~~~~~~~~~~~~~ + +A development version of Swift after 0.2 (revision 1230) introduces a +sequential iteration construct. + +The following example demonstrates a simple application: each step of +the iteration is a string representation of the byte count of the +previous step's output, with iteration terminating when the byte count +reaches zero. + +Here's the program: + +[java] +source~~~~ +include::../../examples/iterate.swift[] +source~~~~ + +echo is the standard unix echo. + +wcl is our application code - it counts the number of bytes in the one +file and writes that count out to another, like this: + +[java] +source~~~~ +$ cat ../wcl +#!/bin/bash +echo -n $(wc -c < $1) > $2 + +$ echo -n hello > a +$ wcl a b +$ cat b +5 +source~~~~ + +Install the above wcl script somewhere and add a transformation catalog +entry for it. Then run the example program like this: + +[java] +source~~~~ +$ swift iterate.swift +Swift svn swift-r3334 cog-r2752 + +RunID: 20100526-2259-gtlz8zf4 +Progress: +SwiftScript trace: extract int value , 16.0 +SwiftScript trace: extract int value , 2.0 +SwiftScript trace: extract int value , 1.0 +Final status: Finished successfully:4 + +$ ls foldout* +foldout0000 foldout0001 foldout0002 foldout0003 +source~~~~ + +Runtime features +---------------- + +Visualising the workflow as a graph +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +When running a workflow, its possible to generate a provenance graph at +the same time: + +[java] +source~~~~~ +$ swift -pgraph graph.dot first.swift +$ dot -ograph.png -Tpng graph.dot +source~~~~ + +graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org. + +Running on a remote site +~~~~~~~~~~~~~~~~~~~~~~~~ + +As configured by default, all jobs are run locally. In the previous +examples, we've invoked echo and tr executables from our SwiftScript +program. These have been run on the local system (the same computer on +which you ran swift). We can also make our computations run on a +remote resource. + +WARNING: This example is necessarily more vague than previous examples, +because its requires access to remote resources. You should ensure that +you can submit a job using the globus-job-run (or globusrun-ws?) +command(s). + +We do not need to modify any SwiftScript code to run on another +resource. Instead, we must modify another catalog, the site catalog. +This catalog provides details of the location that applications will be +run, with the default settings referring to the local machine. We will +modify it to refer to a remote resource - the UC Teraport cluster. If +you are not a UC Teraport user, you should use details of a different +resource that you do have access to. + +The site catalog is located in etc/sites.xml and is a relatively +straightforward XML format file. We must modify each of the following +three settings: gridftp (which indicates how and where data can be +transferred to the remote resource), jobmanager (which indicates how +applications can be run on the remote resource) and workdirectory (which +indicates where working storage can be found on the remote resource). + + +Writing a mapper +~~~~~~~~~~~~~~~~ + +This section will introduce writing a custom mapper so that Swift is +able to access data files laid out in application-specific ways. + +An application-specific mapper must take the form of a Java class that +implements the Mapper + +interface. + +Usually you don't need to implement this interface directly, because +Swift provides a number of more concrete classes with some functionality +already implemented. + +The hierarchy of helper classes is: + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/Mapper.html[Mapper] + +This is the abstract interface for mappers in Swift. You must +implement methods to provide access to mapper properties, to map from a +SwiftScript dataset path (such as foo[1].bar) to a file name, to check +whether a file exists. None of the default Swift mappers implement this +interface directly - instead they use one of the following helper classes. + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/AbstractMapper.html[Abstract Mapper] + +This provides helper methods to manage mapper properties and to handle +existance checking. Examples of mappers which use this class are: +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.array_mapper[Array Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.csv_mapper[CSV Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.fixed_array_mapper[Fixed Array Mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.regexp_mapper[Regexp Mapper], +and http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.single_file_mapper[Single File Mapper]. + +http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/file/AbstractFileMapper.html[AbstractFileMapper] +This provides a helper class for mappers which select files based on +selecting files from a directory listing. It is necessary to write some +helper methods that are different from the above mapper methods. +Examples of mappers which use this class are: +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.simple_mapper[simple_mapper], +http://www.ci.uchicago.edu/swift/guides/userguide.php#mapper.filesys_mapper[filesys_mapper], +and the (undocumented) StructuredRegularExpressionMapper. + +In general, to write a mapper, choose either the AbstractMapper or the +AbstractFileMapper and extend those. If your mapper will generally +select the files it returns based on a directory listing and will +convert paths to filenames using some regular conversion (for example, +in the way that simple_mapper maps files in a directory that match a +particular pattern), then you should probably use the +AbstractFileMapper. If your mapper will produce a list of files in some +other way (for example, in the way that csv_mapper maps based on +filenames given in a CSV file rather than looking at which files are in +a directory), then you should probably use the AbstractMapper. + + +Writing a very basic mapper +~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In this section, we will write a very basic (almost useless) mapper that +will map a SwiftScript dataset into a hardcoded file called +myfile.txt, like this: + + + Swift variable Filename + + var <-----------------------------> myfile.txt + +We should be able to use the mapper we write in a SwiftScript program +like this: + +[java] +source~~~~ +type file; +file f ; +source~~~~ + +First we must choose a base class - AbstractMapper or +AbstractFileMapper. We aren't going to use a directory listing to decide +on our mapping - we are getting the mapping from some other source (in +fact, it will be hard coded). So we will use AbstractMapper. + +So now onto the source code. We must define a subclass of AbstractMapper +and implement several mapper methods: isStatic, existing, and map. These +methods are documented in the javadoc for the Mapper interface. + +Here is the code implementing this mapper. Put this in your source +vdsk directory, make a directory src/tutorial/|and put this file in +src/tutorial/MyFirstMapper.java. + +[java] +source~~~~ +package tutorial; + +import java.util.Arrays; +import java.util.Collection; +import java.util.Collections; + +import org.griphyn.vdl.mapping.AbsFile; +import org.griphyn.vdl.mapping.AbstractMapper; +import org.griphyn.vdl.mapping.Path; +import org.griphyn.vdl.mapping.PhysicalFormat; + +public class MyFirstMapper extends AbstractMapper { + + AbsFile myfile = new AbsFile("myfile.txt"); + + public boolean isStatic() { + return false; + } + + public Collection existing() { + if (myfile.exists()) + return Arrays.asList(new Path[] {Path.EMPTY_PATH}); + else + return Collections.EMPTY_LIST; + } + + public PhysicalFormat map(Path p) { + if(p.equals(Path.EMPTY_PATH)) + return myfile; + else + return null; + } +} +source~~~~ + +Now we need to inform the Swift engine about the existence of this +mapper. We do that by editing the MapperFactory class definition, in +src/org/griphyn/vdl/mapping/MapperFactory.java and adding a +registerMapper call alongside the existing registerMapper calls, like this: + +[java] +source~~~~ +registerMapper("my_first_mapper", tutorial.MyFirstMapper.class); +source~~~~ + +The first parameter is the name of the mapper that will be used in +SwiftScript program. The second parameter is the new Mapper class that +we just wrote. + +Now rebuild Swift using the "ant redist" target. + +This new Swift build will be aware of your new mapper. We can test it +out with a hello world program: + +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting() { + app { + echo "hello" stdout=@filename(t); + } +} + +messagefile outfile ; + +outfile = greeting(); +source~~~~ + +Run this program, and hopefully you will find the "hello" string has +been output into the hard coded output file myfile.txt: + +[java] +source~~~~ +$ cat myfile.txt +hello +source~~~~ + +So that's a first very simple mapper implemented. Compare the source +code to the single_file_mapper in +http://www.ci.uchicago.edu/trac/swift/browser/trunk/src/org/griphyn/vdl/mapping/file/SingleFileMapper.java[SingleFileMapper.java]. +There is not much more code to the single_file_mapper - mostly code to +deal with the file parameter. + + +Starting and restarting +~~~~~~~~~~~~~~~~~~~~~~~ + +Now we're going to try out the restart capabilities of Swift. We will +make a workflow that will deliberately fail, and then we will fix the +problem so that Swift can continue with the workflow. + +First we have the program in working form, restart.swift. + +[java] +source~~~~ +include::../../examples/restart.swift[] +source~~~~ + +We must define some transformation catalog entries: + +[java] +source~~~~ +localhost touch /usr/bin/touch INSTALLED INTEL32::LINUX null +localhost broken /bin/true INSTALLED INTEL32::LINUX null +source~~~~ + +Now we can run the program: + +[java] +source~~~~ +$ swift restart.swift +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1119-3kgzzi15 +Progress: +Final status: Finished successfully:4 +source~~~~ + +Four jobs run - touch, echo, broken and a final echo. (note that broken +isn't actually broken yet). + +Now we will break the broken job and see what happens. Replace the +definition in tc.data for broken with this: + +[java] +source~~~~ +localhost broken /bin/false INSTALLED INTEL32::LINUX null +source~~~~ + +Now when we run the workflow, the broken task fails: + +[java] +source~~~~ +$ swift restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1121-tssdcljg +Progress: +Progress: Stage in:1 Finished successfully:2 +Execution failed: + Exception in broken: +Arguments: [process] +Host: localhost +Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj +stderr.txt: +stdout.txt: +source~~~~ + +From the output we can see that touch and the first echo completed, but +then broken failed and so swift did not attempt to execute the final echo. + +There will be a restart log with the same name as the RunID: + +[java] +source~~~~ +$ ls *20100526-1121-tssdcljg*rlog +restart-20100526-1121-tssdcljg.0.rlog +source~~~~ + +This restart log contains enough information for swift to know which +parts of the workflow were executed successfully. + +We can try to rerun it immediately, like this: + +[java] +source~~~~ +$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1125-7yx0zi6d +Progress: +Execution failed: + Exception in broken: +Arguments: [process] +Host: localhost +Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj +stderr.txt: +stdout.txt: + +---- + +Caused by: + Exit code 1 +source~~~~ + +Swift tried to resume the workflow by executing "broken" again. It did +not try to run the touch or first echo jobs, because the restart log +says that they do not need to be executed again. + +Broken failed again, leaving the original restart log in place. + +Now we will fix the problem with "broken" by restoring the original +tc.data line that works. + +Remove the existing "broken" line and replace it with the successful +tc.data entry above: + +[java] +source~~~~ +localhost broken /bin/true INSTALLED INTEL32::LINUX null +source~~~~ + +Now run again: + +[java] +source~~~~ +$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift + +Swift 0.9 swift-r2860 cog-r2388 + +RunID: 20100526-1128-a2gfuxhg +Progress: +Final status: Initializing:2 Finished successfully:2 +source~~~~ + +Swift tries to run "broken" again. This time it works, and so Swift +continues on to execute the final piece of the workflow as if nothing +had ever gone wrong. + + +bits +---- + +Named and optional parameters +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +anchor:named_parameters +In addition to specifying parameters positionally, parameters can be +named, and if desired a default value can be specified: + +[java] +source~~~~ +(messagefile t) greeting (string s="hello") { + app { + echo s stdout=@filename(t); + } +} +source~~~~ + +When we invoke the procedure, we can specify values for the parameters +by name. The following code can be found in q21.swift. + +[java] +source~~~~ +french = greeting(s="bonjour"); +source~~~~ + +or we can let the default value apply: + +[java] +source~~~~ +english = greeting(); +source~~~~ Deleted: trunk/docs/tutorial-live.xml =================================================================== --- trunk/docs/tutorial-live.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/tutorial-live.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,982 +0,0 @@ - - - -
    - - A Swift Tutorial for ISSGC07 - - - Introduction - -This tutorial is intended to introduce new users to the basics of Swift. -It is structured as a series of small exercise/examples which you can -try for yourself as you read along. - - This is version: $LastChangedRevision$ - - -Environment setup - -First set up the swift environment: - - - -$ cp ~benc/workflow/vdsk-0.1-r877/etc/tc.data ~ -$ cp ~benc/workflow/vdsk-0.1-r877/etc/sites.xml ~ -$ export PATH=$PATH:~benc/workflow/vdsk-0.1-r877/bin - - - - - A first workflow - -The first example program uses an image processing utility to perform -a visual special effect on a supplied file. - - -Here is the program we will use: - - - -type imagefile; - -(imagefile output) flip(imagefile input) { - app { - convert "-rotate" "180" @input @output; - } -} - -imagefile puppy <"input-1.jpeg">; -imagefile flipped <"output.jpeg">; - -flipped = flip(puppy); - - - - - -This simple workflow has the effect of running this command: -convert -rotate 180 input-1.jpeg output.jpeg - - -ACTION: First prepare your working environment: - - - -$ cp ~benc/workflow/input-1.jpeg . - -$ ls *.jpeg -input-1.jpeg - - - -ACTION: Open input-1.jpeg - - -You should see a picture. This is the -picture that we will modify in our first workflow. - - -ACTION: use your favourite text editor to put the above SwiftScript -program into a file called -flipper.swift - - -Once you have put the program into flipper.swift, you can execute -the workflow like this: - - - - -$ swift flipper.swift - -Swift v0.1-dev - -RunID: e1bupgygrzn12 -convert started -convert completed - -$ ls *.jpeg -input-1.jpeg -output.jpeg - - -A new jpeg has appeared - output.jpeg. - -ACTION: Open it. -You should see that the image is different from the input image - it -has been rotated 180 degress. - -The basic structure of this program is a type definition, -a procedure definition, a variable definition and -then a call to the procedure: - - -All data in SwiftScript must have a type. This line defines a new type -called imagefile, which will be the type that all of our images will be. - - - -type imagefile; - - - -Next we define a procedure called flip. This procedure will use the -ImageMagick convert application to rotate a picture around by 180 degrees. - - - -(imagefile output) flip(imagefile input) { - app { - convert "-rotate" "180" @input @output; - } -} - - - -To achieve this, it executes the ImageMagick utility 'convert', passing -in the appropriate commandline option and the name of the input and output -files. - - - -In swift, the output of a program looks like a return value. -It has a type, and also has a variable name -(unlike in most other programming languages). - - - -imagefile puppy <"input-1.jpeg">; -imagefile flipped <"output.jpeg">; - - - -We define two variables, called puppy and flipped. These variables will -contain our input and output images, respectively. - - -We tell swift that the contents of the variables will be stored on -disk (rather than in memory) in the files "input-1.jpeg" (which already -exists), and in "output.jpeg". This is called mapping -and will be discussed in more depth later. - - -flipped = flip(puppy); - - - -Now we call the flip procedure, with 'puppy' as its input and its -output going into 'flipped'. - - -Over the following exercises, we will use this relatively -simple SwiftScript program as a base for future exercises. - - - -A second program - - -Our next example program uses some more swift syntax to produce images that are -rotated by different angles, instead of flipped over all the way. - - -Here is the program in full. We'll go over it section by section. - -type imagefile; - -(imagefile output) rotate(imagefile input, int angle) { - app { - convert "-rotate" angle @input @output; - } -} - -imagefile puppy <"input-1.jpeg">; - -int angles[] = [45, 90, 120]; - -foreach a in angles { - imagefile output <single_file_mapper;file=@strcat("rotated-",a,".jpeg")>; - output = rotate(puppy, a); -} - - - -type imagefile; - - - -We keep the type definition the same as in the previous program. - - - -(imagefile output) rotate(imagefile input, int angle) { - app { - convert "-rotate" angle @input @output; - } -} - - - -This rotate procedure looks very much like the flip procedure -from the previous program, -but we have added another parameter, called angle. Angle is of type 'int', -which is a built-in SwiftScript type for integers. We use that on the -commandline instead of a hard coded 180 degrees. - - - -imagefile puppy <"input-1.jpeg">; - - - -Our input image is the same as before. - - - -int angles[] = [45, 90, 120]; - - - -Now we define an array of integers, and initialise it with three angles. - - - -foreach a in angles { - - - -Now we have a foreach loop. This loop will iterate over each of the elements -in angles. In each iteration, the element will be put in the variable 'a'. - - - - imagefile output <single_file_mapper;file=@strcat("rotated-",a,".jpeg")>; - - - -Inside the loop body, we have an output variable that is mapped differently -for each iteration. We use the single_file_mapper and the @strcat function -to construct a filename and then map that filename to our output variable. - - - - output = rotate(puppy, a); -} - - -Now we invoke rotate, passing in our input image and the angle to -use, and putting the output in the mapped output file. This will happen -three times, with a different output filename and a different angle -each time. - - - -ACTION: Put the program source into a file called in rotate.swift and -execute it with the swift command, like we did for flipper.swift above. - - - -$ ls rotated* -rotated-120.jpeg rotated-45.jpeg rotated-90.jpeg - - - - - -Third example - - -Our third example will introduce some more concepts: complex data -types, the comma-separated values mapper, and the transformation -catalog. - - - -Here's the complete listing: - - - - -type imagefile; -type pgmfile; - -type voxelfile; -type headerfile; - -type volume { - voxelfile img; - headerfile hdr; -}; - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile output) convert(pgmfile inpgm) -{ - app { - convert @inpgm @output; - } -} - -pgmfile slice; - -imagefile slicejpeg <"slice.jpeg">; - -slice = slicer(reference, "-x", ".5"); - -slicejpeg = convert(slice); - - - -IMPORTANT! We need to make some changes to other files in addition -to putting the above source into a file. Read the following notes -carefully to find out what to change. - - -type imagefile; -type pgmfile; -type voxelfile; -type headerfile; - - - -We define some simple types - imagefile as before, as well as three new ones. - - - -type volume { - voxelfile img; - headerfile hdr; -}; - - - -Now we define a complex type to represent a brain scan. -Our programs store brain data in two files - a .img file and a .hdr file. -This complex type defines a volume type, consisting of a voxelfile and a -headerfile. - - - -volume references[] <csv_mapper;file="reference.csv">; - - - -Now that we have defined a more complex type that consists of several -elements (and hence several files on disk), we can no longer use the -same ways of mapping. Instead, we will use a new mapper, the CSV mapper. -This maps rows of a comma-separated value file into an array of complex -types. - -ACTION: Make a file called reference.csv using your -favourite text editor. This is what it should look contain (2 lines): - - -img,hdr -Raw/reference.img,Raw/reference.hdr - -Our mapped structure will be a 1 element array (because there was one -data line in the CSV file), and that element will be mapped to two -files: the img component will map to the file Raw/reference.img and the -hdr component will map to Raw/reference.hdr - - -We also need to put the Raw/reference files into the current directory -so that swift can find them. - -ACTION REQUIRED: Type the following: - - -$ mkdir Raw -$ cp ~benc/workflow/data/reference.* Raw/ - - -Now you will have the reference files in your home directory. - - - -volume reference=references[0]; - - - -We only want the single first element of the references array, so this line -makes a new volume variable and extracts the first element of references. - - - -(imagefile output) convert(pgmfile inpgm) -{ - app { - convert @inpgm @output; - } -} - - - -This procedure is like the previous flip and rotate procedures. It uses -convert to change a file from one file format (.pgm format) to another -format (.jpeg format) - - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - - - -Now we define another procedure that uses a new application called 'slicer'. -Slicer will take a slice through a supplied brain scan volume and produce -a 2d image in PGM format. - - - -We must tell Swift how to run 'slicer' by modifying the -transformation catalog. The transformation catalog -maps logical transformation names into unix executable names. - - -The transformation catalog is in your home directory, in a file called -tc.data. -There is already one entry there, for convert. - - -localhost convert /usr/bin/convert INSTALLED INTEL32::LINUX null - - -ACTION REQUIRED: Open tc.data in your favourite unix text -editor, and add a new line to configure the location of slicer. Note that -you must use TABS and not spaces to separate the fields: - - -localhost slicer /afs/pdc.kth.se/home/b/benc/workflow/slicer-swift INSTALLED INTEL32::LINUX null - - -For now, ignore all of the fields except the second and the third. -The second field 'slicer' specifies a logical transformation name and the -third specifies the location of an executable to perform that -transformation. - - -pgmfile slice; - - - -Now we define a variable which will store the sliced image. It will be -a file on disk, but note that there is no filename mapping defined. This -means that swift will choose a filename automatically. This is useful for -intermediate files in a workflow. - - - -imagefile slicejpeg <"slice.jpeg">; - - -Now we declare a variable for our output and map it to a filename. - - - -slice = slicer(reference, "-x", ".5"); - -slicejpeg = convert(slice); - - - -Finally we invoke the two procedures to slice the brain volume and -then convert that slice into a jpeg. - - -ACTION: Place the source above into a file (for example, third.swift) and -make the other modifications discussed above. Then run the workflow -with the swift command, as before. - - - -Running on another site - - -So far everything has been run on the local site. -Swift can run jobs over the grid to remote resources. It will handle the -transfer of files to and from the remote resource, and execution of jobs -on the remote resource. - - - -We will run the first flip program, but this time on a grid resource -located in chicago. - - - -First clear away the output from the first program: - - - -$ rm output.jpeg -$ ls output.jpeg -ls: output.jpeg: No such file or directory - - - -Now initialise your grid proxy, to log-in to the grid. - - - -$ grid-proxy-init - - -Now we must tell Swift about the other site. This is done through -another catalog file, the site catalog. - -The site catalog is found in sites.xml - -Open sites.xml. There is one entry in there in XML defining the -local site. Because this is the only site defined, all execution will -happen locally. - -Another sites.xml is available for use, in -~benc/workflow/sites-iceage.xml - - -ACTION: Copy ~benc/workflow/sites-iceage.xml to your home directory - and look inside. See how it differs from sites.xml. - -Now we will run the first flipper exercise again, but this time via -Globus GRAM. - -We will use this other sites file to run the first workflow. In -addition to telling swift about the other site in the sites file, -we need to tell swift where to find transformations on the new site. - -ACTION: Edit the transformation catalog and add a line to tell swift where -it can find convert. Conveniently, it is in the same path when running -locally and through GRAM. -Here is the line to add: - - - -iceage convert /usr/bin/convert INSTALLED INTEL32::LINUX null - - -Note the different between this line and the existing convert -definition in the file. All fields are the same except for the first -column, which is the site column. We say 'iceage' here instead of -localhost. This matches up with the site name 'iceage' defined in -the new site catalog, and identifies the name of the remote site. - - -Now use the same swift command as before, but with an -extra parameter to tell swift to use a different sites file: - - - -$ swift -sites.file ~benc/workflow/sites-iceage.xml flipper.swift - - - -If this runs successfully, you should now have an output.jpeg file with -a flipped picture in it. It should look exactly the same as when run locally. -You have used the same program to produce the same output, but used a remote -resource to do it. - - - - - - - -A bigger workflow example - -Now we'll make a bigger workflow that will execute a total of -15 jobs. - - - -As before, here is the entire program listing. Afterwards, we will go through -the listing step by step. - - - -type voxelfile; -type headerfile; - -type pgmfile; -type imagefile; - -type warpfile; - -type volume { - voxelfile img; - headerfile hdr; -}; - -(warpfile warp) align_warp(volume reference, volume subject, string model, string quick) { - app { - align_warp @reference.img @subject.img @warp "-m " model quick; - } -} - -(volume sliced) reslice(warpfile warp, volume subject) -{ - app { - reslice @warp @sliced.img; - } -} - -(volume sliced) align_and_reslice(volume reference, volume subject, string model, string quick) { - warpfile warp; - warp = align_warp(reference, subject, model, quick); - sliced = reslice(warp, subject); -} - - -(volume atlas) softmean(volume sliced[]) -{ - app { - softmean @atlas.img "y" "null" @filenames(sliced[*].img); - } -} - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile outimg) convert(pgmfile inpgm) -{ - app { - convert @inpgm @outimg; - } -} - -(imagefile outimg) slice_to_jpeg(volume inp, string axis, string position) -{ - pgmfile outslice; - outslice = slicer(inp, axis, position); - outimg = convert(outslice); -} - -(volume s[]) all_align_reslices(volume reference, volume subjects[]) { - - foreach subject, i in subjects { - s[i] = align_and_reslice(reference, subjects[i], "12", "-q"); - } - -} - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - -volume subjects[] <csv_mapper;file="subjects.csv">; - -volume slices[] <csv_mapper;file="slices.csv">; -slices = all_align_reslices(reference, subjects); - -volume atlas <simple_mapper;prefix="atlas">; -atlas = softmean(slices); - -string directions[] = [ "x", "y", "z"]; - -foreach direction in directions { - imagefile o <single_file_mapper;file=@strcat("atlas-",direction,".jpeg")>; - string option = @strcat("-",direction); - o = slice_to_jpeg(atlas, option, ".5"); -} - - - - -As before, there are some other changes to make to the environment -in addition to running the program. These are discussed inline below. - - - -type voxelfile; -type headerfile; - -type pgmfile; -type imagefile; - -type warpfile; - - - -We define some simple types, like in the previous programs. We add another -one for a new kind of intermediate file - a warpfile, which will be used by -some new applications that we will use. - - - - -type volume { - voxelfile img; - headerfile hdr; -}; - - - -The same complex type as before, a volume consisting of a pair of files - -the voxel data and the header data. - - - - -(warpfile warp) align_warp(volume reference, volume subject, string model, string quick) { - app { - align_warp @reference.img @subject.img @warp "-m " model quick; - } -} - - - - -Now we define a new transformation called align_warp. We haven't used -align_warp before, so we need to add in a transformation catalog entry -for it. We will be adding some other transformations too, so add those -entries now too. - - - -ACTION: Edit the transformation catalog (like in the third -exercise). Add entries for the following transformations. The table -below lists the path. You must write the appropriate syntax for -transformation catalog entries yourself, using the existing two -entries as examples. - - -Here is the list of transformations to add: - -align_warp (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/AIR/bin/align_warp) -reslice (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/AIR/bin/reslice) -softmean (the path is /afs/pdc.kth.se/home/b/benc/workflow/app/softmean-swift) - - - -These programs come from several software packages: -the AIR (Automated Image Registration) suite -http://bishopw.loni.ucla.edu/AIR5/index.html and -FSL http://www.fmrib.ox.ac.uk/fsl/fsl/intro.html - - -Make sure you have added three entries to the transformation -catalog, listing the above three transformations and the appropriate -path - - - -(volume sliced) reslice(warpfile warp, volume subject) -{ - app { - reslice @warp @sliced.img; - } -} - - - - -This adds another transformation, called reslice. We already added the -transformation catalog entry for this, in the previous step. - - - - - -(volume sliced) align_and_reslice(volume reference, volume subject, string model, string quick) { - warpfile warp; - warp = align_warp(reference, subject, model, quick); - sliced = reslice(warp, subject); -} - - - - -This is a new kind of procedure, called a compound -procedure. A compound procedure does not call applications -directly. Instead it calls other procedures, connecting them together -with variables. This procedure above calls align_warp and then reslice. - - - - -(volume atlas) softmean(volume sliced[]) -{ - app { - softmean @atlas.img "y" "null" @filenames(sliced[*].img); - } -} - - - - -Yet another application procedure. Again, we added the transformation catalog -entry for this above. Note the special @filenames ... [*] syntax. - - - - -(pgmfile outslice) slicer(volume input, string axis, string position) -{ - app { - slicer @input.img axis position @outslice; - } -} - -(imagefile outimg) convert(pgmfile inpgm) -{ - app { - convert @inpgm @outimg; - } -} - - - -These are two more straightforward application transforms - - - -(imagefile outimg) slice_to_jpeg(volume inp, string axis, string position) -{ - pgmfile outslice; - outslice = slicer(inp, axis, position); - outimg = convert(outslice); -} - -(volume s[]) all_align_reslices(volume reference, volume subjects[]) { - - foreach subject, i in subjects { - s[i] = align_and_reslice(reference, subjects[i], "12", "-q"); - } - -} - - - - -slice_to_jpeg and all_align_reslices are compound procedures. They call -other procedures, like align_and_reslice did above. Note how -all_align_reslices uses foreach to run the same procedure on each element -in an array. - - - -volume references[] <csv_mapper;file="reference.csv">; -volume reference=references[0]; - - -The same mapping we used in the previous exercise to map a pair -of reference files into the reference variable using a complex type. - - - -volume subjects[] <csv_mapper;file="subjects.csv">; - - - -Now we map a number of subject images into the subjects array. - - -ACTION REQUIRED: Copy the subjects data files into your -working directory, like this: - - - -$ cp ~benc/workflow/data/anatomy* Raw/ -$ ls Raw/ -anatomy1.hdr anatomy2.hdr anatomy3.hdr anatomy4.hdr reference.hdr -anatomy1.img anatomy2.img anatomy3.img anatomy4.img reference.img - - -ACTION REQUIRED: Create a text file called subjects.csv using your -favourite text editor. List all four image pairs. Here is an example -of how to start: - - - -img,hdr -Raw/anatomy1.img,Raw/anatomy1.hdr -Raw/anatomy2.img,Raw/anatomy2.hdr - - - -Put the above text in students.csv and also add two new lines to list -anatomy data sets 3 and 4. - - - -volume slices[] <csv_mapper;file="slices.csv">; - - - -Slices will hold intermediate volumes that have been processed by some -of our tools. We need to map to tell swift where to put these intermediate -files. Because we need the filenames to correspond, we cannot use -anonymous mapping for these intermediate values like in the second -exercise. We need to populate slices.csv, but we do not need to find -the corresponding files. Swift will create these files as part of -executing the workflow. - - -ACTION REQUIRED: Create a text file called slices.csv with your -text editor, and put the following content into it: - - - -img,hdr -slice1.img,slice1.hdr -slice2.img,slice2.hdr -slice3.img,slice3.hdr -slice4.img,slice4.hdr - - - -slices = all_align_reslices(reference, subjects); - -volume atlas <simple_mapper;prefix="atlas">; -atlas = softmean(slices); - -string directions[] = [ "x", "y", "z"]; - -foreach direction in directions { - imagefile o <single_file_mapper;file=@strcat("atlas-",direction,".jpeg")>; - string option = @strcat("-",direction); - o = slice_to_jpeg(atlas, option, ".5"); -} - - - -Finally we make a number of actual procedure invocations (and declare a few -more variables). The ultimate output of our workflow comes from the o -variable inside the foreach look. This is mapped to a different filename -in each iteration, similar to exercise two. - - - -ACTION: -Put the workflow into a file called final.swift, and -then run the workflow with the swift command. Then open -the resulting files - atlas-x.jpeg, atlas-y.jpeg and atlas-z.jpeg. - - -You should see three brain images, along three different axes. - - - - -The End -
    - Deleted: trunk/docs/tutorial.xml =================================================================== --- trunk/docs/tutorial.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/tutorial.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,1317 +0,0 @@ - - - -
    - - A Swift Tutorial - - - -This is an introductory tutorial on the use of Swift and its -programming language SwiftScript. - - -$LastChangedRevision$ - - - - - -
    Introduction - -This tutorial is intended to introduce new users to the basics of Swift. -It is structured as a series of small exercise/examples which you can -try for yourself as you read along. After the first 'hello world' -example, there are two tracks - the language track (which introduces -features of the SwiftScript language) and the runtime track (which -introduces features of the Swift runtime environment, such as -running jobs on different sites) - - -For information on getting an installation of Swift running, consult the -Swift Quickstart Guide, -and return to this document when you have -successfully run the test SwiftScript program mentioned there. - - -There is also a -Swift User's Guide -which contains more detailed reference -material on topics covered in this manual. - -All of the programs included in this tutorial can be found in your Swift distribution in the examples/swift directory. - -
    - -
    Hello World - -The first example program, -first.swift, -outputs a hello world message into -a file called hello.txt. - - - -type messagefile; - -app (messagefile t) greeting () { - echo "Hello, world!" stdout=@filename(t); -} - -messagefile outfile <"hello.txt">; - -outfile = greeting(); - - -We can run this program as follows: - - -$ cd examples/swift/ -$ swift first.swift -Swift svn swift-r3334 (swift modified locally) cog-r2752 - -RunID: 20100526-1925-8zjupq1b -Progress: -Final status: Finished successfully:1 -$ cat hello.txt -Hello, world! - - -The basic structure of this program is a -type definition, -an application procedure definition, -a variable definition and -then a call to the procedure: - - - -type messagefile; - - - -First we define a new type, called messagefile. -In this example, we will use this messagefile -type as the type for our output message. - - -All data in SwiftScript must be typed, -whether it is stored in memory or on disk. This example defines a -very simple type. Later on we will see more complex type examples. - - - - - -app (messagefile t) greeting() { - echo "Hello, world!" stdout=@filename(t); -} - - - -Next we define a procedure called greeting. This procedure will write out -the "hello world" message to a file. - - - -To achieve this, it executes the unix utility 'echo' with a parameter -"Hello, world!" and directs the standard output into the output file. - - - -The actual file to use is specified by the -return parameter, t. - - - -messagefile outfile <"hello.txt">; - - - -Here we define a variable called outfile. The type of this variable is -messagefile, and we specify that the contents of this variable will -be stored on disk in a file called hello.txt - - - -outfile = greeting(); - - - -Now we call the greeting procedure, with its output going to the -outfile variable and therefore to hello.txt on disk. - - -Over the following exercises, we'll extend this simple -hello world program to demonstrate various features of Swift. - -
    - -
    Language features - -
    Parameters - - -Procedures can have parameters. Input parameters specify inputs to the -procedure and output parameters specify outputs. Our helloworld greeting -procedure already uses an output parameter, t, which indicates where the -greeting output will go. In this section, we will add an input parameter -to the greeting function. -The code changes from first.swift -are highlighted below. - - -type messagefile; - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -messagefile outfile <"hello2.txt">; - -outfile = greeting("hello world"); - - -We have modified the signature of the greeting procedure to indicate -that it takes a single parameter, s, of type 'string'. -We have modified the invocation of the 'echo' utility so that it -takes the value of s as a parameter, instead of the string literal -"Hello, world!". -We have modified the output file definition to point to a different -file on disk. -We have modified the invocation of greeting so that a greeting -string is supplied. - -The code for this section can be found in -parameter.swift. It can be -invoked using the swift command, with output appearing in -hello2.txt: - - -$ swift parameter.swift - - -Now that we can choose our greeting text, we can call the same -procedure with different parameters to generate several output files with -different greetings. The code is in manyparam.swift and can be run as before -using the swift command. - - - -type messagefile; - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -messagefile english <"english.txt">; -messagefile french <"francais.txt">; -english = greeting("hello"); -french = greeting("bonjour"); - -messagefile japanese <"nihongo.txt">; -japanese = greeting("konnichiwa"); - - -Note that we can intermingle definitions of variables with invocations -of procedures. -When this program has been run, there should be three new files in the -working directory (english.txt, francais.txt and nihongo.txt) each containing -a greeting in a different language. - -In addition to specifying parameters positionally, parameters can -be named, and if desired a default value can be specified - see -Named and optional -parameters. -
    -
    Adding another application - -Now we'll define a new application procedure. The procedure we define -will capitalise all the words in the input file. - - -To do this, we'll use the unix 'tr' (translate) utility. - -Here is an example of using tr on the unix -command line, not using Swift: - - -$ echo hello | tr '[a-z]' '[A-Z]' -HELLO - - - -There are several steps: - -transformation catalog -application block - - - -First we need to modify the -transformation catalog to define -a logical transformation for the tc utility. The transformation -catalog can be found in etc/tc.data. -There are already several entries specifying where programs can -be found. Add a new line to the file, specifying where -tr can be found -(usually in /usr/bin/tr -but it may differ on your system), like this: - - - -localhost tr /usr/bin/tr INSTALLED INTEL32::LINUX null - - -For now, ignore all of the fields except the second and the third. -The second field 'tr' specifies a logical application name and the -third specifies the location of the application executable. - - -Now that we have defined where to find tr, we can -use it in SwiftScript. - - - -We can define a new procedure, capitalise which calls -tr. - -(messagefile o) capitalise(messagefile i) { - app { - tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); - } -} - - - - - -We can call capitalise like this: - -messagefile final <"capitals.txt">; -final = capitalise(hellofile); - - - - -So a full program based on the first exercise might look like this: - - -type messagefile {} - -(messagefile t) greeting (string s) { - app { - echo s stdout=@filename(t); - } -} - -(messagefile o) capitalise(messagefile i) { - app { - tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); - } -} - -messagefile hellofile <"hello.txt">; -messagefile final <"capitals.txt">; - -hellofile = greeting("hello from Swift"); -final = capitalise(hellofile); - - - -We can use the swift command to run this: - - -$ swift second_procedure.swift -[...] -$ cat capitals.txt -HELLO FROM SWIFT - - - -
    - -
    Anonymous files - -In the previous section, the file -greeting.txt is used only to -store an intermediate result. We don't really care about which name is used -for the file, and we can let Swift choose the name. - -To do that, omit the mapping entirely when declaring outfile: - -messagefile outfile; - - - - -Swift will choose a filename, which in the present version will be -in a subdirectory called _concurrent. - - -
    - -
    Datatypes - - -All data in variables and files has a data type. So -far, we've seen two types: - - -string - this is a built-in type for storing strings of text in -memory, much like in other programming languages -messagefile - this is a user-defined type used to mark -files as containing messages - - - - -SwiftScript has the additional built-in types: -boolean, integer and -float that function much like their counterparts -in other programming languages. - - -It is also possible to create user defined types with more -structure, for example: - -type details { - string name; - int pies; -} - -Each element of the structured type can be accessed using a . like this: - -person.name = "john"; - - - - -The following complete program, types.swift, outputs a greeting using a user-defined -structure type to hold parameters for the message: - - -type messagefile {} - -type details { - string name; - int pies; -} - -(messagefile t) greeting (details d) { - app { - echo "Hello. Your name is" d.name "and you have eaten" d.pies "pies." stdout=@filename(t); - } -} - -details person; - -person.name = "John"; -person.pies = 3; - -messagefile outfile <"q15.txt>"; - -outfile = greeting(person); - - - - -Structured types can be comprised of marker types for files. See the later -section on mappers for more information about this. - - -
    - -
    Arrays -We can define arrays using the [] suffix in a variable declaration: - -messagefile m[]; - -This program, q5.swift, will declare an array of message files. - - - -type messagefile; - -(messagefile t) greeting (string s[]) { - app { - echo s[0] s[1] s[2] stdout=@filename(t); - } -} - -messagefile outfile <"q5out.txt">; - -string words[] = ["how","are","you"]; - -outfile = greeting(words); - - - -Observe that the type of the parameter to greeting is now an -array of strings, 'string s[]', instead of a single string, 'string s', -that elements of the array can be referenced numerically, for example -s[0], and that the array is initialised using an array literal, -["how","are","you"]. - -
    - -
    Mappers - -A significant difference between SwiftScript and other languages is -that data can be referred to on disk through variables in a very -similar fashion to data in memory. For example, in the above -examples we have seen a variable definition like this: - - -messagefile outfile <"q13greeting.txt">; - - -This means that 'outfile' is a dataset variable, which is -mapped to a file on disk called 'g13greeting.txt'. This variable -can be assigned to using = in a similar fashion to an in-memory -variable. We can say that 'outfile' is mapped onto the disk file -'q13greeting.txt' by a mapper. - - -There are various ways of mapping in SwiftScript. Two forms have already -been seen in this tutorial. Later exercises will introduce more forms. - - -The two forms of mapping seen so far are: - - - -simple named mapping - the name of the file that a variable is -mapped to is explictly listed. Like this: - -messagefile outfile <"greeting.txt">; - - -This is useful when you want to explicitly name input and output -files for your program. For example, 'outfile' in exercise HELLOWORLD. - - - - -anonymous mapping - no name is specified in the source code. -A name is automatically generated for the file. This is useful -for intermediate files that are only referenced through SwiftScript, -such as 'outfile' in exercise ANONYMOUSFILE. A variable declaration -is mapped anonymously by ommitting any mapper definition, like this: - - -messagefile outfile; - - - - - - -Later exercises will introduce other ways of mapping from -disk files to SwiftScript variables. - -TODO: introduce @v syntax. - -
    The regexp mapper -In this exercise, we introduce the regexp mapper. -This mapper transforms a string expression using a regular expression, -and uses the result of that transformation as the filename to map. - -regexp.swift demonstrates the use of this by placing output into a file that -is based on the name of the input file: our input file is mapped -to the inputfile variable using the simple named mapper, and then -we use the regular expression mapper to map the output file. Then we -use the countwords() procedure to count the works in the input file and -store the result in the output file. In order for the countwords() procedure -to work correctly, add the wc utility (usually found in /usr/bin/wc) to tc.data. - - - -The important bit of regexp.swift is: - -messagefile inputfile <"q16.txt">; - -countfile c <regexp_mapper; - source=@inputfile, - match="(.*)txt", - transform="\\1count" - >; - - -
    - -
    fixed_array_mapper - -The fixed array mapper maps a list of files into -an array - each element of the array is mapped into one file in the -specified directory. See fixedarray.swift. - - -string inputNames = "one.txt two.txt three.txt"; -string outputNames = "one.count two.count three.count"; - -messagefile inputfiles[] <fixed_array_mapper; files=inputNames>; -countfile outputfiles[] <fixed_array_mapper; files=outputNames>; - -outputfiles[0] = countwords(inputfiles[0]); -outputfiles[1] = countwords(inputfiles[1]); -outputfiles[2] = countwords(inputfiles[2]); - -
    - -
    - -
    foreach -SwiftScript provides a control structure, foreach, to operate -on each element of an array. -In this example, we will run the previous word counting example -over each file in an array without having to explicitly list the -array elements. The source code for this example is in -foreach.swift. The three input files -(one.txt, two.txt and -three.txt) are supplied. After -you have run the workflow, you should see that there are three output -files (one.count, two.count -and three.count) each containing the word -count for the corresponding input file. We combine the use of the -fixed_array_mapper and the regexp_mapper. - -string inputNames = "one.txt two.txt three.txt"; - -messagefile inputfiles[] <fixed_array_mapper; files=inputNames>; - - -foreach f in inputfiles { - countfile c <regexp_mapper; - source=@f, - match="(.*)txt", - transform="\\1count">; - c = countwords(f); -} - - -
    - -
    If - -Decisions can be made using 'if', like this: - - - -if(morning) { - outfile = greeting("good morning"); -} else { - outfile = greeting("good afternoon"); -} - - - - if.swift contains a simple example of -this. Compile and run if.swift and see that it -outputs 'good morning'. Changing the 'morning' -variable from true to false will cause the program to output 'good -afternoon'. - -
    - -
    Sequential iteration -A development version of Swift after 0.2 (revision 1230) introduces -a sequential iteration construct. - -The following example demonstrates a simple application: each step of the -iteration is a string representation of the byte count of the previous -step's output, with iteration terminating when the byte count reaches zero. - - - -Here's the program: - - - -type counterfile; - -(counterfile t) echo(string m) { - app { - echo m stdout=@filename(t); - } -} - -(counterfile t) countstep(counterfile i) { - app { - wcl @filename(i) @filename(t); - } -} - -counterfile a[] <simple_mapper;prefix="foldout">; - -a[0] = echo("793578934574893"); - -iterate v { - a[v+1] = countstep(a[v]); - trace("extract int value ", at extractint(a[v+1])); -} until (@extractint(a[v+1]) <= 1); - - - - -echo is the standard unix echo. - - wcl -is our application code - it counts the number of bytes in the one file -and writes that count out to another, like this: - - -$ cat ../wcl -#!/bin/bash -echo -n $(wc -c < $1) > $2 - -$ echo -n hello > a -$ wcl a b -$ cat b -5 - - -Install the above wcl script somewhere and add a transformation catalog -entry for it. Then run the example program like this: - - - -$ swift iterate.swift -Swift svn swift-r3334 cog-r2752 - -RunID: 20100526-2259-gtlz8zf4 -Progress: -SwiftScript trace: extract int value , 16.0 -SwiftScript trace: extract int value , 2.0 -SwiftScript trace: extract int value , 1.0 -Final status: Finished successfully:4 - -$ ls foldout* -foldout0000 foldout0001 foldout0002 foldout0003 - - -
    - -
    -
    Runtime features - -
    Visualising the workflow as a graph - - -When running a workflow, its possible to generate a provenance graph at the -same time: - -$ swift -pgraph graph.dot first.swift -$ dot -ograph.png -Tpng graph.dot - -graph.png can then be viewed using your favourite image viewer. -Dot is a utility for drawing directed graphs. It is a part of the graphViz package and must be installed separately. More information about graphViz can be found at http://www.graphviz.org. - -
    - -
    Running on a remote site - -As configured by default, all jobs are run locally. In the previous -examples, we've invoked 'echo' and 'tr' executables from our -SwiftScript program. These have been run on the local system -(the same computer on which you ran 'swift'). We can also make our -computations run on a remote resource. - -WARNING: This example is necessarily more vague than previous examples, -because its requires access to remote resources. You should ensure that you -can submit a job using the globus-job-run (or globusrun-ws?) command(s). - - -We do not need to modify any SwiftScript code to run on another resource. -Instead, we must modify another catalog, the 'site catalog'. This catalog -provides details of the location that applications will be run, with the -default settings referring to the local machine. We will modify it to -refer to a remote resource - the UC Teraport cluster. If you are not a -UC Teraport user, you should use details of a different resource that -you do have access to. - - -The site catalog is located in etc/sites.xml and is a relatively -straightforward XML format file. We must modify each of the following -three settings: gridftp (which indicates how and where data can be -transferred to the remote resource), jobmanager (which indicates how -applications can be run on the remote resource) and workdirectory -(which indicates where working storage can be found on the -remote resource). -
    - -
    Writing a mapper - - -This section will introduce writing a custom mapper so that Swift is able -to access data files laid out in application-specific ways. - - -An application-specific mapper must take the form of a Java class -that implements the -Mapper interface. - - -Usually you don't need to implement this interface directly, because -Swift provides a number of more concrete classes with some functionality -already implemented. - -The hierarchy of helper classes is: - - -Mapper -- This is the abstract interface for mappers in Swift. You -must implement methods to provide access to mapper properties, to map -from a SwiftScript dataset path (such as foo[1].bar) to a file name, -to check whether a file exists. None of the default Swift mappers -implement this interface directly - instead they use one of the -following helper classes. - - -AbstractMapper -- This provides helper methods to manage mapper -properties and to handle existance checking. Examples of mappers which -use this class are: -array_mapper, -csv_mapper, -fixed_array_mapper, -regexp_mapper and -single file mapper -. - - -AbstractFileMapper - - This provides a helper class for mappers -which select files based on selecting files from a directory listing. -It is necessary to write some helper methods that are different from -the above mapper methods. Examples of mappers which use this class -are: -simple_mapper, -filesys_mapper and the (undocumented) -StructuredRegularExpressionMapper. - - - -In general, to write a mapper, choose either the AbstractMapper or the -AbstractFileMapper and extend those. If your mapper will generally -select the files it returns based on a directory listing and will -convert paths to filenames using some regular conversion (for example, in -the way that simple_mapper maps files in a directory that match a -particular pattern), then you should probably use the AbstractFileMapper. -If your mapper will produce a list of files in some other way (for example, -in the way that csv_mapper maps based on filenames given in a CSV -file rather than looking at which files are in a directory), then you -should probably use the AbstractMapper. - - -
    Writing a very basic mapper -In this section, we will write a very basic (almost useless) -mapper that will map a SwiftScript dataset into a hardcoded file -called myfile.txt, like this: - - - - - Swift variable Filename - - var <-----------------------------> myfile.txt - - - - -We should be able to use the mapper we write in a SwiftScript program -like this: - - - -type file; - -file f <my_first_mapper>; - - - -First we must choose a base class - AbstractMapper or AbstractFileMapper. -We aren't going to use a directory listing to decide on our mapping -- we are getting the mapping from some other source (in fact, it -will be hard coded). So we will use AbstractMapper. - - - -So now onto the source code. We must define a subclass of -AbstractMapper and implement several -mapper methods: isStatic, existing, and map. These methods are documented -in the javadoc for the -Mapper -interface. - - - -Here is the code implementing this mapper. Put this in your source -vdsk directory, make a directory -src/tutorial/ and put this -file in src/tutorial/MyFirstMapper.java - - -package tutorial; - -import java.util.Arrays; -import java.util.Collection; -import java.util.Collections; - -import org.griphyn.vdl.mapping.AbsFile; -import org.griphyn.vdl.mapping.AbstractMapper; -import org.griphyn.vdl.mapping.Path; -import org.griphyn.vdl.mapping.PhysicalFormat; - -public class MyFirstMapper extends AbstractMapper { - - AbsFile myfile = new AbsFile("myfile.txt"); - - public boolean isStatic() { - return false; - } - - public Collection existing() { - if (myfile.exists()) - return Arrays.asList(new Path[] {Path.EMPTY_PATH}); - else - return Collections.EMPTY_LIST; - } - - public PhysicalFormat map(Path p) { - if(p.equals(Path.EMPTY_PATH)) - return myfile; - else - return null; - } -} - - - -Now we need to inform the Swift engine about the existence of this -mapper. We do that by editing the MapperFactory class definition, in -src/org/griphyn/vdl/mapping/MapperFactory.java and -adding a registerMapper call alongside the existing registerMapper calls, -like this: - - -registerMapper("my_first_mapper", tutorial.MyFirstMapper.class); - - -The first parameter is the name of the mapper that will be used -in SwiftScript program. The second parameter is the new Mapper class -that we just wrote. - - - -Now rebuild Swift using the 'ant redist' target. - - - -This new Swift build will be aware of your new mapper. We can test it out -with a hello world program: - - -type messagefile; - -(messagefile t) greeting() { - app { - echo "hello" stdout=@filename(t); - } -} - -messagefile outfile <my_first_mapper>; - -outfile = greeting(); - -Run this program, and hopefully you will find the "hello" string has -been output into the hard coded output file myfile.txt: - - -$ cat myfile.txt -hello - - -So that's a first very simple mapper implemented. Compare the -source code to the single_file_mapper in -SingleFileMapper.java. There is -not much more code to the single_file_mapper - mostly code to deal -with the file parameter. - - -
    - - -
    - -
    Starting and restarting - - -Now we're going to try out the restart capabilities of Swift. We will make -a workflow that will deliberately fail, and then we will fix the problem -so that Swift can continue with the workflow. - - - -First we have the program in working form, restart.swift. - - - -type file; - -(file f) touch() { - app { - touch @f; - } -} - -(file f) processL(file inp) { - app { - echo "processL" stdout=@f; - } -} - -(file f) processR(file inp) { - app { - broken "process" stdout=@f; - } -} - -(file f) join(file left, file right) { - app { - echo "join" @left @right stdout=@f; - } -} - -file f = touch(); - -file g = processL(f); -file h = processR(f); - -file i = join(g,h); - - - -We must define some transformation catalog entries: - - - -localhost touch /usr/bin/touch INSTALLED INTEL32::LINUX null -localhost broken /bin/true INSTALLED INTEL32::LINUX null - - - -Now we can run the program: - - - -$ swift restart.swift -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1119-3kgzzi15 -Progress: -Final status: Finished successfully:4 - - - -Four jobs run - touch, echo, broken and a final echo. (note that broken -isn't actually broken yet). - - - -Now we will break the 'broken' job and see what happens. Replace the -definition in tc.data for 'broken' with this: - - -localhost broken /bin/false INSTALLED INTEL32::LINUX null - - -Now when we run the workflow, the broken task fails: - - -$ swift restart.swift - -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1121-tssdcljg -Progress: -Progress: Stage in:1 Finished successfully:2 -Execution failed: - Exception in broken: -Arguments: [process] -Host: localhost -Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj -stderr.txt: -stdout.txt: - - - -From the output we can see that touch and the first echo completed, -but then broken failed and so swift did not attempt to execute the -final echo. - -There will be a restart log with the same name as the RunID: - - - -$ ls *20100526-1121-tssdcljg*rlog -restart-20100526-1121-tssdcljg.0.rlog - - -This restart log contains enough information for swift to know -which parts of the workflow were executed successfully. - -We can try to rerun it immediately, like this: - - -$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift - -Swift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1125-7yx0zi6d -Progress: -Execution failed: - Exception in broken: -Arguments: [process] -Host: localhost -Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj -stderr.txt: -stdout.txt: - ----- - -Caused by: - Exit code 1 - - - - -Swift tried to resume the workflow by executing 'broken' again. It did not -try to run the touch or first echo jobs, because the restart log says that -they do not need to be executed again. - - -Broken failed again, leaving the original restart log in place. - -Now we will fix the problem with 'broken' by restoring the original -tc.data line that works. - -Remove the existing 'broken' line and replace it with the successful -tc.data entry above: - - - -localhost broken /bin/true INSTALLED INTEL32::LINUX null - - - -Now run again: - - - -$ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift - -wift 0.9 swift-r2860 cog-r2388 - -RunID: 20100526-1128-a2gfuxhg -Progress: -Final status: Initializing:2 Finished successfully:2 - - -Swift tries to run 'broken' again. This time it works, and so -Swift continues on to execute the final piece of the workflow as if -nothing had ever gone wrong. - - -
    -
    - -
    bits -
    Named and optional parameters -In addition to specifying parameters positionally, parameters can -be named, and if desired a default value can be specified: - - -(messagefile t) greeting (string s="hello") { - app { - echo s stdout=@filename(t); - } -} - - -When we invoke the procedure, we can specify values for the parameters -by name. The following code can be found in q21.swift. - - -french = greeting(s="bonjour"); - - -or we can let the default value apply: - - -english = greeting(); - - - -
    -
    -
    - Deleted: trunk/docs/type-hierarchy.fig =================================================================== --- trunk/docs/type-hierarchy.fig 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/type-hierarchy.fig 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,29 +0,0 @@ -#FIG 3.2 Produced by xfig version 3.2.5 -Landscape -Center -Inches -Letter -100.00 -Single --2 -1200 2 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 4950 1350 4050 1800 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 5325 1350 6225 1800 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 3525 2100 3150 2850 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 3975 2100 4275 2775 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 6525 2175 6225 2775 -2 1 0 1 0 7 50 -1 -1 0.000 0 0 -1 0 0 2 - 6900 2175 7125 2775 -4 0 0 50 -1 0 12 0.0000 4 195 960 4575 1200 Swift types\001 -4 0 0 50 -1 0 12 0.0000 4 195 1275 2475 3075 Primitive types\001 -4 0 0 50 -1 0 12 0.0000 4 195 615 2475 3330 (eg int)\001 -4 0 0 50 -1 0 12 0.0000 4 195 1170 3975 3075 Marker types\001 -4 0 0 50 -1 0 12 0.0000 4 195 615 5925 3000 Arrays\001 -4 0 0 50 -1 0 12 0.0000 4 150 900 6900 3000 Structures\001 -4 0 0 50 -1 0 12 0.0000 4 195 1440 6225 2100 Composite types\001 -4 0 0 50 -1 0 12 0.0000 4 195 1155 3300 2025 Atomic types\001 Deleted: trunk/docs/type-hierarchy.png =================================================================== (Binary files differ) Added: trunk/docs/userguide/swift-site-model.png =================================================================== (Binary files differ) Property changes on: trunk/docs/userguide/swift-site-model.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: trunk/docs/userguide/type-hierarchy.png =================================================================== (Binary files differ) Property changes on: trunk/docs/userguide/type-hierarchy.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: trunk/docs/userguide/userguide.html =================================================================== --- trunk/docs/userguide/userguide.html (rev 0) +++ trunk/docs/userguide/userguide.html 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,4351 @@ + + + + + +Swift User Guide + + + + + +
    +
    +

    1. Overview

    +
    +

    This manual provides reference material for Swift: the SwiftScript +language and the Swift runtime system. For introductory material, +consult the Swift tutorial +http://www.ci.uchicago.edu/swift/guides/tutorial.php.

    +

    Swift is a data-oriented coarse grained scripting language that supports +dataset typing and mapping, dataset iteration, conditional branching, +and procedural composition.

    +

    Swift programs (or workflows) are written in a language called +SwiftScript.

    +

    SwiftScript programs are dataflow oriented - they are primarily +concerned with processing (possibly large) collections of data files, by +invoking programs to do that processing. Swift handles execution of such +programs on remote sites by choosing sites, handling the staging of +input and output files to and from the chosen sites and remote execution +of program code.

    +
    +
    +
    +

    2. The SwiftScript Language

    +
    +
    +

    2.1. Language basics

    +

    A Swift script describes data, application components, invocations of +applications components, and the inter-relations (data flow) between +those invocations.

    +

    Data is represented in a script by strongly-typed single-assignment +variables. The syntax superficially resembles C and Java. For example, +{ and } characters are used to enclose blocks of statements.

    +

    Types in Swift can be atomic or composite. An atomic type can be +either a primitive type or a mapped type. Swift provides a fixed set +of primitive types, such as integer and string. A mapped type +indicates that the actual data does not reside in CPU addressable memory +(as it would in conventional programming languages), but in POSIX-like +files. Composite types are further subdivided into structures and +arrays. Structures are similar in most respects to structure types in +other languages. Arrays use numeric indices, but are sparse. They can +contain elements of any type, including other array types, but all +elements in an array must be of the same type. We often refer to +instances of composites of mapped types as datasets.

    +

    +type-hierarchy.png +

    +

    Mapped type and composite type variable declarations can be annotated +with a mapping descriptor indicating the file(s) that make up that +dataset. For example, the following line declares a variable named +photo with type image. It additionally declares that the data for +this variable is stored in a single file named shane.jpeg.

    +
    +
    +
    image photo <"shane.jpeg">;
    +

    Component programs of scripts are declared in an app declaration, with +the description of the command line syntax for that program and a list +of input and output data. An app block describes a functional/dataflow +style interface to imperative components.

    +

    For example, the following example lists a procedure which makes use of +the ImageMagick http://www.imagemagick.org/ convert command to +rotate a supplied image by a specified angle:

    +
    +
    +
    app (image output) rotate(image input) {
    +  convert "-rotate" angle @input @output;
    +}
    +

    A procedure is invoked using the familiar syntax:

    +
    +
    +
    rotated = rotate(photo, 180);
    +

    While this looks like an assignment, the actual unix level execution +consists of invoking the command line specified in the app +declaration, with variables on the left of the assignment bound to the +output parameters, and variables to the right of the procedure +invocation passed as inputs.

    +

    The examples above have used the type image without any definition of +that type. We can declare it as a marker type which has no structure +exposed to SwiftScript:

    +
    +
    +
    type image;
    +

    This does not indicate that the data is unstructured; but it indicates +that the structure of the data is not exposed to SwiftScript. Instead, +SwiftScript will treat variables of this type as individual opaque files.

    +

    With mechanisms to declare types, map variables to data files, and +declare and invoke procedures, we can build a complete (albeit simple) +script:

    +
    +
    +
    type image;
    +image photo <"shane.jpeg">;
    +image rotated <"rotated.jpeg">;
    +
    +app (image output) rotate(image input, int angle) {
    +   convert "-rotate" angle @input @output;
    +}
    +
    +rotated = rotate(photo, 180);
    +

    This script can be invoked from the command line:

    +
    +
    +
      $ ls *.jpeg
    +  shane.jpeg
    +  $ swift example.swift
    +  ...
    +  $ ls *.jpeg
    +  shane.jpeg rotated.jpeg
    +

    This executes a single convert command, hiding from the user features +such as remote multisite execution and fault tolerance that will be +discussed in a later section.

    +
    Figure 1. shane.jpeg

    +userguide-shane.jpeg +

    +
    Figure 2. rotated.jpeg

    +userguide-rotated.jpeg +

    +
    +
    +

    2.2. Arrays and Parallel Execution

    +

    Arrays of values can be declared using the [] suffix. An array be +mapped to a collection of files, one element per file, by using a +different form of mapping expression. For example, the filesys_mapper +maps all files matching a particular unix glob pattern into an array:

    +
    +
    +
    file frames[] <filesys_mapper; pattern="*.jpeg">;
    +

    The foreach construct can be used to apply the same block of code to +each element of an array:

    +
    +
    +
    foreach f,ix in frames {
    +  output[ix] = rotate(frames, 180);
    +}
    +

    Sequential iteration can be expressed using the iterate construct:

    +
    +
    +
    step[0] = initialCondition();
    +iterate ix {
    +  step[ix] = simulate(step[ix-1]);
    +}
    +

    This fragment will initialise the 0-th element of the step array to +some initial condition, and then repeatedly run the simulate +procedure, using each execution’s outputs as input to the next step.

    +
    +
    +

    2.3. Ordering of execution

    +

    Non-array variables are single-assignment, which means that they must +be assigned to exactly one value during execution. A procedure or +expression will be executed when all of its input parameters have been +assigned values. As a result of such execution, more variables may +become assigned, possibly allowing further parts of the script to execute.

    +

    In this way, scripts are implicitly parallel. Aside from serialisation +implied by these dataflow dependencies, execution of component programs +can proceed in parallel.

    +

    In this fragment, execution of procedures p and q can happen in +parallel:

    +
    +
    +
    y=p(x);
    +z=q(x);
    +

    while in this fragment, execution is serialised by the variable y, +with procedure p executing before q.

    +
    +
    +
    y=p(x);
    +z=q(y);
    +

    Arrays in SwiftScript are more monotonic - a generalisation of being +assignment. Knowledge about the content of an array increases during +execution, but cannot otherwise change. Each element of the array is +itself single assignment or monotonic (depending on its type). During a +run all values for an array are eventually known, and that array is +regarded as closed.

    +

    Statements which deal with the array as a whole will often wait for the +array to be closed before executing (thus, a closed array is the +equivalent of a non-array type being assigned). However, a foreach +statement will apply its body to elements of an array as they become +known. It will not wait until the array is closed.

    +

    Consider this script:

    +
    +
    +
    file a[];
    +file b[];
    +foreach v,i in a {
    +  b[i] = p(v);
    +}
    +a[0] = r();
    +a[1] = s();
    +

    Initially, the foreach statement will have nothing to execute, as the +array a has not been assigned any values. The procedures r and s +will execute. As soon as either of them is finished, the corresponding +invocation of procedure p will occur. After both r and s have +completed, the array a will be closed since no other statements in the +script make an assignment to a.

    +
    +
    +

    2.4. Compound procedures

    +

    As with many other programming languages, procedures consisting of +SwiftScript code can be defined. These differ from the previously +mentioned procedures declared with the app keyword, as they invoke +other SwiftScript procedures rather than a component program.

    +
    +
    +
    (file output) process (file input) {
    +  file intermediate;
    +  intermediate = first(input);
    +  output = second(intermediate);
    +}
    +
    +file x <"x.txt">;
    +file y <"y.txt">;
    +y = process(x);
    +

    This will invoke two procedures, with an intermediate data file named +anonymously connecting the first and second procedures.

    +

    Ordering of execution is generally determined by execution of app +procedures, not by any containing compound procedures. In this code block:

    +
    +
    +
    (file a, file b) A() {
    +  a = A1();
    +  b = A2();
    +}
    +file x, y, s, t;
    +(x,y) = A();
    +s = S(x);
    +t = S(y);
    +

    then a valid execution order is: A1 S(x) A2 S(y). The compound +procedure A does not have to have fully completed for its return +values to be used by subsequent statements.

    +
    +
    +

    2.5. More about types

    +

    Each variable and procedure parameter in SwiftScript is strongly typed. +Types are used to structure data, to aid in debugging and checking +program correctness and to influence how Swift interacts with data.

    +

    The image type declared in previous examples is a marker type. +Marker types indicate that data for a variable is stored in a single +file with no further structure exposed at the SwiftScript level.

    +

    Arrays have been mentioned above, in the arrays section. A code block +may be applied to each element of an array using foreach; or +individual elements may be references using [] notation.

    +

    There are a number of primitive types:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    type contains

    int

    integers

    string

    strings of text

    float

    floating point numbers, that behave the same as Java doubles

    boolean

    true/false

    +
    +

    Complex types may be defined using the type keyword:

    +
    +
    +
    type headerfile;
    +type voxelfile;
    +type volume {
    +  headerfile h;
    +  voxelfile v;
    +}
    +

    Members of a complex type can be accessed using the . operator:

    +
    +
    +
    volume brain;
    +o = p(brain.h);
    +

    Sometimes data may be stored in a form that does not fit with Swift’s +file-and-site model; for example, data might be stored in an RDBMS on +some database server. In that case, a variable can be declared to have +external type. This indicates that Swift should use the variable to +determine execution dependency, but should not attempt other data +management; for example, it will not perform any form of data stage-in +or stage-out it will not manage local data caches on sites; and it will +not enforce component program atomicity on data output. This can add +substantial responsibility to component programs, in exchange for +allowing arbitrary data storage and access methods to be plugged in to +scripts.

    +
    +
    +
    type file;
    +
    +app (external o) populateDatabase() {
    +  populationProgram;
    +}
    +
    +app (file o) analyseDatabase(external i) {
    +  analysisProgram @o;
    +}
    +
    +external database;
    +file result <"results.txt">;
    +
    +database = populateDatabase();
    +result = analyseDatabase(database);
    +

    Some external database is represented by the database variable. The +populateDatabase procedure populates the database with some data, and +the analyseDatabase procedure performs some subsequent analysis on +that database. The declaration of database contains no mapping; and +the procedures which use database do not reference them in any way; +the description of database is entirely outside of the script. The +single assignment and execution ordering rules will still apply though; +populateDatabase will always be run before analyseDatabase.

    +
    +
    +

    2.6. Data model

    +

    Data processed by Swift is strongly typed. It may be take the form of +values in memory or as out-of-core files on disk. Language constructs +called mappers specify how each piece of data is stored.

    +
    +
    +

    2.7. Mappers

    +

    When a DSHandle represents a data file (or container of datafiles), it +is associated with a mapper. The mapper is used to identify which files +belong to that DSHandle.

    +

    A dataset’s physical representation is declared by a mapping descriptor, +which defines how each element in the dataset’s logical schema is stored +in, and fetched from, physical structures such as directories, files, +and remote servers.

    +

    Mappers are parameterized to take into account properties such as +varying dataset location. In order to access a dataset, we need to know +three things: its type, its mapping, and the value(s) of any +parameter(s) associated with the mapping descriptor. For example, if we +want to describe a dataset, of type imagefile, and whose physical +representation is a file called "file1.bin" located at +"/home/yongzh/data/", then the dataset might be declared as follows:

    +
    +
    +
    imagefile f1<single_file_mapper;file="/home/yongzh/data/file1.bin">
    +

    The above example declares a dataset called f1, which uses a single file +mapper to map a file from a specific location.

    +

    SwiftScript has a simplified syntax for this case, since +single_file_mapper is frequently used:

    +
    +
    +
    binaryfile f1<"/home/yongzh/data/file1.bin">
    +

    Swift comes with a number of mappers that handle common mapping +patterns. These are documented in the mappers section of this +guide.

    +
    +
    +

    2.8. More technical details about SwiftScript

    +

    The syntax of SwiftScript has a superficial resemblance to C and Java. +For example, { and } characters are used to enclose blocks of statements.

    +

    A SwiftScript program consists of a number of statements. Statements may +declare types, procedures and variables, assign values to variables, and +express operations over arrays.

    +
    +

    2.8.1. Variables

    +

    Variables in SwiftScript are declared to be of a specific type. +Assignments to those variables must be data of that type. SwiftScript +variables are single-assignment - a value may be assigned to a variable +at most once. This assignment can happen at declaration time or later on +in execution. When an attempt to read from a variable that has not yet +been assigned is made, the code performing the read is suspended until +that variable has been written to. This forms the basis for Swift’s +ability to parallelise execution - all code will execute in parallel +unless there are variables shared between the code that cause sequencing.

    +
    +
    +

    2.8.2. Variable Declarations

    +

    Variable declaration statements declare new variables. They can +optionally assign a value to them or map those variables to on-disk files.

    +

    Declaration statements have the general form:

    +
    +
    +
    typename variablename (<mapping> | = initialValue ) ;
    +

    The format of the mapping expression is defined in the Mappers section. +initialValue may be either an expression or a procedure call that +returns a single value.

    +

    Variables can also be declared in a multivalued-procedure statement, +described in another section.

    +
    +
    +

    2.8.3. Assignment Statements

    +

    Assignment statements assign values to previously declared variables. +Assignments may only be made to variables that have not already been +assigned. Assignment statements have the general form:

    +
    +
    +
    variable = value;
    +

    where value can be either an expression or a procedure call that returns +a single value.

    +

    Variables can also be assigned in a multivalued-procedure statement, +described in another section.

    +
    +
    +
    +

    2.9. Procedures

    +

    There are two kinds of procedure: An atomic procedure, which describes +how an external program can be executed; and compound procedures which +consist of a sequence of SwiftScript statements.

    +

    A procedure declaration defines the name of a procedure and its input +and output parameters. SwiftScript procedures can take multiple inputs +and produce multiple outputs. Inputs are specified to the right of the +function name, and outputs are specified to the left. For example:

    +
    +
    +
    (type3 out1, type4 out2) myproc (type1 in1, type2 in2)
    +

    The above example declares a procedure called myproc, which has two +inputs in1 (of type type1) and in2 (of type type2) and two +outputs out1 (of type type3) and out2 (of type type4).

    +

    A procedure input parameter can be an optional parameter in which case +it must be declared with a default value. When calling a procedure, both +positional parameter and named parameter passings can be passed, +provided that all optional parameters are declared after the required +parameters and any optional parameter is bound using keyword parameter +passing. For example, if myproc1 is defined as:

    +
    +
    +
    (binaryfile bf) myproc1 (int i, string s="foo")
    +

    Then that procedure can be called like this, omitting the optional

    +
    +
    +
    parameter s:
    +binaryfile mybf = myproc1(1);
    +

    or like this supplying a value for the optional parameter s:

    +
    +
    +
    binaryfile mybf = myproc1 (1, s="bar");
    +
    +

    2.9.1. Atomic procedures

    +

    An atomic procedure specifies how to invoke an external executable +program, and how logical data types are mapped to command line arguments.

    +

    Atomic procedures are defined with the app keyword:

    +
    +
    +
    app (binaryfile bf) myproc (int i, string s="foo") {
    +    myapp i s @filename(bf);
    +}
    +

    which specifies that myproc invokes an executable called myapp, +passing the values of i, s and the filename of bf as command line +arguments.

    +
    +
    +

    2.9.2. Compound procedures

    +

    A compound procedure contains a set of SwiftScript statements:

    +
    +
    +
    (type2 b) foo_bar (type1 a) {
    +    type3 c;
    +    c = foo(a);    // c holds the result of foo
    +    b = bar(c);    // c is an input to bar
    +}
    +
    +
    +
    +

    2.10. Control Constructs

    +

    SwiftScript provides if, switch, foreach, and iterate +constructs, with syntax and semantics similar to comparable constructs +in other high-level languages.

    +
    +

    2.10.1. foreach

    +

    The foreach construct is used to apply a block of statements to each +element in an array. For example:

    +
    +
    +
    check_order (file a[]) {
    +    foreach f in a {
    +        compute(f);
    +    }
    +}
    +

    foreach statements have the general form:

    +
    +
    +
    foreach controlvariable (,index) in expression {
    +    statements
    +}
    +

    The block of statements is evaluated once for each element in +expression which must be an array, with controlvariable set to the +corresponding element and index (if specified) set to the integer +position in the array that is being iterated over.

    +
    +
    +

    2.10.2. if

    +

    The if statement allows one of two blocks of statements to be +executed, based on a boolean predicate. if statements generally have +the form:

    +
    +
    +
    if(predicate) {
    +    statements
    +} else {
    +    statements
    +}
    +

    where predicate is a boolean expression.

    +
    +
    +

    2.10.3. switch

    +

    switch expressions allow one of a selection of blocks to be chosen +based on the value of a numerical control expression. switch +statements take the general form:

    +
    +
    +
    switch(controlExpression) {
    +    case n1:
    +        statements2
    +    case n2:
    +        statements2
    +    [...]
    +    default:
    +        statements
    +}
    +

    The control expression is evaluated, the resulting numerical value used +to select a corresponding case, and the statements belonging to that +case block are evaluated. If no case corresponds, then the statements +belonging to the default block are evaluated.

    +

    Unlike C or Java switch statements, execution does not fall through to +subsequent case blocks, and no break statement is necessary at the +end of each block.

    +
    +
    +

    2.10.4. iterate

    +

    iterate expressions allow a block of code to be evaluated repeatedly, +with an integer parameter sweeping upwards from 0 until a termination +condition holds.

    +

    The general form is:

    +
    +
    +
    iterate var {
    +    statements;
    +} until (terminationExpression);
    +

    with the variable var starting at 0 and increasing by one in each +iteration. That variable is in scope in the statements block and when +evaluating the termination expression.

    +
    +
    +
    +

    2.11. Operators

    +

    The following infix operators are available for use in SwiftScript +expressions.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    operatorpurpose

    +

    numeric addition; string concatenation

    -

    numeric subtraction

    *

    numeric multiplication

    /

    floating point division

    %/

    integer division

    %%

    integer remainder of division

    == !=

    comparison and not-equal-to

    < > ⇐ >=

    numerical ordering

    && ||

    boolean and, or

    !

    boolean not

    +
    +
    +
    +

    2.12. Global constants

    +

    At the top level of a SwiftScript program, the global modified may be +added to a declaration so that it is visible throughout the program, +rather than only at the top level of the program. This allows global +constants (of any type) to be defined. (since Swift 0.10)

    +
    +
    +

    2.13. Imports

    +

    The import directive can be used to import definitions from another +SwiftScript file. (since Swift 0.10)

    +

    For example, a SwiftScript program might contain this:

    +
    +
    +
    import defs;
    +file f;
    +

    which would import the content of defs.swift in the current directory:

    +
    +
    +
    type file;
    +

    Imported files are read from the current working directory.

    +

    There is no requirement that a module is imported only once. If a module +is imported multiple times, for example in different files, then Swift +will only process the imports once.

    +

    Imports may contain anything that is valid in a SwiftScript program, +including code that causes remote execution.

    +
    +
    +
    +
    +

    3. Mappers

    +
    +

    Mappers provide a mechanism to specify the layout of mapped datasets on +disk. This is needed when Swift must access files to transfer them to +remote sites for execution or to pass to applications.

    +

    Swift provides a number of mappers that are useful in common cases. This +section details those standard mappers. For more complex cases, it is +possible to write application-specific mappers in Java and use them +within a SwiftScript program.

    +
    +

    3.1. The single file mapper

    +

    The single_file_mapper maps a single physical file to a dataset.

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    f

    myfile

    f[0]

    INVALID

    f.bar

    INVALID

    +
    +
    + +++ + + + + + + + + + + + +
    parametermeaning

    file

    The location of the physical file including path and file name.

    +
    +

    Example:

    +
    +
    +
    file f <single_file_mapper;file="plot_outfile_param">;
    +

    There is a simplified syntax for this mapper:

    +
    +
    +
    file f <"plot_outfile_param">;
    +
    +
    +

    3.2. The simple mapper

    +

    The simple_mapper maps a file or a list of files into an array by +prefix, suffix, and pattern. If more than one file is matched, each of +the file names will be mapped as a subelement of the dataset.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored.

    +
    +
    +
    +
    type file;
    +file f <simple_mapper;prefix="foo", suffix=".txt">;
    +

    The above maps all filenames that start with foo and have an extension +.txt into file f.

    +
    + +++ + + + + + + + + + + + +
    Swift variableFilename

    f

    foo.txt

    +
    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting(string m) {.
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile <simple_mapper;prefix="foo",suffix=".txt">;
    +
    +outfile = greeting("hi");
    +

    This will output the string hi to the file foo.txt.

    +

    The simple_mapper can be used to map arrays. It will map the array +index into the filename between the prefix and suffix.

    +
    +
    +
    type messagefile;
    +
    +(messagefile t) greeting(string m) {
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +messagefile outfile[] <simple_mapper;prefix="baz",suffix=".txt">;
    +
    +outfile[0] = greeting("hello");
    +outfile[1] = greeting("middle");
    +outfile[2] = greeting("goodbye");
    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    outfile[0]

    baz0000.txt

    outfile[1]

    baz0001.txt

    outfile[2]

    baz0002.txt

    +
    +

    simple_mapper can be used to map structures. It will map the name of +the structure member into the filename, between the prefix and the suffix.

    +
    +
    +
    type messagefile;
    +
    +type mystruct {
    +  messagefile left;
    +  messagefile right;
    +};
    +
    +(messagefile t) greeting(string m) {
    +    app {
    +        echo m stdout=@filename(t);
    +    }
    +}
    +
    +mystruct out <simple_mapper;prefix="qux",suffix=".txt">;
    +
    +out.left = greeting("hello");
    +out.right = greeting("goodbye");
    +

    This will output the string "hello" into the file qux.left.txt and the +string "goodbye" into the file qux.right.txt.

    +
    + +++ + + + + + + + + + + + + + + + +
    Swift variableFilename

    out.left

    quxleft.txt

    out.right

    quxright.txt

    +
    +
    +
    +

    3.3. concurrent mapper

    +

    concurrent_mapper is almost the same as the simple mapper, except that +it is used to map an output file, and the filename generated will +contain an extract sequence that is unique. This mapper is the default +mapper for variables when no mapper is specified.

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt" +pattern A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored.

    +
    +

    Example:

    +
    +
    +
    file f1;
    +file f2 <concurrent_mapper;prefix="foo", suffix=".txt">;
    +

    The above example would use concurrent mapper for f1 and f2, and +generate f2 filename with prefix "foo" and extension ".txt"

    +
    +
    +

    3.4. File system mapper

    +

    filesys_mapper is similar to the simple mapper, but maps a file or a +list of files to an array. Each of the filename is mapped as an element +in the array. The order of files in the resulting array is not defined.

    +

    TODO: note on difference between location as a relative vs absolute path +wrt staging to remote location - as mihael said: It’s because you +specify that location in the mapper. Try location="." instead of +location="/sandbox/…"

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + +
    parametermeaning

    location

    The directory where the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match +all file names that contain foo.

    +
    +

    Example:

    +
    +
    +
    file texts[] <filesys_mapper;prefix="foo", suffix=".txt">;
    +

    The above example would map all filenames that start with "foo" and +have an extension ".txt" into the array texts. For example, if the +specified directory contains files: foo1.txt, footest.txt, +foo__1.txt, then the mapping might be:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    texts[0]

    footest.txt

    texts[1]

    foo1.txt

    texts[2]

    foo__1.txt

    +
    +
    +
    +

    3.5. fixed array mapper

    +

    The fixed_array_mapper maps from a string that contains a list of +filenames into a file array.

    +
    + +++ + + + + + + + + + + + +
    parameterMeaning

    files

    A string that contains a list of filenames, separated by space, +comma or colon

    +
    +

    Example:

    +
    +
    +
    file texts[] <fixed_array_mapper;files="file1.txt, fileB.txt, file3.txt">;
    +

    would cause a mapping like this:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    texts[0]

    file1.txt

    texts[1]

    fileB.txt

    texts[2]

    file3.txt

    +
    +
    +
    +

    3.6. array mapper

    +

    The array_mapper maps from an array of strings into a file

    +
    + +++ + + + + + + + + + + + +
    parametermeaning

    files

    An array of strings containing one filename per element

    +
    +

    Example:

    +
    +
    +
    string s[] = [ "a.txt", "b.txt", "c.txt" ];
    +
    +file f[] <array_mapper;files=s>;
    +

    This will establish the mapping:

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    f[0]

    a.txt

    f[1]

    b.txt

    f[2]

    c.txt

    +
    +
    +
    +

    3.7. regular expression mapper

    +

    The regexp_mapper transforms one file name to another using regular +expression matching.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    parametermeaning

    source

    The source file name

    match

    Regular expression pattern to match, use

    ()

    to match whatever +regular expression is inside the parentheses, and indicate the start and +end of a group; the contents of a group can be retrieved with the

    \\number

    special sequence (two backslashes are needed because the +backslash is an escape sequence introducer)

    transform

    The pattern of the file name to transform to, use \number to +reference the group matched.

    +
    +

    Example:

    +
    +
    +
    string s = "picture.gif";
    +file f <regexp_mapper;
    +  source=s,
    +  match="(.*)gif",
    +  transform="\\1jpg">;
    +

    This example transforms a string ending gif into one ending jpg and +maps that to a file.

    +
    + +++ + + + + + + + + + + + +
    Swift variableFilename

    f

    picture.jpg

    +
    +
    +
    +

    3.8. csv mapper

    +

    The csv_mapper maps the content of a CSV (comma-separated value) file +into an array of structures. The dataset type needs to be correctly +defined to conform to the column names in the file. For instance, if the +file contains columns: name age GPA then the type needs to have member +elements like this:

    +
    +
    +
    type student {
    +  file name;
    +  file age;
    +  file GPA;
    +}
    +

    If the file does not contain a header with column info, then the column +names are assumed as column1, column2, etc.

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterMeaning

    file

    The name of the CSV file to read mappings from.

    header

    Whether the file has a line describing header info; default is

    true

    skip

    The number of lines to skip at the beginning (after header line); +default is 0.

    hdelim

    Header field delimiter; default is the value of the

    delim

    parameter

    delim

    Content field delimiters; defaults are space, tab and comma

    +
    +

    Example:

    +
    +
    +
    student stus[] <csv_mapper;file="stu_list.txt">;
    +

    The above example would read a list of student info from file +"stu_list.txt" and map them into a student array. By default, the file +should contain a header line specifying the names of the columns. If +stu_list.txt contains the following:

    +
    +
    +
    name,age,gpa
    +101-name.txt, 101-age.txt, 101-gpa.txt
    +name55.txt, age55.txt, age55.txt
    +q, r, s
    +

    then some of the mappings produced by this example would be:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    stus[0].name101-name.txt

    stus[0].age

    101-age.txt

    stus[0].gpa

    101-gpa.txt

    stus[1].name

    name55.txt

    stus[1].age

    age55.txt

    stus[1].gpa

    gpa55.txt

    stus[2].name

    q

    stus[2].age

    r

    stus[2].gpa

    s

    +
    +
    +
    +

    3.9. external mapper

    +

    The external mapper, ext maps based on the output of a supplied Unix +executable.

    +
    + +++ + + + + + + + + + + + + + +

    parameter

    meaning

    exec

    The name of the executable (relative to the current directory, if +an absolute path is not specified)

    *

    Other parameters are passed to the executable prefixed with a - symbol

    +
    +

    The output of the executable should consist of two columns of data, +separated by a space. The first column should be the path of the mapped +variable, in SwiftScript syntax (for example [2] means the 2nd element +of an array) or the symbol $ to represent the root of the mapped +variable.

    +

    Example: With the following in mapper.sh,

    +
    +
    +
    #!/bin/bash
    +echo "[2] qux"
    +echo "[0] foo"
    +echo "[1] bar"
    +

    then a mapping statement:

    +
    +
    +
    student stus[] <ext;exec="mapper.sh">;
    +

    would map

    +
    + +++ + + + + + + + + + + + + + + + + + + + +
    Swift variableFilename

    stus[0]

    foo

    stus[1]

    bar

    stus[2]

    qux

    +
    +
    +
    +
    +
    +

    4. Commands

    +
    +

    The commands detailed in this section are available in the bin/ +directory of a Swift installation and can by run from the commandline if +that directory is placed on the PATH.

    +
    +

    4.1. swift

    +

    The swift command is the main command line tool for executing +SwiftScript programs.

    +
    +

    4.1.1. Command-line Syntax

    +

    The swift command is invoked as follows: swift [options] +SwiftScript-program [SwiftScript-arguments]* with options taken from the +following list, and SwiftScript-arguments made available to the +SwiftScript program through the @arg function.

    +

    Swift command-line options

    +

    -help or -h

    +
    +
    +
    Display usage information
    +
    +

    -typecheck

    +
    +
    +
    Does a typecheck of a SwiftScript program, instead of executing it.
    +
    +

    -dryrun

    +
    +
    +
    Runs the SwiftScript program without submitting any jobs (can be
    +used to get a graph)
    +
    +

    -monitor

    +
    +
    +
    Shows a graphical resource monitor
    +
    +

    -resume file

    +
    +
    +
    Resumes the execution using a log file
    +
    +

    -config file

    +
    +
    +
    Indicates the Swift configuration file to be used for this run.
    +Properties in this configuration file will override the default
    +properties. If individual command line arguments are used for
    +properties, they will override the contents of this file.
    +
    +

    -verbose | -v

    +
    +
    +
    Increases the level of output that Swift produces on the console to
    +include more detail about the execution
    +
    +

    -debug | -d

    +
    +
    +
    Increases the level of output that Swift produces on the console to
    +include lots of detail about the execution
    +
    +

    -logfile file

    +
    +
    +
    Specifies a file where log messages should go to. By default Swift
    +uses the name of the program being run and a numeric index (e.g.
    +myworkflow.1.log)
    +
    +

    -runid identifier

    +
    +
    +
    Specifies the run identifier. This must be unique for every
    +invocation and is used in several places to keep files from
    +different executions cleanly separated. By default, a datestamp and
    +random number are used to generate a run identifier. When using this
    +parameter, care should be taken to ensure that the run ID remains
    +unique with respect to all other run IDs that might be used,
    +irrespective of (at least) expected execution sites, program or user.
    +
    +

    -tui

    +
    +
    +
    Displays an interactive text mode monitor during a run. (since Swift
    +0.9)
    +
    +

    In addition, the following Swift properties can be set on the command line:

    +
      +
    • +

      +caching.algorithm +

      +
    • +
    • +

      +clustering.enabled +

      +
    • +
    • +

      +clustering.min.time +

      +
    • +
    • +

      +clustering.queue.delay +

      +
    • +
    • +

      +ip.address +

      +
    • +
    • +

      +kickstart.always.transfer +

      +
    • +
    • +

      +kickstart.enabled +

      +
    • +
    • +

      +lazy.errors +

      +
    • +
    • +

      +pgraph +

      +
    • +
    • +

      +pgraph.graph.options +

      +
    • +
    • +

      +pgraph.node.options +

      +
    • +
    • +

      +sitedir.keep +

      +
    • +
    • +

      +sites.file +

      +
    • +
    • +

      +tc.file +

      +
    • +
    • +

      +tcp.port.range +

      +
    • +
    +
    +
    +

    4.1.2. Return codes

    +

    The swift command may exit with the following return codes:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    valuemeaning

    0

    success

    1

    command line syntax error or missing project name

    2

    error during execution

    3

    error during compilation

    4

    input file does not exist

    +
    +
    +
    +

    4.1.3. Environment variables

    +

    The swift is influenced by the following environment variables:

    +

    GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment +before running Swift. These can be set to inform Swift of the +configuration of your local firewall. More information can be found in +the Globus firewall How-to http://dev.globus.org/wiki/FirewallHowTo.

    +

    COG_OPTS - set in the environment before running Swift. Options set in +this variable will be passed as parameters to the Java Virtual Machine +which will run Swift. The parameters vary between virtual machine +imlementations, but can usually be used to alter settings such as +maximum heap size. Typing java -help will sometimes give a list of +commands. The Sun Java 1.4.2 command line options are documented here +http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/java.html.

    +
    +
    +
    +

    4.2. swift-osg-ress-site-catalog

    +

    The swift-osg-ress-site-catalog command generates a site catalog based +on OSG http://www.opensciencegrid.org/'s ReSS information system +(since Swift 0.9)

    +

    Usage: swift-osg-ress-site-catalog [options]

    +

    --help

    +
    +
    +
    Show help message
    +
    +

    --vo=[name]

    +
    +
    +
    Set what VO to query ReSS for
    +
    +

    --engage-verified

    +
    +
    +
    Only retrieve sites verified by the Engagement VO site verification
    +tests This can not be used together with |--vo|, as the query will
    +only work for sites advertising support for the Engagement VO.
    +
    +
    +
    +
    This option means information will be retrieved from the Engagement
    +collector instead of the top-level ReSS collector.
    +
    +

    --out=[filename]

    +
    +
    +
    Write to [filename] instead of stdout
    +
    +

    --condor-g

    +
    +
    +
    Generates sites files which will submit jobs using a local Condor-G
    +installation rather than through direct GRAM2 submission. (since
    +Swift 0.10)
    +
    +
    +
    +

    4.3. swift-plot-log

    +

    swift-plot-log generates summaries of Swift run log files.

    +

    Usage: swift-plot-log [logfile] [targets]

    +

    When no targets are specified, swift-plog-log will generate an HTML +report for the run. When targets are specified, only those named targets +will be generated.

    +
    +
    +
    +
    +

    5. Executing app procedures

    +
    +

    This section describes how Swift executes app procedures, and +requirements on the behaviour of application programs used in app +procedures. These requirements are primarily to ensure that the Swift +can run your application in different places and with the various fault +tolerance mechanisms in place.

    +
    +

    5.1. Mapping of app semantics into unix process execution semantics

    +

    This section describes how an app procedure invocation is translated +into a (remote) unix process execution. It does not describe the +mechanisms by which Swift performs that translation; that is described +in the next section.

    +

    In this section, this example SwiftScript program is used for reference:

    +
    +
    +
    type file;
    +
    +app (file o) count(file i) {
    +  wc @i stdout=@o;
    +}
    +
    +file q <"input.txt">;
    +file r <"output.txt">;
    +

    The executable for wc will be looked up in tc.data.

    +

    This unix executable will then be executed in some application +procedure workspace. This means:

    +

    Each application procedure workspace will have an application workspace +directory. (TODO: can collapse terms application procedure workspace +and application workspace directory ?

    +

    This application workspace directory will not be shared with any other +application procedure execution attempt; all application procedure +execution attempts will run with distinct application procedure +workspaces. (for the avoidance of doubt: If a SwiftScript procedure +invocation is subject to multiple application procedure execution +attempts (due to Swift-level restarts, retries or replication) then each +of those application procedure execution attempts will be made in a +different application procedure workspace. )

    +

    The application workspace directory will be a directory on a POSIX +filesystem accessible throughout the application execution by the +application executable.

    +

    Before the application executable is executed:

    +
      +
    • +

      +The application workspace directory will exist. +

      +
    • +
    • +

      +The input files will exist inside the application workspace + directory (but not necessarily as direct children; there may be + subdirectories within the application workspace directory). +

      +
    • +
    • +

      +The input files will be those files mapped to input parameters + of the application procedure invocation. (In the example, this + means that the file input.txt will exist in the application + workspace directory) +

      +
    • +
    • +

      +For each input file dataset, it will be the case that @filename + or @filenames invoked with that dataset as a parameter will + return the path relative to the application workspace directory + for the file(s) that are associated with that dataset. (In the + example, that means that @i will evaluate to the path input.txt) +

      +
    • +
    • +

      +For each file-bound parameter of the Swift procedure invocation, + the associated files (determined by data type?) will always exist. +

      +
    • +
    • +

      +The input files must be treated as read only files. This may or + may not be enforced by unix file system permissions. They may or + may not be copies of the source file (conversely, they may be + links to the actual source file). +

      +
    • +
    +

    During/after the application executable execution, the following must +be true:

    +
      +
    • +

      +If the application executable execution was successful (in the + opinion of the application executable), then the application + executable should exit with unix return code 0; if the + application executable execution was unsuccessful (in the opinion + of the application executable), then the application executable + should exit with unix return code not equal to 0. +

      +
    • +
    • +

      +Each file mapped from an output parameter of the SwiftScript + procedure call must exist. Files will be mapped in the same way as + for input files. +

      +
      +
      +
      (? Is it defined that output subdirectories will be precreated
      +before execution or should app executables expect to make them?
      +That's probably determined by the present behaviour of wrapper.sh)
      +
      +
    • +
    • +

      +Output produced by running the application executable on some + inputs should be the same no matter how many times, when or where + that application executable is run. The same can vary depending + on application (for example, in an application it might be + acceptable for a PNG→JPEG conversion to produce different, + similar looking, output jpegs depending on the environment) +

      +
    • +
    +

    Things to not assume:

    +
      +
    • +

      +anything about the path of the application workspace directory +

      +
    • +
    • +

      +that either the application workspace directory will be deleted or + will continue to exist or will remain unmodified after execution + has finished +

      +
    • +
    • +

      +that files can be passed(?def) between application procedure + invocations through any mechanism except through files known to + Swift through the mapping mechanism (there is some exception here + for external datasets - there are a separate set of assertions + that hold for external datasets) +

      +
    • +
    • +

      +that application executables will run on any particular site of + those available, or than any combination of applications will run + on the same or different sites. +

      +
    • +
    +
    +
    +

    5.2. How Swift implements the site execution model

    +

    This section describes the implementation of the semantics described in +the previous section.

    +

    Swift executes application procedures on one or more sites.

    +

    Each site consists of:

    +
      +
    • +

      +worker nodes. There is some execution mechanism through which + the Swift client side executable can execute its wrapper script + on those worker nodes. This is commonly GRAM or Falkon or coasters. +

      +
    • +
    • +

      +a site-shared file system. This site shared filesystem is + accessible through some file transfer mechanism from the Swift + client side executable. This is commonly GridFTP or coasters. This + site shared filesystem is also accessible through the posix file + system on all worker nodes, mounted at the same location as seen + through the file transfer mechanism. Swift is configured with the + location of some site working directory on that site-shared file + system. +

      +
    • +
    +

    There is no assumption that the site shared file system for one site is +accessible from another site.

    +

    For each workflow run, on each site that is used by that run, a run +directory is created in the site working directory, by the Swift client +side.

    +

    In that run directory are placed several subdirectories:

    +
      +
    • +

      +shared/ - site shared files cache +

      +
    • +
    • +

      +kickstart/ - when kickstart is used, kickstart record files for + each job that has generated a kickstart record. +

      +
    • +
    • +

      +info/ - wrapper script log files +

      +
    • +
    • +

      +status/ - job status files +

      +
    • +
    • +

      +jobs/ - application workspace directories (optionally placed + here - see below) +

      +
    • +
    +

    Application execution looks like this:

    +

    For each application procedure call:

    +

    The Swift client side selects a site; copies the input files for that +procedure call to the site shared file cache if they are not already in +the cache, using the file transfer mechanism; and then invokes the +wrapper script on that site using the execution mechanism.

    +

    The wrapper script creates the application workspace directory; places +the input files for that job into the application workspace directory +using either cp or ln -s (depending on a configuration option); +executes the application unix executable; copies output files from the +application workspace directory to the site shared directory using cp; +creates a status file under the status/ directory; and exits, +returning control to the Swift client side. Logs created during the +execution of the wrapper script are stored under the info/ directory.

    +

    The Swift client side then checks for the presence of and deletes a +status file indicating success; and copies files from the site shared +directory to the appropriate client side location.

    +

    The job directory is created (in the default mode) under the jobs/ +directory. However, it can be created under an arbitrary other path, +which allows it to be created on a different file system (such as a +worker node local file system in the case that the worker node has a +local file system).

    +

    +swift-site-model.png +

    +
    +
    +
    +
    +

    6. Technical overview of the Swift architecture

    +
    +

    This section attempts to provide a technical overview of the Swift +architecture.

    +
    +

    6.1. Execution layer

    +

    The execution layer causes an application program (in the form of a unix +executable) to be executed either locally or remotely.

    +

    The two main choices are local unix execution and execution through +GRAM. Other options are available, and user provided code can also be +plugged in.

    +

    The kickstart utility can be used to capture environmental +information at execution time to aid in debugging and provenance capture.

    +
    +
    +

    6.2. SwiftScript language compilation layer

    +

    Step i: text to XML intermediate form parser/processor. parser written +in ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the +intermediate language is in resources/XDTM.xsd.

    +

    Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads +the XML intermediate form. compiles to karajan workflow language - for +example, expressions are converted from SwiftScript syntax into Karajan +syntax, and function invocations become karajan function invocations +with various modifications to parameters to accomodate return parameters +and dataset handling.

    +
    +
    +

    6.3. Swift/karajan library layer

    +

    Some Swift functionality is provided in the form of Karajan libraries +that are used at runtime by the Karajan workflows that the Swift +compiler generates.

    +
    +
    +
    +
    +

    7. Ways in which Swift can be extended

    +
    +

    Swift is extensible in a number of ways. It is possible to add mappers +to accomodate different filesystem arrangements, site selectors to +change how Swift decides where to run each job, and job submission +interfaces to submit jobs through different mechanisms.

    +

    A number of mappers are provided as part of the Swift release and +documented in the mappers section. New mappers can be +implemented in Java by implementing the org.griphyn.vdl.mapping.Mapper +interface. The Swift tutorial +http://www.ci.uchicago.edu/swift/guides/tutorial.php contains a simple +example of this.

    +

    Swift provides a default site selector, the Adaptive Scheduler. New site +selectors can be plugged in by implementing the +org.globus.cog.karajan.scheduler.Scheduler interface and modifying +libexec/scheduler.xml and etc/karajan.properties to refer to the new +scheduler.

    +

    Execution providers and filesystem providers, which allow to Swift to +execute jobs and to stage files in and out through mechanisms such as +GRAM and GridFTP can be implemented as Java CoG kit providers.

    +
    +
    +
    +

    8. Function reference

    +
    +

    This section details functions that are available for use in the +SwiftScript language.

    +
    +

    8.1. @arg

    +

    Takes a command line parameter name as a string parameter and an +optional default value and returns the value of that string parameter +from the command line. If no default value is specified and the command +line parameter is missing, an error is generated. If a default value is +specified and the command line parameter is missing, @arg will return +the default value.

    +

    Command line parameters recognized by @arg begin with exactly one +hyphen and need to be positioned after the script name.

    +

    For example:

    +
    +
    +
    trace(@arg("myparam"));
    +trace(@arg("optionalparam", "defaultvalue"));
    +
    +
    +
    $ swift arg.swift -myparam=hello
    +Swift v0.3-dev r1674 (modified locally)
    +
    +RunID: 20080220-1548-ylc4pmda
    +SwiftScript trace: defaultvalue
    +SwiftScript trace: hello
    +
    +
    +

    8.2. @extractint

    +

    @extractint(file) will read the specified file, parse an integer from +the file contents and return that integer.

    +
    +
    +

    8.3. @filename

    +

    @filename(v) will return a string containing the filename(s) for the +file(s) mapped to the variable v. When more than one filename is +returned, the filenames will be space separated inside a single string +return value.

    +
    +
    +

    8.4. @filenames

    +

    @filenames(v) will return multiple values (!) containing the +filename(s) for the file(s) mapped to the variable v. (compare to + at filename)

    +
    +
    +

    8.5. @regexp

    +

    @regexp(input,pattern,replacement) will apply regular expression +substitution using the Java java.util.regexp API +http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html. +For example:

    +
    +
    +
    string v =  @regexp("abcdefghi", "c(def)g","monkey");
    +

    will assign the value "abmonkeyhi" to the variable v.

    +
    +
    +

    8.6. @strcat

    +

    @strcat(a,b,c,d,…) will return a string containing all of the +strings passed as parameters joined into a single string. There may be +any number of parameters.

    +

    The + operator concatenates two strings: @strcat(a,b) is the same as +a + b

    +
    +
    +

    8.7. @strcut

    +

    @strcut(input,pattern) will match the regular expression in the +pattern parameter against the supplied input string and return the +section that matches the first matching parenthesised group.

    +

    For example:

    +
    +
    +
    string t = "my name is John and i like puppies.";
    +string name = @strcut(t, "my name is ([^ ]*) ");
    +string out = @strcat("Your name is ",name);
    +trace(out);
    +

    will output the message: Your name is John.

    +
    +
    +

    8.8. @strsplit

    +

    @strsplit(input,pattern) will split the input string based on +separators that match the given pattern and return a string array. +(since Swift 0.9)

    +

    Example:

    +
    +
    +
    string t = "my name is John and i like puppies.";
    +string words[] = @strsplit(t, "\\s");
    +foreach word in words {
    +    trace(word);
    +}
    +

    will output one word of the sentence on each line (though not +necessarily in order, due to the fact that foreach iterations execute in +parallel).

    +
    +
    +

    8.9. @toint

    +

    @toint(input) will parse its input string into an integer. This can be +used with @arg to pass input parameters to a SwiftScript program as +integers.

    +
    +
    +
    +
    +

    9. Built-in procedure reference

    +
    +

    This section details built-in procedures that are available for use in +the SwiftScript language.

    +
    +

    9.1. readData

    +

    readData will read data from a specified file.

    +

    The format of the input file is controlled by the type of the return value.

    +

    For scalar return types, such as int, the specified file should contain +a single value of that type.

    +

    For arrays of scalars, the specified file should contain one value per +line.

    +

    For structs of scalars, the file should contain two rows. The first row +should be structure member names separated by whitespace. The second row +should be the corresponding values for each structure member, separated +by whitespace, in the same order as the header row.

    +

    For arrays of structs, the file should contain a heading row listing +structure member names separated by whitespace. There should be one row +for each element of the array, with structure member elements listed in +the same order as the header row and separated by whitespace. (since +Swift 0.4)

    +
    +
    +

    9.2. readdata2

    +

    readdata2 will read data from a specified file, like readdata, but +using a different file format more closely related to that used by the +ext mapper.

    +

    Input files should list, one per line, a path into a Swift structure, +and the value for that position in the structure:

    +
    +
    +
    rows[0].columns[0] = 0
    +rows[0].columns[1] = 2
    +rows[0].columns[2] = 4
    +rows[1].columns[0] = 1
    +rows[1].columns[1] = 3
    +rows[1].columns[2] = 5
    +

    which can be read into a structure defined like this:

    +
    +
    +
    type vector {
    +        int columns[];
    +}
    +
    +type matrix {
    +        vector rows[];
    +}
    +
    +matrix m;
    +
    +m = readData2("readData2.in");
    +

    (since Swift 0.7)

    +
    +
    +

    9.3. trace

    +

    trace will log its parameters. By default these will appear on both +stdout and in the run log file. Some formatting occurs to produce the +log message. The particular output format should not be relied upon. +(since Swift 0.4)

    +
    +
    +

    9.4. writeData

    +

    writeData will write out data structures in the format described for +readData

    +
    +
    +
    +
    +

    10. Swift configuration properties

    +
    +

    Various aspects of the behavior of the Swift Engine can be configured +through properties. The Swift Engine recognizes a global, per +installation properties file which can found in etc/swift.properties +in the Swift installation directory and a user properties file which can +be created by each user in ~/.swift/swift.properties. The Swift Engine +will first load the global properties file. It will then try to load the +user properties file. If a user properties file is found, individual +properties explicitly set in that file will override the respective +properties in the global properties file. Furthermore, some of the +properties can be overridden directly using command line arguments to +the swift command.

    +

    Swift properties are specified in the following format:

    +

    <name>=<value>

    +

    The value can contain variables which will be expanded when the +properties file is read. Expansion is performed when the name of the +variable is used inside the standard shell dereference construct: +configuration file:

    +

    Swift Configuration Variables

    +

    swift.home

    +
    +
    +
    Points to the Swift installation directory ($SWIFT_HOME). In
    +general, this should not be set as Swift can find its own
    +installation directory, and incorrectly setting it may impair the
    +correct functionality of Swift.
    +
    +

    user.name

    +
    +
    +
    The name of the current logged in user.
    +
    +

    user.home

    +
    +
    +
    The user's home directory.
    +
    +

    The following is a list of valid Swift properties:

    +

    Swift Properties

    +

    caching.algorithm

    +
    +
    +
    Valid values: LRU
    +
    +
    +
    +
    Default value: LRU
    +
    +
    +
    +
    Swift caches files that are staged in on remote resources, and files
    +that are produced remotely by applications, such that they can be
    +re-used if needed without being transfered again. However, the
    +amount of remote file system space to be used for caching can be
    +limited using the swift:storagesize profile entry in the sites.xml file. Example:
    +
    +
    +
    +
    <pool handle="example" sysinfo="INTEL32::LINUX">
    +<gridftp url="gsiftp://example.org" storage="/scratch/swift" major="2" minor="4" patch="3"/>
    +<jobmanager universe="vanilla" url="example.org/jobmanager-pbs" major="2" minor="4" patch="3"/>
    +<workdirectory>/scratch/swift</workdirectory>
    +<profile namespace="SWIFT" key="storagesize">20000000</profile>
    +</pool>
    +
    +
    +
    The decision of which files to keep in the cache and which files to
    +remove is made considering the value of the caching.algorithm
    +property. Currently, the only available value for this property is
    +LRU, which would cause the least recently used files to be deleted
    +first.
    +
    +

    clustering.enabled

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Enables clustering.
    +
    +

    clustering.min.time

    +
    +
    +
    Valid values: <int>
    +
    +
    +
    +
    Default value: 60
    +
    +
    +
    +
    Indicates the threshold wall time for clustering, in seconds. Jobs
    +that have a wall time smaller than the value of this property will
    +be considered for clustering.
    +
    +

    clustering.queue.delay

    +
    +
    +
    Valid values: <int>
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    This property indicates the interval, in seconds, at which the
    +clustering queue is processed.
    +
    +

    execution.retries

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 2
    +
    +
    +
    +
    The number of time a job will be retried if it fails (giving a
    +maximum of 1 + execution.retries attempts at execution)
    +
    +

    foreach.max.threads

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 1024
    +
    +
    +
    +
    Limits the number of concurrent iterations that each foreach
    +statement can have at one time. This conserves memory for swift
    +programs that have large numbers of iterations (which would
    +otherwise all be executed in parallel). (since Swift 0.9)
    +
    +

    ip.address

    +
    +
    +
    Valid values: <ipaddress>
    +
    +
    +
    +
    Default value: N/A
    +
    +
    +
    +
    The Globus GRAM service uses a callback mechanism to send
    +notifications about the status of submitted jobs. The callback
    +mechanism requires that the Swift client be reachable from the hosts
    +the GRAM services are running on. Normally, Swift can detect the
    +correct IP address of the client machine. However, in certain cases
    +(such as the client machine having more than one network interface)
    +the automatic detection mechanism is not reliable. In such cases,
    +the IP address of the Swift client machine can be specified using
    +this property. The value of this property must be a numeric address
    +without quotes.
    +
    +
    +
    +
    This option is deprecated and the hostname property should be used
    +instead.
    +
    +

    kickstart.always.transfer

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls when output from Kickstart is transfered back
    +to the submit site, if Kickstart is enabled. When set to false,
    +Kickstart output is only transfered for jobs that fail. If set to
    +true, Kickstart output is transfered after every job is completed
    +or failed.
    +
    +

    kickstart.enabled

    +
    +
    +
    Valid values: true, false, maybe
    +
    +
    +
    +
    Default value: maybe
    +
    +
    +
    +
    This option allows controlling of when Swift uses Kickstart.
    +A value of false disables the use of Kickstart,
    +while a value of true enables the use of Kickstart, in which case
    +sites specified in the sites.xml file must have valid
    +gridlaunch attributes. The maybe value will enable the use of
    +Kickstart only on sites that have the gridlaunch attribute
    +specified.
    +
    +

    lazy.errors

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Swift can report application errors in two modes, depending on the
    +value of this property. If set to false, Swift will report the
    +first error encountered and immediately stop execution. If set to
    +true, Swift will attempt to run as much as possible from a
    +SwiftScript program before stopping execution and reporting all
    +errors encountered.
    +
    +
    +
    +
    When developing SwiftScript programs, using the default value of
    +false can make the program easier to debug. However in production
    +runs, using true will allow more of a SwiftScript program to be
    +run before Swift aborts execution.
    +
    +

    pgraph

    +
    +
    +
    Valid values: true, false, <file>
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Swift can generate a Graphviz <http://www.graphviz.org/> file
    +representing the structure of the SwiftScript program it has run. If
    +this property is set to true, Swift will save the provenance graph
    +in a file named by concatenating the program name and the instance
    +ID (e.g. helloworld-ht0adgi315l61.dot).
    +
    +
    +
    +
    If set to false, no provenance graph will be generated. If a file
    +name is used, then the provenance graph will be saved in the
    +specified file.
    +
    +
    +
    +
    The generated dot file can be rendered into a graphical form using
    +Graphviz <http://www.graphviz.org/>, for example with a command-line
    +such as:
    +
    +
    +
    +
    $ swift -pgraph graph1.dot q1.swift
    +$ dot -ograph.png -Tpng graph1.dot
    +

    pgraph.graph.options

    +
    +
    +
    Valid values: <string>
    +
    +
    +
    +
    Default value: splines="compound", rankdir="TB"
    +
    +
    +
    +
    This property specifies a Graphviz <http://www.graphviz.org>
    +specific set of parameters for the graph.
    +
    +

    pgraph.node.options

    +
    +
    +
    Valid values: <string>
    +
    +
    +
    +
    Default value: color="seagreen", style="filled"
    +
    +
    +
    +
    Used to specify a set of Graphviz <http://www.graphviz.org> specific
    +properties for the nodes in the graph.
    +
    +

    provenance.log

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls whether the log file will contain provenance
    +information enabling this will increase the size of log files,
    +sometimes significantly.
    +
    +

    replication.enabled

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Enables/disables replication. Replication is used to deal with jobs
    +sitting in batch queues for abnormally large amounts of time. If
    +replication is enabled and certain conditions are met, Swift creates
    +and submits replicas of jobs, and allows multiple instances of a job
    +to compete.
    +
    +

    replication.limit

    +
    +
    +
    Valid values: positive integers
    +
    +
    +
    +
    Default value: 3
    +
    +
    +
    +
    The maximum number of replicas that Swift should attempt.
    +
    +

    sitedir.keep

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    Indicates whether the working directory on the remote site should be
    +left intact even when a run completes successfully. This can be used
    +to inspect the site working directory for debugging purposes.
    +
    +

    sites.file

    +
    +
    +
    Valid values: <file>
    +
    +
    +
    +
    Default value: ${swift.home}/etc/sites.xml
    +
    +
    +
    +
    Points to the location of the site catalog, which contains a list of
    +all sites that Swift should use.
    +
    +

    status.mode

    +
    +
    +
    Valid values: files, provider
    +
    +
    +
    +
    Default value: files
    +
    +
    +
    +
    Controls how Swift will communicate the result code of running user
    +programs from workers to the submit side. In files mode, a file
    +indicating success or failure will be created on the site shared
    +filesystem. In provider mode, the execution provider job status
    +will be used.
    +
    +
    +
    +
    provider mode requires the underlying job execution system to
    +correctly return exit codes. In at least the cases of GRAM2, and
    +clusters used with any provider, exit codes are not returned, and so
    +files mode must be used in those cases. Otherwise, provider mode
    +can be used to reduce the amount of filesystem access. (since Swift
    +0.8)
    +
    +

    tc.file

    +
    +
    +
    Valid values: <file>
    +
    +
    +
    +
    Default value: ${swift.home}/etc/tc.data
    +
    +
    +
    +
    Points to the location of the transformation catalog file which
    +contains information about installed applications. Details about the
    +format of the transformation catalog can be found here
    +<http://vds.uchicago.edu/vds/doc/userguide/html/H_TransformationCatalog.html>.
    +
    +

    tcp.port.range

    +
    +
    +
    Valid values: <start>,<end> where start and end are integers
    +
    +
    +
    +
    Default value: none
    +
    +
    +
    +
    A TCP port range can be specified to restrict the ports on which
    +GRAM callback services are started. This is likely needed if your
    +submit host is behind a firewall, in which case the firewall should
    +be configured to allow incoming connections on ports in the range.
    +
    +

    throttle.file.operations

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 8
    +
    +
    +
    +
    Limits the total number of concurrent file operations that can
    +happen at any given time. File operations (like transfers) require
    +an exclusive connection to a site. These connections can be
    +expensive to establish. A large number of concurrent file operations
    +may cause Swift to attempt to establish many such expensive
    +connections to various sites. Limiting the number of concurrent file
    +operations causes Swift to use a small number of cached connections
    +and achieve better overall performance.
    +
    +

    throttle.host.submit

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 2
    +
    +
    +
    +
    Limits the number of concurrent submissions for any of the sites
    +Swift will try to send jobs to. In other words it guarantees that no
    +more than the value of this throttle jobs sent to any site will be
    +concurrently in a state of being submitted.
    +
    +

    throttle.score.job.factor

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    The Swift scheduler has the ability to limit the number of
    +concurrent jobs allowed on a site based on the performance history
    +of that site. Each site is assigned a score (initially 1), which can
    +increase or decrease based on whether the site yields successful or
    +faulty job runs. The score for a site can take values in the (0.1,
    +100) interval. The number of allowed jobs is calculated using the
    +following formula:
    +
    +
    +
    +
    2 + score*throttle.score.job.factor
    +
    +
    +
    +
    This means a site will always be allowed at least two concurrent
    +jobs and at most 2 + 100*throttle.score.job.factor. With a default
    +of 4 this means at least 2 jobs and at most 402.
    +
    +
    +
    +
    This parameter can also be set per site using the jobThrottle
    +profile key in a site catalog entry.
    +
    +

    throttle.submit

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    Limits the number of concurrent submissions for a run. This throttle
    +only limits the number of concurrent tasks (jobs) that are being
    +sent to sites, not the total number of concurrent jobs that can be
    +run. The submission stage in GRAM is one of the most CPU expensive
    +stages (due mostly to the mutual authentication and delegation).
    +Having too many concurrent submissions can overload either or both
    +the submit host CPU and the remote host/head node causing degraded
    +performance.
    +
    +

    throttle.transfers

    +
    +
    +
    Valid values: <int>, off
    +
    +
    +
    +
    Default value: 4
    +
    +
    +
    +
    Limits the total number of concurrent file transfers that can happen
    +at any given time. File transfers consume bandwidth. Too many
    +concurrent transfers can cause the network to be overloaded
    +preventing various other signaling traffic from flowing properly.
    +
    +

    ticker.disable

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    When set to true, suppresses the output progress ticker that Swift
    +sends to the console every few seconds during a run (since Swift 0.9)
    +
    +

    wrapper.invocation.mode

    +
    +
    +
    Valid values: absolute, relative
    +
    +
    +
    +
    Default value: absolute
    +
    +
    +
    +
    Determines if Swift remote wrappers will be executed by specifying
    +an absolute path, or a path relative to the job initial working
    +directory. In most cases, execution will be successful with either
    +option. However, some execution sites ignore the specified initial
    +working directory, and so absolute must be used. Conversely on
    +some sites, job directories appear in a different place on the
    +worker node file system than on the filesystem access node, with the
    +execution system handling translation of the job initial working
    +directory. In such cases, relative mode must be used. (since Swift
    +0.9)
    +
    +

    wrapper.parameter.mode

    +
    +
    +
    Controls how Swift will supply parameters to the remote wrapper
    +script. args mode will pass parameters on the command line. Some
    +execution systems do not pass commandline parameters sufficiently
    +cleanly for Swift to operate correctly. files mode will pass
    +parameters through an additional input file (since Swift 0.95). This
    +provides a cleaner communication channel for parameters, at the
    +expense of transferring an additional file for each job invocation.
    +
    +

    wrapperlog.always.transfer

    +
    +
    +
    Valid values: true, false
    +
    +
    +
    +
    Default value: false
    +
    +
    +
    +
    This property controls when output from the Swift remote wrapper is
    +transfered back to the submit site. When set to false, wrapper
    +logs are only transfered for jobs that fail. If set to true,
    +wrapper logs are transfered after every job is completed or failed.
    +
    +

    Example:

    +
    +
    +
    sites.file=${vds.home}/etc/sites.xml
    +tc.file=${vds.home}/etc/tc.data
    +ip.address=192.168.0.1
    +
    +
    +
    +

    11. Profiles

    +
    +

    Profiles are configuration parameters than can be specified either for +sites or for transformation catalog entries. They influence the +behaviour of Swift towards that site (for example, by changing the load +Swift will place on that sites) or when running a particular procedure.

    +

    Profile entries for a site are specified in the site catalog. Profile +entries for specific procedures are specified in the transformation +catalog.

    +
    +

    11.1. Karajan namespace

    +

    maxSubmitRate limits the maximum rate of job submission, in jobs per +second. For example:

    +
    +
    +
    <profile namespace="karajan" key="maxSubmitRate">0.2</profile>
    +

    will limit job submission to 0.2 jobs per second (or equivalently, one +job every five seconds).

    +

    jobThrottle allows the job throttle factor (see Swift property +throttle.score.job.factor to be +set per site.

    +

    initialScore allows the initial score for rate limiting and site +selection to be set to a value other than 0.

    +

    delayBase controls how much a site will be delayed when it performs +poorly. With each reduction in a sites score by 1, the delay between +execution attempts will increase by a factor of delayBase.

    +

    status.mode allows the status.mode property to be set per-site instead +of for an entire run. See the Swift configuration properties section for +more information. (since Swift 0.8)

    +
    +
    +

    11.2. swift namespace

    +

    storagesize limits the amount of space that will be used on the remote +site for temporary files. When more than that amount of space is used, +the remote temporary file cache will be cleared using the algorithm +specified in the caching.algorithm property.

    +

    wrapperInterpreter - The wrapper interpreter indicates the command +(executable) to be used to run the Swift wrapper script. The default is +"/bin/bash" on Unix sites and "cscript.exe" on Windows sites.

    +

    wrapperInterpreterOptions - Allows specifying additional options to the +executable used to run the Swift wrapper. The defaults are no options on +Unix sites and "Nologo" on Windows sites.

    +

    wrapperScript - Specifies the name of the wrapper script to be used on a +site. The defaults are "_swiftwrap" on Unix sites and "_swiftwrap.vbs" +on Windows sites. If you specify a custom wrapper script, it must be +present in the "libexec" directory of the Swift installation.

    +

    cleanupCommand Indicates the command to be run at the end of a Swift +run to clean up the run directories on a remote site. Defaults are +"/bin/rm" on Unix sites and "cmd.exe" on Windows sites

    +

    cleanupCommandOptions Specifies the options to be passed to the +cleanup command above. The options are passed in the argument list to +the cleanup command. After the options, the last argument is the +directory to be deleted. The default on Unix sites is "-rf". The default +on Windows sites is ["/C", "del", "/Q"].

    +
    +
    +

    11.3. Globus namespace

    +

    maxwalltime specifies a walltime limit for each job, in minutes.

    +

    The following formats are recognized:

    +
      +
    • +

      +Minutes +

      +
    • +
    • +

      +Hours:Minutes +

      +
    • +
    • +

      +Hours:Minutes:Seconds +

      +
    • +
    +

    Example:

    +
    +
    +
    localhost       echo    /bin/echo       INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="00:20:00"
    +

    When replication is enabled (see replication), then +walltime will also be enforced at the Swift client side: when a job has +been active for more than twice the maxwalltime, Swift will kill the job +and regard it as failed.

    +

    When clustering is used, maxwalltime will be used to select which jobs +will be clustered together. More information on this is available in the +clustering section.

    +

    When coasters as used, maxwalltime influences the default coaster +worker maxwalltime, and which jobs will be sent to which workers. More +information on this is available in the coasters section.

    +

    queue is used by the PBS, GRAM2 and GRAM4 providers. This profile +entry specifies which queue jobs will be submitted to. The valid queue +names are site-specific.

    +

    host_types specifies the types of host that are permissible for a job +to run on. The valid values are site-specific. This profile entry is +used by the GRAM2 and GRAM4 providers.

    +

    condor_requirements allows a requirements string to be specified when +Condor is used as an LRM behind GRAM2. Example:

    +
    +
    +
    <profile
    +namespace="globus" key="condor_requirements">Arch == "X86_64" || Arch="INTEL"</profile>
    +

    slots When using coasters, this parameter specifies the +maximum number of jobs/blocks that the coaster scheduler will have +running at any given time. The default is 20.

    +

    workersPerNode - This parameter determines how many coaster workers are +started one each compute node. The default value is 1.

    +

    nodeGranularity - When allocating a coaster worker block, this parameter +restricts the number of nodes in a block to a multiple of this value. +The total number of workers will then be a multiple of workersPerNode * +nodeGranularity. The default value is 1.

    +

    allocationStepSize - Each time the coaster block scheduler computes a +schedule, it will attempt to allocate a number of slots from the number +of available slots (limited using the above slots profile). This +parameter specifies the maximum fraction of slots that are allocated in +one schedule. Default is 0.1.

    +

    lowOverallocation - Overallocation is a function of the walltime of a +job which determines how long (time-wise) a worker job will be. For +example, if a number of 10s jobs are submitted to the coaster service, +and the overallocation for 10s jobs is 10, the coaster scheduler will +attempt to start worker jobs that have a walltime of 100s. The +overallocation is controlled by manipulating the end-points of an +overallocation function. The low endpoint, specified by this parameter, +is the overallocation for a 1s job. The high endpoint is the +overallocation for a (theoretical) job of infinite length. The +overallocation for job sizes in the [1s, +inf) interval is determined +using an exponential decay function: overallocation(walltime) = walltime +* (lowOverallocation - highOverallocation) * exp(-walltime * +overallocationDecayFactor) + highOverallocation The default value of +lowOverallocation is 10.

    +

    highOverallocation - The high overallocation endpoint (as described +above). Default: 1

    +

    overallocationDecayFactor - The decay factor for the overallocation +curve. Default 0.001 (1e-3).

    +

    spread - When a large number of jobs is submitted to the a coaster +service, the work is divided into blocks. This parameter allows a rough +control of the relative sizes of those blocks. A value of 0 indicates +that all work should be divided equally between the blocks (and blocks +will therefore have equal sizes). A value of 1 indicates the largest +possible spread. The existence of the spread parameter is based on the +assumption that smaller overall jobs will generally spend less time in +the queue than larger jobs. By submitting blocks of different sizes, +submitted jobs may be finished quicker by smaller blocks. Default: 0.9.

    +

    reserve - Reserve time is a time in the allocation of a worker that sits +at the end of the worker time and is useable only for critical +operations. For example, a job will not be submitted to a worker if it +overlaps its reserve time, but a job that (due to inaccurate walltime +specification) runs into the reserve time will not be killed (note that +once the worker exceeds its walltime, the queuing system will kill the +job anyway). Default 10 (s).

    +

    maxnodes - Determines the maximum number of nodes that can be allocated +in one coaster block. Default: unlimited.

    +

    maxtime - Indicates the maximum walltime that a coaster block can have. +Default: unlimited.

    +

    remoteMonitorEnabled - If set to "true", the client side will get a +Swing window showing, graphically, the state of the coaster scheduler +(blocks, jobs, etc.). Default: false

    +
    +
    +

    11.4. env namespace

    +

    Profile keys set in the env namespace will be set in the unix +environment of the executed job. Some environment variables influence +the worker-side behaviour of Swift:

    +

    PATHPREFIX - set in env namespace profiles. This path is prefixed onto +the start of the PATH when jobs are executed. It can be more useful +than setting the PATH environment variable directly, because setting +PATH will cause the execution site’s default path to be lost.

    +

    SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift +will use the path specified here as a worker-node local temporary +directory to copy input files to before running a job. If unset, Swift +will keep input files on the site-shared filesystem. In some cases, +copying to a worker-node local directory can be much faster than having +applications access the site-shared filesystem directly.

    +

    SWIFT_EXTRA_INFO - set in env namespace profiles. If set, then Swift +will execute the command specified in SWIFT_EXTRA_INFO on execution +sites immediately before each application execution, and will record the +stdout of that command in the wrapper info log file for that job. This +is intended to allow software version and other arbitrary information +about the remote site to be gathered and returned to the submit side. +(since Swift 0.9)

    +
    +
    +
    +
    +

    12. The Site Catalog - sites.xml

    +
    +

    The site catalog lists details of each site that Swift can use. The +default file contains one entry for local execution, and a large number +of commented-out example entries for other sites.

    +

    By default, the site catalog is stored in etc/sites.xml. This path can +be overridden with the sites.file configuration property, either in +the Swift configuration file or on the command line.

    +

    The sites file is formatted as XML. It consists of <pool> elements, +one for each site that Swift will use.

    +
    +

    12.1. Pool element

    +

    Each pool element must have a handle attribute, giving a symbolic +name for the site. This can be any name, but must correspond to entries +for that site in the transformation catalog.

    +

    Optionally, the gridlaunch attribute can be used to specify the path +to kickstart on the site.

    +

    Each pool must specify a file transfer method, an execution method and +a remote working directory. Optionally, profile settings can +be specified.

    +
    +
    +

    12.2. File transfer method

    +

    Transfer methods are specified with either the <gridftp> element or +the <filesystem> element.

    +

    To use gridftp or local filesystem copy, use the <gridftp> element:

    +
    +
    +
    <gridftp  url="gsiftp://evitable.ci.uchicago.edu" />
    +

    The url attribute may specify a GridFTP server, using the gsiftp URI +scheme; or it may specify that filesystem copying will be used (which +assumes that the site has access to the same filesystem as the +submitting machine) using the URI local://localhost.

    +

    Filesystem access using scp (the SSH copy protocol) can be specified +using the <filesystem> element:

    +
    +
    +
    <filesystem url="www11.i2u2.org" provider="ssh"/>
    +

    For additional ssh configuration information, see the ssh execution +provider documentation below.

    +

    Filesystem access using CoG coasters can be also be +specified using the <filesystem> element. More detail about +configuring that can be found in the CoG coasters section.

    +
    +
    +

    12.3. Execution method

    +

    Execution methods may be specified either with the <jobmanager> or +<execution> element.

    +

    The <jobmanager> element can be used to specify execution through +GRAM2. For example,

    +
    +
    +
    <jobmanager universe="vanilla" url="evitable.ci.uchicago.edu/jobmanager-fork" major="2" />
    +

    The universe attribute should always be set to vanilla. The url +attribute should specify the name of the GRAM2 gatekeeper host, and the +name of the jobmanager to use. The major attribute should always be set +to 2.

    +

    The <execution> element can be used to specify execution through other +execution providers:

    +

    To use GRAM4, specify the gt4 provider. For example:

    +
    +
    +
    <execution provider="gt4" jobmanager="PBS" url="tg-grid.uc.teragrid.org" />
    +

    The url attribute should specify the GRAM4 submission site. The +jobmanager attribute should specify which GRAM4 jobmanager will be used.

    +

    For local execution, the local provider should be used, like this:

    +
    +
    +
    <execution provider="local" url="none" />
    +

    For PBS execution, the pbs provider should be used:

    +
    +
    +
    <execution provider="pbs" url="none" />
    +

    The GLOBUS::queue profile key can be used to +specify which PBS queue jobs will be submitted to.

    +

    For execution through a local Condor installation, the condor provider +should be used. This provider can run jobs either in the default vanilla +universe, or can use Condor-G to run jobs on remote sites.

    +

    When running locally, only the <execution> element needs to be specified:

    +
    +
    +
    <execution provider="condor" url="none" />
    +

    When running with Condor-G, it is necessary to specify the Condor grid +universe and the contact string for the remote site. For example:

    +
    +
    +
    <execution provider="condor" />
    +<profile namespace="globus" key="jobType">grid</profile>
    +<profile namespace="globus" key="gridResource">gt2 belhaven-1.renci.org/jobmanager-fork</profile>
    +

    For execution through SSH, the ssh provider should be used:

    +
    +
    +
    <execution url="www11.i2u2.org" provider="ssh"/>
    +

    with configuration made in ~/.ssh/auth.defaults with the string +www11.i2u2.org changed to the appropriate host name:

    +
    +
    +
    www11.i2u2.org.type=key
    +www11.i2u2.org.username=hategan
    +www11.i2u2.org.key=/home/mike/.ssh/i2u2portal
    +www11.i2u2.org.passphrase=XXXX
    +

    For execution using the CoG Coaster mechanism, the coaster +provider should be used:

    +
    +
    +
    <execution provider="coaster" url="tg-grid.uc.teragrid.org"
    +    jobmanager="gt2:gt2:pbs" />
    +

    More details about configuration of coasters can be found in the section +on coasters.

    +
    +
    +

    12.4. Work directory

    +

    The workdirectory element specifies where on the site files can be +stored.

    +
    +
    +
    <workdirectory>/home/benc</workdirectory>
    +

    This file must be accessible through the transfer mechanism specified in +the <gridftp> element and also mounted on all worker nodes that will +be used for execution. A shared cluster scratch filesystem is +appropriate for this.

    +
    +
    +

    12.5. Profiles

    +

    Profile keys can be specified using the <profile> element. +For example:

    +
    +
    +
    <profile namespace="globus" key="queue">fast</profile>
    +

    The site catalog format is an evolution of the VDS site catalog format +which is documented here +http://vds.uchicago.edu/vds/doc/userguide/html/H_SiteCatalog.html.

    +
    +
    +
    +
    +

    13. The Transformation Catalog - tc.data

    +
    +

    The transformation catalog lists where application executables are +located on remote sites.

    +

    By default, the site catalog is stored in etc/tc.data. This path can +be overridden with the tc.file configuration property, either in the +Swift configuration file or on the command line.

    +

    The format is one line per executable per site, with fields separated by +tabs. Spaces cannot be used to separate fields.

    +

    Some example entries:

    +
    +
    +
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    +TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="0:1"
    +

    The fields are: site, transformation name, executable path, installation +status, platform, and profile entrys.

    +

    The site field should correspond to a site name listed in the sites catalog.

    +

    The transformation name should correspond to the transformation name +used in a SwiftScript app procedure.

    +

    The executable path should specify where the particular executable is +located on that site.

    +

    The installation status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively.

    +

    The profiles field should be set to null if no profile entries are to +be specified, or should contain the profile entries separated by +semicolons.

    +
    +
    +
    +

    14. Build options

    +
    +

    See the Swift download page +http://www.ci.uchicago.edu/swift/downloads/ for instructions on +downloading and building Swift from source. When building, various build +options can be supplied on the ant commandline. These are summarised here:

    +

    with-provider-condor - build with CoG condor provider

    +

    with-provider-coaster - build with CoG coaster provider (see the +section on coasters). Since 0.8, coasters are always built, +and this option has no effect.

    +

    with-provider-deef - build with Falkon provider deef. In order for +this option to work, it is necessary to check out the provider-deef code +in the cog/modules directory alongside swift:

    +
    +
    +
    $ cd cog/modules
    +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef
    +$ cd ../swift
    +$ ant -Dwith-provider-deef=true redist
    +

    with-provider-wonky - build with provider-wonky, an execution provider +that provides delays and unreliability for the purposes of testing +Swift’s fault tolerance mechanisms. In order for this option to work, it +is necessary to check out the provider-wonky code in the |cog/modules| +directory alongside swift:

    +
    +
    +
    $ cd cog/modules
    +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky
    +$ cd ../swift|*
    +$ ant -Dwith-provider-wonky=true redist
    +

    no-supporting - produces a distribution without supporting commands +such as grid-proxy-init. This is intended for when the Swift +distribution will be used in an environment where those commands are +already provided by other packages, where the Swift package should be +providing only Swift commands, and where the presence of commands such +as grid-proxy-init from the Swift distribution in the path will mask the +presence of those commands from their true distribution package such as +a Globus Toolkit package.

    +
    +
    +
    $ ant -Dno-supporting=true redist
    +
    +
    +
    +

    15. Kickstart

    +
    +

    Kickstart is a tool that can be used to gather various information about +the remote execution environment for each job that Swift tries to run.

    +

    For each job, Kickstart generates an XML invocation record. By default +this record is staged back to the submit host if the job fails.

    +

    Before it can be used it must be installed on the remote site and the +sites file must be configured to point to kickstart.

    +

    Kickstart can be downloaded as part of the Pegasus worker package +available from the worker packages section of the Pegasus download page +http://pegasus.isi.edu/code.php.

    +

    Untar the relevant worker package somewhere where it is visible to all +of the worker nodes on the remote execution machine (such as in a shared +application filesystem).

    +

    Now configure the gridlaunch attribute of the sites catalog to point to +that path, by adding a gridlaunch attribute to the pool element in +the site catalog:

    +
    +
    +
    <pool handle="example" gridlaunch="/usr/local/bin/kickstart" sysinfo="INTEL32::LINUX">
    +...
    +</pool>
    +

    There are various kickstat.* properties, which have sensible default +values. These are documented in the properties section.

    +
    +
    +
    +

    16. Reliability mechanisms

    +
    +

    This section details reliabilty mechanisms in Swift: retries, restarts +and replication.

    +
    +

    16.1. Retries

    +

    If an application procedure execution fails, Swift will attempt that +execution again repeatedly until it succeeds, up until the limit defined +in the execution.retries configuration property.

    +

    Site selection will occur for retried jobs in the same way that it +happens for new jobs. Retried jobs may run on the same site or may run +on a different site.

    +

    If the retry limit execution.retries is reached for an application +procedure, then that application procedure will fail. This will cause +the entire run to fail - either immediately (if the lazy.errors +property is false) or after all other possible work has been attempted +(if the lazy.errors property is true).

    +
    +
    +

    16.2. Restarts

    +

    If a run fails, Swift can resume the program from the point of failure. +When a run fails, a restart log file will be left behind in a file named +using the unique job ID and a .rlog extension. This restart log can +then be passed to a subsequent Swift invocation using the -resume +parameter. Swift will resume execution, avoiding execution of +invocations that have previously completed successfully. The SwiftScript +source file and input data files should not be modified between runs.

    +

    Every run creates a restart log file with a named composed of the file +name of the workflow being executed, an invocation ID, a numeric ID, and +the .rlog extension. For example, example.swift, when executed, +could produce the following restart log file: +example-ht0adgi315l61.0.rlog. Normally, if the run completes +successfully, the restart log file is deleted. If however the workflow +fails, swift can use the restart log file to continue execution from a +point before the failure occurred. In order to restart from a restart +log file, the -resume logfile argument can be used after the +SwiftScript program file name. Example:

    +
    +
    +
    $ swift -resume example-ht0adgi315l61.0.rlog example.swift.
    +
    +
    +

    16.3. Replication

    +

    When an execution job has been waiting in a site queue for a certain +period of time, Swift can resubmit replicas of that job (up to the limit +defined in the replication.limit configuration property). When any of +those jobs moves from queued to active state, all of the other replicas +will be cancelled.

    +

    This is intended to deal with situations where some sites have a +substantially longer (sometimes effectively infinite) queue time than +other sites. Selecting those slower sites can cause a very large delay +in overall run time.

    +

    Replication can be enabled by setting the replication.enabled +configuration property to true. The maximum number of replicas that +will be submitted for a job is controlled by the replication.limit +configuration property.

    +

    When replication is enabled, Swift will also enforce the maxwalltime +profile setting for jobs as documented in the profiles section.

    +
    +
    +
    +
    +

    17. Clustering

    +
    +

    Swift can group a number of short job submissions into a single larger +job submission to minimize overhead involved in launching jobs (for +example, caused by security negotiation and queuing delay). In general, +CoG coasters should be used in preference to the clustering +mechanism documented in this section.

    +

    By default, clustering is disabled. It can be activated by setting the +clustering.enabled property to true.

    +

    A job is eligible for clustering if the GLOBUS::maxwalltime profile +is specified in the tc.data entry for that job, and its value is +less than the value of the clustering.min.time property.

    +

    Two or more jobs are considered compatible if they share the same site +and do not have conflicting profiles (e.g. different values for the same +environment variable).

    +

    When a submitted job is eligible for clustering, it will be put in a +clustering queue rather than being submitted to a remote site. The +clustering queue is processed at intervals specified by the +clustering.queue.delay property. The +processing of the clustering queue consists of selecting compatible jobs +and grouping them into clusters whose maximum wall time does not exceed +twice the value of the clustering.min.time property.

    +
    +
    +
    +

    18. Coasters

    +
    +

    Coasters were introduced in Swift v0.6 as an experimental feature.

    +

    In many applications, Swift performance can be greatly enhanced by the +use of CoG coasters. CoG coasters provide a low-overhead job submission +and file transfer mechanism suited for the execution of short jobs (on +the order of a few seconds) and the transfer of small files (on the +order of a few kilobytes) for which other grid protocols such as GRAM +and GridFTP are poorly suited.

    +

    The coaster mechanism submits a head job using some other execution +mechanism such as GRAM, and for each worker node that will be used in a +remote cluster, it submits a worker job, again using some other +execution mechanism such as GRAM. Details on the design of the coaster +mechanism can be found here. http://wiki.cogkit.org/wiki/Coasters

    +

    The head job manages file transfers and the dispatch of execution jobs +to workers. Much of the overhead associated with other grid protocols +(such as authentication and authorization, and allocation of worker +nodes by the site’s local resource manager) is reduced, because that +overhead is associated with the allocation of a coaster head or coaster +worker, rather than with every Swift-level procedure invocation; +potentially hundreds or thousands of Swift-level procedure invocations +can be run through a single worker.

    +

    Coasters can be configured for use in two situations: job execution and +file transfer.

    +

    To use for job execution, specify a sites.xml execution element like this:

    +
    +
    +
    <execution provider="coaster" jobmanager="gt2:gt2:pbs" url="grid.myhost.org">
    +

    The jobmanager string contains more detail than with other providers. It +contains either two or three colon separated fields: 1:the provider to +be use to execute the coaster head job - this provider will submit from +the Swift client side environment. Commonly this will be one of the GRAM +providers; 2: the provider to be used to execute coaster worker jobs. +This provider will be used to submit from the coaster head job +environment, so a local scheduler provider can sometimes be used instead +of GRAM. 3: optionally, the jobmanager to be used when submitting worker +job using the provider specified in field 2.

    +

    To use for file transfer, specify a sites.xml filesystem element like this:

    +
    +
    +
    <filesystem provider="coaster" url="gt2://grid.myhost.org" />
    +

    The url parameter should be a pseudo-URI formed with the URI scheme +being the name of the provider to use to submit the coaster head job, +and the hostname portion being the hostname to be used to execute the +coaster head job. Note that this provider and hostname will be used for +execution of a coaster head job, not for file transfer; so for example, +a GRAM endpoint should be specified here rather than a GridFTP endpoint.

    +

    Coasters are affected by the following profile settings, which are +documented in the Globus namespace profile section:

    +
    + +++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Profile keyBrief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a +multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a +block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a +block’s walltime be if all jobs are infinitely long

    overallocationDecayFactor

    How quickly should the overallocation curve +tend towards the highOverallocation as job walltimes get larger

    spread

    By how much should worker blocks vary in worker size

    workersPerNode

    How many coaster workers to run per execution node

    reserve

    How many seconds to reserve in a block’s walltime for +starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block

    remoteMonitorEnabled

    If true, show a graphical display of the status of +the coaster service

    +
    +
    +
    +
    +

    19. How-To Tips for Specific User Communities

    +
    +
    +

    19.1. Saving Logs - for UChicago CI Users

    +

    If you have a UChicago Computation Institute account, run this command +in your submit directory after each run. It will copy all your logs and +kickstart records into a directory at the CI for reporting, usage +tracking, support and debugging.

    +
    +
    +
    rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose
    +
    +
    +

    19.2. Specifying TeraGrid allocations

    +

    TeraGrid users with no default project or with several project +allocations can specify a project allocation using a profile key in the +site catalog entry for a TeraGrid site:

    +
    +
    +
    <profile namespace="globus" key="project">TG-CCR080002N</profile>
    +

    More information on the TeraGrid allocations process can be found here +http://www.teragrid.org/userinfo/access/allocations.php.

    +
    +
    +

    19.3. Launching MPI jobs from Swift

    +

    Here is an example of running a simple MPI program.

    +

    In SwiftScript, we make an invocation that does not look any different +from any other invocation. In the below code, we do not have any input +files, and have two output files on stdout and stderr:

    +
    +
    +
    type file;
    +
    +(file o, file e) p() {
    +    app {
    +        mpi stdout=@filename(o) stderr=@filename(e);
    +    }
    +}
    +
    +file mpiout <"mpi.out">;
    +file mpierr <"mpi.err">;
    +
    +(mpiout, mpierr) = p();
    +

    Now we define how mpi will run in tc.data:

    +
    +
    +
    tguc    mpi             /home/benc/mpi/mpi.sh   INSTALLED       INTEL32::LINUX GLOBUS::host_xcount=3
    +

    mpi.sh is a wrapper script that launches the MPI program. It must be +installed on the remote site:

    +
    +
    +
    #!/bin/bash
    +mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out
    +

    Because of the way that Swift runs its server side code, +provider-specific MPI modes (such as GRAM jobType=mpi) should not be +used. Instead, the mpirun command should be explicitly invoked.

    +
    +
    +

    19.4. Running on Windows

    +

    Since 10/11/09, the development version of Swift has the ability to run +on a Windows machine, as well as the ability to submit jobs to a Windows +site (provided that an appropriate provider is used).

    +

    In order to launch Swift on Windows, use the provided batch file +(swift.bat). In certain cases, when a large number of jar libraries are +present in the Swift lib directory and depending on the exact location +of the Swift installation, the classpath environment variable that the +Swift batch launcher tries to create may be larger than what Windows can +handle. In such a case, either install Swift in a directory closer to +the root of the disk (say, c:\swift) or remove non-essential jar files +from the Swift lib directory.

    +

    Due to the large differences between Windows and Unix environments, +Swift must use environment specific tools to achieve some of its goals. +In particular, each Swift executable is launched using a wrapper script. +This script is a Bourne Shell script. On Windows machines, which have no +Bourne Shell interpreter installed by default, the Windows Scripting +Host is used instead, and the wrapper script is written in VBScript. +Similarly, when cleaning up after a run, the "/bin/rm" command available +in typical Unix environments must be replaced by the "del" shell command.

    +

    It is important to note that in order to select the proper set of tools +to use, Swift must know when a site runs under Windows. To inform Swift +of this, specify the "sysinfo" attribute for the "pool" element in the +site catalog. For example:

    +
    +
    +
    <pool handle="localhost" sysinfo="INTEL32::WINDOWS">
    +...
    +</pool>
    +
    +
    +
    +
    +

    + + + Added: trunk/docs/userguide/userguide.txt =================================================================== --- trunk/docs/userguide/userguide.txt (rev 0) +++ trunk/docs/userguide/userguide.txt 2011-05-16 19:38:01 UTC (rev 4480) @@ -0,0 +1,3000 @@ +Swift User Guide +================ + +:toc: +:icons: +:website: http://www.ci.uchicago.edu/swift/guides/userguide.php +:numbered: + +Overview +-------- +This manual provides reference material for Swift: the SwiftScript +language and the Swift runtime system. For introductory material, +consult the Swift tutorial +. + +Swift is a data-oriented coarse grained scripting language that supports +dataset typing and mapping, dataset iteration, conditional branching, +and procedural composition. + +Swift programs (or workflows) are written in a language called +SwiftScript. + +SwiftScript programs are dataflow oriented - they are primarily +concerned with processing (possibly large) collections of data files, by +invoking programs to do that processing. Swift handles execution of such +programs on remote sites by choosing sites, handling the staging of +input and output files to and from the chosen sites and remote execution +of program code. + + +The SwiftScript Language +------------------------ + +Language basics +~~~~~~~~~~~~~~~ +A Swift script describes data, application components, invocations of +applications components, and the inter-relations (data flow) between +those invocations. + +Data is represented in a script by strongly-typed single-assignment +variables. The syntax superficially resembles C and Java. For example, +{ and } characters are used to enclose blocks of statements. + +Types in Swift can be atomic or composite. An atomic type can be +either a primitive type or a mapped type. Swift provides a fixed set +of primitive types, such as integer and string. A mapped type +indicates that the actual data does not reside in CPU addressable memory +(as it would in conventional programming languages), but in POSIX-like +files. Composite types are further subdivided into structures and +arrays. Structures are similar in most respects to structure types in +other languages. Arrays use numeric indices, but are sparse. They can +contain elements of any type, including other array types, but all +elements in an array must be of the same type. We often refer to +instances of composites of mapped types as datasets. + +image:type-hierarchy.png[] + +Mapped type and composite type variable declarations can be annotated +with a mapping descriptor indicating the file(s) that make up that +dataset. For example, the following line declares a variable named +photo with type image. It additionally declares that the data for +this variable is stored in a single file named shane.jpeg. + +[java] +source~~~~ +image photo <"shane.jpeg">; +source~~~~ + +Component programs of scripts are declared in an app declaration, with +the description of the command line syntax for that program and a list +of input and output data. An app block describes a functional/dataflow +style interface to imperative components. + +For example, the following example lists a procedure which makes use of +the ImageMagick convert command to +rotate a supplied image by a specified angle: + +[java] +source~~~~ +app (image output) rotate(image input) { + convert "-rotate" angle @input @output; +} +source~~~~ + +A procedure is invoked using the familiar syntax: + +[java] +source~~~~ +rotated = rotate(photo, 180); +source~~~~ + +While this looks like an assignment, the actual unix level execution +consists of invoking the command line specified in the app +declaration, with variables on the left of the assignment bound to the +output parameters, and variables to the right of the procedure +invocation passed as inputs. + +The examples above have used the type image without any definition of +that type. We can declare it as a marker type which has no structure +exposed to SwiftScript: + +[java] +source~~~~ +type image; +source~~~~ + +This does not indicate that the data is unstructured; but it indicates +that the structure of the data is not exposed to SwiftScript. Instead, +SwiftScript will treat variables of this type as individual opaque files. + +With mechanisms to declare types, map variables to data files, and +declare and invoke procedures, we can build a complete (albeit simple) +script: + +[java] +source~~~~ +type image; +image photo <"shane.jpeg">; +image rotated <"rotated.jpeg">; + +app (image output) rotate(image input, int angle) { + convert "-rotate" angle @input @output; +} + +rotated = rotate(photo, 180); +source~~~~ + +This script can be invoked from the command line: +[txt] +source~~~~ + $ ls *.jpeg + shane.jpeg + $ swift example.swift + ... + $ ls *.jpeg + shane.jpeg rotated.jpeg +source~~~~ + +This executes a single convert command, hiding from the user features +such as remote multisite execution and fault tolerance that will be +discussed in a later section. + +.Figure 1. shane.jpeg +image:userguide-shane.jpeg[] + +.Figure 2. rotated.jpeg +image:userguide-rotated.jpeg[] + + +Arrays and Parallel Execution +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Arrays of values can be declared using the [] suffix. An array be +mapped to a collection of files, one element per file, by using a +different form of mapping expression. For example, the filesys_mapper +maps all files matching a particular unix glob pattern into an array: + +[java] +source~~~~ +file frames[] ; +source~~~~ + +The foreach construct can be used to apply the same block of code to +each element of an array: + +[java] +source~~~~ +foreach f,ix in frames { + output[ix] = rotate(frames, 180); +} +source~~~~ + +Sequential iteration can be expressed using the iterate construct: + +[java] +source~~~~ +step[0] = initialCondition(); +iterate ix { + step[ix] = simulate(step[ix-1]); +} +source~~~~ + +This fragment will initialise the 0-th element of the step array to +some initial condition, and then repeatedly run the simulate +procedure, using each execution's outputs as input to the next step. + +Ordering of execution +~~~~~~~~~~~~~~~~~~~~~ +Non-array variables are single-assignment, which means that they must +be assigned to exactly one value during execution. A procedure or +expression will be executed when all of its input parameters have been +assigned values. As a result of such execution, more variables may +become assigned, possibly allowing further parts of the script to execute. + +In this way, scripts are implicitly parallel. Aside from serialisation +implied by these dataflow dependencies, execution of component programs +can proceed in parallel. + +In this fragment, execution of procedures p and q can happen in +parallel: + +[java] +source~~~~ +y=p(x); +z=q(x); +source~~~~ + +while in this fragment, execution is serialised by the variable y, +with procedure p executing before q. + +[java] +source~~~~ +y=p(x); +z=q(y); +source~~~~ + +Arrays in SwiftScript are more monotonic - a generalisation of being +assignment. Knowledge about the content of an array increases during +execution, but cannot otherwise change. Each element of the array is +itself single assignment or monotonic (depending on its type). During a +run all values for an array are eventually known, and that array is +regarded as closed. + +Statements which deal with the array as a whole will often wait for the +array to be closed before executing (thus, a closed array is the +equivalent of a non-array type being assigned). However, a foreach +statement will apply its body to elements of an array as they become +known. It will not wait until the array is closed. + +Consider this script: +[java] +source~~~~ +file a[]; +file b[]; +foreach v,i in a { + b[i] = p(v); +} +a[0] = r(); +a[1] = s(); +source~~~~ + +Initially, the foreach statement will have nothing to execute, as the +array a has not been assigned any values. The procedures r and s +will execute. As soon as either of them is finished, the corresponding +invocation of procedure p will occur. After both r and s have +completed, the array a will be closed since no other statements in the +script make an assignment to a. + + +Compound procedures +~~~~~~~~~~~~~~~~~~~ + +As with many other programming languages, procedures consisting of +SwiftScript code can be defined. These differ from the previously +mentioned procedures declared with the app keyword, as they invoke +other SwiftScript procedures rather than a component program. + +[java] +source~~~~ +(file output) process (file input) { + file intermediate; + intermediate = first(input); + output = second(intermediate); +} + +file x <"x.txt">; +file y <"y.txt">; +y = process(x); +source~~~~ + +This will invoke two procedures, with an intermediate data file named +anonymously connecting the first and second procedures. + +Ordering of execution is generally determined by execution of app +procedures, not by any containing compound procedures. In this code block: + +[java] +source~~~~ +(file a, file b) A() { + a = A1(); + b = A2(); +} +file x, y, s, t; +(x,y) = A(); +s = S(x); +t = S(y); +source~~~~ + +then a valid execution order is: A1 S(x) A2 S(y). The compound +procedure A does not have to have fully completed for its return +values to be used by subsequent statements. + + +More about types +~~~~~~~~~~~~~~~~ + +Each variable and procedure parameter in SwiftScript is strongly typed. +Types are used to structure data, to aid in debugging and checking +program correctness and to influence how Swift interacts with data. + +The image type declared in previous examples is a marker type. +Marker types indicate that data for a variable is stored in a single +file with no further structure exposed at the SwiftScript level. + +Arrays have been mentioned above, in the arrays section. A code block +may be applied to each element of an array using foreach; or +individual elements may be references using [] notation. + +There are a number of primitive types: + +[options="header"] +|================ +|type |contains +|int |integers +|string |strings of text +|float |floating point numbers, that behave the same as Java doubles +|boolean |true/false +|================ + + +Complex types may be defined using the type keyword: + +[java] +source~~~~ +type headerfile; +type voxelfile; +type volume { + headerfile h; + voxelfile v; +} +source~~~~ + +Members of a complex type can be accessed using the . operator: + +[java] +source~~~~ +volume brain; +o = p(brain.h); +source~~~~ + +Sometimes data may be stored in a form that does not fit with Swift's +file-and-site model; for example, data might be stored in an RDBMS on +some database server. In that case, a variable can be declared to have +external type. This indicates that Swift should use the variable to +determine execution dependency, but should not attempt other data +management; for example, it will not perform any form of data stage-in +or stage-out it will not manage local data caches on sites; and it will +not enforce component program atomicity on data output. This can add +substantial responsibility to component programs, in exchange for +allowing arbitrary data storage and access methods to be plugged in to +scripts. + +[java] +source~~~~ +type file; + +app (external o) populateDatabase() { + populationProgram; +} + +app (file o) analyseDatabase(external i) { + analysisProgram @o; +} + +external database; +file result <"results.txt">; + +database = populateDatabase(); +result = analyseDatabase(database); +source~~~~ + +Some external database is represented by the database variable. The +populateDatabase procedure populates the database with some data, and +the analyseDatabase procedure performs some subsequent analysis on +that database. The declaration of database contains no mapping; and +the procedures which use database do not reference them in any way; +the description of database is entirely outside of the script. The +single assignment and execution ordering rules will still apply though; +populateDatabase will always be run before analyseDatabase. + +Data model +~~~~~~~~~~ +Data processed by Swift is strongly typed. It may be take the form of +values in memory or as out-of-core files on disk. Language constructs +called mappers specify how each piece of data is stored. + + +Mappers +~~~~~~~ +When a DSHandle represents a data file (or container of datafiles), it +is associated with a mapper. The mapper is used to identify which files +belong to that DSHandle. + +A dataset's physical representation is declared by a mapping descriptor, +which defines how each element in the dataset's logical schema is stored +in, and fetched from, physical structures such as directories, files, +and remote servers. + +Mappers are parameterized to take into account properties such as +varying dataset location. In order to access a dataset, we need to know +three things: its type, its mapping, and the value(s) of any +parameter(s) associated with the mapping descriptor. For example, if we +want to describe a dataset, of type imagefile, and whose physical +representation is a file called "file1.bin" located at +"/home/yongzh/data/", then the dataset might be declared as follows: + +[java] +source~~~~ +imagefile f1 +source~~~~ + +The above example declares a dataset called f1, which uses a single file +mapper to map a file from a specific location. + +SwiftScript has a simplified syntax for this case, since +single_file_mapper is frequently used: + +[java] +source~~~~ +binaryfile f1<"/home/yongzh/data/file1.bin"> +source~~~~ + +Swift comes with a number of mappers that handle common mapping +patterns. These are documented in the mappers section of this +guide. + +More technical details about SwiftScript +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The syntax of SwiftScript has a superficial resemblance to C and Java. +For example, { and } characters are used to enclose blocks of statements. + +A SwiftScript program consists of a number of statements. Statements may +declare types, procedures and variables, assign values to variables, and +express operations over arrays. + + +Variables +^^^^^^^^^ +Variables in SwiftScript are declared to be of a specific type. +Assignments to those variables must be data of that type. SwiftScript +variables are single-assignment - a value may be assigned to a variable +at most once. This assignment can happen at declaration time or later on +in execution. When an attempt to read from a variable that has not yet +been assigned is made, the code performing the read is suspended until +that variable has been written to. This forms the basis for Swift's +ability to parallelise execution - all code will execute in parallel +unless there are variables shared between the code that cause sequencing. + + +Variable Declarations +^^^^^^^^^^^^^^^^^^^^^ +Variable declaration statements declare new variables. They can +optionally assign a value to them or map those variables to on-disk files. + +Declaration statements have the general form: + +[java] +source~~~~ +typename variablename ( | = initialValue ) ; +source~~~~ + +The format of the mapping expression is defined in the Mappers section. +initialValue may be either an expression or a procedure call that +returns a single value. + +Variables can also be declared in a multivalued-procedure statement, +described in another section. + + +Assignment Statements +^^^^^^^^^^^^^^^^^^^^^ +Assignment statements assign values to previously declared variables. +Assignments may only be made to variables that have not already been +assigned. Assignment statements have the general form: + +[java] +source~~~~ +variable = value; +source~~~~ + +where value can be either an expression or a procedure call that returns +a single value. + +Variables can also be assigned in a multivalued-procedure statement, +described in another section. + + +Procedures +~~~~~~~~~~ +There are two kinds of procedure: An atomic procedure, which describes +how an external program can be executed; and compound procedures which +consist of a sequence of SwiftScript statements. + +A procedure declaration defines the name of a procedure and its input +and output parameters. SwiftScript procedures can take multiple inputs +and produce multiple outputs. Inputs are specified to the right of the +function name, and outputs are specified to the left. For example: + +[java] +source~~~~ +(type3 out1, type4 out2) myproc (type1 in1, type2 in2) +source~~~~ + +The above example declares a procedure called myproc, which has two +inputs in1 (of type type1) and in2 (of type type2) and two +outputs out1 (of type type3) and out2 (of type type4). + +A procedure input parameter can be an optional parameter in which case +it must be declared with a default value. When calling a procedure, both +positional parameter and named parameter passings can be passed, +provided that all optional parameters are declared after the required +parameters and any optional parameter is bound using keyword parameter +passing. For example, if myproc1 is defined as: + +[java] +source~~~~ +(binaryfile bf) myproc1 (int i, string s="foo") +source~~~~ + +Then that procedure can be called like this, omitting the optional +[java] +source~~~~ +parameter s: +binaryfile mybf = myproc1(1); +source~~~~ + +or like this supplying a value for the optional parameter s: +[java] +source~~~~ +binaryfile mybf = myproc1 (1, s="bar"); +source~~~~ + +Atomic procedures +^^^^^^^^^^^^^^^^^ +An atomic procedure specifies how to invoke an external executable +program, and how logical data types are mapped to command line arguments. + +Atomic procedures are defined with the app keyword: + +[java] +source~~~~ +app (binaryfile bf) myproc (int i, string s="foo") { + myapp i s @filename(bf); +} +source~~~~ + +which specifies that myproc invokes an executable called myapp, +passing the values of i, s and the filename of bf as command line +arguments. + + +Compound procedures +^^^^^^^^^^^^^^^^^^^ +A compound procedure contains a set of SwiftScript statements: + +[java] +source~~~~ +(type2 b) foo_bar (type1 a) { + type3 c; + c = foo(a); // c holds the result of foo + b = bar(c); // c is an input to bar +} +source~~~~ + +Control Constructs +~~~~~~~~~~~~~~~~~~ +SwiftScript provides if, switch, foreach, and iterate +constructs, with syntax and semantics similar to comparable constructs +in other high-level languages. + + +foreach +^^^^^^^ +The foreach construct is used to apply a block of statements to each +element in an array. For example: + +[java] +source~~~~ +check_order (file a[]) { + foreach f in a { + compute(f); + } +} +source~~~~ + +foreach statements have the general form: + +[java] +source~~~~ +foreach controlvariable (,index) in expression { + statements +} +source~~~~ + +The block of statements is evaluated once for each element in +expression which must be an array, with controlvariable set to the +corresponding element and index (if specified) set to the integer +position in the array that is being iterated over. + + +if +^^ +The if statement allows one of two blocks of statements to be +executed, based on a boolean predicate. if statements generally have +the form: + +[java] +source~~~~ +if(predicate) { + statements +} else { + statements +} +source~~~~ + +where predicate is a boolean expression. + + +switch +^^^^^^ + +switch expressions allow one of a selection of blocks to be chosen +based on the value of a numerical control expression. switch +statements take the general form: + +[java] +source~~~~ +switch(controlExpression) { + case n1: + statements2 + case n2: + statements2 + [...] + default: + statements +} +source~~~~ + +The control expression is evaluated, the resulting numerical value used +to select a corresponding case, and the statements belonging to that +case block are evaluated. If no case corresponds, then the statements +belonging to the default block are evaluated. + +Unlike C or Java switch statements, execution does not fall through to +subsequent case blocks, and no break statement is necessary at the +end of each block. + + +iterate +^^^^^^^ +iterate expressions allow a block of code to be evaluated repeatedly, +with an integer parameter sweeping upwards from 0 until a termination +condition holds. + +The general form is: + +[java] +source~~~~ +iterate var { + statements; +} until (terminationExpression); +source~~~~ + +with the variable var starting at 0 and increasing by one in each +iteration. That variable is in scope in the statements block and when +evaluating the termination expression. + +Operators +~~~~~~~~~ +The following infix operators are available for use in SwiftScript +expressions. + +[options="header"] +|================= +|operator|purpose +|+|numeric addition; string concatenation +|-|numeric subtraction +|*|numeric multiplication +|/|floating point division +|%/|integer division +|%%|integer remainder of division +|== !=|comparison and not-equal-to +|< > <= >=|numerical ordering +|&& \|\||boolean and, or +|!|boolean not +|================= + +Global constants +~~~~~~~~~~~~~~~~ + +At the top level of a SwiftScript program, the global modified may be +added to a declaration so that it is visible throughout the program, +rather than only at the top level of the program. This allows global +constants (of any type) to be defined. (since Swift 0.10) + + +Imports +~~~~~~~ +The import directive can be used to import definitions from another +SwiftScript file. (since Swift 0.10) + +For example, a SwiftScript program might contain this: + +[java] +source~~~~ +import defs; +file f; +source~~~~ + +which would import the content of defs.swift in the current directory: + +[java] +source~~~~ +type file; +source~~~~ + +Imported files are read from the current working directory. + +There is no requirement that a module is imported only once. If a module +is imported multiple times, for example in different files, then Swift +will only process the imports once. + +Imports may contain anything that is valid in a SwiftScript program, +including code that causes remote execution. + +Mappers +------- +Mappers provide a mechanism to specify the layout of mapped datasets on +disk. This is needed when Swift must access files to transfer them to +remote sites for execution or to pass to applications. + +Swift provides a number of mappers that are useful in common cases. This +section details those standard mappers. For more complex cases, it is +possible to write application-specific mappers in Java and use them +within a SwiftScript program. + + +The single file mapper +~~~~~~~~~~~~~~~~~~~~~~ +The single_file_mapper maps a single physical file to a dataset. + +[options="header"] +|======================= +|Swift variable|Filename +|f|myfile +|f[0]|INVALID +|f.bar|INVALID +|======================= + +[options="header"] +|================= +|parameter|meaning +|file|The location of the physical file including path and file name. +|================= + +Example: +[java] +source~~~~ +file f ; +source~~~~ + +There is a simplified syntax for this mapper: +[java] +source~~~~ +file f <"plot_outfile_param">; +source~~~~ + +The simple mapper +~~~~~~~~~~~~~~~~~ +The simple_mapper maps a file or a list of files into an array by +prefix, suffix, and pattern. If more than one file is matched, each of +the file names will be mapped as a subelement of the dataset. + +[options="header"] +|==================== +|Parameter|Meaning +|location|A directory that the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +|pattern|A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored. +|==================== + +[java] +source~~~~ +type file; +file f ; +source~~~~ + +The above maps all filenames that start with foo and have an extension +.txt into file f. + +[options="header"] +|================ +|Swift variable|Filename +|f|foo.txt +|================= +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting(string m) {. + app { + echo m stdout=@filename(t); + } +} + +messagefile outfile ; + +outfile = greeting("hi"); +source~~~~ + +This will output the string 'hi' to the file foo.txt. + +The simple_mapper can be used to map arrays. It will map the array +index into the filename between the prefix and suffix. + +[java] +source~~~~ +type messagefile; + +(messagefile t) greeting(string m) { + app { + echo m stdout=@filename(t); + } +} + +messagefile outfile[] ; + +outfile[0] = greeting("hello"); +outfile[1] = greeting("middle"); +outfile[2] = greeting("goodbye"); +source~~~~ + +[options="header"] +|======================= +|Swift variable|Filename +|outfile[0]|baz0000.txt +|outfile[1]|baz0001.txt +|outfile[2]|baz0002.txt +|======================= + +simple_mapper can be used to map structures. It will map the name of +the structure member into the filename, between the prefix and the suffix. + +[java] +source~~~~ +type messagefile; + +type mystruct { + messagefile left; + messagefile right; +}; + +(messagefile t) greeting(string m) { + app { + echo m stdout=@filename(t); + } +} + +mystruct out ; + +out.left = greeting("hello"); +out.right = greeting("goodbye"); +source~~~~ + +This will output the string "hello" into the file qux.left.txt and the +string "goodbye" into the file qux.right.txt. + +[options="header"] +|======================= +|Swift variable|Filename +|out.left|quxleft.txt +|out.right|quxright.txt +|======================= + +concurrent mapper +~~~~~~~~~~~~~~~~~ +concurrent_mapper is almost the same as the simple mapper, except that +it is used to map an output file, and the filename generated will +contain an extract sequence that is unique. This mapper is the default +mapper for variables when no mapper is specified. + + +[options="header"] +|================= +|Parameter|Meaning +|location|A directory that the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +pattern A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. When this mapper is used to specify +output filenames, pattern is ignored. +|================= + +Example: +[java] +source~~~~ +file f1; +file f2 ; +source~~~~ + +The above example would use concurrent mapper for f1 and f2, and +generate f2 filename with prefix "foo" and extension ".txt" + + +File system mapper +~~~~~~~~~~~~~~~~~~ +filesys_mapper is similar to the simple mapper, but maps a file or a +list of files to an array. Each of the filename is mapped as an element +in the array. The order of files in the resulting array is not defined. + +TODO: note on difference between location as a relative vs absolute path +wrt staging to remote location - as mihael said: It's because you +specify that location in the mapper. Try location="." instead of +location="/sandbox/..." + +[options="header"] +|====================== +|parameter|meaning +|location|The directory where the files are located. +|prefix|The prefix of the files +|suffix|The suffix of the files, for instance: ".txt" +|pattern|A UNIX glob style pattern, for instance: "*foo*" would match +all file names that contain foo. +|====================== + +Example: +[java] +source~~~~ +file texts[] ; +source~~~~ + +The above example would map all filenames that start with "foo" and +have an extension ".txt" into the array texts. For example, if the +specified directory contains files: foo1.txt, footest.txt, +foo__1.txt, then the mapping might be: + +[options="header"] +|================= +|Swift variable|Filename +|texts[0]|footest.txt +|texts[1]|foo1.txt +|texts[2]|foo__1.txt +|================= + + + +fixed array mapper +~~~~~~~~~~~~~~~~~~ +The fixed_array_mapper maps from a string that contains a list of +filenames into a file array. + +[options="header"] +|================= +|parameter|Meaning +|files|A string that contains a list of filenames, separated by space, +comma or colon +|================= + +Example: + +[java] +source~~~~ +file texts[] ; +source~~~~ + +would cause a mapping like this: + +[options="header"] +|======== +|Swift variable|Filename +|texts[0]|file1.txt +|texts[1]|fileB.txt +|texts[2]|file3.txt +|======== + +array mapper +~~~~~~~~~~~~ +The array_mapper maps from an array of strings into a file + +[options="header"] +|============ +|parameter|meaning +|files|An array of strings containing one filename per element +|============== + +Example: +[java] +source~~~~ +string s[] = [ "a.txt", "b.txt", "c.txt" ]; + +file f[] ; +source~~~~ + +This will establish the mapping: + +[options="header"] +|========== +|Swift variable|Filename +|f[0]|a.txt +|f[1]|b.txt +|f[2]|c.txt +|========== + +regular expression mapper +~~~~~~~~~~~~~~~~~~~~~~~~~ +The regexp_mapper transforms one file name to another using regular +expression matching. + +[options="header"] +|========== +|parameter|meaning +|source|The source file name +|match|Regular expression pattern to match, use |()| to match whatever +regular expression is inside the parentheses, and indicate the start and +end of a group; the contents of a group can be retrieved with the +|\\number|special sequence (two backslashes are needed because the +backslash is an escape sequence introducer) +|transform|The pattern of the file name to transform to, use \number to +reference the group matched. +|========== + +Example: +[java] +source~~~~ +string s = "picture.gif"; +file f ; +source~~~~ + +This example transforms a string ending gif into one ending jpg and +maps that to a file. + +[options="header"] +|=========== +|Swift variable|Filename +|f|picture.jpg +|============= + + +csv mapper +~~~~~~~~~~ +The csv_mapper maps the content of a CSV (comma-separated value) file +into an array of structures. The dataset type needs to be correctly +defined to conform to the column names in the file. For instance, if the +file contains columns: name age GPA then the type needs to have member +elements like this: + +[java] +source~~~~ +type student { + file name; + file age; + file GPA; +} +source~~~~ + +If the file does not contain a header with column info, then the column +names are assumed as column1, column2, etc. + +[options="header"] +|============ +|Parameter|Meaning +|file|The name of the CSV file to read mappings from. +|header|Whether the file has a line describing header info; default is |true| +|skip|The number of lines to skip at the beginning (after header line); +default is 0. +|hdelim|Header field delimiter; default is the value of the |delim| parameter +|delim|Content field delimiters; defaults are space, tab and comma +|============= + +Example: +[java] +source~~~~ +student stus[] ; +source~~~~ + +The above example would read a list of student info from file +"stu_list.txt" and map them into a student array. By default, the file +should contain a header line specifying the names of the columns. If +stu_list.txt contains the following: + +[java] +source~~~~ +name,age,gpa +101-name.txt, 101-age.txt, 101-gpa.txt +name55.txt, age55.txt, age55.txt +q, r, s +source~~~~ + +then some of the mappings produced by this example would be: + +[options="header"] +|========= +|stus[0].name|101-name.txt +|stus[0].age|101-age.txt +|stus[0].gpa|101-gpa.txt +|stus[1].name|name55.txt +|stus[1].age|age55.txt +|stus[1].gpa|gpa55.txt +|stus[2].name|q +|stus[2].age|r +|stus[2].gpa|s +|========= + + + +external mapper +~~~~~~~~~~~~~~~ +The external mapper, ext maps based on the output of a supplied Unix +executable. + +[option="header"] +|============= +|parameter|meaning +|exec|The name of the executable (relative to the current directory, if +an absolute path is not specified) +|*|Other parameters are passed to the executable prefixed with a - symbol +|============== + +The output of the executable should consist of two columns of data, +separated by a space. The first column should be the path of the mapped +variable, in SwiftScript syntax (for example [2] means the 2nd element +of an array) or the symbol $ to represent the root of the mapped +variable. + +Example: With the following in mapper.sh, + +[shell] +source~~~~ +#!/bin/bash +echo "[2] qux" +echo "[0] foo" +echo "[1] bar" +source~~~~ + +then a mapping statement: + +[java] +source~~~~~ +student stus[] ; +source~~~~ + +would map + +[options="header"] +|============ +|Swift variable|Filename +|stus[0]|foo +|stus[1]|bar +|stus[2]|qux +|=========== + +Commands +-------- +The commands detailed in this section are available in the bin/ +directory of a Swift installation and can by run from the commandline if +that directory is placed on the PATH. + + +swift +~~~~~ +The swift command is the main command line tool for executing +SwiftScript programs. + + +Command-line Syntax +^^^^^^^^^^^^^^^^^^^ +The swift command is invoked as follows: swift [options] +SwiftScript-program [SwiftScript-arguments]* with options taken from the +following list, and SwiftScript-arguments made available to the +SwiftScript program through the @arg function. + +Swift command-line options + +-help or -h + + Display usage information + +-typecheck + + Does a typecheck of a SwiftScript program, instead of executing it. + +-dryrun + + Runs the SwiftScript program without submitting any jobs (can be + used to get a graph) + +-monitor + + Shows a graphical resource monitor + +-resume file + + Resumes the execution using a log file + +-config file + + Indicates the Swift configuration file to be used for this run. + Properties in this configuration file will override the default + properties. If individual command line arguments are used for + properties, they will override the contents of this file. + +-verbose | -v + + Increases the level of output that Swift produces on the console to + include more detail about the execution + +-debug | -d + + Increases the level of output that Swift produces on the console to + include lots of detail about the execution + +-logfile file + + Specifies a file where log messages should go to. By default Swift + uses the name of the program being run and a numeric index (e.g. + myworkflow.1.log) + +-runid identifier + + Specifies the run identifier. This must be unique for every + invocation and is used in several places to keep files from + different executions cleanly separated. By default, a datestamp and + random number are used to generate a run identifier. When using this + parameter, care should be taken to ensure that the run ID remains + unique with respect to all other run IDs that might be used, + irrespective of (at least) expected execution sites, program or user. + +-tui + + Displays an interactive text mode monitor during a run. (since Swift + 0.9) + +In addition, the following Swift properties can be set on the command line: + + * caching.algorithm + * clustering.enabled + * clustering.min.time + * clustering.queue.delay + * ip.address + * kickstart.always.transfer + * kickstart.enabled + * lazy.errors + * pgraph + * pgraph.graph.options + * pgraph.node.options + * sitedir.keep + * sites.file + * tc.file + * tcp.port.range + + +Return codes +^^^^^^^^^^^^ + +The swift command may exit with the following return codes: + +[options="header"] +|========= +|value|meaning +|0|success +|1|command line syntax error or missing project name +|2|error during execution +|3|error during compilation +|4|input file does not exist +|=========== + +Environment variables +^^^^^^^^^^^^^^^^^^^^^ + +The swift is influenced by the following environment variables: + +GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment +before running Swift. These can be set to inform Swift of the +configuration of your local firewall. More information can be found in +the Globus firewall How-to . + +COG_OPTS - set in the environment before running Swift. Options set in +this variable will be passed as parameters to the Java Virtual Machine +which will run Swift. The parameters vary between virtual machine +imlementations, but can usually be used to alter settings such as +maximum heap size. Typing 'java -help' will sometimes give a list of +commands. The Sun Java 1.4.2 command line options are documented here +. + + +swift-osg-ress-site-catalog +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +The swift-osg-ress-site-catalog command generates a site catalog based +on OSG 's ReSS information system +(since Swift 0.9) + +Usage: *swift-osg-ress-site-catalog [options]* + +--help + + Show help message + +--vo=[name] + + Set what VO to query ReSS for + +--engage-verified + + Only retrieve sites verified by the Engagement VO site verification + tests This can not be used together with |--vo|, as the query will + only work for sites advertising support for the Engagement VO. + + This option means information will be retrieved from the Engagement + collector instead of the top-level ReSS collector. + +--out=[filename] + + Write to [filename] instead of stdout + +--condor-g + + Generates sites files which will submit jobs using a local Condor-G + installation rather than through direct GRAM2 submission. (since + Swift 0.10) + + +swift-plot-log +~~~~~~~~~~~~~~ +swift-plot-log generates summaries of Swift run log files. + +Usage: swift-plot-log [logfile] [targets] + +When no targets are specified, swift-plog-log will generate an HTML +report for the run. When targets are specified, only those named targets +will be generated. + + +Executing app procedures +------------------------ +This section describes how Swift executes app procedures, and +requirements on the behaviour of application programs used in app +procedures. These requirements are primarily to ensure that the Swift +can run your application in different places and with the various fault +tolerance mechanisms in place. + + +Mapping of app semantics into unix process execution semantics +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This section describes how an app procedure invocation is translated +into a (remote) unix process execution. It does not describe the +mechanisms by which Swift performs that translation; that is described +in the next section. + +In this section, this example SwiftScript program is used for reference: + +[java] +source~~~~~ +type file; + +app (file o) count(file i) { + wc @i stdout=@o; +} + +file q <"input.txt">; +file r <"output.txt">; +source~~~~ + +The executable for wc will be looked up in tc.data. + +This unix executable will then be executed in some application +procedure workspace. This means: + +Each application procedure workspace will have an application workspace +directory. (TODO: can collapse terms application procedure workspace +and application workspace directory ? + +This application workspace directory will not be shared with any other +application procedure execution attempt; all application procedure +execution attempts will run with distinct application procedure +workspaces. (for the avoidance of doubt: If a SwiftScript procedure +invocation is subject to multiple application procedure execution +attempts (due to Swift-level restarts, retries or replication) then each +of those application procedure execution attempts will be made in a +different application procedure workspace. ) + +The application workspace directory will be a directory on a POSIX +filesystem accessible throughout the application execution by the +application executable. + +Before the application executable is executed: + + * The application workspace directory will exist. + + * The input files will exist inside the application workspace + directory (but not necessarily as direct children; there may be + subdirectories within the application workspace directory). + + * The input files will be those files mapped to input parameters + of the application procedure invocation. (In the example, this + means that the file input.txt will exist in the application + workspace directory) + + * For each input file dataset, it will be the case that @filename + or @filenames invoked with that dataset as a parameter will + return the path relative to the application workspace directory + for the file(s) that are associated with that dataset. (In the + example, that means that @i will evaluate to the path input.txt) + + * For each file-bound parameter of the Swift procedure invocation, + the associated files (determined by data type?) will always exist. + + * The input files must be treated as read only files. This may or + may not be enforced by unix file system permissions. They may or + may not be copies of the source file (conversely, they may be + links to the actual source file). + +During/after the application executable execution, the following must +be true: + + * If the application executable execution was successful (in the + opinion of the application executable), then the application + executable should exit with unix return code 0; if the + application executable execution was unsuccessful (in the opinion + of the application executable), then the application executable + should exit with unix return code not equal to 0. + + * Each file mapped from an output parameter of the SwiftScript + procedure call must exist. Files will be mapped in the same way as + for input files. + + (? Is it defined that output subdirectories will be precreated + before execution or should app executables expect to make them? + That's probably determined by the present behaviour of wrapper.sh) + + * Output produced by running the application executable on some + inputs should be the same no matter how many times, when or where + that application executable is run. 'The same' can vary depending + on application (for example, in an application it might be + acceptable for a PNG->JPEG conversion to produce different, + similar looking, output jpegs depending on the environment) + +Things to not assume: + + * anything about the path of the application workspace directory + + * that either the application workspace directory will be deleted or + will continue to exist or will remain unmodified after execution + has finished + + * that files can be passed(?def) between application procedure + invocations through any mechanism except through files known to + Swift through the mapping mechanism (there is some exception here + for external datasets - there are a separate set of assertions + that hold for external datasets) + + * that application executables will run on any particular site of + those available, or than any combination of applications will run + on the same or different sites. + + +How Swift implements the site execution model +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +This section describes the implementation of the semantics described in +the previous section. + +Swift executes application procedures on one or more sites. + +Each site consists of: + + * worker nodes. There is some execution mechanism through which + the Swift client side executable can execute its wrapper script + on those worker nodes. This is commonly GRAM or Falkon or coasters. + + * a site-shared file system. This site shared filesystem is + accessible through some file transfer mechanism from the Swift + client side executable. This is commonly GridFTP or coasters. This + site shared filesystem is also accessible through the posix file + system on all worker nodes, mounted at the same location as seen + through the file transfer mechanism. Swift is configured with the + location of some site working directory on that site-shared file + system. + +There is no assumption that the site shared file system for one site is +accessible from another site. + +For each workflow run, on each site that is used by that run, a run +directory is created in the site working directory, by the Swift client +side. + +In that run directory are placed several subdirectories: + + * shared/ - site shared files cache + + * kickstart/ - when kickstart is used, kickstart record files for + each job that has generated a kickstart record. + + * info/ - wrapper script log files + + * status/ - job status files + + * jobs/ - application workspace directories (optionally placed + here - see below) + +Application execution looks like this: + +For each application procedure call: + +The Swift client side selects a site; copies the input files for that +procedure call to the site shared file cache if they are not already in +the cache, using the file transfer mechanism; and then invokes the +wrapper script on that site using the execution mechanism. + +The wrapper script creates the application workspace directory; places +the input files for that job into the application workspace directory +using either cp or ln -s (depending on a configuration option); +executes the application unix executable; copies output files from the +application workspace directory to the site shared directory using cp; +creates a status file under the status/ directory; and exits, +returning control to the Swift client side. Logs created during the +execution of the wrapper script are stored under the info/ directory. + +The Swift client side then checks for the presence of and deletes a +status file indicating success; and copies files from the site shared +directory to the appropriate client side location. + +The job directory is created (in the default mode) under the jobs/ +directory. However, it can be created under an arbitrary other path, +which allows it to be created on a different file system (such as a +worker node local file system in the case that the worker node has a +local file system). + +image:swift-site-model.png[] + +Technical overview of the Swift architecture +-------------------------------------------- +This section attempts to provide a technical overview of the Swift +architecture. + +Execution layer +~~~~~~~~~~~~~~~ +The execution layer causes an application program (in the form of a unix +executable) to be executed either locally or remotely. + +The two main choices are local unix execution and execution through +GRAM. Other options are available, and user provided code can also be +plugged in. + +The kickstart utility can be used to capture environmental +information at execution time to aid in debugging and provenance capture. + + +SwiftScript language compilation layer +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Step i: text to XML intermediate form parser/processor. parser written +in ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the +intermediate language is in resources/XDTM.xsd. + +Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads +the XML intermediate form. compiles to karajan workflow language - for +example, expressions are converted from SwiftScript syntax into Karajan +syntax, and function invocations become karajan function invocations +with various modifications to parameters to accomodate return parameters +and dataset handling. + + +Swift/karajan library layer +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Some Swift functionality is provided in the form of Karajan libraries +that are used at runtime by the Karajan workflows that the Swift +compiler generates. + + +Ways in which Swift can be extended +----------------------------------- +Swift is extensible in a number of ways. It is possible to add mappers +to accomodate different filesystem arrangements, site selectors to +change how Swift decides where to run each job, and job submission +interfaces to submit jobs through different mechanisms. + +A number of mappers are provided as part of the Swift release and +documented in the mappers section. New mappers can be +implemented in Java by implementing the org.griphyn.vdl.mapping.Mapper +interface. The Swift tutorial + contains a simple +example of this. + +Swift provides a default site selector, the Adaptive Scheduler. New site +selectors can be plugged in by implementing the +org.globus.cog.karajan.scheduler.Scheduler interface and modifying +libexec/scheduler.xml and etc/karajan.properties to refer to the new +scheduler. + +Execution providers and filesystem providers, which allow to Swift to +execute jobs and to stage files in and out through mechanisms such as +GRAM and GridFTP can be implemented as Java CoG kit providers. + + +Function reference +------------------ +This section details functions that are available for use in the +SwiftScript language. + + at arg +~~~~ +Takes a command line parameter name as a string parameter and an +optional default value and returns the value of that string parameter +from the command line. If no default value is specified and the command +line parameter is missing, an error is generated. If a default value is +specified and the command line parameter is missing, @arg will return +the default value. + +Command line parameters recognized by @arg begin with exactly one +hyphen and need to be positioned after the script name. + +For example: + +[java] +source~~~~ +trace(@arg("myparam")); +trace(@arg("optionalparam", "defaultvalue")); +source~~~~ + +[java] +source~~~~ +$ swift arg.swift -myparam=hello +Swift v0.3-dev r1674 (modified locally) + +RunID: 20080220-1548-ylc4pmda +SwiftScript trace: defaultvalue +SwiftScript trace: hello +source~~~~ + + at extractint +~~~~~~~~~~~ + at extractint(file) will read the specified file, parse an integer from +the file contents and return that integer. + + + at filename +~~~~~~~~~ + at filename(v) will return a string containing the filename(s) for the +file(s) mapped to the variable v. When more than one filename is +returned, the filenames will be space separated inside a single string +return value. + + + at filenames +~~~~~~~~~~ + at filenames(v) will return multiple values (!) containing the +filename(s) for the file(s) mapped to the variable v. (compare to + at filename) + + at regexp +~~~~~~~ + at regexp(input,pattern,replacement) will apply regular expression +substitution using the Java java.util.regexp API +. +For example: + +[java] +source~~~~ +string v = @regexp("abcdefghi", "c(def)g","monkey"); +source~~~~ + +will assign the value "abmonkeyhi" to the variable v. + + at strcat +~~~~~~~ + at strcat(a,b,c,d,...) will return a string containing all of the +strings passed as parameters joined into a single string. There may be +any number of parameters. + +The + operator concatenates two strings: @strcat(a,b) is the same as +a + b + + at strcut +~~~~~~~ + at strcut(input,pattern) will match the regular expression in the +pattern parameter against the supplied input string and return the +section that matches the first matching parenthesised group. + +For example: +[java] +source~~~~ +string t = "my name is John and i like puppies."; +string name = @strcut(t, "my name is ([^ ]*) "); +string out = @strcat("Your name is ",name); +trace(out); +source~~~~ + +will output the message: Your name is John. + + at strsplit +~~~~~~~~~ + at strsplit(input,pattern) will split the input string based on +separators that match the given pattern and return a string array. +(since Swift 0.9) + +Example: +[java] +source~~~~ +string t = "my name is John and i like puppies."; +string words[] = @strsplit(t, "\\s"); +foreach word in words { + trace(word); +} +source~~~~ + +will output one word of the sentence on each line (though not +necessarily in order, due to the fact that foreach iterations execute in +parallel). + + + at toint +~~~~~~ + at toint(input) will parse its input string into an integer. This can be +used with @arg to pass input parameters to a SwiftScript program as +integers. + + +Built-in procedure reference +---------------------------- +This section details built-in procedures that are available for use in +the SwiftScript language. + +readData +~~~~~~~~ +readData will read data from a specified file. + +The format of the input file is controlled by the type of the return value. + +For scalar return types, such as int, the specified file should contain +a single value of that type. + +For arrays of scalars, the specified file should contain one value per +line. + +For structs of scalars, the file should contain two rows. The first row +should be structure member names separated by whitespace. The second row +should be the corresponding values for each structure member, separated +by whitespace, in the same order as the header row. + +For arrays of structs, the file should contain a heading row listing +structure member names separated by whitespace. There should be one row +for each element of the array, with structure member elements listed in +the same order as the header row and separated by whitespace. (since +Swift 0.4) + +readdata2 +~~~~~~~~~ +readdata2 will read data from a specified file, like readdata, but +using a different file format more closely related to that used by the +ext mapper. + +Input files should list, one per line, a path into a Swift structure, +and the value for that position in the structure: + +[java] +source~~~~ +rows[0].columns[0] = 0 +rows[0].columns[1] = 2 +rows[0].columns[2] = 4 +rows[1].columns[0] = 1 +rows[1].columns[1] = 3 +rows[1].columns[2] = 5 +source~~~~ + +which can be read into a structure defined like this: + +[java] +source~~~~ +type vector { + int columns[]; +} + +type matrix { + vector rows[]; +} + +matrix m; + +m = readData2("readData2.in"); +source~~~~ + +(since Swift 0.7) + +trace +~~~~~ +trace will log its parameters. By default these will appear on both +stdout and in the run log file. Some formatting occurs to produce the +log message. The particular output format should not be relied upon. +(since Swift 0.4) + +writeData +~~~~~~~~~ +writeData will write out data structures in the format described for +readData + +Swift configuration properties +------------------------------ +Various aspects of the behavior of the Swift Engine can be configured +through properties. The Swift Engine recognizes a global, per +installation properties file which can found in etc/swift.properties +in the Swift installation directory and a user properties file which can +be created by each user in ~/.swift/swift.properties. The Swift Engine +will first load the global properties file. It will then try to load the +user properties file. If a user properties file is found, individual +properties explicitly set in that file will override the respective +properties in the global properties file. Furthermore, some of the +properties can be overridden directly using command line arguments to +the *swift* command. + +Swift properties are specified in the following format: + += + +The value can contain variables which will be expanded when the +properties file is read. Expansion is performed when the name of the +variable is used inside the standard shell dereference construct: +${name}. The following variables can be used in the Swift +configuration file: + +Swift Configuration Variables + +swift.home + + Points to the Swift installation directory ($SWIFT_HOME). In + general, this should not be set as Swift can find its own + installation directory, and incorrectly setting it may impair the + correct functionality of Swift. + +user.name + + The name of the current logged in user. + +user.home + + The user's home directory. + +The following is a list of valid Swift properties: + +Swift Properties + +caching.algorithm + + Valid values: LRU + + Default value: LRU + + Swift caches files that are staged in on remote resources, and files + that are produced remotely by applications, such that they can be + re-used if needed without being transfered again. However, the + amount of remote file system space to be used for caching can be + limited using the swift:storagesize profile entry in the sites.xml file. Example: + +[xml] +source~~~~ + + + +/scratch/swift +20000000 + +source~~~~ + + The decision of which files to keep in the cache and which files to + remove is made considering the value of the caching.algorithm + property. Currently, the only available value for this property is + LRU, which would cause the least recently used files to be deleted + first. + +clustering.enabled + + Valid values: true, false + + Default value: false + + Enables clustering. + +clustering.min.time + + Valid values: + + Default value: 60 + + Indicates the threshold wall time for clustering, in seconds. Jobs + that have a wall time smaller than the value of this property will + be considered for clustering. + +clustering.queue.delay + + Valid values: + + Default value: 4 + + This property indicates the interval, in seconds, at which the + clustering queue is processed. + +execution.retries + + Valid values: positive integers + + Default value: 2 + + The number of time a job will be retried if it fails (giving a + maximum of 1 + execution.retries attempts at execution) + +foreach.max.threads + + Valid values: positive integers + + Default value: 1024 + + Limits the number of concurrent iterations that each foreach + statement can have at one time. This conserves memory for swift + programs that have large numbers of iterations (which would + otherwise all be executed in parallel). (since Swift 0.9) + +ip.address + + Valid values: + + Default value: N/A + + The Globus GRAM service uses a callback mechanism to send + notifications about the status of submitted jobs. The callback + mechanism requires that the Swift client be reachable from the hosts + the GRAM services are running on. Normally, Swift can detect the + correct IP address of the client machine. However, in certain cases + (such as the client machine having more than one network interface) + the automatic detection mechanism is not reliable. In such cases, + the IP address of the Swift client machine can be specified using + this property. The value of this property must be a numeric address + without quotes. + + This option is deprecated and the hostname property should be used + instead. + +kickstart.always.transfer + + Valid values: true, false + + Default value: false + + This property controls when output from Kickstart is transfered back + to the submit site, if Kickstart is enabled. When set to false, + Kickstart output is only transfered for jobs that fail. If set to + true, Kickstart output is transfered after every job is completed + or failed. + +kickstart.enabled + + Valid values: true, false, maybe + + Default value: maybe + + This option allows controlling of when Swift uses Kickstart. + A value of false disables the use of Kickstart, + while a value of true enables the use of Kickstart, in which case + sites specified in the sites.xml file must have valid + gridlaunch attributes. The maybe value will enable the use of + Kickstart only on sites that have the gridlaunch attribute + specified. + +lazy.errors + + Valid values: true, false + + Default value: false + + Swift can report application errors in two modes, depending on the + value of this property. If set to false, Swift will report the + first error encountered and immediately stop execution. If set to + true, Swift will attempt to run as much as possible from a + SwiftScript program before stopping execution and reporting all + errors encountered. + + When developing SwiftScript programs, using the default value of + false can make the program easier to debug. However in production + runs, using true will allow more of a SwiftScript program to be + run before Swift aborts execution. + +pgraph + + Valid values: true, false, + + Default value: false + + Swift can generate a Graphviz file + representing the structure of the SwiftScript program it has run. If + this property is set to true, Swift will save the provenance graph + in a file named by concatenating the program name and the instance + ID (e.g. helloworld-ht0adgi315l61.dot). + + If set to false, no provenance graph will be generated. If a file + name is used, then the provenance graph will be saved in the + specified file. + + The generated dot file can be rendered into a graphical form using + Graphviz , for example with a command-line + such as: + +[shell] +source~~~~ +$ swift -pgraph graph1.dot q1.swift +$ dot -ograph.png -Tpng graph1.dot +source~~~~ + +pgraph.graph.options + + Valid values: + + Default value: splines="compound", rankdir="TB" + + This property specifies a Graphviz + specific set of parameters for the graph. + +pgraph.node.options + + Valid values: + + Default value: color="seagreen", style="filled" + + Used to specify a set of Graphviz specific + properties for the nodes in the graph. + +provenance.log + + Valid values: true, false + + Default value: false + + This property controls whether the log file will contain provenance + information enabling this will increase the size of log files, + sometimes significantly. + +replication.enabled + + Valid values: true, false + + Default value: false + + Enables/disables replication. Replication is used to deal with jobs + sitting in batch queues for abnormally large amounts of time. If + replication is enabled and certain conditions are met, Swift creates + and submits replicas of jobs, and allows multiple instances of a job + to compete. + +replication.limit + + Valid values: positive integers + + Default value: 3 + + The maximum number of replicas that Swift should attempt. + +sitedir.keep + + Valid values: true, false + + Default value: false + + Indicates whether the working directory on the remote site should be + left intact even when a run completes successfully. This can be used + to inspect the site working directory for debugging purposes. + +sites.file + + Valid values: + + Default value: ${swift.home}/etc/sites.xml + + Points to the location of the site catalog, which contains a list of + all sites that Swift should use. + +status.mode + + Valid values: files, provider + + Default value: files + + Controls how Swift will communicate the result code of running user + programs from workers to the submit side. In files mode, a file + indicating success or failure will be created on the site shared + filesystem. In provider mode, the execution provider job status + will be used. + + provider mode requires the underlying job execution system to + correctly return exit codes. In at least the cases of GRAM2, and + clusters used with any provider, exit codes are not returned, and so + files mode must be used in those cases. Otherwise, provider mode + can be used to reduce the amount of filesystem access. (since Swift + 0.8) + +tc.file + + Valid values: + + Default value: ${swift.home}/etc/tc.data + + Points to the location of the transformation catalog file which + contains information about installed applications. Details about the + format of the transformation catalog can be found here + . + + +tcp.port.range + + Valid values: , where start and end are integers + + Default value: none + + A TCP port range can be specified to restrict the ports on which + GRAM callback services are started. This is likely needed if your + submit host is behind a firewall, in which case the firewall should + be configured to allow incoming connections on ports in the range. + +throttle.file.operations + + Valid values: , off + + Default value: 8 + + Limits the total number of concurrent file operations that can + happen at any given time. File operations (like transfers) require + an exclusive connection to a site. These connections can be + expensive to establish. A large number of concurrent file operations + may cause Swift to attempt to establish many such expensive + connections to various sites. Limiting the number of concurrent file + operations causes Swift to use a small number of cached connections + and achieve better overall performance. + +throttle.host.submit + + Valid values: , off + + Default value: 2 + + Limits the number of concurrent submissions for any of the sites + Swift will try to send jobs to. In other words it guarantees that no + more than the value of this throttle jobs sent to any site will be + concurrently in a state of being submitted. + +throttle.score.job.factor + + Valid values: , off + + Default value: 4 + + The Swift scheduler has the ability to limit the number of + concurrent jobs allowed on a site based on the performance history + of that site. Each site is assigned a score (initially 1), which can + increase or decrease based on whether the site yields successful or + faulty job runs. The score for a site can take values in the (0.1, + 100) interval. The number of allowed jobs is calculated using the + following formula: + + 2 + score*throttle.score.job.factor + + This means a site will always be allowed at least two concurrent + jobs and at most 2 + 100*throttle.score.job.factor. With a default + of 4 this means at least 2 jobs and at most 402. + + This parameter can also be set per site using the jobThrottle + profile key in a site catalog entry. + +throttle.submit + + Valid values: , off + + Default value: 4 + + Limits the number of concurrent submissions for a run. This throttle + only limits the number of concurrent tasks (jobs) that are being + sent to sites, not the total number of concurrent jobs that can be + run. The submission stage in GRAM is one of the most CPU expensive + stages (due mostly to the mutual authentication and delegation). + Having too many concurrent submissions can overload either or both + the submit host CPU and the remote host/head node causing degraded + performance. + +throttle.transfers + + Valid values: , off + + Default value: 4 + + Limits the total number of concurrent file transfers that can happen + at any given time. File transfers consume bandwidth. Too many + concurrent transfers can cause the network to be overloaded + preventing various other signaling traffic from flowing properly. + +ticker.disable + + Valid values: true, false + + Default value: false + + When set to true, suppresses the output progress ticker that Swift + sends to the console every few seconds during a run (since Swift 0.9) + +wrapper.invocation.mode + + Valid values: absolute, relative + + Default value: absolute + + Determines if Swift remote wrappers will be executed by specifying + an absolute path, or a path relative to the job initial working + directory. In most cases, execution will be successful with either + option. However, some execution sites ignore the specified initial + working directory, and so absolute must be used. Conversely on + some sites, job directories appear in a different place on the + worker node file system than on the filesystem access node, with the + execution system handling translation of the job initial working + directory. In such cases, relative mode must be used. (since Swift + 0.9) + +wrapper.parameter.mode + + Controls how Swift will supply parameters to the remote wrapper + script. args mode will pass parameters on the command line. Some + execution systems do not pass commandline parameters sufficiently + cleanly for Swift to operate correctly. files mode will pass + parameters through an additional input file (since Swift 0.95). This + provides a cleaner communication channel for parameters, at the + expense of transferring an additional file for each job invocation. + +wrapperlog.always.transfer + + Valid values: true, false + + Default value: false + + This property controls when output from the Swift remote wrapper is + transfered back to the submit site. When set to false, wrapper + logs are only transfered for jobs that fail. If set to true, + wrapper logs are transfered after every job is completed or failed. + +Example: + +[source,xml] +sites.file=${vds.home}/etc/sites.xml +tc.file=${vds.home}/etc/tc.data +ip.address=192.168.0.1 + +Profiles +-------- +Profiles are configuration parameters than can be specified either for +sites or for transformation catalog entries. They influence the +behaviour of Swift towards that site (for example, by changing the load +Swift will place on that sites) or when running a particular procedure. + +Profile entries for a site are specified in the site catalog. Profile +entries for specific procedures are specified in the transformation +catalog. + + +Karajan namespace +~~~~~~~~~~~~~~~~~ +maxSubmitRate limits the maximum rate of job submission, in jobs per +second. For example: + +[source,xml] +0.2 + +will limit job submission to 0.2 jobs per second (or equivalently, one +job every five seconds). + +jobThrottle allows the job throttle factor (see Swift property +throttle.score.job.factor to be +set per site. + +initialScore allows the initial score for rate limiting and site +selection to be set to a value other than 0. + +delayBase controls how much a site will be delayed when it performs +poorly. With each reduction in a sites score by 1, the delay between +execution attempts will increase by a factor of delayBase. + +status.mode allows the status.mode property to be set per-site instead +of for an entire run. See the Swift configuration properties section for +more information. (since Swift 0.8) + +swift namespace +~~~~~~~~~~~~~~~ +storagesize limits the amount of space that will be used on the remote +site for temporary files. When more than that amount of space is used, +the remote temporary file cache will be cleared using the algorithm +specified in the caching.algorithm property. + +wrapperInterpreter - The wrapper interpreter indicates the command +(executable) to be used to run the Swift wrapper script. The default is +"/bin/bash" on Unix sites and "cscript.exe" on Windows sites. + +wrapperInterpreterOptions - Allows specifying additional options to the +executable used to run the Swift wrapper. The defaults are no options on +Unix sites and "Nologo" on Windows sites. + +wrapperScript - Specifies the name of the wrapper script to be used on a +site. The defaults are "_swiftwrap" on Unix sites and "_swiftwrap.vbs" +on Windows sites. If you specify a custom wrapper script, it must be +present in the "libexec" directory of the Swift installation. + +cleanupCommand Indicates the command to be run at the end of a Swift +run to clean up the run directories on a remote site. Defaults are +"/bin/rm" on Unix sites and "cmd.exe" on Windows sites + +cleanupCommandOptions Specifies the options to be passed to the +cleanup command above. The options are passed in the argument list to +the cleanup command. After the options, the last argument is the +directory to be deleted. The default on Unix sites is "-rf". The default +on Windows sites is ["/C", "del", "/Q"]. + + +Globus namespace +~~~~~~~~~~~~~~~~ +maxwalltime specifies a walltime limit for each job, in minutes. + +The following formats are recognized: + + * Minutes + * Hours:Minutes + * Hours:Minutes:Seconds + +Example: +[source,java] +localhost echo /bin/echo INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:20:00" + +When replication is enabled (see replication), then +walltime will also be enforced at the Swift client side: when a job has +been active for more than twice the maxwalltime, Swift will kill the job +and regard it as failed. + +When clustering is used, maxwalltime will be used to select which jobs +will be clustered together. More information on this is available in the +clustering section. + +When coasters as used, maxwalltime influences the default coaster +worker maxwalltime, and which jobs will be sent to which workers. More +information on this is available in the coasters section. + +queue is used by the PBS, GRAM2 and GRAM4 providers. This profile +entry specifies which queue jobs will be submitted to. The valid queue +names are site-specific. + +host_types specifies the types of host that are permissible for a job +to run on. The valid values are site-specific. This profile entry is +used by the GRAM2 and GRAM4 providers. + +condor_requirements allows a requirements string to be specified when +Condor is used as an LRM behind GRAM2. Example: + +[source,xml] +Arch == "X86_64" || Arch="INTEL" + +slots When using coasters, this parameter specifies the +maximum number of jobs/blocks that the coaster scheduler will have +running at any given time. The default is 20. + +workersPerNode - This parameter determines how many coaster workers are +started one each compute node. The default value is 1. + +nodeGranularity - When allocating a coaster worker block, this parameter +restricts the number of nodes in a block to a multiple of this value. +The total number of workers will then be a multiple of workersPerNode * +nodeGranularity. The default value is 1. + +allocationStepSize - Each time the coaster block scheduler computes a +schedule, it will attempt to allocate a number of slots from the number +of available slots (limited using the above slots profile). This +parameter specifies the maximum fraction of slots that are allocated in +one schedule. Default is 0.1. + +lowOverallocation - Overallocation is a function of the walltime of a +job which determines how long (time-wise) a worker job will be. For +example, if a number of 10s jobs are submitted to the coaster service, +and the overallocation for 10s jobs is 10, the coaster scheduler will +attempt to start worker jobs that have a walltime of 100s. The +overallocation is controlled by manipulating the end-points of an +overallocation function. The low endpoint, specified by this parameter, +is the overallocation for a 1s job. The high endpoint is the +overallocation for a (theoretical) job of infinite length. The +overallocation for job sizes in the [1s, +inf) interval is determined +using an exponential decay function: overallocation(walltime) = walltime +* (lowOverallocation - highOverallocation) * exp(-walltime * +overallocationDecayFactor) + highOverallocation The default value of +lowOverallocation is 10. + +highOverallocation - The high overallocation endpoint (as described +above). Default: 1 + +overallocationDecayFactor - The decay factor for the overallocation +curve. Default 0.001 (1e-3). + +spread - When a large number of jobs is submitted to the a coaster +service, the work is divided into blocks. This parameter allows a rough +control of the relative sizes of those blocks. A value of 0 indicates +that all work should be divided equally between the blocks (and blocks +will therefore have equal sizes). A value of 1 indicates the largest +possible spread. The existence of the spread parameter is based on the +assumption that smaller overall jobs will generally spend less time in +the queue than larger jobs. By submitting blocks of different sizes, +submitted jobs may be finished quicker by smaller blocks. Default: 0.9. + +reserve - Reserve time is a time in the allocation of a worker that sits +at the end of the worker time and is useable only for critical +operations. For example, a job will not be submitted to a worker if it +overlaps its reserve time, but a job that (due to inaccurate walltime +specification) runs into the reserve time will not be killed (note that +once the worker exceeds its walltime, the queuing system will kill the +job anyway). Default 10 (s). + +maxnodes - Determines the maximum number of nodes that can be allocated +in one coaster block. Default: unlimited. + +maxtime - Indicates the maximum walltime that a coaster block can have. +Default: unlimited. + +remoteMonitorEnabled - If set to "true", the client side will get a +Swing window showing, graphically, the state of the coaster scheduler +(blocks, jobs, etc.). Default: false + +env namespace +~~~~~~~~~~~~~ +Profile keys set in the env namespace will be set in the unix +environment of the executed job. Some environment variables influence +the worker-side behaviour of Swift: + +PATHPREFIX - set in env namespace profiles. This path is prefixed onto +the start of the PATH when jobs are executed. It can be more useful +than setting the PATH environment variable directly, because setting +PATH will cause the execution site's default path to be lost. + +SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift +will use the path specified here as a worker-node local temporary +directory to copy input files to before running a job. If unset, Swift +will keep input files on the site-shared filesystem. In some cases, +copying to a worker-node local directory can be much faster than having +applications access the site-shared filesystem directly. + +SWIFT_EXTRA_INFO - set in env namespace profiles. If set, then Swift +will execute the command specified in SWIFT_EXTRA_INFO on execution +sites immediately before each application execution, and will record the +stdout of that command in the wrapper info log file for that job. This +is intended to allow software version and other arbitrary information +about the remote site to be gathered and returned to the submit side. +(since Swift 0.9) + +The Site Catalog - sites.xml +---------------------------- +The site catalog lists details of each site that Swift can use. The +default file contains one entry for local execution, and a large number +of commented-out example entries for other sites. + +By default, the site catalog is stored in etc/sites.xml. This path can +be overridden with the sites.file configuration property, either in +the Swift configuration file or on the command line. + +The sites file is formatted as XML. It consists of elements, +one for each site that Swift will use. + + +Pool element +~~~~~~~~~~~~ +Each pool element must have a handle attribute, giving a symbolic +name for the site. This can be any name, but must correspond to entries +for that site in the transformation catalog. + +Optionally, the gridlaunch attribute can be used to specify the path +to kickstart on the site. + +Each pool must specify a file transfer method, an execution method and +a remote working directory. Optionally, profile settings can +be specified. + + +File transfer method +~~~~~~~~~~~~~~~~~~~~ +Transfer methods are specified with either the element or +the element. + +To use gridftp or local filesystem copy, use the element: + +[source,xml] + + +The url attribute may specify a GridFTP server, using the gsiftp URI +scheme; or it may specify that filesystem copying will be used (which +assumes that the site has access to the same filesystem as the +submitting machine) using the URI local://localhost. + +Filesystem access using scp (the SSH copy protocol) can be specified +using the element: + +[source,xml] + + +For additional ssh configuration information, see the ssh execution +provider documentation below. + +Filesystem access using CoG coasters can be also be +specified using the element. More detail about +configuring that can be found in the CoG coasters section. + +Execution method +~~~~~~~~~~~~~~~~ +Execution methods may be specified either with the or + element. + +The element can be used to specify execution through +GRAM2. For example, + +[source,xml] + + +The universe attribute should always be set to vanilla. The url +attribute should specify the name of the GRAM2 gatekeeper host, and the +name of the jobmanager to use. The major attribute should always be set +to 2. + +The element can be used to specify execution through other +execution providers: + +To use GRAM4, specify the gt4 provider. For example: + +[source,xml] + + +The url attribute should specify the GRAM4 submission site. The +jobmanager attribute should specify which GRAM4 jobmanager will be used. + +For local execution, the local provider should be used, like this: + +[source,xml] + + +For PBS execution, the pbs provider should be used: + +[source,xml] + + +The GLOBUS::queue profile key can be used to +specify which PBS queue jobs will be submitted to. + +For execution through a local Condor installation, the condor provider +should be used. This provider can run jobs either in the default vanilla +universe, or can use Condor-G to run jobs on remote sites. + +When running locally, only the element needs to be specified: + +[source,xml] + + +When running with Condor-G, it is necessary to specify the Condor grid +universe and the contact string for the remote site. For example: + +[source,xml] + + grid + gt2 belhaven-1.renci.org/jobmanager-fork + +For execution through SSH, the ssh provider should be used: + +[source,xml] + + +with configuration made in ~/.ssh/auth.defaults with the string +'www11.i2u2.org' changed to the appropriate host name: + +[source,shell] +www11.i2u2.org.type=key +www11.i2u2.org.username=hategan +www11.i2u2.org.key=/home/mike/.ssh/i2u2portal +www11.i2u2.org.passphrase=XXXX + +For execution using the CoG Coaster mechanism, the coaster +provider should be used: + +[source,xml] + + +More details about configuration of coasters can be found in the section +on coasters. + +Work directory +~~~~~~~~~~~~~~ +The workdirectory element specifies where on the site files can be +stored. + +[source,xml] +/home/benc + +This file must be accessible through the transfer mechanism specified in +the element and also mounted on all worker nodes that will +be used for execution. A shared cluster scratch filesystem is +appropriate for this. + +Profiles +~~~~~~~~ +Profile keys can be specified using the element. +For example: + +[source,xml] +fast + +The site catalog format is an evolution of the VDS site catalog format +which is documented here +. + + +The Transformation Catalog - tc.data +------------------------------------ +The transformation catalog lists where application executables are +located on remote sites. + +By default, the site catalog is stored in etc/tc.data. This path can +be overridden with the tc.file configuration property, either in the +Swift configuration file or on the command line. + +The format is one line per executable per site, with fields separated by +tabs. Spaces cannot be used to separate fields. + +Some example entries: +[source,shell] +localhost echo /bin/echo INSTALLED INTEL32::LINUX null +TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1" + +The fields are: site, transformation name, executable path, installation +status, platform, and profile entrys. + +The site field should correspond to a site name listed in the sites catalog. + +The transformation name should correspond to the transformation name +used in a SwiftScript app procedure. + +The executable path should specify where the particular executable is +located on that site. + +The installation status and platform fields are not used. Set them to +INSTALLED and INTEL32::LINUX respectively. + +The profiles field should be set to null if no profile entries are to +be specified, or should contain the profile entries separated by +semicolons. + +Build options +------------- +See the Swift download page + for instructions on +downloading and building Swift from source. When building, various build +options can be supplied on the ant commandline. These are summarised here: + +with-provider-condor - build with CoG condor provider + +with-provider-coaster - build with CoG coaster provider (see the +section on coasters). Since 0.8, coasters are always built, +and this option has no effect. + +with-provider-deef - build with Falkon provider deef. In order for +this option to work, it is necessary to check out the provider-deef code +in the cog/modules directory alongside swift: + +[source,shell] +$ cd cog/modules +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef +$ cd ../swift +$ ant -Dwith-provider-deef=true redist + +with-provider-wonky - build with provider-wonky, an execution provider +that provides delays and unreliability for the purposes of testing +Swift's fault tolerance mechanisms. In order for this option to work, it +is necessary to check out the provider-wonky code in the |cog/modules| +directory alongside swift: + +[source,shell] +$ cd cog/modules +$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky +$ cd ../swift|* +$ ant -Dwith-provider-wonky=true redist + +no-supporting - produces a distribution without supporting commands +such as grid-proxy-init. This is intended for when the Swift +distribution will be used in an environment where those commands are +already provided by other packages, where the Swift package should be +providing only Swift commands, and where the presence of commands such +as grid-proxy-init from the Swift distribution in the path will mask the +presence of those commands from their true distribution package such as +a Globus Toolkit package. + +[source,shell] +$ ant -Dno-supporting=true redist + +Kickstart +--------- +Kickstart is a tool that can be used to gather various information about +the remote execution environment for each job that Swift tries to run. + +For each job, Kickstart generates an XML invocation record. By default +this record is staged back to the submit host if the job fails. + +Before it can be used it must be installed on the remote site and the +sites file must be configured to point to kickstart. + +Kickstart can be downloaded as part of the Pegasus 'worker package' +available from the worker packages section of the Pegasus download page +. + +Untar the relevant worker package somewhere where it is visible to all +of the worker nodes on the remote execution machine (such as in a shared +application filesystem). + +Now configure the gridlaunch attribute of the sites catalog to point to +that path, by adding a gridlaunch attribute to the pool element in +the site catalog: + +[source,xml] + +... + + +There are various kickstat.* properties, which have sensible default +values. These are documented in the properties section. + +Reliability mechanisms +---------------------- +This section details reliabilty mechanisms in Swift: retries, restarts +and replication. + +Retries +~~~~~~~ +If an application procedure execution fails, Swift will attempt that +execution again repeatedly until it succeeds, up until the limit defined +in the execution.retries configuration property. + +Site selection will occur for retried jobs in the same way that it +happens for new jobs. Retried jobs may run on the same site or may run +on a different site. + +If the retry limit execution.retries is reached for an application +procedure, then that application procedure will fail. This will cause +the entire run to fail - either immediately (if the lazy.errors +property is false) or after all other possible work has been attempted +(if the lazy.errors property is true). + +Restarts +~~~~~~~~ +If a run fails, Swift can resume the program from the point of failure. +When a run fails, a restart log file will be left behind in a file named +using the unique job ID and a .rlog extension. This restart log can +then be passed to a subsequent Swift invocation using the -resume +parameter. Swift will resume execution, avoiding execution of +invocations that have previously completed successfully. The SwiftScript +source file and input data files should not be modified between runs. + +Every run creates a restart log file with a named composed of the file +name of the workflow being executed, an invocation ID, a numeric ID, and +the .rlog extension. For example, example.swift, when executed, +could produce the following restart log file: +example-ht0adgi315l61.0.rlog. Normally, if the run completes +successfully, the restart log file is deleted. If however the workflow +fails, swift can use the restart log file to continue execution from a +point before the failure occurred. In order to restart from a restart +log file, the -resume logfile argument can be used after the +SwiftScript program file name. Example: + +[source,shell] +$ swift -resume example-ht0adgi315l61.0.rlog example.swift. + +Replication +~~~~~~~~~~~ +When an execution job has been waiting in a site queue for a certain +period of time, Swift can resubmit replicas of that job (up to the limit +defined in the replication.limit configuration property). When any of +those jobs moves from queued to active state, all of the other replicas +will be cancelled. + +This is intended to deal with situations where some sites have a +substantially longer (sometimes effectively infinite) queue time than +other sites. Selecting those slower sites can cause a very large delay +in overall run time. + +Replication can be enabled by setting the replication.enabled +configuration property to true. The maximum number of replicas that +will be submitted for a job is controlled by the replication.limit +configuration property. + +When replication is enabled, Swift will also enforce the maxwalltime +profile setting for jobs as documented in the profiles section. + +Clustering +---------- +Swift can group a number of short job submissions into a single larger +job submission to minimize overhead involved in launching jobs (for +example, caused by security negotiation and queuing delay). In general, +CoG coasters should be used in preference to the clustering +mechanism documented in this section. + +By default, clustering is disabled. It can be activated by setting the +clustering.enabled property to true. + +A job is eligible for clustering if the GLOBUS::maxwalltime profile +is specified in the tc.data entry for that job, and its value is +less than the value of the clustering.min.time property. + +Two or more jobs are considered compatible if they share the same site +and do not have conflicting profiles (e.g. different values for the same +environment variable). + +When a submitted job is eligible for clustering, it will be put in a +clustering queue rather than being submitted to a remote site. The +clustering queue is processed at intervals specified by the +clustering.queue.delay property. The +processing of the clustering queue consists of selecting compatible jobs +and grouping them into clusters whose maximum wall time does not exceed +twice the value of the clustering.min.time property. + +Coasters +-------- +Coasters were introduced in Swift v0.6 as an experimental feature. + +In many applications, Swift performance can be greatly enhanced by the +use of CoG coasters. CoG coasters provide a low-overhead job submission +and file transfer mechanism suited for the execution of short jobs (on +the order of a few seconds) and the transfer of small files (on the +order of a few kilobytes) for which other grid protocols such as GRAM +and GridFTP are poorly suited. + +The coaster mechanism submits a head job using some other execution +mechanism such as GRAM, and for each worker node that will be used in a +remote cluster, it submits a worker job, again using some other +execution mechanism such as GRAM. Details on the design of the coaster +mechanism can be found here. + +The head job manages file transfers and the dispatch of execution jobs +to workers. Much of the overhead associated with other grid protocols +(such as authentication and authorization, and allocation of worker +nodes by the site's local resource manager) is reduced, because that +overhead is associated with the allocation of a coaster head or coaster +worker, rather than with every Swift-level procedure invocation; +potentially hundreds or thousands of Swift-level procedure invocations +can be run through a single worker. + +Coasters can be configured for use in two situations: job execution and +file transfer. + +To use for job execution, specify a sites.xml execution element like this: + +[source,xml] + + +The jobmanager string contains more detail than with other providers. It +contains either two or three colon separated fields: 1:the provider to +be use to execute the coaster head job - this provider will submit from +the Swift client side environment. Commonly this will be one of the GRAM +providers; 2: the provider to be used to execute coaster worker jobs. +This provider will be used to submit from the coaster head job +environment, so a local scheduler provider can sometimes be used instead +of GRAM. 3: optionally, the jobmanager to be used when submitting worker +job using the provider specified in field 2. + +To use for file transfer, specify a sites.xml filesystem element like this: + +[source,xml] + + +The url parameter should be a pseudo-URI formed with the URI scheme +being the name of the provider to use to submit the coaster head job, +and the hostname portion being the hostname to be used to execute the +coaster head job. Note that this provider and hostname will be used for +execution of a coaster head job, not for file transfer; so for example, +a GRAM endpoint should be specified here rather than a GridFTP endpoint. + +Coasters are affected by the following profile settings, which are +documented in the Globus namespace profile section: + +[options="header"] +|================= +|Profile key|Brief description +|slots|How many maximum LRM jobs/worker blocks are allowed +|workersPerNode|How many coaster workers to run per execution node +|nodeGranularity|Each worker block uses a number of nodes that is a +multiple of this number +|lowOverallocation|How many times larger than the job walltime should a +block's walltime be if all jobs are 1s long +|highOverallocation|How many times larger than the job walltime should a +block's walltime be if all jobs are infinitely long +|overallocationDecayFactor|How quickly should the overallocation curve +tend towards the highOverallocation as job walltimes get larger +|spread|By how much should worker blocks vary in worker size +|workersPerNode|How many coaster workers to run per execution node +|reserve|How many seconds to reserve in a block's walltime for +starting/shutdown operations +|maxnodes|The maximum number of nodes allowed in a block +|maxtime|The maximum number of walltime allowed for a block +|remoteMonitorEnabled|If true, show a graphical display of the status of +the coaster service +|================== + +How-To Tips for Specific User Communities +----------------------------------------- + +Saving Logs - for UChicago CI Users +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +If you have a UChicago Computation Institute account, run this command +in your submit directory after each run. It will copy all your logs and +kickstart records into a directory at the CI for reporting, usage +tracking, support and debugging. + +[source,shell] +rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose + +Specifying TeraGrid allocations +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +TeraGrid users with no default project or with several project +allocations can specify a project allocation using a profile key in the +site catalog entry for a TeraGrid site: + +[source,xml] +TG-CCR080002N + +More information on the TeraGrid allocations process can be found here +. + +Launching MPI jobs from Swift +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Here is an example of running a simple MPI program. + +In SwiftScript, we make an invocation that does not look any different +from any other invocation. In the below code, we do not have any input +files, and have two output files on stdout and stderr: + +[java] +source~~~~ +type file; + +(file o, file e) p() { + app { + mpi stdout=@filename(o) stderr=@filename(e); + } +} + +file mpiout <"mpi.out">; +file mpierr <"mpi.err">; + +(mpiout, mpierr) = p(); +source~~~~ + +Now we define how 'mpi' will run in tc.data: +[source,shell] +tguc mpi /home/benc/mpi/mpi.sh INSTALLED INTEL32::LINUX GLOBUS::host_xcount=3 + +mpi.sh is a wrapper script that launches the MPI program. It must be +installed on the remote site: + +[source,shell] +#!/bin/bash +mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out + +Because of the way that Swift runs its server side code, +provider-specific MPI modes (such as GRAM jobType=mpi) should not be +used. Instead, the mpirun command should be explicitly invoked. + +Running on Windows +~~~~~~~~~~~~~~~~~~ +Since 10/11/09, the development version of Swift has the ability to run +on a Windows machine, as well as the ability to submit jobs to a Windows +site (provided that an appropriate provider is used). + +In order to launch Swift on Windows, use the provided batch file +(swift.bat). In certain cases, when a large number of jar libraries are +present in the Swift lib directory and depending on the exact location +of the Swift installation, the classpath environment variable that the +Swift batch launcher tries to create may be larger than what Windows can +handle. In such a case, either install Swift in a directory closer to +the root of the disk (say, c:\swift) or remove non-essential jar files +from the Swift lib directory. + +Due to the large differences between Windows and Unix environments, +Swift must use environment specific tools to achieve some of its goals. +In particular, each Swift executable is launched using a wrapper script. +This script is a Bourne Shell script. On Windows machines, which have no +Bourne Shell interpreter installed by default, the Windows Scripting +Host is used instead, and the wrapper script is written in VBScript. +Similarly, when cleaning up after a run, the "/bin/rm" command available +in typical Unix environments must be replaced by the "del" shell command. + +It is important to note that in order to select the proper set of tools +to use, Swift must know when a site runs under Windows. To inform Swift +of this, specify the "sysinfo" attribute for the "pool" element in the +site catalog. For example: + +[source,xml] + +... + Deleted: trunk/docs/userguide-rotated.jpeg =================================================================== (Binary files differ) Deleted: trunk/docs/userguide-shane.jpeg =================================================================== (Binary files differ) Deleted: trunk/docs/userguide.xml =================================================================== --- trunk/docs/userguide.xml 2011-05-16 19:29:35 UTC (rev 4479) +++ trunk/docs/userguide.xml 2011-05-16 19:38:01 UTC (rev 4480) @@ -1,4337 +0,0 @@ - - - - -
    - - Swift User Guide - Source control $LastChangedRevision$ - - -
    - Overview - -This manual provides reference material for Swift: the SwiftScript language -and the Swift runtime system. For introductory material, consult -the Swift -tutorial. - - -Swift is a data-oriented coarse grained scripting language that -supports dataset typing and mapping, dataset iteration, -conditional branching, and procedural composition. - - -Swift programs (or workflows) are written in -a language called SwiftScript. - - -SwiftScript programs are dataflow oriented - they are primarily -concerned with processing (possibly large) collections of data files, -by invoking programs to do that processing. Swift handles execution of -such programs on remote sites by choosing sites, handling the staging -of input and output files to and from the chosen sites and remote execution -of program code. - -
    -
    - The SwiftScript Language -
    Language basics - -A Swift script describes data, application components, invocations -of applications components, and the inter-relations (data flow) -between those invocations. - - -Data is represented in a script by strongly-typed single-assignment -variables. The syntax superficially resembles C and Java. For example, -{ and } characters are used to -enclose blocks of statements. - - -Types in Swift can be atomic or -composite. An atomic type can be either a -primitive type or a mapped type. -Swift provides a fixed set of primitive types, such as -integer and string. A mapped -type indicates that the actual data does not reside in CPU addressable -memory (as it would in conventional programming languages), but in -POSIX-like files. Composite types are further subdivided into -structures and arrays. -Structures are similar in most respects to structure types in other languages. -Arrays use numeric indices, but are sparse. They can contain elements of -any type, including other array types, but all elements in an array must be -of the same type. We often refer to instances of composites of mapped types -as datasets. - - - -Mapped type and composite type variable declarations can be annotated with a -mapping descriptor indicating the file(s) that make up -that dataset. For example, the following line declares a variable named -photo with type image. It additionally -declares that the data for this variable is stored in a single file named -shane.jpeg. - - - - image photo <"shane.jpeg">; - - - -Component programs of scripts are declared in an app -declaration, with the description of the command line syntax -for that program and a list of input and output data. An app -block describes a functional/dataflow style interface to imperative -components. - - - -For example, the following example lists a procedure which makes use of -the ImageMagick -convert command to rotate a supplied -image by a specified angle: - - - - app (image output) rotate(image input) { - convert "-rotate" angle @input @output; - } - - - -A procedure is invoked using the familiar syntax: - - - - rotated = rotate(photo, 180); - - - -While this looks like an assignment, the actual unix level execution -consists of invoking the command line specified in the app -declaration, with variables on the left of the assignment bound to the -output parameters, and variables to the right of the procedure -invocation passed as inputs. - - - -The examples above have used the type image without any -definition of that type. We can declare it as a marker type -which has no structure exposed to SwiftScript: - - - - type image; - - - -This does not indicate that the data is unstructured; but it indicates -that the structure of the data is not exposed to SwiftScript. Instead, -SwiftScript will treat variables of this type as individual opaque -files. - - - -With mechanisms to declare types, map variables to data files, and -declare and invoke procedures, we can build a complete (albeit simple) -script: - - - - type image; - image photo <"shane.jpeg">; - image rotated <"rotated.jpeg">; - - app (image output) rotate(image input, int angle) { - convert "-rotate" angle @input @output; - } - - rotated = rotate(photo, 180); - - - -This script can be invoked from the command line: - - - - $ ls *.jpeg - shane.jpeg - $ swift example.swift - ... - $ ls *.jpeg - shane.jpeg rotated.jpeg - - - -This executes a single convert command, hiding from the -user features such as remote multisite execution and fault tolerance that -will be discussed in a later section. - -
    shane.jpeg - -
    -
    rotated.jpeg - -
    -
    - -
    Arrays and Parallel Execution - -Arrays of values can be declared using the [] suffix. An -array be mapped to a collection of files, one element per file, by using -a different form of mapping expression. For example, the -filesys_mapper -maps all files matching a particular unix glob pattern into an array: - - - - file frames[] <filesys_mapper; pattern="*.jpeg">; - - - -The foreach construct can be used -to apply the same block of code to each element of an array: - - - - foreach f,ix in frames { - output[ix] = rotate(frames, 180); - } - - - -Sequential iteration can be expressed using the iterate -construct: - - - - step[0] = initialCondition(); - iterate ix { - step[ix] = simulate(step[ix-1]); - } - - - -This fragment will initialise the 0-th element of the step -array to some initial condition, and then repeatedly run the -simulate procedure, using each execution's outputs as -input to the next step. - - -
    - -
    Ordering of execution - - -Non-array variables are single-assignment, which -means that they must be assigned to exactly one value during execution. -A procedure or expression will be executed when all of its input parameters -have been assigned values. As a result of such execution, more variables may -become assigned, possibly allowing further parts of the script to -execute. - - - -In this way, scripts are implicitly parallel. Aside from serialisation -implied by these dataflow dependencies, execution of component programs -can proceed in parallel. - - - -In this fragment, execution of procedures p and -q can happen in parallel: - - - - y=p(x); - z=q(x); - - -while in this fragment, execution is serialised by the variable -y, with procedure p executing -before q. - - - y=p(x); - z=q(y); - - - -Arrays in SwiftScript are more -monotonic - a generalisation of being -assignment. Knowledge about the -content of an array increases during execution, but cannot otherwise -change. Each element of the array is itself single assignment or monotonic -(depending on its type). -During a run all values for an array are eventually known, and that array -is regarded as closed. - - - -Statements which deal with the array as a whole will often wait for the array -to be closed before executing (thus, a closed array is the equivalent -of a non-array type being assigned). However, a foreach -statement will apply its body to elements of an array as they become -known. It will not wait until the array is closed. - - - -Consider this script: - - - - file a[]; - file b[]; - foreach v,i in a { - b[i] = p(v); - } - a[0] = r(); - a[1] = s(); - - - -Initially, the foreach statement will have nothing to -execute, as the array a has not been assigned any values. -The procedures r and s will execute. -As soon as either of them is finished, the corresponding invocation of -procedure p will occur. After both r -and s have completed, the array a will -be closed since no other statements in the script make an assignment to -a. - - -
    - -
    Compound procedures - -As with many other programming languages, procedures consisting of SwiftScript -code can be defined. These differ from the previously mentioned procedures -declared with the app keyword, as they invoke other -SwiftScript procedures rather than a component program. - - - - (file output) process (file input) { - file intermediate; - intermediate = first(input); - output = second(intermediate); - } - - file x <"x.txt">; - file y <"y.txt">; - y = process(x); - - - -This will invoke two procedures, with an intermediate data file named -anonymously connecting the first and -second procedures. - - - -Ordering of execution is generally determined by execution of -app procedures, not by any containing compound procedures. -In this code block: - - - - (file a, file b) A() { - a = A1(); - b = A2(); - } - file x, y, s, t; - (x,y) = A(); - s = S(x); - t = S(y); - - - -then a valid execution order is: A1 S(x) A2 S(y). The -compound procedure A does not have to have fully completed -for its return values to be used by subsequent statements. - - -
    - -
    More about types - -Each variable and procedure parameter in SwiftScript is strongly typed. -Types are used to structure data, to aid in debugging and checking program -correctness and to influence how Swift interacts with data. - - - -The image type declared in previous examples is a -marker type. Marker types indicate that data for a -variable is stored in a single file with no further structure exposed at -the SwiftScript level. - - - -Arrays have been mentioned above, in the arrays section. A code block -may be applied to each element of an array using foreach; -or individual elements may be references using [] notation. - - -There are a number of primitive types: - - - - typecontains - - intintegers - stringstrings of text - floatfloating point numbers, that behave the same as Java doubles - booleantrue/false - - -
    - - -Complex types may be defined using the type keyword: - - - type headerfile; - type voxelfile; - type volume { - headerfile h; - voxelfile v; - } - - - -Members of a complex type can be accessed using the . -operator: - - - - volume brain; - o = p(brain.h); - - - -Sometimes data may be stored in a form that does not fit with Swift's -file-and-site model; for example, data might be stored in an RDBMS on some -database server. In that case, a variable can be declared to have -external type. This indicates that -Swift should use the variable to determine execution dependency, but should -not attempt other data management; for example, it will not perform any form -of data stage-in or stage-out it will not manage local data caches on sites; -and it will not enforce component program atomicity on data output. This can -add substantial responsibility to component programs, in exchange for allowing -arbitrary data storage and access methods to be plugged in to scripts. - - - - type file; - - app (external o) populateDatabase() { - populationProgram; - } - - app (file o) analyseDatabase(external i) { - analysisProgram @o; - } - - external database; - file result <"results.txt">; - - database = populateDatabase(); - result = analyseDatabase(database); - - - -Some external database is represented by the database -variable. The populateDatabase procedure populates the -database with some data, and the analyseDatabase procedure -performs some subsequent analysis on that database. The declaration of -database contains no mapping; and the procedures which -use database do not reference them in any way; the -description of database is entirely outside of the script. -The single assignment and execution ordering rules will still apply though; -populateDatabase will always be run before -analyseDatabase. - - -
    - -
    Data model -Data processed by Swift is strongly typed. It may be take the form -of values in memory or as out-of-core files on disk. Language constructs -called mappers specify how each piece of data is stored. - -
    Mappers - -When a DSHandle represents a data file (or container of datafiles), it is -associated with a mapper. The mapper is used to -identify which files belong to that DSHandle. - - -A dataset's physical representation is declared by a mapping descriptor, -which defines how each element in the dataset's logical schema is -stored in, and fetched from, physical structures such as directories, -files, and remote servers. - - - -Mappers are parameterized to take into account properties such as -varying dataset location. -In order -to access a dataset, we need to know three things: its type, -its mapping, and the value(s) of any parameter(s) associated -with the mapping descriptor. For example, if we want to describe a dataset, -of type imagefile, and whose physical -representation is a file called "file1.bin" located at "/home/yongzh/data/", -then the dataset might be declared as follows: - - - -imagefile f1<single_file_mapper;file="/home/yongzh/data/file1.bin"> - - - -The above example declares a dataset called f1, which uses a single -file mapper to map a file from a specific location. - - -SwiftScript has a simplified syntax for this case, since single_file_mapper -is frequently used: - - -binaryfile f1<"/home/yongzh/data/file1.bin"> - - - - -Swift comes with a number of mappers that handle common mapping patterns. -These are documented in the mappers section -of this guide. - - -
    - -
    -
    - More technical details about SwiftScript -The syntax of SwiftScript has a superficial resemblance to C and -Java. For example, { and } characters are used to enclose blocks of -statements. - - -A SwiftScript program consists of a number of statements. -Statements may declare types, procedures and variables, assign values to -variables, and express operations over arrays. - - - -
    Variables -Variables in SwiftScript are declared to be of a specific type. -Assignments to those variables must be data of that type. -SwiftScript variables are single-assignment - a value may be assigned -to a variable at most once. This assignment can happen at declaration time -or later on in execution. When an attempt to read from a variable -that has not yet been assigned is made, the code performing the read -is suspended until that variable has been written to. This forms the -basis for Swift's ability to parallelise execution - all code will -execute in parallel unless there are variables shared between the code -that cause sequencing. - -
    - Variable Declarations - -Variable declaration statements declare new variables. They can -optionally assign a value to them or map those variables to on-disk files. - - -Declaration statements have the general form: - - typename variablename (<mapping> | = initialValue ) ; - -The format of the mapping expression is defined in the Mappers section. -initialValue may be either an expression or a procedure call that -returns a single value. - -Variables can also be declared in a multivalued-procedure statement, -described in another section. -
    - -
    - Assignment Statements - -Assignment statements assign values to previously declared variables. -Assignments may only be made to variables that have not already been -assigned. Assignment statements have the general form: - - - variable = value; - -where value can be either an expression or a procedure call that returns -a single value. - - - -Variables can also be assigned in a multivalued-procedure statement, -described in another section. - -
    -
    - -
    Procedures - -There are two kinds of procedure: An atomic procedure, which -describes how an external program can be executed; and compound -procedures which consist of a sequence of SwiftScript statements. - - - -A procedure declaration defines the name of a procedure and its -input and output parameters. SwiftScript procedures can take multiple -inputs and produce multiple outputs. Inputs are specified to the right -of the function name, and outputs are specified to the left. For example: - - -(type3 out1, type4 out2) myproc (type1 in1, type2 in2) - - -The above example declares a procedure called myproc, which -has two inputs in1 (of type type1) -and in2 (of type type2) -and two outputs out1 (of type type3) -and out2 (of type type4). - - - -A procedure input parameter can be an optional -parameter in which case it must be declared with a default -value. When calling a procedure, both positional parameter and named -parameter passings can be passed, provided that all optional -parameters are declared after the required parameters and any -optional parameter is bound using keyword parameter passing. -For example, if myproc1 is defined as: - - -(binaryfile bf) myproc1 (int i, string s="foo") - - -Then that procedure can be called like this, omitting the optional -parameter s: - - -binaryfile mybf = myproc1(1); - - -or like this supplying a value for the optional parameter -s: - - -binaryfile mybf = myproc1 (1, s="bar"); - - - - -
    Atomic procedures - -An atomic procedure specifies how to invoke an -external executable program, and how logical data -types are mapped to command line arguments. - - - -Atomic procedures are defined with the app keyword: - -app (binaryfile bf) myproc (int i, string s="foo") { - myapp i s @filename(bf); -} - - -which specifies that myproc invokes an executable -called myapp, -passing the values of i, s -and the filename of bf as command line arguments. - -
    - -
    Compound procedures - -A compound procedure contains a set of SwiftScript statements: - - -(type2 b) foo_bar (type1 a) { - type3 c; - c = foo(a); // c holds the result of foo - b = bar(c); // c is an input to bar -} - - - -
    -
    -
    - Control Constructs - -SwiftScript provides if, switch, -foreach, and iterate constructs, -with syntax and semantics similar to comparable constructs in -other high-level languages. - -
    foreach - -The foreach construct is used to apply a block of statements to -each element in an array. For example: - - -check_order (file a[]) { - foreach f in a { - compute(f); - } -} - - - -foreach statements have the general form: - - -foreach controlvariable (,index) in expression { - statements -} - - -The block of statements is evaluated once for each element in -expression which must be an array, -with controlvariable set to the corresponding element -and index (if specified) set to the -integer position in the array that is being iterated over. - - -
    - -
    if - -The if statement allows one of two blocks of statements to be -executed, based on a boolean predicate. if statements generally -have the form: - -if(predicate) { - statements -} else { - statements -} - - -where predicate is a boolean expression. - -
    - -
    switch - -switch expressions allow one of a selection of blocks to be chosen based on -the value of a numerical control expression. switch statements take the -general form: - -switch(controlExpression) { - case n1: - statements2 - case n2: - statements2 - [...] - default: - statements -} - -The control expression is evaluated, the resulting numerical value used to -select a corresponding case, and the statements belonging to that -case block -are evaluated. If no case corresponds, then the statements belonging to -the default block are evaluated. - -Unlike C or Java switch statements, execution does not fall through to -subsequent case blocks, and no break -statement is necessary at the end of each block. - -
    - -
    iterate - -iterate expressions allow a block of code to be evaluated repeatedly, with an -integer parameter sweeping upwards from 0 until a termination condition -holds. - - -The general form is: - -iterate var { - statements; -} until (terminationExpression); - -with the variable var starting at 0 and increasing -by one in each iteration. That -variable is in scope in the statements block and when evaluating the -termination expression. - -
    -
    -
    - -
    Operators - -The following infix operators are available for use in -SwiftScript expressions. - - - - operatorpurpose - - +numeric addition; string concatenation - -numeric subtraction - *numeric multiplication - /floating point division - %/integer division - %%integer remainder of division - == !=comparison and not-equal-to - < > <= >=numerical ordering - && ||boolean and, or - !boolean not - - -
    -
    - -
    Global constants - -At the top level of a SwiftScript program, the global -modified may be added to a declaration so that it is visible throughout -the program, rather than only at the top level of the program. This allows -global constants (of any type) to be defined. (since Swift 0.10) - -
    - -
    Imports - -The import directive can be used to import definitions from -another SwiftScript file. (since Swift 0.10) - - -For example, a SwiftScript program might contain this: - -import defs; -file f; - -which would import the content of defs.swift in the -current directory: - -type file; - - - -Imported files are read from the current working directory. - - -There is no requirement that a module is imported only once. If a module -is imported multiple times, for example in different files, then Swift will -only process the imports once. - - -Imports may contain anything that is valid in a SwiftScript program, -including code that causes remote execution. - -
    - -
    -
    - Mappers - -Mappers provide a mechanism to specify the layout of mapped datasets on -disk. This is needed when Swift must access files to transfer them to -remote sites for execution or to pass to applications. - -Swift provides a number of mappers that are useful in common cases. This -section details those standard mappers. For more complex cases, it is -possible to write application-specific mappers in Java and -use them within a SwiftScript program. - - -
    The single file mapper - - -The single_file_mapper maps a single physical file to a dataset. - - - - - Swift variable -------------------> Filename - - f myfile - - f[0] INVALID - - f.bar INVALID - - - - - - - - - parameter - meaning - - - - fileThe location of the physical file including path and file name. - - -
    - -Example: - - file f <single_file_mapper;file="plot_outfile_param">; - -There is a simplified syntax for this mapper: - - - - file f <"plot_outfile_param">; - -
    - -
    The simple mapper -The simple_mapper maps a file or a list of files -into an array by prefix, suffix, and pattern. If more than one file is -matched, each of the file names will be mapped as a subelement of the dataset. - - - - - - - parameter - meaning - - - - locationA directory that the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. When this mapper is used to specify output -filenames, pattern is ignored. - - -
    - - - -Examples: - - - - type file; - file f <simple_mapper;prefix="foo", suffix=".txt">; - -The above maps all filenames that start with foo and -have an extension .txt into file f. - - - - Swift variable -------------------> Filename - - f foo.txt - - - - - - -type messagefile; - -(messagefile t) greeting(string m) {. - app { - echo m stdout=@filename(t); - } -} - -messagefile outfile <simple_mapper;prefix="foo",suffix=".txt">; - -outfile = greeting("hi"); - - -This will output the string 'hi' to the file foo.txt. - - - -The simple_mapper can be used to map arrays. It will map the array index -into the filename between the prefix and suffix. - - -type messagefile; - -(messagefile t) greeting(string m) { - app { - echo m stdout=@filename(t); - } -} - -messagefile outfile[] <simple_mapper;prefix="baz",suffix=".txt">; - -outfile[0] = greeting("hello"); -outfile[1] = greeting("middle"); -outfile[2] = greeting("goodbye"); - - - - - Swift variable -------------------> Filename - - outfile[0] baz0000.txt - outfile[1] baz0001.txt - outfile[2] baz0002.txt - - - - - - -simple_mapper can be used to map structures. It will map the name of the -structure member into the filename, between the prefix and the -suffix. - - -type messagefile; - -type mystruct { - messagefile left; - messagefile right; -}; - -(messagefile t) greeting(string m) { - app { - echo m stdout=@filename(t); - } -} - -mystruct out <simple_mapper;prefix="qux",suffix=".txt">; - -out.left = greeting("hello"); -out.right = greeting("goodbye"); - - -This will output the string "hello" into the file -qux.left.txt and the string "goodbye" -into the file qux.right.txt. - - - - Swift variable -------------------> Filename - - out.left quxleft.txt - out.right quxright.txt - - - - -
    - -
    concurrent mapper - -concurrent_mapper is almost the same as the simple mapper, -except that it is used to map an output file, and the filename -generated will contain an extract sequence that is unique. -This mapper is the default mapper for variables when no mapper is -specified. - - - - - - - parameter - meaning - - - - locationA directory that the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. When this mapper is used to specify output -filenames, pattern is ignored. - - -
    - - - Example: - - file f1; - file f2 <concurrent_mapper;prefix="foo", suffix=".txt">; - -The above example would use concurrent mapper for f1 and -f2, and -generate f2 filename with prefix "foo" and extension ".txt" - -
    - -
    file system mapper - -filesys_mapper is similar to the simple mapper, -but maps a file or -a list of files to an array. Each of the filename is -mapped as an element in the array. The order of files in the resulting -array is not defined. - - -TODO: note on difference between location as a relative vs absolute -path wrt staging to remote location - as mihael said: -It's because you specify that location in the mapper. Try location="." -instead of location="/sandbox/..." - - - - - - parameter - meaning - - - - locationThe directory where the files are located. - prefixThe prefix of the files - suffixThe suffix of the files, for instance: ".txt" - patternA UNIX glob style pattern, for instance: -"*foo*" would match all file names that -contain foo. - - - -
    - - Example: - - file texts[] <filesys_mapper;prefix="foo", suffix=".txt">; - -The above example would map all filenames that start with "foo" -and have an extension ".txt" into the array texts. -For example, if the specified directory contains files: foo1.txt, footest.txt, -foo__1.txt, then the mapping might be: - - - Swift variable -------------------> Filename - - texts[0] footest.txt - texts[1] foo1.txt - texts[2] foo__1.txt - - - -
    - -
    fixed array mapper -The fixed_array_mapper maps from a string that -contains a list of filenames into a file array. - - - - - - parameter - meaning - - - - filesA string that contains a list of filenames, separated by space, comma or colon - - -
    - - Example: - - file texts[] <fixed_array_mapper;files="file1.txt, fileB.txt, file3.txt">; - -would cause a mapping like this: - - - Swift variable -------------------> Filename - - texts[0] file1.txt - texts[1] fileB.txt - texts[2] file3.txt - - - -
    - -
    array mapper - The array_mapper maps from an array of strings -into a file - - - - - - parameter - meaning - - - - filesAn array of strings containing one filename per element - - -
    - - Example: - -string s[] = [ "a.txt", "b.txt", "c.txt" ]; - -file f[] <array_mapper;files=s>; - -This will establish the mapping: - - - Swift variable -------------------> Filename - - f[0] a.txt - f[1] b.txt - f[2] c.txt - - - - -
    - -
    regular expression mapper -The regexp_mapper transforms one file name to -another using regular expression matching. - - - - - - - parameter - meaning - - - - sourceThe source file name - matchRegular expression pattern to match, use -() to match whatever regular expression is inside the -parentheses, and indicate the start and end of a group; the contents of a -group can be retrieved with the \\number special sequence -(two backslashes are needed because the backslash is an escape sequence introducer) - - transformThe pattern of the file name to -transform to, use \number to reference the -group matched. - - -
    - -Example: - - string s = "picture.gif"; - file f <regexp_mapper; - source=s, - match="(.*)gif", - transform="\\1jpg">; - -This example transforms a string ending gif into one -ending jpg and maps that to a file. - - - Swift variable -------------------> Filename - - f picture.jpg - - - - -
    - -
    csv mapper - - -The csv_mapper maps the content of a CSV (comma-separated -value) file into an array of structures. The dataset type needs to be -correctly defined to conform to the column names in the -file. For instance, if the file contains columns: -name age GPA then the type needs to have member elements -like this: - - type student { - file name; - file age; - file GPA; - } - - -If the file does not contain a header with column info, then the column -names are assumed as column1, column2, -etc. - - - - - - - parameter - meaning - - - - fileThe name of the CSV file to read mappings from. - headerWhether the file has a line describing header info; default is true - skipThe number of lines to skip at the beginning (after header line); default is 0. - hdelimHeader field delimiter; default is the value of the delim parameter - delimContent field delimiters; defaults are space, tab and comma - - -
    - - Example: - - student stus[] <csv_mapper;file="stu_list.txt">; - -The above example would read a list of student info from file -"stu_list.txt" and map them into a student array. By default, the file should contain a header line specifying the names of the columns. -If stu_list.txt contains the following: - -name,age,gpa -101-name.txt, 101-age.txt, 101-gpa.txt -name55.txt, age55.txt, age55.txt -q, r, s - -then some of the mappings produced by this example would be: - - - Swift variable -------------------> Filename - - stus[0].name 101-name.txt - stus[0].age 101-age.txt - stus[0].gpa 101-gpa.txt - stus[1].name name55.txt - stus[1].age age55.txt - stus[1].gpa gpa55.txt - stus[2].name q - stus[2].age r - stus[2].gpa s - - - -
    - -
    external mapper - -The external mapper, ext maps based on the output of a -supplied Unix executable. - - - - - - - parameter - meaning - - - - execThe name of the executable -(relative to the current directory, if an absolute path is not -specified) - *Other parameters are passed to the -executable prefixed with a - symbol - - -
    - - -The output of the executable should consist of two columns of data, separated -by a space. The first column should be the path of the mapped variable, -in SwiftScript syntax (for example [2] means the 2nd element of an -array) or the symbol $ to represent the root of the mapped variable. - - - Example: -With the following in mapper.sh, - -#!/bin/bash -echo "[2] qux" -echo "[0] foo" -echo "[1] bar" - - -then a mapping statement: - - - student stus[] <ext;exec="mapper.sh">; - - -would map - - - - Swift variable -------------------> Filename - - stus[0] foo - stus[1] bar - stus[2] qux - - - - - -
    - -
    mapping URIs - -The above mappers may be used to map files based on a URI which can be specified in the filename. This is useful for mapping files on remote machines. - - - - Example: - - - student st <single_file_mapper;file="gsiftp://communicado.ci.uchicago.edu//tmp/student.txt">; - - - - - -
    - -
    -
    Commands - -The commands detailed in this section are available in the -bin/ directory of a Swift installation and can -by run from the commandline if that directory is placed on the -PATH. - -
    - swift - -The swift command is the main command line tool -for executing SwiftScript programs. - -
    Command-line Syntax -The swift command is invoked as follows: -swift [options] SwiftScript-program [SwiftScript-arguments] -with options taken from the following list, and SwiftScript-arguments -made available to the SwiftScript program through the -@arg function. - - Swift command-line options - -help or -h - - Display usage information - - -typecheck - - Does a typecheck of a SwiftScript program, instead of executing it. - - - -dryrun - - Runs the SwiftScript program without submitting any jobs (can be used to get - a graph) - - - - -monitor - - Shows a graphical resource monitor - - - - -resume file - - Resumes the execution using a log file - - - - -config file - - Indicates the Swift configuration file to be used for this run. - Properties in this configuration file will override the default - properties. If individual command line arguments are used for - properties, they will override the contents of this file. - - - - -verbose | -v - - Increases the level of output that Swift produces on the console - to include more detail about the execution - - - - -debug | -d - - Increases the level of output that Swift produces on the console - to include lots of detail about the execution - - - - -logfile file - - Specifies a file where log messages should go to. By default - Swift uses the name of the program being run and a numeric index - (e.g. myworkflow.1.log) - - - - -runid identifier - - Specifies the run identifier. This must be unique for every invocation - and is used in several places to keep files from different executions - cleanly separated. By default, a datestamp and random number are used - to generate a run identifier. When using this parameter, care should be - taken to ensure that the run ID remains unique with respect to all - other run IDs that might be used, irrespective of (at least) expected - execution sites, program or user. - - - - -tui - - Displays an interactive text mode monitor during a run. (since Swift 0.9) - - - - - -In addition, the following Swift properties can be set on the -command line: - - -caching.algorithm -clustering.enabled -clustering.min.time -clustering.queue.delay -ip.address -kickstart.always.transfer -kickstart.enabled -lazy.errors -pgraph -pgraph.graph.options -pgraph.node.options -sitedir.keep -sites.file -tc.file -tcp.port.range - - - -
    -
    Return codes - -The swift command may exit with the following return codes: - - - - - value - meaning - - - - 0success - 1command line syntax error or missing project name - 2error during execution - 3error during compilation - 4input file does not exist - - -
    -
    -
    -
    Environment variables - The swift is influenced by the -following environment variables: - - -GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment before running -Swift. These can be set to inform Swift of the -configuration of your local firewall. More information can be found in -the Globus firewall -How-to. - - -COG_OPTS - set in the environment before running Swift. Options set in this -variable will be passed as parameters to the Java Virtual Machine which -will run Swift. The parameters vary between virtual machine imlementations, -but can usually be used to alter settings such as maximum heap size. -Typing 'java -help' will sometimes give a list of commands. The Sun Java -1.4.2 command line options are documented here. - - - -
    - -
    - -
    swift-osg-ress-site-catalog - -The swift-osg-ress-site-catalog command generates a site -catalog based on OSG's -ReSS information system (since Swift 0.9) - - -Usage: swift-osg-ress-site-catalog [options] - - - --help - -Show help message - - - - --vo=[name] - -Set what VO to query ReSS for - - - - --engage-verified - -Only retrieve sites verified by the Engagement VO site -verification tests This can not be used together with --vo, -as the query will only work for sites advertising support for the -Engagement VO. - -This option means information will be retrieved from the -Engagement collector instead of the top-level ReSS collector. - - - - - --out=[filename] - -Write to [filename] instead of stdout - - - - --condor-g - -Generates sites files which will submit jobs using a local Condor-G -installation rather than through direct GRAM2 submission. (since Swift 0.10) - - - - - - - - -
    - - -
    swift-plot-log - -swift-plot-log generates summaries of Swift run log -files. - - -Usage: swift-plot-log [logfile] [targets] - - -When no targets are specified, swift-plog-log will -generate an HTML report for the run. When targets are specified, only -those named targets will be generated. - -
    - -
    -
    Executing <literal>app</literal> procedures - -This section describes how Swift executes app procedures, -and requirements on the behaviour of application programs used in -app procedures. -These requirements are primarily to ensure -that the Swift can run your application in different places and with the -various fault tolerance mechanisms in place. - - -
    Mapping of <literal>app</literal> semantics into unix -process execution semantics - -This section describes how an app procedure -invocation is translated into a (remote) unix process execution. It does not -describe the mechanisms by which Swift performs that translation; that -is described in the next section. - -In this section, this example SwiftScript program is used -for reference: - - - type file; - - app (file o) count(file i) { - wc @i stdout=@o; - } - - file q <"input.txt">; - file r <"output.txt">; - - - -The executable for wc will be looked up in tc.data. - - - -This unix executable will then be executed in some application -procedure workspace. This means: - - - -Each application procedure workspace will have an application workspace -directory. (TODO: can collapse terms //application procedure workspace// -and //application workspace directory// ? - - - -This application workspace directory will not be shared with any other -application procedure execution attempt; all -application procedure -execution attempts will run with distinct application procedure -workspaces. (for the avoidance of doubt: - If a SwiftScript procedure invocation is subject -to multiple application procedure execution attempts (due to Swift-level -restarts, retries or replication) then each of those application procedure -execution attempts will be made in a different application procedure workspace. -) - - -The application workspace directory will be a directory on a POSIX -filesystem accessible throughout the application execution by the -application executable. - - - -Before the application executable is executed: - - - - - -The application workspace directory will exist. - - - -The input files will exist inside the application workspace -directory (but not necessarily as direct children; there may be -subdirectories within the application workspace directory). - - - -The input files will be those files mapped -to input parameters of the application procedure -invocation. (In the example, this means that the file -input.txt will exist in the application workspace -directory) - - - -For each input file dataset, it will be the case that -@filename or -@filenames invoked with that dataset as a parameter -will return the path -relative to the application workspace directory for the file(s) that are -associated with that dataset. (In the example, that means that @i will -evaluate to the path input.txt) - - - -For each file-bound parameter of the Swift procedure invocation, the -associated files (determined by data type?) will always exist. - - - -The input files must be treated as read only files. This may or may not -be enforced by unix file system permissions. They may or may not be copies -of the source file (conversely, they may be links to the actual source file). - - - - - -During/after the application executable execution, -the following must be true: - - - - -If the application executable execution was successful (in the opinion -of the application executable), then the application executable should -exit with unix return code 0; -if the application executable execution -was unsuccessful (in the opinion of the application executable), then the -application executable should exit with unix return code not equal to -0. - - - -Each file mapped from an output parameter of the SwiftScript procedure -call must exist. Files will be mapped in the same way as for input files. - - -(? Is it defined that output subdirectories will be precreated before -execution or should app executables expect to make them? That's probably -determined by the present behaviour of wrapper.sh) - - - -Output produced by running the application executable on some inputs should -be the same no matter how many times, when or where that application -executable is run. 'The same' can vary depending on application (for example, -in an application it might be acceptable for a PNG->JPEG conversion to -produce different, similar looking, output jpegs depending on the -environment) - - - - - -Things to not assume: - - - - - -anything about the path of the application workspace directory - - - -that either the application workspace directory will be deleted or will -continue to exist or will remain unmodified after execution has finished - - - -that files can be passed(?def) between application procedure invocations -through any mechanism except through files known to Swift through the -mapping mechanism (there is some exception here for external -datasets - there are a separate set of assertions that hold for -external datasets) - - - -that application executables will run on any particular site of those -available, or than any combination of applications will run on the same or -different sites. - - - - -
    - -
    -How Swift implements the site execution model - - - -This section describes the implementation of the semantics described -in the previous section. - - - -Swift executes application procedures on one or more sites. - - - -Each site consists of: - - - - -worker nodes. There is some execution mechanism -through which the Swift client side executable can execute its -wrapper script on those -worker nodes. This is commonly GRAM or Falkon or coasters. - - - -a site-shared file system. This site shared filesystem is accessible -through some file transfer mechanism from the -Swift client side -executable. This is commonly GridFTP or coasters. This site shared -filesystem is also accessible through the posix file system on all worker -nodes, mounted at the same location as seen through the file transfer -mechanism. Swift is configured with the location of some site working -directory on that site-shared file system. - - - - -There is no assumption that the site shared file system for one site is -accessible from another site. - - - -For each workflow run, on each site that is used by that run, a run -directory is created in the site working directory, by the Swift client -side. - - - -In that run directory are placed several subdirectories: - - - - -shared/ - site shared files cache - - - -kickstart/ - when kickstart is used, kickstart record files -for each job that has generated a kickstart record. - - - - -info/ - wrapper script log files - - - -status/ - job status files - - - -jobs/ - application workspace directories (optionally placed here - -see below) - - - - -Application execution looks like this: - - - -For each application procedure call: - - - -The Swift client side selects a site; copies the input files for that -procedure call to the site shared file cache if they are not already in -the cache, using the file transfer mechanism; and then invokes the wrapper -script on that site using the execution mechanism. - - - -The wrapper script creates the application workspace directory; places the -input files for that job into the application workspace directory using -either cp or ln -s (depending on a configuration option); executes the -application unix executable; copies output files from the application -workspace directory to the site shared directory using cp; creates a -status file under the status/ directory; and exits, returning control to -the Swift client side. Logs created during the execution of the wrapper -script are stored under the info/ directory. - - - -The Swift client side then checks for the presence of and deletes a status -file indicating success; and copies files from the site shared directory to -the appropriate client side location. - - - -The job directory is created (in the default mode) under the jobs/ -directory. However, it can be created under an arbitrary other path, which -allows it to be created on a different file system (such as a worker node -local file system in the case that the worker node has a local file -system). - - -
    - -
    - -
    - Technical overview of the Swift architecture - -This section attempts to provide a technical overview of the Swift -architecture. - - -
    karajan - the core execution engine -
    - -
    Execution layer - -The execution layer causes an application program (in the form of a unix -executable) to be executed either locally or remotely. - - -The two main choices are local unix execution and execution through GRAM. -Other options are available, and user provided code can also be plugged in. - - -The kickstart utility can -be used to capture environmental information at execution time -to aid in debugging and provenance capture. - -
    - -
    SwiftScript language compilation layer - -Step i: text to XML intermediate form parser/processor. parser written in -ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the -intermediate language is in resources/XDTM.xsd. - - -Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads -the XML intermediate form. compiles to karajan workflow language - for -example, expressions are converted from SwiftScript syntax into Karajan -syntax, and function invocations become karajan function invocations -with various modifications to parameters to accomodate return parameters -and dataset handling. - -
    - -
    Swift/karajan library layer - -Some Swift functionality is provided in the form of Karajan libraries -that are used at runtime by the Karajan workflows that the Swift -compiler generates. - -
    - -
    - -
    Ways in which Swift can be extended -Swift is extensible in a number of ways. It is possible to add -mappers to accomodate different filesystem arrangements, site selectors -to change how Swift decides where to run each job, and job submission -interfaces to submit jobs through different mechanisms. - -A number of mappers are provided as part of the Swift release and -documented in the mappers section. -New mappers can be implemented -in Java by implementing the org.griphyn.vdl.mapping.Mapper interface. The -Swift -tutorial contains a simple example of this. - -Swift provides a default site selector, the Adaptive Scheduler. -New site selectors can be plugged in by implementing the -org.globus.cog.karajan.scheduler.Scheduler interface and modifying -libexec/scheduler.xml and etc/karajan.properties to refer to the new -scheduler. - -Execution providers and filesystem providers, which allow to Swift -to execute jobs and to stage files in and out through mechanisms such -as GRAM and GridFTP can be implemented as Java CoG kit providers. - -
    - -
    Function reference - -This section details functions that are available for use in the SwiftScript -language. - -
    @arg - -Takes a command line parameter name as a string parameter and an optional -default value and returns the value of that string parameter from the -command line. If no default value is specified and the command line parameter -is missing, an error is generated. If a default value is specified and the -command line parameter is missing, @arg will return the default value. - - -Command line parameters recognized by @arg begin with exactly one hyphen -and need to be positioned after the script name. - - - For example: - -trace(@arg("myparam")); -trace(@arg("optionalparam", "defaultvalue")); - - -$ swift arg.swift -myparam=hello -Swift v0.3-dev r1674 (modified locally) - -RunID: 20080220-1548-ylc4pmda -SwiftScript trace: defaultvalue -SwiftScript trace: hello - - -
    - -
    @extractint - -@extractint(file) will read the specified file, parse an integer from the -file contents and return that integer. - -
    - -
    @filename - -@filename(v) will return a string containing the filename(s) for the file(s) -mapped to the variable v. When more than one filename is returned, the -filenames will be space separated inside a single string return value. - -
    -
    @filenames - -@filenames(v) will return multiple values (!) containing the filename(s) for -the file(s) mapped to the variable v. (compare to -@filename) - -
    -
    @regexp - -@regexp(input,pattern,replacement) will apply regular expression -substitution using the Java java.util.regexp API. For example: - -string v = @regexp("abcdefghi", "c(def)g","monkey"); - -will assign the value "abmonkeyhi" to the variable v. - -
    -
    @strcat - -@strcat(a,b,c,d,...) will return a string containing all of the strings -passed as parameters joined into a single string. There may be any number -of parameters. - - -The + operator concatenates two strings: @strcat(a,b) is the same as a + b - -
    -
    @strcut - -@strcut(input,pattern) will match the regular expression in the pattern -parameter against the supplied input string and return the section that -matches the first matching parenthesised group. - - -For example: - - - -string t = "my name is John and i like puppies."; -string name = @strcut(t, "my name is ([^ ]*) "); -string out = @strcat("Your name is ",name); -trace(out); - - - -will output the message: Your name is John. - -
    - -
    @strsplit - -@strsplit(input,pattern) will split the input string based on separators -that match the given pattern and return a string array. (since Swift 0.9) - - -Example: - - - -string t = "my name is John and i like puppies."; -string words[] = @strsplit(t, "\\s"); -foreach word in words { - trace(word); -} - - - -will output one word of the sentence on each line (though -not necessarily in order, due to the fact that foreach -iterations execute in parallel). - -
    - - -
    @toint - -@toint(input) will parse its input string into an integer. This can be -used with @arg to pass input parameters to a SwiftScript program as -integers. - -
    -
    - -
    Built-in procedure reference - -This section details built-in procedures that are available for use in -the SwiftScript language. - - -
    readData - -readData will read data from a specified file. - - -The format of the input file is controlled by the type of the return -value. - - - -For scalar return types, such as int, the specified file should contain -a single value of that type. - - -For arrays of scalars, the specified file should contain one value -per line. - - -For structs of scalars, the file should contain two rows. -The first row should be structure member names separated by whitespace. -The second row should be the corresponding values for each structure -member, separated by whitespace, in the same order as the header row. - - -For arrays of structs, the file should contain a heading row listing -structure member names separated by whitespace. There should be one row -for each element of the array, with structure member elements listed in -the same order as the header row and separated by whitespace. (since Swift 0.4) - - -
    -
    readdata2 - -readdata2 will read data from a specified file, like readdata, but using -a different file format more closely related to that used by the -ext mapper. - - -Input files should list, one per line, a path into a Swift structure, and -the value for that position in the structure: - -rows[0].columns[0] = 0 -rows[0].columns[1] = 2 -rows[0].columns[2] = 4 -rows[1].columns[0] = 1 -rows[1].columns[1] = 3 -rows[1].columns[2] = 5 - -which can be read into a structure defined like this: - -type vector { - int columns[]; -} - -type matrix { - vector rows[]; -} - -matrix m; - -m = readData2("readData2.in"); - - - - -(since Swift 0.7) - -
    -
    trace - -trace will log its parameters. By default these will appear on both stdout -and in the run log file. Some formatting occurs to produce the log message. -The particular output format should not be relied upon. (since Swift 0.4) - -
    - -
    writeData - -writeData will write out data structures in the format -described for readData - -
    -
    - -
    - - Swift configuration properties - - - - Various aspects of the behavior of the Swift Engine can be - configured through properties. The Swift Engine recognizes a global, - per installation properties file which can found in etc/swift.properties in the Swift installation directory and a user - properties file which can be created by each user in ~/.swift/swift.properties. The Swift Engine - will first load the global properties file. It will then try to load - the user properties file. If a user properties file is found, - individual properties explicitly set in that file will override the - respective properties in the global properties file. Furthermore, - some of the properties can be overridden directly using command line - arguments to the swift command. - - - - - - Swift properties are specified in the following format: - - -<name>=<value> - - - The value can contain variables which will be expanded when the - properties file is read. Expansion is performed when the name of - the variable is used inside the standard shell dereference - construct: ${name}. The following variables - can be used in the Swift configuration file: - - - Swift Configuration Variables - - - - swift.home - - - - - Points to the Swift installation directory - ($SWIFT_HOME). In general, this should not be set -as Swift can find its own installation directory, and incorrectly setting it -may impair the correct functionality of Swift. - - - - - - - - user.name - - - - - The name of the current logged in user. - - - - - - - - user.home - - - - - The user's home directory. - - - - - - - The following is a list of valid Swift properties: - - - Swift Properties - - - - caching.algorithm - - - - - Valid values: LRU - - - - Default value: LRU - - - - - Swift caches files that are staged in on remote - resources, and files that are produced remotely - by applications, such that they can be re-used - if needed without being transfered again. - However, the amount of remote file system space - to be used for caching can be limited using the - swift:storagesize profile - entry in the sites.xml file. Example: - - - -<pool handle="example" sysinfo="INTEL32::LINUX"> - <gridftp url="gsiftp://example.org" storage="/scratch/swift" major="2" minor="4" patch="3"/> - <jobmanager universe="vanilla" url="example.org/jobmanager-pbs" major="2" minor="4" patch="3"/> - <workdirectory>/scratch/swift</workdirectory> - <profile namespace="SWIFT" key="storagesize">20000000</profile> -</pool> - - - - - The decision of which files to keep in the cache - and which files to remove is made considering - the value of the - caching.algorithm property. - Currently, the only available value for this - property is LRU, which would - cause the least recently used files to be - deleted first. - - - - - - - - clustering.enabled - - - - - Valid values: true, false - - - - Default value: false - - - - Enables clustering. - - - - - - - - clustering.min.time - - - - - Valid values: <int> - - - - Default value: 60 - - - - - Indicates the threshold wall time for - clustering, in seconds. Jobs that have a - wall time smaller than the value of this - property will be considered for clustering. - - - - - - - - clustering.queue.delay - - - - - Valid values: <int> - - - - Default value: 4 - - - - - This property indicates the interval, in - seconds, at which the clustering queue is - processed. - - - - - - - execution.retries - - - Valid values: positive integers - - - Default value: 2 - - - The number of time a job will be retried if it - fails (giving a maximum of 1 + - execution.retries attempts at execution) - - - - - - - foreach.max.threads - - - Valid values: positive integers - - - Default value: 1024 - - -Limits the number of concurrent iterations that each foreach statement -can have at one time. This conserves memory for swift programs that -have large numbers of iterations (which would otherwise all be executed -in parallel). (since Swift 0.9) - - - - - - - - ip.address - - - - - Valid values: <ipaddress> - - - - Default value: N/A - - - - The Globus GRAM service uses a callback - mechanism to send notifications about the status - of submitted jobs. The callback mechanism - requires that the Swift client be reachable from - the hosts the GRAM services are running on. - Normally, Swift can detect the correct IP address - of the client machine. However, in certain cases - (such as the client machine having more than one - network interface) the automatic detection - mechanism is not reliable. In such cases, the IP - address of the Swift client machine can be - specified using this property. The value of this - property must be a numeric address without quotes. - - - This option is deprecated and the hostname - property should be used instead. - - - - - - - kickstart.always.transfer - - - - - Valid values: true, false - - - - Default value: false - - - - - This property controls when output from - Kickstart is transfered back to the submit site, - if Kickstart is enabled. When set to - false, Kickstart output is - only transfered for jobs that fail. If set to - true, Kickstart output is - transfered after every job is completed or - failed. - - - - - - - - kickstart.enabled - - - - - Valid values: true, false, maybe - - - - Default value: maybe - - - - - This option allows controlling of - when Swift uses Kickstart. A value of - false disables the use of - Kickstart, while a value of - true enables the use of - Kickstart, in which case sites specified in the - sites.xml file - must have valid - gridlaunch attributes. - The maybe value will - enable the use of Kickstart only - on sites that have the - gridlaunch attribute - specified. - - - - - - - - lazy.errors - - - - - Valid values: true, false - - - - Default value: false - - - - - Swift can report application errors in two - modes, depending on the value of this property. - If set to false, Swift will - report the first error encountered and - immediately stop execution. If set to - true, Swift will attempt to - run as much as possible from a SwiftScript program before - stopping execution and reporting all errors - encountered. - - When developing SwiftScript programs, using the - default value of false can - make the program easier to debug. However - in production runs, using true - will allow more of a SwiftScript program to be run before - Swift aborts execution. - - - - - - - pgraph - - - - - Valid values: true, false, <file> - - - - Default value: false - - - - - Swift can generate a -Graphviz file representing - the structure of the SwiftScript program it has run. If this - property is set to true, - Swift will save the provenance graph in a file - named by concatenating the program name and the - instance ID (e.g. helloworld-ht0adgi315l61.dot). - - - If set to false, no - provenance graph will be generated. If a file - name is used, then the provenance graph will be - saved in the specified file. - - - The generated dot file can be rendered - into a graphical form using - Graphviz, - for example with a command-line such as: - - -$ swift -pgraph graph1.dot q1.swift -$ dot -ograph.png -Tpng graph1.dot - - - - - - - pgraph.graph.options - - - - - Valid values: <string> - - - - Default value: splines="compound", rankdir="TB" - - - - - This property specifies a Graphviz - specific set of parameters for the graph. - - - - - - - - pgraph.node.options - - - - - Valid values: <string> - - - - Default value: color="seagreen", style="filled" - - - - - Used to specify a set of Graphviz - specific properties for the nodes in the graph. - - - - - - - - provenance.log - - - - Valid values: true, false - - - Default value: false - - - This property controls whether the log file will contain provenance information enabling this will increase the size of log files, sometimes significantly. - - - - - - - replication.enabled - - - - - Valid values: true, false - - - - Default value: false - - - -Enables/disables replication. Replication is used to deal with jobs sitting -in batch queues for abnormally large amounts of time. If replication is enabled -and certain conditions are met, Swift creates and submits replicas of jobs, and -allows multiple instances of a job to compete. - - - - - - - replication.limit - - - - - Valid values: positive integers - - - - Default value: 3 - - - -The maximum number of replicas that Swift should attempt. - - - - - - - sitedir.keep - - - - Valid values: true, false - - - - Default value: false - - - -Indicates whether the working directory on the remote site should be -left intact even when a run completes successfully. This can be -used to inspect the site working directory for debugging purposes. - - - - - - - sites.file - - - - - Valid values: <file> - - - - Default value: ${swift.home}/etc/sites.xml - - - - - Points to the location of the site - catalog, which contains a list of all sites that - Swift should use. - - - - - - - - - status.mode - - - - Valid values: files, provider - - - - Default value: files - - - -Controls how Swift will communicate the result code of running user programs -from workers to the submit side. In files mode, a file -indicating success or failure will be created on the site shared filesystem. -In provider mode, the execution provider job status will -be used. - - -provider mode requires the underlying job execution system -to correctly return exit codes. In at least the cases of GRAM2, and clusters -used with any provider, exit codes are not returned, and so -files mode must be used in those cases. Otherwise, -provider mode can be used to reduce the amount of -filesystem access. (since Swift 0.8) - - - - - - - tc.file - - - - Valid values: <file> - - - - Default value: ${swift.home}/etc/tc.data - - - - - Points to the location of the transformation - catalog file which contains information about - installed applications. Details about the format - of the transformation catalog can be found - here. - - - - - - - - tcp.port.range - - - Valid values: <start>,<end> where start and end are integers - Default value: none - -A TCP port range can be specified to restrict the ports on which -GRAM callback services are started. This is likely needed if your - submit host is behind a firewall, in which case the firewall -should be configured to allow incoming connections on ports in -the range. - - - - - - - - throttle.file.operations - - - - - Valid values: <int>, off - - - - Default value: 8 - - - - - Limits the total number of concurrent file - operations that can happen at any given time. - File operations (like transfers) require an - exclusive connection to a site. These - connections can be expensive to establish. A - large number of concurrent file operations may - cause Swift to attempt to establish many such - expensive connections to various sites. Limiting - the number of concurrent file operations causes - Swift to use a small number of cached - connections and achieve better overall - performance. - - - - - - - - throttle.host.submit - - - - - Valid values: <int>, off - - - - Default value: 2 - - - - - Limits the number of concurrent submissions for - any of the sites Swift will try to send jobs to. - In other words it guarantees that no more than - the value of this throttle jobs sent to any - site will be concurrently in a state of being - submitted. - - - - - - - - throttle.score.job.factor - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - The Swift scheduler has the ability to limit - the number of concurrent jobs allowed on a - site based on the performance history of that - site. Each site is assigned a score (initially - 1), which can increase or decrease based on - whether the site yields successful or faulty - job runs. The score for a site can take values - in the (0.1, 100) interval. The number of - allowed jobs is calculated using the - following formula: - - - 2 + score*throttle.score.job.factor - - - This means a site will always be allowed - at least two concurrent jobs and at most - 2 + 100*throttle.score.job.factor. With a - default of 4 this means at least 2 jobs and - at most 402. - - - This parameter can also be set per site - using the jobThrottle profile key in a site - catalog entry. - - - - - - - throttle.submit - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - - Limits the number of concurrent submissions for - a run. This throttle only limits - the number of concurrent tasks (jobs) that are - being sent to sites, not the total number of - concurrent jobs that can be run. The submission - stage in GRAM is one of the most CPU expensive - stages (due mostly to the mutual authentication - and delegation). Having too many concurrent - submissions can overload either or both the - submit host CPU and the remote host/head node - causing degraded performance. - - - - - - - - - throttle.transfers - - - - - Valid values: <int>, off - - - - Default value: 4 - - - - - Limits the total number of concurrent file - transfers that can happen at any given time. - File transfers consume bandwidth. Too many - concurrent transfers can cause the network to be - overloaded preventing various other signaling - traffic from flowing properly. - - - - - - - - ticker.disable - - - - Valid values: true, false - - - - Default value: false - - - -When set to true, suppresses the output progress ticker that Swift sends -to the console every few seconds during a run (since Swift 0.9) - - - - - - - wrapper.invocation.mode - - - -Valid values: absolute, relative - - -Default value: absolute - - -Determines if Swift remote wrappers will be executed by specifying an -absolute path, or a path relative to the job initial working directory. -In most cases, execution will be successful with either option. However, -some execution sites ignore the specified initial working directory, and -so absolute must be used. Conversely on some sites, -job directories appear in a different place on the worker node file system -than on the filesystem access node, with the execution system handling -translation of the job initial working directory. In such cases, -relative mode must be used. (since Swift 0.9) - - - - - - - - wrapper.parameter.mode - - - -Controls how Swift will supply parameters to the remote wrapper script. -args mode will pass parameters on the command line. Some -execution systems do not pass commandline parameters sufficiently cleanly -for Swift to operate correctly. -files mode will pass parameters through an additional -input file (since Swift 0.95). This provides a cleaner communication channel -for parameters, at the expense of transferring an additional file for each -job invocation. - - - - - - - - wrapperlog.always.transfer - - - - - Valid values: true, false - - - - Default value: false - - - - - This property controls when output from - the Swift remote wrapper is transfered - back to the submit site. When set to - false, wrapper logs are - only transfered for jobs that fail. If set to - true, wrapper logs are - transfered after every job is completed or - failed. - - - - - - - - Example: - - -sites.file=${vds.home}/etc/sites.xml -tc.file=${vds.home}/etc/tc.data -ip.address=192.168.0.1 - - - - -
    - - -
    Profiles - -Profiles are configuration parameters than can be specified either for -sites or for transformation catalog entries. They influence the behaviour -of Swift towards that site (for example, by changing the load Swift will -place on that sites) or when running a particular procedure. - - -Profile entries for a site are specified in the site catalog. Profile -entries for specific procedures are specified in the transformation -catalog. - -
    Karajan namespace - maxSubmitRate limits the maximum rate of job submission, in jobs per second. -For example: - -<profile namespace="karajan" key="maxSubmitRate">0.2</profile> - -will limit job submission to 0.2 jobs per second (or equivalently, -one job every five seconds). - - jobThrottle -allows the job throttle factor (see Swift property throttle.score.job.factor) to be set per site. - - initialScore -allows the initial score for rate limiting and site selection to be set to -a value other than 0. - - delayBase controls how much a site will be delayed when it performs poorly. With each reduction -in a sites score by 1, the delay between execution attempts will increase by -a factor of delayBase. - status.mode allows the status.mode property to be set per-site instead of for an entire run. -See the Swift configuration properties section for more information. -(since Swift 0.8) -
    -
    swift namespace - storagesize limits the -amount of space that will be used on the remote site for temporary files. -When more than that amount of space is used, the remote temporary file -cache will be cleared using the algorithm specified in the -caching.algorithm property. - - wrapperInterpreter -The wrapper interpreter indicates the command (executable) to be used to run the Swift wrapper -script. The default is "/bin/bash" on Unix sites and "cscript.exe" on Windows sites. - - wrapperInterpreterOptions -Allows specifying additional options to the executable used to run the Swift wrapper. The defaults -are no options on Unix sites and "//Nologo" on Windows sites. - - wrapperScript -Specifies the name of the wrapper script to be used on a site. The defaults are "_swiftwrap" on -Unix sites and "_swiftwrap.vbs" on Windows sites. If you specify a custom wrapper script, it -must be present in the "libexec" directory of the Swift installation. - - cleanupCommand -Indicates the command to be run at the end of a Swift run to clean up the run directories on a -remote site. Defaults are "/bin/rm" on Unix sites and "cmd.exe" on Windows sites - - cleanupCommandOptions -Specifies the options to be passed to the cleanup command above. The options are passed in the -argument list to the cleanup command. After the options, the last argument is the directory -to be deleted. The default on Unix sites is "-rf". The default on Windows sites is ["/C", "del", "/Q"]. - - -
    -
    Globus namespace - maxwalltime specifies a walltime limit for each job, in minutes. - - -The following formats are recognized: - - Minutes - Hours:Minutes - Hours:Minutes:Seconds - - - Example: - -localhost echo /bin/echo INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:20:00" - - When replication is enabled (see replication), then walltime will also be enforced at the Swift client side: when -a job has been active for more than twice the maxwalltime, Swift will kill the -job and regard it as failed. - - -When clustering is used, maxwalltime will be used to -select which jobs will be clustered together. More information on this is -available in the clustering section. - - -When coasters as used, maxwalltime influences the default -coaster worker maxwalltime, and which jobs will be sent to which workers. -More information on this is available in the coasters -section. - - queue -is used by the PBS, GRAM2 and GRAM4 providers. This profile -entry specifies which queue jobs will be submitted to. The valid queue names -are site-specific. - - host_types -specifies the types of host that are permissible for a job to run on. -The valid values are site-specific. This profile entry is used by the -GRAM2 and GRAM4 providers. - - condor_requirements allows a requirements string to be specified -when Condor is used as an LRM behind GRAM2. Example: <profile namespace="globus" key="condor_requirements">Arch == "X86_64" || Arch="INTEL"</profile> - - slots -When using coasters, this parameter -specifies the maximum number of jobs/blocks that the coaster scheduler will have running at any given time. -The default is 20. - - jobsPerNode -This parameter determines how many coaster workers are -started one each compute node. The default value is 1. - - nodeGranularity -When allocating a coaster worker block, this parameter -restricts the number of nodes in a block to a multiple of this value. The total number of workers will -then be a multiple of jobsPerNode * nodeGranularity. The default value is 1. - - allocationStepSize -Each time the coaster block scheduler computes a schedule, it will attempt to allocate a -number of slots from the number of available slots (limited using the above slots profile). This -parameter specifies the maximum fraction of slots that are allocated in one schedule. Default is -0.1. - - lowOverallocation -Overallocation is a function of the walltime of a job which determines how long (time-wise) a -worker job will be. For example, if a number of 10s jobs are submitted to the coaster service, -and the overallocation for 10s jobs is 10, the coaster scheduler will attempt to start worker -jobs that have a walltime of 100s. The overallocation is controlled by manipulating the end-points -of an overallocation function. The low endpoint, specified by this parameter, is the overallocation -for a 1s job. The high endpoint is the overallocation for a (theoretical) job of infinite length. -The overallocation for job sizes in the [1s, +inf) interval is determined using an exponential decay function: - -overallocation(walltime) = walltime * (lowOverallocation - highOverallocation) * exp(-walltime * overallocationDecayFactor) + highOverallocation - -The default value of lowOverallocation is 10. - - highOverallocation -The high overallocation endpoint (as described above). Default: 1 - - overallocationDecayFactor -The decay factor for the overallocation curve. Default 0.001 (1e-3). - - spread -When a large number of jobs is submitted to the a coaster service, the work is divided into blocks. This -parameter allows a rough control of the relative sizes of those blocks. A value of 0 indicates that all work -should be divided equally between the blocks (and blocks will therefore have equal sizes). A value of 1 -indicates the largest possible spread. The existence of the spread parameter is based on the assumption -that smaller overall jobs will generally spend less time in the queue than larger jobs. By submitting -blocks of different sizes, submitted jobs may be finished quicker by smaller blocks. Default: 0.9. - - reserve -Reserve time is a time in the allocation of a worker that sits at the end of the worker time and -is useable only for critical operations. For example, a job will not be submitted to a worker if -it overlaps its reserve time, but a job that (due to inaccurate walltime specification) runs into -the reserve time will not be killed (note that once the worker exceeds its walltime, the queuing -system will kill the job anyway). Default 10 (s). - - maxnodes -Determines the maximum number of nodes that can be allocated in one coaster block. Default: unlimited. - - maxtime -Indicates the maximum walltime that a coaster block can have. Default: unlimited. - - remoteMonitorEnabled -If set to "true", the client side will get a Swing window showing, graphically, the state of the -coaster scheduler (blocks, jobs, etc.). Default: false - - -
    - -
    env namespace - -Profile keys set in the env namespace will be set in the unix environment of the -executed job. Some environment variables influence the worker-side -behaviour of Swift: - - -PATHPREFIX - set in env namespace profiles. This path is prefixed onto the start -of the PATH when jobs are -executed. It can be more useful than setting the PATH environment variable directly, -because setting PATH will cause the execution site's default path to be lost. - - -SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift will -use the path specified here as a worker-node local temporary directory to -copy input files to before running a job. If unset, Swift will keep input -files on the site-shared filesystem. In some cases, copying to a worker-node -local directory can be much faster than having applications access the -site-shared filesystem directly. - - -SWIFT_EXTRA_INFO - set in env namespace profiles. If set, -then Swift will execute the command specified in -SWIFT_EXTRA_INFO on execution sites immediately before -each application execution, and will record the stdout of that command in the -wrapper info log file for that job. This is intended to allow software -version and other arbitrary information about the remote site to be gathered -and returned to the submit side. (since Swift 0.9) - -
    -
    - -
    The Site Catalog - sites.xml - -The site catalog lists details of each site that Swift can use. The default -file contains one entry for local execution, and a large number of -commented-out example entries for other sites. - - - -By default, the site catalog is stored in etc/sites.xml. -This path can be overridden with the sites.file configuration property, -either in the Swift configuration file or on the command line. - - - -The sites file is formatted as XML. It consists of <pool> elements, -one for each site that Swift will use. - - -
    Pool element - -Each pool element must have a handle attribute, giving a symbolic name -for the site. This can be any name, but must correspond to entries for -that site in the transformation catalog. - - - -Optionally, the gridlaunch attribute can be used to specify the path to -kickstart on the site. - - - -Each pool must specify a file transfer method, an execution method -and a remote working directory. Optionally, profile settings can be specified. - - -
    -
    File transfer method - - -Transfer methods are specified with either -the <gridftp> element or the -<filesystem> element. - - -To use gridftp or local filesystem copy, use the <gridftp> -element: - -<gridftp url="gsiftp://evitable.ci.uchicago.edu" /> - -The url attribute may specify a GridFTP server, using the gsiftp URI scheme; -or it may specify that filesystem copying will be used (which assumes that -the site has access to the same filesystem as the submitting machine) using -the URI local://localhost. - - -Filesystem access using scp (the SSH copy protocol) can be specified using the -<filesystem> element: - -<filesystem url="www11.i2u2.org" provider="ssh"/> - -For additional ssh configuration information, see the ssh execution -provider documentation below. - - -Filesystem access using CoG coasters can be -also be specified using the <filesystem> element. More detail about -configuring that can be found in the CoG -coasters section. - -
    - -
    Execution method - - -Execution methods may be specified either with the <jobmanager> -or <execution> element. - - - -The <jobmanager> element can be used to specify -execution through GRAM2. For example, - - <jobmanager universe="vanilla" url="evitable.ci.uchicago.edu/jobmanager-fork" major="2" /> - -The universe attribute should always be set to vanilla. The -url attribute -should specify the name of the GRAM2 gatekeeper host, and the name of the -jobmanager to use. The major attribute should always be set to 2. - - - -The <execution> element can be used to specify -execution through other execution providers: - - -To use GRAM4, specify the gt4 provider. For example: - -<execution provider="gt4" jobmanager="PBS" url="tg-grid.uc.teragrid.org" /> - -The url attribute should specify the GRAM4 submission site. -The jobmanager -attribute should specify which GRAM4 jobmanager will be used. - - - -For local execution, the local provider should be used, -like this: - -<execution provider="local" url="none" /> - - - - -For PBS execution, the pbs provider should be used: - -<execution provider="pbs" url="none" /> - -The GLOBUS::queue profile key -can be used to specify which PBS queue jobs will be submitted to. - - - -For execution through a local Condor installation, the condor -provider should be used. This provider can run jobs either in the default -vanilla universe, or can use Condor-G to run jobs on remote sites. - - -When running locally, only the <execution> element -needs to be specified: - -<execution provider="condor" url="none" /> - - - -When running with Condor-G, it is necessary to specify the Condor grid -universe and the contact string for the remote site. For example: - - <execution provider="condor" /> - <profile namespace="globus" key="jobType">grid</profile> - <profile namespace="globus" key="gridResource">gt2 belhaven-1.renci.org/jobmanager-fork</profile> - - - - -For execution through SSH, the ssh provider should be used: - -<execution url="www11.i2u2.org" provider="ssh"/> - -with configuration made in ~/.ssh/auth.defaults with -the string 'www11.i2u2.org' changed to the appropriate host name: - -www11.i2u2.org.type=key -www11.i2u2.org.username=hategan -www11.i2u2.org.key=/home/mike/.ssh/i2u2portal -www11.i2u2.org.passphrase=XXXX - - - -For execution using the -CoG Coaster mechanism, the coaster provider -should be used: - -<execution provider="coaster" url="tg-grid.uc.teragrid.org" - jobmanager="gt2:gt2:pbs" /> - -More details about configuration of coasters can be found in the -section on coasters. - -
    -
    Work directory - - -The workdirectory element specifies where on the site files can be -stored. - -<workdirectory>/home/benc</workdirectory> - -This file must be accessible through the transfer mechanism specified -in the <gridftp> element and also mounted on all worker nodes that -will be used for execution. A shared cluster scratch filesystem is -appropriate for this. - - -
    -
    Profiles - - -Profile keys can be specified using -the <profile> element. For example: - -<profile namespace="globus" key="queue">fast</profile> - - -
    - - -The site catalog format is an evolution of the VDS site catalog format which -is documented -here. - -
    - -
    The Transformation Catalog - tc.data - -The transformation catalog lists where application executables are located -on remote sites. - - -By default, the site catalog is stored in etc/tc.data. -This path can be overridden with the tc.file configuration property, -either in the Swift configuration file or on the command line. - - -The format is one line per executable per site, with fields separated by -tabs. Spaces cannot be used to separate fields. - - Some example entries: - -localhost echo /bin/echo INSTALLED INTEL32::LINUX null -localhost touch /bin/touch INSTALLED INTEL32::LINUX null - -TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1" -TGUC R /usr/bin/R INSTALLED INTEL32::LINUX env::R_LIBS=/home/skenny/R_libs - - - -The fields are: site, transformation name, executable path, installation -status, platform, and profile entries. - - -The site field should correspond to a site name listed in the sites -catalog. - -The transformation name should correspond to the transformation name -used in a SwiftScript app procedure. - - -The executable path should specify where the particular executable is -located on that site. - - -The installation status and platform fields are not used. Set them to -INSTALLED and INTEL32::LINUX respectively. - - -The profiles field should be set to null if no profile entries are to be -specified, or should contain the profile entries separated by semicolons. - - -
    shell invocation - -Because the above implementation requires an entry for each executable on a given site, it is often preferable to simply have a single element for each site in the transformation catalog representing a wrapper that sets the environment and then invokes the shell to call a given application. This wrapper is installed on the site and can be used to set the PATH and other environment variables prior to invoking the shell so that each executable need not be entered in the tc.data file. - - for example, the entries for TGUC and localhost can now each be collapsed into a single line: - -localhost shell /usr/local/bin/swiftshell INSTALLED INTEL32::LINUX null -TGUC shell /usr/local/bin/swiftshell INSTALLED INTEL32::LINUX null - -where swiftshell sets up the users's environment so that all the installed applications are added to the PATH before the application is invoked. - - -touch would now be called in the SwiftScript like this: - -app (file tout) shelltest(){ - shell "touch" @filename(tout); -} - - -
    -
    - -
    Build options - -See the -Swift download page for instructions on downloading and -building Swift from source. When building, various build options can -be supplied on the ant commandline. These are summarised here: - - -with-provider-condor - build with CoG condor provider - - -with-provider-coaster - build with CoG coaster provider (see -the section on coasters). Since 0.8, -coasters are always built, and this option has no effect. - - -with-provider-deef - build with Falkon provider deef. In order for this -option to work, it is necessary to check out the provider-deef code in -the cog/modules directory alongside swift: - - -$ cd cog/modules -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef -$ cd ../swift -$ ant -Dwith-provider-deef=true redist - - - - -with-provider-wonky - build with provider-wonky, an execution provider -that provides delays and unreliability for the purposes of testing Swift's -fault tolerance mechanisms. In order for this option to work, it is -necessary to check out the provider-wonky code in the cog/modules -directory alongside swift: - - -$ cd cog/modules -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky -$ cd ../swift -$ ant -Dwith-provider-wonky=true redist - - - -no-supporting - produces a distribution without supporting commands such -as grid-proxy-init. This is intended for when the Swift distribution will be -used in an environment where those commands are already provided by other -packages, where the Swift package should be providing only Swift -commands, and where the presence of commands such as grid-proxy-init from -the Swift distribution in the path will mask the presence of those -commands from their true distribution package such as a Globus Toolkit -package. - -$ ant -Dno-supporting=true redist - - -
    - -
    Kickstart - - -Kickstart is a tool that can be used to gather various information -about the remote execution environment for each job that Swift tries -to run. - - - -For each job, Kickstart generates an XML invocation -record. By default this record is staged back to the submit -host if the job fails. - - - -Before it can be used it must be installed on the remote site and -the sites file must be configured to point to kickstart. - - - -Kickstart can be downloaded as part of the Pegasus 'worker package' available -from the worker packages section of the Pegasus download page. - - -Untar the relevant worker package somewhere where it is visible to all of the -worker nodes on the remote execution machine (such as in a shared application -filesystem). - - -Now configure the gridlaunch attribute of the sites catalog -to point to that path, by adding a gridlaunch -attribute to the pool element in the site -catalog: - - - -<pool handle="example" gridlaunch="/usr/local/bin/kickstart" sysinfo="INTEL32::LINUX"> -[...] -</pool> - - - - - - -There are various kickstat.* properties, which have sensible default -values. These are documented in the -properties section. - - - - -
    - -
    Reliability mechanisms - -This section details reliabilty mechanisms in Swift: retries, restarts -and replication. - - -
    Retries - -If an application procedure execution fails, Swift will attempt that -execution again repeatedly until it succeeds, up until the limit -defined in the execution.retries configuration -property. - - -Site selection will occur for retried jobs in the same way that it happens -for new jobs. Retried jobs may run on the same site or may run on a -different site. - - -If the retry limit execution.retries is reached for an -application procedure, then that application procedure will fail. This will -cause the entire run to fail - either immediately (if the -lazy.errors property is false) or -after all other possible work has been attempted (if the -lazy.errors property is true). - -
    - -
    Restarts - -If a run fails, Swift can resume the program from the point of -failure. When a run fails, a restart log file will be left behind in -a file named using the unique job ID and a .rlog extension. This restart log -can then be passed to a subsequent Swift invocation using the -resume -parameter. Swift will resume execution, avoiding execution of invocations -that have previously completed successfully. The SwiftScript source file -and input data files should not be modified between runs. - - -Every run creates a restart -log file with a named composed of the file name of the workflow -being executed, an invocation ID, a numeric ID, and the .rlog extension. For example, example.swift, when executed, could produce -the following restart log file: example-ht0adgi315l61.0.rlog. Normally, if -the run completes successfully, the restart log file is -deleted. If however the workflow fails, swift -can use the restart log file to continue -execution from a point before the -failure occurred. In order to restart from a restart log -file, the argument can be -used after the SwiftScript program file name. Example: - - -$ swift . - - - -
    - -
    Replication - -When an execution job has been waiting in a site queue for a certain -period of time, Swift can resubmit replicas of that job (up to the limit -defined in the replication.limit configuration property). -When any of those jobs moves from queued to active state, all of the -other replicas will be cancelled. - - -This is intended to deal with situations where some sites have a substantially -longer (sometimes effectively infinite) queue time than other sites. -Selecting those slower sites can cause a very large delay in overall run time. - - -Replication can be enabled by setting the -replication.enabled configuration property to -true. The maximum number of replicas that will be -submitted for a job is controlled by the replication.limit -configuration property. - - -When replication is enabled, Swift will also enforce the -maxwalltime profile setting for jobs as documented in -the profiles section. - -
    - -
    - -
    Clustering - -Swift can group a number of short job submissions into a single larger -job submission to minimize overhead involved in launching jobs (for example, -caused by security negotiation and queuing delay). In general, -CoG coasters should be used in preference -to the clustering mechanism documented in this section. - - - -By default, clustering is disabled. It can be activated by setting the -clustering.enabled -property to true. - - - -A job is eligible for clustering if -the GLOBUS::maxwalltime profile is specified in the tc.data entry for that job, and its value is -less than the value of the -clustering.min.time -property. - - - -Two or more jobs are considered compatible if they share the same site -and do not have conflicting profiles (e.g. different values for the same -environment variable). - - - -When a submitted job is eligible for clustering, -it will be put in a clustering queue rather than being submitted to -a remote site. The clustering queue is processed at intervals -specified by the -clustering.queue.delay -property. The processing of the clustering queue consists of selecting -compatible jobs and grouping them into clusters whose maximum wall time does -not exceed twice the value of the clustering.min.time -property. - - - -
    - - - -
    Coasters -Coasters were introduced in Swift v0.6 as an experimental feature. - - -In many applications, Swift performance can be greatly enhanced by the -use of CoG coasters. CoG coasters provide a low-overhead job submission -and file transfer mechanism suited for the execution of short jobs -(on the order of a few seconds) and the transfer of small files (on the -order of a few kilobytes) for which other grid protocols such as GRAM -and GridFTP are poorly suited. - - -The coaster mechanism submits a head job using some other execution -mechanism such as GRAM, and for each worker node that will be used in -a remote cluster, it submits a worker job, again using some other -execution mechanism such as GRAM. Details on the design of the coaster -mechanism can be found - -here. - - -The head job manages file transfers and the dispatch of execution jobs -to workers. Much of the overhead associated with other grid protocols -(such as authentication and authorization, and allocation of worker nodes -by the site's local resource manager) is reduced, because that overhead -is associated with the allocation of a coaster head or coaster worker, -rather than with every Swift-level procedure invocation; potentially hundreds -or thousands of Swift-level procedure invocations can be run through a single -worker. - - -Coasters can be configured for use in two situations: job execution and -file transfer. - - -To use for job execution, specify a sites.xml execution element like this: - -<execution provider="coaster" jobmanager="gt2:gt2:pbs" url="grid.myhost.org"> - -The jobmanager string contains more detail than with other providers. It -contains either two or three colon separated fields: -1:the provider to be use to execute the coaster head job - this provider -will submit from the Swift client side environment. Commonly this will be -one of the GRAM providers; 2: the provider -to be used to execute coaster worker jobs. This provider will be used -to submit from the coaster head job environment, so a local scheduler -provider can sometimes be used instead of GRAM. 3: optionally, the -jobmanager to be used when submitting worker job using the provider -specified in field 2. - - -To use for file transfer, specify a sites.xml filesystem element like this: - -<filesystem provider="coaster" url="gt2://grid.myhost.org" /> - -The url parameter should be a pseudo-URI formed with the URI scheme being -the name of the provider to use to submit the coaster head job, and the -hostname portion being the hostname to be used to execute the coaster -head job. Note that this provider and hostname will be used for execution -of a coaster head job, not for file transfer; so for example, a GRAM -endpoint should be specified here rather than a GridFTP endpoint. - - -Coasters are affected by the following profile settings, which are -documented in the Globus namespace profile -section: - - - - - profile keybrief description - - slotsHow many maximum LRM jobs/worker blocks are allowed - jobsPerNodeHow many coaster workers to run per execution node - nodeGranularityEach worker block uses a number of nodes that is a multiple of this number - lowOverallocationHow many times larger than the job walltime should a block's walltime be if all jobs are 1s long - highOverallocationHow many times larger than the job walltime should a block's walltime be if all jobs are infinitely long - overallocationDecayFactorHow quickly should the overallocation curve tend towards the highOverallocation as job walltimes get larger - spreadBy how much should worker blocks vary in worker size - jobsPerNodeHow many coaster workers to run per execution node - reserveHow many seconds to reserve in a block's walltime for starting/shutdown operations - maxnodesThe maximum number of nodes allowed in a block - maxtimeThe maximum number of walltime allowed for a block - remoteMonitorEnabledIf true, show a graphical display of the status of the coaster service - - -
    -
    -
    How-To Tips for Specific User Communities -
    Saving Logs - for UChicago CI Users - -If you have a UChicago Computation Institute account, run this command in your -submit directory after each run. It will copy all your logs and kickstart -records into a directory at the CI for reporting, usage tracking, support and debugging. - - - -rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose - - -
    -
    Specifying TeraGrid allocations -TeraGrid users with no default project or with several project -allocations can specify a project allocation using a profile key in -the site catalog entry for a TeraGrid site: - -<profile namespace="globus" key="project">TG-CCR080002N</profile> - - - - -More information on the TeraGrid allocations process can -be found here. - - -
    -
    Launching MPI jobs from Swift - -Here is an example of running a simple MPI program. - - -In SwiftScript, we make an invocation that does not look any different -from any other invocation. In the below code, we do not have any input -files, and have two output files on stdout and stderr: - -type file; - -(file o, file e) p() { - app { - mpi stdout=@filename(o) stderr=@filename(e); - } -} - -file mpiout <"mpi.out">; -file mpierr <"mpi.err">; - -(mpiout, mpierr) = p(); - - - -Now we define how 'mpi' will run in tc.data: - -tguc mpi /home/benc/mpi/mpi.sh INSTALLED INTEL32::LINUX GLOBUS::host_xcount=3 - - - -mpi.sh is a wrapper script that launches the MPI program. It must be installed -on the remote site: - -#!/bin/bash -mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out - - - -Because of the way that Swift runs its server side code, provider-specific -MPI modes (such as GRAM jobType=mpi) should not be used. Instead, the -mpirun command should be explicitly invoked. - -
    -
    Running on Windows - - - Since 10/11/09, the development version of Swift has the -ability to run on a Windows machine, as well as the ability to submit -jobs to a Windows site (provided that an appropriate provider is used). - - - - -In order to launch Swift on Windows, use the provided batch file -(swift.bat). In certain cases, when a large number of jar libraries are -present in the Swift lib directory and depending on the exact location -of the Swift installation, the classpath environment variable that the -Swift batch launcher tries to create may be larger than what Windows can -handle. In such a case, either install Swift in a directory closer to -the root of the disk (say, c:\swift) or remove non-essential jar files -from the Swift lib directory. - - - - - -Due to the large differences between Windows and Unix environments, -Swift must use environment specific tools to achieve some of its goals. -In particular, each Swift executable is launched using a wrapper script. -This script is a Bourne Shell script. On Windows machines, which have no -Bourne Shell interpreter installed by default, the Windows Scripting -Host is used instead, and the wrapper script is written in VBScript. -Similarly, when cleaning up after a run, the "/bin/rm" command available -in typical Unix environments must be replaced by the "del" shell command. - - - - - -It is important to note that in order to select the proper set of tools -to use, Swift must know when a site runs under Windows. To inform Swift -of this, specify the "sysinfo" attribute for the "pool" element in the -site catalog. For example: - - - <pool handle="localhost" sysinfo="INTEL32::WINDOWS"> - ... - </pool> - - - -
    -
    - -
    - Collective Data Management - - - -CDM Features - -Overview: - - 1. The user specifies a CDM policy in a file, customarily fs.data. - 2. fs.data is given to Swift on the command line. - 3. The Swift data module (org.globus.swift.data) is informed of the CDM policy. - 4. At job launch time, the VDL Karajan code queries the CDM policy, - 1. altering the file staging phase, and - 2. sending fs.data to the compute site. - 5. At job run time, the Swift wrapper script - 1. consults a Perl script to obtain policy, and - 2. uses wrapper extensions to modify data movement. - 6. Similarly, stage out can be changed. - - -Command line: - - * swift -sites.file sites.xml -tc.file tc.data -cdm.file fs.data stream.swift - - -CDM policy file format: - -Example: - -# Describe CDM for my job -property GATHER_LIMIT 1 -rule .*input.txt DIRECT /gpfs/homes/wozniak/data -rule .*xfile*.data BROADCAST /dev/shm -rule .* DEFAULT - -The lines contain: - - 1. A directive, either rule or property - 2. A rule has: - 1. A regular expression - 2. A policy token - 3. Additional policy-specific arguments - 3. A property has - 1. A policy property token - 2. The token value - 4. Comments with # . - 5. Blank lines are ignored. - - -Notes: - - 1. The policy file is used as a lookup database by Swift and Perl methods. - 2. For example, a lookup with the database above given the argument input.txt would result in the Direct policy. - 3. If the lookup does not succeed, the result is DEFAULT. - 4. Policies are listed as subclasses of org.globus.swift.data.policy.Policy . - - -Policy Descriptions: - -Default: - - * Just use file staging as provided by Swift/CoG. Identical to behavior if no CDM file is given. - - -Broadcast: - - rule .*xfile*.data BROADCAST /dev/shm - - * The input files matching the pattern will be stored in the given directory, an LFS location, with links in the job directory. - * On the BG/P, this will make use of the f2cn tool. - * On machines not implementing an efficient broadcast, we will just ensure correctness. For example, on a workstation, the location could be in a /tmp RAM FS. - - -Direct: - - rule .*input.txt DIRECT /gpfs/scratch/wozniak/ - - * Allows for direct I/O to the parallel FS without staging. - * The input files matching the pattern must already exist in the given directory, a GFS location. Links will be placed in the job directory. - * The output files matching the pattern will be stored in the given directory, with links in the job directory. - * Example: In the rule above, the Swift-generated file name ./data/input.txt would be accessed by the user job in /gpfs/homes/wozniak/data/input.txt . - - -Local: - - rule .*input.txt LOCAL dd /gpfs/homes/wozniak/data obs=64K - - * Allows for client-directed input copy to the compute node. - * The user may specify cp or dd as the input transfer program. - - * The input files matching the pattern must already exist in the given directory, a GFS location. Copies will be placed in the job directory. - * Argument list: [tool] [GFS directory] [tool arguments]* - - -Gather: - - property GATHER_LIMIT 500000000 # 500 MB - property GATHER_DIR /dev/shm/gather - property GATHER_TARGET /gpfs/wozniak/data/gather_target - rule .*.output.txt GATHER - - * The output files matching the pattern will be present to tasks in the job directory as usual but noted in a _swiftwrap shell array GATHER_OUTPUT. - * The GATHER_OUTPUT files will be cached in the GATHER_DIR, an LFS location. - * The cache will be flushed when a job ends if a du on GATHER_DIR exceeds GATHER_LIMIT. - * As the cache fills or on stage out, the files will be bundled into randomly named tarballs in GATHER_TARGET, a GFS location. - * If the compute node is an SMP, GATHER_DIR is a shared resource. It is protected by the link file GATHER_DIR/.cdm.lock . - * Unpacking the tarballs in GATHER_TARGET will produce the user-specified filenames. - - Summary: - - 1. Files created by application - 2. Acquire lock - 3. Move files to cache - 4. Check cache size - 5. If limit exceeded, move all cache files to outbox - 6. Release lock - 7. If limit was exceeded, stream outbox as tarball to target - - - Notes: - - * Gather required quite a bit of shell functionality to manage the lock, etc. This is placed in cdm_lib.sh . - * vdl_int.k needed an additional task submission (cdm_cleanup.sh) to perform the final flush at workflow completion time . This task also uses cdm_lib.sh . - - -VDL/Karajan processing: - - 1. CDM functions are available in Karajan via the cdm namespace. - 2. These functions are defined in org.globus.swift.data.Query . - 3. If CDM is enabled, VDL skips file staging for files unless the policy is DEFAULT. - - -Swift wrapper CDM routines: - - 1. The cdm.pl script is shipped to the compute node if CDM is enabled. - 2. When linking in inputs, CDM is consulted by _swiftwrap:cdm_lookup(). - 3. The cdm_action() shell function handles CDM methods, typically just producing a link. - - -Test case: - -(See About.txt for more information.) - - 1. Simple test cases are in: - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts/cdm-direct and - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts/all-pairs - 2. Do a: - mkdir cdm - cd cdm - svn co https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/scripts - 3. In cdm-direct, run: - source ./setup.sh local local local - 4. Run workflow: - swift -sites.file sites.xml -tc.file tc.data -cdm.file fs.data stream.swift - 5. Note that staging is skipped for input.txt - policy: file://localhost/input.txt : DIRECT - FILE_STAGE_IN_START file=input.txt ... - FILE_STAGE_IN_SKIP file=input.txt policy=DIRECT - FILE_STAGE_IN_END file=input.txt ... - 6. In the wrapper output, the input file is handled by CDM functionality: - Progress 2010-01-21 13:50:32.466572727-0600 LINK_INPUTS - CDM_POLICY: DIRECT /homes/wozniak/cdm/scripts/cdm-direct - CDM: jobs/t/cp_sh-tkul4nmj input.txt DIRECT /homes/wozniak/cdm/scripts/cdm-direct - CDM[DIRECT]: Linking jobs/t/cp_sh-tkul4nmj/input.txt to /homes/wozniak/cdm/scripts/cdm-direct/input.txt - Progress 2010-01-21 13:50:32.486016708-0600 EXECUTE - 7. all-pairs is quite similar but uses more policies. - - -PTMap case: - - 1. Start with vanilla PTMap: - cd cdm - mkdir apps - cd apps - https://svn.mcs.anl.gov/repos/wozniak/collab/cdm/apps/ptmap - 2. Source setup.sh - 3. Use start.sh, which - 1. applies CDM policy from fs.local.data - - -CDM site-aware policy file format: - -Example: - -# Describe CDM for my job -# Use DIRECT and BROADCAST if on cluster1, else use DEFAULT behavior -property GATHER_LIMIT 1 -rule cluster1 .*input.txt DIRECT /gpfs/homes/wozniak/data -rule cluster1 .*xfile*.data BROADCAST /dev/shm -rule ANYWHERE .* DEFAULT - -The lines contain: - - 1. A directive, either rule or property - 2. A rule has: - 1. A regular expression for site matchin - 2. A regular expression for filename matching - 3. A policy token - 4. Additional policy-specific arguments - 3. A property has - 1. A policy property token - 2. The token value - 4. Comments with # . - 5. Blank lines are ignored. - - - -
    -
    - From davidk at ci.uchicago.edu Tue May 17 10:30:44 2011 From: davidk at ci.uchicago.edu (davidk at ci.uchicago.edu) Date: Tue, 17 May 2011 15:30:44 -0000 Subject: [Swift-commit] r4483 - in trunk: . docs docs/cookbook docs/tutorial docs/userguide Message-ID: <20110517153042.D75039CD2E@svn.ci.uchicago.edu> Author: davidk Date: 2011-05-17 10:30:41 -0500 (Tue, 17 May 2011) New Revision: 4483 Added: trunk/docs/userguide/userguide-rotated.jpg trunk/docs/userguide/userguide-shane.jpg Removed: trunk/docs/cookbook/cookbook-asciidoc.html trunk/docs/cookbook/cookbook-asciidoc.pdf trunk/docs/tutorial/tutorial.html trunk/docs/userguide/userguide.html Modified: trunk/build.xml trunk/docs/build_docs.sh trunk/docs/tutorial/tutorial.pdf trunk/docs/tutorial/tutorial.txt trunk/docs/userguide/userguide.txt Log: Updates for doc build scripts and guides Modified: trunk/build.xml =================================================================== --- trunk/build.xml 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/build.xml 2011-05-17 15:30:41 UTC (rev 4483) @@ -55,8 +55,6 @@ fixeol: change newlines to the unix standard. - docs: - Build Swift documentation from asciidoc txt files @@ -261,18 +259,7 @@ - - - - - - - - - - - Modified: trunk/docs/build_docs.sh =================================================================== --- trunk/docs/build_docs.sh 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/build_docs.sh 2011-05-17 15:30:41 UTC (rev 4483) @@ -1,23 +1,36 @@ #!/bin/bash +# crash: Report a problem and exit +crash() +{ + MSG=$1 + echo ${MSG} >&2 + exit 1 +} + +# Verify correct arguments if [ -n "$1" ]; then INSTALLATION_DIRECTORY=$1 else - echo Error: Must specify a directory for installation - exit 1 + crash "Error: Must specify a directory for installation" fi +# Create installation directory if needed if [ ! -d "$INSTALLATION_DIRECTORY" ]; then - mkdir $INSTALLATION_DIRECTORY || exit 1 + mkdir $INSTALLATION_DIRECTORY || crash "Unable to create directory $INSTALLATION_DIRECTORY" fi +# Gather version information +pushd .. > /dev/null 2>&1 +VERSION=`svn info |grep URL|awk -F / '{print $NF}'` +popd > /dev/null 2>&1 echo Installing docs into $INSTALLATION_DIRECTORY -cd docs || exit 1 +# Convert files DIRECTORIES=*/ for directory in $DIRECTORIES do - cd $directory || exit 1 + pushd $directory > /dev/null 2>&1 FILES=*.txt for file in $FILES do @@ -26,8 +39,15 @@ echo Converting $directory"$file" to PDF a2x --format=pdf --no-xmllint $file done - cp *.html $INSTALLATION_DIRECTORY || exit 1 - cp *.pdf $INSTALLATION_DIRECTORY || exit 1 - cd .. || exit 1 + + if [ ! -d "$INSTALLATION_DIRECTORY/$VERSION" ]; then + mkdir $INSTALLATION_DIRECTORY/$VERSION || crash "Unable to create directory $INSTALLATION_DIRECTORY/$VERSION" + fi + + if [ ! -d "$INSTALLATION_DIRECTORY/$VERSION/$directory" ]; then + mkdir $INSTALLATION_DIRECTORY/$VERSION/$directory || crash "Unable to create directory $INSTALLATION_DIRECTORY/$VERSION/$directory" + fi + cp *.html $INSTALLATION_DIRECTORY/$VERSION/$directory || crash "Unable to copy html files to $INSTALLATION_DIRECTORY/$VERSION/$directory" + cp *.pdf $INSTALLATION_DIRECTORY/$VERSION/$directory || crash "Unable to copy pdf files to $INSTALLATION_DIRECTORY/$VERSION/$directory" + popd > /dev/null 2>&1 done -cd .. Deleted: trunk/docs/cookbook/cookbook-asciidoc.html =================================================================== --- trunk/docs/cookbook/cookbook-asciidoc.html 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/cookbook/cookbook-asciidoc.html 2011-05-17 15:30:41 UTC (rev 4483) @@ -1,1497 +0,0 @@ - - - - - -Swift Cookbook - - - - - -
    -
    -

    Overview

    -
    -

    This cookbook covers various recipes involving setting up and running Swift under diverse -configurations based on the application requirements and the underlying -infrastructures. The Swift system comprises of SwiftScript language and the -Swift runtime system. For -introductory material, consult the Swift tutorial found -here.

    -
    -
    -
    -

    Swift Basics

    -
    -
    -

    Installation

    -

    This section takes you through the installation of the Swift system on your -computer. We will start with the prerequisites as explained in the subsequent -section.

    -
    -

    Prerequisites

    -
    Check your Java

    Swift is a Java application. Make sure you are running Java version 5 or higher. You -can make sure you have Java in your $PATH (or $HOME/.soft file depending upon -your environment)

    -

    Following are the possible ways to detect and run Java:

    -
    -
    -
    $ grep java $HOME/.soft
    -#+java-sun # Gives you Java 5
    -+java-1.6.0_03-sun-r1
    -$ which java
    -/soft/java-1.6.0_11-sun-r1/bin/java
    -$ java -version
    -java version "1.6.0_11"
    -Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
    -Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
    -
    -
    -
    -
    -

    Setting up to run Swift

    -

    This is simple. We will be using a pre-compiled version of Swift that can be -downloaded from here. Download and untar the latest precompiled version as follows:

    -
    -
    -
    $ tar xf swift-0.92.1.tar.gz
    -
    -
    -

    Environment Setup

    -

    The examples were tested with Java version 1.6. Make sure you do not already -have Swift in your PATH. If you do, remove it, or remove any +swift or @swift -lines from your $HOME/.soft or $HOME/.bash_profile file. Then do:

    -
    -
    -
    PATH=$PATH:/path/to/swift/bin
    -
    -

    Note that the environment will be different when using Swift from prebuilt distribution (as above) and trunk. The PATH setup when using swift from trunk would be as follows:

    -
    -
    -
    PATH=$PATH:/path/to/swift/dist/swift-svn/bin
    -
    -
    - - - -
    -
    Warning
    -
    Do NOT set SWIFT_HOME or CLASSPATH in your environment unless you -fully understand how these will affect Swift’s execution.
    -
    -

    To execute your Swift script on a login host (or "localhost") use -the following command:

    -
    -
    -
    swift -tc.file tc somescript.swift
    -
    -
    -
    -

    Setting transformation catalog

    -

    The transformation catalog lists where application executables are located on -remote sites.

    -

    By default, the site catalog is stored in etc/tc.data. This path can be -overridden with the tc.file configuration property, either in the Swift -configuration file or on the command line.

    -

    The format is one line per executable per site, with fields separated by tabs -or spaces.

    -

    Some example entries:

    -
    -
    -
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    -TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX GLOBUS::maxwalltime="00:00:10"
    -
    -

    The fields are: site, transformation-name, executable-path, installation-status, platform, and profile entries.

    -

    The site field should correspond to a site name listed in the sites catalog.

    -

    The transformation-name should correspond to the transformation name used in a -SwiftScript app procedure.

    -

    The executable-path should specify where the particular executable is located -on that site.

    -

    The installation-status and platform fields are not used. Set them to -INSTALLED and INTEL32::LINUX respectively.

    -

    The profiles field should be set to null if no profile entries are to be -specified, or should contain the profile entries separated by semicolons.

    -
    -
    -

    Setting swift configuration

    -

    Many configuration properties could be set using the Swift configuration file. -We will not cover them all in this section. see -here for details. In this section we will cover a simple configuration file with the most basic properties.

    -
    -
    -
    # A comment
    -wrapperlog.always.transfer=true
    -sitedir.keep=true
    -execution.retries=1
    -lazy.errors=true
    -status.mode=provider
    -use.provider.staging=true
    -provider.staging.pin.swiftfiles=false
    -clustering.enabled=false
    -clustering.queue.delay=10
    -clustering.min.time=86400
    -foreach.max.threads=100
    -provenance.log=true
    -
    -
    -
    -

    Setting sites.xml

    -

    sites.xml specifies details of the sites that Swift can run on. Following is -an example of a simple sites.xml file entry for running Swift on local -environment:

    -
    -
    -
    <pool handle="localhost">
    -<filesystem provider="local" />
    -<execution provider="local" />
    -<workdirectory >/var/tmp</workdirectory>
    -<profile namespace="karajan" key="jobThrottle">.07</profile>
    -<profile namespace="karajan"
    -key="initialScore">100000</profile>
    -</pool>
    -
    -
    -
    -

    First SwiftScript

    -

    Your first SwiftScript -Hello Swift-World!

    -

    A good sanity check that Swift is set up and running OK locally is this:

    -
    -
    -
    $ which swift
    -
    -/home/wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift
    -
    -$ echo 'trace("Hello, Swift world!");' >hello.swift
    -
    -$ swift hello.swift
    -
    -Swift svn swift-r3202 cog-r2682
    -
    -RunID: 20100115-1240-6xhzxuz3
    -
    -Progress:
    -
    -SwiftScript trace: Hello, Swift world!
    -
    -Final status:
    -
    -$
    -
    -

    A good first tutorial in using Swift is at: -http://www.ci.uchicago.edu/swift/guides/tutorial.php. Follow the steps in that -tutorial to learn how to run a few simple scripts on the login host.

    -
    -
    -

    second SwiftScript

    -

    Following is a more involved Swift script.

    -
    -
    -
    type file;
    -
    -app (file o) cat (file i)
    -{
    -    cat @i stdout=@o;
    -}
    -
    -file out[]<simple_mapper; location="outdir", prefix="f.",suffix=".out">;
    -
    -foreach j in [1:@toint(@arg("n","1"))] {
    -
    -    file data<"data.txt">;
    -
    -    out[j] = cat(data);
    -}
    -
    -
    -

    Swift Commandline Options

    -

    A description of Swift Commandline Options

    -

    Also includes a description of Swift inputs and outputs.

    -
    -
    -

    What if Swift hangs

    -

    Owing to its highly multithreaded architecture it is often the case that the -underlying java virtual machine gets into deadlock situations or Swift hangs -because of other complications in its threaded operations. Under such -situations, Swift hang-checker chips in and resolves the situation.

    -
      -
    1. -

      -how to use the information to identify and correct the deadlock. -

      -
    2. -
    3. -

      -How close to the Swift source code can we make the hang-checker messages, so that the user can relate it to Swift functions, expressions, and ideally source code lines? -

      -
    4. -
    5. -

      -The current Hang Checker output is actually very nice and useful already: -

      -
    6. -
    -
    -
    -
    Registered futures:
    -Rupture[] rups  Closed, 1 elements, 0 listeners
    -Variation vars - Closed, no listeners
    -SgtDim sub - Open, 1 listeners
    -string site  Closed, no listeners
    -Variation[] vars  Closed, 72 elements, 0 listeners
    -
    -
    -
    -

    Resuming a stopped or crashed Swift Run

    -

    I had a .rlog file from a Swift run that ran out of time. I kicked it off -using the -resume flag described in section 16.2 of the Swift User Guide and -it picked up where it left off. Then I killed it because I wanted to make -changes to my sites file.

    -
    -
    -
    . . .
    -Progress:  Selecting site:1150  Stage in:55  Active:3  Checking status:1
    -Stage out:37  Finished in previous run:2462  Finished successfully:96
    -Progress:  Selecting site:1150  Stage in:55  Active:2  Checking status:1
    -Stage out:38  Finished in previous run:2462  Finished successfully:96
    -Cleaning up...
    -Shutting down service at https://192.5.86.6:54813
    -Got channel MetaChannel: 1293358091 -> null
    -+ Done
    -Canceling job 9297.svc.pads.ci.uchicago.edu
    -
    -

    No new rlog file was emitted but it did recognize the progress that had been -made, the 96 tasks that finished sucessfully above and resumed from 2558 tasks -finished.

    -
    -
    -
    [nbest at login2 files]$ pwd
    -/home/nbest/bigdata/files
    -[nbest at login2 files]$
    -~wilde/swift/src/stable/cog/modules/swift/dist/swift-svn/bin/swift \
    -> -tc.file tc -sites.file pbs.xml ~/scripts/mcd12q1.swift -resume
    -> mcd12q1-20100310-1326-ptxe1x1d.0.rlog
    -Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    -locally)
    -RunID: 20100311-1027-148caf0a
    -Progress:
    -Progress:  uninitialized:4
    -Progress:  Selecting site:671  Initializing site shared directory:1  Finished
    -in previous run:1864
    -Progress:  uninitialized:1  Selecting site:576  Stage in:96  Finished in
    -previous run:1864
    -Progress:  Selecting site:1150  Stage in:94  Submitting:2  Finished in
    -previous run:2558
    -Progress:  Selecting site:1150  Stage in:94  Submitted:2  Finished in previous
    -run:2558
    -Progress:  Selecting site:1150  Stage in:93  Submitting:1  Submitted:2
    -Finished in previous run:2558
    -Progress:  Selecting site:1150  Stage in:90  Submitting:1  Submitted:5
    -Finished in previous run:2558
    -Progress:  Selecting site:1150  Stage in:90  Submitted:5  Active:1  Finished
    -in previous run:2558
    -
    -

    From Neil: A comment about that section of the user guide: It says "In order -to restart from a restart log file, the -resume logfile argument can be used -after the SwiftScript? program file name." and then puts the -resume logfile -argument before the script file name. I’m sure the order doesn’t matter but -the contradiction is confusing.

    -

    Notes to add (from Mike):

    -
      -
    • -

      -explain what aspects of a Swift script make it restartable, and which - aspects are notrestartable. Eg, if your mappers can return different data at -different times, what happens? What other non-determinsitc behavior would -cause unpredictable, unexpected, or undesired behavior on resumption? -

      -
    • -
    • -

      -explain what changes you can make in the execution environment (eg - increasing or reducing CPUs to run on or throttles, etc); fixing tc.data -entries, env vars, or apps, etc. -

      -
    • -
    • -

      -note that resume will again retry failed app() calls. Explain if the retry - count starts over or not. -

      -
    • -
    • -

      -explain how to resume after multiple failures and resumes - i.e. if a .rlog - is generated on each run, which one should you resume from? Do you have a -choice of resuming from any of them, and what happens if you go backwards to -an older resume file? -

      -
    • -
    • -

      -whap happens when you kill (eg with C) a running swift script? Is the - signal caught, and the resume file written out at that point? Or written out -all along? (Note case in which script ws running for hours, then hit C, but -resume fie was short (54 bbytes) and swift shows no sign of doing a resume? -(It silently ignored resume file instead of acknowleging that it found one -with not useful resume state in it???) Swift should clearly state that its -resuming and what its resume state is. -

      -
    • -
    -

    swift -resume ftdock-[id].0.rlog \[rest of the exact command line from initial -run\]

    -
    -
    -

    Passing an array to swift?

    -

    Arrays can be passed to Swift in one of the following ways:

    -
      -
    1. -

      -You can write the array to a file and read in in swift using -readData (or readData2). -

      -
    2. -
    3. -

      -Direct the array into a file (possibly with a "here document" which expands the array) and then read the file in Swift with readData() or process it with a Swift app() function? -

      -
    4. -
    5. -

      -You can use @strsplit on a comma separated command line arg and that works well for me. -

      -
    6. -
    -
    -

    Mappers

    -

    SimpleMapper

    -
    -
    -
    $ cat swiftapply.swift
    -
    -
    -
    -
    type RFile;
    -trace("hi 1");
    -app (RFile result) RunR (RFile rcall)
    -{
    -  RunR @rcall @result;
    -}
    -trace("hi 2");
    -RFile rcalls[] ;
    -RFile results[] ;
    -trace("start");
    -foreach c, i in rcalls {
    -  trace("c",i,@c);
    -  trace("r",i,@filename(results[i]));
    -  results[i] = RunR(c);
    -}
    -
    -
    -
    $ ls calldir resdir
    -calldir:
    -rcall.1.Rdata  rcall.2.Rdata  rcall.3.Rdata  rcall.4.Rdata
    -resdir:
    -result.1.Rdata result.2.Rdata result.3.Rdata result.4.Rdata
    -$
    -
    -

    Notes:

    -

    how the .'s match -prefix and suffix dont span dirs -intervening pattern must be digits -these digits become the array indices -explain how padding= arg works & helps (including padding=0) -figure out and explain differences between simple_mapper and -filesys_mapper -FIXME: Use the "filesys_mapper" and its "location=" parameter to map the -input data from /home/wilde/bigdata/*

    -

    Abbreviations for SingleFileMapper -Notes:

    -

    within <> you can only have a literal string as in <"filename">, not an -expression. Someday we will fix this to make <> accept a general expression. -you can use @filenames( ) (note: plural) to pull off a list of filenames.

    -

    writeData()

    -

    example here

    -
    -
    -
    $ cat writedata.swift
    -
    -
    -
    -
    type file;
    -
    -file f <"filea">;
    -file nf <"filenames">;
    -nf = writeData(@f);
    -
    -
    -
    $ swift writedata.swift
    -Swift svn swift-r3264 (swift modified locally) cog-r2730 (cog modified
    -locally)
    -RunID: 20100319-2002-s9vpo0pe
    -Progress:
    -Final status:
    -$ cat filenames
    -filea$
    -
    -

    StructuredRegexpMapper -IN PROGRESS This mapper can be used to base the mapped filenames of an output -array on the mapped filenames of an existing array. landuse outputfiles[] -<structured_regexp_mapper; source=inputfiles, -location="./output",match="(.)*tif", transform="\\1histogram">;

    -

    Use the undocumented "structured_regexp_mapper" to name the output -filenames based on the input filenames:

    -

    For example:

    -
    -
    -
    login2$ ls /home/wilde/bigdata/data/sample
    -h11v04.histogram  h11v05.histogram  h12v04.histogram  h32v08.histogram
    -h11v04.tif        h11v05.tif        h12v04.tif        h32v08.tif
    -login2$
    -
    -login2$ cat regexp2.swift
    -type tif;
    -type mytype;
    -
    -tif  images[]<filesys_mapper;
    -location="/home/wilde/bigdata/data/sample", prefix="h", suffix=".tif">;
    -
    -mytype of[] <structured_regexp_mapper; source=images, match="(h..v..)",
    -transform="output/myfile.\\1.mytype">;
    -
    -foreach image, i in images {
    -   trace(i, at filename(images));
    -   trace(i, at filename(of[i]));
    -}
    -login2$
    -
    -login1$ swift regexp2.swift
    -Swift svn swift-r3255 (swift modified locally) cog-r2723 (cog modified
    -locally)
    -
    -RunID: 20100310-1105-4okarq08
    -Progress:
    -SwiftScript trace: 1, output/myfile.h11v04.mytype
    -SwiftScript trace: 2, home/wilde/bigdata/data/sample/h11v05.tif
    -SwiftScript trace: 3, home/wilde/bigdata/data/sample/h12v04.tif
    -SwiftScript trace: 0, output/myfile.h32v08.mytype
    -SwiftScript trace: 0, home/wilde/bigdata/data/sample/h32v08.tif
    -SwiftScript trace: 3, output/myfile.h12v04.mytype
    -SwiftScript trace: 1, home/wilde/bigdata/data/sample/h11v04.tif
    -SwiftScript trace: 2, output/myfile.h11v05.mytype
    -Final status:
    -login1$
    -
    -
    -
    -
    -
    -
    -

    Coasters

    -
    -

    Coasters were introduced in Swift v0.6 as an experimental feature. In many -applications, Swift performance can be greatly enhanced by the use of CoG -coasters. CoG coasters provide a low-overhead job submission and file transfer -mechanism suited for the execution of short jobs (on the order of a few -seconds). A detailed information on coasters can be found at http://www.ci.uchicago.edu/swift/guides/userguide.php#coasters.

    -

    Following is a coasters setup case-study for a PBS underlying provider where sites.xml coaster settings were:

    -
    -
    -
    <execution provider="coaster" jobmanager="local:pbs"/>
    -<profile namespace="globus" key="project">CI-CCR000013</profile>
    -
    -<!-- Note that the following is going to be defunct in the new version (0.93+) and replaced by
    -"ProviderAttributes" key and may not work in the future Swift versions-->
    -
    -<!--<profile namespace="globus" key="ppn">24:cray:pack</profile>-->
    -
    -<profile namespace="globus" key="providerAttributes">
    -pbs.aprun
    -pbs.mpp=true
    -</profile>
    -
    -<profile namespace="globus" key="workersPerNode">24</profile>
    -<profile namespace="globus" key="maxTime">100000</profile>
    -
    -<profile namespace="globus" key="lowOverallocation">100</profile>
    -<profile namespace="globus" key="highOverallocation">100</profile>
    -
    -<profile namespace="globus" key="slots">20</profile>
    -<profile namespace="globus" key="nodeGranularity">5</profile>
    -<profile namespace="globus" key="maxNodes">5</profile>
    -<profile namespace="karajan" key="jobThrottle">20.00</profile>
    -<profile namespace="karajan" key="initialScore">10000</profile>
    -

    The following table briefly describes the elements on the coasters setup:

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    profile key brief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a block’s walltime be if all jobs are infinitely long

    workersPerNode

    How many coaster workers to run per execution node reserve How many seconds to reserve in a block’s walltime for starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block coaster service

    jobThrottle

    the number of concurrent jobs allowed on a site

    -
    -
    -

    For Advanced Users

    -

    One of the main reason that one would initially deviate from coaster -defaults into more complex pool entries is to force jobs to fit into some -site-imposed constraint. For instance a typical submission to the experimental -queue requires a user to request upto 3 nodes for under 1 hour. This setup -could be achieved with a careful tuning of coaters parameters.

    -
    -
    -

    Coaster providers: local, ssh, pbs

    -

    Settings and examples for different coaster providers mechanisms.

    -
    -
    -
    -
    -

    Swift on Diverse Infrastructures

    -
    -
    -

    Beagle

    -

    Swift is now installed on Beagle as a module. Swift supports a Coasters based, -computing environment for Beagle. A detailed Swift documentation is maintained -[[here]. To get started -with Swift on Beagle follow the steps outlined below:

    -

    step 1. Load the Swift module on Beagle as follows: module load swift

    -

    step 2. Create and change to a directory where your Swift related work will -stay. (say, mkdir swift-lab, followed by, cd swift-lab)

    -

    step 3. To get started with a simple example running /bin/cat to read an input file data.txt and write to an output file f.nnn.out, copy the folder at /home/ketan/labs/catsn to the above directory. (cp -r /home/ketan/catsn . followed by cd catsn).

    -

    step 4. In the sites file: beagle-coaster.xml, make the following two -changes: 1) change the path of workdirectory to your preferred location -(say to /lustre/beagle/$USER/swift-lab/swift.workdir) and 2) Change the -project name to your project (CI-CCR000013) . The workdirectory will contain -execution data related to each run, e.g. wrapper scripts, system information, -inputs and outputs.

    -

    step 5. Run the example using following commandline (also found in run.sh): -swift -config cf -tc.file tc -sites.file beagle-coaster.xml catsn.swift -n=1 -. You can further change the value of -n to any arbitrary number to run that -many number of concurrent cat

    -

    step 6. Check the output in the generated outdir directory (ls outdir)

    -

    Note: Running from sandbox node or requesting 1 hour walltime for upto 3 nodes -will get fast prioritized execution. Good for small tests

    -
    -
    -

    PADS

    -

    Swift on PADS -To execute your Swift script on the PADS cluster use this command:

    -
    -
    -
    swift -tc.file tc -sites.file pbs.xml modis.swift
    -
    -

    where the contents of a simple pbs.xml sites file could be:

    -
    -
    -
    <config>
    -  <pool handle="pbs">
    -    <execution provider="pbs" url="none"/>
    -    <profile namespace="globus" key="queue">fast</profile>
    -    <profile namespace="globus" key="maxwalltime">00:05:00</profile>
    -    <profile namespace="karajan" key="initialScore">10000</profile>
    -    <profile namespace="karajan" key="jobThrottle">.10</profile>
    -    <filesystem provider="local"/>
    -    <workdirectory >/home/you/swiftwork</workdirectory>
    -  </pool>
    -</config>
    -
    -
    -

    OSG

    -

    This section describes how to get Swift running on the OSG Grid. We will use a -manual coaster setup to get Swift running on OSG.

    -
    Coaster setup on OSG

    The following figure shows an abstract scheme for the manual coasters setup on -OSG.

    -
    -
    -Coaster setup -
    -
    -

    In the following steps, we will go through the process of manually setting

    -
    -
    -

    Bionimbus

    -

    This section explains a step by step procedure on getting Swift running on the -Bionimbus cloud. We will use the manual coasters configuration on the -Bionimbus cloud.

    -

    step1. Connect to the gateway (ssh gatewayx.lac.uic.edu)

    -

    step2. Start a virtual machine (euca-run-instances -n 1 -t m1.small -emi-17EB1170)

    -

    step3. Start the coaster-service on gateway -coaster-service -port 1984 -localport 35753 -nosec

    -

    step4. Start the Swift-script from the gateway using normal Swift commandline

    -

    swift -config cf -tc.file tc -sites.file sites.xml yourscript.swift -aparam=999

    -
    -
    cf
    -
    -
    wrapperlog.always.transfer=true
    -sitedir.keep=true
    -execution.retries=1
    -lazy.errors=true
    -status.mode=provider
    -use.provider.staging=true
    -provider.staging.pin.swiftfiles=false
    -foreach.max.threads=100
    -provenance.log=true
    -
    -
    -
    tc
    -
    -
    localhost modftdock /home/ketan/swift-labs/bionimbus-coaster-modftdock/app/modftdock.sh null null GLOBUS::maxwalltime="1:00:00"
    -
    -

    (See below for a sample sites.xml for this run)

    -

    step5. Connect back to gateway from virtual machines using reverse ssh tunneling as follows:

    -
    From the gateway prompt

    ssh -R *:5000:localhost:5000 root at 10.101.8.50 sleep 999

    -

    WHERE: -*=network interface, should remain the same on all cases

    -

    localhost=the gateway host, should remain the same

    -

    5000(LEFT OF localhost)=the port number on localhost to listen to **THIS WILL -vary depending upon which port you want to listen to

    -

    5000(RIGHT OF localhost)=the port on target host that you want to forward

    -

    root at 10.101.8.50=the ip of the Virtual Machine on Bionimbus cloud, this will -vary based on what ip you get for your Virtual Machine instance

    -

    #On anywhere as long as provide the correct callback uri: here the -"http://140.221.9.110:42195" is the callback uri of previous ones

    -

    step6. Start the worker from the virtual machine -worker.pl http://localhost:42195 tmp /tmp # where 42195 is the port where the -coaster service is listening to the workers

    -
    -
    sites.xml for the above run
    -
    -
    <config>
    -  <pool handle="localhost">
    -    <execution provider="coaster-persistent" url="http://localhost:1984" jobmanager="local:local"/>
    -    <profile namespace="globus" key="workerManager">passive</profile>
    -
    -    <profile namespace="globus" key="workersPerNode">4</profile>
    -    <profile namespace="globus" key="maxTime">10000</profile>
    -    <profile namespace="globus" key="lowOverAllocation">100</profile>
    -    <profile namespace="globus" key="highOverAllocation">100</profile>
    -    <profile namespace="globus" key="slots">100</profile>
    -    <profile namespace="globus" key="nodeGranularity">1</profile>
    -    <profile namespace="globus" key="maxNodes">10</profile>
    -    <profile namespace="karajan" key="jobThrottle">25.00</profile>
    -    <profile namespace="karajan" key="initialScore">10000</profile>
    -    <profile namespace="swift" key="stagingMethod">proxy</profile>
    -    <filesystem provider="local"/>
    -    <workdirectory>/home/ketan/swift-labs/bionimbus-coaster-modftdock/swift.workdir</workdirectory>
    -  </pool>
    -</config>
    -
    -
    -
    -
    -

    Debugging Swift

    -
    -

    Swift errors are logged in several places:

    -
      -
    1. -

      -All text from standard output and standard error produced by running the -swift command -

      -
    2. -
    3. -

      -The .log file from this run. It will be named swiftscript.uniqueID.log -where "swiftscript" is the name of your *.swift script source file, and -uniqueID is a long unique id which starts with the date and time you ran the -swift command. -

      -
    4. -
    5. -

      -$HOME/.globus/coasters directory on remote machines on which you are -running coasters -

      -
    6. -
    7. -

      -$HOME/.globus/scripts directory on the host on which you run the Swift -command, when swift is submitting to a local scheduler (Condor, PBS, SGE, -Cobalt) -

      -
    8. -
    9. -

      -$HOME/.globus/??? on remote systems that you access via Globus -

      -
    10. -
    -
    -
    -
    -

    Log Processing

    -
    -

    To properly generate log plots, you must enable VDL/Karajan logging. Make sure -log4.properties contains:

    -
    -
    -
    log4j.logger.swift=DEBUG
    -log4j.logger.org.globus.cog.abstraction.coaster.service.job.manager.Cpu=DEBUG
    -
    -
    -

    Make a basic load plot from Coasters Cpu log lines

    -
    Generate the log (may set log4j.logger.swift=INFO for this one)

    (assuming the log is titled swift-run.log)

    -
    -
    Convert the log times to Unix time
    -
    -
    ./iso-to-secs < swift-run.log > swift-run.time
    -
    -
    -
    Make the start time file (this contains the earliest timestamp)
    -
    -
    make LOG=swift-run.log start-time.tmp
    -
    -

    or

    -
    -
    -
    extract-start-time swift-run.log > start-time.tmp
    -
    -
    -
    Normalize the transition times
    -
    -
    ./normalise-event-start-time < swift-run.time > swift-run.norm
    -
    -
    -
    Build up a load data file:
    -
    -
    ./cpu-job-load.pl < swift-run.norm > load.data
    -
    -
    -
    Plot with the JFreeChart-based plotter in usertools/plotter:
    -
    -
    lines.zsh load.cfg load.eps load.data
    -
    -
    -

    Make a basic job completion plot from Coasters Cpu log lines

    -
    -
    Same as above, but, build up a completed data file:
    -
    -
    ./cpu-job-completed.pl < swift-run.norm > completed.data
    -
    -
    -
    Plot with the JFreeChart-based plotter in usertools/plotter:
    -
    -
    lines.zsh completed.cfg completed.eps completed.data
    -
    -
    -
    -

    Make a basic Block allocation plot from Coasters Block log lines

    -

    Same as above, but:

    -
    -
    Build up a block allocation data file:
    -
    -
    ./block-level.pl < swift-run.norm > blocks.data
    -
    -
    -
    Plot with the JFreeChart-based plotter in usertools/plotter:
    -
    -
    lines.zsh blocks.{cfg,eps,data}
    -
    -
    -
    -
    -

    Problem Reporting

    -

    When reporting problems to swift-user at ci.uchicago.edu, please attach the -following files and information:

    -
      -
    1. -

      -tc.data and sites.xml (or whatever you named these files) -

      -
    2. -
    3. -

      -your .swift source file and any .swift files it imports -

      -
    4. -
    5. -

      -any external mapper scripts called by your .swift script -

      -
    6. -
    7. -

      -all text from standard output and standard error produced by running the -swift command -

      -
    8. -
    9. -

      -The .log file from this run. It will be named swiftscript.uniqueID.log -

      -
    10. -
    11. -

      -where "swiftscript" is the name of your *.swift script source file, and -uniqueID is a long unique id which starts with the date and time you ran the -swift command. -

      -
    12. -
    13. -

      -The swift command line you invoked -

      -
    14. -
    15. -

      -Any swift.properties entries you over-rode ($HOME/.swift/swift.properties, --config.file argument properties file, any changes to etc/swift.proerties from -your swift distribution) -

      -
    16. -
    17. -

      -Which swift distribution you are running (release; svn revisions; other -local changes you mave have made or included) -

      -
    18. -
    -
    -
    -
    -
    -

    - - - Deleted: trunk/docs/cookbook/cookbook-asciidoc.pdf =================================================================== --- trunk/docs/cookbook/cookbook-asciidoc.pdf 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/cookbook/cookbook-asciidoc.pdf 2011-05-17 15:30:41 UTC (rev 4483) @@ -1,4267 +0,0 @@ -%PDF-1.4 -5 0 obj -<< /S /GoTo /D (section.1) >> -endobj -8 0 obj -(Overview) -endobj -9 0 obj -<< /S /GoTo /D (section.2) >> -endobj -12 0 obj -(Swift Basics) -endobj -13 0 obj -<< /S /GoTo /D (subsection.2.1) >> -endobj -16 0 obj -(Installation) -endobj -17 0 obj -<< /S /GoTo /D (subsubsection.2.1.1) >> -endobj -20 0 obj -(Prerequisites) -endobj -21 0 obj -<< /S /GoTo /D (subsection.2.2) >> -endobj -24 0 obj -(Setting up to run Swift) -endobj -25 0 obj -<< /S /GoTo /D (subsubsection.2.2.1) >> -endobj -28 0 obj -(Environment Setup) -endobj -29 0 obj -<< /S /GoTo /D (subsubsection.2.2.2) >> -endobj -32 0 obj -(Setting transformation catalog) -endobj -33 0 obj -<< /S /GoTo /D (subsubsection.2.2.3) >> -endobj -36 0 obj -(Setting swift configuration) -endobj -37 0 obj -<< /S /GoTo /D (subsubsection.2.2.4) >> -endobj -40 0 obj -(Setting sites.xml) -endobj -41 0 obj -<< /S /GoTo /D (subsection.2.3) >> -endobj -44 0 obj -(First SwiftScript) -endobj -45 0 obj -<< /S /GoTo /D (subsection.2.4) >> -endobj -48 0 obj -(second SwiftScript) -endobj -49 0 obj -<< /S /GoTo /D (subsection.2.5) >> -endobj -52 0 obj -(Swift Commandline Options) -endobj -53 0 obj -<< /S /GoTo /D (subsection.2.6) >> -endobj -56 0 obj -(What if Swift hangs) -endobj -57 0 obj -<< /S /GoTo /D (subsection.2.7) >> -endobj -60 0 obj -(Resuming a stopped or crashed Swift Run) -endobj -61 0 obj -<< /S /GoTo /D (subsection.2.8) >> -endobj -64 0 obj -(Passing an array to swift?) -endobj -65 0 obj -<< /S /GoTo /D (subsubsection.2.8.1) >> -endobj -68 0 obj -(Mappers) -endobj -69 0 obj -<< /S /GoTo /D (section.3) >> -endobj -72 0 obj -(Coasters) -endobj -73 0 obj -<< /S /GoTo /D (subsection.3.1) >> -endobj -76 0 obj -(For Advanced Users) -endobj -77 0 obj -<< /S /GoTo /D (subsection.3.2) >> -endobj -80 0 obj -(Coaster providers: local, ssh, pbs) -endobj -81 0 obj -<< /S /GoTo /D (section.4) >> -endobj -84 0 obj -(Swift on Diverse Infrastructures) -endobj -85 0 obj -<< /S /GoTo /D (subsection.4.1) >> -endobj -88 0 obj -(Beagle) -endobj -89 0 obj -<< /S /GoTo /D (subsection.4.2) >> -endobj -92 0 obj -(PADS) -endobj -93 0 obj -<< /S /GoTo /D (subsection.4.3) >> -endobj -96 0 obj -(OSG) -endobj -97 0 obj -<< /S /GoTo /D (subsection.4.4) >> -endobj -100 0 obj -(Bionimbus) -endobj -101 0 obj -<< /S /GoTo /D (section.5) >> -endobj -104 0 obj -(Debugging Swift) -endobj -105 0 obj -<< /S /GoTo /D (section.6) >> -endobj -108 0 obj -(Log Processing) -endobj -109 0 obj -<< /S /GoTo /D (subsection.6.1) >> -endobj -112 0 obj -(Make a basic load plot from Coasters Cpu log lines) -endobj -113 0 obj -<< /S /GoTo /D (subsubsection.6.1.1) >> -endobj -116 0 obj -(Make a basic job completion plot from Coasters Cpu log lines) -endobj -117 0 obj -<< /S /GoTo /D (subsubsection.6.1.2) >> -endobj -120 0 obj -(Make a basic Block allocation plot from Coasters Block log lines) -endobj -121 0 obj -<< /S /GoTo /D (subsection.6.2) >> -endobj -124 0 obj -(Problem Reporting) -endobj -125 0 obj -<< /S /GoTo /D [126 0 R /FitH ] >> -endobj -128 0 obj << -/Length 277 -/Filter /FlateDecode ->> -stream -x??Q?JCA ??W??^Lv?????????J/ZZ??"?}????X?>??endstream -endobj -126 0 obj << -/Type /Page -/Contents 128 0 R -/Resources 127 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 140 0 R ->> endobj -129 0 obj << -/D [126 0 R /XYZ 56.6929 815.7613 null] ->> endobj -136 0 obj << -/D [126 0 R /XYZ 56.6929 759.0684 null] ->> endobj -127 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -143 0 obj << -/Length 2501 -/Filter /FlateDecode ->> -stream -x??\]s?6}????5????c_v??????dcw????,??6??Rr??? ? -???8?v??I?XG??? ?^?"?H!$???B??$?X?/p?h????8??]????????0?H*???BR$?? -1CUq{???????~vE?|QU???????????B??J?|??????"!h?????^|{?x&??? -??.~????q?I???#? -)??????7????F??R?8?b?Y?d?? BD3???K$??4^T?}???F'c??q??w?Gy;??qPQ?Q -dvE0??????,??????1%b??4SG???PY*6?\?c.#~?? a?{?b????M?"U^?w?EB)???#R????,????? ???l??3?q??_??4-?Q[G?Vv??ov??j5?/?M?fl?)9bt???!\#???3A?+a#2?|? 7?} ?@?O(???s:?H??E4??]k?nd??a??$??H?F??!E???P?R?M -j=??.?????n?/??A)??El#? -??P!Z"???L?~???<?H?`??2???r#5?z????j'J??>?Q????n??~?y?6??m??????i???m?? ?b??"&?&?Gex??9R?yN?~?|M(xQ"??KG?$d????7?A??k??4k???oN?u?Y?c??}??9q4 ??-),??`2?????X#I??3??? /?R??I?W:ZF???c???.?%D(?@^??I??????f?P???h?????zL???J?"6? -??2,?`??E?yN>Y?`r??????cr???r {H1?????rfCr?J?E???????r)?Ha"??z?f????L#???I??j?I?m0&?hmCF?^?G?Kk???????????^%'qC??$g?$?QN???k?g5??3? -[?v0l?h?CF??Q}j1*?D?p?????b????????fQ/?i?)q?$?"?????2???5?6??i???R?&?(!????5?e? =?;cO??h???T??%??????|F(?????? -?&*??(?c?Oj??gJ???b??t?L@F??psV?LxT??w(?K???|s?Zn??????~?vh "????gZL?%?? }r??????):?t???!?g/?\?? ?V|@uB?N????;?/??{?????q???-(?Elw`?w? ?????M????>?C:??LG??4z???%o?????r????=?C?;w%???nKw"?j?????w?}?3o??????5?????{?Gef@?F????$yH???#u?~OGk???? -=??q?3'?????????????v?????????_?m{?O?>)%E?h?8T?nh???NR????-?0l?hM??x&@F?m?s?? -n????p????]???lcgF -fE?)???C'.*P??E ~:ZfQ???????1Bgr??????b??7/o?G? ?F?"}??7???8dI?b???j????H)??T&??h??xi??y???????% -??C??HG?$ -h????J??,?(?%??#?zYm?????OiS?i??bElb??Y??0!? ?x??$???1??E;J0??h????[?Q????+???z?]??????1\?~n?S? eEl+???Q -~?9???h??a???? 1p?G5??s??*??7m?Z-??z_?j?~ zD-Y5*?(?#?D?X?J A??W???zT??P??8?V??k?w?W1t????k?nW?????2??????*?Bz?j?XF9?2?????\a??b"???O?`Hh)????#zk?wj?endstream -endobj -142 0 obj << -/Type /Page -/Contents 143 0 R -/Resources 141 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 140 0 R -/Annots [ 145 0 R 149 0 R 150 0 R 151 0 R 152 0 R 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R 163 0 R 164 0 R 165 0 R 166 0 R 167 0 R 168 0 R 169 0 R 170 0 R 171 0 R 172 0 R 173 0 R 174 0 R 175 0 R 176 0 R 177 0 R ] ->> endobj -145 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 706.3558 113.3799 715.332] -/Subtype /Link -/A << /S /GoTo /D (section.1) >> ->> endobj -149 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 678.4604 123.8304 687.4366] -/Subtype /Link -/A << /S /GoTo /D (section.2) >> ->> endobj -150 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 660.5476 140.3783 669.3942] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.1) >> ->> endobj -151 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 640.5575 178.8938 651.4615] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.1.1) >> ->> endobj -152 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 622.6248 186.3259 633.5287] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.2) >> ->> endobj -153 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 604.692 204.239 615.596] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.2.1) >> ->> endobj -154 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 586.7593 248.0736 597.6632] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.2.2) >> ->> endobj -155 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 568.8265 233.6979 579.7305] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.2.3) >> ->> endobj -156 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 550.8938 193.8574 561.7977] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.2.4) >> ->> endobj -157 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 532.961 161.698 543.865] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.3) >> ->> endobj -158 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 515.0283 171.093 525.9322] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.4) >> ->> endobj -159 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 497.0955 210.1262 507.9995] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.5) >> ->> endobj -160 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 479.1628 175.5165 490.0667] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.6) >> ->> endobj -161 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 461.23 263.2368 472.134] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.7) >> ->> endobj -162 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 443.2973 197.7727 454.2012] -/Subtype /Link -/A << /S /GoTo /D (subsection.2.8) >> ->> endobj -163 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 425.3645 162.2866 436.2685] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.2.8.1) >> ->> endobj -164 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 399.5065 109.7037 408.4827] -/Subtype /Link -/A << /S /GoTo /D (section.3) >> ->> endobj -165 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 381.4741 177.0411 390.4403] -/Subtype /Link -/A << /S /GoTo /D (subsection.3.1) >> ->> endobj -166 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 361.6036 227.7101 372.5076] -/Subtype /Link -/A << /S /GoTo /D (subsection.3.2) >> ->> endobj -167 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 335.7456 209.7673 344.7218] -/Subtype /Link -/A << /S /GoTo /D (section.4) >> ->> endobj -168 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 315.7755 123.2131 326.6794] -/Subtype /Link -/A << /S /GoTo /D (subsection.4.1) >> ->> endobj -169 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 299.9 120.0951 308.7467] -/Subtype /Link -/A << /S /GoTo /D (subsection.4.2) >> ->> endobj -170 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 281.9673 115.4724 290.8139] -/Subtype /Link -/A << /S /GoTo /D (subsection.4.3) >> ->> endobj -171 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 264.0345 139.0835 272.8812] -/Subtype /Link -/A << /S /GoTo /D (subsection.4.4) >> ->> endobj -172 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 234.2163 143.0086 245.0954] -/Subtype /Link -/A << /S /GoTo /D (section.5) >> ->> endobj -173 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [55.6967 206.3209 136.9314 217.2] -/Subtype /Link -/A << /S /GoTo /D (section.6) >> ->> endobj -174 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 188.2537 299.9385 199.1576] -/Subtype /Link -/A << /S /GoTo /D (subsection.6.1) >> ->> endobj -175 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 170.3209 374.7175 181.2249] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.6.1.1) >> ->> endobj -176 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [93.5547 152.3882 387.4395 163.2921] -/Subtype /Link -/A << /S /GoTo /D (subsubsection.6.1.2) >> ->> endobj -177 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[1 0 0] -/Rect [70.6406 134.4554 171.6511 145.3594] -/Subtype /Link -/A << /S /GoTo /D (subsection.6.2) >> ->> endobj -144 0 obj << -/D [142 0 R /XYZ 56.6929 815.7613 null] ->> endobj -141 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -181 0 obj << -/Length 4471 -/Filter /FlateDecode ->> -stream -x??]?o??????]?3H?KR%(?????????H?@??????D??????x?%R?v? 0???xz?{<??& ??E??i??H?RF???? ^\???N??Yk??-?????/??Q?([?].E,??"?)?r?.?6?.O????jM????????????O?"?OY???? ????' ??,??????w'_???YiNP???[??????? -????8???n0?qN7' ???Q?d{rz?]?Q??1?q????Z??$???????$I?ftA(? I??? -&=??2?fY??H-?t?q?on?f?&xy[?+?,?T.??????4C?0??g?U Y???Bg0?a??zn??e?$nW4YMU?????????v?s??????J*j??A???q/??F?m???y?K?m?G?rSqXmI?????1?:6???w????-7???I??u? ??muQ?y?@???JD"p s?~9VMyS?\'8$M?WR<?m???1w??)?Cs?8??E?u?SHX%?????=?7??E}?o?V???/-??????o????X\??NY????D?Eb???????????K??u#?u?;4?l??{???8?MUl??????q????M?G????e -?3??(?PQX?$?uS?~??W????bm??-W3w??lJ??(G??@??A54R!\G?ESQ?%)?Q?6??'?1I????D????n ?Z??E;?5e?<xmI0J?????b?k?D????O??Z(?(???v???nE? -????????V??"??B~s(???*??]??????uS???M)/*Y|??EODe?Ra?_kyh?x?P?WI??![????)xWm?J??h?????7)Y??R??:???? =?Az???Ngs??=??? ????I5Y????@u??tw??????H?J?C -?^_ ?????@??_?????>?./??6????"c)???q?e?R?Pvh/rQG Ay5??_q??!J?l?K?e??\\Z?]???=B?&???????j?*#?????O??C???,UQkW??{.?w?????2????`??`?dc -???B^|????I???c3c;F)^?? -Kt]q -=H[???Ei??b)?????b=???r?4?MJ?c?<??$d???????? e)a?a?Q????3r? ???1/?Ip?5om?B??6??!$?o&???Z>?/?%F4C 2??????KSh?D$??)?=r$c@?H?K?QI? QRJf???rb??Zln??=q???&???,V @]t=D4qh??]t?b;ZE5:?????I?w?HP?P??d*%?H@???? -?R>?N?A?I&?3D?8!M?7???l?!a?C?????0n%?'?k)?]M2M;?`?????3v??H)D?;n?B?R.?????0Bf{????B?????0??^k???m?kC?gz?5x?H???3?F?5??pJ?W{(?}?????? ???????w?;M????2??2????????6,?Q??]J?6k??n???f??H?4~?'?~??1 -?-%?&???k??b;Z?? ???O? /??^?M_r??]??=?:=???>??n?V? -z?S??)???Y0?*!??????m????????????8?????K96(?#????^w=K???m?? H??|??Ah.???bz?????/???fb?m????????vn????m???,W??????%??S???o? ???vm???x?U?C?????@Az[??T?A?gQx???9$%?@:?s-2??;??F8????s#?u???~`"(?)?????;zE????QDf, x??B????(iX???Y??2~s?a???eh? ??3??? ?i? ???????0????g7{^dW?TX??=?9?? ??3??????[?G5?~???a?d?g$}ft -??????|Zy?? -??efz??o???M;-??ur????"%^??qZ?????$????&????kL76????V???7y???/#?=?1?+???g?%{????????<4n??????N??????P??A ?3t}?i??\]? -G?D???cH????T?? -?M.????Y?r???????>%????0??SqM???5?GjQ?m?]?4#????R?u?T???o???,"???.9!???Gr??IV??q?JV?y#C???Hsu?K?y*'%@Q??F???Fp??g????A????????g?q"?\??W???vS??? /?mS?{y?;?C??S?ry~???????H~???F??M?????eS?X??)???????8??C5??:e???;AK?7???????q?=Q?Y??NnX???FJ??????????nzu?T?????u?-???)~l=???~6???c?u?????5;z??????pf?@???H??m???i????l??|~?W?}??\????,| -?J9?m?>j??J<?V]????=z????:E8b?~O?? -_y???F?????Y??(ZD?O?d???(Q?M?E?C??9?.g9t????_D?t??L????KA[??`] ??+???????u???I???(????Q??OH??B????,)???Z??????#3??|???i??????????????????gqp?x!??????8=?vE?_?B?+?Q?B????b6????E??Gxx?m????J\?\??{?F??? {s????wE?@?T???TQ????\Ex)???7???????????????eVd?jQ,?4=??@1N?8K7??`?xa?w??U=???Yw5??? endstream -endobj -180 0 obj << -/Type /Page -/Contents 181 0 R -/Resources 179 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 140 0 R -/Annots [ 184 0 R 202 0 R ] ->> endobj -178 0 obj << -/Type /XObject -/Subtype /Form -/FormType 1 -/PTEX.FileName (/autonfs/home/davidk/dblatex-0.3/latex/graphics/warning.pdf) -/PTEX.PageNumber 1 -/PTEX.InfoDict 210 0 R -/Matrix [1.00000000 0.00000000 0.00000000 1.00000000 0.00000000 0.00000000] -/BBox [0.00000000 0.00000000 160.00000000 183.00000000] -/Resources << -/ProcSet [ /PDF ] -/ExtGState << -/R7 211 0 R ->>>> -/Length 212 0 R -/Filter /FlateDecode ->> -stream -x??R;N1 ?} -????? ?f?,?l?Rp}?L2?@??_^??m9o??}??o?xV??C??0??|?? ?rf "??p????W??~???+}??????r??"??M??3?\??!?4K)?~????Vvfm???5~??[G#?6??y GI?7??????????)endstream -endobj -210 0 obj -<< -/Producer (GPL Ghostscript SVN PRE-RELEASE 8.61) -/CreationDate (D:20100125210321Z) -/ModDate (D:20100125210321Z) ->> -endobj -211 0 obj -<< -/Type /ExtGState -/OPM 1 ->> -endobj -212 0 obj -252 -endobj -184 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [321.5267 691.4354 340.6647 702.3393] -/Subtype/Link/A<> ->> endobj -202 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [444.2645 336.0762 463.4026 346.9802] -/Subtype/Link/A<> ->> endobj -182 0 obj << -/D [180 0 R /XYZ 56.6929 815.7613 null] ->> endobj -6 0 obj << -/D [180 0 R /XYZ 56.6929 759.0684 null] ->> endobj -183 0 obj << -/D [180 0 R /XYZ 56.6929 731.2722 null] ->> endobj -10 0 obj << -/D [180 0 R /XYZ 56.6929 677.8333 null] ->> endobj -185 0 obj << -/D [180 0 R /XYZ 56.6929 641.7915 null] ->> endobj -14 0 obj << -/D [180 0 R /XYZ 56.6929 641.7915 null] ->> endobj -186 0 obj << -/D [180 0 R /XYZ 56.6929 615.3924 null] ->> endobj -18 0 obj << -/D [180 0 R /XYZ 56.6929 574.9607 null] ->> endobj -187 0 obj << -/D [180 0 R /XYZ 56.6929 550.1206 null] ->> endobj -188 0 obj << -/D [180 0 R /XYZ 56.6929 500.6172 null] ->> endobj -189 0 obj << -/D [180 0 R /XYZ 56.6929 502.0767 null] ->> endobj -193 0 obj << -/D [180 0 R /XYZ 56.6929 491.1178 null] ->> endobj -194 0 obj << -/D [180 0 R /XYZ 56.6929 480.1588 null] ->> endobj -195 0 obj << -/D [180 0 R /XYZ 56.6929 469.1999 null] ->> endobj -196 0 obj << -/D [180 0 R /XYZ 56.6929 458.241 null] ->> endobj -197 0 obj << -/D [180 0 R /XYZ 56.6929 447.2821 null] ->> endobj -198 0 obj << -/D [180 0 R /XYZ 56.6929 436.3232 null] ->> endobj -199 0 obj << -/D [180 0 R /XYZ 56.6929 425.3643 null] ->> endobj -200 0 obj << -/D [180 0 R /XYZ 56.6929 414.4054 null] ->> endobj -22 0 obj << -/D [180 0 R /XYZ 56.6929 378.6212 null] ->> endobj -201 0 obj << -/D [180 0 R /XYZ 56.6929 352.0227 null] ->> endobj -203 0 obj << -/D [180 0 R /XYZ 56.6929 320.0948 null] ->> endobj -204 0 obj << -/D [180 0 R /XYZ 56.6929 321.5543 null] ->> endobj -26 0 obj << -/D [180 0 R /XYZ 56.6929 285.77 null] ->> endobj -205 0 obj << -/D [180 0 R /XYZ 56.6929 261.7619 null] ->> endobj -206 0 obj << -/D [180 0 R /XYZ 56.6929 229.2362 null] ->> endobj -207 0 obj << -/D [180 0 R /XYZ 56.6929 230.6956 null] ->> endobj -208 0 obj << -/D [180 0 R /XYZ 56.6929 175.3142 null] ->> endobj -209 0 obj << -/D [180 0 R /XYZ 56.6929 176.7737 null] ->> endobj -179 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F57 148 0 R /F90 192 0 R >> -/XObject << /Im1 178 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -215 0 obj << -/Length 4909 -/Filter /FlateDecode ->> -stream -x??]mo????_??~??,?W?:4?6 -?^S????|???g?vW????%?Q?H??]??n????h??3r?4ZA?/Z? d.V1?g??6? ?z+???i??!Z?T_?\\???U? g???U?A?C??0????f????????Zc/?4????]?t??x??x5#?U???????1????k9??V???]|uc?2b??a.???????j+t??Zp?z?@?i?V? ??#???dw????G?-??B????R?a??@????????Q?Q]!v????js?U?????UON??6m}???A?,??]?????5'M?#d??l^??M????#???I?uw??????+?.??[?????????????"?? ????6?P?????E[f#?W??U[?n???_??&F`??????l??,???T/?3???x???? -?4H??b????}?I??&???????d6/4 p??]???????@YQX{)??td/?J???7??????????%P?x?1?????M????Ubw?)?p!???Z?????3?@?t?(_???O?+:>???w?'?"??j3 at r?Mj""?$??M??]B9@ ?E6?O???3tci???&2b9 -?"?K?@????????X8l,} -???? ??H? g??T??????}?I ??? G?ypB??E?I?K?H?,?eE.Fs??1??? ???c3 ???2.?p(g??&J?z??`??:????k???? -?????]?F??M??"*?Q????????X?fNUDf" ???%C ?K?Z??;????????????8????????/???u?v????1A????So[?E?YP???/E/???,?w?gWk??? -??z???R?]??????g???6??l=?ZS?D?(zxy,?;?????o4?F*?K?i???m????+V(??G??H???o?[?p???6????2v?+%??? -k?Y$?? ?}?}L??e?????Lt?k??P?v??4???????Y -???c?????@??gz??F??W?????e; ?7?Z???i???Xn????4\?????R???N????D???c?E1?p??P?#1?YY"98?z5?ol???? -?????N??E???_??????"??dO~?????_????????A81j&V!Y?V? ??p?1???,???6??@9???o?????18?sM?? 9"? ?Vn??I?????1 "F0^???I?_????a??fb?%???????H?)??? S1?????L????~???V?'?9?? K????4?????Fo??|1?Q????V??kR?/?L??xT?y ?YbD?y?a???>?k????i??tlLf?kF58:?"???a?Ef???????(?d???3?{?X?????-?X?l???4??t23????x?y???T??V?Y?y?? MJp??N]?O?jS?>z?=???l?zs?+?????uw&[$G?V???????B??2 n??7Pa???N??E,:8$?7P??*??????5?????J}?ne??? ???}e&??8?v??o??j?? ????????1S?}k*?????I??o??T????0??T??o?>>?? -??????N?{[???}???>?!?A/6?Df_p[???>.CO<{?'???5x??O??u -y?S????g????"???J???f?a???*[?$??o??W??eJe??l????3?????[?!?w???a?C2[R?????C??u#????1???u xs?n?Vj?-8???QM????< -.??-?????mi????Y?????Ce?n?z t?*?!?E??B?GpAU?9?(???#??m??^?D?u?!1T?W`?4?"??y:?=??&UAeL_^???$??6???P?? -U ?????y?????(????M?'3?!'?u?!??|?1&??G?G%p?&?? ?? #???v????? ?w???????S^?j?m??j? - ?)???gN'[?ypqqX???Z[?P???%???u?????'??i????*??s?????????*o???S?}iK???????N? -?:Frv??????}L???? -??SW?s??l??L#??8??-???.HW??{? |u?e??`?8??M'?=n?a?:N?\sC????tG??f?????&X??y??????S? ?0zC????1??b??F?]b? ?)_ ??}????m"???W??A??(?s|N8|@?v?8b?????>q?x??u??M?H?ni????k?q?|??c?lQ?EXfFv???3]??#?k????m??????,???d???Q7&&?\? f?+#?^??w$????u\k??(????g?C??????{F??;j?Q+T????&?F?y%%??????o?>? ??II?R?6on???????? r??k??wSB)?,?>Ry??? K??t?q???o?? ???HN???????#??P=???????G??+Y???Dx????b??+J???] ??G?1?F?QIy??????-?L?&vD Qhv5?if?qe?F???[?E?????mo?? -an?p??uW????? -??t???dT"a??3r????#Ny??)?????*/?@?????Y???a+6Dj1,S??q5%??"??|?["o?????_??\m???????Co?X??_ ??Ov?/????8??F?Iendstream -endobj -214 0 obj << -/Type /Page -/Contents 215 0 R -/Resources 213 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 140 0 R -/Annots [ 233 0 R ] ->> endobj -233 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [548.7873 407.9685 567.9254 418.8724] -/Subtype/Link/A<> ->> endobj -216 0 obj << -/D [214 0 R /XYZ 56.6929 815.7613 null] ->> endobj -217 0 obj << -/D [214 0 R /XYZ 56.6929 742.9593 null] ->> endobj -218 0 obj << -/D [214 0 R /XYZ 56.6929 744.4188 null] ->> endobj -30 0 obj << -/D [214 0 R /XYZ 56.6929 710.1122 null] ->> endobj -219 0 obj << -/D [214 0 R /XYZ 56.6929 687.1371 null] ->> endobj -220 0 obj << -/D [214 0 R /XYZ 56.6929 608.8432 null] ->> endobj -221 0 obj << -/D [214 0 R /XYZ 56.6929 610.3027 null] ->> endobj -222 0 obj << -/D [214 0 R /XYZ 56.6929 599.3438 null] ->> endobj -34 0 obj << -/D [214 0 R /XYZ 56.6929 449.3441 null] ->> endobj -232 0 obj << -/D [214 0 R /XYZ 56.6929 423.4797 null] ->> endobj -234 0 obj << -/D [214 0 R /XYZ 56.6929 393.02 null] ->> endobj -235 0 obj << -/D [214 0 R /XYZ 56.6929 394.4795 null] ->> endobj -236 0 obj << -/D [214 0 R /XYZ 56.6929 383.5206 null] ->> endobj -237 0 obj << -/D [214 0 R /XYZ 56.6929 372.5617 null] ->> endobj -238 0 obj << -/D [214 0 R /XYZ 56.6929 361.6028 null] ->> endobj -239 0 obj << -/D [214 0 R /XYZ 56.6929 350.6439 null] ->> endobj -240 0 obj << -/D [214 0 R /XYZ 56.6929 339.685 null] ->> endobj -241 0 obj << -/D [214 0 R /XYZ 56.6929 328.7261 null] ->> endobj -242 0 obj << -/D [214 0 R /XYZ 56.6929 317.7672 null] ->> endobj -243 0 obj << -/D [214 0 R /XYZ 56.6929 306.8083 null] ->> endobj -244 0 obj << -/D [214 0 R /XYZ 56.6929 295.8494 null] ->> endobj -245 0 obj << -/D [214 0 R /XYZ 56.6929 284.8904 null] ->> endobj -246 0 obj << -/D [214 0 R /XYZ 56.6929 273.9315 null] ->> endobj -247 0 obj << -/D [214 0 R /XYZ 56.6929 262.9726 null] ->> endobj -38 0 obj << -/D [214 0 R /XYZ 56.6929 228.666 null] ->> endobj -248 0 obj << -/D [214 0 R /XYZ 56.6929 205.6909 null] ->> endobj -249 0 obj << -/D [214 0 R /XYZ 56.6929 177.2885 null] ->> endobj -250 0 obj << -/D [214 0 R /XYZ 56.6929 176.6907 null] ->> endobj -251 0 obj << -/D [214 0 R /XYZ 56.6929 165.7318 null] ->> endobj -252 0 obj << -/D [214 0 R /XYZ 56.6929 154.7729 null] ->> endobj -253 0 obj << -/D [214 0 R /XYZ 56.6929 143.814 null] ->> endobj -254 0 obj << -/D [214 0 R /XYZ 56.6929 132.8551 null] ->> endobj -255 0 obj << -/D [214 0 R /XYZ 56.6929 121.8962 null] ->> endobj -256 0 obj << -/D [214 0 R /XYZ 56.6929 110.9373 null] ->> endobj -257 0 obj << -/D [214 0 R /XYZ 56.6929 99.9784 null] ->> endobj -213 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R /F98 231 0 R /F57 148 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -260 0 obj << -/Length 4318 -/Filter /FlateDecode ->> -stream -x??]m???????=8/pf?*J????k{?pm/????????xm??????%E??D??8?/????y?_??? ?d&2????D ?6[=??????7??YX??/??7??xV?"?????,?(?X?r,+???X???X??? *?????????W/?QE?,WE3??r)D>[? -!hS??b2??3/??r7??xYZ? ? ?kV??y? -????on0?ENf???(/???F??e?~????????[???~Vh?)Bd?g&y?????Li??h?3??i?) -???f4???? ?W?????D?O?y?M?}?:V???-??Um"IT.(E?$?Q??[B?|>???cz?c??????????q???T?,H?8??F?????~?6?N?]U?5?W?r????7K???Nm????|0??]??x????????????~??n?vu????????|v,gw^?k???6??? -? -8?f???l??)0?\??*????a??h9UQ???????Y2??}{??'?}??????~f??mhl? -?G?:j???????I????~?S?.?j??u?? ?dQ??2??P?6???ux=n??????z`&O??(?d??Ju???????P?p??R?R?*Y?_?f2????1??7=???35o?IT??l???:?????+5???v?Uco?e?bH??????V5b08W$?c -??v_k3?V?u`1Q+n????&;)7?6h4?QA?X??<???????}\TgU.??Rl?m?j)?????C?????z??6h?T???????Cm??SB??????<?????}@??(?^h?j+????f\-R??F??x_??~?????0P2j.???R?????R"????Vo????a?H&?????P??? Hp9?o;y??W???Sh6#g????m? ?@???,C?+G|??V????Ww?????h???4G?f??n?A?????7?=?(?0?;)??I?? ??'F?N??j???j?3?rT??`[9h4?D}??6??C?Fl?h?Y?T)?u??????OhS?('E??V*????z?M?$/????*W?}?#NP???$???A?v?M? ?Q?F?????q?*??){?j???(7????S4B????! -F?g?9? ?Q??/?l?R?????_????v_??4|??r<x???O????P???Z??h?N -6r?g???8?=_. ???.??W??????+U???????YvQ? -??e??J/?<]???J?r?.??`?wk?????HIjv??3?/??5??? -? -????"??@??V?7rlD?????I???8?P1 -???`?}?s ?V*?w???+??K????[???f??????)??C????ry???????=?gL??? ?H?>f??V7b=?#????O??R.~e???+}z?}? ??ET???`?\UH?!??j????????f9 -?8???V??kv??!|?$??IR?\;?@????]?o???~?$}}???4j?K?>7A???B-?9^d???.?l?R?Ws?i?????a????? ?@ >u?i??t???"??T???cVH???????t??????9)sGy??F?_O?????Y??S?????E?;BM????eQ"?4?L??G??p??`????T????n?!????F?????????????aq???Qu(?T?3W?u ?? ??>?C??s???6O+l????B?Q????Rcx?W?3???I????? -???y]???=>??/?/?????3?????????/?jn???????????L???B???Z-???\??5?o?????<=?&??????0&D?w???????L????l??N???????oJ??T???W??[27?3??j??E?z?f?o??9Z????3?16L?????m? -?rWzB????-?????f???l?????????F?T0\-?n??x???)Y??I???S??4??@e???\??%cS??nJ?n3pNl2??N???1?g????-UU?}? ?? ???)[v?B"????e??G??,/???s??j6???=$???C??Ww?#`????l???*???bER?N -?m?z???hTF0>??? ??G?L"!????t?Y?e?ZN?L????25B??DS_??mctAG?PIx7B???*a?;G???9??}??"Y? (h_[[#$?\?,?'?+?k?????eB??????????????)X?UA?i?JE?d{??682???????4?6??A?tW??v?>??#?[p???6?P?Q??????n??(PY?u:?R*LK??? -?f??p^??@?T???.[}u??4]?w?? ???[/?e$n?%?-?????>?/??X???A????`3?v(???? -R?y!*m?|?l??k??D?h??E?P????S*6:?C????/?? sY???? -?B??I{P ??????????4M??????>??G8?XH??s???!???jvO"?:?3??=??>V?Vo?????|??)?e???H?/w?^??C?v?O????n?x??V?8U?@_ot?`???v?? -???C??X?p?O >\?????aoN*.J?I???G???5Nfy??% t????K?b??????B?U]R?5??xX???jW??=?@?S?6?????K?!?|]??????? ??w???~??p?*?Q?=????????w????v???????)?4????jP?>j&???JU?3????9???9 -?W??7?3T?Vw^??v??????oM??L -?Z?g?h1?T???[???y[W??X.?:I??hy\m??\?g????l_[??????7??jy*?G???R8???q??Q??R'?x??I,?'o?c}??BRK?`???/-?jgMY+?????k?M.?6?V??f??????U=?[2o????> endobj -283 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [216.7201 469.032 428.9318 479.9359] -/Subtype/Link/A<> ->> endobj -261 0 obj << -/D [259 0 R /XYZ 56.6929 815.7613 null] ->> endobj -42 0 obj << -/D [259 0 R /XYZ 56.6929 759.0684 null] ->> endobj -262 0 obj << -/D [259 0 R /XYZ 56.6929 738.4887 null] ->> endobj -263 0 obj << -/D [259 0 R /XYZ 56.6929 703.155 null] ->> endobj -264 0 obj << -/D [259 0 R /XYZ 56.6929 704.6144 null] ->> endobj -265 0 obj << -/D [259 0 R /XYZ 56.6929 693.6555 null] ->> endobj -266 0 obj << -/D [259 0 R /XYZ 56.6929 682.6966 null] ->> endobj -267 0 obj << -/D [259 0 R /XYZ 56.6929 671.7377 null] ->> endobj -268 0 obj << -/D [259 0 R /XYZ 56.6929 660.7788 null] ->> endobj -269 0 obj << -/D [259 0 R /XYZ 56.6929 649.8199 null] ->> endobj -270 0 obj << -/D [259 0 R /XYZ 56.6929 638.861 null] ->> endobj -271 0 obj << -/D [259 0 R /XYZ 56.6929 627.9021 null] ->> endobj -272 0 obj << -/D [259 0 R /XYZ 56.6929 616.9432 null] ->> endobj -273 0 obj << -/D [259 0 R /XYZ 56.6929 605.9843 null] ->> endobj -274 0 obj << -/D [259 0 R /XYZ 56.6929 595.0254 null] ->> endobj -275 0 obj << -/D [259 0 R /XYZ 56.6929 584.0665 null] ->> endobj -276 0 obj << -/D [259 0 R /XYZ 56.6929 573.1076 null] ->> endobj -277 0 obj << -/D [259 0 R /XYZ 56.6929 562.1487 null] ->> endobj -278 0 obj << -/D [259 0 R /XYZ 56.6929 551.1898 null] ->> endobj -279 0 obj << -/D [259 0 R /XYZ 56.6929 540.2309 null] ->> endobj -280 0 obj << -/D [259 0 R /XYZ 56.6929 529.272 null] ->> endobj -281 0 obj << -/D [259 0 R /XYZ 56.6929 518.3131 null] ->> endobj -282 0 obj << -/D [259 0 R /XYZ 56.6929 507.3542 null] ->> endobj -46 0 obj << -/D [259 0 R /XYZ 56.6929 444.7788 null] ->> endobj -284 0 obj << -/D [259 0 R /XYZ 56.6929 417.8872 null] ->> endobj -285 0 obj << -/D [259 0 R /XYZ 56.6929 398.9923 null] ->> endobj -286 0 obj << -/D [259 0 R /XYZ 56.6929 400.4518 null] ->> endobj -287 0 obj << -/D [259 0 R /XYZ 56.6929 389.4929 null] ->> endobj -288 0 obj << -/D [259 0 R /XYZ 56.6929 378.534 null] ->> endobj -289 0 obj << -/D [259 0 R /XYZ 56.6929 367.5751 null] ->> endobj -290 0 obj << -/D [259 0 R /XYZ 56.6929 356.6162 null] ->> endobj -291 0 obj << -/D [259 0 R /XYZ 56.6929 345.6572 null] ->> endobj -292 0 obj << -/D [259 0 R /XYZ 56.6929 334.6983 null] ->> endobj -293 0 obj << -/D [259 0 R /XYZ 56.6929 323.7394 null] ->> endobj -294 0 obj << -/D [259 0 R /XYZ 56.6929 312.7805 null] ->> endobj -295 0 obj << -/D [259 0 R /XYZ 56.6929 301.8216 null] ->> endobj -296 0 obj << -/D [259 0 R /XYZ 56.6929 290.8627 null] ->> endobj -297 0 obj << -/D [259 0 R /XYZ 56.6929 279.9038 null] ->> endobj -298 0 obj << -/D [259 0 R /XYZ 56.6929 268.9449 null] ->> endobj -299 0 obj << -/D [259 0 R /XYZ 56.6929 257.986 null] ->> endobj -300 0 obj << -/D [259 0 R /XYZ 56.6929 247.0271 null] ->> endobj -50 0 obj << -/D [259 0 R /XYZ 56.6929 212.0137 null] ->> endobj -301 0 obj << -/D [259 0 R /XYZ 56.6929 185.9542 null] ->> endobj -54 0 obj << -/D [259 0 R /XYZ 56.6929 141.8097 null] ->> endobj -302 0 obj << -/D [259 0 R /XYZ 56.6929 114.9182 null] ->> endobj -258 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F98 231 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -305 0 obj << -/Length 7113 -/Filter /FlateDecode ->> -stream -x??]]w#7r}???C4'V????S]???ox3{w7kx??e=???=og???_?quwxs????????[????}#??f??j#?W?????????k~?j%??v???L??]??;?ei?=+D?;?????,gK?7WeQ??}??( ^?l?pU3?Q4??f}???_?G?W^U???W??4?@]7?5k??`e?&???c%}?? -??P[??u???5" ;V?}_????ox}?Q'??????????????mw??j? MW?asX????5?,???v?????0_?????dF????qe=+??Z+&O_Y ?]Y???g{eY?_/?[uMY???????????????q?0v???,?????????7????????????????a?????dJa?5????????z7??????7??W?????&?????v???? ??=??I????!???O??x8??.b'{H-?cwF????Mw??,Z??K[???e"??????Uk??????vL???/??????`"]????? ?w??? ^??q4j???????/???8?ltu?P?.??(?R?Y+ -9?????j???E?}S????????Xh?>d1??)Y? q?M???+;??]?2?nX?xW?^??XD~???m?]t D?u??????Q ~R!??26???,K???8>6[#??g?[??x???`L -i??OV"0???0?S?0?!?(???(\?&~|o -?&????e?E?gcO?G~?????H?T???B????)???????[{ -^????l?A???x???h?\M??????]?-9`?????? -/es???2`??StE?z? ?j??Z?&??_??-???j9?????:???????o?????(??}?x???? V?@?#????#? -???Mz?F?vC4?yC?l??' -??[{????C?Q?u??????lH]}?q?hT?m?5?l???d?N??[m????????JF????0???Hn???>Pvn???%?V-??J?? -XQ??? -??K?h?????????Z? B??d$??&??*G-&=??J???H????U?^?????/Y?W??(?2?|?m?Z????'???Z?9DE?$cO?G~?5??????0?=?&?}v????????1G?1?G5j????????S???/:o5 v????????m[?????????FiH???h??'. at +???+???M??=c-??x?.?q?iG6r?5j?????Ft?S???G ?????7??3???TW?~f????P?cW?a????:=?o??????l????v?.v??{?K??J~????xd/?B??Z? )?Z????_?????R???n???(K??????!?????????R?????W????????a????x#3?Y?????e????k???^_???u?S?l?Bz????_?V???0? ?:I?C5???Z?R??S????,?:????+????I-?x????vCh??8??8????f????O??z???9,?2v?|s??v -?[tZJ?? -???]^#+ ?'? ???Z -??7????O????g?eY?f?8^M???K?????T+;U??K?^???3?,/?H???v?{??/Z?????@??hU?1"pOfC??>7Wz????????7??I?7????>C?????'gp??[F????=i?Si???]???????(CWz? ?Jo,G??F?]??)???y?^??/~??2?.???^?9?7?Jo???8f?[J???|???t??p?Ks5?vZ?Q$?xTu%??????o?^&????$??????v???n?(=??}????Mb??8 ;??pv??|v?a?A????r?p?A?Op~H?A?37??33Z>????cz7F??XcW??o???????@???u?M>h??J?l.[c^~\?2????J???m??[^tB?y????vg???i?:d?V?n?u?&?|zng -????/$??DH??*y?? ??a? Qwe???o??a??,;1"?L0{?V???PV?N1?????6? .??^??~%s%o??????????8?M[T5og?'?MYkx?S?? ????x???;?.??????I?????*??f1???r????????Pvp??????i??fvF&(iS^??H?/P??v?9?o??????? .?S?(????B??????n?(???i?u??'O?#4?50?!??;???y=??U????u? - ?.E%???p?9?????u\?_-????f??vB ??????????8?????B?????w??w?*??????V?E?3} -??-?}y-?9I^???6?K???????????2??????iOio?@??????nXl?7??7z/???hB?_????W?v8m??????????}?o????"??y?q?????&?~1???s?????6???Q?????????x]wf??!P???U!K?R-??????gD?^WAl??F?c9?zF5%????? ?M4????? -?????D???U??+k?D?A???y?-??\???t??gIh7????q`??>0"??r??y???(84f9r???w???}??yM?? -V*?O?w?WVG?#? -??j?L>y -??J ? -????u?cp3#??uq???ir?6-Z??=?????J???yQ?S{)???S??E??L?k????????A#vsp???d???%3f??99)?????p`??B??????N^????+tS???34E??L??;?v????K???W-??????Vv?ZfN?7 -??p ?yX?^??m?(P? -<?;R~e??/???.v????[??fx??????M?`?(??m?#??|??Tr/???????????fp???dCwUK^?^5D?????0??h??"????h?r#??ZY??u?????#????K???l?????kY?_6*?.R?T?d[R?Zi)?????????cG^?a??????????8?VS?e)X?G67?9??ks?8????<~?/l??????a#_?a?>??mS???????????REX??[W????LV~f?O?p???wnV??a5_??6q?????a?F?a???N.=??(??b???????D??X????6??P\??|\??9?w???????????????"??4-??SWs??iY?????c?p|8(`???&?k ?????`i???V=o?9????=???hV???=?=?K_??rff?-?? ??? +?[u?????a> ???G???????~????~0????V{???e?e???(?`G4K????e??k??????-?F??`?#[}????8=??AL?b?77?s??S?[r/???????q?p??NM,??5XuH@?U?$.????oR????H??(?M?B??????("?}?u?!;q?agh?t?O??(????\?#??t9 -jd??\?g???z?5C??;?"G?? ??azI?'?QHP?~:?2-?????8?R?OF?G??8?tx??2<+nO???c?? ???r?K?O?U?(D?\????m??D??j?????g p???>AL?????87?>7Z?????I? ?.?3D8B? p?? p? Q??2T??P?e"=TX?, -??6-?Q\??}\D??9:wB???P?H?O??8E??>E\?ci??8?k?x?\?????(??o?$~^L????????????????">/n?6??#??z??.?FtD?L6?Z????&?????D??+?? ??s?????? -?y???I?J?U>C?? ??w?k??`Q????m?+?>???~m?? ???????8?'??> endobj -306 0 obj << -/D [304 0 R /XYZ 56.6929 815.7613 null] ->> endobj -307 0 obj << -/D [304 0 R /XYZ 56.6929 759.0684 null] ->> endobj -308 0 obj << -/D [304 0 R /XYZ 56.6929 742.9638 null] ->> endobj -309 0 obj << -/D [304 0 R /XYZ 56.6929 711.0834 null] ->> endobj -310 0 obj << -/D [304 0 R /XYZ 56.6929 681.1955 null] ->> endobj -311 0 obj << -/D [304 0 R /XYZ 56.6929 682.6549 null] ->> endobj -312 0 obj << -/D [304 0 R /XYZ 56.6929 671.696 null] ->> endobj -313 0 obj << -/D [304 0 R /XYZ 56.6929 660.7371 null] ->> endobj -314 0 obj << -/D [304 0 R /XYZ 56.6929 649.7782 null] ->> endobj -315 0 obj << -/D [304 0 R /XYZ 56.6929 638.8193 null] ->> endobj -316 0 obj << -/D [304 0 R /XYZ 56.6929 627.8604 null] ->> endobj -58 0 obj << -/D [304 0 R /XYZ 56.6929 590.7101 null] ->> endobj -317 0 obj << -/D [304 0 R /XYZ 56.6929 563.1566 null] ->> endobj -318 0 obj << -/D [304 0 R /XYZ 56.6929 529.3186 null] ->> endobj -319 0 obj << -/D [304 0 R /XYZ 56.6929 530.7781 null] ->> endobj -320 0 obj << -/D [304 0 R /XYZ 56.6929 519.8192 null] ->> endobj -321 0 obj << -/D [304 0 R /XYZ 56.6929 508.8603 null] ->> endobj -322 0 obj << -/D [304 0 R /XYZ 56.6929 497.9014 null] ->> endobj -323 0 obj << -/D [304 0 R /XYZ 56.6929 486.9425 null] ->> endobj -324 0 obj << -/D [304 0 R /XYZ 56.6929 475.9836 null] ->> endobj -325 0 obj << -/D [304 0 R /XYZ 56.6929 465.0247 null] ->> endobj -326 0 obj << -/D [304 0 R /XYZ 56.6929 454.0658 null] ->> endobj -327 0 obj << -/D [304 0 R /XYZ 56.6929 443.1069 null] ->> endobj -328 0 obj << -/D [304 0 R /XYZ 56.6929 432.148 null] ->> endobj -329 0 obj << -/D [304 0 R /XYZ 56.6929 375.9587 null] ->> endobj -330 0 obj << -/D [304 0 R /XYZ 56.6929 375.3609 null] ->> endobj -331 0 obj << -/D [304 0 R /XYZ 56.6929 364.402 null] ->> endobj -332 0 obj << -/D [304 0 R /XYZ 56.6929 353.4431 null] ->> endobj -333 0 obj << -/D [304 0 R /XYZ 56.6929 342.4842 null] ->> endobj -334 0 obj << -/D [304 0 R /XYZ 56.6929 331.5253 null] ->> endobj -335 0 obj << -/D [304 0 R /XYZ 56.6929 320.5664 null] ->> endobj -336 0 obj << -/D [304 0 R /XYZ 56.6929 309.6075 null] ->> endobj -337 0 obj << -/D [304 0 R /XYZ 56.6929 298.6486 null] ->> endobj -338 0 obj << -/D [304 0 R /XYZ 56.6929 287.6897 null] ->> endobj -339 0 obj << -/D [304 0 R /XYZ 56.6929 276.7308 null] ->> endobj -340 0 obj << -/D [304 0 R /XYZ 56.6929 265.7719 null] ->> endobj -341 0 obj << -/D [304 0 R /XYZ 56.6929 254.813 null] ->> endobj -342 0 obj << -/D [304 0 R /XYZ 56.6929 243.8541 null] ->> endobj -343 0 obj << -/D [304 0 R /XYZ 56.6929 232.8952 null] ->> endobj -344 0 obj << -/D [304 0 R /XYZ 56.6929 221.9362 null] ->> endobj -345 0 obj << -/D [304 0 R /XYZ 56.6929 210.9773 null] ->> endobj -346 0 obj << -/D [304 0 R /XYZ 56.6929 200.0184 null] ->> endobj -347 0 obj << -/D [304 0 R /XYZ 56.6929 189.0595 null] ->> endobj -348 0 obj << -/D [304 0 R /XYZ 56.6929 178.1006 null] ->> endobj -349 0 obj << -/D [304 0 R /XYZ 56.6929 167.1417 null] ->> endobj -350 0 obj << -/D [304 0 R /XYZ 56.6929 156.1828 null] ->> endobj -351 0 obj << -/D [304 0 R /XYZ 56.6929 145.2239 null] ->> endobj -352 0 obj << -/D [304 0 R /XYZ 56.6929 134.265 null] ->> endobj -353 0 obj << -/D [304 0 R /XYZ 56.6929 123.3061 null] ->> endobj -354 0 obj << -/D [304 0 R /XYZ 56.6929 112.3472 null] ->> endobj -303 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F90 192 0 R /F52 139 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -357 0 obj << -/Length 4253 -/Filter /FlateDecode ->> -stream -x??]???????q(/pfI?????y!???Eq?Z[???\I?fQ?? _?^?o????"HD??? -9ORZ??(??VQL??g??E$?Y????????b?f??66?_?^?????2??<^???bN??F??&$?x?z?{?????w???gu????~???V) ?& @?? -c$?".?F0,I??????/???XI?H???????t??9|sEI??lu7??0c??U???\?9\?x??????! i???&2??\?$???p~????0?5?????d|?]Q?p? X???|?????+????????]?Zm?????7?^w?qn?F?n???P???c??V?~???????????h??QC?F?|??P???O??C?Z27?l??|, ??BE?*?!o?Y -2???l??Q???o -?????|? ??)??J?????n??l?? -??+!?C??????k?g?/?"A????wu?V????y????kN??n4z[W]??JcJt]??kn?????f,?}Ww?"?? ????O4??\?????5?????K???DX??*z??1????u ??C\?????AI??*'??M?c|??RKhgw????}?we?2?A?Y??JF=??k??;H?E??-????? F?_?-Q?7 pS*&TOE?????7?O???!V?6E#?4???E??)M??)hoSNPcS6(?/? ??r,???<???^???????A6?hZyy? ??F?JS0?Z????????h?Q???>WJ^U????~?? ?3Y?Y????8t???Z?????? jt??:??@???-?o2?`?Pk???????????????z?U????P?WO7?RLqQ"3R???4?r4???-????b'?J?"??*??[S?e%Y!{?;?\?!?????D??"?e??k?H?Ah?"?F>??e{W?[?H?pLeH c]??? -?? ??p?"????MtP?"???r?????7???H?y?S?]m0%?A??Z??:WV???0 -9??yR?M?pM?uh?NP?6(,??z?2?/2???M??2c??`??3? .?;???+??'\??Y???t??)???f*???V&?????5;&?o??????U~?Q?|{???? -?A(????a at nJ???Z??H?????.+-?_?X?uu???b}gr?6oUK?nSS????????u??6YW??)??Z -????Da??6?d???cN?????Y??>?A?O4U????9????$?B???y?M?T9?????R???U1Wq?jE -?- x??b9TJ??T?~????Z?8?? -????9?6??]?? ??I??C%e=H??zIBm,I wB?dIw'?"c?p?2?l@???d??Sx??SMa'???7o?R??o!? -????????????j??g??kq?????d! -m?eK??e??mR?)_ I?L??~Li~?7?nWo?l??????D??bA?7?? -????Q??oU?R??????4g?}?UVeWb??p.??~)??aL?8??PoS???W??$?????p??AS?GnLE???B????W??HR???4"???[?2??????????N?R) ?)?????>??+??Ta?ua?h?3Z??DTEXq|_??L????,w??h?O ??S -BW??J6~?s?0?i?o?????.c??79d??&<]????E??}???FCCq??h???S????q;}???6j'????j?????O ?Dm????y??"B??N??M?rx???=66?0??KR??~?? ?.??$9K M??)L?s????>?]02I?8l"^DI??[/??h~I;O?v? \3AC????O4j?????P E?-????P]&??G??Z?p??j???l??f????S4???E?t6:1???/]???'?1?O?c??:xY ??pc?|?n?? ?SP????8???N{??c??Bu?gQ]PF?A?r???;,[?j*???@??GOn? /??????'?c?????I_z???c??9z?xI~???[xC7??/==b???O?1????i????t??{???X??4y ??-M8??Z???`fk?W??w?fb?-??)?e{wHg??x? -?????/?<,f????????-M8l^S?m?????y?l??m??>?]?I???*??? -??F??t???????-M8?^S?+`[???u??[@/???"?9?+??I_\;?? ?/??o?,&???JqNi? u? -.c0T^?17?$?/o0?????X.?Qjs?Vy??,?>??/?H0?d??$?.o:???"7?"????w?6??-??c??].G? -.x????S.???\?D?????L{??KR??\ ? ????D4?V??a??0?4 ^>n{??3?*???????@[?c?????:??T`?@8?t?5r?O???2?D??)?*?>?:?#?-?v?s??????E?t?oUL?v??=?cn??????%,?xSP??'|????9???:?6?g????9???x?Zq??v??E?s69??9??/?'i?????R?#?h*?U??A??^? 2??,????d??)_?A?????Y? ??? nQLq????.C?2?t???A??pAq?O?z2?s?}????y2??s?3??d??=??M~,??t??|q??p[??R|?y??%?]}?9????n???s????n?)7q?=M!?f???{??|g -??????3eE???B??X6?K????|)??t?T?(4????I??v?]N?>i???????q?e??$J?\N??9???:?&?I?)??????S??>)$J1??????={?\????C??ht??5?OI7Z??????i?9}?cn??WF?????[}?i???+OM???3 -I??????????????e?|o@?T?>???,6=G??_9[]qendstream -endobj -356 0 obj << -/Type /Page -/Contents 357 0 R -/Resources 355 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 382 0 R ->> endobj -358 0 obj << -/D [356 0 R /XYZ 56.6929 815.7613 null] ->> endobj -62 0 obj << -/D [356 0 R /XYZ 56.6929 465.1132 null] ->> endobj -359 0 obj << -/D [356 0 R /XYZ 56.6929 436.1462 null] ->> endobj -360 0 obj << -/D [356 0 R /XYZ 56.6929 410.4223 null] ->> endobj -361 0 obj << -/D [356 0 R /XYZ 56.6929 390.5382 null] ->> endobj -362 0 obj << -/D [356 0 R /XYZ 56.6929 358.6989 null] ->> endobj -66 0 obj << -/D [356 0 R /XYZ 56.6929 328.8596 null] ->> endobj -363 0 obj << -/D [356 0 R /XYZ 56.6929 303.1056 null] ->> endobj -364 0 obj << -/D [356 0 R /XYZ 56.6929 280.7073 null] ->> endobj -365 0 obj << -/D [356 0 R /XYZ 56.6929 282.1668 null] ->> endobj -366 0 obj << -/D [356 0 R /XYZ 56.6929 253.0585 null] ->> endobj -367 0 obj << -/D [356 0 R /XYZ 56.6929 255.3499 null] ->> endobj -368 0 obj << -/D [356 0 R /XYZ 56.6929 244.391 null] ->> endobj -369 0 obj << -/D [356 0 R /XYZ 56.6929 233.4321 null] ->> endobj -370 0 obj << -/D [356 0 R /XYZ 56.6929 222.4732 null] ->> endobj -371 0 obj << -/D [356 0 R /XYZ 56.6929 211.5143 null] ->> endobj -372 0 obj << -/D [356 0 R /XYZ 56.6929 200.5554 null] ->> endobj -373 0 obj << -/D [356 0 R /XYZ 56.6929 189.5965 null] ->> endobj -374 0 obj << -/D [356 0 R /XYZ 56.6929 178.6376 null] ->> endobj -375 0 obj << -/D [356 0 R /XYZ 56.6929 167.6787 null] ->> endobj -376 0 obj << -/D [356 0 R /XYZ 56.6929 156.7198 null] ->> endobj -377 0 obj << -/D [356 0 R /XYZ 56.6929 145.7609 null] ->> endobj -378 0 obj << -/D [356 0 R /XYZ 56.6929 134.802 null] ->> endobj -379 0 obj << -/D [356 0 R /XYZ 56.6929 123.8431 null] ->> endobj -380 0 obj << -/D [356 0 R /XYZ 56.6929 112.8842 null] ->> endobj -381 0 obj << -/D [356 0 R /XYZ 56.6929 101.9253 null] ->> endobj -355 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -385 0 obj << -/Length 5016 -/Filter /FlateDecode ->> -stream -x??]{o?????ba?u???)??????????@?4(?^???}??'????%?C%va?*?????f8?pDg??d?%-'?(?M?7gxr#??????%??Tysv???I?JA???r"(9?????4??Y????[-?3??????/W????7??G???? -???\B?!????? -?X^L/?a?????8??XyI??PR?z???,???a??????0?YI&?3N?%??Y??>?G??~K3?????a?R>? ????????N}|??$+?(a????(????,=?%???@\??L??^1????d&/?\??V??????????x;Mz??o????m^lA?d3???FO??????Sb=25\o?Tj|???r??\vu?WW2?X^?I?D?2.GiB.K??k}? -??G??!+?%e)?4Y??z?^/V??t?D9?i???x?JK1????u?W?>??|?`?'?1G =????q&?H????????;?g `??T?;Q??kY?@[??J?xY?yY?????????%@?7????LhN?+V.t???^??,1?kp??????????????(|?](????fuh???np?Q?q? -^??>??%?2?????X?XWa????????????|?*?????@9??????A???????????7????k?]???i?8????b?=??n?[}%c|?q?=V??O??j{cx???????????>}?:?????W??nSi?:??~???.V??!????ko??v=_m5?V?? )? ??|!?????.??????3OW?????7?x??^??????K???iot?????????|?U???j_m?jW???? ?a??]W???oo???\?k?Mj???:|:4?4????_??k}????)3?+??w:?????BGQ?w???j?}q?y????Mu?8????l? -????? -!/???~z??m???????w?????Z??ZT=w????k????-?????????????x--??^????L????1u?:?W????>?F~??????|???????? ??z,?;s??O?+?4???w8??nS????`+[???g????h? -??92?8H-?l:\N_?6$?j1????3"??4?fH?K??AV?R???/??Wmm?????E?3?M?5?q?#???L~?L^?T?Sj?=?1???d??T??Zs?]?$T?u-???=??;=??s??^??[?????nt????V?2?_??? -??\?G?????E?????1?b ?Z?????????-??}3+`?,YK.9Q???@2??K??X[?z??????H at o -?vk(-?p#?(????? C??d? -~?s?b?7????$??r?n??*?9+F?=z?A^[%}f2T????R#?????e?????y?fs"Z?-e?]?d??aX?????c,???@??c^??wt?????'?J8G???????W?J????i!u5????E?6Q?H??tJ?lJMW?]?^??K????)?4]?j? v?&?6jh[???c?????p|?!RYQ??????7?Y ?[??!s? -FE?El ??8????????n9>?@j{ ??,>x?-?Y?)?E/ l??K??e?RX ?q???R?PnFowT -???q?o\?????X^e???R?;6>?????r?????ww??????X???(??,?c?? ??A??[?????????????O?|?{6???7???????`%??'?>G????a>??n???Y??l??? ???? -??????p?#?e?x^???)?Yl??????M??=??^?Yt?????'?s?d|????!??SC5w?6|?w?6??????x??%?f?X-W?"L??DY?DBw?2!??kI?????OaF???{O?+???????C?|q\?5 -6??8??!?:aew=? *??L??????p??C?v???@?[Py??s?M?m?R??!? ?????P? -y??5f?"C???(X??2??X0tb??Po?r?&??P??+/>F}O%??]+?)X[??~???y??{ f?S????3TF????]???a???X???F_ |?FK???/}2{&0?RL0f??Q??,??????M? -J?N??D:?nw8L?j?5?1/?|??Oh0? -?%?%R]????F?S?U??9??????q? -V 7Z??q?????3=zg?,xVK???r??G?V?,{??P6?4??v8???C?~ $??Q%?Cnp_?????????}????-?k???=w-`?,YK.???H??@P2{??%Y<?????>=FOe??RZ9O??uT. -??X???gyQQ?,??8?H?????? ??R???????x?W?W???s -???rM?I???"??????????7?AXu????????>?.?O?j??????L????>?l92???????O?yw:?????9??no?=??-)qB?P?SA?O????>n\S >E3*?^????4n?x-?9???????????V??3????v??u??>?mX????N????RC?????8WkH-7???Z???;_|?????n????e???&;??}?9??m???????k??'?????iSm???????^??3???;L?;G?? -?= ?n?y?????? J6?????f?b|??0v??V?F??i -?zpQ|?? K??B??H1R?(?i?? ??BJ?HQ?C???S???h?J$??1?,??7???q?m??????K?0?*?p?5??F??4?> ?? ?1??L?2f?b?????-#??)?j?%? - 8sT)dMW$???|????5]>?8.?'???????q??Db7Df??0?C?]N??? -??!?.?z?n?????U???$?3sC?5w??y0???AH7kCfh&?Av??l?L??\t??3SCr5u? ?< -???A?.??$=?? -cw?F??p??????? ?????53` -o^a?? Y???Y???Al7'???0Q?] ?W???8?8?????TN-`*$?8?k?>?@? K?2.??????X??9?^??? 0??}7?`??&QK??L!????l?aE?????Z??????-????J?$?m??4???i?Y??XM??i?????/?7?ut1??'?3x??,ZG??????oA/X4[??-Z-ZI?y)?z)2Z}Em??hv??}?>?Y???*??}???????>?????'\33??U8?wu??EY????A?o???"-?LwT?YIWo????n?4??9_??f~?????? ??L@???B~??y?P\(?fK?%?%?Z?\o???b??`8??!7???? ?????0na?{???C???F{r????????[??????Z?????????o???a????p??_k?9Tm?^???????d6?yS????'??t???7??)x?^???U?&??j[?n??_m?.9Tm?^?????-?H~c??SO ? -Q -???.??,?s?C???)??o????j???3?????m???;?& -T??????7???? -???R?@n??vE??*??%?5]??N?>k??@????P9?????mN?~uv?'8?]?c<.*??_3??S??6?D?E@?\??????6? ??R????? -??X?oZ???'-|HuV?. -???`$k#;??z???!?jHZu!?A?g?xL?????}q] ???????u???M?]C???? f?S?Z?????K??;?G??f -G??_?W??endstream -endobj -384 0 obj << -/Type /Page -/Contents 385 0 R -/Resources 383 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 382 0 R ->> endobj -386 0 obj << -/D [384 0 R /XYZ 56.6929 815.7613 null] ->> endobj -387 0 obj << -/D [384 0 R /XYZ 56.6929 759.0684 null] ->> endobj -388 0 obj << -/D [384 0 R /XYZ 56.6929 752.3934 null] ->> endobj -389 0 obj << -/D [384 0 R /XYZ 56.6929 741.4345 null] ->> endobj -390 0 obj << -/D [384 0 R /XYZ 56.6929 730.4756 null] ->> endobj -391 0 obj << -/D [384 0 R /XYZ 56.6929 719.5167 null] ->> endobj -392 0 obj << -/D [384 0 R /XYZ 56.6929 708.5578 null] ->> endobj -393 0 obj << -/D [384 0 R /XYZ 56.6929 697.5989 null] ->> endobj -394 0 obj << -/D [384 0 R /XYZ 56.6929 513.8231 null] ->> endobj -395 0 obj << -/D [384 0 R /XYZ 56.6929 515.2826 null] ->> endobj -396 0 obj << -/D [384 0 R /XYZ 56.6929 486.092 null] ->> endobj -397 0 obj << -/D [384 0 R /XYZ 56.6929 488.3835 null] ->> endobj -398 0 obj << -/D [384 0 R /XYZ 56.6929 477.4246 null] ->> endobj -399 0 obj << -/D [384 0 R /XYZ 56.6929 466.4657 null] ->> endobj -400 0 obj << -/D [384 0 R /XYZ 56.6929 455.5068 null] ->> endobj -401 0 obj << -/D [384 0 R /XYZ 56.6929 444.5479 null] ->> endobj -402 0 obj << -/D [384 0 R /XYZ 56.6929 415.3573 null] ->> endobj -403 0 obj << -/D [384 0 R /XYZ 56.6929 417.6487 null] ->> endobj -404 0 obj << -/D [384 0 R /XYZ 56.6929 406.6898 null] ->> endobj -405 0 obj << -/D [384 0 R /XYZ 56.6929 395.7309 null] ->> endobj -406 0 obj << -/D [384 0 R /XYZ 56.6929 384.772 null] ->> endobj -407 0 obj << -/D [384 0 R /XYZ 56.6929 373.8131 null] ->> endobj -408 0 obj << -/D [384 0 R /XYZ 56.6929 362.8542 null] ->> endobj -409 0 obj << -/D [384 0 R /XYZ 56.6929 351.8953 null] ->> endobj -410 0 obj << -/D [384 0 R /XYZ 56.6929 340.9364 null] ->> endobj -411 0 obj << -/D [384 0 R /XYZ 56.6929 234.8692 null] ->> endobj -412 0 obj << -/D [384 0 R /XYZ 56.6929 236.3287 null] ->> endobj -413 0 obj << -/D [384 0 R /XYZ 56.6929 225.3698 null] ->> endobj -414 0 obj << -/D [384 0 R /XYZ 56.6929 214.4109 null] ->> endobj -415 0 obj << -/D [384 0 R /XYZ 56.6929 203.452 null] ->> endobj -416 0 obj << -/D [384 0 R /XYZ 56.6929 192.4931 null] ->> endobj -417 0 obj << -/D [384 0 R /XYZ 56.6929 181.5342 null] ->> endobj -418 0 obj << -/D [384 0 R /XYZ 56.6929 170.5752 null] ->> endobj -419 0 obj << -/D [384 0 R /XYZ 56.6929 159.6163 null] ->> endobj -420 0 obj << -/D [384 0 R /XYZ 56.6929 148.6574 null] ->> endobj -421 0 obj << -/D [384 0 R /XYZ 56.6929 137.6985 null] ->> endobj -422 0 obj << -/D [384 0 R /XYZ 56.6929 126.7396 null] ->> endobj -423 0 obj << -/D [384 0 R /XYZ 56.6929 115.7807 null] ->> endobj -424 0 obj << -/D [384 0 R /XYZ 56.6929 104.8218 null] ->> endobj -425 0 obj << -/D [384 0 R /XYZ 56.6929 93.8629 null] ->> endobj -383 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -428 0 obj << -/Length 6847 -/Filter /FlateDecode ->> -stream -x??][s#7v~??`6y?T, ??;?+???e?j????????C?2/#?R???qm4?9b?Iz?v?!O??;?\t????/?%)??jV??d?l?pAgw???.????BW????_??????4%/g?og%'eE?YM+?5??????????v?????????????_?? .e?Z\Zf????D=?b?4E??K+qYU_????L^w??? -/M?j? -^KV?^?? ??~??$oj6{???? -?=\L|?J??Y]???????9?i]????????EQvB?????3???jtv%?U?k?3N???gL???l??n??????(???Q????????. g? -J???/???????w???Oc7~????emn???wo.??N,?!y??n??|q??g?\??l?*?+HV _??kRe %??q???a~??1.??Xr?2R???}?/?L?J6l???F??vv?9'U?? -?,* -???????j?????E??9??M?^?-??_S?B?,x?h)?S??????+y?h.??W????_?3?. "?????8?3??]?k/V?????????????!=??@T??\????c??1V@????G?C??????U??F - -??{\???+?m??(|'7??????]??h?]l?u\0?q\h??????d????S]?v?5?yQN^??x???t?/?d?H?????3R4`$??)=y%1?h??c`T1B?q??????h?????n?Ud???!??VR -7?+?^_???3??? - l?YcA?m?:K??f???MXm? -??[^[<*9?i????x?h??xR???%??#???`?@[b???-1??u??H???r=_???????wX?????m????AR&f??????UT?E???????u?'???Jx????????Dx?b??e???E?6??????d?Pu?o1 -?,?}DFt?j????4??4??FTs??? -1???^]c?d??1?JQ? $WY??0?@???f3????V\???????"M#??o3???0??????S?m???r??o77?E{???\??Y?R????su?|???J?=???C?? _??z? -??m?Hx???{??A\$???+?????b?_n??7?? ?m]Z??R(??l?E Et1W??????V??/???????????????????????a???ln???l???,T+ ?? ??????HS>.o??y??j???OW??????};W4?????????N???^+??Q?W???S??[???????h?{??U??????j&?????????:2????_K?????f??/w???5?ZP)???i???s?vv?b?v?Y???+?D+V4??c??M??? \]???u?{1????????k??vsX+?}????yx???_????????+????]^???~?????????$?%9,??????????{-????$??b???U?Y?O?x?????az*??|-?o?p?D !?]&)?5EEh?u???????o?8???@^???????????c?H?k??????????7??????\?????D????p?(u??}??:1?w?????n??B??"?Z4??Jaq?????N?r?0i!VNGI???!NH???????-????8O9?#?k7T???J?@?? ??u???i?%??D???????x???# ?R?c?w?p=-sB???F'????"????.?????????t??f1?F?x?+P?@W7??u4?5?K>?,wF??41???T???C?f?;?.???=??W?s??nD???!??*????????M?????0=*w???!~??)|??O?1???N?1*#?6`PZ\???W?mG? -??a?7]m?8?????A??????>???:f??Go?@F?IpH???@?????????"???0|?????>?Y???V?m??0?@???!f?J??fc ?6??F??a?"??"Z??F -?u????? ?U???t?td?g?Fqt??#i??????eE??W3W?^?^A?#????%>???`???e??mm?d#????z?>?{??9}?N??E?Xlp??y???r????[??x????v(u%79r?Z?????+?W??????L^3 ?5@?y? -C?M%?Tvf/.?V??dV? -???}\???????IrVK???ON?P?????J?*ZZ?Bx?"? -?.?r?x?T?c??2????f??)????????@J?i???????4?Y5??omk??u?F??h?%?????n)J???3WW??????? -x??V????o???}??????Aj?F????Py?z?n?I?].??sxt{Ajvf????????` ??f[?????=$m?p????9?juV?fu f?W?\???>???yI?Bcm&\?O????2?Yi??$??YHri?5?-{?g}???] ?Y?? ??XM?r?\?oc????F??}{?;???<>/????8????|????!??%n??G????%? -?]??=????a???6\??????LJ?Qbt????e?S??=n?? -iU\?#B/?a?j?????qKt??4A??????$n3?????wON/???/???]>???;??Cm????2Bi?????Gx?z#?+c????Bf/? -@???[???y??jJ\??????jh?$?Z??'\???h???????g?} -G>??P?O,xT?'N?c?X@?? cTF?X?A?D? ->?p?????n???:??)#D???d -???9??}J -?b??????n?@?????7?????????=?-? -????????|??????B0{???$?? 1j?????????=???????S????????Re?pWB?h?????????? ?0?A`=??????+? K? 8?$???iH??DC?0?k?_?yh??F? -+R??}???|???W?S?6??| $??P ? ? -?.(\?G?\a?n8?? 6??D??{?"? -???;??}??AmQ?{?v??'?1?`:C??8xD???@[???cI??j??g??N^_K????nL?? 1??]f???(??a*???T>??????q_{> endobj -454 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [55.6967 391.8345 314.7523 402.7384] -/Subtype/Link/A<> ->> endobj -429 0 obj << -/D [427 0 R /XYZ 56.6929 815.7613 null] ->> endobj -430 0 obj << -/D [427 0 R /XYZ 56.6929 760.0646 null] ->> endobj -431 0 obj << -/D [427 0 R /XYZ 56.6929 749.1057 null] ->> endobj -432 0 obj << -/D [427 0 R /XYZ 56.6929 738.1468 null] ->> endobj -433 0 obj << -/D [427 0 R /XYZ 56.6929 727.1879 null] ->> endobj -434 0 obj << -/D [427 0 R /XYZ 56.6929 716.229 null] ->> endobj -435 0 obj << -/D [427 0 R /XYZ 56.6929 705.2701 null] ->> endobj -436 0 obj << -/D [427 0 R /XYZ 56.6929 694.3112 null] ->> endobj -437 0 obj << -/D [427 0 R /XYZ 56.6929 683.3523 null] ->> endobj -438 0 obj << -/D [427 0 R /XYZ 56.6929 672.3934 null] ->> endobj -439 0 obj << -/D [427 0 R /XYZ 56.6929 661.4345 null] ->> endobj -440 0 obj << -/D [427 0 R /XYZ 56.6929 650.4756 null] ->> endobj -441 0 obj << -/D [427 0 R /XYZ 56.6929 639.5167 null] ->> endobj -442 0 obj << -/D [427 0 R /XYZ 56.6929 628.5578 null] ->> endobj -443 0 obj << -/D [427 0 R /XYZ 56.6929 617.5989 null] ->> endobj -444 0 obj << -/D [427 0 R /XYZ 56.6929 606.64 null] ->> endobj -445 0 obj << -/D [427 0 R /XYZ 56.6929 595.6811 null] ->> endobj -446 0 obj << -/D [427 0 R /XYZ 56.6929 584.7222 null] ->> endobj -447 0 obj << -/D [427 0 R /XYZ 56.6929 573.7633 null] ->> endobj -448 0 obj << -/D [427 0 R /XYZ 56.6929 562.8044 null] ->> endobj -449 0 obj << -/D [427 0 R /XYZ 56.6929 551.8455 null] ->> endobj -450 0 obj << -/D [427 0 R /XYZ 56.6929 540.8865 null] ->> endobj -451 0 obj << -/D [427 0 R /XYZ 56.6929 529.9276 null] ->> endobj -452 0 obj << -/D [427 0 R /XYZ 56.6929 518.9687 null] ->> endobj -70 0 obj << -/D [427 0 R /XYZ 56.6929 480.7463 null] ->> endobj -453 0 obj << -/D [427 0 R /XYZ 56.6929 444.5815 null] ->> endobj -455 0 obj << -/D [427 0 R /XYZ 56.6929 368.9204 null] ->> endobj -456 0 obj << -/D [427 0 R /XYZ 56.6929 370.3799 null] ->> endobj -457 0 obj << -/D [427 0 R /XYZ 56.6929 359.421 null] ->> endobj -458 0 obj << -/D [427 0 R /XYZ 56.6929 348.4621 null] ->> endobj -459 0 obj << -/D [427 0 R /XYZ 56.6929 337.5031 null] ->> endobj -460 0 obj << -/D [427 0 R /XYZ 56.6929 315.5853 null] ->> endobj -461 0 obj << -/D [427 0 R /XYZ 56.6929 304.6264 null] ->> endobj -462 0 obj << -/D [427 0 R /XYZ 56.6929 293.6675 null] ->> endobj -463 0 obj << -/D [427 0 R /XYZ 56.6929 282.7086 null] ->> endobj -464 0 obj << -/D [427 0 R /XYZ 56.6929 271.7497 null] ->> endobj -465 0 obj << -/D [427 0 R /XYZ 56.6929 260.7908 null] ->> endobj -466 0 obj << -/D [427 0 R /XYZ 56.6929 249.8319 null] ->> endobj -467 0 obj << -/D [427 0 R /XYZ 56.6929 238.873 null] ->> endobj -468 0 obj << -/D [427 0 R /XYZ 56.6929 227.9141 null] ->> endobj -469 0 obj << -/D [427 0 R /XYZ 56.6929 216.9552 null] ->> endobj -470 0 obj << -/D [427 0 R /XYZ 56.6929 205.9963 null] ->> endobj -471 0 obj << -/D [427 0 R /XYZ 56.6929 195.0374 null] ->> endobj -472 0 obj << -/D [427 0 R /XYZ 56.6929 184.0785 null] ->> endobj -473 0 obj << -/D [427 0 R /XYZ 56.6929 173.1196 null] ->> endobj -474 0 obj << -/D [427 0 R /XYZ 56.6929 162.1607 null] ->> endobj -475 0 obj << -/D [427 0 R /XYZ 56.6929 151.2018 null] ->> endobj -476 0 obj << -/D [427 0 R /XYZ 56.6929 140.2429 null] ->> endobj -477 0 obj << -/D [427 0 R /XYZ 56.6929 129.284 null] ->> endobj -478 0 obj << -/D [427 0 R /XYZ 56.6929 118.3251 null] ->> endobj -479 0 obj << -/D [427 0 R /XYZ 56.6929 107.3662 null] ->> endobj -426 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F52 139 0 R /F92 225 0 R /F96 228 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -482 0 obj << -/Length 308 -/Filter /FlateDecode ->> -stream -x??P=O?0??+nL??wv|?A?? -5[???n?Hh?*?=.IZ?Z? ????{??0??????H??a???= -?9?@J?ns1~0^zV ?XI?h????+ ?j?L????`rW??E??y>?R????????AJ$?1?[????d?=??:q???????6??z?9?*?0(3?1@?2O???W?2????s?U????+n??m?/;N?e^????%tf????G?$?r??R???z????Qv?*4?}Y??'EB?a???z? ^??? -?nB??vs?D?qsm/m???q???oz?8t?????endstream -endobj -481 0 obj << -/Type /Page -/Contents 482 0 R -/Resources 480 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 382 0 R ->> endobj -483 0 obj << -/D [481 0 R /XYZ 56.6929 815.7613 null] ->> endobj -480 0 obj << -/Font << /F50 132 0 R /F51 135 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -486 0 obj << -/Length 3502 -/Filter /FlateDecode ->> -stream -x??[K???????!U?T?0???????q?dw|H?>P5b?"e>vv????H?"5k[???v???n4?~???_?P??X???+f4??M?x??/o?????V?Y?=??}??E?b-??a???i?E??,??,?;?z???????r]?=???LE???????T???<'?v?WS???O!X?? ?e!04 #40 b{??gX?=??-??<`,???b???}??2??????)??j j??????????S?]L????T???!???lV?<?? ?b9???!??? Ud?G?e?m?TY3????=^/J??u(???f?????f[??y:?????W?z8z(???f??m?d???v?o?4?N????9?_M?/??dq?9?+& y?q????\????uG??M2???X0??/ -???D??9K3t?2Z6??B?p1?~???g?r?[)??,?z???p9??????4-?.kF?UjY????????v?~?]?????(???#/??y;??|???8 ?3P0?? ?????d???????????????? ??3q3? -,???I??1?????`B??/??aA???`/BG`?r~- PF?&???mb?????? ?????$???????\?N7e?K0 ?l?$s?g??????T????j?????????r?K??????-^????\! -0s*??E??Z$?2??Z????:?o:???;?? -?I????55 fS?x/????????C>u?bC????zc? ?^?^??]??????bA=e??L???38?SqXl??K]lj???<ZP?N`]3?????????? ?0#?X?C6????P?Ue??e?a??Q?>P}??{????x{??[?/?;:???|????w]$?s?OH-t)^8?!?F?u?{?*??%bN?3????w?O???*]8?????>?H??&T1yJ9b?_n????`???????????#? -g&?'Z@>?wt???>?\b????T??Mi?uz?x??1j??.O?n?%??_b?W???e??(Hr???k:?Vn?|????E?z?S?-????rD???{?????Z`?$?cG[[w?????.?? $????'??u?W??lf?h??{}?a?K?KM??!??;?^?Ll -??=?l?????f?8?rw?O???]??????n?1-?K?t;??u??????+???P??a???9 ???O8? ??,(??*!0('??,???I? -???.???G?W??????{zp??@?nT????r??S(??? -0?.??????'_?eTB??p??T??c????g??['~????'??/?r?3??x??}W^????L??????$X@???????z?????x?endstream -endobj -485 0 obj << -/Type /Page -/Contents 486 0 R -/Resources 484 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 382 0 R -/Annots [ 492 0 R ] ->> endobj -492 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [204.0186 316.2483 223.1566 327.1523] -/Subtype/Link/A<> ->> endobj -487 0 obj << -/D [485 0 R /XYZ 56.6929 815.7613 null] ->> endobj -74 0 obj << -/D [485 0 R /XYZ 56.6929 553.0513 null] ->> endobj -488 0 obj << -/D [485 0 R /XYZ 56.6929 522.509 null] ->> endobj -78 0 obj << -/D [485 0 R /XYZ 56.6929 468.7561 null] ->> endobj -489 0 obj << -/D [485 0 R /XYZ 56.6929 440.3707 null] ->> endobj -82 0 obj << -/D [485 0 R /XYZ 56.6929 409.4559 null] ->> endobj -490 0 obj << -/D [485 0 R /XYZ 56.6929 372.4592 null] ->> endobj -86 0 obj << -/D [485 0 R /XYZ 56.6929 372.4592 null] ->> endobj -491 0 obj << -/D [485 0 R /XYZ 56.6929 345.105 null] ->> endobj -484 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F57 148 0 R /F52 139 0 R /F90 192 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -495 0 obj << -/Length 4141 -/Filter /FlateDecode ->> -stream -x??]_s?????????pd?w3M??4/I{??C?Z?m?$??????? ?A?h5??4???$r??],???Y`??,x??????p$r?-V? ???{?/??Y??K??????q?(Q??|q}??)??? ??T,?o?????;\-)???6???{?????(Y?h??G??HZ,????s?=K0<(??7???'/?????DIP??q?????~??[??? ?XY??|????,????,????????z??.e???O??!Z? ?y??+?\??F?A??k6??!??3D??TJ?p?y??&9f%?"_????y\????<`?%4K?s66m?S??xU??G?????[?s}E??g??zu?"?V?I????????? -^?? ????C\?9????????H6Tr????=??%?.?0k?j?C???d?C?bPcC????J??j NB????*??F???>?+??o7?r)V???)??-XR8C7n???}?@8??m'Lb?R??i??$?b????)x?o0"g? ??g?2????!???U?F????f???#??tE?-9D??S6=?3d??kr?$????n?Q??jv?zw?)ys???t???>n4!?$??!?w?????ev????7u0??s???????A?zi"d?)?T??vK%?????????;'(#\???zVs???Z.?T??????4?:r?/`?????????i? -3????;.??[????tC.&???IH?M ??F?Ld^6?>E??'?1iy?UrH?J?'E?A -U -T??C??hf?y^?G???f??}{??-?BK?????\&\???9??????n??s+&:?????????X_'wC??";?K??&zA??Rr????)??g????b??S?8?IM?5?????? -??^???]B -???????"N??y6%??+????????? -?Ev?4???4?t??@f???*????M????38???5/?4q??*???M?d???]?????j"s+0b?C3???~&!??{???83`??7?&!??7??????{z? -w?4? -^\???F??? 1?BM????(-P!??@??????0??"I??????xO?n??N??y6)?C????>????(g at q?8???8?t??E?x??K?)?1??|?.??zDz 1????????H ,S? ?*??s???rL?(??mb??????rl??O?fsXo??c}?D???I?!L??}E??(?8??5?=?,G??b?BQ??'??\%???=!@^ A????&:?43?a?Xn??^-?9M?h??????qvL? -???F??/ k 1L\s??X??/?.Q^.?h????f??(??J????F? o&???N\? ???????8?v?EBC?????j?a??~??Ap.O??>??J??D?dA8??x??T)LE7????i???q??g??j??m????T'???????`>??? -?"??C???)??8??? ?c????(??????b??=?w? !F`???I?g?!'?B??"s|? -?????_??;M???????f??????????C?})??x??./??3???g??tt#Q6????????q?T#??'D??? ?1???X.??G??C????????m??????o?m?:4????????Jy?? -?9?`?"i??L?? ???? -c?+????5?7aG2S??y$???p???cpOMT?~OM??6??]M??u????????n_????m,q??????M?D:?s???g??z??i???_K????f6?????F?W4???????J-????1\???c6?<"+??p8.?"U<@???x@(`?b?\?p?????.p?????|m?????????oj}??????I?;4??}}PL???w???^]???Eu?.H??+???-?Z2Z^?K?%?????f?(U??T???jw?6????t?????G -??KJ.?`??k?\p??????U} bZ -?fN?I*????]??Zp??;????7I2?T???Sw?f?ZV???W?????nx}??? ????V+[????Z?????m???V'?>&?w??6$_0*dW???Z9? ?L I)b?K*JTpS(??[1}?? ?K?????J???F?%???+WL??M?B?? -?Q??L??4r ???????p????(??u{?~s[??????>??%??%t?C?[???K??D?4?M&??LM?yM?m? f??/?$??|;k?wa??wqqX???Z[7S???%???[?7??iD?????}n?op??????GeR?c?????Oc??????"??9???<(+??;xC???i?j??A: #?s??????`?uNy?S?? ?Wc?:??(??-???> endobj -496 0 obj << -/D [494 0 R /XYZ 56.6929 815.7613 null] ->> endobj -90 0 obj << -/D [494 0 R /XYZ 56.6929 759.0684 null] ->> endobj -497 0 obj << -/D [494 0 R /XYZ 56.6929 738.4887 null] ->> endobj -498 0 obj << -/D [494 0 R /XYZ 56.6929 716.6059 null] ->> endobj -499 0 obj << -/D [494 0 R /XYZ 56.6929 718.0654 null] ->> endobj -500 0 obj << -/D [494 0 R /XYZ 56.6929 671.774 null] ->> endobj -501 0 obj << -/D [494 0 R /XYZ 56.6929 673.2335 null] ->> endobj -502 0 obj << -/D [494 0 R /XYZ 56.6929 662.2746 null] ->> endobj -503 0 obj << -/D [494 0 R /XYZ 56.6929 651.3157 null] ->> endobj -504 0 obj << -/D [494 0 R /XYZ 56.6929 640.3568 null] ->> endobj -505 0 obj << -/D [494 0 R /XYZ 56.6929 629.3979 null] ->> endobj -506 0 obj << -/D [494 0 R /XYZ 56.6929 618.439 null] ->> endobj -507 0 obj << -/D [494 0 R /XYZ 56.6929 607.4801 null] ->> endobj -508 0 obj << -/D [494 0 R /XYZ 56.6929 596.5212 null] ->> endobj -509 0 obj << -/D [494 0 R /XYZ 56.6929 585.5623 null] ->> endobj -510 0 obj << -/D [494 0 R /XYZ 56.6929 574.6034 null] ->> endobj -511 0 obj << -/D [494 0 R /XYZ 56.6929 563.6445 null] ->> endobj -94 0 obj << -/D [494 0 R /XYZ 56.6929 526.4941 null] ->> endobj -512 0 obj << -/D [494 0 R /XYZ 56.6929 498.9406 null] ->> endobj -98 0 obj << -/D [494 0 R /XYZ 56.6929 383.4193 null] ->> endobj -513 0 obj << -/D [494 0 R /XYZ 56.6929 355.0339 null] ->> endobj -514 0 obj << -/D [494 0 R /XYZ 56.6929 215.6368 null] ->> endobj -515 0 obj << -/D [494 0 R /XYZ 56.6929 215.0589 null] ->> endobj -516 0 obj << -/D [494 0 R /XYZ 56.6929 204.1 null] ->> endobj -517 0 obj << -/D [494 0 R /XYZ 56.6929 193.1411 null] ->> endobj -518 0 obj << -/D [494 0 R /XYZ 56.6929 182.1822 null] ->> endobj -519 0 obj << -/D [494 0 R /XYZ 56.6929 171.2233 null] ->> endobj -520 0 obj << -/D [494 0 R /XYZ 56.6929 160.2644 null] ->> endobj -521 0 obj << -/D [494 0 R /XYZ 56.6929 149.3055 null] ->> endobj -522 0 obj << -/D [494 0 R /XYZ 56.6929 138.3466 null] ->> endobj -523 0 obj << -/D [494 0 R /XYZ 56.6929 127.3877 null] ->> endobj -493 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R /F98 231 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -526 0 obj << -/Length 5323 -/Filter /FlateDecode ->> -stream -x??]]????}?_???a?Ua??^?^?i?iR???}H???????P????{@|$@??^?U>?8?!?p?? t??t'$??|???? e???*???oo????+??i??????q0?I??????, I??, R??0???~?????X???qp????t?????{8??285a??( -IJ?l6???q6?R -'????????y??V3S?????????? f+???W????????QNg????!KB??????????aD? ???A ?x6O????hs;????AQ )?f!??,?U????# ??T?|????9?%N??w??l?gi*?????[!??y?Ie??8K??N.?+pl?@???~&~r??4?$bQ??O?A?A????6?C`S.???P?]?1??f3??>???4?Q~???BS????????c?*??,?1?J??Kq??0?$"a????@???P????G?s?n??r[X @?h??????p?]?U:OH????J+{????*???O! ??????V?]???a??????zk{?_.??4??O!??e1Roe?[?q????S??h'???Un?A???? ?`???k+ ?*???YF?FW[????r9??????wG???%$???_wm????9????Y?$c???1x?\?,???,iN?;??++ Z?eX???dI??G???? ?qXl?izX???|?nz???? ??? -??*bj ????A?k?[]?c"?L?aJRg2????????Fy??D@????y|?? A??'??*??????? Ix?X>?w??z\/a??jH&Ap=?????!b|hC?DL?????????8???b5?S?K?O?r??4???????y??6n?,? }???N1K??t?u?? -G???????N*??$? ?????`?B?i.%???\??w"W??????!?W*??TI?=B?EE????????H_????>7>????9S?$?B6t?m????y?F?]?(?H??s?????????r?q}?z??"? v??s????v??YN ????^???F(??b???????EC????&?????5yB?.?s????($i?g a"O?????5j??Fz}BI?/@ZF?pq?*? ??????f`???eD?oDM????A??p???]|)??z??M?R????l??U??????[W;D|?P?L??????)EzOQ+?f???"????????e?0;?\~?????sN6?;YRK\T -P??FW?}?$?t???gK??&?$??JL????z#?????_,?, ?!??F,??? ?????+?????r 4????q?)??C -?f??)l??i!?????8??#?zva?~*?^?K?!??t????`,???UW?????^??Qi?zT??E?2?c?N?????t??m ?( ?$?????0?]?}=?????+??Rz ??????????\?k?#B?8Gj??0h??F;o?x????K??????EsU?????T?(>?T???????`???c+?xl??????y??`????gT??=???????????K?.??????BC??IU?????%dc ????R??R?N#x??G??'a?????Nh??O??h? ?[????????a?=????^VZ????>?? ????z??:v?g????^??O??e4I??>+?^VV?>??????)?&?vb4_?? L??~.?[??u#??%???1?????(???N?OA(? ???4????&?a?v?^??w???C?L?O????^N????9DZDYL?????? ??????V?????4???[a?????0u??g#4f??????&?D4e???????.?????;9???~jv??7wv)?|??z?'FE???C???#=??@ ???????)???cJ???K???(LCB?????qhM?????????o%PVO?? ?=?;???\X?#d?]?e??\X??????TJ???9??y3?a#????^?3???XXg??:???.m`ca?!?jmh?^??&????*????;??Vi?w???"c??/?`??r7NS???[ki?????UX?m[g?fA??EvV????F???Ks???????{?\?????UX?;?_s?&&?*?]s?I????M?1x??q~xW?fA?????p???]??&?#??nj???M?qu?[????7?E????\bc????lt??=??????S.j????????!??????? ?V'?????b[?????,????????p????1???$?oJhm????_?? -l?????=6?;B~?`{?l????????p>oKTh???endstream -endobj -525 0 obj << -/Type /Page -/Contents 526 0 R -/Resources 524 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 557 0 R -/Annots [ 530 0 R 531 0 R 532 0 R ] ->> endobj -530 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [342.6799 664.3934 440.3138 675.2726] -/Subtype/Link/A<> ->> endobj -531 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [55.6967 562.6401 130.2369 573.544] -/Subtype/Link/A<> ->> endobj -532 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [306.5539 502.9987 440.0533 513.8778] -/Subtype/Link/A<> ->> endobj -527 0 obj << -/D [525 0 R /XYZ 56.6929 815.7613 null] ->> endobj -528 0 obj << -/D [525 0 R /XYZ 56.6929 759.0684 null] ->> endobj -529 0 obj << -/D [525 0 R /XYZ 56.6929 752.3934 null] ->> endobj -533 0 obj << -/D [525 0 R /XYZ 56.6929 470.0323 null] ->> endobj -534 0 obj << -/D [525 0 R /XYZ 56.6929 469.4545 null] ->> endobj -535 0 obj << -/D [525 0 R /XYZ 56.6929 458.4955 null] ->> endobj -536 0 obj << -/D [525 0 R /XYZ 56.6929 447.5366 null] ->> endobj -537 0 obj << -/D [525 0 R /XYZ 56.6929 425.6188 null] ->> endobj -538 0 obj << -/D [525 0 R /XYZ 56.6929 414.6599 null] ->> endobj -539 0 obj << -/D [525 0 R /XYZ 56.6929 403.701 null] ->> endobj -540 0 obj << -/D [525 0 R /XYZ 56.6929 392.7421 null] ->> endobj -541 0 obj << -/D [525 0 R /XYZ 56.6929 381.7832 null] ->> endobj -542 0 obj << -/D [525 0 R /XYZ 56.6929 370.8243 null] ->> endobj -543 0 obj << -/D [525 0 R /XYZ 56.6929 359.8654 null] ->> endobj -544 0 obj << -/D [525 0 R /XYZ 56.6929 348.9065 null] ->> endobj -545 0 obj << -/D [525 0 R /XYZ 56.6929 337.9476 null] ->> endobj -546 0 obj << -/D [525 0 R /XYZ 56.6929 326.9887 null] ->> endobj -547 0 obj << -/D [525 0 R /XYZ 56.6929 316.0298 null] ->> endobj -548 0 obj << -/D [525 0 R /XYZ 56.6929 305.0709 null] ->> endobj -549 0 obj << -/D [525 0 R /XYZ 56.6929 294.112 null] ->> endobj -550 0 obj << -/D [525 0 R /XYZ 56.6929 283.1531 null] ->> endobj -551 0 obj << -/D [525 0 R /XYZ 56.6929 261.2353 null] ->> endobj -552 0 obj << -/D [525 0 R /XYZ 56.6929 250.2764 null] ->> endobj -102 0 obj << -/D [525 0 R /XYZ 56.6929 212.0539 null] ->> endobj -553 0 obj << -/D [525 0 R /XYZ 56.6929 175.8891 null] ->> endobj -554 0 obj << -/D [525 0 R /XYZ 56.6929 150.0412 null] ->> endobj -555 0 obj << -/D [525 0 R /XYZ 56.6929 130.1159 null] ->> endobj -556 0 obj << -/D [525 0 R /XYZ 56.6929 98.2355 null] ->> endobj -524 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F90 192 0 R /F92 225 0 R /F96 228 0 R /F57 148 0 R /F52 139 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -560 0 obj << -/Length 4741 -/Filter /FlateDecode ->> -stream -x??]]s??}????>H3L??W'qf?&n??Ik?/i?-m??re7??? xA???3??4??W????X????W????????hV5/XU?|???e????3>?\B?????.???.K???(??V?????"gM}(U.??K?R?T6^??B?D@??MS,!??????)???.Dv~??????????????zs?????g?g}~???O??yq{?O????n??????????????~o}????????????O!????_?6??f3?;?[????n?? ???Q??????vG3"???????p????????_??^??? ??v{R?<:??y!??0?B?D?&???ANC??Ca??/??B?Y? -??O???N?y?????]o?8????}?t??]??~????5/^???3Z????7??Gzb?k8/4?/??W?hU??? -?K?!?9??I???f}?gD?^3?{?Rd,k2?s?b??9???/ju?9uw??]w??l?????????8:h{8?O?????c?t??j;???}?????????$7?q?t???? ?t??q?????????]??v????j??L??"K??a????R?d??K=E???d???J????W?n?f65?f?I9gBp??????4?*?,C?4????F^W???Ak????%??????2 f??~t?O?????$[oV??_????a?*k?ek2???? -Q????O???s5??|5????T/?F???ZP ? FC8??f??k??.8??@P?6???Ys??$?2???'?????|?n?\S(@??( -??????A?!<+?yC< ??UK??}???/?&?Sjg? -??a~???3??=?????j???n???PT/>?-f8???2?a?g3 -?g#f?4????w?j????k?T????? -???,k???I? ?$??W??u??,??Z??? hC??e ??D?&???Q?s????E?V???p?6???? m???L?l?Ix7??o????]?6j]?6?,Y???|f?(x/[?}?????{??S?&N?}????7??Y? -Y?m?g 2WkD??4????}?????? -??K"0G????MGUo]+zqd???????;)^ tR?3?g?K??N????n???????fQ?6?@ust.Ugde??????52??2??????A??+??)?pe*?1?B^???a7z??y^?B??b???e=??Ck????,s?+????v?5???l? -?v???=??:??y?.5?Q{?M??K??J]???????'?y??????"?r?2????x:???????A??|\3O?b???^V?T_??D7? ??3j?'?????v?R?:Jx2?qTk????:O??ne+?u9??&s*wk2?`2/??:<??????????Em?T???&????W?}???L^????0??O???z) -??!g?c???? X/[X?????<8? ??????????.N-p?E]?T??e&????)-????%1??(????Q+)????$??7j????8?LM??~ -?!?B*Y??7? ? -K?????~?]??e?=???h???Bd??~??H{}? -??? ??p *vrR?:B??}u?a???,A?#]1??(?U?XgL"??x??]N? -p>???&*??f???H???X????1??????1???? ??:??@???-??^.????c*?????Q%g56??&??(?t5???2???6 -?ts????n:?????????Z[?o??????????DAg=?Hg???z?:?? -???r??x??j????9?q???????Q=?p????????m???????8??U????Mg??MG?ra??$??td'????u??n:(?i7???*?T9OE-<?,?C??fsq?3?@N`B ????#??]m???X?c[???G9O?????5?S9[???7????e<???~6|??D?SU9????u?E??O*?b????E???OH?&.4m?Q??mMo?????Y??]2q?'??????qM??V??Z???C0?9?~??q?Y?RB?_?wnJ???|?????o???s?0?TDy ???,[?xF!?L??????g??I??6???Y?y??? &? -V????38?~?w??:?'??qpp7k?t?_?A??_??1?\?I??$??-9????g??Y????8?Q?8[x,2??}??@??c???t?;??????e???eTMB????SV?? i????? ?A@??????????L?@j?^?&t??lj?yg{????>??)#???Ztendstream -endobj -559 0 obj << -/Type /Page -/Contents 560 0 R -/Resources 558 0 R -/MediaBox [0 0 595.2756 841.8897] -/Parent 557 0 R ->> endobj -561 0 obj << -/D [559 0 R /XYZ 56.6929 815.7613 null] ->> endobj -562 0 obj << -/D [559 0 R /XYZ 56.6929 759.0684 null] ->> endobj -563 0 obj << -/D [559 0 R /XYZ 56.6929 732.2374 null] ->> endobj -106 0 obj << -/D [559 0 R /XYZ 56.6929 702.5053 null] ->> endobj -564 0 obj << -/D [559 0 R /XYZ 56.6929 667.2187 null] ->> endobj -565 0 obj << -/D [559 0 R /XYZ 56.6929 648.7762 null] ->> endobj -566 0 obj << -/D [559 0 R /XYZ 56.6929 650.2357 null] ->> endobj -567 0 obj << -/D [559 0 R /XYZ 56.6929 639.2768 null] ->> endobj -110 0 obj << -/D [559 0 R /XYZ 56.6929 604.5727 null] ->> endobj -568 0 obj << -/D [559 0 R /XYZ 56.6929 578.7294 null] ->> endobj -569 0 obj << -/D [559 0 R /XYZ 56.6929 544.1788 null] ->> endobj -570 0 obj << -/D [559 0 R /XYZ 56.6929 545.5039 null] ->> endobj -571 0 obj << -/D [559 0 R /XYZ 56.6929 504.4775 null] ->> endobj -572 0 obj << -/D [559 0 R /XYZ 56.6929 505.8025 null] ->> endobj -573 0 obj << -/D [559 0 R /XYZ 56.6929 466.699 null] ->> endobj -574 0 obj << -/D [559 0 R /XYZ 56.6929 466.1012 null] ->> endobj -575 0 obj << -/D [559 0 R /XYZ 56.6929 426.9777 null] ->> endobj -576 0 obj << -/D [559 0 R /XYZ 56.6929 426.3998 null] ->> endobj -577 0 obj << -/D [559 0 R /XYZ 56.6929 385.3734 null] ->> endobj -578 0 obj << -/D [559 0 R /XYZ 56.6929 386.6985 null] ->> endobj -579 0 obj << -/D [559 0 R /XYZ 56.6929 345.6721 null] ->> endobj -580 0 obj << -/D [559 0 R /XYZ 56.6929 346.9971 null] ->> endobj -114 0 obj << -/D [559 0 R /XYZ 56.6929 312.2931 null] ->> endobj -581 0 obj << -/D [559 0 R /XYZ 56.6929 289.04 null] ->> endobj -582 0 obj << -/D [559 0 R /XYZ 56.6929 270.1143 null] ->> endobj -583 0 obj << -/D [559 0 R /XYZ 56.6929 271.4393 null] ->> endobj -584 0 obj << -/D [559 0 R /XYZ 56.6929 230.4129 null] ->> endobj -585 0 obj << -/D [559 0 R /XYZ 56.6929 231.7379 null] ->> endobj -118 0 obj << -/D [559 0 R /XYZ 56.6929 197.0339 null] ->> endobj -586 0 obj << -/D [559 0 R /XYZ 56.6929 173.7809 null] ->> endobj -587 0 obj << -/D [559 0 R /XYZ 56.6929 138.6325 null] ->> endobj -588 0 obj << -/D [559 0 R /XYZ 56.6929 139.9576 null] ->> endobj -589 0 obj << -/D [559 0 R /XYZ 56.6929 98.9312 null] ->> endobj -590 0 obj << -/D [559 0 R /XYZ 56.6929 100.2562 null] ->> endobj -558 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R /F90 192 0 R /F57 148 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -593 0 obj << -/Length 1322 -/Filter /FlateDecode ->> -stream -x???Y??6???)??rQqIJ????J??(z?@?6e?l)?/??0?Rh??>?FQ?6m?????]?;q??4L?;??V/?|?????w/ZJ&????-i??H??,c??}??? -]??}?J???1??}9?^H?????B?>7?j?? ???f -~?*?j????????3??P]?T???:?? ??b?Ao~dA???????T-tgQ?:???dPgwx???-??nE??-1?TB|????b?d??z??$?lqJ?l?K??h|(?z ??????> endobj -596 0 obj << -/Type /Annot -/Border[0 0 0]/H/I/C[0 1 1] -/Rect [170.804 721.5872 284.337 732.4912] -/Subtype/Link/A<> ->> endobj -594 0 obj << -/D [592 0 R /XYZ 56.6929 815.7613 null] ->> endobj -122 0 obj << -/D [592 0 R /XYZ 56.6929 759.0684 null] ->> endobj -595 0 obj << -/D [592 0 R /XYZ 56.6929 738.4887 null] ->> endobj -597 0 obj << -/D [592 0 R /XYZ 56.6929 712.6209 null] ->> endobj -598 0 obj << -/D [592 0 R /XYZ 56.6929 692.6956 null] ->> endobj -599 0 obj << -/D [592 0 R /XYZ 56.6929 672.7703 null] ->> endobj -600 0 obj << -/D [592 0 R /XYZ 56.6929 652.845 null] ->> endobj -601 0 obj << -/D [592 0 R /XYZ 56.6929 632.9197 null] ->> endobj -602 0 obj << -/D [592 0 R /XYZ 56.6929 612.9945 null] ->> endobj -603 0 obj << -/D [592 0 R /XYZ 56.6929 581.114 null] ->> endobj -604 0 obj << -/D [592 0 R /XYZ 56.6929 561.1887 null] ->> endobj -605 0 obj << -/D [592 0 R /XYZ 56.6929 529.3083 null] ->> endobj -591 0 obj << -/Font << /F50 132 0 R /F51 135 0 R /F52 139 0 R >> -/ProcSet [ /PDF /Text ] ->> endobj -606 0 obj << -/Type /Encoding -/Differences [ 0 /.notdef 1/dotaccent/fi/fl/fraction/hungarumlaut/Lslash/lslash/ogonek/ring 10/.notdef 11/breve/minus 13/.notdef 14/Zcaron/zcaron/caron/dotlessi/dotlessj/ff/ffi/ffl/notequal/infinity/lessequal/greaterequal/partialdiff/summation/product/pi/grave/quotesingle/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 127/.notdef 128/Euro/integral/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE/Omega/radical/approxequal 144/.notdef 147/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe/Delta/lozeng e/Ydieresis 160/.notdef 161/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis] ->> endobj -230 0 obj << -/Length1 1647 -/Length2 8562 -/Length3 532 -/Length 9439 -/Filter /FlateDecode ->> -stream -x??weT???.?-8$@?F?????? -4?44nA?C  ????@?????????s?????3s~?u{?????T=U???????TUg?BMA?P[GVvA?2b????(CY?@N??&6?'???V -2qCm?MA?m -2pr8?iRP;7???@???????????&S? O?` [???3?j?:>Q???A ??%`??TTu?????(k??lA??"T?Lm?fE????0??6-fP[ ?wi?O\??? ??r5????v ???? ;,`&??Og??m?l???x?7??I?}????V???e?"??????? -n?v?? -?=mD6?[?@?????3q???6?? ??'?i?{?+.!??e??Xx?f?{?L??? ?zt??C???C at si????ke$aN5^y?????????{tw?? ???2?F?? -9#>? ??O%{?Y????XS?s,??g?????>?0q?riz7?Q????? ???K??`4???J??|???????\??I??f-}n??n?y?S?e????:n???3? {?? K?Sw?PB[1[[V_U?i??sMw????R????.????R?????5nL???7!{?x0R.EVX?Jc{?4???&>/??g?U!?P?????q???e+?(???{T2/?`?????{)GrU???n??vM???????R????:??2w??h?g?????|*^w??A??h?????\s??&??o? -kU???Nq4?j?@?[?`?P? |+l?a&?^??? -??o??&??3?o?k?]7??--?9?o????????uxg??<^???E??!?????k???(?zy*?\?%????_?Re?e?????y|?(e?????c`2???j@????*??b??~N???NHE?r???????=??B&?M????#w,i??b??i??qJ??D?I?p?{?????g?kkf=;gd"D?5?\??????5?N????oc D??w???5.E??j6??,A??O?????iUn??2??z?q*??uZ???>??a?!?S??????^??/???P?$??n???U??%????]r6?p??????:??P?t,5? -@???}u -??????1~?$2??f???NH?H?2??3?????-I?????}????X?R??????6jSn4???i]D?r???????>???j?Bm????m(? ?%_???x@????w?u??m??Fd?|:?2??=????+?V???.??)?.? ???2???c,c?????8]?1U[?^?? ??=?y??0!Uh?/"H??,??Vy\????:??q?cI?-???oYL???-9?[?E}{??&[? ??N(??A??1?????? ]{?Xs? g???G?????l??0?? -?????]????,u/?????_?????QY)?{5??5Q??n#????????H5k?x ??L?Q1 ???qE0???I"???? ~8F9"????UP??V?e=????I??D^4?^,??YZg??S[g??9f3????8T? ??=|v???XW??????????;??? ??????272?????????l-=??w???fJ?-?J?;?7?F????[?????_?l???['Y?-9????wCA???Fb?C??\?M?? ?0???r????????`??gOp.??????`,?????!b-h??x(1W??)??q????5???U?S?je at Q?dXUy????4???jD??(?????{j"s??J?v?f??yl???`8,?,/x?Q#?h^??y???,3????% ?7F ??|???R_?????I?XG??w w??-t5???zb?K?\?]w????J!?+t??D?9&???K?)6??????h ???bL?????4??y' -'??$?3?^??t??I&DHj????????U?Tf?z?? 7?x?C.i$Qd?????q?{?{????s???+?[?nm#??16)??? -???S{???%dj???n2HT?K??%Ovp?{&?B????~?W?F???m~4D.??Qk?5??Y??? -?W ?h??Lc?HO???h???F?? ?R9???\???*v?? 4??yX?V?]O9 ???u;=?h ???6? -???0.???9?)?OC?>?k??AK35????%???j??~???*(?X???])????P;??w91??H???????6.??????C??v?g?Nm????;???????[??d??%?#4q! -??&???v?R>m=,??$Q?+?&i9H0? SU?{???<?)? -c|???L7???#???oE`??XL?y?4???v?`??1sFV?{R9???G? -\/???TV?R??8????????Z??oP?&80??J??????{\??????5??????5`-?1???????[ ??@X?{??g,?A???Q:??B??A?:*??H'???w?1???[?7??? -????&?%?H???kgr?,??? ?V?2??^(?\?????.4? ???C??????n?Y??r?h?(4??k??"??o??X?Ws??}?k"?V????OX\h????MsZ???q?9??'????u]x??X??7]?g&??????}??;?b8B?9???W???} ?n0i????.v ???7???? /B? ???D?h~?},,Fp??,c?:]?Jzb?h?E?F??7\pNNf)????Zy*T??0?????H??y?C????|?[o,E?;LD?qA?????????8'-??z?? -A>H| -??i?5$S???4??Q???DJ???l???/, -k??? -?&?>??a?????e? -???i?\???#???U????t?s'2Z_?? -Q??I|??_???????qA\2?N?#'?On???U?(z?h;\??p?????v??G?6???? -???gS?T8a/?O?n?}????&?????nN?L????#fM????^?\`?39$?$5?+??? 8JB@*????$?;?4??"??Y?7?h{A?B?,?l??I?1??%??$??)?y??B????? ?KN???????wK?????????:??o92? q%o??O1R???s??V???3P????????r?PJ=)??????2???A^?? -y`}?]K,???}??&?k?i???? #??:]???)w?/?]????? ?\??????^9l??I??dp????F) ??f[g???Y???_?P??? D???s'???UB?l??`E?????/U.??p?rB??$???????;He?m?????? - -,? -?+:??s~????Zo!9?`?D~fb??b?xx>f;???2??w/p>~?B?LR_?h?R/?????????rQ???7V"???????Yt(???????I????%??^o??cF??Z?P? -j -?]a?X??=??? ???????E?q?=g??0 ??Ui ??.?????e??*??B?J -?1*?H??h??KM??????t?]?L??G???~?.?rq} ?'????p -???)???6????????????>?A?J????o???? -??zM?*?_?wf????u ?zn?????????|_z?s9???s ?G9?4"??)?dk?????EO%{???6?sH??.l*?'?Q??E{_???x??????aW??gcVc??O?????5 UynM?a??z????*?uU+???5Q?s 7#?? j?? ????N?5a?????P?i????????bh???@@? ?? -f?vcm ])???9???}??@?S????'??H??X7?.Wo??1???[Q?,w?2y4?D?n??"??3X??D???M???&???x?y?5?c????? ?(?E????FM7???????mY=P?? ????#x07?|z?9"?U?}??f4[????/?g???????j??/? ???J5?? -~?u)!?2??E???Ae??????@?j????x??`8O??i?j?f??? ??d=?e$??d??3r????o????f?g?E*? 8 -G?????_?8?`???bwKr?="1?|???Y^w?-??%??????????Vv??e??g+?e?:??c:?G??????? ?-???/v?{????0IZ/?fQ?V?????cL???~u?? ??q??f??5?????????g?G??~kd?? ???&??W?U?_?-j[?Rc/??of????:C????|u??^W?? -t??N(T??\z_????N??}?!??ky?7l??? -?Q?E?D#????????M????}?KU???:Y?J?<[F?L??P??^0]??_`?(Mtz`?J?$??????=2"?r??????[u??}????R.????z?2???????????????????v??LM?p?\???|t?a??eXN?O??*w?W|?:??7??E>'?[???>????AVOl?Cq?w???????l'?????*IQ????B2??w???j?XB??]?fi?.????"|NDZj??|???K?? L?-9??h???f?? q?Fh?R&????`4\c??~???s??lf????E?!??i???N+?? s?`/???? ???O??x??.???e@?~?`e'??????7?GDd?O??cYup/{qCl?3R1??>8(?#.?Y???????.g$u(??Qt$???Z???s?$.??Is?t?xp???? ??Wr??+?G\??'????p?1,??????`???o=?2 "??o???8?{???:?fT??j?]0??????@;?} -??"f??:$w;??? H0??>\ -???????S???N?{Q]???~??+aX????p?#?L2I?.??P??I??Xk??-????,?mf}HWS?8?N7T???5????%?8?2k????Eo????Nk?jrA???a2???r?j? -?kM ????%8w???e??? ?????@??? 8????l????????R/??RWg????}7{?? ?P\?6?\?g?M?I%????w??G??????>???$?K??? ???i?~?,W????_?r?^W/n??2U?IJ?'r5??Wpz "v??xx????u?Y?4?I??PO??LQB??????`p~kxP??%WO\e"???j$A ??J??6??UD???v?W???I?j?|??iQ?BY?^sK??????N??????1? -M???????????K^1Q???75???.6??M???????X?o}Pt??????T????N@%u????.'n????QIU??????O?~f?_=}!??p???;????R??u(l??R??y??? u??o??(k?W?'??(I??%*2,_?-zI?:bz?x??Y?s#?9F??????GP?7U8R??G?0????9?&"?;??_??c^?x2?%???Id&,?L*0?????9????^?v???7???lv6?*??`93???[??!?????pk???Cqcr???F??YBJV??????O???? -??????????C?endstream -endobj -231 0 obj << -/Type /Font -/Subtype /Type1 -/Encoding 606 0 R -/FirstChar 2 -/LastChar 120 -/Widths 607 0 R -/BaseFont /SEIUYP+NimbusRomNo9L-ReguItal -/FontDescriptor 229 0 R ->> endobj -229 0 obj << -/Ascent 669 -/CapHeight 669 -/Descent -193 -/FontName /SEIUYP+NimbusRomNo9L-ReguItal -/ItalicAngle -15.5 -/StemV 78 -/XHeight 441 -/FontBBox [-169 -270 1010 924] -/Flags 4 -/CharSet (/fi/hyphen/a/b/c/e/f/g/h/i/k/l/m/n/o/p/r/s/t/u/x) -/FontFile 230 0 R ->> endobj -607 0 obj -[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 444 0 444 278 500 500 278 0 444 278 722 500 500 500 0 389 389 278 500 0 0 444 ] -endobj -227 0 obj << -/Length1 761 -/Length2 1025 -/Length3 532 -/Length 1574 -/Filter /FlateDecode ->> -stream -x??RiTW?S -??P%.?!F?H6?P??D#DQ?EA3/0&?????h???*??TQYTZ??(Z??7???????VPk??)?l?t??w???w???c9?G?KPb?8????? X.??y???x +????d??b????4?<?[,? ?,LhSI,1?????7?h ?)?* jh???T*H?j0??#????L?(???SP`L?p?G? W??M?i??R ?L???2????:?P??N'?i???o??K.????M}?S? -?N}? 4ZI 'PH?}????89D1??oUF!jL!????=9qd?F|??x7?_?????5??????h+??v???r?v_?}?w!??z??kW_???Zz??????????pX???????[?E???ax\n???ff??F??OrD????????c???g???5:??????????????GB?R/???7?6!?Ls???*+ -Y?I},?U*?x???=?????G?6r3????c"?$k????????/ -8dl at M]=N?-{? )?????q?6???????ii??k????g????,"?6d?1???gMStv?!Ug???{?97N??D??;?u.~1{???1???3p???^i??c??[7w???BM?# uliB]?N&??q?S'?T??X-?X;_?/2Fq?[?x9Sa??b?}#p? |???n?[?u?N?\???r??????????????????Nd?????.??n*?X;?D??????mw??u&;?Y??A??????3???=?4?7???> endobj -226 0 obj << -/Ascent 694 -/CapHeight 683 -/Descent -194 -/FontName /ILEVCY+CMMI10 -/ItalicAngle -14.04 -/StemV 72 -/XHeight 431 -/FontBBox [-32 -250 1048 750] -/Flags 4 -/CharSet (/arrowhookright) -/FontFile 227 0 R ->> endobj -609 0 obj -[278 ] -endobj -608 0 obj << -/Type /Encoding -/Differences [ 0 /.notdef 45/arrowhookright 46/.notdef] ->> endobj -224 0 obj << -/Length1 753 -/Length2 637 -/Length3 532 -/Length 1177 -/Filter /FlateDecode ->> -stream -x??R{PTU.? ??+ z?!T??]\?G???B?k#1?r??????x? ??kP?2J"|?pJ?B?X?gE?0? ???C]P? ?????????????????*????aM?|T??R?T B<= ?X???`, ??? -dz -@%@$ -?$R?(?d#CjX?N?~?$2dH??c????1-P?8 Y???Z5???` -dR!!@P$??x?!)D8?(?R?@?p??'??R!????8??g??)?P??h?,?9?/L-?k?a?nN~>??pLGj???.Y?B(i2?B?v????^? -a1-??(?>?Q ??<?? ?????????}H ?p??*#??(C???<????1??|?>????v?"???x????N$?b?/?3"??* ???"?@?X(?h?k\4?@M3???????????P??A??w??i?????}9m?R?$?D\?0?b?? ???ZMr)Bh?8??C????/?W???t?9;??L?g???7??e? ?L??,r??=3z?ZS??K?Z? -?????N8??1??z????w??????9?? -x???n???'?*J#/???????_?n?kl?Sp?&?????????Gn-?84q_?>?????????????#\Y?r5?S?PvQa??)???t?Rv.m??y??>???-???_????cXZ?1I??mZ?endstream -endobj -225 0 obj << -/Type /Font -/Subtype /Type1 -/Encoding 610 0 R -/FirstChar 32 -/LastChar 32 -/Widths 611 0 R -/BaseFont /MPWXML+CMSY10 -/FontDescriptor 223 0 R ->> endobj -223 0 obj << -/Ascent 750 -/CapHeight 683 -/Descent -194 -/FontName /MPWXML+CMSY10 -/ItalicAngle -14.035 -/StemV 85 -/XHeight 431 -/FontBBox [-29 -960 1116 775] -/Flags 4 -/CharSet (/arrowleft) -/FontFile 224 0 R ->> endobj -611 0 obj -[1000 ] -endobj -610 0 obj << -/Type /Encoding -/Differences [ 0 /.notdef 32/arrowleft 33/.notdef] ->> endobj -191 0 obj << -/Length1 1612 -/Length2 17846 -/Length3 532 -/Length 18762 -/Filter /FlateDecode ->> -stream -x???c????%?v?Qi??m??i??m[??m??J???????_?s??????c<+0cF?Xk?*(? -????l?i???,l?\?d?leh?f.??0????Cg ;[Cg?:??@`L??D???? CJ lg??haf?L@???NIMM?_?B?) I?????Y??m??G2xF?O???D?Q????L?`? ?|??? ??O3?t????I?ld??#?-??S?W?M -?[?|????bWY?[+?)?h?K5?p????????9??<'?6.e?iI????o???B?$O??.???yK??Y3[?a??????HP?????q???G??u??6IB?;?c??6?????2??V?E??????v?vs???Q_?$?p?xbxt????0?????L?[??????P?!t"???"??5=Fe????F?0}'Y???g -??X??T???????u???p??8?h???7?F[V?????E"??ap?w? ??xPOx3???L??1??????.?X?pb? ?FE~?Qs??+?L??FN?/??O?2??}#9^$?|S?p?>lM%T Y???????MR?p?Th??nCvF0??????y )PrP#???????^nY?fk7"????f?Z??0??8??~Y&???|?huK??"9N?tY? -??e??-2#????kLg???a-6g?X??m???^???A0MTC??F???Z?Y??E}M?????i?????N??3??R !?N>???m?bS??g?.P?+ _?#S?&?m??-a?yh?q;!l?%n?????? 9???[C?^???????????????????(?{b????-m?K&Gu?u???? ?? ??? 'C??_e?4??A"<*??L?n7?("??????????9???????v0f?*b_l???HV??c???v?Y]?????;??????4?9[j?b??v?A?f?l?{[P1?A??@L?*G?t?]jpANw??k??e6 -?????`\f??????2j?-?;??C??? -??iC????jd????SG????uh'!???-?????W??? 9?5r?k??LN???+??I???!?X?k?y?b?+..????n??\?O???,?v?#H?7.@ ??C?????????A?/gx{T?}e? -W7 c?Dx??,\{i?N?&??Yw?4+w?U?(?j?? ? ?F??zcL???o?`2]_V7?F??2?/?g<y?@+'PB?%|A?"?W???)!?~DtY?i???y/?????K????7??q??U???h?a?u -f:G -???L???q? -?q???h?<???Jo???Y???n?A? -? e???<&?d?- ?????S?sW>>B@?3K?@ ?#????k??@qn -??HXr|W???"?????4u??7N7>????? -(_??g???? -???|>s>?h?h????T??@??lWr???B?pl???????&???kc?>?)?????? -?U?g??)??72?]{m7 at A????? -^???t???CL0'?o?H[d??:???U??F-??F???? ? -??????45?<???T?m???u??U?h8???C???Cg=?D????x@???6?????l?!?A"uv?H???????G? _Z?8????=?>~?y???|?K????? ?N?2>,S??ot1???M?KU\,Te\??????????m?^[?Wzg???| -???'.???*c????????Ho-??^ ? ??,D??D???D?1 -Qc9&??Pi??n,??u1?Bk?[vh???*??@? ?"?O?:I??xl>w???+?X??????Q?_h?#?,0?%]9?????P?,+~o??ZF?p?????S?"???( -n???Pv`!??*???v?? lO??9?]?}D???v?q???}-??(???O??q{-?894?wATq?K \?4?t?Fw?o0???G?S?wnB???}Q??4;k? -h x?A??i?`??\???fwdr?38?b?{d?we??:? -?N??n??????=?N?A??x?/9l&?D:?B? d???W???-V?#GY????h|???S{??x?fo??|?d???j??g?7?8F??L??w\<4? ES.uM_????vJ?????a?????[4???????=??>???]tv???? ??A)GCm)?;&?????1?:?P?i?'Uh??69zh???t?Je????sdU-???????"ob????V{]@6?.?L??????QQ2???[=_???s?i7??(?#p?i???Mk??U?????(?'???PR???x??.??x6W??i?T??=n?22?0l???R??????????mud??P?+?c???nL??tdq2:??t?~R|??zK?8t????q????*B?1c?"?Z??j?E?????? -?U????? -?>??r???????B7?i?XU4Os -?'?[??t ???X??? Z?(???h?????f&??P2?6??????+??i????Sn0??$?????nd1 i???H????w?f??????i??Na?s?????4???>???? ~&???a?????? -??"@??7(?t???[&o??^*??4J?uG?l???gl?4??? ???T ^H?"?:??????? ??????<(|?& ???! _|?!,m?=???????r???`B?< ??????%?B???pF?Y??'????????+??3&?????? xb?U?[/GL?B???? ??s????P?e??r?r??? -??:?k8Zs?? ??G?;l?)?)`??????$????????!+?H??_m? ?Z????5l?J?K??z.l=i?~_?W,"kjz??6~???a???r????W???%??? ???`~?)[?/?N+?N/?d???l?Z(?????????L????^I`?qi?4??G??l`:(?E????0_?Z?? 6g????Jc}?8??Z???N??}???"???N???*??'J??I?S?Xx6?'?`??%??5??W????W?????*?/?{4?"??-??[??R??}i?$`?/U?`???5P?5? ?\???k???j2FG?\????????xs??Lfwf? ?A ?,n???O. ??@1??M{6Ay?H?3^???j? -?z?`1?P??){??6??bwB ?D ?^?Z/???C?? -?N?f?K,ux?X7r??wBB ????bs?[??3+???? ???B=???+??o??f1]?9??? -J?h?9??(M??v?fM?????i????+?#fDUs?2??R? -t?j??o???[???(]f?'?????J2?????m2???kHB??RO?:)Hd?{?y?s??0?"?#{?_f??3Q' a;?C?A?U?<`? ??iWX'a??? -?"5??!??F??~W?R?N*?I?0p?{?????,???v?x\?J??\????mD{?????81???5 ??5j*i???????w8??]?:8??1? ?=???lf??????????????*?????(ic ????? -?B?S?w?????tv@??[cNU?1?{B?,????T??r????t????_? -???C[)??B8?Z -_J1??z(??p?g"??QCA????k?^R?;?eQ+?_^myxjA|???,?JG[?Dqq??j0%!?N???zBs?t?9???WpOn??sve3??I?n???@'???A\?%????e??U?#?5%????;\'m?0`???f?9? ?@D????qe1????4D|]?t?C2?????/?f?????{???Ty?????f????(??J???????!???)v|?,???/??9??s?C?0ko1r?j~UMu? -?e?(/V?i?Y??[*[?m?)?T?d+?????$~f*a???????2??M?!)?t+W????&??/?{jK')vZ?eLD?j??T?erY|?^w??b?????A??G?V>?4?i??]+?_?? -/??MZU?FE~ ?n????u]???@?R?n?b?Aia?P?????C?E????9???{*??{?(??G?1^??\?^????B? -? ??l -??'<+??JS?l?` -QT?4\r??s????p??y??l4?1???j?}(T ?,E3Zs?&????.?%B?????&PYa??w?????!??T?????o??.:?3???\?O??o^??c?;?$????,???-?-*????1>??^?M?6X_"K???q??????G3?N???S?O?L?*%?Y??C)A8u??2??2??r??#B?k????-).?????53??_T???}H?????J?7?)???}? ?~??????hKu"V?gXA??^A???S???_?P????X??9??!)??J2??r?}??N?????????mO#???????? ???U&?B???cX ??k?&?+????y*n8???em?~??????}|KT???cO?s??Y$?'?? 3&K??2_S?K.h%?Q??L$???D?EP?????}]?j +S? ??eu)???&???w???????MEp?b??}|??CXh0?9??;?"t ?3g????^?2HpZ_??O???6e?=\???? ?B$f????u?????L??8'??-kZQ???q???t???:???&?? -? ??..4[??6???p?!uf??N??rK??V???????#x?.?%$$?8%F?m{GT??Z? ?: -:u?%Xz7X^ -??????5?????q?a??5??????/k#???.?~???$t[?}$B????Bx????{?1?)?wc??/zf? ???np{?;Q??Y??^??-?e}n?p? -OK%R??I??????@G?Q?'??*w??!4???`?t|?c&?????q???J?P?Ia0x???2o?8????+???J*W,S?????@????Z??V???T????]??u???HE????2????o?m?"M?L??D?t?T??l?????K?}L5 )??K???B?$C????PS =?Y5SdQa^lg3???????? -????G??g?0vE???U?%? $ 8?M=FZ-6x???4?"g????)?EK?l%R?4??h?????HM?M?j??uD{=???"*1`?,?????:?T?s/?0 ??Bn???GH?\??Xw o-?????U -L?sI??E?n:?f??3???54a?[???C??n?}!f??k?3??9??A?]??????S?7-?? ?qb??b??7?? ?????I?{7??N?N? p????lV?\IB2qf7AG?/y![M?F=Fr???EkN6??L??k Dq???RU??lZ?,?M??D ????x???M??? -K?? -k ????X???] k??ExB??=SB];-??<+@?JA6,?2??{ -???d????7?'??7????/???k?P?uD??u???~%]???`K????6?VFo????9G???z~^??I{{?)????m?=` ?jC _+v?}??:???????U?/?????[??y?????rn???.I?=G&????????g?+?????&Q???????????n&'??n?O?M????T??%xx???X???B??$W???-????o?????zok?B??8???f?-bD???]X??j??r?????-?N??/???;M??.s?k~8?b{?o.??;?:??I???p?????y?G??`C6h?1 "?.?]??nX?#?BL/??J;??HG?w?7??Q_??? -?) ?le=?h?E}9? -o-k???????Q?l?K^???^ ???????"?\??? -????[??e???#??1??r????????=??Ft/%z? ?~H ???Z??:l?P????h?QV??nI?C?g????? ?]?9N??Eo?-? -?$????V??!??$?v????6?yq?z.?~??F??i???]???o?*?v2??PI?? - ???@F??6d??????8F`:@(??????T?Z? ?MJ1Wq????u???????L??@?K??n?2j:?B?????XAU??"x?N?{????v? 2??b?72M???e?+??o ????7D??????N???7e?r??x??hx????8???y??4u ?Bo[???EL28??l????(?`???#?????xZ?R??? ???????)???-[?t??@l?A9???*?????l?b?i??f??"6N??????E?GX?>@?)?E??'?????????a2?@? n5??G?;??????????B?a??#3?;w@??^?w{^??%?Q\9iQ!=G?(??ab????c2"A???J??lB?????)??R??s?????'?[??;?B??_????N|?z3P -??z?A??{m?L:}???7??7??S?S???????I7??4?sl`??????u??\R????I?u0?S?%?}?_??z?I??Jm~??t???J?L?.3?? >BY?N,?g???0'KG??8??o}o??ca???*??????6?D?????\??{??f???C??1~'"?o? ???*??jM.J -??':E:?????H???_???,E1?jO?Sw?uJiGI???5v?t???\'1???/? ?_^??kG??X,u??~???????????[???f:?? ?? ??Yc?c ?RszMu??????,,???]?b?rG"?p??Cwz??%? ?*?99 ??R?1?uH_??9???? ??????D?oC?????>? ?<?x?4????&???7??.5N?V??vG??????I?d???2^?E??h???`?? ????FZ?+??y?&{p-????????J?'1+Ky??,:??mc:?;L???p?7??FG????????????b??$h???]?k? ??R?0?s??!??G?>DU? ???s?????:GXJ????=??I,?? ?O??*??L??n???~???N?!y?|???8??? -????????F8x??b?TSl?t??;???????(h)!????*5Bd?*?w?Y?rF?@???yV????P??Q?}????A?????? b?<&_??v ?8H?)u?vb????wWT5Pz?}?k??H???? -?=:??e?n=????>??Jd?Cf -?k???zoS???nG.?!jP0a?#.?S?%?D-W?j8?~e???7?=hpfx_??c??O?L?1??_$??sA???g???S?5(???1wj??{C?.???U?}?GE+*YN????8G??OF?d??Di?{??~R?&?B%????R??? ???Q??^???5K1?b???8?????do?@?!??????M????? cD??LO8????6G??,??????eX?@:??c? ??Gn?C??????h??? 1@???7?????6Z?L?????U ?z+F+??"?? ?V?C4 ?o???{??/????]4:???k}SjT????????? h:6???\?o???Eq?\??/E?N?H??????( ?r1t7Z8????.ULt!9 ?B?{F?? (AM!p?Q5??C?On??:??Ka??_i???hA??d?B??hAC2?/??}b -Y?S??q??O?f???,? -&?Y?c????????M?C?|'W W?( q~O??3'??Ho?????G?5A??r???A$????hC?D?O???/?p)g&???W?z|???\?<'?~? ?? Vy?e?-?|?/?yG(rH7YQ#A???A??{?ar?4?_80l?A??? )???%?c??Yh?(r???\W?.?t? O?H?G????U??&M???????~P?????l?#??sp?????9f?=b?rP??cL8hh?`??b -x?3C???Bkf?x%??????#??c? ??e4??*??&??/???6??9???????0g??/AjlA??Q?????+?X?_??@??l??+n?#Q???a?~??????g??v|?a??A?7%??}+?l?@?e!,???)@{ 3VG???h???0?9m? -??????W???I?? -w_}?? ? ?? -???"?n\?N?Sc??????;Tk?&)??b????sS????? ????>Q??-??'m?+? - -?????k??$1??lI???w?EhA'8s?O? ?? -??/I(???'_????N??A??'?L???:7?w?,p*?.]~?????r9?$g??i?5?@???L??(?G?6?eT??????A?eI? n??k??7yF?_?&?rQ???q!?f?7L?7 -?QL??iv??x=?*?&`?????Q??????PLM?zhZ?s??$:?F???????[?p5.??8&??"v????1#?????s?5??wVs???&?%???i_!?X??wK?????????`?o?Bz??????"??e????p??G@?=?TiS?O??Q*?z -f,B`??uu*???2T1???W?zX>??%5???? -K?Q?????W?IBK?vY<L???%?Dz{????L?p??????b??=_????&2%??>?$9P$? d???????Z|??0%?D???????$???]???i3w???hi???????(r???????|?a?$??>???]?%5??< ??U?????T????=???d?I?%7V*}.??N?4?d??k???kf[K??Zu?/ qI???&4??u??d&V??????HV??Q????7?-#Kt"??n????"* :?|????4??-T?????+??`i$?7????^83*G???: ??????6?W?l -??ftd?z"?sexX~=|:`C?;;???$????(v??sP#???k?BI?? ?????????R?w?K????2?4??I?E??W?'"??"???? ?>???c?V???p?;?PI???D?%:?YDiYP+?/H??s:?%@(?L6??'??l???h3? -&K??"? ??|?<2???j?+??{? '?O|?v????v??????K?$^vie??Apg?????????I?>????????????? B.;m?`??:?x?:?? -K????!???????g ??????G sc??????a?/ -???j??%????%;{????^3]?A?????-??R??j?e??'x0?72*,?72??_?P?endstream -endobj -192 0 obj << -/Type /Font -/Subtype /Type1 -/Encoding 606 0 R -/FirstChar 33 -/LastChar 126 -/Widths 612 0 R -/BaseFont /QTEVNQ+NimbusMonL-Regu -/FontDescriptor 190 0 R ->> endobj -190 0 obj << -/Ascent 625 -/CapHeight 557 -/Descent -147 -/FontName /QTEVNQ+NimbusMonL-Regu -/ItalicAngle 0 -/StemV 41 -/XHeight 426 -/FontBBox [-12 -237 650 811] -/Flags 4 -/CharSet (/exclam/quotedbl/numbersign/dollar/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/at/A/B/C/D/E/F/G/H/I/J/L/M/N/O/P/R/S/T/U/V/X/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/braceright/asciitilde) -/FontFile 191 0 R ->> endobj -612 0 obj -[600 600 600 600 0 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 600 600 600 600 600 600 0 600 600 600 600 600 0 600 600 600 600 600 0 600 0 0 600 600 600 0 600 0 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 0 600 600 ] -endobj -147 0 obj << -/Length1 1626 -/Length2 14351 -/Length3 532 -/Length 15230 -/Filter /FlateDecode ->> -stream -x??veT]??-????????Cpv????KpH?`?%$???????}??o????y???xg?3?^U?f??Yk?MM???,n?hn)?vcfga????]5T????--@?w;75??????,e?f)???HYv~~~$j????? ??? -@???K????O?_[????y?tY?4????N?`?w???@MKK???%? -do ?TU??W????hd-??.f?5ws{?Z?]-?V?.?,@G????\Y???]fW'K ?=?? h???? ?d??ru}?\?.f`???9@`????_??V?rrq|????{Sstus?????Y??d???????????w7???}??#?????????{??@`W?????_??- W'{3????`N.??i??????d?p??6s???tu}?y???;?????7sr???;???]????jio??????????Fb?kV??V?v??-?????a??w?????wf?`{o???????{J????,?s"?H??"?????=q?U??t?????_?e???U???w ???1????????? 1s?{????u?????J8?[??O????%?`?wY?X??a????,-?@n@????{???k?-,]?A`?w]?n)?????_|Z6 ??/????[?+?w??&?*????)??_\?oT{7-o?wn?V????,????p??2????9?????;!~6??"??@??\+??????u???]?????2?i0??????t3[?O??r?]\?????W????g????????(f??9???o`T????z ???A?kaP?cg`f???sM8K???k?????????P?=mg??Y??%}w!?*M/?n?q)j??n?????:?G6???Qu -??g8??6N??;? J?? ?['?`F}"n;F#Vm??1M???-m???@?%l?1cn""?? *Ml?s.??G? -??H?*4lO -????#?\???t?????C?D????A?oR???=????|+3???h?M?o???$??'?Y?m???6??D??????4??????&J???p???$?>??,??`)??g+?????f??[!T?R???O?*?L???3[??2?O??I?hM at Ih?X5??/5?t%?"??????c!? mb?=?1I8K? -k.\L?5?Tx???6??????C???1%?z???^?(?]iu??+\?_RR????G?J???v|?*q?`?JOm?I?L??{T????0????-e?, ???z?Z$3cS????}"?=8f\V???????6 Mp???DG????a$um@[?????z?????eI? -E*}?Wa?(?!????2R??u?[W?@?$E?K.?1`?~ ?,Eg? 5\???$s???1# ?Xc??H?\Z???????H??M?T?.?)??1gc?m??B`???N?a(?2|??K??&e\TM;PC???? -???????>?.d???_a<6?W[???????T??=?|. -?C???=,???U?z??G?YR9e?\9y???[?0??y?O??V`?d>Y??"?$?8?F??b??,??? I?RG??x????????`???~A?S???ck=????? -?!>Y??Hk????h?st?F+%????2\E>???^?Wb3M???S?%???????c????????6 -?n????C?d?oT?C?j?K????n???0o????a?????Jmkw?!??????Ko?2|???@p?=?n?N???/?"?V7?w?d??v??P?????x???UaG????I?UP??H????u?y?????!?gE??a??q?p up?V???3?? ???R8A??l?Q?h??C??4?Sr??B???V+[?????6??_??4G?d?????^????[??H????c???????Y??8?30g?!?ws??C,e?q?X???p?N??X ?? ?!???5Nj??M????$?=?0 -??????\?/????4dw????????. 'I???????zC?$?????>3.0??0??_???c??0U1-P??y?s???????*?? -?u'd?*:D2??R?C????%g(???>???3L3?H??yi?>`i?,B?U?0Q???mn???O3????i??"'^k? -??I>??? -?T???R+?a?| .?? >uYK??5v????jZ??S??$]???+rEc?)??????Q??h????d?lQ3H_6,? -/??Q???ob?0ZmC?????;9?T ???s??VSoE?d?y&??+?/r?m;?*??sL???&??.?4o-?R7ex?"?0jD?vm??Eg?{j0~?????? ?T?M*:?1>??Z?y ?}[?;??O)C?????V"F?MSm??pl??h?j(b????????z???I at h????Do? -? .?????o6sB???y?\? -??pm?IO??I?????I\??????7=~?????? E?8>?5????:??? -???=$t?l??k}?~?j?X?????S???[D?L?F?u?IE??O(t?????kry.&???5? ?/????%*?Q???'??h??(u???#;f?g#????[?:?45?"]?1zb??)1?3???_?KhH?I}????i??o%?-???y???-??`kG?~?????p~6?6#V??Q?sL?? -?M???J?Oy?p?X?U+d?s???$?@?T?'??y?????O? ????=/???r?:4?????X?OI+'wfL?i?Pu??|i?????V?h??h?G%????????m?{??%??[??qc?4g?Iq -?W?t?k -???????V??0,X?l!W?????(????p?y????)|?d?7? ??K??&;???b;?&?Sq?{?q?H2TmO?f?HLdL~~? $??h?J?Y?)S?Q??FB?P??P??Xx@&@??ms????S??[??rG3??Y??I??Fe*??B+L\?????]????>F??Jv??m??`X???n????}AM?^?+D????^??oS??pQ??b?????6p??g'????5s?u3?V?:?/?????Q?k1?Je?N?X=?}???s=???9?xlg\?????????H?~??P?Q???hr?/?B[????]'?9z?????U*Bs???ifiD?bby?1??+????m??1????Y?3I?w???x?%8FJi2c???L??????I??&.:?{?????o??8?ue{???????j????`$??25?????}#?4*????????`?Z??a?0{???>?????Z@D?Q?L -??X????4??? ???f1?/FOe{???M?~?????eY????~8 Esr*? -?@??'??4?"??]OA?s???]??,?w;?w???%?N|TM?I_??d?oE??n?'rZf4dzL? ???8???Hi??????U?kq7?S[?????U?0????:?/??`?$ ???h?f??+!S???J??*k=???T?"8?????q??b????K?? -?i???q>?? -????? ??^WW????L????]?????)????nX?B.n?G????_t?Z?X?????fX? $u?hu:F?c? P?z8.),????`?=m?~??Y??"M??? ?L?*?Q9?X??o?1? -?\??J?i?fdB???????????tb?>?U??(0D???M??a??h$_?|IM?@g?)5)?Avj??'?- -u??L+W??~b???A?t????+???%?H?J=??=?;yYp?g?U??'???????f ?4??:?=V]??!?%??T<_???????!+s???(?kb?=/A???????O?Z|P?}]????D ?YB?=y3?O??WN Sj?pe??????y?P???????`B|???AWZ?????????????\X?EQ? -?\?????A?P?(??D1?d:AFu1O?????j?R(???% -rQR??F???$l?Gh2???a8k?P??T ?GHS?j?.*.-@=?)??n%?9?S|9L?~?????A8e?]?wx?w?$?h?G??7Pu???$????v???????R?Gcp????j??G???^"S]???j:??kkTfH?t??????j?w??(42z? -?l???????\G?7EM??{< -??I??N??3?'[{ ????!=9?Df< )?/????)L??d$??????_? ??9L -??L?u???7?H?a,?L???????g?QH?3??????=J?^?8%?jL`3???S}????q'???^?g?,G????e@?'rAA$?@?w???D;??7:???)5????%?v.??+>?-X????1J???Y????^????z3R5G???U?&???e;? ??P??L?"?)???l?j#?? ?t????????M??1`a?W?=?????gO5?hVS\??z?/???? ?N?????1#n? -N?W?;??S?2 4???????a ??i?*F????????yI??????kk?P???d???????x??z}??X??C?t)???&??KG?m?0???7???[(*.@?~z??9)c?N?!??L??!?????7o? /6J?7?tM?A? ?JN?m???[[?n????x?>bj??z??W??]3?,?8?I??4>??a??? O????.~T?gG??v? 0l?? -?,c?5qr? ?1??????i?b???J??M?{?w???vG?Lo|S???~v??8?3??-?~?Gd???????M???????N??@?x?Z?l?L]??????S-uZy&?a????Fp?X?pVS_??[S???T?????T?????????lA?d? -A}??s+j? jB}?m???*Ij[L+J?>b?,m?l??GHc????9? -"???????x_? \?h?G????&?{?*?%zC?G?6????A??&??HnF?a??|?Y?:+y???o-????C?M???(i3Zr>?V???tg?*?/??Z#?[?XNx?#Uv?????)?Z?? ???$???/??i?5#t?+?[??'Q????G?[I?E??z??kp?|?oM\^?y<2[?}??|$? ??I??c??+??0-W??P? ?8~m'kt-n?? `?? -O????E?d??????????????u??%l???????5D1????g?&U|a~?P?ure!`_?P?V? -"?;???????f????????'????? ?!,????X?^l\I??????$??????????@A2_3+???D??L@?d??~?H?"?]f@? -u?H??????s??????C????6/? zf?????s?k??44?sVL?b5????? ???? ?a????#?0L?.a?_jF???3?? -^ -m6v!j??@u???????t?Lo??5???K??,?#??? -???z?Y????>??7? ?^?j??? y?Td>Z?5 ?8h?~???O????i?tT?z?3z+???^u??(3 -?????[9"??? -lrV???????<??[?????_?h???((?K7Z-m%?X?_?N~???"jya??Z???8???????? :?? ????`@^??r?-?6)|z??>??NZT??+??;A???F??N?vu??VLg? \p????@$??[??3G!-??f???(!>????e ??#?Oy??|??rh?^QT????Z?E?Ds??j?t?hx???????????gc????NUz?d???{Q?5?e?D?u?<_8s???6????fZB,v???R b??/ ?v?%??? ??0?}?c?C?v??s???1PZ?????R?s~???FY"?S?]???r at SRRT????o?,(?|v???W_???G"U???f?B??? ?X^ ?0????8]????F4GW??V?M?1??uG.???v??qE??6?f|??2S?7?? ?; ???GM?4???I?D?=? ?5 ?~?_??r?~?(??e??]q?}'m?F?jm?B?'?? -??-?????_?Cda?Zl????d?? 6|?LU?m"?E?Y=??W ??0w8F?m?hM^?{I???=???b?08???? ?'?;?z??W9??vP????cY????Sh???zjLz??W????n*A??W.?? -???Ov?,5M?jdGiU??b???F?'7?{>??"???.b*E}2??=?????'y MA??d? ?t?=?z?E??d^?+ ?? ???P?g????????)?xl???7q6x-?H?s???szy?& I$??9????%????????W>??H???N?}???? ????+Q2???????,?Mi?z0?Y?4??;??;d???]??uH}?????G?'???" ????yt*!????x???Iw??q&??WZ{????I????HA?>?V?~8H?s?!^((+7s?????????r]??^??q?3?VJt????l??????? -ho????80???Gm?~(?X?&+??r?Oh???<??.1??????????`0iIi?uSh????F??????J??R???????8??M?,g??r??????????)?B???Tm?>E,}?Ex?&?Hq??`???j9?%?-m!u??E?W?? - c?? ->?Z?d??D????g??pn7L8??e)????????n??? ?c???N~!p?zN?v??S?(?l??W??? n??p?=(??w#??????-4P?j??? DT?D???????H?S?????{?)DfP#K???,z_^???Z??@?T???a?K?/??'???????????@???9F>=Q??????W???4????9?sq(?t?P??~?S? -?? -?Db]?+3?"?hL???"?-c>BJ^^GK?????????5?7?S&?w??N?#M??????6?Q?9????@????? -??$)?nt???w?C???}?fU??u;??q ?l???n?P~?????s?w_4??W??= -?=?p??0p???*:61??=KNR?Y@???`Kq?_??;Wi_i??r?`?4]n?C??/????ju???????I? ?D????#>C?b??v9?z?sX_1??T??i?r?????z? -t?Q????e?dc?+.pKb?????Fm!????l??}???!??? M9?????U{??7?%???{??3`??????&?W??u?Kf$??Y?'N????7?x?????s&?~?*r??T??9 -??????Qs??{61??????????zc>??A?]C?Z??]???p?|>? -???$L?yo?6?(?:L????5?X.40vw?1???v?? -Gj?>T?(?*'b+?T?MJ??$Jv? S?79Kr?????kb? -l??/ -?d??"???A?????????\C?????E?^w?c*8?qp(?H?C?bt????~t??????(???Q???oc?j?p?y???E?@F -v?4?????U??????'?1~??????1p5??J??????mPR??}?S?\?_?????[}LU?%?[[]???fd&9?#?g??*?5?$?+#M?&x???Iz????? R??/??? ???IX??g?~???D?r?e????????X?=G???np???Ki?????w??? ?> !???P?????h?$?2??Dj>w?K??????????5?_?}?tI?((?uNH;`4?????|???????OOP?Z??%?0l??????*?OMSLRJ?e0?h?V?^???X??\??0????`??<{?Y???9F???,?^4?s???p#?????x8?3:f?V?1+? ??????^??????n3R????)9? g? -=?1 [??:???0??xIE??H?l???????????z7? ?M,4?0o??????1d??Rp%?F~??????A????|??k?d????W??XX?*x^?BXa?)??XZ???0??43Z'9=}?Vb????H?????[S??ZV??G?y?zC????X??V?%??02Y??-H??8? 7Ydf?_~?\??aS*?E?L??xk?%??v6 -?j?-j?=????s!?????,?^7ea????????8!e?HP?3??hf????????"?fry???m?? -I"???S??{pakx?? "?R?wv8??^??07???t?%?Et?O???U?(?x?K?~]???? E?m????f3?W????.')?T??E?????Q1??$/<" Fk??\????B??$=Kf?????f?U???? +???bL/?V??>??~?+w???Y?? S?]??lK? -?v ??M??_?`??{~,J????j?? %*J???j????`?c?+v??h??~?8b=P??? -????-??{u?(??????m.s??y??8??????IY?????????@<[ ]{??"?X}??.?:??Kb^9B?????CU*lGs??i}?r?D??\D?%?D???s???? ?a?9?jC?????|?E????1?_??A?????G?qz1???"??9u?{??????`f1???z??F??<.????????yl?????rK.y;?:??U1?"?j?????_?[&??#??7??L?4??Uf? ??p?:?? YV??.??Ss??R?# "??i???????2h?^? ?YZ?x??g3??l 9L/??N?h???????eij?????Ev?v??????9?G???V?o?o+:=??W.?u??" ???6?????? -???????????????????????l?endstream -endobj -148 0 obj << -/Type /Font -/Subtype /Type1 -/Encoding 606 0 R -/FirstChar 2 -/LastChar 122 -/Widths 613 0 R -/BaseFont /EUPTSE+NimbusRomNo9L-Medi -/FontDescriptor 146 0 R ->> endobj -146 0 obj << -/Ascent 690 -/CapHeight 690 -/Descent -209 -/FontName /EUPTSE+NimbusRomNo9L-Medi -/ItalicAngle 0 -/StemV 140 -/XHeight 461 -/FontBBox [-168 -341 1000 960] -/Flags 4 -/CharSet (/fi/parenleft/parenright/comma/hyphen/period/slash/one/two/three/four/five/six/seven/nine/colon/equal/A/B/C/D/E/F/G/I/J/L/M/N/O/P/S/T/U/X/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/r/s/t/u/v/w/x/y/z) -/FontFile 147 0 R ->> endobj -613 0 obj -[556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 333 0 0 250 333 250 278 0 500 500 500 500 500 500 500 0 500 333 0 0 570 0 0 0 722 667 722 722 667 611 778 0 389 500 0 667 944 722 778 611 0 0 556 667 722 0 0 722 0 0 0 0 0 0 0 0 500 556 444 556 444 333 500 556 278 333 556 278 833 556 500 556 0 444 389 333 556 500 722 500 500 444 ] -endobj -138 0 obj << -/Length1 1608 -/Length2 10437 -/Length3 532 -/Length 11293 -/Filter /FlateDecode ->> -stream -x??ueT]??-????9??Kp? 8?A????!?Kpw ?????w?????u??7?c??WU?Y?j?Z??RM?U??( ;?r?qT at v?????`%VI??9????BK+?4uA???N@!?.? -4pq8QhR{wG????A[C????????B?????? -??^?\??{; ?????Q8Y [ @JU?????ANE Mmj??mAf%? 2, ??,f?9????l?XP?)j4?n????r????v (???,M?N?=p?@`3[g????- ?w??F???^?? P'??#?? ??UMZ?_?O?6?=? C????FK?7?xR??l2??/63Z?L'?z???&c??????D????? -?????/F_??wgS7???d????????T?K?cTE=?5Z??S???-???=^NX8i????B???????K??????????~?#????Y?t??h??x5BSA?f?x 3??q???3?P3?U??h@??????F"?=???B???n??0py?????"??d?V??E?? -?0?2???x>f???C?c\a\????g????6??~??T3???q??2U1?r<??P?D? uHzh????$??E?|B????????? H?????#*?b?U.'r?x?%?58???.#~ ??????Dtd!;7???S?;???L?ra?_n?a???????D??.4?[Q7????u7Jg5?K????k!??|l.??K?$4?`???o?COk?Q/? -???????9????A?????W????M?%??u??}s?V{]?=?e????Lb?+~??h??DS?/?)\mJ)@m???Z5??v??q?[Fc?\Y??7?(T????2???h???sQ=???ly]?R,}/??S????z??V -???;]{Ky??`/?$nR?:~N???bu#?????dm???? ??L?E????E?m?%???A??A$?? -??y2??]??vS?k?SC ?????q]???^??#????&!R???Q>1???^?{?jE???J\?cB=D?E??U?m?H}???????So??Im????nu">?g+X???Dy??a?M?????*??;3?_.?????8?)????y???0?s-??nm???{$????j8? ???Y6???~?????????\?????Y????A?D???F?ztA??e ?hM??R?J???:v 7 -1?u?]q???xW??Ej???L??l3?mZ?P??M?V?|???}q{>V????s8?(?{=?????*]2s??????7??+@?$???Gz??r?1???7!??ES?? -????<3 -???yd>E{?;??0?B???Y?4????#?8???` ?O????o?uS?t=r?"?OCi?i??r??I;&U? ??4?b[M?z??'?+?L???V ?X9]/?ID?E???????????????C??l?2?A??z?x?E????uf??n"??b~?S2 ?iylk3?{O????N??6u??ru`??H> ????????t? -69?jA61???{M?*??? ?|???]Z??????yS ??1??`{??4?77?[?)??Zn???F'?K??z3-?p?nL??m???????,E??????N9?n-??c?!?6`aU??~???Ye?Y}???"ge??q?????~( -?7??A?'???[C??\:?????:D??????^Ue?M??\A??rui?~Mir??O?????Y=???M??>??6?JL? ?3?.]?{?b???h??L/?T??P??f???x?,?&????:????@?@???2?3>???bo?!s??\cF?)^??n??@$r??4????????????m??>+?z?*????CoI?*?????U;Y?k? -?+????>?R??I????%?????F? -?h ;B?Dy??/?Q?????????(?]????r%???{?Vnz?????4???n?????????????Z `????tM?????s?:???cx??U|;?v??v#?7+?{??e](??????C?(??vrphW??g????E????QqN?fv?H???7x?6?C%$??$\$?;bAbM?_ z??:????Wt? -??:.b?R???qmG@???,?s????~a???}Zm?!???*?????s??[j|?X.?YN?R? ?O?Z-??dyj??|??D?b??#??k??\????c$??"?Sl?m??Q=?"9?D6sL??????????V9P??K_|?? -}????\?k????F?????s??e?M;?]?3?3H???j??~Q???J??1?t?x??h??~?VPG _?.??????`???????W?@???x?LZu?]?????6? -1??*??Qt???Il?dJl?? ~?6]???1o???7?"?`DM?`?v?:Q???b.0wG???qH?????&?t???7?k?mX].7?????D? ?Q???:2?6??TX??{*VIT/*<^3?j??\{f?csIt0??5O??Q7*P??f??!t?k??=c???VY*????e?&.t+(??Z?M?8?j[??L?????>??#?TNPaIY?#N!??8???A??0??v??}??????8?????5?%?y!??Q[p?i????X|i -u{??z??v?T??!9?E?E,.?E???\??w?Z????ZE??5/?I???i6;?;?S???????D?h? -k?????? ?zM??(?#?G -?????nOL?6? -y?^$?^???>g^??BX????o2???E???x'A|????5l???.?????*????P?$SQ]???E?b].??? uf?2 -?b?????????zs cp??M?L?V?7K??? -e?fcL ?z???u?N?(?7T:J??-\???j?????????~A~;?7?y_?????W??(#]??d3??z~ ???a?ID??%??dQR|cL?J/g?uGtS? ???8?T?4<,? ?n??[:??e?7?+??[?=??k??>.???????_?[??l???o?p???Ik???f???Y??w -?s+.o???ve6{??r?/??z' ??e?Z%y??V?@? ??????d????U???? ? K?=??!?? j??39W?T?b??m??????1?A?????n?&x?2m???&&??|?Q0????/??%??9#r??Pu?a??m&x)??.?Z?Zw???Jwv??]4????????J??W??|?xS>Y?H"??@?8n?#?.7???AH?rW????h`??????p???,?????[x.?'y??????z?d?????k?G?7?R.?O?Y??? -?^?'?????f$??*??F?????RB:-??H?I?w?!?????~??5??????#?P???0.??5J&??;?G???'d?d??;???????:??(??%??d??-t?;???5??d4?yT?)&???gd??O=y????@WM?????????????^p???l??????4S??6tBd???I??,C -U(?VU?? -??@?%U,??S??.E?aV9!gXtm????{9???????Y_@k?0??5UE?X^??a??b?}m#????F?K?5???????L"5r??|???#??H?[C? ????z%9Uf??GW?9?*i???~??%!??hI????I?????D7?t|????Z;F??ol?????;???u -???*???k??Zg"????5?vB??c. -?W^ QH???a>u?K?h?~?VxQi?`C -O (5?2?k???????????????gU?]?????R???s??u?\W6K?}e-?%????? ??L??G??h???5?????=????????1??05?X??w???r??'?DF??ygm??S??|?#??vhB@???? 6??,?Q_???gg?p??h?:M?<_?????F???[??? ??6?S?K=?sH?Me+??]??Fg?????(?@w? ??????)$??x? 5???"???c\??U??(?7????G?!??????}???????!??^*??E????? -????wX?e?????s??P????? -X??&?7?????Z?}?t2 f>??9hV?Y ???r??.*????????????v?B???n??zg\?^??P?(|J>??C"Qv??Z??L????'B??????.4? -O(?#??E???"y????B?^|i????O? -Z????|ppx????-??n?[?;w??.?Q??????7???????Oozd?n????6/??? ?????d|?`?DU?i??5???q?CJO\.b zY???*??1U??,?[GO???M1??????^9???/8????-'yb??x ??a?????MFnQ???G?8?L?w?z -t??????A??????????W???MH? ?Xc????????N??L??Q1??Ads?J????I?Gf/??+??B? ??D???9?M JG?:`???%Q??0????????&?g??]?q?H[XL??????X??Q 16Xxzc??kg?G8?????J???h??[O.?*???.^y??????c7? -_l?|?/V??):?k5????+?????f/`* -p?6?O?%??-i%???????/???@"???????????s?u08??l?e??'??Rb? ?M?Z(?????=???1V -???u???X?Yo?m?????????1?C??-???Q?l2?? -???b?m$F??B -???~#??S??4?????W?Wf ?????}????u*?@?e1??5??\w???.?|HgBUB8??!4%??/??HVa=Y&D?G-???`w???R?t?4We???? ?_EOQ#DQ?g?r?|H}?o?3k?t?'??? ?jSB??'?I?[??E?U?Y?x?KvF??}???????2"?s??@H)?`???^D?A??u?=?~t?.???9Fr????=+??n[??,?R???7??%7???m????*<???4{?.m?}??.?@?/????y -?T|? -???? :? ?????%wR?_??!??0??????Md? -??O?????jv6??G2?vn????E?@e?????m?a?,??xL?K?%EaC???=???;(??????l?j$????k??]? )????d???U??6?@T?Iz0?,~?MRn??1%?????ia??mg?Bd??DEC???-???2???Q??Rq'7??)8?:???^?b???IZ??????F??????T -J??]?rQ???@*B\SZ?L?(?b?FRAS{L???????+?^????0??ITwe?? ?:[??$a+?w??S?8?"?A?G?S?(]???5???? ???F??????z???62??8?l?)????}??hx?m?0?A1?O????$??w']?&??g"m???????? -n???h?L??? ??B?H9???o??G??(??F?{????4?`?4> L ?\??H??&?MG??CNX???|??A ???mXM?fN?Dy???8?I -1E?O?]????i????3???t?fR,d?G?????b?????????a???????7?.>9|?:?y -??S??@;?~=?0?|??S?=?$???x???u3???????????J!.?\ ??=????b?f?D?K??0r???A?]!8??fl???i??&C???x C/z]?????S?>?p=????f?!>-;CQ*????b_P?:?KX?@<2???s! ???2?JT??7??????V??t??&???05Fr??O?????2G??*?q -?hZ"?FO??R??A}???W?8??????Q]D -????C? ?*?SH????? H???M?????Nl?1'?`p??$T????;N?$W,?????a??? f??H??????I??e&km???qZe?#??D??$k???6?\?z?7?BtW?Mp??{~qOw?;?????Q?_FJT?5J?"?????l?4????????`f 4ut???:????^??endstream -endobj -139 0 obj << -/Type /Font -/Subtype /Type1 -/Encoding 606 0 R -/FirstChar 2 -/LastChar 121 -/Widths 614 0 R -/BaseFont /DCGXEA+NimbusSanL-Bold -/FontDescriptor 137 0 R ->> endobj -137 0 obj << -/Ascent 722 -/CapHeight 722 -/Descent -217 -/FontName /DCGXEA+NimbusSanL-Bold -/ItalicAngle 0 -/StemV 141 -/XHeight 532 -/FontBBox [-173 -307 1003 949] -/Flags 4 -/CharSet (/fi/comma/period/one/two/three/four/five/six/seven/eight/colon/question/A/B/C/D/E/F/G/I/L/M/O/P/R/S/U/W/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y) -/FontFile 138 0 R ->> endobj -614 0 obj -[611 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 0 278 0 0 556 556 556 556 556 556 556 556 0 333 0 0 0 0 611 0 722 722 722 722 667 611 778 0 278 0 0 611 833 0 778 667 0 722 667 0 722 0 944 0 0 0 0 0 0 0 0 0 556 611 556 611 556 333 611 611 278 278 556 278 889 611 611 611 611 389 556 333 611 556 778 556 556 ] -endobj -134 0 obj << -/Length1 1166 -/Length2 6834 -/Length3 544 -/Length 7647 -/Filter /FlateDecode ->> -stream -x??ye\Tk?.?1(?1H7Cw7H#? ?C? 0t?? ? ??!?HHH#??R??????????{>?o?w???????u??}=???X?? y??PU? ????\m== ?pm^??'?.(?ge5??\???J?P0 -??+?Qw???'??(( H -?K????B%"?%?z?0W?P??????w?2?? -?? =?H?????t?@=$??w??gU???spD9? -L8??y???$$$???!@e??d?[xA]????(??p??]?v?s???*v0??q??(R??i??????AP@[???1??~????F??|?| ????_+???C?]|?N??B??*?F:j????_Y???;J^??0?WP\??)w?"B?d????GT ??>?????#??s??_#yA?=?? ????????A?`(??o?X -?????????7????5T=]\?P??O9?wzx???q??G:????_^?g? ?O??x4P`D???/?`?0?? q??.?l??w?Cx?~?@^????# ? ?zx???n???*p?w??\ v??W?7 ?tw?????{???=??A(? -??8??H=u?{?vQ?@???=.?+j|v??(??ro??G????V???xj?????l??#?{???*?b????|8$?$??14????u$G????4I??????|??????Xe??H #?????w?t?i? +?tw?8%(.?t?]??%?? u( 8?E?hv6N?d?4'h?vNZ?Nb3;??H(?!R -UwdKkV*&?1?)x?X?jY3?,??B.??/?5?;~~??c?s1???o? ??H??6??????C.:? ? -?????48T????1?jz? ?X?d?g????q -N???O?n$?tn???D!i?w? ??]?R????%???qA?? ?.?Xp?-9t?Z?(??L?@?K?z=.?K?j???H?????E??Q????????????? -[?6???s?EB}?? ????/???v???v?, ?+Z ?ax???6Y?y???e?????{ZP[T?????VT???v&n???x?????}??S?TV?>????^?????GP???uRR?;?d?'????[?6???y|?&%?h??????????????? IO????$????)1W???H?|?:?z????m?????=1?/???x??????}PR<(F'? l#??5???????x?Gy;?D??kaI?R?gF9K????sJ!?? -?F??}YeK???C/F???Ld????:??O???????&??j?'??g? ?=?M??D?W`V?g?{??z$??????[??v?????a???nu -????|3?Sj??}???????rr???3?|???L??L????? o|?|m&?O?? -?!D~??3??-??&Lw pF?E????? -f?3???T4.p5????J2???ff??/?l??Nu??????8K?$??? -????/+m>?????*?'?????2]6 ??u??O??AL? -!*??wT,?????~c??.?`Tv?[?v*6#f9 at Y?U??jK? ?????N????kO]e/f???~????? ?5$?l?_??????????Mz?D??H]??X0?'???P????:r??\%?KQ|???????9?kd??j??????I???b9??3?C????J}?]??????M?????. ?4?w??%?????E?}?"*?~E???51?&??3[vYX?? 0??$:z N?~=E???FoLe? k????????b445??????iX???W?? -g?x?????? -????'?V?? -??[????????e???????9?%?Rw -!k?=j???:?/Z????;??V??ik???s?(? ?eH???$l?u?????m????"cD ?? g?bN?? ??U????????q* ??O?$??7Wh$???w?I?\O?????0J;og??f?NLH74? ???&???????????;???V?V?!?'G?r??-L??&?}???C?==KYVp$?a?? -h?=????1????P???4?}d4??)k??h?z?LE???G???&?.u6? -;&H????? c????z`.cEc?z?H?9i???I+?.?????E^W?? ???|?? -?{?&?3U??,7???> -p??&d??PH?????bkOL:?T{??.???;?????+}?_?Mg????W?U???';???? ?N??x????p-+?C?+1lY??5????XAYo??E?L?sn????91+z"~f;?Fk%F?u?27?r76cNS+~ ,fqaB?N????z?????)???????oJ%??vWOOI??e???2??(????????g6|?cy?"W??j$q?_??????b=r?O????jtB??3{D+S?_??Z?1u??g?e???0???y??"m??????T????-??\  Io?[?a??0???a??R??t?z|3u?V Q?????r????O?n) -????qrz?}]P?T?4?)+?I??( -! -k#?:?eO/c+?(???+??B?Tq??L?I??UbD????LxC?XEV???Ie+TMI????g??P???J? -2#?z????:??D??v???? ?S8???#??Ps????d9??O?g?p???$M???y/??RI???v1????*?? -??????B?G??+????l????5?\??????Y????????2?i???oS??)?a-????&5? ???T)??6{??6f??=MMZ?H?Q[NZ=-?KD??V?'x??uK????????Unh?????? ?1'~?"?hY???#???~?sq???#?0?+?L"????Mu'?/\??=?A?$??Ibk????d??D??~?????{?jY=?"\,??)2b???l ^6?i -1??%?????|pj$;?Aeo??b V? ???t,t8???~~?`?': B?J?& -????_w8?:???1???????_l/%??do\??Y?5?5??H-???Q#?y)??k*V?h???~?[%???*??*r:Y????U?Xz????&???????I?66{?2~r?_9??SHr??????a?b??????-{?7R??|? Xs??'??z??Q??3? n???#???WhV?9?bW?-?g?6?????r??x??4?1E?p???jb???|w???? ??.|???l?%?R?G?????=???_%Yo|??6po??9D[??????????8s??n?\?ba?????H?;`0i? -K?xWTK?mx?tO?>w?kP?Y?P?v^G???O???ex?Sm~??M? ?tA??)???Wh?u???%??K'??C?r? -yH???`????yj?r???FfO?_???????ht?=?8?5???.?b?-?B???au???7?$E?????'?[Q5???~+??/!???z#;???~.??D???9m&Ml??|R????o??iM'?rR?#?S?/?_??`yJ??CF????l????}hhk_???????c??GG??????V??W? +??6?!s???B -?5GJ."%/? -?s?cBc?D"?=??p???NDP?OZ?9j??mj??l?????I0c???????E?{? ??Q+?EDB%$??f_P??P&>????? -S???\?k?M???????H???H?g? v?,:?_?? s?? -??)????x[??k?U?????z??~mV ?1?k?Q?-e????P????$?#?Ga????'????#s???{??G/????x -?6????;r???,O?? T%h?,b7????D|?r?????BTe?z ???E|??d?B?ueZ??1??N%S????g??? ?}"(?C9r???a?:?k?D0n@?{H???????n]O??????i?? -o??e?????> endobj -133 0 obj << -/Ascent 712 -/CapHeight 712 -/Descent -213 -/FontName /REDTNG+NimbusSanL-Regu -/ItalicAngle 0 -/StemV 85 -/XHeight 523 -/FontBBox [-174 -285 1001 953] -/Flags 4 -/CharSet (/quoteright/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/A/C/D/E/F/H/I/L/M/N/O/P/S/T/W/underscore/a/c/d/e/f/h/i/l/m/n/o/r/s/t/u/v/w/x/y) -/FontFile 134 0 R ->> endobj -615 0 obj -[222 0 0 0 0 0 0 278 278 556 556 556 556 556 556 556 556 556 556 0 0 0 0 0 0 0 667 0 722 722 667 611 0 722 278 0 0 556 833 722 778 667 0 0 667 611 0 0 944 0 0 0 0 0 0 0 556 0 556 0 500 556 556 278 0 556 222 0 0 222 833 556 556 0 0 333 500 278 556 500 722 500 500 ] -endobj -131 0 obj << -/Length1 1630 -/Length2 19463 -/Length3 532 -/Length 20368 -/Filter /FlateDecode ->> -stream -x???spfo?&?v??I?V???'?m?;f??m[??c???????9S???g??????p-\?^??6?? -????1P???????@?????Y??V??[?Ah? -?+g???q?X????y@S?(???`???????;x:Y?[????5h????S?? ???h?z:[??(???m?l?v.!??U?@??`fi?((jI?K?%??@;??? -@????? ki?s????6?>L??L-?)???/??3???4????0:???8?l-????,??NFv.{?b??3?q5?'??r3?%??d??????/?????????? ?oTEQ???ba??Olg??j???_KS{?J???/?_?????3????O,c ????????o??`N??J???????3?8???Lm???a?b???????To??`??/o?Y??,]??6f?p?,c????mni????H??????[n????tn@?5?????????????'?h?$o??7$????e??>??(?o!?????7r?+G??%????Z???F?????{??.#;??=???hl???>F??6??'??j??w??0)??m?3?K?7?o?Z:?[zM-]L,fF6{?/???)???????????????ZX?X??C??U@;??Z?_??????????,??f???P?? ??z:???????7???`???x30spX?????? q????oB? ????rF.N???uc?W?????I?????????3:*.Fv??? -?Q??:9?%?_ ?o??????=?&p+??&?!Vi?.??9???:??????% -?????=?i????5????P? m??3??)???*S|??,2???HEr?\?0?*???`??????[;??n{?:D?JlH????e?r????e[?y?t?%C LA?o?dI?A???v??y ????????k?b??|b at Q?#3\S??Y????-\???JH???+b??"????I?h?`[_?? #?vS)l?? ?;???x&q????l\???{Q??Dh??C?&?s????????????|?Y??|??!I4????=*???g -?w????_R?K( -???q-???m~?Q??Q?E J?????c?r??sr"-~?s/CK#??j?%??l???MK????sRs??u?U?3?{Z$??????E????/Ky_^YO?"???7 ?X?!?%??#j?!??????e~?!:F?s???@!?Q ~?%?d??,?7Dm?n?????J?(:ZX?y??jOAHQ???T -??C??^?Q??tY??tp??H?z[?|vu?;?WW????k??+A???+#("fGr???#b??"????????V8?$??????7h?8?oj?P8E`??????HYzW0D -l# -????BC?:KR7?B??[??????????8???4=e?q?y4?? N??[5?d?_???g??????????u??M???O~8?=????)?????!7PU?]w??q+??(??%y?I??????LZ/???Y?p -??R?????zZ]` -??p{?K?)??????_?X?NfJ(?K??{7%UO(V?lp?YD>?????}?SS"P? z?DV?JC?i8'?l??????a??g?9*??????IhJ???|?????7??{ no??I -???6???d_????^ )???W???+???????????s9\???Z)E???D??2?UY????h?p?\???V?}^ ?Pm??g?-} -?6N???UEH^e?? ??g ?J??t?#?3=?M???2F6????"?????????O??>?????sp?K=?x????Ow?{??????o?B??????)R-4?|i?z_?-ld??p}?>??L?v?C??T??W[????U??"9?? -?nT??e%?C???5??~?4 -?g?????_??????;1&k??????????]????A?#} -Z5 - -M8??????????EN?S??>???? hV??I???H?????'?<1?Fv?J???D?F?M??4?+d?>?2??Oq?r?@?? ??,$ye???k????w???? -????P9?0,??L0?\???j9d?)? -j???-?????+?,d?qL$???KA???H??p?/ws?3?????~=/^G?OW?~???3?[????w?-/??????*??????T?|???3h??F???4???????:5?????? .????? -w??!?y??u*?q -??H??????3?R&???????vk^(?3+V???1?????Q?RF?f?*?I m?k??5????%??,????e{?A^??8G??1???b?$? ??C?Li?????????l?-??J??T?T?{???=??C?_??7{???Xe???$??M *?[N?L?n.5?S!?1??kB:?.=6?$?!????sq?L)? ??o??a????9???/??E?6{``?\? ?Qw?Npx??]?=?EZk?sS?4Oc ?q???ra?m?n??D?q?U?? -O???*??q??D?t 'U?C?RC?S+F:s??*A?B[2?'K?q6~??Kn????N`'??<?=???)heT?? -[???TGH???????,???%??9???X??`??[????Naf????l?a*f????rQ?D??.$?a\W`9??x?9??,??hk?Y??vN:Or?aW??? -?.??Z? -??t. -/?K???y^9???q?v8p?*?^?Cw???S??n?>?#f???tb????"f??????=$?U?????*??????po???z???????}l@?????ys???4???????t?;?????R??~??e4????v???h?w???V?????????|h?:??5???_?n,D?^@]??T"?G`d?n?z?6??O?]`!N8C?"y?P?s??????*???c??N???*~??#?V -5>??i?3??wI?????,8??D?????}???VF;{?]?5??g?x#??ca[?S????0z?{????$&"z3|B*??J)?I?#P??g?|?Bw??yv.??1?,?? -K?n?>t??q?!?=?\QP$A??s*E????w?|xQ??"?T}? ???.?? ??X?^???~???????a?????{?????*]???????7??>?????5??B#?"?M????|y? -H??6?^Be?o}?u??$??????,?"_????5??&?????????t????F???gY?)??u??L?"]~? ??#?>v^??r?obJ??????f???}??s4??2?q???&t8?D??4n?????'J].ifH_"?S?)????f??????y????W??x??P?&?Ih.?Jpl??#?????Y??%?#?5o??e?~??&Pz4e?????B????$????????.b???n -Y -??g[???Cd?I a????9???ZF????>`n???=D?5?? F???7??? L?b??i?? ?O3???N?`?#f\??_L??Rt??????[D???z????WzD?2???????j?????U??Sq??????D???\%????? ??????b -?jR?{???8????g@?Y???-wd??????4??#r?A,??7~???Ni????h???? ?k?+??3??5^????~?6????At?J?@?.EA?m;????4???&?k???'<?? '?b?X????/g1?bW??O?p8'?R?/??J!!?G?-1E??RY??-??????j?T???9???????}????v'J??a? J?-2K?xl8???_o[ ??k?M??ph}?y#??N??????6??NF?My????B??????? ????H??S????O?L?$?S7 - e?y?????g?~?8???b??_?XC??tmp=?{?#?3jXT?6??e????\"?x?E?0????3ZU]??:^?\dR??9 ? ?s???Y??????\??R?L>? -w?,???r???????a??BvJ??????g???f?? ????q>? ?M??5H?|????Z?????"?O"????????R[??deh,???u??*E????A.??\!v?d??Q.??:??b;?????Y?b?Y+?R????E~??S??6?o4???X?X?-Dr ????4T???JG?=?R?????-??N.+??f?~M?aw??d???6???&iG)???p?.??B@?Wg?e}?9??k?E=S??d????O?? -?????L??H?a?????z???? d??mo????\#?;?5?P?6?/?????r?[f??!"W?N???n???| -$??? -J??0???JT?,lNeF???a?A?????$???X?7?t??8 ?U^??a??8?z[W?5;??IJz??????????Hys??%???B?h?Q4?0?PjH? 9E?v?a?m???????nUT??e?:q??A? ??$?????????b?4?*?????E??y??%;?B3?!?l ~???T?P?1d? ?Iz?k8j???:??????$?E?E)c(_???Ew-??????4???KM'???y??3?n?8??XWa?y;G?Y*G?#??/?lv?????8x???+pY?kM?%?????L???\|?Z??x3??r ??8A[??=(?o????'5A?*?,????*(??0@?f?A??o?5#?TPO??g??U?2??6=??%????}???@???a+#U.??y?c???#/?pG???8??`1???<4?eSh?P-?B+?uz??-??? J????t9?;????0?????8c??auy?%??hA???C;%???>???J??m??3???uHJ5&???????????3wQ6I???E??M??????K?? *UK???i?7`P?????@e??E@'?w??-?"?6k'??[??U?????}P???.??]&??????~g????<"???S???X?AL??`?b79T???????R??U?/e1???????Jb?e????????F1g???????=f? ?X???IV?????h?????D?Pm??@J6????d4 at B;??3????@P???A?g??}O?k??????/s#??5I??`4?????? u>?^*????????mg??)$\?i6mr? -?t??X9?a??]u?=D??8?[??[f??ehZeK???X?pd????????\?????=?2??~rq?!???pQ??>?Hl+??`?l&/z 8E?0?1?BA?????M? ???mES?w? ?????7??U??AF?p???B?>vu#???E?17?p:??w???%_???U -???d?[@??FG?T?Q???s.??Y(J(????T?G??P?mR???M?\>Tc???1Qck???%l;?Np????i?G?u?o???2???;?????ga,??????-k???%e??`?>gO!???.?7????Q??F?D???c_~???tTM???3\???~:??OE?O?e?c?8?ZJY -'??m??4W???{?U?g?C\?~??????h?LC???n"Wt?????;??VQK?I@?4 ?_a -?Y:*B?j?????m??{?S??D?C??C-???[??I? -??4MA?\2?0??)'@8?S, ??>?>?j ?T9?????9o???iud9??$v?fG??L?'?>b?)n-????????g???c?? H? '??N1 ??? -?%e;? -8*?_?v,Z??pv????`??G?"???F1{U?[?%L?^ByT?g$?4%(??U??G?kS?&}?QIs??g?v?k? -?:&4 -M???cu?Y??_:q?_???b??T?Ej????*?z?A?`???5"|??sy??;?????dn?mG???wFW-n?vh?]?aw?_?? -??e -G???d?@??L8??3#?? -(??q"W?7?}??m?j??9B??E\f(D??G????(???UvmD-?S?P????C?{Vc$?"?L?N?????????P??vL??? ?o?????u?7,MM???????S](@??J???????;5~mV??[p?X T2 ?????bl???g????\F??????B???v??eF&_h}?1???h??j6????G? -??yy??),5????k??hIo??8?'?m?????RRF?q|?Jul?=~ -?????0wn>wP{-W?s{????? -??u)??*-wU???s?d?n???`??X{7S?? -p;>(W?,w?? ??x?{?-?Z ?,?)9=?p???+?n?3y???P????I?<?????4???;7???%4??d?cj??^P: JQ"?b?F?&???? -?????/??'????o??_c?WAY???Z??:???ww?*8 <5?XA???3??@N?s??.L?b?@??w?KP?*???????,????l??C?Jw? ??#a?T?|U?.4F????Mp?w???????s?????(?? ?o?;?? .*WU?nO??5 ;! ??m?7A???'??I?H??8x?* ?LH??ok_?@S/??X???$?a?VZS?yzK"!??_H??eX???|!?1?-?S?Q+P?L??RZT?(_^?k~?9??????Ig??????b???Y?'&???????dqk???W?\???5?f?9;y1?b??r F0? V?n?D?\[?? ? -\?a_K3???;*?v?UR?c??o??1{'??X3s??1]e?? w?H????6l?T??G`0\?SMs?`-???o???Y?????k??>}????{??.~8%.??'2??+F??????T? -?A??X??? ??i?!9@??s????0"??S?I????|?O?Eq????????}????????o@]?T???_+yh?G?? ?????7?J?P??A???7X?Us?($<*?N0j?e???u7?~?????C??Fh?J -???'??F(oW?St??,???????????p?:ck?L)??????y:,Do%?mr??`?;???????C??h!??W - -f??G4 -"?|8?,_R?-???9?w?#??a??sX???kCu\,????????[?h? \~?v?VF??qG??&??$e?????R??6?X???|X=??&??? ??N???bibl ??rb?y????????H?>?_?^|?c????`?Gk???)eW?th??kk???s^Zn???????-????]?[?8??]????:???zZ}??!V+??a????%?^8QB????A?j???sW/?K?????T???"4xN???* ????,5G?k? $???AV????????z??+?????????j$J????r?1???????Z8??*hoHV9&(??? -W?q?< ??|??????_?4?v{???NO,}??6??D~w??P? t??o?NZ?#?%Q?d)?? i? ?~?m5?!?>S???R? -??M??L?D$???k+???>??=???"?H?n6?c1??\?????,?/n???A???=?nG?O???o?!HU??2?L?}????M`??u?h??qJ??T????E???k?C[????*\?L?H???????$????+? 'Am?MW?z?L?8y??? ???N?0???????H?b???t?\?:I?T?GV ??????Z?].W?&i? ?O-?I)??? -a+?????=8FjKPosMT}U?n??}f3????,????5?#?}^A????w?-??4??Z???>8;?fj??g????V????c?????0?5? -?-????$u????B???X?%?7?P? -? /????C?~??b(?h+?? Dv?b?M????[???tC*??u????Wg8???.?O??F8?j?? ???vR*??q/z?b??i????g??)?Uh3m???b?V???`?>????q?'?[m???>?????M?BMzc?oRm???w?O????16'v?t??D??????i8[??#??Ua ???L??P?V w??P??^??\3??H?????????]%???????M?[????[ ????NLOB1?3#?????17??rL]??6??????6l.???h?k qi??d#?c??7i?%??????/@dX??M?C~?V?????L???]???'tbw?0??\?0?^w?q??jN??Cr2a???ejrPq??~?'??I?b}????? ?h????N??????V??*??F???3?3????QM??R?A??????-???|???|???3?5?p?????D Q??Nh?X?x2??N?7?tvj??)???????OU? ?%? ?????,???jd?d -dK??????u?X??????[??X??I????ay?](?????????n*?E?%.?g????@??H?EH`:?hg???Z.[X???[A??y?p?Z0?????8k?W??????8??sC?6?i?? Mp?:o?q#?????HI$?]^??G?Ysuq?LOp??j?? ??N??#?(?eL?S3??]-.3?8????e??b ???8?2? -[74??^=|???e??[???T?-7M?? f-?J???#Y2??28/UyN??;? ;?;?'???J?1??Jd????1%?,?M -V ? ???? ?O???! \?. ->/?Fn?r]?j?????d?}???? ??????VE?Qf?,??M?g??E??oy?g??????????V? -"i?k??^?N?????4U??}?Fy???7|????#=-??J?8? ??h$?O at tW|?O? ???4?]?&B?s?i>?:??g:+????>?y -?iR?????q??q??&???+?|"??a?{_.e+???O??u?n?-?2 -?W8?xb???(?????"??1??3?Vzx?:G)?m?jvE??A????m???6????????OT^>? -????/L??????8W?H7??uo?i@???'???Ug?????? ????D?????/???????????Yk????K???-hy?,G?1?2???????*R?o??:?p??Qxi???`? Jb -[????????????!6?G ??n??Y???V????a?????KIp@?? p?&.Q*7dnhts?SR??SG??(?}qS??? -6]R{??J@ K????]??P??=?\?L???L^?a?????? 9DS????~?w}????????Ob??????P(??En??T??Z?r@?z???j&W~???h?? ~?0?4?'xf?6~ud?#R????"???B#??&?&??????NF[??'&J$(??s??x????::?,?$t???????LLdba????????_;???8p?T??[?(?q??g??Br?,???8gd^?}?Jg??R??7QG?23????~?}_??x????HV7?p?2?LZ0?!q??E%????kY8?Th???2???>w????????????T?7???O??8????/3?f? -?}?"?5?>px?a???=.PB?R?ZVA?;?=.?????O??????U_?8??.d???d?4]4XrOC???g?Ls????04?Gn??["(????R?T??JE?g???0?E;&e|??Z??^[>}??*??c?????G?[??M??h??d??U???-?K??/{????8~k?3??? -??????~QS????] -{?k?{4"?S? #@???Zp=?{???p*?+??9?Wl&??H????w?*{z8?7#m` ??#?8a-??????i????8fL^C?|?,????@z?????,?>?Zs>>??$%?3?1T?k?5?$v?n???v?????q???A|?????$4 ?V? ??'3????L??{????1?s?U???Z2?0$?q?Sf??????qW???{8?zPg?|U?m?EZp???????TC]???Lz;???>??,,?9??W_?yHh%?L?${?N.?.5U?^Ss???I$??r1????^b?|???????D?=wA?}Z? ??=????9????????Wlmr??r????tt?Y?WJ?$??&?(???p????X^_i?j?5w??&?E?J???m_v*??ld+o3?GQ?_?????B?\?*??/???5???qt???o?\??d0>?8D?_P????M???H??R0z:?r!QQp?N?.??26xQ???=? d??g?+i2T?? -?A# ??g????V h?w,6??A ?!?GtOe?>??????????p? ????5???)#"X?I!???????gMQ?mH ???h ?yM]?BGN??????l?;?????S6?kI%???e?-V -?c??$F??w?tk -?h?,??-??U?%?^^G?z8 X(Yt???jV/k -?w??A???? -(t????8??b??^G)U?\??gj?#a?u????+??6+?{o??F4??I?A:V????:??????Fj7L???$???|?N????"'7?r?E??????????^S?Wc>??????j?i3??????f[????U#???????A? I?7?fut Ms ?M?}@???&7?C????lL?O?U!?E?????p ?? -????'??LJ???KK??o?I???\??#?Rf???g=????f?????| ?m8??q??T???'?>?m?????1>?p??p??????????q?{?cbi1??i????U?m??xCe5#??ox???Z????8?$^H?[7 -?????u??????7K,%bL?50V??????2??b? ?]?????1oY??????w??O??*b??z*w{???Y??????e?????%o>qM9w.????n,??~????"6g,?????7????b????6+??s????}?dp?z@?&w???u?v??K?S??8V?J? ???O6?S1a???juT???H??1??g?y??%?????x8??????z?????&???q?\??????eE????R b+??5?[?w???????>?????%??[??JY|+ ?%F??=2?????????b???e???"??id???r!???M?j~?????n??xD?:b&??&??9c???4?????_l??#zA?Y?u?b,HZ]??d{??M#C? -???t?q??E}}q??]?t? \????2??U???/?zL??W?? cU???c???_??????4?LX???'Y??}??|S??1?L?? ??F2{z?~?f????&%???s9 ???z<^(R?????-BKX???0?Y-???J:?F?I???????? -+?t!?1??+???ty???8?q?? -V?tv?b???3??z5?B?/4???????B?[~?????A??N?>N?EM??O??v?"OpW?&g??im???????be??e"??l??0r2??? -???????????N??F??????m??P???4?eL_ s????d#????v)Bs?k?A???|?#?N??P???C?$??B20S?????"?e?l>}=yQo???F#?0??=8??? ?wS???+??????9p48??0(?;? - (?wY=???c?????'o?> endobj -130 0 obj << -/Ascent 678 -/CapHeight 651 -/Descent -216 -/FontName /EXVUAL+NimbusRomNo9L-Regu -/ItalicAngle 0 -/StemV 85 -/XHeight 450 -/FontBBox [-168 -281 1000 924] -/Flags 4 -/CharSet (/fi/fl/exclam/quotedbl/numbersign/dollar/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/bullet) -/FontFile 131 0 R ->> endobj -616 0 obj -[556 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 333 408 500 500 0 778 333 333 333 500 564 250 333 250 278 500 500 500 500 500 500 500 500 500 500 278 278 564 564 564 444 921 722 667 667 722 611 556 722 722 333 389 722 611 889 722 722 556 0 667 556 611 722 722 944 722 722 0 333 278 333 0 500 0 444 500 444 500 444 333 500 500 278 278 500 278 778 500 500 500 500 333 389 278 500 500 722 500 500 444 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 350 ] -endobj -140 0 obj << -/Type /Pages -/Count 6 -/Parent 617 0 R -/Kids [126 0 R 142 0 R 180 0 R 214 0 R 259 0 R 304 0 R] ->> endobj -382 0 obj << -/Type /Pages -/Count 6 -/Parent 617 0 R -/Kids [356 0 R 384 0 R 427 0 R 481 0 R 485 0 R 494 0 R] ->> endobj -557 0 obj << -/Type /Pages -/Count 3 -/Parent 617 0 R -/Kids [525 0 R 559 0 R 592 0 R] ->> endobj -617 0 obj << -/Type /Pages -/Count 15 -/Kids [140 0 R 382 0 R 557 0 R] ->> endobj -618 0 obj << -/Type /Outlines -/First 7 0 R -/Last 107 0 R -/Count 6 ->> endobj -123 0 obj << -/Title 124 0 R -/A 121 0 R -/Parent 107 0 R -/Prev 111 0 R ->> endobj -119 0 obj << -/Title 120 0 R -/A 117 0 R -/Parent 111 0 R -/Prev 115 0 R ->> endobj -115 0 obj << -/Title 116 0 R -/A 113 0 R -/Parent 111 0 R -/Next 119 0 R ->> endobj -111 0 obj << -/Title 112 0 R -/A 109 0 R -/Parent 107 0 R -/Next 123 0 R -/First 115 0 R -/Last 119 0 R -/Count -2 ->> endobj -107 0 obj << -/Title 108 0 R -/A 105 0 R -/Parent 618 0 R -/Prev 103 0 R -/First 111 0 R -/Last 123 0 R -/Count -2 ->> endobj -103 0 obj << -/Title 104 0 R -/A 101 0 R -/Parent 618 0 R -/Prev 83 0 R -/Next 107 0 R ->> endobj -99 0 obj << -/Title 100 0 R -/A 97 0 R -/Parent 83 0 R -/Prev 95 0 R ->> endobj -95 0 obj << -/Title 96 0 R -/A 93 0 R -/Parent 83 0 R -/Prev 91 0 R -/Next 99 0 R ->> endobj -91 0 obj << -/Title 92 0 R -/A 89 0 R -/Parent 83 0 R -/Prev 87 0 R -/Next 95 0 R ->> endobj -87 0 obj << -/Title 88 0 R -/A 85 0 R -/Parent 83 0 R -/Next 91 0 R ->> endobj -83 0 obj << -/Title 84 0 R -/A 81 0 R -/Parent 618 0 R -/Prev 71 0 R -/Next 103 0 R -/First 87 0 R -/Last 99 0 R -/Count -4 ->> endobj -79 0 obj << -/Title 80 0 R -/A 77 0 R -/Parent 71 0 R -/Prev 75 0 R ->> endobj -75 0 obj << -/Title 76 0 R -/A 73 0 R -/Parent 71 0 R -/Next 79 0 R ->> endobj -71 0 obj << -/Title 72 0 R -/A 69 0 R -/Parent 618 0 R -/Prev 11 0 R -/Next 83 0 R -/First 75 0 R -/Last 79 0 R -/Count -2 ->> endobj -67 0 obj << -/Title 68 0 R -/A 65 0 R -/Parent 63 0 R ->> endobj -63 0 obj << -/Title 64 0 R -/A 61 0 R -/Parent 11 0 R -/Prev 59 0 R -/First 67 0 R -/Last 67 0 R -/Count -1 ->> endobj -59 0 obj << -/Title 60 0 R -/A 57 0 R -/Parent 11 0 R -/Prev 55 0 R -/Next 63 0 R ->> endobj -55 0 obj << -/Title 56 0 R -/A 53 0 R -/Parent 11 0 R -/Prev 51 0 R -/Next 59 0 R ->> endobj -51 0 obj << -/Title 52 0 R -/A 49 0 R -/Parent 11 0 R -/Prev 47 0 R -/Next 55 0 R ->> endobj -47 0 obj << -/Title 48 0 R -/A 45 0 R -/Parent 11 0 R -/Prev 43 0 R -/Next 51 0 R ->> endobj -43 0 obj << -/Title 44 0 R -/A 41 0 R -/Parent 11 0 R -/Prev 23 0 R -/Next 47 0 R ->> endobj -39 0 obj << -/Title 40 0 R -/A 37 0 R -/Parent 23 0 R -/Prev 35 0 R ->> endobj -35 0 obj << -/Title 36 0 R -/A 33 0 R -/Parent 23 0 R -/Prev 31 0 R -/Next 39 0 R ->> endobj -31 0 obj << -/Title 32 0 R -/A 29 0 R -/Parent 23 0 R -/Prev 27 0 R -/Next 35 0 R ->> endobj -27 0 obj << -/Title 28 0 R -/A 25 0 R -/Parent 23 0 R -/Next 31 0 R ->> endobj -23 0 obj << -/Title 24 0 R -/A 21 0 R -/Parent 11 0 R -/Prev 15 0 R -/Next 43 0 R -/First 27 0 R -/Last 39 0 R -/Count -4 ->> endobj -19 0 obj << -/Title 20 0 R -/A 17 0 R -/Parent 15 0 R ->> endobj -15 0 obj << -/Title 16 0 R -/A 13 0 R -/Parent 11 0 R -/Next 23 0 R -/First 19 0 R -/Last 19 0 R -/Count -1 ->> endobj -11 0 obj << -/Title 12 0 R -/A 9 0 R -/Parent 618 0 R -/Prev 7 0 R -/Next 71 0 R -/First 15 0 R -/Last 63 0 R -/Count -8 ->> endobj -7 0 obj << -/Title 8 0 R -/A 5 0 R -/Parent 618 0 R -/Next 11 0 R ->> endobj -619 0 obj << -/Names [(Doc-Start) 136 0 R (Item.1) 307 0 R (Item.10) 562 0 R (Item.11) 563 0 R (Item.12) 597 0 R (Item.13) 598 0 R (Item.14) 599 0 R (Item.15) 600 0 R (Item.16) 601 0 R (Item.17) 602 0 R (Item.18) 603 0 R (Item.19) 604 0 R (Item.2) 308 0 R (Item.20) 605 0 R (Item.3) 309 0 R (Item.4) 360 0 R (Item.5) 361 0 R (Item.6) 362 0 R (Item.7) 554 0 R (Item.8) 555 0 R (Item.9) 556 0 R (_beagle) 491 0 R (_bionimbus) 513 0 R (_coaster_providers_local_ssh_pbs) 489 0 R (_coasters) 453 0 R (_debugging_swift) 553 0 R (_environment_setup) 205 0 R (_first_swiftscript) 262 0 R (_for_advanced_users) 488 0 R (_installation) 186 0 R (_log_processing) 564 0 R (_make_a_basic_block_allocation_plot_from_coasters_block_log_lines) 586 0 R (_make_a_basic_job_completion_plot_from_coasters_cpu_log_lines) 581 0 R (_make_a_basic_load_plot_from_coasters_cpu_log_lines) 568 0 R (_mappers) 363 0 R (_osg) 512 0 R (_overview) 183 0 R (_pads) 497 0 R (_passing_an_array_to_swift) 359 0 R (_prerequisites) 187 0 R ( _problem_reporting) 595 0 R (_resuming_a_stopped_or_crashed_swift_run) 317 0 R (_second_swiftscript) 284 0 R (_setting_sites_xml) 248 0 R (_setting_swift_configuration) 232 0 R (_setting_transformation_catalog) 219 0 R (_setting_up_to_run_swift) 201 0 R (_swift_basics) 185 0 R (_swift_commandline_options) 301 0 R (_swift_on_diverse_infrastructures) 490 0 R (_what_if_swift_hangs) 302 0 R (lstlisting.-1) 188 0 R (lstlisting.-10) 285 0 R (lstlisting.-11) 310 0 R (lstlisting.-12) 318 0 R (lstlisting.-13) 329 0 R (lstlisting.-14) 364 0 R (lstlisting.-15) 366 0 R (lstlisting.-16) 387 0 R (lstlisting.-17) 394 0 R (lstlisting.-18) 396 0 R (lstlisting.-19) 402 0 R (lstlisting.-2) 203 0 R (lstlisting.-20) 411 0 R (lstlisting.-21) 455 0 R (lstlisting.-22) 498 0 R (lstlisting.-23) 500 0 R (lstlisting.-24) 514 0 R (lstlisting.-25) 528 0 R (lstlisting.-26) 533 0 R (lstlisting.-27) 565 0 R (lstlisting.-28) 569 0 R (lstlisting.-29) 571 0 R (lstlisting.-3) 206 0 R (lstlisting.-30) 573 0 R (l stlisting.-31) 575 0 R (lstlisting.-32) 577 0 R (lstlisting.-33) 579 0 R (lstlisting.-34) 582 0 R (lstlisting.-35) 584 0 R (lstlisting.-36) 587 0 R (lstlisting.-37) 589 0 R (lstlisting.-4) 208 0 R (lstlisting.-5) 217 0 R (lstlisting.-6) 220 0 R (lstlisting.-7) 234 0 R (lstlisting.-8) 249 0 R (lstlisting.-9) 263 0 R (lstnumber.-1.1) 189 0 R (lstnumber.-1.2) 193 0 R (lstnumber.-1.3) 194 0 R (lstnumber.-1.4) 195 0 R (lstnumber.-1.5) 196 0 R (lstnumber.-1.6) 197 0 R (lstnumber.-1.7) 198 0 R (lstnumber.-1.8) 199 0 R (lstnumber.-1.9) 200 0 R (lstnumber.-10.1) 286 0 R (lstnumber.-10.10) 295 0 R (lstnumber.-10.11) 296 0 R (lstnumber.-10.12) 297 0 R (lstnumber.-10.13) 298 0 R (lstnumber.-10.14) 299 0 R (lstnumber.-10.15) 300 0 R (lstnumber.-10.2) 287 0 R (lstnumber.-10.3) 288 0 R (lstnumber.-10.4) 289 0 R (lstnumber.-10.5) 290 0 R (lstnumber.-10.6) 291 0 R (lstnumber.-10.7) 292 0 R (lstnumber.-10.8) 293 0 R (lstnumber.-10.9) 294 0 R (lstnumber.-11.1) 311 0 R (lstnumber.-11.2) 312 0 R (lstnumber.-11.3) 313 0 R (lstnumber.-11.4) 314 0 R (lstnumber.-11.5) 315 0 R (lstnumber.-11.6) 316 0 R (lstnumber.-12.1) 319 0 R (lstnumber.-12.10) 328 0 R (lstnumber.-12.2) 320 0 R (lstnumber.-12.3) 321 0 R (lstnumber.-12.4) 322 0 R (lstnumber.-12.5) 323 0 R (lstnumber.-12.6) 324 0 R (lstnumber.-12.7) 325 0 R (lstnumber.-12.8) 326 0 R (lstnumber.-12.9) 327 0 R (lstnumber.-13.1) 330 0 R (lstnumber.-13.10) 339 0 R (lstnumber.-13.11) 340 0 R (lstnumber.-13.12) 341 0 R (lstnumber.-13.13) 342 0 R (lstnumber.-13.14) 343 0 R (lstnumber.-13.15) 344 0 R (lstnumber.-13.16) 345 0 R (lstnumber.-13.17) 346 0 R (lstnumber.-13.18) 347 0 R (lstnumber.-13.19) 348 0 R (lstnumber.-13.2) 331 0 R (lstnumber.-13.20) 349 0 R (lstnumber.-13.21) 350 0 R (lstnumber.-13.22) 351 0 R (lstnumber.-13.23) 352 0 R (lstnumber.-13.24) 353 0 R (lstnumber.-13.25) 354 0 R (lstnumber.-13.3) 332 0 R (lstnumber.-13.4) 333 0 R (lstnumber.-13.5) 334 0 R (lstnumber.-13.6) 335 0 R (lstnumber.-13.7) 336 0 R (lstnumbe r.-13.8) 337 0 R (lstnumber.-13.9) 338 0 R (lstnumber.-14.1) 365 0 R (lstnumber.-15.1) 367 0 R (lstnumber.-15.10) 376 0 R (lstnumber.-15.11) 377 0 R (lstnumber.-15.12) 378 0 R (lstnumber.-15.13) 379 0 R (lstnumber.-15.14) 380 0 R (lstnumber.-15.15) 381 0 R (lstnumber.-15.2) 368 0 R (lstnumber.-15.3) 369 0 R (lstnumber.-15.4) 370 0 R (lstnumber.-15.5) 371 0 R (lstnumber.-15.6) 372 0 R (lstnumber.-15.7) 373 0 R (lstnumber.-15.8) 374 0 R (lstnumber.-15.9) 375 0 R (lstnumber.-16.1) 388 0 R (lstnumber.-16.2) 389 0 R (lstnumber.-16.3) 390 0 R (lstnumber.-16.4) 391 0 R (lstnumber.-16.5) 392 0 R (lstnumber.-16.6) 393 0 R (lstnumber.-17.1) 395 0 R (lstnumber.-18.1) 397 0 R (lstnumber.-18.2) 398 0 R (lstnumber.-18.3) 399 0 R (lstnumber.-18.4) 400 0 R (lstnumber.-18.5) 401 0 R (lstnumber.-19.1) 403 0 R (lstnumber.-19.2) 404 0 R (lstnumber.-19.3) 405 0 R (lstnumber.-19.4) 406 0 R (lstnumber.-19.5) 407 0 R (lstnumber.-19.6) 408 0 R (lstnumber.-19.7) 409 0 R (lstnumber.-19.8) 410 0 R (lst number.-2.1) 204 0 R (lstnumber.-20.1) 412 0 R (lstnumber.-20.10) 421 0 R (lstnumber.-20.11) 422 0 R (lstnumber.-20.12) 423 0 R (lstnumber.-20.13) 424 0 R (lstnumber.-20.14) 425 0 R (lstnumber.-20.15) 430 0 R (lstnumber.-20.16) 431 0 R (lstnumber.-20.17) 432 0 R (lstnumber.-20.18) 433 0 R (lstnumber.-20.19) 434 0 R (lstnumber.-20.2) 413 0 R (lstnumber.-20.20) 435 0 R (lstnumber.-20.21) 436 0 R (lstnumber.-20.22) 437 0 R (lstnumber.-20.23) 438 0 R (lstnumber.-20.24) 439 0 R (lstnumber.-20.25) 440 0 R (lstnumber.-20.26) 441 0 R (lstnumber.-20.27) 442 0 R (lstnumber.-20.28) 443 0 R (lstnumber.-20.29) 444 0 R (lstnumber.-20.3) 414 0 R (lstnumber.-20.30) 445 0 R (lstnumber.-20.31) 446 0 R (lstnumber.-20.32) 447 0 R (lstnumber.-20.33) 448 0 R (lstnumber.-20.34) 449 0 R (lstnumber.-20.35) 450 0 R (lstnumber.-20.36) 451 0 R (lstnumber.-20.37) 452 0 R (lstnumber.-20.4) 415 0 R (lstnumber.-20.5) 416 0 R (lstnumber.-20.6) 417 0 R (lstnumber.-20.7) 418 0 R (lstnumber.-20.8) 419 0 R (lst number.-20.9) 420 0 R (lstnumber.-21.1) 456 0 R (lstnumber.-21.10) 465 0 R (lstnumber.-21.11) 466 0 R (lstnumber.-21.12) 467 0 R (lstnumber.-21.13) 468 0 R (lstnumber.-21.14) 469 0 R (lstnumber.-21.15) 470 0 R (lstnumber.-21.16) 471 0 R (lstnumber.-21.17) 472 0 R (lstnumber.-21.18) 473 0 R (lstnumber.-21.19) 474 0 R (lstnumber.-21.2) 457 0 R (lstnumber.-21.20) 475 0 R (lstnumber.-21.21) 476 0 R (lstnumber.-21.22) 477 0 R (lstnumber.-21.23) 478 0 R (lstnumber.-21.24) 479 0 R (lstnumber.-21.3) 458 0 R (lstnumber.-21.4) 459 0 R (lstnumber.-21.5) 460 0 R (lstnumber.-21.6) 461 0 R (lstnumber.-21.7) 462 0 R (lstnumber.-21.8) 463 0 R (lstnumber.-21.9) 464 0 R (lstnumber.-22.1) 499 0 R (lstnumber.-23.1) 501 0 R (lstnumber.-23.10) 510 0 R (lstnumber.-23.11) 511 0 R (lstnumber.-23.2) 502 0 R (lstnumber.-23.3) 503 0 R (lstnumber.-23.4) 504 0 R (lstnumber.-23.5) 505 0 R (lstnumber.-23.6) 506 0 R (lstnumber.-23.7) 507 0 R (lstnumber.-23.8) 508 0 R (lstnumber.-23.9) 509 0 R (lstnumber.-24 .1) 515 0 R (lstnumber.-24.2) 516 0 R (lstnumber.-24.3) 517 0 R (lstnumber.-24.4) 518 0 R (lstnumber.-24.5) 519 0 R (lstnumber.-24.6) 520 0 R (lstnumber.-24.7) 521 0 R (lstnumber.-24.8) 522 0 R (lstnumber.-24.9) 523 0 R (lstnumber.-25.1) 529 0 R (lstnumber.-26.1) 534 0 R (lstnumber.-26.10) 543 0 R (lstnumber.-26.11) 544 0 R (lstnumber.-26.12) 545 0 R (lstnumber.-26.13) 546 0 R (lstnumber.-26.14) 547 0 R (lstnumber.-26.15) 548 0 R (lstnumber.-26.16) 549 0 R (lstnumber.-26.17) 550 0 R (lstnumber.-26.18) 551 0 R (lstnumber.-26.19) 552 0 R (lstnumber.-26.2) 535 0 R (lstnumber.-26.3) 536 0 R (lstnumber.-26.4) 537 0 R (lstnumber.-26.5) 538 0 R (lstnumber.-26.6) 539 0 R (lstnumber.-26.7) 540 0 R (lstnumber.-26.8) 541 0 R (lstnumber.-26.9) 542 0 R (lstnumber.-27.1) 566 0 R (lstnumber.-27.2) 567 0 R (lstnumber.-28.1) 570 0 R (lstnumber.-29.1) 572 0 R (lstnumber.-3.1) 207 0 R (lstnumber.-30.1) 574 0 R (lstnumber.-31.1) 576 0 R (lstnumber.-32.1) 578 0 R (lstnumber.-33.1) 580 0 R (lstnu mber.-34.1) 583 0 R (lstnumber.-35.1) 585 0 R (lstnumber.-36.1) 588 0 R (lstnumber.-37.1) 590 0 R (lstnumber.-4.1) 209 0 R (lstnumber.-5.1) 218 0 R (lstnumber.-6.1) 221 0 R (lstnumber.-6.2) 222 0 R (lstnumber.-7.1) 235 0 R (lstnumber.-7.10) 244 0 R (lstnumber.-7.11) 245 0 R (lstnumber.-7.12) 246 0 R (lstnumber.-7.13) 247 0 R (lstnumber.-7.2) 236 0 R (lstnumber.-7.3) 237 0 R (lstnumber.-7.4) 238 0 R (lstnumber.-7.5) 239 0 R (lstnumber.-7.6) 240 0 R (lstnumber.-7.7) 241 0 R (lstnumber.-7.8) 242 0 R (lstnumber.-7.9) 243 0 R (lstnumber.-8.1) 250 0 R (lstnumber.-8.2) 251 0 R (lstnumber.-8.3) 252 0 R (lstnumber.-8.4) 253 0 R (lstnumber.-8.5) 254 0 R (lstnumber.-8.6) 255 0 R (lstnumber.-8.7) 256 0 R (lstnumber.-8.8) 257 0 R (lstnumber.-9.1) 264 0 R (lstnumber.-9.10) 273 0 R (lstnumber.-9.11) 274 0 R (lstnumber.-9.12) 275 0 R (lstnumber.-9.13) 276 0 R (lstnumber.-9.14) 277 0 R (lstnumber.-9.15) 278 0 R (lstnumber.-9.16) 279 0 R (lstnumber.-9.17) 280 0 R (lstnumber.-9.18) 281 0 R (ls tnumber.-9.19) 282 0 R (lstnumber.-9.2) 265 0 R (lstnumber.-9.3) 266 0 R (lstnumber.-9.4) 267 0 R (lstnumber.-9.5) 268 0 R (lstnumber.-9.6) 269 0 R (lstnumber.-9.7) 270 0 R (lstnumber.-9.8) 271 0 R (lstnumber.-9.9) 272 0 R (page.1) 182 0 R (page.10) 496 0 R (page.11) 527 0 R (page.12) 561 0 R (page.13) 594 0 R (page.2) 216 0 R (page.3) 261 0 R (page.4) 306 0 R (page.5) 358 0 R (page.6) 386 0 R (page.7) 429 0 R (page.8) 483 0 R (page.9) 487 0 R (page.i) 129 0 R (page.ii) 144 0 R (section.1) 6 0 R (section.2) 10 0 R (section.3) 70 0 R (section.4) 82 0 R (section.5) 102 0 R (section.6) 106 0 R (subsection.2.1) 14 0 R (subsection.2.2) 22 0 R (subsection.2.3) 42 0 R (subsection.2.4) 46 0 R (subsection.2.5) 50 0 R (subsection.2.6) 54 0 R (subsection.2.7) 58 0 R (subsection.2.8) 62 0 R (subsection.3.1) 74 0 R (subsection.3.2) 78 0 R (subsection.4.1) 86 0 R (subsection.4.2) 90 0 R (subsection.4.3) 94 0 R (subsection.4.4) 98 0 R (subsection.6.1) 110 0 R (subsection.6.2) 122 0 R (subs ubsection.2.1.1) 18 0 R (subsubsection.2.2.1) 26 0 R (subsubsection.2.2.2) 30 0 R (subsubsection.2.2.3) 34 0 R (subsubsection.2.2.4) 38 0 R (subsubsection.2.8.1) 66 0 R (subsubsection.6.1.1) 114 0 R (subsubsection.6.1.2) 118 0 R] -/Limits [(Doc-Start) (subsubsection.6.1.2)] ->> endobj -620 0 obj << -/Kids [619 0 R] ->> endobj -621 0 obj << -/Dests 620 0 R ->> endobj -622 0 obj << -/Type /Catalog -/Pages 617 0 R -/Outlines 618 0 R -/Names 621 0 R -/PageMode /UseOutlines -/OpenAction 125 0 R ->> endobj -623 0 obj << -/Author(Swift team)/Title(Swift Cookbook)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() -/CreationDate (D:20110516141543-05'00') -/PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) ->> endobj -xref -0 624 -0000000001 65535 f -0000000002 00000 f -0000000003 00000 f -0000000004 00000 f -0000000000 00000 f -0000000009 00000 n -0000017512 00000 n -0000197747 00000 n -0000000054 00000 n -0000000080 00000 n -0000017636 00000 n -0000197624 00000 n -0000000125 00000 n -0000000156 00000 n -0000017761 00000 n -0000197513 00000 n -0000000207 00000 n -0000000238 00000 n -0000017886 00000 n -0000197452 00000 n -0000000294 00000 n -0000000326 00000 n -0000018640 00000 n -0000197328 00000 n -0000000377 00000 n -0000000419 00000 n -0000018891 00000 n -0000197254 00000 n -0000000475 00000 n -0000000511 00000 n -0000024963 00000 n -0000197167 00000 n -0000000567 00000 n -0000000616 00000 n -0000025277 00000 n -0000197080 00000 n -0000000672 00000 n -0000000718 00000 n -0000026281 00000 n -0000197006 00000 n -0000000774 00000 n -0000000810 00000 n -0000031939 00000 n -0000196919 00000 n -0000000861 00000 n -0000000897 00000 n -0000033321 00000 n -0000196832 00000 n -0000000948 00000 n -0000000985 00000 n -0000034452 00000 n -0000196745 00000 n -0000001036 00000 n -0000001080 00000 n -0000034577 00000 n -0000196658 00000 n -0000001131 00000 n -0000001169 00000 n -0000042833 00000 n -0000196571 00000 n -0000001220 00000 n -0000001278 00000 n -0000049927 00000 n -0000196460 00000 n -0000001329 00000 n -0000001374 00000 n -0000050241 00000 n -0000196399 00000 n -0000001430 00000 n -0000001456 00000 n -0000068232 00000 n -0000196274 00000 n -0000001502 00000 n -0000001529 00000 n -0000074711 00000 n -0000196200 00000 n -0000001580 00000 n -0000001617 00000 n -0000074835 00000 n -0000196126 00000 n -0000001668 00000 n -0000001721 00000 n -0000074960 00000 n -0000196000 00000 n -0000001767 00000 n -0000001818 00000 n -0000075085 00000 n -0000195926 00000 n -0000001869 00000 n -0000001894 00000 n -0000079739 00000 n -0000195839 00000 n -0000001945 00000 n -0000001968 00000 n -0000080744 00000 n -0000195752 00000 n -0000002019 00000 n -0000002041 00000 n -0000080869 00000 n -0000195677 00000 n -0000002092 00000 n -0000002121 00000 n -0000089288 00000 n -0000195585 00000 n -0000002168 00000 n -0000002203 00000 n -0000094884 00000 n -0000195467 00000 n -0000002250 00000 n -0000002284 00000 n -0000095199 00000 n -0000195349 00000 n -0000002336 00000 n -0000002406 00000 n -0000096080 00000 n -0000195270 00000 n -0000002463 00000 n -0000002543 00000 n -0000096456 00000 n -0000195191 00000 n -0000002600 00000 n -0000002684 00000 n -0000098747 00000 n -0000195112 00000 n -0000002736 00000 n -0000002773 00000 n -0000003183 00000 n -0000003431 00000 n -0000002826 00000 n -0000003305 00000 n -0000193559 00000 n -0000172896 00000 n -0000193386 00000 n -0000172255 00000 n -0000164316 00000 n -0000172084 00000 n -0000003368 00000 n -0000163588 00000 n -0000152003 00000 n -0000163418 00000 n -0000194632 00000 n -0000011340 00000 n -0000006110 00000 n -0000003529 00000 n -0000011277 00000 n -0000006484 00000 n -0000151224 00000 n -0000135699 00000 n -0000151051 00000 n -0000006638 00000 n -0000006793 00000 n -0000006953 00000 n -0000007118 00000 n -0000007278 00000 n -0000007440 00000 n -0000007605 00000 n -0000007770 00000 n -0000007935 00000 n -0000008092 00000 n -0000008251 00000 n -0000008411 00000 n -0000008571 00000 n -0000008728 00000 n -0000008888 00000 n -0000009053 00000 n -0000009208 00000 n -0000009368 00000 n -0000009528 00000 n -0000009683 00000 n -0000009843 00000 n -0000010000 00000 n -0000010160 00000 n -0000010320 00000 n -0000010475 00000 n -0000010627 00000 n -0000010787 00000 n -0000010952 00000 n -0000011117 00000 n -0000016152 00000 n -0000019266 00000 n -0000016002 00000 n -0000011451 00000 n -0000017449 00000 n -0000017573 00000 n -0000017041 00000 n -0000017698 00000 n -0000017823 00000 n -0000017948 00000 n -0000018011 00000 n -0000018074 00000 n -0000134755 00000 n -0000115700 00000 n -0000134584 00000 n -0000018137 00000 n -0000018200 00000 n -0000018263 00000 n -0000018326 00000 n -0000018388 00000 n -0000018451 00000 n -0000018514 00000 n -0000018577 00000 n -0000018702 00000 n -0000017245 00000 n -0000018765 00000 n -0000018828 00000 n -0000018951 00000 n -0000019014 00000 n -0000019077 00000 n -0000019140 00000 n -0000019203 00000 n -0000016838 00000 n -0000016973 00000 n -0000017020 00000 n -0000026970 00000 n -0000024407 00000 n -0000019418 00000 n -0000024774 00000 n -0000024837 00000 n -0000024900 00000 n -0000025025 00000 n -0000025088 00000 n -0000025151 00000 n -0000025214 00000 n -0000115373 00000 n -0000113916 00000 n -0000115212 00000 n -0000113581 00000 n -0000111726 00000 n -0000113420 00000 n -0000111161 00000 n -0000101424 00000 n -0000110984 00000 n -0000025339 00000 n -0000024549 00000 n -0000025402 00000 n -0000025463 00000 n -0000025526 00000 n -0000025589 00000 n -0000025652 00000 n -0000025715 00000 n -0000025778 00000 n -0000025840 00000 n -0000025903 00000 n -0000025966 00000 n -0000026029 00000 n -0000026092 00000 n -0000026155 00000 n -0000026218 00000 n -0000026342 00000 n -0000026405 00000 n -0000026468 00000 n -0000026531 00000 n -0000026594 00000 n -0000026657 00000 n -0000026719 00000 n -0000026782 00000 n -0000026845 00000 n -0000026908 00000 n -0000034702 00000 n -0000031531 00000 n -0000027133 00000 n -0000031876 00000 n -0000032001 00000 n -0000032064 00000 n -0000032126 00000 n -0000032189 00000 n -0000032252 00000 n -0000032315 00000 n -0000032378 00000 n -0000032441 00000 n -0000032504 00000 n -0000032566 00000 n -0000032629 00000 n -0000032692 00000 n -0000032755 00000 n -0000032818 00000 n -0000032881 00000 n -0000032944 00000 n -0000033007 00000 n -0000033070 00000 n -0000033133 00000 n -0000033195 00000 n -0000033258 00000 n -0000031673 00000 n -0000033383 00000 n -0000033446 00000 n -0000033509 00000 n -0000033572 00000 n -0000033635 00000 n -0000033697 00000 n -0000033760 00000 n -0000033823 00000 n -0000033886 00000 n -0000033949 00000 n -0000034012 00000 n -0000034075 00000 n -0000034138 00000 n -0000034201 00000 n -0000034264 00000 n -0000034327 00000 n -0000034389 00000 n -0000034514 00000 n -0000034639 00000 n -0000045285 00000 n -0000042019 00000 n -0000034826 00000 n -0000042141 00000 n -0000042204 00000 n -0000042267 00000 n -0000042330 00000 n -0000042393 00000 n -0000042456 00000 n -0000042519 00000 n -0000042581 00000 n -0000042644 00000 n -0000042707 00000 n -0000042770 00000 n -0000042895 00000 n -0000042958 00000 n -0000043021 00000 n -0000043084 00000 n -0000043147 00000 n -0000043210 00000 n -0000043273 00000 n -0000043336 00000 n -0000043399 00000 n -0000043462 00000 n -0000043525 00000 n -0000043588 00000 n -0000043650 00000 n -0000043713 00000 n -0000043776 00000 n -0000043838 00000 n -0000043901 00000 n -0000043964 00000 n -0000044027 00000 n -0000044090 00000 n -0000044153 00000 n -0000044216 00000 n -0000044279 00000 n -0000044342 00000 n -0000044405 00000 n -0000044467 00000 n -0000044530 00000 n -0000044593 00000 n -0000044656 00000 n -0000044719 00000 n -0000044782 00000 n -0000044845 00000 n -0000044908 00000 n -0000044971 00000 n -0000045034 00000 n -0000045097 00000 n -0000045159 00000 n -0000045222 00000 n -0000051498 00000 n -0000049742 00000 n -0000045409 00000 n -0000049864 00000 n -0000049989 00000 n -0000050052 00000 n -0000050115 00000 n -0000050178 00000 n -0000050303 00000 n -0000050366 00000 n -0000050429 00000 n -0000050492 00000 n -0000050555 00000 n -0000050618 00000 n -0000050680 00000 n -0000050743 00000 n -0000050806 00000 n -0000050869 00000 n -0000050932 00000 n -0000050995 00000 n -0000051058 00000 n -0000051121 00000 n -0000051184 00000 n -0000051247 00000 n -0000051309 00000 n -0000051372 00000 n -0000051435 00000 n -0000194749 00000 n -0000059343 00000 n -0000056705 00000 n -0000051609 00000 n -0000056827 00000 n -0000056890 00000 n -0000056953 00000 n -0000057016 00000 n -0000057079 00000 n -0000057142 00000 n -0000057205 00000 n -0000057268 00000 n -0000057331 00000 n -0000057394 00000 n -0000057457 00000 n -0000057519 00000 n -0000057582 00000 n -0000057645 00000 n -0000057708 00000 n -0000057771 00000 n -0000057834 00000 n -0000057897 00000 n -0000057960 00000 n -0000058023 00000 n -0000058086 00000 n -0000058148 00000 n -0000058211 00000 n -0000058274 00000 n -0000058337 00000 n -0000058400 00000 n -0000058463 00000 n -0000058526 00000 n -0000058589 00000 n -0000058652 00000 n -0000058714 00000 n -0000058777 00000 n -0000058840 00000 n -0000058903 00000 n -0000058966 00000 n -0000059029 00000 n -0000059092 00000 n -0000059155 00000 n -0000059218 00000 n -0000059281 00000 n -0000069929 00000 n -0000066368 00000 n -0000059441 00000 n -0000066723 00000 n -0000066786 00000 n -0000066849 00000 n -0000066912 00000 n -0000066975 00000 n -0000067038 00000 n -0000067100 00000 n -0000067163 00000 n -0000067226 00000 n -0000067289 00000 n -0000067352 00000 n -0000067415 00000 n -0000067478 00000 n -0000067541 00000 n -0000067604 00000 n -0000067667 00000 n -0000067728 00000 n -0000067791 00000 n -0000067854 00000 n -0000067917 00000 n -0000067980 00000 n -0000068043 00000 n -0000068106 00000 n -0000068169 00000 n -0000068294 00000 n -0000066510 00000 n -0000068357 00000 n -0000068420 00000 n -0000068483 00000 n -0000068545 00000 n -0000068608 00000 n -0000068671 00000 n -0000068734 00000 n -0000068797 00000 n -0000068860 00000 n -0000068923 00000 n -0000068986 00000 n -0000069049 00000 n -0000069112 00000 n -0000069174 00000 n -0000069237 00000 n -0000069300 00000 n -0000069363 00000 n -0000069426 00000 n -0000069489 00000 n -0000069552 00000 n -0000069615 00000 n -0000069678 00000 n -0000069741 00000 n -0000069803 00000 n -0000069866 00000 n -0000070639 00000 n -0000070454 00000 n -0000070066 00000 n -0000070576 00000 n -0000075209 00000 n -0000074306 00000 n -0000070724 00000 n -0000074648 00000 n -0000074773 00000 n -0000074897 00000 n -0000075022 00000 n -0000075147 00000 n -0000074448 00000 n -0000081621 00000 n -0000079554 00000 n -0000075333 00000 n -0000079676 00000 n -0000079801 00000 n -0000079864 00000 n -0000079927 00000 n -0000079990 00000 n -0000080052 00000 n -0000080115 00000 n -0000080178 00000 n -0000080241 00000 n -0000080304 00000 n -0000080367 00000 n -0000080429 00000 n -0000080492 00000 n -0000080555 00000 n -0000080618 00000 n -0000080681 00000 n -0000080806 00000 n -0000080931 00000 n -0000080994 00000 n -0000081057 00000 n -0000081120 00000 n -0000081180 00000 n -0000081243 00000 n -0000081306 00000 n -0000081369 00000 n -0000081432 00000 n -0000081495 00000 n -0000081558 00000 n -0000089602 00000 n -0000087161 00000 n -0000081758 00000 n -0000087841 00000 n -0000087904 00000 n -0000087967 00000 n -0000087319 00000 n -0000087494 00000 n -0000087667 00000 n -0000088030 00000 n -0000088093 00000 n -0000088156 00000 n -0000088219 00000 n -0000088282 00000 n -0000088345 00000 n -0000088408 00000 n -0000088470 00000 n -0000088533 00000 n -0000088596 00000 n -0000088659 00000 n -0000088722 00000 n -0000088785 00000 n -0000088848 00000 n -0000088911 00000 n -0000088974 00000 n -0000089037 00000 n -0000089099 00000 n -0000089162 00000 n -0000089225 00000 n -0000089351 00000 n -0000089414 00000 n -0000089477 00000 n -0000089540 00000 n -0000194866 00000 n -0000096833 00000 n -0000094573 00000 n -0000089752 00000 n -0000094695 00000 n -0000094758 00000 n -0000094821 00000 n -0000094947 00000 n -0000095010 00000 n -0000095073 00000 n -0000095136 00000 n -0000095262 00000 n -0000095325 00000 n -0000095388 00000 n -0000095451 00000 n -0000095514 00000 n -0000095577 00000 n -0000095639 00000 n -0000095702 00000 n -0000095765 00000 n -0000095828 00000 n -0000095891 00000 n -0000095954 00000 n -0000096017 00000 n -0000096143 00000 n -0000096204 00000 n -0000096267 00000 n -0000096330 00000 n -0000096393 00000 n -0000096519 00000 n -0000096582 00000 n -0000096645 00000 n -0000096708 00000 n -0000096770 00000 n -0000099438 00000 n -0000098359 00000 n -0000096957 00000 n -0000098684 00000 n -0000098810 00000 n -0000098501 00000 n -0000098873 00000 n -0000098936 00000 n -0000098999 00000 n -0000099062 00000 n -0000099124 00000 n -0000099187 00000 n -0000099250 00000 n -0000099312 00000 n -0000099375 00000 n -0000099536 00000 n -0000111426 00000 n -0000113821 00000 n -0000113797 00000 n -0000115610 00000 n -0000115585 00000 n -0000135325 00000 n -0000151621 00000 n -0000163948 00000 n -0000172614 00000 n -0000194140 00000 n -0000194959 00000 n -0000195037 00000 n -0000197819 00000 n -0000208006 00000 n -0000208045 00000 n -0000208083 00000 n -0000208213 00000 n -trailer -<< -/Size 624 -/Root 622 0 R -/Info 623 0 R -/ID [<67FDFAA0CD9D108A567B8B97804AD5DB> <67FDFAA0CD9D108A567B8B97804AD5DB>] ->> -startxref -208484 -%%EOF Deleted: trunk/docs/tutorial/tutorial.html =================================================================== --- trunk/docs/tutorial/tutorial.html 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/tutorial/tutorial.html 2011-05-17 15:30:41 UTC (rev 4483) @@ -1,1594 +0,0 @@ - - - - - -A Swift Tutorial - - - - - -
    -
    -

    1. Abstract

    -
    -

    This is an introductory tutorial on the use of Swift and its programming -language SwiftScript.

    -
    -
    -
    -

    2. Introduction

    -
    -

    This tutorial is intended to introduce new users to the basics of Swift. -It is structured as a series of small exercise/examples which you can -try for yourself as you read along. After the first hello world -example, there are two tracks - the language track (which introduces -features of the SwiftScript language) and the runtime track (which -introduces features of the Swift runtime environment, such as running -jobs on different sites).

    -

    For information on getting an installation of Swift running, consult the -Swift Quickstart Guide http://www.ci.uchicago.edu/swift/guides/quickstartguide.php, and -return to this document when you have successfully run the test -SwiftScript program mentioned there.

    -

    There is also a Swift User’s Guide -http://www.ci.uchicago.edu/swift/guides/userguide.php which contains -more detailed reference material on topics covered in this manual. All -of the programs included in this tutorial can be found in your Swift -distribution in the examples/swift directory.

    -
    -
    -
    -

    3. Hello World

    -
    -

    The first example program, first.swift, outputs a hello world message -into a file called hello.txt.

    -
    -
    -
    first.swift
    -
    -
    -
    type messagefile;
    -
    -app (messagefile t) greeting() {
    -    echo "Hello, world!" stdout=@filename(t);
    -}
    -
    -messagefile outfile <"hello.txt">;
    -
    -outfile = greeting();
    -
    -

    We can run this program as follows:

    -
    -
    -
    $ cd examples/swift/
    -$ swift first.swift
    -Swift svn swift-r3334 (swift modified locally) cog-r2752
    -
    -RunID: 20100526-1925-8zjupq1b
    -Progress:
    -Final status:  Finished successfully:1
    -$ cat hello.txt
    -Hello, world!
    -

    The basic structure of this program is a type definition, an -application procedure definition, a variable definition and then a -call to the procedure:

    -
    -
    -
    type messagefile;
    -

    First we define a new type, called messagefile. In this example, we will -use this messagefile type as the type for our output message.

    -

    All data in SwiftScript must be typed, whether it is stored in memory or -on disk. This example defines a very simple type. Later on we will see -more complex type examples.

    -
    -
    -
    app (messagefile t) greeting() {
    -    echo "Hello, world!" stdout=@filename(t);
    -}
    -

    Next we define a procedure called greeting. This procedure will write -out the "hello world" message to a file.

    -

    To achieve this, it executes the unix utility echo with a parameter -"Hello, world!" and directs the standard output into the output file.

    -

    The actual file to use is specified by the return parameter, t.

    -

    messagefile outfile <"hello.txt">;

    -

    Here we define a variable called outfile. The type of this variable is -messagefile, and we specify that the contents of this variable will be -stored on disk in a file called hello.txt

    -

    outfile = greeting();

    -

    Now we call the greeting procedure, with its output going to the outfile -variable and therefore to hello.txt on disk.

    -

    Over the following exercises, we’ll extend this simple hello world -program to demonstrate various features of Swift.

    -
    -
    -
    -

    4. Language features

    -
    -
    -

    4.1. Parameters

    -

    Procedures can have parameters. Input parameters specify inputs to the -procedure and output parameters specify outputs. Our helloworld greeting -procedure already uses an output parameter, t, which indicates where the -greeting output will go. In this section, we will add an input parameter -to the greeting function.

    -

    The code changes from first.swift are highlighted below.

    -
    -
    -
    type messagefile;
    -
    -app (messagefile t) greeting (string s) {
    -    echo s stdout=@filename(t);
    -}
    -
    -messagefile outfile <"hello2.txt">;
    -
    -outfile = greeting("hello world");
    -

    We have modified the signature of the greeting procedure to indicate -that it takes a single parameter, s, of type string.

    -

    We have modified the invocation of the echo utility so that it takes -the value of s as a parameter, instead of the string literal "Hello, -world!".

    -

    We have modified the output file definition to point to a different file -on disk.

    -

    We have modified the invocation of greeting so that a greeting string is -supplied.

    -

    The code for this section can be found in parameter.swift. It can be -invoked using the swift command, with output appearing in hello2.txt:

    -
    -
    -
    $ swift parameter.swift
    -

    Now that we can choose our greeting text, we can call the same procedure -with different parameters to generate several output files with -different greetings. The code is in manyparam.swift and can be run as -before using the swift command.

    -
    -
    -
    type messagefile;
    -
    -app (messagefile t) greeting (string s) {
    -    echo s stdout=@filename(t);
    -}
    -
    -messagefile english <"english.txt">;
    -messagefile french <"francais.txt">;
    -english = greeting("hello");
    -french = greeting("bonjour");
    -
    -messagefile japanese <"nihongo.txt">;
    -japanese = greeting("konnichiwa");
    -

    Note that we can intermingle definitions of variables with invocations -of procedures.

    -

    When this program has been run, there should be three new files in the -working directory (english.txt, francais.txt and nihongo.txt) each -containing a greeting in a different language.

    -

    In addition to specifying parameters positionally, parameters can be -named, and if desired a default value can be specified - see Named and Optional Parameters.

    -
    -
    -

    4.2. Adding another application

    -

    Now we’ll define a new application procedure. The procedure we define -will capitalise all the words in the input file.

    -

    To do this, we’ll use the unix tr (translate) utility. Here is an -example of using tr on the unix command line, not using Swift:

    -
    -
    -
    $ echo hello | tr '[a-z]' '[A-Z]'
    -HELLO
    -
    There are several steps
      -
    • -

      -transformation catalog -

      -
    • -
    • -

      -application block -

      -
    • -
    -

    First we need to modify the transformation catalog to define a logical -transformation for the tc utility. The transformation catalog can be -found in etc/tc.data. There are already several entries specifying -where programs can be found. Add a new line to the file, specifying -where tr can be found (usually in /usr/bin/tr but it may differ on -your system), like this:

    -
    -
    -
    localhost       tr      /usr/bin/tr     INSTALLED       INTEL32::LINUX  null
    -

    For now, ignore all of the fields except the second and the third. The -second field tr specifies a logical application name and the third -specifies the location of the application executable.

    -

    Now that we have defined where to find tr, we can use it in SwiftScript.

    -

    We can define a new procedure, capitalise, which calls tr.

    -
    -
    -
    (messagefile o) capitalise(messagefile i) {
    -    app {
    -        tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    -    }
    -}
    -

    We can call capitalise like this:

    -
    -
    -
    messagefile final <"capitals.txt">;
    -final = capitalise(hellofile);
    -

    So a full program based on the first exercise might look like this:

    -
    -
    -
    type messagefile;
    -
    -app (messagefile t) greeting (string s) {
    -    echo s stdout=@filename(t);
    -}
    -
    -app (messagefile o) capitalise(messagefile i) {
    -    tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o);
    -}
    -
    -messagefile hellofile <"hello.txt">;
    -messagefile final <"capitals.txt">;
    -
    -hellofile = greeting("hello from Swift");
    -final = capitalise(hellofile);
    -

    We can use the swift command to run it like this.

    -
    -
    -
    $ swift second_procedure.swift
    -...
    -$ cat capitals.txt
    -HELLO FROM SWIFT
    -
    -
    -

    4.3. Anonymous files

    -

    In the previous section, the file greeting.txt is used only to store -an intermediate result. We don’t really care about which name is used -for the file, and we can let Swift choose the name.

    -

    To do that, omit the mapping entirely when declaring outfile:

    -
    -
    -
    messagefile outfile;
    -

    Swift will choose a filename, which in the present version will be in a -subdirectory called _concurrent.

    -
    -
    -

    4.4. Datatypes

    -

    All data in variables and files has a data type. So far, we’ve seen two -types:

    -
      -
    • -

      -string - this is a built-in type for storing strings of text in - memory, much like in other programming languages -

      -
    • -
    • -

      -messagefile - this is a user-defined type used to mark files as - containing messages -

      -
    • -
    -

    SwiftScript has the additional built-in types: boolean, integer and -float that function much like their counterparts in other programming -languages.

    -

    It is also possible to create user defined types with more structure, -for example:

    -
    -
    -
    type details {
    -    string name;
    -    int pies;
    -}
    -

    Each element of the structured type can be accessed using a . like this:

    -
    -
    -
    person.name = "john";
    -

    The following complete program, types.swift, outputs a greeting using a -user-defined structure type to hold parameters for the message:

    -
    -
    -
    type messagefile;
    -
    -type details {
    -    string name;
    -    int pies;
    -}
    -
    -app (messagefile t) greeting (details d) {
    -    echo "Hello. Your name is" d.name "and you have eaten" d.pies "pies." stdout=@filename(t);
    -}
    -
    -details person;
    -
    -person.name = "John";
    -person.pies = 3;
    -
    -messagefile outfile <"q15.txt">;
    -
    -outfile = greeting(person);
    -

    Structured types can be comprised of marker types for files. See the -later section on mappers for more information about this.

    -
    -
    -

    4.5. Arrays

    -

    We can define arrays using the [] suffix in a variable declaration:

    -
    -
    -
    messagefile m[];
    -

    This program, q5.swift, will declare an array of message files.

    -
    -
    -
    type messagefile;
    -
    -app (messagefile t) greeting (string s[]) {
    -     echo s[0] s[1] s[2] stdout=@filename(t);
    -}
    -
    -messagefile outfile <"q5out.txt">;
    -
    -string words[] = ["how","are","you"];
    -
    -outfile = greeting(words);
    -

    Observe that the type of the parameter to greeting is now an array of -strings, string s[], instead of a single string, string s, that -elements of the array can be referenced numerically, for example s[0], -and that the array is initialised using an array literal, -["how","are","you"].

    -
    -
    -

    4.6. Mappers

    -

    A significant difference between SwiftScript and other languages is that -data can be referred to on disk through variables in a very similar -fashion to data in memory. For example, in the above examples we have -seen a variable definition like this:

    -
    -
    -
    messagefile outfile <"q13greeting.txt">;
    -

    This means that outfile is a dataset variable, which is mapped to a -file on disk called g13greeting.txt. This variable can be assigned to -using = in a similar fashion to an in-memory variable. We can say that -outfile is mapped onto the disk file q13greeting.txt by a mapper.

    -

    There are various ways of mapping in SwiftScript. Two forms have already -been seen in this tutorial. Later exercises will introduce more forms.

    -

    The two forms of mapping seen so far are:

    -

    simple named mapping - the name of the file that a variable is mapped to -is explictly listed. Like this:

    -
    -
    -
    messagefile outfile <"greeting.txt">;
    -

    This is useful when you want to explicitly name input and output files -for your program. For example, outfile in exercise HELLOWORLD.

    -

    anonymous mapping - no name is specified in the source code. A name is -automatically generated for the file. This is useful for intermediate -files that are only referenced through SwiftScript, such as outfile in -exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by -ommitting any mapper definition, like this:

    -
    -
    -
    messagefile outfile;
    -

    Later exercises will introduce other ways of mapping from disk files to -SwiftScript variables.

    -

    TODO: introduce @v syntax.

    -
    -

    4.6.1. The Regexp Mapper

    -

    In this exercise, we introduce the regexp mapper. This mapper -transforms a string expression using a regular expression, and uses the -result of that transformation as the filename to map.

    -

    regexp.swift demonstrates the use of this by placing output into a -file that is based on the name of the input file: our input file is -mapped to the inputfile variable using the simple named mapper, and then -we use the regular expression mapper to map the output file. Then we use -the countwords() procedure to count the works in the input file and -store the result in the output file. In order for the countwords() -procedure to work correctly, add the wc utility (usually found in -/usr/bin/wc) to tc.data.

    -

    The important bit of regexp.swift is:

    -
    -
    -
    messagefile inputfile <"q16.txt">;
    -
    -countfile c <regexp_mapper;
    -             source=@inputfile,
    -             match="(.*)txt",
    -             transform="\\1count"
    -            >;
    -
    -
    -

    4.6.2. fixed_array_mapper

    -

    The fixed array mapper maps a list of files into an array - each -element of the array is mapped into one file in the specified directory. -See fixedarray.swift.

    -
    -
    -
    type messagefile {}
    -type countfile {}
    -
    -(countfile t) countwords (messagefile f) {
    -    app {
    -        wc "-w" @filename(f) stdout=@filename(t);
    -    }
    -}
    -
    -string inputNames = "one.txt two.txt three.txt";
    -string outputNames = "one.count two.count three.count";
    -
    -messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    -countfile outputfiles[] <fixed_array_mapper;files=outputNames>;
    -
    -outputfiles[0] = countwords(inputfiles[0]);
    -outputfiles[1] = countwords(inputfiles[1]);
    -outputfiles[2] = countwords(inputfiles[2]);
    -
    -
    -
    -

    4.7. foreach

    -

    SwiftScript provides a control structure, foreach, to operate on each -element of an array.

    -

    In this example, we will run the previous word counting example over -each file in an array without having to explicitly list the array -elements. The source code for this example is in foreach.swift. The -three input files: one.txt, two.txt and three.txt are supplied. -After you have run the workflow, you should see that there are three -output files: one.count, two.count and three.count, each -containing the word count for the corresponding input file. We combine -the use of the fixed_array_mapper and the regexp_mapper.

    -
    -
    -
    type messagefile {}
    -type countfile {}
    -
    -(countfile t) countwords (messagefile f) {
    -    app {
    -        wc "-w" @filename(f) stdout=@filename(t);
    -    }
    -}
    -
    -string inputNames = "one.txt two.txt three.txt";
    -
    -messagefile inputfiles[] <fixed_array_mapper;files=inputNames>;
    -
    -
    -foreach f in inputfiles {
    -  countfile c<regexp_mapper;
    -            source=@f,
    -            match="(.*)txt",
    -            transform="\\1count">;
    -  c = countwords(f);
    -}
    -
    -
    -

    4.8. If

    -

    Decisions can be made using if, like this:

    -
    -
    -
    if(morning) {
    -  outfile = greeting("good morning");
    -} else {
    -  outfile = greeting("good afternoon");
    -}
    -

    if.swift contains a simple example of this. Compile and run if.swift -and see that it outputs "good morning". Changing the morning variable -from true to false will cause the program to output "good afternoon".

    -
    -
    -

    4.9. Sequential iteration

    -

    A development version of Swift after 0.2 (revision 1230) introduces a -sequential iteration construct.

    -

    The following example demonstrates a simple application: each step of -the iteration is a string representation of the byte count of the -previous step’s output, with iteration terminating when the byte count -reaches zero.

    -

    Here’s the program:

    -
    -
    -
    type counterfile;
    -
    -app (counterfile t) echo(string m) {
    -    echo m stdout=@filename(t);
    -}
    -
    -app (counterfile t) countstep(counterfile i) {
    -    wcl @filename(i) @filename(t);
    -}
    -
    -counterfile a[]  <simple_mapper;prefix="foldout">;
    -
    -a[0] = echo("793578934574893");
    -
    -iterate v {
    -  a[v+1] = countstep(a[v]);
    - trace("extract int value ",@extractint(a[v+1]));
    -} until (@extractint(a[v+1]) <= 1);
    -

    echo is the standard unix echo.

    -

    wcl is our application code - it counts the number of bytes in the one -file and writes that count out to another, like this:

    -
    -
    -
    $ cat ../wcl
    -#!/bin/bash
    -echo -n $(wc -c < $1) > $2
    -
    -$ echo -n hello > a
    -$ wcl a b
    -$ cat b
    -5
    -

    Install the above wcl script somewhere and add a transformation catalog -entry for it. Then run the example program like this:

    -
    -
    -
    $ swift iterate.swift
    -Swift svn swift-r3334 cog-r2752
    -
    -RunID: 20100526-2259-gtlz8zf4
    -Progress:
    -SwiftScript trace: extract int value , 16.0
    -SwiftScript trace: extract int value , 2.0
    -SwiftScript trace: extract int value , 1.0
    -Final status:  Finished successfully:4
    -
    -$ ls foldout*
    -foldout0000  foldout0001  foldout0002  foldout0003
    -
    -
    -
    -
    -

    5. Runtime features

    -
    -
    -

    5.1. Visualising the workflow as a graph

    -

    When running a workflow, its possible to generate a provenance graph at -the same time:

    -
    -
    -
    $ swift -pgraph graph.dot first.swift
    -$ dot -ograph.png -Tpng graph.dot
    -

    graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org.

    -
    -
    -

    5.2. Running on a remote site

    -

    As configured by default, all jobs are run locally. In the previous -examples, we’ve invoked echo and tr executables from our SwiftScript -program. These have been run on the local system (the same computer on -which you ran swift). We can also make our computations run on a -remote resource.

    -
    - - - -
    -Warning -This example is necessarily more vague than previous examples, -because its requires access to remote resources. You should ensure that -you can submit a job using the globus-job-run (or globusrun-ws?) -command(s).
    -
    -

    We do not need to modify any SwiftScript code to run on another -resource. Instead, we must modify another catalog, the site catalog. -This catalog provides details of the location that applications will be -run, with the default settings referring to the local machine. We will -modify it to refer to a remote resource - the UC Teraport cluster. If -you are not a UC Teraport user, you should use details of a different -resource that you do have access to.

    -

    The site catalog is located in etc/sites.xml and is a relatively -straightforward XML format file. We must modify each of the following -three settings: gridftp (which indicates how and where data can be -transferred to the remote resource), jobmanager (which indicates how -applications can be run on the remote resource) and workdirectory (which -indicates where working storage can be found on the remote resource).

    -
    -
    -

    5.3. Writing a mapper

    -

    This section will introduce writing a custom mapper so that Swift is -able to access data files laid out in application-specific ways.

    -

    An application-specific mapper must take the form of a Java class that -implements the Mapper -http://www.ci.uchicago.edu/swift/javadoc/vdsk/org/griphyn/vdl/mapping/Mapper.html -interface.

    -

    Usually you don’t need to implement this interface directly, because -Swift provides a number of more concrete classes with some functionality -already implemented.

    -

    The hierarchy of helper classes is:

    - -

    This is the abstract interface for mappers in Swift. You must -implement methods to provide access to mapper properties, to map from a -SwiftScript dataset path (such as foo[1].bar) to a file name, to check -whether a file exists. None of the default Swift mappers implement this -interface directly - instead they use one of the following helper classes.

    - -

    This provides helper methods to manage mapper properties and to handle -existance checking. Examples of mappers which use this class are: -Array Mapper, -CSV Mapper, -Fixed Array Mapper, -Regexp Mapper, -and Single File Mapper.

    -

    AbstractFileMapper -This provides a helper class for mappers which select files based on -selecting files from a directory listing. It is necessary to write some -helper methods that are different from the above mapper methods. -Examples of mappers which use this class are: -simple_mapper, -filesys_mapper, -and the (undocumented) StructuredRegularExpressionMapper.

    -

    In general, to write a mapper, choose either the AbstractMapper or the -AbstractFileMapper and extend those. If your mapper will generally -select the files it returns based on a directory listing and will -convert paths to filenames using some regular conversion (for example, -in the way that simple_mapper maps files in a directory that match a -particular pattern), then you should probably use the -AbstractFileMapper. If your mapper will produce a list of files in some -other way (for example, in the way that csv_mapper maps based on -filenames given in a CSV file rather than looking at which files are in -a directory), then you should probably use the AbstractMapper.

    -
    -
    -

    5.4. Writing a very basic mapper

    -

    In this section, we will write a very basic (almost useless) mapper that -will map a SwiftScript dataset into a hardcoded file called -myfile.txt, like this:

    -
    -
    -
    Swift variable                            Filename
    -
    -
    -
    -
    var   <----------------------------->    myfile.txt
    -
    -

    We should be able to use the mapper we write in a SwiftScript program -like this:

    -
    -
    -
    type file;
    -file f <my_first_mapper;>;
    -

    First we must choose a base class - AbstractMapper or -AbstractFileMapper. We aren’t going to use a directory listing to decide -on our mapping - we are getting the mapping from some other source (in -fact, it will be hard coded). So we will use AbstractMapper.

    -

    So now onto the source code. We must define a subclass of AbstractMapper -and implement several mapper methods: isStatic, existing, and map. These -methods are documented in the javadoc for the Mapper interface.

    -

    Here is the code implementing this mapper. Put this in your source -vdsk directory, make a directory src/tutorial/|and put this file in -src/tutorial/MyFirstMapper.java.

    -
    -
    -
    package tutorial;
    -
    -import java.util.Arrays;
    -import java.util.Collection;
    -import java.util.Collections;
    -
    -import org.griphyn.vdl.mapping.AbsFile;
    -import org.griphyn.vdl.mapping.AbstractMapper;
    -import org.griphyn.vdl.mapping.Path;
    -import org.griphyn.vdl.mapping.PhysicalFormat;
    -
    -public class MyFirstMapper extends AbstractMapper {
    -
    -  AbsFile myfile = new AbsFile("myfile.txt");
    -
    -  public boolean isStatic() {
    -    return false;
    -  }
    -
    -  public Collection existing() {
    -    if (myfile.exists())
    -      return Arrays.asList(new Path[] {Path.EMPTY_PATH});
    -    else
    -      return Collections.EMPTY_LIST;
    -  }
    -
    -  public PhysicalFormat map(Path p) {
    -    if(p.equals(Path.EMPTY_PATH))
    -      return myfile;
    -    else
    -      return null;
    -  }
    -}
    -

    Now we need to inform the Swift engine about the existence of this -mapper. We do that by editing the MapperFactory class definition, in -src/org/griphyn/vdl/mapping/MapperFactory.java and adding a -registerMapper call alongside the existing registerMapper calls, like this:

    -
    -
    -
    registerMapper("my_first_mapper", tutorial.MyFirstMapper.class);
    -

    The first parameter is the name of the mapper that will be used in -SwiftScript program. The second parameter is the new Mapper class that -we just wrote.

    -

    Now rebuild Swift using the "ant redist" target.

    -

    This new Swift build will be aware of your new mapper. We can test it -out with a hello world program:

    -
    -
    -
    type messagefile;
    -
    -(messagefile t) greeting() {
    -    app {
    -        echo "hello" stdout=@filename(t);
    -    }
    -}
    -
    -messagefile outfile <my_first_mapper;>;
    -
    -outfile = greeting();
    -

    Run this program, and hopefully you will find the "hello" string has -been output into the hard coded output file myfile.txt:

    -
    -
    -
    $ cat myfile.txt
    -hello
    -

    So that’s a first very simple mapper implemented. Compare the source -code to the single_file_mapper in -SingleFileMapper.java. -There is not much more code to the single_file_mapper - mostly code to -deal with the file parameter.

    -
    -
    -

    5.5. Starting and restarting

    -

    Now we’re going to try out the restart capabilities of Swift. We will -make a workflow that will deliberately fail, and then we will fix the -problem so that Swift can continue with the workflow.

    -

    First we have the program in working form, restart.swift.

    -
    -
    -
    type file;
    -
    -app (file f) touch() {
    -    touch @f;
    -}
    -
    -app (file f) processL(file inp) {
    -    echo "processL" stdout=@f;
    -}
    -
    -app (file f) processR(file inp) {
    -    broken "process" stdout=@f;
    -}
    -
    -app (file f) join(file left, file right) {
    -    echo "join" @left @right stdout=@f;
    -}
    -
    -file f = touch();
    -
    -file g = processL(f);
    -file h = processR(f);
    -
    -file i = join(g,h);
    -

    We must define some transformation catalog entries:

    -
    -
    -
    localhost   touch   /usr/bin/touch  INSTALLED   INTEL32::LINUX  null
    -localhost   broken  /bin/true   INSTALLED   INTEL32::LINUX  null
    -

    Now we can run the program:

    -
    -
    -
    $ swift restart.swift
    -Swift 0.9 swift-r2860 cog-r2388
    -
    -RunID: 20100526-1119-3kgzzi15
    -Progress:
    -Final status:  Finished successfully:4
    -

    Four jobs run - touch, echo, broken and a final echo. (note that broken -isn’t actually broken yet).

    -

    Now we will break the broken job and see what happens. Replace the -definition in tc.data for broken with this:

    -
    -
    -
    localhost    broken     /bin/false   INSTALLED       INTEL32::LINUX  null
    -

    Now when we run the workflow, the broken task fails:

    -
    -
    -
    $ swift restart.swift
    -
    -Swift 0.9 swift-r2860 cog-r2388
    -
    -RunID: 20100526-1121-tssdcljg
    -Progress:
    -Progress:  Stage in:1  Finished successfully:2
    -Execution failed:
    -    Exception in broken:
    -Arguments: [process]
    -Host: localhost
    -Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj
    -stderr.txt:
    -stdout.txt:
    -

    From the output we can see that touch and the first echo completed, but -then broken failed and so swift did not attempt to execute the final echo.

    -

    There will be a restart log with the same name as the RunID:

    -
    -
    -
    $ ls *20100526-1121-tssdcljg*rlog
    -restart-20100526-1121-tssdcljg.0.rlog
    -

    This restart log contains enough information for swift to know which -parts of the workflow were executed successfully.

    -

    We can try to rerun it immediately, like this:

    -
    -
    -
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    -
    -Swift 0.9 swift-r2860 cog-r2388
    -
    -RunID: 20100526-1125-7yx0zi6d
    -Progress:
    -Execution failed:
    -    Exception in broken:
    -Arguments: [process]
    -Host: localhost
    -Directory: restart-20100526-1125-7yx0zi6d/jobs/m/broken-msn1gisj
    -stderr.txt:
    -stdout.txt:
    -
    -----
    -
    -Caused by:
    -    Exit code 1
    -

    Swift tried to resume the workflow by executing "broken" again. It did -not try to run the touch or first echo jobs, because the restart log -says that they do not need to be executed again.

    -

    Broken failed again, leaving the original restart log in place.

    -

    Now we will fix the problem with "broken" by restoring the original -tc.data line that works.

    -

    Remove the existing "broken" line and replace it with the successful -tc.data entry above:

    -
    -
    -
    localhost       broken          /bin/true   INSTALLED       INTEL32::LINUX  null
    -

    Now run again:

    -
    -
    -
    $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift
    -
    -Swift 0.9 swift-r2860 cog-r2388
    -
    -RunID: 20100526-1128-a2gfuxhg
    -Progress:
    -Final status:  Initializing:2  Finished successfully:2
    -

    Swift tries to run "broken" again. This time it works, and so Swift -continues on to execute the final piece of the workflow as if nothing -had ever gone wrong.

    -
    -
    -
    -
    -

    6. bits

    -
    -
    -

    6.1. Named and optional parameters

    -

    anchor:named_parameters -In addition to specifying parameters positionally, parameters can be -named, and if desired a default value can be specified:

    -
    -
    -
    (messagefile t) greeting (string s="hello") {
    -    app {
    -        echo s stdout=@filename(t);
    -    }
    -}
    -

    When we invoke the procedure, we can specify values for the parameters -by name. The following code can be found in q21.swift.

    -
    -
    -
    french = greeting(s="bonjour");
    -

    or we can let the default value apply:

    -
    -
    -
    english = greeting();
    -
    -
    -
    -
    -

    - - - Modified: trunk/docs/tutorial/tutorial.pdf =================================================================== --- trunk/docs/tutorial/tutorial.pdf 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/tutorial/tutorial.pdf 2011-05-17 15:30:41 UTC (rev 4483) @@ -2477,19 +2477,28 @@ /Length1 761 /Length2 1025 /Length3 532 -/Length 1573 +/Length 1576 /Filter /FlateDecode >> stream -x??RiTW?S -uA???(??l A??DS?" ???????aB?A???j=??? -?????D????w j?n(????S?????y???????????.A?PJ??;???`?\?????1X?`"F?S -?_$????@?x?b??X??`?`B?FbI?p -f????DIL??@?P?PCs(5? ??8@?V????S ? -Q??(?????? n?&?$???4???+?B2?\?d?-%pu@????I?? ??????\?S?g"?^?>??VG4?:?-??hu$??@!???F?7???t??U??1?ORC??????r?-?8?~?$[??8=Z6???????1j?i%LkX?W????i???|??????[??*?????????6O^????u&??Cap?r?9 ??'? ???>??i{n??9I??.% ?~?.0???T at KzM???.,s??}??Y??'???l?,?s??????????=??H}f?`?4x?????Kn?{Ou?Xc?`??J???D4[?F9?;???h?$?5$o0j?olK?K!??W.?*hz?{??q????6?q??W?Qm??EN2??<Z??v??b?????9hd???Uyih?jM?#???2Q?C????uO%??(7??.??????GY??W?????n/v??~!PEn??????? k???~????k???8????????nia? ??%?g=?\?(+f?i?'??1?'?O(?!)B??*????L?endstream +x??R{XSe?'?"?K~DS&? ???@??(?MH?;?????u8??)??C1$n?r)?T?@??iya????? &???? ???z:????????????X?Q???X?Ny?9|1??e|??<?? +%!Ba????E"?T?/?? ??B_ ??LKM??{({ ? $Hb +r?J??C??A4?? ?????H+`:$3 ?a???XS1???$????H?:??R$?iQ?}\&?"QWg*?H??i-?????R?Z?h????z??h0u?c???(H9?B? ?????t??U??1?OUC??????'?X??C4 +?i@????x??d%??:??y?4???j??Q?S1?Zx??c?_1m???*????@?s?m?m??????Yh???z(?>%??_???/.(Dc????C ??X?O?R3vF=?L?? A-m8??~:b??,[-?OJ??+p???? +????=w?j?????"bj???m???Xg??tr??Q[t??ULd??????- ????m?}?? +/?8(c ?T?p???/;?^h5?????F??!??????(??]??J?_1p??Q]?????O????\)?*? ?Y?Q?8???k?????pA??Y}?,????-??-??7? n{m?l_????q??'?)?ry?k+kK?K-??? +????????A???b????S\?J?> endobj 290 0 obj << /Ascent 694 /CapHeight 683 /Descent -194 -/FontName /RZVZYK+CMMI10 +/FontName /NAMLFL+CMMI10 /ItalicAngle -14.04 /StemV 72 /XHeight 431 @@ -2525,22 +2534,21 @@ /Length1 753 /Length2 637 /Length3 532 -/Length 1177 +/Length 1176 /Filter /FlateDecode >> stream -x??RmPTU.? ??? z?!????,?? -a??R??s???ra?^???]??Dt?L???/????PlG??0"? ~,H?R j u'?Y????s????@?T???~???+]C?,wb?%??y?~??h?^??e?~?8?3?????y7?F??'sb???joG??V??? ????em??)z???yI-????b?q???????{??????_??U^8??nt??ZS?T"??+x?|??;?L?????Q??.????'1???????{GSJF??[???;"O?h?sZ?qN|???E?,2^????j?????|??,nQ^s??Sw??2???Y~??KyI????+o???????K?.??1Y????>?,z?g???5t?]???m? ??!???j}??M?I???[??-??2? -?i?oIV}p?&?????K/????CXh/-???G??m?$v??L??????\6g8?+"?v??\ ?p?hS??? +s]?~?.??w?`?pr*;?1????[?u????!?\?Vwz'????q?%?????CM??O?{?z??ak???5XJy?Q?-c??k???cy???v??2???_F6_? *???&?kY?8\?p?xSR???w??OWowH?`??9?UgG?7"?H,xn?????C????m^X??????6??+?u?e}?????#?_J? +?+?[?Y?v????],?JY??w???,|????ys??)???@?? ?U?i, at u???lK?????m ??Z?[?|??|??c?????????X???\???0v?X~???)????????n??????s??Djeg2?O??<$?"?????@?x&p5???`L +?7???endstream endobj 289 0 obj << /Type /Font @@ -2549,14 +2557,14 @@ /FirstChar 32 /LastChar 32 /Widths 639 0 R -/BaseFont /CAGRTG+CMSY10 +/BaseFont /XXBLOH+CMSY10 /FontDescriptor 287 0 R >> endobj 287 0 obj << /Ascent 750 /CapHeight 683 /Descent -194 -/FontName /CAGRTG+CMSY10 +/FontName /XXBLOH+CMSY10 /ItalicAngle -14.035 /StemV 85 /XHeight 431 @@ -2590,7 +2598,7 @@ ??D?&VV @????dn? ?VS??????/??!c?????? dn ???? ?????:???????-?3?5 ???%%/???WHm??F?Eck? @d?u?????^L?lMA?????K? `p????n????q????6 '??????????o?? [k????????????????`?vN?N&? {g?????????la??On'?_7???o??????%???????d?p?;???09?[y??????/.N [??b@p?9?Z????????;?U'????????_?????8?????f?,?s?8??m?E`?gP?l??,???????O?+??_ ??gfh??02????????????P??????'????-?????O????;????B??X[????_0??7?@??cm??? -7?Y{?6?g???$??p????6C???? ????6???A?@SE???????o??eW?5:Z?l??W3 ,????S??X???z??????I??H??????('?L??w????j???a????(E???-???sx1?=? ?l??? ??????? ????rF?? w?????Y?U????k??0b?&v????????????_??&.??U????[??\?k??@w? ???? O?ezV?s=N?????`? ?H?}Y?jq??]?_z?.W??{]c?4?G??????Ci???~lk??T?u??@!?e'?Q ?~R??F??????6???????~?;???.6G??g2?BL?'{d_???8?n?f0???? ????'????#?}w??t?q??5z???)???#md_? ?m;e???3:x??%??5?o???x??????>7\(??px[???g???f?`?F~A?R:?{????? ?-??(u?5???R03?F?T#???;Qx???X??s?m?R??5???????.dM????p?[????Z8????DL????j?OH??\(yt?^G??'T??=?Di? ???25??u??.?>'???t?tX,????r%} '?'C?6^????5z???)???#md_? ?m;e???3:x??%??5?o???x??????>7\(??px[???g???f?`?F~A?R:?{????? ?-??(u?5???R03?F?T#???;Qx???X??s?m?R??5???????.dM????p?[????Z8????DL????j?OH??\(yt?^G??'T??=?Di? ???25??u??.?>'???t?tX,????r%} '?'C?6^??????q??Fm???:??h?]?|n?????????v8e?V??/e???????5? ,I???x??"?^&O??8*???vj?4????Pv?[????? e)??t?f?T ??5^??6?3i0?????'??e?X???+?6^{2? ? ??_??6?k?y??????*=u??<8??m'?X]r$?#z?????????%??????}w?E?1B?m???Z.5|???c??????lY;???s~?j_??x??2?U0\:??4O????L??i?w?3HV?8c??&'Oc?Cw~?>???6??a?|-??????????G?`2?? ?dJ???*?D?i ???????p?2XA????{3?Z?W????d???',r????]?'fB????*?p}H?\l?????+j??f??$(?@?????????U?????k?JG??X=? ?5K^Jm? @@ -2704,7 +2712,7 @@ ?"???????^?s???,?0G???^2???? ?[?3a-??>?Mz:?E????~??I0?n1?:r)?cd?o9??<??L?O+???`?U????e R( ??????`????\'?J?/??????p???????%]-!?V?Nu?;??t k??!??+?????`?#?W#?v????xU?T\?????[:????1??SP?}?">R????";d??JhB??'??y/^?Z?N?>????Fx?B???8z??H?]gm??88?t ??S?f???!? ]??i%?P?H???L?G???m??H"?-9?????ZM??g?\????h????S?????+?u??k?C10^X?iM-I[W??e????$?1?P???!??xs]?-?O?$???????+?O%??*?OLt.????'d -? }?E?????endstream +? }?E?????~endstream endobj 158 0 obj << /Type /Font @@ -2713,14 +2721,14 @@ /FirstChar 33 /LastChar 125 /Widths 641 0 R -/BaseFont /TUPMAR+NimbusMonL-Regu +/BaseFont /WEBKWJ+NimbusMonL-Regu /FontDescriptor 156 0 R >> endobj 156 0 obj << /Ascent 625 /CapHeight 557 /Descent -147 -/FontName /TUPMAR+NimbusMonL-Regu +/FontName /WEBKWJ+NimbusMonL-Regu /ItalicAngle 0 /StemV 41 /XHeight 426 @@ -2740,56 +2748,64 @@ /Filter /FlateDecode >> stream -x??teTl?6??? ????t#? 0? LHw?4??tJ -HH+-?????A????Y??????????Z3k?}?}???k???AG?G?b T???<???-??-?q??Hh???pW?=&??????A?? -( 0??vAA????6 @?? -9:???zF\\????v?z?????????/??w7 ~O???p' ?? -(h???j=???2<????&t?? ;???9(??????n -?{?%?`?@;?}???????n ???8Bm???;?C ??+??w?v??????{?{??L???? w8?>????_u??l??s?@?0?p?i?C?n?vOs??m@`????e ??`??6?????????e ` ???*?@??6P{W vOs???v??'??to?????'????5??0??/???}N;?}nG?????? ?????`/?????{f8??????]??@l>-?>%???2??O??????-??????F???o???????Z6n?????/0?~?4???? -?{?????P7????wo#?_U?'????R??????? ?)????: ?????????? -??@?+ ???????? -3p????!?????{??t?g??f?????l???:?S7?v?3??&?????T??/?/????GP???1??G Aa??K??D?:k??? /??/???????,?F??????#}? -??~??i? -?!??{??l????q???@/???4?N*?93; ^?8????Yw?z_?{i?????HG`f??D??]m8o??????S{??6?87:?]?:??G4?L]?DK??b\?!|??xY?Fq??_5V?????\???gYr??v?U?y|????0??????.?>???????ho?5e????g??????k??+7?E???E?S?U??9??fa???3f?C{????N??>?1d?'`_?6o????,?????????q?????k/Ca???K???N?7??e?M??[&?a }Ql?Z??"????)?4?G?8?;?Z$V??-?|? .??????-?7??l:?zp??????Z??B???c?_?#?2o{?lsb?d+?????k?OX ???Y?V=7??????i^????????V?I??pu?=0?UK??O???? ?E%?f#?j?r?~N{??S??3M???.Z^??:oY?){?:B{Bx?????N?J? -?????&-?/?$hX?A<z=~t8V??e\?F???SN?]bd???>-???Q7??F???9_Z??*??i???Y??????;???jG??p?????W??_$O??e[~Z?????6???????f9?@z???? -/?????????[??~n2??=B1?`????E?K???xk"\cT?DNM?~ -?????D?????ed? ????h????w?$pm:??R???Yg.??~"Jq?@*??,????~?x??FxfMS=F??1?o|W???????M?Q?:3{???2????Y?????????-??bZ?K???TL???C'Xs?o*?/?/e??k?=Z???} ????(??E?}I -?? <?FiG>C?>???U???.{?mF??$5%2???j?B?1?g??m[?e?F"I-ED?17??&(?_&@?S3???]-?r?z7m???M?\?):?o??c?HmR???? ?ha]?5??/\?????>T?k`+?;???b????K??Q?C????c>??????+?&???j???v???{f??J???0% Y???d??? -?gKJOv?HJ)?????}n?????^?k4?T??????D1?Q"?!q????W?K???G?zk???o?-m????svM?P?Q?V??m?5????v??O? ,??D??O????????:??U??3#????p>?(?=^O??????6?u?uc.???@?r?e?gH?I!w?R??~j?JY3`?a??h???&j?????????? ?`????d?Tz?????? ??b?gt[W??K?{0?Y?S??O?K`?t?+}?%?????#,??d!?(?a&???????jW? ?}nmj&??y?8[??1D2??? l?`h??:J?`???????f?????;?~?$??j??.?T[M?F??mDi???rX????@?\?`?=??8P??{? ??\?XU?????? ??7???q?4@?@0 ???@.???wk0?{.9?s???????@??7? +u?`?? ?j +????m]v? ???C????{??c?d?f ???Y?????h +?????{O;?-?wK?{?{n +?p?'?w. ?ss????}O??)??U7 +t????a?{?{?????>??{k77?????^???]?y??s???s;???|??El??e?C??{ ??? ??3?q_??????c?iA??)??3?y?}"?$???o??'??5?/?????N??pq??v???? ?~?X??????l\???? d??Z??\?????{????9???B?p?????_fL? ???m??.????n?B]@`?????>???o??#???[ +?? ???=????>C5 +%??f??q??? +?????? 5!v??{?R????|??????07?r-????????/7 '?2c????v?Q?6?[???G}?[?8QHV*R????????????B????[-?a_?>BW???.????P?g#Q??E????????Q?\???]Q?????{9D?8Vk?aE?!?m?5?%????on??:=??;???aU???)Z@??U????i???g??(?t?W???~???L??>N???Tj?Qb??NW??W-?%??RUk?p????I?r??^??'??!?? ????|??\?????????Y?e? ++"?G_??????g'????r:?N???????z??,??z5z???*;???}???]upO?E???f??[?\????^?C??????6v?q? ? b??\???????F?zA????g?KuX????X0+????_?|????N?R??}W6?zj???q??l?/+^??????7y???_?,??I?p>????%?PR?C?y??Qu~??MFt? K( f?u?t?pd???oU?kT???h??Q ???g???~????/???$p?????????NEpQ +PT6i????G*n??+Be??1????R!???)???????u +???????z?h5?Y?g??A???68u8kv?????5T?E?kAt? 9q??? U??!?8k6?m???????:M?G???;?????X?;)?/??G2?"U(m?g??~|w?!i]??^?D9??R????3????t?|??Y6?Zv?$??RD??c?j??y?d??3?*???U?Zn?????.?{???????p,T?r?}#?$ZP?{E?r????T?t??Jt? l!|???T??~wA8B??n?Id?' #??2"t+{??|B?t?Um.w??N??n?vz???<T??Q{ghE??y#?Uh???k?i=A????s???P&?p??vSB????????#??, +???:???my?,???/?yv?]?????????b?Cu7???6W???>????f??2?=????3l!?c/%??? ????ap?y??r?_w?c?i??v?]??????Nq +4? ,9?JW?e??Ob1?3??)k????>??"?)??'?)?y???????Cm?F??GE??P??P???U??C5?K?y?^?V5????G?-?{"Hx?86S4?U???j????a2?k?T???ca"??2?f?0?{???P [??$??n?n?O7?h?????? o??bL`,??~?Axzo???????0?=o?S???!??,??.T???$??F??8????x???n??jv?8???49??8?????Q???????? ?oi?? a?o?B!???/7?????.)??????t??#:??>R?!={?;]v? ??p+4?JC?!?? ?????R??? '?)?B < +???se'?[?j?T ?&+p???/??????01Pp|???)z`y??~?O(? +?? +????q??? ??j~?!??????{??U??t~X??O ?;?)?J? ?F????k*?_???????I? ??_?eWi'????2??!M???KDu???Z?h?sugy|? ?h??[?!?E??????5_)????jF???????? +???%???.}NI??x??0? ?;?y????}?$??}????6?A +s??9????M??X?$?2gL=+???}???]?f1My???^?*??Pvd????o k'Z,j???TB???? W1???}W,????1??``?????8???G?4R??g;??V????k???rZ?Bw??!???????l???????:?0LI?xk^!?/.q$^??X???????[?????f?S???x?K?~%k?V?:uE???,?N????VI??'?? +Ej???????eXT?Rv?;T??u???????!=??]+bi?x?`???%-?#?Q?? +?;?Q?0'?G????Z???=M?o?w?PdO?R?>??s~|(????t?H??%[J?????{*h?R??D??>?????%:'?<|!w[?4???%?\??7V?J??_e????7}?m??????%*?????????H???r?wL?V?q?????z;???~z ???J??????]K_?\BY -huT?*O -????Ni???4??;D???0??????i/=??a\?^p????`?e????????rJ?F???/?5??(1o?B{?? ? -??Hp!y??o????!gv9y0_w8C?K???G?? ?P?I^???? ?gF\-?V?|??4???x?????G??;?????W??m???L????V????&? ?o??Vl4?????OI+??D>}g\???????????S???m?A ?T?c]?oIt?u??N?:q?X?fn?LF???N`??hq???4?}??`?????2?TD?:?o:^fb?9w??F???vN?/j?o?K???D^??f??1?f?{a??O??????O??&?:??3???QN?l_?:d?_(????,?f?;?X?3???`?Hzl,z???w?~?????T?z?"????E?C??[-??O? T?i?|??$82? w?a?)??i?*!O???S2?lx??`?b?%?IW+?C?lm?M0d>p0?????HBlw?+?~??wh??,u??G#? g????eL??,???#??l????%?.????g_V????????Q???o??_?l??/?98?$???L??m'????y?B????????^no?[????RU????????(???^w??qX?=????{4?y???v?[???g?????U?~?|"?d???E???Rt?????}?]??u.N????o????=???`^?+Vo????X???3?G??o:p???? py_h?~???!*u???%?????????F?????? ??????]??:9d??Y?>?EJ?G{/???O?7??q?6??s? ??Dm[??? -??;??{N)Kr?D??????M?$F??,e???C]i$????/?z??????s????W????A??_O?f????pK? ?~?? ????w?R??T???`?3?????(??]-???tA*?PZ????PM?ll??$?.??S$??M?`?'???4C?F???!zG?????N???]????2"??????? ??#q?:?x?}???*?q7??&???%G&? n????v!-}?Q??????g???w????E?OX?h??0??x>?2??i?0e?u?????Y???'1X?????/???c??P??; ?;K&??]bN?BI?:`C?E????' -?L???H??i????7???????5??=??L1?4??bj??kH?3???#i?4?kUP?yZ?93??????C$MS??E?G?????'????h?C?l?.????Vendstream +?r????qN???E??.????D??{e?????X?????7?q#d'?)+?????#'???BVp?j?G??.;??X%#? )>????ki?? 1??\???eXW?T?kp-p{sKYi?M?zU,??Z???? +?(??}7?????>C8?8??PJ?}??-k??l?m?j??x,?/? ?Y??? ?jd>N?F%M~??????f?F??b?(?I)???4?Yx%???'??e???w? ?k????[.Qz[[???N??m~p W`O?R?:??s~z(^???tnKg?%YH?}???= 4V??U"?Q ??v?Y???]:???_?Yh?p* ???#H%q??2?B???^???0???b=?t?s??S?S??J%T4???? ??K>?u???"????)?L s??z)F?M??????}?Z??TL????? ???VO?Z??? + ??N???????Dn?1"W??f? +??????x???Q???K?h?A IA??o^Or1?}|?L?I}@???+??|{o??&????h??:_??????????R?|gH?s?????-'??s_W???g?t?1r~!/???G?+?]]?.??s??7?????????H\?f?.?????cy7?X??\V??!?\i~H& +??EK?k#?R?Z?e????$???+>? ???u%8?}???}u?? +(??bw?)?P?:??9??(?j???V?HM???`?Ui?I??? -f?]%'W?1?8Z|&?%?8O=?h??M?p?????????bR?F???'?5??(!w?\{???2??pP.!y??O????:!gVy_;wC?sB??'??@??qn??)?? ?{Z\-?5V?|??T?m??8?????G=?3??>?}?~??~?? ?v???????F?t???.?l4??IsOI??zE???`\???????????s???M?~?T?C=]?OqT?U??v?Q?X?FN?tz??.?0N*`??pa???4?]-?1??????dx??w*Nf|?)g??Z???vN?/j?g?C???H^??j??1?f ?sn??G??????/?w?]?? 63?\?Q?go]??g??+???//???9??1?wOa?Hz{l,j????>??????:?B????}???-?O?T?i????$82? 7?!?I??)?J!?/??2Alx>? ?vb?%?qg ?c?LM?u)0x.` ???%?? HBlg??n??gp??,e?,?`?????="?xb??????g?\?7uF??J?~?fK"???n??;v????yx.D3{???-??<??#?????&????Z?R51 X??4)_]:???Mj?q?o??u???{S??Js??D??|??4j???g?W_??;? + +??R? ?r?b.;Kd??m(?????@?L%?|!D? ????l??U?1s?Z??y_??s?7???/???9??C8??(?=A??g9???54?U2"=bT?? ?2?9?????2?kG?y??O??%?$r?Bb????H?G??6Dk?g????p?}?'[??E??'?Jq?3?G?b ??{?????]~?@??`??~?Y?????????3??=???v?YP?Uc??4D|;kG|????@1??Y%,?q>,cEk????p7lq?????l]? ???icL3c???Q????}??<,??c???'???_??)???g???p???*{L??7?B{?Gm +{d?|?e0u??!?Gm[???? +????X??????~?[O??(#X??z??oH?@?nhps??`K?x{?-?=??[t? ??e???{h??Sz$?%:}?b?5AF??[y+??$@,H????TZ??????????/?b{?? ???7/?Xf)S???G!? +??c3]?L??L???C??,????E????g_W?>????]??????????^????m?_? PF????????X??_??n??I?D?-?5??Bb??)?ooU@??O?J??xb????8 +?-??R?_?>??v??1o?/.d? +???BR??Cj?$?+Ju?????e?????N ?+?0????? +L(?s??\??u?z.?????5ZJ#Y??Y??9????O?c?? +_??-w??L?Mw????yN?V)S????/?d??????)???R??u'!O?~x??????]?;? ????Z1??*?>?????h +I?Pz?4??w?WU<\???f^??????1?U?r?1?`Y?W"??>?7niVD??o??????{??,?T??7??q???Y??i?r????5?\?g? Y |*yA?}|???[O?+=????`?d?2???Rd??=!f???????I ???y-! u[????*?????)" %Q?0??bU??/*?4h? ?r_a???h? ??a??k?%??:y??Wo??=?P?K?:a??(??I$?=b???????o?-?r???s X=W?m????????y-??????r??p +Nc?r?*???R?IP>???p?~d?z????V??A2!??????K?????????c?|?=????b??S*)???]??? ?;????'?ed@???g?????#?????&?????,P?>?}???w???68?#?q???5@??- r????Gp????? JY?C&Z??????-?'??td?c????J??n}??U#o'????z?&9?}?O?u????\y]????0? 2???*??jb2'??noq:??o?????i????*??G?W?n????i?Jk??e?8Y?5] ??h>I??????8YM`#??Wfkc??J??????(??S??????(j??$????X?????.???)z?$??????????E,ky?g7??`?&J????w???+?BZEg?S?h?Y/?n????]?X?_~(?1?m??A????rDZ:q???? }7???%??}?/?R?|"?{#(??g???@??o? U????`fy?O?g? ?l????G???XM??.Y?&???'???h??=?vHpF?,%?L??V? ??.|?? ?m7?z??/X????"???????y?4i~?G?B??31??};Y??N?????eZwR +??????yF????g?H7o#n???h??o?3pDN??a???1??&?????tp????V??U??????G??????GM???_?????;u?o?> endobj 147 0 obj << /Ascent 669 /CapHeight 669 /Descent -193 -/FontName /WPJZOO+NimbusRomNo9L-ReguItal +/FontName /WCZJLE+NimbusRomNo9L-ReguItal /ItalicAngle -15.5 /StemV 78 /XHeight 441 @@ -2825,91 +2841,88 @@ /Filter /FlateDecode >> stream -x??weP??-?Npk???????@c?4??? ?,??w????5?wg?N?7??????uUW?????{?s???R]?U?l ?;CX9?8?? 'KwM??*XP??=?x?????J?- ???(?Zd?V..??? --@??????t4???Y?i?+`?????Lw??3????'???t??A?_'j??`r??? -U? ??:y?3?????a????????@F? -? -???? -?l -??5w?7,Iw???hzKz[]?r?\?nN w????;?????6r?r????????7!7?[???? -L?q?r?@oU?e???bg???;?? -??EZ??+7???{#$???_???????7?7???o???????O&?#?l??km? ??o?????Vnno?}???????;z?P??V?????>C?? -???????p)??.. ?w}???4???0!???g???eG?iw??#}W:???4????{????y7??? ???^??????!???????i?3?D???=c0?ga?;?;?@???$?v?(?oEG?t???????.??wH?s??i?=?????]sI? -u*? ???1p???????<%g?`???-??x??A?&1}U?????i??B?9 ????SJ??Aok~sK>?#"?N??dW?Oq o?x?B??p??E????y???3Y??3?? -?#???????%J?g ??Al?.v?.?d?i??3:h??-,??4??]1???????c?/?6H?k?????q?I????7X?A??N?'??IE??@??8_?(/?????G????Z!???'?I,?????J??]?????3??.G??i?|??z-????P?R??#?)? ????_???R9?` o?2w1??4??1???????{??+0??)??d???"??<1? - C&{?_i?,JeR??B??:???x?x?Q:;??0M???????Qz?????O? V?????X?????Z?B??Z?MT -????J?? -?w??`???????Z60?9 -?BG?W?????8!?????$k??5-??v???*zb?H8?????/,??'???fO~???????!hl??W??.>??B?1??S?@??`??2?K7?{n??^?Q??&guF????????T? ???????Pf??S?b?Z?O?sd -??s???,?}MBR(3'm?u5??3?&+$k???4?????}?L ???tVC[MDh????W?????/?q????1 -]????l - ????w!?W??b >?2?????l?????n??y????[#zT??L?????S??Y?? ?????n?C???O?s??207+)a?u"dF :?????pP??\c???x -???{??C?_??:d?V?Gk???{?/?0??a???{:]?N???{???=??vqw?~v??>a?[?3)???nf? ?C?????!?8???}??u??l??T?@?? -v????(*.??C??????S?F2s3????MV?????4*??gD??w?=??D?????L???Q??G? ??mcn???i???8????o'?YV!?0t???hw???u?U?v}]i?=?1?\A?1T?}??cWGcK?j?1\?j????*?*?F?e?b????I??V???>???@????k?{???v?)?%???????? -??5?r*?X?SRi??^???o??)?{?*5=? x?X?\??????PG??S??|?K?;?]???cSU?0[;?e???E[?j???????5?t\a6I(??D????_??nqdm??O>eci>l??P?$??p???Ajn?niWm??e???E??????v??????[???3??????,%?m????Z?vp?u????w%^?(???M??7 o??[ ;26[?n????H?? -?????t?L?Y?B ???????}??*!?Z+??????h~BvxLWhm???????~h#O:?d???J??#?_t?i????V?3????:?????? o???!?v???|????????o??????????R@???`?`?????6o???;?g%0???x????????zZ??X??rv??{?h??`P????aG?BB(?T^`nF??L??F??a?????.}????t1+????o??????i??0??z??(?h{??&?|w??i??#?U6Z?E?fj?f??V?:?*??{A??=?qT?G?Om??V????bP.??????y????? ? ??.;??? ????E??Q6gk?%~%%?????? ???q??S?"??x????1Rvj?d??????F?3?k??s?H&/b& ?Y???^U?? -1??????D~]}???5????E?7??$????????MF?'?.v???b???U-R?}???t???G??x? }??Nz?!c?qxa27D??z?^z??&q??7b??????z?m!-???n????6M?6?"Bu??*?Gy~?sA?:?+?s?FY?????}?????]????IK??????y??k?3?P??d?cO????V?*_?f?Gt0???????b??Pn???? x?*|G???????? ???q??/? -?uz?:!?4{K??p?!X??J ]?P?@??SU#????"u???)?u?? -V?i? -?@???.?????U?B?A*??{?2c???"?n???DfRm???]?efO???/??4?W:?{U?[??n?2k??[ja}??%? -???<s{?????R= ?G??v??\??????????n?%?5O?]l?(??% ??i????R??g,NJ]X(!?1h")?B ?=????O??X>?l??????YB?a??y??????C| Le?(?&??`?M?Ug??1(?8mv5?? ??cw,????oJ? ??L????ax???0????????q????V[Z?????X;m???????????"?V"?i?D}@^~k8??%??1????V(?????;??g?}b 70??<?? -2??&]}?Z??g4?M?>_s|?e????nT????GU?????????????l???@n???Q:"Q?{?g????Y/\|?j!?;?L)3??sS???%? -?v??60y#+???NT?n????}?????yr#0`?5' ??1)????$Tm9T?e?,?% ?U???{?] -8????h?{ }??OB\?????gSR..?{????u -'?m? [???T???$B??z??]d?wa:?i?r\1?|???l???H???=Od? c??U????????Fd?W?]????????b?mZe???? UM?,?6????z?????+????_??{??3\???f>??????v????7???j??s?*?j??s?Y?3?pga{YZX?fn?? TyJ73???q?O?@???-~?}??.K????@??c?<-=::+9?v ?????0????;????"??????????*1?9?{??~q?P??!?\tR?uO?*g?]m?X???w&???t?f1?x?z?????8?]F/? ?1???r????H?;?e"B)?AE?A???x?ye????>????C?[?Z?cK?q?)z9u????0D?I? S???????s5??;???IC?5t?l?jX??t0???.0????2*x??_??|#?g??k???*? ?X?t6???>????u?vlj?7?|e]R?4k??*??`U?A ?J?Y,?D[2H?n?}:???V??? G?????8??Q? -????`?"??$?-?.K?;H?,??l{?????i??3?a ??C??!?Q:?"4`k,??P????\d>??????;?T?.{?Wd?e??j?0? ?6? -#WW1???6\??? e???P???8 ???/C?m???????w/?]?w2??(???????C?'??!?!? >?y?|??PY+??i???F??]a?r -?J??n???{?&????????kVV$I?H?t???T=??x? ??s?pS?y?A?I????-?t.3??l?????B?eY??i?TC&R??????+]A?`????o??{?Yj??5??y>???? -.|D?? HA;?+U2?????E<d??? ??s?!?,?} ? r??r-y??O??? ?????"?A??h??I??b????^?j??M}??Qi 2?I????-'_?Yt???@\?S?'(t9E>(??>??*??`d?1??$pL?x?; j?z????f????1e?T(@? p?Y?yr%\?6???P;d?4???? -Gf??7+?? -???V -V3?????l????)?q?u???(?W???U)???p? ?w????PF_????.??67?cS??$[??N????a??1No*?M=???:?2??\???*u?x#?w?????|Y"{???)p? -???????.?????/?(??6??v????wu???Q?m?(DY7[??a?K???&?'?L?.? -?s????A?#.???)3Bd ?g?????\&"?????h?r???8?yefV?!p??)E???????Ja??`s????????.??7Y??^V?[C?>?g?, ?=?6n????>Kb4t=5???=N?7>??:1??_?8???>???ng????????N?S?yq?? .???? -5?4??*@?r?8??fP???;F???????????o????I?.??u???nL.?????C????E?*gg)Rgw?oH?f????2k3????d]i?!ae????#T?m -?zF???/.z?YZ??9? -?????oe?rQ>????5???}L?O???m?(B??T????? -?]?%???91????k?????????????%??????6??? -?W?????']{?nvv ??O??????nx?PN???rN?6? Xu>????? :?,:_ -`%???]!???]0 \?^?? ???x?HQ????uv ??Ke??U?QM? ??0?lz???w>???? -?????})??O;?S?I ?9 6???,?>???im?;??1}??????vC????J?[?QEs??G???w>??w??2?1`?6? -????d?$j???????? +}$?O?c??3Y<8?`?d?z???+D&?+_?V? Vf5@????mg15?)?d@??a?s??{??Y?@ ??W??F??k5k ?LpD??%?(I??I?S????]~?.?eL^?T?[?*zr??hFc??]P???s?H??-5??c??.]??????'k?y?; -??+? q??????9\fW*U4???Y.?A?H?z@?c???????i?W???.l?~_~$d?:s>mk'?PR?g???r?$H].'??0??6_?:?? -? ?]?u??F?? ???#??i? -?L?-??????????i?1??@?X`??Q ???D,?r];?=?V?f?2?S)>???5??])??<^?????-R.~????S????-?n-?wX?l2?$??N?rMr_?p>??.?^|"S[B??()?Rv ????#X???wy??????8??=R;??? -??*?d??????iA?w??}v?????>H????ssaBa??E???????{??'?'??8?}q?l???0?U?,?('?&???[???KK`?????0?c?DL W????'4(? ?j?ofc?#????????}"&0WQ????????????(!?Q????zG1??G????{??? -?$??~}?W,??;?`?N?at????\??? A?"???M??????????????7xw~???y'g?^?q????hxL+Xj???'B???2]?p&??????~??~?X?j}UG?JT?????H??????~?J????J ?????*/B/h???H?WA??Kt?UVo?????U?0????@?Pj&??~????? ?faR???^?????5??F*?????t?d??j???d??Ox?4L?_2?"?30KO?????D?????&8?f?3?F*??t?^|-W ????J??????'??????C??>* -?DA ???????8?In?3?p?!?A???%:d????`D -???v????$lH??Ny?????????M?????3ZU*rh??Q|?wEn? -?d?????????K?]?A}?H??q?aju??2?s"D?kM????q?%c!-a??t $?R??\4??%?BX?0?w??Z?f???:?p???w8L?6G?H?,?FHU$?j??@?q?????+?&U>???}{??-X????=VY??`g?????0?4|??T^?J??? -a???5h??|=???Xl{!?8u?6?? -lL?? ????N*?????v?7?V?BC )?3???[??1? =[m???~?/[??? ?|w`???R?PO?'o????L????2??o=?H??????2??d?????N???_?j?#b???] ??a?gt[??J?!I?t????X??]???_?T-Z????G73?a???:n??? ?>??Sx??^??>????m?pb -xh????;dv?m:6???;T3j?' ?????#?|?>?^????????\q?????/Z?AG?Rc??U"^Sw?????P?:??? IA??2?n?(5?`J??\Y?_C??????W^bw?Y?,?'Tk)?9U??? -?b?F^??P???9????;? ttg?nQ ????Z?6??%????G????6 6??o?tRB???@????!2n???&?`?P????k??"??w??m??????SmXr{!?u(v1?bD??!?M~5Rw?SD??"??? -2?????nxV??-??~???ot?FW~??Ky?b??? c$??m?????o???P4???Z???,Ei??????????|g?P????V?????kR???6?????h?M@?H"Y?e??U1??????`?#"????dW?Kv +o0?D?????A????y???3Y??3?? +?#???????JJ??r? ?F;k?G?4??? +??? +?m?????? ??]?{u???Ek??5j7????????xq?V??'?t?????"???$ t??Y???z?R???g?????!i m?=?qi?R? +6??d +"M? {??s??k.?P|JhL??-??? Z????P??U????O???H?? ?J???v|?????????f????M???b?i???K?h?rZ@"???^s?!?,?????H?^2????I????y??9X??f?? ?]????3o??}???? ?e?????:{me?????9?VwS??B?u?)?jp????1?s6?9?????? + b?CA???????4??>M??ij????4|MM???????????3?gk?|? ?0??a0????&2??F???k[??m?E?:??%??z?2??6.)???L?????;??j?d??I?Q?????v??5?????.nkj?????T???f????{?\E???;?0??E?d??Ik'??? ? ? +IZqb< +??%j}? ??? ??jhs??puS???? +????????1???:??+>???M?!y?b??.$?J2Y ??yB???R???]9?"???2/>#?z+$?A?*\?I?|y?;_?y6?Xv?? +A|?X???6?b? ?m:?f%%,?v????~G?????j?!?kL??O??s?w{????^? ???h-_z???????=sO?k???7`{????X?,??????Z??#?tk?c&?????????a| ?_??;?????O????c?????^\?N?TE????????U??i4Q9???v??A{?m??M?!t0mX?g2?????6?*??lY~???d??j???+???8??+h?#?????v??hl U?6? \m???????Q?*??? ?-oE>n????? ?? ???W??ie??[pp?|?????=@!???WN?CpJj/???S'????m?<?u?Q?A?2^@?V6??`v?t~????-?d??f??y?0K@?b????????O????n?BO???&T?d? _??p??!???????Z4???E +?????_X}????o{??H??el?/???)ZRN?Ko?]%.0uG???RtU/???e??-T??Y????fU????\E?(?Oq#(PGue{ S?(k?;7????????bY58i??6?~???????????x_???U?jy??????lf???U????'4\???0?m?):?BJ?eI?#_?*?1dV?_#3???=l???,*W???V?&??/?????y??+Gfd????V???1????m???W? 9=?oT????p???f?e9Y??d???D?6(?Y???x???23 ?I??.??O?b????k???i??+D??K?z??F??????????#?? +?? ?@ 2of'???????U&????.??$gJ???x?????W?v??V????q??t]# ?>vI?k(?@?g?Q?&?4????????[???L??)gC$u(?W????V???Ww?k????Pr ????r*??Y$?=kg?T&?p;w???U??`1?XxON????????%z?R?????Km??&(]&3+??nP#?_ +?\?tk????dia????V?P?????+???Mm?6???vaW:,i?s?C??~E??d????H?tx??w^ +?\@r?z?`s???p??fX??z??c??HF??7=??x????KR)q>?g?,?????"????M8F?,I?^j????xa#??8????s?G2?F`;??g????Q"a???????z??XP??W????*?????'5?????r?;u?????3?I?????d??e???b2?"?????_ +?x`."?g}?;??????)?????? +?0?????>"2?D?u?a~????? ???1 +??????????q?Z???6???]#?P???e.[?SKZ???f=?Fl?B?G???x??4O????q$4A|????NK&?f?%Y??C??9????L=???Go?C?:??]?ecE +Og>?+?NL +??o???n??????]'?rb?V*?_0g????O?W~???y?e}p???}XU?J?{a|e??????u???Hw?T??j?K??Z?sv=?????(??E???? ??*?'9??q???y?~y,=H}?&6?K??[??,??? +e#?Z????/D`??0???t????;??6?p%2???? 5???N??u?P??1~?w?Hb??Kcc???QIs0\? so?&?*??'+?z`??'?zVk???:?rO????&5?R??y?X?n???Y???W??b??T?y?*??!Y?7?%?hK?i???O?RWc?J??3a??4??g^=??a?S? +??????eI`rg??$? a??Z8?????Q*{_???D>????????E?A?G?I?? am???\?h??\?g??:B???f???????^b?'1??x??t?hF??l??H?C?9???????[6????>\c/???4>X$?>??z??z????{s^x'??????&???Z{?o?0?????o??8?e{?P?b????????F???_?R\??H?+?o?}8???D???;??,?T?7?M,D??D??j)7?D??G??????r Kj1??N??????g?????oNo?i????[?\??G7ss???go????#?C?`??+??r/???B;g+??????s????C?U?????K$???_?N???Y?#??c??????H)&)??_^!2?p\???2??2?"???l;??)L??J? +?????S? +J0F>?T.0z??Y[p??#?-???"?HZ??ln?S??-c?J&j???WQ???D3?K?l?nV??E??l?a??+(>???,? ?ER??z?'?? ?O???H?qfk???#>3???i[+????/???V??8^??`9??5?Qm??B? 7?h??^?????T???n???MsXTHg?l?Y|?6???f?Y????K?\o?)??&??rUt`???J ?????!?3??????vGc?j?9Q5?4+]a??"2??y??2t???^?6??V????Z??'?4??????5????gt]Ef ???&?S$`??kpQ?????@????h???=? +B+??xObm?x@?#??????*????)1{z?'e??]%L?~???? +-?a?b)??H??XN?????:G?6?B??J?[C??~??|^P?3o?]???u???{4?l??\S??}??<*?10?^w? ??)'?a_A2?C?*/??l?"?'??????qV5?????i?`&??hS?x???}b??uJb???????????HDy,???{o?? ?Ue??*?????? +E?ld;???Q??=??Eb??^?y???-IWA?_???a?}?????9??????6z!H^????qcP?X?*?5??w?????6?T?"????=VY??? +??i??b=?????? E%?????a??????-??&??Z_??T???:????????_????h?R?t?x,??? Z(???T?b??f???`s$;DV, ????S=???`l??&Fe2??B?Y?T??)?W3e?????mE??B?{??+ +???????h?E# +?*j??@?????Q>i+?U????}{?F-X????=?Y??`'k?p???04|??T??J??? +a???5h??|]???l;!o?X5?6?? +lt?? ????N*????????7??BC ??3??[?}1L +????????_?j??????? +??a5gtZ??J?!???4??????]???_??Sx??^??>????u?pb +xh????3dz?m26???;T3j?' ?????#?|?>?^?V??????\q?????7J?A[?R}??U"NCg????P???? IA??2?N?(5HJ??\Y?_]??????W^bw?Y?,?;Ds)?9E????b????a????S????wv??N?3???"?5???+J???,??]&Op?? +??~|????BHu??f???>L???FzV??eC?R??[???&Z??qQ?#{??????! ?d???KlGT??*???????????83W0?(?.*????*?T?i?r???7??M#D?????^M??%??7????3?V7\????m$?a>??5??"hZ??>??d???F I1???}?E(2}??r?h=?:????9???~?Y?/?k???FO#???z?yxJ???5?p?????Q?+?}?@????)??Ha*_?_??????wv??????#?%??] ?D 3?{???????6??T????kH??oV?"E\A(7???X??Xh??? +?m?????F1??AS???????????`??;?$????vFc?g??yz_???????\G??Q?????o???b???%??_?:.??gh4??2?:$70??i-????-[8?t??]2a:8??????$??!???4?qD)??"?$????v'i???G5?o!e???c????^????? +?? +e???A>!???|/]?IC???????`?4w???]?Q???\*endstream endobj 116 0 obj << /Type /Font @@ -2918,14 +2931,14 @@ /FirstChar 2 /LastChar 119 /Widths 643 0 R -/BaseFont /GMEBOS+NimbusRomNo9L-Medi +/BaseFont /RZQDYA+NimbusRomNo9L-Medi /FontDescriptor 114 0 R >> endobj 114 0 obj << /Ascent 690 /CapHeight 690 /Descent -209 -/FontName /GMEBOS+NimbusRomNo9L-Medi +/FontName /RZQDYA+NimbusRomNo9L-Medi /ItalicAngle 0 /StemV 140 /XHeight 461 @@ -2952,7 +2965,7 @@ 6 ??????=?????x:??;?? 2{wl??#?l ?????????of 8]??2??@????????l?????2?6?:?=?D??????c?????????mm-]??m?W?r0s-??????4tx?mbf -??gP$??m?L??9???????ATf?????????+?h ?(g???@??S???'??A????y?w??]??r???????b???r?V??? ?~??2??w???oef???D?=P???????{??M??`b`??? $f?4R0s04?[???/??????????_m?3?????bjfha????\???Fg?.?_??E??T?i?~??????????;???C????0??m\???,z&??????b???o??????????? @??h&??J????V???6?1?3'???F??????nCG{?wE?:??%?s????. at C??C?????j???1??.f??@??:??\?J?N???M?2???@?? ????#??])?_C]X??????OR??\?5?6?_~?:EH)????gs2?_???~m?)*?>CN??????Q??:??`???"{&?Fa??C??;:??;???????????????#?q?D???????Z?aP??W???J???t??????WWj??~\l???s?x???CN??????Q??:??`???"{&?Fa??C??;:??;???????????????#?q?D???????Z?aP??W???J???t??????WWj??~\l???s?x????r?H5?J nZ???????d8???H?a^??U!???V??0{cC? ?Q?????? ?????BZ?x??[8???????9y?^???"??Z???? ??????)?????(???Y?kl??%??N???w??7?H?K????I????!=?????? ?????6? *??)9VBZ.???e?0?_??J???8?pI?!H??????????&EQ??w`ay?}??????K??? ????n2??yd?????O?f???w56 ??? ? ????i?/?p?L?2`?2:?[??3t?,?pX????l???M}B?5?K??:???a??a?? @@ -3044,7 +3057,7 @@ ?)??Dt\???L??.#XxH?=_N?B*Ga??@b? qk??9???&ORD ????4?U`_r: ?7N0???=?q+?????w 5E?g~a4??0??th??8M????q?{????i@]?b3?%\????FO/???3?7???????? ?0nhzj???????f?im???]?]L?:G?L8]?????? ??qS&H?%??xRc???nB??Z?????c]?n%??O?p0?E??]]?22?q?S?????&)o???P]?~?=c????,3?????x?+?I????:?D]V??l9??s?|?0?A?dYk???rhp?A?W??8?"?%Mz?pD?6??#;'3?w???a?w????g???O?p?2?S??5??x?????RuN????y??c???c[?B????f`?mb?e?>????'ZU?TL~??gP -y?7?q???????^?)???o:???:????{?9jd??A?5?5V?I?J?????sc??2??o?y?W 2a1??n>?c.?G??,?wiT=d?_~???????@}{+}{ ????endstream +y?7?q???????^?)???o:???:????{?9jd??A?5?5V?I?J?????sc??2??o?y?W 2a1??n>?c.?G??,?wiT=d?_~???????@}{+}{ ??b?endstream endobj 107 0 obj << /Type /Font @@ -3053,14 +3066,14 @@ /FirstChar 2 /LastChar 121 /Widths 644 0 R -/BaseFont /BDKNUS+NimbusSanL-Bold +/BaseFont /JUYHSN+NimbusSanL-Bold /FontDescriptor 105 0 R >> endobj 105 0 obj << /Ascent 722 /CapHeight 722 /Descent -217 -/FontName /BDKNUS+NimbusSanL-Bold +/FontName /JUYHSN+NimbusSanL-Bold /ItalicAngle 0 /StemV 141 /XHeight 532 @@ -3084,7 +3097,7 @@  ???;??C?h???=A?CpM????{pBpB ?!???=s???4o???????v????V=+??S9[?5DC?????ZPk??`????p????C?????????a?`?=????#? H$*.?w? ??G?tP?/@?? ???{Hn???!?z??:C!?zw???.????????>???a?g???1??>111???_@??????g???J?*q????\;??-?{\??*???!?1^w;^ ??oT f?w?M???[3E(bs?????9??^0???Aa??d?? -4?A?< j???|??;fA?@? 1???x?8???q?????a?~?pW????????????? ????????l?6H?5????f?C???k???7? ? ?@??????-???w??+?)?*>?????????S???x?E???r?(&$?O?i??Du?????7???s?{???p??&??s??_ ???@[?$?w?????Z????j??P?pv?C????????V????t? ???????D#???????!??P9????d??+C?!?:P????v?Ke???C????K?? ???w??8? ???g???????n ???"?] F??+???@ ????????ko?o????-??m$B???]???z?l}?68??`??uF??E???r*??;M?Q?u??2C?DG +4?A?< j???|??;fA?@? 1???x?8???q?????a?~?pW????????????? ????????l?6H?5????f?C???k???7? ? ?@??????-???w???)?????????????S???x?E???r?(&$?O?i??Du?????7???s?{???p??&??s??_ ???@[?$?w?????Z????j??P?pv?C????????V????t? ???????D#???????!??P9????d??+C?!?:P????v?Ke???C????K?? ???w??8? ???g???????n ???"?] F??+???@ ????????ko?o????-??m$B???]???z?l}?68??`??uF??E???r*??;M?Q?u??2C?DG O?U??r?o??&% #ES??9????'8??????I??J{???3???????UZa??i8?"???tg?M?????W{w?S ???????s??8??p?"??yD?zg????)~??Ye;???|?> endobj 101 0 obj << /Ascent 712 /CapHeight 712 /Descent -213 -/FontName /XDADQD+NimbusSanL-Regu +/FontName /IETVQT+NimbusSanL-Regu /ItalicAngle 0 /StemV 85 /XHeight 523 @@ -3175,7 +3188,7 @@ ?+hJ?????T?@[???5@????? ca ?uRL???>??lM,?)???/????d4???t7?????m,????,?f????{?l??5?v1?'??rS?%d?h??????/??????????3?oT???ln??Ol'??j???_K;c?J???/?_?????????O,# ????????o??`???J???????3?8? M??NNa?b???????Tohoo??/o?Y??,????? p?,c;??mfa ????H??????-7q??:W???D???P?M??????`4?c??s?@??2??? ????B????????????? -?bm-gh?w??c???-?????Y4?????C k?????V?;?????????????????B '1 w??????9????o??%W?5:Z[??r?????????N????????????? -??????D?EUUh?7 ?_? +?????E????i?7 ?_? ?Y???on?Q???????1? f??)?|D?>?c^?y?0/?@??Q/z?f?"7?,?i??~Q??q???f:.?b??$??V?`?'???]????? ?6??C????Q??hC|???mZT?^???j?????J???_???v W?E? ??~?0?}?t??w??Hog??x6Bl?"q??????-.??=?y#+9[P?M???????? y??:??O+?[??z?O-?6?=?\A?`?K?o\?????~??d?B*??9???? ??:?S?_?\?`+h?P?C??????5?(Z?KA?5?a?,?V?2c:?od???|?-??5~????O??|????????]p|^??R?P>+??bn???????? -??? ,84??K??(?endstream +??? ,84??K???(?endstream endobj 100 0 obj << /Type /Font @@ -3318,14 +3331,14 @@ /FirstChar 2 /LastChar 149 /Widths 646 0 R -/BaseFont /JDSEUT+NimbusRomNo9L-Regu +/BaseFont /DVQCOG+NimbusRomNo9L-Regu /FontDescriptor 98 0 R >> endobj 98 0 obj << /Ascent 678 /CapHeight 651 /Descent -216 -/FontName /JDSEUT+NimbusRomNo9L-Regu +/FontName /DVQCOG+NimbusRomNo9L-Regu /ItalicAngle 0 /StemV 85 /XHeight 450 @@ -3542,7 +3555,7 @@ >> endobj 653 0 obj << /Author()/Title(A Swift Tutorial)/Subject()/Creator(DBLaTeX-0.3)/Producer(pdfeTeX-1.21a)/Keywords() -/CreationDate (D:20110516142225-05'00') +/CreationDate (D:20110517090245-05'00') /PTEX.Fullbanner (This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) kpathsea version 3.5.4) >> endobj xref @@ -3554,116 +3567,116 @@ 0000000000 00000 f 0000000009 00000 n 0000014704 00000 n -0000190452 00000 n +0000190454 00000 n 0000000054 00000 n 0000000084 00000 n 0000014828 00000 n -0000190366 00000 n +0000190368 00000 n 0000000129 00000 n 0000000159 00000 n 0000020667 00000 n -0000190241 00000 n +0000190243 00000 n 0000000205 00000 n 0000000241 00000 n 0000020792 00000 n -0000190167 00000 n +0000190169 00000 n 0000000292 00000 n 0000000321 00000 n 0000028277 00000 n -0000190080 00000 n +0000190082 00000 n 0000000372 00000 n 0000000417 00000 n 0000034470 00000 n -0000189993 00000 n +0000189995 00000 n 0000000468 00000 n 0000000502 00000 n 0000034721 00000 n -0000189906 00000 n +0000189908 00000 n 0000000553 00000 n 0000000581 00000 n 0000041326 00000 n -0000189819 00000 n +0000189821 00000 n 0000000632 00000 n 0000000657 00000 n 0000042332 00000 n -0000189695 00000 n +0000189697 00000 n 0000000708 00000 n 0000000734 00000 n 0000047548 00000 n -0000189621 00000 n +0000189623 00000 n 0000000790 00000 n 0000000826 00000 n 0000048177 00000 n -0000189547 00000 n +0000189549 00000 n 0000000882 00000 n 0000000925 00000 n 0000054278 00000 n -0000189460 00000 n +0000189462 00000 n 0000000976 00000 n 0000001002 00000 n 0000055787 00000 n -0000189373 00000 n +0000189375 00000 n 0000001053 00000 n 0000001074 00000 n 0000056287 00000 n -0000189299 00000 n +0000189301 00000 n 0000001125 00000 n 0000001164 00000 n 0000064645 00000 n -0000189174 00000 n +0000189176 00000 n 0000001210 00000 n 0000001245 00000 n 0000064769 00000 n -0000189100 00000 n +0000189102 00000 n 0000001296 00000 n 0000001350 00000 n 0000065081 00000 n -0000189013 00000 n +0000189015 00000 n 0000001401 00000 n 0000001444 00000 n 0000072874 00000 n -0000188926 00000 n +0000188928 00000 n 0000001495 00000 n 0000001530 00000 n 0000072999 00000 n -0000188839 00000 n +0000188841 00000 n 0000001581 00000 n 0000001627 00000 n 0000087023 00000 n -0000188765 00000 n +0000188767 00000 n 0000001678 00000 n 0000001720 00000 n 0000100510 00000 n -0000188653 00000 n +0000188655 00000 n 0000001766 00000 n 0000001789 00000 n 0000100635 00000 n -0000188592 00000 n +0000188594 00000 n 0000001840 00000 n 0000001888 00000 n 0000002310 00000 n 0000002552 00000 n 0000001939 00000 n 0000002429 00000 n -0000187104 00000 n -0000167604 00000 n -0000186932 00000 n -0000166974 00000 n -0000159388 00000 n -0000166803 00000 n +0000187106 00000 n +0000167606 00000 n +0000186934 00000 n +0000166976 00000 n +0000159390 00000 n +0000166805 00000 n 0000002490 00000 n -0000158674 00000 n -0000147555 00000 n -0000158504 00000 n -0000188106 00000 n +0000158676 00000 n +0000147557 00000 n +0000158506 00000 n +0000188108 00000 n 0000008468 00000 n 0000004598 00000 n 0000002649 00000 n 0000008405 00000 n 0000004908 00000 n -0000146940 00000 n -0000135584 00000 n -0000146767 00000 n +0000146942 00000 n +0000135586 00000 n +0000146769 00000 n 0000005062 00000 n 0000005217 00000 n 0000005372 00000 n @@ -3694,18 +3707,18 @@ 0000009330 00000 n 0000014641 00000 n 0000014765 00000 n -0000135249 00000 n -0000127186 00000 n -0000135071 00000 n +0000135251 00000 n +0000127188 00000 n +0000135073 00000 n 0000014015 00000 n 0000014226 00000 n 0000014436 00000 n 0000014890 00000 n 0000014953 00000 n 0000015016 00000 n -0000126251 00000 n -0000107393 00000 n -0000126080 00000 n +0000126253 00000 n +0000107395 00000 n +0000126082 00000 n 0000015079 00000 n 0000015142 00000 n 0000015205 00000 n @@ -3828,18 +3841,18 @@ 0000035664 00000 n 0000035727 00000 n 0000035790 00000 n -0000188222 00000 n +0000188224 00000 n 0000042709 00000 n 0000040449 00000 n 0000035963 00000 n 0000040571 00000 n 0000040634 00000 n -0000105178 00000 n -0000103721 00000 n -0000105017 00000 n -0000103386 00000 n +0000105180 00000 n +0000103724 00000 n +0000105019 00000 n +0000103389 00000 n 0000101532 00000 n -0000103225 00000 n +0000103228 00000 n 0000040697 00000 n 0000040760 00000 n 0000040823 00000 n @@ -4060,7 +4073,7 @@ 0000080831 00000 n 0000080894 00000 n 0000080957 00000 n -0000188339 00000 n +0000188341 00000 n 0000089223 00000 n 0000085806 00000 n 0000081117 00000 n @@ -4183,31 +4196,31 @@ 0000101201 00000 n 0000101264 00000 n 0000101327 00000 n -0000103626 00000 n -0000103602 00000 n -0000105415 00000 n -0000105390 00000 n -0000105505 00000 n -0000126814 00000 n -0000135494 00000 n -0000147236 00000 n -0000159026 00000 n -0000167336 00000 n -0000187626 00000 n -0000188440 00000 n -0000188518 00000 n -0000190524 00000 n -0000202016 00000 n -0000202055 00000 n -0000202093 00000 n -0000202222 00000 n +0000103629 00000 n +0000103605 00000 n +0000105417 00000 n +0000105392 00000 n +0000105507 00000 n +0000126816 00000 n +0000135496 00000 n +0000147238 00000 n +0000159028 00000 n +0000167338 00000 n +0000187628 00000 n +0000188442 00000 n +0000188520 00000 n +0000190526 00000 n +0000202018 00000 n +0000202057 00000 n +0000202095 00000 n +0000202224 00000 n trailer << /Size 654 /Root 652 0 R /Info 653 0 R -/ID [<624EFF68B3B6150ADBBC3276EFE85189> <624EFF68B3B6150ADBBC3276EFE85189>] +/ID [<77C88A09910A7BCE92C6C49BCDC069CB> <77C88A09910A7BCE92C6C49BCDC069CB>] >> startxref -202485 +202487 %%EOF Modified: trunk/docs/tutorial/tutorial.txt =================================================================== --- trunk/docs/tutorial/tutorial.txt 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/tutorial/tutorial.txt 2011-05-17 15:30:41 UTC (rev 4483) @@ -40,15 +40,15 @@ .first.swift ************ -[java] -source~~~~ + +---- include::../../examples/first.swift[] -source~~~~ +---- ************ We can run this program as follows: -[java] -source~~~~ + +---- $ cd examples/swift/ $ swift first.swift Swift svn swift-r3334 (swift modified locally) cog-r2752 @@ -58,16 +58,16 @@ Final status: Finished successfully:1 $ cat hello.txt Hello, world! -source~~~~ +---- The basic structure of this program is a type definition, an application procedure definition, a variable definition and then a call to the procedure: -[java] -source~~~~ + +---- type messagefile; -source~~~~ +---- First we define a new type, called messagefile. In this example, we will use this messagefile type as the type for our output message. @@ -77,12 +77,12 @@ on disk. This example defines a very simple type. Later on we will see more complex type examples. -[java] -source~~~~ + +---- app (messagefile t) greeting() { echo "Hello, world!" stdout=@filename(t); } -source~~~~ +---- Next we define a procedure called greeting. This procedure will write out the "hello world" message to a file. @@ -121,10 +121,10 @@ The code changes from first.swift are highlighted below. -[java] -source~~~~ + +---- include::../../examples/parameter.swift[] -source~~~~ +---- We have modified the signature of the greeting procedure to indicate that it takes a single parameter, s, of type 'string'. @@ -142,20 +142,20 @@ The code for this section can be found in parameter.swift. It can be invoked using the swift command, with output appearing in hello2.txt: -[java] -source~~~~ + +---- $ swift parameter.swift -source~~~~ +---- Now that we can choose our greeting text, we can call the same procedure with different parameters to generate several output files with different greetings. The code is in manyparam.swift and can be run as before using the swift command. -[java] -source~~~~ + +---- include::../../examples/manyparam.swift[] -source~~~~ +---- Note that we can intermingle definitions of variables with invocations of procedures. @@ -175,11 +175,11 @@ To do this, we'll use the unix tr (translate) utility. Here is an example of using tr on the unix command line, not using Swift: -[java] -source~~~~ + +---- $ echo hello | tr '[a-z]' '[A-Z]' HELLO -source~~~~ +---- .There are several steps - transformation catalog @@ -192,10 +192,10 @@ where *tr* can be found (usually in /usr/bin/tr but it may differ on your system), like this: -[java] -source~~~~ + +---- localhost tr /usr/bin/tr INSTALLED INTEL32::LINUX null -source~~~~ +---- For now, ignore all of the fields except the second and the third. The second field tr specifies a logical application name and the third @@ -205,38 +205,38 @@ We can define a new procedure, capitalise, which calls tr. -[java] -source~~~~ + +---- (messagefile o) capitalise(messagefile i) { app { tr "[a-z]" "[A-Z]" stdin=@filename(i) stdout=@filename(o); } } -source~~~~ +---- We can call capitalise like this: -[java] -source~~~~ + +---- messagefile final <"capitals.txt">; final = capitalise(hellofile); -source~~~~ +---- So a full program based on the first exercise might look like this: -[java] -source~~~~ + +---- include::../../examples/second_procedure.swift[] -source~~~~ +---- We can use the swift command to run it like this. -[java] -source~~~~ + +---- $ swift second_procedure.swift ... $ cat capitals.txt HELLO FROM SWIFT -source~~~~ +---- Anonymous files ~~~~~~~~~~~~~~~ @@ -246,10 +246,10 @@ To do that, omit the mapping entirely when declaring outfile: -[java] -source~~~~ + +---- messagefile outfile; -source~~~~ +---- Swift will choose a filename, which in the present version will be in a subdirectory called _concurrent. @@ -272,28 +272,28 @@ It is also possible to create user defined types with more structure, for example: -[java] -source~~~~ + +---- type details { string name; int pies; } -source~~~~ +---- Each element of the structured type can be accessed using a . like this: -[java] -source~~~~ + +---- person.name = "john"; -source~~~~ +---- The following complete program, types.swift, outputs a greeting using a user-defined structure type to hold parameters for the message: -[java] -source~~~~ + +---- include::../../examples/types.swift[] -source~~~~ +---- Structured types can be comprised of marker types for files. See the later section on mappers for more information about this. @@ -304,17 +304,17 @@ We can define arrays using the [] suffix in a variable declaration: -[java] -source~~~~ + +---- messagefile m[]; -source~~~~ +---- This program, q5.swift, will declare an array of message files. -[java] -source~~~~ + +---- include::../../examples/q5.swift[] -source~~~~ +---- Observe that the type of the parameter to greeting is now an array of strings, string s[], instead of a single string, string s, that @@ -331,10 +331,10 @@ fashion to data in memory. For example, in the above examples we have seen a variable definition like this: -[java] -source~~~~ + +---- messagefile outfile <"q13greeting.txt">; -source~~~~ +---- This means that outfile is a dataset variable, which is mapped to a file on disk called g13greeting.txt. This variable can be assigned to @@ -349,10 +349,10 @@ simple named mapping - the name of the file that a variable is mapped to is explictly listed. Like this: -[java] -source~~~~ + +---- messagefile outfile <"greeting.txt">; -source~~~~ +---- This is useful when you want to explicitly name input and output files for your program. For example, outfile in exercise HELLOWORLD. @@ -363,10 +363,10 @@ exercise ANONYMOUSFILE. A variable declaration is mapped anonymously by ommitting any mapper definition, like this: -[java] -source~~~~ + +---- messagefile outfile; -source~~~~ +---- Later exercises will introduce other ways of mapping from disk files to SwiftScript variables. @@ -391,8 +391,8 @@ The important bit of regexp.swift is: -[java] -source~~~~ + +---- messagefile inputfile <"q16.txt">; countfile c ; -source~~~~ +---- fixed_array_mapper ^^^^^^^^^^^^^^^^^^ @@ -408,10 +408,10 @@ element of the array is mapped into one file in the specified directory. See fixedarray.swift. -[java] -source~~~~ + +---- include::../../examples/fixedarray.swift[] -source~~~~ +---- foreach ~~~~~~~ @@ -427,23 +427,23 @@ containing the word count for the corresponding input file. We combine the use of the fixed_array_mapper and the regexp_mapper. -[java] -source~~~~ + +---- include::../../examples/foreach.swift[] -source~~~~ +---- If ~~ Decisions can be made using 'if', like this: -[java] -source~~~~ + +---- if(morning) { outfile = greeting("good morning"); } else { outfile = greeting("good afternoon"); } -source~~~~ +---- if.swift contains a simple example of this. Compile and run if.swift and see that it outputs "good morning". Changing the morning variable @@ -462,18 +462,18 @@ Here's the program: -[java] -source~~~~ + +---- include::../../examples/iterate.swift[] -source~~~~ +---- echo is the standard unix echo. wcl is our application code - it counts the number of bytes in the one file and writes that count out to another, like this: -[java] -source~~~~ + +---- $ cat ../wcl #!/bin/bash echo -n $(wc -c < $1) > $2 @@ -482,13 +482,13 @@ $ wcl a b $ cat b 5 -source~~~~ +---- Install the above wcl script somewhere and add a transformation catalog entry for it. Then run the example program like this: -[java] -source~~~~ + +---- $ swift iterate.swift Swift svn swift-r3334 cog-r2752 @@ -501,7 +501,7 @@ $ ls foldout* foldout0000 foldout0001 foldout0002 foldout0003 -source~~~~ +---- Runtime features ---------------- @@ -512,11 +512,11 @@ When running a workflow, its possible to generate a provenance graph at the same time: -[java] -source~~~~~ + +----- $ swift -pgraph graph.dot first.swift $ dot -ograph.png -Tpng graph.dot -source~~~~ +---- graph.png can then be viewed using your favourite image viewer. The dot application is part of the graphViz project. More information can be found at http://www.graphviz.org. @@ -621,11 +621,11 @@ We should be able to use the mapper we write in a SwiftScript program like this: -[java] -source~~~~ + +---- type file; file f ; -source~~~~ +---- First we must choose a base class - AbstractMapper or AbstractFileMapper. We aren't going to use a directory listing to decide @@ -640,8 +640,8 @@ vdsk directory, make a directory src/tutorial/|and put this file in src/tutorial/MyFirstMapper.java. -[java] -source~~~~ + +---- package tutorial; import java.util.Arrays; @@ -675,17 +675,17 @@ return null; } } -source~~~~ +---- Now we need to inform the Swift engine about the existence of this mapper. We do that by editing the MapperFactory class definition, in src/org/griphyn/vdl/mapping/MapperFactory.java and adding a registerMapper call alongside the existing registerMapper calls, like this: -[java] -source~~~~ + +---- registerMapper("my_first_mapper", tutorial.MyFirstMapper.class); -source~~~~ +---- The first parameter is the name of the mapper that will be used in SwiftScript program. The second parameter is the new Mapper class that @@ -696,8 +696,8 @@ This new Swift build will be aware of your new mapper. We can test it out with a hello world program: -[java] -source~~~~ + +---- type messagefile; (messagefile t) greeting() { @@ -709,16 +709,16 @@ messagefile outfile ; outfile = greeting(); -source~~~~ +---- Run this program, and hopefully you will find the "hello" string has been output into the hard coded output file myfile.txt: -[java] -source~~~~ + +---- $ cat myfile.txt hello -source~~~~ +---- So that's a first very simple mapper implemented. Compare the source code to the single_file_mapper in @@ -736,30 +736,30 @@ First we have the program in working form, restart.swift. -[java] -source~~~~ + +---- include::../../examples/restart.swift[] -source~~~~ +---- We must define some transformation catalog entries: -[java] -source~~~~ + +---- localhost touch /usr/bin/touch INSTALLED INTEL32::LINUX null localhost broken /bin/true INSTALLED INTEL32::LINUX null -source~~~~ +---- Now we can run the program: -[java] -source~~~~ + +---- $ swift restart.swift Swift 0.9 swift-r2860 cog-r2388 RunID: 20100526-1119-3kgzzi15 Progress: Final status: Finished successfully:4 -source~~~~ +---- Four jobs run - touch, echo, broken and a final echo. (note that broken isn't actually broken yet). @@ -767,15 +767,15 @@ Now we will break the broken job and see what happens. Replace the definition in tc.data for broken with this: -[java] -source~~~~ + +---- localhost broken /bin/false INSTALLED INTEL32::LINUX null -source~~~~ +---- Now when we run the workflow, the broken task fails: -[java] -source~~~~ + +---- $ swift restart.swift Swift 0.9 swift-r2860 cog-r2388 @@ -790,26 +790,26 @@ Directory: restart-20100526-1121-tssdcljg/jobs/1/broken-1i6ufisj stderr.txt: stdout.txt: -source~~~~ +---- From the output we can see that touch and the first echo completed, but then broken failed and so swift did not attempt to execute the final echo. There will be a restart log with the same name as the RunID: -[java] -source~~~~ + +---- $ ls *20100526-1121-tssdcljg*rlog restart-20100526-1121-tssdcljg.0.rlog -source~~~~ +---- This restart log contains enough information for swift to know which parts of the workflow were executed successfully. We can try to rerun it immediately, like this: -[java] -source~~~~ + +---- $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift Swift 0.9 swift-r2860 cog-r2388 @@ -824,11 +824,9 @@ stderr.txt: stdout.txt: ----- - Caused by: Exit code 1 -source~~~~ +---- Swift tried to resume the workflow by executing "broken" again. It did not try to run the touch or first echo jobs, because the restart log @@ -842,15 +840,15 @@ Remove the existing "broken" line and replace it with the successful tc.data entry above: -[java] -source~~~~ + +---- localhost broken /bin/true INSTALLED INTEL32::LINUX null -source~~~~ +---- Now run again: -[java] -source~~~~ + +---- $ swift -resume restart-20100526-1121-tssdcljg.0.rlog restart.swift Swift 0.9 swift-r2860 cog-r2388 @@ -858,7 +856,7 @@ RunID: 20100526-1128-a2gfuxhg Progress: Final status: Initializing:2 Finished successfully:2 -source~~~~ +---- Swift tries to run "broken" again. This time it works, and so Swift continues on to execute the final piece of the workflow as if nothing @@ -871,30 +869,29 @@ Named and optional parameters ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -anchor:named_parameters In addition to specifying parameters positionally, parameters can be named, and if desired a default value can be specified: -[java] -source~~~~ + +---- (messagefile t) greeting (string s="hello") { app { echo s stdout=@filename(t); } } -source~~~~ +---- When we invoke the procedure, we can specify values for the parameters by name. The following code can be found in q21.swift. -[java] -source~~~~ + +---- french = greeting(s="bonjour"); -source~~~~ +---- or we can let the default value apply: -[java] -source~~~~ + +---- english = greeting(); -source~~~~ +---- Added: trunk/docs/userguide/userguide-rotated.jpg =================================================================== (Binary files differ) Property changes on: trunk/docs/userguide/userguide-rotated.jpg ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: trunk/docs/userguide/userguide-shane.jpg =================================================================== (Binary files differ) Property changes on: trunk/docs/userguide/userguide-shane.jpg ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Deleted: trunk/docs/userguide/userguide.html =================================================================== --- trunk/docs/userguide/userguide.html 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/userguide/userguide.html 2011-05-17 15:30:41 UTC (rev 4483) @@ -1,4351 +0,0 @@ - - - - - -Swift User Guide - - - - - -
    -
    -

    1. Overview

    -
    -

    This manual provides reference material for Swift: the SwiftScript -language and the Swift runtime system. For introductory material, -consult the Swift tutorial -http://www.ci.uchicago.edu/swift/guides/tutorial.php.

    -

    Swift is a data-oriented coarse grained scripting language that supports -dataset typing and mapping, dataset iteration, conditional branching, -and procedural composition.

    -

    Swift programs (or workflows) are written in a language called -SwiftScript.

    -

    SwiftScript programs are dataflow oriented - they are primarily -concerned with processing (possibly large) collections of data files, by -invoking programs to do that processing. Swift handles execution of such -programs on remote sites by choosing sites, handling the staging of -input and output files to and from the chosen sites and remote execution -of program code.

    -
    -
    -
    -

    2. The SwiftScript Language

    -
    -
    -

    2.1. Language basics

    -

    A Swift script describes data, application components, invocations of -applications components, and the inter-relations (data flow) between -those invocations.

    -

    Data is represented in a script by strongly-typed single-assignment -variables. The syntax superficially resembles C and Java. For example, -{ and } characters are used to enclose blocks of statements.

    -

    Types in Swift can be atomic or composite. An atomic type can be -either a primitive type or a mapped type. Swift provides a fixed set -of primitive types, such as integer and string. A mapped type -indicates that the actual data does not reside in CPU addressable memory -(as it would in conventional programming languages), but in POSIX-like -files. Composite types are further subdivided into structures and -arrays. Structures are similar in most respects to structure types in -other languages. Arrays use numeric indices, but are sparse. They can -contain elements of any type, including other array types, but all -elements in an array must be of the same type. We often refer to -instances of composites of mapped types as datasets.

    -

    -type-hierarchy.png -

    -

    Mapped type and composite type variable declarations can be annotated -with a mapping descriptor indicating the file(s) that make up that -dataset. For example, the following line declares a variable named -photo with type image. It additionally declares that the data for -this variable is stored in a single file named shane.jpeg.

    -
    -
    -
    image photo <"shane.jpeg">;
    -

    Component programs of scripts are declared in an app declaration, with -the description of the command line syntax for that program and a list -of input and output data. An app block describes a functional/dataflow -style interface to imperative components.

    -

    For example, the following example lists a procedure which makes use of -the ImageMagick http://www.imagemagick.org/ convert command to -rotate a supplied image by a specified angle:

    -
    -
    -
    app (image output) rotate(image input) {
    -  convert "-rotate" angle @input @output;
    -}
    -

    A procedure is invoked using the familiar syntax:

    -
    -
    -
    rotated = rotate(photo, 180);
    -

    While this looks like an assignment, the actual unix level execution -consists of invoking the command line specified in the app -declaration, with variables on the left of the assignment bound to the -output parameters, and variables to the right of the procedure -invocation passed as inputs.

    -

    The examples above have used the type image without any definition of -that type. We can declare it as a marker type which has no structure -exposed to SwiftScript:

    -
    -
    -
    type image;
    -

    This does not indicate that the data is unstructured; but it indicates -that the structure of the data is not exposed to SwiftScript. Instead, -SwiftScript will treat variables of this type as individual opaque files.

    -

    With mechanisms to declare types, map variables to data files, and -declare and invoke procedures, we can build a complete (albeit simple) -script:

    -
    -
    -
    type image;
    -image photo <"shane.jpeg">;
    -image rotated <"rotated.jpeg">;
    -
    -app (image output) rotate(image input, int angle) {
    -   convert "-rotate" angle @input @output;
    -}
    -
    -rotated = rotate(photo, 180);
    -

    This script can be invoked from the command line:

    -
    -
    -
      $ ls *.jpeg
    -  shane.jpeg
    -  $ swift example.swift
    -  ...
    -  $ ls *.jpeg
    -  shane.jpeg rotated.jpeg
    -

    This executes a single convert command, hiding from the user features -such as remote multisite execution and fault tolerance that will be -discussed in a later section.

    -
    Figure 1. shane.jpeg

    -userguide-shane.jpeg -

    -
    Figure 2. rotated.jpeg

    -userguide-rotated.jpeg -

    -
    -
    -

    2.2. Arrays and Parallel Execution

    -

    Arrays of values can be declared using the [] suffix. An array be -mapped to a collection of files, one element per file, by using a -different form of mapping expression. For example, the filesys_mapper -maps all files matching a particular unix glob pattern into an array:

    -
    -
    -
    file frames[] <filesys_mapper; pattern="*.jpeg">;
    -

    The foreach construct can be used to apply the same block of code to -each element of an array:

    -
    -
    -
    foreach f,ix in frames {
    -  output[ix] = rotate(frames, 180);
    -}
    -

    Sequential iteration can be expressed using the iterate construct:

    -
    -
    -
    step[0] = initialCondition();
    -iterate ix {
    -  step[ix] = simulate(step[ix-1]);
    -}
    -

    This fragment will initialise the 0-th element of the step array to -some initial condition, and then repeatedly run the simulate -procedure, using each execution’s outputs as input to the next step.

    -
    -
    -

    2.3. Ordering of execution

    -

    Non-array variables are single-assignment, which means that they must -be assigned to exactly one value during execution. A procedure or -expression will be executed when all of its input parameters have been -assigned values. As a result of such execution, more variables may -become assigned, possibly allowing further parts of the script to execute.

    -

    In this way, scripts are implicitly parallel. Aside from serialisation -implied by these dataflow dependencies, execution of component programs -can proceed in parallel.

    -

    In this fragment, execution of procedures p and q can happen in -parallel:

    -
    -
    -
    y=p(x);
    -z=q(x);
    -

    while in this fragment, execution is serialised by the variable y, -with procedure p executing before q.

    -
    -
    -
    y=p(x);
    -z=q(y);
    -

    Arrays in SwiftScript are more monotonic - a generalisation of being -assignment. Knowledge about the content of an array increases during -execution, but cannot otherwise change. Each element of the array is -itself single assignment or monotonic (depending on its type). During a -run all values for an array are eventually known, and that array is -regarded as closed.

    -

    Statements which deal with the array as a whole will often wait for the -array to be closed before executing (thus, a closed array is the -equivalent of a non-array type being assigned). However, a foreach -statement will apply its body to elements of an array as they become -known. It will not wait until the array is closed.

    -

    Consider this script:

    -
    -
    -
    file a[];
    -file b[];
    -foreach v,i in a {
    -  b[i] = p(v);
    -}
    -a[0] = r();
    -a[1] = s();
    -

    Initially, the foreach statement will have nothing to execute, as the -array a has not been assigned any values. The procedures r and s -will execute. As soon as either of them is finished, the corresponding -invocation of procedure p will occur. After both r and s have -completed, the array a will be closed since no other statements in the -script make an assignment to a.

    -
    -
    -

    2.4. Compound procedures

    -

    As with many other programming languages, procedures consisting of -SwiftScript code can be defined. These differ from the previously -mentioned procedures declared with the app keyword, as they invoke -other SwiftScript procedures rather than a component program.

    -
    -
    -
    (file output) process (file input) {
    -  file intermediate;
    -  intermediate = first(input);
    -  output = second(intermediate);
    -}
    -
    -file x <"x.txt">;
    -file y <"y.txt">;
    -y = process(x);
    -

    This will invoke two procedures, with an intermediate data file named -anonymously connecting the first and second procedures.

    -

    Ordering of execution is generally determined by execution of app -procedures, not by any containing compound procedures. In this code block:

    -
    -
    -
    (file a, file b) A() {
    -  a = A1();
    -  b = A2();
    -}
    -file x, y, s, t;
    -(x,y) = A();
    -s = S(x);
    -t = S(y);
    -

    then a valid execution order is: A1 S(x) A2 S(y). The compound -procedure A does not have to have fully completed for its return -values to be used by subsequent statements.

    -
    -
    -

    2.5. More about types

    -

    Each variable and procedure parameter in SwiftScript is strongly typed. -Types are used to structure data, to aid in debugging and checking -program correctness and to influence how Swift interacts with data.

    -

    The image type declared in previous examples is a marker type. -Marker types indicate that data for a variable is stored in a single -file with no further structure exposed at the SwiftScript level.

    -

    Arrays have been mentioned above, in the arrays section. A code block -may be applied to each element of an array using foreach; or -individual elements may be references using [] notation.

    -

    There are a number of primitive types:

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - -
    type contains

    int

    integers

    string

    strings of text

    float

    floating point numbers, that behave the same as Java doubles

    boolean

    true/false

    -
    -

    Complex types may be defined using the type keyword:

    -
    -
    -
    type headerfile;
    -type voxelfile;
    -type volume {
    -  headerfile h;
    -  voxelfile v;
    -}
    -

    Members of a complex type can be accessed using the . operator:

    -
    -
    -
    volume brain;
    -o = p(brain.h);
    -

    Sometimes data may be stored in a form that does not fit with Swift’s -file-and-site model; for example, data might be stored in an RDBMS on -some database server. In that case, a variable can be declared to have -external type. This indicates that Swift should use the variable to -determine execution dependency, but should not attempt other data -management; for example, it will not perform any form of data stage-in -or stage-out it will not manage local data caches on sites; and it will -not enforce component program atomicity on data output. This can add -substantial responsibility to component programs, in exchange for -allowing arbitrary data storage and access methods to be plugged in to -scripts.

    -
    -
    -
    type file;
    -
    -app (external o) populateDatabase() {
    -  populationProgram;
    -}
    -
    -app (file o) analyseDatabase(external i) {
    -  analysisProgram @o;
    -}
    -
    -external database;
    -file result <"results.txt">;
    -
    -database = populateDatabase();
    -result = analyseDatabase(database);
    -

    Some external database is represented by the database variable. The -populateDatabase procedure populates the database with some data, and -the analyseDatabase procedure performs some subsequent analysis on -that database. The declaration of database contains no mapping; and -the procedures which use database do not reference them in any way; -the description of database is entirely outside of the script. The -single assignment and execution ordering rules will still apply though; -populateDatabase will always be run before analyseDatabase.

    -
    -
    -

    2.6. Data model

    -

    Data processed by Swift is strongly typed. It may be take the form of -values in memory or as out-of-core files on disk. Language constructs -called mappers specify how each piece of data is stored.

    -
    -
    -

    2.7. Mappers

    -

    When a DSHandle represents a data file (or container of datafiles), it -is associated with a mapper. The mapper is used to identify which files -belong to that DSHandle.

    -

    A dataset’s physical representation is declared by a mapping descriptor, -which defines how each element in the dataset’s logical schema is stored -in, and fetched from, physical structures such as directories, files, -and remote servers.

    -

    Mappers are parameterized to take into account properties such as -varying dataset location. In order to access a dataset, we need to know -three things: its type, its mapping, and the value(s) of any -parameter(s) associated with the mapping descriptor. For example, if we -want to describe a dataset, of type imagefile, and whose physical -representation is a file called "file1.bin" located at -"/home/yongzh/data/", then the dataset might be declared as follows:

    -
    -
    -
    imagefile f1<single_file_mapper;file="/home/yongzh/data/file1.bin">
    -

    The above example declares a dataset called f1, which uses a single file -mapper to map a file from a specific location.

    -

    SwiftScript has a simplified syntax for this case, since -single_file_mapper is frequently used:

    -
    -
    -
    binaryfile f1<"/home/yongzh/data/file1.bin">
    -

    Swift comes with a number of mappers that handle common mapping -patterns. These are documented in the mappers section of this -guide.

    -
    -
    -

    2.8. More technical details about SwiftScript

    -

    The syntax of SwiftScript has a superficial resemblance to C and Java. -For example, { and } characters are used to enclose blocks of statements.

    -

    A SwiftScript program consists of a number of statements. Statements may -declare types, procedures and variables, assign values to variables, and -express operations over arrays.

    -
    -

    2.8.1. Variables

    -

    Variables in SwiftScript are declared to be of a specific type. -Assignments to those variables must be data of that type. SwiftScript -variables are single-assignment - a value may be assigned to a variable -at most once. This assignment can happen at declaration time or later on -in execution. When an attempt to read from a variable that has not yet -been assigned is made, the code performing the read is suspended until -that variable has been written to. This forms the basis for Swift’s -ability to parallelise execution - all code will execute in parallel -unless there are variables shared between the code that cause sequencing.

    -
    -
    -

    2.8.2. Variable Declarations

    -

    Variable declaration statements declare new variables. They can -optionally assign a value to them or map those variables to on-disk files.

    -

    Declaration statements have the general form:

    -
    -
    -
    typename variablename (<mapping> | = initialValue ) ;
    -

    The format of the mapping expression is defined in the Mappers section. -initialValue may be either an expression or a procedure call that -returns a single value.

    -

    Variables can also be declared in a multivalued-procedure statement, -described in another section.

    -
    -
    -

    2.8.3. Assignment Statements

    -

    Assignment statements assign values to previously declared variables. -Assignments may only be made to variables that have not already been -assigned. Assignment statements have the general form:

    -
    -
    -
    variable = value;
    -

    where value can be either an expression or a procedure call that returns -a single value.

    -

    Variables can also be assigned in a multivalued-procedure statement, -described in another section.

    -
    -
    -
    -

    2.9. Procedures

    -

    There are two kinds of procedure: An atomic procedure, which describes -how an external program can be executed; and compound procedures which -consist of a sequence of SwiftScript statements.

    -

    A procedure declaration defines the name of a procedure and its input -and output parameters. SwiftScript procedures can take multiple inputs -and produce multiple outputs. Inputs are specified to the right of the -function name, and outputs are specified to the left. For example:

    -
    -
    -
    (type3 out1, type4 out2) myproc (type1 in1, type2 in2)
    -

    The above example declares a procedure called myproc, which has two -inputs in1 (of type type1) and in2 (of type type2) and two -outputs out1 (of type type3) and out2 (of type type4).

    -

    A procedure input parameter can be an optional parameter in which case -it must be declared with a default value. When calling a procedure, both -positional parameter and named parameter passings can be passed, -provided that all optional parameters are declared after the required -parameters and any optional parameter is bound using keyword parameter -passing. For example, if myproc1 is defined as:

    -
    -
    -
    (binaryfile bf) myproc1 (int i, string s="foo")
    -

    Then that procedure can be called like this, omitting the optional

    -
    -
    -
    parameter s:
    -binaryfile mybf = myproc1(1);
    -

    or like this supplying a value for the optional parameter s:

    -
    -
    -
    binaryfile mybf = myproc1 (1, s="bar");
    -
    -

    2.9.1. Atomic procedures

    -

    An atomic procedure specifies how to invoke an external executable -program, and how logical data types are mapped to command line arguments.

    -

    Atomic procedures are defined with the app keyword:

    -
    -
    -
    app (binaryfile bf) myproc (int i, string s="foo") {
    -    myapp i s @filename(bf);
    -}
    -

    which specifies that myproc invokes an executable called myapp, -passing the values of i, s and the filename of bf as command line -arguments.

    -
    -
    -

    2.9.2. Compound procedures

    -

    A compound procedure contains a set of SwiftScript statements:

    -
    -
    -
    (type2 b) foo_bar (type1 a) {
    -    type3 c;
    -    c = foo(a);    // c holds the result of foo
    -    b = bar(c);    // c is an input to bar
    -}
    -
    -
    -
    -

    2.10. Control Constructs

    -

    SwiftScript provides if, switch, foreach, and iterate -constructs, with syntax and semantics similar to comparable constructs -in other high-level languages.

    -
    -

    2.10.1. foreach

    -

    The foreach construct is used to apply a block of statements to each -element in an array. For example:

    -
    -
    -
    check_order (file a[]) {
    -    foreach f in a {
    -        compute(f);
    -    }
    -}
    -

    foreach statements have the general form:

    -
    -
    -
    foreach controlvariable (,index) in expression {
    -    statements
    -}
    -

    The block of statements is evaluated once for each element in -expression which must be an array, with controlvariable set to the -corresponding element and index (if specified) set to the integer -position in the array that is being iterated over.

    -
    -
    -

    2.10.2. if

    -

    The if statement allows one of two blocks of statements to be -executed, based on a boolean predicate. if statements generally have -the form:

    -
    -
    -
    if(predicate) {
    -    statements
    -} else {
    -    statements
    -}
    -

    where predicate is a boolean expression.

    -
    -
    -

    2.10.3. switch

    -

    switch expressions allow one of a selection of blocks to be chosen -based on the value of a numerical control expression. switch -statements take the general form:

    -
    -
    -
    switch(controlExpression) {
    -    case n1:
    -        statements2
    -    case n2:
    -        statements2
    -    [...]
    -    default:
    -        statements
    -}
    -

    The control expression is evaluated, the resulting numerical value used -to select a corresponding case, and the statements belonging to that -case block are evaluated. If no case corresponds, then the statements -belonging to the default block are evaluated.

    -

    Unlike C or Java switch statements, execution does not fall through to -subsequent case blocks, and no break statement is necessary at the -end of each block.

    -
    -
    -

    2.10.4. iterate

    -

    iterate expressions allow a block of code to be evaluated repeatedly, -with an integer parameter sweeping upwards from 0 until a termination -condition holds.

    -

    The general form is:

    -
    -
    -
    iterate var {
    -    statements;
    -} until (terminationExpression);
    -

    with the variable var starting at 0 and increasing by one in each -iteration. That variable is in scope in the statements block and when -evaluating the termination expression.

    -
    -
    -
    -

    2.11. Operators

    -

    The following infix operators are available for use in SwiftScript -expressions.

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    operatorpurpose

    +

    numeric addition; string concatenation

    -

    numeric subtraction

    *

    numeric multiplication

    /

    floating point division

    %/

    integer division

    %%

    integer remainder of division

    == !=

    comparison and not-equal-to

    < > ⇐ >=

    numerical ordering

    && ||

    boolean and, or

    !

    boolean not

    -
    -
    -
    -

    2.12. Global constants

    -

    At the top level of a SwiftScript program, the global modified may be -added to a declaration so that it is visible throughout the program, -rather than only at the top level of the program. This allows global -constants (of any type) to be defined. (since Swift 0.10)

    -
    -
    -

    2.13. Imports

    -

    The import directive can be used to import definitions from another -SwiftScript file. (since Swift 0.10)

    -

    For example, a SwiftScript program might contain this:

    -
    -
    -
    import defs;
    -file f;
    -

    which would import the content of defs.swift in the current directory:

    -
    -
    -
    type file;
    -

    Imported files are read from the current working directory.

    -

    There is no requirement that a module is imported only once. If a module -is imported multiple times, for example in different files, then Swift -will only process the imports once.

    -

    Imports may contain anything that is valid in a SwiftScript program, -including code that causes remote execution.

    -
    -
    -
    -
    -

    3. Mappers

    -
    -

    Mappers provide a mechanism to specify the layout of mapped datasets on -disk. This is needed when Swift must access files to transfer them to -remote sites for execution or to pass to applications.

    -

    Swift provides a number of mappers that are useful in common cases. This -section details those standard mappers. For more complex cases, it is -possible to write application-specific mappers in Java and use them -within a SwiftScript program.

    -
    -

    3.1. The single file mapper

    -

    The single_file_mapper maps a single physical file to a dataset.

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    f

    myfile

    f[0]

    INVALID

    f.bar

    INVALID

    -
    -
    - --- - - - - - - - - - - - -
    parametermeaning

    file

    The location of the physical file including path and file name.

    -
    -

    Example:

    -
    -
    -
    file f <single_file_mapper;file="plot_outfile_param">;
    -

    There is a simplified syntax for this mapper:

    -
    -
    -
    file f <"plot_outfile_param">;
    -
    -
    -

    3.2. The simple mapper

    -

    The simple_mapper maps a file or a list of files into an array by -prefix, suffix, and pattern. If more than one file is matched, each of -the file names will be mapped as a subelement of the dataset.

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - -
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match -all file names that contain foo. When this mapper is used to specify -output filenames, pattern is ignored.

    -
    -
    -
    -
    type file;
    -file f <simple_mapper;prefix="foo", suffix=".txt">;
    -

    The above maps all filenames that start with foo and have an extension -.txt into file f.

    -
    - --- - - - - - - - - - - - -
    Swift variableFilename

    f

    foo.txt

    -
    -
    -
    -
    type messagefile;
    -
    -(messagefile t) greeting(string m) {.
    -    app {
    -        echo m stdout=@filename(t);
    -    }
    -}
    -
    -messagefile outfile <simple_mapper;prefix="foo",suffix=".txt">;
    -
    -outfile = greeting("hi");
    -

    This will output the string hi to the file foo.txt.

    -

    The simple_mapper can be used to map arrays. It will map the array -index into the filename between the prefix and suffix.

    -
    -
    -
    type messagefile;
    -
    -(messagefile t) greeting(string m) {
    -    app {
    -        echo m stdout=@filename(t);
    -    }
    -}
    -
    -messagefile outfile[] <simple_mapper;prefix="baz",suffix=".txt">;
    -
    -outfile[0] = greeting("hello");
    -outfile[1] = greeting("middle");
    -outfile[2] = greeting("goodbye");
    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    outfile[0]

    baz0000.txt

    outfile[1]

    baz0001.txt

    outfile[2]

    baz0002.txt

    -
    -

    simple_mapper can be used to map structures. It will map the name of -the structure member into the filename, between the prefix and the suffix.

    -
    -
    -
    type messagefile;
    -
    -type mystruct {
    -  messagefile left;
    -  messagefile right;
    -};
    -
    -(messagefile t) greeting(string m) {
    -    app {
    -        echo m stdout=@filename(t);
    -    }
    -}
    -
    -mystruct out <simple_mapper;prefix="qux",suffix=".txt">;
    -
    -out.left = greeting("hello");
    -out.right = greeting("goodbye");
    -

    This will output the string "hello" into the file qux.left.txt and the -string "goodbye" into the file qux.right.txt.

    -
    - --- - - - - - - - - - - - - - - - -
    Swift variableFilename

    out.left

    quxleft.txt

    out.right

    quxright.txt

    -
    -
    -
    -

    3.3. concurrent mapper

    -

    concurrent_mapper is almost the same as the simple mapper, except that -it is used to map an output file, and the filename generated will -contain an extract sequence that is unique. This mapper is the default -mapper for variables when no mapper is specified.

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    ParameterMeaning

    location

    A directory that the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt" -pattern A UNIX glob style pattern, for instance: "foo" would match -all file names that contain foo. When this mapper is used to specify -output filenames, pattern is ignored.

    -
    -

    Example:

    -
    -
    -
    file f1;
    -file f2 <concurrent_mapper;prefix="foo", suffix=".txt">;
    -

    The above example would use concurrent mapper for f1 and f2, and -generate f2 filename with prefix "foo" and extension ".txt"

    -
    -
    -

    3.4. File system mapper

    -

    filesys_mapper is similar to the simple mapper, but maps a file or a -list of files to an array. Each of the filename is mapped as an element -in the array. The order of files in the resulting array is not defined.

    -

    TODO: note on difference between location as a relative vs absolute path -wrt staging to remote location - as mihael said: It’s because you -specify that location in the mapper. Try location="." instead of -location="/sandbox/…"

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - -
    parametermeaning

    location

    The directory where the files are located.

    prefix

    The prefix of the files

    suffix

    The suffix of the files, for instance: ".txt"

    pattern

    A UNIX glob style pattern, for instance: "foo" would match -all file names that contain foo.

    -
    -

    Example:

    -
    -
    -
    file texts[] <filesys_mapper;prefix="foo", suffix=".txt">;
    -

    The above example would map all filenames that start with "foo" and -have an extension ".txt" into the array texts. For example, if the -specified directory contains files: foo1.txt, footest.txt, -foo__1.txt, then the mapping might be:

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    texts[0]

    footest.txt

    texts[1]

    foo1.txt

    texts[2]

    foo__1.txt

    -
    -
    -
    -

    3.5. fixed array mapper

    -

    The fixed_array_mapper maps from a string that contains a list of -filenames into a file array.

    -
    - --- - - - - - - - - - - - -
    parameterMeaning

    files

    A string that contains a list of filenames, separated by space, -comma or colon

    -
    -

    Example:

    -
    -
    -
    file texts[] <fixed_array_mapper;files="file1.txt, fileB.txt, file3.txt">;
    -

    would cause a mapping like this:

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    texts[0]

    file1.txt

    texts[1]

    fileB.txt

    texts[2]

    file3.txt

    -
    -
    -
    -

    3.6. array mapper

    -

    The array_mapper maps from an array of strings into a file

    -
    - --- - - - - - - - - - - - -
    parametermeaning

    files

    An array of strings containing one filename per element

    -
    -

    Example:

    -
    -
    -
    string s[] = [ "a.txt", "b.txt", "c.txt" ];
    -
    -file f[] <array_mapper;files=s>;
    -

    This will establish the mapping:

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    f[0]

    a.txt

    f[1]

    b.txt

    f[2]

    c.txt

    -
    -
    -
    -

    3.7. regular expression mapper

    -

    The regexp_mapper transforms one file name to another using regular -expression matching.

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    parametermeaning

    source

    The source file name

    match

    Regular expression pattern to match, use

    ()

    to match whatever -regular expression is inside the parentheses, and indicate the start and -end of a group; the contents of a group can be retrieved with the

    \\number

    special sequence (two backslashes are needed because the -backslash is an escape sequence introducer)

    transform

    The pattern of the file name to transform to, use \number to -reference the group matched.

    -
    -

    Example:

    -
    -
    -
    string s = "picture.gif";
    -file f <regexp_mapper;
    -  source=s,
    -  match="(.*)gif",
    -  transform="\\1jpg">;
    -

    This example transforms a string ending gif into one ending jpg and -maps that to a file.

    -
    - --- - - - - - - - - - - - -
    Swift variableFilename

    f

    picture.jpg

    -
    -
    -
    -

    3.8. csv mapper

    -

    The csv_mapper maps the content of a CSV (comma-separated value) file -into an array of structures. The dataset type needs to be correctly -defined to conform to the column names in the file. For instance, if the -file contains columns: name age GPA then the type needs to have member -elements like this:

    -
    -
    -
    type student {
    -  file name;
    -  file age;
    -  file GPA;
    -}
    -

    If the file does not contain a header with column info, then the column -names are assumed as column1, column2, etc.

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ParameterMeaning

    file

    The name of the CSV file to read mappings from.

    header

    Whether the file has a line describing header info; default is

    true

    skip

    The number of lines to skip at the beginning (after header line); -default is 0.

    hdelim

    Header field delimiter; default is the value of the

    delim

    parameter

    delim

    Content field delimiters; defaults are space, tab and comma

    -
    -

    Example:

    -
    -
    -
    student stus[] <csv_mapper;file="stu_list.txt">;
    -

    The above example would read a list of student info from file -"stu_list.txt" and map them into a student array. By default, the file -should contain a header line specifying the names of the columns. If -stu_list.txt contains the following:

    -
    -
    -
    name,age,gpa
    -101-name.txt, 101-age.txt, 101-gpa.txt
    -name55.txt, age55.txt, age55.txt
    -q, r, s
    -

    then some of the mappings produced by this example would be:

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    stus[0].name101-name.txt

    stus[0].age

    101-age.txt

    stus[0].gpa

    101-gpa.txt

    stus[1].name

    name55.txt

    stus[1].age

    age55.txt

    stus[1].gpa

    gpa55.txt

    stus[2].name

    q

    stus[2].age

    r

    stus[2].gpa

    s

    -
    -
    -
    -

    3.9. external mapper

    -

    The external mapper, ext maps based on the output of a supplied Unix -executable.

    -
    - --- - - - - - - - - - - - - - -

    parameter

    meaning

    exec

    The name of the executable (relative to the current directory, if -an absolute path is not specified)

    *

    Other parameters are passed to the executable prefixed with a - symbol

    -
    -

    The output of the executable should consist of two columns of data, -separated by a space. The first column should be the path of the mapped -variable, in SwiftScript syntax (for example [2] means the 2nd element -of an array) or the symbol $ to represent the root of the mapped -variable.

    -

    Example: With the following in mapper.sh,

    -
    -
    -
    #!/bin/bash
    -echo "[2] qux"
    -echo "[0] foo"
    -echo "[1] bar"
    -

    then a mapping statement:

    -
    -
    -
    student stus[] <ext;exec="mapper.sh">;
    -

    would map

    -
    - --- - - - - - - - - - - - - - - - - - - - -
    Swift variableFilename

    stus[0]

    foo

    stus[1]

    bar

    stus[2]

    qux

    -
    -
    -
    -
    -
    -

    4. Commands

    -
    -

    The commands detailed in this section are available in the bin/ -directory of a Swift installation and can by run from the commandline if -that directory is placed on the PATH.

    -
    -

    4.1. swift

    -

    The swift command is the main command line tool for executing -SwiftScript programs.

    -
    -

    4.1.1. Command-line Syntax

    -

    The swift command is invoked as follows: swift [options] -SwiftScript-program [SwiftScript-arguments]* with options taken from the -following list, and SwiftScript-arguments made available to the -SwiftScript program through the @arg function.

    -

    Swift command-line options

    -

    -help or -h

    -
    -
    -
    Display usage information
    -
    -

    -typecheck

    -
    -
    -
    Does a typecheck of a SwiftScript program, instead of executing it.
    -
    -

    -dryrun

    -
    -
    -
    Runs the SwiftScript program without submitting any jobs (can be
    -used to get a graph)
    -
    -

    -monitor

    -
    -
    -
    Shows a graphical resource monitor
    -
    -

    -resume file

    -
    -
    -
    Resumes the execution using a log file
    -
    -

    -config file

    -
    -
    -
    Indicates the Swift configuration file to be used for this run.
    -Properties in this configuration file will override the default
    -properties. If individual command line arguments are used for
    -properties, they will override the contents of this file.
    -
    -

    -verbose | -v

    -
    -
    -
    Increases the level of output that Swift produces on the console to
    -include more detail about the execution
    -
    -

    -debug | -d

    -
    -
    -
    Increases the level of output that Swift produces on the console to
    -include lots of detail about the execution
    -
    -

    -logfile file

    -
    -
    -
    Specifies a file where log messages should go to. By default Swift
    -uses the name of the program being run and a numeric index (e.g.
    -myworkflow.1.log)
    -
    -

    -runid identifier

    -
    -
    -
    Specifies the run identifier. This must be unique for every
    -invocation and is used in several places to keep files from
    -different executions cleanly separated. By default, a datestamp and
    -random number are used to generate a run identifier. When using this
    -parameter, care should be taken to ensure that the run ID remains
    -unique with respect to all other run IDs that might be used,
    -irrespective of (at least) expected execution sites, program or user.
    -
    -

    -tui

    -
    -
    -
    Displays an interactive text mode monitor during a run. (since Swift
    -0.9)
    -
    -

    In addition, the following Swift properties can be set on the command line:

    -
      -
    • -

      -caching.algorithm -

      -
    • -
    • -

      -clustering.enabled -

      -
    • -
    • -

      -clustering.min.time -

      -
    • -
    • -

      -clustering.queue.delay -

      -
    • -
    • -

      -ip.address -

      -
    • -
    • -

      -kickstart.always.transfer -

      -
    • -
    • -

      -kickstart.enabled -

      -
    • -
    • -

      -lazy.errors -

      -
    • -
    • -

      -pgraph -

      -
    • -
    • -

      -pgraph.graph.options -

      -
    • -
    • -

      -pgraph.node.options -

      -
    • -
    • -

      -sitedir.keep -

      -
    • -
    • -

      -sites.file -

      -
    • -
    • -

      -tc.file -

      -
    • -
    • -

      -tcp.port.range -

      -
    • -
    -
    -
    -

    4.1.2. Return codes

    -

    The swift command may exit with the following return codes:

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    valuemeaning

    0

    success

    1

    command line syntax error or missing project name

    2

    error during execution

    3

    error during compilation

    4

    input file does not exist

    -
    -
    -
    -

    4.1.3. Environment variables

    -

    The swift is influenced by the following environment variables:

    -

    GLOBUS_HOSTNAME, GLOBUS_TCP_PORT_RANGE - set in the environment -before running Swift. These can be set to inform Swift of the -configuration of your local firewall. More information can be found in -the Globus firewall How-to http://dev.globus.org/wiki/FirewallHowTo.

    -

    COG_OPTS - set in the environment before running Swift. Options set in -this variable will be passed as parameters to the Java Virtual Machine -which will run Swift. The parameters vary between virtual machine -imlementations, but can usually be used to alter settings such as -maximum heap size. Typing java -help will sometimes give a list of -commands. The Sun Java 1.4.2 command line options are documented here -http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/java.html.

    -
    -
    -
    -

    4.2. swift-osg-ress-site-catalog

    -

    The swift-osg-ress-site-catalog command generates a site catalog based -on OSG http://www.opensciencegrid.org/'s ReSS information system -(since Swift 0.9)

    -

    Usage: swift-osg-ress-site-catalog [options]

    -

    --help

    -
    -
    -
    Show help message
    -
    -

    --vo=[name]

    -
    -
    -
    Set what VO to query ReSS for
    -
    -

    --engage-verified

    -
    -
    -
    Only retrieve sites verified by the Engagement VO site verification
    -tests This can not be used together with |--vo|, as the query will
    -only work for sites advertising support for the Engagement VO.
    -
    -
    -
    -
    This option means information will be retrieved from the Engagement
    -collector instead of the top-level ReSS collector.
    -
    -

    --out=[filename]

    -
    -
    -
    Write to [filename] instead of stdout
    -
    -

    --condor-g

    -
    -
    -
    Generates sites files which will submit jobs using a local Condor-G
    -installation rather than through direct GRAM2 submission. (since
    -Swift 0.10)
    -
    -
    -
    -

    4.3. swift-plot-log

    -

    swift-plot-log generates summaries of Swift run log files.

    -

    Usage: swift-plot-log [logfile] [targets]

    -

    When no targets are specified, swift-plog-log will generate an HTML -report for the run. When targets are specified, only those named targets -will be generated.

    -
    -
    -
    -
    -

    5. Executing app procedures

    -
    -

    This section describes how Swift executes app procedures, and -requirements on the behaviour of application programs used in app -procedures. These requirements are primarily to ensure that the Swift -can run your application in different places and with the various fault -tolerance mechanisms in place.

    -
    -

    5.1. Mapping of app semantics into unix process execution semantics

    -

    This section describes how an app procedure invocation is translated -into a (remote) unix process execution. It does not describe the -mechanisms by which Swift performs that translation; that is described -in the next section.

    -

    In this section, this example SwiftScript program is used for reference:

    -
    -
    -
    type file;
    -
    -app (file o) count(file i) {
    -  wc @i stdout=@o;
    -}
    -
    -file q <"input.txt">;
    -file r <"output.txt">;
    -

    The executable for wc will be looked up in tc.data.

    -

    This unix executable will then be executed in some application -procedure workspace. This means:

    -

    Each application procedure workspace will have an application workspace -directory. (TODO: can collapse terms application procedure workspace -and application workspace directory ?

    -

    This application workspace directory will not be shared with any other -application procedure execution attempt; all application procedure -execution attempts will run with distinct application procedure -workspaces. (for the avoidance of doubt: If a SwiftScript procedure -invocation is subject to multiple application procedure execution -attempts (due to Swift-level restarts, retries or replication) then each -of those application procedure execution attempts will be made in a -different application procedure workspace. )

    -

    The application workspace directory will be a directory on a POSIX -filesystem accessible throughout the application execution by the -application executable.

    -

    Before the application executable is executed:

    -
      -
    • -

      -The application workspace directory will exist. -

      -
    • -
    • -

      -The input files will exist inside the application workspace - directory (but not necessarily as direct children; there may be - subdirectories within the application workspace directory). -

      -
    • -
    • -

      -The input files will be those files mapped to input parameters - of the application procedure invocation. (In the example, this - means that the file input.txt will exist in the application - workspace directory) -

      -
    • -
    • -

      -For each input file dataset, it will be the case that @filename - or @filenames invoked with that dataset as a parameter will - return the path relative to the application workspace directory - for the file(s) that are associated with that dataset. (In the - example, that means that @i will evaluate to the path input.txt) -

      -
    • -
    • -

      -For each file-bound parameter of the Swift procedure invocation, - the associated files (determined by data type?) will always exist. -

      -
    • -
    • -

      -The input files must be treated as read only files. This may or - may not be enforced by unix file system permissions. They may or - may not be copies of the source file (conversely, they may be - links to the actual source file). -

      -
    • -
    -

    During/after the application executable execution, the following must -be true:

    -
      -
    • -

      -If the application executable execution was successful (in the - opinion of the application executable), then the application - executable should exit with unix return code 0; if the - application executable execution was unsuccessful (in the opinion - of the application executable), then the application executable - should exit with unix return code not equal to 0. -

      -
    • -
    • -

      -Each file mapped from an output parameter of the SwiftScript - procedure call must exist. Files will be mapped in the same way as - for input files. -

      -
      -
      -
      (? Is it defined that output subdirectories will be precreated
      -before execution or should app executables expect to make them?
      -That's probably determined by the present behaviour of wrapper.sh)
      -
      -
    • -
    • -

      -Output produced by running the application executable on some - inputs should be the same no matter how many times, when or where - that application executable is run. The same can vary depending - on application (for example, in an application it might be - acceptable for a PNG→JPEG conversion to produce different, - similar looking, output jpegs depending on the environment) -

      -
    • -
    -

    Things to not assume:

    -
      -
    • -

      -anything about the path of the application workspace directory -

      -
    • -
    • -

      -that either the application workspace directory will be deleted or - will continue to exist or will remain unmodified after execution - has finished -

      -
    • -
    • -

      -that files can be passed(?def) between application procedure - invocations through any mechanism except through files known to - Swift through the mapping mechanism (there is some exception here - for external datasets - there are a separate set of assertions - that hold for external datasets) -

      -
    • -
    • -

      -that application executables will run on any particular site of - those available, or than any combination of applications will run - on the same or different sites. -

      -
    • -
    -
    -
    -

    5.2. How Swift implements the site execution model

    -

    This section describes the implementation of the semantics described in -the previous section.

    -

    Swift executes application procedures on one or more sites.

    -

    Each site consists of:

    -
      -
    • -

      -worker nodes. There is some execution mechanism through which - the Swift client side executable can execute its wrapper script - on those worker nodes. This is commonly GRAM or Falkon or coasters. -

      -
    • -
    • -

      -a site-shared file system. This site shared filesystem is - accessible through some file transfer mechanism from the Swift - client side executable. This is commonly GridFTP or coasters. This - site shared filesystem is also accessible through the posix file - system on all worker nodes, mounted at the same location as seen - through the file transfer mechanism. Swift is configured with the - location of some site working directory on that site-shared file - system. -

      -
    • -
    -

    There is no assumption that the site shared file system for one site is -accessible from another site.

    -

    For each workflow run, on each site that is used by that run, a run -directory is created in the site working directory, by the Swift client -side.

    -

    In that run directory are placed several subdirectories:

    -
      -
    • -

      -shared/ - site shared files cache -

      -
    • -
    • -

      -kickstart/ - when kickstart is used, kickstart record files for - each job that has generated a kickstart record. -

      -
    • -
    • -

      -info/ - wrapper script log files -

      -
    • -
    • -

      -status/ - job status files -

      -
    • -
    • -

      -jobs/ - application workspace directories (optionally placed - here - see below) -

      -
    • -
    -

    Application execution looks like this:

    -

    For each application procedure call:

    -

    The Swift client side selects a site; copies the input files for that -procedure call to the site shared file cache if they are not already in -the cache, using the file transfer mechanism; and then invokes the -wrapper script on that site using the execution mechanism.

    -

    The wrapper script creates the application workspace directory; places -the input files for that job into the application workspace directory -using either cp or ln -s (depending on a configuration option); -executes the application unix executable; copies output files from the -application workspace directory to the site shared directory using cp; -creates a status file under the status/ directory; and exits, -returning control to the Swift client side. Logs created during the -execution of the wrapper script are stored under the info/ directory.

    -

    The Swift client side then checks for the presence of and deletes a -status file indicating success; and copies files from the site shared -directory to the appropriate client side location.

    -

    The job directory is created (in the default mode) under the jobs/ -directory. However, it can be created under an arbitrary other path, -which allows it to be created on a different file system (such as a -worker node local file system in the case that the worker node has a -local file system).

    -

    -swift-site-model.png -

    -
    -
    -
    -
    -

    6. Technical overview of the Swift architecture

    -
    -

    This section attempts to provide a technical overview of the Swift -architecture.

    -
    -

    6.1. Execution layer

    -

    The execution layer causes an application program (in the form of a unix -executable) to be executed either locally or remotely.

    -

    The two main choices are local unix execution and execution through -GRAM. Other options are available, and user provided code can also be -plugged in.

    -

    The kickstart utility can be used to capture environmental -information at execution time to aid in debugging and provenance capture.

    -
    -
    -

    6.2. SwiftScript language compilation layer

    -

    Step i: text to XML intermediate form parser/processor. parser written -in ANTLR - see resources/VDL.g. The XML Schema Definition (XSD) for the -intermediate language is in resources/XDTM.xsd.

    -

    Step ii: XML intermediate form to Karajan workflow. Karajan.java - reads -the XML intermediate form. compiles to karajan workflow language - for -example, expressions are converted from SwiftScript syntax into Karajan -syntax, and function invocations become karajan function invocations -with various modifications to parameters to accomodate return parameters -and dataset handling.

    -
    -
    -

    6.3. Swift/karajan library layer

    -

    Some Swift functionality is provided in the form of Karajan libraries -that are used at runtime by the Karajan workflows that the Swift -compiler generates.

    -
    -
    -
    -
    -

    7. Ways in which Swift can be extended

    -
    -

    Swift is extensible in a number of ways. It is possible to add mappers -to accomodate different filesystem arrangements, site selectors to -change how Swift decides where to run each job, and job submission -interfaces to submit jobs through different mechanisms.

    -

    A number of mappers are provided as part of the Swift release and -documented in the mappers section. New mappers can be -implemented in Java by implementing the org.griphyn.vdl.mapping.Mapper -interface. The Swift tutorial -http://www.ci.uchicago.edu/swift/guides/tutorial.php contains a simple -example of this.

    -

    Swift provides a default site selector, the Adaptive Scheduler. New site -selectors can be plugged in by implementing the -org.globus.cog.karajan.scheduler.Scheduler interface and modifying -libexec/scheduler.xml and etc/karajan.properties to refer to the new -scheduler.

    -

    Execution providers and filesystem providers, which allow to Swift to -execute jobs and to stage files in and out through mechanisms such as -GRAM and GridFTP can be implemented as Java CoG kit providers.

    -
    -
    -
    -

    8. Function reference

    -
    -

    This section details functions that are available for use in the -SwiftScript language.

    -
    -

    8.1. @arg

    -

    Takes a command line parameter name as a string parameter and an -optional default value and returns the value of that string parameter -from the command line. If no default value is specified and the command -line parameter is missing, an error is generated. If a default value is -specified and the command line parameter is missing, @arg will return -the default value.

    -

    Command line parameters recognized by @arg begin with exactly one -hyphen and need to be positioned after the script name.

    -

    For example:

    -
    -
    -
    trace(@arg("myparam"));
    -trace(@arg("optionalparam", "defaultvalue"));
    -
    -
    -
    $ swift arg.swift -myparam=hello
    -Swift v0.3-dev r1674 (modified locally)
    -
    -RunID: 20080220-1548-ylc4pmda
    -SwiftScript trace: defaultvalue
    -SwiftScript trace: hello
    -
    -
    -

    8.2. @extractint

    -

    @extractint(file) will read the specified file, parse an integer from -the file contents and return that integer.

    -
    -
    -

    8.3. @filename

    -

    @filename(v) will return a string containing the filename(s) for the -file(s) mapped to the variable v. When more than one filename is -returned, the filenames will be space separated inside a single string -return value.

    -
    -
    -

    8.4. @filenames

    -

    @filenames(v) will return multiple values (!) containing the -filename(s) for the file(s) mapped to the variable v. (compare to - at filename)

    -
    -
    -

    8.5. @regexp

    -

    @regexp(input,pattern,replacement) will apply regular expression -substitution using the Java java.util.regexp API -http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html. -For example:

    -
    -
    -
    string v =  @regexp("abcdefghi", "c(def)g","monkey");
    -

    will assign the value "abmonkeyhi" to the variable v.

    -
    -
    -

    8.6. @strcat

    -

    @strcat(a,b,c,d,…) will return a string containing all of the -strings passed as parameters joined into a single string. There may be -any number of parameters.

    -

    The + operator concatenates two strings: @strcat(a,b) is the same as -a + b

    -
    -
    -

    8.7. @strcut

    -

    @strcut(input,pattern) will match the regular expression in the -pattern parameter against the supplied input string and return the -section that matches the first matching parenthesised group.

    -

    For example:

    -
    -
    -
    string t = "my name is John and i like puppies.";
    -string name = @strcut(t, "my name is ([^ ]*) ");
    -string out = @strcat("Your name is ",name);
    -trace(out);
    -

    will output the message: Your name is John.

    -
    -
    -

    8.8. @strsplit

    -

    @strsplit(input,pattern) will split the input string based on -separators that match the given pattern and return a string array. -(since Swift 0.9)

    -

    Example:

    -
    -
    -
    string t = "my name is John and i like puppies.";
    -string words[] = @strsplit(t, "\\s");
    -foreach word in words {
    -    trace(word);
    -}
    -

    will output one word of the sentence on each line (though not -necessarily in order, due to the fact that foreach iterations execute in -parallel).

    -
    -
    -

    8.9. @toint

    -

    @toint(input) will parse its input string into an integer. This can be -used with @arg to pass input parameters to a SwiftScript program as -integers.

    -
    -
    -
    -
    -

    9. Built-in procedure reference

    -
    -

    This section details built-in procedures that are available for use in -the SwiftScript language.

    -
    -

    9.1. readData

    -

    readData will read data from a specified file.

    -

    The format of the input file is controlled by the type of the return value.

    -

    For scalar return types, such as int, the specified file should contain -a single value of that type.

    -

    For arrays of scalars, the specified file should contain one value per -line.

    -

    For structs of scalars, the file should contain two rows. The first row -should be structure member names separated by whitespace. The second row -should be the corresponding values for each structure member, separated -by whitespace, in the same order as the header row.

    -

    For arrays of structs, the file should contain a heading row listing -structure member names separated by whitespace. There should be one row -for each element of the array, with structure member elements listed in -the same order as the header row and separated by whitespace. (since -Swift 0.4)

    -
    -
    -

    9.2. readdata2

    -

    readdata2 will read data from a specified file, like readdata, but -using a different file format more closely related to that used by the -ext mapper.

    -

    Input files should list, one per line, a path into a Swift structure, -and the value for that position in the structure:

    -
    -
    -
    rows[0].columns[0] = 0
    -rows[0].columns[1] = 2
    -rows[0].columns[2] = 4
    -rows[1].columns[0] = 1
    -rows[1].columns[1] = 3
    -rows[1].columns[2] = 5
    -

    which can be read into a structure defined like this:

    -
    -
    -
    type vector {
    -        int columns[];
    -}
    -
    -type matrix {
    -        vector rows[];
    -}
    -
    -matrix m;
    -
    -m = readData2("readData2.in");
    -

    (since Swift 0.7)

    -
    -
    -

    9.3. trace

    -

    trace will log its parameters. By default these will appear on both -stdout and in the run log file. Some formatting occurs to produce the -log message. The particular output format should not be relied upon. -(since Swift 0.4)

    -
    -
    -

    9.4. writeData

    -

    writeData will write out data structures in the format described for -readData

    -
    -
    -
    -
    -

    10. Swift configuration properties

    -
    -

    Various aspects of the behavior of the Swift Engine can be configured -through properties. The Swift Engine recognizes a global, per -installation properties file which can found in etc/swift.properties -in the Swift installation directory and a user properties file which can -be created by each user in ~/.swift/swift.properties. The Swift Engine -will first load the global properties file. It will then try to load the -user properties file. If a user properties file is found, individual -properties explicitly set in that file will override the respective -properties in the global properties file. Furthermore, some of the -properties can be overridden directly using command line arguments to -the swift command.

    -

    Swift properties are specified in the following format:

    -

    <name>=<value>

    -

    The value can contain variables which will be expanded when the -properties file is read. Expansion is performed when the name of the -variable is used inside the standard shell dereference construct: -configuration file:

    -

    Swift Configuration Variables

    -

    swift.home

    -
    -
    -
    Points to the Swift installation directory ($SWIFT_HOME). In
    -general, this should not be set as Swift can find its own
    -installation directory, and incorrectly setting it may impair the
    -correct functionality of Swift.
    -
    -

    user.name

    -
    -
    -
    The name of the current logged in user.
    -
    -

    user.home

    -
    -
    -
    The user's home directory.
    -
    -

    The following is a list of valid Swift properties:

    -

    Swift Properties

    -

    caching.algorithm

    -
    -
    -
    Valid values: LRU
    -
    -
    -
    -
    Default value: LRU
    -
    -
    -
    -
    Swift caches files that are staged in on remote resources, and files
    -that are produced remotely by applications, such that they can be
    -re-used if needed without being transfered again. However, the
    -amount of remote file system space to be used for caching can be
    -limited using the swift:storagesize profile entry in the sites.xml file. Example:
    -
    -
    -
    -
    <pool handle="example" sysinfo="INTEL32::LINUX">
    -<gridftp url="gsiftp://example.org" storage="/scratch/swift" major="2" minor="4" patch="3"/>
    -<jobmanager universe="vanilla" url="example.org/jobmanager-pbs" major="2" minor="4" patch="3"/>
    -<workdirectory>/scratch/swift</workdirectory>
    -<profile namespace="SWIFT" key="storagesize">20000000</profile>
    -</pool>
    -
    -
    -
    The decision of which files to keep in the cache and which files to
    -remove is made considering the value of the caching.algorithm
    -property. Currently, the only available value for this property is
    -LRU, which would cause the least recently used files to be deleted
    -first.
    -
    -

    clustering.enabled

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    Enables clustering.
    -
    -

    clustering.min.time

    -
    -
    -
    Valid values: <int>
    -
    -
    -
    -
    Default value: 60
    -
    -
    -
    -
    Indicates the threshold wall time for clustering, in seconds. Jobs
    -that have a wall time smaller than the value of this property will
    -be considered for clustering.
    -
    -

    clustering.queue.delay

    -
    -
    -
    Valid values: <int>
    -
    -
    -
    -
    Default value: 4
    -
    -
    -
    -
    This property indicates the interval, in seconds, at which the
    -clustering queue is processed.
    -
    -

    execution.retries

    -
    -
    -
    Valid values: positive integers
    -
    -
    -
    -
    Default value: 2
    -
    -
    -
    -
    The number of time a job will be retried if it fails (giving a
    -maximum of 1 + execution.retries attempts at execution)
    -
    -

    foreach.max.threads

    -
    -
    -
    Valid values: positive integers
    -
    -
    -
    -
    Default value: 1024
    -
    -
    -
    -
    Limits the number of concurrent iterations that each foreach
    -statement can have at one time. This conserves memory for swift
    -programs that have large numbers of iterations (which would
    -otherwise all be executed in parallel). (since Swift 0.9)
    -
    -

    ip.address

    -
    -
    -
    Valid values: <ipaddress>
    -
    -
    -
    -
    Default value: N/A
    -
    -
    -
    -
    The Globus GRAM service uses a callback mechanism to send
    -notifications about the status of submitted jobs. The callback
    -mechanism requires that the Swift client be reachable from the hosts
    -the GRAM services are running on. Normally, Swift can detect the
    -correct IP address of the client machine. However, in certain cases
    -(such as the client machine having more than one network interface)
    -the automatic detection mechanism is not reliable. In such cases,
    -the IP address of the Swift client machine can be specified using
    -this property. The value of this property must be a numeric address
    -without quotes.
    -
    -
    -
    -
    This option is deprecated and the hostname property should be used
    -instead.
    -
    -

    kickstart.always.transfer

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    This property controls when output from Kickstart is transfered back
    -to the submit site, if Kickstart is enabled. When set to false,
    -Kickstart output is only transfered for jobs that fail. If set to
    -true, Kickstart output is transfered after every job is completed
    -or failed.
    -
    -

    kickstart.enabled

    -
    -
    -
    Valid values: true, false, maybe
    -
    -
    -
    -
    Default value: maybe
    -
    -
    -
    -
    This option allows controlling of when Swift uses Kickstart.
    -A value of false disables the use of Kickstart,
    -while a value of true enables the use of Kickstart, in which case
    -sites specified in the sites.xml file must have valid
    -gridlaunch attributes. The maybe value will enable the use of
    -Kickstart only on sites that have the gridlaunch attribute
    -specified.
    -
    -

    lazy.errors

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    Swift can report application errors in two modes, depending on the
    -value of this property. If set to false, Swift will report the
    -first error encountered and immediately stop execution. If set to
    -true, Swift will attempt to run as much as possible from a
    -SwiftScript program before stopping execution and reporting all
    -errors encountered.
    -
    -
    -
    -
    When developing SwiftScript programs, using the default value of
    -false can make the program easier to debug. However in production
    -runs, using true will allow more of a SwiftScript program to be
    -run before Swift aborts execution.
    -
    -

    pgraph

    -
    -
    -
    Valid values: true, false, <file>
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    Swift can generate a Graphviz <http://www.graphviz.org/> file
    -representing the structure of the SwiftScript program it has run. If
    -this property is set to true, Swift will save the provenance graph
    -in a file named by concatenating the program name and the instance
    -ID (e.g. helloworld-ht0adgi315l61.dot).
    -
    -
    -
    -
    If set to false, no provenance graph will be generated. If a file
    -name is used, then the provenance graph will be saved in the
    -specified file.
    -
    -
    -
    -
    The generated dot file can be rendered into a graphical form using
    -Graphviz <http://www.graphviz.org/>, for example with a command-line
    -such as:
    -
    -
    -
    -
    $ swift -pgraph graph1.dot q1.swift
    -$ dot -ograph.png -Tpng graph1.dot
    -

    pgraph.graph.options

    -
    -
    -
    Valid values: <string>
    -
    -
    -
    -
    Default value: splines="compound", rankdir="TB"
    -
    -
    -
    -
    This property specifies a Graphviz <http://www.graphviz.org>
    -specific set of parameters for the graph.
    -
    -

    pgraph.node.options

    -
    -
    -
    Valid values: <string>
    -
    -
    -
    -
    Default value: color="seagreen", style="filled"
    -
    -
    -
    -
    Used to specify a set of Graphviz <http://www.graphviz.org> specific
    -properties for the nodes in the graph.
    -
    -

    provenance.log

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    This property controls whether the log file will contain provenance
    -information enabling this will increase the size of log files,
    -sometimes significantly.
    -
    -

    replication.enabled

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    Enables/disables replication. Replication is used to deal with jobs
    -sitting in batch queues for abnormally large amounts of time. If
    -replication is enabled and certain conditions are met, Swift creates
    -and submits replicas of jobs, and allows multiple instances of a job
    -to compete.
    -
    -

    replication.limit

    -
    -
    -
    Valid values: positive integers
    -
    -
    -
    -
    Default value: 3
    -
    -
    -
    -
    The maximum number of replicas that Swift should attempt.
    -
    -

    sitedir.keep

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    Indicates whether the working directory on the remote site should be
    -left intact even when a run completes successfully. This can be used
    -to inspect the site working directory for debugging purposes.
    -
    -

    sites.file

    -
    -
    -
    Valid values: <file>
    -
    -
    -
    -
    Default value: ${swift.home}/etc/sites.xml
    -
    -
    -
    -
    Points to the location of the site catalog, which contains a list of
    -all sites that Swift should use.
    -
    -

    status.mode

    -
    -
    -
    Valid values: files, provider
    -
    -
    -
    -
    Default value: files
    -
    -
    -
    -
    Controls how Swift will communicate the result code of running user
    -programs from workers to the submit side. In files mode, a file
    -indicating success or failure will be created on the site shared
    -filesystem. In provider mode, the execution provider job status
    -will be used.
    -
    -
    -
    -
    provider mode requires the underlying job execution system to
    -correctly return exit codes. In at least the cases of GRAM2, and
    -clusters used with any provider, exit codes are not returned, and so
    -files mode must be used in those cases. Otherwise, provider mode
    -can be used to reduce the amount of filesystem access. (since Swift
    -0.8)
    -
    -

    tc.file

    -
    -
    -
    Valid values: <file>
    -
    -
    -
    -
    Default value: ${swift.home}/etc/tc.data
    -
    -
    -
    -
    Points to the location of the transformation catalog file which
    -contains information about installed applications. Details about the
    -format of the transformation catalog can be found here
    -<http://vds.uchicago.edu/vds/doc/userguide/html/H_TransformationCatalog.html>.
    -
    -

    tcp.port.range

    -
    -
    -
    Valid values: <start>,<end> where start and end are integers
    -
    -
    -
    -
    Default value: none
    -
    -
    -
    -
    A TCP port range can be specified to restrict the ports on which
    -GRAM callback services are started. This is likely needed if your
    -submit host is behind a firewall, in which case the firewall should
    -be configured to allow incoming connections on ports in the range.
    -
    -

    throttle.file.operations

    -
    -
    -
    Valid values: <int>, off
    -
    -
    -
    -
    Default value: 8
    -
    -
    -
    -
    Limits the total number of concurrent file operations that can
    -happen at any given time. File operations (like transfers) require
    -an exclusive connection to a site. These connections can be
    -expensive to establish. A large number of concurrent file operations
    -may cause Swift to attempt to establish many such expensive
    -connections to various sites. Limiting the number of concurrent file
    -operations causes Swift to use a small number of cached connections
    -and achieve better overall performance.
    -
    -

    throttle.host.submit

    -
    -
    -
    Valid values: <int>, off
    -
    -
    -
    -
    Default value: 2
    -
    -
    -
    -
    Limits the number of concurrent submissions for any of the sites
    -Swift will try to send jobs to. In other words it guarantees that no
    -more than the value of this throttle jobs sent to any site will be
    -concurrently in a state of being submitted.
    -
    -

    throttle.score.job.factor

    -
    -
    -
    Valid values: <int>, off
    -
    -
    -
    -
    Default value: 4
    -
    -
    -
    -
    The Swift scheduler has the ability to limit the number of
    -concurrent jobs allowed on a site based on the performance history
    -of that site. Each site is assigned a score (initially 1), which can
    -increase or decrease based on whether the site yields successful or
    -faulty job runs. The score for a site can take values in the (0.1,
    -100) interval. The number of allowed jobs is calculated using the
    -following formula:
    -
    -
    -
    -
    2 + score*throttle.score.job.factor
    -
    -
    -
    -
    This means a site will always be allowed at least two concurrent
    -jobs and at most 2 + 100*throttle.score.job.factor. With a default
    -of 4 this means at least 2 jobs and at most 402.
    -
    -
    -
    -
    This parameter can also be set per site using the jobThrottle
    -profile key in a site catalog entry.
    -
    -

    throttle.submit

    -
    -
    -
    Valid values: <int>, off
    -
    -
    -
    -
    Default value: 4
    -
    -
    -
    -
    Limits the number of concurrent submissions for a run. This throttle
    -only limits the number of concurrent tasks (jobs) that are being
    -sent to sites, not the total number of concurrent jobs that can be
    -run. The submission stage in GRAM is one of the most CPU expensive
    -stages (due mostly to the mutual authentication and delegation).
    -Having too many concurrent submissions can overload either or both
    -the submit host CPU and the remote host/head node causing degraded
    -performance.
    -
    -

    throttle.transfers

    -
    -
    -
    Valid values: <int>, off
    -
    -
    -
    -
    Default value: 4
    -
    -
    -
    -
    Limits the total number of concurrent file transfers that can happen
    -at any given time. File transfers consume bandwidth. Too many
    -concurrent transfers can cause the network to be overloaded
    -preventing various other signaling traffic from flowing properly.
    -
    -

    ticker.disable

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    When set to true, suppresses the output progress ticker that Swift
    -sends to the console every few seconds during a run (since Swift 0.9)
    -
    -

    wrapper.invocation.mode

    -
    -
    -
    Valid values: absolute, relative
    -
    -
    -
    -
    Default value: absolute
    -
    -
    -
    -
    Determines if Swift remote wrappers will be executed by specifying
    -an absolute path, or a path relative to the job initial working
    -directory. In most cases, execution will be successful with either
    -option. However, some execution sites ignore the specified initial
    -working directory, and so absolute must be used. Conversely on
    -some sites, job directories appear in a different place on the
    -worker node file system than on the filesystem access node, with the
    -execution system handling translation of the job initial working
    -directory. In such cases, relative mode must be used. (since Swift
    -0.9)
    -
    -

    wrapper.parameter.mode

    -
    -
    -
    Controls how Swift will supply parameters to the remote wrapper
    -script. args mode will pass parameters on the command line. Some
    -execution systems do not pass commandline parameters sufficiently
    -cleanly for Swift to operate correctly. files mode will pass
    -parameters through an additional input file (since Swift 0.95). This
    -provides a cleaner communication channel for parameters, at the
    -expense of transferring an additional file for each job invocation.
    -
    -

    wrapperlog.always.transfer

    -
    -
    -
    Valid values: true, false
    -
    -
    -
    -
    Default value: false
    -
    -
    -
    -
    This property controls when output from the Swift remote wrapper is
    -transfered back to the submit site. When set to false, wrapper
    -logs are only transfered for jobs that fail. If set to true,
    -wrapper logs are transfered after every job is completed or failed.
    -
    -

    Example:

    -
    -
    -
    sites.file=${vds.home}/etc/sites.xml
    -tc.file=${vds.home}/etc/tc.data
    -ip.address=192.168.0.1
    -
    -
    -
    -

    11. Profiles

    -
    -

    Profiles are configuration parameters than can be specified either for -sites or for transformation catalog entries. They influence the -behaviour of Swift towards that site (for example, by changing the load -Swift will place on that sites) or when running a particular procedure.

    -

    Profile entries for a site are specified in the site catalog. Profile -entries for specific procedures are specified in the transformation -catalog.

    -
    -

    11.1. Karajan namespace

    -

    maxSubmitRate limits the maximum rate of job submission, in jobs per -second. For example:

    -
    -
    -
    <profile namespace="karajan" key="maxSubmitRate">0.2</profile>
    -

    will limit job submission to 0.2 jobs per second (or equivalently, one -job every five seconds).

    -

    jobThrottle allows the job throttle factor (see Swift property -throttle.score.job.factor to be -set per site.

    -

    initialScore allows the initial score for rate limiting and site -selection to be set to a value other than 0.

    -

    delayBase controls how much a site will be delayed when it performs -poorly. With each reduction in a sites score by 1, the delay between -execution attempts will increase by a factor of delayBase.

    -

    status.mode allows the status.mode property to be set per-site instead -of for an entire run. See the Swift configuration properties section for -more information. (since Swift 0.8)

    -
    -
    -

    11.2. swift namespace

    -

    storagesize limits the amount of space that will be used on the remote -site for temporary files. When more than that amount of space is used, -the remote temporary file cache will be cleared using the algorithm -specified in the caching.algorithm property.

    -

    wrapperInterpreter - The wrapper interpreter indicates the command -(executable) to be used to run the Swift wrapper script. The default is -"/bin/bash" on Unix sites and "cscript.exe" on Windows sites.

    -

    wrapperInterpreterOptions - Allows specifying additional options to the -executable used to run the Swift wrapper. The defaults are no options on -Unix sites and "Nologo" on Windows sites.

    -

    wrapperScript - Specifies the name of the wrapper script to be used on a -site. The defaults are "_swiftwrap" on Unix sites and "_swiftwrap.vbs" -on Windows sites. If you specify a custom wrapper script, it must be -present in the "libexec" directory of the Swift installation.

    -

    cleanupCommand Indicates the command to be run at the end of a Swift -run to clean up the run directories on a remote site. Defaults are -"/bin/rm" on Unix sites and "cmd.exe" on Windows sites

    -

    cleanupCommandOptions Specifies the options to be passed to the -cleanup command above. The options are passed in the argument list to -the cleanup command. After the options, the last argument is the -directory to be deleted. The default on Unix sites is "-rf". The default -on Windows sites is ["/C", "del", "/Q"].

    -
    -
    -

    11.3. Globus namespace

    -

    maxwalltime specifies a walltime limit for each job, in minutes.

    -

    The following formats are recognized:

    -
      -
    • -

      -Minutes -

      -
    • -
    • -

      -Hours:Minutes -

      -
    • -
    • -

      -Hours:Minutes:Seconds -

      -
    • -
    -

    Example:

    -
    -
    -
    localhost       echo    /bin/echo       INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="00:20:00"
    -

    When replication is enabled (see replication), then -walltime will also be enforced at the Swift client side: when a job has -been active for more than twice the maxwalltime, Swift will kill the job -and regard it as failed.

    -

    When clustering is used, maxwalltime will be used to select which jobs -will be clustered together. More information on this is available in the -clustering section.

    -

    When coasters as used, maxwalltime influences the default coaster -worker maxwalltime, and which jobs will be sent to which workers. More -information on this is available in the coasters section.

    -

    queue is used by the PBS, GRAM2 and GRAM4 providers. This profile -entry specifies which queue jobs will be submitted to. The valid queue -names are site-specific.

    -

    host_types specifies the types of host that are permissible for a job -to run on. The valid values are site-specific. This profile entry is -used by the GRAM2 and GRAM4 providers.

    -

    condor_requirements allows a requirements string to be specified when -Condor is used as an LRM behind GRAM2. Example:

    -
    -
    -
    <profile
    -namespace="globus" key="condor_requirements">Arch == "X86_64" || Arch="INTEL"</profile>
    -

    slots When using coasters, this parameter specifies the -maximum number of jobs/blocks that the coaster scheduler will have -running at any given time. The default is 20.

    -

    workersPerNode - This parameter determines how many coaster workers are -started one each compute node. The default value is 1.

    -

    nodeGranularity - When allocating a coaster worker block, this parameter -restricts the number of nodes in a block to a multiple of this value. -The total number of workers will then be a multiple of workersPerNode * -nodeGranularity. The default value is 1.

    -

    allocationStepSize - Each time the coaster block scheduler computes a -schedule, it will attempt to allocate a number of slots from the number -of available slots (limited using the above slots profile). This -parameter specifies the maximum fraction of slots that are allocated in -one schedule. Default is 0.1.

    -

    lowOverallocation - Overallocation is a function of the walltime of a -job which determines how long (time-wise) a worker job will be. For -example, if a number of 10s jobs are submitted to the coaster service, -and the overallocation for 10s jobs is 10, the coaster scheduler will -attempt to start worker jobs that have a walltime of 100s. The -overallocation is controlled by manipulating the end-points of an -overallocation function. The low endpoint, specified by this parameter, -is the overallocation for a 1s job. The high endpoint is the -overallocation for a (theoretical) job of infinite length. The -overallocation for job sizes in the [1s, +inf) interval is determined -using an exponential decay function: overallocation(walltime) = walltime -* (lowOverallocation - highOverallocation) * exp(-walltime * -overallocationDecayFactor) + highOverallocation The default value of -lowOverallocation is 10.

    -

    highOverallocation - The high overallocation endpoint (as described -above). Default: 1

    -

    overallocationDecayFactor - The decay factor for the overallocation -curve. Default 0.001 (1e-3).

    -

    spread - When a large number of jobs is submitted to the a coaster -service, the work is divided into blocks. This parameter allows a rough -control of the relative sizes of those blocks. A value of 0 indicates -that all work should be divided equally between the blocks (and blocks -will therefore have equal sizes). A value of 1 indicates the largest -possible spread. The existence of the spread parameter is based on the -assumption that smaller overall jobs will generally spend less time in -the queue than larger jobs. By submitting blocks of different sizes, -submitted jobs may be finished quicker by smaller blocks. Default: 0.9.

    -

    reserve - Reserve time is a time in the allocation of a worker that sits -at the end of the worker time and is useable only for critical -operations. For example, a job will not be submitted to a worker if it -overlaps its reserve time, but a job that (due to inaccurate walltime -specification) runs into the reserve time will not be killed (note that -once the worker exceeds its walltime, the queuing system will kill the -job anyway). Default 10 (s).

    -

    maxnodes - Determines the maximum number of nodes that can be allocated -in one coaster block. Default: unlimited.

    -

    maxtime - Indicates the maximum walltime that a coaster block can have. -Default: unlimited.

    -

    remoteMonitorEnabled - If set to "true", the client side will get a -Swing window showing, graphically, the state of the coaster scheduler -(blocks, jobs, etc.). Default: false

    -
    -
    -

    11.4. env namespace

    -

    Profile keys set in the env namespace will be set in the unix -environment of the executed job. Some environment variables influence -the worker-side behaviour of Swift:

    -

    PATHPREFIX - set in env namespace profiles. This path is prefixed onto -the start of the PATH when jobs are executed. It can be more useful -than setting the PATH environment variable directly, because setting -PATH will cause the execution site’s default path to be lost.

    -

    SWIFT_JOBDIR_PATH - set in env namespace profiles. If set, then Swift -will use the path specified here as a worker-node local temporary -directory to copy input files to before running a job. If unset, Swift -will keep input files on the site-shared filesystem. In some cases, -copying to a worker-node local directory can be much faster than having -applications access the site-shared filesystem directly.

    -

    SWIFT_EXTRA_INFO - set in env namespace profiles. If set, then Swift -will execute the command specified in SWIFT_EXTRA_INFO on execution -sites immediately before each application execution, and will record the -stdout of that command in the wrapper info log file for that job. This -is intended to allow software version and other arbitrary information -about the remote site to be gathered and returned to the submit side. -(since Swift 0.9)

    -
    -
    -
    -
    -

    12. The Site Catalog - sites.xml

    -
    -

    The site catalog lists details of each site that Swift can use. The -default file contains one entry for local execution, and a large number -of commented-out example entries for other sites.

    -

    By default, the site catalog is stored in etc/sites.xml. This path can -be overridden with the sites.file configuration property, either in -the Swift configuration file or on the command line.

    -

    The sites file is formatted as XML. It consists of <pool> elements, -one for each site that Swift will use.

    -
    -

    12.1. Pool element

    -

    Each pool element must have a handle attribute, giving a symbolic -name for the site. This can be any name, but must correspond to entries -for that site in the transformation catalog.

    -

    Optionally, the gridlaunch attribute can be used to specify the path -to kickstart on the site.

    -

    Each pool must specify a file transfer method, an execution method and -a remote working directory. Optionally, profile settings can -be specified.

    -
    -
    -

    12.2. File transfer method

    -

    Transfer methods are specified with either the <gridftp> element or -the <filesystem> element.

    -

    To use gridftp or local filesystem copy, use the <gridftp> element:

    -
    -
    -
    <gridftp  url="gsiftp://evitable.ci.uchicago.edu" />
    -

    The url attribute may specify a GridFTP server, using the gsiftp URI -scheme; or it may specify that filesystem copying will be used (which -assumes that the site has access to the same filesystem as the -submitting machine) using the URI local://localhost.

    -

    Filesystem access using scp (the SSH copy protocol) can be specified -using the <filesystem> element:

    -
    -
    -
    <filesystem url="www11.i2u2.org" provider="ssh"/>
    -

    For additional ssh configuration information, see the ssh execution -provider documentation below.

    -

    Filesystem access using CoG coasters can be also be -specified using the <filesystem> element. More detail about -configuring that can be found in the CoG coasters section.

    -
    -
    -

    12.3. Execution method

    -

    Execution methods may be specified either with the <jobmanager> or -<execution> element.

    -

    The <jobmanager> element can be used to specify execution through -GRAM2. For example,

    -
    -
    -
    <jobmanager universe="vanilla" url="evitable.ci.uchicago.edu/jobmanager-fork" major="2" />
    -

    The universe attribute should always be set to vanilla. The url -attribute should specify the name of the GRAM2 gatekeeper host, and the -name of the jobmanager to use. The major attribute should always be set -to 2.

    -

    The <execution> element can be used to specify execution through other -execution providers:

    -

    To use GRAM4, specify the gt4 provider. For example:

    -
    -
    -
    <execution provider="gt4" jobmanager="PBS" url="tg-grid.uc.teragrid.org" />
    -

    The url attribute should specify the GRAM4 submission site. The -jobmanager attribute should specify which GRAM4 jobmanager will be used.

    -

    For local execution, the local provider should be used, like this:

    -
    -
    -
    <execution provider="local" url="none" />
    -

    For PBS execution, the pbs provider should be used:

    -
    -
    -
    <execution provider="pbs" url="none" />
    -

    The GLOBUS::queue profile key can be used to -specify which PBS queue jobs will be submitted to.

    -

    For execution through a local Condor installation, the condor provider -should be used. This provider can run jobs either in the default vanilla -universe, or can use Condor-G to run jobs on remote sites.

    -

    When running locally, only the <execution> element needs to be specified:

    -
    -
    -
    <execution provider="condor" url="none" />
    -

    When running with Condor-G, it is necessary to specify the Condor grid -universe and the contact string for the remote site. For example:

    -
    -
    -
    <execution provider="condor" />
    -<profile namespace="globus" key="jobType">grid</profile>
    -<profile namespace="globus" key="gridResource">gt2 belhaven-1.renci.org/jobmanager-fork</profile>
    -

    For execution through SSH, the ssh provider should be used:

    -
    -
    -
    <execution url="www11.i2u2.org" provider="ssh"/>
    -

    with configuration made in ~/.ssh/auth.defaults with the string -www11.i2u2.org changed to the appropriate host name:

    -
    -
    -
    www11.i2u2.org.type=key
    -www11.i2u2.org.username=hategan
    -www11.i2u2.org.key=/home/mike/.ssh/i2u2portal
    -www11.i2u2.org.passphrase=XXXX
    -

    For execution using the CoG Coaster mechanism, the coaster -provider should be used:

    -
    -
    -
    <execution provider="coaster" url="tg-grid.uc.teragrid.org"
    -    jobmanager="gt2:gt2:pbs" />
    -

    More details about configuration of coasters can be found in the section -on coasters.

    -
    -
    -

    12.4. Work directory

    -

    The workdirectory element specifies where on the site files can be -stored.

    -
    -
    -
    <workdirectory>/home/benc</workdirectory>
    -

    This file must be accessible through the transfer mechanism specified in -the <gridftp> element and also mounted on all worker nodes that will -be used for execution. A shared cluster scratch filesystem is -appropriate for this.

    -
    -
    -

    12.5. Profiles

    -

    Profile keys can be specified using the <profile> element. -For example:

    -
    -
    -
    <profile namespace="globus" key="queue">fast</profile>
    -

    The site catalog format is an evolution of the VDS site catalog format -which is documented here -http://vds.uchicago.edu/vds/doc/userguide/html/H_SiteCatalog.html.

    -
    -
    -
    -
    -

    13. The Transformation Catalog - tc.data

    -
    -

    The transformation catalog lists where application executables are -located on remote sites.

    -

    By default, the site catalog is stored in etc/tc.data. This path can -be overridden with the tc.file configuration property, either in the -Swift configuration file or on the command line.

    -

    The format is one line per executable per site, with fields separated by -tabs. Spaces cannot be used to separate fields.

    -

    Some example entries:

    -
    -
    -
    localhost  echo    /bin/echo       INSTALLED       INTEL32::LINUX  null
    -TGUC       touch   /usr/bin/touch  INSTALLED       INTEL32::LINUX  GLOBUS::maxwalltime="0:1"
    -

    The fields are: site, transformation name, executable path, installation -status, platform, and profile entrys.

    -

    The site field should correspond to a site name listed in the sites catalog.

    -

    The transformation name should correspond to the transformation name -used in a SwiftScript app procedure.

    -

    The executable path should specify where the particular executable is -located on that site.

    -

    The installation status and platform fields are not used. Set them to -INSTALLED and INTEL32::LINUX respectively.

    -

    The profiles field should be set to null if no profile entries are to -be specified, or should contain the profile entries separated by -semicolons.

    -
    -
    -
    -

    14. Build options

    -
    -

    See the Swift download page -http://www.ci.uchicago.edu/swift/downloads/ for instructions on -downloading and building Swift from source. When building, various build -options can be supplied on the ant commandline. These are summarised here:

    -

    with-provider-condor - build with CoG condor provider

    -

    with-provider-coaster - build with CoG coaster provider (see the -section on coasters). Since 0.8, coasters are always built, -and this option has no effect.

    -

    with-provider-deef - build with Falkon provider deef. In order for -this option to work, it is necessary to check out the provider-deef code -in the cog/modules directory alongside swift:

    -
    -
    -
    $ cd cog/modules
    -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef
    -$ cd ../swift
    -$ ant -Dwith-provider-deef=true redist
    -

    with-provider-wonky - build with provider-wonky, an execution provider -that provides delays and unreliability for the purposes of testing -Swift’s fault tolerance mechanisms. In order for this option to work, it -is necessary to check out the provider-wonky code in the |cog/modules| -directory alongside swift:

    -
    -
    -
    $ cd cog/modules
    -$ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky
    -$ cd ../swift|*
    -$ ant -Dwith-provider-wonky=true redist
    -

    no-supporting - produces a distribution without supporting commands -such as grid-proxy-init. This is intended for when the Swift -distribution will be used in an environment where those commands are -already provided by other packages, where the Swift package should be -providing only Swift commands, and where the presence of commands such -as grid-proxy-init from the Swift distribution in the path will mask the -presence of those commands from their true distribution package such as -a Globus Toolkit package.

    -
    -
    -
    $ ant -Dno-supporting=true redist
    -
    -
    -
    -

    15. Kickstart

    -
    -

    Kickstart is a tool that can be used to gather various information about -the remote execution environment for each job that Swift tries to run.

    -

    For each job, Kickstart generates an XML invocation record. By default -this record is staged back to the submit host if the job fails.

    -

    Before it can be used it must be installed on the remote site and the -sites file must be configured to point to kickstart.

    -

    Kickstart can be downloaded as part of the Pegasus worker package -available from the worker packages section of the Pegasus download page -http://pegasus.isi.edu/code.php.

    -

    Untar the relevant worker package somewhere where it is visible to all -of the worker nodes on the remote execution machine (such as in a shared -application filesystem).

    -

    Now configure the gridlaunch attribute of the sites catalog to point to -that path, by adding a gridlaunch attribute to the pool element in -the site catalog:

    -
    -
    -
    <pool handle="example" gridlaunch="/usr/local/bin/kickstart" sysinfo="INTEL32::LINUX">
    -...
    -</pool>
    -

    There are various kickstat.* properties, which have sensible default -values. These are documented in the properties section.

    -
    -
    -
    -

    16. Reliability mechanisms

    -
    -

    This section details reliabilty mechanisms in Swift: retries, restarts -and replication.

    -
    -

    16.1. Retries

    -

    If an application procedure execution fails, Swift will attempt that -execution again repeatedly until it succeeds, up until the limit defined -in the execution.retries configuration property.

    -

    Site selection will occur for retried jobs in the same way that it -happens for new jobs. Retried jobs may run on the same site or may run -on a different site.

    -

    If the retry limit execution.retries is reached for an application -procedure, then that application procedure will fail. This will cause -the entire run to fail - either immediately (if the lazy.errors -property is false) or after all other possible work has been attempted -(if the lazy.errors property is true).

    -
    -
    -

    16.2. Restarts

    -

    If a run fails, Swift can resume the program from the point of failure. -When a run fails, a restart log file will be left behind in a file named -using the unique job ID and a .rlog extension. This restart log can -then be passed to a subsequent Swift invocation using the -resume -parameter. Swift will resume execution, avoiding execution of -invocations that have previously completed successfully. The SwiftScript -source file and input data files should not be modified between runs.

    -

    Every run creates a restart log file with a named composed of the file -name of the workflow being executed, an invocation ID, a numeric ID, and -the .rlog extension. For example, example.swift, when executed, -could produce the following restart log file: -example-ht0adgi315l61.0.rlog. Normally, if the run completes -successfully, the restart log file is deleted. If however the workflow -fails, swift can use the restart log file to continue execution from a -point before the failure occurred. In order to restart from a restart -log file, the -resume logfile argument can be used after the -SwiftScript program file name. Example:

    -
    -
    -
    $ swift -resume example-ht0adgi315l61.0.rlog example.swift.
    -
    -
    -

    16.3. Replication

    -

    When an execution job has been waiting in a site queue for a certain -period of time, Swift can resubmit replicas of that job (up to the limit -defined in the replication.limit configuration property). When any of -those jobs moves from queued to active state, all of the other replicas -will be cancelled.

    -

    This is intended to deal with situations where some sites have a -substantially longer (sometimes effectively infinite) queue time than -other sites. Selecting those slower sites can cause a very large delay -in overall run time.

    -

    Replication can be enabled by setting the replication.enabled -configuration property to true. The maximum number of replicas that -will be submitted for a job is controlled by the replication.limit -configuration property.

    -

    When replication is enabled, Swift will also enforce the maxwalltime -profile setting for jobs as documented in the profiles section.

    -
    -
    -
    -
    -

    17. Clustering

    -
    -

    Swift can group a number of short job submissions into a single larger -job submission to minimize overhead involved in launching jobs (for -example, caused by security negotiation and queuing delay). In general, -CoG coasters should be used in preference to the clustering -mechanism documented in this section.

    -

    By default, clustering is disabled. It can be activated by setting the -clustering.enabled property to true.

    -

    A job is eligible for clustering if the GLOBUS::maxwalltime profile -is specified in the tc.data entry for that job, and its value is -less than the value of the clustering.min.time property.

    -

    Two or more jobs are considered compatible if they share the same site -and do not have conflicting profiles (e.g. different values for the same -environment variable).

    -

    When a submitted job is eligible for clustering, it will be put in a -clustering queue rather than being submitted to a remote site. The -clustering queue is processed at intervals specified by the -clustering.queue.delay property. The -processing of the clustering queue consists of selecting compatible jobs -and grouping them into clusters whose maximum wall time does not exceed -twice the value of the clustering.min.time property.

    -
    -
    -
    -

    18. Coasters

    -
    -

    Coasters were introduced in Swift v0.6 as an experimental feature.

    -

    In many applications, Swift performance can be greatly enhanced by the -use of CoG coasters. CoG coasters provide a low-overhead job submission -and file transfer mechanism suited for the execution of short jobs (on -the order of a few seconds) and the transfer of small files (on the -order of a few kilobytes) for which other grid protocols such as GRAM -and GridFTP are poorly suited.

    -

    The coaster mechanism submits a head job using some other execution -mechanism such as GRAM, and for each worker node that will be used in a -remote cluster, it submits a worker job, again using some other -execution mechanism such as GRAM. Details on the design of the coaster -mechanism can be found here. http://wiki.cogkit.org/wiki/Coasters

    -

    The head job manages file transfers and the dispatch of execution jobs -to workers. Much of the overhead associated with other grid protocols -(such as authentication and authorization, and allocation of worker -nodes by the site’s local resource manager) is reduced, because that -overhead is associated with the allocation of a coaster head or coaster -worker, rather than with every Swift-level procedure invocation; -potentially hundreds or thousands of Swift-level procedure invocations -can be run through a single worker.

    -

    Coasters can be configured for use in two situations: job execution and -file transfer.

    -

    To use for job execution, specify a sites.xml execution element like this:

    -
    -
    -
    <execution provider="coaster" jobmanager="gt2:gt2:pbs" url="grid.myhost.org">
    -

    The jobmanager string contains more detail than with other providers. It -contains either two or three colon separated fields: 1:the provider to -be use to execute the coaster head job - this provider will submit from -the Swift client side environment. Commonly this will be one of the GRAM -providers; 2: the provider to be used to execute coaster worker jobs. -This provider will be used to submit from the coaster head job -environment, so a local scheduler provider can sometimes be used instead -of GRAM. 3: optionally, the jobmanager to be used when submitting worker -job using the provider specified in field 2.

    -

    To use for file transfer, specify a sites.xml filesystem element like this:

    -
    -
    -
    <filesystem provider="coaster" url="gt2://grid.myhost.org" />
    -

    The url parameter should be a pseudo-URI formed with the URI scheme -being the name of the provider to use to submit the coaster head job, -and the hostname portion being the hostname to be used to execute the -coaster head job. Note that this provider and hostname will be used for -execution of a coaster head job, not for file transfer; so for example, -a GRAM endpoint should be specified here rather than a GridFTP endpoint.

    -

    Coasters are affected by the following profile settings, which are -documented in the Globus namespace profile section:

    -
    - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Profile keyBrief description

    slots

    How many maximum LRM jobs/worker blocks are allowed

    workersPerNode

    How many coaster workers to run per execution node

    nodeGranularity

    Each worker block uses a number of nodes that is a -multiple of this number

    lowOverallocation

    How many times larger than the job walltime should a -block’s walltime be if all jobs are 1s long

    highOverallocation

    How many times larger than the job walltime should a -block’s walltime be if all jobs are infinitely long

    overallocationDecayFactor

    How quickly should the overallocation curve -tend towards the highOverallocation as job walltimes get larger

    spread

    By how much should worker blocks vary in worker size

    workersPerNode

    How many coaster workers to run per execution node

    reserve

    How many seconds to reserve in a block’s walltime for -starting/shutdown operations

    maxnodes

    The maximum number of nodes allowed in a block

    maxtime

    The maximum number of walltime allowed for a block

    remoteMonitorEnabled

    If true, show a graphical display of the status of -the coaster service

    -
    -
    -
    -
    -

    19. How-To Tips for Specific User Communities

    -
    -
    -

    19.1. Saving Logs - for UChicago CI Users

    -

    If you have a UChicago Computation Institute account, run this command -in your submit directory after each run. It will copy all your logs and -kickstart records into a directory at the CI for reporting, usage -tracking, support and debugging.

    -
    -
    -
    rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose
    -
    -
    -

    19.2. Specifying TeraGrid allocations

    -

    TeraGrid users with no default project or with several project -allocations can specify a project allocation using a profile key in the -site catalog entry for a TeraGrid site:

    -
    -
    -
    <profile namespace="globus" key="project">TG-CCR080002N</profile>
    -

    More information on the TeraGrid allocations process can be found here -http://www.teragrid.org/userinfo/access/allocations.php.

    -
    -
    -

    19.3. Launching MPI jobs from Swift

    -

    Here is an example of running a simple MPI program.

    -

    In SwiftScript, we make an invocation that does not look any different -from any other invocation. In the below code, we do not have any input -files, and have two output files on stdout and stderr:

    -
    -
    -
    type file;
    -
    -(file o, file e) p() {
    -    app {
    -        mpi stdout=@filename(o) stderr=@filename(e);
    -    }
    -}
    -
    -file mpiout <"mpi.out">;
    -file mpierr <"mpi.err">;
    -
    -(mpiout, mpierr) = p();
    -

    Now we define how mpi will run in tc.data:

    -
    -
    -
    tguc    mpi             /home/benc/mpi/mpi.sh   INSTALLED       INTEL32::LINUX GLOBUS::host_xcount=3
    -

    mpi.sh is a wrapper script that launches the MPI program. It must be -installed on the remote site:

    -
    -
    -
    #!/bin/bash
    -mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out
    -

    Because of the way that Swift runs its server side code, -provider-specific MPI modes (such as GRAM jobType=mpi) should not be -used. Instead, the mpirun command should be explicitly invoked.

    -
    -
    -

    19.4. Running on Windows

    -

    Since 10/11/09, the development version of Swift has the ability to run -on a Windows machine, as well as the ability to submit jobs to a Windows -site (provided that an appropriate provider is used).

    -

    In order to launch Swift on Windows, use the provided batch file -(swift.bat). In certain cases, when a large number of jar libraries are -present in the Swift lib directory and depending on the exact location -of the Swift installation, the classpath environment variable that the -Swift batch launcher tries to create may be larger than what Windows can -handle. In such a case, either install Swift in a directory closer to -the root of the disk (say, c:\swift) or remove non-essential jar files -from the Swift lib directory.

    -

    Due to the large differences between Windows and Unix environments, -Swift must use environment specific tools to achieve some of its goals. -In particular, each Swift executable is launched using a wrapper script. -This script is a Bourne Shell script. On Windows machines, which have no -Bourne Shell interpreter installed by default, the Windows Scripting -Host is used instead, and the wrapper script is written in VBScript. -Similarly, when cleaning up after a run, the "/bin/rm" command available -in typical Unix environments must be replaced by the "del" shell command.

    -

    It is important to note that in order to select the proper set of tools -to use, Swift must know when a site runs under Windows. To inform Swift -of this, specify the "sysinfo" attribute for the "pool" element in the -site catalog. For example:

    -
    -
    -
    <pool handle="localhost" sysinfo="INTEL32::WINDOWS">
    -...
    -</pool>
    -
    -
    -
    -
    -

    - - - Modified: trunk/docs/userguide/userguide.txt =================================================================== --- trunk/docs/userguide/userguide.txt 2011-05-17 15:29:13 UTC (rev 4482) +++ trunk/docs/userguide/userguide.txt 2011-05-17 15:30:41 UTC (rev 4483) @@ -59,12 +59,11 @@ with a mapping descriptor indicating the file(s) that make up that dataset. For example, the following line declares a variable named photo with type image. It additionally declares that the data for -this variable is stored in a single file named shane.jpeg. +this variable is stored in a single file named shane.jpg. -[java] -source~~~~ -image photo <"shane.jpeg">; -source~~~~ +---- +image photo <"shane.jpg">; +---- Component programs of scripts are declared in an app declaration, with the description of the command line syntax for that program and a list @@ -75,19 +74,17 @@ the ImageMagick convert command to rotate a supplied image by a specified angle: -[java] -source~~~~ +---- app (image output) rotate(image input) { convert "-rotate" angle @input @output; } -source~~~~ +---- A procedure is invoked using the familiar syntax: -[java] -source~~~~ +---- rotated = rotate(photo, 180); -source~~~~ +---- While this looks like an assignment, the actual unix level execution consists of invoking the command line specified in the app @@ -99,10 +96,9 @@ that type. We can declare it as a marker type which has no structure exposed to SwiftScript: -[java] -source~~~~ +---- type image; -source~~~~ +---- This does not indicate that the data is unstructured; but it indicates that the structure of the data is not exposed to SwiftScript. Instead, @@ -112,39 +108,37 @@ declare and invoke procedures, we can build a complete (albeit simple) script: -[java] -source~~~~ +---- type image; -image photo <"shane.jpeg">; -image rotated <"rotated.jpeg">; +image photo <"shane.jpg">; +image rotated <"rotated.jpg">; app (image output) rotate(image input, int angle) { convert "-rotate" angle @input @output; } rotated = rotate(photo, 180); -source~~~~ +---- This script can be invoked from the command line: -[txt] -source~~~~ - $ ls *.jpeg - shane.jpeg +---- + $ ls *.jpg + shane.jpg $ swift example.swift ... - $ ls *.jpeg - shane.jpeg rotated.jpeg -source~~~~ + $ ls *.jpg + shane.jpg rotated.jpg +---- This executes a single convert command, hiding from the user features such as remote multisite execution and fault tolerance that will be discussed in a later section. -.Figure 1. shane.jpeg -image:userguide-shane.jpeg[] +.Figure 1. shane.jpg +image:userguide-shane.jpg[] -.Figure 2. rotated.jpeg -image:userguide-rotated.jpeg[] +.Figure 2. rotated.jpg +image:userguide-rotated.jpg[] Arrays and Parallel Execution @@ -155,30 +149,26 @@ different form of mapping expression. For example, the filesys_mapper maps all files matching a particular unix glob pattern into an array: -[java] -source~~~~ -file frames[] ; -source~~~~ +---- +file frames[] ; +---- The foreach construct can be used to apply the same block of code to each element of an array: -[java] -source~~~~ +---- foreach f,ix in frames { output[ix] = rotate(frames, 180); -} -source~~~~ +---- Sequential iteration can be expressed using the iterate construct: -[java] -source~~~~ +---- step[0] = initialCondition(); iterate ix { step[ix] = simulate(step[ix-1]); } -source~~~~ +---- This fragment will initialise the 0-th element of the step array to some initial condition, and then repeatedly run the simulate @@ -199,20 +189,18 @@ In this fragment, execution of procedures p and q can happen in parallel: -[java] -source~~~~ +---- y=p(x); z=q(x); -source~~~~ +---- while in this fragment, execution is serialised by the variable y, with procedure p executing before q. -[java] -source~~~~ +---- y=p(x); z=q(y); -source~~~~ +---- Arrays in SwiftScript are more monotonic - a generalisation of being assignment. Knowledge about the content of an array increases during @@ -228,8 +216,7 @@ known. It will not wait until the array is closed. Consider this script: -[java] -source~~~~ +---- file a[]; file b[]; foreach v,i in a { @@ -237,7 +224,7 @@ } a[0] = r(); a[1] = s(); -source~~~~ +---- Initially, the foreach statement will have nothing to execute, as the array a has not been assigned any values. The procedures r and s @@ -255,8 +242,7 @@ mentioned procedures declared with the app keyword, as they invoke other SwiftScript procedures rather than a component program. -[java] -source~~~~ +---- (file output) process (file input) { file intermediate; intermediate = first(input); @@ -266,7 +252,7 @@ file x <"x.txt">; file y <"y.txt">; y = process(x); -source~~~~ +---- This will invoke two procedures, with an intermediate data file named anonymously connecting the first and second procedures. @@ -274,8 +260,7 @@ Ordering of execution is generally determined by execution of app procedures, not by any containing compound procedures. In this code block: -[java] -source~~~~ +---- (file a, file b) A() { a = A1(); b = A2(); @@ -284,7 +269,7 @@ (x,y) = A(); s = S(x); t = S(y); -source~~~~ +---- then a valid execution order is: A1 S(x) A2 S(y). The compound procedure A does not have to have fully completed for its return @@ -320,23 +305,21 @@ Complex types may be defined using the type keyword: -[java] -source~~~~ +---- type headerfile; type voxelfile; type volume { headerfile h; voxelfile v; } -source~~~~ +---- Members of a complex type can be accessed using the . operator: -[java] -source~~~~ +---- volume brain; o = p(brain.h); -source~~~~ +---- Sometimes data may be stored in a form that does not fit with Swift's file-and-site model; for example, data might be stored in an RDBMS on @@ -350,8 +333,7 @@ allowing arbitrary data storage and access methods to be plugged in to scripts. -[java] -source~~~~ +---- type file; app (external o) populateDatabase() { @@ -367,7 +349,7 @@ database = populateDatabase(); result = analyseDatabase(database); -source~~~~ +---- Some external database is represented by the database variable. The populateDatabase procedure populates the database with some data, and @@ -404,10 +386,9 @@ representation is a file called "file1.bin" located at "/home/yongzh/data/", then the dataset might be declared as follows: -[java] -source~~~~ +---- imagefile f1 -source~~~~ +---- The above example declares a dataset called f1, which uses a single file mapper to map a file from a specific location. @@ -415,10 +396,9 @@ SwiftScript has a simplified syntax for this case, since single_file_mapper is frequently used: -[java] -source~~~~ +---- binaryfile f1<"/home/yongzh/data/file1.bin"> -source~~~~ +---- Swift comes with a number of mappers that handle common mapping patterns. These are documented in the mappers section of this @@ -454,10 +434,9 @@ Declaration statements have the general form: -[java] -source~~~~ +---- typename variablename ( | = initialValue ) ; -source~~~~ +---- The format of the mapping expression is defined in the Mappers section. initialValue may be either an expression or a procedure call that @@ -473,10 +452,9 @@ Assignments may only be made to variables that have not already been assigned. Assignment statements have the general form: -[java] -source~~~~ +---- variable = value; -source~~~~ +---- where value can be either an expression or a procedure call that returns a single value. @@ -496,10 +474,9 @@ and produce multiple outputs. Inputs are specified to the right of the function name, and outputs are specified to the left. For example: -[java] -source~~~~ +---- (type3 out1, type4 out2) myproc (type1 in1, type2 in2) -source~~~~ +---- The above example declares a procedure called myproc, which has two inputs in1 (of type type1) and in2 (of type type2) and two @@ -512,23 +489,20 @@ parameters and any optional parameter is bound using keyword parameter passing. For example, if myproc1 is defined as: -[java] -source~~~~ +---- (binaryfile bf) myproc1 (int i, string s="foo") -source~~~~ +---- Then that procedure can be called like this, omitting the optional -[java] -source~~~~ +---- parameter s: binaryfile mybf = myproc1(1); -source~~~~ +---- or like this supplying a value for the optional parameter s: -[java] -source~~~~ +---- binaryfile mybf = myproc1 (1, s="bar"); -source~~~~ +---- Atomic procedures ^^^^^^^^^^^^^^^^^ @@ -537,12 +511,11 @@ Atomic procedures are defined with the app keyword: -[java] -source~~~~ +---- app (binaryfile bf) myproc (int i, string s="foo") { myapp i s @filename(bf); } -source~~~~ +---- which specifies that myproc invokes an executable called myapp, passing the values of i, s and the filename of bf as command line @@ -553,14 +526,13 @@ ^^^^^^^^^^^^^^^^^^^ A compound procedure contains a set of SwiftScript statements: -[java] -source~~~~ +---- (type2 b) foo_bar (type1 a) { type3 c; c = foo(a); // c holds the result of foo b = bar(c); // c is an input to bar } -source~~~~ +---- Control Constructs ~~~~~~~~~~~~~~~~~~ @@ -574,23 +546,21 @@ The foreach construct is used to apply a block of statements to each element in an array. For example: -[java] -source~~~~ +---- check_order (file a[]) { foreach f in a { compute(f); } } -source~~~~ +---- foreach statements have the general form: -[java] -source~~~~ +---- foreach controlvariable (,index) in expression { statements } -source~~~~ +---- The block of statements is evaluated once for each element in expression which must be an array, with controlvariable set to the @@ -604,14 +574,13 @@ executed, based on a boolean predicate. if statements generally have the form: -[java] -source~~~~ +---- if(predicate) { statements } else { statements } -source~~~~ +---- where predicate is a boolean expression. @@ -623,8 +592,7 @@ based on the value of a numerical control expression. switch statements take the general form: -[java] -source~~~~ +---- switch(controlExpression) { case n1: statements2 @@ -634,7 +602,7 @@ default: statements } -source~~~~ +---- The control expression is evaluated, the resulting numerical value used to select a corresponding case, and the statements belonging to that @@ -654,12 +622,11 @@ The general form is: -[java] -source~~~~ +---- iterate var { statements; } until (terminationExpression); -source~~~~ +---- with the variable var starting at 0 and increasing by one in each iteration. That variable is in scope in the statements block and when @@ -701,18 +668,16 @@ For example, a SwiftScript program might contain this: -[java] -source~~~~ +---- import defs; file f; -source~~~~ +---- which would import the content of defs.swift in the current directory: -[java] -source~~~~ +---- type file; -source~~~~ +---- Imported files are read from the current working directory. @@ -754,16 +719,14 @@ |================= Example: -[java] -source~~~~ +---- file f ; -source~~~~ +---- There is a simplified syntax for this mapper: -[java] -source~~~~ +---- file f <"plot_outfile_param">; -source~~~~ +---- The simple mapper ~~~~~~~~~~~~~~~~~ @@ -782,11 +745,10 @@ output filenames, pattern is ignored. |==================== -[java] -source~~~~ +---- type file; file f ; -source~~~~ +---- The above maps all filenames that start with foo and have an extension .txt into file f. @@ -796,8 +758,7 @@ |Swift variable|Filename |f|foo.txt |================= -[java] -source~~~~ +---- type messagefile; (messagefile t) greeting(string m) {. @@ -809,15 +770,14 @@ messagefile outfile ; outfile = greeting("hi"); -source~~~~ +---- This will output the string 'hi' to the file foo.txt. The simple_mapper can be used to map arrays. It will map the array index into the filename between the prefix and suffix. -[java] -source~~~~ +---- type messagefile; (messagefile t) greeting(string m) { @@ -831,7 +791,7 @@ outfile[0] = greeting("hello"); outfile[1] = greeting("middle"); outfile[2] = greeting("goodbye"); -source~~~~ +---- [options="header"] |======================= @@ -844,8 +804,7 @@ simple_mapper can be used to map structures. It will map the name of the structure member into the filename, between the prefix and the suffix. -[java] -source~~~~ +---- type messagefile; type mystruct { @@ -863,7 +822,7 @@ out.left = greeting("hello"); out.right = greeting("goodbye"); -source~~~~ +---- This will output the string "hello" into the file qux.left.txt and the string "goodbye" into the file qux.right.txt. @@ -895,12 +854,10 @@ |================= Example: -[java] -source~~~~ +---- file f1; file f2 ; -source~~~~ - +---- The above example would use concurrent mapper for f1 and f2, and generate f2 filename with prefix "foo" and extension ".txt" @@ -927,10 +884,9 @@ |====================== Example: -[java] -source~~~~ +---- file texts[] ; -source~~~~ +---- The above example would map all filenames that start with "foo" and have an extension ".txt" into the array texts. For example, if the @@ -961,10 +917,9 @@ Example: -[java] -source~~~~ +---- file texts[] ; -source~~~~ +---- would cause a mapping like this: @@ -987,12 +942,11 @@ |============== Example: -[java] -source~~~~ +---- string s[] = [ "a.txt", "b.txt", "c.txt" ]; file f[] ; -source~~~~ +---- This will establish the mapping: @@ -1023,14 +977,13 @@ |========== Example: -[java] -source~~~~ +---- string s = "picture.gif"; file f ; -source~~~~ +---- This example transforms a string ending gif into one ending jpg and maps that to a file. @@ -1050,14 +1003,13 @@ file contains columns: name age GPA then the type needs to have member elements like this: -[java] -source~~~~ +---- type student { file name; file age; file GPA; } -source~~~~ +---- If the file does not contain a header with column info, then the column names are assumed as column1, column2, etc. @@ -1074,23 +1026,21 @@ |============= Example: -[java] -source~~~~ +---- student stus[] ; -source~~~~ +---- The above example would read a list of student info from file "stu_list.txt" and map them into a student array. By default, the file should contain a header line specifying the names of the columns. If stu_list.txt contains the following: -[java] -source~~~~ +---- name,age,gpa 101-name.txt, 101-age.txt, 101-gpa.txt name55.txt, age55.txt, age55.txt q, r, s -source~~~~ +---- then some of the mappings produced by this example would be: @@ -1130,20 +1080,18 @@ Example: With the following in mapper.sh, -[shell] -source~~~~ +---- #!/bin/bash echo "[2] qux" echo "[0] foo" echo "[1] bar" -source~~~~ +---- then a mapping statement: -[java] -source~~~~~ +---- student stus[] ; -source~~~~ +---- would map @@ -1355,8 +1303,7 @@ In this section, this example SwiftScript program is used for reference: -[java] -source~~~~~ +---- type file; app (file o) count(file i) { @@ -1365,7 +1312,7 @@ file q <"input.txt">; file r <"output.txt">; -source~~~~ +---- The executable for wc will be looked up in tc.data. @@ -1616,21 +1563,19 @@ For example: -[java] -source~~~~ +---- trace(@arg("myparam")); trace(@arg("optionalparam", "defaultvalue")); -source~~~~ +---- -[java] -source~~~~ +---- $ swift arg.swift -myparam=hello Swift v0.3-dev r1674 (modified locally) RunID: 20080220-1548-ylc4pmda SwiftScript trace: defaultvalue SwiftScript trace: hello -source~~~~ +---- @extractint ~~~~~~~~~~~ @@ -1659,10 +1604,9 @@ . For example: -[java] -source~~~~ +---- string v = @regexp("abcdefghi", "c(def)g","monkey"); -source~~~~ +---- will assign the value "abmonkeyhi" to the variable v. @@ -1682,13 +1626,12 @@ section that matches the first matching parenthesised group. For example: -[java] -source~~~~ +---- string t = "my name is John and i like puppies."; string name = @strcut(t, "my name is ([^ ]*) "); string out = @strcat("Your name is ",name); trace(out); -source~~~~ +---- will output the message: Your name is John. @@ -1699,14 +1642,13 @@ (since Swift 0.9) Example: -[java] -source~~~~ +---- string t = "my name is John and i like puppies."; string words[] = @strsplit(t, "\\s"); foreach word in words { trace(word); } -source~~~~ +---- will output one word of the sentence on each line (though not necessarily in order, due to the fact that foreach iterations execute in @@ -1757,20 +1699,18 @@ Input files should list, one per line, a path into a Swift structure, and the value for that position in the structure: -[java] -source~~~~ +---- rows[0].columns[0] = 0 rows[0].columns[1] = 2 rows[0].columns[2] = 4 rows[1].columns[0] = 1 rows[1].columns[1] = 3 rows[1].columns[2] = 5 -source~~~~ +---- which can be read into a structure defined like this: -[java] -source~~~~ +---- type vector { int columns[]; } @@ -1782,7 +1722,7 @@ matrix m; m = readData2("readData2.in"); -source~~~~ +---- (since Swift 0.7) @@ -1855,15 +1795,14 @@ amount of remote file system space to be used for caching can be limited using the swift:storagesize profile entry in the sites.xml file. Example: -[xml] -source~~~~ +---- /scratch/swift 20000000 -source~~~~ +---- The decision of which files to keep in the cache and which files to remove is made considering the value of the caching.algorithm @@ -2002,11 +1941,10 @@ Graphviz , for example with a command-line such as: -[shell] -source~~~~ +---- $ swift -pgraph graph1.dot q1.swift $ dot -ograph.png -Tpng graph1.dot -source~~~~ +---- pgraph.graph.options @@ -2241,10 +2179,11 @@ Example: -[source,xml] +---- sites.file=${vds.home}/etc/sites.xml tc.file=${vds.home}/etc/tc.data ip.address=192.168.0.1 +---- Profiles -------- @@ -2263,8 +2202,9 @@ maxSubmitRate limits the maximum rate of job submission, in jobs per second. For example: -[source,xml] +---- 0.2 +---- will limit job submission to 0.2 jobs per second (or equivalently, one job every five seconds). @@ -2326,8 +2266,9 @@ * Hours:Minutes:Seconds Example: -[source,java] +---- localhost echo /bin/echo INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="00:20:00" +---- When replication is enabled (see replication), then walltime will also be enforced at the Swift client side: when a job has @@ -2353,9 +2294,9 @@ condor_requirements allows a requirements string to be specified when Condor is used as an LRM behind GRAM2. Example: -[source,xml] -Arch == "X86_64" || Arch="INTEL" +---- +Arch == "X86_64" || Arch="INTEL" +---- slots When using coasters, this parameter specifies the maximum number of jobs/blocks that the coaster scheduler will have @@ -2485,8 +2426,9 @@ To use gridftp or local filesystem copy, use the element: -[source,xml] +---- +---- The url attribute may specify a GridFTP server, using the gsiftp URI scheme; or it may specify that filesystem copying will be used (which @@ -2496,8 +2438,9 @@ Filesystem access using scp (the SSH copy protocol) can be specified using the element: -[source,xml] +---- +---- For additional ssh configuration information, see the ssh execution provider documentation below. @@ -2514,9 +2457,9 @@ The element can be used to specify execution through GRAM2. For example, -[source,xml] +---- - +---- The universe attribute should always be set to vanilla. The url attribute should specify the name of the GRAM2 gatekeeper host, and the name of the jobmanager to use. The major attribute should always be set @@ -2527,21 +2470,24 @@ To use GRAM4, specify the gt4 provider. For example: -[source,xml] +---- +---- The url attribute should specify the GRAM4 submission site. The jobmanager attribute should specify which GRAM4 jobmanager will be used. For local execution, the local provider should be used, like this: -[source,xml] +---- +---- For PBS execution, the pbs provider should be used: -[source,xml] +---- +---- The GLOBUS::queue profile key can be used to specify which PBS queue jobs will be submitted to. @@ -2552,37 +2498,41 @@ When running locally, only the element needs to be specified: -[source,xml] +---- +---- When running with Condor-G, it is necessary to specify the Condor grid universe and the contact string for the remote site. For example: -[source,xml] +---- grid gt2 belhaven-1.renci.org/jobmanager-fork +---- For execution through SSH, the ssh provider should be used: -[source,xml] +---- - +---- with configuration made in ~/.ssh/auth.defaults with the string 'www11.i2u2.org' changed to the appropriate host name: -[source,shell] +---- www11.i2u2.org.type=key www11.i2u2.org.username=hategan www11.i2u2.org.key=/home/mike/.ssh/i2u2portal www11.i2u2.org.passphrase=XXXX +---- For execution using the CoG Coaster mechanism, the coaster provider should be used: -[source,xml] +---- +---- More details about configuration of coasters can be found in the section on coasters. @@ -2592,8 +2542,9 @@ The workdirectory element specifies where on the site files can be stored. -[source,xml] +---- /home/benc +---- This file must be accessible through the transfer mechanism specified in the element and also mounted on all worker nodes that will @@ -2605,8 +2556,9 @@ Profile keys can be specified using the element. For example: -[source,xml] +---- fast +---- The site catalog format is an evolution of the VDS site catalog format which is documented here @@ -2626,9 +2578,10 @@ tabs. Spaces cannot be used to separate fields. Some example entries: -[source,shell] +---- localhost echo /bin/echo INSTALLED INTEL32::LINUX null TGUC touch /usr/bin/touch INSTALLED INTEL32::LINUX GLOBUS::maxwalltime="0:1" +---- The fields are: site, transformation name, executable path, installation status, platform, and profile entrys. @@ -2665,11 +2618,12 @@ this option to work, it is necessary to check out the provider-deef code in the cog/modules directory alongside swift: -[source,shell] +---- $ cd cog/modules $ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-deef $ cd ../swift $ ant -Dwith-provider-deef=true redist +---- with-provider-wonky - build with provider-wonky, an execution provider that provides delays and unreliability for the purposes of testing @@ -2677,11 +2631,12 @@ is necessary to check out the provider-wonky code in the |cog/modules| directory alongside swift: -[source,shell] +---- $ cd cog/modules $ svn co https://svn.ci.uchicago.edu/svn/vdl2/provider-wonky -$ cd ../swift|* +$ cd ../swift $ ant -Dwith-provider-wonky=true redist +---- no-supporting - produces a distribution without supporting commands such as grid-proxy-init. This is intended for when the Swift @@ -2692,8 +2647,9 @@ presence of those commands from their true distribution package such as a Globus Toolkit package. -[source,shell] +---- $ ant -Dno-supporting=true redist +---- Kickstart --------- @@ -2718,10 +2674,11 @@ that path, by adding a gridlaunch attribute to the pool element in the site catalog: -[source,xml] +---- ... +---- There are various kickstat.* properties, which have sensible default values. These are documented in the properties section. @@ -2768,8 +2725,9 @@ log file, the -resume logfile argument can be used after the SwiftScript program file name. Example: -[source,shell] +---- $ swift -resume example-ht0adgi315l61.0.rlog example.swift. +---- Replication ~~~~~~~~~~~ @@ -2850,8 +2808,9 @@ To use for job execution, specify a sites.xml execution element like this: -[source,xml] +---- +---- The jobmanager string contains more detail than with other providers. It contains either two or three colon separated fields: 1:the provider to @@ -2865,9 +2824,9 @@ To use for file transfer, specify a sites.xml filesystem element like this: -[source,xml] +---- - +---- The url parameter should be a pseudo-URI formed with the URI scheme being the name of the provider to use to submit the coaster head job, and the hostname portion being the hostname to be used to execute the @@ -2911,8 +2870,9 @@ kickstart records into a directory at the CI for reporting, usage tracking, support and debugging. -[source,shell] +---- rsync --ignore-existing *.log *.d login.ci.uchicago.edu:/disks/ci-gpfs/swift/swift-logs/ --verbose +---- Specifying TeraGrid allocations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -2920,8 +2880,9 @@ allocations can specify a project allocation using a profile key in the site catalog entry for a TeraGrid site: -[source,xml] +---- TG-CCR080002N +---- More information on the TeraGrid allocations process can be found here . @@ -2934,8 +2895,7 @@ from any other invocation. In the below code, we do not have any input files, and have two output files on stdout and stderr: -[java] -source~~~~ +---- type file; (file o, file e) p() { @@ -2948,18 +2908,20 @@ file mpierr <"mpi.err">; (mpiout, mpierr) = p(); -source~~~~ +---- Now we define how 'mpi' will run in tc.data: -[source,shell] +---- tguc mpi /home/benc/mpi/mpi.sh INSTALLED INTEL32::LINUX GLOBUS::host_xcount=3 +---- mpi.sh is a wrapper script that launches the MPI program. It must be installed on the remote site: -[source,shell] +---- #!/bin/bash mpirun -np 3 -machinefile $PBS_NODEFILE /home/benc/mpi/a.out +---- Because of the way that Swift runs its server side code, provider-specific MPI modes (such as GRAM jobType=mpi) should not be @@ -2994,7 +2956,8 @@ of this, specify the "sysinfo" attribute for the "pool" element in the site catalog. For example: -[source,xml] +---- ... +----