Sunday, October 2, 2011

scene builder

  1. will have database,tomcat,webview,user account
  2. will have in-channel for data,requirement and rules
  3. will have run command
  4. will have run save option
  5. will have favourable selection criteria
  6. will have favourables isolation criteria
  7. will have favourables as start set for next run option
  8. generates an xml with the favourable scenes organized as nodes and options to see its predecessors
  9. later,will have networking option between user accounts and across physical networks
  10. later will have , 3 way scene building with moderator
  11. later will have n party scene building with moderator
  12. later will have archive reference for common paths
rules are interdata relations, data a and b's OK range with c in range OK range

data represented in sets
as none,as one,as n-1, as n defines it
if n is represented as j,k clone or other, in programming a visitor may have life
dependency or other on another one
data as,
A B C but if some scene is not favourable its as,
A B C D, D is the marker for non favourable

lte mac

Angles:
  1. uses 8 timers
  2. transport channels 
  3. crnti and harq 
  4. mimo phy 
  5. platform interface
  6. user interface
  7. platform driver states 
  8. mac states 
  9. phy states
  10. internal queues
  11. mdb's
  12. Memory tabulation
  13. Event path counters(will show if previous event path has been taken ,entry till return definer)
  14. Event path markers(shows what events are in progress now) is Event counters
  15. Assertions
  16. Multi level checks for data, datastructures
  17. spec version to code mapping information
  18. doxygen based annotation
  19. perl based automation tool , multithreaded
  20. perl tool capable of remote communication by independent channel
  21. perl tool capable of log generation
  22. scripts directory individually runnable
code will cover the above areas plus,

timestamping
will have module specific in-ram traces(circular)
will have platform event traces
will have platform data structure and protocol internals dump
will have xml interface for default globals and current globals
will have hardware submodule in-ram dump

will work with plarform debugger to give a verbose snap

later, xml for default interfaces and methods and a metadata channel
derived from java model