This formatted dataset (AnalysisDatabaseGBD) originates from raw data files from the Institute of Health Metrics and Evaluation (IHME) Global Burden of Disease Study (GBD2017) affiliated with the University of Washington. We are volunteer collaborators with IHME and not employed by IHME or the University of Washington.

The population weighted GBD2017 data are on male and female cohorts ages 15-69 years including noncommunicable diseases (NCDs), body mass index (BMI), cardiovascular disease (CVD), and other health outcomes and associated dietary, metabolic, and other risk factors. The purpose of creating this population-weighted, formatted database is to explore the univariate and multiple regression correlations of health outcomes with risk factors. Our research hypothesis is that we can successfully model NCDs, BMI, CVD, and other health outcomes with their attributable risks.

These Global Burden of disease data relate to the preprint: The EAT-Lancet Commission Planetary Health Diet compared with Institute of Health Metrics and Evaluation Global Burden of Disease Ecological Data Analysis. The data include the following: 1. Analysis database of population weighted GBD2017 data that includes over 40 health risk factors, noncommunicable disease deaths/100k/year of male and female cohorts ages 15-69 years from 195 countries (the primary outcome variable that includes over 100 types of noncommunicable diseases) and over 20 individual noncommunicable diseases (e.g., ischemic heart disease, colon cancer, etc). 2. A text file to import the analysis database into SAS 3. The SAS code to format the analysis database to be used for analytics 4. SAS code for deriving Tables 1, 2, 3 and Supplementary Tables 5 and 6 5. SAS code for deriving the multiple regression formula in Table 4. 6. SAS code for deriving the multiple regression formula in Table 5 7. SAS code for deriving the multiple regression formula in Supplementary Table 7
8. SAS code for deriving the multiple regression formula in Supplementary Table 8 9. The Excel files that accompanied the above SAS code to produce the tables

For questions, please email davidkcundiff@gmail.com. Thanks.

The simulated synthetic aperture sonar (SAS) data presented here was generated using PoSSM [Johnson and Brown 2018]. The data is suitable for bistatic, coherent signal processing and will form acoustic seafloor imagery. Included in this data package is simulated sonar data in Generic Data Format (GDF) files, a description of the GDF file contents, example SAS imagery, and supporting information about the simulated scenes. In total, there are eleven 60 m x 90 m scenes, labeled scene00 through scene10, with scene00 provided with the scatterers in isolation, i.e. no seafloor texture. This is provided for beamformer testing purposes and should result in an image similar to the one labeled "PoSSM-scene00-scene00-starboard-0.tif" in the Related Data Sets tab. The ten other scenes have varying degrees of model variation as described in "Description_of_Simulated_SAS_Data_Package.pdf". A description of the data and the model is found in the associated document called "Description_of_Simulated_SAS_Data_Package.pdf" and a description of the format in which the raw binary data is stored is found in the related document "PSU_GDF_Format_20240612.pdf". The format description also includes MATLAB code that will effectively parse the data to aid in signal processing and image reconstruction. It is left to the researcher to develop a beamforming algorithm suitable for coherent signal and image processing. Each 60 m x 90 m scene is represented by 4 raw (not beamformed) GDF files, labeled sceneXX-STARBOARD-000000 through 000003. It is possible to beamform smaller scenes from any one of these 4 files, i.e. the four files are combined sequentially to form a 60 m x 90 m image. Also included are comma separated value spreadsheets describing the locations of scatterers and objects of interest within each scene. In addition to the binary GDF data, a beamformed GeoTIFF image and a single-look complex (SLC, science file) data of each scene is provided. The SLC data (science) is stored in the Hierarchical Data Format 5 (https://www.hdfgroup.org/), and appended with ".hdf5" to indicate the HDF5 format. The data are stored as 32-bit real and 32-bit complex values. A viewer is available that provides basic graphing, image display, and directory navigation functions (https://www.hdfgroup.org/downloads/hdfview/). The HDF file contains all the information necessary to reconstruct a synthetic aperture sonar image. All major and contemporary programming languages have library support for encoding/decoding the HDF5 format. Supporting documentation that outlines positions of the seafloor scatterers is included in "Scatterer_Locations_Scene00.csv", while the locations of the objects of interest for scene01-scene10 are included in "Object_Locations_All_Scenes.csv". Portable Network Graphic (PNG) images that plot the location of objects of all the objects of interest in each scene in Along-Track and Cross-Track notation are provided.

The SAS2RAW database is a log of the 28 SAS-2 observation intervals and contains target names, sky coordinates start times and other information for all 13056 photons detected by SAS-2. The original data came from 2 sources. The photon information was obtained from the Event Encyclopedia, and the exposures were derived from the original "Orbit Attitude Live Time" (OALT) tapes stored at NASA/GSFC. These data sets were combined into FITS format images at HEASARC. The images were formed by making the center pixel of a 512 x 512 pixel image correspond to the RA and DEC given in the event file. Each photon's RA and DEC was converted to a relative pixel in the image. This was done by using Aitoff projections. All the raw data from the original SAS-2 binary data files are now stored in 28 FITS files. These images can be accessed and plotted using XIMAGE and other columns of the FITS file extensions can be plotted with the FTOOL FPLOT. This is a service provided by NASA HEASARC .

The Semantic Artist Similarity dataset consists of two datasets of artists entities with their corresponding biography texts, and the list of top-10 most similar artists within the datasets used as ground truth. The dataset is composed by a corpus of 268 artists and a slightly larger one of 2,336 artists, both gathered from Last.fm in March 2015. The former is mapped to the MIREX Audio and Music Similarity evaluation dataset, so that its similarity judgments can be used as ground truth. For the latter corpus we use the similarity between artists as provided by the Last.fm API. For every artist there is a list with the top-10 most related artists. In the MIREX dataset there are 188 artists with at least 10 similar artists, the other 80 artists have less than 10 similar artists. In the Last.fm API dataset all artists have a list of 10 similar artists. There are 4 files in the dataset.mirex_gold_top10.txt and lastfmapi_gold_top10.txt have the top-10 lists of artists for every artist of both datasets. Artists are identified by MusicBrainz ID. The format of the file is one line per artist, with the artist mbid separated by a tab with the list of top-10 related artists identified by their mbid separated by spaces.artist_mbid \t artist_mbid_top10_list_separated_by_spaces mb2uri_mirex and mb2uri_lastfmapi.txt have the list of artists. In each line there are three fields separated by tabs. First field is the MusicBrainz ID, second field is the last.fm name of the artist, and third field is the DBpedia uri.artist_mbid \t lastfm_name \t dbpedia_uri There are also 2 folders in the dataset with the biography texts of each dataset. Each .txt file in the biography folders is named with the MusicBrainz ID of the biographied artist. Biographies were gathered from the Last.fm wiki page of every artist.Using this datasetWe would highly appreciate if scientific publications of works partly based on the Semantic Artist Similarity dataset quote the following publication:Oramas, S., Sordo M., Espinosa-Anke L., & Serra X. (In Press). A Semantic-based Approach for Artist Similarity. 16th International Society for Music Information Retrieval Conference.We are interested in knowing if you find our datasets useful! If you use our dataset please email us at mtg-info@upf.edu and tell us about your research. https://www.upf.edu/web/mtg/semantic-similarity

IntroductionA required step for presenting results of clinical studies is the declaration of participants demographic and baseline characteristics as claimed by the FDAAA 801. The common workflow to accomplish this task is to export the clinical data from the used electronic data capture system and import it into statistical software like SAS software or IBM SPSS. This software requires trained users, who have to implement the analysis individually for each item. These expenditures may become an obstacle for small studies. Objective of this work is to design, implement and evaluate an open source application, called ODM Data Analysis, for the semi-automatic analysis of clinical study data.MethodsThe system requires clinical data in the CDISC Operational Data Model format. After uploading the file, its syntax and data type conformity of the collected data is validated. The completeness of the study data is determined and basic statistics, including illustrative charts for each item, are generated. Datasets from four clinical studies have been used to evaluate the application’s performance and functionality.ResultsThe system is implemented as an open source web application (available at https://odmanalysis.uni-muenster.de) and also provided as Docker image which enables an easy distribution and installation on local systems. Study data is only stored in the application as long as the calculations are performed which is compliant with data protection endeavors. Analysis times are below half an hour, even for larger studies with over 6000 subjects.DiscussionMedical experts have ensured the usefulness of this application to grant an overview of their collected study data for monitoring purposes and to generate descriptive statistics without further user interaction. The semi-automatic analysis has its limitations and cannot replace the complex analysis of statisticians, but it can be used as a starting point for their examination and reporting.

The SAS2RAW database is a log of the 28 SAS-2 observation intervals and contains target names, sky coordinates start times and other information for all 13056 photons detected by SAS-2. The original data came from 2 sources. The photon information was obtained from the Event Encyclopedia, and the exposures were derived from the original "Orbit Attitude Live Time" (OALT) tapes stored at NASA/GSFC. These data sets were combined into FITS format images at HEASARC. The images were formed by making the center pixel of a 512 x 512 pixel image correspond to the RA and DEC given in the event file. Each photon's RA and DEC was converted to a relative pixel in the image. This was done by using Aitoff projections. All the raw data from the original SAS-2 binary data files are now stored in 28 FITS files. These images can be accessed and plotted using XIMAGE and other columns of the FITS file extensions can be plotted with the FTOOL FPLOT. This is a service provided by NASA HEASARC .

Abstract (en): The purpose of this data collection is to provide an official public record of the business of the federal courts. The data originate from 94 district and 12 appellate court offices throughout the United States. Information was obtained at two points in the life of a case: filing and termination. The termination data contain information on both filing and terminations, while the pending data contain only filing information. For the appellate and civil data, the unit of analysis is a single case. The unit of analysis for the criminal data is a single defendant. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed consistency checks.; Standardized missing values.; Checked for undocumented or out-of-range codes.. All federal court cases, 1970-2000. 2012-05-22 All parts are being moved to restricted access and will be available only using the restricted access procedures.2005-04-29 The codebook files in Parts 57, 94, and 95 have undergone minor edits and been incorporated with their respective datasets. The SAS files in Parts 90, 91, 227, and 229-231 have undergone minor edits and been incorporated with their respective datasets. The SPSS files in Parts 92, 93, 226, and 228 have undergone minor edits and been incorporated with their respective datasets. Parts 15-28, 34-56, 61-66, 70-75, 82-89, 96-105, 107, 108, and 115-121 have had identifying information removed from the public use file and restricted data files that still include that information have been created. These parts have had their SPSS, SAS, and PDF codebook files updated to reflect the change. The data, SPSS, and SAS files for Parts 34-37 have been updated from OSIRIS to LRECL format. The codebook files for Parts 109-113 have been updated. The case counts for Parts 61-66 and 71-75 have been corrected in the study description. The LRECL for Parts 82, 100-102, and 105 have been corrected in the study description.2003-04-03 A codebook was created for Part 105, Civil Pending, 1997. Parts 232-233, SAS and SPSS setup files for Civil Data, 1996-1997, were removed from the collection since the civil data files for those years have corresponding SAS and SPSS setup files.2002-04-25 Criminal data files for Parts 109-113 have all been replaced with updated files. The updated files contain Criminal Terminations and Criminal Pending data in one file for the years 1996-2000. Part 114, originally Criminal Pending 2000, has been removed from the study and the 2000 pending data are now included in Part 113.2001-08-13 The following data files were revised to include plaintiff and defendant information: Appellate Terminations, 2000 (Part 107), Appellate Pending, 2000 (Part 108), Civil Terminations, 1996-2000 (Parts 103, 104, 115-117), and Civil Pending, 2000 (Part 118). The corresponding SAS and SPSS setup files and PDF codebooks have also been edited.2001-04-12 Criminal Terminations (Parts 109-113) data for 1996-2000 and Criminal Pending (Part 114) data for 2000 have been added to the data collection, along with corresponding SAS and SPSS setup files and PDF codebooks.2001-03-26 Appellate Terminations (Part 107) and Appellate Pending (Part 108) data for 2000 have been added to the data collection, along with corresponding SAS and SPSS setup files and PDF codebooks.1997-07-16 The data for 18 of the Criminal Data files were matched to the wrong part numbers and names, and now have been corrected. Funding insitution(s): United States Department of Justice. Office of Justice Programs. Bureau of Justice Statistics. (1) Several, but not all, of these record counts include a final blank record. Researchers may want to detect this occurrence and eliminate this record before analysis. (2) In July 1984, a major change in the recording and disposition of an appeal occurred, and several data fields dealing with disposition were restructured or replaced. The new structure more clearly delineates mutually exclusive dispositions. Researchers must exercise care in using these fields for comparisons. (3) In 1992, the Administrative Office of the United States Courts changed the reporting period for statistical data. Up to 1992, the reporting period...

Context

ViC dataset is a collection for implementing a Dynamic Spectrum Access(DSA) system testbed in the CBRS band in the USA. This data is a DSA system which consists of a 2-tier user : Incident user: generating a chirp signal with a Radar system, Primary user: LTE-TDD signal with a CBSD base station system, and corresponds to signal waveforms in the band 3.55-3.56 GHz (Ch1), 3.56-3.57 GHz (Ch2) respectively. There are a total of 12 classes, excluding the assumption that two of the 16 cases are used by CBSD base stations, depending on the presence or absence of two users in two channels. The labels of each data have the following meanings :

0000 (0) : All off 0001 (1) : Ch2 - Radar on 0010 (2) : Ch2 - LTE on 0011 (3) : Ch2 – LTE, Radar on 0100 (4) : Ch1 – Radar on 0101 (5) : Ch1 – Radar on / Ch2 – Radar on 0110 (6) : Ch1 – Radar on /Ch2 – LTE on 0111 (7) : Ch1 – Radar on / Ch2 – LTE, Radar on 1000 (8) : Ch1 – LTE on 1001 (9) : Ch1 – LTE on / Ch2 – Radar on (X) 1010 (10) : Ch1 – LTE on / Ch2 – LTE on (X) 1011 (11) : Ch1 – LTE on / Ch2 – LTE, Radar on 1100 (12) : Ch1 – LTE, Radar on 1101 (13) : Ch1 – LTE, Radar on / Ch2 – Radar on (X) 1110 (14) : Ch1 – LTE, Radar on / Ch2 – LTE on (X) 1111 (15) : Ch1 – LTE, Radar on / Ch2 – LTE, Radar on

Content

This dataset has a total of 7 types consisting of one raw dataset expressed in two extensions, 4 processed datasets processed in different ways, and a label. Except for one of the datasets, all are Python version of numpy files, and the other is a csv file.

(Raw) The raw data is a IQ data generated from testbeds created by imitating the SAS system of CBRS in the United States. In the testbeds, the primary user was made using the LabView communication tool and the USRP antenna (Radar), and the secondary user was made by manufacturing the CBSD base station. This has both csv format and numpy format exist.

(Processed) All of these data except one are normalized to values between 0 and 255 and consist of spectrogram, scalogram, and IQ data. The other one is a spectrogram dataset which is not normalized. They are measured between 250us. In the case of spectrograms and scalograms, the figure formed at 3.56 GHz to 3.57 GHz corresponds to channel 1, and at 3.55 GHz to 3.56 GHz corresponds to channel 2. Among them, signals transmitted from the CBSD base station are output in the form of LTE-TDD signals, and signals transmitted from the Radar system are output in the form of Chirp signals.

(Label) All of the above five data share one label. This label has a numpy format.

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. The School Health Center Healthy Adolescent Relationship Program (SHARP) was a school health center (SHC) provider-delivered multi-level intervention to reduce adolescent relationship abuse (ARA) among adolescents ages 14-19 seeking care in SHCs. This study tested the effectiveness of a brief relationship abuse education and counseling intervention in SHCs. The SHARP intervention consisted of three levels of integrated intervention: A brief clinical intervention on healthy and unhealthy relationships for SHC (cisgender and transgender) male and female patients delivered by SHC providers during all clinic visits (evaluated via client pre- and post-surveys and chart review) Development of an ARA-informed SHC staff and clinic environment (evaluated via provider pre and post-training surveys and interviews) SHC-based youth-led outreach activities within the school to promote healthy relationships and improve student safety (evaluated by focus groups with youth leaders and measures of school climate) The collection consists of: 3 SAS data files sharp_abuse_data_archive.sas7bdat (n=1,011; 272 variables) sharp_blt2exit_long_data_archive.sas7bdat (n=1,949; 259 variables) sharp_chart_data_archive_icpsr.sas7bdat (n=936; 24 variables) 2 Stata data files SHARP_Provider Immediate Post_0829 and 0905 training_final-ICPSR.dta (n=38; 21 variables) SHARP_Provider Pre and Followup_final.dta-ICPSR.dta (n=66; 102 variables) 5 SAS syntax files NIJ SHARP - Analyses.sas NIJ SHARP - DataMgmt_Final.sas NIJ SHARP - Formats.sas SHARP - Chart Extraction Data-MASKED.sas SHARP - Chart Extraction Formats.sas 3 Stata syntax files code-for-SHARP-dating-violence-analyses-deidentified-MASKED.do SHARP_Provider Data to Archive-MASKED.do SHARP-analyses-deidentified-MASKED.do 3 PI provided codebooks SHARP Codebook_Client Chart Data.xlsx (1 worksheet) SHARP Codebook_Client Survey Data.xlsx (3 worksheets) SHARP Codebook_Provider Survey Data.xlsx (1 worksheet) For confidentiality reasons, qualitative data from focus groups are not currently available. Focus groups were conducted with each student outreach team following the conclusion of data collection. Discussions focused on awareness about ARA, the school-wide campaign, using the SHC as a resource, and what else can be done to prevent ARA in schools.

Abstract (en): This study is part of a time-series collection of national surveys fielded continuously since 1952. The election studies are designed to present data on Americans' social backgrounds, enduring political predispositions, social and political values, perceptions and evaluations of groups and candidates, opinions on questions of public policy, and participation in political life. A Black supplement of 263 respondents, who were asked the same questions that were administered to the national cross-section sample, is included with the national cross-section of 1,571 respondents. In addition to the usual content, the study contains data on opinions about the Supreme Court, political knowledge, and further information concerning racial issues. Voter validation data have been included as an integral part of the election study, providing objective information from registration and voting records or from respondents' past voting behavior. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed consistency checks.; Standardized missing values.; Performed recodes and/or calculated derived variables.; Checked for undocumented or out-of-range codes.. United States citizens of voting age living in private households in the continental United States. A representative cross-section sample, consisting of 1,571 respondents, plus a Black supplement sample of 263 respondents. 2015-11-10 The study metadata was updated.1999-12-14 The data for this study are now available in SAS transport and SPSS export formats, in addition to the ASCII data file. Variables in the dataset have been renumbered to the following format: 2-digit (or 2-character) year prefix + 4 digits + [optional] 1-character suffix. Dataset ID and version variables have also been added. In addition, SAS and SPSS data definition statements have been created for this collection, and the data collection instruments are now available as a PDF file. face-to-face interview, telephone interviewThe SAS transport file was created using the SAS CPORT procedure.

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed.This study sought to examine any major changes in schools in the past two years as an evaluation of the Safe and Civil Schools Initiative. Students, faculty, and administrators were asked questions on topics including school safety, climate, and the discipline process.This collection includes 6 SAS data files: "psja_schools.sas7bdat" with 66 variables and 15 cases, "psja_schools_v01.sas7bdat" with 104 variables and 15 cases, "psja_staff.sas7bdat" with 39 variables and 2,921 cases, "psja_staff_v01.sas7bdat" with 202 variables and 2,398 cases, "psja_students.sas7bdat" with 97 variables and 4,382 cases, and "psja_students_v01.sas7bdat" with 332 variables and 4,267 cases. Additionally, the collection includes 1 SAS formats catalog "formats.sas7bcat", and 10 SAS syntax files.

This database is a compilation of nightside, high-latitude ionosphere meso-scale flow characteristics built on those used in Gabrielse et al. 2018. It is the most complete version. If you would like to use the database, please contact Christine Gabrielse (cgabrielse@ucla.edu, cgabrielse@gmail.com, and/or christine.gabrielse@aero.org). Depending on how the results are used, the main authors request co-authorship on publications that utilize this database.

The methodology and selection criteria can be found in Gabrielse et al. 2018.

The following list describes the columns in each data file labeled, ***_FLOW-DATA-PCvsAO_YYYY.txt The first three letters (RNK or SAS) designate the station used (Rankin Inlet or Saskatoon). Files named ***_FLOW-DATA-PCvsAO_poleward_YYYY.txt are for poleward-directed flows. Each text file is for a different year (YYYY).

AO=Auroral Oval for Rankin Inlet; equatorward of the auroral oval for Saskatoon (not used) PC=Polar Cap for Rankin Inlet; Auroral Oval for Saskatoon

(Note: the data files for RNK and SAS have the same format, so the PC designator means flows above the pertinent boundary (polar cap boundary for RNK, auroral oval equatorward boundary at SAS) and the AO designator means flows below the pertinent boundary.)

 time [YYYYMMDDhhmmss]
 flagAO [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed]
 flagPC [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed]
 FWHMavg_AO [degrees]
 FWHMkmavg_AO=[km]
 longtestranges=[ignore]
 Velmaxavg_AO=[m/s, actual average of max V in each range gate used]
 VelmaxFITavg_AO=[m/s, determined from the Gaussian fits]
 FWHMavg_PC=[degrees]
 FWHMkmavg_PC=[km]
 Velmaxavg_PC=[m/s, actual average of max V in each range gate used]
 VelmaxFITavg_PC=[m/s, determined from the Gaussian fits]

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; For the bearings/orientation, see the orientation text files. The following four variables were calculated in a first step but are not those used in the paper. They were not found with the strict selection criteria. Please do not use. mbearingAO=[degrees in magnetic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] mbearingPC=[degrees in magnetic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)]
gbearingAO=[degrees in geographic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] gbearingPC=[degrees in geographic coordinates, a negative value is South of East (clockwise from East), a positive value is North of East (CC)] ;;;;;;;;;;;;;;; minlatAO=[degrees, min geographic latitude of the flow] maxlatAO=[degrees, max geographic latitude of the flow] minlatPC=[degrees, min geographic latitude of the flow] maxlatPC=[degrees, max geographic latitude of the flow] mltAO=[degrees (MLT)] mltPC=[degrees (MLT)] AE=[nT] AL=[nT] SYMH=[nT] IMFBy=[nT] IMFBz=[nT]
F107=[sfu]

The following list describes the columns in each data file labeled, ***_orientation_YYYY.txt Files named ***_orientation_poleward_YYYY.txt are for poleward-directed flows. Each text file is for a different year (YYYY). The orientation was determined when enough bearings between RGs were available. See Gabrielse et al. [2018] for description. https://doi.org/10.1029/2018JA025440 AO=auroral oval PC=polar cap

 time [YYYYMMDDhhmmss]
 mbearingAO [degrees clockwise from magnetic North]
 gbearingAO [degrees clockwise from geographic North]
 mbearingPC [degrees clockwise from magnetic North]
 gbearingPC [degrees clockwise from geographic North]

The following list describes the columns in each data file labeled, _SPEC_TEST__noRG1-2.txt

 time [YYYYMMDDhhmmss]
 RG [the range gate number at which the polar cap boundary was determined at RNK, or the auroral oval's equatorial boundary at SAS]

This SAS macro generates childhood mortality estimates (neonatal, post-neonatal, infant (1q0), child (4q1) and under-five (5q0) mortality) and standard errors based on birth histories reported by women during a household survey. We have made the SAS macro flexible enough to accommodate a range of calculation specifications including multi-stage sampling frames, and simple random samples or censuses. Childhood mortality rates are the component death probabilities of dying before a specific age. This SAS macro is based on a macro built by Keith Purvis at MeasureDHS. His method is described in Estimating Sampling Errors of Means, Total Fertility, and Childhood Mortality Rates Using SAS (www.measuredhs.com/pubs/pdf/OD17/OD17.pdf, section 4). More information about Childhood Mortality Estimation can also be found in the Guide to DHS Statistics (www.measuredhs.com/pubs/pdf/DHSG1/Guide_DHS_Statistics.pdf, page 93). We allow the user to specify whether childhood mortality calculations should be based on 5 or 10 years of birth histories, when the birth history window ends, and how to handle age of death with it is reported in whole months (rather than days). The user can also calculate mortality rates within sub-populations, and take account of a complex survey design (unequal probability and cluster samples). Finally, this SAS program is designed to read data in a number of different formats.

InfoGroup’s Historical Business Backfile consists of geo-coded records of millions of US businesses and other organizations that contain basic information on each entity, such as: contact information, industry description, annual revenues, number of employees, year established, and other data. Each annual file consists of a “snapshot” of InfoGroup’s data as of the last day of each year, creating a time series of data 1997-2019. Access is restricted to current Harvard University community members. Use of Infogroup US Historical Business Data is subject to the terms and conditions of a license agreement (effective March 16, 2016) between Harvard and Infogroup Inc. and subject to applicable laws. Most data files are available in either .csv or .sas format. All data files are compressed into an archive in .gz, or GZIP, format. Extraction software such as 7-Zip is required to unzip these archives.

Integrated Postsecondary Education Data System (IPEDS) Complete Data Files from 1980 to 2023. Includes data file, STATA data file, SPSS program, SAS program, STATA program, and dictionary. All years compressed into one .zip file due to storage limitations.Updated on 2/14/2025 to add Microsoft Access Database files.From IPEDS Complete Data File Help Page (https://nces.ed.gov/Ipeds/help/complete-data-files):Choose the file to download by reading the description in the available titles. Then, click on the link in that row corresponding to the column header of the type of file/information desired to download.To download and view the survey files in basic CSV format use the main download link in the Data File column.For files compatible with the Stata statistical software package, use the alternate download link in the Stata Data File column.To download files with the SPSS, SAS, or STATA (.do) file extension for use with statistical software packages, use the download link in the Programs column.To download the data Dictionary for the selected file, click on the corresponding link in the far right column of the screen. The data dictionary serves as a reference for using and interpreting the data within a particular survey file. This includes the names, definitions, and formatting conventions for each table, field, and data element within the file, important business rules, and information on any relationships to other IPEDS data.For statistical read programs to work properly, both the data file and the corresponding read program file must be downloaded to the same subdirectory on the computer’s hard drive. Download the data file first; then click on the corresponding link in the Programs column to download the desired read program file to the same subdirectory.When viewing downloaded survey files, categorical variables are identified using codes instead of labels. Labels for these variables are available in both the data read program files and data dictionary for each file; however, for files that automatically incorporate this information you will need to select the Custom Data Files option.

Abstract (en): This data collection provides comparable measures of state appellate and trial court caseloads by type of case for the 50 states, the District of Columbia, and Puerto Rico. Court caseloads are tabulated according to generic reporting categories developed by the Court Statistics Project Committee of the Conference of State Court Administrators. These categories describe differences in the unit of count and the point of count when compiling each court's caseload. Major areas of investigation include (1) case filings in state appellate and trial courts, (2) case processing and dispositions in state appellate and trial courts, and (3) appellate opinions. Within each of these areas of state government investigation, cases are separated by main case type, including civil cases, capital punishment cases, other criminal cases, juvenile cases, and administrative agency appeals. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Performed consistency checks.; Checked for undocumented or out-of-range codes.. State appellate and trial court cases in the United States. 2005-11-04 On 2005-03-14 new files were added to one or more datasets. These files included additional setup files as well as one or more of the following: SAS program, SAS transport, SPSS portable, and Stata system files. The metadata record was revised 2005-11-04 to reflect these additions.2003-08-27 Part 45, Appellate Court Data, 2001, and Part 46, Trial Court Data, 2001, have been added to the data collection, along with corresponding SAS and SPSS data definition statements and PDF codebooks.2002-08-13 Part 43, Appellate Court Data, 2000, and Part 44, Trial Court Data, 2000, have been added to the data collection, along with corresponding SAS and SPSS data definition statements and PDF codebooks.2001-10-31 Part 41, Appellate Court Data, 1999, and Part 42, Trial Court Data, 1999, have been added to the data collection, along with corresponding SAS and SPSS data definition statements and PDF codebooks.2000-03-23 Part 39, Appellate Court Data, 1998, and Part 40, Trial Court Data, 1998, have been added to the data collection, along with corresponding SAS and SPSS data definition statements and PDF codebooks.1999-07-16 Part 37, Appellate Court Data, 1997, and Part 38, Trial Court Data, 1997, have been added to the data collection, along with corresponding SAS and SPSS data definition statements and PDF codebooks. Funding insitution(s): State Justice Institute (SJI-91-N-007-001-1). United States Department of Justice. Office of Justice Programs. Bureau of Justice Statistics. The Court Statistics Project Web page is: http://www.ncsconline.org/D_Research/csp/CSP_Main_Page.html.A user guide containing court codes and variable descriptions for the 1987 data and the codebooks for the 1995-2001 data are provided as Portable Document Format (PDF) files, and the codebooks for the 1988-1992 data are available in both ASCII text and PDF versions.

Sabotaging milkweed by monarch caterpillars (Danaus plexippus) is a famous textbook example of disarming plant defence. By severing leaf veins, monarchs are thought to prevent the flow of toxic latex to their feeding site. Here, we show that sabotaging by monarch caterpillars is not only an avoidance strategy. While young caterpillars appear to avoid latex, late-instar caterpillars actively ingest exuding latex, presumably to increase sequestration of cardenolides used for defence against predators. Comparisons with caterpillars of the related but non-sequestering common crow butterfly (Euploea core) revealed three lines of evidence supporting our hypothesis. First, monarch caterpillars sabotage inconsistently and therefore the behaviour is not obligatory to feed on milkweed, whereas sabotaging precedes each feeding event in Euploea caterpillars. Second, monarch caterpillars shift their behaviour from latex avoidance in younger to eager drinking in later stages, whereas Euploea caterpil..., , , Readme for the statistical documentation for the publication: Monarchs sabotage milkweed to acquire toxins, not to disarm plant defense Authors: Anja Betz, Robert Bischoff, Georg Petschenka

For the statistical documentation, we provide the following files: This readme gives a brief outline of the different files and data provided in the statistical documentation Subfolders for each experiment containing

• Excel files with just the data, SAS code files for analysis of each dataset with comments SAS dataset files (sas7bdat) a data dictionary.txt that defines all variables of all datasets

Disclaimer: Excel automatically formats numbers. We do not take any responsibility for automatic formatting of the numbers by Excel. This might lead to different results, if the Excel files are used for analysis. The sas7bdat files, or data at the start of the individual sas-analysis files should be resistant to automatic formatting, so we suggest using them for analysis.

The datasets co...

Abstract (en): Roll call voting records for both chambers of the United States Congress through the second session of the 105th Congress are presented in this data collection. Each data file in the collection contains information for one chamber of a single Congress. The units of analysis in each part are the individual members of Congress. Each record contains a member's voting action on every roll call vote taken during that Congress, along with variables that identify the member (e.g., name, party, state, district, uniform ICPSR member number, and most recent means of attaining office). In addition, the codebook provides descriptive information for each roll call, including the date of the vote, outcome in terms of nays and yeas, name of initiator, the relevant bill or resolution number, and a synopsis of the issue. ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection: Checked for undocumented or out-of-range codes.. All roll call votes in the United States Congress. 2010-05-06 Data for the 105th Congress, House, and Senate (Parts 209-210), have been added to this collection, along with the standard ICPSR full product suite of files.2004-06-17 Variables were added to Part 110, Senate (55th Congress), and data within certain variables were corrected. SAS and SPSS data definition statements and the codebook have been modified to reflect these changes.2001-08-24 Logical record length data for the 8th session of the Senate, Part 16, is being made available along with SAS and SPSS data definition statements. The codebook has been modified to reflect these changes.1998-12-17 Data for the 104th Congress, House and Senate (Parts 207-208), have been added to this collection, along with corresponding machine-readable documentation and SAS and SPSS data definition statements.1997-02-24 Data for the 102nd and 103rd Congresses, House, and Senate (Parts 203-206) have been added to this collection, along with corresponding machine-readable documentation and SAS and SPSS data definition statements. The technical format has been standardized for all Congresses. Each file contains data for one chamber of a single Congress.

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. This study sought to: (1) document the spectrum of injuries and injury characteristics observed among physically-abused older adults reported to Adult Protective Services (APS) and compare those findings to injuries found among non-abused older adults, (2) identify observable injury characteristics and abuse circumstances that healthcare providers, law enforcement and prosecutors consider to be key forensic markers of physical abuse, (3) document information and evidence integral for achieving successful criminal prosecution, and (4) describe approaches that community-based frontline workers can employ to better document evidence of physical abuse. The data included in this collection were collected under a National Institute of Justice-funded project that sought to document the spectrum and characteristics of injuries observed among physically abused, community-dwelling APS clients. The collection includes two SAS datasets: injury.sas7bdat (with 47 variables and 403 cases) and subjectleveldata.sas7bdat (with 122 variables and 165 cases); and three SAS System Program Files: analysis-code-v1.sas, cleaned-injury-datasets-v1.sas, and formats.sas. Demographic variables in the collection are in the subjectleveldata.sas7bdat dataset, and include age, year of birth, gender, race, language, and level of education.

These data are part of NACJD's Fast Track Release and are distributed as they were received from the data depositor. The files have been zipped by NACJD for release, but not checked or processed except for the removal of direct identifiers. Users should refer to the accompanying readme file for a brief description of the files available with this collection and consult the investigator(s) if further information is needed. Teenage adolescent females residing in Baltimore, Maryland who were involved in a relationship with a history of violence were sought after to participate in this research study. Respondents were interviewed and then followed through daily diary entries for several months. The aim of the research was to understand the context regarding teen dating violence (TDV). Prior research on relationship context has not focused on minority populations; therefore, the focus of this project was urban, predominantly African American females. The available data in this collection includes three SAS (.sas7bdat) files and a single SAS formats file that contains variable and value label information for all three data files. The three data files are:

final_baseline.sas7bdat (157 cases / 252 variables) final_partnergrid.sas7bdat (156 cases / 76 variables) hart_final_sas7bdata (7004 cases / 23 variables)