Move Increment to Move Point Conversion Script?

DAN_M
Matthew D. Hoedeman
KIRBSTER269
davehocum


I am aware of the hazards of incremental moves. I do not use them exclusively, My primary use is as you proposed, short transitions always away from the model, primarily like an avoidance move would be. KIRBSTER269's illustration is excellent and appreciated. davehocum's comment is intriguing. All this considered, my desire remains, I feel the convenience of thinking in the incremental mindset while programming outweighs the hazards that incremental moves present. My preference doesn't matter much, as it is my organization's policy not to use them. Well, at least not let them remain after the program is proven and posted.

What I propose is a script that converts them after the program is finished. One that figures out the XYZ of where the incremental move starts, adds the XYZ translations of the incremental move itself, calculates the coordinates of the resultant position and hardcodes that position as a move point. I assume there is some existing infrastructure for these calculations, as this is exactly what PC-DMIS is doing when you click "Show Path Lines". Speaking of pathlines, I understand that I can go through and manipulate them to accomplish roughly what I'm after, but in a large program this would take a considerable amount of time.

Does this exist? How difficult would it be to make it exist? Can you think of any Commands or functions that would help?

DAN_M
Matthew D. Hoedeman
KIRBSTER269
davehocum


I am aware of the hazards of incremental moves. I do not use them exclusively, My primary use is as you proposed, short transitions always away from the model, primarily like an avoidance move would be. KIRBSTER269's illustration is excellent and appreciated. davehocum's comment is intriguing. All this considered, my desire remains, I feel the convenience of thinking in the incremental mindset while programming outweighs the hazards that incremental moves present. My preference doesn't matter much, as it is my organization's policy not to use them. Well, at least not let them remain after the program is proven and posted.

What I propose is a script that converts them after the program is finished. One that figures out the XYZ of where the incremental move starts, adds the XYZ translations of the incremental move itself, calculates the coordinates of the resultant position and hardcodes that position as a move point. I assume there is some existing infrastructure for these calculations, as this is exactly what PC-DMIS is doing when you click "Show Path Lines". Speaking of pathlines, I understand that I can go through and manipulate them to accomplish roughly what I'm after, but in a large program this would take a considerable amount of time.

Does this exist? How difficult would it be to make it exist? Can you think of any Commands or functions that would help?

I apologize for side tracking this thread, I personal do not have a an answer for you.

replace the command itself should be easy,
interesting is to find the right startpoint from the increment movement.
You have to check the last "Hit" and consider the ClearanceCube.
i think it should be possible to extract this informations and build a script around it.
But i dont have a working script