Changes between Version 18 and Version 19 of NetworkDynamicConverterFunctions


Ignore:
Timestamp:
11/12/12 16:09:18 (7 years ago)
Author:
lxwang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetworkDynamicConverterFunctions

    v18 v19  
    8181 if start and end values present, store in observation.period attribute 
    8282 
     83'''base.net''' 
     84 
     85  base.net activity information is ignored for now. base.net is only assumed to be a network object, not networkDynamic (behavior subject to change). base.net not required; if it is not given, create a new base.net with the max number of vertices required, and use the edge info (without timing) to create edges. This assumes that there are no isolate vertices greater than the max number of vertices given. If base.net parameter is supplied without any other edge or vertex info, returns the base.net casted into a networkDynamic object. An easy way to create a basic nD object is  
     86 
     87{{{ 
     88networkDynamic(network.initialize(n)) 
     89}}} 
     90 
     91Both vertex info and edge info are optional. If vertex info is missing, and edge info is present, try to infer the vertices required for the edges. If both are missing, and there is no base.net, return an empty list (since 0 node networks are not supported). 
     92 
     93 
    8394Determines if '''building from network list''', as that specifies both edge and vertex dynamics at the same time 
    8495 
     
    110121    apply activation spells to vertices 
    111122   
    112 Determine edge data schema. 
    113  
    114 If base.net exists, determine if the set of vertex.ids present in the edges data is consistent with it and take action appropriate to construct.mode    
     123  Determine edge data schema. 
     124 
     125  If base.net exists, determine if the set of vertex.ids present in the edges data is consistent with it and take action appropriate to construct.mode    
    115126 
    116127  If toggles