Description

We need to implement version control in Zemax.

Tasks

A list of sequential tasks for the project. The project is complete when all tasks are complete

• [x] @Abeer: conduct research on version control practices in Zemax
• [x] @Jenny: implement Zemax version control via github

Notes

Current situation:

• optics01: payload, grism, relay lenses, foreoptic
  • Desktop → Optics_Zemax → FINCHEye_Payload or FINCHEye_Components
• optics02: slit
• naming convention of Zemax files: [system component][name][last updated]
• Version History:
  • within each folder, update log file with file name, last updated date and time, last updated by, update details [see example for payload]

A git repository should be organized like this: [src]

• check in the *.zmx files into the repository. The *.zmx files are saved as ASCI files and are suitable to document the changes like in programming languages.
• do not check in the *.zda session files. This should be user depended temp files
• add Zemax Documents files to the repository which must be copied into the working documents files folder
• realease versions of OpticStudio models should be saved as a *.zar Archive file in some folder outside the repository

Here is the protocol for naming conventions: [src]