Initial commit

CU-ESIIL · Apr 17, 2024 · b424400 · b424400
commit b424400
Show file tree

Hide file tree

Showing 104 changed files with 10,859 additions and 0 deletions.
diff --git a/.DS_Store b/.DS_Store
diff --git a/.github/.DS_Store b/.github/.DS_Store
diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
@@ -0,0 +1,21 @@
+ name: Publish docs via GitHub
+ on:
+   push:
+     branches:
+       - main
+
+ jobs:
+   build:
+     name: Deploy docs
+     runs-on: ubuntu-latest
+     steps:
+       - uses: actions/checkout@v3
+       - uses: actions/setup-python@v4
+         with:
+           python-version: 3.9
+       - name: run requirements file
+         run:  pip install -r requirements.txt 
+       - name: Deploy docs
+         run: mkdocs gh-deploy --force
+         env:
+           GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,48 @@
+# History files
+.Rhistory
+.Rapp.history
+
+# Session Data files
+.RData
+.RDataTmp
+
+# User-specific files
+.Ruserdata
+
+# Example code in package build process
+*-Ex.R
+
+# Output files from R CMD build
+/*.tar.gz
+
+# Output files from R CMD check
+/*.Rcheck/
+
+# RStudio files
+.Rproj.user/
+
+# produced vignettes
+vignettes/*.html
+vignettes/*.pdf
+
+# OAuth2 token, see https://github.com/hadley/httr/releases/tag/v0.3
+.httr-oauth
+
+# knitr and R markdown default cache directories
+*_cache/
+/cache/
+
+# Temporary files created by R markdown
+*.utf8.md
+*.knit.md
+
+# R Environment Variables
+.Renviron
+
+
+
+# translation temp files
+po/*~
+
+# RStudio Connect folder
+rsconnect/
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Environmental Data Science Innovation and Inclusion Lab (ESIIL)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -0,0 +1,72 @@
+# Postdoc OASIS
+This is the central hub for information pertaining to ESIIL Postdocs
+
+# [Your Name]
+
+Welcome to the [Your Name] repository, part of the Environmental Data Science Innovation and Inclusion Lab (ESIIL). This repository serves as the central hub for our research at ESIIL, hosting your project description, proposals, bio, codebase, and more.
+
+## Your Project
+
+[Provide a brief overview of your project here. Explain what you aim to achieve, the importance of your project, and its expected impact.]
+
+## Project Proposal
+
+[Link to the detailed project proposal document or include the proposal directly in the repository. This should outline the goals, methodologies, anticipated challenges, and projected timelines.]
+
+## Collaborators and Co-Authors 
+
+[List the names and a brief description of people you work with, possibly linking to their personal or professional web pages.]
+
+- **Collaborator 1**: Brief description.
+- **Collaborator 2**: Brief description.
+- ...
+
+## Code Repository
+
+This section of the repository will include all the code developed for the project. You can structure it as follows:
+
+- **Analysis Code**: Scripts for data analysis, statistical modeling, etc.
+- **Data Processing**: Scripts for cleaning, merging, and managing datasets.
+- **Visualization**: Code for creating figures, charts, and interactive visualizations.
+
+## Meeting Notes and Agendas
+
+When you meet with your advisor, collaborators, or a team, you should take notes here. 
+
+## Contributing to This Repository
+
+To maintain the quality and integrity of the repository, please adhere to the following guidelines:
+
+- Make sure all commits have a clear and concise message.
+- Document any major changes or decisions in the meeting notes.
+- Review and merge changes through pull requests to ensure oversight.
+
+## Getting Help
+
+If you encounter any issues or have questions about how to contribute, please refer to the [ESIIL Support Page](https://esiil.org/support) or contact the repository maintainers directly.
+
+## Customize Your Repository
+
+As a new working group, you'll want to make this repository your own. Here's how to get started:
+
+1. **Edit This Readme**: Replace the placeholder content with information about your specific project. Ensure that the introduction, project overview, and objectives clearly reflect your group's research focus.
+
+2. **Update Bio**: Add details about your expertise, role in the project, and professional background. Include links to personal or professional web pages to foster community engagement and collaboration.
+
+3. **Organize Your Code**: Structure your codebase in a way that is logical and accessible. Use directories and clear naming conventions to make it easy for all members to find and contribute to different parts of the project.
+
+4. **Document Your Data**: Include a data directory with README files explaining the datasets, sources, and any preprocessing steps. This will help new members understand and work with the project's data effectively.
+
+5. **Outline Your Methods**: Create a detailed METHODS.md file where you describe the methodologies, software, and tools you will be using in your research. This transparency will support reproducibility and collaborative development.
+
+6. **Set Up Project Management**: Utilize the 'Issues' and 'Projects' features on GitHub to track tasks, discuss ideas, and manage your workflow. This can help in maintaining a clear view of progress and priorities.
+
+7. **Add a License**: Choose and include an appropriate open-source license for your project, ensuring that the broader community understands how they can use and contribute to your work.
+
+8. **Create Contribution Guidelines**: Establish a CONTRIBUTING.md file with instructions for members on how to propose changes, submit issues, and contribute code.
+
+9. **Review and Merge Workflow**: Decide on a workflow for reviewing and merging changes. Will you use branch protection? Who will have merge privileges? Document this process to avoid confusion.
+
+10. **Establish Communication Channels**: Beyond GitHub, set up additional communication channels like Slack, Discord, or email lists for quick and informal discussions.
+
+Remember, the goal is to make your repository clear, accessible, and useful for all current and future members of your working group. Happy researching!
diff --git a/docs/.DS_Store b/docs/.DS_Store
diff --git a/docs/assets/.DS_Store b/docs/assets/.DS_Store
diff --git a/docs/assets/cyverse_basics/app_launch.png b/docs/assets/cyverse_basics/app_launch.png
diff --git a/docs/assets/cyverse_basics/app_settings.png b/docs/assets/cyverse_basics/app_settings.png
diff --git a/docs/assets/cyverse_basics/apps.png b/docs/assets/cyverse_basics/apps.png
diff --git a/docs/assets/cyverse_basics/click_cyverse_utils.png b/docs/assets/cyverse_basics/click_cyverse_utils.png
diff --git a/docs/assets/cyverse_basics/clone.png b/docs/assets/cyverse_basics/clone.png
diff --git a/docs/assets/cyverse_basics/cyverse-utils.png b/docs/assets/cyverse_basics/cyverse-utils.png
diff --git a/docs/assets/cyverse_basics/email.png b/docs/assets/cyverse_basics/email.png
diff --git a/docs/assets/cyverse_basics/final.png b/docs/assets/cyverse_basics/final.png
diff --git a/docs/assets/cyverse_basics/go_to_analysis.png b/docs/assets/cyverse_basics/go_to_analysis.png
diff --git a/docs/assets/cyverse_basics/jupyterlab.png b/docs/assets/cyverse_basics/jupyterlab.png
diff --git a/docs/assets/cyverse_basics/key.png b/docs/assets/cyverse_basics/key.png
diff --git a/docs/assets/cyverse_basics/launch.png b/docs/assets/cyverse_basics/launch.png
diff --git a/docs/assets/cyverse_basics/new_key.png b/docs/assets/cyverse_basics/new_key.png
diff --git a/docs/assets/cyverse_basics/open_cyverse_utils.png b/docs/assets/cyverse_basics/open_cyverse_utils.png
diff --git a/docs/assets/cyverse_basics/paste_key.png b/docs/assets/cyverse_basics/paste_key.png
diff --git a/docs/assets/cyverse_basics/script_1.png b/docs/assets/cyverse_basics/script_1.png
diff --git a/docs/assets/cyverse_basics/settings.png b/docs/assets/cyverse_basics/settings.png
diff --git a/docs/assets/cyverse_basics/ssh.png b/docs/assets/cyverse_basics/ssh.png
diff --git a/docs/assets/cyverse_basics/use_this_app.png b/docs/assets/cyverse_basics/use_this_app.png
diff --git a/docs/assets/cyverse_basics/username.png b/docs/assets/cyverse_basics/username.png
diff --git a/docs/assets/esiil_content/.DS_Store b/docs/assets/esiil_content/.DS_Store
diff --git a/docs/assets/esiil_content/ESIIL_logo.png b/docs/assets/esiil_content/ESIIL_logo.png
diff --git a/docs/assets/esiil_content/favicon.ico b/docs/assets/esiil_content/favicon.ico
diff --git a/docs/assets/esiil_content/stac_mount_save/Ansel_Adams_datacube.png b/docs/assets/esiil_content/stac_mount_save/Ansel_Adams_datacube.png
diff --git a/docs/assets/esiil_content/stac_mount_save/Ansel_adams_Jackson_hole.png b/docs/assets/esiil_content/stac_mount_save/Ansel_adams_Jackson_hole.png
diff --git a/...e/David-Yarrow-sorrel-sky-gallery-Photographic-Print-Cindys-Shotgun-Wedding.png b/...e/David-Yarrow-sorrel-sky-gallery-Photographic-Print-Cindys-Shotgun-Wedding.png
diff --git a/docs/assets/esiil_content/stac_mount_save/View_Ansel-Adams_Camera.png b/docs/assets/esiil_content/stac_mount_save/View_Ansel-Adams_Camera.png
diff --git a/docs/assets/esiil_content/stac_mount_save/anim.gif b/docs/assets/esiil_content/stac_mount_save/anim.gif
diff --git a/docs/assets/esiil_content/stac_mount_save/antelopeinpython.png b/docs/assets/esiil_content/stac_mount_save/antelopeinpython.png
diff --git a/docs/assets/esiil_content/stac_mount_save/bison.png b/docs/assets/esiil_content/stac_mount_save/bison.png
diff --git a/docs/assets/esiil_content/stac_mount_save/drink-firehose.png b/docs/assets/esiil_content/stac_mount_save/drink-firehose.png
diff --git a/docs/assets/esiil_content/stac_mount_save/mouseinsnake.png b/docs/assets/esiil_content/stac_mount_save/mouseinsnake.png
diff --git a/docs/index.md b/docs/index.md
@@ -0,0 +1,65 @@
+# [Your Name]
+
+Welcome to the [Your Name] repository, part of the Environmental Data Science Innovation and Inclusion Lab (ESIIL). This repository serves as the central hub for our research at ESIIL, hosting your project description, proposals, bio, codebase, and more.
+
+## Your Project
+
+[Provide a brief overview of your project here. Explain what you aim to achieve, the importance of your project, and its expected impact.]
+
+## Project Proposal
+
+[Link to the detailed project proposal document or include the proposal directly in the repository. This should outline the goals, methodologies, anticipated challenges, and projected timelines.]
+
+## Collaborators
+- ...
+
+## Code Repository
+
+This section of the repository will include all the code developed for the project. You can structure it as follows:
+
+- **Analysis Code**: Scripts for data analysis, statistical modeling, etc.
+- **Data Processing**: Scripts for cleaning, merging, and managing datasets.
+- **Visualization**: Code for creating figures, charts, and interactive visualizations.
+
+## Meeting Notes and Agendas
+
+Meeting notes and agendas will be regularly updated here to keep all group members informed and engaged with the progress and direction of the project.
+
+## Contributing to This Repository
+
+We welcome contributions from all group members. To maintain the quality and integrity of the repository, please adhere to the following guidelines:
+
+- Make sure all commits have a clear and concise message.
+- Document any major changes or decisions in the meeting notes.
+- Review and merge changes through pull requests to ensure oversight.
+
+## Getting Help
+
+If you encounter any issues or have questions about how to contribute, please refer to the [ESIIL Support Page](https://esiil.org/support) or contact the repository maintainers directly.
+
+## Customize Your Repository
+
+As a new working group, you'll want to make this repository your own. Here's how to get started:
+
+1. **Edit This Readme**: Replace the placeholder content with information about your specific project. Ensure that the introduction, project overview, and objectives clearly reflect your group's research focus.
+
+2. **Update Group Member Bios**: Add details about each group member's expertise, role in the project, and professional background. Include links to personal or professional web pages to foster community engagement and collaboration.
+
+3. **Organize Your Code**: Structure your codebase in a way that is logical and accessible. Use directories and clear naming conventions to make it easy for all members to find and contribute to different parts of the project.
+
+4. **Document Your Data**: Include a data directory with README files explaining the datasets, sources, and any preprocessing steps. This will help new members understand and work with the project's data effectively.
+
+5. **Outline Your Methods**: Create a detailed METHODS.md file where you describe the methodologies, software, and tools you will be using in your research. This transparency will support reproducibility and collaborative development.
+
+6. **Set Up Project Management**: Utilize the 'Issues' and 'Projects' features on GitHub to track tasks, discuss ideas, and manage your workflow. This can help in maintaining a clear view of progress and priorities.
+
+7. **Add a License**: Choose and include an appropriate open-source license for your project, ensuring that the broader community understands how they can use and contribute to your work.
+
+8. **Create Contribution Guidelines**: Establish a CONTRIBUTING.md file with instructions for members on how to propose changes, submit issues, and contribute code.
+
+9. **Review and Merge Workflow**: Decide on a workflow for reviewing and merging changes. Will you use branch protection? Who will have merge privileges? Document this process to avoid confusion.
+
+10. **Establish Communication Channels**: Beyond GitHub, set up additional communication channels like Slack, Discord, or email lists for quick and informal discussions.
+
+Remember, the goal is to make your repository clear, accessible, and useful for all current and future members of your working group. Happy researching!
+
diff --git a/docs/resources/.DS_Store b/docs/resources/.DS_Store