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 way queries generate #44

Open
balabalaboy opened this issue Feb 20, 2023 · 3 comments
Open

the way queries generate #44

balabalaboy opened this issue Feb 20, 2023 · 3 comments

Comments

@balabalaboy
Copy link

balabalaboy commented Feb 20, 2023

Hello, thank you very much for such a good job.
I am a beginner and after reading your thesis I have a general understanding of the principles of this project. But there are some details that I am a little confused about. What about the query pairs on the training data randomly generated or labelling before training?How the number of queries is decided.
If I want to finetune against my training set, how should I do it?

@jiangwei221
Copy link
Collaborator

  1. Query pair are generated by projecting the dense depth from one camera to another, and then randomly subsampled.
  2. The number of queries can be any number that fits your memory.
  3. Simplest way would be create a dataloader that returns the same data format as the default dataloder, and load the pertained weights then start fine-tuning with lower learning rate.

@balabalaboy
Copy link
Author

Thanks for your reply, I'll try.

@balabalaboy
Copy link
Author

balabalaboy commented Feb 23, 2023

Hello, I wanted to see how the learning rate decayed during training, but I didn't seem to find it. Does the learning rate remain the same during training?
I found that the current early stopping and learning rate adjustment mechanisms are based on the validation loss of several consecutive epochs. COTR does not seem to be verified every epoch, and the verification is performed after a certain number of epochs.

  1. Query pair are generated by projecting the dense depth from one camera to another, and then randomly subsampled.
  2. The number of queries can be any number that fits your memory.
  3. Simplest way would be create a dataloader that returns the same data format as the default dataloder, and load the pertained weights then start fine-tuning with lower learning rate.

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

2 participants