 |
I'm -1 on this idea. It needlessly clutters the interface to put "download" buttons for versions of Slicer4 that don't exist. I've never seen that done anywhere else. A much simplier alternative is to add a line that says "Why are there no 32-bit binary distributions available for Linux?" and link off to somewhere that describes the technical reasons why. If someone writes that page/section, I can make the link. |
 |
Michael: Very good point. I like the idea of the question. Having this questions/answers nicely organized with some graphic would be very helpful. Assigning the issue to Steve for feedback |
 |
The discussion started with the observation by Ron that many real-world image analysis tasks cannot be completed on 32 bit systems. Also it was noted by Kilian that he gets a lot of support questions about EMSegmenter that end up being memory issues (particularly on win32) since the segmenter has one volume per-structure in the atlas. The goal here was to make it clear to users what they can expect before they download the wrong version. This could be in the form of a table with a title like "Which Slicer version is best for me?" that points out the trade-offs. |
|
|
Doesn't sound like you need a table or a discussion of tradeoffs -- that's needlessly complicated. download.slicer.org is specifically aimed at making first- or second-contact with Slicer be as straightforward as possible. Correct me if I'm wrong: what you want to have is something that says, "Limitations of 32-bit Slicer builds", and have that refer to some accurate, helpful, focused text on the topic, possible as part of an FAQ. The answer to this question should include what you probably generally can do with 32-bit Slicer (to keep the lowest common denominator low) as well as what you probably or definitely can't do (to minimize user surprise and set reasonable expectations). I am not sufficiently familiar with this limitations to write the text, but I can make the link and add the pointer. |
|
|
Whichever you think is best Mike - just go ahead. |
|
|
The text can simply say: "Note that many clinical research tasks, such as processing of large CT or MR volumetric datasets, require more memory than can be accommodated with a 32 bit program. We advise the use of the 64 bit versions of the Slicer wherever feasible." |
 |
|
|
|
Can the download page be updated with this warning? Some of the students helping Sonia have been tripped up with this issue. |
|
|
Hi Folks, During the past few years, possible improvements that would help minimizing user confusion related to either Slicer documentation or Slicer wiki have been entered in the Slicer bug tracker. Looking retrospectively, it seems not to be the most efficient way of keeping track of these tasks. These ones have been re-targeted from one release to an other (particularly the one related to Mediawiki) To avoid cluttering the bug tracker and artificially increase the amount of issues left to complete the coming 4.3 release (or the coming ones), I just marked these issues as closed and created a wiki page to better document what could be improved. See http://www.slicer.org/slicerWiki/index.php/Documentation/Labs/DocumentationImprovments If you think, tracking these issue with mantis still makes sense, feel free to re-open the issue. Do not hesitate to improve the wiki page. For the first draft, I simply referenced the closes issue. Let me know what you think, |
- Anonymous
