Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BatchTask produces nonsensical log messages #77

Open
logological opened this issue Jul 17, 2015 · 3 comments
Open

BatchTask produces nonsensical log messages #77

logological opened this issue Jul 17, 2015 · 3 comments

Comments

@logological
Copy link
Member

The DKPro Lab BatchTask produces logging messages such as the following:

2015-07-17 15:19:31  INFO [main] (BatchTask) - Completed configuration 2 of 1 (200%  ETA 00:00:-9.-165  RUN 00:00:18.331  AVG 9166  LAST 8274)

There are a couple problems here — first, in the "Completed configuration x of y" part, we have x > y. Second, the progress percentage is greater than 100%. Third, the ETA has negative values for the seconds and milliseconds.

I was able to reproduce this problem using several different experiments. For a simple and ready-made one, run de.tudarmstadt.ukp.dkpro.tc.groovyexamples.single.unit.BrownUnitPosDemo from DKPro TC 0.8.0-SNAPSHOT. (Be sure to adjust the logging level first so that DKPro Lab's messages are visible.)

@daxenberger
Copy link
Member

This problem occurs in DKPro TC Cross-Validation setups (as a product of overrding the execute() method of the BatchTask). Maybe the FoldDimensionBundle which we use to split the input data into n folds/dimensions isn't properly handeled by the ProgressMeter?

@reckart
Copy link
Member

reckart commented Aug 19, 2015

Sounds like a bug in TC rather than in Lab. The ProgressMeter just shows what it's being told. If it is getting told that there are 100 things to do but 200 things that have been done, then the output will be as you see it. I don't think that ProgressMeter should start throwing exceptions in such a case. What would you expect?

@daxenberger
Copy link
Member

No, ProgressMeter itself is not the problem. Either, we are using FoldDimensionBundle (used for the split into folds in crossvalidation setups) in DKPro TC incorrectly, or the execute() Method in BatchTask, which calculates the expected size for the ProgressMeter (ll. 154ff in BatchTask), does not handle Dimensions from FoldDimensionBundles correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants