5/20    What is an effective way of representing data in a timing diagram?
        specific information that needs to be included is: what signal
        it is, when it goes on, how long it is on for. Is it better to
        record, at every possible timestep, what signal is on/off; or is
        it better to represent it as, for a given signal, the time the
        pulse go on and then how long they last? (the pulses do not all
        stay on for the same time).
        \_ That's really vague. What kind of data? Usually it's shown
           relative to the clocks that drive the data.
                \_ sorry. the clock isn't really relevant since this
                   sequence can start at any time. specifically, I
                   need to somehow store how I want ~50 signals to
                   go off (in terms of duration and when the pulses
                   begins. what I'm looking for is an efficient way
                   of storing this information. that information
                   will later be used to actually drive those 50
                   different signals (which are just pulses).
        \_ "better" is a funny word.  What constraints do you have?  If you
           store the state for each tick you'll use more space.  If you need
           to check against 50 different signal data points each tick you'll
           use more time and probably have more complex code.