NTTC (Name That Twitter Community!): Process and analyze community-detected data
by Chris Lindgren chris.a.lindgren@gmail.com Distributed under the BSD 3-clause license. See LICENSE.txt or http://opensource.org/licenses/BSD-3-Clause for details.
Documentation: https://nttc.readthedocs.io/en/latest/
Overview
A set of functions that process and create topic models from a sample of community-detected Twitter networks' tweets. It also analyzes if there are potential persistent community hubs (either/and by top mentioned or top RTers).
It assumes you seek an answer to the following questions:
- What communities persist or are ephemeral across periods in the corpora, and when?
- What can these communities be named, based on their top RTs and users, top mentioned users, as well as generated topic models?
- Of these communities, what are their topics over time?
Accordingly, it assumes you have a desire to investigate communities across periods and the tweets from each detected community across already defined periodic episodes with the goal of naming each community AND examining their respective topics over time in the corpus.
It functions only with Python 3.x and is not backwards-compatible (although one could probably branch off a 2.x port with minimal effort).
Warning: nttc performs no custom error-handling, so make sure your inputs are formatted properly! If you have questions, please let me know via email.
System requirements
- arrow
- tsm
- nltk
- networkx
- matplot
- pandas
- numpy
- emoji
- pprint
- gensim
- spacy
- tqdm
- sklearn
- joblib
- MulticoreTSNE
- hdbscan
- seaborn
- stop_words
Installation
pip install nttc
Known Issues or Limitations
- Please contact me if you discover any issuess.
Example notebooks
- See the
assets/examplesfolder for example uses.
Distribution update terminal commands
# Create new distribution of code for archiving sudo python setup.py sdist bdist_wheel # Distribute to Python Package Index python -m twine upload --repository-url https://upload.pypi.org/legacy/ dist/*
Metadata
Release files for nttc 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| nttc-0.6.1.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nttc-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.2 kB
Release files / nttc-0.6.1.tar.gz
| Download URL | nttc-0.6.1.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51261625d8c16d56aa159a70727c41a425a184349db817fe703a4a3e481655c9
|
|
BLAKE2b-256 checksum How to use checksums |
b654ac88e328296cc75e3c5c91c84fd4d358260104575d10a2e04d5a65aab2cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.6.5
|
Release files / nttc-0.6.1-py3-none-any.whl
| Download URL | nttc-0.6.1-py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
712c8e5733bf43748f3a4806757081f2f56b9b9e1501b3804a175c8c7ec32acb
|
|
BLAKE2b-256 checksum How to use checksums |
e80825211da3e3742a54ae96104fcad946c9738734627c1c72ae63fd69f82565
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.6.5
|
Security for nttc 0.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.