We are at the close of Week 10, and it’s been all about laying the groundwork. We’ve taken a deep dive into the concept design, mapping out the architecture of our system and pinpointing exactly what we want to achieve with our prototype. This week was the planning phase.

Through brainstorming sessions and collaborative discussions, we’ve set the stage for what’s to come. We’ve outlined a robust plan for a prototype that not only works but also provides a diverse range of options for users, giving us a solid base to build upon.

Next week, we’re moving from the drawing board to the field. Our aim is to bring to life a working prototype with at least five options for the user, setting a strong foundation for when we scale up to over 100 choices. This transition from planning to implementation is where the magic begins, where we start to see our project breathe and take shape.

It’s time to roll up our sleeves even higher and turn these well-laid plans into action. Let’s make this prototype a reality and witness the first true spark of life in our project.

This week, we took a deep dive into the heart of our project—optimizing the algorithm. It’s not just about cranking up the efficiency; we’re also expanding the horizon to include a wider array of choices. The end goal? To ensure that the advice we provide to the end user isn’t just good—it’s the best we can possibly offer.

As we brainstormed, it became clear that further research is crucial, particularly in the realm of Unity and how we can leverage its capabilities. Our Blackjack example has laid a strong foundation, and it’s time we built upon it.

In the coming week, we are focused on enhancing our understanding of Unity’s environment. This isn’t just about technical finesse; it’s about ensuring our end product truly resonates with the users’ needs. So, we are gearing up for another week of research, development, and innovation.

Week 8 was very eventful! Our PDR presentation at CAE USA in Tampa went off without a hitch. And that facility tour? Talk about getting a firsthand look into what makes CAE tick. The depth of their operations is genuinely remarkable.

As we step into our next tasks, we’re setting our sights on expanding the scale of our algorithm implementation. It’s a hefty task, and given its magnitude, a revisit to some of our timelines might be in order.

Speaking of alignment, we have our usual weekly catch-up with CAE this week. This will make sure they’re on board and in sync with any new objectives and adjustments we’re contemplating. Keeping them in the loop is key.

Week 5 has been a hallmark of collaborative learning! We joined forces with the Champs team and stepped up our game by getting Six Sigma White Belt certified. It’s amazing to see how processes and organized collaboration can significantly amp up efficiency and success.

This week’s journey into the principles of Six Sigma opened our eyes to the critical role that structured processes play in our daily operations. We’re not just creating software; we’re crafting a well-oiled machine that thrives on meticulous organization and seamless teamwork.

As we gear up for Week 6, our mission is to channel these new insights into our algorithm. We’re diving deep into optimization strategies to ensure our PDR example isn’t just good, but great. Expect some serious brainstorming sessions and a little bit of algorithm magic!

Welcome back to another week with Team Simul8.

As we conclude Week 7, it’s imperative to reflect on our significant strides. This week was primarily dedicated to enhancing our Preliminary Design Review (PDR). The collective effort during our sessions was evident through the meticulous peer review process, which greatly contributed to refining our presentation.

One of our notable accomplishments includes the completion of the Blackjack example. This model now incorporates comprehensive strategies and provides suggestions for the most optimal choices, demonstrating the potential of our project in a practical application.

As we transition into Week 8, our immediate focus is the preparation for the critical presentation in Tampa. This client meeting is not just an opportunity to exhibit our project’s progress and potential but also a platform to receive direct feedback and insights that could be pivotal for our project’s future direction. Consequently, our preparations will not only involve logistical arrangements but also the intellectual consolidation of our work thus far.

The impending week demands a comprehensive refinement of our PDR, ensuring every aspect of our project is articulated with clarity, precision, and substantiated by the data and findings we’ve gathered. This refinement isn’t about overhauling the content, but about fine-tuning and potentially adding layers of depth where necessary, enhancing the narrative of our journey, the milestones achieved, and the challenges overcome or anticipated.

This week, we started our proof of concept. Our meeting revolved around delving deep into our learning algorithm, primarily via gaming examples. We started with a very simplistic understanding of Blackjack and soon found out that we had to incorporate a strategy that could optimize player wins. Questions bubbled up about the intricacies of gameplay strategies—when to hit when to stand—and how various factors, such as the cards played, influence these decisions.

The Tic-Tac-Toe example showed a good but simplistic implantation of our algorithm, acting as another lens to comprehend it’s nuances. While exploring these examples, an underlying theme became evident: identifying optimal strategies is pivotal, and nodes represent various strategies a player could employ.

Our project architecture also took center stage. We dissected our system’s architecture, pinpointing where our learning algorithm examples could mesh within the established framework. One question really revealed a flaw in our plan:  “Why aren’t the Red and Blue Teams mirror images of each other?” This led to enlightening discussions on game dynamics, code reusability, and the significance of consistent terminology.

Coming next week, we should expect to add strategies to our Blackjack Proof of Concept, update our system architecture, and lastly gear up for our peer presentations. Stay tuned as our project quickly develops!