Atmospheric Radiation Measurement program climate research facility operations quarterly report January 1 - March 31, 2008.
Bibliographic record
Abstract
Individual raw data streams from instrumentation at the Atmospheric Radiation Measurement (ARM) Program Climate Research Facility (ACRF) fixed and mobile sites are collected and sent to the Data Management Facility (DMF) at Pacific Northwest National Laboratory (PNNL) for processing in near real time. Raw and processed data are then sent daily to the ACRF Archive, where they are made available to users. For each instrument, we calculate the ratio of the actual number of data records received daily at the Archive to the expected number of data records. The results are tabulated by (1) individual data stream, site, and month for the current year and (2) site and fiscal year (FY) dating back to 1998. Table 1 shows the accumulated maximum operation time (planned uptime), actual hours of operation, and variance (unplanned downtime) for the period January 1 - March 31, 2008, for the fixed sites. The AMF is being deployed to China and is not in operation this quarter. The second quarter comprises a total of 2,184 hours. The average as well as the individual site values exceeded our goal this quarter. The Site Access Request System is a web-based database used to track visitors to the fixed and mobile sites, all of which have facilities that can be visited. The NSA locale has the Barrow and Atqasuk sites. The SGP site has a central facility, 23 extended facilities, 4 boundary facilities, and 3 intermediate facilities. The TWP locale has the Manus, Nauru, and Darwin sites. FKB represents the AMF statistics for the Haselbach, Germany, past deployment in 2007. NIM represents the AMF statistics for the Niamey, Niger, Africa, past deployment in 2006. PYE represents just the AMF Archive statistics for the Point Reyes, California, past deployment in 2005. In addition, users who do not want to wait for data to be provided through the ACRF Archive can request a research account on the local site data system. The seven computers for the research accounts are located at the Barrow and Atqasuk sites; the SGP central facility; the TWP Manus, Nauru, and Darwin sites; and the DMF at PNNL. In addition, the ACRF serves as a data repository for a long-term Arctic atmospheric observatory in Eureka, Canada (80 degrees 05 minutes N, 86 degrees 43 minutes W) as part of the multiagency Study of Environmental Arctic Change (SEARCH) Program. NOAA began providing instruments for the site in 2005, and currently cloud radar data are available. The intent of the site is to monitor the important components of the Arctic atmosphere, including clouds, aerosols, atmospheric radiation, and local-scale atmospheric dynamics. Because of the similarity of ACRF NSA data streams and the important synergy that can be formed between a network of Arctic atmospheric observations, much of the SEARCH observatory data are archived in the ARM archive. Instruments will be added to the site over time. For more information, please visit http://www.db.arm.gov/data. The designation for the archived Eureka data is YEU and is now included in the ACRF user metrics. This quarterly report provides the cumulative numbers of visitors and user accounts by site for the period April 1, 2007 - March 31, 2008. Table 2 shows the summary of cumulative users for the period April 1, 2007 - March 31, 2007. For the second quarter of FY 2008, the overall number of users was nearly as high as the last reporting period, in which a new record high for number of users was established. This quarter, a new record high was established for the number of user days, particularly due to the large number of field campaign activities in conjunction with the AMF deployment in Germany, as well as major field campaigns at the NSA and SGP sites. This quarter, 37% of the Archive users are ARM science-funded principal investigators and 23% of all other facility users are either ARM science-funded principal investigators or ACRF infrastructure personnel. For reporting purposes, the three ACRF sites and the AMF operate 24 hours per day, 7 days per week, and 52 weeks per year. Time is reported in days instead of hours. If any lost work time is incurred by any employee, it is counted as a workday loss. Table 3 reports the consecutive days since the last recordable or reportable injury or incident causing damage to property, equipment, or vehicle for the period January 1 - March 31, 2008. There were no incidents this reporting period.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.005 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.049 | 0.039 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".