generated from CU-ESIIL/Working_group_OASIS
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit bcad7a1
Showing
50 changed files
with
1,926 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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 }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# [Your Working Group Name] | ||
|
||
Welcome to the **[Your Working Group Name]** repository, an integral part of the Environmental Data Science Innovation and Inclusion Lab (ESIIL). This repository is the central hub for our working group, encompassing our project overview, proposals, team member information, codebase, and more. | ||
|
||
## Our Project | ||
[Provide a brief overview of your project here. Describe what you aim to achieve, the importance of your project, and its expected impact.] | ||
|
||
## Documentation | ||
- Access detailed documentation on our [GitHub Pages site](https://your-gh-pages-url/). | ||
- Find comprehensive guides, tutorials, and additional resources. | ||
|
||
## Project Proposal | ||
[Link to the detailed project proposal document or include it directly in the repository. Outline the goals, methodologies, anticipated challenges, and projected timelines.] | ||
|
||
## Group Members | ||
- Member 1: Brief description or role within the group. | ||
- Member 2: Brief description or role within the group. | ||
- ... | ||
- [Link to more detailed bios or profiles if available.] | ||
|
||
## Repository Structure | ||
- **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 | ||
- Regular updates to keep all group members informed and engaged with the project's progress and direction. | ||
|
||
## Contributing to This Repository | ||
- Contributions from all group members are welcome. | ||
- Please adhere to these guidelines: | ||
- Ensure commits have clear and concise messages. | ||
- Document major changes in the meeting notes. | ||
- Review and merge changes through pull requests for oversight. | ||
|
||
## Getting Help | ||
- If you encounter any issues or have questions, please refer to the [ESIIL Support Page](https://esiil-support-page-url/) or contact the repository maintainers directly. | ||
|
||
## Customize Your Repository | ||
- **Edit This Readme**: Update with information specific to your project. | ||
- **Update Group Member Bios**: Add detailed information about each group member's expertise and role. | ||
- **Organize Your Code**: Use logical structure and clear naming conventions. | ||
- **Document Your Data**: Include a data directory with README files for datasets. | ||
- **Outline Your Methods**: Create a METHODS.md file for methodologies and tools. | ||
- **Set Up Project Management**: Use 'Issues' and 'Projects' for task tracking. | ||
- **Add a License**: Include an appropriate open-source license. | ||
- **Create Contribution Guidelines**: Establish a CONTRIBUTING.md file. | ||
- **Review and Merge Workflow**: Document your process for reviewing and merging changes. | ||
- **Establish Communication Channels**: Set up channels like Slack or Discord for 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! |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
# [Your Working Group Name] | ||
|
||
Welcome to the [Your Working Group Name] repository, part of the Environmental Data Science Innovation and Inclusion Lab (ESIIL). This repository serves as the central hub for our working group, hosting our project description, proposals, member bios, codebase, and more. | ||
|
||
## Our 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.] | ||
|
||
## Group Members | ||
|
||
[List the names and a brief description of each group member, possibly linking to their personal or professional web pages.] | ||
|
||
- **Member 1**: Brief description or role within the group. | ||
- **Member 2**: Brief description or role within the group. | ||
- ... | ||
|
||
## 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! | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
science art | ||
================ | ||
2024-01-25 | ||
|
||
# Ty’s art opinion | ||
|
||
In the context of the ongoing discussions for the redesign of our ESIIL | ||
office space, I would like to offer my personal perspective on the art | ||
and aesthetic that might enrich our environment: | ||
|
||
**Urban Realism with a Personal Touch**: I have a strong appreciation | ||
for artworks that reflect a realistic depiction of nature and urban life | ||
but with an imaginative twist. Art that integrates with and elevates our | ||
daily surroundings could offer a fresh perspective on the mundane. | ||
|
||
**Nature in the Workplace**: On a personal note, I find that art which | ||
brings elements of the outdoors inside can create a serene and | ||
motivating atmosphere, conducive to the values of sustainability that | ||
ESIIL embodies. | ||
|
||
**Interactive Art**: I believe that art installations which invite | ||
interaction or present a playful exaggeration of reality can energize | ||
our space. They have the potential to foster a creative dialogue among | ||
the team and with visitors. | ||
|
||
**Dimensionality and Engagement**: From my viewpoint, art that breaks | ||
out of the traditional two-dimensional space and engages with the viewer | ||
in three dimensions can transform the feel of an office. Such dynamic | ||
pieces could encourage innovative thinking and collaboration. | ||
|
||
**Art with a Message**: It’s my opinion that the art we choose should | ||
subtly reflect our collective social and environmental commitments. | ||
Pieces that prompt introspection about our role in larger societal | ||
issues could resonate well with our team’s ethos. | ||
|
||
**Community Connection**: Lastly, I feel that our office should not just | ||
be a place for work but also a space that invites community interaction. | ||
Art can be a bridge between ESIIL and the public, making our office a | ||
hub for inspiration and engagement. | ||
|
||
![](../assets/esiil_art/antenna_girl.png) | ||
|
||
![](../assets/esiil_art/child_plant_interaction.png) | ||
|
||
![](../assets/esiil_art/hen_harrier.png) | ||
![](../assets/esiil_art/tree_hair.png) | ||
![](../assets/esiil_art/sculpture_toothpaste.png) | ||
![](../assets/esiil_art/tree%20hands.png) | ||
![](../assets/esiil_art/paperclip.png) | ||
![](../assets/esiil_art/fancy_dandilion.png) | ||
![](../assets/esiil_art/tree_palm.png) | ||
![](../assets/esiil_art/swans.png) ![](../assets/esiil_art/diver.png) | ||
![](../assets/esiil_art/looker.png) | ||
![](../assets/esiil_art/veg_as_hair.png) | ||
![](../assets/esiil_art/turtle.png) | ||
![](../assets/esiil_art/peel_back.png) | ||
![](../assets/esiil_art/tree_eyes.png) | ||
![](../assets/esiil_art/gull_trash.png) | ||
![](../assets/esiil_art/monolith-alpha.png) | ||
![](../assets/esiil_art/veg_from_box.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
--- | ||
title: "science art" | ||
date: "2024-01-25" | ||
format: gfm | ||
editor_options: | ||
markdown: | ||
wrap: 72 | ||
--- | ||
|
||
# Ty's art opinion | ||
|
||
In the context of the ongoing discussions for the redesign of our ESIIL office space, I would like to offer my personal perspective on the art and aesthetic that might enrich our environment: | ||
|
||
**Urban Realism with a Personal Touch**: I have a strong appreciation for artworks that reflect a realistic depiction of nature and urban life but with an imaginative twist. Art that integrates with and elevates our daily surroundings could offer a fresh perspective on the mundane. | ||
|
||
**Nature in the Workplace**: On a personal note, I find that art which brings elements of the outdoors inside can create a serene and motivating atmosphere, conducive to the values of sustainability that ESIIL embodies. | ||
|
||
**Interactive Art**: I believe that art installations which invite interaction or present a playful exaggeration of reality can energize our space. They have the potential to foster a creative dialogue among the team and with visitors. | ||
|
||
**Dimensionality and Engagement**: From my viewpoint, art that breaks out of the traditional two-dimensional space and engages with the viewer in three dimensions can transform the feel of an office. Such dynamic pieces could encourage innovative thinking and collaboration. | ||
|
||
**Art with a Message**: It's my opinion that the art we choose should subtly reflect our collective social and environmental commitments. Pieces that prompt introspection about our role in larger societal issues could resonate well with our team's ethos. | ||
|
||
**Community Connection**: Lastly, I feel that our office should not just be a place for work but also a space that invites community interaction. Art can be a bridge between ESIIL and the public, making our office a hub for inspiration and engagement. | ||
|
||
![](../assets/esiil_art/antenna_girl.png) | ||
|
||
![](../assets/esiil_art/child_plant_interaction.png) | ||
|
||
|
||
|
||
![](../assets/esiil_art/hen_harrier.png) | ||
![](../assets/esiil_art/tree_hair.png) | ||
![](../assets/esiil_art/sculpture_toothpaste.png) | ||
![](../assets/esiil_art/tree hands.png) | ||
![](../assets/esiil_art/paperclip.png) | ||
![](../assets/esiil_art/fancy_dandilion.png) | ||
![](../assets/esiil_art/tree_palm.png) | ||
![](../assets/esiil_art/swans.png) | ||
![](../assets/esiil_art/diver.png) | ||
![](../assets/esiil_art/looker.png) | ||
![](../assets/esiil_art/veg_as_hair.png) | ||
![](../assets/esiil_art/turtle.png) | ||
![](../assets/esiil_art/peel_back.png) | ||
![](../assets/esiil_art/tree_eyes.png) | ||
![](../assets/esiil_art/gull_trash.png) | ||
![](../assets/esiil_art/monolith-alpha.png) | ||
![](../assets/esiil_art/veg_from_box.png) | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
Oops, something went wrong.