19

Often in Star Trek (almost all variations of it) they talk about "level N" diagnostics.

Is there an actual description of what the diagnostic levels mean?

  • @Pixel: Thank you for your edit! :) – jimjim Jan 30 '13 at 6:58
  • 1
    Huhm. I feel absolutely certain I answered this question before from a reallife perspective, but cannot find it. What I remember answering was basically the same as Stefan's answer: In reallife, we have unit tests, integration tests, and others. Unit tests are the fastest, but aren't as thorough (a level-1 diagnostic), while integration tests are much slower, but tests everything together (a higher level diagnostic). – Izkata Jan 30 '13 at 11:35
  • I'm pretty sure the TNG technical manual talks about this (basically saying what Stefan and Izkata are saying, but with some additional canon-specific details), but I don't have it with me to confirm... – Micah Jan 30 '13 at 13:05
  • 1
  • You're very welcome, @Arjang! – Pixel Jan 30 '13 at 19:05
17

According to the tech manuals diagnostic levels indicate how much of a disruption on the system the diagnostic will take, where level 5 is run a self check usually taking a few minutes, all the way to level 1 shut it down, physically check, and carefully reinitialize. The details of each diagnostic level and time taken change depending on the system being diagnosed. Level 4 diagnostic on a navigational thruster probably takes less time and involves different measures than a Level 4 diagnostic on the warp core. Here are some generalizations of the measures at different diagnostic levels.

  1. Take system out of service, full shutdown, manual inspection, observed re-initialization, manual testing.
  2. Take system out of service, limited manual inspection, crew monitored automated tests.
  3. Take system out of service, minimal manual inspection, automated tests.
  4. Take system out of service, automated tests.
  5. Automated tests.
| improve this answer | |
5

I have not come across one in Star Trek but I run a software consultancy and have a similar protocal for software that my company produces.

Warning - SPECULATION (although it is supported by good engineering princples):

The higher (or lower depending on how you do it) number means that you get more detailed information. Some people ask why you would not put it on the highest level at all times, the reason you do not and you try to pick your level carefully is that you risk too much information being spewed out and causing you to miss something important or to have to spend a lot of time sifting through information to find what you need.

Also, more output means more time spent producing output - not much of a consideration normally but on a real time machine (like a nuclear power plant monitor) a couple of microseconds writing output and not monitoring the systems can be serious. There is also the fact that more diagnostics means bigger log files which can cause an issue on some systems where users do not delete them and you end up with, literally, years of log files eating disk space up!

| improve this answer | |
  • This does not provide an answer to the question, and is more of a boast about your company's diagnostic levels. Moreover, you clearly are unsure about the levels used in Star Trek (higher (or lower depending on how you do it) number). – AStopher Apr 9 '17 at 9:23
  • Not sure how you got a boast out of that. The vast majority of software systems use diagnostics and I did not disclose any company details. The comments on the question seem to imply people found my answer helpful. When I said higher or lower I was discussing diagnostic systems in general, not just Star Trek. – Stefan Apr 19 '17 at 10:32
  • Exactly, it's generalized. – AStopher Apr 19 '17 at 10:34
  • Yes but that does not mean it is not relevant and helpful but, obviously, you are entitiled to your opinion. – Stefan Apr 19 '17 at 12:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.