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
There are a number of functions which "construct" dataframes, e.g., concat() and append(). How these work should be harmonized to a common data model.
At the moment, concat() requires that all input be pyam.IamDataFrames. append() on the other hand, can take any castable object such as pd.DataFrame or even file names which are read in at execution time.
The pros and cons deal with user experience vs. explicit interfaces using native datatypes. It is not clear which outweighs the other, so further comments from devs and users is appreciated.
So let us assume you have data in two files a.csv and b.csv that you want to combine. The options would look as follows:
The trickiness here is that our constructor currently supports two primary castable types: pd.DataFrames and files. If we choose "Explicit Interfaces", that would suggest that we no longer support reading files directly in pyam.IamDataFrame.__init__ .
I'd be in favour of the user experience too and refactoring the back end so they all get sent to the same format_data (or similar) pipeline which handles all the different possibilities
There are a number of functions which "construct" dataframes, e.g.,
concat()
andappend()
. How these work should be harmonized to a common data model.At the moment,
concat()
requires that all input bepyam.IamDataFrame
s.append()
on the other hand, can take any castable object such aspd.DataFrame
or even file names which are read in at execution time.The pros and cons deal with user experience vs. explicit interfaces using native datatypes. It is not clear which outweighs the other, so further comments from devs and users is appreciated.
So let us assume you have data in two files
a.csv
andb.csv
that you want to combine. The options would look as follows:User Experience
Explicit Interfaces
The trickiness here is that our constructor currently supports two primary castable types:
pd.DataFrame
s and files. If we choose "Explicit Interfaces", that would suggest that we no longer support reading files directly inpyam.IamDataFrame.__init__
.Thoughts? @znicholls @danielhuppmann others?
The text was updated successfully, but these errors were encountered: