StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POxts merge odd behaviour
primarykey
Id
7678090
data
AcceptedAnswerId
7678624
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-10-06T17:20:24.517
FavoriteCount
1
LastActivityDate
2011-10-18T23:33:31.467
LastEditDate
2011-10-06T18:27:18.497
LastEditorUserId
982644
OwnerUserId
982644
ParentId
0
PostTypeId
1
Score
3
ViewCount
1402
LastEditorDisplayName
text
Body
I have 3 xts objects all of whose indicies are 'Date' objects: <pre><code> > a a 1995-01-03 1.76 1995-01-04 1.69 > b b 1995-01-03 1.67 1995-01-04 1.63 > c c 1995-01-03 1.795 1995-01-04 1.690 </code></pre> To verify the indices are the same: <pre><code> > index(a) == index(b) [1] TRUE TRUE > index(a) == index(c) [1] TRUE TRUE </code></pre> Now I'm seeing this odd behaviour: <pre><code> > merge.xts(a,b) a b 1995-01-03 NA 1.67 1995-01-03 1.76 NA 1995-01-04 NA 1.63 1995-01-04 1.69 NA </code></pre> While the following merge works fine: <pre><code> > merge.xts(a,c) a c 1995-01-03 1.76 1.795 1995-01-04 1.69 1.690 </code></pre> I can't figure out what could possibly be going on here. Any idea? Update: <pre><code> > dput(a) structure(c(1.76, 1.69), .indexCLASS = "Date", .indexTZ = "", .CLASS = "xts", class = c("xts", "zoo"), index = structure(c(789168240, 789254580), tzone = "", tclass = "Date"), .Dim = c(2L, 1L), .Dimnames = list(NULL, "a")) > dput(b) structure(c(1.67, 1.63), .indexCLASS = "Date", .indexTZ = "", .CLASS = "xts", class = c("xts", "zoo"), index = c(789109200, 789195600), .Dim = c(2L, 1L), .Dimnames = list( NULL, "b")) > dput(c) structure(c(1.795, 1.69), .indexCLASS = "Date", .indexTZ = "", .CLASS = "xts", class = c("xts", "zoo"), index = c(789109200, 789195600), .Dim = c(2L, 1L), .Dimnames = list( NULL, "c")) </code></pre> Indeed, the problem is that the indices are not identical (as verified by <code>.index(a) == .index(b)</code> ). Converting to numeric then recreating an xts and recomputing the dates with <code>asDate</code> fixed the problem. This objects were created from the <code>to.daily</code> method from xts.
Tags
<r><xts>
Title
xts merge odd behaviour
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USfunctor
UserOwnerUserId
1. USfunctor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POxts merge odd behaviour
 UserUserId
 USrichallensf
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POxts merge odd behaviour
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POxts merge odd behaviour
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.