40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Wed Nov 22 17:52:25 2017, gautam, Update, Optimal Control, Visualizing cost functions
|
Tue Jan 2 16:37:26 2018, gautam, Update, Optimal Control, Oplev loop tuning 
|
Wed Jan 3 12:33:16 2018, rana, Update, Optimal Control, Oplev loop tuning
|
Wed Jan 3 16:25:32 2018, awade, Update, Optimal Control, Oplev loop tuning
|
Tue Jan 9 21:57:29 2018, gautam, Update, Optimal Control, Oplev loop tuning
|
|
Message ID: 13498
Entry time: Wed Jan 3 12:33:16 2018
In reply to: 13497
Reply to this: 13500
|
Author: |
rana |
Type: |
Update |
Category: |
Optimal Control |
Subject: |
Oplev loop tuning |
|
|
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.
Quote: |
The current version of the code I am using is here: although I may not have inculded some of the data files required to run it, to be fixed...
|
|