Epi DEMIC deconvolution error in Icy protocols for batch deconvolution

Dear all,

I have an Icy protocol I use to deconvolve images in batch, and the Epi DEMIC bloc is appearing empty (i.e. nothing in the grey box).

When I try to re-add a new Epi DEMIC bloc, I get the following message:

Unable to insert block: plugins.ferreol.demics.EpiDEMIC
Reason: java.lang.NullPointerException: null
Stack trace:
java.lang.NullPointerException
	at plugins.adufour.ezplug.EzVar.setEnabled(EzVar.java:387)
	at plugins.ferreol.demics.EpiDEMIC.initialize(EpiDEMIC.java:658)
	at plugins.ferreol.demics.EpiDEMIC.declareInput(EpiDEMIC.java:1164)
	at plugins.adufour.blocks.lang.BlockDescriptor.<init>(BlockDescriptor.java:140)
	at plugins.adufour.protocols.gui.block.WorkFlowContainer$MenuItemTransferHandler.importData(WorkFlowContainer.java:925)
	at plugins.adufour.protocols.gui.block.WorkFlowContainer.drop(WorkFlowContainer.java:836)
	at java.awt.dnd.DropTarget.drop(Unknown Source)
	at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(Unknown Source)
	at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(Unknown Source)
	at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(Unknown Source)
	at sun.awt.dnd.SunDropTargetEvent.dispatch(Unknown Source)
	at java.awt.Component.dispatchEventImpl(Unknown Source)
	at java.awt.Container.dispatchEventImpl(Unknown Source)
	at java.awt.Component.dispatchEvent(Unknown Source)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
	at java.awt.LightweightDispatcher.processDropTargetEvent(Unknown Source)
	at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
	at java.awt.Container.dispatchEventImpl(Unknown Source)
	at java.awt.Window.dispatchEventImpl(Unknown Source)
	at java.awt.Component.dispatchEvent(Unknown Source)
	at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
	at java.awt.EventQueue.access$500(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.awt.EventQueue$3.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.awt.EventQueue$4.run(Unknown Source)
	at java.awt.EventQueue$4.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

I wondered if anyone has experienced this problem please?

Many thanks for your help!

David

Dear David,

I am inviting @FerreolS to join this topic.
I can reproduce your issue with Icy version 2.1.2.0 and EpiDEMIC plugin version 1.2.2.0.

Best regards,
Marion

1 Like

Thank you Marion and thank you both for your help!

1 Like

Dear David
Thank you for reporting this issue. I’m also able to reproduce it with the latest Icy.
It is probably a regression likely caused by a recent update of icy and/or protocols plugin. Unfortunately I’m very busy these weeks and I will not able to dig into this in a close future. You can either fix that issue in the code (everything is here https://github.com/FerreolS/tipi4icy ) or wait a month or two until I fix that issue.
I’m sorry to not be able to do it faster.
Regards,

Ferréol

2 Likes

Dear Ferréol,

Thank you for making Epi DEMIC in the first place! And thank you for looking into it when you can.

I’m sorry I don’t have the skills to fix the code myself unfortunately, but if this is a regression issue, in the meantime would it be possible that the bloc and protocol would work if I had access to older versions of Icy, and the Epi DEMIC and Protocols plugins, from last year for example?

Many thanks and all the best,

David

1 Like

You’re right. It can we a good way to wait the fix.
The protocol was working fine before Icy migration to maven (2.0.3) and maybe some versions
after.
Regards,

Ferréol

1 Like

Dear Ferréol and Marion,

The protocol is now working with Icy 2.0.2.0, after I disable the automatic updates in Preferences.

Thanks for your help and all the best!

David

1 Like