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

'Could not find a good frame' error #14

Open
christinahedges opened this issue Mar 18, 2017 · 8 comments
Open

'Could not find a good frame' error #14

christinahedges opened this issue Mar 18, 2017 · 8 comments

Comments

@christinahedges
Copy link

When I run the examples from your readme I get the error

'ERROR: Could not find a good frame.'

I've rolled back the versions and it'll work only on version 1.0.0, which runs but throws up several warnings. Anything more recent just quits with the above error. I haven't tried with any other TPFs.

I'm using a mac, python 2.7.11 and just updated all my local packages to see if that would help. (Numpy 1.12.0, astropy 1.3.1)

@mirca
Copy link
Member

mirca commented Mar 18, 2017

hi @rawien, thanks for reporting. I will take a look at that soon.

@mirca
Copy link
Member

mirca commented Mar 18, 2017

Hi @rawien,
I do see the same error in the 2.3.0 version, but it works with the dev version. Can you use the dev version for now?
Thanks

@barentsen
Copy link
Member

Oh dear, I am finding the same. I intend to push a new release to pip soon to resolve this.

@christinahedges
Copy link
Author

christinahedges commented Mar 18, 2017

Thanks for getting back to me, same error on my linux machine now too. I'll try the dev version.

Update:
Dev version works, though if you run the example in the readme the contrast is very different and the date doesn't display, the frame number does. Still great to have it working! Thanks

@brandoncastillo
Copy link

I am having the same issue and was wondering if this was resolved or if I need to cycle back to the dev version. I'm using python3.5.2.
Thank you

@barentsen
Copy link
Member

@brandoncastillo Oops! I am unable to reproduce this problem, likely because I haven't pushed a release to pypi for a long while. I believe this issue was fixed on the master branch a few months ago.

I just published version 2.3.1 on pypi. Would you mind running

pip install k2flix --upgrade

and check if you still encounter the problem? Thanks++!

@brandoncastillo
Copy link

It looks like upgrading it did the trick thank you very much

@barentsen
Copy link
Member

@brandoncastillo Many thanks for reporting the issue and trying out the new version. I appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants