hvvka / page-replacement Goto Github PK

• PEP-8 variable/function/class compliance
• Adding function/class documentation
• Python 3 compliance checking
• Algorithm verification (if implemented properly)
• OPT algorithm project documentation (latex)

• Add type suggestions.
• Reorder methods to be top-down.
• Manage useless comments and docstrings.
• Verify implementation with literature.

• Implement helper methods to map page_table.
• LRU test.
• Clock test.

python 3.6.x

• PEP-8 variable/function/class compliance.
• Add function/class documentation.
• Python 3 compliance checking.
• Algorithm verification. Is it implemented properly? Write unit tests.
• Aging algorithm Latex documentation.

• Generate trace data.
• First 20 bits should be limited from 0 to X. Note: chose X=2
• Last 12 bits can be random <0, F>.
• Parametrize number of lines. Note: --pages=< file size in lines >
• Investigate upper bound (X): parse swim.trace and gcc.trace to see how many pages are repeated.
• Remove old trace files from project.

• Bash script for running trace generation and invoking algorithms.
• Prepare XLSX file with serialized results for traces: 100000, 250000 and 500000 and (for each) frames: 16, 32, 64.
• Create charts out of it.

Don't use print anymore.

All the messages should be logged.
Printing during algorithm execution should have level debug.

• useless comments deleting
• exception handling while file opening

• Implement helper methods to map page_table.
• Aging test.
• OPT test.

https://www.overleaf.com/project/5bc346d271944f6a1987f69c

TODO
\section:

• 3. Projekt aplikacji (wstęp) @zxxa
• 3.3 Koncepcja działania algorytmów (wstęp) @hvvka
• 3.5 Struktura danych wejściowych @zxxa
• 4.1.3 CircularQueue
• 4.3 Metoda odczytu danych wejściowych @zxxa
• 5.2 Analiza wykonania algorytmów @hvvka
• 5.3 Wnioski z testów i badań @hvvka
• 6. Podsumowanie @zxxa
• 5.1.2 Opis testów unittests (jeden przykładowy) @hvvka

ogólne:

• nie wklejać kodu do punktów – czytać z pliku @zxxa

nowe:

• dodać nowe template @zxxa
• podpisać listingi kodu @hvvka
• poprawić podpisy tabel/obrazków @hvvka

When we got algorithms results in vmsim.py, then

• serialize them into separate CSV files.

Generally, taking input from user doesn't work correctly (at least for MacOS). Input args are read in wrong order and sometimes evaluated to None (even though they were provided).

The method should be either fixed, or simply changed to some nice wrapper.

• PEP-8 variable/function/class compliance.
• Add function/class documentation.
• Python 3 compliance checking.
• Algorithm verification. Is it implemented properly? Write unit tests.
• LRU algorithm Latex documentation.

• Boolean parameter in algorithms' constructor
• Method for getting page_table state (with info about hits, evict etc.)

• PEP-8 variable/function/class compliance.
• Add function/class documentation.
• Python 3 compliance checking.
• Algorithm verification. Is it implemented properly? Write unit tests.
• OPT algorithm Latex documentation.

At the very end:

• Copy and translate most important parts from latex documentation (would be nice to have charts) to README.
• Translate report from latex to markdown.
• Add report to wiki page.

• PEP-8 variable/function/class compliance.
• Add function/class documentation.
• Python 3 compliance checking.
• Clock algorithm Latex documentation.