Task is 4135 error
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I would be extremely grateful for your kind support. I have been trying to benchmark 3 learners namely logreg, randomforest, rpart, using batchtools. Unfortunately the execution of my program gets struck (it doesn’t stop nor execute) upon reaching reaching ml task id=189778 and dataid=4135, I am unsure what may be the problem.
The program stays struck nomatter how long I leave it.
The last log for the execution shows as follows:
[bt]: This is batchtools v0.9.11
[bt]: Starting calculation of 1 jobs
[bt]: Setting working directory to 'C:/Users/Comm/Documents/BENCHMARKv18/Data/Results/Batchtools'
[bt]: Memory measurement disabled
[bt]: Starting job [batchtools job.id=285]
[bt]: Generating problem instance for problem '4135' ...
[bt]: Applying algorithm 'eval' on problem '4135' for job 285 (seed = 286) ...
Data '4135' file 'description.xml' found in cache.
Data '4135' file 'dataset.arff' found in cache.
Task: Amazon_employee_access, Learner: classif.logreg
Resampling: repeated cross-validation
Measures: acc brier
I will look forward to your kind guidance. I don’t understand if there is some problem with the task or it has something to do with the batchtools as the execution of the other tasks works perfectly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the batchtools v0.9.11 log for job 285 and task/data 4135, comparing it with tasks that complete. Check whether the stall occurs during problem generation, learner execution, or repeated cross-validation for Amazon_employee_access. Done means identifying whether the task or batchtools causes the hang and documenting a reproducible diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100