[Documentation] Compare to parsl
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
No repository file, test, or documentation entry point is named. Start by determining where a Parsl comparison belongs, then use the provided Python configuration as the source example and define the comparison's scope and completion criteria before documenting it.
Written by the indexing model from the issue text.
Description
#!/bin/env python3
import os
import parsl
from parsl.app.app import python_app, bash_app
from parsl.config import Config
from parsl.channels import LocalChannel
from parsl.providers import SlurmProvider
from parsl.executors import FluxExecutor
from parsl.launchers import SimpleLauncher
from parsl.addresses import address_by_hostname
from parsl.data_provider.files import File
# Update to import config for your machine
config = Config(
executors=[
FluxExecutor(
label="hera_flux",
# launch_cmd='{flux} start -v 2 {python} {manager} {protocol} {hostname} {port}',
launch_cmd='srun --tasks-per-node=1 ' + FluxExecutor.DEFAULT_LAUNCH_CMD,
provider=SlurmProvider(
channel=LocalChannel(),
nodes_per_block=2,
init_blocks=1,
partition='pdebug',
walltime='00:10:00',
launcher=SimpleLauncher(),
),
)
],
)
parsl.load(config)
remote = False
shared_dir = "/usr/workspace/corbett8/Flux/"
@python_app
def py_mpi(parsl_resource_specification={}):
from mpi4py import MPI
return MPI.COMM_WORLD.Get_size(), MPI.COMM_WORLD.Get_rank()
print(py_mpi(parsl_resource_specification={"num_tasks": 6}).result())
parsl.clear()
- Dominant language
- Python
- Stars
- 77
- Forks
- 7
- Avg merge
- 10h 32m
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pyiron/executorlib
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pyiron/executorlib#1054 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pyiron/executorlib#1032 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pyiron/executorlib#1005 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
pyiron/executorlib#1049 · 1 comment ·
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 35/100
pyiron/executorlib#999 · 1 comment ·
All issues in pyiron/executorlib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·