Minutes from the 7/28/04 and 8/04/04 LCLS SLC IOC meetings. Plus other
notes.

No Meeting:   8/11/04
Next Meeting: 8/18/04 in B5, Rm 211.

(1) There is NO meeting this Wed due to the Lehmann review.  The controls
    breakout session is 8/11/04 8:00am to 10:30 in B48, 2nd floor Pine
    conference room.  The SLC IOC will be presented at 9:00 for anybody
    interested.

(2) Review of functional requirements will be Oct 1.  Design starts Oct 15.
    When specifying functional requirements, tag functions that 
    will probably be EPICS and those that will probably be on top of EPICS.
    Part of the design will be a list of PVs and functions that the EPICS 
    IOC app developers MUST provide.

ACTION: All		    Due: Oct 1
    
(3) Prototyping continues by Debbie with these goals:
    - get cmlog working
    - get DBMain started
    Note that Debbie has got part of cmlog working already.

ACTION: Debbie		    Due: Aug 18

(4) Conversion of database and messages from IEEE format to platform-dependent
    format:

    We should think about creating a definition file for each message
    so that we can use some tool to (automatically) generate a conversion 
    routine to be used by the SLC IOC.  This is like RPC does with messages
    that it sends between different platforms - RPCGEN created XDL conversion
    routines.  Does anybody know something better than RPCGEN and XDL?

    As for the conversion of data in the SLC database, does the SLC IOC get
    the data type of each secondary as part of the database download?  If yes,
    then the conversion on the SLC IOC can be based on that data type.

ACTION: ??		    Due: Oct

(5) CMLOG IOC errlog listener decision:

    Mike Laznovsky is assigned this work.  No one on tech-talk has responded
    to his email asking if anyone has done it already.  Debbie has 
    got the old cmlogVxLogMsg built on 3.14 for vxWorks-only.  It has a 
    few problems.  Can Debbie continue to work on cmlogVxLogMsg (soon to be
    known as cmlogIOCLogMsg)?

ACTION: RonC		    Due: Aug 18

(6) Structure of the SLC IOC application directory:

    Debbie mentions that currently all source for the SLC IOC application
    is under one directory making it hard for multiple people to develop
    the different areas (MSG, DB, CMLOG, MGNT, BPM, FBCK, etc).  She is
    looking into splitting things up into different directories.  At some
    point, we will put the prototype into shared space 
    (ie, /afs/slac/g/lcls/epics/ioc/slc) where all can have access.

ACTION: Debbie and Steph    Due: Aug 18

(7) CMLOG message logging by non-EPICS SLC tasks on the IOC:

    We want to send specific message codes to cmlog and on to the VMS SLC 
    message log.  Examples of the types of code would be those in 
    ref_c_inc:msgdef.hc (on the Alpha).  But EPICS errlog only deals 
    with text strings.  So for the SLC tasks where we want to use a specific 
    message code, we have to use straight cmlog calls, not errlogPrintf.

    We may have to send text strings instead of 10 individual 4-byte arguments
    depending on data conversion issues.  Whatever we decide for message
    logging, both the Unix process that forwards messages to the SLC errlog
    and the VMS process that receives the SLC IOC messages may need some minor 
    tweaks.

ACTION: ??		    Due: Oct

(8) SLC IOC in the LCLS Test Stand:

    We will want to test SLC IOCs in the LCLS test stand at the FFTB beamline.
    Will the mccdev alphaserver and the development proxy talk to IOCs on 
    LEBnet?

ACTION: Steph		    Due: Oct


Stephanie