8000 Add example dataflows by aakashkolli · Pull Request #41 · urban-toolkit/curio · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add example dataflows #41

8000
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Jun 12, 2025

Conversation

aakashkolli
Copy link
Contributor

Describe your changes

Started to add new, standardized example dataflow tutorials to the /docs/examples directory, adapted from selected UIC CS 424 student assignments. Includes Markdown files, datasets, and images/animations.

To ensure proper ordering of files, renamed all example Markdown filenames to use leading zeros (e.g., 1-visual-analytics.md01-visual-analytics.md through 09-...md) so that 10-...md correctly follows 09-...md.

Issue resolved by this PR (if any)

  • Issue Number: N/A
  • Link: N/A

Type of change (Check all that apply)

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update
  • Other: Creation of new example workflows

Parts of Curio impacted by this PR:

  • Frontend
  • Backend
  • Sandbox

Testing

  • Unit Tests
  • Manual Testing (please provide details below)

For each new example dataflow tutorial, I manually loaded the corresponding json dataflow file into a running Curio instance. I executed each node, from data loading to final visualization, verifying that each node runs without errors. I confirmed that the outputs match the descriptions, images, and animations provided in the Markdown tutorials.

Screenshots (if relevant)

Checklist (Check all that apply)

  • I have manually loaded each .json test from the tests/ folder into Curio, ran all the nodes one by one, and checked that they run without errors and give the expected results
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

I did not make any changes that affect or add functionality, so some of the above do not apply.

@fabio-miranda fabio-miranda merged commit b5aa115 into urban-toolkit:main Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0