I Play Dungeons in the Police Station-Chapter 386 - 237: Program Bugged

Li Xiang concentrated the computing resources of the workstation on the stock market model, which was just barely enough for now.

Fortunately, there was no conflict between Li Xiang and it. While Xiao Mu was trading stocks, he was working at the institute and didn’t need a computer.

When he needed to use the computer, the stock market was closed, and there was no need for the model.

The time they used the workstation’s computing power was perfectly staggered, not delaying his improvements to Xiao Mu.

However, after several days of simulation calculations, Li Xiang discovered a problem: the computing power of his workstation was still too weak to support the learning of the stock market model.

Considering the vast number of stocks in the market, using this workstation for simulated trading was still too far-fetched.

When encountering large data sets, it would freeze and crash, then restart.

At this rate, forget about a month—a year might not even be enough to complete this model.

"What should I do? Is the plan going to fail?"

If the model couldn’t be completed, his plan to make money through stocks was doomed to die before it was born. Was he supposed to use this million to continue buying chips to expand?

Li Xiang immediately dismissed this idea.

This over one million was the renovation money given by Lin Feifei; he couldn’t misappropriate it. If Lin Feifei found out, she’d definitely be angry.

Besides, spending this million on chips would only buy seven or eight pieces, which wouldn’t be enough. Then what?

"Just leave it for now."

With insufficient computing power in the workstation, it was difficult to complete the model’s simulation learning, so Li Xiang had to put this money-making plan aside, to be revisited when conditions permitted.

This was quite regrettable to Li Xiang, as he lamented his lack of access to superior computing workstations.

"If only I had a supercomputer."

At this time, Li Xiang was envious of the institute’s ability to apply for access to a supercomputer, which would be tremendously beneficial for their project research.

But with the price of a supercomputer being tens of millions to billions, Li Xiang could only swallow and admit he couldn’t afford it. He simply couldn’t.

Even selling himself wouldn’t be enough.

Although he coveted the institute’s supercomputer access, he was just an artist, and using a supercomputer required strict permission checks, which he didn’t have.

But unexpectedly, he soon got the chance to utilize a supercomputer.

That afternoon, Li Xiang was sitting in the studio, continuing his drawing when Xiao Qian brought in the latest numbered skull and took away his completed painting. At that moment, he heard an argument outside.

"Xiao Qian, what’s happening outside?"

"Brother Li, it’s a BUG in the core program of the skull digital restoration model over in the R&D department. No one can figure it out, so they’ve been arguing."

"Oh? I’ll go take a look."

Upon hearing this, Li Xiang immediately set down his paper and pen and stood up to head outside.

"Eh?"

Qian Zhaoping looked at the skull specimen in his hand and didn’t know what to say.

You’re an expert in Skull Restoration Technique, so there’s no need to meddle in program matters.

What can you achieve by just looking? Can the program fix itself?

With no choice, Qian Zhaoping put down the skull and followed him out.

Outside, two people were arguing, while Professor Xiang sat in front of a computer, examining the code to locate the program’s BUG.

But from the way his brow was furrowed, it was clear he hadn’t found the issue yet.

"Everyone be quiet; this is not a marketplace. If you want to argue, do it at home."

Even Professor Xiang was getting annoyed. These two were the key members of the R&D department, technically capable, but their design philosophies clashed. Now that the system had a problem, the two began to argue.

As the project leader, he had to coordinate their relationships and cover for them.

Now, with a problem in the skull digital restoration model’s core program, he had to come over and diagnose the issue one bit at a time.

As he wracked his brains over here, the argument continued over there, and his temper flared.

Seeing Professor Xiang get angry, the two stopped arguing and stood aside, quietly observing.

Li Xiang quietly walked over and also began to watch.

This program was developed in Python, a common language due to its simplicity and widespread use. It seamlessly works with data structures and other commonly-used algorithms.

Because of its mature development language, many useful libraries in Python can be used in AI, like Numpy for scientific computing, Scipy for advanced computation, and Pybrain for machine learning.

It’s the most suitable choice for developing the skull digital restoration model.

With his ability, just one glance behind Professor Xiang was enough for him to understand the problem: a BUG in their core program caused contradictions during operation. Once it reached that crucial node, it would crash automatically.

Soon, during calculations, Professor Xiang also found this system BUG. But as this was a core program issue, to solve it, they would have to start over. But completely starting from scratch would render all their previous code useless.

He was pondering whether there was a compromise to save development time.

"There’s no other way. The core code has a problem; the logic isn’t coherent. We have to redesign the underlying logic."

Li Xiang saw Professor Xiang’s dilemma, but it was insoluble. This wasn’t a matter of trade-offs that would resolve the issue.

"Oh? You understand programming too?"

Hearing this voice, Professor Xiang looked up to find that the dissent came from Li Xiang.

His words clearly identified the problem, suggesting he understood programming too.

Qian Zhaoping broke into a cold sweat, seeing Li Xiang dare to voice an opinion to Professor Xiang.

He didn’t even notice the project development supervisors had just been scolded?

When Professor Xiang was conducting research, interruptions were extremely annoying. It was surprising Li Xiang dared to interrupt with his comments.

One has to admire his courage, like a newborn calf unafraid of tigers.

Perhaps Professor Xiang wouldn’t hold grudges against him, given Li Xiang was an expert in Skull Restoration Technique, but he certainly wouldn’t let him make random comments.

"I understand a bit; the core program seems logically coherent, but there’s a conflict during execution, leading to contradictions. At crucial nodes, it freezes and crashes. This is a problem with the underlying program design; it needs to be rebuilt. Simply optimizing won’t resolve the core issues."

"Li Xiang, what grounds do you have to say my program has problems? Don’t just because you know a little Skull Restoration Technique think you can criticize here. Programming isn’t your domain to comment on."

The speaker was one of the two who had been arguing earlier, also a project supervisor. The skull digital restoration model’s core underlying code was developed under his leadership, and now Professor Xiang hadn’t said anything, but Li Xiang, who was an outsider, dismissed it entirely. How was he supposed to accept this?

"Su Bohai, mind your manners."

Seeing the conflict escalating, Professor Xiang immediately intervened, reprimanding Su Bohai before looking at Li Xiang. "Is there really no other solution?"

Professor Xiang understood that this system BUG was extremely concealed, even unnoticed by its developer, Su Bohai. Yet Li Xiang, just by standing behind for a while, identified the problem, leading Professor Xiang to suspect that Li Xiang’s programming skills might rival his own.

But to start all over, he couldn’t immediately make such a decision.

"Professor Xiang, don’t listen to an outsider’s opinion—this underlying logic was developed by our team. Please give us more time to optimize."

Su Bohai couldn’t understand why Professor Xiang would so readily heed Li Xiang, simply because he was a Skull Restoration Technique expert? Did that grant him the right to critique at will?

Starting from scratch, he had to recall that their team had worked tirelessly for two months to complete this core underlying code. Now it was being dismissed so carelessly; it seemed too abrupt.

"There’s no way to continue optimizing. This program has already been optimized for a day, yet no fundamental issues have been clarified. How can we optimize? Even if we force optimizations, with an unstable foundation, operational problems will surely arise later. Li Xiang is right; this section of core code needs to be redone."

Professor Xiang seemed determined to listen to Li Xiang and start from scratch.