-
These will certainly not compile in the current codebase.
-
Add a TimeInvariantWrapperTransform member of TimeVaryingTransform, and use that in TimeVaryingTransform::project for thread safety. This is the strategy previously used in Distribute, but putting the alias on TimeVaryingTransform gives us more safety if Distribute is not in fact the top level transform. Note: copies are only made off of calls to project, so having the alias on every TimeVaryingTransform is not too wasteful.
-
…ms were receiving empty Templates)
-
PlotDetection for single roc point
-
Now, Stream takes a single transform argument. The old interface remains, renamed to DirectStream. If that transform is a pipe, Stream will split its child transforms appropriately, and set up a DirectStream. Adjacent non-timeVarying transforms are grouped in pipes, time varying transforms all get separate stages. The default behavior isn't necessarily ideal if e.g. a lot of light time varying stages are present, in that case its possible the additional synchronization costs will outweight gains from paraellelism (due to having more separate single thread stages). In these cases DirectStream may be preferable, however current algorithms seem largely unaffected.
-
allow File::name to be queried using 'name' property
-
…ingTransforms in parallel
