Search NASA⌕ Search

SEARCH · Search NASA

Results for “input files”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5

RAPTURE User's Manual

This User's Guide serves as a brief introduction to the RAPTURE radiation effects analysis code. It includes an overview of the input format, RAPTURE's error- and consistency-checking of the user-provided input files, the automatic-differentiation and convergce-checking schemes employed by RAPTURE, and the RAPTURE output files. A variety of example problems are included in this Guide which collectively demonstrate RAPTURE's current capabilities and provide a suite of test problems and template input files for the user. This Guide includes, for each problem, the problem description, RAPTURE input files, and comparison of the RAPTURE solution with solutiong generated with the Monte Carlo transport code ITS, the legacy deterministic code ADEPT, and, where possible, published experimental results. An appendix includes a description of all keywords and options in the RAPTURE input file.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

PROTEUS-MOC User Manual

The PROTEUS-MOC code is a three-dimensional (3D) neutron transport code based on the finite element mesh and the method of characteristics (MOC) which combines a 2D MOC with the discontinuous Galerkin finite element method for the axial direction. Thus, for PROTEUS-MOC, a 3D geometry is represented with by the implicit extrusion of a single 2D planar geometry with different material assignments allowable on each plane. The code requires four input files for a steady-state calculation without the thermal feedback: a driver input, a mesh input, a cross section input, and a material assignment input. With thermal feedback, a T/H input file is needed. For kinetics, a kinetics driver input file is required. The PROTEUS-MOC software produces a text output file as well as a data file which includes integral and average quantities such on fluxes, powers, temperatures, densities, etc. The detailed output file can be converted to the VTK format using the post processing code so that the outputs can be visualized using a visualization software such as VisIt.

97 MATHEMATICS AND COMPUTING↗

Montepy

Montepy is an object-oriented Python interface for MCNP input files. It excels at reading, editing, creating, and writing MCNP input files. The Monte Carlo N Particle (MCNP) code is a Monte Carlo transport solver for simulating many different types of radiation problems and is developed by Los Alamos National Laboratory. Montepy creates an object-oriented interface for the MCNP input file to allow for efficient automated modifications to large, complex simulations.

Gale, Micah [Idaho National Laboratory (INL), Idah↗

Model Data Archive for Manuscript Titled "Evaluation of a Coupled Surface–Subsurface Hydrologic Model Using Dense Water‑Level Sensors in a Mixed Urban–Rural Watershed"

This archive provides scripts, input files, and datasets used for the implementation and evaluation of a fully coupled surface–subsurface hydrologic model in the Neches River Basin, southeast Texas. The study uses the Advanced Terrestrial Simulator (ATS) to simulate coupled surface–subsurface hydrologic processes over a mixed urban–rural watershed and evaluates model performance using a dense network of 136 in situ water-level sensors, nine U.S. Geological Survey (USGS) stream gauges, and SSEBop-derived evapotranspiration estimates during the period October 2014–June 2024. The workflow is implemented primarily in Python 3 using the Watershed Workflow package. The Jupyter notebooks can be executed using open-source software such as Anaconda JupyterLab or Visual Studio Code. Other data files include TXT, CSV, XML, SHP, TIF, NetCDF, HDF5, and ExodusII files, which can be processed using the provided Python scripts. ATS input files are provided in XML format and can be edited using any commonly used text editor. This archive contains: *Scripts and input files used to generate the ATS model setup, including watershed discretization, mesh generation, parameter mapping, and model configuration. *Jupyter notebooks used for preprocessing observational data, evaluating streamflow, water levels, and evapotranspiration, computing performance metrics, and generating the figures presented in the manuscript. *ATS simulation outputs and processed observational datasets, including OneRain and DD6 water-level sensors, USGS streamflow observations, GIS data, and supporting spatial datasets used throughout the study.

Dense water-level sensor network↗

Level-2 Milestone 4468: Lorenz Simulation Interface Beta Release

The goal of Lorenz is to develop a sophisticated web-based framework as a front end to Livermore Computing Center resources. The primary features include: a personalized dashboard for each user, giving an at-a-glace overview of all computing center resources; a front-end to job submission and management; and a software framework to extend the convenience of web interfaces into simulation codes, including support for setting up, launching, steering, and monitoring simulations. Because the breadth of desktop operating systems in use both inside and outside LLNL spans all flavors of Linux, Mac, and Windows, the decision was made to use exclusively web-based technologies in Lorenz. Recent advancements in AJAX and Javascript programming, along with coming advances in the form of HTML5 and CSS3, made the browser the preferred development platform. The goal is to provide the user with a robust application interface that requires nothing more than a modern, standards-based web browser. This approach not only provides convenient access to Lorenz for internal and external users, but also has significant advantages over conventional applications in terms of rapid deployment and updates. The first phase of the Lorenz project is a system “dashboard”, known as MyLC, that gives LC users a rich set of portal applications, or “portlets”, from which to choose. Information that previously required knowledge of dozens of different commands, files, and web pages is now available in one convenient location. This includes account information, bank and disk usage, quotas, cluster utilization, news items, active jobs on LC systems, and more. The extensible software design of the dashboard allows users and staff members to develop their own portlets, and for them to be shared with all users or just within work groups. The second major phase of Lorenz was built on the idea that HPC centers are managed around batch processing, and “jobs” (or “runs”) progress through several discrete stages: setup, submission, queuing/waiting, running, completion, analysis, and archiving. Lorenz aims to ultimately tie all of these pieces together, including integration with the dashboard and application portals. In addition to helping guide users through the process of defining batch parameters, monitoring job progress, and interacting with jobs and job output, Lorenz also aims to promote access to additional tools and capabilities which to this point have been limited to use by power users. Ultimately Lorenz will assist users in choosing the appropriate resources, such as cluster and file system, given the requirements of a job. The third major phase of Lorenz, the subject of this milestone, is the development of an application portal. This involves teaming with application codes to provide a simple graphical interface to the simulations, which in turn seamlessly ties into job submission and monitoring. This will allow users to directly define simulation parameters and launch applications using a simple but powerful web front-end. Because many complex multi-physics codes can have thousands of inputs, providing a general GUI for building an input deck from scratch is impractical. However, most users of large applications start with an existing input file, and make some number of small changes to it. The application portal will feature a process that combines trusted and validated input files with a GUI that guides the user toward making the relatively minor changes needed for their particular problem. The input files will be in the form of templates, containing most of the data needed for a particular problem along with parameterization of changeable inputs. For expert users, there ultimately will be a way to edit the final input file directly - in the event that there are input changes needed that were not captured in the GUI.

97 MATHEMATICS AND COMPUTING↗

User's Guide for the Updated EST/BEST Software System

This User's Guide describes the structure of the IPACS input file that reflects the modularity of each module. The structured format helps the user locate specific input data and manually enter or edit it. The IPACS input file can have any user-specified filename, but must have a DAT extension. The input file may consist of up to six input data blocks; the data blocks must be separated by delimiters beginning with the $ character. If multiple sections are desired, they must be arranged in the order listed.

Shah, Ashwin↗

NIF Ignition Target 3D Point Design

We have developed an input file for running 3D NIF hohlraums that is optimized such that it can be run in 1-2 days on parallel computers. We have incorporated increasing levels of automation into the 3D input file: (1) Configuration controlled input files; (2) Common file for 2D and 3D, different types of capsules (symcap, etc.); and (3) Can obtain target dimensions, laser pulse, and diagnostics settings automatically from NIF Campaign Management Tool. Using 3D Hydra calculations to investigate different problems: (1) Intrinsic 3D asymmetry; (2) Tolerance to nonideal 3D effects (e.g. laser power balance, pointing errors); and (3) Synthetic diagnostics.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

AutoSIM

AutoSIM enables several instances of an executable to run in parallel on a directory of input files and consolidate results, at scale on the world's fastest supercomputers. The software accomplishes this by balancing compression, transmission, and computation of input files, executables, and output files to allow scalable parallel runs of any executable. The software breaks-up simulations into a configurable number of "churns" or sequential instances of executable invocations on a configurable number of cores/node. It sends the executable, supporting files, and appropriate number of input files to each node for independent execution, and then transfers the executable results to a shared disk for post-processing analysis. This MPI-based code has been demonstrated using EnergyPlus, DOE's flagship whole-building simulation engine, but was architected to allow scalable runtime of any software for any application (e.g. sensitivity analysis and uncertainty quantification). The code has also been demonstrated to scale on the Titan supercomputer using 131,072 processors to run 524,288 EnergyPlus annual simulations, and write 45TB of data to disk in 68 mins 08 secs.

New, Joshua R↗

Systems and methods for enhanced power system model validation

A system for enhanced power system model validation is provided. The system includes a computing device including at least one processor in communication with at least one memory device. The at least one processor is programmed to store a plurality of models for a plurality of devices and a plurality of input files associated with the plurality of models, receive, from a user, a selection of model of the plurality of models to simulate, retrieve one or more input files of the plurality of input files, perform a model validity check on the selected model, if the selected model passed the model validity check, perform a model calibration on the selected model, and if the selected model passed the model calibration, perform a post evaluation on the selected model.

Wang, Honggang↗

Water Security Toolkit User Manual Version 1.2.

The Water Security Toolkit (WST) is a suite of open source software tools that can be used by water utilities to create response strategies to reduce the impact of contamination in a water distribution network . WST includes hydraulic and water quality modeling software , optimizati on methodologies , and visualization tools to identify: (1) sensor locations to detect contamination, (2) locations in the network in which the contamination was introduced, (3) hydrants to remove contaminated water from the distribution system, (4) locations in the network to inject decontamination agents to inactivate, remove, or destroy contaminants, (5) locations in the network to take grab sample s to help identify the source of contamination and (6) valves to close in order to isolate contaminate d areas of the network. This user manual describes the different components of WST , along w ith examples and case studies. License Notice The Water Security Toolkit (WST) v.1.2 Copyright c 2012 Sandia Corporation. Under the terms of Contract DE-AC04-94AL85000, there is a non-exclusive license for use of this work by or on behalf of the U.S. government. This software is distributed under the Revised BSD License (see below). In addition, WST leverages a variety of third-party software packages, which have separate licensing policies: Acro Revised BSD License argparse Python Software Foundation License Boost Boost Software License Coopr Revised BSD License Coverage BSD License Distribute Python Software Foundation License / Zope Public License EPANET Public Domain EPANET-ERD Revised BSD License EPANET-MSX GNU Lesser General Public License (LGPL) v.3 gcovr Revised BSD License GRASP AT&T Commercial License for noncommercial use; includes randomsample and sideconstraints executable files LZMA SDK Public Domain nose GNU Lesser General Public License (LGPL) v.2.1 ordereddict MIT License pip MIT License PLY BSD License PyEPANET Revised BSD License Pyro MIT License PyUtilib Revised BSD License PyYAML MIT License runpy2 Python Software Foundation License setuptools Python Software Foundation License / Zope Public License six MIT License TinyXML zlib License unittest2 BSD License Utilib Revised BSD License virtualenv MIT License Vol Common Public License vpykit Revised BSD License Additionally, some precompiled WST binary distributions might bundle other third-party executables files: Coliny Revised BSD License (part of Acro project) Dakota GNU Lesser General Public License (LGPL) v.2.1 PICO Revised BSD License (part of Acro project) i Revised BSD License Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of Sandia National Laboratories nor Sandia Corporation nor the names of its con- tributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IM- PLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SANDIA CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUD- ING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ii Acknowledgements This work was supported by the U.S. Environmental Protection Agency through its Office of Research and Development (Interagency Agreement # DW8992192801). The material in this document has been subject to technical and policy review by the U.S. EPA, and approved for publication. The views expressed by individual authors, however, are their own, and do not necessarily reflect those of the U.S. Environmental Protection Agency. Mention of trade names, products, or services does not convey official U.S. EPA approval, endorsement, or recommendation. The Water Security Toolkit is an extension of the Threat Ensemble Vulnerability Assessment-Sensor Place- ment Optimization Tool (TEVA-SPOT), which was also developed with funding from the U.S. Environ- mental Protection Agency through its Office of Research and Development (Interagency Agreement # DW8992192801). The authors acknowledge the following individuals for their contributions to the devel- opment of TEVA-SPOT: Jonathan Berry (Sandia National Laboratories), Erik Boman (Sandia National Laboratories), Lee Ann Riesen (Sandia National Laboratories), James Uber (University of Cincinnati), and Jean-Paul Watson (Sandia National Laboratories). iii Acronyms ATUS American Time-Use Survey BLAS Basic linear algebra sub-routines CFU Colony-forming unit CVAR Conditional value at risk CWS Contamination warning system EA Evolutionary algorithm EDS Event detection system EPA U.S. Environmental Protection Agency EC Extent of Contamination ERD EPANET results database file GLPK GNU Linear Programming Kit GRASP Greedy randomized adaptive sampling process HEX Hexadecimal HTML HyperText markup language INP EPANET input file LP Linear program MC Mass consumed MILP Mixed integer linear program MIP Mixed integer program MSX Multi-species extension for EPANET NFD Number of failed detections NS Number of sensors NZD Non-zero demand PD Population dosed PE Population exposed PK Population killed TAI Threat assessment input file TCE Tailed-conditioned expectation TD Time to detection TEC Timed extent of contamination TEVA Threat ensemble vulnerability assessment TSB Tryptic soy broth TSG Threat scenario generation file TSI Threat simulation input file VAR Value at risk VC Volume consumed WST Water Security Toolkit YML YAML configuration file format for WST iv Symbols Notation Definition Example { , } set brackets { 1,2,3 } means a set containing the values 1,2, and 3. [?] is an element of s [?] S means that s is an element of the set S . [?] for all s = 1 [?] s [?] S means that the statement s = 1 is true for all s in set S . P summation P n i =1 s i means s 1 + s 2 + * * * + s n . \ set minus S \ T means the set that contains all those elements of S that are not in set T . %7C given %7C is used to define conditional probability. P ( s %7C t ) means the prob- ability of s occurring given that t occurs. %7C ... %7C cardinality Cardinality of a set is the number of elements of the set. If set S = { 2,4,6 } , then %7C S %7C = 3. v

Klise, Katherine A.↗

Turbomachinery Forced Response Prediction System (FREPS): User's Manual

The turbomachinery forced response prediction system (FREPS), version 1.2, is capable of predicting the aeroelastic behavior of axial-flow turbomachinery blades. This document is meant to serve as a guide in the use of the FREPS code with specific emphasis on its use at NASA Lewis Research Center (LeRC). A detailed explanation of the aeroelastic analysis and its development is beyond the scope of this document, and may be found in the references. FREPS has been developed by the NASA LeRC Structural Dynamics Branch. The manual is divided into three major parts: an introduction, the preparation of input, and the procedure to execute FREPS. Part 1 includes a brief background on the necessity of FREPS, a description of the FREPS system, the steps needed to be taken before FREPS is executed, an example input file with instructions, presentation of the geometric conventions used, and the input/output files employed and produced by FREPS. Part 2 contains a detailed description of the command names needed to create the primary input file that is required to execute the FREPS code. Also, Part 2 has an example data file to aid the user in creating their own input files. Part 3 explains the procedures required to execute the FREPS code on the Cray Y-MP, a computer system available at the NASA LeRC.

Morel, M. R.↗

Biogeochemistry simulations for the Salt Marsh Accretion Response to Temperature eXperiment (SMARTX)

Coastal ecosystems have been largely ignored in Earth system models but are important zones for carbon and nutrient processing. Interactions between water, microbes, soil, sediments, and vegetation are important for mechanistic representation of coastal processes and ecosystem function. To investigate the role of these feedbacks, we used a reactive transport model (PFLOTRAN) that has the capability to be connected to the Energy Exascale Earth System Model (E3SM). PFLOTRAN was used to incorporate redox reactions and track chemical species important for coastal ecosystems as well as define simple representations of vegetation dynamics. Our goal was to incorporate oxygen flux, salinity, pH, sulfur cycling, and methane production along with plant-mediated transport of gases and tidal flux. Using porewater profile and incubation data for model calibration and evaluation, we were able to create depth-resolved biogeochemical soil profiles for saltmarsh habitat and use this updated representation to simulate direct and indirect effects of elevated CO2 and temperature on subsurface biogeochemical cycling. We found that simply changing the partial pressure of CO2 or increasing temperature in the model did not fully reproduce observed changes in the porewater profile, but the inclusion of plant or microbial responses to CO2 and temperature manipulations was more accurate in representing porewater concentrations. This indicates the importance of characterizing tightly coupled vegetation-subsurface processes for developing predictive understanding and the need for measurement of plant-soil interactions on the same time scale to understand how hotspots or moments are generated.Included in this data package are PFLOTRAN input (PFLOTRAN input files and chemical database) files for simulating single column biogeochemistry, root, and tide interactions at the Global Change Research Wetland (Kirkpatrick Marsh; Edgewater, MD). The biogeochemical network includes soil organic matter decomposition, nitrogen, iron, and sulfur cycling, and methanogenesis. Reduced species can be oxidized and plant processes include oxygen and nutrient priming, methane release, and nutrient uptake.Inputs:TAI_database.dat - geochemical database for reactions, more information on database structure and variables can be found here https://www.pflotran.org/documentation/user_guide/cards/pages/geochemical_database.htmlswamp.in - input file for biogeochemical network in PFLOTRANswamp_eCO2.in - input file for biogeochemical network in PFLOTRAN with input gas partial pressures/concentrations adjusted for elevated CO2 treatmentsOutputs:swamp_obs_0.tec - hourly porewater concentrations from from multiple depths in the soil columnswamp_eCO2_obs_0.tec - hourly porewater concentrations from multiple depths in the soil column for elevated CO2 treatmentsPFLOTRAN code access: https://github.com/fmyuan/pflotran-elm-interface.git

54 ENVIRONMENTAL SCIENCES↗

DABAM: An open-source database of X-ray mirrors metrology

An open-source database containing metrology data for X-ray mirrors is presented. It makes available metrology data (mirror heights and slopes profiles) that can be used with simulation tools for calculating the effects of optical surface errors in the performances of an optical instrument, such as a synchrotron beamline. A typical case is the degradation of the intensity profile at the focal position in a beamline due to mirror surface errors. This database for metrology (DABAM) aims to provide to the users of simulation tools the data of real mirrors. The data included in the database are described in this paper, with details of how the mirror parameters are stored. An accompanying software is provided to allow simple access and processing of these data, calculate the most usual statistical parameters, and also include the option of creating input files for most used simulation codes. In conclusion, some optics simulations are presented and discussed to illustrate the real use of the profiles from the database.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

epJSON Editor

The software provides an interface to the EnergyPlus input file, providing similar functionality to the IdfEditor tool but written in Python and specifically targeting the JSON-formatted input file. This interface occupies (as IdfEditor did previously) the niche between directly editing the input file and use of a more full-featured graphical user interface, providing both advanced and novice users with a simple interface. An extensive effort was made to gather stakeholder feedback in order to avoid merely duplicating the features of IdfEditor and to build an interface that met the needs of users both now and into the future.

Glazer, Jason↗

NEQAIR v15.0 Release Notes: Nonequilibrium and Equilibrium Radiative Transport and Spectra Program

NEQAIR v15.0 provides the first steps to improved coupling between NEQAIR and the DPLR CFD code, which will be fully realized in v15.1. The plan is to release NEQAIR v15.1 and DPLR 4.05 at the same time. The improvements implemented in NEQAIR v15.0 have focused on improving stability, solution robustness, usability and providing different options for running the code. It is also the first version of the code to have a new input file and line of sight format since 2009. Backward compatibility with previous formats of the input files (neqair.inp and LOS.dat) has also been provided. NEQAIR v15.0 supersedes the prerelease of this version, as well as NEQAIR v14.0, v13.2, v13.1 and the suite of NEQAIR2009 versions. These updates have predominantly been performed by Brett Cruden and Aaron Brandis from AMA Inc at NASA Ames Research Center between 2016 and 2018. NEQAIR v15.0 is a standalone software tool for line-by-line spectral computation of radiative intensities and/or radiative heat flux, with one-dimensional transport of radiation. In order to accomplish this, NEQAIR v15.0, as in previous versions, requires the specification of distances (in cm), temperatures (in K) and number densities (in parts/cc) of constituent species along lines of sight. Therefore, it is assumed that flow quantities have been extracted from flow fields computed using other tools, such as CFD codes like DPLR or LAURA, and that lines of sight have been constructed and written out in the format required by NEQAIR v15.0. There are two principal modes for running NEQAIR v15.0. In the first mode NEQAIR v15.0 is used as a tool for creating synthetic spectra of any desired resolution (including convolution with a specified instrument/slit function). The first mode is typically exercised in simulating/interpreting spectroscopic measurements of different sources (e.g. shock tube data, plasma torches, etc.). In the second mode, NEQAIR v15.0 is used as a radiative heat flux prediction tool for flight projects. Correspondingly, NEQAIR has also been used to simulate the radiance measured on previous flight missions. This report summarizes the database updates, corrections that have been made to the code, changes to input files, parallelization, the current usage recommendations, including test cases, and an indication of the performance enhancements achieved.

Brandis, Aaron M.↗

Uncertainty Quantification for Electronic Hamiltonian

This program will generate random points for electrons within the dimensions given by a parameter input file. Based on these randomly generated electron positions and the nuclear positions given by a position input file it will generate a value for the total electronic energy of an isolated system. This total electronic energy is calculated using the electronic Hamiltonian for a monoatomic system with atoms having the same number of protons and neutrons. The size of the system is defined by the parameter input file. The program will do this many times to generate a distribution of theoretically possible electronic total energies of the system. A user can then compare the total electronic energy given by their electronic structure method to make sure it falls within the distribution of theoretically possible values.

Savchick, JuniperC↗

Interface Program for Reliability Predictions

CARE3MENU generates input file for CARE III program. Used to predict reliabilities of complex, redundant, fault-tolerant systems, including digital computers, aircraft, and nuclear and chemical control systems. CARE III input file often becomes complicated and not easily formatted with text editor. Provides easy interactive method of creating input file by automatically formatting set of user-supplied inputs for CARE III system. CARE3MENU provides detailed online help for most of its screen formats.

Bavuso, S. J.↗

Tool for Merging Proposals Into DSN Schedules

A Practical Extraction and Reporting Language (Perl) script called merge7da has been developed to facilitate determination, by a project scheduler in NASA's Deep Space Network, of whether a proposal for use of the DSN could create a conflict with the current DSN schedule. Prior to the development of merge7da, there was no way to quickly identify potential schedule conflicts: it was necessary to submit a proposal and wait a day or two for a response from a DSN scheduling facility. By using merge7da to detect and eliminate potential schedule conflicts before submitting a proposal, a project scheduler saves time and gains assurance that the proposal will probably be accepted. merge7da accepts two input files, one of which contains the current DSN schedule and is in a DSN-standard format called '7da'. The other input file contains the proposal and is in another DSN-standard format called 'C1/C2'. merge7da processes the two input files to produce a merged 7da-format output file that represents the DSN schedule as it would be if the proposal were to be adopted. This 7da output file can be loaded into various DSN scheduling software tools now in use.

Khanampornpan, Teerapat↗