Dear Morteza, Christian, Justin,
Yes, this is the most likely explanation. The updated recordings are longer, and they use the full range of 16-bit signed integers, so they are more likely to overflow. The example code doesn't use all of the recording segments or channels, so we didn't encounter this issue when testing the code. In all likelihood, your files are not corrupted, and I apologize for all of the confusion.
I have updated the helper_code file to promote the signal data to 64-bit signed integers for the checksum calculation, and I have disabled the checksum calculation by default to avoid the problem with incorrect checksums. Due to the size of the data, we will not be able to shared updated files now, but we will plan to regenerate all of the checksums at the end of the Challenge.
(On behalf of the Challenge team.)
Please post questions and comments in the forum. However, if your question reveals information about your entry, then please email info at physionetchallenge.org
. We may post parts of our reply publicly if we feel that all Challengers should benefit from it. We will not answer emails about the Challenge to any other address. This email is maintained by a group. Please do not email us individually.