-
Notifications
You must be signed in to change notification settings - Fork 17
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
JoSS Review: Manuscript #21
Comments
Sorry, could you please explain how the issue has been addressed? |
|
Thank you @tonggehua ! I still have most of my review to do - I'll try to do it within the next week (a lot on my plate at the moment!) |
Okay, just checking over the points above now! For the bolding, I am referring to the first word (before the colon) after each section. For example, we would change: * Modular: ``Virtual Scanner`` consists of modules corresponding to steps in the MRI signal chain [@webb2016magnetic]. Since modern MRI systems contain multiple levels of hardware and software, it is important for researchers to select the appropriate steps for simulation when developing acquisition paradigms, analysis methods, or hardware components. Students may also choose to focus on individual aspects of the experiment. to * **Modular**: ``Virtual Scanner`` consists of modules corresponding to steps in the MRI signal chain [@webb2016magnetic]. Since modern MRI systems contain multiple levels of hardware and software, it is important for researchers to select the appropriate steps for simulation when developing acquisition paradigms, analysis methods, or hardware components. Students may also choose to focus on individual aspects of the experiment. And the difference in markdown (rendered here) is:
Given how it renders, I suggested this change because I missed that there was a small section heading with a colon when I first read. Does that make sense? |
This is the start of review for openjournals/joss-reviews#1637.
Manuscript
The introduction does a good job to communicate a statement of need, but I'd like to see a few more references for:
It would be helpful to flush out the point about vendor neutrality - most that read aren't familiar with MRI
or that there are different companies that make the machines, software, and thus simulators.
General Comments
Very good job on explaining your roadmap, and real life use cases. This is a cool tool I'm excited to see development for.
The text was updated successfully, but these errors were encountered: