smartsim

SmartSim Infrastructure Library.

https://github.com/craylabs/smartsim

Science Score: 77.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 4 DOI reference(s) in README
  • Academic publication links
    Links to: arxiv.org, sciencedirect.com
  • Committers with academic emails
    2 of 30 committers (6.7%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.4%) to scientific vocabulary

Keywords

hpc machine-learning simulation workflow
Last synced: 6 months ago · JSON representation ·

Repository

SmartSim Infrastructure Library.

Basic Info
  • Host: GitHub
  • Owner: CrayLabs
  • License: bsd-2-clause
  • Language: Python
  • Default Branch: develop
  • Homepage:
  • Size: 32.7 MB
Statistics
  • Stars: 250
  • Watchers: 6
  • Forks: 37
  • Open Issues: 63
  • Releases: 0
Topics
hpc machine-learning simulation workflow
Created over 5 years ago · Last pushed 6 months ago
Metadata Files
Readme Contributing License Citation

README.md



Home    Install    Documentation    Cray Labs    Contact    Join us on Slack!   


[![License](https://img.shields.io/github/license/CrayLabs/SmartSim)](https://github.com/CrayLabs/SmartSim/blob/master/LICENSE.md) ![GitHub last commit](https://img.shields.io/github/last-commit/CrayLabs/SmartSim) ![GitHub deployments](https://img.shields.io/github/deployments/CrayLabs/SmartSim/github-pages?label=doc%20build) ![PyPI - Wheel](https://img.shields.io/pypi/wheel/smartsim) ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/smartsim) ![GitHub tag (latest by date)](https://img.shields.io/github/v/tag/CrayLabs/SmartSim) ![Language](https://img.shields.io/github/languages/top/CrayLabs/SmartSim) [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black) [![codecov](https://codecov.io/gh/CrayLabs/SmartSim/branch/develop/graph/badge.svg?token=96HFI2F45E)](https://codecov.io/gh/CrayLabs/SmartSim) [![Downloads](https://static.pepy.tech/personalized-badge/smartsim?period=total&units=international_system&left_color=grey&right_color=orange&left_text=Downloads)](https://pepy.tech/project/smartsim)

SmartSim

SmartSim is made up of two parts 1. SmartSim Infrastructure Library (This repository) 2. SmartRedis

The two library components are designed to work together, but can also be used independently.

SmartSim is a workflow library that makes it easier to use common Machine Learning (ML) libraries, like PyTorch and TensorFlow, in High Performance Computing (HPC) simulations and applications. SmartSim launches ML infrastructure on HPC systems alongside user workloads.

SmartRedis provides an API to connect HPC workloads, particularly (MPI + X) simulations, to the ML infrastructure, namely the The Orchestrator database, launched by SmartSim.

Applications integrated with the SmartRedis clients, written in Fortran, C, C++ and Python, can send data to and remotely request SmartSim infrastructure to execute ML models and scripts on GPU or CPU. The distributed Client-Server paradigm allows for data to be seamlessly exchanged between applications at runtime without the utilization of MPI.


Table of Contents - SmartSim - Quick Start - SmartSim Infrastructure Library - Experiments - Hello World - Hello World MPI - Experiments on HPC Systems - Interactive Launch Example - Batch Launch Examples - Infrastructure Library Applications - Redis + RedisAI - Local Launch - Interactive Launch - Batch Launch - SmartRedis - Tensors - Datasets - SmartSim + SmartRedis Tutorials - Run the Tutorials - Online Analysis - Lattice Boltzmann Simulation - Online Processing - Singular Value Decomposition - Online Inference - PyTorch CNN Example - Publications - Cite - bibtex


Quick Start

The documentation has a number of tutorials that make it easy to get used to SmartSim locally before using it on your system. Each tutorial is a Jupyter notebook that can be run through the SmartSim Tutorials docker image which will run a jupyter lab with the tutorials, SmartSim, and SmartRedis installed.

```bash docker pull ghcr.io/craylabs/smartsim-tutorials:latest docker run -p 8888:8888 ghcr.io/craylabs/smartsim-tutorials:latest

click on link to open jupyter lab

```

SmartSim Infrastructure Library

The Infrastructure Library (IL), the smartsim python package, facilitates the launch of Machine Learning and simulation workflows. The Python interface of the IL creates, configures, launches and monitors applications.

Experiments

The Experiment object is the main interface of SmartSim. Through the Experiment users can create references to user applications called Models.

Hello World

Below is a simple example of a workflow that uses the IL to launch hello world program using the local launcher which is designed for laptops and single nodes.

```python from smartsim import Experiment

exp = Experiment("simple", launcher="local")

settings = exp.createrunsettings("echo", exeargs="Hello World") model = exp.createmodel("hello_world", settings)

exp.start(model, block=True) print(exp.get_status(model)) ```

Hello World MPI

The Experiment.createrunsettings method returns a RunSettings object which defines how a model is launched. There are many types of RunSettings supported by SmartSim.

  • RunSettings
  • MpirunSettings
  • SrunSettings
  • AprunSettings

The following example launches a hello world MPI program using the local launcher for single compute node, workstations and laptops.

```Python from smartsim import Experiment

exp = Experiment("helloworld", launcher="local") mpisettings = exp.createrunsettings(exe="echo", exeargs="Hello World!", runcommand="mpirun") mpisettings.settasks(4)

mpimodel = exp.createmodel("helloworld", mpisettings)

exp.start(mpimodel, block=True) print(exp.getstatus(model)) ```

If an argument of run_command="auto" (the default) is passed to Experiment.create_run_settings, SmartSim will attempt to find a run command on the system with which it has a corresponding RunSettings class. If one can be found, Experiment.create_run_settings will instance and return an object of that type.


Experiments on HPC Systems

SmartSim integrates with common HPC schedulers providing batch and interactive launch capabilities for all applications:

  • Slurm
  • SGE
  • PBSPro
  • Local (for laptops/single node, no batch)

In addition, on Slurm and PBS systems, Dragon can be used as a launcher. Please refer to the documentation for instructions on how to insall it on your system and use it in SmartSim.

Interactive Launch Example

The following launches the same hello_world model in an interactive allocation.

```bash

get interactive allocation (Slurm)

salloc -N 3 --ntasks-per-node=20 --ntasks 60 --exclusive -t 00:10:00

get interactive allocation (PBS)

qsub -l select=3:ncpus=20 -l walltime=00:10:00 -l place=scatter -I -q

```

This same script will run on a SLURM, PBS, or SGE system as the launcher is set to auto in the Experiment initialization. The run command like mpirun, aprun or srun will be automatically detected from what is available on the system.

```python

hello_world.py

from smartsim import Experiment

exp = Experiment("helloworldexp", launcher="auto") run = exp.createrunsettings(exe="echo", exeargs="Hello World!") run.settasks(60) run.settasksper_node(20)

model = exp.createmodel("helloworld", run) exp.start(model, block=True, summary=True)

print(exp.get_status(model)) bash

in interactive terminal

python hello_world.py ```

This script could also be launched in a batch file instead of an interactive terminal. For example, for Slurm:

```bash

!/bin/bash

SBATCH --exclusive

SBATCH --nodes=3

SBATCH --ntasks-per-node=20

SBATCH --time=00:10:00

python /path/to/hello_world.py bash

on Slurm system

sbatch runhelloworld.sh ```

Batch Launch Examples

SmartSim can also launch workloads in a batch directly from Python, without the need for a batch script. Users can launch groups of Model instances in a Ensemble.

The following launches 4 replicas of the the same hello_world model.

```python

hello_ensemble.py

from smartsim import Experiment

exp = Experiment("helloworldbatch", launcher="auto")

define resources for all ensemble members

batch = exp.createbatchsettings(nodes=4, time="00:10:00", account="12345-Cray") batch.set_queue("premium")

define how each member should run

run = exp.createrunsettings(exe="echo", exeargs="Hello World!") run.settasks(60) run.settasksper_node(20)

ensemble = exp.createensemble("helloworld", batchsettings=batch, runsettings=run, replicas=4) exp.start(ensemble, block=True, summary=True)

print(exp.get_status(ensemble)) ```

bash python hello_ensemble.py

Similar to the interactive example, this same script will run on a SLURM, PBS, or SGE system as the launcher is set to auto in the Experiment initialization. Local launching does not support batch workloads.


Infrastructure Library Applications

  • Orchestrator - In-memory data store and Machine Learning Inference (Redis + RedisAI)

Redis + RedisAI

The Orchestrator is an in-memory database that utilizes Redis and RedisAI to provide a distributed database and access to ML runtimes from Fortran, C, C++ and Python.

SmartSim provides classes that make it simple to launch the database in many configurations and optionally form a distributed database cluster. The examples below will show how to launch the database. Later in this document we will show how to use the database to perform ML inference and processing.

Local Launch

The following script launches a single database using the local launcher.

Experiment.create_database will initialize an Orchestrator instance corresponding to the specified launcher.

```python

rundblocal.py

from smartsim import Experiment

exp = Experiment("local-db", launcher="local") db = exp.create_database(port=6780, # database port interface="lo") # network interface to use

by default, SmartSim never blocks execution after the database is launched.

exp.start(db)

launch models, analysis, training, inference sessions, etc

that communicate with the database using the SmartRedis clients

stop the database

exp.stop(db) ```

Interactive Launch

The Orchestrator, like Ensemble instances, can be launched locally, in interactive allocations, or in a batch.

The following example launches a distributed (3 node) database cluster in an interactive allocation.

```bash

get interactive allocation (Slurm)

salloc -N 3 --ntasks-per-node=1 --exclusive -t 00:10:00

get interactive allocation (PBS)

qsub -l select=3:ncpus=1 -l walltime=00:10:00 -l place=scatter -I -q queue

```

```python

run_db.py

from smartsim import Experiment

auto specified to work across launcher types

exp = Experiment("db-on-slurm", launcher="auto") dbcluster = exp.createdatabase(dbnodes=3, dbport=6780, batch=False, interface="ipogif0") exp.start(db_cluster)

print(f"Orchestrator launched on nodes: {db_cluster.hosts}")

launch models, analysis, training, inference sessions, etc

that communicate with the database using the SmartRedis clients

exp.stop(db_cluster) bash

in interactive terminal

python run_db.py ```

Batch Launch

The Orchestrator can also be launched in a batch without the need for an interactive allocation. SmartSim will create the batch file, submit it to the batch system, and then wait for the database to be launched. Users can hit CTRL-C to cancel the launch if needed.

```Python

rundbbatch.py

from smartsim import Experiment

exp = Experiment("batch-db-on-pbs", launcher="auto") dbcluster = exp.createdatabase(dbnodes=3, dbport=6780, batch=True, time="00:10:00", interface="ib0", account="12345-Cray", queue="cl40")

exp.start(db_cluster)

print(f"Orchestrator launched on nodes: {db_cluster.hosts}")

launch models, analysis, training, inference sessions, etc

that communicate with the database using the SmartRedis clients

exp.stop(db_cluster) ```

bash python run_db_batch.py


SmartRedis

The SmartSim IL Clients (SmartRedis) are implementations of Redis clients that implement the RedisAI API with additions specific to scientific workflows.

SmartRedis clients are available in Fortran, C, C++, and Python. Users can seamlessly pull and push data from the Orchestrator from different languages.

Tensors

Tensors are the fundamental data structure for the SmartRedis clients. The Clients use the native array format of the language. For example, in Python, a tensor is a NumPy array while the C/C++ clients accept nested and contiguous arrays.

When stored in the database, all tensors are stored in the same format. Hence, any language can receive a tensor from the database no matter what supported language the array was sent from. This enables applications in different languages to communicate numerical data with each other at runtime.

For more information on the tensor data structure, see the documentation

Datasets

Datasets are collections of Tensors and associated metadata. The Dataset class is a user space object that can be created, added to, sent to, and retrieved from the Orchestrator.

For an example of how to use the Dataset class, see the Online Analysis example

For more information on the API, see the API documentation

SmartSim + SmartRedis Tutorials

SmartSim and SmartRedis were designed to work together. When launched through SmartSim, applications using the SmartRedis clients are directly connected to any Orchestrator launched in the same Experiment.

In this way, a SmartSim Experiment becomes a driver for coupled ML and Simulation workflows. The following are simple examples of how to use SmartSim and SmartRedis together.

Run the Tutorials

Each tutorial is a Jupyter notebook that can be run through the SmartSim Tutorials docker image which will run a jupyter lab with the tutorials, SmartSim, and SmartRedis installed.

bash docker pull ghcr.io/craylabs/smartsim-tutorials:latest docker run -p 8888:8888 ghcr.io/craylabs/smartsim-tutorials:latest Each of the following examples can be found in the SmartSim documentation.

Online Analysis

Using SmartSim, HPC applications can be monitored in real time by streaming data from the application to the database. SmartRedis clients can retrieve the data, process, analyze it, and finally store any updated data back to the database for use by other clients.

The following is an example of how a user could monitor and analyze a simulation. The example here uses the Python client; however, SmartRedis clients are also available for C, C++, and Fortran. All SmartRedis clients implement the same API.

The example will produce this visualization while the simulation is running.

Lattice Boltzmann Simulation

Using a Lattice Boltzmann Simulation, this example demonstrates how to use the SmartRedis Dataset API to stream data over the Orchestrator deployed by SmartSim.

The simulation will be composed of two parts: fv_sim.py which will generate data from the Simulation and store it in the Orchestrator, and driver.py which will launch the Orchestrator, start fv_sim.py and check for data posted to the Orchestrator to plot updates in real-time.

The following code highlights the sections of fv_sim.py that are responsible for transmitting the data needed to plot timesteps of the simulation to the Orchestrator.

```Python

fv_sim.py

from smartredis import Client import numpy as np

initialization code omitted

save cylinder location to database

cylinder = (X - xres/4)**2 + (Y - yres/2)2 < (y_res/4)2 # bool array client.put_tensor("cylinder", cylinder.astype(np.int8))

for time_step in range(steps): # simulation loop for i, cx, cy in zip(idxs, cxs, cys): F[:,:,i] = np.roll(F[:,:,i], cx, axis=1) F[:,:,i] = np.roll(F[:,:,i], cy, axis=0)

bndryF = F[cylinder,:]
bndryF = bndryF[:,[0,5,6,7,8,1,2,3,4]]

rho = np.sum(F, 2)
ux  = np.sum(F * cxs, 2) / rho
uy  = np.sum(F * cys, 2) / rho

Feq = np.zeros(F.shape)
for i, cx, cy, w in zip(idxs, cxs, cys, weights):
    Feq[:,:,i] = rho * w * ( 1 + 3*(cx*ux+cy*uy)  + 9*(cx*ux+cy*uy)**2/2 - 3*(ux**2+uy**2)/2 )
F += -(1.0/tau) * (F - Feq)
F[cylinder,:] = bndryF

# Create a SmartRedis dataset with vorticity data
dataset = Dataset(f"data_{str(time_step)}")
dataset.add_tensor("ux", ux)
dataset.add_tensor("uy", uy)

# Put Dataset in db at key "data_{time_step}"
client.put_dataset(dataset)

```

The driver script, driver.py, launches the Orchestrator database and runs the simulation in a non-blocking fashion. The driver script then uses the SmartRedis client to pull the DataSet and plot the vorticity while the simulation is running.

```Python

driver.py

time_steps, seed = 3000, 42

exp = Experiment("finitevolumesimulation", launcher="local")

db = exp.create_database(port=6780, # database port interface="lo") # network interface db should listen on

create the lb simulation Model reference

settings = exp.createrunsettings("python", exeargs=["fvsim.py", f"--seed={seed}", f"--steps={timesteps}"]) model = exp.createmodel("fvsimulation", settings) model.attachgeneratorfiles(tocopy="fv_sim.py") exp.generate(db, model, overwrite=True)

exp.start(db) client = Client(address=db.get_address()[0], cluster=False)

start simulation (non-blocking)

exp.start(model, block=False, summary=True)

poll until simulation starts and then retrieve data

client.pollkey("cylinder", 200, 100) cylinder = client.gettensor("cylinder").astype(bool)

for i in range(0, timesteps): client.pollkey(f"data{str(i)}", 10, 1000) dataset = client.getdataset(f"data{str(i)}") ux, uy = dataset.gettensor("ux"), dataset.get_tensor("uy")

# analysis/plotting code omitted

exp.stop(db) ```

For more examples of how to use SmartSim and SmartRedis together to perform online analysis, please see the online analsysis tutorial section of the SmartSim documentation.

Online Processing

Each of the SmartRedis clients can be used to remotely execute TorchScript code on data stored within the database. The scripts/functions are executed in the Torch runtime linked into the database.

Any of the functions available in the TorchScript builtins can be saved as "script" or "functions" in the database and used directly by any of the SmartRedis Clients.

Singular Value Decomposition

For example, the following code sends the built-in Singular Value Decomposition to the database and execute it on a dummy tensor.

```python import numpy as np from smartredis import Client

don't even need to import torch

def calcsvd(inputtensor): return input_tensor.svd()

connect a client to the database

client = Client(cluster=False)

get dummy data

tensor = np.random.randint(0, 100, size=(5, 3, 2)).astype(np.float32)

client.puttensor("input", tensor) client.setfunction("svd", calc_svd)

client.runscript("svd", "calcsvd", "input", ["U", "S", "V"])

results are not retrieved immediately in case they need

to be fed to another function/model

U = client.gettensor("U") S = client.gettensor("S") V = client.get_tensor("V") print(f"U: {U}, S: {S}, V: {V}") ```

The processing capabilities make it simple to form computational pipelines of functions, scripts, and models.

See the full TorchScript Language Reference documentation for more information on available methods, functions, and how to create your own.

Online Inference

Where available, SmartSim supports the following frameworks for querying Machine Learning models from C, C++, Fortran and Python with the SmartRedis Clients:

RedisAI Version Libraries Supported Version
1.2.7 PyTorch 2.7.1
TensorFlow\Keras 2.16.2
ONNX Runtime 1.17.3

A number of other libraries are supported through ONNX, like SciKit-Learn and XGBoost.

A more detailed breakdown of supported toolkit versions for different platforms is available in the installation section of the documentation.

Note: It's important to remember that SmartSim utilizes a client-server model. To run experiments that utilize the above frameworks, you must first start the Orchestrator database with SmartSim.

PyTorch CNN Example

The example below shows how to spin up a database with SmartSim and invoke a PyTorch CNN model using the SmartRedis clients.

```python

simpletorchinference.py

import io import torch import torch.nn as nn from smartredis import Client from smartsim import Experiment

exp = Experiment("simple-online-inference", launcher="local") db = exp.create_database(port=6780, interface="lo")

class Net(nn.Module): def init(self): super().init() self.conv = nn.Conv2d(1, 1, 3)

def forward(self, x):
    return self.conv(x)

torchmodel = Net() exampleforwardinput = torch.rand(1, 1, 3, 3) module = torch.jit.trace(torchmodel, exampleforwardinput) modelbuffer = io.BytesIO() torch.jit.save(module, modelbuffer)

exp.start(db, summary=True)

address = db.get_address()[0] client = Client(address=address, cluster=False)

client.puttensor("input", exampleforwardinput.numpy()) client.setmodel("cnn", modelbuffer.getvalue(), "TORCH", device="CPU") client.runmodel("cnn", inputs=["input"], outputs=["output"]) output = client.get_tensor("output") print(f"Prediction: {output}")

exp.stop(db) ```

The above python code can be run like any normal python script: bash python simple_torch_inference.py

For more examples of how to use SmartSim and SmartRedis together to perform online inference, please see the online inference tutorials section of the SmartSim documentation.


Publications

The following are public presentations or publications using SmartSim


Cite

Please use the following citation when referencing SmartSim, SmartRedis, or any SmartSim related work:

Partee et al., “Using Machine Learning at Scale in HPC Simulations with SmartSim: An Application to Ocean Climate Modeling”, Journal of Computational Science, Volume 62, 2022, 101707, ISSN 1877-7503

Available: https://doi.org/10.1016/j.jocs.2022.101707.

bibtex

latex @article{PARTEE2022101707, title = {Using Machine Learning at scale in numerical simulations with SmartSim: An application to ocean climate modeling}, journal = {Journal of Computational Science}, volume = {62}, pages = {101707}, year = {2022}, issn = {1877-7503}, doi = {https://doi.org/10.1016/j.jocs.2022.101707}, url = {https://www.sciencedirect.com/science/article/pii/S1877750322001065}, author = {Sam Partee and Matthew Ellis and Alessandro Rigazzi and Andrew E. Shao and Scott Bachman and Gustavo Marques and Benjamin Robbins}, keywords = {Deep learning, Numerical simulation, Climate modeling, High performance computing, SmartSim}, }

Owner

  • Name: Cray Labs
  • Login: CrayLabs
  • Kind: organization

Citation (CITATION.cff)

cff-version: 1.1.0
authors:
  - family-names: Partee
    given-names: Sam
    orcid: https://orcid.org/0000-0001-6005-5116
    email: spartee@hpe.com
  - family-names: Ellis
    given-names: Matthew
    orcid: https://orcid.org/0000-0002-5782-5447
  - family-names: Rigazzi
    given-names: Alessandro
    orcid: https://orcid.org/0000-0003-2132-7726
  - family-names: Bachman
    given-names: Scott
    orcid: https://orcid.org/0000-0002-6479-4300
  - family-names: Marques
    given-names: Gustavo
    orcid: https://orcid.org/0000-0001-7238-0290
  - family-names: Shao
    given-names: Andrew
    orcid: https://orcid.org/0000-0003-3658-512X
  - family-names: Benjamin
    given-names: Robbins
    orcid: https://orcid.org/0000-0003-3658-512X

title: "Using Machine Learning at Scale in HPC Simulations with SmartSim: An Application to Ocean Climate Modeling"
doi: 10.5281/zenodo.4682270
date-released: 2021-4-12
license: "BSD-2-Clause"

GitHub Events

Total
  • Issues event: 11
  • Watch event: 17
  • Issue comment event: 33
  • Push event: 43
  • Pull request review comment event: 287
  • Pull request review event: 267
  • Pull request event: 55
  • Fork event: 1
  • Create event: 3
Last Year
  • Issues event: 11
  • Watch event: 17
  • Issue comment event: 33
  • Push event: 43
  • Pull request review comment event: 287
  • Pull request review event: 267
  • Pull request event: 55
  • Fork event: 1
  • Create event: 3

Committers

Last synced: over 1 year ago

All Time
  • Total Commits: 990
  • Total Committers: 30
  • Avg Commits per committer: 33.0
  • Development Distribution Score (DDS): 0.757
Past Year
  • Commits: 150
  • Committers: 11
  • Avg Commits per committer: 13.636
  • Development Distribution Score (DDS): 0.793
Top Committers
Name Email Commits
Sam Partee s****e@h****m 241
Al Rigazzi a****i@h****m 158
Sam Partee P****1@g****m 90
Sam Partee p****1@g****m 73
Matt Drozt d****t@h****m 63
Audrey Pratt 9****e 38
EricGustin e****4@g****m 38
Sam Partee s****e@c****m 34
Andrew Shao a****o@h****m 30
Chris McBride 3****a 29
amandarichardsonn 3****n 28
Matthew Ellis m****s@c****m 26
Alessandro Rigazzi a****i@c****m 26
Matt Ellis m****3 18
Jim Edwards j****s@u****u 14
Andrew Shao a****o@c****m 12
Eric Gustin 3****n 11
Celia Tandon c****n@h****m 10
Bill Scherer 3****i 9
Julia Putko 8****o 8
Alyssa Cote 4****e 7
Ben Albrecht b****t 6
Soohhoon Choi s****i@c****m 5
Al Rigazzi a****i@h****m 5
Matt Ellis m****s@h****m 4
Riccardo Balin r****n@c****u 2
Benjamin Robbins b****s@h****m 2
Soohoo Choi s****i@h****m 1
Marius Kurz 8****z 1
Sam Partee s****e@o****m 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 117
  • Total pull requests: 462
  • Average time to close issues: 3 months
  • Average time to close pull requests: 10 days
  • Total issue authors: 22
  • Total pull request authors: 16
  • Average comments per issue: 0.65
  • Average comments per pull request: 1.04
  • Merged pull requests: 369
  • Bot issues: 0
  • Bot pull requests: 3
Past Year
  • Issues: 18
  • Pull requests: 75
  • Average time to close issues: 12 days
  • Average time to close pull requests: 7 days
  • Issue authors: 9
  • Pull request authors: 10
  • Average comments per issue: 0.33
  • Average comments per pull request: 0.88
  • Merged pull requests: 38
  • Bot issues: 0
  • Bot pull requests: 2
Top Authors
Issue Authors
  • ashao (27)
  • al-rigazzi (25)
  • MattToast (22)
  • amandarichardsonn (11)
  • juliaputko (6)
  • mellis13 (5)
  • Spartee (5)
  • b-fg (4)
  • AlyssaCote (4)
  • billschereriii (2)
  • syedalihasany (2)
  • ankona (2)
  • TomMelt (1)
  • SJaffa (1)
  • p3jitnath (1)
Pull Request Authors
  • ankona (137)
  • MattToast (104)
  • amandarichardsonn (98)
  • juliaputko (97)
  • al-rigazzi (95)
  • ashao (71)
  • AlyssaCote (55)
  • mellis13 (21)
  • billschereriii (10)
  • github-actions[bot] (6)
  • rickybalin (4)
  • ben-albrecht (3)
  • jsta (2)
  • FoamScience (2)
  • EricGustin (1)
Top Labels
Issue Labels
type: feature (45) area: launcher (18) area: build (16) type: refactor (12) area: api (12) bug: minor (10) area: CI/CD (10) type: usability (10) type: bug (8) User Issue (8) repo: smartsim (7) area: orchestrator (6) area: Dragon (6) area: ML (6) type: chore (6) area: third-party (5) bug: major (5) Epic (5) API break (5) area: docs (5) area: test (4) area: job (4) short task (3) Short task (3) good first issue (3) area: generation (2) bug: critical (2) help wanted (1) area: telemetry (1) area: settings (1)
Pull Request Labels
ignore-for-release (62) area: CI/CD (27) bug: minor (26) type: feature (26) type: refactor (24) area: api (23) area: test (22) area: launcher (22) area: build (22) type: usability (21) area: docs (21) repo: smartsim (18) non-user-facing (14) type: chore (12) short task (11) API break (10) area: third-party (9) area: Dragon (9) area: settings (9) bug: major (9) area: release (8) area: orchestrator (8) area: ML (6) area: job (6) area: python (5) area: telemetry (5) area: generation (4) type: design (3) area: workload manager (2) Short task (2)

Packages

  • Total packages: 1
  • Total downloads:
    • pypi 446 last-month
  • Total docker downloads: 101,707
  • Total dependent packages: 0
  • Total dependent repositories: 1
  • Total versions: 12
  • Total maintainers: 2
pypi.org: smartsim

AI Workflows for Science

  • Versions: 12
  • Dependent Packages: 0
  • Dependent Repositories: 1
  • Downloads: 446 Last month
  • Docker Downloads: 101,707
Rankings
Docker downloads count: 4.1%
Stargazers count: 5.2%
Forks count: 6.8%
Dependent packages count: 10.1%
Average: 10.5%
Downloads: 15.2%
Dependent repos count: 21.5%
Maintainers (2)
Last synced: 6 months ago

Dependencies

doc/requirements-doc.txt pypi
  • breathe ==4.31.0
  • docutils ==0.17
  • ipython *
  • jinja2 ==3.0.3
  • nbsphinx >=0.8.2
  • sphinx ==4.4.0
  • sphinx-book-theme ==0.2.0
  • sphinx-fortran ==1.1.1
  • tensorflow ==2.5.2
  • torch ==1.7.1
requirements-dev.txt pypi
  • black >=20.8b1
  • click ==8.0.2
  • coloredlogs ==10.0
  • filelock >=3.4.2
  • isort >=5.6.4
  • psutil >=5.7.2
  • pylint >=2.6.0
  • pytest >=6.0.0
  • pytest-cov >=2.10.1
  • redis ==3.5.3
  • redis-py-cluster ==2.1.3
  • smartredis >=0.3.1
  • tabulate >=0.8.9
  • tqdm >=4.50.2
requirements.txt pypi
  • coloredlogs ==10.0
  • filelock >=3.4.2
  • protobuf ==3.20
  • psutil >=5.7.2
  • redis ==3.5.3
  • redis-py-cluster ==2.1.3
  • smartredis >=0.3.1
  • tabulate >=0.8.9
  • tqdm >=4.50.2
.github/workflows/build_docs.yml actions
  • actions/checkout v2 composite
  • ad-m/github-push-action v0.6.0 composite
.github/workflows/release.yml actions
  • actions/checkout v2 composite
  • actions/download-artifact v2 composite
  • actions/setup-python v2 composite
  • actions/upload-artifact v2 composite
  • pypa/gh-action-pypi-publish release/v1 composite
.github/workflows/run_tests.yml actions
  • actions/checkout v2 composite
  • actions/setup-python v2 composite
  • codecov/codecov-action v2 composite
docker/dev/Dockerfile docker
  • ubuntu 20.04 build
docker/docs/dev/Dockerfile docker
  • ubuntu 20.04 build
docker/prod/Dockerfile docker
  • ubuntu 20.04 build
docker/testing/Dockerfile docker
  • ubuntu 21.10 build
docker-compose.yml docker
  • smartsim-docs dev-latest
  • smartsim-tutorials dev-latest
  • smartsim-tutorials v0.4.1