Skip to content

Commit

Permalink
Update project report link
Browse files Browse the repository at this point in the history
  • Loading branch information
wulffern committed Apr 28, 2024
1 parent f02d869 commit 8f477a6
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions lectures/lp_project_report.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ link here.


| **Item** | **Description** | **OK** |
|:----------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:------|
|:-----------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------|
| Is the problem description clearly defined? | Describe which parts of the problem you chose to focus on. The problem description should match the results you've achieved. | |
| Is there a clear explanation why the problem is worth solving? | The reader might need help to understand why the problem is interesting | |
| Is status of state-of-the-art clearly explained? | You should make sure that you know what others have done for the same problem. Check IEEEXplore. Provide summary and references. Explain how your problem or solution is different | |
Expand All @@ -215,6 +215,6 @@ link here.
| Chronology | Don't let the report follow the timeline of the work done. What I mean by that is don't write "first I did this, then I spent huge amount of time on this, then I did that". No one cares what the timeline was. The report does not need to follow the same timeline as the actual work. | |
| Too much time | How much time you spent on something should not be correlated to how much text there is in the report. No one cares how much time you spent on something. The report is about why, how, what and does it work. | |
| Length | A report should be concise. Only include what is necessary, but no more. Shorter is almost always better than longer. | |
| Template | Use <https://github.com/wulffern/dic2021/tree/main/2021-10-19_project_report> template for the report. Write in LaTeX. You will need LaTeX for your project and master thesis. Use <http://overleaf.com> if you're uncomfortable with local text editors and LaTeX. | |
| Template | Use [IEEEtran.cls](https://ewh.ieee.org/conf/ijcnn/2003/IEEEtran.cls). Example can be seen from an old version of this document at <https://github.com/wulffern/dic2021/tree/main/2021-10-19_project_report>. Write in LaTeX. You will need LaTeX for your project and master thesis. Use <http://overleaf.com> if you're uncomfortable with local text editors and LaTeX. | |
| Spellcheck | Always use a spellchecker. Misspelled words are annoying, and may change content and context (peaked versus piqued) | |

4 changes: 2 additions & 2 deletions pdf/version.tex
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
{\noindent Built on Fri Apr 26 10:08:22 CEST 2024} \\
{\noindent from 7df29f8ecf9b6706a35acbda9223e1c184e50e84}
{\noindent Built on Fri Apr 26 15:16:02 CEST 2024} \\
{\noindent from f23eabbf613d503af6e657ca8f7267c506bc4913}

0 comments on commit 8f477a6

Please sign in to comment.