Skip to content
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

Things to add to documentation. #12

Open
pcklink opened this issue Apr 8, 2020 · 7 comments
Open

Things to add to documentation. #12

pcklink opened this issue Apr 8, 2020 · 7 comments

Comments

@pcklink
Copy link

pcklink commented Apr 8, 2020

  • Manually set slice spacing in Slicer to something low for fine control of fiducial placement
  • High(er) contrast instruction images (or use a segmentation or outlines?)
  • Suggest people start with a high-contrast template (e.g., NMT). These are much easier and the experience really helps when dealing with the lower contrast stimuli.
@jclauneuro
Copy link

Thanks for your feedback. I've never used the set slice spacing feature. Would be great if you could provide a demo on how to use that effectively. This can certainly be added to the doc.

Once we've finalized the protocol, we will update with better images. Probably using NMTv1.3 as the example as you've indicated.

@pcklink
Copy link
Author

pcklink commented Apr 9, 2020

Screenshot 2020-04-09 20 47 35

This is where you can set how finely/coarsely Slicer moves through slices.

@greydongilmore
Copy link
Contributor

I have been working and developing in 3D Slicer and I never knew this was an option that a user could set without python code! Will definitely add this to the docs.

@bmahmou
Copy link

bmahmou commented Apr 10, 2020

Should we also include fiducial scale adjustment? the default is ok but it can make a difference in accuracy when placing the points

@pcklink
Copy link
Author

pcklink commented Apr 10, 2020

Probably a good idea to try to keep that uniform. I made them smaller myself.

@pcklink
Copy link
Author

pcklink commented Apr 21, 2020

The protocol could have a clearer starting point
-- ready to get started takes you to AFIDs protocol >> skipping the linear transform
-- have a steps list (numbered?)

@jclauneuro
Copy link

Agree, the AC-PC transform should be the first step of the AFIDs protocol probably with a small blurb about the role of that transformation (why is it important) and perhaps some historical background. This issue is not specific to afids-macaca and can probably be moved to afids-protocol.

@greydongilmore greydongilmore transferred this issue from afids/afids-macaca May 7, 2020
@greydongilmore greydongilmore transferred this issue from afids/afids-protocol-old Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants