1 / 2

Procedure Development and Control PDAC Status

Page 2. PDAC Current Status. Current delivery in Mission Ops is Cycle 11.1Notable functionalities currently available:Organization of the automated procedures by CCS version, system, typeControls user access, tracks updates/versions, change historyProvides access to IMARS Standard Out Data and the Timeliner Compiler

afi
Download Presentation

Procedure Development and Control PDAC Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    2. Page 2 PDAC Current Status Current delivery in Mission Ops is Cycle 11.1 Notable functionalities currently available: Organization of the automated procedures by CCS version, system, type Controls user access, tracks updates/versions, change history Provides access to IMARS Standard Out Data and the Timeliner Compiler “Parses” ground database of IMARS Standard Out Date for use in compilation Provides details on the commands and its arguments (if applicable) Allows the user to search for commands or CVT by ops name or PUI Produces and manages an automated procedures “package” ready for uplink Executable (.tlx), address (.tla) and listing file (.tll) Tracking tag file (1 file for all procedures onboard) Swapped and unswapped files provided LIF headers and checksum added to files destined for onboard

    3. Page 3 PDAC Future Work PDAC Cycle 11.2 (comprised of minor fixes) will be available end of October PDAC Cycle 12.0 (port to Linux) Code inspections were complete on 8/24 Due to PDAC’s use of the SUID bit for controlling access to checked-in procedures, the method for invoking external commands had to be redesigned. PDAC currently uses the system() function provided by C, however this function does not work correctly on Linux when utilizing the SUID bit. As a result the code was changed to use fork()/exec() Verification tests against the Level B requirements is in progress Formal PDAC test scheduled for 2/6 – 2/21 AIX vs. Linux performance metrics shows a substantial improvement SRs in work Batch re-compile of automated procedures Side-by-side DIFF listings when an automated procedure is updated Ability to build a database of commands and telemetry in procedures so that they can be compared against a new standard out delivery and affected procedures can be easily identified

More Related