We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I would like to know that is there any specific reason for using task_id along with x_coor, y_coor while creating pos_embedding ?
if self.pos_embedding_type == "linear": if len(self.tasks)>1: self.pos_embedding = nn.Linear(3, self._num_filters[-1] * 2)
Anyhow we know that 6 task_id ct_feats are concatenated next to each other and are sliced accordingly later in the below code snippet.
for idx, task in enumerate(self.tasks): out_dict_list[idx]["ct_feat"] = ct_feat[:, :, idx * self.obj_num : (idx+1) * self.obj_num]
what is the purpose of diluting ct_feat dimensions (256) with task_id.
Thanking you in advance.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
I would like to know that is there any specific reason for using task_id along with x_coor, y_coor while creating pos_embedding ?
Anyhow we know that 6 task_id ct_feats are concatenated next to each other and are sliced accordingly later in the below code snippet.
what is the purpose of diluting ct_feat dimensions (256) with task_id.
Thanking you in advance.
The text was updated successfully, but these errors were encountered: