Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “CHECK”

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 469 records · Page 26

Regression Verification Using Impact Summaries

Regression verification techniques are used to prove equivalence of syntactically similar programs. Checking equivalence of large programs, however, can be computationally expensive. Existing regression verification techniques rely on abstraction and decomposition techniques to reduce the computational effort of checking equivalence of the entire program. These techniques are sound but not complete. In this work, we propose a novel approach to improve scalability of regression verification by classifying the program behaviors generated during symbolic execution as either impacted or unimpacted. Our technique uses a combination of static analysis and symbolic execution to generate summaries of impacted program behaviors. The impact summaries are then checked for equivalence using an o-the-shelf decision procedure. We prove that our approach is both sound and complete for sequential programs, with respect to the depth bound of symbolic execution. Our evaluation on a set of sequential C artifacts shows that reducing the size of the summaries can help reduce the cost of software equivalence checking. Various reduction, abstraction, and compositional techniques have been developed to help scale software verification techniques to industrial-sized systems. Although such techniques have greatly increased the size and complexity of systems that can be checked, analysis of large software systems remains costly. Regression analysis techniques, e.g., regression testing [16], regression model checking [22], and regression verification [19], restrict the scope of the analysis by leveraging the differences between program versions. These techniques are based on the idea that if code is checked early in development, then subsequent versions can be checked against a prior (checked) version, leveraging the results of the previous analysis to reduce analysis cost of the current version. Regression verification addresses the problem of proving equivalence of closely related program versions [19]. These techniques compare two programs with a large degree of syntactic similarity to prove that portions of one program version are equivalent to the other. Regression verification can be used for guaranteeing backward compatibility, and for showing behavioral equivalence in programs with syntactic differences, e.g., when a program is refactored to improve its performance, maintainability, or readability. Existing regression verification techniques leverage similarities between program versions by using abstraction and decomposition techniques to improve scalability of the analysis [10, 12, 19]. The abstractions and decomposition in the these techniques, e.g., summaries of unchanged code [12] or semantically equivalent methods [19], compute an over-approximation of the program behaviors. The equivalence checking results of these techniques are sound but not complete-they may characterize programs as not functionally equivalent when, in fact, they are equivalent. In this work we describe a novel approach that leverages the impact of the differences between two programs for scaling regression verification. We partition program behaviors of each version into (a) behaviors impacted by the changes and (b) behaviors not impacted (unimpacted) by the changes. Only the impacted program behaviors are used during equivalence checking. We then prove that checking equivalence of the impacted program behaviors is equivalent to checking equivalence of all program behaviors for a given depth bound. In this work we use symbolic execution to generate the program behaviors and leverage control- and data-dependence information to facilitate the partitioning of program behaviors. The impacted program behaviors are termed as impact summaries. The dependence analyses that facilitate the generation of the impact summaries, we believe, could be used in conjunction with other abstraction and decomposition based approaches, [10, 12], as a complementary reduction technique. An evaluation of our regression verification technique shows that our approach is capable of leveraging similarities between program versions to reduce the size of the queries and the time required to check for logical equivalence. The main contributions of this work are: - A regression verification technique to generate impact summaries that can be checked for functional equivalence using an off-the-shelf decision procedure. - A proof that our approach is sound and complete with respect to the depth bound of symbolic execution. - An implementation of our technique using the LLVMcompiler infrastructure, the klee Symbolic Virtual Machine [4], and a variety of Satisfiability Modulo Theory (SMT) solvers, e.g., STP [7] and Z3 [6]. - An empirical evaluation on a set of C artifacts which shows that the use of impact summaries can reduce the cost of regression verification.

Backes, John↗

Patient-specific QA and delivery verification of scanned ion beam at NIRS-HIMAC

Purpose: To evaluate a patient-specific QA program and system for constancy checking of a scanning delivery system developed at the National Institute of Radiological Sciences.Methods: For the patient-specific QA, all the planned beams are recalculated on a water phantom with treatment planning software (TPS). The recalculated dose distributions are compared with the measured distributions using a 2D ionization chamber array at several depths, and evaluated using gamma index analysis with criteria of 3% and 3 mm and a pass rate of 90%. For the constancy check, the authors developed the multiwire proportional chamber (MWPC), which can record the delivered 2D fluence images in a slice-by-slice manner. During irradiation for dosimetric QA with the 2D ionization chamber array and an accordion-type water phantom, the 2D fluence images are recorded using the MWPC in the delivery system. These recorded images are then compared to those taken in the treatment session to check the constancy check. This analysis also employs gamma index analysis using the same criteria as in the patient-specific QA. These patient-specific QA and constancy check evaluations were performed using the data of 122 patients.Results: In the patient-specific QA, the measured dose distributions agreed well with those calculated by the TPS, and the QA criteria were satisfied in all measurements. The additional check of the fluence comparison ensured the constancy of the delivered field during each treatment irradiation.Conclusions: The authors established a patient-specific QA program and additional check of delivery constancy in every treatment session. Fluence comparison is a strong tool for constancy checking of the delivery system.

61 RADIATION PROTECTION AND DOSIMETRY↗

A computer aided treatment event recognition system in radiation therapy

Purpose: To develop an automated system to safeguard radiation therapy treatments by analyzing electronic treatment records and reporting treatment events. Methods: CATERS (Computer Aided Treatment Event Recognition System) was developed to detect treatment events by retrieving and analyzing electronic treatment records. CATERS is designed to make the treatment monitoring process more efficient by automating the search of the electronic record for possible deviations from physician's intention, such as logical inconsistencies as well as aberrant treatment parameters (e.g., beam energy, dose, table position, prescription change, treatment overrides, etc). Over a 5 month period (July 2012–November 2012), physicists were assisted by the CATERS software in conducting normal weekly chart checks with the aims of (a) determining the relative frequency of particular events in the authors’ clinic and (b) incorporating these checks into the CATERS. During this study period, 491 patients were treated at the University of Iowa Hospitals and Clinics for a total of 7692 fractions. Results: All treatment records from the 5 month analysis period were evaluated using all the checks incorporated into CATERS after the training period. About 553 events were detected as being exceptions, although none of them had significant dosimetric impact on patient treatments. These events included every known event type that was discovered during the trial period. A frequency analysis of the events showed that the top three types of detected events were couch position override (3.2%), extra cone beam imaging (1.85%), and significant couch position deviation (1.31%). The significant couch deviation is defined as the number of treatments where couch vertical exceeded two times standard deviation of all couch verticals, or couch lateral/longitudinal exceeded three times standard deviation of all couch laterals and longitudinals. On average, the application takes about 1 s per patient when executed on either a desktop computer or a mobile device. Conclusions: CATERS offers an effective tool to detect and report treatment events. Automation and rapid processing enables electronic record interrogation daily, alerting the medical physicist of deviations potentially days prior to performing weekly check. The output of CATERS could also be utilized as an important input to failure mode and effects analysis.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

SU-F-T-241: Reduction in Planning Errors Via a Process Control Developed Using the Eclipse Scripting API

Purpose: Errors found during initial physics plan checks frequently require replanning and reprinting, resulting decreased departmental efficiency. Additionally, errors may be missed during physics checks, resulting in potential treatment errors or interruption. This work presents a process control created using the Eclipse Scripting API (ESAPI) enabling dosimetrists and physicists to detect potential errors in the Eclipse treatment planning system prior to performing any plan approvals or printing. Methods: Potential failure modes for five categories were generated based on available ESAPI (v11) patient object properties: Images, Contours, Plans, Beams, and Dose. An Eclipse script plugin (PlanCheck) was written in C# to check errors most frequently observed clinically in each of the categories. The PlanCheck algorithms were devised to check technical aspects of plans, such as deliverability (e.g. minimum EDW MUs), in addition to ensuring that policy and procedures relating to planning were being followed. The effect on clinical workflow efficiency was measured by tracking the plan document error rate and plan revision/retirement rates in the Aria database over monthly intervals. Results: The number of potential failure modes the PlanCheck script is currently capable of checking for in the following categories: Images (6), Contours (7), Plans (8), Beams (17), and Dose (4). Prior to implementation of the PlanCheck plugin, the observed error rates in errored plan documents and revised/retired plans in the Aria database was 20% and 22%, respectively. Error rates were seen to decrease gradually over time as adoption of the script improved. Conclusion: A process control created using the Eclipse scripting API enabled plan checks to occur within the planning system, resulting in reduction in error rates and improved efficiency. Future work includes: initiating full FMEA for planning workflow, extending categories to include additional checks outside of ESAPI via Aria database queries, and eventual automated plan checks.

60 APPLIED LIFE SCIENCES↗

Building validation tools for knowledge-based systems

The Expert Systems Validation Associate (EVA), a validation system under development at the Lockheed Artificial Intelligence Center for more than a year, provides a wide range of validation tools to check the correctness, consistency and completeness of a knowledge-based system. A declarative meta-language (higher-order language), is used to create a generic version of EVA to validate applications written in arbitrary expert system shells. The architecture and functionality of EVA are presented. The functionality includes Structure Check, Logic Check, Extended Structure Check (using semantic information), Extended Logic Check, Semantic Check, Omission Check, Rule Refinement, Control Check, Test Case Generation, Error Localization, and Behavior Verification.

Stachowitz, R. A.↗

From Partial to Global Assume-Guarantee Contracts: Compositional Realizability Analysis in FRET

Realizability checking refers to the formal procedure that aims to determine whether an implementation exists, always complying to a set of requirements, regardless of the stimuli provided by the system’s environment. Such a check is essential to ensure that the specification does not allow behavior that can force the system to violate safety constraints. In this paper, we present an approach that decomposes realizability checking into smaller, more tractable problems. More specifically, our approach automatically partitions specifications into sets of non-interfering requirements. We prove that checking whether a specification is realizable reduces to checking that each partition is realizable.We have integrated realizability checking and implemented our decomposition approach within the open-source Formal Requirements ElicitationTool (FRET). A FRET user may check the realizability of a specification monolithically or compositionally. We evaluate our approach by comparing monolithic and compositional checking and showcase the strengths of our decomposition approach on a variety of industrial-level case studies

Anastasia Mavridou↗

SU-F-T-165: Daily QA Analysis for Spot Scanning Beamline

Purpose: The dosimetric results of our daily quality assurance over the last 8 years for discrete pencil beam scanning proton therapy will be presented. Methods: To perform the dosimetric checks, a multi-ion chamber detector is used, which consists of an array of 5 single parallel plate ion chambers that are aligned as a cross separated by 10cm each. The Tracker is snapped into a jig, which is placed on the tabletop. Different amounts of Solid Water buildup are added to shift the dose distribution. The dosimetric checks consist of 3 parts: position check, range check and volume dose check. Results: The average deviation of all position-check data were 0.2±1.3%. For the range check, the average deviation was 0.1%±1.2%, which also corresponds to a range stability of better than 1 mm over all measurements. The volumetric dose output readings were all within ±1% with the exception of 2 occasions when the cable to the dose monitor was being repaired. Conclusion: Morning QA using the Tracker device gives very stable dosimetric readings but is also sensitive to mechanical and output changes in the proton therapy delivery system.

07 ISOTOPE AND RADIATION SOURCES↗

TU-D-201-06: HDR Plan Prechecks Using Eclipse Scripting API

Purpose: Automate brachytherapy treatment plan quality check using Eclipse v13.6 scripting API based on pre-configured rules to minimize human error and maximize efficiency. Methods: The HDR Precheck system is developed based on a rules-driven approach using Eclipse scripting API. This system checks for critical plan parameters like channel length, first source position, source step size and channel mapping. The planned treatment time is verified independently based on analytical methods. For interstitial or SAVI APBI treatment plans, a Patterson-Parker system calculation is performed to verify the planned treatment time. For endobronchial treatments, an analytical formula from TG-59 is used. Acceptable tolerances were defined based on clinical experiences in our department. The system was designed to show PASS/FAIL status levels. Additional information, if necessary, is indicated appropriately in a separate comments field in the user interface. Results: The HDR Precheck system has been developed and tested to verify the treatment plan parameters that are routinely checked by the clinical physicist. The report also serves as a reminder or checklist for the planner to perform any additional critical checks such as applicator digitization or scenarios where the channel mapping was intentionally changed. It is expected to reduce the current manual plan check time from 15 minutes to <1 minute. Conclusion: Automating brachytherapy plan prechecks significantly reduces treatment plan precheck time and reduces human errors. When fully developed, this system will be able to perform TG-43 based second check of the treatment planning system’s dose calculation using random points in the target and critical structures. A histogram will be generated along with tabulated mean and standard deviation values for each structure. A knowledge database will also be developed for Brachyvision plans which will then be used for knowledge-based plan quality checks to further reduce treatment planning errors and increase confidence in the planned treatment.

61 RADIATION PROTECTION AND DOSIMETRY↗

The effectiveness of pretreatment physics plan review for detecting errors in radiation therapy

Purpose: The pretreatment physics plan review is a standard tool for ensuring treatment quality. Studies have shown that the majority of errors in radiation oncology originate in treatment planning, which underscores the importance of the pretreatment physics plan review. This quality assurance measure is fundamentally important and central to the safety of patients and the quality of care that they receive. However, little is known about its effectiveness. The purpose of this study was to analyze reported incidents to quantify the effectiveness of the pretreatment physics plan review with the goal of improving it. Methods: This study analyzed 522 potentially severe or critical near-miss events within an institutional incident learning system collected over a three-year period. Of these 522 events, 356 originated at a workflow point that was prior to the pretreatment physics plan review. The remaining 166 events originated after the pretreatment physics plan review and were not considered in the study. The applicable 356 events were classified into one of the three categories: (1) events detected by the pretreatment physics plan review, (2) events not detected but “potentially detectable” by the physics review, and (3) events “not detectable” by the physics review. Potentially detectable events were further classified by which specific checks performed during the pretreatment physics plan review detected or could have detected the event. For these events, the associated specific check was also evaluated as to the possibility of automating that check given current data structures. For comparison, a similar analysis was carried out on 81 events from the international SAFRON radiation oncology incident learning system. Results: Of the 356 applicable events from the institutional database, 180/356 (51%) were detected or could have been detected by the pretreatment physics plan review. Of these events, 125 actually passed through the physics review; however, only 38% (47/125) were actually detected at the review. Of the 81 events from the SAFRON database, 66/81 (81%) were potentially detectable by the pretreatment physics plan review. From the institutional database, three specific physics checks were particularly effective at detecting events (combined effectiveness of 38%): verifying the isocenter (39/180), verifying DRRs (17/180), and verifying that the plan matched the prescription (12/180). The most effective checks from the SAFRON database were verifying that the plan matched the prescription (13/66) and verifying the field parameters in the record and verify system against those in the plan (23/66). Software-based plan checking systems, if available, would have potential effectiveness of 29% and 64% at detecting events from the institutional and SAFRON databases, respectively. Conclusions: Pretreatment physics plan review is a key safety measure and can detect a high percentage of errors. However, the majority of errors that potentially could have been detected were not detected in this study, indicating the need to improve the pretreatment physics plan review performance. Suggestions for improvement include the automation of specific physics checks performed during the pretreatment physics plan review and the standardization of the review process.

60 APPLIED LIFE SCIENCES↗

Concurrent error detecting codes for arithmetic processors

A method of concurrent error detection for arithmetic processors is described. Low-cost residue codes with check-length l and checkbase m = 2 to the l power - 1 are described for checking arithmetic operations of addition, subtraction, multiplication, division complement, shift, and rotate. Of the three number representations, the signed-magnitude representation is preferred for residue checking. Two methods of residue generation are described: the standard method of using modulo m adders and the method of using a self-testing residue tree. A simple single-bit parity-check code is described for checking the logical operations of XOR, OR, and AND, and also the arithmetic operations of complement, shift, and rotate. For checking complement, shift, and rotate, the single-bit parity-check code is simpler to implement than the residue codes.

Lim, R. S.↗

Finding Feasible Abstract Counter-Examples

A strength of model checking is its ability to automate the detection of subtle system errors and produce traces that exhibit those errors. Given the high computational cost of model checking most researchers advocate the use of aggressive property-preserving abstractions. Unfortunately, the more aggressively a system is abstracted the more infeasible behavior it will have. Thus, while abstraction enables efficient model checking it also threatens the usefulness of model checking as a defect detection tool, since it may be difficult to determine whether a counter-example is feasible and hence worth developer time to analyze. We have explored several strategies for addressing this problem by extending an explicit-state model checker, Java PathFinder (JPF), to search for and analyze counter-examples in the presence of abstractions. We demonstrate that these techniques effectively preserve the defect detection ability of model checking in the presence of aggressive abstraction by applying them to check properties of several abstracted multi-threaded Java programs. These new capabilities are not specific to JPF and can be easily adapted to other model checking frameworks; we describe how this was done for the Bandera toolset.

Pasareanu, Corina S.↗

Verification and Planning Based on Coinductive Logic Programming

Coinduction is a powerful technique for reasoning about unfounded sets, unbounded structures, infinite automata, and interactive computations [6]. Where induction corresponds to least fixed point's semantics, coinduction corresponds to greatest fixed point semantics. Recently coinduction has been incorporated into logic programming and an elegant operational semantics developed for it [11, 12]. This operational semantics is the greatest fix point counterpart of SLD resolution (SLD resolution imparts operational semantics to least fix point based computations) and is termed co- SLD resolution. In co-SLD resolution, a predicate goal p( t) succeeds if it unifies with one of its ancestor calls. In addition, rational infinite terms are allowed as arguments of predicates. Infinite terms are represented as solutions to unification equations and the occurs check is omitted during the unification process. Coinductive Logic Programming (Co-LP) and Co-SLD resolution can be used to elegantly perform model checking and planning. A combined SLD and Co-SLD resolution based LP system forms the common basis for planning, scheduling, verification, model checking, and constraint solving [9, 4]. This is achieved by amalgamating SLD resolution, co-SLD resolution, and constraint logic programming [13] in a single logic programming system. Given that parallelism in logic programs can be implicitly exploited [8], complex, compute-intensive applications (planning, scheduling, model checking, etc.) can be executed in parallel on multi-core machines. Parallel execution can result in speed-ups as well as in larger instances of the problems being solved. In the remainder we elaborate on (i) how planning can be elegantly and efficiently performed under real-time constraints, (ii) how real-time systems can be elegantly and efficiently model- checked, as well as (iii) how hybrid systems can be verified in a combined system with both co-SLD and SLD resolution. Implementations of co-SLD resolution as well as preliminary implementations of the planning and verification applications have been developed [4]. Co-LP and Model Checking: The vast majority of properties that are to be verified can be classified into safety properties and liveness properties. It is well known within model checking that safety properties can be verified by reachability analysis, i.e, if a counter-example to the property exists, it can be finitely determined by enumerating all the reachable states of the Kripke structure.

Bansal, Ajay↗

Fires in P-3 Aircraft Oxygen Systems

Fires in three P3 aircraft oxygen systems have occurred: one in the Royal Australian Air Force (RAAF) in 1984 and two in the U.S. Navy in 1998 and 2003. All three fires started in the aluminum manifold and check valve (MCV) assembly and produced similar damages to the aircraft in which they occurred. This paper discusses a failure analysis conducted by the NASA Johnson Space Center White Sands Test Facility (WSTF) Oxygen Hazards and Testing Team on the 2003 U.S. Navy VP62 fire. It was surmised that the fire started due to heat generated by an oxygen leak past a silicone check valve seal or possibly because of particle impact near the seat of one of the MCV assembly check valves. An additional analysis of fires in several check valve poppet seals from other aircraft is discussed. These burned poppet seals came from P3 oxygen systems that had been serviced at the Naval Air Station (NAS) in Jacksonville following standard fill procedures. It was concluded that these seal fires occurred due to the heat from compression heating, particle impact, or the heat generated by an oxygen leak past the silicone check valve seal. The fact that catastrophic fires did not occur in the case of each check valve seal fire was attributed to the protective nature of the aluminum oxide layer on the check valve poppets. To prevent future fires of this nature, the U.S. and Canadian fleets of P3 aircraft have been retrofitted with MCV assemblies with an upgraded design and more burn-resistant materials.

Stoltzfus, Joel↗

The Quality Control Algorithms Used in the Creation of NASA Kennedy Space Center Lightning Protection System Towers Meteorological Database

An accurate database of meteorological data is essential for designing any aerospace vehicle and for preparing launch commit criteria. Meteorological instrumentation were recently placed on the three Lightning Protection System (LPS) towers at Kennedy Space Center (KSC) launch complex 39B (LC-39B), which provide a unique meteorological dataset existing at the launch complex over an extensive altitude range. Data records of temperature, dew point, relative humidity, wind speed, and wind direction are produced at 40, 78, 116, and 139 m at each tower. The Marshall Space Flight Center Natural Environments Branch (EV44) received an archive that consists of one-minute averaged measurements for the period of record of January 2011 - April 2015. However, before the received database could be used EV44 needed to remove any erroneous data from within the database through a comprehensive quality control (QC) process. The QC process applied to the LPS towers' meteorological data is similar to other QC processes developed by EV44, which were used in the creation of meteorological databases for other towers at KSC. The QC process utilized in this study has been modified specifically for use with the LPS tower database. The QC process first includes a check of each individual sensor. This check includes removing any unrealistic data and checking the temporal consistency of each variable. Next, data from all three sensors at each height are checked against each other, checked against climatology, and checked for sensors that erroneously report a constant value. Then, a vertical consistency check of each variable at each tower is completed. Last, the upwind sensor at each level is selected to minimize the influence of the towers and other structures at LC-39B on the measurements. The selection process for the upwind sensor implemented a study of tower-induced turbulence. This paper describes in detail the QC process, QC results, and the attributes of the LPS towers meteorological database.

Orcutt, John M.↗

SU-E-T-642: Safety Procedures for Error Elimination in Cyberknife Stereotactic Radiosurgery (SRS) and Stereotactic Body Radiation Therapy (SBRT)

Purpose: Cyberknife system is used for providing stereotactic radiosurgery (SRS) and stereotactic body radiation therapy (SBRT) hypofractionation scheme. The whole treatment delivery is based on live imaging of the patient. The minor error made at any stage may bring severe radiation injury to the patient or damage to the system itself. Several safety measures were taken to make the system safer. Methods: The radiation treatment provided thru a 6MV linac attached to Kuka robot (Cyberknife G4, Accuray Inc. Sunnyvale, CA, USA). Several possible errors were identified related to patient alignment, treatment planning, dose delivery and physics quality assurance. During dose delivery, manual and visual checks were introduced to confirm pre and intra-treatment imaging to reduce possible errors. One additional step was introduced to confirm that software tracking-tools had worked correctly with highest possible confidence level. Robotic head move in different orientations over and around the patient body, the rigidity of linac-head cover and other accessories was checked periodically. The vender was alerted when a tiny or bigger piece of equipment needed additional interlocked support. Results: As of our experience treating 525 patients on Cyberknife during the last four years, we saw on and off technical issues. During image acquisition, it was made essential to follow the site-specific imaging protocols. Adequate anatomy was contoured to document the respective doses. Followed by auto-segmentation, manual tweaking was performed on every structure. The calculation box was enclosing the whole image during the final calculation. Every plan was evaluated on slice-by slice basis. To review the whole process, a check list was maintained during the physics 2nd-check. Conclusion: The implementation of manual and visual additional checks introduced along with automated checks for confirmation was found promising in terms of reduction in systematic errors and making the system safer than before.

60 APPLIED LIFE SCIENCES↗

SU-D-BRD-06: Creating a Safety Net for a Fully Automated, Script Driven Electronic Medical Record

Purpose: Demonstrate the effectiveness of in-house software in ensuring EMR workflow efficiency and safety. Methods: A web-based dashboard system (WBDS) was developed to monitor clinical workflow in real time using web technology (WAMP) through ODBC (Open Database Connectivity). Within Mosaiq (Elekta Inc), operational workflow is driven and indicated by Quality Check Lists (QCLs), which is triggered by automation software IQ Scripts (Elekta Inc); QCLs rely on user completion to propagate. The WBDS retrieves data directly from the Mosaig SQL database and tracks clinical events in real time. For example, the necessity of a physics initial chart check can be determined by screening all patients on treatment who have received their first fraction and who have not yet had their first chart check. Monitoring similar “real” events with our in-house software creates a safety net as its propagation does not rely on individual users input. Results: The WBDS monitors the following: patient care workflow (initial consult to end of treatment), daily treatment consistency (scheduling, technique, charges), physics chart checks (initial, EOT, weekly), new starts, missing treatments (>3 warning/>5 fractions, action required), and machine overrides. The WBDS can be launched from any web browser which allows the end user complete transparency and timely information. Since the creation of the dashboards, workflow interruptions due to accidental deletion or completion of QCLs were eliminated. Additionally, all physics chart checks were completed timely. Prompt notifications of treatment record inconsistency and machine overrides have decreased the amount of time between occurrence and execution of corrective action. Conclusion: Our clinical workflow relies primarily on QCLs and IQ Scripts; however, this functionality is not the panacea of safety and efficiency. The WBDS creates a more thorough system of checks to provide a safer and near error-less working environment.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Total metals, carbon, nitrogen & anion concentration data; Slate River & East River floodplains, Crested Butte, CO; May 2022-October 2022

This data package includes processed and undiluted measurements for metal, total carbon, total nitrogen, and anion concentrations from pore water (groundwater) and surface water samples from the Slate River and East River floodplains of Crested Butte, CO, focus field sites for the SLAC Floodplain Hydro-Biogeochemistry SFA. The data was generated as part of the work targeting the overarching research question for the SLAC SFA: How do ubiquitous subsurface interfaces mediate molecular-scale biogeochemical processes and groundwater quality in floodplains and watersheds? Samples were collected between May and October of 2022. These measurements were all recorded at the Arizona Laboratory for Emerging Contaminants (ALEC) at the University of Arizona located in Tucson, AZ. Groundwater samples were extracted from a network of installed rhizon (Rhizosphere Research Products, part no. 19.60.21F, 0.6 micrometer mesh size) and piezometer wells within the river floodplain. All water samples were shaded from sun exposure during extraction from the subsurface and preserved at 4C until measured at ALEC.Analysis by ICP-MS (metals):Measurements for total metals were made on the Agilent 7700x ICP-MS (for total metals) – Agilent Technologies, Santa Clara, CA. The analytical QA/QC protocol was adapted from US EPA Method 200.8 for analysis by ICP-MS. Calibration standards were prepared from multi-element stock solutions (SPEX Certiprep, Metuchen, NJ). Calibration curves include at least 7 points with correlation coefficients > 0.995. The QC protocol includes a continuing calibration blank (CCB), a continuing calibration verification (CCV) solution and at least one quality control sample (QCS) to be analyzed just after calibration and again after every 12 samples and at the completion of the run. The QCS solutions are from an independent source, such as NIST SRM 1643e - Trace elements in water, or QCS solutions from High Purity Standards (Charleston, SC). Acceptable QC responses must be between 90 and 110% of the certified value. Lastly, a suitable internal standard (usually Rh, In, Ga or Ge) is added using on-line addition into the sample line and mixing tee.Analysis by Shimadzu TOC-L (TOC/TN):The TOC-L system is a combustion technique where liquid samples are injected and combusted into CO2 for carbon detection by non-dispersive infrared (NDIR) and NO for detection by chemiluminescence. A calibration curve using five standard solutions between 0.1 and 7 ppm for carbon and 0.05 and 3.5 ppm for nitrogen is made for each type of measurement with a linearity >0.99. All samples, standards, and QC’s are prepared in 24mL scintillation vials that have been baked for 4hrs at 475 Cº and made using RO water (18.2mΩ). QC’s include a calibration blank check (CCB), continuing calibration check (CCC), and a certified reference material check (CRM). All QC’s are within ±10% error and are run before and after each batch of samples. Samples are diluted and rerun if any measurement concentrations are above the highest standard.Analysis by Ion Chromatography (Anions):The instrument used is the Thermo Scientific Dionex ICS-6000 using AS+AG22 column set for anion analysis with sodium carbonate eluent. A calibration curve using five standard solutions between 5 and 250 umol/L is made with a linearity >0.99. Standards and QC’s are prepared in 15mL polypropylene conical tubes, pipetted along with the samples into 1.5mL polypropylene vials. Dilutions are made using RO water (18.2mΩ). QC’s include a calibration blank check (CCB), continuing calibration check (CCC), and a certified reference material check (CRM). All QC’s are within ±10% error and are run before and after each batch of samples. Samples are diluted and rerun if any measurement concentrations are above the highest standard.All files are in csv format.

54 ENVIRONMENTAL SCIENCES↗

Texas International Airlines LOFT program

A line-oriented flight training program which allows the crew to work as a team to solve all problems, abnormal or emergency, within the crew concept. A line-oriented check ride takes place every six months for the pilot as a proficiency check. There are advantages and disadvantages to this program. One disadvantage is that since it is designed as a check-ride, the scenarios must be structured so that the average pilot will complete the check-ride without complication. This system is different from a proficiency check which can be stopped at a problem area so training to proficiency can take place before proceeding with the check.

Sommerville, J.↗