mirror of
https://github.com/kuhyx/WUT_Computer_Science.git
synced 2026-11-11 18:53:53 +01:00
Krzysztof kuhy Rudnicki
ffa5dad02a
The 250-line cap applies to prose too, and the reports were the worst
offenders -- ENUME's projectA.tex alone was 1,876 lines. Each is now a
preamble plus one \input{} per section, which is how a long LaTeX document is
normally organised; not one byte of prose was rewritten.
"The PDF is unchanged" is checked by a script rather than by eye, because
hashing the PDF cannot work: pdflatex stamps a /CreationDate and an /ID into
every build, so two runs of the SAME source already differ. tex_fingerprint.sh
compares what a reader sees instead -- page count plus a hash of the extracted
text -- and it is stable across rebuilds of untouched sources, which is the
property that makes it usable as a gate.
It earned its keep immediately. Both ECOTE reports quote an example LaTeX
document inside an lstlisting block, so \end{document} appears in the middle
of the file; splitting on the FIRST one stranded everything after it. Same
page count, different text, caught automatically. EOPSY lab3 exposed a second
bug: a \section{} title that runs onto the next line.
Result: 19 .tex over the cap -> 1. The survivor,
ELAC/.../03-building-nfa-...tex, is 418 lines of consecutive tikz figures
with no subsection to split on and needs a hand-placed boundary.
Verified: 29 splits across two passes (section, then subsection for the
pieces still over), every one reporting `unchanged` from
scripts/tex_fingerprint.sh --check.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172dj34FDpao6wsix8ZuCzE
17 lines
933 B
TeX
17 lines
933 B
TeX
\section{Finishing comments}
|
|
Both by looking at the source code and simulation results we can say that the
|
|
simulation uses First in First out algorithm. First 8 pages were mapped
|
|
correctly because of the memory.conf file, pages up to 32 were mapped correctly
|
|
because they are mapped by default by the application. \\
|
|
Then we got page faults which were resolved by first in first out algorithm.
|
|
\begin{thebibliography}{9}
|
|
\bibitem{mmuWiki} \href{https://en.wikipedia.org/wiki/Memory_management_unit}{Wiki Memory Management Unit}
|
|
\bibitem{faultWiki} \href{https://en.wikipedia.org/wiki/Page_fault}{[Wiki Page Fault]}
|
|
\bibitem{Page Replacement Algorithms}
|
|
\href{https://www.geeksforgeeks.org/page-replacement-algorithms-in-operating-systems/}{[Geeks
|
|
for Geeks page replacament algorithms]}
|
|
\bibitem{pageWiki}
|
|
\href{https://en.wikipedia.org/wiki/Page_replacement_algorithm}{Wikipedia Page
|
|
replacament algorithm}
|
|
\end{thebibliography}
|