You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will be hosting a virtual hackathon event to examine performance of passive acoustic-equipped underwater gliders using data collected during an Underwater Glider Challenge (aka 'Glider Rodeo'). This hackathon will consist of NOAA researchers and we will invite other researchers with interest in underwater gliders and passive acoustic monitoring.
What RAM will participants typically need?
2Gb (default) for most work but up to 14 Gb for some tutorials (we are in preliminary preparations, so TBD).
Image Requirements
Good Question. We will need R and Python (packages may vary by participant). We are in preliminary preparations, so TBD.
Storage Requirements
We would like a Shared-Public directory for our primary datasets (size TBD), and we expect some participants to upload environmental data (geographic area is small in scope, so should be reasonable). We will encourage groups to download to Shared-Public directory to limit multiple copies of same/similar datasets. We are in preliminary preparations, so TBD.
Checklist for workshop organizer (person planning/leading the workshop) and hub point-of-contact (PoC; Openscapes team member helping with hub setup and logistics. Usually @ateucher).
Hub PoC: Send confirmation to organizer that the request is received and the hub is available for the workshop (a comment in this issue thread is fine)
Organizer: Add your event in the workshop spreadsheet. Please check if there are any other workshops scheduled around the same time and if so, let the hub PoC know to make sure the hub can support multiple workshops at the same time.
Organizer: Submit a ticket by email to 2i2c for the workshop and request a new password for the workshop, as per instructions, cc'ing hub PoC (@ateucher; andy [at] openscapes [dot] org) and @eeholmes (eli [dot] holmes [at] noaa [dot] gov). You will receive confirmation of the new password for the workshop from 2i2c once it is reset.
Organizer: Two weeks before event. I have tested the default hub images on the nmfs-openscapes.2i2c.cloud hub or conferred with hub PoC on plan for a workshop specific image.
Organizer: In the week before the event (or when hub PoC indicates password should be live). I tested that the workshop password works and images work.
Organizer: After the event, open an issue in the Workshop Planning repo to report back.
Hub PoC: After event, put in a 2i2c ticket to reset password.
Hub PoC: After event, log in to the hub as admin, enumerate the participant directories and update the workshop spreadsheet with the actual number of participants.
Hub PoC: After event, delete the participant directories.
Hub PoC: Close the issue. If the workshop was completed, close as "completed". If the workshop was cancelled before being held, close as "Not Planned" and note in the comments that it was cancelled.
Workshop Description
We will be hosting a virtual hackathon event to examine performance of passive acoustic-equipped underwater gliders using data collected during an Underwater Glider Challenge (aka 'Glider Rodeo'). This hackathon will consist of NOAA researchers and we will invite other researchers with interest in underwater gliders and passive acoustic monitoring.
Workshop Start Date
2026-09-14
Workshop End Date
2026-19-18
Workshop Start Time
7:00 AM PST
Workshop End Time
7:00 PM PST
Workshop URL
https://nmfs-pam-glider.github.io/GliderRodeo/content/hackathon.html
Reset Date
2026-09-28
Estimated Number of Participants
~40 (no idea)
Compute Requirements
What RAM will participants typically need?
2Gb (default) for most work but up to 14 Gb for some tutorials (we are in preliminary preparations, so TBD).
Image Requirements
Good Question. We will need R and Python (packages may vary by participant). We are in preliminary preparations, so TBD.
Storage Requirements
We would like a Shared-Public directory for our primary datasets (size TBD), and we expect some participants to upload environmental data (geographic area is small in scope, so should be reasonable). We will encourage groups to download to Shared-Public directory to limit multiple copies of same/similar datasets. We are in preliminary preparations, so TBD.
Checklist for workshop organizer (person planning/leading the workshop) and hub point-of-contact (PoC; Openscapes team member helping with hub setup and logistics. Usually @ateucher).
Hub PoC: Send confirmation to organizer that the request is received and the hub is available for the workshop (a comment in this issue thread is fine)
Organizer: Add your event in the workshop spreadsheet. Please check if there are any other workshops scheduled around the same time and if so, let the hub PoC know to make sure the hub can support multiple workshops at the same time.
Organizer: Submit a ticket by email to 2i2c for the workshop and request a new password for the workshop, as per instructions, cc'ing hub PoC (@ateucher; andy [at] openscapes [dot] org) and @eeholmes (eli [dot] holmes [at] noaa [dot] gov). You will receive confirmation of the new password for the workshop from 2i2c once it is reset.
Hub PoC: Confirm
[Event]or[Support]issue opened in 2i2c-org/infrastructure in response to ticket (example)Hub PoC: Add new password and dates to workshop password spreadsheet.
Organizer: Two weeks before event. I have tested the default hub images on the nmfs-openscapes.2i2c.cloud hub or conferred with hub PoC on plan for a workshop specific image.
Organizer: In the week before the event (or when hub PoC indicates password should be live). I tested that the workshop password works and images work.
Organizer: After the event, open an issue in the Workshop Planning repo to report back.
Hub PoC: After event, put in a 2i2c ticket to reset password.
Hub PoC: After event, log in to the hub as admin, enumerate the participant directories and update the workshop spreadsheet with the actual number of participants.
Hub PoC: After event, delete the participant directories.
Hub PoC: Close the issue. If the workshop was completed, close as "completed". If the workshop was cancelled before being held, close as "Not Planned" and note in the comments that it was cancelled.