-
Notifications
You must be signed in to change notification settings - Fork 15
Partial solution to #18 #26
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
Conversation
nice. I dont know that I ever would've caught that. 2 quick things:
|
Great, can clean up once I have time to dig into the failing tests. Yes, totally fine with switching to <=, though I think that's logically another issue. @jkoschinsky is great if she's willing!! |
Yes, great, thanks!!
…________________________________
From: Jamie Saxon ***@***.***>
Sent: Friday, February 4, 2022 10:00:10 PM
To: pysal/access ***@***.***>
Cc: Julia Koschinsky ***@***.***>; Mention ***@***.***>
Subject: Re: [pysal/access] Partial solution to #18 (PR #26)
Great, can clean up once I have time to dig into the failing tests.
Yes, totally fine with switching to <=, though I think that's logically another issue.
@jkoschinsky<https://github.com/jkoschinsky> is great if she's willing!!
—
Reply to this email directly, view it on GitHub<#26 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADILY74RIGVQMN3CCSOYDCDUZQ45VANCNFSM5NQTIJWQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Codecov Report
@@ Coverage Diff @@
## master #26 +/- ##
==========================================
+ Coverage 98.21% 98.33% +0.12%
==========================================
Files 17 18 +1
Lines 1118 1204 +86
==========================================
+ Hits 1098 1184 +86
Misses 20 20
Continue to review full report at Codecov.
|
Hi @knaaptime or @jGaboardi, please have a look if you like, and merge / close. I've fixed the failing tests (it was a unit test failure¡), and also added a new class of tests, that assert:
Sorry it took me so long to get to this. |
Also tagging @jkoschinsky for info. |
@knaaptime Can you give this PR a review? |
Hey @jGaboardi, waiting on @knaaptime, I just approved. Anything else needed, for this to rebuild docs / version on the new site? Or is that now all automagic? Thanks again for all your support with this project. @jkoschinsky for info. |
@JamesSaxon sorry for the super late attention here. So we need a fresh release of |
Hi @jGaboardi, yeah -- the PR is in, so public version should be updated. |
@JamesSaxon Are you thinking patch release ( |
Fair question -- patch release, in this case. |
This solves the issue noted by @knaaptime in #18, in his notebook, that the two-stage numbers were not affected by changes in the OD matrix. (Thanks!)
This fixes a bug where it was not the weighted values that were getting summed in the two-stage calculation! This was basically a one-line bug, that the suffix "r" had been added, but then not used.
I wrote a completely "base python" gravity-based 2SFCA below, that we could add as an additional unit test.' With that fix, the package and the function below (for the four simple cases!!) agree, point-identical.
https://gist.github.com/4a3c3d1c571523db43785e43b256ba78
See if this looks reasonable?