Tanmay's Log

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
  
 
-- Referring to the Book "Structure and Interpretation of Computer Programs" 2nd Edition, by Harold Abelson, Gerald Jay Sussman (1996) .
 
-- Referring to the Book "Structure and Interpretation of Computer Programs" 2nd Edition, by Harold Abelson, Gerald Jay Sussman (1996) .
 +
 
-- Event Driven Simulation: In which Actions (Events) trigger further events that happen at a later point in time, which trigger further events and so on.
 
-- Event Driven Simulation: In which Actions (Events) trigger further events that happen at a later point in time, which trigger further events and so on.
  

Revision as of 10:17, 19 July 2010

Log of My Research and Design for the COSC 427 Design Study

19th June

-- Referring to the Book "Structure and Interpretation of Computer Programs" 2nd Edition, by Harold Abelson, Gerald Jay Sussman (1996) .

-- Event Driven Simulation: In which Actions (Events) trigger further events that happen at a later point in time, which trigger further events and so on.

Objects to be modeled: -- Real Life elementary components:

1) Wires --- Carry binary signals : 0 / 1. They also have to perform some tasks (inform connected components) about change in their value.
2) Digital Function Blocks --- Which are connected between Wires carrying inputs to other wires - outputs. These need to listen for changes in the state of wires connecting these blocks. A change in the state of 1 wire might trickle down to changes in the neighboring wires based on the output of these function blocks.
3) Operations Queue --- to help model the time delay of performing various tasks during the simulation.
4) Probe --- To trigger on change in value and print value on screen
Personal tools