You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File "test.py", line 19, in <module>
df = orca.merge_tables(target='c', tables=['c', 'b', 'a']) # error on this line
File "/Users/maurer/Dropbox/Git-imac/udst/orca/orca/orca.py", line 1799, in merge_tables
cast_table = frames[cast]
KeyError: 'a'
Twin-Clouds-iMac:Desktop maurer$ python test.py
Traceback (most recent call last):
File "test.py", line 19, in <module>
df = orca.merge_tables(target='c', tables=['c', 'b', 'a']) # throws error
File "/Users/maurer/Dropbox/Git-imac/udst/orca/orca/orca.py", line 1799, in merge_tables
cast_table = frames[cast]
KeyError: 'a'
This is a bug, right? I can see how it's a potentially ambiguous merge, but if we just resolve it in a consistent way it seems like a supportable use case. Overlapping broadcasts are helpful if you want to do different merge combinations at different times with maximum efficiency.
I don't see an obvious source for the error, but will dig into it more when I have a chance.
I'm running Orca 1.5.1 and Pandas 0.22.0
The text was updated successfully, but these errors were encountered:
I'm having trouble merging sets of tables with overlapping broadcast relationships.
For example, these combinations run:
But this combination raises an error:
This came up in real-world use (https://github.com/ual/urbansim_parcel_bayarea/issues/11), but here's a stand-alone demonstration that you can paste into a python script:
Here is the error:
This is a bug, right? I can see how it's a potentially ambiguous merge, but if we just resolve it in a consistent way it seems like a supportable use case. Overlapping broadcasts are helpful if you want to do different merge combinations at different times with maximum efficiency.
I don't see an obvious source for the error, but will dig into it more when I have a chance.
I'm running Orca 1.5.1 and Pandas 0.22.0
The text was updated successfully, but these errors were encountered: