Epic: Follow ups from new packing !3268
Things to follow up from !3268 (merged) and related MRs
- #199 (closed)
- #200 (closed)
- #203 (closed)
- #205 (closed)
- Moore#414 (closed)
- Moore#422 (closed)
- DaVinci#49 (closed)
Related issues
- Show closed items
Is blocked by
Relates to
- Moore #354
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Rosen Matev added Persistency label
added Persistency label
- Rosen Matev marked this issue as related to #199 (closed)
marked this issue as related to #199 (closed)
- Rosen Matev marked this issue as related to #200 (closed)
marked this issue as related to #200 (closed)
- Rosen Matev marked this issue as related to #203 (closed)
marked this issue as related to #203 (closed)
- Rosen Matev marked this issue as related to #205 (closed)
marked this issue as related to #205 (closed)
- Rosen Matev marked this issue as related to Moore#414 (closed)
marked this issue as related to Moore#414 (closed)
- Rosen Matev marked this issue as related to Moore#422 (closed)
marked this issue as related to Moore#422 (closed)
- Rosen Matev marked this issue as related to DaVinci#49 (closed)
marked this issue as related to DaVinci#49 (closed)
- Rosen Matev removed the relation with Moore#414 (closed)
removed the relation with Moore#414 (closed)
- Rosen Matev removed the relation with Moore#422 (closed)
removed the relation with Moore#422 (closed)
- Rosen Matev removed the relation with DaVinci#49 (closed)
removed the relation with DaVinci#49 (closed)
- Rosen Matev marked this issue as related to Moore#414 (closed)
marked this issue as related to Moore#414 (closed)
- Rosen Matev marked this issue as related to Moore#422 (closed)
marked this issue as related to Moore#422 (closed)
- Rosen Matev marked this issue as related to DaVinci#49 (closed)
marked this issue as related to DaVinci#49 (closed)
- Rosen Matev marked this issue as related to Moore#354 (closed)
marked this issue as related to Moore#354 (closed)
- Developer
How about the following suggestion:
Currently, there is one algorithm instance for each possible input container, each of which produces (at most) one packed buffer. For this algorithm, the input is optional. Now, all instances for the same type of container could be combined into a single
SplittingMergingTransformer
which happily takes (a vector of) optional inputs, and which can output a vector of (optional) outputs. So all algorithms under the 'packers' control flow node could be 'collapsed' into one algorithm per type of input container. - Contributor
@graven I guess you forgot but this was what I wanted at the beginning. I even tried to implement a gaudi algorithm that can do vector input vector output. But I couldn't get it work..
Collapse replies - Developer
SplittingMergingTransformer
has only existed since gaudi/Gaudi!1315 (merged), which was created only about a month ago ;-)
- Contributor
@rmatev I am going through persistency related issues. I see all issues in this epic are closed. Can we close this now?
- Sevda Esen closed
closed