git HEAD - very slow response after resizing view area on high res (0.7mm iso) scans

[gdevenyi]

I have two scans I'm trying to view at 0.7mm (a T1 and T2), and I wanted to increase the viewing area, so I used the ability to resize the view area. After doing so register is exceptionally slow to respond to anything.

[rdvincent]

@gdevenyi Thanks for the report - I've not experienced anything like this. Does anything else seem wrong or incorrect, or is the UI just slow to respond?

[gdevenyi]

The top half the intensity/ratio control on the overlap column bugged out (blank), but that may have been due to the "non responsive" GUI rather than a glitch.

[rdvincent]

@gdevenyi Can you send me the mincinfo for these files when you have a second?

[gdevenyi]

Can't do mincinfo because they're NIFTIs, but here's the PrintHeader outputs

 Spacing [0.7, 0.7, 0.7]
 Origin [-90, 126, -72]
 Direction 
1 0 0
0 -1 0
0 0 1

 Size : 260 311  260

  Image Dimensions   : [260, 311, 260]
  Bounding Box       : {[-90 126 -72], [92 343.7 110]}
  Voxel Spacing      : [0.7, 0.7, 0.7]
  Intensity Range    : [0, 26.0918]
  Mean Intensity     : 1.0136
  Direction Cos Mtx. : 
1 0 0
0 -1 0
0 0 1

  Voxel->RAS x-form  : 
  Image Metadata: 
    bitpix = 32
    cal_max = 0
    cal_min = 0
    datatype = 16
    dim[0] = 3
    dim[1] = 260
    dim[2] = 311
    dim[3] = 260
    dim[4] = 1
    dim[5] = 1
    dim[6] = 1
    dim[7] = 1
    intent_code = 0
    intent_p1 = 0
    intent_p2 = 0
    intent_p3 = 0
    pixdim[0] = -1
    pixdim[1] = 0.7
    pixdim[2] = 0.7
    pixdim[3] = 0.7
    pixdim[4] = 0
    pixdim[5] = 0
    pixdim[6] = 0
    pixdim[7] = 0
    qform_code = 2
    qoffset_x = 90
    qoffset_y = -126
    qoffset_z = -72
    quatern_b = -0
    quatern_c = 1
    quatern_d = 0
    scl_inter = 0
    scl_slope = 1
    sform_code = 1
    slice_duration = 0
    slice_end = 0
    slice_start = 0
    srow_x = -0.7 -0 0 90
    srow_y = -0 0.7 -0 -126
    srow_z = 0 0 0.7 -72
    toffset = 0
    vox_offset = 352

 Spacing [0.7, 0.7, 0.7]
 Origin [-90, 126, -72]
 Direction 
1 0 0
0 -1 0
0 0 1

 Size : 260 311  260

  Image Dimensions   : [260, 311, 260]
  Bounding Box       : {[-90 126 -72], [92 343.7 110]}
  Voxel Spacing      : [0.7, 0.7, 0.7]
  Intensity Range    : [0, 25.5968]
  Mean Intensity     : 1.01203
  Direction Cos Mtx. : 
1 0 0
0 -1 0
0 0 1

  Voxel->RAS x-form  : 
  Image Metadata: 
    bitpix = 32
    cal_max = 0
    cal_min = 0
    datatype = 16
    dim[0] = 3
    dim[1] = 260
    dim[2] = 311
    dim[3] = 260
    dim[4] = 1
    dim[5] = 1
    dim[6] = 1
    dim[7] = 1
    intent_code = 0
    intent_p1 = 0
    intent_p2 = 0
    intent_p3 = 0
    pixdim[0] = -1
    pixdim[1] = 0.7
    pixdim[2] = 0.7
    pixdim[3] = 0.7
    pixdim[4] = 0
    pixdim[5] = 0
    pixdim[6] = 0
    pixdim[7] = 0
    qform_code = 2
    qoffset_x = 90
    qoffset_y = -126
    qoffset_z = -72
    quatern_b = -0
    quatern_c = 1
    quatern_d = 0
    scl_inter = 0
    scl_slope = 1
    sform_code = 1
    slice_duration = 0
    slice_end = 0
    slice_start = 0
    srow_x = -0.7 -0 0 90
    srow_y = -0 0.7 -0 -126
    srow_z = 0 0 0.7 -72
    toffset = 0
    vox_offset = 352

[rdvincent]

@gdevenyi OK I created two MINC files that are similar (random floats, 0.7mm isotropic, same lengths) and I can't easily reproduce the behavior. How easy is it to trigger this on your system? Is there some sequence of events that consistently causes the problem?

[gdevenyi]

Dragging the adjustment bars to make the middle window as large as possible triggers the problems.

[rdvincent]

@gdevenyi Thanks, I have it now.

[rdvincent]

@gdevenyi I think this should be fixed, at the cost of enforcing a minimum (very small) size for the panels.