Issue running EMgetADP and EMEBSDDI on Windows with relatively large EBSD pattern

[IMBalENce]

Hello,

I tested a few EMsoft nightly build versions (5.0.20210101 up to 5.0.20210708) on Windows 10 Enterprise for indexing patterns from our two EBSD systems with no binning (480x480 from TSL and 640x480 from HKL). There seem to have some issue running EMgetADP and EMEBSDDI for both data when the number of threads is set to greater than 1 (The CPU has more than 4 cores so should be sufficient).

Running EMgetADP in CMD mode jump out the calculation right away (similar for EMEBSDDI)

Running EMgetADP in EMsoftWorkbench yield the follow error msg:

By setting the number of threads to 1 can get the calculation done correctly, but at significantly slower speed.

I also tested a few different values for the Pattern Size. It seems the program can accept the pattern sizes less than 420 pixels for both dimensions when the num of threads is set to >1. Below is a screen shot of the EMEBSDDIpreview result by using the top-left 300x300 pixels.

The EMEBSDDI program also crashes during indexing 480x480 pattern files from TSL even if binning 4 is set in the .nml file. EBSD maps with smaller pattern size works fine in both EMgetADP and EMEBSDDI with 10+ threads.

Would you have any idea what causes this? Thank you.

BR
ZX

[luqi-cloud]

I encountered the same issue in EMsoft-5.0.20200909.-Win64 in Win10 (ryzen 3960X 24 cores). Failed to use number of threads for parallel execution greater than 1. It generally take more than one day to index 50000 pattern using only one thread. But the result is correct.

Also, I failed to run EMEBSDDI using multiple GPUs .