Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Training percentage is not changed

See original GitHub issue

Describe the bug

Training: 0%| I am curious whether this should be updated during the training process? What does it mean and why it’s always 0?

Training:   0%|                                                                                                                                                                                                                                   | 19/18446744073709551614 [00:30<8397595460610142:26:08,  1.64s/it]
Running evaluation for step: 20, epoch: 9
Evaluation train: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:00<00:00,  2.48it/s]
Evaluation valid: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  8.17it/s]
Evaluation test : 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00,  4.10it/s]
╒═══════════════╤═════════╤═══════════╤════════════╕
│ recommended   │    loss │   roc_auc │   accuracy │
╞═══════════════╪═════════╪═══════════╪════════════╡
│ train         │  9.4732 │    0.4988 │     0.6348 │
├───────────────┼─────────┼───────────┼────────────┤
│ validation    │ 10.2174 │    0.4984 │     0.6346 │
├───────────────┼─────────┼───────────┼────────────┤
│ test          │ 10.0118 │    0.4991 │     0.6395 │
╘═══════════════╧═════════╧═══════════╧════════════╛
╒════════════╤═════════╕
│ combined   │    loss │
╞════════════╪═════════╡
│ train      │  9.4732 │
├────────────┼─────────┤
│ validation │ 10.2174 │
├────────────┼─────────┤
│ test       │ 10.0118 │

To Reproduce Steps to reproduce the behavior:

ludwig init_config --dataset /data/rotten_tomatoes.csv --target=recommended --output /data/rotten_tomatoes.yaml
ludwig train --config rotten_tomatoes.yaml --dataset /data/rotten_tomatoes.csv

Expected behavior the number should vary?

Screenshots

Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]
Python version - 3.8
Ludwig version - 0.6.0.dev

Additional context Add any other context about the problem here.

Issue Analytics

State:
Created a year ago
Comments:12 (2 by maintainers)

Top GitHub Comments

1reaction

arnavgarg1commented, Oct 1, 2022

Hi @Jeffwan - great catch, and thanks for sharing. I was able to reproduce this locally using the steps you mentioned. I will investigate and have a fix for you next week.

1reaction

Jeffwancommented, Aug 29, 2022

Let me follow your steps and see how it goes. I will bring more details back later