[Loris-dev] Issue: same hash for different files

[Cecile Madjar]

Hi Alfredo,

Actually, the function that computes the md5hash is in
https://github.com/SPINEProject/Loris-MRI/blob/62ae20930af73935a3a03071307b2575abf165f1/uploadNeuroDB/NeuroDB/MRI.pm#L1135
.

My guess is that the list of headers used to determine the uniqueness of
the file is not enough to differentiate between the two segmentation files
you mention even though they are from two completely different images.
Maybe you need to add another header in that function to make sure that
each segmentation file you insert is unique? I don't know what those files
look like but I would investigate in that direction if I were you.

Hope this helps,

Cécile


On Mon, Aug 22, 2022 at 4:32 PM Morales Pinzon, Alfredo <
AMORALESPINZON at bwh.harvard.edu> wrote:

> Dear LorisDev team,
>
> I just came across an issue for about 100 segmentations that I’m attaching
> to some images using the script “register_processed_data.pl”. I found
> that the hash for two different files is exactly the same, and thus one of
> the files cannot be uploaded. The segmentations are different and are
> linked to two different images.
>
> Here is the code that is finding the “duplicate” hash in the database:
>
> https://github.com/SPINEProject/Loris-MRI/blob/62ae20930af73935a3a03071307b2575abf165f1/uploadNeuroDB/NeuroDB/MRI.pm#L1188-L1206
>
> What do you think I can do in this case? I’m happy to share the anonymized
> segmentation files if needed.
>
> I am running Loris-MRI v23.0-release.
>
> On a side note, when the script “ register_processed_data.pl” exits there
> is no error message send to the terminal. Can we add an error printer
> when this happens? This is where the script is exiting in my case:
>
> https://github.com/SPINEProject/Loris-MRI/blob/62ae20930af73935a3a03071307b2575abf165f1/uploadNeuroDB/register_processed_data.pl#L329
>
> Best regards,
> Alfredo.
>
> The information in this e-mail is intended only for the person to whom it
> is addressed.  If you believe this e-mail was sent to you in error and the
> e-mail contains patient information, please contact the Mass General
> Brigham Compliance HelpLine at
> https://www.massgeneralbrigham.org/complianceline .
>
> Please note that this e-mail is not secure (encrypted).  If you do not
> wish to continue communication over unencrypted e-mail, please notify the
> sender of this message immediately.  Continuing to send or respond to
> e-mail after receiving this message means you understand and accept this
> risk and wish to continue to communicate over unencrypted e-mail.
> _______________________________________________
> Loris-dev mailing list
> Loris-dev at bic.mni.mcgill.ca
> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20220822/9bc595e5/attachment-0001.html>