https://github.com/cbroeckl/viva.el.birdos

a repository to enable the VEB community to share code for analysis of baseball, specifically Cardinals, analysis

https://github.com/cbroeckl/viva.el.birdos

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
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (9.8%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

a repository to enable the VEB community to share code for analysis of baseball, specifically Cardinals, analysis

Basic Info
  • Host: GitHub
  • Owner: cbroeckl
  • License: gpl-3.0
  • Language: HTML
  • Default Branch: main
  • Size: 410 KB
Statistics
  • Stars: 1
  • Watchers: 0
  • Forks: 1
  • Open Issues: 0
  • Releases: 0
Created 12 months ago · Last pushed 11 months ago
Metadata Files
Readme License

README.md

viva.el.birdos

A repository to enable the VEB community to share code for baseball, specifically St Louis Cardinals, analysis. For folks wanting to contribute:

for working in R:

  1. Create a github account
  2. Download the github desktop software, install on your computer
  3. Download R, install
  4. Download Rstudio, install
  5. Open github desktop, 'clone a repository' and find cbroeckl/viva.el.birdos
    • in upper left, find 'current repository', and click 'add' then 'clone repository'
    • find cbroeckl/viva.el.birdos, clone.
    • this downloads all content to your local drive. ('my documents/github' on windows, by default)
    • in your local repository, i suggest creating a new directory for your files, called by your VEB username or your name.
    • add your R code files to the existing files set, ideally in your personal subdirectory you just created.
    • once you are comfortable sharing you files publicly, 'push' your code back to the repository
      • in github destop, find your edited new file, fill in description in lower left of window (required)
      • 'commit' edit (just below description you just entered)
      • 'push origin' to copy your local code to the viva.el.birdos repository.

for working in Python:

hopefully some one (aaron) with python experience can add something here.

overview

the idea here is that we can learn from each other. Note that if you edit code from viva.el.birdos locally, it stays local, UNLESS you push it back to the repository. any edits you 'push' will replace the versions on the viva.el.birdos repository. Github does use versioning, which means any chance can be rolled back, but do be mindful that editing code collectively means you may be editing other people's code, and overwriting other documents. if you aren't sure you want to do that, save the file as a new file name, which prevents issues. We will be learning as we go.

Owner

  • Name: Corey Broeckling
  • Login: cbroeckl
  • Kind: user
  • Location: Fort Collins, CO, USA
  • Company: Colorado State University

GitHub Events

Total
  • Watch event: 1
  • Push event: 7
  • Fork event: 1
  • Create event: 2
Last Year
  • Watch event: 1
  • Push event: 7
  • Fork event: 1
  • Create event: 2