You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you very much for your open source code.
According to the prompt on the homepage, the flickr30K feature used is in mdb format, and msgpack is used to read it~
When using the flickr30K image feature file you provided, this error occurred when reading feats and boxes_feats: unhashable type: 'slice'
This error occurred in this paragraph: dump = self.txn.get(img_id.encode("utf-8"))\ nbb = self.name2nbb[img_id]\ img_dump = msgpack.loads(dump, raw=False)\ feats = img_dump["features"][:nbb, :]\ img_bb = img_dump["norm_bb"][:nbb, :]\ feats = img_dump["features"][:nbb, :] img_bb = img_dump["norm_bb"][:nbb, :]
The two lines in bold appear where this bug appears. What is the reason for this?
The text was updated successfully, but these errors were encountered:
Hey, are using the environment file eUG.yml that I provided? Especially all the packages related to reading the .mdb data
Thanks for your reply~
Today I changed the version of lmdb, msgpack and msgpack_numpy to match eUG.yml However, the same bug occured. I think it might be better to provide the screeshot of those features as below:
Is there anything different here from your experiment?
Thanks a lot~
Thank you very much for your open source code.
According to the prompt on the homepage, the flickr30K feature used is in mdb format, and msgpack is used to read it~
When using the flickr30K image feature file you provided, this error occurred when reading feats and boxes_feats:
unhashable type: 'slice'
This error occurred in this paragraph:
dump = self.txn.get(img_id.encode("utf-8"))\ nbb = self.name2nbb[img_id]\ img_dump = msgpack.loads(dump, raw=False)\ feats = img_dump["features"][:nbb, :]\ img_bb = img_dump["norm_bb"][:nbb, :]\
feats = img_dump["features"][:nbb, :]
img_bb = img_dump["norm_bb"][:nbb, :]
The two lines in bold appear where this bug appears. What is the reason for this?
The text was updated successfully, but these errors were encountered: