Daily Log

[annarupert]

Group Log for October 25th

• Today we worked on our hypothesis in a workshop format and found ways to strengthen our hypothesis.
• We also created this documentation issue to highlight the tasks that complete throughout this project.

[annarupert]

Group Log for October 27th

• Today we worked more on the hypothesis workshop and got insight and questions from another group. This was super helpful for us because it allowed us to see our work from an outside perspective.
• We all have access to our data via One Drive and have been looking through it sporadically.

[kbuzard]

@ecn310/accidentsteam Please share the OneDrive folder with Dylan and me so that we can see what your data looks like and help when needed.

[kbuzard]

@ecn310/accidentsteam Here is my feedback on your documentation:

1. The structure of the master documentation on the wiki looks good!
   • I don't understand the distinction you're making between the group log and the stream of consciousness. To me, those are the same thing, and it's what you have here on this thread.
   • Please add a link to the OneDrive folder.
2. The do-file is missing
   • I know that your team was running a lot of commands during class yesterday. Everything you're learning from the experimenting--anything that you might want to use or build off of, all that should be kept in a do-file.
3. Somewhere you should be keeping track of the work you're doing to figure out how to test your hypothesis. This is an example of what I mean by "task documentation."
4. There haven't been any posts to this daily log about what you've done in class this week--on your data and on your documentation.

[annarupert]

@kbuzard

Tagging you in the group as requested, sorry!

1. We can call the daily log the "daily log/stream of consciousness" if that would be more straightforward?
2. The one drive link is now added.
3. Additionally, we have had trouble with the do-file because we had not substantial graphs or experiments with the data. I am not sure what would be on the do-file without that?
4. Should the stream of consciousness be updated every class or can it be updated at the end of the week? Either is fine just want to make sure we are on top of it.

Please let us know if there is anything else we can do to improve our grade on this assignment, I think we misunderstood aspects of it prior to the workshop!

Thanks

[kbuzard]

We can call the daily log the "daily log/stream of consciousness" if that would be more straightforward?

Daily log is fine as a name. To your question in 4, it should be updated whenever anyone does anything. So definitely every class period that you work on it together; then just one person can post about what the group accomplished if you're all working together. But you should also post if anyone is doing any work outside of class. It's best practice to do this right when you're wrapping up work; if you wait, you might forget to do it at all, or you might forget to include important details.

The OneDrive link works great. Thanks!

Additionally, we have had trouble with the do-file because we had not substantial graphs or experiments with the data. I am not sure what would be on the do-file without that?

At minimum, your do-file should have the commands to open the data. Then, include any commands that you've used to explore the data, with notes about what makes sense, what doesn't make sense, what you're going to try next. This is the easiest place to document all the exploratory work you're doing. It's not just for final, perfected code.

[annarupert]

Hi @kbuzard I went through the variables a little more and was able to find some not so ugly ways to represent the data, the do-file should be updated and I will make sure that we have a concrete update to this log to highlight that after class tomorrow.

Thank you for the feedback!

[annarupert]

Group Log November 8th Prior to and In Class Updates

Prior to Class

• Today we looked at our data and noticed a significant amount of outliers. We created an issue in our course project repo to discuss how to append our data so we can use these variables properly.

Outliers issue

Post Class Update from Will

In class we started to look at the state of our data. Anna started an issue on the topic, which I replied to with a lot of findings on the standard deviation and range on the variables. We also helped sync the onedrive on to the computers of everybody in the group.

[Yuhan-2435]

Group Log November 10th

• We continued worked on the outliers in our group data, focus on variable total_djtr_days this time.
  • issue: Outliers issue
  • do-file: datafix
• We created a new variable called injuries_percapita to better show the percentage of injuries in each establishments. We will continue work on this variable.
• We also worked on the relationship between the size of establishment and the total number of injuries. But it is hard to find out a better way to deal with problems (strange outliers, large range and std.dev, etc) we met today.

[annarupert]

Group Log November 15th

Prior to Class

• I found research to help support our data issues and documented it on a new issue entitled Data Fix Search.
• I created a new task to update our lit review with the paper from Prof Singleton, with a special focus on the way he processed the OSHA data.

  After Class

  • Updated the do file that create the new variable inj_rate. Inj_Rate
  • Continued to work on lit review, we are summarizing Prof. Singletons approach on fixing our data.

[annarupert]

Group Log November 17th

• We created two new issues, one about the Lit Review and one about the Data Brainstorming.
• We continued our work on inj_rate. Remove outliers, find the correlations between inj_rate and other variables that are related to the establishment size.
• Task: Make sure the lit review can be applied to the writing section.

[kbuzard]

@ecn310/accidentsteam I'm still catching up and just finished checking over your progress and al your documentation.

I have just a few suggestions on the documentation:

• It's a little confusing to have two issues open on the lit review. I suggest reviewing and seeing if they can be merged, or if you can do something in the titles or posts on each to make clearer why there are two separate issues.
• The "Task Documentation" section of your wiki is a little confusing. I suggest making this just "Documentation", and then make the two bullet points under it clearer. That is, explain what the group log is for, and then explain that you're using Issues to document each task.

Overall, I think you're headed in the right direction and making good progress. Let us know if you need help getting the variables into shape for your analysis, and make sure you're checking back in to make sure your analysis is aligned with your hypothesis.

[annarupert]

@kbuzard Thank you for the feedback!

I am going to rename the lit review with a more specific name and I have updated the documentation slide on the wiki as well. I will make sure I update with a log post here for the day and recap what I did more specifically.

[annarupert]

Group Log November 27th

• Today I looked through the feedback from Dr.Buzard to see what we could fix/update on our documentation.

• I updated the Wiki so that it was more self explanatory and easier to navigate.

• I also renamed the lit review issues so that they were easier to understand.

• Our original lit review assignment is now labeled with the word "original".

• The new lit review issue will be used to actually brainstorm and write the lit review and is a more targeted task.

• We will use this issue to upload our complete individual sections of the lit review so we can consolidate it into our final project. It is now entitled Outlining and Writing the Final Lit Review .

[Yuhan-2435]

Group Log November 29th

• Today we finished the plan for final submission and posted it on the discussion board for in the exercises repo.
• We plan on using the feedback Dr.Buzard gave us and adding it to our plan by the end of the weekend.
• We also added the plan to our Wiki.
• Our goal was to figure out the task distributions and deadlines, which as of now are separated as

Will: Data Fix Anna and Yuhan: Data Analysis Tomoyoshi: Lit Review

[Yuhan-2435]

Group Log December 1st

Overall:

• Today Will worked on finishing the data fix for all of our variables which is now complete and posted on #11.
• Anna and Yuhan are working on Data Analysis and are going to have all graphs finished by Monday after offices hours.
• Tomoyoshi is still working on the Lit Review and is doing some extra research to solidify that portion of our paper.

Work in Issue #17 First Draft Analysis

• We Sort the var annual_average_employees into deciles so its can be easily understood in a graph! Do-File
• We plan on combining the data fix that Will completed today and the work that we did on the decile to have a clear and concise interpretation of our data to finish our analysis with.

[kbuzard]

@ecn310/accidentsteam I think you need a few more task issues to cover everything that's in the plan for the rest of the semester. Some of them can be grouped together so it's not overwhelming.

In particular, you have the presentation coming up in less than a week. Who's responsible for that? What is the plan for getting it pulled together?

[annarupert]

Thank you @kbuzard! Here is a quick update based on your feedback.

Dec 2 Update

• Today I made a new issue for our presentation plan for Dec 8 #18

• I also worked on planning out the items that need to be completed for our presentation.

• As of now, I think we have most of the issues open that we need but I will open more on Monday when we move towards finalizing some other aspects of our project.

• I will also create a new do-file tomorrow that will combine the data fix and all of the new variables we have created for analysis.

[Yuhan-2435]

Dec 3 Update

• I used the decile created by the decile.do file to work on the bar graphs of the deciles and the variables, and uploaded the graph to #17.
• bar graphs

[annarupert]

Dec 3 Update Part 2

• I added a cumulative do-file onto github which combines all of Wills work and all of the work Yuhan and I have been doing on the analysis.
• I also plan on completing the analysis and submitting it onto github by EOD.

[annarupert]

Dec 6 Update

• Today we created an issue for the discussion section of our paper that Yuhan is working on, can be found here #20
• Tomoyoshi is currently finishing up the Lit Review which can be found under #13
• We also completed the data portion of the project #19 which will helped me complete by explaining our data fix.
• I am currently finishing the presentation for Friday and will post it in the presentation issue #18 and as a file on the code page.
• We completed the documentation plan which is on our wiki and has its own issue incase it needs to be edited, found here #21 .

[annarupert]

Daily Log for Dec 8th

• I submitted the presentation for tomorrow on issues and on home page #18
• I finished the analysis and put it in the issue #17

[annarupert]

Daily Log for Dec 9th

• we presented our presentation and got feedback, our presentation is on our repo home page.
• I created issues for the abstract #24, introduction #23, and output analysis portion of the project #22
• I also updated our documentation plan for full credit.

[annarupert]

Dec 9th Goals and Log

• update analysis based on Professor Buzards notes, as of now create box plot and post to GitHub issue #17
• Post the most recent version of our paper onto GitHub.

[annarupert]

Daily Log Dec 12

• I uploaded our basically finished paper, we are just missing our bibliography and obviously any edits that @kbuzard gives us.
• Our project is under files on the home page of our repo.

[Yuhan-2435]

Daily Log Dec 19

• I created a folder Reproducibility Package, and subfolders Data, Output. I moved related files into the folders.

[annarupert]

Daily Log Dec 19

• Yuhan and I completed the editing and data documentation for the rest of the project.
• We closed all issues and added the final to our wiki!

@kbuzard Thank you for a great semester!!

[kbuzard]

You're welcome! And thank you for all your hard work. I'm looking forward to enjoying the finished product and will get comments and the grading rubric to you ASAP (these take a LONG time to grade!)