You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the network attributes hyper, multiple, and loops must be FALSE for networkLites. In principle, it may be possible to support these with the current data structure. hyper would make use of tibblelist columns (as referenced in #2) to allow a vector of tails and heads for each edge. multiple could use an edge id mechanism similar to that in network to allow referencing a particular one of several parallel edges. loops by itself would not require extensive changes, but the existing code would need to be checked for correctness. As in #2 EpiModel runtime needs to be considered when making any generalizations to networkLite. I am not aware of any need for these options in current applications, but wanted to note that in principle they could be supported.
The text was updated successfully, but these errors were encountered:
Currently the network attributes
hyper
,multiple
, andloops
must beFALSE
fornetworkLite
s. In principle, it may be possible to support these with the current data structure.hyper
would make use oftibble
list
columns (as referenced in #2) to allow a vector of tails and heads for each edge.multiple
could use an edge id mechanism similar to that innetwork
to allow referencing a particular one of several parallel edges.loops
by itself would not require extensive changes, but the existing code would need to be checked for correctness. As in #2 EpiModel runtime needs to be considered when making any generalizations tonetworkLite
. I am not aware of any need for these options in current applications, but wanted to note that in principle they could be supported.The text was updated successfully, but these errors were encountered: