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

## Licensing Infrastructure

- Issues
- Solutions
- Experience

- Matthias Schröder for
- N.Høimyr, M.Katzarova, P.Saiz, A.M.Osborne, A.Thys, P.Bähler, H.Hansbakk

## Issues

- Commercial software requires licences
- Several schemes possible
- Single user
- Node locked
- Network/Floating
- Site wide
- Home use

##  Management Aspects

- Licences need to be managed
- Purchase the correct number
- Too few: users are very unhappy
- Too many: your management is very unhappy
- Install them
- Keep them accessible
- Renew them in time
- Warn the product maintainer, so he can take action
- Retire unused versions

## Service Issues

- Appropriate Infrastructure needed
- Assure availability
- Monitor usage
- Adapt number of licences to usage
- Inform about issues
- Make sure you can contact the users
- Keep track of available products
- 120 products in database
- Products can have many features

## Licence Management Systems

- Challenge: many different systems
- Macrovision FlexLM
- IBM LUM
- Wolfram MathLM
- Microsoft SMS logs
- Many proprietary systems
- No common interface
- Some are plain incompatible
- Require different operating systems
- Some require hardware keys

## Our Setup

**Product**
**database**

- Log parser

- Clients

- Licence servers

- Web-
- interface

## Log Parser

- Read logfiles of different license managers
- Each with own format...
- ~ 1k lines of perl, C or shell per parser
- Extract needed information and store in DB
- Which product, feature, version
- Used by whom, when, from which host
- Provides unified interface
- Long term storage in DB
- Easy access

## Web Interface – Product Information

## Web Interface – Product Maintainer Page

## Usage Monitoring

- Do we have enough/too many licences?
- Maximum number of concurrent users
- Number of denials
- For the different operating systems
- For the different versions of the product

## Usage Monitoring 2

- Lists of users
- Current users
- Ask user X to free a licence for Y
- Warn them about imminent changes
- Recent users
- Inform about planned changes, downtimes
- With email address

## Web Interface - Statistics

- Version 6.4 of TotalView not used anymore, consider retirement

## Web Interface - Statistics

## Server Monitoring

- Availability of Service very important
- Systems must be up at all times
- Licence manager daemons as well
- Have redundant servers
- 2*3 Solaris
- 3+1+1+1 Windows
- Not all licence managers allow fallback setup
- Monitor servers and daemons and start/stop daemons
- If vendor is not flexible enough: no fallback

## If things go wrong

- Problems in fetching a logfile
- No stats for a product for that week

## If things go wrong

- Problems in parsing a logfile
- Strange results...

## Conclusion

- Proper infrastructure helps managing licences
- Monitoring essential for estimate of needs
- Variety of licence managers does not ease task
- Log parsers help in dealing with variety
# Presentation: 420214

## Flood Sensorweb

- Uses Dartmouth Flood Observatory QUIKScat Global Flood Atlas:
- B. Brakenridge, Anderson, Ngiem, Caquard, et al.,* “*Flood Warnings, Flood Disaster Assessments, and Flood Hazard Reduction: The Roles of Orbital Remote Sensing,” Proc 30th Intl Symp on Remote Sensing of the Environment, Honolulu, HI, Nov 10-14, 2003

## Floods - Detection

**Dartmouth-Flood Observatory QuikSCAT**
- The DFO in collaboration with JPL/QuikSCAT processes QuikSCAT Scatterometer data to assess surface water conditions.
- VV/HH ratio is used to assess surface water properties of the areas in 0.25 lat/lon degree bins
- The 7 day running mean is used to dampen effects of short-duration rainfall over urban areas.
- This data is then compared to the seasonal (90 day) average of the previous year to screen out wetlands.

- POC: Brakenridge/DFO  Ngiem/JPL

## MODIS Image Brahmaputra, India Aug 6, 2003

***MODIS Image Brahmaputra, India Aug 6, 2003***

***EO-1 Hyperion Image Brahmaputra Aug 6, 2003***

- Flood alerts are then used to retask EO-1.

- 250M resolution

- (10M ALI Pan band possible)   30M resolution

## Impact

- Higher resolution data is acquired of:
***key locations*** (pre-determined satellite gauging reaches) and
***times*** (active flooding regions)
- With the end result of improved flood science.

## Status - Floods

- September, October 2003 - Several demonstrations performed to track flooding in the Brahmaputra River basin, India
- December 2003 – continued demonstrations to track Yellow River, China

## Volcano Sensorweb

- Uses University of Hawaii, Hawaii Institute for Geophysics & Planetology detectors:
- Harris, A. et al., (2002) Web-Based Hot Spot Monitoring using GOES: What it is and How it Works,** ***Advances in Environmental Monitoring and Modelling *_[http://www.](http://www.kcl.ac.uk/advances)__[kcl](http://www.kcl.ac.uk/advances)__[.ac.](http://www.kcl.ac.uk/advances)__[uk](http://www.kcl.ac.uk/advances)__[/advances](http://www.kcl.ac.uk/advances)_* Vol. 1 No. 3 (2002) pp.5-36*
- Wright, R., Flynn, LP, Garbeil, H, Harris, AJL, and Pilger, E. (2002). _[Automated volcanic eruption detection using MODIS.](http://modis.higp.hawaii.edu/papers/wright.pdf)_ *Remote Sensing of Environment*, 82, 135-155.
- Flynn, LP, Wright, R, Garbeil, H, Harris, AJL, and Pilger, E. (2002). _[A global thermal alert using MODIS: initial results from 2000-2001.](http://modis.higp.hawaii.edu/papers/flynn.pdf)_ *Advances in Environmental Monitoring and Modeling*, 1, 5-36.

## Volcano Sensorweb

**Re-tasking**

**Earth **
**Observer **
**One**

**GOES, MODIS, **
**AVHRR Triggers**

## Status - Volcanoes

- Demonstrations in progress using MODVOLC
- Recent triggers of
- Kilauea, HI;
- Belinda, Antarctica
- SGM /GOES & AVHRR linkup in progress
- End impact is
- larger archive of active volcano remote sensing imagery
- Increased imagery of early phenomena imagery
# Presentation: 400529

## Fire Service Research needs

- Graduate Infrastructure at masters and doctorate levels
- Require research at all levels in higher ed programs AA,AS, BS, MS, Phd
- Need Research into Fire Issues
- What, when, why, how we do everything?

## Fire Service Research needs

- Encourage Doctoral students to conduct research into fire service issues
- Need a refereed journal for the fire service
- Encourage and Support those programs and research efforts dealing with fire issues and policy

## Fire Service Research needs

- Fund visiting professorships to study fire issues & Policies
- Support NETC as the repository for emer. Service research

## RESEARCH TOPICS

- Impact of Higher ed on the careers of FF (Where do they go?)
- Correlation response time and losses
- Property
- Life
- Injury

## RESEARCH TOPICS

- Changes in courage or risk taking related to education/training levels
- Acceptance of Residential Sprinklers as a solution to the fire problem
- Impact of performance based codes
- Impact of diversity on the fire service
- Impact of females on the fire service

## RESEARCH TOPICS

- Seat belt use or lack of by the fire service
- Staffing levels
- Alternate education levels to achieve experience
- Rotate to a major FD for an internship to gain command or live fire experience
- Impact of “simulation only” based fire training on FF and Officer capability

## RESEARCH TOPICS

- Feasibility of a Nat’l Response Team(s) for major incidents
- Radio Communication at Large Scale Incidents
- Longitudinal Study of the impact of fire safety education
- National Registry and/or Nat’l Standardized Exam

## RESEARCH TOPICS

- Legal Issues in the Fire Service
- Medical and Physical Fitness in the Fire Service
# Presentation: 770094

## National Depot for Shift-Adjusted Ratings U.S. Geological Survey:Status and Planned Upgrades

**U.S. Geological Survey**

**National Depot for Shift-Adjusted Ratings U.S. Geological Survey:****Status and Planned Upgrades**

**Mark E. Smith, USGS Central Region**
**Interagency Water Resource Meeting**
**Southwestern Division**
**Fort Worth, TX**
**March 27-28, 2007**

## National Ratings Depot

**Announced in OSW Technical Memorandum 2005.01**
**Latest expanded, shift-adjusted rating retrieved from all stage-discharge sites at 8pm local time**
**Available on web by site:**_**[http://nwis.waterdata.usgs.gov/nwisweb/data/exsa_rat/08048000.rdb](http://nwis.waterdata.usgs.gov/nwisweb/data/exsa_rat/08048000.rdb)**_
**Tab delimited (rdb) format**
**Detailed information on current shift included**

## National Ratings Depot

**>5000 Ratings Daily**

- Monthly Web Hits to the National Ratings Depot

## National Ratings Depot

***Major users requesting data.***

## National Ratings Depot

**W Fork Trinity River at Ft Worth (Sta. 08048000) – retrieved 3/24/07**
- # //RATING SHIFTED="20070323200000 CDT"
- # //RATING ID="  13" TYPE="STGQ" NAME="stage-discharge" AGING=A
- # //RATING REMARKS=""
- # //RATING EXPANSION="logarithmic"
- # //RATING OFFSET1=0.00
- # //RATING_INDEP ROUNDING="2223456782" PARAMETER="Gage height IN feet"
- # //RATING_DEP ROUNDING="2222233332" PARAMETER="Discharge IN cfs"
- # //RATING_DATETIME BEGIN=19891001000100 BZONE=CDT END=20060930235959 EZONE=CDT AGING=A
- # //RATING_DATETIME BEGIN=20061001000000 BZONE=CDT END=23821230180000 EZONE=CST AGING=W
- # //SHIFT_PREV BEGIN="20061106060000" BZONE="CST" END="--------------" EZONE="---"
- # //SHIFT_PREV STAGE1="0.19" SHIFT1="0.08" STAGE2="0.76" SHIFT2="0.08" STAGE3="1.40" SHIFT3="0.00"
- # //SHIFT_PREV COMMENT="Start +0.08 on peak of debris removing rise for #764"

## National Ratings Depot

**W Fork Trinity River at Ft Worth (Sta. 08048000) – retrieved 3/24/07**
- INDEP	SHIFT	DEP	STOR
- 16N		16N	16N	1S
- 0.11	0.08	0.00	*
- 0.12	0.08	0.10	*
- 0.13	0.08	0.14
- 0.14	0.08	0.20	 	** **
- No specific plans to modify this format (or tabling structure):
- Easy to retrieve (command line program), fairly robust in feeding the automated processes used by COE and NWS
- Selected a single format for all users that utilized scarce USGS resources as efficiently as possible	** **
- However, prepared to discuss more robust formats available now.For example, XML.

## When will the Depot be able to...?

**Approved upgrades that will be forthcoming:**
- Means to retrieve/identify ratings that have been modified
- Provide data corrections in addition to ratings/shifts
- Provide explicitly the base-rating table in addition to the shifted-rating table (currently the base rating CAN be derived / reconstructed using the starred (*) rating-input points and removing the shift curve in effect)
- NOTE:	Roll out of upgrades subject to programmers’ scheduling –
- 		Probably sometime in FY08

## National Ratings Depot

**Questions?**
# Presentation: 118337

## A Litany on Usability: A mostly users view

- David Evensky
- Sandia National Laboratories
- Livermore CA

## Resource Allocation

- Users can allocate CPU's, but we still have to share storage, networks, and messaging fabric.
- QoS for heavily contended control fabric (messaging?)
- Node allocation to prevent space shared jobs from suffering cross talk.
- Such fragmentation has been conjectured as a cause for intermittent slow downs for some codes on space shared machines.

## Architectural Assumptions“What do you mean there is no default route?”

- Tools available in the community at large (open source & commercial) make assumptions about disks per node, network topology, and direct network reachability (no direct routes only ssh tunnels, etc.)
- Storage & I/O remain problems.

## Architectural Assumptions “But my distributed objects code uses java!”

- Systems that are optimized for a single class of problems have difficulty running other classes of problems.
-  Systems **must** be designed in cooperation with user community. (language set, apparent disk per node.)
- Users should not *have* to see the node structure, resource management systems should take care of the basic functionality. There should be a way of cleanly exposing this for those that wish to fully optimize their performance.
-  I should be able to login to systems that I am using, if I *want or need*.

## Need standards and common practices 

-  How can I get my data (big D) into the cluster for processing, and get it back out. How do I prevent any solution to this problem from being an ad hoc stovepipe solution?
- Need std tools. everyone that builds a cluster rewrites similar tools for administrators and users.

## Attic

- Dusty decks. How can I quickly run old programs on modern machines, without wasting large amounts of valuable programmer time?
- Even not-so-dusty ones have to be rewritten at every purchase variation.
- Special optimizations for specific processors and networks still crucial to achieving performance.

## Open source “Linux rules”“I am elite, give me warz, dude”

- Using an open source OS and home grown systems. Need to provide users with
- understandable documentation
- training
- development assistance to run effectively on this class of machines.

## Fault Tolerance

- Make it easy for users to do checkpoint restart.
- Integrated with resource management system.
- When a HW fault occurs (assuming we get that info from the HW) that we report to the user that his job was killed because of  HW rather than a mysterious 'Bus Error'.
- Process migration (auto-magic migration to hot spares).
# Presentation: 483003

**NM-WG Next Steps, and how work from the DAMED WG is Related**

**Data Intensive Distributed Computing Group **
**Lawrence Berkeley National Laboratory**

**Brian L. Tierney**
**Dan Gunter**

## NM-WG: Next Steps

- In my view, our next task is to define a schemas for network performance characteristic information
- Goal: Publish network performance information in a manner that is useful to:
- Grid middleware and applications
- Network engineers
- Grid sysadmins

## Sample Queries

- What is the *available bandwidth* from Host A to Host B (or site A to site B, or domain A to domain B)?
- What is the *round trip delay* from host A to host B
- Is the path from host A to host B and back asymmetric?
- What is the *packet loss* rate from site A to site B?
- What is the hop-by-hop *available bandwidth* from site A to site B?
- What is the *achievable bandwidth* from host A to host B, and what are all the characteristics that might have affected the results (OS version, host speed, MTU, etc.)
- What is the bottleneck link in terms of capacity from site A to site B?
- What are the QoS options from host A to host B?
- Many more......
**NOTE**: all of these queries might ask for the last measured value, average of past N values, prediction of future values, etc.

## This Requires

- Standard names for characteristics
- Standard names for attributes
- Standard units
- Standard names for statistical methods
- Averaging, prediction, etc.
- Standard ways to represent relationships between network entities and paths and hops.

## Network Characteristic Naming

- This has been addressed by the Discovery and Monitoring Event Descriptions WG (DAMED)
- DAMED Terminology
**Event **the smallest stand-alone unit of measurement information
**Event type **a type of event, e.g. “delay.TCP”
**Target **the entity being measured in an event
**Target type **a type of target, e.g. “network.path”

## Currently Defined DAMED-style Names for Network Characteristics

- bandwidth.achievable.TCP.singleStream
- bandwidth.achievable.TCP.multiStream
- bandwidth.achievable.UDP.singleStream
- delay.roundTrip
- delay.oneWay
- loss.oneWay
- hop.bandwidth.capacity
- hop.bandwidth.utilized
- Note: "path" is implied if "hop" is not specified in these event names
- Sample target: for a network path (layer 3):
- 	target = src IP, src port, dest IP, dest port

## Question: program/event name boundary 

- We did _not_ include the program name in the event name ~ delay.roundtrip.ping
- Advantage: easy to compare two different programs measuring the same thing
- Disadvantage: can’t as easily distinguish between different tools measuring the same thing

## Next Steps?	

- Would like to have 1st rough draft by next GGF
- Volunteers?
- One document? Or multiple documents?
- Relationship to CIM/DMTF?
- Relationship to GLUE?
- Other efforts in this area?
# Presentation: 191804

##  PMDB

- VIDEO I

** ****PMDB**

**Predisposing and Precipitating Factors**

## AWARENESS

- Self

- Others

- Environment

## VIOLENCE

- 	Any physical assault,
- 	threatening behavior,
- 	or verbal abuse that occurs while working or on duty.
**National Institute for Occupational Safety and Health (NIOSH)**

## PREDISPOSING FACTORS

-    Individual characteristics a person brings into a situation which may contribute to a violent incident.

## INDICATORS FOR DISRUPTIVE BEHAVIOR

- Individual Characteristics
- Diagnoses Associated with Violence
- Basic Motives for Violent Behavior
- Other Factors Associated with a High Potential for Violence

## INDIVIDUAL CHARACTERISTICS

| Loner / Withdrawn | Substance Abuse |
| --- | --- |
| Fascination with Violent Music, Games, Movies | Views world as hostile |
| Obsession with Weapons | Views world as threatening |
| Poor Interpersonal Skills | Low Frustration Tolerance |
| Poor Employment Hx | Impatient |
| Suspicious of Others | Financial Stress |
| Problem with Authority Figures | Blames Others for Problems |
| Frequent Mood Swings | Shunned by Co-workers |

## DIAGNOSES ASSOCIATED WITH VIOLENCE

**Intoxication / Substance Abuse**
**Delirium**
**Paranoid Schizophrenia**
**Mood Disorders**
**Mania / Bipolar**
**Post Traumatic Stress Disorder**
**Organic Disorders / Dementia**
**Brain Damage / Head Injury**
**Borderline Personality Disorder**
**Antisocial Personality Disorder**

## VIOLENCE 
is NOT a DIAGNOSIS!

- is _**NOT**_ a DIAGNOSIS!

## REMEMBER!

**Not all violent individuals are mentally ill.**
**Not all mentally ill individuals are violent.**

## REMEMBER!

- 	Given the right set of circumstances, ANY person has the potential for violence in order to regain control of his / her environment.

## BASIC MOTIVES

**Fear**
**Anger**
**Frustration**
**Manipulation**
**Intimidation**
**Brain Damage / Dementia**
**Responses to Pain, Medication, Illness**

## OTHER FACTORS

**OTHER FACTORS**

**History of Past Violence**
**Psychiatric Commitment, Jail Homelessness**
**Availability of Weapon**
**History of Abuse**
**Economic Instability**
**Organizational Changes**
**Increase of Domestic Violence**

## PRECIPITATING FACTORS

**PRECIPITATING FACTORS**

- External, Environmental Factors
- That Impact on an Individual by:
- Increasing the Odds
- Lighting the Fuse

## LIGHTING THE FUSE

**  ****Environment**
**  ****Poor Customer Service**
**  ****Noise or Poor Lighting**
**  ****Traffic and Parking**
**  ****Inflexible Processes**
**  ****Other?**

## INCREASING THE ODDS

**Lack of Privacy**
**Loss of Control**
**Loss of Dignity**
**Loss of Identity**
**Loss of Independence**
**Fear of Pain**
**Frustration with System**

## NEW EMPLOYEE ORIENTATIONAwareness Training

_**Options**_
**PMDB Facility Policy**
**Video I (Predisposing / Precipitating Factors)**
**Videos II or III (Verbal – Nonverbal Interventions or Limit Setting)**
**PMDB Handouts**

**PMDB**

##  PMDB

** ****PMDB**

**Predisposing and Precipitating Factors**
# Presentation: 682277

## Slide 1

## Slide 2

## Slide 3

## Florida School Accountability System - Historical Overview

-   Began Nov ‘95 using SB Rule 6A-1.09981 to implement part of 229.591
-   Based on 2 years’ performance based on district NRT data in Reading and Math, plus statewide Writing                                  	data against minimum criteria
-   Initially identified 158 schools as having “Critically Low” student performance
-   By Nov ‘96 number of low performing schools was 71, less than half the original number
-   By Nov ‘97, there were only 30 “Critically Low” schools
-   By Nov ‘98, there were only 4 CL schools remaining

## 	June ‘99 began School Grading era, still using 6A-1.09981, but implementing new statutory 	language in 229.57	

-  	Grades “A” through “F” based on one year’s performance on FCAT Reading, Writing and Math
-  	 In June ‘99 78 “F”s and 613 “D”s were issued
-   	In June ‘00 only 4 “F”s and 397 “D”s were issued
-   	In the first year, low performing (F and D) schools outnumbered high performing (A and B) schools
-   	By 2000, the number of “A” schools nearly tripled and high performing schools now outnumber low
- 	performing school

## What became of the first F’s?

**1999 F’s Schools In 2000**

## How it works?

**FCAT**
**Test Data**
**1.1m 2001**
**2.9m 2002**

**Survey 2/3**
**Demographics**
**(1.8m)**

**Accurate?**

**Accurate?**

**Merge Files**
** ****by Grade**

**Accurate?**

**Analyze Data**
**Against Standards**

**Yes**

**Accurate?**

**Yes**

**Publish/Post**
**School Grades**

**No**

**Yes**

**Yes**

**No**

**No**

**No**

**No**

## Slide 8

## Grade Appeals

**Must be filed within 30 days**
**Commissioner has final authority **
**± 110 schools in 35 districts filed in 2000**
- 51%	Misclassified Students (ESE, LEP, Grade Level)
- 24%	Philosophy
- 15%	Estimated Percent Tested
- 15%	Procedural
-   8%	Not Originally Graded
**Necessitates active files by student**
**Interactive process with schools & districts**
- ESE/LEP Placement Updates
- Grade Level Mis-Assignments
- Mid-Year Promotions
- Lost Test Documents
- Test Administration Anomalies
- Test Invalidation Records
# Presentation: 070772

## Science Archives in the 21st Century

***Ed Grayzeck***
***National Space Science Data Center***
***25 April, 2007***

## Workshop

- Sponsored by NSSDC
**LOGISTICS: presentations, posters, hardcopy, lunch, parking, ...**
**INFORMAL DINNER: 94****th**** Aero Squadron (College Park) menu, interested?**
**INTEREST GROUP: communication via yahoo group for ‘ScienceArchives’**
- Discussion: best practices, lessons learned, policies, problem areas, novel approaches, promising technologies
- Format: Mix of invited talks, oral presentations, and posters
- Announcements on “http://nssdc.gsfc.nasa.gov/nost/conf/Archive21st/”
- NSSDC will post summary and highlights from workshop
- Exec Committee: Mike A’Hearn, Jeanne Behnke, Tom McGlynn, Michele Weiss, NSSDC

## GOALS

**Communication**
- One goal is to establish the level of commonality of problems and best practices, as seen by the archives, and their interest in continuing to communicate on such matters.
- Another goal is to identify broadly based techniques and best practices that address common concerns, and to get these identified and documented in a summary document.
- A third goal is to establish more frequent, alternative, modes of communication among the archives should this be of interest.  This may include the establishment of ad hoc working groups to address particular issues and/or the development of best practices documents.
# Presentation: 322979

## American beechFagus  grandifolia  Ehrh. Synonyms: F.  americana,  F.   ferruginea,  F.  mexicana.  Other common names;  beech, beech nuts, beech tree,  Carolina beech, gray beech, red beech, white beech, ridge beech.

**FOOD:**
- The seeds were used by many tribes for food.  They were often stored and later used in winter when plant food was scarce.  The seeds are rich in oil, which contains up to 22% protein.  When eaten raw they are tender, crispy, sweet and nutty.
- Only the young tender leaves were used as a potherb in soups or stews.  The leaves become very fibrous and tough in a short period of time.
-  The inner bark was dried, ground up into a fine powder and used as a thickening agent in soups and stews, or mixed with grain when baking bread.
- Colonists dried and ground up the seeds to use as a coffee substitute. Some people have reported gastrointestinal ailments after eating large amounts.

- Photo courtesy of:  ©William S. Justice. Courtesy of _[Smithsonian Institution, Dept. of Systematic Biology, Botany](http://www.nmnh.si.edu/botany/index.html#?collections)_. This copyrighted image may be freely used for any non-commercial purpose. For commercial use please contact _[George F. Russell](mailto:russell.rusty@nmnh.si.edu)_.

- Slide developed by Pat Broyles, Soil Conservationist, Manhattan, KS. PMC.  USDA is an equal opportunity employer.

## American beech 

**CULTURALLY:**
- The Potawatomi carved mixing and serving bowls from the beech.  The portion of the tree selected had a wavy grain since this indicated the hardest part and thus would resist the cutting edges of tools used to chop up foods.
- The Iroquois would use the seed oil, either by itself or mixed with bear fat, as a hair treatment or mosquito repellant.
- An edible semi-drying oil can be squeezed from the nut meats.
**MEDICINALLY:**
- The Cherokees chewed the nuts as a dewormer.
- Most often it was used to treat skin problems.  A poultice of leaves and bark was boiled and placed on the skin as an antidote for poison ivy, burns, frostbite, rash and scalds.

- Photo courtesy of:  Robert H. Mohlenbrock. USDA NRCS. 1995. *Northeast wetland flora: Field office guide to plant species*. Northeast National Technical Center, Chester, PA. Courtesy of _[USDA NRCS Wetland Science Institute](http://www.pwrc.usgs.gov/WLI/)_. This image is not copyrighted and may be freely used for any purpose. Please credit the artist, original publication if applicable, and the USDA-NRCS PLANTS Database. The following format is suggested and will be appreciated: **Robert H. Mohlenbrock** @ USDA-NRCS PLANTS Database / **USDA NRCS. 1995. *****Northeast wetland flora: Field office guide to plant species*****. Northeast National Technical Center, Chester, PA.**

- Slide developed by Pat Broyles, Soil Conservationist, Manhattan, KS. PMC.  USDA is an equal opportunity employer.
# Presentation: 106749

## MNM Fatal 2005-26

- Machinery
- September 27, 2005 (Florida)
- Phosphate Operation
- Dozer Operator
- 60 years old
- 35 years mining experience

## Overview

- The victim was operating a dozer that slid into a water filled pit.  The dozer was pushing material at the edge of the pit to construct a ramp for a pump when the ground underneath it failed.

## Slide 3

## Causal Factors

- Policies, standards, and controls were inadequate and failed to ensure that the ramp was designed and constructed of materials capable of supporting the load that it would be subjected to.
- No risk assessment was conducted to identify all foreseeable hazards and discuss methods to minimize the hazards associated with the construction of the ramp.

## Best Practices

- Stop, Look, Analyze, and Manage, SLAM each task to identify all potential hazards. Initiate action to protect yourself when performing every task.
- Evaluate the stability of the ground prior to operating equipment near any drop off or edge.
- Use equipment (excavator) that can perform the work from a safe distance away from the edge of a pond where the stability of the ground may be unknown.
- Require that flotation devices be worn by persons performing work where there is a danger of falling in the water.
# Presentation: 073178

## Evaluation of ECMWF T511 Nature Run using Cyclone Statistics

- Joe Terry                                                         Software Integration and Visualization Office       NASA/Goddard Space Flight Center

- April 2007

- 1.

## Utilize Goddard’s cyclone tracking software (Terry and Atlas, AMS conf, Aug 1996): 

-   Identifies and tracks mostly extratropical cyclones (cutoff at 20 deg N/S latitude)
-   Interfaces with GrADS contouring algorithm
-   Uses SLP field at 4hPa contour interval
-   Finds centroid of inner-most closed isobar
-   Tracks the centers using extrapolation and 500hPa steering

- Cyclone tracks generated:
-   Nature run at one degree for Jun 2005 to May 2006 (each month and season)
-   NCEP operational analysis at one degree for 2000 to 2006  (each month, 68 of 84 months were available)

- _Cyclone Tracking_

- 2.

## Cyclone Diagnostics

-   Tracks
-   Lifespan
-   Distribution by central pressure
-   Deepening rate
-   Mean direction and speed  (total, zonal and meridional speed)
-   Cyclone, genesis and lysis density

- Goals:
-   Identify any trends or biases
-   Identify any conspicuous anomalies and determine source
-   Assess realism

- _Cyclone Diagnostics_

- 3.

## EXAMPLES OF DIAGNOSTIC RESULTS

- 4.

## 5.

## 6.

- 7.

- 8.

## 9.

## 10.

## 11.

## 12.

**Cyclogenesis density** from NCEP reanalysis over Southern Hemisphere.  (*Simmonds and Keay, Journal of Climate, March 2000*)

- DJF

- JJA

- 13.

## 14.

**Cyclolysis density** from NCEP reanalysis over Southern Hemisphere.  (*Simmonds and Keay, Journal of Climate, March 2000*)

- DJF

- JJA

- 15.

## CASES OF PROMINENT ANOMALIES

- 16.

- 17.

- 18.

- 19.

## 20.

- 21.

- 22.

- Tropical Cyclone Tracks for the period 1979-1988 (from BMRC)

- 23.

- Table of Monthly SH Tropical Cyclone Frequencies from Joint Typhoon Warning Center

- 24.

- 25.

## 26.

- 27.

## 28.

## Conclusions

-         *  No evidence of significant biases or negative trends
- 2.  Few notable anomalies
-         *  Departures from analyses are explainable and basically realistic
- 3.  Diversity
-  *  Healthy (but not excessive) variability in statistics
-         *  Variety of blocking patterns
-         *  Shifts in storm track
-         *  Tropical cyclone interactions with mid-latitude systems

- _Conclusions_

- 29.
# Presentation: 540468

## ARRL ARIA Update

- Status as of June 2002

## ARIA Overview

- To determine the noise and signal levels on amateur bands at 70 cm and above.
- The initial focus is on the 2.4 GHz amateur allocation.
- A group of volunteers has been identified to make the necessary tests and measurements.

## ARIA Drive-Around Tests

- Participants go to various unspecified locations.
- Relative determinations of what signals (narrowband and broadband) and noise levels are found at these locations.
- Reported on a standardized form.
- Volunteers have started doing some of the drive-around tests.

## The next phase of the study

- Measurements of signal and noise levels.
- ARRL has designed calibrated amplified broadband noise sources.
- Used to radiate a signal of a known field strength, which is then used to calibrate a test fixture consisting of an antenna and receiver. This is then used to measure the field strength of a given signal or noise.
- ARRL has also written a calibration procedure for using the noise source to make accurate measurements.

## Some preliminary results

- Santa Clara Valley, CA
- 2400-2410 MHz downconverted to 144-154 MHz

## Comments from 2.4 GHz Amateur Radio Users

- “Out here in the Bay Area, any 2.4 ham repeaters that existed in the shared spectrum have already been moved because the spectrum is full of trash.”
- “The noise floor is so high as to be unusable.”
- “Illegal amplifiers are easily available for 2.4 wireless data, and deployed with impunity.”
- “Performance of our Amateur Television station on 2.4Ghz located on Black Mountain has also suffered tremendously from this interference. Its output frequency is around 2427 MHz.”
- “2.4 is the next 11 meters, illegal amps and all.”

## Uncalibrated measurements in my hotel room last night

| Freq (MHz) | Signal (6 dB/S unit) |
| --- | --- |
| 2400.925 | S1 |
| 2421.400 | S2 |
| 2449.600 | S1 |

## Uncalibrated measurements made in this room now

| Freq (MHz) | Signal (6 dB/S unit) |
| --- | --- |
| 2421.400 | S2 |
# Presentation: 748670

## National Technical  Information Service (NTIS)       

**NTIS’ Handle System****® and the *****NTIS e-Government***** *****Virtual Library Initiative***
**CENDI Handles****®**** Workshop**
**January 29, 2003**
- Walter L. Finch
- Director Program Planning
- National Technical Information Service
- Springfield, VA 22161
- (703) 605-6407  wfinch@ntis.gov

## NTIS Background

- National Technical Information Service (NTIS), Technology Administration, Department of Commerce
- Established 1945 to collect and provide permanent access to nation’s largest collection of scientific, technical, engineering and business-related information in order to support the nation’s economic growth and job creation
- Approximately 3 million reports
- 200 employees located in Springfield, VA
- Full cost recovery – No appropriations

## NTIS Collection

- NTIS receives approximately 45,000 information products annually
- Electronic, web harvesting, & paper input (scanned into tiff/pdf files)
- All reports input are abstracted, indexed (using controlled vocabulary) & cataloged in the NTIS Database

## Improving Access to Government Information through the NTIS e-Government Virtual Library Initiative

**One Source****.**

**One Search.**

**One ****Solution****.**

## NTIS e-Government Virtual Library Initiative

- Provide single point of entry to search more than 750,000 reports in the NTIS Database (1990-present)
- Access to over 350,000 full-text reports available as downloadable pdf files (1997-present)

## NTIS e-Government Virtual Library Initiative  (Continued)

- Linking to other agency web sites for free download of reports
- If reports held only by NTIS
- Free if 20 or fewer pages
- $8.95 if greater than 20 pages
- Customized CD-ROM on demand
- E-Commerce online ordering & delivery

## NTIS e-Government Virtual Library Initiative -- Commitment

- Collect & archive full-text STI reports and provide permanent availability
- Provide permanent links to agency web sites to download full-text reports
- Provide access from NTIS collection to permanent archived copy if agency removes report from web

## NTIS Digital Identifier -- Handles System®

- NTIS will work with other agencies that maintain a Handle System
- NTIS will manage a system that assigns, manages, and resolves _*persistent*_  Handles for digital objects in multiple locations

## NTIS’ Implementation of Handles

- Links to DOE - OSTI’s Information Bridge
- PURL -  Persistent URL
- Assigned PURL as Handle
- Working with OSTI to ensure permanency
- Will begin working with DTIC to incorporate DTIC’s Handle in NTIS Database

## NTIS Handles Database

- Contains Handle and Accession Number
- NTIS Bibliographic Database contains metadata

## Future Enhancements

- In the future, NTIS will provide Database vendors (i.e. CSA, DIALOG , etc.) and other lessees with a Handle for each record in the NTIS Bibliographic Database enabling linking to full-text.

- Walter L. Finch
- Director Program Planning
- National Technical Information Service
- Springfield, VA 22161
- (703) 605-6405  wfinch@ntis.gov
# Presentation: 866939

## THREE SANTEE EXPERIMENTAL FOREST WATERSHEDS  - SOME HYDROLOGIC STUDIES 

- Coastal SC

**THREE SANTEE ****EXPERIMENTAL FOREST**** ****WATERSHED****S**** **** - SOME ****HYDROLOGIC STUDIES **
**OF HISTORICAL DATA**

## Monitored Watersheds 

**WS 79**

- Turkey Creek

**Monitored ****Watersheds **

**WS 7****8**

## SANTEE EXPERIMENTALWATERSHEDS DEVELOPMENT

***WS 78 (5000 ha)****** *****Turkey Creek**
***Data from: 1964-1976***
***WS 79 (500 ha)***
***Data from: 1967-1973***
***WS 80  (206 ha)***
***Data from: 1969-1981***

**77**

**78**

**SEF**

## WS 78 – 5000 ha

**WS 78 – 5000 ha**

## WS 79 – 500 ha

**WS 7****9**** – 500 ha**

## WS 80 – 206 ha

## Slide 7

## Slide 8

## Slide 9
# Presentation: 861679

## THEMIS Instrumentation

- Dr. John Bonnell
- Space Sciences Laboratory, UC Berkeley

- Mission Objectives and Measurements:
-  THEMIS=Time History of Events and Macroscale Interactions during Substorms
-  What Events to Register?
-  What Interactions to Monitor?
-  What Instruments are Required to Perceive Them?

## THEMIS = Time History of Events and Macroscale Interactions during Substorms

- What Events?
-  Substorm Onset (GBO All-Sky Cameras and Mags)
-  Current Disruption and Redirection (THEMIS Probes)
-  Magnetic Reconnection (THEMIS Probes)

- P1

- P3,P4,P5

- P2

- 1000-1500 km/s!

## What Interactions? 

- Mission Objectives and Measurements

- Plasma
- Heating

- Plasma Flows

- Plasma Waves

- Magnetic Field Reconfiguration
- (Reconnection, Current Diversion/Disruption)

## Probe Carrier and Probes

- Shunt

- 2X Propulsion
- Tanks

- Transponder

- Battery

- Sun Sensor

- ESA/IDPU

- BAU

- IRU

- Single Point
- Ground

- Harness Bridge (harness not shown)

- Radial EFIs

**Top cut-away view of THEMIS probe**

**Oblique, external view of THEMIS probe**

**Oblique view of THEMIS probes mounted**
**On Probe Carrier (modified D-II 3****rd**** Stage)**

| THEMIS Stats |  |
| --- | --- |
| Probe Dimensions | 80x80x40 cm |
| Instrument Package | 25.7 kg |
| Probe Dry Mass (Instruments+SC) | 77.0 kg |
| Probe Fuel | 49.0 kg |
| Probe Wet Mass (Dry+Fuel) | 126.0 kg |
| Instrument+SC Power | 33.6 W |
| Data Volume per Orbit | 370 Mbits |
| Data Rate to Ground | 1 kbps 
to 1 Mbps |

## What Instruments on the Probes?

- Mission Objectives and Measurements

**Electrostatic Analyzer (ESA)**
**3D e- and i+ from 5-30,000 eV**
**Once per spin (3-s period) **

**Solid State Telescope (SST)**
**3D e- 25-800 keV**
**3D i+ 25 keV- 6 MeV**
**Once per spin (3-s period) **

**Flux Gate Magnetometer (FGM)**
**3-axis B-Field**
**0-128 Hz**

**Search Coil Magnetometer (SCM)**
**3-axis B-Field**
**10-4000 Hz**

**Electric Field Instrument (EFI)**
**3-axis E-Field**
**0-4000 Hz**

## Mission Objectives and Measurements

- Plasma
- Heating

- Plasma Flows

- Plasma Waves

- Magnetic Field Reconfiguration
- (Reconnection, Current Diversion/Disruption)

**Electrostatic Analyzer (ESA)**
**3D e- and i+ from 5-30,000 eV**
**Once per spin (3-s period) **

**Solid State Telescope (SST)**
**3D e- 25-800 keV**
**3D i+ 25 keV- 6 MeV**
**Once per spin (3-s period) **

**Flux Gate Magnetometer (FGM)**
**3-axis B-Field**
**0-128 Hz**

**Search Coil Magnetometer (SCM)**
**3-axis B-Field**
**10-4000 Hz**

**Electric Field Instrument (EFI)**
**3-axis E-Field**
**0-4000 Hz**
# Presentation: 570578

## Tropospheric Temperature Trends from MSU/AMSU 5.0Christy et al. 2003 (JAOT, in press)

**John R. Christy,**
**Roy W. Spencer, Daniel Braswell, W. B. Norris**
**University of Alabama in Huntsville**
**David E. Parker, The MetOffice**

## Slide 2

## Slide 3

## Christy et al. 2001

**Christy et al. 2001**

## Geographical Distribution of Trend Differences between upper-air and surface

**Geographical Distribution of Trend Differences between upper-air and surface**

## UAH Approach

**UAH emphasizes empirically determined corrections, temporal/spatial averaging and high reproducibility**
**Minimum thresholds set for Target Coefficients: overlap length (1 yr); variance explained (~40%)**
**Intersatellite biases calculated directly, latitude by latitude, apart from Target Coefficients**
**Diurnal corrections calculated directly**
**Backbone built from best overlaps N-6,-9,-10 (w/o NOAA-7/9, or NOAA-8/9 - Christy et al. 1998)**

## Slide 7

## Diurnal Cycle Issues

**UAH uses empirical methods (cross-swath differences) to determine diurnal cycle from direct calculation**
**Model must correctly reproduce not just the 1st harmonic, but the higher order, “even” harmonics to capture asymmetry in diurnal cycle, i.e. phase and amplitude of:**
**Stratospheric semi-diurnal tide propagation down to troposphere**
**Latent heating (14% amp. in tropical precip)**
**Solar absorption (vapor, clouds)**

## #1 (later)

- #11 (earlier)

**We estimate the diurnal***** *****Tb gradient (********T****b****/********t) with *****cross-swath***** Tb gradients**
**       ****{[(T****8****+T****9****)/2 – (T****3****+T****4****)/2]****asc****/********t   +   [(T****3****+T****4****)/2 – (T****8****+T****9****)/2] ]****desc****/********t }/2**

- Asc. (12 hrs later)

- Desc.

- 12 hours apart

- #11(later)

- #1 (earlier)

## Global 

**Operational processing uses 2-dimensional regression fits of cross-swath Tb gradient averages:**
**	****- Harmonic in month**
**	****- 2nd order polynomial in local time drift**
**(2.5 deg. latitude bands done separately/ land & ocean separately)**

- Global

## Slide 11

## Differences in ResultsUAH vs. RSS

**Tropical differences occur **_**after**_** the NOAA6/9 period**
**Extratropical SH shows largest trend differences concentrated in N-6/9 period**
**Extratropical NH shows smallest trend differences**

## Slide 13

## VIZ-B MT Sonde Comparisons1979-2000

## Slide 15

## Slide 16

## Slide 17

## Upper Air Datasets, 1950’s-?

**Retrospectively corrected radiosonde datasets: NOAA (support, update), Hadley - HadRT3 (support collaborative activities)**
**Improve sonde info/practices, expand tropics (need fine vertical resolution)**
**Microwave-based (1979): UAH, RSS - “operational research” support**
**Reanalyses: NCEP-100 hPa?, ER40, NOAA/NASA (multi-source or blended products)**
# Presentation: 947574

## USDA Human Pandemic Planning MeetingDecember 8, 2006

- Presented By:
- Jennifer Hatcher
- Senior Director Government Relations
- Food Marketing Institute

## FMI Food Safety Website

- _[www.fmi.org/foodsafety/avian_flu.htm](http://www.fmi.org/foodsafety/avian_flu.htm)_

## FMI’s Consumer Guide To Understanding Bird Flu, Seasonal Flu, and Pandemic Flu

## A Planning Resource

## Key Areas of Recommendations in FMI Planning Resource Guide 

- Business Continuity
- Dealing with Consumers
- Dealing with Associates
- Human Resources Recommendations
- Retail Store Recommendations
- Distribution Center and Transportation Recommendations
- Product Supplier Recommendations
- Dealing with the Media

## Disaster Preparedness

## Distributing Assistance

- _[http://ebt.nacha.org/](http://ebt.nacha.org/)_

## What the Supermarket Industry Needs from the Government

- Need to be a Part of the Critical Infrastructure
- Priority for Fuel and Cash
- First Responder

## Thank You

- Jennifer Hatcher
- Senior Director Government Relations
- Food Marketing Institute
- Phone: 202-220-0734
- Email: _[jhatcher@fmi.org](mailto:jhatcher@fmi.org)_
# Presentation: 517673

## Office of Public AffairsFactors in Decisions on Communication about FDA Actions

**Heidi Rebello**
- Deputy Assistant Commissioner for
- Public Affairs
- U.S. Food and Drug Administration

## Today’s Discussion

-  Organizational overview
-  FDA’s communication goals
-  Key issues
-  Criteria for issuing press
-  Communications challenges
-  New approaches

## Office of Public AffairsStatistics

-  # of press officers: 10
-  Media inquiries: 50-100/day
-  Press releases: Up to 25/month
-  Media briefings: 5-10/month
-  Stand up press conferences: 5-10/year
-  Public meetings: 20-30/year
-  Congressional hearings: > 50 in 2007/2008

## FDA Communication Goals

- Give consumers timely, understandable, useful, actionable information
- Foster public trust and confidence

## Key Issues

- Product safety and surveillance
-      	--Food safety
-      	--Medical product safety
- Regulatory action
- Agency initiatives

## Criteria for Issuing Press Paper

- Has the agency taken an action?
- Do we have enough data or information?
- Do we understand the issue well enough  to explain it?
- Do we have a clear message to the public?
- Can we assure the public that we are finding solutions?

## Communication Challenges

- Variety of audiences and expectations
- Issues are scientific and regulatory
- Legal limits on disclosure (Commercial Confidential Information, open investigation)
- Data not easily accessible
- Issues may be value-laden or emotional

## Other Challenges

- The public’s understanding & acceptance of:
- Scientific uncertainty
- Benefit/risk assessments
- Limitations with adverse event reporting

## More Challenges

- Consistency
- Crisis communications
- Reaching other audiences
- Evaluating the effectiveness of our communication program

## Some New Approaches

- Revamped Web site
- Risk Communication Advisory Committee
- Greater access to Subject Matter Experts (more interviews, editorial boards, tours of FDA science labs)
- Putting things into context
- Reaching out to science writers

## Summary

- Communications is a responsibility and
-    top priority for FDA
- High-level support in the agency
- A real will and desire to keep the public informed
- We welcome your advice and guidance
# Presentation: 277042

## Informing Airline Personnel

**Informing Airline Personnel**

**Notes:**
Section VII

## How Does the Dispatcher Facilitate CDM?

- The dispatcher, dispatch supervisor, or air traffic coordinator will monitor Advisories and EDCT reports.
- Pass any GDP/GS information on to the Captain & station personnel.

## What to tell the Captain during a  GDP

- What - Tell the Captain that there is a ground delay program for the specified airport.
- Why - Tell the Captain why there is a GDP.
- When - Tell the Captain what their EDCT is.

## Push Back Time

- Remember that the EDCT is the wheels up time.
- Therefore, estimate your taxi time and subtract it from the EDCT to get your push time.
- Example:   EDCT=2100z
- 			Taxi Time = 15 minutes
- 			Have the Captain push at 2045.

## What to tell the Captain when the EDCT changes

- A flight’s EDCT may change due to compression, a revision, or an airline substitution.
- Tell the Captain what the revised EDCT is.
- Tell the Captain the suggested taxi time.
- Tell the Captain to notify the ATC Tower and station of the new EDCT.
- Tower should “trust and verify.”
- Trust what the pilot is telling you.
- Verify the EDCT later.

## Exemption Policies

- Lifeguard Flights are exempt from the GDP.  ATCSCC has to be notified.  Lifeguard in RMKS doesn’t do it.
- International flights are exempted.
- Active flights are exempted.
- Remember exempted flights are assigned a slot and given control times but they should not receive a delay.

## What to tell the Captain during a GS

- What - Tell the Captain that there is a ground stop for the specified airport.
- Why - Tell the Captain why there is a GS.
- When - Tell the Captain when the ground stop is supposed to end and when to expect an update.
- The EDCT on the GS EDCT list report is an UPDATE time rather than a departure time.

## Slide 8