Jump to content

Git inspection plan versioning


---
 Share

Recommended Posts

I'm trying to imagine would it make sense and what would the workflow be using git to manage Calypso plan revisions.

Anyone tried?

 

Or any feedback of Calypso built-in versioning?

 

Link to comment
Share on other sites

I use the plan name by adding a date to the end of the name.

3032943-202_A_OP35_04-15-2024

3032943-202 = Part Number

A = Revision level of part

OP35 = Operation number

04-15-2024 = Revision control of CMM program

 

Then I use an excel workbook for setup information which is named the same as the plan name with a "#" prefix (This keeps the workbook at the top of the list). 

The workbook is stored in the plan name folder.

#3032943-202_OP35_04-15-2024.xlsx

The workbook has a worksheet named Rev History; this is where all changes are documented.

Feel free to use the workbook attached.

 

#Master CMM Setup workbook 2023.xlsx

Link to comment
Share on other sites

We are using that - only thing which will come into mind will be current state of program. You can recall previous versions, but that will destroy "current working version".
You can make in autorun to call specific version, but i think it have some problems with using different versions simultaneously. That function make changes in program directory.

Link to comment
Share on other sites

Thank you both,

Martin I didn't know recall version works, so I would just make a copy and keep the latest vesrion separate. I have to try it out sometime soon.

1 thing I don't see anywhere, comparing to git (or similar versioning system) is when you make specific changes in rev. 1.5, you cannot port them to lower version.

Like there are no "branches".

Link to comment
Share on other sites

 Share

×
×
  • Create New...