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
When creating a dataset with dim_process (and also probably with dim_material and dim_time, although I didn't try), there is a problem if you try to later use the flow_selection param when creating a Bundle. Because the dataset is constructed by adding a prefix source. and target. (note the dot), pandas gets angry whenever floweaver.dataset.eval_selection gets called.
I was able to solve this by editing dataset.py and replacing all the dots with underscores on lines 28 and 70-77, then replacing flow_selection string with underscores as well. Can submit a PR if desired, but I might be missing some other places where the dot is important and not realize it (haven't looked too extensively at the rest of the code)
The text was updated successfully, but these errors were encountered:
Thanks for reporting this and sorry for the slow response. Replacing with underscores is a pragmatic solution but wouldn't be compatible with the way it's worked previously so I'd like to try to figure out what the problem is and make it work with dots if possible. I'll try to take a look soon, or help with diagnosing the underlying problem also welcome.
When creating a dataset with
dim_process
(and also probably withdim_material
anddim_time
, although I didn't try), there is a problem if you try to later use theflow_selection
param when creating aBundle
. Because the dataset is constructed by adding a prefixsource.
andtarget.
(note the dot), pandas gets angry wheneverfloweaver.dataset.eval_selection
gets called.For example, if I have created a
Dataset
like so:This fails with the following traceback:
Full traceback here: https://gist.github.com/mskoh52/7054199865c214ad1de8f0e4772582d4
I was able to solve this by editing
dataset.py
and replacing all the dots with underscores on lines 28 and 70-77, then replacingflow_selection
string with underscores as well. Can submit a PR if desired, but I might be missing some other places where the dot is important and not realize it (haven't looked too extensively at the rest of the code)The text was updated successfully, but these errors were encountered: