Finesse Benchmark Database

  Overview

finesse-benchmark-database is a data generation factory for atomic probes in the Finesse benchmark. It generates probes_atomic.jsonl files from Wikimedia Wikipedia datasets, leveraging Hugging Face's datasets library, tokenizers from transformers, and optional PyTorch support. This tool is designed to create high-quality, language-specific probe datasets for benchmarking fine-grained understanding in NLP tasks.… See the full description on the dataset page: https://huggingface.co/datasets/enzoescipy/finesse-benchmark-database.

The NIST Computational Chemistry Comparison and Benchmark Database is a collection of experimental and ab initio thermochemical properties for a selected set of gas-phase molecules. The goals are to provide a benchmark set of experimental data for the evaluation of ab initio computational methods and allow the comparison between different ab initio computational methods for the prediction of gas-phase thermochemical properties. The data files linked to this record are a subset of the experimental data present in the CCCBDB.

The following dataset includes "Active Benchmarks," which are provided to facilitate the identification of City-managed standard benchmarks. Standard benchmarks are for public and private use in establishing a point in space. Note: The benchmarks are referenced to the Chicago City Datum = 0.00, (CCD = 579.88 feet above mean tide New York). The City of Chicago Department of Water Management’s (DWM) Topographic Benchmark is the source of the benchmark information contained in this online database. The information contained in the index card system was compiled by scanning the original cards, then transcribing some of this information to prepare a table and map. Over time, the DWM will contract services to field verify the data and update the index card system and this online database.This dataset was last updated September 2011. Coordinates are estimated. To view map, go to https://data.cityofchicago.org/Buildings/Elevation-Benchmarks-Map/kmt9-pg57 or for PDF map, go to http://cityofchicago.org/content/dam/city/depts/water/supp_info/Benchmarks/BMMap.pdf. Please read the Terms of Use: http://www.cityofchicago.org/city/en/narr/foia/data_disclaimer.html.

Dataset enabling organizations to benchmark their data literacy capability globally.

Dataset Description

This dataset provides a benchmark for automatic data product creation. The task is framed as follows: given a natural language data product request and a corpus of text and tables, the objective is to identify the relevant tables and text documents that should be included in the resulting data product which would useful to the given data product request. The benchmark brings together three variants: HybridQA, TAT-QA, and ConvFinQA, each consisting of:

A corpus… See the full description on the dataset page: https://huggingface.co/datasets/ibm-research/data-product-benchmark.

These are locations that are to be used as an elevation reference and contain the official elevation and last known latitude and longitude.

In the last two decades, alignment analyses have become an important technique in quantitative historical linguistics and dialectology. Phonetic alignment plays a crucial role in the identification of regular sound correspondences and deeper genealogical relations between and within languages and language families. Surprisingly, up to today, there are no easily accessible benchmark data sets for phonetic alignment analyses. Here we present a publicly available database of manually edited phonetic alignments which can serve as a platform for testing and improving the performance of automatic alignment algorithms. The database consists of a great variety of alignments drawn from a large number of different sources. The data is arranged in a such way that typical problems encountered in phonetic alignment analyses (metathesis, diversity of phonetic sequences) are represented and can be directly tested.

Benchmark is a Point FeatureClass representing land-surveyed benchmarks in Cupertino. Benchmarks are stable sites used to provide elevation data. It is primarily used as a reference layer. The layer is updated as needed by the GIS department. Benchmark has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

ID: Unique identifier assigned to the Benchmark type: Integer, length: 4, domain: none

REF_MARK: The reference mark associated with the Benchmark type: String, length: 10, domain: none

ELEV: The elevation of the Benchmark type: Double, length: 8, domain: none

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

Description: A more detailed description of the Benchmark type: String, length: 200, domain: none

Owner: The owner of the Benchmark type: String, length: 10, domain: none

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none Operator:

The user responsible for updating this database type: String, length: 255, domain: OPERATOR

last_edited_date: The date the database row was last updated type: Date, length: 8, domain: none

created_date: The date the database row was initially created type: Date, length: 8, domain: none

VerticalDatum: The vertical datum associated with the Benchmarktype: String, length: 100, domain: none

This feature class is maintained to keep construction, mapping and all city services in and adjacent to the city on the same vertical datum. Thus minimizing mistakes or conflicts in construction or maintenance of the infrastructure of the city. This feature class represents the cities vertical control network which was started approximatley in 1971. The oringinal bench mark used to start the network was a NGS (Nationa Geodetic Survey) monument located in the northwest part of the city (Stapleton Airport/Peoria and Smith). Level loops and runs were added and extended as the city grew. Which also incorporated more NGS monuments. The datum used when the program started was NGVD (National Geodetic Vertical Datum) of 1929 . In June of 2006 the city converted from NGVD 1929 to NAVD (North American Vertical Datum) of 1988 using Corpscon 6.0.1 and the Geoid 2003. This network has been successful and should be maintained until a improved alternative can be utilized.

The Datum of the majority of the City of Sacramento benchmarks is the National Geodetic Vertical Datum of 1929 (NGVD 29) and was based upon a plane datum with reference to four U.S. Government monuments. Some North American Vertical Datum 1988 (NAVD 88) differential baselines have been conducted and the elevations of those benchmarks have been included and identified in this database.VERTICAL CONTROL DISCLAIMER AND GENERAL USE DISCLAIMER City of Sacramento Vertical Control Network, also known as “City of Sacramento Datum” information, is furnished by the Department of Public Works - Engineering Services. It was developed and collected for the purpose of establishing reference points for all survey activities within Sacramento City limits. City of Sacramento makes no warranties, expressed or implied, concerning the accuracy, completeness, reliability, or suitability of this data for any other particular use. Furthermore, the City of Sacramento assumes not liability for any errors, omissions, or inaccuracies associated with the use or misuse of such data. The City of Sacramento tries to keep this information current and accurate.If you find a missing or destroyed City of Sacramento benchmark please contact the City Land Surveyor by calling (916) 808-8777.

ACCEPTABLE USE The City of Sacramento Datum (unadjusted NGVD29) local benchmarks provided here are acceptable as City of Sacramento benchmarks for the purpose of establishing and extending vertical control to design surveys. Reference Sacramento City Code, §1.12.010.All information compiled on this website is provided as a public service and for general informational purposes only. In preparation of these pages, every effort has been made by the Department of Public Works - Engineering Services to offer the most current, correct and concise information possible. The City of Sacramento and its authorized agents and contractors disclaim any responsibility for typographical errors and accuracy of the information that may be contained on the City of Sacramento website; www.cityofsacramento.orgBy accessing the information, data, materials and links contained in the City of Sacramento World Wide Web pages, you hereby agree to and accept the following terms and conditions: The Department of Public Works - Engineering Services shall not be liable for the improper or incorrect use of data, information, materials, links or related graphics described and /or contained herein. The Department of Public Works - Engineering Services shall not be liable for any demand claim, regardless of form or action, arising out of or incident to the posting of information or data on this website; the accessing or use of any information or data on this website; and/or the acts or omissions of any person or entity accessing or using any information from this website.The user hereby recognizes that the information, data, materials and related graphics are dynamic and may change over time without notice. The Department of Public Works - Engineering Services is not responsible for the use or reliance upon this information. There are links and pointers to third party internet websites contained in the City of Sacramento website. These sites linked from the City of Sacramento website are not under the City’s control. The City of Sacramento and its authorized agents and contractors do not assume any responsibility or liability for any information, communications or materials available at such linked sites, or at any link contained in a liked site. Each individual site has its own set of policies about what information is appropriate for public access. User assumes sole responsibility for use of third party links and pointers.

Dummy Dataset for AutoTrain Benchmark

This dataset contains dummy data that's needed to create AutoTrain projects for benchmarks like RAFT. See here for more details.

The Chicago Building Energy Use Benchmarking Ordinance calls on existing municipal, commercial, and residential buildings larger than 50,000 square feet to track whole-building energy use, report to the City annually, and verify data accuracy every three years. The law, which was phased in from 2014-2017, covers less than 1% of Chicago’s buildings, which account for approximately 20% of total energy used by all buildings. For more details, including ordinance text, rules and regulations, and timing, please visit www.CityofChicago.org/EnergyBenchmarking

The ordinance authorizes the City to share property-specific information with the public, beginning with the second year in which a building is required to comply.

The dataset represents self-reported and publicly-available property information by calendar year. Please note that the "Data Year" column refers to the year to which the data apply, not the year in which they were reported. That column and filtered views under "Related Content" can be used to isolate specific years.

Point geometry with attributes displaying geodetic control stations (benchmarks) in East Baton Rouge Parish, Louisiana.

The Benchmark Energy & Geometry Database (BEGDB) collects results of highly accurate quantum mechanics (QM) calculations of molecular structures, energies and properties. These data can serve as benchmarks for testing and parameterization of other computational methods.

Comprehensive performance benchmark database for ColdFusion 2025 with real-world metrics across different workload types, hardware configurations, and JVM tuning scenarios

A total of 12 software defect data sets from NASA were used in this study, where five data sets (part I) including CM1, JM1, KC1, KC2, and PC1 are obtained from PROMISE software engineering repository (http://promise.site.uottawa.ca/SERepository/), the other seven data sets (part II) are obtained from tera-PROMISE Repository (http://openscience.us/repo/defect/mccabehalsted/).

Mountain glaciers are closely coupled to climate processes, ecosystems, and regional water resources. To enhance physical understanding of these connections, the USGS maintains a collection of glacier mass balance and climate data across the western United States and Alaska. In some cases, records of glacier mass balance extend back to the mid-1940s. These data have been incorporated from various sources, primarily original USGS studies, but also including work from the University of Alaska, and the Juneau Icefield Research Program (JIRP). The core of this collection is composed of mass balance data from the USGS Benchmark Glaciers. These five glaciers are Lemon Creek Glacier, AK (1953 -Present), South Cascade Glacier, WA (1958 - Present), Gulkana and Wolverine glaciers, AK (1966 - Present), and Sperry Glacier, MT (2005 - Present). Datasets from each benchmark glacier are composed of, at a minimum, point mass balances, glacier hypsometry, daily temperature and precipitation, geode ...

Los Angeles County Department of Public Works’ Vertical Control Network is composed of more than 1,700 miles (2,720 kilometers) of level runs and comprise nearly 9,000 benchmarks. The basic accuracy of the net is reflected by an indicated field probable error of ± 0.017 feet per mile (4 mm per kilometer) of leveling as determined from conditions of closure. However, because of varying degrees of subsidence and heaving, the true datum is recovered only by obtaining substantial agreement of a number of benchmarks.For each active benchmark, a point representation was created in GIS by locating them based on their description. Parcel data, mile markers, the County Address Management System (CAMS), LARIAC aerials, oblique photos, 2-foot contour lines and/or Google Street View were used in assisting with the location.The creation of the benchmarks in GIS greatly enhances the Vertical Control Network by adding visual context with respect to their representative geospatial locations. With a glance, geospatial patterns can be observed and out-of-place benchmarks can be quickly identified and remapped to the correct location after verification.To facilitate the adjustment, indexing and distribution of adjusted values in the network, the county territory was divided into 33 quads or areas. For identification purposes, each quad was given a name (for example, “Rosemead”, “La Mirada”, “Santa Fe”, and etc.). Index maps, county maps, and other information can be accessed and downloaded on the basis of each of the quads by going to Survey Division’s Benchmark Retrieval System (https://pw.lacounty.gov/sur/benchmark). General adjustments are carried out every 5 to 10 years and the provided elevation data is expected to remain sound during this period. When a quad is adjusted, new elevations will be published and the date of the readjustment will be noted. No historical data is provided, but it can be acquired from Survey Division’s Public Records Counter or via the fee based Optional Technical Research (OTR) program. For general questions, contact:Hector Chang626-458-7038hchang@dpw.lacounty.govFor survey-related questions, contact:Charles Springstun626-320-9896cspring@dpw.lacounty.govThe following resources can be used to obtain historical benchmark data:PUBLIC RECORDS COUNTER900 S. Fremont Ave, 4th FloorAlhambra, CA 918037:00 AM to 5:00 PM Mon – ThursPhone: (626) 458-5137OPTIONAL TECHNICAL RESEARCH (OTR)7:00 AM to 5:00 PM Mon – ThursPhone: (626) 458-5131

Benchmark locations as identified by the Department of Public Works.

Performance comparison on the benchmark noisy database.