Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Paper: Developing a Graph Convolution-Based Analysis Pipeline for Multi-Modal Neuroimage Data: An Application to Parkinson's Disease #477
Hm... looks like you might have a bibtex issue. Here's the message from the server:
referenced this pull request
May 23, 2019
@deniederhut thanks for your comments. Where did you find that server output? My
Anyway, I've fixed that error, and I figured out the
I didn't expect the warnings to prevent a build (else I figured they would be errors), but I'm trying to fix them now. I've resolved all but a few Warning types that I don't know how to resolve. E.g.:
I've checked my footnotes and they are all entered according to the docs.
The citation is in the
seem related to the translation between
Anyway, these are my thoughts... pls let me know if you have any other suggestions, and where you got the output from the server that you posted earlier. Thanks so much!! I'm learning a lot
Success! Thanks for the help and patience. FYI, I got my references to appear by adding the lines
I added the lines before my Appendix section to try and put the References before the Appendix, but the References still inserted at the end. Any idea how to "append" an Appendix to the very end, after References?.
These lines also caused helpful errors to appear in my
Hi @AngelosPsy, thanks for checking in! I would say, if you have some comments that point to specific words/sentences, then on the rst file will be best. Otherwise, more general comments about a section, etc may be better to leave here To keep more of a record.
Also FYI, I will be adding more to the results later this week. I have the results but am currently out of town. Thanks!
OK, since from what I understand the paper is not 100% ready yet (i.e., the results are missing) I will just place my general comments here. After revisions, I can go through the paper sentence by sentence and make more specific comments. I understand that you are out of town so I do not expect and immediate answer. Also, if you are on vacation, please feel free to ignore my message until you return – it is good to have real vacation
Discussions and Conclusions
Thanks for your helpful feedback, and patience regarding my travels! I have addressed your points, and have made some comments below.
In general, I reduced the Background and combined it with the Methods section, and reworded/revised a lot of the paper. My goal is to include enough technical background for neuroimaging and deep learning so that an outsider to the fields could understand and implement the methods, in line with the "pipeline" format. However, that's easier said than done and if things are still too wordy or verbose please let me know!
This is generated by the build system of SciPy. Do you know if there is a way for me to change it? If so, I'll look into it!
I changed this to 'psychiatric symptoms (i.e., depression)'. I am referring to issues such as depression. Hopefully that makes it more clear; otherwise I can try something else.
Do you know the limit? I believe newly updated abstract is currently exactly 150 words.
This is also a result of the build process. I tried moving the footnotes but they were still inserted in the same place. (I have also tried putting the Appendices after the Results, but the build process seems to always put the Results at the very end)
I do not know how the text would look like after you have reduced it to fit in the 8-page limit but here are some additional comment to the present version of the ms.
@AngelosPsy I have made the suggested changes.
@cbcunc Is it okay if the Footnotes and References exceed the 8-page limit? If so, then the paper is now 8 pages, except that it insists on keeping the last line on page 9. When I shorten sections, the build process just widens that gaps of the math sections to keep the last line on page 9. Any advice?
I am not seeing the changes in the build server. Do you I need to create a pull request, or was that done when I pushed to my fork and the changes are just waiting to be approved?