As we entered June, the Maeumjigi team completed the major developments of the 1st semester Capstone project and focused entirely on building safety nets and preparing for the final presentation.
In the final week of May (27th-30th), we dedicated our efforts to wrapping up the results of the highly anticipated 4th Fine-Tuning (fine_tuning_4) and solidifying the system's framework.
On May 21st and 22nd, the Maeumjigi Capstone team embarked on massive data generation and preparation for the 4th Fine-Tuning (fine_tuning_4).
Over the two days of May 19th and 20th, the automation of evaluation for the 3rd fine-tuning (fine_tuning_3) and the enhancement of backend/frontend features for building the actual app service proceeded in parallel.
I must correct my previous assumption that "May 13th was the last of Maeumjigi's May development"! On May 17th, a massive wave of backend integration testing and report drafting hit us.
On May 13th, after fixing the hardcoding bugs discovered yesterday, we finally resumed proper inference testing for the 2nd round fine-tuned models.
The 2nd round of fine-tuning (fine_tuning_2) parallel training, which was ambitiously started to correct the LoRA hyperparameter mistake (alpha/rank setup error), finally ended on May 12th!
May 8th was the day we were building our capstone design mid-term presentation (PPT) based on the fine-tuning results. However, while happily filling in the slides, I discovered a massive, chilling mistake.
May 7th was the day we synthesized the fine-tuning results of our 5 models (Llama3.3-70B, DSR1-70B, HCX-Omni-8B, Qwen35-9B, HCX-Text-1.5B) and proceeded with full-scale visualization and local environment setup.
On May 6th, we finally escaped the long swamp of fine-tuning! After several nights of work and hyperparameter tuning, the training for mid-size models like HCX-Omni-8B and Qwen35-9B was successfully completed.
After experiencing the OOM (Out of Memory) hell during the fine-tuning of massive 70B models, on May 4th, we attempted a bold change in strategy. By drastically reducing the batch size, we barely managed to push the 70B models (Llama3.3, DeepSeek-R1) to checkpoint-1200 and 1300, but the training time was absurdly long, resulting in terrible efficiency.
On May 3, having gained enough experience with the 8B models, our team finally challenged the ultimate kings of performance: fine-tuning massive 70B (70 billion parameters) models. We attempted to train both Llama 3.3 70B and DeepSeek-R1 70B, but as expected, we hit a massive hardware resource wall.
April 19 is the day we evaluated the performance of the model (M6) trained on the virtual synthetic dataset (v5) we painstakingly created, and wrote the 7th-week weekly report based on it. Was the data we generated while enduring a $10 bill bomb worth it?
April 14 is the day we resumed the synthetic data (v5) generation work, which had been temporarily halted since the bill bomb incident. We increased the API billing limit (lifted the restriction) and ran the system, but once again, it didn't go smoothly.
On April 9, using the Colab notebook we ambitiously completed yesterday, we finally attempted the first training (fine-tuning) of our artificial intelligence model (Llama 3.1). However, reality was not that easy, and we had to face numerous errors. It was also a tough day as we had to simultaneously create the presentation materials for the 6th week of the Capstone Design project.
April 8th was the day we experienced the biggest crisis and a 'laugh-and-cry' happening while working on the Maeumjigi project. It was the Claude API monthly limit exceeded & bill bomb incident.
April 7 was the day we attempted integration by running the frontend code built by a teammate in a local environment, and also the day we launched a massive script using Artificial Intelligence (AI) to 'synthesize' 60,000 new counseling data points to fill our dataset gaps.
April 5th marks the day we wrapped up the arduous data preprocessing journey (v1~v4) by generating a final report, while simultaneously kicking off the frontend project that will become the face of the Maeumjigi web service.
This is the record of April 3, the day we began in earnest the task of refining the training conversation data to feed into the deep learning model (Llama 3.1). It was also the day we ran a massive pipeline that makes the Artificial Intelligence (AI) read the text and judge the emotion on its own, going beyond simple data merging.
This is the record of April 1, when we began processing a massive amount of conversation data into a format suitable for training the Llama 3.1 model, which will become the core engine of the Maeumjigi project.
This is the record of March 31, when we conducted the Android build test of the MND Convention reservation alarm app, which was the initial direction of the Maeumjigi project, while simultaneously starting the Llama 3.1 fine-tuning data preprocessing, hinting at a full transition into an AI-based project.
This is the record of March 30, when we officially started developing the 'MND Convention Reservation Alarm' application, which was the initial idea for the Maeumjigi project. Based on the coding rules we set last time, we established a detailed project plan and laid the foundation for Test-Driven Development (TDD).
This is the record of March 26, 2026, the very first day of the grand journey of the "Maeumjigi" capstone project. At that time, instead of the current AI-based "Maeumjigi", the project took its first steps simply as an Android alarm application.