diff --git a/content/blog/2024/frx/index.md b/content/blog/2024/frx/index.md index b9ab8c710..feff6b2f5 100644 --- a/content/blog/2024/frx/index.md +++ b/content/blog/2024/frx/index.md @@ -17,9 +17,7 @@ This project aims to make it easier for administrators to provide a service that caption="An example leaderboard for a data challenge, taken from the [Cellmap Challenge](https://cellmapchallenge.janelia.org/). Users make submissions that are run against secure and private infrastructure and data, and provides feedback about the submission's performance. Learn more about the FRX challenges project here: https://2i2c.org/frx-challenges/" >}} -It is designed to be lightweight and flexible, and can be run on a variety of shared infrastructure. For those who wish to run this project on cloud infrastructure, we've also published a Helm Chart to help you deploy `frx-challenges` with Kubernetes: - -https://2i2c.org/frx-challenges-helm-chart/ +It is designed to be lightweight and flexible, and can be run on a variety of shared infrastructure. For those who wish to run this project on cloud infrastructure, we've also published a [Helm Chart to help you deploy `frx-challenges` with Kubernetes](https://2i2c.org/frx-challenges-helm-chart/). While it can be run on its own, we believe that it naturally complements other tools and services for interactive computing and data, such as **JupyterHub**, **Jupyter Book**, and **Binder**. More on that below. @@ -47,7 +45,7 @@ Data challenges are harder than you think! While it is simple enough to run some - **Submissions must retain user and team identity**, which means that we must keep track of users and their submissions over time, since data challenges are designed to encourage iterative improvement and optimization. - **Evaluations must use potentially complex resources and data** since many data challenges operate by publicly sharing a small dataset, and then running it against a much more complex dataset. -- **Evaluations must be totally secure**, so that submissions can't do nefarious things like mine cryptocurrency or gain access to the challenge's private data. +- **Evaluations must be totally secure**, so that submissions can't do nefarious things like mine cryptocurrency or extract the challenge's private data in unintended ways. - **Evaluations must be automated**, so that running the challenge does not require extensive human intervention and can scale to many users. - **Evaluation must be flexible**, so that the infrastructure can accept a variety of types of submissions (e.g. code, data, model weights, etc), run them with arbitrary environments designed by the organizers, and run them with the right hardware to get the job done. @@ -61,4 +59,6 @@ This is still the **very early stages** of the project, and we imagine it will e ## Acknowledgements -Many thanks to the Howard Hughes Medical Institute (HHMI) for collaborating with us on the [Cellmap Challenge](https://cellmapchallenge.janelia.org/), which led to the creation of this project. +Thanks to the Howard Hughes Medical Institute (HHMI) for collaborating with us on the [Cellmap Challenge](https://cellmapchallenge.janelia.org/), which led to the creation of this project. + +Thanks to Kristen Ratan and [Strategies for Open Science](https://strategiesos.org/about/) (Stratos) for enabling this collaboration, and providing strategic guidance and support. \ No newline at end of file diff --git a/content/blog/2024/retrospective/index.md b/content/blog/2024/retrospective/index.md index 3e477ebfb..743f8afd6 100644 --- a/content/blog/2024/retrospective/index.md +++ b/content/blog/2024/retrospective/index.md @@ -55,6 +55,11 @@ Here are a few community highlights from this year: - The NeuroHackademy used our infrastructure to support their annual summer school: http://2i2c.org/blog/2024/neurohackademy-summer-school-reflections/ - We enabled ephemeral and sharable interactive computing environments for workshops in the geospatial community: http://2i2c.org/blog/2024/amerigeo-workshop/ - We ran a pilot for an HHMI-funded Spyglass project for reproducing their pre-print with a live interactive environment using BinderHub to support publishing infrastructure: https://2i2c.org/blog/2024/hhmi-spyglass-mysql/ +- We began a collaboration around biomedical infrastructure for +- We began a collaboration with [Development Seed](https://developmentseed.org/) around the NASA VEDA project, to support them with interactive cloud environments for geospatial research: https://2i2c.org/blog/2024/veda-devseed-collab/index.md +- Several members in our community network showed off their work at [AGU 2024](https://www.agu.org/annual-meeting): https://2i2c.org/blog/2024/agu/ +- We co-organized a workshop alongside [Project Pythia](https://projectpythia.org/) to create computational narrative content for geospatial analytics, and upgrade their stack to Jupyter Book 2.0: https://2i2c.org/blog/2024/project-pythia-cookoff/ + ## Open source technology enhancements