flowpm

Particle Mesh Simulation in TensorFlow, based on fastpm-python simulations
To install:
$ pip install flowpm
For a minimal working example of FlowPM, see this notebook. The steps are as follows:
import tensorflow as tf
import numpy as np
import flowpm
stages = np.linspace(0.1, 1.0, 10, endpoint=True)
initial_conditions = flowpm.linear_field(32, # size of the cube
100, # Physical size of the cube
ipklin, # Initial power spectrum
batch_size=16)
# Sample particles
state = flowpm.lpt_init(initial_conditions, a0=0.1)
# Evolve particles down to z=0
final_state = flowpm.nbody(state, stages, 32)
# Retrieve final density field
final_field = flowpm.cic_paint(tf.zeros_like(initial_conditions), final_state[0])
Mesh TensorFlow implementation
FlowPM provides a Mesh TensorFlow implementation of FastPM, for running distributed simulations across very large supercomputers.
Here are the instructions for installing and running on Cori-GPU. More info about this machine here: https://docs-dev.nersc.gov/cgpu/
- Login to a cori-gpu node to prepare the environment:
$ module add esslurm
$ salloc -C gpu -N 1 -t 30 -c 10 --gres=gpu:1 -A m1759
- First install dependencies
$ module purge && module load gcc/7.3.0 python3 cuda/10.1.243
$ pip install --user tensorflow==2.1
$ pip install --user mesh-tensorflow
NOTE: we are installing our own tensorflow 2.1 version until a module is available at NERSC
- Install the Mesh TensorFlow branch of FlowPM
$ git clone https://github.com/modichirag/flowpm.git
$ cd flowpm
$ git checkout mesh
$ pip install --user -e .
- To run the demo comparing the distributed computation to single GPU:
$ cd examples
$ sbatch lpt_job.sh
This will generate a plot comparison.png showing from a set of initial
conditions, the result of a single LPT step on single GPU TensorFlow vs Mesh
TensorFlow.
TPU setup
To run FlowPM on Google TPUs here is the procedure
- Step 1: Setting up a cloud TPU in the desired zone, do from the GCP console:
$ gcloud config set compute/region europe-west4
$ gcloud config set compute/zone europe-west4-a
$ ctpu up --name=flowpm --tpu-size=v3-32
- Step 2: Installing dependencies and FlowPM:
$ git clone https://github.com/modichirag/flowpm.git
$ cd flowpm
$ git checkout mesh
$ pip3 install --user mesh-tensorflow
$ pip3 install --user -e .
It's so easy, it's almost criminal.
Notes on using and profiling for TPUs
There a few things to keep in mind when using TPUs, in particular, the section
on Excessive tensor padding from this document: https://cloud.google.com/tpu/docs/troubleshooting
See the README in the script folder for more info on how to profile
Metadata
Release files for flowpm 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| flowpm-0.1.1.tar.gz | 1.6 MB | Without provenance | Details |
Release files / flowpm-0.1.1.tar.gz
| Download URL | flowpm-0.1.1.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f926bd25d68b0240e9e466501734394506a073b2c52054f5cd89fd6f60f85e5
|
|
BLAKE2b-256 checksum How to use checksums |
6a0e3a7b8dc3dea612771696cad63063f725a85de63b3f680e86b3c3e456c500
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/54.0.0 requests-toolbelt/0.9.1 tqdm/4.58.0 CPython/3.7.10
|
Security for flowpm 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.