Recent changes to bugs

Can't import 2D images

Anonymous — Tue, 28 Mar 2006 13:12:31 -0000

When I try to import a set of 2D images numbered
image021.tif to image177.tif, Microview doesn't import
them, then gives a crash message when it is closed.
This is the same for bmp and png files, and for 24 bit
colour and 256 shades of grey.

The Microview.exe.log says:

LookupError Exception in Tk callback
Function: <function <lambda> at 0x05F40B30> (type:
<type 'function'>)
Args: ()
Traceback (innermost last):
File "Pmw.pyo", line 1784, in __call__
None
File "Pmw.pyo", line 2126, in <lambda>
None
File "Pmw.pyo", line 2105, in _doCommand
None
File "MicroViewIO.pyo", line 388, in ImageImport
None
LookupError: unknown encoding: cp1252

Steven Hammer
steven.hammer@ed.ac.uk

importing raw data

Anonymous — Tue, 18 Jan 2005 19:11:56 -0000

Cannot import raw data using .ngo and .img files as
described in your HOWTO MicroView import/export raw
data document. After selecting .ngo file from the
File/Open dialog box nothing happens. I installed version
1.15.

t_clarin@hotmail.com

Volume Render Plugin does not display everything

Andrew Wheatley — Thu, 25 Sep 2003 15:40:40 -0000

Linux version 1.1beta1:

All but the image at the top of the 'Render Image...'
plugin
show up when called. No error messages.

vff image shifted

Andrew Wheatley — Tue, 23 Sep 2003 15:19:52 -0000

The slice of a 3d vff image on the z and y axes appear
to be shifted along the x-axis by about 40% of the
image width. The x axis is fine.
I've tested the appearance of the z axis with my own
software.

I checked out the software on Sept 22. I'd attach the
file but its
64 Megs.

VFF files not saved correctly

Anonymous — Thu, 14 Aug 2003 13:17:42 -0000

When using "Image Import..." on the file menu to create
a volume, if the Z spacing is set to, say, 29mm, the
volume displays correctly. However, once saved as a
*.vff file, the volume is the wrong size (compressed to
Z=1mm I think).

Workaround is to save everything as a *.vtk file.
Volume isn't compressed then.

I would use vffheader to check how it is being saved,
but vffheader doesn't run, coming up with a 'The
instruction at "0x77fc911e" referenced memory at
"0x0145259d". The memory could not be "read".' error.

Steven Hammer
steven.hammer@ed.ac.uk

raw file import not fuctional on 1.15 b2

Anonymous — Wed, 11 Jun 2003 13:26:53 -0000

In testing 1.15 b2 as part of background research
on this GEMS product we find that Microview
cannot import 2D or 3D files using the described
.nfo methodology. While we find that the Analyze
format does work it performs a byte reversal on
the code. We have not tested the earlier implementation
to see if this functionality was broken during an
upgrade.

The platform is a Dual P4 Xeon platform with 2Gb
of memory and running Windows NT SP4.

Doug Morris, NIH
dmorris@nih.gov

Isosurface remains in memory after close?

Ken Kozloff — Wed, 19 Mar 2003 18:24:31 -0000

After displaying an isosurface, then closing MicroView,
it looks like the volume or surface information is kept as
an active task in WindowsXP and the process must be
closed manually through the task manager.

File reading problem -> Isosurface messed up

Mathieu Malaterre — Mon, 17 Mar 2003 19:11:43 -0000

Step to reproduce bug:

1. Start MicroView (without filename)
2. Open a VTK StructuredPoints image
3. Go To plugins/Isosurface

The isosurface will be calculated on the last image.

Another way to see the bug is through the command line:

$ MicroView filename.vtk
Traceback (most recent call last):
File
"/usr/lib/python2.2/site-packages/MicroView/MicroView.py",
line 1867, in ?
MView = MicroView()
File
"/usr/lib/python2.2/site-packages/MicroView/MicroView.py",
line 668, in __init__
self.OnFileOpen(tmpFileName)
File
"/usr/lib/python2.2/site-packages/MicroView/MicroView.py",
line 1305, in OnFileOpen
self.ProcessImage()
File
"/usr/lib/python2.2/site-packages/MicroView/MicroView.py",
line 1444, in ProcessImage
if self.reader.DoesElementSizeExist() == 1:
File
"/usr/lib/python2.2/site-packages/vtkEVS/EVSImageReader.py",
line 137, in DoesElementSizeExist
spacing = self.GetDataSpacing()
File
"/usr/lib/python2.2/site-packages/vtkMultiIO/vtkMultiImageReader.py",
line 153, in __getattr__
return getattr(self._reader, attr)
AttributeError: GetDataSpacing

This only happen with VTK structured points images.

Save As feature is generating incorrect header information

Faruq Ladak — Fri, 14 Mar 2003 22:35:22 -0000

When saving a file as vff using the File | Save As
feature, the origin in the new file is incorrect if the
origin in the original file is something other than
(0, 0, 0) and the spacing is something other than
(1, 1, 1).

MV crashes when loading images that have been reoriented

Faruq Ladak — Thu, 06 Mar 2003 17:24:18 -0000

MicroView crashes when loading images that have
been reoriented using the Reorient Image plugin.