Guide-yakabatana mibvunzo · Pakati Nhanho
Structuring a Machine Learning Project Quiz
Organize ML code, data references, notebooks, tests, configuration and artifacts around a reproducible team workflow. for collaborators.
Mubvunzo 1 ye 8
Chii chinofanira purojekiti README kubatsira mubatsiri mutsva kunzwisisa?
Tarisa mubvunzo wese8 mibvunzo
Mhinduro uye tsananguro zvinoonekwa paunenge uchitora bvunzo.
- Chii chinofanira purojekiti README kubatsira mubatsiri mutsva kunzwisisa?
- Production credentials for every collaborator
- Every hyperparameter before defining a task
- Data access, workflow commands, prerequisites and limitations
- A guarantee that evaluation results will be accurate
- Sei uchiparadzanisa kodhi inogona kushandiswazve kubva kumabhuku ekuongorora?
- It prevents tests from importing shared transformations
- It lets scripts, tests and notebooks share one implementation
- It requires separate code copies for each notebook
- It forces notebooks to execute cells in order
- Maseti edata akajeka kana akawanda anofanirwa kubatwa sei?
- Commit every copy to the repository
- Store access tokens beside the raw data
- Replace data governance with folder names
- Use controlled storage and versioned references rather than blindly committing them to Git
- Ndekupi kunofanirwa kuchengetwa ma paramita anosiyana pane anomhanya?
- Parameters that vary between runs without editing core logic
- Source constants manually rewritten for every run
- Notebook output text from a previous experiment
- Serialized predictions from the last model
- Chii mutsauko pakati pembishi uye yakagadziriswa data rutsigiro?
- Guaranteeing the model is unbiased
- Eliminating data versioning
- Tracing transformations and rerunning preprocessing
- Storing only final predictions
- Why should generated artifacts have a clear storage policy?
- They are always safe to commit
- They can be large, sensitive or needed to reproduce results
- They replace source code
- They automatically contain the project license
- How should a team treat a project template such as Cookiecutter Data Science?
- Copy every folder even when unused
- Treat its layout as a legal requirement
- Use it instead of tests
- Use it as a starting convention and adapt it to the workflow
- Which automated check would catch a feature transform changing its expected columns or missing-value behavior?
- A test for expected columns and missing-value cases
- A linter checking code style
- A type annotation on the function signature
- A README description of the transform