NASSA INFILTED

[EspinozaGuerreroLuisAlberto]

Nasa space NASA

National Aeronautics and Space Administration

Headquarters

Washington, DC 20546-0001

Office of the Chief Information Officer

Reply to Attn of:

TO:

Distribution

FROM: Chief Information Officer

SUBJECT: NASA Federal Source Code Framework

This memo defines NASA OCIO activities and provides roles and responsibilities to ensure compliance with Office of Management and Budget (OMB) M-16-21 "Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software."

In 2016, OMB released M-16-21, which seeks to ensure that new custom-developed Federal source code be made broadly available for reuse across the Federal Government. M-16-21 also requires agencies, when commissioning new custom software, to release at least 20 percent of new custom-developed code as Open Source Software (OSS) for three years, and to collect data concerning new custom software to gauge performance. This approach is consistent with the Digital Government Strategy "Shared Platform" approach, which enables federal employees to work together both within and across agencies to reduce costs, streamline development, apply uniform standards, and ensure consistency in creating and delivering information.

NASA OCIO is the responsible office for developing, maintaining, disseminating, and implementing new policy and procedural requirements of M-16-21.

The following actions are assigned to the NASA OCIO nformation Management Office:

By December 6, 2016: Inventory and publish a machine-readable source code project inventory that conforms to the code.json schema for cataloging metadata of code projects on code.nasa.gov.

Annually, beginning in FY 2017: Release a minimum of 20% of custom code as Open Source Software each year. The percentage calculation shall be based on the total number of code projccts in the code inventory.

By July 2017: In coordination with the Office of Procurement and the Office of General Counsel, develop and implement a policy or process that requires NASA to apply the 3-Step Software Solutions Analysis (as outlined in the M-16-21) during the

procurement phase for new IT systems. When contracting for developer services, NASA will encourage vendors to use open source technology wherever possible.

By FY 2018: Implement a policy or process that will ensure appropriate ights to custom code, recognizing that a vast majority of code produced within NASA is written by contractors. In order to increase the percentage of delivery of source code using free and open licensing, OCIO will work with the OMB code.gov and Tech Transfer teams to develop core contract language to disseminate within the agency. NASA OCIO will coordinate with the Office of Procurement, Office of General Counsel, Office of the Chief Engineer, the Space Technology Mission Directorate, and other stakeholders to ensure appropriate contract language is in place by FY 2018.

More information about the implementation of these requirements wil follow. This is for your general awareness. The OCIO will work to meet the initial inventory of machine- readable source code for the December 2016 milestone. All questions regarding this memo should be directed to Jason Duley at (650) 604-1834 or [email protected].

Rghee P. Wynn

Chief Information Officer

Attachments

OMB M-16-21 "Federal Source Code Policy: Achieving Efficiency, Transparency, and Innovation through Reusable and Open Source Software."

CC:

Administrator/Mr. Bolden

Deputy Administrator/Dr. Newman Associate Administrator/Mr. Lightfoot Chief of Staff/Mr. French

Deputy Associate Administrator/Ms. Roe

White House Liaison/Ms. Kornell

Associate Administrator for Strategy and Plans/Mr. Cremins

Chief Financial Officer/Mr. Radzanowski

Chief Information Officer/Ms. Wynn

Chief Engineer/Mr. Roe

Chief Health and Medical Officer/Dr. Williams

Chief Safety and Mission Assurance/Mr. Wilcutt

Chief Scientist/Dr. Stofan

Chief Technologist/Vacant

General Counsel/Ms. Thompson-King

Inspector General/Mr. Martin

By pelopedment Creator Licensor Criteria Luis Alberto Espinoza Guerrero Ingeniero Eléctrico [email protected] Espinoza Guerrero Luis Alberto LAEG ESCRITURA PROYECTOS BigDate Big Data Corp Cap Cop Gap Company Agreement asume ads phenomenall. Creator Licensor Criteria . ACTOR LAEG adv.Luis Alberto Espinoza Guerrero adj's.

Python SWIG wrapper for the SRI Language Modeling (SRILM) Toolkit

Use your SRILM language model's from Python. The code is based off Nitin Madnani's wrappers.

Requirements

GNU make

Simplified Wrapper and Interface Generator (SWIG)

Python 2.4+

SRI Language Modeling Toolkit

Installation

Copy the appropriate makefile to Makefile.

Modify the environmental variables at the top of Makefile.

run make

Usage

from srilm import LanguageModel >>> lm = LanguageModel(lm_directory="/Users/james/languagemodels", vocab_file="gigaword.vocab", lm_file="gigaword.lm", n=3) >>> lm.trigram("new", "york", "times") -1.0087490081787109 >>> lm.trigram("new", "york", "city") -0.8258976936340332 >>>

See srilm.py for more details.