The authors describe an extension of previous work showing the application of deeplabcut in a real-time setting. Work here tracks whiskers of head fixed mice and provides examples where specific movements of individual whiskers could trigger behavioral feedback. While the work is impressive for describing very short latency feedback and potentially an extension of two previous papers Kane et al Elife and Forys et al eNeuro, it does have issues with being an accessible tool.
I am having trouble examining the software that the authors use. They give a couple of links to zenodo but unfortunately I was unable to open anything using these links in various combinations, please provide corrected links and/or attach the files. From what I can tell the authors have not provided an open source tool in a usable format. It is not explicitly clear that the authors will be sharing the full methods approach.
I have already corrected the DOIs for zenodo to URLs.
I think we need to attach GitHub repositories, with all author-related information being deleted.
Reviewer 1 (part 1 of 3)
> The authors describe an extension of previous work showing the application of deeplabcut in a real-time setting. Work here tracks whiskers of head fixed mice and provides examples where specific movements of individual whiskers could trigger behavioral feedback. While the work is impressive for describing very short latency feedback and potentially an extension of two previous papers Kane et al Elife and Forys et al eNeuro, it does have issues with being an accessible tool.
>
> I am having trouble examining the software that the authors use. They give a couple of links to zenodo but unfortunately I was unable to open anything using these links in various combinations, please provide corrected links and/or attach the files. From what I can tell the authors have not provided an open source tool in a usable format. It is not explicitly clear that the authors will be sharing the full methods approach.
I have already corrected the DOIs for zenodo to URLs.
I think we need to attach GitHub repositories, with all author-related information being deleted.
The main trouble here is the policy of anonymized review process in eNeuro.
We are supposed to try not to reveal our identity from the manuscript etc. by mentioning e.g. "approval by LaGeSo" and "we previously showed (Takahashi et al., 2016)". It looks like the review process will be delayed if we fail to do so.
So I feel that directly providing a GitHub repository is not a nice thing when we claim we developed the program (even though I show up as a NEET on GitHub).
The main trouble here is the policy of anonymized review process in eNeuro.
We are supposed to try not to reveal our identity from the manuscript etc. by mentioning e.g. "approval by LaGeSo" and "we previously showed (Takahashi et al., 2016)". It looks like the review process will be delayed if we fail to do so.
So I feel that directly providing a GitHub repository is not a nice thing when we claim we developed the program (even though I show up as a NEET on GitHub).
Keisuke Sehara
Reviewer 1 (part 1 of 3)
I have already corrected the DOIs for zenodo to URLs.
I think we need to attach GitHub repositories, with all author-related information being deleted.
can be of help? https://guides.github.com/activities/citable-code/
The main trouble here is the policy of anonymized review process in eNeuro.
We are supposed to try not to reveal our identity from the manuscript etc. by mentioning e.g. "approval by LaGeSo" and "we previously showed (Takahashi et al., 2016)". It looks like the review process will be delayed if we fail to do so.
So I feel that directly providing a GitHub repository is not a nice thing when we claim we developed the program (even though I show up as a NEET on GitHub).
added zip archives of GitHub repositories + HTML documentation