Differences between revisions 7 and 8
Revision 7 as of 2006-11-16 19:25:17
Size: 1278
Comment:
Revision 8 as of 2006-11-16 19:25:31
Size: 1282
Comment:
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
This is the C1OMC .. directory on the PCIX frontend computer.   This is the C1OMC .. directory on the PCIX frontend computer.
Line 17: Line 17:
This is the C1   This is the C1

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

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]).

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 C1OMC .. directory on the PCIX frontend computer.
  • /cvs/cds/caltech/chans/daq/
    • This is the C1

Get the latest CVS code from (...) 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.

==

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