-
Notifications
You must be signed in to change notification settings - Fork 4
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
ocr cleaner has bug with gcc library / scikit image version #9
Comments
I've seen two people say to run: Would you have time to try it? |
yep! |
Lord I hope the fix is that easy, an image that doesn't reproduce when you build it again is my worst nightmare. |
It could also help to try installing sckit-learn from conda instead of pip. But I have a terrible feeling there is going to be some new conflict with nolearn (I can't remember off the top of my head why I stayed with python 2.7 in the first place but it was some dependency issue). |
Okay, here is an update! The first error was with libgfortran:
I resolved with:
(if you install without the version you get another error). Then I get this error about numpy versions:
And I'm still trying random numpy versions (from repos where it's reported to work) to see if it resolves. |
It's been resolving the conda enviroment for easily 5 minutes now. :/ |
Is it worth trying to update the entire thing to python 3+, or is that a forest path I don't want to venture down? |
Ack! Thank you for fighting the good fight. I wish dependency hell was a
thing of the past. Need smarter python.
Daniel Snider ツ
…On Fri, Jan 4, 2019 at 5:12 PM Vanessa Sochat ***@***.***> wrote:
It's been resolving the conda enviroment for easily 5 minutes now. :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABqDWMT8AysmENh_Ni6yAmnJa1tJNf9lks5u_9GxgaJpZM4ZtQp7>
.
|
It's a scary forest. My recent adventure down that path may help you a lot.
I recently got `pydicom` and `gdcm` working in py3. Here's how:
pydicom/pydicom#331 (comment)
…On Fri, Jan 4, 2019 at 5:16 PM Vanessa Sochat ***@***.***> wrote:
Is it worth trying to update the entire thing to python 3+, or is that a
forest path I don't want to venture down?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABqDWPFeFIA-mQxM1kvvd05NKgK-aMitks5u_9KpgaJpZM4ZtQp7>
.
|
Thanks, this might help! The issue is with scikit learn but maybe a global update can resolve still... |
okay, so this won't work unless the model is rebuilt from scratch. It was built with an older sklearn, specifically even if I can get the pickle to load the _classes attribute is missing:
This would require downloading the entire CIFAR dataset and doing over. Did you test the original image and it doesn't work for you? -> https://hub.docker.com/r/vanessa/dicom-scraper It's dangerous to use this as a base, but we could potentially do that and install gdcm to read your images. It of course is a (long term) bad idea because we will forever be stuck with that python version, etc., but if you want a quick way to run it that might be easiest. |
That’s sad. Sorry about that. I appreciate your smart, pragmatic advice. The original docker image for the OCR scraper didn’t like my compressed dicom images. If you can share any results showing how well the ocr scraper works that would help me consider the options. We could trade notes later next week!
Thank you again,
… On Jan 4, 2019, at 6:16 PM, Vanessa Sochat ***@***.***> wrote:
okay, so this won't work unless the model is rebuilt from scratch. It was built with an older sklearn, specifically even if I can get the pickle to load the _classes attribute is missing:
AttributeError: 'LinearSVC' object has no attribute 'classes_'`
This would require downloading the entire CIFAR dataset and doing over. Did you test the original image and it doesn't work for you? -> https://hub.docker.com/r/vanessa/dicom-scraper
It's dangerous to use this as a base, but we could potentially do that and install gdcm to read your images. It of course is a (long term) bad idea because we will forever be stuck with that python version, etc., but if you want a quick way to run it that might be easiest.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hey I haven't lost hope - there are still two things to try!
I'll try both this weekend and post an update. It would be really cool to be able to do that comparison! :) |
hey @danielsnider this isn't going to easily work unfortunately, and even rebuilding the model would require substantial refactoring that would probably require a full time effort (I do this in my free time, mostly for fun). You can likely use the old image if you can find non-gdcm images, but it's probably not worth it. I'm generally unhappy and disappointed with this work, and wish I could allocate the time to do it over - it was literally a small weekend project I did and then nobody needed it, so I didn't work on it further. Do you think it's worth trying to plug in some newer / better OCR implementation and update the image so you have something to test against? |
I'm generally disappointed with python dependencies! No worries tho. I've
got a presentation Monday so I have to stick to my OCR implementation at
the moment. I'll let you know how goes and I'll be very happy to share it
nicely.
Daniel Snider ツ
…On Sat, Jan 5, 2019 at 2:08 PM Vanessa Sochat ***@***.***> wrote:
hey @danielsnider <https://github.com/danielsnider> this isn't going to
easily work unfortunately, and even rebuilding the model would require
substantial refactoring that would probably require a full time effort (I
do this in my free time, mostly for fun). You can likely use the old image
if you can find non-gdcm images, but it's probably not worth it.
I'm generally unhappy and disappointed with this work, and wish I could
allocate the time to do it over - it was literally a small weekend project
I did and then nobody needed it, so I didn't work on it further. Do you
think it's worth trying to plug in some newer / better OCR implementation
and update the image so you have something to test against?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABqDWN8c_NW5taftkGwfd5Obwy0-QoaPks5vAPgSgaJpZM4ZtQp7>
.
|
Thanks. How do we do the same thing for Windows10? |
The entire container libraries / base needs to be debugged, unfortunately.
See notes in #8
The text was updated successfully, but these errors were encountered: