For the future though we will change the code so it disambiguates overlapping run ranges by using the conditions set that was most recently created.  That’s the default for most conditions anyways.

Nah, I think there should be some sort of pseudo-tag like “best_calibration_constants”, so that we don’t have to just assume that the last set entered for a run range are the set that should be used.  

Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link: