It has happenned to me that the program crashed during the creation of a .ppl file. Next time I started the program, it found the "existing" .ppl and tried to resume after it. This resulted in the annotation finishing normally, but with a lot of errors and missing values.
The right way to fix it would be tha PPLprocessor writes things incrementally in an .ppl.tmp file within the loop. When the loop is finished, it can rename the file to .ppl. This may be the case with other ResourceProcessors
It has happenned to me that the program crashed during the creation of a .ppl file. Next time I started the program, it found the "existing" .ppl and tried to resume after it. This resulted in the annotation finishing normally, but with a lot of errors and missing values.
The right way to fix it would be tha PPLprocessor writes things incrementally in an .ppl.tmp file within the loop. When the loop is finished, it can rename the file to .ppl. This may be the case with other ResourceProcessors