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

Model Manager issue NameError #652

Closed
M-crazy opened this issue Aug 20, 2019 · 9 comments
Closed

Model Manager issue NameError #652

M-crazy opened this issue Aug 20, 2019 · 9 comments
Assignees
Labels
Easy to fix The issue is easy to fix and probably it will be release in a next minor release enhancement New feature or request
Milestone

Comments

@M-crazy
Copy link

M-crazy commented Aug 20, 2019

Is this a bug? Multi layer method call error:
Test failed: NameError at line 474: name 'test2' is not defined

Interpretation script:

def test2():
    test3()

def test1():
    test2()
@nmanovic
Copy link
Contributor

@M-crazy , please published here 4 files to debug on our side. Otherwise we cannot help you.

@nmanovic nmanovic added the question Further information is requested label Aug 20, 2019
@M-crazy
Copy link
Author

M-crazy commented Aug 20, 2019

Thanks for your quick reply.This error is not just for my model, you can use any model you want

@nmanovic nmanovic added Easy to fix The issue is easy to fix and probably it will be release in a next minor release enhancement New feature or request good first issue and removed question Further information is requested labels Aug 20, 2019
@nmanovic nmanovic added this to the 1.0.0 - Alpha milestone Aug 20, 2019
@M-crazy
Copy link
Author

M-crazy commented Aug 20, 2019

@nmanovic Thank you for helping to troubleshoot the problem,It's helpful to me

@M-crazy
Copy link
Author

M-crazy commented Aug 22, 2019

hi,@nmanovic
This is a new question

In the Interpretation script,whether I can pre-process my input before detect?

@nmanovic
Copy link
Contributor

@M-crazy, it is not implemented for now. Could you please describe your scenario?

@M-crazy
Copy link
Author

M-crazy commented Aug 27, 2019

@nmanovic , I use data preprocessing as a new layer,now it works

@bsekachev bsekachev changed the title Model Maneger issue NameError Model Manager issue NameError Sep 20, 2019
@benhoff
Copy link
Contributor

benhoff commented Oct 29, 2019

It would be worth adding this limitation directly to the Auto Annotation README.

I believe this is an issue with using exec and the scoping of that call. On way to get around this limitation is to create a class, and put all the methods in the class. This allows multi-level method calling as the scope is controlled by the class itself.

@nmanovic
Copy link
Contributor

@M-crazy , I will close the issue for now. I believe it was fixed in the past somehow or workaround methods exist. Don't hesitate to reopen the issue.

Semi-automatic and automatic annotation automation moved this from To do to Done Mar 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Easy to fix The issue is easy to fix and probably it will be release in a next minor release enhancement New feature or request
Development

No branches or pull requests

4 participants