Skip to content

Kl/scrum 36 chats#51

Merged
kevin-lann merged 33 commits intodevelopfrom
kl/scrum-36-chats
Mar 7, 2025
Merged

Kl/scrum 36 chats#51
kevin-lann merged 33 commits intodevelopfrom
kl/scrum-36-chats

Conversation

@kevin-lann
Copy link
Contributor

@kevin-lann kevin-lann commented Mar 6, 2025

Description

This PR is for three tickets:
SCRUM-30
SCRUM-36
SCRUM-37

This PR Includes:

  • Chats are now saved for each user
  • Copy, Delete chats
  • Chat name automatically generated by AI
  • Chatbot now answers questions about program requirements

Type of change

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings

kevin-lann and others added 28 commits February 21, 2025 16:17
@minhhaitran08
Copy link
Contributor

minhhaitran08 commented Mar 6, 2025

The chat bot is returning information as expected.
But for the chat log manipulation:

  • I haven't been able to create a new chat thus can't test the delete chat log function. When I click on the New Threat button nothing happen.
  • My chat log still only have the default name: New Thread.
  • When I reload the page or move to a different tab (Timetable Builder or My Timetable) the chat page is reset and everything is deleted.
  • I can copy Morpheus answer into my clip board
  • I can edit my message

@thomasyzy7
Copy link
Contributor

thomasyzy7 commented Mar 6, 2025

Program requirement is well done!

Some of the aspects that worked flawlessly:

  • Describing what each breath requirements are
  • Fetching courses from a particular breath requirement
  • Fetching courses with no prerequisities and has a particular breath requirement.
  • Asking for program requirements for a specific program
  • Asking for all of the CMS streams.
  • Describing the courses mentioned in the programs

Things that I think should be worked on:

  • The title is oftertimes too lengthy, often going out of bounds and there is currently no way right now to access the full title. (we can fix this by revealing the title when hovered, like ChatGPT).
  • when switching between different chatlogs, if both chatlogs require scrolling, then when switching, there is a brief flash containing messages from the top of the chatlog before switching to more recent entries. Below is a video demonstrating this phonemona:
2025-03-06.16-46-26.mov

More AI focused issues:

  • Trouble fetching lecture + tutorial times for particular courses, I tried asking for cscc01 lectures and tutorials and sometimes information is missing, sometimes it is made up.

Copy link
Contributor

@MasahisaSekita MasahisaSekita left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI chatbot seems functional and the UI is working properly. Everything seems good.

@thomasyzy7
Copy link
Contributor

a level course refers to first year courses, and vice versa
b level course refers to second year courses, and vice versa
c level course refers to third year courses, and vice versa
d level coures refers to 4th year courses, and vice versa

Currently there is issues when asking for letter level courese (A level for example).

Above is a context that seemed to work.
Here are some of the working test cases:

provide me 5 b level courses and 1 c level courses
give me all of the b level courses from the information stream of cs

Here are some of the cases that didn't work (data is extremely inconsistent, the AI kept on changing answers when I switched chatlogs):
image
image
image

@kevin-lann kevin-lann merged commit 46f0384 into develop Mar 7, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants