Double-computing of peaks in beads_to_ERF_model

[jakebeal]

The beads_to_ERF_model.m file computes peaks twice, once for the designated ERF channel and once for all channels including the designated ERF channel. This redundancy makes our code more vulnerable, and should be refactored out by having just the all-channels computation, but treating some aspects of it specially.

[coverney]

What aspects should be treated specially?

[jakebeal]

Off the top of my head, I'm not sure --- this is a place to dig through the code. The guiding principle, however, is this:

• The ERF channel (and secondary channel) are processed for purpose of getting an ERF conversion.
• Currently, all other channels get processed just as an FYI, so you can check and see if things look sane on the other channels and make decisions about secondary channel if needed.

In the future, we might want to do more with the other channels, such as compare their peaks also in certifying identity between color models (if we aren't already; I don't remember).