My console freeze when I run my "lazy prediction" script

Question

0.00/5 (No votes)

See more:

I have tried to use the "lazypredict" package but whenever I ran it, it stuck at certain place. Originally , I thought it just took time to run the data, so I have left my computer running for 2 weeks. It keep in the same status after 2 weeks? May I know if there is anyway I can solve this problem ?

I only got one line in my console and keep stuck at the same status for 2 weeks:

59%|█████▊ | 17/29 [13:50:35<5:34:46, 1673.91s/it]

What I have tried:

I have tried to trim down the the data size so that the lazy prediction can be run completely, but it still freeze at the same place

Posted 26-May-22 19:38pm

kk009911

Updated 26-May-22 19:54pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2022-05-26T19:54:00

Really, we can't help you: we have no access to yoru code or the data it is working with.

But two weeks for a single line of text looks like a problem to me - and it's either your code or the data it's working with that is at fault.

So start debugging it: pdb — The Python Debugger — Python 3.10.4 documentation[^] may help to start working out where the problem is, but it needs access to your code while it's running and with your data to even begin working anything out. Even then, it's probably going to take quite a bit of time to work out where the problem is, let alone how to fix it!

Good luck - but we can't do anything for you.