CollectionReaderDescription/AnalysisEngineDescription as Discriminator

4 views
Skip to first unread message

Torsten Zesch

unread,
Feb 12, 2016, 12:10:50 PM2/12/16
to dkpro-lab-developers
When using CollectionReaderDescription/AnalysisEngineDescription as Discriminators the values in the discriminators.txt are somewhat bloated as the Descriptors seem to contain whole type systems.

Is there a way around that, e.g. by "naming" discriminator values?

thanks,
Torsten

Richard Eckart de Castilho

unread,
Feb 12, 2016, 12:21:39 PM2/12/16
to dkpro-lab-...@googlegroups.com
Hi,

if you use Groovy, yes ;) But the support is in general also available for Java.

So first Groovy ;)

def dimDataset = new ClosureDimension("dataset", [
datasetX: { createReaderDescription(...) },
datasetY: { createReaderDescription(...) }])

The discriminators.txt file will then have

dataset = datasetX

The underlying support to enabled this is the "Discriminable" and has
e.g. also been used in DKPro TC to name feature extractor configurations:

de.tudarmstadt.ukp.dkpro.tc.core.util.ExperimentUtil.NamedArrayList<T>

Cheers,

-- Richard
Reply all
Reply to author
Forward
0 new messages