StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17602713
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-11T20:19:44.110
FavoriteCount
0
LastActivityDate
2013-07-11T23:00:05.463
LastEditDate
2013-07-11T23:00:05.463
LastEditorUserId
980833
OwnerUserId
419842
ParentId
17580935
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<h2>A working example on gitHub</h2> <p><a href="https://github.com/nathanvan/minimalbugexample/tree/e6d62a6da7127fc165332935db04aa88b4575ae6" rel="nofollow">I put a working example on gitHub so that it is easy to browse the different files</a>. </p> <p>FYI, it's not quite a minimal example since it was built with <code>devtools</code>. The "extras" are (1) that <code>roxygen2</code> comments are what builds the NAMESPACE file, and (2) it incorporates unit testing with <code>testthat</code>. All of that can be ignored for the purposes of this example.</p> <h2>The key fix</h2> <p>The short answer that I did, in fact, need to change my NAMESPACE file to: </p> <pre><code>export(make.a.Matrix) export(transpose.a.Matrix) importFrom(Matrix,Matrix) importFrom(Matrix,t) </code></pre> <p>So that R could find the right version of transpose. See this <a href="http://obeautifulcode.com/R/How-R-Searches-And-Finds-Stuff/" rel="nofollow">post</a> for a great description of how R searches for functions. </p> <p>Although not strictly necessary, I modified my DESCRIPTION file to be a tad bit cleaner:</p> <pre><code>Package: minimalbugexample Title: Description: Version: 0.1.3 Author: Nathan VanHoudnos <nathanvan@letterafterFmail.com> Maintainer: Nathan VanHoudnos <nathanvan@letterafterFmail.com> Depends: R (>= 3.0.1), Matrix (>= 1.0) Suggests: testthat (>= 0.7.1.99) License: GPL LazyData: true Collate: 'minimalbugexample-package.r' 'use-Matrix-package.R' </code></pre> <p>Note that I am using <code>Depends:</code> for <code>Matrix</code> instead of <code>Imports:</code> so that the user will be able to use the <code>Matrix</code> objects that the functions return. If this example only used the <code>Matrix</code> stuff internally without presenting it to the user, I'd have used <code>Imports:</code>. </p> <h2>Proof that it works</h2> <pre><code>> require(minimalbugexample) > make.a.Matrix(1:12, 3, 4) 3 x 4 Matrix of class "dgeMatrix" [,1] [,2] [,3] [,4] [1,] 1 4 7 10 [2,] 2 5 8 11 [3,] 3 6 9 12 > transpose.a.Matrix(1:12, 3, 4) 4 x 3 Matrix of class "dgeMatrix" [,1] [,2] [,3] [1,] 1 2 3 [2,] 4 5 6 [3,] 7 8 9 [4,] 10 11 12 > t( make.a.Matrix(1:12, 3, 4)) 4 x 3 Matrix of class "dgeMatrix" [,1] [,2] [,3] [1,] 1 2 3 [2,] 4 5 6 [3,] 7 8 9 [4,] 10 11 12 </code></pre> <p>Note that the last command would have failed if I had specified <code>Matrix</code> in <code>Imports:</code> and not <code>Depends:</code>.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhen writing an R package that uses the Matrix package, why do I have to specify Matrix::t() instead of just t()?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJosh O'Brien
UserOwnerUserId
1. USNathan VanHoudnos
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhen writing an R package that uses the Matrix package, why do I have to specify Matrix::t() instead of just t()?
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.