-
Notifications
You must be signed in to change notification settings - Fork 303
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
resolve discrepancy of estimating Moran's I corrected for rates between GeoDa and pysal #1011
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. One question on "geoda_rate": we only discuss T/F for this when adjusted=True. What is the behavior when adjusted=False?
Adding a note here that when this gets merged, we need to port to https://github.com/pysal/esda |
@sjsrey If adjusted=True (or |
@weikang9009 if adjusted=False, is geoda_rate ignored? |
@sjsrey yes. If |
@weikang9009 maybe we should add to the docs that:
|
@sjsrey Thank you for the suggestion. Have updated the docs (for |
This PR is to reopen PR #989 which was unmerged but closed because of some complication I made. It is to resolve the discrepancy in estimating EBI (Moran's I corrected for rates) between GeoDa and pysal as pointed out in issue #987. Now users could choose to conform with Geoda by setting parameter
geoda_rate=True
:or to use the original implementation of correcting rates in pysal which conform with the Assunção's paper by setting parameter
geoda_rate=False
: