More responses due to the char limitation.
> W6 and Q1: OmniJARVIS on other environments.
Thank you for your suggestions. We have indeed begun extending OmniJARVIS to other environments, starting with Atari Montezuma’s Revenge game, where it achieved a score of 3600. This initial success illustrates the model’s potential for generalization. Details on adapting OmniJARVIS to different environments are further elaborated in the **General Response**. We are committed to ongoing efforts to expand its applicability across various domains, demonstrating its versatility and broader utility.
> W7: Add limitations.
Thanks for your comments. We discuss the limitations of OmniJARVIS in the **General Response**, which will be inserted in the updated manuscript.
> W8 and Q6: More analysis on agent failure modes.
Thank you for your inquiry regarding the failure modes of OmniJARVIS and its behaviors, particularly in challenging tasks such as obtaining a diamond. The primary failure modes can be categorized into the following:
1. **Planning Errors**: During programmatic tasks, OmniJARVIS occasionally produces incorrect thoughts or plans. For instance, it might attempt to mine stone without a wooden pickaxe. These errors stem from inaccuracies within the QA dataset and hallucinations inherent in the language model.
2. **Action Execution Failures**: The FSQ GROOT decoder (our low-level control policy) sometimes fails to translate the behavior code into actions properly, particularly with less frequently occurring fsq codes due to data imbalance in the interaction dataset.
3. **Hallucinations in perception**: Errors in visual recognition by the Llava model can lead to incorrect scene interpretations, such as mistaking a stone for iron ore. These hallucinations hinder the agent’s reasoning and decision-making processes.
In the specific task of obtaining a diamond, these failure modes manifest when OmniJARVIS incorrectly plans or executes sequences due to the above issues. However, OmniJARVIS has a high success rate on finishing such tasks and correctly sequences tasks from mining basic materials to crafting necessary tools and finally obtaining the diamond, demonstrating effective integration of vision, language, and action within one unified model.
> Q3: why not re-using language tokens?
Thank you for your question about integrating behavior tokens into the LLM vocabulary. We employ different strategies based on the tokenizer used:
1. Reserved Tokens: When possible, we use reserved tokens from the language tokenizer for behavior tokens to maintain semantic integrity. This happens with the tokenizer of Fuyu VLM.
2. Reusing Infrequently Used Tokens: In the absence of suitable reserved tokens, we repurpose infrequently used tokens, as seen with the Llama tokenizer. This happens with the LLaVA tokenizer. We apologize for not making this clear and have updated the manuscript.
Furthermore, our FSQ design compresses extensive codebook sizes into up to 35 tokens (when the FSQ setting is 8+8+8+6+5), optimizing vocabulary use without semantic loss. These approaches balance semantic preservation with efficient vocabulary management.
> Q4: Confusion on training dataset tokens.
Thank you for your attention to detail. The 1T tokens were indeed a typo, the correct calculation should be 1B behavior and language tokens in total. We apologize for the confusion and will correct this in the revised manuscript.
> Q5: How OmniJARVIS works without instruction?
Thank you for your question. In the absence of instructions, OmniJARVIS effectively models a dataset with gameplay video only -- the videos are segmented into trunks with a default length of 128, and then all trunks are converted to codes by the behavior tokenizer. OmniJARVIS is tasked to predict these codes based on the initial visual observations of the corresponding segments. The goal of this ablation is to verify the necessity of including plans, thoughts, and other means of instruction (the "language" modality) in the VLA modeling of OmniJARVIS.
> Minor 2: checkmark in training settings
Apologies for the confusion. We use a checkmark to indicate when the model's training data includes specific information. In Q5, the first row without an instruction represents unconditional OmniJARVIS, which is unable to follow human language instructions. With richer synthetic data, including thought, memory, and caption data, OmniJARVIS can better follow instructions, leading to improved learning with lower loss. This demonstrates the effectiveness of synthetic data. We will follow your suggestion to replace the symbols.