Skip to content
 
 

Latest commit

 

History

8 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

Mini Project1 - Text Analysis

Please read the entire assignment.

Groups

  • Group 0: kyandall, jtyuill, cgoering, jvijayak, asaucer, cdamron3
  • Group 1: hneel, mjohn326, sydlwils, dkim68, pshu, ncash3
  • Group 2: eabbott9, aalkafou, mmariaru, cfinley6, jbell96, cliddel2
  • Group 3: wch356, pstorch1, smurph61, bjy819, lwang111, hsaleh5
  • Group 4: gwright30, wknepp, kha5, sbombry1, bxy539, mjakowsk
  • Group 5: hnaicker, hawad, aberard, rkabarwa, dmengeli
  • Group 6: tcartier, cwolver1, jpark127, smaciasa, pvickery
  • Group 7: kbc177, asangiul, econstan, lsantucc, melawady, spastor
  • Group 8: astubbin, pmarino, aamphone, tgarrio1, arother1
  • Group 9: jbronyah, emolder, oyoungbl, jmurph91, tlopez7
  • Group 10: hcrettol, ksaravan, amart170, ltipto11, ccough13
  • Group 11: bdowlin2, dbritto3, ddemarco, jzr266, bslessma
  • Group 12: gelkhoda, spate198, cboddick, gkhot, ttb615
  • Group 13: smazunda, afink12, kbissonn, hvo5, ggood3
  • Group 14: bnoyes, dlong37, dpate172, pvathana, jharves1

Workflow

  1. To start, fork repository github.com/utk-cs445-fall26/MiniProject1
    1. Go to github.com/utk-cs445-fall26/MiniProject1
    2. Click on "Fork Repository" button
    3. Select your GitHubID as the organization to fork to
    4. ** Important: go to Settings and enable issue tracking**
  2. Create new notebook YourUTKID.ipynb in your fork.
  3. Open your notebook and add a text cell describing goals and ways to achieve your goal (data sources/comparisons)
  4. save your notebook and push to your repository
  5. At https://github.com/[YourGHUsername]/MiniProject1 Create a pull request on the original repository utk-cs445-fall26/MiniProject1 to turn in that initial description.
  6. From your assigned group, Comment on the description produced by your peer listed to the right of your netID by creating an issue on their fork (see the groups on fdac/news)
    • if you are the last listed netID of your group, the peer you will comment on will be the first member of your group
  7. Respond to issue raised by the peer appearing to the left of your netID in your fork
    • if your are the first listed netID of your group, the peer you respond to will be the last member of your group
  8. Work on the analysis and presentation

Social Workflow with deadlines

  1. Each assignment must be completed INDIVIDUALLY - Discussion should be based on results you collect.
  2. Do the first six steps listed above before the class on Sep 3rd: if you have any issues, we need to clarify them before Sep 3rd.
  3. Come up with an idea of what analysis you are going to use and what data sources you will use. Discuss it with your assigned peer on Sep 3rd. You present the idea to the peer you commented on in the above section. You produce a comment for the peer you responded to in the above section. To access your peer's forked repository, manually enter the url: https://github.com/YourPeersGHUsername/MiniProject1

When you raise an issue, you should assign it to the GHUSER who should comment on it.

  1. Start doing the analysis and discuss your progress with your peer so that you are done on Sep 10th. In case you encounter any problems retrieving, storing, or analyzing data please discuss them with your peer and, if needed, escalate.
  2. Prepare a few slides (or a jupyter notebook) explaining the approach and findings and present to a small group as specified below.

At the end of the presentations within the group a vote will be held (by that group) for one presentation to be selected for the presentation to the entire class. The first person listed in each group will record that in this issue

What operational data traces are expected

  1. I expect you to make at least one commit (in your cloned repo) by Sep 3rd and at least three by Sep 10th.
  2. Each interaction with your peer should result in an issue that describes your peers comments. You should raise at least one issue against your peers repository peer/MiniProject1 (see above), and you should make at least one commment on the issue raised against your fork (you/MiniProject1).

Presentations should include

  • What is the question?
  • What was the approach?
  • What problems did I encounter?
  • What results did I get?
  • What new ideas did this generate?

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages