New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments on manuscript #54
Comments
Merged
dhimmel
pushed a commit
that referenced
this issue
Sep 9, 2019
zietzm
added a commit
that referenced
this issue
Sep 9, 2019
This build is based on 76374a3. This commit was created by the following Travis CI build and job: https://travis-ci.com/greenelab/xswap-manuscript/builds/126464775 https://travis-ci.com/greenelab/xswap-manuscript/jobs/232371267 The full commit message that triggered this build is copied below: Add bdsullivan authorship (#56) Merges #56 Refs #54
zietzm
added a commit
that referenced
this issue
Sep 9, 2019
This build is based on 76374a3. This commit was created by the following Travis CI build and job: https://travis-ci.com/greenelab/xswap-manuscript/builds/126464775 https://travis-ci.com/greenelab/xswap-manuscript/jobs/232371267 The full commit message that triggered this build is copied below: Add bdsullivan authorship (#56) Merges #56 Refs #54
Oops. Double-sided scanning fail (haven't beaten the new department's copy machine into submission yet) -- sorry for confusion. Full review attached. |
dhimmel
pushed a commit
that referenced
this issue
Nov 12, 2022
Closing now that we've merged #57. Thanks @bdsullivan for the feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1765_001.pdf
Old-school markup attached, that should probably be broken into multiple issues. Mixture of fine-grained (e.g. typos and concerns about figure legends/clarity) and broader-scale concerns (e.g. lack of definitions of technical terms, organization, and seemingly overly-explanatory language "justifying" the approach/results).
Overall, I have some qualms about the tone of the paper (e.g. what is being explained, where, and at what level of detail), and would be happy to have a call to discuss this more broadly. I also feel like the paper suffers from a lack of technical specificity in much of the narrative. I'm still not 100% sure I know what you algorithm you're using when you say "edge reconstruction", which worries me.
Let me know how you'd like to approach things from here. Thanks!
The text was updated successfully, but these errors were encountered: