Created on 11th February 2024
•
Finding the perfect accommodation for your long-awaited vacation can be a difficult and risky challenge. Some of the primary problems with the current system are,
We solve these problems by implementing and giving the following features,
The biggest challenge was to learn all of the different frameworks and tools that we needed to implement the desired features. In particular, learning data manipulation with Qdrant and integrating the backend features with Streamlit was particularly time-consuming. Qdrant was used to create our personalized vector dataset, data processing, and addressing the hotel reviews through sentimental analysis. Much of our time was spent cleaning the data into leaving with only the ones that would benefit with the model’s recommendation. In addition, some parts of the data were either missing or casted with the wrong type, leading to issues in implementing what was originally considered straightforward functions. With such a small detail being so easy to glance over, we spent much of our time debugging edge cases which took away time to develop the important features of our model.
Streamlit allowed for us to create session states, which allows for variables to be shared throughout (re)runs and user sessions. In our case we used a decoder model to generate explanations for each of the hotels we chose. To make the generated text persistent, we had to create multiple session states for each of our hotels and save the explanations generated in them which were later retrieved in app reruns.
While developing, we also noticed the very prevalent slow run times while trying to check the performance of our model. OpenAI API and Ares API took time to generate due to their large traffic. Being on a limited token usage for both of our API proved to be fairly nerve-wracking as well, especially knowing that we can only test our model a limited number of times. Regardless, our team did our best to persevere through the difficulties.
Tracks Applied (1)
traversaal.ai