ECR Title: RCG V2.7	DCC No: E1300534-v1
Date: June 13, 2013
Requester: R. Bork	Impacted Subsystem(s): DAQ/CDS
Description of Proposed Change(s): Changes are to be made to the Real-time Code Generator (RCG) and DAQ software for requested feature additions/modifications and to fix reported code bugs. Details of the code changes are documented in LIGO-T1300494 and LIGO-T1300500. Once completed, this software is to become the next release of CDS software, Version 2.7.
Reason for Change(s): Primary reasons for changes are: Support for two DAQ frame types: commissioning and science frames, to reduce the overall long term data storage requirements. Additional support for UINT32 data types for storage of ODC state vector information. Modifications to RCG IIR filter support: - Reduce number of filter module EPICS channels that are recorded by DAQ to reduce the overall DAQ load. - Provide additional switch setting EPICS channels and switch position checking in support of Guardian scripts.
Estimated Cost: Costs covered under INS manpower.
Schedule Impact Estimate: None. Plan is to complete installation at sites prior to next engineering run, scheduled for mid July, 2013.
Nature of Change (check all that apply): Safety Correct Hardware Correct Documentation	Improve Hardware Improve/Clarify Documentation Change Interface Change Requirement
Importance: Desirable for ease of use, maintenance, safety Desirable for improved performance, reliability Essential for performance, reliability Essential for function Essential for safety	Urgency: No urgency Desirable by date/event: __15Jul13__________ Essential by date/event: ____________ Immediately (ASAP)
Impacted Hardware (select all that apply): Repair/Modify. List part & SNs: ______________________ Scrap & Replace. List part & SNs:_____________________ Installed units? List IFO, part & SNs: _________________ Future units to be built	Impacted Documentation (list all dwgs, design reports, test reports, specifications, etc.): RCG Developer’s Guide T080135 RCG V2.7 Release Notes (New)
Disposition of the proposed change(s): The disposition of this proposed engineering change request is to be completed by Systems Engineering and indicated in the “Notes and Changes” metadata field in the DCC entry for this ECR. The typical dispositions are as follows: Additional Information Required: in which case the additional information requested is defined. The ECR requester then re-submits the ECR with the new information using the same DCC number for the ECR but with the next version number. Rejected: in which case the reason(s) for the rejection are to be given Approved Approved with Caveat(s): in which case the caveat(s) are listed TRB: the ECR is referred to an ad-hoc Technical Review Board for further evaluation and recommendation. It is the System Engineer’s (or designee’s) responsibility to organize the TRB. The System Engineer (or designee) then makes a technical decision based on the TRB’s recommendation. Links to the TRB’s documentation (charge, memos, final report, etc.) are to be added to the “Related Documents” field for this ECR. CCB: a change request for approval of additional funds or schedule impact is to be submitted to the Configuration Control Board. Links to the CCB’s documentation (CR, etc.) are to be added to the “Related Documents” field for this ECR. Concurrence by Project Management: Acknowledgement/acceptance/approval of the disposition is to be indicated by the electronic “signature” feature in the DCC entry for this ECR, by one the following personnel: Systems Scientist Systems Engineer Deputy Systems Engineer