Initial Review Response
Thank you for taking the time to review my paper and provide helpful feedback.
"the experiments do not include multiple baselines that account for context or memory such as transformer, SSMs, LSTMs..."
This is a very valid point, I will look to add a LSTM and transformer baseline to address this inherent weakness.
"the experiments are limited to a single small-scale dataset. It would be interesting to understand how the proposed method would perform on various LfD tasks. Ideally, it would be nice to include tasks that require the policy to be reactive, for instance, tasks involving interaction with an object like pushing, or sticking to your example, drawing the drawings from different starting positions."
I can look to extend the evaluation to simulated robotics motions using Franka Emika Panda in MuJoCo. For the reactivity point, the current method will definitely require tuning of the state update step, as this is essentially exponential smoothing whose parameters impact the responsiveness of motions to new inputs. It is worth mentioning that this is dependent on the relationship between prediction latency and underlying controller frequency. One option is to make the update parameters tunable based on inputs which should help address this problem but I will need to implement this extension. To address this point I'll look to simulate a toy task in MuJoCo that requires responsiveness to visual inputs.
"the paper lacks ablations of some components and hyperparameters it includes (ResNet, ...)."
I'll try to add more ablations, I definitely agree with this point.
"I am willing to raise the score (to a positive score) if more baselines and tasks are included in the evaluation."
Thanks, this work is very much an initial step in the direction of developing architectures that incorporate ideas from dynamical systems theory (for which there is much existing work). I do think the current work is far from perfect, however, I think it has the potential to instigate more discussion around this general direction and it may be practically useful but there is certainly more work required to further develop related approaches.
"why does the proposed approach lead to a higher jerk than the temporal ensembling baseline (figure 3f)?"
This is an excellent question and something I was trying to understand when preparing the results as it is very relevant for real robot experiments. I think this result depends very much on the parameters for both the proposed layer and temporal ensembling. In the proposed layer, the parameter alpha weighs the state update step and was set to 0.25, in contrast the temporal ensembling weight parameter was set to 0.001 with a prediction horizon of 2. The relationship between these parameter choices and the resulting jerk in motions would address your question. I didn't include this in the paper but I think it may be feasible to draw a direct comparison between the weighting applied in both approaches, the current discrepancy is likely an artefact of the parameters used.
"why the latency of the ESN is worse than their method in Table 1 but better in Table 2?"
Yeah this is a confusing result, I wanted to reformat this table to be more informative. This metric is suboptimal as it is a combination of the mean prediction latency times number of predictions required to complete the drawing task. The short answer is in the difference in the number of predictions between the single and multi-task case.
In the single task case all architectures make essentially the same number of predictions and hence the latency score is more indicative of computational overhead. Here the ESN generally performs best, it is only on the S character task it performs worse. In the multi-task case, the ESN solves the task in less predictions but it is highly inaccurate on fitting the spatial characteristics of the demonstration and hence while it converges to the expected end point for the task in less predictions it doesn't fit the data very well. This isn't communicated well in this table so I'll look to add information on the number of predictions such that it communicates the prediction latency and number of predictions.
"can you elaborate further on how the proposed method ensures the preservation of the echo state property?"
So in the shared code there is actually a typo that needs to be addressed. The echo state property is actually maintained according to the following scheme: https://www.sciencedirect.com/science/article/abs/pii/S0893608012001852?via%3Dihub
"how would the proposed method perform on more reactive and complex tasks, for instance, tasks involving interaction with an object like pushing, or sticking to your example, drawing the drawings from different starting positions?"
This still needs to be tested but likely it would work well with the appropriate parameter tuning.
** I am running out of space so I will follow up on the other questions in another official comment.