Menu

#6 display coordinates vary with loading

open
nobody
3
2003-05-14
2001-06-19
Anonymous
No

I use the file dialog to select a dataset.
I browse to the directory of the data and click on one
of the
files in the no header dataset I want to load.
The interface selects a name and a file range e.g.
I.001-I.124 for me
as defaults.

The bug is, the location in 3D space seems to vary
depending on
which of the 124 files I click on in order to get the
above selection.
If I always select I.001 the data loads fine. If I
select I.060 the
same slicer UI appears, but it operates differently -
the data loads
in a different position. If this is the desired
behavior then I think
the file loading UI should indicate the position at
which the data
will load.

Discussion

  • Lauren O'Donnell

    Logged In: YES
    user_id=240253

    I do not fully understand the bug report. By position, do
    you mean the number that the image is given in the slicer,
    or do you mean the way the volume is centered in the cube
    for viewing?

    The slice numbers always start at 0 regardless of the image
    number that was read in. The placement of the volume just
    centers it in the cube.

    I think you will not get emailed when I post this comment:
    it would be better if you apply for a sourceforge account
    and login before posting bug reports. (this one was posted
    by "nobody")

     
  • Simon Warfield

    Simon Warfield - 2001-06-23

    Logged In: YES
    user_id=12338

    Try this:
    load a data set into slicer by browsing to the file names
    and selecting the first file e.g. I.001
    load the dataset again by browsing to a different first file
    name e.g. I.060
    the slices which are loaded are not displayed at the same
    location as when the entire data set is loaded starting at
    file I.001. Instead there is an offset and the two loaded
    data sets are not ``registered''.

     
  • Steve Pieper

    Steve Pieper - 2003-05-14
    • priority: 5 --> 3
     

Log in to post a comment.

MongoDB Logo MongoDB