gdtiti / alembic

Automatically exported from code.google.com/p/alembic
0 stars 0 forks source link

Generalized abcmerge utility #183

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
This should probably be corrected, but as I understand it, this ticket 
represents

A low level helper function used to merge two alembic files. It sounded like 
write/overwrite should occur in file order as read/written.

Original issue reported on code.google.com by scottmmo...@gmail.com on 7 Jul 2011 at 3:00

GoogleCodeExporter commented 8 years ago
I'm almost positive this is a description of the abcstitcher, in which case, 
this ticket is a duplicate of the one already extent for that utility.

Otherwise, I don't know what this could mean (there'd certainly be no 
library-level function to do this).  Recommend close.

Original comment by ard...@gmail.com on 7 Jul 2011 at 7:58

GoogleCodeExporter commented 8 years ago
We're looking to do things like have two mostly identical abc files that differ 
in their values or samples and have one overlayed on top of the other. We also 
talked about having this system merge samples together. So if one.abc had 
samples at 1 and 7 and two.abc had samples for the same geometry at 4 and 9 the 
result would have samples at 1, 4, 7, 9.

I'm not familiar with abcstitcher, unfortunately. Would that cover this 
behavior?

Original comment by asuter on 7 Jul 2011 at 8:08

GoogleCodeExporter commented 8 years ago
AbcStitcher doesn't currently handle this behavior.
It currently doesn't support acyclic time sampling at all.

You can use it to stitch together one.abc that would have samples 1-10, two.abc 
with samples 11-100, and three.abc 101-104   to create a single file with 
samples 1-104.

Original comment by miller.lucas on 7 Jul 2011 at 8:34

GoogleCodeExporter commented 8 years ago
Changing these to general backlog since 1.1 has not been defined yet. 

Original comment by imchicarica@gmail.com on 7 Jul 2011 at 9:25

GoogleCodeExporter commented 8 years ago
Regardless of the state of abcstitcher, this is another example of 
filter/merge/etc. utilities for Alembic that are needed for pipeline 
integration and workflow construction.

Original comment by ard...@gmail.com on 8 Jul 2011 at 7:59

GoogleCodeExporter commented 8 years ago

Original comment by scottmmo...@gmail.com on 26 Aug 2011 at 8:44

GoogleCodeExporter commented 8 years ago

Original comment by ble...@gmail.com on 26 Aug 2011 at 11:58

GoogleCodeExporter commented 8 years ago

Original comment by scottmmo...@gmail.com on 29 Aug 2011 at 10:41

GoogleCodeExporter commented 8 years ago

Original comment by ble...@gmail.com on 19 Sep 2011 at 9:53

GoogleCodeExporter commented 8 years ago
This probably won't make it into 1.1

Original comment by miller.lucas on 25 Jun 2012 at 6:12

GoogleCodeExporter commented 8 years ago
This is probably best addressed by individual facilities as the logic of what 
needs merging and the restrictions on how to do it are most likely pipeline 
specific.

Original comment by miller.lucas on 13 Sep 2013 at 6:11