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 for your wonderful work and code release.
In the file constants.py, variables TASKS and corresponding TEXT_EMBEDDINGS are given. The correspondence has been checked using the link you gave in the same file. Here I have two questions.
(1) It seems that TASKS has redundent and totally same terms, shown in the following image.
(2) In the file utils.py where the variable TASKS is used, it seems that the text embedding does not match their actual task at all! For example, if close_drawer is in the filename, it will get the task embedding of "Slide open drawer from right to left"!
The mismatch makes me wonder if the FiLM condition in the network really works as expected.
Looking forward to your reply.
The text was updated successfully, but these errors were encountered:
Hi, thanks for reaching out! When we were training the agent, the TASKS and TEXT_EMBEDDINGS were the same names and count. The FiLM conditioning seemed to work during evaluations as in the same scene with different task combinations, we were able to solve a particular task with just text
Thank you for your wonderful work and code release.
In the file constants.py, variables
TASKS
and correspondingTEXT_EMBEDDINGS
are given. The correspondence has been checked using the link you gave in the same file. Here I have two questions.(1) It seems that
TASKS
has redundent and totally same terms, shown in the following image.(2) In the file utils.py where the variable
TASKS
is used, it seems that the text embedding does not match their actual task at all! For example, ifclose_drawer
is in the filename, it will get the task embedding of "Slide open drawer from right to left"!The mismatch makes me wonder if the FiLM condition in the network really works as expected.
Looking forward to your reply.
The text was updated successfully, but these errors were encountered: