-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPF Parallelization fails #687
Comments
Unfortunately, I don't think this is as simple as setting |
I don't think this is related to copy-on-write behavior (though I could be wrong). A potentially important difference is that in the SSB PR each worker is writing its results into the shared array, while in WPF the worker functions |
To clarify what I meant, simply adding Essentially, your comment just above it will no longer be true. # hopefully the data entries remain as views until dispatch time...
fit_inputs = ... That might be fine for WPF (which anyway has a slow runtime, and initialization might be negligible), but this was not the case for SSB in my tests. |
There have been reports of the
mpire
distributed WPF optimization failing with errors likeThis appears to only affect Windows systems.
I think the fix is to enable
dill
serialization:py4DSTEM/py4DSTEM/process/wholepatternfit/wpf.py
Lines 748 to 753 in 1137637
should be modified to become:
mpire
produces threads differently on Windows vs UNIX and so there can be serialization errors that only show up one one platform when transmitting complicated objects to threads. Unfortunately I do not have a Windows machine to test this on at the moment, so someone else will have to try this and let us know.The text was updated successfully, but these errors were encountered: