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

_gibbs fails on dataframes with floats #41

Closed
lkursell opened this issue Apr 26, 2016 · 4 comments
Closed

_gibbs fails on dataframes with floats #41

lkursell opened this issue Apr 26, 2016 · 4 comments
Labels

Comments

@lkursell
Copy link
Collaborator

_gibbs fails with:
IndexError: index 6283 is out of bounds for axis 0 with size 6283
When the are floats in the sink_df. The error occurs when trying to create the order to walk through the sequences.

Probably want to add a check so that a less cryptic error message is given to the user.

@lkursell lkursell added the bug label Apr 26, 2016
@wdwvt1
Copy link
Contributor

wdwvt1 commented Apr 26, 2016

Can you post the dataset + command that causes this. I thought I had every error where an index error occurs isolated, but definitely need to see what slipped through.

@wdwvt1
Copy link
Contributor

wdwvt1 commented Apr 26, 2016

this can be resolved by changing line 529 in sourcetracker2/sourcetracker.py to be sink_sum = np.int(sink.sum()). alternatively we can floor or ceiling this value, but we just need to ensure its not non-integer.

@lkursell
Copy link
Collaborator Author

Should we make the user address their int problem? or just call floor and add a note saying that is what we do?

On Apr 26, 2016, at 3:52 PM, Will Van Treuren [email protected] wrote:

this can be resolved by changing line 529 in sourcetracker2/sourcetracker.py to be sink_sum = np.int(sink.sum()). alternatively we can floor or ceiling this value, but we just need to ensure its not non-integer.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #41 (comment)

@wdwvt1
Copy link
Contributor

wdwvt1 commented Jul 15, 2016

This is now resolved in PR #51 and noted in the readme.md.

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

No branches or pull requests

2 participants