Parallel lattice_track bugfix and help #675
Conversation
|
As a side comment, the default 'spawn' is non fonctionnal on MAC architectures. This had already been discussed but is still an issue in my opinion. |
I have been working 90% on macOS for years, using 3 different machines, several macOS versions and python versions, and I have never been able to reproduce the problem. I also googled for problems with So I think that the problem is in the installation of python or AT, or in some configuration. I suggest that if @simoneliuzzo can reproduce the problem, I may have a look at his setup. Also, be aware that starting at python 3.13 (the next one), "spawn" will be the default on all platforms. This may be a sign that "fork" may disappear in some time. Better make sure that "spawn" works! |
| @@ -30,6 +30,7 @@ class _Dst(object): | |||
| OrbMaxIter = 20 # Max. number of iterations for orbit | |||
| omp_num_threads = int(os.environ.get('OMP_NUM_THREADS', '0')) | |||
| patpass_poolsize = multiprocessing.cpu_count() | |||
| patpass_startmethod = None | |||
There was a problem hiding this comment.
Could you document the new patpass_startmethod option in the docstring of DConstant, a few lines later?
Well I have tried the spawn method on a MAC at home and on Linux at ESRF and both failed, I am quite surprised that it works for you in fact... you are probably the only person that know for whom it works. |
Done |
This answers #673 raised by @simoneliuzzo.
The arguments pool_size and start_method were not correctly documented for the new tracking interface.
These were also not correctly handled in the new interface, leading to possible errors when set while use_mp=False.
A variable was added to at.lattice.DConstant to set the start_method at the top level.