improve the ability to auto detect the need to disable fast cloning
When you get a chance, please contact Bill Tanenbaum to learn how smart cmsrun is about knownig when to automatically disable fast cloning. I am under the impression that cmsrun does a better job at this than does art. If, indeed, cmsrun is smarted, please add their capabilities to art.
#1 Updated by Rob Kutschke over 6 years ago
I spoke again with Bill. cmsrun has fastCloning on by default. It has good, but not perfect, automatic detection, on a product by product basis, to disable fast Cloning when appropriate. He tells me that the implementation is that the source puts information about the schema ( or a pointer to it?) into the FileBlock object. The output modules can get the FIleBlock object from art and decide of the schema are compatible or not. There are still (very rare) occaisions on which it is necessary to disable fast Cloning in the config file; that does it for all data products.
We definitely want this feature but it is still a low priority.
#2 Updated by Christopher Green over 6 years ago
- Due date set to 09/30/2013
- Category set to I/O
- Target version set to 1.09.00
- Start date deleted (
- Estimated time set to 48.00 h
- Scope set to Internal
- Experiment Mu2e added
- SSI Package art added
Testing is likely to take up the bulk of the time for this issue.