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

## National Bioterrorism Hospital Preparedness Program 

**Brad Austin, M.P.H.**
- Commander, U.S. Public Health Service
- Hospital Bioterrorism Preparedness Program
- Human Resources and Services Administration
- US Department of Health and Human Services

## Mission Statement

*“**To ready hospitals and supporting health care systems to deliver coordinated and effective care to victims of terrorism and other public health emergencies”*

## Cooperative Agreements with:

- State Health Departments
- DC, New York, Chicago, Los Angeles
- Puerto Rico, Virgin Islands, American Samoa, Guam, Northern Marianas
**Marshall Islands, Micronesia and Palau just added in FY 2003 **

## Hospital Preparedness Program

- $135 M for hospital preparedness (2002)
- $514 M appropriated in 2003
- New guidance just published May 2
- “Hospital preparedness and infrastructure”

## Surge Capacity

- Hospital bed capacity
- 500 acutely ill patients / million population
- Decontamination facilities
- 500 acutely ill patients / million population
- Isolation facilities
- At least one per grantee
- To support 10 patients at a time

## Surge Capacity

- Maximum patient load
- To prepare for an overwhelming number of patients either for an acute period or over an extended period of time

## Surge Capacity

- Beds
- Staffing
- Equipment
- EMS Systems

## Surge Capacity

- Health care personnel
- 250 additional / million in urban areas
- 125 additional / million in rural areas
- Personal protective equipment
- Sufficient to protect these personnel

## Surge Capacity

- Pharmaceutical caches
- Local pharmacies
- Till Strategic National Stockpile is delivered
- Communications and information technology
- Secure and redundant
- Connects health care system components

## Regionalization Approaches

- One hospital alone not sufficient
- HRSA lets grantees define this to best facilitate their own geography and circumstances

## Surge Capacity and Regionalization

- Primary health clinics, IHS facilities, VA hospitals, military medical facilities
- Integrate strengths of individual facilities and systems
- Begin by assessing your current local and regional capacity

## More Program Information

- _[http://www.hrsa.gov/bioterrorism.htm](http://www.hrsa.gov/bioterrorism.htm)_
- CDR Brad Austin
- (301) 443-1860
- BAustin@hrsa.gov
# Presentation: 004604

## Computer Homework #3: Vertical Orbit Correction

- Given the following middle layer commands:
- 	y = getam('BPMy');     % Vertical orbit at BPMs (result is vector of length num_bpmy)
- 	Ry = getrespmat('BPMy', 'VCM');       % Get the vertical BPM response matrix 			                  % Matrix size is num_bpmy*num_vcm
-      num_bpmy = length(getam('BPMy'));	% get the number of vert. BPMs
-      num_vcm = length(getam('VCM'));	% get the number of vert. correctors
- 	vcm = getsp('VCM');   % Get the vertical corrector setpoints
- 	setsp('VCM', vcm);     % Set the vertical correctors (absolute)
- 	stepsp('VCM', vcm);    % Increment the vertical correctors
*To solve the following homework problem, please also consult the computer class slides (if you cannot find them: *_[http://als.lbl.gov/als_physics/csteier/uspas08/](http://als.lbl.gov/als_physics/csteier/uspas08/)_*) from Monday, they include one example very similar to part of this homework!*
**Write a Matlab script to**:
-  1. Create a random orbit error with the following commands (before starting set the correctors to zero and take a reference orbit):
- 	vcm_err = 0.1 * randn(num_vcm,1);     % num_vcm horizontal correctors at the ALS
- 	stepsp(‘VCM', vcm_err);

- USPAS, Annapolis

- June 16-20, 2008

## Homework #3 (continued)

*For the following parts remember for loops in Matlab (>>help for), as well as the possibility to add new data to a vector (like yrms(loop)=std(gety) with loop being incrmented in the for loop).*
- 2. Correct the orbit using various numbers of SVs:
-     a. Plot the singular values (i.e. the diagonal elements of the matrix S after the SVD inversion) of the response matrix (using semilogy)
-     b. Plot the remaining RMS and Max orbit error (std and max(abs)) vs. # of the singular values used in the orbit correction (the example in the computer class used 48).
-         i.e., plot the orbit error when 1 sv is used, 1:2 sv, 1:3 sv, 1:4 sv, etc. (up to num_vcm)
*	**Important: Do not forget to remove previous correction before applying new one!*
-     c. Plot the total corrector strength change  (sum(abs(DeltaVCM))) as well as total strength plus initial error (sum(abs(DeltaVCM+vcm_err)))  vs.
-         # of the singular values used.
-     d. How many singular values would you recommend using?
- Now remove the random orbit error (removing what you did in 1.) and only put one big error in, set any of the VCMs for example to 1 A.
- Repeat step 2. a-d above. Does the ‘optimum’ number of SVs change?

- USPAS, Annapolis

- June 16-20, 2008
# Presentation: 208093

## Jefferson LabSite Report

**Kelvin Edwards**
**Thomas Jefferson National Accelerator Facility**
**Newport News, Virginia USA**
**Kelvin.Edwards@jlab.org**
**757-269-7770**
**http://cc.jlab.org**
**HEPiX – October, 2004**

## Central Computing

- Email
- Distracted by SPAM problem 
- Evaluated and purchased MXLogic
- Offsite solution
- Filters virus/spam before getting to Lab
- Upgraded our email hardware
- Windows builds
- Purchased MS Enterprise Agreement
- Developed an automatic build process
- Upgrading all of our systems to Windows XP
- Still evaluating SP2, problems with CAD, etc.

## File Server Storage

- Adaptec 2200S Raid and Linux XFS
- Linux kernel 2.6 and Adaptec firmware (build 7244)
- It doesn’t work (I/O errors, etc.)
- RedHat EL3 WS kernel works fine, but no XFS support
- Tested ext3 performance
- unacceptable (20MB/s read, 34MB/s write)
- XFS performance (approx 100MB/s read/write)
- Dropped back to prior Adaptec BIOS and 2.6 kernel works fine

## File Server Storage (cont)

- Purchased 2 StorageTek B280 systems
- 14 TB of disk space
- 4 Sun V210 head units
- Stable, but slow, NFS performance
- Aggregate -- 6MB/s write, 63MB/s read
- Each node -- 0.13 MB/s write, 1.4MB/s read average

## File Server Storage (cont)

- Evaluating 10TB Panasas system
- Tested 2 protocols (directFLOW and NFS)
- No directFLOW problems
- NFS finally stable at version 2.1.4c
- Good performance with either
- Aggregate -- 160-185MB/s write, 100-180MB/s read
- Each node – 3.5 - 5MB/s write, 2.5 - 4.5 MB/s read

## Jasmine Changes

- Jasmine is Jlab’s mass storage system (disk+tape) stores ~1PB and can routinely move 20TB/day.
- Disk cache system recently rewritten for performance and reliability
- I/O load spread out over pool of many disk servers
- Files belong to file groups (per experiment) with quotas
- Quotas may be exceeded if there is enough disk space; allows more flexible use of disk
- Files deleted from servers in a modified LRU fashion
- Files may be pinned until used by the batch farm

## Jasmine changes (2)

- New programmatic interfaces for
- Batch Farm (Auger)
- Other services that need to move files (SRM, DAQ, LQCD disk cache)
- More reliance on MySQL database; concurrency and load are challenging
- Writing 9940B tapes
- Experiment data rates now ~30MB/sec

## Auger Changes

- Auger is Jlab’s Batch farm management system.
- Uses LSF to run jobs, keeps accounting in a database for web or command line presentation.
- Users can submit thousands of jobs using a compact job description that includes file retrieval and storage.
- Interfaces with Jasmine to stage files to disk before the job runs on the farm to keep CPUs busy

## Jasmine & Auger Web Interface

- Java Server Pages

## Projects

- Email upgrade
- Still evaluating software/hardware
- Desktop systems
- MacOS-X
- Linux, Unix
- Windows
- Power/Cooling issues
- Reached limit of current Computer Room
- New Computer Center to open in Jan 2006
- Increased power requirements for 800 MHz FSB systems
- 1.3A to 2.1A (single CPU)
- 1.6A to 2.8A (dual CPU)
- Shutdown problems with non-ACPI enabled systems
# Presentation: 172052

## Integrating 3-D Scanning into the AGSharing Special Purpose Devices

*Michael E. Papka*
*and *
*Futures Laboratory*
*Argonne National Laboratory*

## Integrating remote devices

*Analytical Electron Microscope *
*Web based interface*
*Collaborative*
*Custom built*
*Other devices*
*Telescope*
*MRI machines*
*3D scanners*
*Remote nodes?*

## What does it mean to have a remote device in a shared space?

*Controls?*
*How does control get exported, does everyone have control?*
*Status?*
*What is the status of the device? How is that updated?** *
*Data?*
*What data is shared? How does this change?*

## Interface to remote device

*Device specific*
*Does every device need a custom application?*
*Generalized toolkit*
*Definition by abstract interface? *
*Self publishing interfaces?*
*Generic client front-end*

## Access Grid Entities

## 3-D scanner integration

*This is **not **how to display in 3D on AG*
*Interface to remote scanner*
*Interact with scanner*
*Interact with output *

## Interaction with scanner

- Security
- Server

- Virtual Venue

- Venues Server

- Access Grid Node

*Interaction with scanner*

- Scanner
- Server

**Scanner**
**User #1**

**Scanner**
**User #2**

## To acquire a scan

*Operating the scanner*
*Exporting of controls*
*Handling multiple users*
*Addressing problems of distance*

*User Commands: Keyboard, Mouse, Menus, Buttons *

## Example of 3D Object

*Vase*
*136192 Polygons*
*17s scanning (1 scan)*
*~8000 poly/s*
*~1 Mbit/s*
*Isis*
*375284 Polygons*
*44m scanning (34 scans)*
*~140 poly/s*

## Output viewer

*Controls*
*Changing viewpoint*
*Rendering output*
*Changing view parameters*
*Hiding information*
*Performing measurements*
*Capturing images*

## Scanner to AG

*What does the scanner output?*
*Conversion of output (server) to client format*
*Conversion to AG supported format*
*What about node capabilities?*

## Intelligent interaction with output

*Knowledge of application performance*
*Network services*
*Graphics capabilities *
*Knowledge of underlying machine capabilities*
*Machine querying tools*

## Output on the AG

*Interactive interface*
*Flexible interface *
*Collaborative*
*Annotation*
*Recordable*
*Model*
*Interaction*
*Annotation*

## Interface

*Same client interface for all devices?*
*How is sharing information presented?*
*In interface?*
*In data**?*
*Does everyone get the same controls?*
*Does everyone get the same view?*
*How are different presentation modalities handled?*
*Sitting at laptop versus presenting in front of group*

## Annotation

*How do you annotate?*
*Pointing*
*Voice comments*
*Data manipulation*

## ? Device Integration

**scanner**

**Remote**
**Device**
**Server**

**Control**
**Stream**

**Data**
**Stream**

**C**

**C**

**Multicast**

## References

*Scanner Information*
*www.cyberware.com*
*www.cyra.com*
# Presentation: 253722

## Population Genetics of Puccinia coronata f. sp. avenae

- Population Genetics of *Puccinia coronata *f. sp*. avenae*
*Hattie Dambroski and Martin Carson*
*USDA-ARS*
*Cereal Disease Laboratory*
*Saint Paul, MN*

## Oat Crown Rust

**Oat Crown Rust**

## Puccinia Pathway

**Puccinia Pathway**

## Objective

**Objective**

- To study the diversity and population structure of *Puccinia coronata*.
-  sexual populations in the north
-  asexual populations in the south

## Microsatellites

- DNA isolated from germinated and non-germinated urediniospores
- Five DNA samples isolated from aeciospores
- 41 dinucleotide microsatellites
- Target sequence (CA)n
- Highly Polymorphic, allelic diversity ranges from 2 to 22

## Populations

**Populations**

** ****Northern Populations**
** ****MN, ND, SD, ****WI****, ****NE**
** ****Southern Populations**
** ****NC, FL, LA, ****AL**
** ****Texas**
** ****California**
** ****Foreign Populations**
** ****Brazil, Israel, Russia, Egypt, ****Australia****, ****Mexico****, ****Canada****, ****Uruguay****, ****Turkey****, ****Argentina**

## Isolates

## Statistics

- HO ranged from 0.014 to 0.973
- HE from 0.166 to 0.742
- 11 loci are in Hardy-Weinberg equilibrium (P<0.05)

## Preliminary Results

**Preliminary Results**

- AMOVA showed most molecular variance within populations vs. among populations
- Neighbor joining tree based on genetic distance

## Tree Results

**Tree Results**

- Group with little genetic differentiation forming between north, south and Texas populations (asexual pop.)
- Northern aecial isolates form a group with greater genetic differentiation between isolates (sexual pop.)
- California isolates forming own group with great genetic differentiation from other groups

## Things yet to do.....

**Things yet to do.....**

- Finish U.S. Isolates
- Screen Foreign Isolates
- Screen Markers on other Rust species
- Analyze data
# Presentation: 721248

## SUDS Testing Trends 2001Quarterly trends of positive tests

***Maupin, Medical Center of Louisiana, New Orleans***

**Notes:**
SUDS test assay kits unavailable for clinical testing Jan. – Mar. 2001.

A single positive SUDS/negative EIA reported but the Western blot was repeatedly indeterminate. 

## SUDS Test Performance - 2001

**413 SUDS test performed for obstetric indications**
**9/12 positive SUDS confirmed - EIA/WB**
**HIV seroprevalence – 2.2% among SUDS tested pregnant women**
**Sensitivity /Specificity:****	****100% / 99.3%**
**POS PV/ NEG PV:****	****	****75% /100%**
**SUDS identified an estimated 8.4% of HIV exposed births in the New Orleans metropolitan region* **

***Maupin, Medical Center Louisiana, New Orleans***

**Notes:**
SUDS testing in 2001 implemented with confirmation of a positive SUDS with a second/repeat SUDS test.

No cases of a negative SUDS associated with positive EIA confirmed with Western blot.

Sensitivity, specificity, positive/negative predictive value corresponds to the test performance demonstrated in 1999 (similar seroprevalence of 2.3%).

*Estimates based on crude comparisons of the Hospital Office of Infection Control database with the Louisiana Office of Public Health database (metropolitan perinatal transmission rates for 2001: 2.8% of HIV exposed births).

## SUDS Testing Trends 1999-2001Monthly trend of total tests conducted

***Maupin, Medical Center of Louisiana, New Orleans***

**Notes:**
Annual total for 1999: 703 tests performed (seroprevalence, 2.3%)
Annual total for 2000: 1075 tests performed (seroprevalence, 0.9%)
Annual total for 2001 – 413 tests performed. (test assay kits unavailable for the months of Jan. – Mar.)
# Presentation: 249206

## Analysis of Seasonal to Decadal Variability in a Coupled General Circulation Model

- Sonya K. Miller1, Michele M. Rienecker2, Max J. Suarez2, Siegfried D. Schubert2, Philip J. Pegion1, Julio T. Bacmeister3

*Affiliations:*
*Global Modeling and Assimilation Office, NASA/GSFC*
*(1) Science Applications International Corporation*
*(2) NASA/Goddard Space Flight Center*
*(3) Goddard Earth Sciences and Technology Center, UMBC*
*Greenbelt, MD*

- Contact Information:
- Sonya.K.Miller.1@gsfc.nasa.gov
- http://gmao.gsfc.nasa.gov
# Presentation: 906575

## ESM2.1

## Background

- Use CM2.1
- Make as few changes to physical climate as possible
- Focus on biology issues
- Exchange LM2 with LM3V
- Add ocean bio-chemistry
- GOAL: Drift less than 10 ppm atm pCO2 per century in 1860 control

## Exchange LM2 with LM3V

- Used atm-mixed layer model for development
- Found many problems and did some tuning (both physical climate and biology)
- Last big issue was “water leak”
- Mixed layer model with LM2
- LM3V
- Happy with LM3V atm-mixed layer model simulation
- Developing new flux adjustments/atm-mixed layer model in OMSK

## ESM2.1- Where we stand

- Everything originally slated to go into ESM2.1 – now in it
- Development on-going
- New stuff will go into ESM3
- LM3V and Topaz (ocean bio-chemistry)
- Start from CM2.1 1860 control, year 1901
- 100 year test

## ESM2.1- Where we stand

- Relatively happy with run (*a good ****start***)
- Physical climate seems very similar to CM2.1
- Carbon drifts => tuning needed
- Soil carbon needs initialized better
- Ocean carbon needs more tuning
- Seems possible to get close to goal of drift less than 10 ppm pCO2 per century

## ESM2.1 – Physical climate

- Compare ESM2.1 physical climate to CM2.1
- LM2 => LM3V
- Ocean color changes
- Global time series
- Difference maps/sections
- ENSO

## Global top of atm net radiation

## Global heat flux into ocean

- T_REF Annual Mean Difference

- T_REF Difference

- Zonal mean Precipitation difference (cm/day)

## Nino3.4SST(170W to 120W, 5S to 5N)

## ESM2.1					CM2.1

- ESM2.1					CM2.1

## ESM2.1- Where we stand

- Relatively happy with run (a good **start**)
- Physical climate seems very similar to CM2.1
- Carbon drifts => tuning needed
- Soil carbon needs initialized better
- Ocean carbon needs more tuning
- Seems possible to get close to goal of carbon drift less than 10 ppm pCO2 per century
# Presentation: 487616

## Improving Data Access and Outreach

- MODIS Land Data Products
- Marilyn Kaminski – NSIDC DAAC
- John Dwyer – LP DAAC

## User Community Continues to Grow

**User Community Continues to Grow**

## Data Access 

- Entire Inventory
- Eos Data Gateway
- Specialized Collections
- Data Pools
- Machine-to-Machine Gateway
- Subscriptions
- NSIDC Unique
- SNOWI/MODIS SNOWI
- LP DAAC Unique
- GloVis
- USGS Seamless (MOD13A2)

## Tools

- HEW Subsetting Applicance (HSA)
- HDF-EOS to GeoTIFF (HEG)
- MS2GT
- MRT
- MRTSwath
- LDOPE Tools
- MODextract

## Outreach

- Upcoming Workshops
- MODIS Vegetation Workshop – U.MT
- EOS Snow and Ice – Maryland
- MODIS & ASTER – U. Saskatchewan
- MODIS & ASTER – EDC
- IGARSS Tutorial Workshop – Anchorage
- User Email Broadcasts
- Newsletter
- Web Site Content
# Presentation: 132547

## Role of Project Officer

- During the acquisition process . . .
- Define the requirement.
- Prepare/process 40-1, 60-1a, or 60-1.
- Monitor the contract.
- Ensure Government funds are expended properly.

## Role of Project Officer

- During the acquisition process . . .
- Remember limitations of authority.
- Avoid circumstances/situations subject to criticism or additional claims.
- Complete administrative responsibilities.

## Role of Contracting Officer

- Has authority to obligate Government.
- Solicits proposals/bids/quotes.
- Modifies terms of contract.
- Issues instructions to contractors to start/stop work.

## Role of Contracting Officer

- Approves items not authorized by contract.
- Executes supplemental agreements.
- Renders decisions in accordance with FAR and Agency regulations.
- Takes action regarding termination.
- Gives guidance to contractors.

## Examples of Prohibited Actions

- Using public office for private gain.
- Giving preferential treatment to any person.
- Making decisions outside official channels.
- Affecting the public’s confidence in the Government’s integrity.

## Ratification of Unauthorized Commitments

**UNAUTHORIZED COMMITMENT:** An agreement that is not binding solely because the Government representative who made it lacked the authority to enter into that agreement on behalf of the Government.
**RATIFICATION:**  The act of approving an unauthorized commitment by an official who has the authority to do so.
# Presentation: 400090

## Proposal to study the effect of HFS gas flow rate on ELM characteristics

- D. Mueller, R. Maingi

## Load-and-Dump Gas Injectors Have Different Flow Characteristics and Delay Time

## Comparable Performance with Shouder Fueling but ELMs different (drsep=0)

## Comparable Performance with Shouder Fueling but ELMs different (drsep=-0.7cm)

- Midplane
- P=1400 torr

- Shoulder
- P=700 torr

## H-mode Access Developed with CS shoulder fueling Changed ELM characteristics, flow rate or location?

**CS shoulder gave comparable or higher stored energy than CS midplane in comparison shots **
**More CS shoulder gas needed as drsep is increased for H-mode access -> increased leakage to outboard side?**
**ELM free periods with CS shoulder fueling**
**Difference in  ELMs using CS mid or CS shoulder is due to location or flow rate (or both).   **
**Match CS mid flow rate for location comparison.**
**Modify flow rate (t) to change ELM behavior.**
**Proposed controllable made valve possible by redesign of PF1A that gives access to CS at shoulder from outside vacuum.  Detailed design in progress.  Goal to provide up to 100 Tl/s and no/little “dribble”.**

**H-mode Access Developed with CS shoulder fueling ****Changed ELM characteristics, flow rate or location?**
# Presentation: 549171

## Monopoly Agreements & Cartels

- 陈
- 懿
- 华

- Yee Wah Chin

- 2006 U.S./China Legal Exchange
- Washington, D.C.
- December 8, 2006

- docprcaml

- 12/7/06

## Lessons Learned

- Legislation to enunciate general principles
- Implementing regulations & enforcement to develop specifics
- Exemptions
- Remedies

- docprcaml

- 12/7/06

## General Principles

- Differentiation between agreements among competitors and among undertakings at different levels of an industry
- Principle of “purpose or effect of eliminating or restricting competition” as test for violation
- Limited number of specific prohibitions
- Per se offensive horizontal agreements
- Differentiation between price fixing & bidrigging
- Resale price agreements
- U.S. per se rule / rule of reason – cert. granted 12/7/06 in *Leegin Creative Leather Products, Inc. v. PSKS, Inc.*, No. 06-480
- EU per se rule

- docprcaml

- 12/7/06

## Development of Specifics

- Procedural challenges
- Rules for the process by which
- future rules will be developed
- enforcers will implement the law
- Insulation from political influence
- Substantive standards
- Definitions
- Horizontal agreements – Arts. 3, 7; implementing regulations
- Vertical agreements – Arts. 3, 8, 15; implementing regulations
- “other monopoly agreements determined by the Anti-Monopoly Law Enforcement Authority[ies?]” or “imposing other trading conditions [that] eliminate [or] restrict competition” – Arts. 8, 9, 15

- docprcaml

- 12/7/06

## Exemptions

- Nature, scope & duration
- Cannot be justified on ground of fostering competition
- Non-competition factors
- Cost-benefit analysis – Art. 10 preamble
- Draft & interpret narrowly, to minimize distortions in the marketplace
- SOEs; administrative monopolies
- Experience of U.S.
- Articles of Confederation
- U.S. Constitution
- Sherman Act
- De facto exemptions? – Arts. 2, 44.

- docprcaml

- 12/7/06

## Remedies

- Penalties
- Goal of restoring competition, not just punishing offenders
- Minimum percentage of turnover v. absolute amount that may be adjusted by regulation as economy evolves
- Leniency

- docprcaml

- 12/7/06

## Monopoly Agreements & Cartels

- 陈
- 懿
- 华

- Yee Wah Chin
- yeewah.chin@gmail.com

- 谢
- 谢

- Thank you

- docprcaml

- 12/7/06
# Presentation: 663526

## Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

**Task 7.1**:   Monitor implementation
**Task 7.2:**   Evaluate the plan
- 	**Task 7.2 (a):**  Indicators or benchmarks
- 	**Task 7.2 (b):**  Update vulnerability assessments
- 	**Task 7.2 (c):**  Update capability assessment
**Task 7.3:   **Continued public involvement
**Task 7.4:    **Periodic evaluation report

**Tasks in Step Seven**

**Slide 42.1**

**Notes:**
This template should be used to insert text and graphics

##     Hazard Mitigation Planning VI

-     Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

**	****	**
**     ****Worksheet #5: Geographic Planning Area Policies**

**Slide 42.2**

**Notes:**
This template should be used to insert text and graphics

## Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

**Worksheet #5A: Community Mitigation Action Plan**

**Slide 42.3**

**Notes:**
This template should be used to insert text and graphics

## Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

-      number of development permits issued annually
-      reason  for permits denial
-      location of new infrastructure
-      yearly number of new culverts/bridges
-      acreage of wetlands lost annually
-      number of new housing units in hazard areas
-      number and location of new mobile home units
-      evacuation route capacity in relation to population growth
-      number of businesses that purchase flood insurance
-      percentage of vacant land/uninhabited structures in hazard areas
-      number of repetitive flood damage properties sold/acquired/relocated

**Benchmarks of Progress**

**Slide 42.4**

**Notes:**
This template should be used to insert text and graphics

## Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

**Task 8.1**:    Designate an executive position to review and present
- 	     the plan
**Task 8.2:**    Local governing body decides whether to authorize

**Tasks in Step Eight**

**Slide 42.5**

**Notes:**
This template should be used to insert text and graphics

## Hazard Mitigation Planning VI

**Session Name: Hazard Mitigation Planning VI**
**Coastal Hazards Management Course**

**Task 9.1:**    Follow Local Governing Body’s Standard Legal Processes
**Task 9.2:**    Hold Public Meetings
**Task 9.3:**    Incorporate Public Comments and Revise the Plan
**Task 9.4:**    Submit the Plan to State authorities and FEMA

**Tasks in Step Nine**

**Slide 42.6**

**Notes:**
This template should be used to insert text and graphics
# Presentation: 476291

## Data Stewardship Subgroup for Climate Services

- Sub-Regional Climate
- Services Meeting
- Boulder, CO 8/24-25/04

## One (BIG) Goal

- Establish Quality Control and Assurance Standards
- Partner with ER, NCDC and CSD to determine national standards
- Training on the importance of data accuracy, measurement and consistency
- Establish regional intranet site with best practices, training materials, national and regional QC standards

## Regional Quality Control and Assurance Standards

**To begin addressing this issue a survey was implemented to determine:**
**the state of QC/QA across Central Region**
**the minimum level of QC standards for the WFO and RFC**
**the software and techniques used at each field office**
**Results:**
**As expected, QC/QA in some disarray**
**All offices doing well in some aspects but office-to-office consistency poor**
**Need more consistency in tools used, timeliness and regional enforcement **

## Partnership with ER, NCDC and CSD to determine national standards

**Once the Central Region, Eastern Region and NCDC team have determined standards the recommendations will be sent to other regions and HQ for input and revision**
**Complex and long term process**
**Do we need to include other partners in the process?**

## Training

**Team will create or make available tools that will emphasize:**
**the importance of accuracy, consistency and measurement**
**the importance of gage exposure and surrounding environment**
**the importance of station metadata**
**operational best practices of quality control**

## Data Stewardship Intranet Website

**Site should include but not be limited to:**
**Training Materials mentioned previously**
**Current Regional QC output**
**Link to NCDC QC/QA procedures**
**Link to NCDC operational changes to field office data**
**Standardized QC procedures for all field offices**
**Best practices for QC/QA**
**Should we put all or part of this on the internet?**

## We’re Looking for Ideas and Input

***Quality Control/Assurance***
***Climate Monitoring***
***Data Partnerships***

## Thank You
# Presentation: 013070

## Comments on Dark Energy Experiments

- Tim Mckay
- July 14, 2001

- Outline:
- General comments on techniques
- Some scary lensing details
- Comments on survey depths

## Measurements of dark energy

- Basic approaches:
- 	Cluster counting
- X-ray selection: Flux limited
- SZ surveys: redshift independence
- Lensing surveys: clean mass selection?
- Optical surveys (!)
- 	Structure Formation
- Galaxy LSS from spectroscopic surveys
- Weak lensing power spectrum
- 	Angular diameter distance
- Strong lensing statistics
- 	Luminosity distance
- Type Ia SNe

## What to worry about...

- Age of statistical astronomy, large samples are not a problem
- Systematics _will_* *limit all these experiments: Predictions must include estimates of these
- Cluster counting:
- 	Mass thresholds, cluster evolution...
- Structure formation:
- 	Bias, selection function....
- Strong lens surveys:
- 	Selection effects, halo profiles....

## An example from lensing, mass scale...

## Some predictions...

- SNe will play a key role:
- Discovered dark energy
- Local physics....
- Systematics known
- Evolution
- Dust
- Malmquist bias
- Lensing magnification

- Ground or space?

## Comparison of ground and space based optical surveys

- We have completed detailed comparisons of ground based and space based optical surveys from first principles
- 	Gary Bernstein, 2001, submitted to PASP
- Calculations for PSF photometry
- Includes undersampled and dithered images
- Includes cosmic ray rates
- Includes intra-pixel sensitivity variations (10% gutters)
- Calculated for point source and galaxy photometry
- Determines astrometric errors
- Determines galaxy shape errors

- Allows us to answer some commonly arising questions about imaging strategies:
- What amount of dithering is ideal?
- What pixel size optimizes the productivity of a camera?
- Which is more efficient; space-based or ground-based observing?

## Supernova survey efficiency for SNAP and LSST:

- z=1.5

- z=1.0

- z=0.8

- LSST is better at z<0.7
- SNAP is much faster for high-z objects

## Weak Lensing Survey Speed: including effects of galaxy size

- Galaxies must be resolved for use in weak lensing analyses. HDF studies (Gardner & Satyapal, 2000) show that galaxies become _*much*_ smaller at faint magnitudes.

- Median HDF galaxy sizes at 3 magnitudes

- Approximately 85% of galaxies with r<30 are between r=27 and 30....

## A few conclusions

- Many techniques required to constrain dark energy
- All will be systematics limited
- Sensitivity estimates should include reasonable systematics guesses
- Only SNe have detected dark energy and faced systematics:
- 	They will play a key role in the coming decade
# Presentation: 701316

## Future Recording Requirements and Capabilities in the Oil and Gas Industry

- Future Recording Requirements and Capabilities in the Oil and Gas Industry

- Turning Science Fiction into Practical Applications
**Daniel W. Nagala, UTSI International**

*International Symposium on Transportation Recorders*

## Introduction 

- Introduction

- Pipeline System Data Recording Concepts
- Incident Analysis Today
- Future Vision and System Requirements

## Typical Pipeline SCADA System

**Users**

**Server Components**

**Communications**

**RTUs & PLCs**

**Field Devices**

**Master Station**
**Connectivity**

## Current State of Industry

- Minimal Information Maintained
- Disparate Systems and Techniques
- Not Correlated in Time and Sequence

## Present Day Usage

- After an Incident or Anomalous Operational Event
- Difficulties in Gathering Pertinent Data
- Limitations and Deficiencies

## Future Vision

*Full Scope Inline Simulation Systems*
- Integration of Advanced Data Recording and Sophisticated Analysis Tools
- Seamless Access to Real-Time, Historical, and Simulated Views

## Conceptual Architecture

## Key Functional Components

- Common Configuration Definitions
- Historical Archive and Retrieval
- Historical Playback
- Transparent Switching Between Real-Time, History, and Simulation
- Standardized Interprocess Communication

## Data Requirements

- Every Data Item Acquired, Calculated, Entered, or Derived, At Real-time Resolution
- All Operator Actions, Including Navigation
- Alarms and Events in Correct Sequence
- All Configuration Changes, Updates, and Modifications

## User Interfaces

- Common Views Used by all Functions
- Simultaneous Access to Multiple Sources of Information
- Seamless Integration of Real-Time, Simulation, Historical Playback, and Training Functions

## Benefits

- Availability of Accurate and Precise Details
- Proactive and Preventive Response Protocols
- Facilitation of Better Training Programs
- Better Information for Enterprise-Wide Decisions to be Based Upon

## Summary

- Advances in Computer Technology Will Allow Techniques Like *Full Scope Inline Simulation* to Become a Reality Within the Next Six to Eight Years

## Contacts

**UTSI International Corporation**
- 1560 West Bay Area Boulevard
- Suite 300
- Friendswood, Texas USA 77546
- Telephone:	(281) 480-8786
- Fax:		(281) 480-8008
- Email:		info@utsi.com
- WWW:	      http://www.utsi.com
- Daniel W. Nagala (*dnagala@utsi.com*)
- President & CEO
- Gerald E. Snow (*gsnow@utsi.com*)
- Vice President, Marketing

**UTSI International Corporation**
- Middle East North Africa
- Al-Masaood Tower, Suite 704
- Abu Dhabi,      UAE
- Telephone:	971-2-333-336
- Fax:  		971-2-333-337
- Email:  	          jsanow@utsi.com
- Jeffry S. Sanow (*jss@utsi.com*)
- Regional Marketing Director - MENA
# Presentation: 840573

## Autonomous Operation Robotic Vehicle System

**S**mall
**B**usiness
**I**nnovation
**R**esearch

**Omnitech Robotics**

- Englewood, CO

**ACCOMPLISHMENTS**
-  Open system architecture hardware and software infrastructure for configuring vehicle to use a variety of sensors and navigation strategies
-  Graphical interface for programming
**COMMERCIALIZATION**
-  Control system for environmental cleanup robotic vehicles
-  Sales exceed $250,000 annually

**GOVERNMENT/ SCIENCE APPLICATIONS**
-  Military vehicle operation for land mine proofing and clearance

***Vehicle Capable of Remote Control, Teleoperation, or Autonomous Operation ***

- Jet Propulsion Laboratory

- 1992 Phase II; NAS7-1302
- Success Story # 7-010

**INNOVATION**
- Vehicle control system providing for Teleremote or
-  autonomous operation using multiple sensor inputs
# Presentation: 071926

## Control Room Logbook (CRL)

- _[http://www-cpd.fnal.gov/CRL/](http://www-cpd.fnal.gov/CRL/)_
- Status Meeting
- Suzanne Panacek

- CRL, spanacek@fnal.gov

- 04/05/2005

## Project Drivers

- User feedback
- Users: D0, Minos, CMS, MiniBoone, Computer Security, Mipp, Westing House, EGO
- Each installation has designated admin. Casual and frequent communication via email or phone.
- New ways to use the CRL
- The Web is the preferred way to use it. All new development is in the CRLW (CRL Web application). The desktop application is still available and provides the base code for the CRLW.
- The users have now a large archive of entries (D0 – 400,000 entries). They want to categorize, organize, make lists, and link entries in their own context.
- Need for speed, and more speed, especially for retrieving and searching entries.
- New users – outside the control room and outside FNAL
- Projects are using the CRL outside control room for keeping meeting notes or a log of any kind (computer security)
- Users outside of FNAL are interested. Savanna Westing house and EGO are using it.

- CRL, spanacek@fnal.gov

- 04/05/2005

## Deliverables

- Current deliverables
- Release about every other month
- User’s Manual
- Web site
- Web server (crlweb) CRLW upgrades
- New web server to off load crlweb  (current load: max daily hits 25000, max daily data transfer 700 MB)

- CRL, spanacek@fnal.gov

- 04/05/2005

## Future Deliverables

- Test CRLW with the latest release of Tomcat, Java, and Apache on new web server.
- Context building
- Speed improvements
- Indexing for searches - maybe
- Simplify installation and deployment
- Clarify licensing for international and commercial users.
- New users: ILC ?

- CRL, spanacek@fnal.gov

- 04/05/2005

## Milestones

- Last 3 months:
- Ability to move entries from one category to another
- Speed improvements
- Minor fixes such as buffer limits on forms (forms are getting more and more popular)
- Purchased new web server
- Resolved licensing for Savanna Westing House and made CRLW available on Fermi tools
- Installation at EGO (European Gravitational Observatory) in progress.
- Next 3 months
- Requirements and design for ‘context building’
- Speed improvements
- New web server
- New users (ILC?)

- CRL, spanacek@fnal.gov

- 04/05/2005

## Effort Profile

- People:
- Suzanne Panacek – development, documentation, upgrades on crlweb.  50%.
- Etta Burns purchasing and installing the new web server. ?%
- Ongoing program of work at about 30%.

- CRL, spanacek@fnal.gov

- 04/05/2005

## Risk

- No major risks
- Minor Risk:
- Upgrading to Tomcat 5 and Java 1.5 requires major changes in code.
- Speeding up the search and becomes very complex (can we use what the HEPBook is using?)

- CRL, spanacek@fnal.gov

- 04/05/2005
# Presentation: 201900

## METS Creationin a production environment

- METS Opening Day
- _[Corey Keith](http://www.coreykeith.com/)_
- ckeith@loc.gov

## Introduction

- Evolution of Tools
- Demo

**Notes:**
Don’t make the mistakes we did

## Carl’s Talk

- METS Editor
- Pros
- Create and edit all METS
- Cons
- Too much METS knowledge needed for production staff
- Too slow for volume production

## Just Enough Approach

- Appropriate tools product appropriate metadata
- Extract Technical

## Version 1.0

- Access DB -> XML via XML Spy
- Filesystem directory structure -> XML via Perl Script
- XSLT builds METS object
- PROFILE + Filenaming Conventions = Structmap
- Extract technical metadata from files
- Descriptive from DB

**Notes:**
Lots of Access Skills at LOC
Is this needed

## Pros

- Production staff understood the database
- Higher Throughput
- “METS Creation” and profiles controlled by generation

## Cons

- DB wasn’t normalized
- Multiple copies of DB
- Little constraints on DB data
- Scalability
- Weak descriptive metadata

**Notes:**
DB was designed by production staff

## Version 2.0

- MYSQL DB
- MS Access Frontend
- Apache/Tomcat
- Cocoon
- XML/XSLT

**Notes:**
Roy Tennet XML4LIB XML/XSLT as a hammer

I look at XML/XSLT as a hammer -- once you have it, > and know how to use it, you find all kinds of uses for it that would > not necessarily have occurred to you without that tool in your hand. I > liken this to Perl (insert your favorite web scripting language here), > which once you know it, you find all kinds of uses to which to put it. 
Cocoon in later dissemintation presentation

## Demo

## Pros

- Multiple interfaces to back end DB
- Centralized DB & Application Code
- Better support for MODS
- Controlled
- Instant feedback XML generation on the fly
- Profile Validation

## Cons

- Still using Access for front end
- Efficient data entry from web based forms?

## What you need to take away from this presentation

- Avoid developing your own METS editor
- Use your best hammer for the job
- Perl, Java, XSLT
- Tradeoffs between expressing features of METS and usability
- Specialized tools appropriate for the complexity of the profile

**Notes:**
Use XML Spy
Hammer = PERL/JSP/XML|XSLT
Keep the user in mind
# Presentation: 694027

## Stuff on MPC simulationsfor Ken/Matt 

- R. Seto
- march 29

## define eres=(e_prim-clus_e)/e_prim

- define fiducial as 12<r<18

- egood

- ebad

- emed

- this one
- must reflect
- mickeys
- thrown x and y
- distribution

- this
- shows
- the edges
- of the MPC

## eres vs e for R<r_fiducial

- slice up plot into bins of e_prim and fit width
- fit the widths to
- delta E/E_prim = A+B/sqrt(E_prim)
- fit for A and B
- One slice fit for E_prim=25 GeV
- delta E=0.03
- sqrt(25)=5
- B~15% if A is 0
- Ken and matt should do a full fit

- slice
- E_prim=25

## x,y prim for e_prim 0-5 GeVand eres in “medium” areashows leakage

- to get this plot I looked at data with e=0-5 GeV. I think this better because of the smaller radius of the showers?

## delta x =x_prim-x_clus

- For egood
- centered at 0.5, 0.5
- peak is not in center
- Shows structure of MPC modules
- RMS ~ 1cm

## same plot for emed

- peak now in center
- RMS ~ 1.5-2 (wider)

## snippet of code

- 	float r=sqrt(prim_x*prim_x+prim_y*prim_y);
-       h_cluse->Fill(clus_e);
-       h_prime->Fill(prim_e);
-       h_eres->Fill((prim_e-clus_e)/prim_e);
- 	if(r>12 && r<18)h_eres_vs_e->Fill((prim_e-clus_e)/prim_e,prim_e);
-       h_xy->Fill(prim_x,prim_y);
-       h_clus_xy->Fill(clus_x,clus_y);
- 	if( (prim_e-clus_e)/prim_e < 0.1){
-       		h_xy_egood->Fill(prim_x,prim_y);
-       		h_clus_xy_egood->Fill(clus_x,clus_y);
- 		h_delta_xy_egood->Fill(prim_x-clus_x,prim_y-clus_y);
- 		h_delta_x_egood_vs_e->Fill(prim_x-clus_x,prim_e);
- 	}
- 	if( (prim_e-clus_e)/prim_e > 0.1 && (prim_e-clus_e)/prim_e < 0.9 ){
-       		h_xy_emed->Fill(prim_x,prim_y);
-       		h_clus_xy_emed->Fill(clus_x,clus_y);
- 		h_delta_xy_emed->Fill(prim_x-clus_x,prim_y-clus_y);
- 	}
- 	if( (prim_e-clus_e)/prim_e > 0.9){
-       		h_xy_ebad->Fill(prim_x,prim_y);
-       		h_clus_xy_ebad->Fill(clus_x,clus_y);
- 	}
-    }

## notes

- I made the pictures just using the output file and root
- you should read the data files from mickey as he has set up. The filelist will let you read many files – this is the fun4all mode (which is all set up for you) – the ability to read many files is something we will have to figure out (its not hard)
- In my case I used a TChain – I cheated, but it wont allow me to a  access stiff  if its not in the ttree
# Presentation: 202937

## Antarctic field work

-  and the
- graduate student experience

- Jill Mikucki
- OPP-Polar Postdoc
- Harvard University

## ...or what I learned in field camp.

*...**or what I learned in field camp.*

- McMurdo Dry Valleys LTER and Microbial Observatories

-   Lessons learned
-   Postdoc transition
-   Preparing the Polar Postdoc application
-   Status

## Antarctic Field Research: The Process

## Antarctic Field Research: Character building 

- Antarctic Field Research: **Character building **

_**Teamwork:**_
-   Collaborate
-  “Speak new languages”
-  Develop a culture of ***synthesis***
- _ __**Leadership:**_
-  Make decisions
-  Take responsibility
-  Communicate effectively
-  Mentor* *

**Notes:**
a survival tactic in the Antarctic
A thesis was traditionally taught as a singular journey, but as sciences embraces complexity collaboration is critical. I worked within the context of a long term dataset.

## Antarctic Field Research: Independence 

- Antarctic Field Research:** Independence **

-   Explore
-   Provide a new perspective
-   Ask new questions
-  Develop research thesis under a powerful support network (PIs, OPP and Raytheon)

## Antarctic Field Research: Legacy 

-   The role of research in the history of Antarctic exploration
-   Contribution to a long-term dataset
-   Community of polar investigators

## Antarctic Field Research: Graduate student/Postdoc transition 

-   Opportunity to learn new skills
-   Continue my training as a polar scientist but ask
- 	compelling new questions
-   View the system and data with a new perspective

## Antarctic Field Research: Postdoc proposal thoughts 

-   Discussed my ideas with other Antarctic PIs
-   Read NRC reports (Frontiers in Polar Biology		 in the Genomic Era)
-   Met with prospective sponsor
-   Talked to my program manager
-   Thought about my career goals

## Antarctic Field Research: A few months in...

-   Training on new (*prototype*) equipment
-   Exposure to new disciplines, techniques and perspectives
-   Field season planning (SIP, etc)
-   Share the Antarctic process with colleagues and outreach

- Pearson Biogeochemistry Group

- Moving-wire interface for the isotopic analysis of nucleic acids

## With appreciation!

*With appreciation!*

## Questions?
# Presentation: 909045

## http://lcweb.loc.gov/z3950/agency/

rden@loc.gov

- rden@loc.gov

- Z39.50 Maintenance Agency

- Library of Congress

## Historical Background

- 1978-82
-  Early  Development/ Investigation
- 1982-83
- Linked Systems Project  Protocol
- 1883-84
- Submitted to  ANSI Z39 (renamed   “NISO” in 1985).   Z39.50-1984.  Ballot failed.

## Historical Background (continued)

- 1984-87
- Continued Development
- 1988
-  Re-submitted.  Approved as Z39.50-1988.
- 1979-89
-  Z39 SC D

## Historical Background (continued)

- 1984-91
-  ISO SR
- 1990
- ZIG
- 1989-90
- Z39.50 Maintenance Agency established

## Historical Background (continued)

- 1992
- Z39.50-1992 (version 2)
- 1990-95
- Development of version 3
- 1995
- Z39.50-1995
- 1998
-  ISO 23950

## Maintenance Agency Responsibilities

- Maintenance
- Development
- Registration
- Implementor Information

## Formal Standards Maintenance

- Defect Reports
- Amendments
- New versions

## Informal Maintenance

- Clarifications
- Commentaries
- Implementor Agreements

## Z39.50 Resources - Z39.50 Document - Related Specifications - Object Identifiers -  Implementor Register - Z39.50 Profiles - 

**ZIG Meetings - Site Index**
# Presentation: 868933

## Where Do We Go From HERE?(now that all of the technologies have grown up!*)

**Kenneth A. LaBel****	****	****Michael J.Sampson**
**ken.label@nasa.gov****	****michael.j.sampson@nasa.gov**
**301-286-9936****	****	****	****301-286-3335**
**Co- Managers NEPP Program**
**** Apologies to The Alan Parsons Project***

## The Problem(s) – A Sampling

**New Silicon**
**-90nm CMOS**
**-new materials**

**New Architectures**
**-new interconnects**
**-new power distribution**
**-new frequencies**

**New Design Flows/Tools**
**-programming algorithms, application**
**-design rules, tools, simulation, layout**
**-hard/soft IP instantiation**

**New Package**
**-Inspection**
**-Lead free**

**New Workmanship**
**-inspection, lead free**
**-stacking, double-sided**
**-signal integrity**

**New Board Material**
**-thermal coefficients**
**-material interfaces**

**New Connectors**
**-higher-speed, lower noise**
**-serial/parallel**

***Can we “qualify” without breaking the bank?***

- Challenge for New Electronic Technologies Insertion  Workshop at NASA/GSFC presented by Ken LaBel

- Jan 30-Feb 1, 2007

## Statistics and “Qualification”

**66096****	****	****Hours**

**2754****	****	****Days**

**7.54****	****	****Years**

***and I forgot temperature variations!!!***

- Challenge for New Electronic Technologies Insertion  Workshop at NASA/GSFC presented by Ken LaBel

- Jan 30-Feb 1, 2007

## So What Now?

**Do we**
***Put our heads in the sand and hide?***
***Run screaming and try working in another field?***
***Accept unknown risk?***
**OR do we**
***Work together to develop a way forward?***
***Critically look at “qualification” versus risk reduction/acceptance?***
***Determine how to work in an interdisciplinary manner?***
***Develop a group/sub-groups to recommend approaches?***
***Develop a white paper on how to get our arms around this growing challenge?***
***???***

- Challenge for New Electronic Technologies Insertion  Workshop at NASA/GSFC presented by Ken LaBel

- Jan 30-Feb 1, 2007