ericamarie9016 / threeza-crowd

Repository Assignment

This repository contains all folders and files that we worked on for EDS 214.

Credit: https://www.researchgate.net

Repository Objectives:

1. Organize all of our work for this project in one place. Be an appropriate landing page for others to view our work.

2. Communicate the chemistry change of local streams within the Luquillo Experimental Forest (LEF).

3. Show a clear progression in our workflow.

Project Introduction:

Hello! Thank you for taking the time to read through our repository. I hope you find everything easily. This is all the work we completed for the EDS 214 group project. We would also like to give a big thank you to Julian Brun for all of his hard work towards this course. Below you will find more information regarding the repository. Happy Coding! :)

This Repository contains the following folders and files:

Folders:

Plots:

A folder containing all of the plots created and included in the slideshow presentation.

Scripts:

A folder containing all of the scripts that we wrote for the both graphs.

Misc:

R generated files and a backup code document that we created in case we lost any data.

Files:

• .gitignore: A list of filetypes that should not be uploaded to the repository.
• LICENSE: The licensing for the repository.
• README.md: this file that you are reading right now outlining our goals and explaining the contents of the repository.
• Assignment_Instructions: The original assignment instructions.

Contact Information:

If you have any questions, comments, or concerns, please reach out to a group member using the information below:

Michael Zargari Github: @mzargari Email: [email protected]
Meagan Brown Github: @meaganbrown Email: [email protected]
Hailey Veirs Github: @hveirs Email: [email protected]
Erica Dale Github: @ericamarie9016 Email: [email protected]

Assignment Workflow

1. Create a coding workflow.
2. Divide up tasks
3. Draft pseduocode.
4. Work on code for first question
5. Brainstorm code to create our second code
6. Divide up tasks
7. Draft pseduocode.
8. Work on code for our second question.
9. Take notes on our progress along the way.
10. Clean up repository and put files in neat folders
11. Update readme
12. Make final touches and thank teaching team for the great semester! (Thank you for such a great semester!!)

Coding Etiquette

The following rules should be upheld at all times when coding or working in this repo:

1. Include informative comments throughout your code, using the double hashtag (##) symbol.
2. Comment out lines of code using a singlular hashtag (#) symbol
3. Space out your code to make it easier to read (putting spaces between operators).
4. Give informative names to all of your objects.
5. Keep your code to under 80 characters in length per line to avoid text travelling off screen (add guidance line as reference).
6. When naming folders, keep all text lowercase and use a dash (-) instead of spaces. i.e. “meds-courses”
7. When naming files, keep all text lowercase and use a underscore (_) instead of spaces. i.e. “sb_water_2022”

Have a Great Day!

- Michael, Meagan, Hailey, Erica