| abstract | - A self-diagnostic was a diagnostic that a machine, system, or android performed on itself to check for errors, usually on a regular basis. Soong-type androids like Data would initiate self-diagnostics at regular intervals to verify that all functions were within established parameters. Data ran a self-diagnostic in 2369 after it seemed that he had lost over 90 minutes of memories as his internal chronometer was not in sync with the ship's chronometer leading him to believe that he was experiencing a malfunction. It later turned out that he had been abducted by solanogen-based lifeforms and that his systems were functioning properly. (TNG: "Schisms" ) That same year, after the USS Enterprise-D computer began experiencing a series of malfunctions due to an interface experiment conducted by Data and Geordi La Forge, he stated that he would perform a self-diagnostic. (TNG: "A Fistful of Datas" ) In 2372, after B'Elanna Torres had repaired Automated Personnel Unit 3947 for the most part, he reported that his self-diagnostic showed that he was operating at 68% of peak operating capabilities. (VOY: "Prototype") Later that year, The Doctor ran a level-two self diagnostic on his program when he claimed to have suffered lapses in concentration. Kes believed that it was not a technical problem, but that he had feelings for Danara Pel. (VOY: "Lifesigns") In 2373, after the effects of long-term use had begun affecting The Doctor, he claimed that his self-diagnostic routines have always indicated that in the event of cascade failure he should be completely re-initialized. But the crew of USS Voyager were worried that if he did that, all his memories and individualism would be erased. (VOY: "The Swarm")
|
