Skip to content

Commit

Permalink
Merge pull request #108 from AdrianMarzil/EverythingAnywhere_readme-1
Browse files Browse the repository at this point in the history
Update readme_EverythingAnywhereAllAtOnce.md
  • Loading branch information
RomiP committed Aug 10, 2023
2 parents 77332fd + cb5b184 commit 224ea33
Showing 1 changed file with 41 additions and 30 deletions.
71 changes: 41 additions & 30 deletions book/projects/project_readmes/readme_EverythingAnywhereAllAtOnce.md
Original file line number Diff line number Diff line change
@@ -1,51 +1,62 @@
# Everything Anywhere All At Once
# Everything, Anywhere, All At Once (EAAAO!)

## Team Members

Add your team members in this section.
Feel free to include links to GitHub profiles or personal websites.

The following people contributed to our project throughout the week:
* Project lead: [name of person](url to their webpage)
* Project lead (if more than one): [name of person](url to their webpage)
* Project lead: [Shanshan ](url to their webpage)
* Project lead: [Adrian Marziliano](https://github.com/AdrianMarzil)
* Helper: [name of person](url to their webpage)
* Helper (if more than one): [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [name of person](url to their webpage)
* Team member: [Romina Piunno](url to their webpage)
* Team member: [Michael Studinger](https://science.gsfc.nasa.gov/sed/bio/michael.studinger)
* Team member: [Zach Fair](url to their webpage)
* Team member: [Phillip Arndt](url to their webpage)
* Team member: [David Shean](url to their webpage)
* Team member: [Zheng Liu](https://github.com/liuzheng-arctic)


## Project Goals

What were the goals of your project?
Remember, small, clear, actionable goals are a great way to foster hacking success!
List or state them here.
For example: Our team was interested in further exploring the tutorial material and learning how to collaborate on object oriented code.
Our goal for the week was to design a simple Python class called "Pho" (the ICESat-2 mascot) and have each person contribute a function to describe Pho or let it perform an action based on
Our team was motivated to resolve a common frustration among the ICESat-2 science community regarding the uncertainty of the satellite's flight paths and timing.
Our goal for the week was to design a simple Python script to help researchers more succesffuly plan their field site visits to align with ICESat-2 flyovers.


## Project Outcomes
We were successful in creating a (notebook/function?) which receives a user-input AOI, finds the potential ICESat-2 data points within a (25km?) radius of this AOI, and draws the three track lines (beam pairs) associated with these data points, and outputs an interactive map of these data points and tracks along with. The script also allows for this output to be saved as a GeoJSON file which can then be saved on a mobile device to allow for planning in the field.

List and describe, if desired, any project outcomes accomplished during the week.
These may be individual or aggregate, large or small.
The idea is to capture what your team learned and accomplished.
Links to relevant outputs are a great way to capture these outcomes, so long as the links are likely to remain valid for some time (this readme - with this list - will be archived as part of the Hackweek JupyterBook).
Some examples might be:
Zheng Liu pitched this idea to the ICESat-2 Hackweek group on August 7, 2023.

* We submitted a [Pull Request (PR) to the earthaccess library](https://nsidc.github.io/earthaccess/) to fix a typo.
* Kate opened a [discussion on icepyx](https://github.com/icesat2py/icepyx/discussions).
* Sam and Harvey put in a [SlideRule feature request](https://github.com/orgs/ICESat2-SlideRule/discussions).
* six team members wrote [functions for Pho](link to project team repository).
* We wrote a code block that finds the highest and lowest photon in a granule.
* [Example Workflow Jupyter Notebook](your notebook url here).
* We drafted a conference abstract for submission to [conference](https://www.agu.org/).
The group completed tasks for this project as follows:
* Michael created a user interface that accepted a single latitude/longitude AOI point and created a circle polygon (radius: 25km)
* Phillip downloaded ICESat-2 time specific orbit (cycle) kml's from the 'Technical Specs' page (https://icesat-2.gsfc.nasa.gov/science/specs) and converted them to a geodataframe
* Adrian (under Phillip's guidance) clipped the orbit geodataframe using the AOI circle polygon
* Zachary drew the beam pairs for the clipped
* Shanshan created the interactive map output to display the beam pairs, AOI, and time stamps for the user-input latitude/longitude
* Romina synthesized these tasks into a single workflow and (notebook?)
* David assisted in advising the group on designing a project framework, file formatting, processing efficiency, and


## Files
Example:
* `.gitignore`
<br> Globally ignored files by `git` for the project.
* `environment.yml`
<br> `conda` environment description needed to run this project.
* `README.md`
<br> Description of the project. [Sample](https://geohackweek.github.io/wiki/github_project_management.html#project-guidelines)

## Folders

## Notebooks
Example: Links to relevant outputs are a great way to capture these outcomes, so long as the links are likely to remain valid for some time (this readme - with this list - will be archived as part of the Hackweek JupyterBook).
Some examples might be:
* [Example Workflow Jupyter Notebook](your notebook url here).


## Future Efforts

There are multiple ideas to improve upon this work to increase the effectiveness of ICESat-2 flight prediction.
There are currently no plans for this team to continue work on this project after the 2023 Hackweek, but we are open to suggestions and

Have you built any great new collaborations you anticipate continuing after the Hackweek?
Is your team planning to keep meeting to continue hacking or draft a conference abstract or proposal?
Did you start doing some work that relates to your research and enables you to contribute to shared tools for working with ICESat-2 data products?
Expand Down

0 comments on commit 224ea33

Please sign in to comment.