40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Wed Nov 22 17:52:25 2017, gautam, Update, Optimal Control, Visualizing cost functions globalCosts.pdf
    Reply  Tue Jan 2 16:37:26 2018, gautam, Update, Optimal Control, Oplev loop tuning loopOpt_180102_1706.pdfglobalCosts.pdf
       Reply  Wed Jan 3 12:33:16 2018, rana, Update, Optimal Control, Oplev loop tuning 
          Reply  Wed Jan 3 16:25:32 2018, awade, Update, Optimal Control, Oplev loop tuning 
       Reply  Tue Jan 9 21:57:29 2018, gautam, Update, Optimal Control, Oplev loop tuning loopOpt_180108_2232.pdf
Message ID: 13500     Entry time: Wed Jan 3 16:25:32 2018     In reply to: 13498
Author: awade 
Type: Update 
Category: Optimal Control 
Subject: Oplev loop tuning 

Another cool feature is client side pre-commit hooks. They can be used to run checks on the local version at the time of commit and refuses to push until the pass/fail exits 0.

Can be the same as the Gitlab CI or just basic code quality checks.  I use them to prevent jupyter notebooks being commited with uncleared cells. It needs to be set up on the user's computer manually and is not automatically cloned with the directory: a script can be included in the repo to do this and run manually on first time clone.


When putting code into git.ligo.org, one way to have automated testing is to use the Gitlab CI. This is an automated 'checker', much like the 'Travis' system used in GitHub. Essentially, you give it a make files which it runs somewhere and your GIT repo web page gets a little 'failed/passing' badge telling you if its working. You can also browse the logs to see in detail what happened. This avoids the 'but it works on my computer!' thing that we usually hear.


ELOG V3.1.3-