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

What are iters1 and iters2 in droid_frontend.py #107

Open
shomeAvataar opened this issue Jul 24, 2023 · 0 comments
Open

What are iters1 and iters2 in droid_frontend.py #107

shomeAvataar opened this issue Jul 24, 2023 · 0 comments

Comments

@shomeAvataar
Copy link

shomeAvataar commented Jul 24, 2023

I am unable to understand the significance of iters1 and iters2 in droid_frontend.py even after going through the paper and code. I understand that the update operation does. However I am not clear why two such update sequences are needed.
Specifically, what do the two update operations do in the following code in droid_frontend.py (lines 50 to 66):

 ` for itr in range(self.iters1):
        self.graph.**update**(None, None, use_inactive=True)

    # set initial pose for next frame
    poses = SE3(self.video.poses)
    d = self.video.distance([self.t1-3], [self.t1-2], beta=self.beta, bidirectional=True)

    if d.item() < self.keyframe_thresh:
        self.graph.rm_keyframe(self.t1 - 2)
        
        with self.video.get_lock():
            self.video.counter.value -= 1
            self.t1 -= 1

    else:
        for itr in range(self.iters2):
            self.graph.**update**(None, None, use_inactive=True)

    # set pose for next itration
    self.video.poses[self.t1] = self.video.poses[self.t1-1]
    self.video.disps[self.t1] = self.video.disps[self.t1-1].mean()`

Also what does it mean by set pose for next iteration?

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

1 participant