Skip to content
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

Executable tutorial submission #2686

Closed
wants to merge 24 commits into from
Closed

Executable tutorial submission #2686

wants to merge 24 commits into from

Conversation

kthfre
Copy link
Contributor

@kthfre kthfre commented Oct 18, 2024

Assignment Proposal

Title

End-to-end training of a neural network to deployment in a live application

Names and KTH ID

Deadline

  • Task 2

Category

  • Executable tutorial

Description

I'd like to make an executable tutorial that goes through the training of a neural network in a Jupyter notebook on Colab, handling the intermediary steps, and deployment to some live application, so the end-to-end process. I'd put limited focus on the ML aspects and greater focus on the DevOps aspects. I'd like to whip together my own functionality for the DevOps parts, if I may, as it's a fun learning experience and could be meaningful scripts for future usage. The deployment criteria for the model could be to exceed previous test data accuracy, but there could also be any other reasonable criteria. I haven't fully decided on the functionality for the MLops/DevOps part. The bare minimum is actually deploying the model live when fulfilling the criteria. Other things being considered are model storage/rollback, job scheduling/queue in running notebooks, monitoring of multiple notebooks, etc.

Architecture wise there would be:

  • The Colab notebook running the ML stuff (and some network connectivity).
  • An MLops tool consisting of a backend and a corresponding GUI (web).
  • A demo web application that uses the model on the backend.

I asked TA about this briefly in a lab session (not previous, but one before that) and it sounded OK. I meant to register it earlier, but other coursework came in between. I think it's still OK to register an MLops task since it's asynchronous and there is no "week" folder structure in the directory tree. So if it is, and the proposal sounds OK, is all I have to do commit to a deadline and deliver?

Relevance

Jupyter Notebook/Lab is often used for processing, preparing, and visualizing data, as well as subsequently training machine learning models. The process of deriving a model is often an iterative process to determine suitable model architectures and optimal hyperparameters. Models may furthermore require continuous altering after deployment as more data becomes available or use cases change. This process is presumably often done manually, particularly as data scientists and conventional developers may be different teams, but there are clear benefits in automating the process.

Submission

Github repository

@algomaster99
Copy link
Collaborator

@kthfre there are some conflicts here. Always create a new branch from the default branch and create a PR using that.

@algomaster99 algomaster99 self-assigned this Oct 18, 2024
@sofiabobadilla sofiabobadilla self-assigned this Oct 21, 2024
@sofiabobadilla
Copy link
Collaborator

@kthfre
Your PR is also adding a feedback task.
Please fix this so you only modify the executable tutorial README

@kthfre
Copy link
Contributor Author

kthfre commented Oct 22, 2024

@algomaster99 @sofiabobadilla sorry this is fixed. Does the feedback assignment require a submission PR as well or is it enough to reply to PR giving feedback to with the actual feedback?

@algomaster99
Copy link
Collaborator

Does the feedback assignment require a submission PR as well or is it enough to reply to PR giving feedback to with the actual feedback?

Yes. Feeback requires a proposal PR (see #2676). And then you can add another PR editing the proposal to have a link to the feedback comment.

@algomaster99
Copy link
Collaborator

sorry this is fixed.

It is still not fixed. I can see 2 file changes above.

@algomaster99
Copy link
Collaborator

@kthfre one way to fix it would be to run git pull <main repository remote name> 2024 --rebase and then git push <your remote name> 2024 --force.

@algomaster99
Copy link
Collaborator

It seems the that the GitHub link has already been submitted. https://github.com/KTH/devops-course/tree/2024/contributions/executable-tutorial/golman

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.

3 participants