Week 8: Updates and Reevaluation
Adam P -
Welcome back once more, my loyal followers. I have continued to code my refinement algorithm over this past week. It’s taking me a long time to code it, with this project proving to be more work than I anticipated, so it’s now that I’m deciding I will not be able to complete the website during the duration of the Senior Project. I will be focusing my efforts exclusively on coding my algorithm to fulfill its basic purposes. I still fully intend to complete the website once I’m finished with the algorithm, but it will not be within the confines of this project. I am sorry to any out there who may have been looking forward to testing out my website, but the wait will be a little longer.
Mainly what I’ve been working on this week was simplifying how the program took commands so that it would be easier and quicker for me to test and troubleshoot it. I am recoding how user input is processed so that one command is capable of creating a new event, naming this event, linking it to other events and specifying the link type and value, and establishing a character’s presence at said event at a certain age. This will be far easier compared to when I was sending 4 commands to accomplish the same task. I use a modifier called “.split()” to break up the user input in order to read all the different arguments, like the new event’s name, its constraints (like if it could only occur in 2025), its linked events, and its present characters with their ages. At present, the structure of the command is as follows: add event <name> <constraint_type: value> <link_type: target_event: value> <character_name: age>. The “value” simply represents the quantity describing a link. So if I were to link an event called “submitting blog post” to another event “birth of Adam” with the link type of “birth” and a value of 18, that would mean that “submitting blog post” takes place at least 18 years after “birth of Adam.”
I’m also trying to work out the logic for reprocessing every event that’s already been added to a test case once a new one gets added. This needs to be done in order for refinements to be made when events are linked. That’s all for this week, folks. See you next time.
Comments:
All viewpoints are welcome but profane, threatening, disrespectful, or harassing comments will not be tolerated and are subject to moderation up to, and including, full deletion.