Project

General

Profile

Feature #302

every process should maybe have a 'key' to split detector/accelerator stuff

Added by Tunnell, Christopher over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Tunnell, Christopher
Category:
common_py
Target version:
Start date:
28 January 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

this is I guess a standard map reduce thing I ditched, but here's what I'm thinking:

"accelerator" is the key and the JSON datastructure gets passed
"detector" is the key and the JSOn datastructure gets passed

but each processor looks at the key to see if it should process it. The accelerator one will either cache the value if the geometry hasn't changed or only spit out something once.

#1

Updated by Tunnell, Christopher over 10 years ago

  • Target version changed from MAUS-v0.0.1 to Future MAUS release
#2

Updated by Tunnell, Christopher over 10 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

it's all just mixed together now

#3

Updated by Rogers, Chris over 10 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.3

Also available in: Atom PDF