The Mech Touch

Chapter 6809 Data-Driven Design Approach

Much to Ves' surprise, the SF-02 processor cluster began to produce fantastic productivity gains in less time than expected.

He and his wife only taught the smart Als for a couple of days before they suddenly gained enough comprehension to complete many design tedious and time-consuming work assignments.

Ves was not entirely sure what level Momo had reached, but Polly's competency had reached the equivalent of a young Journeyman Mech Designer!

While her grasp on fundamental sciences was impressively deep, she had yet to learn the full breadth of high technologies that a first-class Journeyman Mech Designer was supposed to know. However, Polly did not need to learn how to apply over a hundred different high technologies when the Larkinson Clan did not even make use of most of them. Ves found that it was already enough to impart knowledge relevant to the ongoing mech design projects to the smart Al based on the ARMOR POLISHER template.

Once Ves and the other mech designers started to work with the SF-02 in earnest, they found that their progress was much faster than before!

"This is amazing, Ves!" Gloriana joyously exclaimed as she held a physical projection of Momo in her arms. The black cat looked incredibly pleased after receiving praise. "Momo has learned the basic principles of archetech to the extent where she can design basic design solutions and accurately simulate the performance of archemetal components. I have been trying out the data-driven design approach. The method is rather crude in my eyes, but that does not detract from its effectiveness. I finally understand why all of those first-class mech designers are trained to design their mechs by relying on large amounts of data. It is not only easier for me to find the right solutions through a process of elimination, but it is also faster so long as Momo receives enough processing power! What she said made a lot of sense. In contrast to the more standard design approach where mech designers wracked their brains and manually came up with elegant solutions, the data-driven design approach was mainly about brute forcing the right answers.

A typical way of using the data-driven design approach was by designing multiple rough solutions. It didn't matter if they were sloppy or incomplete. As long as you threw them into a simulation program and let it run for a while, the resulting data would show which solutions produced more performance gains than others.

If necessary, the mech designer could repeat this process. He would select the best-scoring rough solution as the baseline and develop minor variations that leaned in different directions.

This is the end of Part One. Upgrade Premium to read full content:

Upgrade Now