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
Interface name changes #1211
Interface name changes #1211
Conversation
- Re-order and modify page on fixels and dixels to emphasize that 'fixel' is the dominant term, and 'dixel' may not be relevant for many readers. - Couple of spelling errors fixed. - Add instructions on how to deal with 'too many open files' error.
This page is not "Crashes, errors and performance issues". In addition, some entries that were duplicated between two pages were removed, and some pages from FAQs have been moved into this page.
I'm getting questions about this all the time, and the most convenient and accurate solution has always been to use this algorithm. If this for some very specific reason didn't work well, msmt_5tt didn't work either; and either the -fa parameter of dhollander could be tweaked for a good solution, or, worst case, manual selection of responses was the last resort. Offering a quick, convenient and accurate solution has always been my intention here, with the aim of multi-tissue csd to be more accessible, and hence to encourage its adoption. It's also good for the perception of msmt-csd that it produces a good quality output; which does depend on good quality responses, obtained without hassle.
This section about setting the CPU architecture was included in the standalone installer instructions due to the fact that we used to run with -march=native - this was likely to cause issues for this type of installation specifically. Now that the default is up to the compiler, there is no longer any reason for this section to be where it is.
More to follow, this is a work in progress at this stage. Just committing now to check the readthedocs output for layout.
- tck2connectome: Add references. - FAQ: Add descriptions of some common issues encountered, including: tcknormalise requiring warpcorrect to be applied beforehand; 5ttgen fsl failing at the FIRST segmentation step.
…ect to the Tournier et al. 2013 publication, differences with respect to 'tax' algorithm
Bonus: via this, the latest |
@dchristiaens: I also have |
@Lestropie , I suppose you may understand this better than I do; see these tests failing: https://travis-ci.org/MRtrix3/mrtrix3/jobs/317859241 From my end, it seems more (pylint) tests started failing since I've merged in EDIT: I've probably got it figured out... |
FYI, in preparation for this merging to |
Alright, there we go. Just to stress the above again: there's now also a |
For anyone who wishes to continue discussing anything interface (naming) related, please resort to #1147. The issue is left open for that purpose. Should it lead to anything, happily create another branch and pull request. |
Late to the party, but: Should |
Up to you. I think the |
Starting to implement some name changes on the TODO list (#1147). I started with the least controversial one (
-stride
-->-strides
). It would be good to get some of this done if we prefer to do adev
tomaster
release soon, for the sake of getting #1206 out.I marked this as "help / test wanted" because some of this requires widespread scattered changes, in code as well as scripts and documentation. It's very easy to overlook some bits here... so if anyone finds time: always welcome to help out, and even just check that nothing gets forgotten.