Response to comments
Thanks for the review. We address your points below.
>> It's unclear if the same performance gain could be achieved via curriculum learning. In some sense, the auxiliary task can be viewed as a partial sorting, i.e., so it's a simpler task than the original target task.
Thanks for your suggestions for other methods such as curriculum learning and scratchpad training. Typically in curriculum learning, one has to progressively include sequences of higher and higher lengths. Our goal instead is to understand whether we can generalize from training on short sequences alone (length up to 20). Nonetheless, we have included curriculum learning as a baseline in the updated draft.
Regarding scratchpad training, the work of Anil et al.’22 observed that fine-tuning on scratchpad data only helps length generalization to a limited extent. Is there a particular scratchpad that you had in mind? We had trouble coming up with meaningful scratchpads for the sorting problem that were length-efficient. (E.g., we considered adding all the steps of some sorting algorithm like merge-sort or insertion-sort as a scratchpad, but these blow up the input length considerably, making it super inefficient for both training and inference. Our approach of training via subtasks does not suffer from this issue.) In Appendix E we have added a comparison to a length-efficient scratchpad—however, this scratchpad is not particularly different from the natural input/output representation. We would be interested in hearing what scratchpads you think might be useful to compare to.
To summarize, we followed your suggestion and added comparisons to the above two methods. The results are in Appendix E of the updated draft. These experiments show that task hinting is the only method in this collection which achieves non-trivial performance for sequence lengths beyond 50. For easier readability the results are also included in the table below.
| n-> | 50 | 100 |
| -------- | ------- |------- |
| Standard | 98 |0 |
| Curriculum | 98.4 |1.2 |
| Scratchpad | 98.2 |0 |
| Hinting | 99.8 |92.6 |
>> Could you clarify the role of the mask values in Figure 3.1? Why are there mask values of 0 after some 1's? Not sure why you need to pad when training decoder models.
A mask value of 1 means that we penalize the predictions made at the corresponding position during the loss function computation. Since we use padding, we use a mask value of 0 to avoid adding terms corresponding to these padding positions into our loss function. (The use of padding is simply for ease of training: the padding makes each training example be the same length.) We will clarify this further in the final version.
>> Could you provide more details on the fill hint task? Its current explanation is unclear.
Thanks for the question. The motivation for the fill hint task is the following: to sort data with repeated elements, a sorting algorithm must be able to keep track of the number of copies of an element that have been output already, and the number still to be output. Instances of the fill task consist of a number, say 17, repeated some number k (say k=5) times, followed by a prefix consisting of the same number 17 repeated r < k times. The goal of the task is to teach the model that k-r copies of the number 17 still need to be output. We will make this discussion clearer in the final version.
>> Does this idea work for tasks other than sorting? Could you apply the same to many other tasks?
To demonstrate the effectiveness of our proposed task-hinting framework beyond sorting, we have added results for the LEGO task, which has been studied in recent works in the context of generalization. These results are given in Appendix C.2, and again demonstrate the benefits of task hinting. Briefly, the LEGO task consists of a variable resolution problem over 12 variables where during training the model is only provided supervision for the first $n=6$ variables. We then measure the accuracy of the model in predicting the correct values for variables 7 to 12. For easier readability we include the results in the table below as well. Please see Appendix C.2 for more details.
| n-> | 7 | 8 | 9 | 10 | 11 | 12 |
| -------- | ------- | ------- | ------- | ------- | ------- | ------- |
| Standard | 99.9 | 99.4 | 94.8 | 84.5 | 67.6 | 41.3 |
| Hinting | 99.9 | 99.9 | 98.4 | 91.9 | 79.3 | 56.5 |
>> Can you use the factor analysis (e.g., those introduced in the recent paper [1]) for the interpretation part? Especially see the induction head analysis of this aforementioned paper.
Thanks for the reference! This work seems to be subsequent to the submission of our paper. We will definitely look into it and investigate whether this analysis can be applied to our setting to further demystify the mechanisms of the learned models.