Pipeline

Overall goal

Now that you have attempted the image basics exercise, this next one is meant to provide some deeper exposure to the code base and the registration pipeline.

Getting started

GitHub Classroom is no longer used. Start by opening the pipeline starter repository, selecting Fork, and creating the fork under your own GitHub account.

Clone your fork and start working on it. The process is the same as earlier: make changes to the pipeline.py script and run the tests in test_pipeline.py. Once the tests pass locally, commit and push your changes to your fork so that GitHub Actions can run the tests there.

Work in your own fork, not in the ubern-mialab starter repository. If GitHub displays a 404 page, contact a teaching assistant to request access before forking. If GitHub asks you to enable workflows in your fork, open the Actions tab and enable them.

GitHub runs its 'actions' behind the scenes, and you'll either see a red ❌ or a green ✅ next to the commit message you entered previously.

The goal really is to get the green ✅ every time you make a change, which will only happen when all the functions are completed correctly (correctly as defined by the tests in test_pipeline.py). Clicking on the check mark will show more details about completion of the homework.

Once you're done, please share both the link to your fork and the URL or SHA of your final commit with us on Slack, so we can confirm you've completed the assignment for the bonus grade (if such a need arises).

If you have any trouble, please do not hesitate to reach out to your friendly neighborhood TAs on Slack.