{"push_id":656962922,"size":2,"distinct_size":2,"ref":"refs/heads/Issue1366","head":"ef48731f07f4d2421ffdcc0bd24bc7e94118c38d","before":"0a79a0374b2f48550c450de9629d191e9f4d5a7a","commits":[{"sha":"a9070890e4bf1a2eacbc7895c3c50d38501e5cb5","author":{"email":"b112983fe7236771be67c24b76ba2dad66e40583@gmail.com","name":"helfrij"},"message":"Minor change to the dark current correction analysis block, how the dark current corrected value is calculated.","distinct":true,"url":"https://api.github.com/repos/acquaman/acquaman/commits/a9070890e4bf1a2eacbc7895c3c50d38501e5cb5"},{"sha":"ef48731f07f4d2421ffdcc0bd24bc7e94118c38d","author":{"email":"b112983fe7236771be67c24b76ba2dad66e40583@gmail.com","name":"helfrij"},"message":"Made significant changes to the BioXAS mono classes and region control classes. The region control is now a subclass of AMPseudoMotorControl, and most of the duplicate functionality has been removed. Still remaining is the region control specific move() slot, which makes additional connect statements with the move action in order to get notifications for when the current step in the crystal change changes. Haven't quite decided how to resolve this, either to leave as is, or make some more significant changes to the process of building up the required crystal change actions. The region control is no longer the parent of the component controls: instead these are created in the monochromator class and set using the control's public setters. BioXASSide builds and runs, but motors related to the mono are in the process of being reset--not able to test that the region control functionality remains unchanged just yet. #1366","distinct":true,"url":"https://api.github.com/repos/acquaman/acquaman/commits/ef48731f07f4d2421ffdcc0bd24bc7e94118c38d"}]}