|
From: An C. T. <tca...@gm...> - 2012-01-03 06:50:51
|
Hello Jens,
I just checked the revision number of "org.dllearner.confparser" package
and it is currently 2322. therefore, I think it should be the parser for
the old configuration file structure and I tried to use the old examples
files and it can parse the learning configuration file. However, when
the ComponenManager tried to create the learning algorithm component, an
exception occurred:
org.dllearner.core.LearningProblemUnsupportedException: Warning: No
suitable constructor registered for algorithm
org.dllearner.algorithms.celoe.CELOE and problem java.lang.Class.
Registered constructors for org.dllearner.algorithms.celoe.CELOE: [].
at
org.dllearner.core.ComponentManager.learningAlgorithm(ComponentManager.java:493)
at org.dllearner.cli.Start.<init>(Start.java:331)
at org.dllearner.gui.Config.loadFile(Config.java:137)
at org.dllearner.gui.StartGUI.actionPerformed(StartGUI.java:298)
I checked CELOE class anf reconised that the method
supportedLearningProblems() was commented out. I uncommented this method
and it can work. However, there still has another problem that in my
computer, the accuracy value displayed wrongly. Only question marks (?,
in console) or square sign (in GUI) were displayed instead.
Cheers,
An.
On 1/3/2012 5:08 PM, An C. Tran wrote:
> Hello Jens,
>
> I checked out the head revision of the trunk but I could not get
> DLLearner works as well.
> The problem comes from the configuration parser. It seems to me that a
> semi-colon is requires after each configuration entry.
> For example, I tried to run the "trains" examples and the following
> exception was thrown:
>
> INFO - Loading file .... trains_owl.conf.
> INFO - starting component manager ... OK (0ms)
> org.dllearner.confparser.ParseException: Encountered " <ID> "ks "" at
> line 10, column 1.
> Was expecting:
> ";" ...
>
> I tried to add a semi colon at the end of each config option and it
> passed the above exception but another exception occurred:
>
> Exception in thread "AWT-EventQueue-0" java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:796)
> at java.util.HashMap$KeyIterator.next(HashMap.java:828)
> at org.dllearner.gui.Config.loadFile(Config.java:150)
> at org.dllearner.gui.StartGUI.actionPerformed(StartGUI.java:298)
>
> I checked the Config.java and Start.java and it seems to me that
> Start.java does not adapt to the new structure of config file.
> It is still looking for "import" instruction instead of ks.filename
>
> However, it is strange to me that the binary version of DLLearner
> 1.0.1 runs well. I wonder that there is some source codes of the
> interface package have not been committed?
>
> Thank you so much.
>
> Cheers,
> An.
>
>
> On 1/2/2012 9:10 PM, Jens Lehmann wrote:
>> Hello,
>>
>> On 02.01.2012 07:36, An C. Tran wrote:
>>> Hi all,
>>>
>>> I just checked out the source code of DLLearner 1.0.1 (Revision 3518:
>>> /branches/1.0.1) but it did not work for me.
>>> I started by launching StartGUI.java and tested by opening a
>>> configuration file. However, the following exception occurred:
>>>
>>> Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
>>> at
>>> org.dllearner.reasoning.FastInstanceChecker.init(FastInstanceChecker.java:202)
>>>
>>> at org.dllearner.cli.Start.initComponent(Start.java:690)
>>> at org.dllearner.cli.Start.<init>(Start.java:281)
>>> at org.dllearner.gui.Config.loadFile(Config.java:137)
>>> at org.dllearner.gui.StartGUI.actionPerformed(StartGUI.java:298)
>>>
>>> I tried with "examples/forte/uncle_owl_large.conf" and
>>> "examples/trains/trains_owl.conf".
>>> I think this will happen with others as well.
>>>
>>> I tried to remove the comment for "rc = new
>>> OWLAPIReasoner(sources);" at
>>> line 199 but other exceptions happened for the reasoner class (e.g.
>>> if I
>>> use OWL file, exception will happen with OWLAPIReasoner.java and so
>>> on).
>>>
>>> Are there anyone get this revision runs successfully?
>> Chris Shellenbarger (in CC) created the branch for testing various
>> things, e.g. running several learning processes in parallel, about a
>> year ago. Since then, there have been many changes in the main branch
>> (trunk), including the incorporation of some of Chris' ideas from the
>> branch. So all the development is happening in the trunk at the moment.
>> Naming the branch "1.0.1" back then is probably confusing.
>>
>> So unless you have a specific reason for using this branch which I am
>> not aware of, I think it is better to stick with the trunk version.
>>
>> Kind regards,
>>
>> Jens
>>
>
|