BEE-spoke-data/govdocs1-by-extension huggingface dataset:
# Presentation: 171572

## ADMINISTRATIVE

**ADMINISTRATIVE**
**CONTROLS**

## Slide 2

## Administrative controls
are changes in the work 
schedule or operation that
 reduce a miner’s noise exposure by limiting the amount of time that the miner is exposed to noise

- are changes in the work
- schedule or operation that
-  reduce a miner’s noise exposure by limiting the amount of time that the miner is exposed to noise

## 
The noise standard requires 
the use of all feasible engineering and administrative controls to reduce a miner’s noise exposure to the permissible exposure level, or to as low a level as is possible

- The noise standard requires
- the use of all feasible engineering and administrative controls to reduce a miner’s noise exposure to the permissible exposure level, or to as low a level as is possible

**Notes:**
Even if these controls does not bring the miner into compliance with the noise standard

## These controls may be

**These controls may be**
** ****used separately or in**
** ****combination**

**MSHA’S NOISE POLICY STATES THAT THE AGENCY’S POLICY ON LABOR / MANAGEMENT AGREEMENTS WILL NOT BE AFFECTED BY THE NOISE STANDARD**

## MSHA POLICY

**	****Will not require an operator**
**to hire additional miners**
**in order to “exhaust” **
**all feasible**
**Administrative Controls **

## When setting up
Administrative Controls
a time resolved noise dosimeter should be used along with a time motion study on the affected miner

**Administrative Controls**
**a time resolved noise dosimeter should be used along with a time motion study on the affected miner**

## Table of Permissible NoiseExposures

_**Duration per day (hrs)**_**          **_**Noise level (dBA)**_** **
- 		8					90
- 		4					95
- 		2				        100
- 		1					105
- 		1⁄2					110
- 		1⁄4					115	_** **_
_**            **_

## 
Ways to control 
noise exposure
administratively without
modifying the noise

**Ways to control **
**noise exposure**
**administratively without**
**modifying the noise**

## Changing Work Practices

- Switch** **/ rotate miners from high- to low-noise exposure
- jobs or occupations
- Limit the duration of noisy tasks

## Change Production Schedule

- Schedule machine operating
- times so as to reduce the
- number of miners exposed
- to noise** **

## Administrative Controlscan include:

- Restricting access to high-noise areas
- Using remote sensing and monitoring
- Designating low-noise walkways
- Prohibiting congregation in high-noise areas
- Scheduling work tasks during down periods
- Taking breaks in quiet areas

## The application of 
Administrative Controls 
 should not result in the 
exposure of another 
miner to excessive noise

**Administrative Controls**** **
** ****should not result in the **
**exposure of another **
**miner to excessive noise**

**Notes:**
When Administrative Controls are implemented a copy of the Control (s) must be given to the miner and a copy of the Control must be posted.

##             They can whisper to you now.

**            ****They can whisper to you now.**
**Don’t make them shout at you in the future.**
# Presentation: 313542

## Planetary Data System

**Management Council**

- Project Management Message

- Laverne Hall
- June 3, 2004

*http://pds.jpl.nasa.gov/*

- PDS Management Council

## PDS Management Summary

***Assessment of PDS Progress Since Last MC ******(KEEP UP THE GOOD WORK!!!)***
- Demonstrated improvements in communication and coordination of efforts via shared working groups, telecons, etc.
- Continued significant technical progress with PDS-D/Website D02 release and cross-node reconciliation of large number of dataset holdings.
***Evaluation Reports - PDS Mid-Year from HQ and PDSWG***
- HQ Mid-Year:  Very good rating with both strengths, weaknesses , and mitigating circumstances sighted.
- PDSWG:  Varied in content with remaining outstanding issues to be reviewed and corrected/improved where needed.
***PDS Briefings/Exchanges***
- PDS benchmarking against other data systems - Videocon of lessons learned with EOSDIS (May 22, 2004)
- JPL Project Managers on upcoming required quarterly reporting on mission archive status (June 2nd, 2004)
***PDS Reporting***
- Continued efforts to streamline reporting process; however, components asked for are still needed in monthlies (significant highlights, fevers, metrics, and concerns).
- Quarterly reporting revisions over time sighted as area of noted improvement by GPMC and HQ.
***Second Round PDS POP***
- May 13th expectations/format not well communicated by authorities outside of PDS.
- Most nodes did excellent job in reducing overguide; some supported through burden savings.
- Redo on May 25th went better with some minor changes requested on a limited number of charts.
***Another Independent PDS Assessment (per HQ/PO directive)***
- Individual PDS areas briefings/interviews (May 28 , 2004 on)
- Awaiting McCleese White Paper (expected July 1, 2004 release)

- PDS Management Council

## Starter Management Schedule for Next 12-Months (Draft)

- PDS Management Council

## PDS/Flight Management & Functional Alignment Strategy

- Decision Making & Communications Process/Structure for Effective Project
- Need for streamlined approval authority structure within PDS
- Management by consensus vs. advisory groups vs. responsible authorities
- Need to assess Flight Project Practices and what is and is not applicable to PDS
- Signatories on Project Documents
- Documents to be used external to PDS
- Requires PE, PM, PS (ex., PAG)
- Documents internal to PDS
- Requires PM, PS, PSE (ex., SRD)
- Formal Planning and Scheduling
- Based on requirements (controlled set, signed-off).
- Change Request Process
- Need for formal process, approval authority, waiver authority, etc.
- Formal Review Process
- Assessment/reassessment of upcoming mission requirements challenges every 2 years.
- Tech/Peer/CD/Acceptance/etc. Reviews for major system deliveries.

- PDS Management Council
# Presentation: 692009

## GPRA:  New Climate Observations Introduced

-      FY2005 Target: 1014 new ocean observing platforms deployed;
-      December 2004:  221 total ocean observing platforms (relative to total FY04 deployments); 120 ARGO floats

- Dec. 04

**B**

## GPRA:  Reduce the Error in Global Measurements of Sea Surface Temperature

-      FY05 target: 0.5 °C; Long-term Target: Error of 0.2 °C by 2008
-      Long-term measure:  annual targets, progress reported quarterly

- More rapid expansion of the in situ network over the next several years will minimize the satellite bias error, enabling more accurate global sea surface temperature from a combination of satellite and in situ measurements.

- Note: this measure is proposed as a new GPRA for FY2006; it is already reported on quarterly

- Satellite bias error: the systematic difference between satellite-derived vs. in situ measurements of sea surface temperature

- Dec. 04

**B**
# Presentation: 208085

## Motor drivers for asyn motor device support

**Motor drivers for asyn motor device support**

- Mark Rivers
- GeoSoilEnviroCARS, Advanced Photon Source
- University of Chicago

## Problems with existing support

- Complex
- Device and driver support need to be written for each new controller
- Interaction of common (device-independent) device and driver support vs device-dependent code is not clear
- One thread per controller type, not per controller
- Multiple serial controllers of same type block each other
- I/O is driven by device support, not atomic
- Conflicts if other software talks to controller simultaneously
- No way to have other records communicate with the driver
- Can’t exploit controller-specific features that motor record does not know about
- Non-standard interface between device and driver support

## Current Status

- Working drivers for Newport XPS and MM4005 controllers done at APS.  Delta Tau PMAC done at Diamond.
- Continuing to refine the API, devMotorAsyn, drvMotorAsyn based on this experience

## Newport XPS

- Architecture and features
- Ethernet TCP/IP socket interface
- Can drive steppers, DC, wide variety
- Lot of auxilliary I/O.  48 bits of digital I/O, 4 A/D, 4 D/A
- vxWorks on Intel internally
- TCL/Tk interpreter
- No good device/driver support using “old” model
- Success in using asyn generic device support to set parameters not supported by motor record
- Success in using asyn generic device support to read fields with I/O Intr scanning
- Will be doing coordinated motion soon
- Probably first outside of new API using SNL program
- Then extend API to handle coordinated motion

## Newport XPS – Auxilliary I/O

- Done on separate sockets
- Uses asyn generic device support
- Rapid polling, I/O Intr scanned record

## Newport XPS

- Generic device support to read readback, and control jerk times
- Uses asynInterposeInterface for asynDrvUser interface
- grecord(ao,"$(P)$(R)MIN_JERK_TIME") {
-     field(DESC,"Min jerk time")
-     field(PREC,"3")
-     field(VAL,".01")
-     field(DTYP, "asynFloat64")
-     field(OUT,"@asyn($(PORT))MIN_JERK_TIME")
- }
- grecord(ao,"$(P)$(R)MAX_JERK_TIME") {
-     field(DESC,"Max jerk time")
-     field(PREC,"3")
-     field(VAL,".03")
-     field(DTYP, "asynFloat64")
-     field(OUT,"@asyn($(PORT))MAX_JERK_TIME")
- }
- grecord(ai,"$(P)$(R)READBACK") {
-     field(DESC,"Readback")
-     field(PREC,"4")
-     field(DTYP, "asynFloat64")
-     field(SCAN, "I/O Intr")
-     field(INP,"@asyn($(PORT))POSITION")
- }

## Newport MM4005

- Simpler than XPS.  Serial or GPIB
- Converted in about 1 day
- Now can have EPICS interface to features motor record does not support
- Already have coordinated motion (“trajectory scanning”) with SPEC macros to use it
- Re-do this as a standard API in the future
- Given MM4005 support should be less than a day each to convert other serial drivers to asyn device support

## Summary

- 2-3 times fewer lines of code
- 2-3 times fewer files
- New features and flexibility
- Path forward to take advantage of new controller features
- Plan motor record enhancements/fixes after new asyn interface matures
# Presentation: 200120

## Slide 1

## Slide 2

## Slide 3

## The new NIF ignition design relies on sophisticated 3D  codes and targets, to give a confidence in ignition at 1 MJ

**The new NIF ignition design relies on sophisticated 3D  codes and targets, to give a confidence in ignition at 1 MJ**

**Sophisticated target design/fab compensates for limitations in drivers**

## direct drive

**direct drive**

## Symmetric direct drive ignition on the NIF requires major changes to the facility

**Symmetric direct drive ignition on the NIF requires major changes to the facility**

**Polar Direct Drive( PDD) achieves direct drive ignition with NIF’s **
**beams in the Indirect Drive configuration **

**direct drive**

## Direct drive: Rochester, NRL and the Laboratories 

**Non symmetric laser illumination PDD is being explored**
**Aggressive pulse shaping increases the margin for ignition**
**•    ****Target designs which push our understanding offer hope for ignition at substantially lower laser energy-NRL V****in****~ 5 10****7**** ignition at ~ 200kJ **

**Aggressive 2D designs  are being validated experimentally**

**direct drive**

## The three high yield concepts being explored on Z  involve 

**The three high yield concepts being explored on Z  involve **
**aggressive physics which will have pay off for all x-ray drive platforms**

**Pulse power**

## Pulse power

**Pulse power**

**Beryllium capsules important for lower T****r**** ~ 220eV of pulse power**

## Pulse power

**Pulse power**

## Advances in x-ray drive could reduce the lost energy or more 

**Target fabrication R & D can further enhance the margin for ignition**

**Advances in x-ray drive could reduce the lost energy or more **
**effectively use the 4 MJ of laser energy potentially available **
**from NIF**

**The small capsule to case ratio results in low energy coupling**
**	****- advanced symmetry control could allow less**
**	**** ****hohlraum loss**
**More energy on NIF is available with green and even 1 micron**
** **

**advanced x-ray drive**

## Systematic asymmetries can be compensated by hohlraum and capsule design

**advanced x-ray drive**

## Shimmed targets tolerate smaller case/capsule with 

**Shimmed targets tolerate smaller case/capsule with **
** ****increased  efficiency of x-ray drive**

**advanced x-ray drive**

## Slide 14

## Slide 15

## Funded by OFES/NNSA

## - Validation needed at 10 ps

**- Validation needed at 10 ps**

## Slide 18

## Slide 19

## Nova, OMEGA and Z/R optimize annual 

**Nova, OMEGA and Z/R optimize annual **
**Shot rate, but still measured in shots/day**

## -size?

**-size?**

## Slide 22

## Slide 23

## Slide 24

## Slide 25
# Presentation: 798708

## TC4 Validation Mission

- July-August 2009

## TC4

- Mission consisted of 3 aircraft
- ER2 - mostly full participation - but landed before Aura overpass
- DC8 - mostly full participation - bulk of Aura validation
- WB57 - Participated in only 3 San Jose flights near the end of the mission - landed before overpass.

## DC-8 Payload

| Measurement | Instrument Name  | PI |
| --- | --- | --- |
| H2O, CO, CH4, N2O | DLH, DACOM | G. Diskin, G. Sachsse, LaRC |
| Cloud Part.  | 2DS, CPI | P. Lawson, SPEC Inc. |
| Aerosols | LARGE | B. Anderson, LaRC |
| Aerosol Comp. | PALMS | D. Murphy |
| Cloud Part.  | RICE, SID2, PIP, CVI | A. Heymsfield, NCAR |
| SO2, Organic Acids | CIMS | J. Crounse, CalTech |
| Ozone | FASTOZ | M. Avery, LaRC |
| CO2 | MACDONNA | S. Vey, LaRC |
| NO-NO2 | TD-LIF | R. Cohen, UC Berkley |
| Many gases | WAS | D. Blake, UC Irvine |
| HNO3, SO2, aerosol sulfate | SAGA | J. Dibb, U. NH |
| Drop T, humid, winds | Dropsondes | M. Kurylo, HQ |
| Winds, T | MMS | P. Bui, ARC |
| Precip Radar | APR2 | E. Smith, GSFC |
| O3/Aerosol Lidar | DIAL | E. Browell, LaRC |
| H2O/Aerosol Lidar | LASE | E. Browell |
| Broadband radiom. | BBIR | A. Bucholtz |
| Actinic Flux | CAFS | R. Shetter, NCAR |
| Solar Spec. Fluc | SSFR | P. Pilewske |

## DC-8 and WB-57 Flights

- DC-8 and WB-57 Flights

- Underpass
- Flight Segment

- http://code613-3.gsfc.nasa.gov/People/Lait/met/tc4/kml/flights/

## July 17 - SO2 Plume Sample

- July 17 - SO2 Plume Sample

- DC-8

- Red = 1 DU of SO2

## Plume

## No Depolarization

- Sulfate aerosols

## Plume

## No Depolarization

- - Sulfate aerosols

## CIMS  John Crounse 

- CIMS  John Crounse

## Plumes

- Urban SO2

- CIMS  John Crounse

## San Jose

- Guayaquil, EC

- Volcano

- Volcano

- CIMS  John Crounse

- Volcanic Plume

## SAGA MC/IC  Dibb/Scheuer

- SO2/(SO2+SO4)
- Ratio is high - plume is fresh

- Plume is fresh

## Slide 14

## Lightning strikes plane about here

- Lightening Burn Hole on Tail

- July 24 - Zeus tries to take out the Aura Project, but fails

- (undoctored photo before strike)

## TC4 

- Lots of good validation data despite mission problems - SO2, NO2, Ozone
- Not as much TTL data as we would like
- Workshop early next year
- Thanks for Aura team for field participation and special products
# Presentation: 527904

## Module 4: Protecting the Personal Security of the Child Support Worker

- Module 4: Protecting the Personal Security of the Child Support Worker

- Module 4

## Learning Objectives 

- Learning Objectives

- Identify what can be done to protect your working environment
- Define security as a priority

- Module 4

## Introduction

-  Child support offices can be targets for:
- Theft
- Unauthorized Access
- Threats
- Physical Abuse
- Effective barriers (physical and psychological) can reduce threats

- Module 4

## What can be done to protect your environment

- Possible protections:
- Door Codes
- ID Badges
- Furniture Arrangement

- SOS Buttons
- Bullet Proof Glass
- Metal Detectors

- Module 4

## What can be done to protect your environment

- Possible protections:
- Single public access
- Security guards
- Closed circuit TV

- Windows to view clients
- Parking lot lights

- Module 4

## What is Biometrics?

**Biometrics **
- Technologies That Automatically Recognize A Person Using Distinguishing Biological Traits

- Module 4

## Examples of Biometrics

**Finger Scans**
**Iris Identification**
**Face Geometry**
**Hand Finger Geometry**
**Signature Verification**
**Voice Recognition**
**Key Stroke Dynamics**

- Module 4

## Policies and Procedures

-  Establish procedures for all staff:
- Verbal Threats
- Bomb Threats
- Physical Threats

- Module 4

## Make Security A Priority

-  How do we ensure personnel security?
- Training
- Train all staff
- Continuous training

- Module 4

## Summary

-  What would you do to protect your environment?
- Escort  visitors
- Lock all offices, conference room and storage rooms
- Close and lock all windows

- Module 4
# Presentation: 943101

## Non working channels in cft according e-log on 4/3/2003

- CFTX2: 9 fibers between 1347 and 1406, 8 belong to VLPC7 in 9A5  mcm 1
- CFTX3: 11 fibers between 15 and 50, 8 belong to VLPC8 in 6A0 mcm 8
- This board was swapped and the problem remains-cassette problem
- CTX5: 11 fibers between 2183 and 2233, 8B6 MCM7 should be swapped
- CFTX6:  9 fibers between 4611 and 4670, 8 belong to VLPC2 in 7A2 mcm 8
- Not on list of unbiased VLPCs, possible mapping error
- CFTX6: 10	fibers between 1167 and 1202, 8 belong to VLPC8 in 5A4 mcm 8
- CFTX7: 9 fibers beween 909 and 948, 8 belong to VLPC7 in 6A2 mcm8
- CFTX8: 5 fibers between 4228 and 4284
- CFTU3: 8 fibers between 4301 and 4340, all belong to VLPC7 in AA6 mcm1
- Not on list of unbiased VLPCs, possible mapping error
- CFTU4: 8 fibers between 5412 and 5489,  8B2 and 8B3
# Presentation: 046581

## Module 6

**From Precontemplation to ****Contemplation—Building****Readiness**

## Take Time to... 

- Establish rapport and trust
- Explore events that precipitated treatment entry
- Commend clients for entering treatment

## Coerced Clients

- “Decontaminate” the referral process
- Honor the client’s anger and sense of dehumanization
- Avoid assumptions about the type of treatment needed
- Make it clear that the clinician will help the client derive what the client perceives is needed and useful out of their time together
# Presentation: 261096

## WIC Foods for Pregnancy

**WIC Foods for Pregnancy**

**     ****New &**
** ****Improved!**

- The new WIC foods help you and your baby meet today’s nutrition needs as recommended by your health care provider during pregnancy.  You can continue
- to enjoy milk, cereal, eggs, juice, peanut butter and beans plus fruits,
- vegetables and whole grains!

- Your New WIC Foods:

|       Are lower in fat and higher 
      in fiber |       Improve the variety of   
      foods available |
| --- | --- |
|       Promote healthy weight 
      gain for you and your baby |       Are consistent with Dietary
      Guidelines and MyPyramid
      recommendations! |

| GRAINS | FRUITS  and VEGETABLES |  | DAIRY | PROTEIN |
| --- | --- | --- | --- | --- |
| 36 ounces iron-fortified cereal |  144 fluid ounces of vitamin C-rich juice |  | 22 quarts of milk | 1 dozen eggs |
| 1 pound whole wheat bread | $8 cash value voucher for fruits and vegetables |  | More allowed substitutions | 1 pound dried beans or peas |
| Or other whole grain options |   |   |   | Or 4, 15 ounce cans of 
beans or peas |
|   |   |   |   | 18 ounces of peanut butter |

**  ****What You Will Receive:**

**Eat WIC foods for a healthy you and a healthy growing baby!**
# Presentation: 426366

## Extensible Terascale Facility Workshop Redux

- Richard S. Hirsh
- Division Director
- Advanced Computational Infrastructure
- And research (ACIR)
- September 20, 2002

## Some History First

- Terascale funding arrived in FY00
- Two competitions so far
- FY00 – Terascale Computing System
- FY01 – Distributed Terascale Facility
- FY02 – 2 ETF (Extensible Terascale Facility) Dear Colleague Letters
- One for PIs & one for the Community

## How we got to today 

- DTF award creates the TeraGrid
- Four sites connected (UIUC, UCSD, ANL, Caltech)
- Focus on commodity computing, data services and computing, visualization
- But . . . .
- Four sites mesh-connected – will not scale

## At last year’s SC meeting in Denver

- I gave a lunchtime briefing about the TeraGrid
- NSF moving rapidly into Grid computing
- Not just ACIR (NMI Program in ANIR)
- TeraGrid needed to encompass more than just the 4 original sites to be a national infrastructure
- Promised a workshop (this workshop) during the summer

## Objective of This Workshop

- To inform you about NSF’s plans for continued expansion of the TeraGrid as a foundation for Cyberinfrastructure.
- To outline the NSF’s plans for FY2003 and beyond.
- To get input from you on what enhancements to TeraGrid would most benefit the science and engineering research community.

## An Urban Legend . . .

- appears mysteriously and spreads spontaneously in varying forms
- contains elements of humor or horror (the horror often "punishes" someone who flouts society's conventions)
- makes good storytelling
- does NOT have to be false, although most are. ULs often have a basis in fact, but it's their life after-the-fact (particularly in reference to the second and third points) that gives them particular interest

## FY03 and beyond

- Asked for $20M – Senate mark-up now at $10M
- Will issue solicitation (based on input from this workshop) for connections to TeraGrid
- Thoughts right now would be to add
- Computational resources
- Data sites
- Instruments or sensors
- ????

## Structure of this Workshop

- Architects of the TeraGrid will outline (before lunch)
- Currently available resources
- The extensible ETF backplane characteristics
- Software and hardware compatibility
- Organizational issues
- Already available in “The TeraGrid: A Primer”

## Structure of this Workshop (2)

- Town Hall Roundtable to answer questions (after lunch)
- submit questions online during morning session or during lunch
- NSF will capture and publish on another FAQ page
- computers at back of room at NSF for use, or
- URL - http://www.mcs.anl.gov/etf/etftopics.htm
- Organized/collated by Dick Hilderbrandt & Rick Stevens
- answered during Town Hall session led by Rick
- NSF will publish on FAQ page

## Thank you for attending

- We want your input
# Presentation: 679120

## Advisory Committee on Student Financial Assistance

**Comments of Chris Carter**
**University of California**
- March 7, 2002

## Selected UC Numbers

- 138,803
- 2000-2001 undergraduate enrollment
- 9
- Number of UC campuses currently enrolling students

## Undergraduate Financial Aid Policy at UC

- UC will maintain affordability for California residents
- Financing is the responsibility of a partnership  between
- Student
- Parents
- University and  state & federal governments

## Need-Based Financial Aid at UC

- Nearly half -- 46% -- of undergraduates at UC received need-based financial assistance in  2000-2001
- Nine of ten need-based aid recipients received gift assistance

## Grant Recipients by Source

- Undergraduates
- Federal Grants:		41,700 recipients
- State Grants:		36,200 recipients
- UC Grants			42,900 recipients

## UC’s Institutional Grant Policy

- Use grants to keep work and debt levels manageable
- Work fewer than 20 hours weekly while enrolled and full-time when not enrolled
- Limit the need to borrow such that payments are manageable given average wage of a 1st year graduate of UC

## Unmet Need Levels

- For 2000-2001, average unmet need was $2,542
- In same year, loan/work levels averaged about $6,500 for all undergraduates

## Indicators of Success:  1

## Indicators of Success:  2

- UC compares favorably relative to other top-ranked institutions in terms of percent of students who are Pell eligible.

## Implications of no Institutional Aid

- With no institutional grant program, the average unmet need of a UC aid recipient would almost double to $4,879
- Loan/work levels would increase by about $2,300 or one third

## Economic Recession

- Tends to drive up demand for financial aid
- Family incomes tend to be flat or fall while costs increase
- Declining state revenues put pressure on student fees to increase

## Funding for UC Grants	

- UC seeks to hold Students harmless in the face of increasing enrollment and prospective fee increases
- UC policy dedicates one third of all increases in fee revenue to the University’s student aid program

## Prospects for 2002-2003

- Governor has proposed cutting support for UC’s financial aid program by $17 million, or about 10%
- A fee increase is not being actively discussed/considered at this time
# Presentation: 657313

## Data from APS Survey

- March 2007

- April 18, 2007

## CFN Site Evaluated at Several Times

## Acoustic Radiation

## Overview

- Measurement Locations
- Vibration Results
- PSD
- One-Third Octave Bands
- Acoustic Noise
- Slab Stiffness

## Slide 5

## Slide 6

- Vibration Measurements
- Chiller
- AHU
- Tunnel Roof
- Experiment Hall Floor

## Vibration in PSD

## PSD Data from APS

## Roof of Storage Ring Tunnel

## 24” Slab Next to Tunnel

## Several Experiment Hall Locations

## Compare APS with BNL

## Compare with Data from Others

## Vibration in One-Third Octave Bands

## Experiment Hall in 1/3 Octaves

## Experiment Hall in 1/3 Octaves

## Experiment Hall in 1/3 Octaves

## Experiment Hall in 1/3 Octaves

## Spatial Variation

- Compare spectra from mezzanine and several on-grade locations.

## Spatial Variation

- Show how vibrations vary between mechanical mezzanine and tunnel

## Maximum Vibration Velocity

**Receptor Locations**

**Source Locations**

## The 60 Hz tone?

- ~ 60 Hz tone at floor and tunnel is not due to either Utility Bldg chiller or pump in Mezzanine

## Acoustic Noise in APS Experiment Hall

## Noise – Old APS Study

- Comfort and user fatigue issue
- Used old PNC criteria, now obsolete
- Philosophy based on “lessons learned” from BNL NSLS I

## NC Characterizations

## NSLS I (1989)

- Several identifiable “hot spots” from user equipment
- Minimum noise spectrum (which approximates “ambient”) was NC-58
- Maximum noise EHS issue (81 dBA)

## APS (2007)

- No apparent “hot spots”, probably because of hutches
- Minimum noise spectrum (approximates ambient) was NC-59

## Comparison of Noise(NSLS I in 1989, APS in 2007)

- Primary observations:
- NSLS I “Hot spots” had _*very*_ high noise levels
- Minima were almost identical
- Mean values differed by only 3 dB

## Improved Noise Control in Building
Distance to air movers
Absorbent material for reverberation

Administrative Noise Control
Hutches

- Improved Noise Control in Building
- Distance to air movers
- Absorbent material for reverberation
- Administrative Noise Control
- Hutches

## Stiffness Properties of Slab

## Measure Slab Stiffness Properties

- Strike slab with hammer
- Measure force and response
- Stiffness spectrum is force spectrum divided by displacement spectrum (FRF)

## Stiffness in Spectral Terms

- “Static” stiffness is the low-frequency portion that is constant with frequency.
- Slab-on-grade behaves like Kelvin element.

**Static Stiffness**

## Summary of Static Stiffness

- High stiffness beneath experiment hall
- Lower stiffness in perimeter corridor and near joints

## Improve Slab Performance
Stiffness (flat portion)
Function of t^1.5

Impedance (sloping portion)
Function of t^2

- Stiffness (flat portion)
- Function of t^1.5
- Impedance (sloping portion)
- Function of t^2
# Presentation: 010672

## L0 prototype modules

- L0#3 --- both sensor and cable are bonded.                     AVDD and DVDD tied together.
- L0#4 --- only cable is bonded.
- L0#5 --- ch1-64: only cable bonded. ch65-128 both sensor and cable bonded. Kapton backing for grounding is done.
- Firmware ready for testing (thanks to Mike).

-  bug fix for the preamp reset.
-  capability to choose one pipeline cell (cal_sr in init).
-  ensure all pipeline cell reset by extra 46 clocks.

## L0#3 (cable and sensor)

- Disabling this channel

## L0#4 (only cable)

- bottom cable

- top cable

## L0#5 (cable and/or sensor)

- cable only

- cable + sensor

## Band Width dependence

- BW=15

- BW=8

- All three modules reasonable response!

## Status Summary

- BW=4, ramp slope=1 for this summary.
- L0#3 and L0#5(sensor part) have similar noise level.            ~2.2 ADC counts (1500e) of noise increase relative to the bare chip. Random noise by ~1.6 ADC (1100e).
- L0#5 (only cable part): ~1.0 ADC counts (700e) of noise increase relative to the bare chip. Random noise by ~0.9 ADC (600e).
- L0#4 has higher noise for the bottom cable.
- All has reasonable bandwidth dependence.
- Common mode noise when sensor bonded (?).

- cf. ENC = 300 + 41C @40pF                                     1100e  27pF(cable+sensor),  600e  15pF(cable)

## Plan

- L0#5 put on the L0 structure.
- Test and compare the result with the current status.
- Kapton (grounding mesh) backing for L0#3.
- Test before putting it onto the L0 structure.
- L0#3 put on the L0 structure.
- Simultaneous read out of L0#5 and L0#3 on the structure.

## SVX4 preamp reset issue

- pipeline cell

- release preamp reset

- 350ns

- This is quite small effect at the front end.  acceptable.                          cf. 4.4mV/fC at preamp, voltage gain of 3.4 at pipeline.
- Should gone by the real time pedestal subtraction.

## Sara sees pipeline cell dependence of gain (2 or 3%) in her hybrid/module testing.
The same effect has been observed in single chip (1 or 2% variation).

Wafer dependence???

- The same effect has been observed in single chip (1 or 2% variation).
- Wafer dependence???

- Pipeline cell dependence of gain

- Different symbols  denote different channel.
# Presentation: 200388

## Slide 1

## Slide 2

## Numerical issues & Simple Tracers

- Michael Prather & Xin Zhu, UCI
- 5 Nov 2003
**Goal:  Compare the GMI/GISS23L met fields **
**	****	****run with (a) GMI code & (b) UCI CTM**
- Met Fields
- Simple Tracers
- provide a benchmark for the comparison
- 	(also basic info for trop chem analysis)

## Numerical issues & Simple Tracers

**Met Fields **
- We have 2 consecutive years of GISS23L met fields
- The netcdf met fields from GMI
- 			are different from both of these (alas!?)
- GMI/GISS23L statistics for {u,v,T,bl-ht} look fine
- GMI/GISS23L statistics for {rain, convective flux} are *odd*
- 		only 1 3-D rain (stratiform – cumulus from clouds?)
- 		entraining and non-entraining updrafts combined.
-   *- we can solve this and try to simulate the GMI runs –*
*	**	**	**	**	**	**	**	**	**but*

## Numerical issues & Simple Tracers

**Met Fields:  GMI/GISS23L**
- What differences can we expect?
- 	UCI CTM core is very different (SOM, op-split)
- 	UCI CTM advection is SOM plus diff flux limiters
- 	UCI CTM has very different convection.
- Test of “cousin” met fields for interannual (?)

## Numerical issues & Simple Tracers

**Simple Tracers**
- Jae Hoon did a fantastic job in running
- 		the first draft of the simple tracers
- Xin Zhu did preliminary analysis over the weekend
- found some “undocumented features”
- basically ready to go

## Simple Tracers 

- ff-CO2:
- 	1995 fossil fuel pattern (TransCom3 version)
- 	6.3? Pg-C/yr,  no loss???
- ff-CO:
- 	Harvard fossil fuel CO emission grid (annual)
- 	60-day lifetime (5 d in strat)
- bb-CO:
- 	Harvard biomass burning CO emissions (annual)
- CH3I:
- 	oceanic source (latitude?), 5-day lifetime

## ff-CO2:  column density, Dec Y7 vs. DecY8

- ff-CO2:  column density, Dec Y7 vs. DecY8

## ff-CO2:  log mixing ratio, Jun Y8 vs. DecY8

- ff-CO2:  log mixing ratio, Jun Y8 vs. DecY8

## ff-CO2:  annual growth (12-month diffs)

- ff-CO2:  annual growth (12-month diffs)

## bb-CO:  log mixing ratio

- 	JUN					DEC

## bb-CO:  total burden

- 	and annual diff

## ff-CO:  rel.diff. between Jan-start & Jul-start (+6 mon)

## CH3I:  log mixing ratio

- CH3I:  log mixing ratio
- 	too much at mid-lats

## NOT CONTRAILS                                             CONTRAILS

**NOT CONTRAILS                                             CONTRAILS**
# Presentation: 118809

## Plan forthe EMCal trigger board check

- H.Torii, Kyoto Univ.
- 2002/Oct/10
- ERT Level1 Meeting

## What did we earned from Test Bench

- Test bench setup
- At the first moment, we found 4 noisy tiles.
- After replacing some ACIS cards and adjusting the parameters for AMU/ADC chips, the noisy tiles have gone and the offline readout became fine.
- We tried “enable/disable switch” and “CalDAC”
- At the threshold of 30 or 31 for 2x2,4x4A,B,C
- Enable/disable switch
- Set all 144 towers as disable,
- The trigger output appeared Noise !!!
- Set 4towers(1tile) as disable
- One tile shows random trigger output
- Another tile shows no trigger output, but shows the output in very low efficiency when we put test puleses. Cross talk???
- Set the threshold from 30 to 40
- The trigger output have gone.

## Cont.

- CALDAC (pulsar inside the ASIC)
- Basic setup
- Modified the serial data for the MONDO chip
- Set the CALDAC to the maximum(63) setting for all 36 MONDO chips.
- Modified the GTM code
- To send the correct mode bit.
- Set 144 channels as CALDAC enable.
- Shows the trigger output
- Set 4 channels(1tile) as CALDAC enable.
- Shows the trigger output
-  Work very fine!!!! Will use for the noisy ASIC search

## Plan for the noisy ASIC search

- Need timing coincidence
- GTM for EMC
- GTM for ERT
-  Willl use PPG
- EMCal Trigger board works like an analog board, not digital.
- It’s enough to send the mode bit from GTM in the appropriate timing.
- Plan to start from next week
# Presentation: 538759

## Implementation of Bioregional Plans

**A Proposal for 2-Levels of Cooperation**

## Cooperating NECO Agencies Meeting on September 15

- Overview for new NECO BLM Managers
- Refresher: CDFG, USMC, DMG
- “How to Use NECO” primer for Biologists
- Post-ROD Cooperation discussed
- 		♦ Implementation Status
- 		♦ Need for Cooperators Meetings

## 6 Bioregional Plans - Status

- All are/almost completed
- Need to move out on Implementation

## Bioregional Plans Decisions and Commitments

- Public Lands Health
- Listed & Unlisted Species & Habitats
- Livestock Grazing & Burros
- Other Managed Uses
- Routes of Travel
- Land Tenure
- Public Education
- Monitoring
- Include commitment for continued Cooperation

## Importance of Cooperation in Implementation

- Values/Decisions cross # Agencies
- Achieves all Agencies’ Mandates
- Supports Budget Process
- Supports CDCA Consistency
- Better addresses Lawsuits
- Includes Governments & NGOs
- NGOs are still stakeholders, will volunteer

## Proposal: Greater CDCA Cooperative Management for Implementation

- 	2 Levels of Cooperation for Maximum Efficiency & Effectiveness:
- 		♦ Bioregions: each with a unique group
- 		♦ CDCA: Desert Managers Group

## Cooperation at Bioregion Level

- Scope: Implementation, process, budget, priorities, etc. specific to Bioregions
- Informal - Agencies & NGOs work together as much as possible
- Agencies represented at DMG, too
- NGOs primarily involved at this level
- Work not to conflict with agencies mandates, authorities, daily affairs, FACA (= DMG)
- Elevates CDCA-wide issues to DMG
- Relieves DMG of work focus on the routine
- Regular progress reports

## Cooperation at DMG Level

- Scope: similar to Bioregion but CDCA-wide
- Formal – already chartered
- Agencies in 1 or more Bioregions
- NGOs involvement is ad hoc, only
- Agenda is primarily bottom-up from Bioregions
- Relieves Bioregions of non-routine/CDCA-scope work
- Reduces problem solving workload for Bioregions
- Top-down for solutions, priorities, funding CDCA-wide in scope.  Is Proactive on high-priority funding needs
- DMG may invite ad hoc Bioregion support
- Regular progress reports
# Presentation: 205150

## DAQ Monitor

- T. Yasuda
- Fermilab

## Introduction

- Purposes
- Performance monitoring during a run.
- Performance tuning tool during commissioning.
- Diagnostic tool in case of problems.
- Program
- Server (DM_Server) and Client (DAQ_Monitor.py) system.
- Communicates with DAQ system elements using itc.
- Client displays information using Python/Tkinter + Pmw (Python mega widgets) modules.

## Trigger/DAQ Monitor

**Trigger/DAQ**
**Monitor **
**Server**

**Data**
**Logger**

**Monitor**
**Display**

**L3**

**L1/**
**L2**
**TCC**

**Data**
**Distributor**

**EXAMINE**

- T. Yasuda	4/26/99
- Updated             5/18/01

## How it works

- DM_Server:
- an itc server with an itc processor to handle messages.
- Contains a DM_Task class object.
- DM_Task class object contains separate monitoring class objects for DAQ sub-processes, e.g. TCC, Distributor, etc.
- Requests data to the DAQ sub-processes by sending an itc message at fixed intervals, except L3 filter monitor that pushes data to DM_Server.

## How it works

- DAQ sub-processes sends monitoring info in the form of an itc message.
- L1 TCC sends an Opaque message with a c-struct.
- L2 TCC sends an Opaque message with a l2monitor class.
- CR, DL, DSM, SDAQ, and L3 filter send a string message.
- distributer sends its own message class (xdr encoded).
- Messages received from the DAQ sub-processes are handled by callback methods.

## How it works

- Opaque messages sent to receiver clients are xdr encoded.
- DAQ_Monitor display
- Receiver (Display) clients send a string message to request data from the DM_Server at fixed intervals.
- Display clients receives data from the DM_Server and in the case of Opaque message, the message is xdr decoded.
- Currently all opaque messages are xdr encoded on the server and decoded on the client. Do we need this?
- xdr decoding in python is very slow.

## Software

- A cvs package: daq_monitor
- Written in C++ (server) and python (display client).
- Uses itc for communication.
- Different message types for individual sub-processes that run C++ server/client.
- String and opaque messages only for python (display) clients.
- Messages are encoded/decoded in XDR in some cases.
- Compiles on SGI, Digital Unix and Linux.

## What’s next?

- Switch to a new version of L1 Tcc monitor info
- Include L2 monitor
- DM_Server can accept l2monitor message from TCC and send it to display client.
- l2monitor package has been SWIGed so that info can be interpreted using python.
- SWIGed code has memory leak!!
- Oklahoma student Isaac Hall working on display.
- Include strip charts and other gooddies
- MSU student Joe Kozminski started to work on this.

## Instructions

- To start the DAQ Monitor server (on d0olc)
- setup d0online
- start_daq_monitor_server
- or start_daq daq_monitor
- To start a DAQ monitor display client (from any online node)
- setup d0online
- start_daq_monitor_display

## Slide 10

## Slide 11

## Slide 12

## Slide 13

## Slide 14

## Slide 15

## Slide 16

## Slide 17
# Presentation: 135715

## BFD: An Overview

- Martin C. Stoufer
- DSD/DIDC
- July 9, 2004

## Summary

- Review:
- What is the Software Development Cycle?
- What is Software Asset Management?
- Who is S.A.M. best suited for?
- Why does this breakdown so easy?
- What is BFD?
- What is it good for?
- Who can use BFD?
- Links & Resources

## The Software Development Cycle

- Develop

- Test

- Verify

- Integrate/Merge

- Baseline

## What is Software Asset Management?

- Software inventory    What are the projects?
- Version tracking    Every version is a ‘product’
- Policies    When to release?    Who to release to?

- The concept of treating your software project as a commodity and
-  not just a bunch of code that works.

- Procedures    How do they get it?
- Technologies    How are they getting it?
- Delivery    Verify they got it correctly.

## Who is S.A.M. best suited for? 

- The Lone Wolf
- No need. The code stays in one place, evolves slowly and organically.
- A small group of friends
- Maybe. Both the developers and code base are centralized.Specific goals are short term and verification testing is quick.
- The medium commercial venture
- Possibly. Money and investors drive the need. ‘*Legitimacy*’
- A large collaborative project
- Absolutely. Size, complexity, and dependencies require it.

## Why does this cycle breakdown so much?

- Success

- Size of project

- Amount of  S.A.M.

- Nothing gets done

- You’re flipping burgers

- Log/linear

## Why does this cycle breakdown so much?

## What is BFD?

- Not an IDE.
- Drives the entire Software Development Cycle.
- Other products only do a specific subset successfully.   Sometimes for big $$$
- Tinderbox, ClearCase, CVS
- Introduces the concept of multi-project grouping
- Allows an entire software concept project to be presented as such.
- Enforces an ordered procession of steps.
- Won’t perform miracles for the lazy or untrained.

## BFD Example

## Who can use BFD?

- Managers
- Those who decide to integrate/re-baseline
- Developers
- Those who write the code
- Software designers
- Those who design, test, and verify
- Not the end user!
- They should only enjoy a successful project

## Links & Resources

- BFD
- _[http://bfd.lbl.gov](http://bfd.lbl.gov/)_
- ClearCase
- _[http://www.rational.com/products/clearcase/index.](http://www.rational.com/products/clearcase/index.jsp)__[jsp](http://www.rational.com/products/clearcase/index.jsp)_
- Tinderbox
- _[http://www.mozilla.org/tinderbox.html](http://www.mozilla.org/tinderbox.html)_
# Presentation: 546995

## Training Overview

- Classes taught last year by OSW
- Classes taught last year by Regions
- Developing Infrastructure- OED, EDC, IDP, EDNA
- Needs—an unscientific assessment

## OSW Classes last year

## Regional Classes last year

**Western Region**
- Slope-Area Measurements – Tucson, 04/02
- Field and Records, Portland, 06/02
- Watershed Modeling, Step-Backwater, Botswana, 10/02
- Ratings Refresher, Salt Lake City, 11/02
-  _[Publicly Available Web- and CD-Based Training](file:///PubTraining.html)_
-  _[Technician’s Advisory Committee’s Toolbox](file:///../WRTAC/ToolBox/Index.htm)_

## Regional Classes last year

**Northeast  Region**
- Indirect  Measurements – NY, 09/01
- Field and Records, PA, 09/02
- Ratings, NY, 09/02

## Regional Classes last year

**Southeast  Region**

## Alphabet Soup

- Office of Employee Development (OED)—Bureau-wide training and employee development office
- Partners with disciplines for effective needs assessment, presentation and delivery of technical courses
-  Met jointly with, October 28 and 29
- Outlined concerns
- Defined roles and responsibilities for training support
- Outlined process and timeline for training development

## Alphabet Soup

- Employee Development Committee (EDC) – Water Discipline Committee
-  Met via conference call in January to redefine charter
- Provided guidance and feedback on employee development to AD for Water, Water Senior Staff, and OED
- Primary focus is on technical and scientific training
-  Will review and assess existing training programs

## Alphabet Soup

- Employee Development Needs Assessment (EDNA) – Water Discipline Committee
-  Met via conference call in January to redefine charter
- Provided guidance and feedback on employee development to AD for Water, Water Senior Staff, and OED
- Primary focus is on technical and scientific training
-  Will review and assess existing training programs
# Presentation: 330206

## NOISE: Into the 21st Century

## What is NOISE?

## NOISE is...

- Committed to the pursuit of responsible aviation noise mitigation policies.
- Committed to reduce aviation noise and its detrimental impact on America’s communities.
- Not anti-aviation.

## Who Belongs to Noise?

- Local elected officials
- Local governments
- Communities
- Airports

## NOISE Objectives

- Advocacy
- Outreach
- Information
- Technical assistance

## NOISE Goals

- Forge partnerships with organizations that are committed to noise abatement
- Advocate noise abatement policies that are both responsible and acceptable to all parties involved.
- Insure that the voice of affected communities is heard.

## But the scenery of aviation noise mitigation is changing...

##  Through...

- Increased sensitivity in Congress.
- The emmergence of neighborhood noise mitigation groups.
- Increased organization at the grassroots level.

## Because...

## The number of airports in the United States is growing.

## What does this mean?

## Increasingly more people are being affected by aviation noise.

## For example...

## Therefore...

- It can be expected that aviation noise mitigation will begin to come to the for front.

## Recent examples...

- NASA Reauthorization (HR 1654)
- FAA Reauthorization (S. 82)
- The coverage of aviation noise mitigation in the media...

## What are major newspapers saying???

## The New York Times

## Slide 18

## The Record Newark , New Jersey

## “Flight paths of airplanes leaving the Newark, New Jersey International Airport are being altered to reduce aviation noise over parts of New Jersey....”

## The Los Angeles Times

## “The City of Burbank and the Burbank Airport should seek a compromise in their ongoing fight over the expansion of the airport...”

- “The City of Burbank and the Burbank Airport should seek a compromise in their ongoing fight over the expansion of the airport...”

## NOISE in the 21st Century...

## Will...

- Start a public dialog with the aviation industry, communities, elected officials and airports.
- Continue to form partnerships with noise abatement organizations from around the U.S.
-  Continue to pursue responsible aviation noise mitigation strategies.

## The National Organization to Insure a Sound Controlled Environment
# Presentation: 512055

## Evacuation Liaison Teams

**Into the Future**

## Evacuations are Primarily a State Responsibility

- The Federal Government is committed to assist
- DOT and FEMA are partners

## DOT/FEMA Partnership:FEMA Responsibilities

- Establish ELT as part of ESF-1
- Coordinate expansion of ELT to all Regions
- Region 4 in 2000
- Begin Regions 3 & 6 in 2001
- Mission assign ELT during evacuations

- Assist with SOP
- Assist with TDFS
- Data from evacuation studies
- Add TDFS to Hurrevac
- Provide ELT work station in ROCs
- Include ELT in training courses
- Exercises
- Scenario development
- FEMA staff & other ESFs

## DOT/FEMA Partnership:DOT Responsibilities

**Office of Emergency Transportation**
- Lead organization
- Coordinate multi-region DOT Issues
- Integrate ELT into Activation Information Management (AIM) System
- Future hosting of server and backup

## DOT/FEMA Partnership:DOT Responsibilities

**Federal Highway Administration**
- Lead for Travel Demand Forecasting System
- And other ITS applications
- Contractor support for exercises
- Cover ELT in Emergency Preparedness Seminars
- FHWA Divisions work closely with state DOTs

## DOT/FEMA Partnership:DOT Responsibilities

**Regional Emergency Transportation Coordinators**
- Lead for ELT when operational
- Regional training for ELT federal and state partners
- Organization and management of exercises

## Theodore Roosevelt...

**Not every problem can be solved,**
**But every problem **
**  ****can be addressed****.**