1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
|
Description: remove steps requirering Internet for the documentation.
Author: Étienne Mollier <emollier@debian.org>
Forwarded: not-needed
Last-Update: 2024-01-14
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- python-parsl.orig/docs/conf.py
+++ python-parsl/docs/conf.py
@@ -43,11 +43,6 @@
'sphinx.ext.napoleon'
]
-url = 'https://raw.githubusercontent.com/Parsl/parsl-tutorial/master/1-parsl-introduction.ipynb'
-r = requests.get(url)
-with open(os.path.join(os.path.dirname(__file__), '1-parsl-introduction.ipynb'), 'wb') as f:
- f.write(r.content)
-
nbsphinx_execute = 'never'
def linkcode_resolve(domain, info):
@@ -61,9 +56,6 @@
# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
-intersphinx_mapping = {
- 'python': ('https://docs.python.org/3', None),
-}
# The suffix(es) of source filenames.
# You can specify multiple suffix as a list of string:
#
--- python-parsl.orig/docs/index.rst
+++ python-parsl/docs/index.rst
@@ -105,7 +105,6 @@
:maxdepth: 2
quickstart
- 1-parsl-introduction.ipynb
userguide/index
userguide/glossary
faq
--- python-parsl.orig/docs/userguide/configuration/examples.rst
+++ python-parsl/docs/userguide/configuration/examples.rst
@@ -134,8 +134,6 @@
ASPIRE 1 (NSCC)
---------------
-.. image:: https://www.nscc.sg/wp-content/uploads/2017/04/ASPIRE1Img.png
-
The following snippet shows an example configuration for accessing NSCC's **ASPIRE 1** supercomputer. This example uses the `parsl.executors.HighThroughputExecutor` executor and connects to ASPIRE1's PBSPro scheduler. It also shows how ``scheduler_options`` parameter could be used for scheduling array jobs in PBSPro.
.. literalinclude:: ../../../parsl/configs/ASPIRE1.py
@@ -146,8 +144,6 @@
Illinois Campus Cluster (UIUC)
------------------------------
-.. image:: https://campuscluster.illinois.edu/wp-content/uploads/2018/02/ND2_3633-sm.jpg
-
The following snippet shows an example configuration for executing on the Illinois Campus Cluster.
The configuration assumes the user is running on a login node and uses the `parsl.providers.SlurmProvider` to interface
with the scheduler, and uses the `parsl.launchers.SrunLauncher` to launch workers.
@@ -157,8 +153,6 @@
Bridges (PSC)
-------------
-.. image:: https://insidehpc.com/wp-content/uploads/2016/08/Bridges_FB1b.jpg
-
The following snippet shows an example configuration for executing on the Bridges supercomputer at the Pittsburgh Supercomputing Center.
The configuration assumes the user is running on a login node and uses the `parsl.providers.SlurmProvider` to interface
with the scheduler, and uses the `parsl.launchers.SrunLauncher` to launch workers.
@@ -170,8 +164,6 @@
CC-IN2P3
--------
-.. image:: https://cc.in2p3.fr/wp-content/uploads/2017/03/bandeau_accueil.jpg
-
The snippet below shows an example configuration for executing from a login node on IN2P3's Computing Centre.
The configuration uses the `parsl.providers.LocalProvider` to run on a login node primarily to avoid GSISSH, which Parsl does not support.
This system uses Grid Engine which Parsl interfaces with using the `parsl.providers.GridEngineProvider`.
@@ -182,8 +174,6 @@
CCL (Notre Dame, TaskVine)
--------------------------
-.. image:: https://ccl.cse.nd.edu/software/taskvine/taskvine-logo.png
-
To utilize TaskVine with Parsl, please install the full CCTools software package within an appropriate Anaconda or Miniconda environment
(instructions for installing Miniconda can be found `in the Conda install guide <https://docs.conda.io/projects/conda/en/latest/user-guide/install/>`_):
@@ -208,8 +198,6 @@
Expanse (SDSC)
--------------
-.. image:: https://www.hpcwire.com/wp-content/uploads/2019/07/SDSC-Expanse-graphic-cropped.jpg
-
The following snippet shows an example configuration for executing remotely on San Diego Supercomputer
Center's **Expanse** supercomputer. The example is designed to be executed on the login nodes, using the
`parsl.providers.SlurmProvider` to interface with the Slurm scheduler used by Comet and the `parsl.launchers.SrunLauncher` to launch workers.
@@ -220,8 +208,6 @@
Improv (Argonne LCRC)
---------------------
-.. image:: https://www.lcrc.anl.gov/sites/default/files/styles/965_wide/public/2023-12/20231214_114057.jpg?itok=A-Rz5pP9
-
**Improv** is a PBS Pro based supercomputer at Argonne's Laboratory Computing Resource
Center (LCRC). The following snippet is an example configuration that uses `parsl.providers.PBSProProvider`
and `parsl.launchers.MpiRunLauncher` to run on multinode jobs.
@@ -242,8 +228,6 @@
Frontera (TACC)
---------------
-.. image:: https://frontera-portal.tacc.utexas.edu/media/filer_public/2c/fb/2cfbf6ab-818d-42c8-b4d5-9b39eb9d0a05/frontera-banner-home.jpg
-
Deployed in June 2019, Frontera is the 5th most powerful supercomputer in the world. Frontera replaces the NSF Blue Waters system at NCSA
and is the first deployment in the National Science Foundation's petascale computing program. The configuration below assumes that the user is
running on a login node and uses the `parsl.providers.SlurmProvider` to interface with the scheduler, and uses the `parsl.launchers.SrunLauncher` to launch workers.
@@ -254,8 +238,6 @@
Kubernetes Clusters
-------------------
-.. image:: https://d1.awsstatic.com/PAC/kuberneteslogo.eabc6359f48c8e30b7a138c18177f3fd39338e05.png
-
Kubernetes is an open-source system for container management, such as automating deployment and scaling of containers.
The snippet below shows an example configuration for deploying pods as workers on a Kubernetes cluster.
The KubernetesProvider exploits the Python Kubernetes API, which assumes that you have kube config in ``~/.kube/config``.
@@ -266,8 +248,6 @@
Midway (RCC, UChicago)
----------------------
-.. image:: https://rcc.uchicago.edu/sites/rcc.uchicago.edu/files/styles/slideshow-image/public/uploads/images/slideshows/20140430_RCC_8978.jpg?itok=BmRuJ-wq
-
This Midway cluster is a campus cluster hosted by the Research Computing Center at the University of Chicago.
The snippet below shows an example configuration for executing remotely on Midway.
The configuration assumes the user is running on a login node and uses the `parsl.providers.SlurmProvider` to interface
@@ -279,8 +259,6 @@
Open Science Grid
-----------------
-.. image:: https://www.renci.org/wp-content/uploads/2008/10/osg_logo.png
-
The Open Science Grid (OSG) is a national, distributed computing Grid spanning over 100 individual sites to provide tens of thousands of CPU cores.
The snippet below shows an example configuration for executing remotely on OSG. You will need to have a valid project name on the OSG.
The configuration uses the `parsl.providers.CondorProvider` to interface with the scheduler.
@@ -291,9 +269,6 @@
Polaris (ALCF)
--------------
-.. image:: https://www.alcf.anl.gov/sites/default/files/styles/965x543/public/2022-07/33181D_086_ALCF%20Polaris%20Crop.jpg?itok=HVAHsZtt
- :width: 75%
-
ALCF provides documentation on `how to use Parsl on Polaris <https://docs.alcf.anl.gov/polaris/workflows/parsl/>`_.
Polaris uses `parsl.providers.PBSProProvider` and `parsl.launchers.MpiExecLauncher` to launch tasks onto the HPC system.
@@ -302,8 +277,6 @@
Stampede2 (TACC)
----------------
-.. image:: https://www.tacc.utexas.edu/documents/1084364/1413880/stampede2-0717.jpg/
-
The following snippet shows an example configuration for accessing TACC's **Stampede2** supercomputer. This example uses theHighThroughput executor and connects to Stampede2's Slurm scheduler.
.. literalinclude:: ../../../parsl/configs/stampede2.py
@@ -312,8 +285,6 @@
Summit (ORNL)
-------------
-.. image:: https://www.olcf.ornl.gov/wp-content/uploads/2018/06/Summit_Exaop-1500x844.jpg
-
The following snippet shows an example configuration for executing from the login node on Summit, the leadership class supercomputer hosted at the Oak Ridge National Laboratory.
The example uses the :class:`parsl.providers.LSFProvider` to provision compute nodes from the LSF cluster scheduler and the `parsl.launchers.JsrunLauncher` to launch workers across the compute nodes.
@@ -323,8 +294,6 @@
TOSS3 (LLNL)
------------
-.. image:: https://hpc.llnl.gov/sites/default/files/Magma--2020-LLNL.jpg
-
The following snippet shows an example configuration for executing on one of LLNL's **TOSS3**
machines, such as Quartz, Ruby, Topaz, Jade, or Magma. This example uses the `parsl.executors.FluxExecutor`
and connects to Slurm using the `parsl.providers.SlurmProvider`. This configuration assumes that the script
|
