Thanks for your detailed reviews and thoughtful questions. Below, we address all your comments.
> **Q1** Problem setting to be optimized.
**A1** There are certainly variations of our task setup that could be explored, each with its own trade-offs and assumptions (for example, a third setting would be one where the agent can only move to an adjacent position in each action). The task setup you suggest, where the agent gets to observe all patches between its previous and current patch, has the risk of leading to fairly uninteresting search behaviors, where a (close-to) optimal strategy may be to always move to a maximally distant uncovered location (since on average, that implies as many revealed subareas as possible, which in turn leads to on average more targets being discovered). Furthermore, when the agent makes a movement that is not vertical or horizontal, there are multiple possible paths that could be filled in, thus becoming a bit ill-defined how to do the fill-in in many cases. We therefore believe our current task formulation is reasonable, but we do recognize that parts of the suggestion could be incorporated in future work, although arguably the "intermediate" revealed sub-areas ought to be blurred due to movement.
> **Q2** Details on training and testing are missing.
**A2** We discuss the implementation details in Appendix section A4. Also, in the main paper starting on Line 383, we write: "Both xView and DOTA are satellite image datasets, with roughly 3000 px per dimension and representing approximately 60 object categories. We use 50%, 17%, and 33% of the large satellite images to train, validate, and test the methods, respectively". **For convenience, we provide the anonymous link to the script for training and inference of DiffVAS in Appendix section A4 of the updated draft.** We are committed to open-sourcing the GitHub link upon acceptance, including all model weights, to facilitate an easy reproduction of all our experimental results. We would be happy to provide any further details about our experiments if you require any additional specifics or clarification.
> **Q3** Details about inference with E2EVAS and MPS-VAS.
**A3** During inference, at each search step, we provide only the partially observed glimpses to the policy network, rather than the full search image. Specifically, we input an image with black patches representing unobserved areas and the ground truth content for the already observed regions. Based on the policy's action, we then update the input image by adding the newly revealed patch, which corresponds to the patch selected by the policy for querying. Aside from that, the E2EVAS and MPSVAS remain unchanged from the original version.
> **Q4** Motivate the experimental setup in multi-target and zero-shot setting.
**A4** In both xView and DOTA, **due to the large combinatorial space of possible category subsets, we selected only a representative subset for evaluation**. Moreover, certain classes are extremely rare within the dataset. For instance, images containing at least one instance of class Cement-Mixer appear only once. Consequently, including such classes as targets is not meaningful, as evaluating performance based on a single image does not provide robust analysis/results. Furthermore, regarding the multi-target results, in addition to those reported in Table 2 of the main paper, Table 9 in the Appendix includes 3 more multi-target combinations, bringing the total to 6 combinations in this work.
The zero-shot results are presented starting around line 494 in the main paper. In this section, we train models on DOTA using categories that do not appear in xView. Then, in Table 7, we report the zero-shot performance on the unseen xView classes. **These additional details have been included in Appendix A9 of the updated draft.**
> **Q5** How do you sample episodes during training?
**A5** The details of our training and evaluation settings are provided in Appendix A4. During training, we randomly sample an image from the training set and select a random budget within the range {1 to N-1} (where N is the number of grids). We then extract the set of target categories if at least one instance of each category is present in the image, based on the ground truth annotations (which also include the precise locations of these target objects as a bounding box). Once the target category set is determined, we randomly select a category from this set to train our policy. The rationale for using a random-budget and random-target is to ensure that the policy learns to be robust against the target category and budget constraint. Across various experiments, we demonstrate that DiffVAS consistently outperforms the baseline across different budgets and target categories. **These additional details have already been included in Appendix A10 of the updated draft**. Moreover, we would be happy to incorporate any other specific training details you suggest for the final version.