Closed vivek-bala closed 9 years ago
It seems to be an issue related to mpi4py when it tries to receive large numpy arrays, as described here: https://groups.google.com/forum/#!msg/mpi4py/OJG5eZ2f-Pg/EnhN06Ozg2oJ.
Hmmm.. did you also get the same error on Stampede with the recent version ?
Update from the discussion we had today with @vivek-bala . I have been able to reproduce the same error as @vivek-bala with the new version. However, it seems that the GROMACS/LSDMap pattern works fine using 16 cores instead of 64 cores (64 is the value specified by default in the file stampede.rcfg). Vivek reached the same conclusion and found that with 32, 64 cores, the error comes up. But not with 16.
Thanks for the update. What are the next steps to address this issue?
Can you please try to reproduce this with a regular PBS script? We need to see whether the problem lies one the ExTASY / Radical-Pilot, on the LSDMap or possibly on the Stampede end.
Have you opened a ticket with TACC?
Not that I am aware of. Maybe Vivek has opened one.
Could be related to #101
This is fixed now with /opt/apps/intel14/mvapich2_2_0/python/2.7.6/lib/python2.7/site-packages/mpi4py/bin/python-mpi.
@vivek-bala Hello,
May I know how you fixed it? We are also getting same error at our end.
Cheers, Samir Shaikh
hi @samcom12 - that ticket is quite a blast from the past! :-P
If my memory served correctly, the problem was resolved by TACC staff providing a new mpi4py
deployment. I do not know what was changed in that deployment, and I doubt that knowledge can be recovered at this point.