Climate and Sustainability Hackathon with Cloudera and AMD

2321 Registered Allowed team size: 1 - 4
2321 Registered Allowed team size: 1 - 4

Winners are announced.

starts on:
Oct 18, 2023, 04:05 AM UTC (UTC)
ends on:
Nov 27, 2023, 04:55 AM UTC (UTC)
starts on:
Jan 29, 2024, 05:05 AM UTC (UTC)
ends on:
Mar 07, 2024, 04:55 AM UTC (UTC)


Submission Guide

Here's a sample submission guideline created by us:

Phase 1

During this phase, teams will have 4 weeks to develop and deliver a proposal for their project

Your idea submission must have the following:

  • Problem Statement: what is the specific climate issue that your project will be focusing on
  • Approach: how will your project employ machine learning methods to solve this problem
  • Differentiator: how will your project stand out from the other submissions

Phase 2

For those selected to move on to the project phase, you will have 2 weeks to work on and provide 2 main deliverables. (1) a GitHub repository structured as outlined below, and (2) a video, no longer than 5 minutes, that explains your project to the judges.

Your GitHub repository should adhere to the following file structure:

        ├── src/        
        ├── scripts/
        │   ├──
        │   ├──
        │   ├──
        │   └──
        ├── app/
        ├── static/
        ├── .project-metadata.yaml
        └── requirements.txt

File structure explanations and examples:

  • src/ - Core code/classes necessary for the project (this is code that generally defines processes)
  • scripts/ - Utility scripts for project and application setup (this is code that generally executes processes, these scripts will be called by the .project-metadata.yaml file)
    • - script to download necessary dataset
    • - script to install dependencies pinned in requirements
    • - script to prep data and train and/or validate model
    • - script to launch the visualization/application. The linked example is for a Streamlit application, though several other options and examples exist, just take a look in the AMP catalog.
  • app/ - Assets needed to support the front end application (this is code that purely supports the front-end). The linked example goes along with the example also linked, so it will be a good example for a Streamlit application.
  • static/ - Any images referenced in project docs
  • .project-metadata.yaml - Declarative configuration file that specifies necessary steps to recreate the project in CML. The linked example includes comments for specific lines that may need to be modified. If you follow the exact naming convention documented here, then you will not have very much that needs to be modified.
  • - Should fully describe your project including: overview of your AMP, a brief overview of any novel ML techniques used, an explanation of the project structure, and instructions to run your AMP.
  • requirements.txt - list of pinned dependencies

Social Share

View All Notifications