-
Notifications
You must be signed in to change notification settings - Fork 23
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
Various comments #128
Comments
Thanks @bkamins for the very useful comments. I have responded below.
Sorry, did not understand this. What is the purpose of cross linking?
There is a constructor for creating an empty TSFrame object but currently it does not work with a DataFrame without any columns. Ideally,
Right now,
Yes, to both.
It means that the original DataFrame does not need to have a column named If the column number or name isn't specified in the constructor then
Yes.
Yes, of course. Got missed.
Thanks, did not know about this.
Yes.
Not that both of these are not intended but were lower priority earlier. I believe these would be good enhancements.
Alright, will fix this.
This is done to keep the API simple with a single join method supporting all kinds of joins. R zoo/xts follow this convention.
Okay.
This is possible with Tables.jl implementation:
There hasn't been much thought about taking this path actually. Not sure if TSFrames should handle panel data use cases or another package which uses composition with TSFrame? |
So that in the generated documentation you can click on |
x-link to
Index
is missingIndex
?In general mention in the description the second argument in the constructor.
Mention that any Tables.jl table is also accepted.
What if index column is not called
:Index
? (the same with other places - the docs above said that the index column does not have to be calledIndex
, but maybe I misunderstood)I would throw
ArgumentError
for easier error handling (also in other places)Why not just
Period
(this would allow for supporting user extensions of special date/time types)This is minor, but it is incorrect as it allows:
String
, while it would be better to allow forAbstractString
Bool
(neither rows nor columns) - maybe this is intendedBetween
,Not
etc. (maybe this is intended?)This is incorrect.
coredata
can have:coredata
column name. fields and properties should not be mixed. I would use a function to expose:coredata
field instead. Eg.getdataframe(tsf::TSFrame) = getfield(tsf, :coredata)
People did not like extending this function in packages. Better add methods for
innerjoin
etc.You might consider allowing passing kwargs like
renamecols
.DataFrames
prefix is not neededMaybe you want
TSFrame
to be iterable? I.e. have length and support something like:for row in tsf
# here have
DataFrameRow
with dataend
How do you want to support panel data (so essentially
TSFrame
grouped by some column)The text was updated successfully, but these errors were encountered: