Differences between revisions 17 and 19 (spanning 2 versions)
⇤ ← Revision 17 as of 2006-11-16 22:02:43 →
Size: 3288
Editor: BramSlagmolen
Comment:
← Revision 19 as of 2006-11-16 22:19:20 → ⇥
Size: 3568
Editor: BramSlagmolen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This writing is an glorified version of R. Wards entry in the 40m ilog ([http://www.ldas-sw.ligo.caltech.edu/ilog/pub/ilog.cgi?group=40m&date_to_view=11/06/2006&anchor_to_scroll_to=2006:11:06:17:34:27-rward entry]). This writing is an glorified version of R. Ward's core entry in the 40m ilog ([http://www.ldas-sw.ligo.caltech.edu/ilog/pub/ilog.cgi?group=40m&date_to_view=11/06/2006&anchor_to_scroll_to=2006:11:06:17:34:27-rward entry]).
Line 5: Line 5:
=== Directory structure ===
Line 7: Line 6:
 * [[font][color=green]advLigo/] == Directory structure ==

 * '''advLigo/'''
Line 10: Line 11:
 * /cvs/cds/caltech/target/c1omc/  * '''/cvs/cds/caltech/target/c1omc/'''
Line 13: Line 14:
 * /cvs/cds/caltech/chans/param/  * '''/cvs/cds/caltech/chans/param/'''
Line 16: Line 17:
 * /cvs/cds/caltech/chans/daq/  * '''/cvs/cds/caltech/chans/daq/'''
Line 20: Line 21:
=== Simulink model === == Simulink model ==
Line 28: Line 29:
=== Making the FE code === == Making the FE code ==
Line 30: Line 31:
To make the real-time linux executable, go to the top directory (advLigo/) and type 'make omc'. Where 'omc' is the name of the Simulink model. This will generate a whole bunch of files and folders in the advLigo/target directory. To make the real-time linux executable, go to the top directory ('''advLigo/''') and type 'make omc'. Where 'omc' is the name of the Simulink model. This will generate a whole bunch of files and folders in the '''advLigo/target''' directory.
Line 32: Line 33:
On the C1OMC front-end computer, remove the old target directories (c1omc and c1omcepics). Then copy the advLigo/target/omcepics to /cvs/cds/caltech/target/c1omcepics on the front-end computer. On the C1OMC front-end computer, remove the old target directories ('''c1omc''' and '''c1omcepics'''). Then copy the '''advLigo/target/omcepics''' to '''/cvs/cds/caltech/target/c1omcepics''' on the front-end computer.
Line 35: Line 36:
=== Checking/updating the parameter files === == Checking/updating the parameter files ==
Line 37: Line 38:
Copy the file in advLigo/target/omcepics/db/C1/autoBurt.req to /cvs/cds/caltech/target/c1omcepics Copy the file in '''advLigo/target/omcepics/db/C1/autoBurt.req''' to '''/cvs/cds/caltech/target/c1omcepics'''
Line 39: Line 40:
Find the file omc.par in advLigo/build/omcepics, and modify it with the following sed commands: Find the file 'omc.par' in '''advLigo/build/omcepics''', and modify it with the following sed commands:
Line 41: Line 42:
 s/%IFO%/C1/g  * s/%IFO%/C1/g
  Set the %IFO% to your local IFO-name.
Line 43: Line 45:
 s/datarate = 16384/datarate = 32768/g  * s/datarate = 16384/datarate = 32768/g
  Set the datarate to your local configuration.
Line 45: Line 48:
 s/ifoid = 1/ifoid = 0/g  * s/ifoid = 1/ifoid = 0/g
  Set the ifoid to your local ifo ID.
Line 47: Line 51:
 s/rmid = 0/rmid = 1/g  * s/rmid = 0/rmid = 1/g
  Set rmid to your local reflective memory ID.

Then rename it as 'tpchn_C2.par', and place it in '''/cvs/cds/caltech/chans/param/'''
Line 50: Line 57:
Then rename it as tpchn_C2.par, and place it in /cvs/cds/caltech/chans/param/ == Location of the FE executable ==
copy the front-end executable in '''advLigo/src/fe/omc/omcfe.rtl''' to '''/cvs/cds/caltech/target/c1omc/'''
Line 53: Line 61:
=== Location of the FE executable ===
copy the front-end executable in advLigo/src/fe/omc/omcfe.rtl to /cvs/cds/caltech/target/c1omc/		 == DAQ Channels ==
take the file located at '''advLigo/src/epics/util/C1OMC.ini''', modify it to suit
your tastes, and place it in '''/cvs/cds/caltech/chans/daq/'''

take the file located at '''advLigo/src/epics/util/C1OMC.txt''', and put it in
'''/cvs/cds/caltech/chans/'''
Line 57: Line 69:
=== DAQ Chennels ===
take the file located at advLigo/src/epics/util/C1OMC.ini, modify it to suit
your tastes, and place it in /cvs/cds/caltech/chans/daq/

take the file located at advLigo/src/epics/util/C1OMC.txt, and put it in
/cvs/cds/caltech/chans/


=== Restarting the FE ===		 == Restarting the FE ==

Here is described the various steps on how to get a new Simulink model running on the new PCIX front-end computers (in this work the C1OMC at the 40m).

This writing is an glorified version of R. Ward's core entry in the 40m ilog ([http://www.ldas-sw.ligo.caltech.edu/ilog/pub/ilog.cgi?group=40m&date_to_view=11/06/2006&anchor_to_scroll_to=2006:11:06:17:34:27-rward entry]).

Directory structure

  • advLigo/

    • This is the top working/modeling directory at a location to your taste.

  • /cvs/cds/caltech/target/c1omc/

    • This is the frontend executable directory with the .rtl files.

  • /cvs/cds/caltech/chans/param/

    • This is the .. directory on the PCIX front-end computer.

  • /cvs/cds/caltech/chans/daq/

    • This is the .. directory on the PCIX front-end computer

Get the latest CVS code from ([http://ldas-sw.ligo.caltech.edu/cgi-bin/cvsweb.cgi/cds/?cvsroot=CDS LIGO/LSC CVS Repositories]) and place it in a suitable directory to work in. There are a few special Simulink modules for the ADC and DAC, LIGO filter modules, etc. which are required.

You can modify the Simulink model 'omc.mdl' appropriately. Make sure you have the correct dcuid number, as it could be wrong in CVS. For more info on this see [http://www.ligo.caltech.edu/%7Eaivanov/daq_handbook.html LIGO Data Acquisition Handbook], not sure how relevant this is to the C1OMC system.

The Simulink model can only have a three (3) character file name, which usually correspond to the system name here 'omc'. Also, the model itself can only be 1 layer deep (due to current restrictions). This means that in your Simulink model you have a top-layer, and you are only allowed to place a sub-layer in your model. You can have multiple sub-layers in your top-layer.

Making the FE code

To make the real-time linux executable, go to the top directory (advLigo/) and type 'make omc'. Where 'omc' is the name of the Simulink model. This will generate a whole bunch of files and folders in the advLigo/target directory.

On the C1OMC front-end computer, remove the old target directories (c1omc and c1omcepics). Then copy the advLigo/target/omcepics to /cvs/cds/caltech/target/c1omcepics on the front-end computer.

Checking/updating the parameter files

Copy the file in advLigo/target/omcepics/db/C1/autoBurt.req to /cvs/cds/caltech/target/c1omcepics

Find the file 'omc.par' in advLigo/build/omcepics, and modify it with the following sed commands:

  • s/%IFO%/C1/g
    • Set the %IFO% to your local IFO-name.
  • s/datarate = 16384/datarate = 32768/g
    • Set the datarate to your local configuration.
  • s/ifoid = 1/ifoid = 0/g
    • Set the ifoid to your local ifo ID.
  • s/rmid = 0/rmid = 1/g
    • Set rmid to your local reflective memory ID.

Then rename it as 'tpchn_C2.par', and place it in /cvs/cds/caltech/chans/param/

Location of the FE executable

copy the front-end executable in advLigo/src/fe/omc/omcfe.rtl to /cvs/cds/caltech/target/c1omc/

DAQ Channels

take the file located at advLigo/src/epics/util/C1OMC.ini, modify it to suit your tastes, and place it in /cvs/cds/caltech/chans/daq/

take the file located at advLigo/src/epics/util/C1OMC.txt, and put it in /cvs/cds/caltech/chans/

Restarting the FE

Use the procedure in the wiki to restart c1omc [http://lhocds.ligo-wa.caltech.edu:8000/40m/Computer_Restart_Procedures#c1omc c1omc restart]

Simulink_to_Front-End_code (last edited 2012-01-03 23:02:37 by localhost)