Handling of partially corrupted Parmay Matrix files

[jhmigueles]

Currently, the function readParmayMatrix() assumes that the total number of packets declared in the binary file header (headerPackeNum) exactly matches the actual number of packet headers (MDTCPACK) observed in the file. When this count is inconsistent, for example, due to invalid or truncated data at the end of a .bin file, the function intentionally fails and marks the file as corrupted. The manufacturer informed that this scenario may occur when copying, downloading or transferring files, and that this doesn't mean that the available packets in the file are unreliable. Thus, I suggest not marking the file as corrupr, but using the smaller of the two values for the number of packets (declared vs. observed), and add this information to the QClog.

[jhmigueles]

Also related with partially corrupted files, when imputing temperature, current approach is to impute using the mean of the surrounding temperature values. If any of the surrounding values is missing (e.g., corrupted packet), then this triggers an error.

Solution to implement: If not available both surrounding values, then leave it as missing value (i.e., NA)