Formal implementation and case studies for the Advanced Algorithms course.
You can see in detail the section's structure in the table of contents of the pdf. More formally: - \section{Problem title} - Informal description of the problem. - Link to the pdf description, footnotes would be best. - \subsection{Solution name} - Informal description of the solution.
You are free to describe your algorithm as you want, but in order for it to be easily understandable take care to be formal and include pseudo-code and use case examples. A detailed description of the computational classes and memory cost can help greatly. You can add any credits you deem necessary, and link to your implementation, if you like.
The following style guide shall be followed:
-
Sections: New sections should go in a new page, with two blank lines over in the .tex file, and one before the following .tex.
-
Subsections: New subsections and subsubsections should have one blank line right after them.
-
Line limit: Try to stay under the 120 characters per line, break over the 120 and after you end a sentence.
-
Indentation: 4 spaces.
-
Packages: Included at the start of the document, add a brief description and try to indent them as the previous ones.
-
Computational cost: You should add it in a hbox like this:
\begin{framed} \noindent \textbf{Computational cost}: $O(m + MAX\_TIME)$. \end{framed}
New solutions can be submitted through pull requests. No new branches will be added. If you are not familiar with them, you can find an in-depth description here.
If you find any problem in the solutions or any other detail, please use the repository's Issues section.
I'm using slack to organize, if you want to synchronize our efforts, you should find the team at unipi-inf-lm.slack.com