SEARCH · Engineering Papers

Results for “date”

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.

SourceResearch connectionFrom yearThrough year

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

At least 307 records · Page 17

All sources NASA NTRS DOE OSTI

DOE OSTI2024

HarDWR - Harmonized Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on data sourced from WestDAAT - Changed using a Site ID column to identify unique records to using aa combination of Site ID and Allocation ID - Removed the Water Management Area (WMA) column from the harmonized records. The replacement is a separate file which stores the relationship between allocations and WMAs. This allows for allocations to contribute to water right amounts to multiple WMAs during the subsequent cumulative process. - Added a column describing a water rights legal status - Added "Unspecified" was a water source category - Added an acre-foot (AF) column - Added a column for the classification of the right's owner v1.02 - Added a .RData file to the dataset as a convenience for anyone exploring our code. This is an internal file, and the one referenced in analysis scripts as the data objects are already in R data objects. v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description Here we present an updated database of Western U.S. water right records. This database provides consistent unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of seven broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of inter-sectoral water allocation changes though water markets (Grogan et al., *in review*). Specifically, the data were formatted for use as input to a process-based hydrologic model, Water Balance Model (WBM), with a water rights module (Grogan et al., *in review*). While this specific study motivated the development of the database presented here, water management in the U.S. West is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al., 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. West. We produced the water rights database presented here in four main steps: (1) data collection, (2) data quality control, (3) data harmonization, and (4) generation of cumulative water rights curves. Each of steps (1)-(3) had to be completed in order to produce (4), the final product that was used in the modeling exercise in Grogan et al. (*in review*). All data in each step is associated with a spatial unit called a Water Management Area (WMA), which is the unit of water right administration utilized by the state in which the right came from. Steps (2) and (3) required use to make assumptions and interpretation, and to remove records from the raw data collection. We describe each of these assumptions and interpretations below so that other researchers can choose to implement alternative assumptions an interpretation as fits their research aims. Motivation for Changing Data Sources The most significant change has been a switch from collecting the raw water rights directly from each state to using the water rights records presented in WestDAAT, a product of the Water Data Exchange (WaDE) Program under the Western States Water Council (WSWC). One of the main reasons for this is that each state of interest is a member of the WSWC, meaning that WaDE is partially funded by these states, as well as many universities. As WestDAAT is also a database with consistent categorization, it has allowed us to spend less time on data collection and quality control and more time on answering research questions. This has included records from water right sources we had previously not known about when creating v1.0 of this database. The only major downside to utilizing the WestDAAT records as our raw data is that further updates are tied to when WestDAAT is updated, as some states update their public water right records daily. However, as our focus is on cumulative water amounts at the regional scale, it is unlikely most records updates would have a significant effect on our results. The structure of WestDAAT led to several important changes to how HarWR is formatted. The most significant change is that WaDE has calculated a field known as `SiteUUID`, which is a unique identifier for the Point of Diversion (POD), or where the water is drawn from. This separate from `AllocationNativeID`, which is the identifier for the allocation of water, or the amount of water associated with the water right. It should be noted that it is possible for a single site to have multiple allocations associated with it and for an allocation to be able to be extracted from multiple sites. The site-allocation structure has allowed us to adapt a more consistent, and hopefully more realistic, approach in organizing the water right records than we had with HarDWR v1.0. This was incredibly helpful as the raw data from many states had multiple water uses within a single field within a single row of their raw data, and it was not always clear if the first water use was the most important, or simply first alphabetically. WestDAAT has already addressed this data quality issue. Furthermore, with v1.0, when there were multiple records with the same water right ID, we selected the largest volume or flow amount and disregarded the rest. As WestDAAT was already a common structure for disparate data formats, we were better able to identify sites with multiple allocations and, perhaps more importantly, allocations with multiple sites. This is particularly helpful when an allocation has sites which cross WMA boundaries, instead of just assigning the full water amount to a single WMA we are now able to divide the amount of water between the number of relevant WMAs. As it is now possible to identify allocations with water used in multiple WMAs, it is no longer practical to store this information within a single column. Instead the stAllocationToWMATab.csv file was created, which is an allocation by WMA matrix containing the percent Place of Use area overlap with each WMA. We then use this percentage to divide the allocation's flow amount between the given WMAs during the cumulation process to hopefully provide more realistic totals of water use in each area. However, not every state provides areas of water use, so like HarDWR v1.0, a hierarchical decision tree was used to assign each allocation to a WMA. First, if a WMA could be identified based on the allocation ID, then that WMA was used; typically, when available, this applied to the entire state and no further steps were needed. Second was the spatial analysis of Place of Use to WMAs. Third was a spatial analysis of the POD locations to WMAs, with the assumption that allocation's POD is within the WMA it should belong to; if an allocation still had multiple WMAs based on its POD locations, then the allocation's flow amount would be divided equally between all WMAs. The fourth, and final, process was to include water allocations which spatially fell outside of the state WMA boundaries. This could be due to several reasons, such as coordinate errors / imprecision in the POD location, imprecision in the WMA boundaries, or rights attached with features, such as a reservoir, which crosses state boundaries. To include these records, we decided for any POD which was within one kilometer of the state's edge would be assigned to the nearest WMA. Other Changes WestDAAT has Allowed In addition to a more nuanced and consistent method of assigning water right's data to WMAs, there are other benefits gained from using the WestDAAT dataset. Among those is a consistent categorization of a water right's legal status. In HarDWR v1.0, legal status was effectively ignored, which led to many valid concerns about the quality of the database related to the amounts of water the rights allowed to be claimed. The main issue was that rights with legal status' such as "application withdrawn", "non-active", or "cancelled" were included within HarDWR v1.0. These, and other water rights status' which were deemed to not be in use have been removed from this version of the database. Another major change has been the addition of the "unspecified water source category. This is water that can come from either surface water or groundwater, or the source of which is unknown. The addition of this source category brings the total number of categories to three. Due to reviewer feedback, we decided to add the acre-foot (AF) column so that the data may be more applicable to a wider audience. We added the ownerClassification column so that the data may be more applicable to a wider audience. File Descriptions The dataset is a series of various files organized by state sub-directories. In addition, each file begins with the state's name, in case the file is separate from its sub-directory for some reason. After the state name is the text which describes the contents of the file. Here is each file described in detail. Note that st is a placeholder for the state's name. stFullRecords_HarmonizedRights.csv: A file of the complete water records for each state. The column headers for each of this type of file are: state - The name of the state to which the allocations belong to. FIPS - The two digit numeric state ID code. siteID - The site location ID for POD locations. A site may have multiple allocations, which are the actual amount of water which can be drawn. In a simplified hypothetical, a farm stead may have an allocation for "irrigation" and an allocation for "domestic" water use, but the water is drawn from the same pumping equipment. It should be noted that many of the site ID appear to have been added by WaDE, and therefore may not be recognized by a given state's water rights database. allocationID - The allocation ID for the water right. For most states this is the water right ID, and what is recommended to use should a right be looked up on a given state's water rights database. The water amounts associated with these IDs tend to be finer scaled than those associated with siteID. It should be noted that some allocations may be extracted from multiple sites, particularly for larger Places of Use. ownerClassification - A classification of the types of owners for water rights. The most common is `Private` which incorporates a wide range of entities. Several classifications would be grouped into a government category, most of which are for the U.S. Federal Government. These allocations could be listed as "Federal", "United States of America", or as the names of any number of federal agencies. The last major grouping of entities is for "Native American"s. priorityDate - The date we use as the water right priority date for our modeling analysis. This is the legal priority date when it is available. However, for some rights, specifically from California and New Mexico, we used a pseudo priority date (e.g. well completion date or start of well drilling date) when a legal priority date was not available. The most questionable dates come from New Mexico, where the only date associated with certain water right records was the date the allocation was recorded in the database. As the allocation record creation tended to be within a few months of the filing of the application of the water right, from manually double checking the water rights, and our analysis focuses on aggregating water rights on the timescale of years, we determined it was acceptable to use such dates to include as many records as possible. primaryBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories WestDAAT. This column is the original WaDE category for the primary water use at the PoD site. allocationBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories for WestDAAT. This column is the original WaDE category

Economics↗

NASA NTRS1969

Space Flight Handbooks: Volume III. Planetary Flight Handbook: Part 7 - Direct Trajectories to Jupiter, Saturn, Uranus and Neptune. Supplement B. Tabular Trajectory Data for Direct Trajectories to Uranus and Neptune

The trajectory data are presented chronologically and are organized by holding the arrival date constant while varying the Earth departure date in increments of 10 days. Upon completion of the specified range of Earth departure dates, the arrival date is incremented and the range of departure dates is repeated. For long trip times, where the variation of the trajectory parameters is relatively small, the size of the increment of the arrival date is increased. The range of departure and arrival dates and their corresponding increments are given in Table 5-1 for each launch opportunity. The criterion for the selection of these dates is that they encompass the region in which the Earth departure hyperbolic excess speed is less than or equal to 0.65 EMOS. There are two lines of print for each trajectory (departure-date/arrival date pair). In the first line the two left most columns contain the dates of departure and arrival. The next 18 columns of the first line can be divided into three groups: six columns of data related to departure, six columns pertinent to the heliocentric phase of the mission, and six columns related to arrival at the target planet. The second line of print contains, respectively, the Delta V requirements for departure and arrival, the total Delta V requirement, the heliocentric transfer trajectory type, and four parameters defining conditions at arrival. The value computed for the arrival Delta V is for entry into a circular orbit. The radius selected for this orbit, while necessarily somewhat arbitrary, is representative of the broad range of orbit radii which tend to minimize the arrival Delta V for the range of excess speeds between 0.1 and 0.8 EMOS. The value selected for Uranus and Neptune is 3 planet radii. Significant reductions in the computed Delta V can be realized by assuming entry into an elliptical orbit having a periapsis radius equal to the selected circular-orbit radius. The magnitude of the reduction can be determined from Figures 2-6 and 2-8 i n Section 2.

Source record↗

DOE OSTI2023

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review)

Economics↗

DOE OSTI2024

HarDWR - Cumulative Water Rights Curves

Economics↗

DOE OSTI2020

HarDWR - Cumulative Water Rights Curves

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on Harmonized Water Rights Records v2.0 sourced from WestDAAT - Added "Unspecified" was a water source category, and files associated with this category v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description This product an updated version of the database used as input to the WBM model (Grogan et al. in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (2024). This database contains 2,667 individual .csv files, three for each Water Management Area (WMA) in the 11-state region. File Naming WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either "S" for surface water rights, "G" for groundwater rights, or "U" for unspecified. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the [###] unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al. in review) For those whom may be interested in exploring our code more in depth, we are also making available an internal data file for convenience. The file is in .RData format and contains everything described above as well as some minor additional objects used within the code calculating the cumulative curves. For completeness, here is a detailed description of the various objects which can be found within the .RData file: states: A character vector containing the state names for those states in the study region. More importantly, the index of the state name is also the index in which that state's data can be found in the various following list objects. For example, if California is the second index in this object, the data for California will also be in the second index for each accompanying list. wmasRightsPersGrd: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for groundwater. wmasRightsPersSur: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for surface water. wmasRightsPersUnsp: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The data frames in this object are the same as the above described .csv files, specifically for water from an unspecified source. wmasRightsTotsGrd: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for groundwater. This object is provided for convenience to check out original total values, if desired. wmasRightsTotsSur: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for surface water. This object is provided for convenience to check out original total values, if desired. wmasRightsTotsUnsp: A list of nested lists of data frames. Each state has one entry in the top level list and consist of a list with one data frame per WMA. The values in the data frames of this object would be the equivalent to multiplying the CUML column by the sector percentage columns to create the sector total ft3s-1, specifically for water from an unspecified source. This object is provided for convenience to check out original total values, if desired. wmaIDByState: A list of data frames which contain the by state allocation by WMA matrix. There is a matrix for each state in a different data frame within the object.

Economics↗

DOE OSTI2025

SPRUCE Vegetation Phenology in Experimental Plots from PhenoCam Imagery, 2015-2024

This data set consists of PhenoCam data from the SPRUCE experiment from the beginning of whole ecosystem warming (Hanson et al. 2017) in August 2015 through March 31 of 2025 (2015-08-24 to 2025-03-31), with start- and end-of-season phenological transition dates derived through the end of autumn 2024. Digital cameras, or phenocams, installed in each SPRUCE enclosure track seasonal variation in vegetation “greenness”, a proxy for vegetation phenology and associated physiological activity. Three separate regions of interest (ROIs) were defined for each camera field of view, corresponding to different vegetation types and demarcating (1) Picea trees (vegetation type EN, for evergreen needleleaf); (2) Larix trees (vegetation type DN, for deciduous needleleaf); and (3) the mixed shrub layer (vegetation type SH). This data set consists of three sets of data files: (1) 3-day summary product files: One file for each camera and each ROI (i.e. vegetation type), characterizing vegetation color at a 3-day time step. • Contains 36 files in *.csv format inside a compressed (*.zip) file. (2) Transition date file: Estimates “greenness rising” (spring) and “greenness falling” (autumn) transition dates derived from the smoothed daily green chromatic coordinate (GCC) values, for each camera and each ROI (i.e., vegetation type). • Contains one file in *.csv format. (3) Snow flag files: Indicate days with snow on trees or snow on ground for each experimental enclosure. • Contains two files in *.csv format, one for snow on trees and one for snow on ground. This data set consists of two sets of companion files: (1) Accompanying HTML files show the 90th quantiles of the mean GCC plotted together with transition dates for each vegetation type and plot. • Contains three files in HTML format, one for each vegetation type. • One additional file in HTML format with the transition dates plotted for each vegetation type, by year. (2) R files for processing PhenoCam files and flags. • Contains five files in R file(*.R) format and the components of the phenocamr package (Version 1.1.4) used for calculating transition dates for 2015-2024. These are contained in a compressed (*.zip) file. User Note: All imagery is posted in near-real time to the PhenoCam Project web page (https://phenocam.nau.edu), where it is publicly available. Scroll to “spruce” in the Gallery or link directly to the 29 SPRUCE cameras at https://tinyurl.com/sprucecams. This data set is based on the complete camera record from SPRUCE and supersedes all previously released PhenoCam datasets (see Related Data Sets). The estimated transition dates for previously released datasets may differ slightly (in most cases, by ±3 days or less), because following standard PhenoCam processing protocols (Richardson et al. 2018, Scientific Data), smoothing and interpolation, outlier removal, and transition date estimation are always conducted using the full data record.

54 ENVIRONMENTAL SCIENCES↗

NASA NTRS1971

Space Flight Handbooks, Volume 3 - Planetary Flight Handbook. Part 8 - Jupiter Swingby Missions to Saturn, Uranus, Neptune, and Pluto. Supplement - Tabular Trajectory Data

Source record↗

NASA NTRS1981

Planetary Flight Handbook: Part 7 - Direct Trajectories to Jupiter, Saturn, Uranus, and Neptune. Supplement A: Tabular Trajectory for Direct Trajectories to Jupiter and Saturn

Source record↗

NASA NTRS2016

The Potassium-Argon Laser Experiment (karle): In Situ Geochronology for Planetary Missions

Isotopic dating is an essential tool to establish an absolute chronology for geological events. It enables a planet's crystallization history, magmatic evolution, and alteration to be placed into the framework of solar system history. The capability for in situ geochronology will open up the ability for this crucial measurement to be accomplished as part of lander or rover complement. An in situ geochronology package can also complement sample return missions by identifying the most interesting rocks to cache or return to Earth. Appropriate application of in situ dating will enable geochronology on more terrains than can be reached with sample-return missions to the Moon, Mars, asteroids, outer planetary satellites, and other bodies that contain rocky components. The capability of flight instruments to conduct in situ geochronology is called out in the NASA Planetary Science Decadal Survey and the NASA Technology Roadmap as needing development to serve the community's needs. Beagle 2 is the only mission launched to date with the explicit aim to perform in situ K-Ar isotopic dating [1], but it failed to communicate and was lost. The first in situ K-Ar date on Mars, using SAM and APXS measurements on the Cumberland mudstone [2], yielded an age of 4.21 +/- 0.35 Ga and validated the idea of K-Ar dating on other planets, though the Curiosity method is not purpose-built for dating and requires many assumptions that degrade its precision. To get more precise and meaningful ages, multiple groups are developing dedicated in situ dating instruments.

planetary↗

DOE OSTI2024

SPRUCE Vegetation Phenology in Experimental Plots from Phenocam Imagery, 2015-2023

This data set consists of PhenoCam data from the SPRUCE experiment from the beginning of whole ecosystem warming (Hanson et al. 2017) in August 2015 through March 31 of 2024, with start- and end-of-season phenological transition dates derived through the end of autumn 2023. Digital cameras, or phenocams, installed in each SPRUCE enclosure track seasonal variation in vegetation “greenness”, a proxy for vegetation phenology and associated physiological activity. Three separate regions of interest (ROIs) were defined for each camera field of view, corresponding to different vegetation types and demarcating (1) Picea trees (vegetation type EN, for evergreen needleleaf); (2) Larix trees (vegetation type DN, for deciduous needleleaf); and (3) the mixed shrub layer (vegetation type SH). This data set consists of three sets of data files: (1) 3-day summary product files: One file for each camera and each ROI (i.e. vegetation type), characterizing vegetation color at a 3-day time step • Contains 36 files in *.csv format inside a compressed (*.zip) file. (2) Transition date file: Estimates “greenness rising” (spring) and “greenness falling” (autumn) transition dates derived from the smoothed daily green chromatic coordinate (GCC) values, for each camera and each ROI (i.e. vegetation type) • Contains one file in *.csv format (3) Snow flag files: Indicate days with snow on trees or snow on ground for each experimental enclosure • Contains two files in *.csv format, one for snow on trees and one for snow on ground This data set consists of two sets of companion files: (1) Accompanying HTML files show the 90th quantiles of the mean GCC plotted together with transition dates for each vegetation type and plot. • Contains three files in HTML format, one for each vegetation type • One additional file in HTML format with the transition dates plotted for each vegetation type, by year (2) R files for processing Phenocam files and flags. • Contains five files in R file (*.R) format in one compressed (*.zip) file User Note: All imagery is posted in near-real time to the PhenoCam Project web page (http://phenocam.sr.unh.edu/), where it is publicly available. Scroll to “spruce” in the Gallery or link directly to the 29 SPRUCE cameras at https://tinyurl.com/sprucecams. The data reported here are based on the complete camera record from SPRUCE and supersedes the previously released data inclusive of the 2015-2022 data (see Related Data Sets). The estimated transition dates for previously released datasets may differ slightly (in most cases, by ±3 days or less), because following standard PhenoCam processing protocols (Richardson et al. 2018, Scientific Data), smoothing and interpolation, outlier removal, and transition date estimation are always conducted using the full data record.

Spruce and Peatland Responses Under Changing Envir↗

DOE OSTI2026

Identification of drug repurposing candidates for amyotrophic lateral sclerosis using electronic health records: a retrospective cohort study

Amyotrophic lateral sclerosis (ALS) is a progressive neurodegenerative disease with a life expectancy of only 3–5 years and few approved treatments. To identify drug repurposing candidates for the treatment of ALS, we analysed the electronic health records (EHRs) of a large cohort of military veterans with ALS. We analysed the EHRs of individuals in the US Veterans Health Administration (VHA) database who were diagnosed with ALS between Jan 1, 2009 and Dec 31, 2019 to assess medication effects. Individuals without recorded prescriptions after the date of diagnosis were excluded. Two sets of criteria were applied to ascertain exposure. Exposure criteria A were met if the dispense date or the end date of the medication was within 12 months of ALS diagnosis and the end date was at least 6 months after the dispense date. Exposure criteria B were met if there were at least two dispenses within 6 months before diagnosis and 12 months after diagnosis. Propensity score-matched control groups were generated on the basis of confounders included in the EHR, with methodology of potential outcomes used to infer treatment effects. The primary outcome was death. A standard Cox proportional hazards analysis was done to assess association with survival. Survival was defined as the time from diagnosis date recorded in the EHR to death reported in the Department for Veterans Affairs Vital Status File. Follow-up survival time was censored on Dec 31, 2020, for those alive on this date. Downstream protein targets of drugs with clinically significant effects were analysed using the protein–protein interaction networks-based algorithm PathFX. The EHRs of 11 003 individuals with ALS in the VHA database were appropriate for analysis. 162 medications with treatment groups of 30 or more individuals were identified. Among these 162 medications, 27 were associated with statistically significant changes (≥0·1) in the hazard ratio (HR) for death. 18 of the medications were associated with a reduced HR for death (prolonged survival), and nine were associated with an increased HR for death (reduced survival). Drugs associated with reduced HR included HMG-CoA reductase inhibitors (simvastatin, pravastatin, lovastatin, and atorvastatin), PDE5 inhibitors (vardenafil and sildenafil), and α-adrenergic antagonists (tamsulosin and terazosin). The medications associated with an increased HR were drugs used either in the management of clinical features of ALS associated with poor outcomes or in end-of-life care. PathFx analysis identified a complex of proteins interacting with several of the identified drugs. To our knowledge, this analysis is the largest EHR-based study for identifying drug repurposing candidates for ALS. We identified several drugs that warrant further assessment as therapeutic options in ALS, as well as a protein network complex that might serve as a therapeutic target for ALS.

Reimer, Richard J. [Stanford Univ., CA (United Sta↗

DOE OSTI2020

Interpreting and reporting 40 Ar/ 39 Ar geochronologic data

The 40Ar/39Ar dating method is among the most versatile of geochronometers, having the potential to date a broad variety of K-bearing materials spanning from the time of Earth’s formation into the historical realm. Measurements using modern noble-gas mass spectrometers are now producing 40Ar/39Ar dates with analytical uncertainties of ~1%, thereby providing precise time constraints for a wide range of geologic and extraterrestrial processes. Analyses of increasingly smaller subsamples have revealed age dispersion in many materials, including some minerals used as neutron fluence monitors. Accordingly, interpretive strategies are evolving to address observed dispersion in dates from a single sample. Moreover, inferring a geologically meaningful “age” from a measured “date” or set of dates is dependent on the geological problem being addressed and the salient assumptions associated with each set of data. We highlight requirements for collateral information that will better constrain the interpretation of 40Ar/39Ar data sets, including those associated with single-crystal fusion analyses, incremental heating experiments, and in situ analyses of microsampled domains. To ensure the utility and viability of published results, we emphasize previous recommendations for reporting 40Ar/39Ar data and the related essential metadata, with the amendment that data conform to evolving standards of being findable, accessible, interoperable, and reusable (FAIR) by both humans and computers. Our examples provide guidance for the presentation and interpretation of 40 Ar/ 39 Ar dates to maximize their interdisciplinary usage, reproducibility, and longevity.

58 GEOSCIENCES↗

DOE OSTI2026

Daily, 30 m Resolution NDSI Data for the East River Watershed, CO for 2000-2020

This dataset contains daily Normalized Difference Snow Index (NDSI) values at 30 m spatial resolution for the East River watershed in Colorado, USA. The temporal range of these data includes water years 2001-2020. These data were created using the Spatial and Temporal Adaptive Reflectance Fusion Model (STARFM). This model fuses low spatial and high temporal resolution data from MODIS (500 m, daily) with high spatial and low temporal resolution data from Landsat (30 m, 16 days) to create a 30m synthetic daily snow product. This product allows for the analysis of historical snow covered area trends in the East River Watershed at fine spatiotemporal resolutions where it was not available previously. This research was performed as a part of the Department of Energy’s Subsurface Biogeochemical Research Program with the primary intent of better understanding the timing and spatial patterns of water delivery to the Critical Zone in mountain watersheds. Each .zip file contains one "water year" of data (October 1 - September 30; i.e., water year 2010 starts October 1, 2010 and ends September 30, 2011). Each zip file contains the following: STARFM daily Normalized Difference Snow Index (NDSI) fusion data files in GeoTiff format with one layer for each day between Landsat data acquisition dates (i.e., for dates of Landsat acquisition, the Landsat image is included for that date). The study area is located in an area of Landsat path overlap, so Landsat dates acquisitions are every 7-9 days. Landsat NDSI files containing the high spatial (30m), low temporal (7-9 days due to Landsat path overlap) resolution data used as input to STARFM in GeoTiff format with one layer for each day. Dates for which no Landsat data were obtained are included as NoData layers. MODIS NDSI files containing the high temporal (daily), low spatial (500m) resolution data used as input to STARFM in GeoTiff format with one layer for each day. Please note the MODIS data were resampled to 30m pixels for input into the STARFM model. The data have a scale factor of 10,000 and a no data value of -32767. The projection of all datasets is WGS 84 (EPSG: 4326), which has a latitude/longitude based degree resolution of 0.0002694946 X 0.0002694946, and approximates to the 30 m spatial resolution mentioned above. The Layer Index files in .csv format. They contain information for each layer in the above GeoTiff files regarding the corresponding date for each layer, the fraction of pixels in the image that contain valid data (missing data is due to either cloud cover or poor data quality; these values are not percent snow cover). Dates of Landsat overpass are indicated in these files. If no Landsat data were able to be obtained due to cloud cover or lack of Landsat Tier 1 data available on Google Earth Engine, this is also noted.

EARTH SCIENCE > CRYOSPHERE > SNOW/ICE↗

DOE OSTI2023

SPRUCE Vegetation Phenology in Experimental Plots from Phenocam Imagery, 2015-2022

This data set consists of PhenoCam data from the SPRUCE experiment from the beginning of whole ecosystem warming (Hanson et al. 2017) in August 2015 through March 31 of 2023, with start- and end-of-season phenological transition dates derived through the end of autumn 2022. Digital cameras, or phenocams, installed in each SPRUCE enclosure track seasonal variation in vegetation “greenness”, a proxy for vegetation phenology and associated physiological activity. Three separate regions of interest (ROIs) were defined for each camera field of view, corresponding to different vegetation types and demarcating (1) Picea trees (vegetation type EN, for evergreen needleleaf); (2) Larix trees (vegetation type DN, for deciduous needleleaf); and (3) the mixed shrub layer (vegetation type SH). This data set consists of three sets of data files: 3-day summary product files: One file for each camera and each ROI (i.e. vegetation type), characterizing vegetation color at a 3-day time step Contains 35 files in *.csv format inside a compressed (*.zip) file. Transition date file: Estimates “greenness rising” (spring) and “greenness falling” (autumn) transition dates derived from the smoothed daily green chromatic coordinate (GCC) values, for each camera and each ROI (i.e. vegetation type) Contains one file in *.csv format Snow flag files: Indicate days with snow on trees or snow on ground for each experimental enclosure Contains two files in *.csv format, one for snow on trees and one for snow on ground This data set consists of two sets of companion files: Accompanying HTML files show the 90th quantiles of the mean GCC plotted together with transition dates for each vegetation type and plot. Contains three files in HTML format, one for each vegetation type One additional file in HTML format with the transition dates plotted for each vegetation type, by year R files for processing Phenocam files and flags. Contains five files in R file (*.R) format in one compressed (*.zip) file User Note: All imagery is posted in near-real time to the PhenoCam Project web page (http://phenocam.sr.unh.edu/), where it is publicly available. Scroll to “spruce” in the Gallery or link directly to the 29 SPRUCE cameras at https://tinyurl.com/y7z5mau7. The data reported here are based on the complete camera record from SPRUCE and supersedes the previously released phenocam datasets (see Related Data Sets). The estimated transition dates for previously released datasets may differ slightly (in most cases, by ±3 days or less), because following standard PhenoCam processing protocols (Richardson et al. 2018, Scientific Data), smoothing and interpolation, outlier removal, and transition date estimation are always conducted using the full data record.

SPRUCE Experiment, Marcell Experimental Forest, Sp↗

NASA NTRS2012

Influences of the El Nino Southern Oscillation and the Pacific Decadal Oscillation on the Timing of the North American Spring

Detrended, modelled first leaf dates for 856 sites across North America for the period 1900-2008 are used to examine how the El Nino Southern Oscillation (ENSO) and the Pacific Decadal Oscillation (PDO) separately and together might influence the timing of spring. Although spring (mean March through April) ENSO and PDO signals are apparent in first leaf dates, the signals are not statistically significant (at a 95% confidence level (p <0.05)) for most sites. The most significant ENSO/PDO signal in first leaf dates occurs for El Nino and positive PDO conditions. An analysis of the spatial distributions of first leaf dates for separate and combined ENSO/PDO conditions features a northwest-southeast dipole that is significantly (at p <0.05) different than the distributions for neutral conditions. The nature of the teleconnection between Pacific SST's and first leaf dates is evident in comparable composites for detrended sea level pressure (SLP) in the spring months. During positive ENSO/PDO, there is an anomalous flow of warm air from the southwestern US into the northwestern US and an anomalous northeasterly flow of cold air from polar regions into the eastern and southeastern US. These flow patterns are reversed during negative ENSO/PDO. Although the magnitudes of first leaf date departures are not necessarily significantly related to ENSO and PDO, the spatial patterns of departures are significantly related to ENSO and PDO. These significant relations and the long-lived persistence of SSTs provide a potential tool for forecasting the tendencies for first leaf dates to be early or late.

McCabe, Gregory J.↗

NASA NTRS2017

The Potassium-Argon Laser Experiment (KArLE): Design Concepts

The absolute ages of geologic events are fundamental information for understanding the timing and duration of surface processes on planetary bodies. Absolute ages can place a planet's history in the context of the solar system evolution. For example, "when was Mars warm and wet?" is one of the key questions of planetary science. If Mars was warm and wet until 3.7 billion years ago, for instance, it suggests that Mars was still warm and wet when life appeared on Earth. Mars history has been discussed so far based on crater chronology, but the current constraints for Martian chronology models come from the cratering history of the Moon [1]. Moreover, the lunar chronology model itself is fraught with uncertainty because our understanding of lunar chronology is constrained only in a few time periods and itself needs further investigation relating crater-counting ages to absolute ages [2]. Although sample return missions would provide highly accurate radiometric ages of returned samples, they are very expensive and technically challenging. In situ geochronology is highly valuable because they would have larger number of mission opportunities and the capability of iterative measurements for multiple rocks from multiple geologic units. The capability of flight instruments to perform in situ dating is required in the NASA Planetary Science Decadal Survey and the NASA Technology Roadmap. Beagle 2 is the only mission launched to date with the explicit aim to perform in situ potassium-argon (K-Ar) dating [3], but it did not happen because of the communication failure to the spacecraft. The first in situ K-Ar dating on Mars, using SAM and APXS measurements on the Cumberland mudstone [4], yielded an age of 4.21 +/- 0.35 Ga and validated the idea of K-Ar dating on other planets. However, the Curiosity method is not purposebuilt for dating and requires many assumptions that degrade its accuracy. To obtain more accurate and meaningful ages, multiple groups are developing dedicated in situ dating instruments [5-8].

design↗

NASA NTRS2021

Using Remote Sensing to Monitor the Spring Phenology of Acadia National Park Across Elevational Gradients

Greenup dates and their responses to elevation and temperature variations across the mountains of Acadia National Park are monitored using remote sensing data, including Landsat 8 surface reflectances (at a 30-m spatial resolution) and VIIRS reflectances adjusted to a nadir view (gridded at a 500-m spatial resolution), during the 2013–2016 growing seasons. The 30-m resolution provides a better scale for studying the phenology variation across elevational gradients than the 500-m resolution, as greenup dates monitored at 30-m scale have better agreement with leaf-out dates recorded in the field alongside the north–south-oriented hiking trails on three of the park’s tallest mountains (466 m, 418 m, and 380 m), and can provide landcover-specific analysis. The spring phenology responses to temperature and elevation vary among different spatial scales. Greenup dates of Acadia National Park monitored at 30-m scale show a weak advancing trend with higher spring temperature, while greenup dates monitored at 500 m show a weak delaying trend. The species mix within landcover at 30-m scale could weaken the advancing trend detected at field observation level. The landcover mix and elevation variation within 500-m scale could alter the spring phenology response to spring temperature variation. Greenup dates monitored at both 30-m and 500-m scales vary among different elevational zones, aspects, landcovers, and years. However, the relationship between greenup dates and elevation is rather weak.

Yan Liu↗

DOE OSTI2024

Leaf phenology data at The Morton Arboretum Forestry Plots 2019-2023

We are collecting long-term leaf phenology data at The Morton Arboretum to determine seasonal patterns of leaf production in trees. This data on leaf phenology will be integrated with other ongoing data streams to create a connection between above- and below-ground tree processes. This data package contains raw and smooth outputs from phenology data, as well as extracted phenophase dates (i.e., start, peak, and end of season): the raw and smooth outputs from the PhenoCam GUI can be found in the "leafRaw.csv" and "leafSmooth.csv" files, respectively, and the extracted phenophase dates can be found in the "leafPhenophaseDates2019-2023.csv" file. Extracted phenophase dates for evergreen species in 2023 are currently unavailable, and the files will be updated once they are extracted. Additional information on units and other file-level metadata can be found within each data file's respective data dictionary, and metadata for each of the 23 surveyed plots can be found within the "Location_metadata.csv" file. While the "leafRaw.csv" and the "leafSmooth.csv" files contain all data for all species, the "leafPhenophaseDates2019-2023.csv" file currently excludes the dates for evergreen species in 2023. Another version of the file will be added as those dates are extracted.

54 ENVIRONMENTAL SCIENCES↗