Skip to content

Commit 39b5fa0

Browse files
committed
small additions
1 parent dad291e commit 39b5fa0

File tree

3 files changed

+5
-4
lines changed

3 files changed

+5
-4
lines changed

_site/assets/js/search-data.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@
204204
},"29": {
205205
"doc": "Project 3",
206206
"title": "Deliverables and Rubrics",
207-
"content": "Your final delivarable should be a Replication Report following the I4R framework. It should be submitted as a PDF, typed up in LaTeX (Chat-GPT can be really helpful for this). Please use the LaTeX template attached. Read the replicaton report template carefully as it contains all the information you need to pursue for a successful replication. Knowing LaTeX is a super-power and makes your work look really pretty! . In addition, you should submit a well-organized, compressed (.zip) folder that contains a Jupyter notebook and all the data used. We should be able to replicate your work by running the notebook locally on our computers. Here is the list of deliverables and the grading rubrics. See the replication report for more details. Deliverables . Replication Report (50%) . | Deliverable | Points | . | Abstract | 5% | . | Introduction | 5% | . | Reproducibility | 5% | . | Replication | 25% | . | Conclusion | 5% | . | Clarity, Style and Presentation | 5% | . Code & Analysis (50%) . | Deliverable | Points | . | Checkpoint (see details below) | 15% | . | Data Cleaning & Pre-Processing | 5% | . | Modeling (regressions) | 10% | . | Visualizations (figures, tables) | 15% | . | Clarity, Style and Presentation | 5% | . Grading Rubrics . For each deliverable, we will award points according to the following percentage scale: . | Grade | Description | . | Excellent (above 90%) | Work that is free of all but the most minor errors and demonstrates creativity and/or a very deep understanding of what you are doing. | . | Good (80-90%) | Work that is free of fundamental errors and demonstrates a basic understanding of what you’re doing. | . | Fair (60-80%) | Work with fundamental errors in analysis and/or conveys a lack of understanding of the basics of the work you are attempting to do. | . | Lacking (below 60%) | Work that is severely lacking or incomplete. | . ",
207+
"content": "Your final delivarable should be a Replication Report following the I4R framework. It should be submitted as a PDF, typed up in LaTeX (Chat-GPT can be really helpful for this). Please use the LaTeX template attached. Read the replicaton report template carefully as it contains all the information you need to pursue for a successful replication. Knowing LaTeX is a super-power and makes your work look really pretty! . Past replication reports have taken 10-15 pages, although we will not be checking the page count very carefully. That being said, please be concise in your work. Writing more information than necessary often comes at the cost of clarity. Your communication and presentation is very important for a replication exercise. In addition, you should submit a well-organized, compressed (.zip) folder that contains a Jupyter notebook and all the data used. We should be able to replicate your work by running the notebook locally on our computers. Here is the list of deliverables and the grading rubrics. See the replication report for more details. Deliverables . Replication Report (50%) . | Deliverable | Points | . | Abstract | 5% | . | Introduction | 5% | . | Reproducibility | 5% | . | Replication | 25% | . | Conclusion | 5% | . | Clarity, Style and Presentation | 5% | . Code & Analysis (50%) . | Deliverable | Points | . | Checkpoint (see details below) | 15% | . | Data Cleaning & Pre-Processing | 5% | . | Modeling (regressions) | 10% | . | Visualizations (figures, tables) | 15% | . | Clarity, Style and Presentation | 5% | . Grading Rubrics . For each deliverable, we will award points according to the following percentage scale: . | Grade | Description | . | Excellent (above 90%) | Work that is free of all but the most minor errors and demonstrates creativity and/or a very deep understanding of what you are doing. | . | Good (80-90%) | Work that is free of fundamental errors and demonstrates a basic understanding of what you’re doing. | . | Fair (60-80%) | Work with fundamental errors in analysis and/or conveys a lack of understanding of the basics of the work you are attempting to do. | . | Lacking (below 60%) | Work that is severely lacking or incomplete. | . ",
208208
"url": "/sp24/proj3/#deliverables-and-rubrics",
209209

210210
"relUrl": "/proj3/#deliverables-and-rubrics"
@@ -218,7 +218,7 @@
218218
},"31": {
219219
"doc": "Project 3",
220220
"title": "Submission Checklists",
221-
"content": "Checkpoint (due Friday, April 12, 2024) . This will be a separate gradescope assignment that will be due earlier. There is no need to submit any code, a write-up of your progress so far (preferably in LaTeX) will suffice. You must include: . | Group composition (names and assigned responsibilities). | Chosen paper. | Screenshots of the project code organization (including any relevant data/notebook/code). | Screenshots of LaTeX project in Overleaf following the I4R template. | A description of what you have attempted to do so far. | A summary of what’s going well and what you are struggling with. | A note on how course staff may help you succeed. | . Project (due Friday, April 26, 2024) . | A PDF of the Replication Report (submitted to the project 3 written assignment on Gradescope) | A PDF file of the Jupyter Notebook containing all the analysis (submitted to the project 3 written assignment on Gradescope) | A well-organized compressed (.zip) file containing: (submitted to the project 3 coding assignment on Gradescope) . | A Jupyter Notebook that can easily be run to replicate all your results | All datasets that you downloaded and used in the notebook | Figures and Plots (if not already included in the report or notebook) | . | . ",
221+
"content": "Checkpoint (due Friday, April 12, 2024) . This will be a separate gradescope assignment that will be due earlier. There is no need to submit any code, a write-up of your progress so far (preferably in LaTeX) will suffice. Everything must be submitted as a pdf, although it’s fine if this pdf is not written in LaTeX (but the final submission must be written in LaTeX). You must include: . | Group composition (names and assigned responsibilities). | Chosen paper. | Screenshots of the project code organization (including any relevant data/notebook/code). | Screenshots of LaTeX project in Overleaf following the I4R template. | A description of what you have attempted to do so far. | A summary of what’s going well and what you are struggling with. | A note on how course staff may help you succeed. | . Project (due Friday, April 26, 2024) . | A PDF of the Replication Report (submitted to the project 3 written assignment on Gradescope) | A PDF file of the Jupyter Notebook containing all the analysis (submitted to the project 3 written assignment on Gradescope) | A well-organized compressed (.zip) file containing: (submitted to the project 3 coding assignment on Gradescope) . | A Jupyter Notebook that can easily be run to replicate all your results | All datasets that you downloaded and used in the notebook | Figures and Plots (if not already included in the report or notebook) | . | . ",
222222
"url": "/sp24/proj3/#submission-checklists",
223223

224224
"relUrl": "/proj3/#submission-checklists"

0 commit comments

Comments
 (0)