When LATTE encounters error (at least in batch mode), it indicated it failed to complete, without any further explanation. Users thus cannot tell whether the error is due to bugs that he/she cannot fix, or is due to issues that he/she can fix (problem with the input csv, network failures, etc.)
E.g., this is an excerpt of the output
|===========================================| 1.8M/1.8M (100.00%) 8s
done.
Nearest neighbour plot... done.
Running BLS algorithm... Detrend data prior to BLS analysis... done.
TIC 82121827 failed to complete. Continue anyway. You can find a list of the failed IDs stored in the output folder.
I suspect in this case it might be some bugs in LATTE, as the output indicated that the analysis of the TIC is almost done (maybe issues related to running BLS?)
For the above case TIC 82121827 in sector 9, I believed the error happened during the second run of BLS (or right before that), as the last file generated is the first BLS run plot.
When LATTE encounters error (at least in batch mode), it indicated it failed to complete, without any further explanation. Users thus cannot tell whether the error is due to bugs that he/she cannot fix, or is due to issues that he/she can fix (problem with the input csv, network failures, etc.)
E.g., this is an excerpt of the output
I suspect in this case it might be some bugs in LATTE, as the output indicated that the analysis of the TIC is almost done (maybe issues related to running BLS?)
The input csv:
12 is another example, though it reports the specific case where the transit times in input csv are out of range.
workaround to obtain error
Run LATTE in interactive mode rather than batch mode. LATTE will then output the stacktrace of the error.