Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2009
    Posts
    2

    Unanswered: General Data Collection Storage

    I am designing a new laboratory database. I want to store the raw results for all tests together.

    In some cases, the result is a single value. However, the result is sometimes a raw waveform or signal.

    Which case below is ideal (and why)? ... or provide your own ideal option.

    Option 1: Store each individual data point as a separate result row (with an offset from t=0).

    OR

    Option 2: Create a signal_header table (start time, sample rate, units, etc) which links to a raw_signal_value table (signal, offset index, value).

    OR

    Option 3: Store the raw data in an external file to retrieve when necessary.

  2. #2
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >I am designing a new laboratory database.
    I doubt this is the first of its kind.
    What architectures have been used in the past?

    >I want to store the raw results for all tests together.
    Perhaps you should consider Third Normal Form.

    >In some cases, the result is a single value.
    Really?
    What is the Unit of Measure for stored single value?
    For example, say your are storing temperature (as a single value).
    Degrees Farenheit, Celcius,Kelvin, etc?

    >However, the result is sometimes a raw waveform or signal.
    In database or computer science terms, EXACTLY how is a "waveform" stored?
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •