Search NASA⌕ Search

Engineering topics

Page, J.

Publications and source records attributed to Page, J..

13 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2025

Initial measurement of reactor antineutrino oscillation at SNO+

The SNO+ collaboration reports its first spectral analysis of long-baseline reactor antineutrino oscillation using 114 tonne-years of data. Fitting the neutrino oscillation probability to the observed energy spectrum yields constraints on the neutrino mass-squared difference Δ$m^2_{21}$. In the ranges allowed by previous measurements, the best-fit Δ$m^2_{21}$ is ($8.85^{+1.10}_{-1.33}$) × 10 -5 eV 2 . This measurement is continuing in the next phases of SNO+ and is expected to surpass the present global precision on Δ$m^2_{21}$ with about three years of data. In the following, we first describe the configuration of the SNO+ detector when it was partially filled with scintillator, and a characterization of the detector response using intrinsic radioactivity. Next, we detail the event selection and expectations for reactor IBDs and (α, n) reactions. Then, we present the results of an energy spectrum analysis using 114 tonne-years of data. We conclude with prospects of future results from the SNO+ detector, which has been operating fully-filled with 780 tonnes of scintillator

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
DOE OSTI2024

Event-by-event direction reconstruction of solar neutrinos in a high light-yield liquid scintillator

The direction of individual B 8 solar neutrinos has been reconstructed using the SNO + liquid scintillator detector. Prompt, directional Cherenkov light was separated from the slower, isotropic scintillation light using time information, and a maximum likelihood method was used to reconstruct the direction of individual scattered electrons. A clear directional signal was observed, correlated with the solar angle. The observation was aided by a period of low primary fluor concentration that resulted in a slower scintillator decay time. This is the first time that event-by-event direction reconstruction in high light-yield liquid scintillator has been demonstrated in a large-scale detector. Published by the American Physical Society 2024

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
DOE OSTI2023

Evidence of Antineutrinos from Distant Reactors Using Pure Water at SNO+

The SNO+ Collaboration reports the first evidence of reactor antineutrinos in a Cherenkov detector. The nearest nuclear reactors are located 240 km away in Ontario, Canada. Here, this analysis uses events with energies lower than in any previous analysis with a large water Cherenkov detector. Two analytical methods are used to distinguish reactor antineutrinos from background events in 190 days of data and yield consistent evidence for antineutrinos with a combined significance of 3.5 σ.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
DOE OSTI2021

Optical calibration of the SNO+ detector in the water phase with deployed sources

SNO+ is a large-scale liquid scintillator experiment with the primary goal of searching for neutrinoless double beta decay, and is located approximately 2 km underground in SNOLAB, Sudbury, Canada. The detector acquired data for two years as a pure water Cherenkov detector, starting in May 2017. During this period, the optical properties of the detector were measured in situ using a deployed light diffusing sphere, with the goal of improving the detector model and the energy response systematic uncertainties. The measured parameters included the water attenuation coefficients, effective attenuation coefficients for the acrylic vessel, and the angular response of the photomultiplier tubes and their surrounding light concentrators, all across different wavelengths. Finally, the calibrated detector model was validated using a deployed tagged gamma source, which showed a 0.6% variation in energy scale across the primary target volume.

47 OTHER INSTRUMENTATION↗
NASA NTRS1984

Evaluating software testing strategies

The strategies of code reading, functional testing, and structural testing are compared in three aspects of software testing: fault detection effectiveness, fault detection cost, and classes of faults detected. The major results are the following: (1) Code readers detected more faults than did those using the other techniques, while functional tester detected more faults than did structural testers; (2) Code readers had a higher fault detection rate than did those using the other methods, while there was no difference between functional testers and structural testers; (3) Subjects testing the abstract data type detected the most faults and had the highest fault detection rate, while individuals testing the database maintainer found the fewest faults and spent the most effort testing; (4) Subjects of intermediate and junior expertise were not different in number or percentage of faults found, fault detection rate, or fault detection effort; (5) subjects of advanced expertise found a greater number of faults than did the others, found a greater percentage of faults than did just those of junior expertise, and were not different from the others in either fault detection rate or effort; and (6) Code readers and functional testers both detected more omission faults and more control faults than did structural testers, while code readers detected more interface faults than did those using the other methods.

Selby, R. W., Jr.↗
NASA NTRS1984

Managers Handbook for Software Development

Methods and aids for the management of software development projects are presented. The recommendations are based on analyses and experiences with flight dynamics software development. The management aspects of organizing the project, producing a development plan, estimation costs, scheduling, staffing, preparing deliverable documents, using management tools, monitoring the project, conducting reviews, auditing, testing, and certifying are described.

Agresti, W.↗
NASA NTRS1984

An approach to software cost estimation

A general procedure for software cost estimation in any environment is outlined. The basic concepts of work and effort estimation are explained, some popular resource estimation models are reviewed, and the accuracy of source estimates is discussed. A software cost prediction procedure based on the experiences of the Software Engineering Laboratory in the flight dynamics area and incorporating management expertise, cost models, and historical data is described. The sources of information and relevant parameters available during each phase of the software life cycle are identified. The methodology suggested incorporates these elements into a customized management tool for software cost prediction. Detailed guidelines for estimation in the flight dynamics environment developed using this methodology are presented.

Mcgarry, F.↗
NASA NTRS1983

Recommended approach to sofware development

A set of guideline for an organized, disciplined approach to software development, based on data collected and studied for 46 flight dynamics software development projects. Methods and practices for each phase of a software development life cycle that starts with requirements analysis and ends with acceptance testing are described; maintenance and operation is not addressed. For each defined life cycle phase, guidelines for the development process and its management, and the products produced and their reviews are presented.

Mcgarry, F. E.↗
NASA NTRS1981

Methodology evaluation: Effects of independent verification and intergration on one class of application

The effects of an independent verification and integration (V and I) methodology on one class of application are described. Resource profiles are discussed. The development environment is reviewed. Seven measures are presented to test the hypothesis that V and I improve the development and product. The V and I methodology provided: (1) a decrease in requirements ambiguities and misinterpretation; (2) no decrease in design errors; (3) no decrease in the cost of correcting errors; (4) a decrease in the cost of system and acceptance testing; (5) an increase in early discovery of errors; (6) no improvement in the quality of software put into operation; and (7) a decrease in productivity and an increase in cost.

Page, J.↗