Reports until 15:10, Tuesday 24 June 2025
H1 CDS
david.barker@LIGO.ORG - posted 15:10, Tuesday 24 June 2025 (85298)
New rev-lock model build/install procedure

Today's h1asc model change was a good opportunity to consolidate the new model build procedure now that H1 models are rev-locked (source code locked to specific subversion revision numbers).

1) build the model as normal to verify that it builds (user controls on h1build)

> rtcds build h1asc

2) run model through check_model_changes to check if DAQ changes are pending (user myself on opslogin0)

> check_model_changes h1asc

In this case 4 fast channels are to be added to the DAQ

3) run rev-update on model to check subversion status (user controls on h1build)

> rtcds rev-update h1asc

This showed that the h1asc.mdl model has local mods pending commit.

4) commit local mods to subversion (user myself on opslogin0)

Using the DAQ change information from 2) I committed h1asc.mdl to subversion

> svn ci -m "Elenna 23jun2025 add 4 DQ chans DC6_[P,Y]_[IN1,OUT]" h1asc.mdl

5) run rev-update again (user controls on h1build)

> rtcds rev-update h1asc

At this point I was able to accept svn HEAD as the rev-lock versions for h1asc's source files

6) do a rev-locked build of h1asc (user controls on h1build)

> rtcds build --rev-locked h1asc

7) install the model (user controls on h1build)

> rtcds install h1asc