You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would help to have the intended-to-be-unique-per-run file names include hostname and process id information to reduce the chance of namespace collisions. I see Matlab includes a getpid function (https://www.mathworks.com/help/symbolic/mupad_ref/getpid.html). Another option is to create a unique "work" directory within the user specified temp_dir or dir_scratch for each run - then you don't need to worry about unique names within the run "work" directory.
@davidackerman - I'm hoping you might get the chance to address this at some point but it is not critical since I've worked around it for now.
The text was updated successfully, but these errors were encountered:
The usage of randi here:
https://github.com/khaledkhairy/EM_aligner/blob/master/renderer_api/load_all_transformations.m#L10
causes problems when I run concurrent compiled solve_montage_SL processes on the same cluster node. Apparently, compiled Matlab binaries bake in the random generator seed so concurrent runs will get the same sequence of "random" numbers (see https://www.mathworks.com/matlabcentral/answers/104306-why-does-my-compiled-rand-function-give-the-same-values-every-time-i-run-my-matlab-generated-standal).
It would help to have the intended-to-be-unique-per-run file names include hostname and process id information to reduce the chance of namespace collisions. I see Matlab includes a getpid function (https://www.mathworks.com/help/symbolic/mupad_ref/getpid.html). Another option is to create a unique "work" directory within the user specified temp_dir or dir_scratch for each run - then you don't need to worry about unique names within the run "work" directory.
@davidackerman - I'm hoping you might get the chance to address this at some point but it is not critical since I've worked around it for now.
The text was updated successfully, but these errors were encountered: