Getting started
View repository
Getting started / Choose your projectRead source ↗

Choose what to build

Choose a question you want to answer. Use Cookbooks to find a sample source and its limits. The ideas below can start with any source that fits; PokéAPI is one optional starter.

Hackathon tracks

The event page lists the current tracks, rules and judging. Choose a track that fits the work your agent will demonstrate.

Analyse some data

Start with a small sample from a Cookbook, or use the PokéAPI starter. Then:

  1. Write your question.
  2. Check what each row and field means.
  3. Query the data and compare a few results with the source.
  4. Save the SQL and explain what you found, including any gaps.

Combine sources

Choose a second source. Check the join key and what each row represents. Look for duplicates and missing matches; company names alone often are not enough to join records.

Try these guides:

  • VDM and USL compares the SQL and model options, with their tested limits.
  • EDGAR and SIC walks through a USL model, relationships and data-quality checks. The foreign-key check found one invalid record; materialisation remains unverified.
  • EDGAR, PUDL and NOAA is an advanced walkthrough. PUDL is blocked, its weather period is partial, and its data-quality result is unverified.

On the shared instance, replace sample database, container, namespace and model names with your assigned names. Use shared sources only with read permission. Leave other teams' objects alone.

Save the joined result and explain any duplicates, missing matches or date gaps.

Build an app or chart

Show real query results in the interface and make errors visible. Keep platform credentials on the server, out of browser code. A deployed app needs its own access and authentication setup.

The PUDL chart example uses Python and a local HTML chart. Its sample data can check the layout, but a real query is needed to show the connection works. The example is available once PUDL works on your instance.

PUDL's energy-source codes describe fuel categories, not generation. For generation analysis, register and check the generator table first.

Prepare your demo

Use the demo template to record your setup, query and result, including anything you have not checked. Follow the official event rules for submission details.

Built from the repository documentation. Use your own account and team names on the shared instance.