-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
Currently, the last step before HistTuples is (sometimes) AnalysisCacheTask. In the current method, there is no single "law run EverythingTask" that will do the appropriate AnalysisCacheTasks.
In an example, bbWW is running a production v2601a. AnaTupleMergeTask is the end goal as it can easily be frozen and shared. Similarly, AnalysisCacheTasks could be frozen and shared, but in current law handling, one would need to submit each individual AnalysisCacheTask with argument --producer-to-run.
In a perfect world, there would be some fake intermediate task, similar to HistTupleProducerTask. This task (ProductionTask?) would be empty, but would have the full workflow_requires of HistTuple, forcing the entire AnaTuple/AnalysisCache subset to run.
Metadata
Metadata
Assignees
Labels
No labels