This README.txt file was generated on 5 November 2022 by Claudia Adam ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Swell and magmatic fluxes along the Louisville hotspot chain Data associated with Adam et al. (2022) published in Geochemistry, Geophysics, Geosystems # # Authors: Include contact information for at least the # first author and corresponding author (if not the same), # specifically email address, phone number, and institution. # Contact information for all authors is preferred. # 2. Author Information First Author Contact Information Name: Claudia Adam Institution:Department of Geology, Kansas State University, Address: Manhattan, KS 66506 USA Email:cadam@ksu.edu Corresponding Author Contact Information Name:Claudia Adam Institution: Department of Geology, Kansas State University, Address:Manhattan, KS 66506 USA Email:cadam@ksu.edu Author Contact Information (if applicable) Name: Madison Smith Institution: Department of Geology, Kansas State University, Address: Manhattan, KS 66506 USA Email:madiso6@ksu.edu Author Contact Information (if applicable) Name:Pamela Kempton Institution: Department of Geology, Kansas State University, Address: Manhattan, KS 66506 USA Email:pkempton@ksu.edu Author Contact Information (if applicable) Name:Matthew Brueseke Institution: Department of Geology, Kansas State University, Address: Manhattan, KS 66506 USA Email:brueseke@ksu.edu --------------------- DATA & FILE OVERVIEW --------------------- # # Directory of Files in Dataset: List and define the different # files included in the dataset. This serves as its table of # contents. # Directory of Files A. Filename: 2022GC010568_data_Louisville.dat Short description: The ascii file contains 6 columns Column 1: longitude Column 2: latitude Column 3: distance from active volcanism (in meters) Column 4: volcanism age (in Ma) Column 5: magmatism flux (in m3s-1) Column 6: swell flux (in m3s-1) B. Filename: Short description: C. Filename: Short description: (optional) Additional Notes on File Relationships, Context, or Content: # # File Naming Convention: Define your File Naming Convention # (FNC), the framework used for naming your files systematically # to describe what they contain, which could be combined with the # Directory of Files. # File Naming Convention (if not included above): file name includes a 12-digit identifier (i.e. 22022GC010568) supplied by the journal publishing the paper (Geochemistry, Geophysics, Geosystems) # # Data Description: A data description, dictionary, or codebook # defines the variables and abbreviations used in a dataset. This # information can be included in the README file, in a separate # file, or as part of the data file. If it is in a separate file # or in the data file, explain where this information is located # and ensure that it is accessible without specialized software. # (We recommend using plain text files or tabular plain text CSV # files exported from spreadsheet software.) # ----------------------------------------- DATA DESCRIPTION FOR: [FILENAME] ----------------------------------------- 1. Number of variables: The ascii file 022GC010568_data_Louisville.dat contains 6 columns Column 1: longitude Column 2: latitude Column 3: distance from active volcanism (in meters) Column 4: volcanism age (in Ma) Column 5: magmatism flux (in m3s-1) Column 6: swell flux (in m3s-1) 2. Number of cases/rows: The ascii file 022GC010568_data_Louisville.dat contains 168 rows that provide the previously described variables along the Louisville hotspot chain main axis 3. Missing data codes: Code/symbol Definition Code/symbol Definition N/A 4. Variable List Example. Name: Gender Description: Gender of respondent 1 = Male 2 = Female 3 = Other A. Name: Description: Value labels if appropriate B. Name: Description: Value labels if appropriate -------------------------- METHODOLOGICAL INFORMATION -------------------------- # # Software: If specialized software(s) generated your data or # are necessary to interpret it, please provide for each (if # applicable): software name, version, system requirements, # and developer. # 1. Software-specific information: Name: Version: System Requirements: (if available) Executable URL: Source Repository URL: Developer: Product URL: (optional) Additional Notes: # # Equipment: If specialized equipment generated your data, # please provide for each (if applicable): equipment name, # manufacturer, model, and calibration information. Be sure # to include specialized file format information in the data # dictionary. # 2. Equipment-specific information: Manufacturer: Model: (if applicable) Embedded Software / Firmware Name: Embedded Software / Firmware Version: Additional Notes: # # Dates of Data Collection: List the dates and/or times of # data collection. # 3. Date of data collection (single date, range, approximate date) : README_Template.txt Displaying README_Template.txt.