Just a note that we should wrap this one up ASAP

Thank you very much for the great work, which help me a lot in extracting the water depths from IceSat 2 data.

During the implementation of the codes, I got the error:
TypeError: atl03sp() got an unexpected keyword argument 'asset'

when using
df_0 = icesat2.atl03sp(parms,asset=asset, version='006', resources=granules_list)

Remove
asset=asset, version='006' can make the codes work.
However, I can not get the similar list as your features:
Available photon-rate features: ['sc_orient' 'solar_elevation' 'rgt' 'track' 'background_rate' 'segment_id' 'segment_dist' 'cycle' 'distance' 'snowcover' 'atl08_class' 'quality_ph' 'atl03_cnf' 'landcover' 'relief' 'yapc_score' 'height' 'ref_azimuth' 'ref_elev' 'geoid' 'pair' 'geometry' 'spot']

especially for the feature "distance", which is used in this line:
# add a column for along-track distance df['along_track_meters'] = df['segment_dist']+df['distance']-np.min(df['segment_dist'])

I checked the API of atl03sp but it was not mention anything about asset or version.

Do I miss something here?

Here are my granule 'ATL03_20230725085527_05372007_006_02.h5' and available features:
Available photon-rate features: ['region' 'rgt' 'pair' 'track' 'solar_elevation' 'segment_id' 'background_rate' 'segment_dist' 'sc_orient' 'cycle' 'yapc_score' 'x_atc' 'y_atc' 'landcover' 'quality_ph' 'height' 'relief' 'atl08_class' 'atl03_cnf' 'snowcover' 'ref_azimuth' 'ref_elev' 'geoid' 'geometry' 'spot']

Regards,
Thang

Docker image tags match github shas
https://quay.io/repository/cryointhecloud/cryo-hub-image?tab=tags

Instead of the date we can put the sha here to keep track

(#62 (comment))

For this event, Docker Images are managed at https://github.com/CryoInTheCloud/hub-image ,

So we can disable pushing images:
https://github.com/ICESAT-2HackWeek/ICESat-2-Hackweek-2023/blob/main/.github/workflows/repo2docker.yaml

#56 (comment)

Checks aren't necessary to merge, so can leave it as-is, but it looks like the preview workflow will run currently against any PR:

This PR didn't get a preview #50

Simply because WARNING: Non-consecutive header level increase; 2 to 4 [myst.header] raises an error code

Log:
https://github.com/ICESAT-2HackWeek/ICESat-2-Hackweek-2023/actions/runs/5720017208/job/15499143677?pr=50

I think we want the warnings to still raise errors, but at least create the preview link.

Suggest we add text below the sponsor logos to acknowledge our specific funding source:

NASA Cryo ICESat-2 Mission 80NSSC23PA905

The current ICESat-2 Jupyter Book has sidebar links to schedule and and team that currently link to the default template. Need to update these to link to the current hackweek website version.

To encourage use of the CryoHub, should we disable the binder-badge.yaml for this event?

CC: @scottyhq, @tsnow03

For example:

https://icesat-2-2023.hackweek.io/tutorials/data-access-and-format/earthdata_search.html#searching-for-data-and-s3-links-using-earthdata-search :

You can use this syntax to get images and captions appearing identically on the website and jupyterhub (https://jupyterbook.org/en/stable/content/figures.html#figures):

```{figure} ../images/C-3PO_droid.png
---
height: 150px
name: directive-fig
---
Here is my figure caption!
```

@andypbarrett @asteiker are one of you able to open a follow-up PR to fix? If you don't have time today we can get to it later, since as mentioned above things look good running the notebook in CryoCloud JupyterHub

Many tutorials notebooks download data to their subfolder. In addition to encouraging the use of /tmp for data downloads (https://docs.2i2c.org/data/filesystem/#the-tmp-directory).

I think adding common large binary formats (*.tif, *.h5, *.nc) to .gitignore will help steer people away from committing large files to the repository. cc @jomey @YoungHyunKoo