NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 491 - Grid/Collection stitching Class Not Found
Grid/Collection stitching Class Not Found
Status: RESOLVED FIXED
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Windows
: P4 normal
Assigned To: Johannes Schindelin
Depends on:
Blocks:
 
Reported: 2012-09-13 20:49 CDT by Conor
Modified: 2013-01-10 16:26 CST
3 users (show)

See Also:

Description Conor 2012-09-13 20:49:59 CDT
Hi,

When I run Grid/Collection stitiching with unknown position I get the error: Plugin or Class not found: "Stitching_grid" followed by: java.lang.ClassNotFoundException: Stitching_Grid after it finds all files. This function was working fine until I did a clean reinstall of Fiji, now it produces this error. This happens even with very small sets of images. (and sets of images that worked previously)

Conor


Information about your version of Java - this information is useful for the Fiji developers:

  os.arch => amd64
  os.name => Windows 7
  os.version => 6.1
  java.version => 1.6.0_24
  java.vendor => Sun Microsystems Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_24-b07
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 19.1-b02
  java.vm.vendor => Sun Microsystems Inc.
  java.vm.info => mixed mode
  java.awt.graphicsenv => sun.awt.Win32GraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.6
  sun.cpu.endian => little
  sun.desktop => windows
  file.separator => \

The up-to-date check says: UP_TO_DATE
Comment 1 Johannes Schindelin 2012-09-13 21:23:52 CDT
Could you run Help>Update Fiji and verify in the advanced mode that you have the file plugins/Stitching_.jar? If not, you might need to update it manually (although in that case, I would not understand why the updater would not do that automatically for you).
Comment 2 Conor 2012-09-13 22:01:26 CDT
Hi,
I think everything is up to date http://imgur.com/3IDcM Here is an image. Also, here is an image of the error http://imgur.com/neauB
Comment 3 Johannes Schindelin 2012-09-13 23:02:03 CDT
Hmm. Indeed, from the screenshots, it looks as if everything was alright. Would you be willing to send me a Fiji package made by Plugins>Utilities>Make Fiji Package? Ideally you would use Help>Upload Sample Image to get it to me.
Comment 4 Conor 2012-09-13 23:09:52 CDT
Ok, uploaded as fiji-win64-20120913020640Bug491.zip
Comment 5 Johannes Schindelin 2012-09-14 00:27:45 CDT
I unpacked that file onto the Desktop on a Windows 7 Enterprise 64-bit and it correctly opens the plugin when I click on Plugins>Stitching>Grid/Collection stitching.

Puzzled...

Could you unpack the package onto your Desktop (careful not to overwrite any existing Fiji.app folder, if any) and try again?
Comment 6 Conor 2012-09-14 01:08:47 CDT
Hello,

Well this is embarrassing, I unpacked it and it runs just fine. Maybe I had it in some secured subfolder by accident.

Thanks for the help!

Conor
Comment 7 Johannes Schindelin 2012-09-14 03:10:20 CDT
No worries! If you hit the issue, so do others, and the bug is really surprising!

So I would really like to do something about it, such as warning the user that they are running in a restricted folder.

Did you have Fiji.app in C:/Program Files, perchance? For above-mentioned warning I'd need a better idea how to detect the situation... :-)
Comment 8 Conor 2012-09-14 03:44:37 CDT
Hello,
I was running out of the downloads folder. It appears to continue to have this problem if I run it from there. If I move it up one level the problem goes away. 

I got access to another computer after you solved this and I can run from the downloads folder on it with no problem.

Conor
Comment 9 Lars Damgaard 2013-01-10 16:26:43 CST
I just experienced exactly the same problem; my Fiji.app folder is on my Desktop. However, i after closing and opening Fiji again, the problem had dissappeared. So maybe this is also what happened to Conor, and thus not a restricted folder issue?