-
Notifications
You must be signed in to change notification settings - Fork 1
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
ual.py household reconciliations #9
Comments
I'm not sure this is an issue. I haven't verified it, but my reading of the code is that 'households' has an index named 'household_id' (per orca_test assertion), and https://github.com/ual/bayarea_urbansim/blob/ual-development/baus/ual.py#L360-L368 From your email, this came up because an orca_test assertion involving that index is failing somewhere, right? My first thought is that it could be a bug in orca_test, actually. Pandas treats indexes as completely separate from the rest of the DataFrame, which makes those bits of orca_test more bug prone because there are multiple cases to cover. In December we merged an orca_test PR that added support for multi-indexes.. Maybe this broke support somewhere for DataFrames with just a single index? |
I had this thought as well. I commented out the orca_test check but the code just fails later when it tries to set |
OK I just pushed these changes to I had to comment out the orca_test functionality bc for some reason orca isn't storing the index name in the households table. |
I think there is a bug around line 367 of ual.py. Line 358 seems to drop the
household_id
from the households table with this command:and then on line 367 it attempts to merge with the units table and use
household_id
as the index only that column is no longer associated with the households table. can you confirm, Sam? Looks like this is the result of changes that were made in June.The text was updated successfully, but these errors were encountered: