I am revising an old program written sometime before 2012 and it's brought up some questions. First, why would one ever measure a plane and then construct an offset plane with an offset of zero? Second, if one did this, shouldn't dimensions referencing those planes give the same results? that is, the planes should be interchangeable? Instead this is what I'm seeing. I'm currently using version 2022.2 but this is translated from something earlier, probably last saved in 2017R1 in case that could possibly matter. The routine is saved as 2022.2 now though.
louisd, no I am not certain this was executed from the start, in fact the screenshot I posted is from the program as last saved, theoretically in 2017. But I did ctrl-e the constructed plane, ctl-l the constructed plane and dimensions (those dimensions were inserted by me anyway, originally the dim for OUTPLN appears later) and even created another offset 0 plane and dimensioned it, all with the same results shown.
I am interested in how running in its entirety can affect these results though, if you can explain. I would think once the first plane is measured then running the constructed plane onward should be sufficient. Apparently not though, or at least maybe not, because when I ran the program (which admittedly had changes but not to these features) the results made sense:
Also for anyone wondering I think the text color change must've been a result of the screenshot process, the text color is all the same within the progra (plus it didn't happen this time.)
TO BE CLEAR, THIS IS NOT A RESOLUTION. I am still very curious about this result and how it may be related to a full vs. partial execution, or any other possible reason. And thank you everyone for the help!
louisd, no I am not certain this was executed from the start, in fact the screenshot I posted is from the program as last saved, theoretically in 2017. But I did ctrl-e the constructed plane, ctl-l the constructed plane and dimensions (those dimensions were inserted by me anyway, originally the dim for OUTPLN appears later) and even created another offset 0 plane and dimensioned it, all with the same results shown.
I am interested in how running in its entirety can affect these results though, if you can explain. I would think once the first plane is measured then running the constructed plane onward should be sufficient. Apparently not though, or at least maybe not, because when I ran the program (which admittedly had changes but not to these features) the results made sense:
Also for anyone wondering I think the text color change must've been a result of the screenshot process, the text color is all the same within the progra (plus it didn't happen this time.)
TO BE CLEAR, THIS IS NOT A RESOLUTION. I am still very curious about this result and how it may be related to a full vs. partial execution, or any other possible reason. And thank you everyone for the help!
If you execute a routine partially, the resultant values of that execution are stored in the ACTL and MEAS results... which are then fed into dimensional outcomes.
Every time you execute a routine entirely, all of the ACTL and MEAS results will change based on the ACTUAL and MEASURED values of that component you just measured.
If you don't like your ACT and MEAS values varying on a routine you set as read-only, i suggest you open & execute the routine offline (you can do this generally by opening another routine first, then opening the routine you want to simulate executing second). doing an offline execution will make the ACTUAL and MEASURED values identically match all the theoretical values. It makes the routine look very "clean" as the 3 rows of coordinate values being displayed for each feature will be identical.
