This week I researched backend alternatives to Parse and concluded that, for the purpose of my project, Parse is the best solution despite its lack of existence within the next year or so. Therefore, I added back the Parse support so that calendar events are created, added to the EventGraph to make predictions, and stored on a remote server. I also made a number of changes to my event simulator and added it to the application (exclusively to show how I've been conducting my simulations). I still have some changes to make on the prediction algorithm, as I have not touched it since my last check in, but these updates will allow me to start testing the algorithm in the real world rather than via simulation soon. Notable files include CalendarEvent.java and EventSimulator.java.
@poorvi-vora
This week I researched backend alternatives to Parse and concluded that, for the purpose of my project, Parse is the best solution despite its lack of existence within the next year or so. Therefore, I added back the Parse support so that calendar events are created, added to the EventGraph to make predictions, and stored on a remote server. I also made a number of changes to my event simulator and added it to the application (exclusively to show how I've been conducting my simulations). I still have some changes to make on the prediction algorithm, as I have not touched it since my last check in, but these updates will allow me to start testing the algorithm in the real world rather than via simulation soon. Notable files include CalendarEvent.java and EventSimulator.java.