From 2fb89c607cb39611d4f3774d3b7231f1ec944b2e Mon Sep 17 00:00:00 2001 From: Braeden Sowinski Date: Fri, 8 Apr 2022 13:45:10 -0700 Subject: [PATCH] Update README.md --- test/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/test/README.md b/test/README.md index 1b0dd8b..d520896 100644 --- a/test/README.md +++ b/test/README.md @@ -4,4 +4,10 @@ If you're looking in here, I know this codespace is a mess, I didn't think I wou But to be fair, I think a problem as complex as schedule generation should be seen. Currently the tests are being run in python since it is a lot easier for me to quickly test and edit the algorithm. Once I get the algorithm complete, I plan on rewriting it in GoLang, using the python -script as a reference. \ No newline at end of file +script as a reference. + +Hello again! If you're reading this part, again ingore the awful codespace, but `generateScheduleV3` +in `tinker.py` is the best one yet. It uses real sample data from my school in 2018. This puts the +algorithm through the realistic obstacles it may face. It uses a different approach that you can read +about in `tinker.py` about the function. Hopefully this will get a larger success rate than the previous +versions!