Regularly the software stops when an problematic file is in the folder to analyze. When LCT encounters such an error, it stops... That is horrible for large datasets. Perhaps a way around this issue can be programmed, giving a summary of all major errors after the entire Batch is processed?
(Some real samples sets may include blanks, which may not align properly. Running the entire batch could be a repetitive struggle now.)
Regularly the software stops when an problematic file is in the folder to analyze. When LCT encounters such an error, it stops... That is horrible for large datasets. Perhaps a way around this issue can be programmed, giving a summary of all major errors after the entire Batch is processed? (Some real samples sets may include blanks, which may not align properly. Running the entire batch could be a repetitive struggle now.)