Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Third Party Software
-
Labels:None
-
Story Points:2
-
Team:Architecture
Description
mpi4py 2 does not build with python3.7. Update to v3.0.0.
Attachments
Activity
I have no idea how to do that. ci_lsst is using MPI but I've never run anything outside of my laptop or lsst_dev and I wouldn't know where to start on doing the test you ask.
Hsin-Fang Chiang can correct any minor details I'm missing from not being familiar with the LSST cluster, but it would be something like:
singleFrameDriver.py /datasets/hsc/repo --calib /datasets/hsc/calib/20180117 --output /scratch/somewhere --id visit=1248 --batch-type slurm --job mpiTest --time 600 --cores 48
|
Paul Price
added a comment - Hsin-Fang Chiang can correct any minor details I'm missing from not being familiar with the LSST cluster, but it would be something like:
singleFrameDriver.py /datasets/hsc/repo --calib /datasets/hsc/calib/20180117 --output /scratch/somewhere --id visit=1248 --batch-type slurm --job mpiTest --time 600 --cores 48
I ran a few singleFrameDriver using this ticket branch + w_2019_05 with multiple nodes on verification cluster, and the execution went fine as far as I can tell from the logs.
Hsin-Fang Chiang
added a comment - I ran a few singleFrameDriver using this ticket branch + w_2019_05 with multiple nodes on verification cluster, and the execution went fine as far as I can tell from the logs. Thank you for testing.
ci_hsc doesn't really exercise mpi4py. I would feel much better if, before merging, you had actually run an image on the cluster.