nasa-openscapes / 2021-cloud-hackathon Goto Github PK

We will use the pre-installed git extension in 2i2c JupyterLab for interacting with git/github. We need to update Tutorial 00 instructions with JupyterLab Git extension

so not scattered throughout

Great work on this repo, thanks so much! We'd like to use some of the code in here for a tutorial in a few weeks for an ICESat-2 science team workshop, where @tsnow03 and I will be discussing the new 2i2c-hosted hub for the IS-2/cryo community. But I don't see a license in this repo... Without an explicit license, code is by default (in the US at least) copyright to the author with all rights reserved, so I can't really use it until a license is put on the repo.

Our content will all be BSD/MIT-licensed (with CC-BY for non-code), it would be awesome if your license choice could be compatible, but that's obviously your call.

Thanks!

add into book, with breakout room screenshots etc

Just a few ideas as followup for @virdi from the Clinic

• consider having them create their own repo in their GitHub account so they'll have push access
• reorder the "git clone" step to be before step 3

both the filename and title

so not scattered throughout

earthdata authentification

Is there a reason this is not using earthdata?

from earthdata import Auth
auth = Auth().login()
url = "https://archive.podaac.earthdata.nasa.gov/s3credentials"
response = requests.get(url).json()

I was trying to run the tutorials from AGU workshop & 2021 Hackathon using mybinder.org yesterday.

Seems like it could be a good approach to let more people take advantage of the great stuff that you all have been putting together, outside of the time frame of specific events like AGU or the Hackathon. Any thoughts?

This worked to a point (you can try it at https://mybinder.org/v2/gh/gaelforget/corn/gfdev01) but what I mostly wanted to try out were the direct data access notebooks and these failed on mybinder (despite, I believe, having added my .netrc file in the right place). After looking more carefully at the repo webpage, my guess is that the errors I ran into had to do with direct data access being restricted to "AWS / us-west-2" and this brings a few questions :

• is my guess correct or am I overlooking another issue?
• is there or will there be a work around for this?
• would extending the S3 buckets to other regions / worldwide suffice ? (assuming that e.g. NASA would pay for that)

Add and organize content for Pre-Hackathon Clinic