Changes between Version 14 and Version 15 of NetworkDynamicConverterFunctions


Ignore:
Timestamp:
10/24/12 18:37:50 (7 years ago)
Author:
skyebend
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetworkDynamicConverterFunctions

    v14 v15  
    114114 if network.list is non-NULL vertex.* and edge.* must be NULL and the reverse 
    115115 
     116Bookeeping 
     117 
     118 if start and end values present, store in observation.period attribute 
    116119 
    117120Determines if building from network list, as that specifies both edge and vertex dynamics at the same time 
     
    214217=== Exporting from nD === 
    215218  
    216 (maybe only keep an "as.data.frame" function aliased to most common use case? ).  
     219(maybe only keep an "as.data.frame" function aliased to most common use case? ).  All of these methods should handle censoring. Check the soon-to-be-added {{{observation.period}}} attribute #155 (if present) and set all onset.censored spells (-Inf) to value of start, and terminus-censored spells (Inf) to value of end. (discussion on #149) 
    217220 
    218221 
     
    252255Add "include.censoring=T" attribute 
    253256 
    254  
    255  
    256  
    257  
    258  
    259  
    260  
    261  
    262  
    263  
     257get.slice.networks: how do we handle censoring here? 
     258 
     259get.slice.networks: the output list of networks should have time labels (perhaps as a network attribute?) 
     260 
     261since "changes" is so similar to "toggles" should we just make those the same argument? The converter can detect whether there is an extra column or not (what should the column be called?) 
     262 
     263 
     264 
     265 
     266 
     267