Checking file or data integrity

5 visualizaciones (últimos 30 días)
Sasha Egan
Sasha Egan el 19 de Jul. de 2018
Comentada: Sasha Egan el 20 de Jul. de 2018
G'day mates, I am collecting data from a multi-channel DAQ, therefore, the datasets tend to be quite large. I am splitting each channel out from the lumped data into its own respective vector and saving an interim copy as a .mat binary. Is there a way to verify that the data saved in the .mat binary and the vector in memory are identical? i.e. ( in pseudo-code )
A = [ channel 1 ]
A_check = checksum (a)
save A as A.mat
A.mat_check = checksum(A.mat)
assert {
A_check equals A.mat_check
} throw exception e1 CheckSumsDoNotMatch
if (A_check != A.mat_check)
...try again...
Cheers.

Respuesta aceptada

Jan
Jan el 20 de Jul. de 2018
Editada: Jan el 20 de Jul. de 2018
Maybe with FEX: DataHash or FEX: GetMD5:
A = rand(1, 1e6);
A_check = DataHash(A); % Or: GetMD5(a, 'Binary')
save('A.mat', A);
FileData = load('A.mat');
A_reloaded_check = DataHash(FileData.A);
if ~isequal(A_check, A_reloaded_check)
error('Saving failed!');
end
You should definitely stop with an error. If the saving fails, there is a severe problem, which cannot be handled reliably by repeating. Either the disk is damaged or the CPU melts down.
[EDITED] Guillaume is right: Calculating the checksums has no advantage. I suggested it only, because there might be a need anywhere, which was not mentioned in the question. An efficient version of my code would be:
A = rand(1, 1e6);
save('A.mat', A);
FileData = load('A.mat');
if ~isequal(A, FileData.A)
error('Saving failed!');
end
  2 comentarios
Guillaume
Guillaume el 20 de Jul. de 2018
Editada: Guillaume el 20 de Jul. de 2018
I don't really see the point in computing the hashes. It's just going to take as long as simply comparing the matrices themselves. After loading the mat file, you could just do:
if ~isequal(A, FileData.A)
error(...)
What's puzzling me is why the question in the first place? If you suspect that for some reason the data does not survive the round trip through a mat file, then you should have procedures in place to detect hard disk corruption and recover from such. That should happen at the OS or hardware level, not within matlab.
matlab itself, will not corrupt a mat file.
Sasha Egan
Sasha Egan el 20 de Jul. de 2018
To allay your puzzle. Because I was writing directly to a network drive. Stuff happens in between sometimes. I was looking for an easy way of checking that the write was successful without resorting to writing the data locally...thank you for the suggestions. :-)

Iniciar sesión para comentar.

Más respuestas (0)

Categorías

Más información sobre Get Started with MATLAB en Help Center y File Exchange.

Etiquetas

Productos


Versión

R2014b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by