Developed a bi-directional G.729 VOIP Compression Application. This system is used in the Avionic Systems Division Audio lab to test commercial and in house-built G.729 audio systems.

The application can:

1. Support audio compression for encoding and decoding with G.729, G.729a, and G.729c algorithms.
2. Encode/Decode Raw and Wave audio files.
3. Encode in real-time audio captured from the microphone, and sends it to another G.729 system.
4. Decode in real time G.729 data received over the network.
5. Down sample multiple files at the same time.
6. Media player (play, stop, resume audio)
7. Logs the process of the application to a file.
8. Cross/Platform (Windows / Linux)

I worked for ERC, At NASA's Kennedy Space Center Inc as part of the Test and Operations Support Contract (TOSC) team, we provided overall management and implementation of ground systems capabilities, flight hardware processing and launch operations. These tasks support the International Space Station, Exploration Ground Systems, the Space Launch System, Orion Multi-Purpose Crew Vehicle and Launch Services programs.

• Software and Launch displays developer for the Thermal Control Subsystem I worked on launch displays, and scripts for testing the SLS Core Stage, Interim Cryogenic Propulsion Stage (ICPS), and the Mobile Launcher II (ML II).
• Configured and Maintained Virtual Machines administrated by the GSS group. We simulate the Launch Computers environment in the Launch Control Center. This facilitated the process of dev elopment, and testing for the subsystem teams, since they didn’t have to go through the process of requesting a Launch Computer which might take a few days / weeks.
• Developed, Updated and troubleshooted software tools to facilitate the development process for the Subsystem teams.

I worked in the Ground Support Services team (GSS). I was one of the SVMs and Linux DDEs admin, and developer. A SVM is a Virtual machine that contains the Launch Control Center (LCC) software. Thanks to this, the subsystem teams do not have to request a set in the firing rooms for development purposes. This way we reduce the development processes due to the lack of resources in the firing rooms of the LCC.

I was also assigned to support the Thermal Control Subsystem as a Software and Launch displays developer to fulfill the requirements post DCR. The displays and software that I'm developing are going to be used on launch day for the Artemis 1 mission. I am in constant communication with our NASA counterpart to follow NASA's recommendations.

Working on the only specialize software group in the TOSC contract provided me the opportunity to collaborate with different subsystems group, and to learn from their field. On my time here, I have provided software support to the Mechanical, Flight Controls, Thermal Control and Electrical Subsystem groups by helping them with their software, launch displays development, troubleshooting, and documentation.

I helped develop a script for the Flight controls Team to calculate Fast Fourier Transformation Sine Waves, and Phase and gain. This script provides them with the capability to test the actuators from the SLS Core Stage and the SLS Boosters once they arrive to the Vehicle Assembly Building (VAB). The project that I am currently working on is classified as (Class C) safety-critical following NASA's criteria. This means that the software provides full or partial verification of safety-critical systems, including hardware or software subsystems.

Another project that I worked on was LCS Lite which goal is to provide the capability of having Launch Control Center software environment in a container (Docker) without having access to the internet. Having this capability in the scenario of a government shutdown or a hurricane everyone in our contract would be able to work even if the servers are shutdown at NASA's Kennedy Space Center. This would greatly benefit the Artemis program to keep moving towards its goal of going back to the Moon by 2024.

Skills: Bash scripting, Python, C++, networking, Linux, Java, Docker

At Johnson Space Center I worked in the Advance Caution And Warning System group (ACAWS). My role was to develop a simulation for a mission abort scenario while astronauts were en route to the Moon. The goal of ACAWS is to develop essential technology that enables deep-space mission crews to more effectively handle off-nominal conditions. On deep-space missions, round-trip communication time delay makes it impossible to close the loop with Mission Control on Earth prior to taking critical actions. The ACAWS integrated suite of intelligent system technologies can provide crew support to identify the problems, decide when to take actions, and what actions to take. Determining what parts of the system are affected by failures – either becoming disabled or losing a level of redundancy – is a critical precursor to correcting a problem. ACAWS leverages the efforts of creating a diagnostic model of a system to reason about the propagation of failures through the system.

Accomplishments:

1. Developed a Lunar Mission Simulation and Launch Displays used to train Flight Controllers and Astronauts.
2. Developed multiple failures to affect the Orion Spacecraft during the mission simulation. This helped us to exercise the Orion cockpit, and the Ground displays. These failures were detected by our autonomous system to detect failures (ACAWS).
3. Generate reliable, and high-fidelity sensor data for the different systems of the Orion spacecraft.
4. Created a GUI application to inject failures.
5. This Application reduces the number of steps and knowledge the user needs to have, in order to simulate a failure in the Orion Spacecraft.
6. Automated processes by developing scripts to perform a certain task.

1. Arranged programming projects by analyzing requirements, preparing flowcharts and diagrams using knowledge of computer capabilities, subject matter, programming language, and logic.
2. Developed systems by encoding project requirements, confirmed program operation by conducting tests, modifying program sequence, and/or codes..
3. Maintained professional and technical knowledge by attending educational workshops, reviewing professional publications, establishing personal networks, participating in professional societies.

I was 1 of 10 students from the United States selected to participate in the Research Experiences for Undergraduates (REU) within the Computer Science department at Missouri University of Science and Technology.

Throughout this program we conducted research in the field of Cloud Computing guided by PhD students. I worked with group made up of three students from different countries and backgrounds. The title of our research was A Secure Document Comparison Protocol. Text-based document comparison for similarity is common task in a variety of fields. However, when the document data is confidential, secure protocols are necessary to ensure the confidentiality of both comparison parties. The comparison context for this project was a client-server comparison, in which the client queries a single document to be compared to a collection of documents owned by the server. This type of comparison is important in select applications. For instance, a doctor may wish to compare the symptoms of one of his patients against a database of patient records held by another doctor. However, releasing patient medical data is unlawful, so a comparison protocol would have to leak no information about patients not under a doctor’s care. A second example is academic journal submissions. A journal receiving a paper submission needs to compare the paper against digital archives to detect plagiarism, without revealing the content of the submission.

Definition 1: A document comparison protocol is secure if it

1. does not reveal the server documents to the client
2. does not reveal the client document to the server
3. does not reveal any comparison scores to the server

If the protocol revealed comparison scores to the server, the server could learn which documents the client document is most similar to as well as how similar in general it is to the record collection, which is unacceptable because then the server learns information about the client document.

Our contributions include:

1. secure comparison protocol
2. an implementation of the protocol as a Java GUI application

The protocol fully satisfies the notion of security detailed by Definition 1.

We developed a client/server application that securely computed the similarities between two documents. While computing the similarities neither party will be able to access the document. The protocol that we used assures the protection of the data from unauthorized users. In our application, the user needed to select the collection where he/she wants to compare the document. After this, he/she submitted the document that he/she wanted to compare to the selected collection. This process is a secure procedure because the application encrypts the document before sending it to the server. By doing this, we prevented the server of knowing the information that it contains. For example, let say that a doctor would like to know the risk factor of heart disease in a specific patient. If the doctor requested a file of a patient from a server, the privacy of that patient is being violated because unauthorized users can access that data. With our application, the doctor is required to send the document with the information history of the patient. The application encrypted the information of the document before sending it. Then, the server received the encrypted document, so there is no way for the server to know any information regarding the patient. Afterwards the server calculated the similarity of the encrypted document with all the documents in the collection chose by the user and it returned a similarity score between 0 to 1 for each document.

Skills: Java, C, Java Native Library, Encryption, RSA, Unix, Latex, Research, Cloud Computing, Number Theory, Vector Space Model, Lucene Library, Paillier cryptosystem, homomorphic, k-NN query, Networking, Data Communication, Multithreading