create new branch with simplified README and introduction #1002
Conversation
starting to deemph
…ensemble/libensemble into docs/README_welcome_simplify
README.rst
Outdated
| libEnsemble helps users take advantage of massively parallel resources to solve design, | ||
| decision, and inference problems and expands the class of problems that can benefit from | ||
| increased parallelism. | ||
| • **Adaptive ensembles**: Generate parallel tasks on-the-fly based on previous computations. |
There was a problem hiding this comment.
Heres my effort:
- Dynamic ensembles: Generate new tasks on-the-fly based on previous computations.
- Extreme scaling: Run identical scripts on or across_ laptops, clusters, and leadership-class machines.
- Dynamic resource management: Dynamically assign and reassign CPU/GPU resources to tasks.
- Application monitoring: Ensemble members can run, monitor, and cancel apps.
- Heterogeneous resources Automatic detection and correct assignment on Nvidia, AMD and Intel GPUs.
- Low start-up cost: No additional background services or processes required.
Thoughts?
There was a problem hiding this comment.
In Dynamic resources
we have dropped: "partitions of any size" (e.g. nodes) - which to my mind made clear it included nodes, but I'm guessing thats obvious already
There was a problem hiding this comment.
Coordinated data-flow between tasks - does this mean via the manager? I'm not sure about this one.
There was a problem hiding this comment.
Here's my effort:
Looks good! But I wonder if there's a way of combining the Dynamic resource management and Heterogeneous resources sections?
In Dynamic resources
Yeah, that's what I was thinking. Plus "nodes" is covered in my mind by "extreme scaling".
Coordinated data-flow between tasks - does this mean via the manager? I'm not sure about this one.
I'm trying to emphasize that the tasks don't exist independently, each in a "bubble" (which is the case for most multi-task workflow systems). They can communicate state with the manager and each other
There was a problem hiding this comment.
Oh yeah, I'm also trying to avoid redundant adjectives whenever possible.
| @@ -271,102 +82,14 @@ Resources | |||
| doi = {10.1109/tpds.2021.3082815} | |||
| } | |||
|
|
|||
| **Example Compatible Packages** | |||
There was a problem hiding this comment.
As we have community examples, we should prob have a link to that.
There was a problem hiding this comment.
Community Examples is still linked to on line 67 on the right
| - OPAL_ Object Oriented Parallel Accelerator Library. (See this `IPAC manuscript`_.) | ||
| - WarpX_ Advanced electromagnetic particle-in-cell code. (See example `WarpX + libE scripts`_.) | ||
|
|
||
| See a complete list of `example user scripts`_. |
There was a problem hiding this comment.
Is this link to examples somewhere (in quickstart)?
There was a problem hiding this comment.
Also we should check pdf still works okay.
Now it'll be easier to discuss changes to the README and rtd splash-page independent of other changes I'm making.
This doesn't have to come in for this release, maybe for 1.0