Mission Statement:

Improve implementation of SCAM as a CAM option.

Goal:

SCAM should be implemented with a minimal number of CPP tokens, preferably
none. 
  
Motivation:

There are currently in excess of 150 occurances of SCAM or BFB_CAM_SCAM_IOP
CPP tokens in CAM's source code.  This extensive use of CPP to implement
SCAM as an option is extremely fragile.  It is proving to be a significant
cost to CAM developers to keep from breaking SCAM as we try and move the
CAM infrastructure forward.

Authority: 
   AMWG

Project Lead:
   None

Scientific Lead: 
   None

Implementation Plan:

This project has not yet received even an initial exploration to determine
what the difficulties are in integrating SCAM into CAM.  It is too early to
be able to venture any guesses about a plan or effort required.

Resources: