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
We currently have an option -M, --maxreferences that restricts the maximum number of edges leaving a node, to avoid the celebrity problem. However, we currently accomplish this by reading through their tweets reverse-chronologically until we've found enough mentions and retweets. This means -M 30 will get the 30 most recent retweets or mentions for each user. This is not always desirable; what if we want the strongest links between users instead of the most recent?
We should provide an option like -C, --common that changes behavior to read all mentions and retweets per user, sort by occurrence, and use the top X most occurring connections rather than most recent activity.
The text was updated successfully, but these errors were encountered:
milo-trujillo
changed the title
Add an option for getting most common edges instead of most frequent
Add an option for getting most common edges instead of most recent
Nov 8, 2019
Typo in title. This should be a pretty simple change, need to add a dictionary (or Counter from collections) for all the retweet usernames, then just get the top X from the dict. Requires adding an extra field to the options object, maybe passing an extra argument through the acquire code to the retweet collector.
We currently have an option
-M, --maxreferences
that restricts the maximum number of edges leaving a node, to avoid the celebrity problem. However, we currently accomplish this by reading through their tweets reverse-chronologically until we've found enough mentions and retweets. This means-M 30
will get the 30 most recent retweets or mentions for each user. This is not always desirable; what if we want the strongest links between users instead of the most recent?We should provide an option like
-C, --common
that changes behavior to read all mentions and retweets per user, sort by occurrence, and use the top X most occurring connections rather than most recent activity.The text was updated successfully, but these errors were encountered: