Hi,
From the paper I expected Chain-of-Causation (CoC) reasoning to be part of supervised fine-tuning, not only trajectory prediction. The default configs in this repo look trajectory-focused: vla_processor.yaml uses label_components: ["traj_future"] and does not add a cot block in components_order.
load_physical_aiavdataset (used by PAIDataset) loads images and ego trajectories but does not expose ground-truth CoC text, so it’s unclear how one would train CoC supervision with the stock data path.
In TrainableReasoningVLA.forward there is a losses["others"] term, but with the default masks it isn’t obvious that this is meant for CoC.
Could you clarify: Is the released recipe intentionally trajectory-centric, while full CoC-supervised SFT used internal data and a different pipeline? If CoC SFT is supported here, what config + data fields should users set?
Thanks.
Hi,
From the paper I expected Chain-of-Causation (CoC) reasoning to be part of supervised fine-tuning, not only trajectory prediction. The default configs in this repo look trajectory-focused: vla_processor.yaml uses label_components: ["traj_future"] and does not add a cot block in components_order.
load_physical_aiavdataset (used by PAIDataset) loads images and ego trajectories but does not expose ground-truth CoC text, so it’s unclear how one would train CoC supervision with the stock data path.
In TrainableReasoningVLA.forward there is a losses["others"] term, but with the default masks it isn’t obvious that this is meant for CoC.
Could you clarify: Is the released recipe intentionally trajectory-centric, while full CoC-supervised SFT used internal data and a different pipeline? If CoC SFT is supported here, what config + data fields should users set?
Thanks.