ProM 6 (dev) plugin update

[Deleted User]

Probably you already know this issue and it's due to the in-progress-development-status of ProM 6.

I set up the dev environment for plugins implementation as explained in the documentation. First of all many compliments for the macro editor for combining plugin, it's really useful and simple to use. However, when launching the application, the plugin update procedure gives some warning of type:

"Method X is could not be added as a plugin. The context should be asked as first parameter and should be a the same, or a superclass of org.processmining.contexts.gui.GUIPluginContext.
Plugin X could not be added as a plugin. At least one variant has to be specified".

I hope this warning could be useful.

[Deleted User]

I hope this is the right place to post such info. If not, please point me to the correct location.

JBuijs

Grace,

The error should be easy to fix by the plug-in author.
What is the exact plug-in where this error occurs for that you would like to run? And could you notify the author of this plug-in of this error? He/she should be able to fix it and release a new, correct, version of the plug-in.

Hope this helps,

Joos

[Deleted User]

Joos,

in the following I post the list of plugins that seem to generate the error (extracted from the Eclipse red console messages during the startup of "ProM with GUI").
The list is huge (about 100 entries; maybe there are some duplicates). If someone could replicate this situation probabily a mailing list message would be the best alerting strategy.

-- in what follows I removed the prefix "org.processmining.plugins"
guidetreeminer.GuideTreeMinerPlugin
bpel.exporting.BpelExport
statistics.abstraction.existence.ExistenceAbstractionPlugin
statistics.abstraction.definition.AbstractionDefinitionPlugin
statistics.r.dataset.RDataSetPlugin
statistics.abstraction.projection.ProjectionPlugin
statistics.abstraction.lastoccurrence.LastOccurrenceAbstractionPlugin
statistics.r.basiccommand.RcommandPlugin
statistics.abstraction.attributeprojection.AttributeProjectionPlugin
statistics.abstraction.bag.BagAbstractionPlugin
statistics.abstraction.cardinality.CardinalityAbstractionPlugin
statistics.abstraction.set.SetAbstractionPlugin
statistics.r.regressioncommand.RegressionPlugin
statistics.r.regressioncommand.a.RegressionPlugin
statistics.r.basiccommand.RConnectPlugin
statistics.abstraction.composition.AbstractionCompositionPlugin
heuristicsnet.miner.heuristics.miner.FlexibleHeuristicsMinerPlugin
heuristicsnet.miner.heuristics.miner.HeuristicsMinerPlugin
heuristicsnet.miner.mdh.miner.MDHPlugin
log.timeframe.TimeFrame
log.logfilters.ui.LogFilterPlugin
signaturediscovery.SignatureDiscoveryPlugin
abstractions.PatternAbstractionsPlugin
loginsertstart.AddStPlugin
regressionmining.gui.RegMinerPlugin
pnml.exporting.PnmlExportNetToPNML
pnml.exporting.PnmlExportNetToEPNML
context.ContextMiningPlugin
petrinet.unfolding.UnfoldPN
tracealignment.TraceAlignmentPlugin
ltlchecker.LTLChecker
log.reverse.TraceReverser
operationalsupport.OperationalSupportPlugin
flex.replayer.FlexLogReplayer
flex.replayer.FlexReplayBenchmark
conformance.etconformance.ETCPlugin
tsml.exporting.TsmlExportTS
lola.LoLA_Plugin
wendy.Wendy_Plugin
declare.exporting.DeclareExport
heuristicsnet.miner.genetic.miner.GeneticMinerPlugin4UITopia
fuzzymodel.miner.FuzzyMiner
fuzzymap.FuzzyMapVisualization
ptnBasedPreprocess.plugin.PatternBasedPreprocessPlugIn
fuzzymap.miner.FuzzyMapMiner
ATPN2010
BPM2010
configuration.exporting.CfgExportNet
connectionfactories.logpetrinet.LogPetrinetConnectionFactory
log.exporting.ExportLogMxml
log.exporting.ExportLogMxmlGz
log.exporting.ExportLogXes
log.exporting.ExportLogXesGz
guidetreeminer.GuideTreeMinerPlugin
bpel.exporting.BpelExport
statistics.abstraction.existence.ExistenceAbstractionPlugin
statistics.abstraction.definition.AbstractionDefinitionPlugin
statistics.r.dataset.RDataSetPlugin
statistics.abstraction.projection.ProjectionPlugin
statistics.abstraction.lastoccurrence.LastOccurrenceAbstractionPlugin
statistics.r.basiccommand.RcommandPlugin
statistics.abstraction.attributeprojection.AttributeProjectionPlugin
statistics.abstraction.bag.BagAbstractionPlugin
statistics.abstraction.cardinality.CardinalityAbstractionPlugin
statistics.abstraction.set.SetAbstractionPlugin
statistics.r.regressioncommand.RegressionPlugin
statistics.r.regressioncommand.a.RegressionPlugin
statistics.r.basiccommand.RConnectPlugin
statistics.abstraction.composition.AbstractionCompositionPlugin
heuristicsnet.miner.heuristics.miner.FlexibleHeuristicsMinerPlugin
heuristicsnet.miner.heuristics.miner.HeuristicsMinerPlugin
heuristicsnet.miner.mdh.miner.MDHPlugin
log.timeframe.TimeFrame
log.logfilters.ui.LogFilterPlugin
signaturediscovery.SignatureDiscoveryPlugin
abstractions.PatternAbstractionsPlugin
loginsertstart.AddStPlugin
regressionmining.gui.RegMinerPlugin
pnml.exporting.PnmlExportNetToPNML
pnml.exporting.PnmlExportNetToEPNML
context.ContextMiningPlugin
petrinet.unfolding.UnfoldPN
tracealignment.TraceAlignmentPlugin
ltlchecker.LTLChecker
log.reverse.TraceReverser
flex.replayer.FlexLogReplayer
flex.replayer.FlexReplayBenchmark
conformance.etconformance.ETCPlugin
tsml.exporting.TsmlExportTS
lola.LoLA_Plugin
wendy.Wendy_Plugin
declare.exporting.DeclareExport
heuristicsnet.miner.genetic.miner.GeneticMinerPlugin4UITopia
fuzzymodel.miner.FuzzyMiner
fuzzymap.FuzzyMapVisualization
ptnBasedPreprocess.plugin.PatternBasedPreprocessPlugIn
fuzzymap.miner.FuzzyMapMiner

JBuijs

Grace,

This is a known problem that needs to be solved by the plug-in developers individually.

We are preparing an official release of ProM 6 for the BPM 2010 conference at the moment. Testing is nearing completion. Installing the BPM 2010 package from the package manager should install all tested and working packages/plug-ins for ProM.
Other packages are not tested as thoroughly as the ones included in the BPM 2010 package.

I understand that the red error messages appear alarming but everything still works.

Good luck in developing plug-ins!

Joos

[Deleted User]

Ok, thank you for the answer. I will wait the next release.

JBuijs

Hi Grace,

You don't need to wait until the next release. ProM and its plug-ins work and you can also start developing your own plug-ins without problems.

Joos

[Deleted User]

Hi Joos,

first of all a premise: I'm interested in "developing" new plugins chaining existing ones, as I saw in the macro definition window of the plugin development application.

The issue is not completely clear to me: (almost) everything in the "production" release works, but the same plugins working in production are not working in the development version (as I reported above).

Is it right?

If so, I don't understand why you say that "everything still works", because from my point of you it does not. By the way, it's quite strange that some plugins working in production (e.g. Heuristics Miner) are not working in the development release.

However, I understand that testing the production package in sight of BPM 2010 it's the team priority, thus I'm not complaining.

If the above thesis it's wrong, please help me solve my being stuck.

And thank you for the time you commit to answer my question!

JBuijs

Hi Grace,

Where did you read about the macro's? These were, unfortunately, removed from the functionality list in early 2009.
It is however possible to call plug-ins on resulting objects from other plug-ins programmatically so in a way it is still possible but only by creating a special plug-in.

Furthermore, there is not much difference between 'release' and 'production' at the moment. Releases are still beta releases after significant source code updates of ProM. Packages are released and tested continuously.
Even when you install the 'source code version' of ProM and the latest beta release side-by-side they will use the same directory to read the installed packages so these should be the same.
The heuristicsminer f.i. should work from the .exe/.bat launch and when you start ProM from Eclipse.

If you still encounter problems, please contact me via e-mail so we can work this out and get you going.

And no thanks, its (part of) my job

Joos

[Deleted User]

I see I didn't explained patently. I get the plugin error when launching the ProM "development environment", as explained here for developing plugin. Launching "ProM with GUI" I can open the "macro definition" window that allow to access a (fantastic) functionality for chaining plugin together. Here those plugins I mentioned above are not present at all, even if they are accessible launching "ProM with UITopia" and in the executable package.

JBuijs

Then I'm afraid that we found the problem. The only 'GUI' for ProM is UITopia. The 'launch ProM with GUI' option in Eclipse was a test version of ProM which is actually discontinued. The only GUI that has been developed and tested is UITopia.

Joos

[Deleted User]

Well, I am taken aback!
Thus, if I got the point, the macro definition will not be possibile in the "stable" version. It's a pity, the composition system is really easy to understand and powerful. So the plugin development documentation is outdated?

However, how to compose plugins? Will it be necessary to write Java code?

JBuijs

To be very brief: yes and yes.

The document you refer to is indeed outdated. A more up-to-date version can be found at http://prom.win.tue.nl:8000/Tracsites/wiki/GettingStarted
If you would like to automatically chain plug-ins you would indeed need to write Java code.

I'm really sorry!

Joos

[Deleted User]

No need to be sorry, only I didn't understand.

Really a pity, I found great the macro definition (I didn't use it thoroughly, thus it's only a first impression). Ok, going back to Java will make me feel younger

JBuijs

Okay, good luck! And keep me updated of your progress since I'm planning to create a plug-in in the near future that would also call several other plug-ins so we might be able to help each other.

Enjoy your rejuvenation cure