StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POiGraph creating subgraph
primarykey
Id
12368680
data
AcceptedAnswerId
12376262
AnswerCount
1
ClosedDate
2012-09-12T12:09:08.687
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-11T11:27:17.067
FavoriteCount
0
LastActivityDate
2012-09-13T10:46:31.473
LastEditDate
LastEditorUserId
0
OwnerUserId
1216815
ParentId
0
PostTypeId
1
Score
4
ViewCount
3652
LastEditorDisplayName
text
Body
I have the following problem: I have the following graph: <code>g6</code> which does not include <code>isolate vertices</code>. The vertices are mainly grouped into two <code>ethnic groups</code>, given as attribute, namely: <code>mestizo and saraguro</code>. So I run the <code>subgraph</code>option for saraguros as follows: <blockquote> g2saraguro <- subgraph(g6, which(V(g6)$ethnic=="saraguro")) summary(g2saraguro) </blockquote> which did work: <blockquote> Vertices: 166 Edges: 330 Directed: TRUE No graph attributes. Vertex attributes: ii, village, parroquia, canton, provinz, kindR, ethnic, situation, researcha. Edge attributes: question, activity. </blockquote> However, if I try the same with <code>mestizo</code>, there is a proble, since it just identify: <blockquote> s2mestizo <- subgraph(g6,V(g6)$ethnic=="mestizo") summary(s2mestizo) Vertices: 2 Edges: 3 Directed: TRUE No graph attributes. Vertex attributes: ii, village, parroquia, canton, provinz, kindR, ethnic, situation, researcha. Edge attributes: question, activity. </blockquote> but in the reality that is no the case, if I see: <code>V(g6)$ethnic</code>, <code>mestizo</code> are the majority <code>!!</code> I really don´t know where the problem is, with <code>igraph 0.6</code> the procedure to form a <code>subgraph</code> should be in that or a similar way, without <code>1-based indexing</code>. thanks a lot for any help regards Vladimir 
Tags
<r><igraph>
Title
iGraph creating subgraph
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVlad
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POiGraph creating subgraph
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POiGraph creating subgraph
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.