https://github.com/cmudig/tempo

https://github.com/cmudig/tempo

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.2%) to scientific vocabulary
Last synced: 11 months ago · JSON representation

Repository

Basic Info
  • Host: GitHub
  • Owner: cmudig
  • Language: Svelte
  • Default Branch: main
  • Size: 17.7 MB
Statistics
  • Stars: 1
  • Watchers: 2
  • Forks: 0
  • Open Issues: 4
  • Releases: 0
Created over 2 years ago · Last pushed about 1 year ago
Metadata Files
Readme

README.md

Tempo: Collaborative Predictive Model Specification

Tempo is an interactive tool to help data scientists and domain experts define specifications for predictive models. It includes a simple, yet precise query language for aggregating temporal event data, as well as a built-in subgroup discovery interface powered by Divisi.

For more information and examples of how Tempo could be used in cross-functional teams, please see our paper at CHI'25 (link coming soon).

Setup Instructions

To set up, cd into the main repository directory, and run pip install -r requirements.txt. Then cd into the client directory and run npm install && npm run build.

Create a directory called datasets and place any datasets you'd like to load within that directory (see below for more details).

To run the tool, cd into the main directory and run:

bash python -m tempo_server.server <parent of datasets directory>

Then visit http://127.0.0.1:4999 in your browser to see the tool.

(Development) To automatically rebuild the client while changing the source code, cd into the client directory and run npm run autobuild. After making changes to the source code, you will need to reload the browser page to see the updated version.

Importing Datasets

The structure expected for the datasets directory is as follows:

<parent folder> - datasets - <dataset name> - spec.json - <data files>

Below is an example of the dataset specification (spec.json):

json { "data": { "sources": [ // place data files in the dataset folder (.csv or .arrow) and provide their relative paths here { "type": "attributes", "path": "data/attributes.csv" }, { "type": "events", "path": "data/events.csv" }, { "type": "intervals", "path": "data/intervals.csv" } ] }, "slices": { "sampler": { // subgroup discovery settings used by Divisi "min_items_fraction": 0.02, "n_samples": 100, "max_features": 3, "scoring_fraction": 1.0, "num_candidates": 20, "similarity_threshold": 0.5, "n_slices": 20 } }, "models": { "default": { // optionally provide a default model spec "variables": {} } } }

The datasets directory in this repo contains an example sourced from an e-commerce behavior dataset on Kaggle.

Citation

TBD

Owner

  • Name: CMU Data Interaction Group
  • Login: cmudig
  • Kind: organization
  • Location: Pittsburgh, PA

People, Visualization, Analysis, Machine Learning

GitHub Events

Total
  • Issues event: 4
  • Watch event: 1
  • Push event: 7
  • Public event: 1
  • Create event: 1
Last Year
  • Issues event: 4
  • Watch event: 1
  • Push event: 7
  • Public event: 1
  • Create event: 1

Committers

Last synced: about 1 year ago

All Time
  • Total Commits: 152
  • Total Committers: 4
  • Avg Commits per committer: 38.0
  • Development Distribution Score (DDS): 0.039
Past Year
  • Commits: 71
  • Committers: 2
  • Avg Commits per committer: 35.5
  • Development Distribution Score (DDS): 0.056
Top Committers
Name Email Commits
Venkatesh Sivaraman v****8@g****m 146
phiofuni j****0@g****m 4
Elias Benbourenane e****e@g****m 1
Anika Vaishampayan 9****1 1

Issues and Pull Requests

Last synced: about 1 year ago

All Time
  • Total issues: 4
  • Total pull requests: 2
  • Average time to close issues: N/A
  • Average time to close pull requests: 28 days
  • Total issue authors: 1
  • Total pull request authors: 2
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.0
  • Merged pull requests: 1
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 4
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 1
  • Pull request authors: 0
  • Average comments per issue: 0.0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • rkboyce (4)
Pull Request Authors
  • eliasbenb (1)
  • anikavaish01 (1)
Top Labels
Issue Labels
question (1)
Pull Request Labels