Programming to allow for a choice between 2 different Auto Calibrate commands

In hindsight, the initial comment of "Would you like to calibrate?" is answered as YES when the individual runs the program, therefore is redundant.
However, if this is placed at the beginning of each and every program, it MIGHT come in hand.,. although this in and of itself could be considered a "complete" autocalibration program, and doesn't need to be inserted into any programs; merely run as "the calibration program", then run whatever programs you need to.

Good call on posting the code, however since this is, as stated above, more or less for new users, some explanation as to what you're doing would be helpful.
Maybe an explanation on why your autocalibration program uses ALL_TIPS_WITH_DEFAULTS as opposed to a custom parameter set, or why you would NOT want to say yes it moved.

In my opinion (and I do consider this an opinion), if you're calibrating, regardless of if the sphere actually physically moved or not, the first probe should ALWAYS answer "Yes, the sphere has moved", to designate that tip as the "Master" (because answering YES tells PC-DMIS that the probe is the master).
Then, theoretically, every probe after that could answer NO, but still DCC the calibration, and you'd only need to take 1 manual point every time and walk away (setup-dependent, of course)

AndersI provided a good explanation somewhere on the forum on why it's not necessarily a good idea to "truly" calibrate the master, hence why I believe you should always answer YES for calibration at least once. Something along the lines of, you want the master to be theoretically perfect, to reduce the amount of errors and such and such.

In hindsight, the initial comment of "Would you like to calibrate?" is answered as YES when the individual runs the program, therefore is redundant.
However, if this is placed at the beginning of each and every program, it MIGHT come in hand.,. although this in and of itself could be considered a "complete" autocalibration program, and doesn't need to be inserted into any programs; merely run as "the calibration program", then run whatever programs you need to.

Good call on posting the code, however since this is, as stated above, more or less for new users, some explanation as to what you're doing would be helpful.
Maybe an explanation on why your autocalibration program uses ALL_TIPS_WITH_DEFAULTS as opposed to a custom parameter set, or why you would NOT want to say yes it moved.

In my opinion (and I do consider this an opinion), if you're calibrating, regardless of if the sphere actually physically moved or not, the first probe should ALWAYS answer "Yes, the sphere has moved", to designate that tip as the "Master" (because answering YES tells PC-DMIS that the probe is the master).
Then, theoretically, every probe after that could answer NO, but still DCC the calibration, and you'd only need to take 1 manual point every time and walk away (setup-dependent, of course)

AndersI provided a good explanation somewhere on the forum on why it's not necessarily a good idea to "truly" calibrate the master, hence why I believe you should always answer YES for calibration at least once. Something along the lines of, you want the master to be theoretically perfect, to reduce the amount of errors and such and such.