Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "data.lmdb" file in data seem to be corrupted #16

Open
Gggggjr opened this issue Aug 16, 2024 · 5 comments
Open

The "data.lmdb" file in data seem to be corrupted #16

Gggggjr opened this issue Aug 16, 2024 · 5 comments

Comments

@Gggggjr
Copy link

Gggggjr commented Aug 16, 2024

Dear Stevenlsw,
I hope this message finds you well. I encountered an issue that the "data.lmdb" file in data seem to be corrupted .I use python==3.6 and LMDB version is 1.2.1. This is my error report.
image

@stevenlsw
Copy link
Owner

hi, i think this is the keys in the training set, note in the provided lmdb we only store testing keys, the training keys needs to be generated follow the instructions. If you not sure how, please contact me and i could give you instructions.

@Gggggjr
Copy link
Author

Gggggjr commented Sep 2, 2024

hi, I would be very grateful if you could give me a more detailed instructions.

@JaehongJaehongMin
Copy link

Thank you for kindly sharing the implementation.

However, I'm encountering the same issue.
Could you please explain how to handle this key error?

@JaehongJaehongMin
Copy link

JaehongJaehongMin commented Nov 9, 2024

RULSTM repository explains how to download mdb files set consists of rgb, flow, obj mdb files.
But I have no idea how to get lmdb file or convert mdb file to lmdb file.

@stevenlsw
Copy link
Owner

Hi, we only provide the key in testing split, for training split, you need to generate key pair by yourself as it take too much storage. For conversion, you could refer to this scripts and extract the training data yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants