m5sum checksum target values in wrong order? #61
Comments
|
Yes, thanks for pointing. Fixed in aa8b8c0 |
apsdehal
pushed a commit
that referenced
this issue
May 8, 2020
… files (#61) * [fix] Change some configs and project Readme files * [fix] add missing dataset configs in M4C series A few configs were broken in #55. This commits adds them back. * [fix] Fix pythia BERT configs Co-authored-by: Ronghang <[email protected]>
apsdehal
pushed a commit
that referenced
this issue
May 8, 2020
… files (#61) * [fix] Change some configs and project Readme files * [fix] add missing dataset configs in M4C series A few configs were broken in #55. This commits adds them back. * [fix] Fix pythia BERT configs Co-authored-by: Ronghang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I downloaded yesterday the coco.tar.gz features file (240GB) and when I made the md5sum checksum I got ab7947b04f3063c774b87dfbf4d0e981 instead of the target b22e80997b2580edaf08d7e3a896e324 value. The funny thing is that ab7947b04f3063c774b87dfbf4d0e981 is the target value said to belong to the OpenImages features file, so I believe the target values where misplaced by accident. Is that correct? Thanks.
The text was updated successfully, but these errors were encountered: